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
Exclusive IP Zone configuration for NIC agent
Following is the configuration example for Exclusive IP zone with NIC and IP resources. In the following sample, nic_value represents the base NIC name (for example, bge0) and zone_name is the name of the exclusive IP zone. (For more details about Zone resource configuration, refer to the Zone agent section.)
group grp1 ( SystemList = { sysA = 0 } ContainerInfo@sysA = { Name = zone_name, Type = Zone, Enabled = 1 } AutoStartList = { sysA } Administrators = { z_zone_res_sysA } ) IP ip_res ( Device = nic_value Address = "166.93.3.10" NetMask = "255.255.255.0" ExclusiveIPZone = 1 ) NIC nic_res ( Device = nic_value NetworkHosts = { "166.93.3.1" } ExclusiveIPZone = 1 ) Zone zone_res ( ) ip_res requires nic_res ip_res requires zone_res
Note that whenever a fault is detected for a NIC resource configured in an exclusive IP zone, perform the following steps to clear the fault.
- Repair the device configured with NIC resource. Verify that the device is healthy (check for cable connectivity, network connectivity, and so on).
- If the state of the exclusive IP zone on the system on which the NIC was faulted is:
Running: No action is required, and the next NIC monitor cycle will clear the fault after detecting the healthy NIC device.
NOT running: Clear the fault on the NIC device by invoking 'clearNICFaultInZone' action entry point for the NIC resource as follows:
# hares -action nic_res clearNICFaultInZone -sys sysA
Note:
When a NIC resource is configured for an Exclusive IP zone, Arctera recommends to set the ToleranceLimit attribute to a non-zero value.
With a NIC resource configured for an Exclusive IP zone, the NIC resource is monitored inside the zone when the zone is functional. While the zone is shutting down if the NIC monitor program is invoked, the monitor may falsely report the NIC resource as offline. This may happen if some of the networking services are offline but the zone is not completely shut down. Such reports can be avoided if you override and set the ToleranceLimit value to a non-zero value.
Calculate the ToleranceLimit value as follows: Time taken by a zone to completely shut down must be less than or equal to NIC resource's MonitorInterval value + (MonitorInterval value x ToleranceLimit value).
For example, if a zone takes 90 seconds to shut down and the MonitorInterval for NIC agent is set to 60 seconds (default value), set the ToleranceLimit value to 1.