Checklist to ensure the proper operation of MultiNICB
For the MultiNICB agent to function properly, you must satisfy each item in the following list:
-
Each interface must have a unique MAC address.
-
A MultiNICB resource controls all the interfaces on one IP subnet.
-
At boot time, you must configure and connect all the interfaces that are under the MultiNICB resource and give them test IP addresses.
-
All test IP addresses for the MultiNICB resource must belong to the same subnet as the virtual IP address.
-
Solaris: Reserve the base IP addresses, which the agent uses to test the link status, for use by the agent. These IP addresses do not get failed over.
-
Solaris: The IgnoreLinkStatus attribute is set to 1 (default) when using trunked interfaces.
-
If you specify the NetworkHosts attribute, then that host must be on the same subnet as the other IP addresses for the MultiNICB resource.
-
Solaris: Test IP addresses have "nofailover" and "deprecated" flags set at boot time.
-
Solaris: /etc/default/mpathd/
has TRACK_INTERFACES_ONLY_WITH_GROUPS=yes.
-
Solaris: If you are not using Solaris in.mpathd, all MultiNICB resources on the system have the UseMpathd attribute set to 0 (default). You cannot run in.mpathd on this system.
-
Solaris: If you are using Solaris in.mpathd, all MultiNICB resources on the system have the UseMpathd attribute set to 1.
-
AIX: If any network host is meant to respond to a broadcast ping, run
no -o bcastping = 1
on the network host.
-
AIX: You must use the AIX SMIT configuration tool to configure the test IP addresses and to make them persistent across reboots. If you do not use SMIT is to configure the IP addresses the agent may failover incorrectly.
-
Ensure that media speed settings are the same for both the interface and the corresponding switch port. Symantec recommends setting the media speed to 100 Mbps full duplex.