Setting a virtual IP on a specific Network interface with WebLogic 10.3.4 PS3

If you want High Availability in WebLogic you need to enable the WebLogic server migration, configure the nodemanager, use a virtual / floating IP in your managed servers and channels. For more information see my nodemanager blogpost.
Before PS3 you could only add a virtual IP on a pre-defined network interface and subnet mask, these fixed values are defined in the nodemanager.properties.

Example of the pre PS3 nodemanager.properties
Interface=eth0
NetMask=255.255.255.0

If you want to use more then one network interface you need to change the wlsifconfig.sh script in your WebLogic domain folder and check for the IP address and override the default interface and subnet mask.

For Exalogic, Oracle had to make this more flexible ( because of all the Exalogic infinity band switches, some are only used for specific network Channels traffic like replication etc ).  What you can see here. The documentation of these new nodemanager properties will soon be released


In WebLogic PS3 you can do the following scenarios. ( put this in the nodemanager.properties )

the old one, every Virtual IP is set on the eth0 interface with 255.255.255.0 as subnet mask
Interface=eth0
NetMask=255.255.255.0

or leave Interface / netmask empty and use the following
Interface=
NetMask=
eth0=*,Netmask=255.255.255.0

or combine these properties, in this case the eth1 interface will be used for Virtual IPs when it is in the range of 2 and 100 else the default eth0 interface will be used and the subnet mask is always 255.255.255.0
Interface=eth0
NetMask=255.255.255.0
eth1=10.10.10.2-10.10.10.100

or leave interface and netmask empty, in this example the eth0 interface will handle the 10.10.10.2 - 10.10.10.100 IP range with subnet  255.255.255.0 and eth1 200.10.10.2 - 200.10.10.100 with subnet 255.255.248.0
Interface=
NetMask=
eth0=10.10.10.2-10.10.10.100,NetMask=255.255.255.0
eth1=200.10.10.1-200.10.10.255,NetMask=255.255.248.0