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
Solaris 11: Change of behavior in IPv4 and IPv6 interface state
On Solaris 11, ipadm and ifconfig commands are supported, but the OS recommends to use the ipadm command for managing IP and NIC. The ifconfig command allows IPv4 and IPv6 IPs to be plumbed only after the NIC is plumbed for the respective protocol. Therefore, to plumb an IPv4 address, NIC has to be plumbed for IPv4 and to plumb an IPv6 address, NIC has to be plumbed for IPv6.
Prior to VCS 6.2, on Solaris 11, the NIC agent used to monitor the IPv4-specific-NIC or IPv6-specific-NIC configured using the Protocol attribute of the NIC resource. In VCS 6.2 and going forward, the NIC agent will use the ipadm command to monitor the network interface.
The ipadm command does not distinguish between the NIC plumbed for IPv4 or IPv6. If any IP (IPv4 or IPv6) is brought online on the NIC interface, the ipadm command shows the interface as online. This change of behavior is also reflected in the NIC agent. Hence, VCS 6.2 onwards, if the NIC has an active IPv4 IP and no IPv6 IP, the IPv6 NIC resource detects the NIC as online. Similarly, if the NIC has an active IPv6 IP and no IPv4 IP, the IPv4 NIC resource detects the NIC as online.