InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - AIX
- Introducing bundled agents
- Storage agents
- About the storage agents
- DiskGroup agent
- IMF awareness
- Support for online migration for DiskGroup agent
- Dependencies for DiskGroup agent
- Agent functions for DiskGroup agent
- State definitions for DiskGroup agent
- Attributes for DiskGroup agent
- Resource type definition
- Notes for DiskGroup agent
- Sample configurations for DiskGroup agent
- Debug log levels for DiskGroup agent
- DiskGroupSnap agent
- Dependencies for DiskGroupSnap agent
- Agent functions for DiskGroupSnap agent
- State definitions for DiskGroupSnap agent
- Attributes for DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Resource type definition for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Debug log levels for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Dependencies for VolumeSet agent
- Agent functions for VolumeSet agent
- State definitions for VolumeSet agent
- Attributes for VolumeSet agent
- Resource type definition for VolumeSet agent
- Sample configurations for VolumeSet agent
- Agent notes for VolumeSet agent
- Inaccessible volumes prevent the VolumeSet agent from coming online
- Debug log levels for VolumeSet agent
- LVMVG agent
- Dependencies for LVMVG agent
- Agent functions for LVMVG agent
- State definitions for LVMVG agent
- Attributes for LVMVG agent
- Resource type definition for LVMVG agent
- Notes for LVMVG agent
- Disks renamed after device renaming
- About the updatepv action
- LVMVG support in a VIO server environment
- Deactivation failure using the varyoffvg command on losing storage connectivity
- LVMVG Agent Supports JFS or JFS2
- Volume group needs to be imported
- Varyonvg options
- SyncODM Attribute
- Major Numbers
- Autoactivate Options
- LVMVG agent support for the Subsystem Device Driver (SDD)
- LVMVG agent support for the Hitachi's HiCommand Dynamic Link Manager (HDLM)
- LVMVG agent support for the EMC PowerPath
- The hadevice utility
- Removing a ghost disk from VxVM control
- Sample configuration for LVMVG agent
- Debug log levels for LVMVG agent
- Mount agent
- IMF awareness
- Dependencies for Mount agent
- Agent functions for Mount agent
- State definitions for Mount agent
- Attributes for Mount agent
- Resource type definition for Mount agent
- Notes for Mount agent
- High availability fire drill
- VxFS file system lock
- IMF usage notes
- IPv6 usage notes
- Bringing a Mount resource online in the WPAR
- Selecting the attribute values for a Mount resource for the WPAR's root file system for NFS mounts
- Support for namefs file system
- Taking a group with the Mount resource offline can take several minutes if the file system is busy
- Example 1
- Example 2
- Example 3
- Enabling Level two monitoring for the Mount agent
- Sample configurations for Mount agent
- Debug log levels 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
- Dependencies for IPMultiNICB agent
- Requirements for IPMultiNICB
- The haipswitch utility for IPMultiNICB agent
- Agent functions for IPMultiNICB agent
- State definitions for IPMultiNICB agent
- Attributes for IPMultiNICB agent
- Resource type definition for IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- Debug log levels for IPMultiNICB agent
- MultiNICB agent
- The haping utility for MultiNICB agent
- Dependencies for MultiNICB agent
- Agent functions for MultiNICB agent
- State definitions for MultiNICB agent
- Attributes for MultiNICB agent
- Resource type definition for MultiNICB agent
- Trigger script for MultiNICB agent
- Sample configurations for MultiNICB agent
- Debug log levels for MultiNICB agent
- DNS agent
- Dependencies for DNS agent
- Agent functions for DNS agent
- State definitions for DNS agent
- Attributes for DNS agent
- Resource type definition for DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- High availability fire drill for DNS agent
- Monitor scenarios for DNS agent
- Sample Web server configuration for DNS agent
- Secure DNS update for BIND 9 for DNS agent
- Setting up secure updates using TSIG keys for BIND 9 for DNS agent
- Sample configurations for DNS agent
- Debug log levels for DNS agent
- File share agents
- About the file service agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- The Samba agents
- Before using the Samba agents
- Supported versions for Samba agents
- Notes for configuring the Samba agents
- SambaServer agent
- Dependencies for SambaServer agent
- Agent functions for SambaServer agent
- State definitions for SambaServer agent
- Attributes for SambaServer agent
- Resource type definitions for SambaServer agent
- Notes for SambaServer agent
- Sample configurations for SambaServer agent
- Debug log levels for SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- About the services and applications agents
- Apache HTTP server agent
- Application agent
- IMF awareness
- High availability fire drill for Application agent
- Dependencies for Application agent
- Agent functions
- State definitions for Application agent
- Attributes for Application agent
- Resource type definition for Application agent
- Notes for Application agent
- Sample configurations for Application agent
- Debug log levels for Application agent
- CoordPoint agent
- LPAR agent
- Dependencies for LPAR agent
- Agent functions for LPAR agent
- State definitions for LPAR agent
- Required attributes for LPAR agent
- Optional attributes for LPAR agent
- Group attribute for LPAR agent
- System attribute for LPAR agent
- Resource type definition for LPAR agent
- Sample configurations for LPAR agent
- Notes for LPAR agent
- VCS requirements to manage the LPAR agent
- Configuring password-less SSH communication between VCS nodes and HMC
- Verifying password-less SSH status
- Live Partition Mobility support for LPARs managed by VCS
- Setting the SysDownPolicy attribute for the LPAR service group
- Configuring the LPAR agent for DR in a Global Cluster environment
- Debug log levels for LPAR agent
- MemCPUAllocator agent
- Dependencies
- Agent functions
- Attributes
- Resource type definition
- MemCPUAllocator agent notes
- Configuring password free SSH communication between VCS nodes and HMC
- Dynamic resource allocation scenarios
- Scenario 1: A DLPAR node has minimum resources
- Scenario 2: Bringing another service group online
- Scenario 3: DLPAR has required resources
- Scenario 4: Cannot allocate required resources
- Scenario 5: Service group failover
- Configuring MemCPUAllocator
- Debug log levels
- Process agent
- IMF awareness
- High availability fire drill for Process agent
- Dependencies for Process agent
- Agent functions for Process agent
- State definitions for Process agent
- Attributes for Process agent
- Resource type definition for Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- Debug log levels for Process agent
- ProcessOnOnly agent
- RestServer agent
- WPAR agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Attributes for Mount agent
Table: Required attributes
Required attribute | Description |
|---|---|
BlockDevice | Block device for mount point. When you specify the block device to mount, enclose IPv6 addresses in square brackets. The mount command requires square brackets around the IPv6 address to differentiate between the colons in the address and the colon that separates the remote host and remote directory. Note: If the block device to be mounted is renamed after device renaming, you must update the value of the BlockDevice attribute for Mount type resources. Type and dimension: string-scalar Examples:
|
FsckOpt | Mandatory for the following file systems types:
Use this attribute to specify options for the fsck command. You must correctly set this attribute for local mounts. If the mount process fails, the fsck command is executed with the specified options before it attempts to remount the block device. Its value must include either -y, -n, or -p. The -p option is only for jfs or jfs2 file systems on AIX. Refer to the fsck manual page for more information. For NFS mounts, the value of this attribute is not applicable and is ignored. Type and dimension: string-scalar Example: "-n" Example: "-y" Note: When you use the command line, add the % sign to escape '-'. For example: hares -modify MntRes FsckOpt %-y |
FSType | Type of file system. Supports jfs, jfs2, nfs, namefs, or vxfs. Type and dimension: string-scalar Example: "vxfs" |
MountPoint | Directory for mount point Type and dimension: string-scalar Example: "/tmp/mnt" |
Table: Optional attributes for AIX
Optional attribute | Description |
|---|---|
MountOpt | Options for the mount command. Refer to the mount manual page for more information. Do not set the VxFS mount option "mntlock=key". The agent uses this option only when bringing a Mount resource online. Type and dimension: string-scalar Example: "rw" |
SnapUmount | If the value of this attribute is 1, this attribute automatically unmounts VxFS snapshots when the file system is unmounted. If the value of this attribute is 0, and snapshots are mounted, the resource cannot be brought offline. In this case, failover does not occur. Type and dimension: integer-scalar Default: 0 |
CkptUmount | If the value of this attribute is 1, this attribute automatically unmounts VxFS Storage Checkpoints when file system is unmounted. If the value of this attribute is 0, and Storage Checkpoints are mounted, then failover does not occur. Type and dimension: integer-scalar Default: 1 |
AccessPermissionChk | If the value of this attribute is 1 or 2, the monitor verifies that the values of the MntPtPermission, MntPtOwner, and MntPtGroup attributes are the same as the actual mounted file system values. If any of these do not match the values that you have defined, a message is logged. If the value of this attribute is 2, and if the mounted file system permissions do not match the attribute values, the Monitor agent function returns the state as OFFLINE. Type and dimension: integer-scalar Default: 0 |
CreateMntPt | If the value of this attribute is 0, no mount point is created. The mount can fail if the mount point does not exist with suitable permissions. If the value of this attribute is 1 or 2, and a mount point does not exist, the agent creates a mount point with system default permissions when the resource is brought online. If the permissions for the mount point are less than 555, a warning message is logged. If the value of this attribute is 2, and the mount point does not exist, the agent creates a mount point with system default permissions when the resource is brought online. If the permissions for the mount point are less than 555, a warning message is logged. In addition, VCS deletes the mount point and any recursively created directories when the resource is brought offline. The mount point gets deleted only if it is empty, which is also true for recursive mount points. Type and dimension: integer-scalar Default: 0 |
MntPtGroup | This attribute specifies the group ownership of the mounted file system. The agent verifies the group ownership of the mounted file system every monitor cycle if the value of the AccessPermissionChk attribute is not 0. Type and dimension: string-scalar Example: "grp1" |
MntPtOwner | This attribute specifies the user ownership of the mounted file system. The agent verifies the user ownership of the mounted file system every monitor cycle if the value of the AccessPermissionChk attribute is not 0. Type and dimension: string-scalar Example: "usr1" |
MntPtPermission | This attribute specifies the permissions of the mounted file system in an absolute format of a four-digit octal. The agent verifies the mode of the mounted file system every monitor cycle if the value of the AccessPermissionChk attribute is not 0. Type and dimension: string-scalar Example: "0755" |
OptCheck | The value of this attribute determines if VCS should verify the mount options. The state of the resource is determined based on the result of the verification. If the value of this attribute is 0 (default), the mount options are not checked. If the value of the OptCheck attribute is 1, 2 or 3, a check is performed to see if the mount command options that you have specified for VCS are set in the MountOpt attribute. The MountOpt attributes should be the same as the actual mount command options. If the actual mount options differ from the MountOpt attribute, a message is logged. The state of the resource depends on the value of this attribute. If the value of the attribute is 1, the state of the resource is unaffected. If the value is 2, the state of the resource is set to offline. If the value is 3, state of the resource is set to unknown. Type and dimension: integer-scalar Default: 0 |
RecursiveMnt | If the value of this attribute is 1, VCS creates all the parent directories of the mount point if necessary. Type and dimension: boolean-scalar Default: 0 |
ReuseMntPt | If the same mount point needs to be specified in more than one mount resource, set the value of this attribute to 1. Note that this attribute only accepts a value of 1 or 0. To use this attribute, the cluster administrator needs to add this attribute to the ArgList resource type attribute of the agent. Set the appropriate group and resource dependencies such that only one resource can come online on a system at a time. Type and dimension: integer-scalar Default: 0 |
VxFSMountLock | This attribute is only applicable to File System (VxFS). This attribute controls a file system locking feature to prevent accidental unmounts. This attribute can take three values: 0, 1, or 2. VxFSMountLock=0 The resource does not detect any changes to the lock when VCS reports that it is online after you set the value to zero.
VxFSMountLock=1 The resource does not detect changes to the lock when VCS reports it online after the value was set to one. VCS does not monitor the lock.
VxFSMountLock=2 When the value of the VxFSMountLock is 2, the file system is locked and the agent monitors any change to mntlock.
Type and dimension: integer-scalar Default: 1 |
CacheRestoreAccess | This attribute is applicable only if:
The value of this attribute determines whether to perform restore access operation or not. Following are the values:
Type and dimension: boolean-scalar Default: 0 Note: For the procedure and implications of enabling writeback caching, refer to the InfoScale SmartIO for Solid State Drives Solutions Guide. |
Table: Internal attribute
Internal attribute | Description |
|---|---|
AEPTimeout | This is an internal attribute. Do not modify this attribute. This attribute is used to pass the timeout value of agent entry points. |