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
Required attributes for LPAR agent
Table:
Required attribute | Description |
---|---|
LPARName | Name of the logical partition (LPAR). Type-dimension: string-scalar Default: NA Example: "lpar1" |
MCName | Names of the HMCs that manage LPARs. The value of this attribute cannot be local to a management LPAR because all LPARs in a VCS cluster must use the same HMC names. Note: The value is a string that can be IPv4 or IPV6 addresses or host names of HMCs. Type-dimension: string-keylist Default: NA Example: { hmc1, hmc2 } |
MCUser | Names of the users to communicate with HMCs using password-less SSH. You must provide the MCName and MCUser value pairs in the proper order. For example, if you specify MCName as { hmc1, hmc2 } and MCUser as { hmcuser1, hmcuser2 }, hmcuser1 can communicate with hmc1 and hmcuser2 can communicate with hmc2. Type-dimension: string-keylist Default: { hscroot } Example: { hmcuser1, hmcuser2 } |