We are moving our SAP landscape towards a virtualized SAP environment by using application virtualization and SAP LVM. To enable this we are installing our Netweaver ASs as a 'distributed installations' on virtual hostnames and virtual IP addresses.
By this, a SAP System consists of one physical resource (host and OS) and two services (DB and central instance). The services are running on the virtual hostnames and IP-addresses.
The following example shows the describes scenario:
In this example, the host tl-sap17 owns 3 IP-Adresses and hostnames at a time wheen both services are running on it. (OS is Windows 2008 R2 x64)
The following behaviour of the Netweaver AS is a problem in this concept in our opinion:
All outgoing TCP connections are binded to the IP of the physical host. This means that RFC-Connections to other systems are initiated by 10.244.40.119 which is wrong. The connections should be owned by 10.244.40.118, the central instance which is the application server.
We are facing different problems with our Network Administration associated whith firewall-rules etc.
Is there a way to configure the TCP binding behaviour of the WebAS just like in many other software products?