Cluster Server 7.3.1 Bundled Agents Reference Guide - Linux
- Introducing Bundled agents
- Storage agents
- About the storage agents
- 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
- LVMLogicalVolume agent
- LVMVolumeGroup agent
- Dependencies for LVMVolumeGroup agent
- Agent functions for LVMVolumeGroup agent
- State definitions for LVMVolumeGroup agent
- Attributes for LVMVolumeGroup agent
- Resource type definition for LVMVolumeGroup agent
- LVMVolumeGroup agent notes
- Enabling volume group activation protection for Dynamic Multi-Pathing
- Notes for volume group activation protection
- Sample configurations for LVMVolumeGroup agent
- Debug log levels for LVMVolumeGroup 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
- Support for spaces in directory names
- Support for multiple bindfs
- High availability fire drill
- VxFS file system lock
- IMF usage notes
- Enabling Level two monitoring for the Mount agent
- RHEL 7: NFS file system version
- RHEL 7: Configuring bind mounts
- Support for Amazon EFS
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- VMwareDisks agent
- SFCache agent
- AWS EBSVol agent
- AzureDisk agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- Dependencies for NIC agent
- Bonded network interfaces for NIC agent
- Agent functions for NIC agent
- State definitions for NIC agent
- Attributes for NIC agent
- Resource type definition for NIC agent
- Notes for the NIC agent
- Case 1
- Case 2
- Case 3
- Sample configurations for NIC agent
- Debug log levels for NIC agent
- IPMultiNIC agent
- MultiNICA agent
- Dependencies for MultiNICA agent
- IP Conservation Mode (ICM) for MultiNICA agent
- Performance Mode (PM) for MultiNICA agent
- Agent function for MultiNICA agent
- Attributes for MultiNICA agent
- Resource type definition for MultiNICA agent
- Sample configurations for MultiNICA agent
- IPv6 configuration for MultiNICA agent
- Mixed mode configuration - IPv4 and IPv6 for MultiNICA agent
- Debug log levels for MultiNICA 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
- AWSIP agent
- AWSRoute53 agent
- AzureIP agent
- AzureDNSZone agent
- File share agents
- About the file service agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- 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 on Linux
- Resource type definition for Application agent
- Notes for Application agent
- Sample configurations for Application agent
- Debug log levels for Application agent
- CoordPoint agent
- KVMGuest agent
- Dependencies for KVMGuest agent
- Agent functions for KVMGuest agent
- State definitions for KVMGuest agent
- Attributes for KVMGuest agent
- Resource type definition for KVMGuest agent
- Notes for KVMGuest agent
- Support for guests created on RHEL 6, RHEL 7 (KVM environment), and SuSE Enterprise Linux 11 SP2 and SP3
- Storage and network configurations
- Guest live migration
- Managing virtual machines in RHEV environment
- Managing ISO image in SuSE KVM
- Using VCS to migrate virtual machines
- Configuring the KVMGuest agent for DR in a global cluster setup
- Configuring a non-admin user for RHEV-M that is using AD-based domain
- Virtual machine failover if host crashes
- KVMGuest agent requires curl and xpath commands in RHEV environment
- RHEV environment: If a node on which the VM is running panics or is forcefully shutdown, VCS is unable to start the VM on another node
- Sample configurations for KVMGuest environment
- Sample configurations for RHEV environment
- Sample Configuration for SuSE KVM
- Debug log levels for KVMGuest agent
- 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
- AzureAuth agent
- Infrastructure and support agents
- Testing agents
- Replication agents
- About the replication agents
- RVG agent
- RVGPrimary agent
- RVGSnapshot
- RVGShared agent
- RVGLogowner agent
- RVGSharedPri agent
- VFRJob agent
- Overview
- Dependencies for VFRJob agent
- High availability of scheduler and replicator daemons
- Agent functions for VFRJob agent
- State definitions for VFRJob agent
- Attributes for VFRJob Agent
- Resource type definitions for VFRJob agent
- High availability of VFR daemons
- Configuration of VFRJob service groups on the source system
- Sample configuration of VFRJob agent on source system
- Configuration for VFRJob service groups on the target system
- Sample configuration of VFRJob agent on target system
- Changing file replication direction
- Notes for the VFRJob agent
Attributes for Mount agent
Table: Required attributes
Required attribute | Description |
|---|---|
BlockDevice | Block device for mount point. For LVM2, use the actual mapper path to the volume. Type and dimension: string-scalar Examples:
|
FsckOpt | Mandatory for non-NFS mounts. 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 or -n. Refer to the fsck manual page for more information. The -y argument enables the VxFS file systems to perform a log replay before a full fsck operation. For NFS mounts, the value of this attribute is not applicable and is ignored. Type and dimension: string-scalar VxFS 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 vxfs, bind, ext2, ext3, ext4, xfs, nfs, or reiserfs. Type and dimension: string-scalar |
MountPoint | Directory for mount point. Type and dimension: string-scalar Example: "/mnt/apache1" |
Table: Optional attributes
Optional attribute | Description |
|---|---|
CkptUmount | If the value of this attribute is 1, this attribute automatically unmounts VxFS Storage Checkpoints when the 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: boolean-scalar Default: 1 |
MountOpt | Options for the mount command. Refer to the Mount manual page for more information. Do not specify -o in the MountOpt field. The agent uses this option only when bringing a Mount resource online. Type and dimension: string-scalar Example: "rw" |
VxFSMountLock | This attribute is applicable to Veritas File System (VxFS). It controls the agent's use of the locking feature provided by vxfs to prevent accident unmounts. If the value of this attribute is 0, the agent does not lock the mount point when the resource is brought online. It does not monitor the status of the lock when the resource is online. No warnings appear if the mount has been locked with a key different than "VCS". If the value of this attribute is 1, during online, the agent uses the key "VCS" to lock the mount point. The monitor agent function monitors the locks during every cycle.
During offline, the agent, as required, unlocks using whatever key needed. Type and dimension: boolean-scalar Default: 1 |
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: boolean-scalar Default: 0 |
AccessPermissionChk | If the value of this attribute is set to 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 of the mount point is 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 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 set to 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 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 |
CacheRestoreAccess | This attribute is applicable only if:
The value of this attribute determines whether to perform restore access operation or not. The following are the values:
Type and dimension: boolean-scalar Default: 0 Note: For the procedure and implications of enabling writeback caching, refer to the Veritas 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. |