InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - AIX
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- Notes for DiskGroup agent
- Sample configurations for DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- LVMVG agent
- Notes for LVMVG agent
- Mount agent
- Sample configurations for Mount agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- IPMultiNIC agent
- MultiNICA 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
- Notes for configuring the Samba agents
- SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- LPAR agent
- Notes for LPAR agent
- MemCPUAllocator agent
- MemCPUAllocator agent notes
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- RestServer agent
- WPAR agent
- Infrastructure and support agents
- Testing agents
- Replication agents
SCSI-3 based disk as a coordination point
In case the coordination point is a SCSI-3 based disk, the CoordPoint agent uses the vxfenadm command to confirm that the registered keys on the disk are intact. The Monitor agent function contains the monitoring functionality for SCSI-3 disks and CP servers.
If the agent detects an anomaly, the agent reports it to you so you can repair the coordination point. You may have to perform an online coordinator point replacement procedure if the problem is isolated to the keys registered or you can repair the coordination points automatically (if some keys are missing on one or more coordination points) by configuring the ActionOnCoordPointFault
attribute. For more information on using the attribute, refer to the Attributes section.
Note:
The CoordPoint agent that runs on a given client cluster node monitors the keys for coordination points visible to that node alone.
For important information about this agent, refer to:
More Information