Please enter search query.
Search <book_title>...
InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - AIX
Last Published:
2025-04-14
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Setting the SysDownPolicy attribute for the LPAR service group
Arctera recommends to set the SysDownPolicy attribute for the LPAR service group. If the SysDownPolicy attribute is not set and the managed LPAR on one system goes down (but the physical server and managed LPAR are alive), VCS tries to start the managed LPAR on the other node. If the managed LPAR configuration exists on the other node, it leads to concurrency violation and might corrupt the managed LPAR data.