InfoScale™ Cluster Server 9.0 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
- 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 and RHEL 8: NFS file system version
- RHEL 7 and RHEl 8: Configuring bind mounts
- Support for Amazon EFS
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- Mount agent limitations
- VMwareDisks agent
- SFCache agent
- AWS EBSVol agent
- AzureDisk agent
- GoogleDisk 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
- GoogleIP agent
- OCIIP agent
- File share agents
- About the file service agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- 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
- Using Application agent with IMF
- Level two monitoring through MonitorProgram
- Using Application agent with ProPCV
- Requirement for programs
- Requirement for default profile
- Support for cloned Application agent
- Application monitoring inside Docker container
- Using the hadockersetup utility
- Requirement for systemd support
- Sample configurations for Application agent
- Debug log levels for Application agent
- AppMonHB agent
- AzureAuth 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
- RestServer 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
AppMonHB agent
The AppMonHB agent integrates with the application and with VMware. It monitors the application states, and if the application is unable to come online or to recover from a failure, it uses the heartbeat mechanism to inform VMware of the state. Additionally, if the VM is in an unhealthy state, AppMonHB cannot heartbeat with VMware, which indicates that corrective action is required. VMware may then restart the VM or move it, according to the virtualization configuration in your environment. AppMonHB is designed to wait for a predefined, customizable duration before taking any corrective action in case a fault occurs in any of the critical service groups. If the faulted service groups come online within this duration, no corrective action is taken.
For details on application monitoring on single-node clusters, refer to the Cluster Server Administrator's Guide - Linux.
Table: Required attributes
Required attribute | Description |
|---|---|
Provider | Virtualization environment in which the single-node cluster is configured. This attribute is used as a switch to toggle between the supported virtualization environments. Type and dimension: string-scalar Default: VMware Note: As of now, only VMware is supported. |
ServiceGroupName | List of service groups for the agent to track. If a service group from this list faults and is unable to recover, the appropriate corrective action is triggered. Type and dimension: string-vector Default: No value |
WaitBeforeCorrectiveAction | Number of seconds to wait before any pending online or failover attempts are made. Thereafter, the possible corrective actions are evaluated. This duration provides a grace window so that agent does not rush to perform any corrective actions. Type and dimension: integer-scalar Default: 300 |
The resource type for the AppMonHB agent is defined in types.cf as follows:
type AppMonHB (
static int MonitorInterval = 10
static int NumThreads = 1
static int OfflineMonitorInterval = 10
static str ArgList[] = { ServiceGroupName, WaitBeforeCorrectiveAction, Provider }
static str Operations = None
str ServiceGroupName[]
int WaitBeforeCorrectiveAction = 300
str Provider = VMware
)The following sample from a main.cf file represents an application monitoring configuration in a single-node cluster.
group VCSAppMon (
SystemList = { hostname = 0 }
)
AppMonHB VCSAppMonRes (
ServiceGroupName = { Application_SG }
)