InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Disk agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- Mount agent
- Sample configurations for Mount agent
- Zpool agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- MultiNICB agent
- Sample configurations for MultiNICB agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- NetBios agent
- Service and application agents
- AlternateIO agent
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- LDom agent
- Dependencies
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- Project agent
- RestServer agent
- Zone agent
- Infrastructure and support agents
- Testing agents
- Replication agents
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 base IP addresses.
All base IP addresses for the MultiNICB resource must belong to the same subnet as the virtual IP address.
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.
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 base IP addresses for the MultiNICB resource.
Test IP addresses have "nofailover" and "deprecated" flags set at boot time.
/etc/default/mpathd has TRACK_INTERFACES_ONLY_WITH_GROUPS=yes.
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.
If you are using Solaris in.mpathd, all MultiNICB resources on the system have the UseMpathd attribute set to 1.