virtual IP for outbound communication

[Former Member]

Dear All,

The system uses physical IP for outbound communication

instead of virtual one, despite we explicitely maintain parameters :

SAPLOCALHOST

SAPLOCALHOSTFULL

We found out a parameter to force the ABAP gateway to virtual

IP, parameter : gw/local_addr

It works, but is valid only for RFC calls out of the ABAP gateway.

ICM and other communication components, like the advanced adapter engine

still use the physical one. In this situation, SAP servers are not decoupled securely and permanently

from their physical network identities as described in

Note 962955 - Use of virtual TCP/IP host

Do you have a solution?

KR,

Laurent

[Former Member]

Hi,

Initially FW was open for virtual source IP only.

But connection failed.

Output from netstat -an showed that it was effectively using physical.

FW rules are maintained for 3 IP : 1 virtual and 2 physical (cluster).

KR,

Laurent

[Former Member]

Hi Laurent

I've got the same problem: telnet connection to sapms port is ok only for physical ip, but not for virtual.

Did you solve the issue?

[Former Member]

Hi,

Thx, but all systems were installed with virtual hostname.

sapinst -nogui SAPINST_USE_HOSTNAME=<virtual_hostname>

You are right, from SM51 all hosts and instances point to the virtual

name but still outbound comm use physical one.

KR,

Laurent

[markus_doehr2]

> Thx, but all systems were installed with virtual hostname.

> sapinst -nogui SAPINST_USE_HOSTNAME=<virtual_hostname>

> You are right, from SM51 all hosts and instances point to the virtual

> name but still outbound comm use physical one.

Where do you see that? using "netstat -an"?

Are the target machines (to be reached via virtual interface) also reachable using the physical interface?

Markus

[markus_doehr2]

You have to "install" the system using a virtual IP - then you can completely separate the virtual from the physical IP.

Note 1282975 - Use of virtual TCP/IP host names in Windows

Markus