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
Optional attributes for LPAR agent
Table:
Optional attributes | Description |
---|---|
ProfileName | Name of the profile used to start LPAR. If you do not provide the profile name, the agent uses the default profile. Type-dimension: string-scalar Default: NA Example: {lpar1} |
VIOSName | Names of the virtual input output servers (VIO servers) that provide virtual resources to the LPAR. If there are multiple VIO servers available for an LPAR, you must specify names of all the VIO servers in the attribute so that VCS does not treat the LPAR as faulted till all the VIO servers go down. If one VIO server fails, LPARs can perform input and output operations through the other VIO servers. When all the VIO servers specified in the VIOSName attribute are down, VCS fails over the managed LPAR to another system. If you do not specify VIOSName, the LPAR agent does not fail over the LPAR after a VIO server crash. Type-dimension: string-keylist Default: NA Example: {vios1, vios2 } |
ProfileFile | Absolute path of the LPAR profile file on the management LPAR. Type-dimension: string-scalar Default: NA Example: "/config/lpar-profile.profile" For the steps to create a profile file, refer to the InfoScale Virtualization Guide for AIX. |
RemoveProfileOnOffline | If this attribute is set to 1, LPAR configuration and its VIOS mappings (as specified in the profile file present in the path mentioned in the ProfileFile attribute) are deleted after the LPAR resource is brought offline or is faulted. Type-dimension: boolean-scalar Default: 0 |
DROpts | Defines the DR options. The value of this attribute consists of the following keys:
If any of the keys are not specified or have default value, the vcsnr script retains all the configuration that is inside the LPAR on which this script is installed. Type and dimension: string-association |