Virtual Ethernet environment offers various advantages and flexibility, but you should be aware of the challenges. The various independent clusters consisting of VIO client partitions in the same physical computer can be configured with the heartbeat routed through the same physical Ethernet adapters to additional nodes outside the physical computer. Ensure that each cluster has a unique cluster ID. Unique cluster IDs eliminate conflict and allow the Virtual Ethernet environment to greatly reduce the required number of physical Ethernet adapters. According to IBM, there are issues to be aware that are not the fault of the applicable Cluster Management Software or the configuration. Rather, the issues arise as a direct consequence of I/O virtualization.
To reiterate, although some of these may be viewed as configuration restrictions, many are direct consequences of I/O Virtualization.
The issues and recommendation are as follows:
If two or more Clustered nodes use a VIO server or servers in the same frame, the Cluster Management Software cannot detect and react to single physical interface failures. This behavior does not limit the availability of the entire cluster because VIOS itself routes traffic around the failure. The behavior of the VIOS is analogous to AIX the EtherChannel. Notification of individual Adapter failures must use other methods (not based on the VIO server) .
All Virtual Ethernet interfaces that are defined to the Cluster Management Software should be treated as "single-Adapter networks" according to IBM. To correctly monitor and detect failure of the network interface, you must create a file that includes a list of clients to ping. Due to the nature of Virtual Ethernet, other mechanisms to detect the failure of network interfaces are not effective.
If the VIO server has only a single physical interface on a network, then the Cluster Management Software can detect a failure of that interface. However, that failure isolates the node from the network.
Check the IBM documentation for detailed information on the Virtual Ethernet and various configuration scenarios using virtual I/O Server. For information about the above issues, see the following link:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10390