InfoScale™ 9.0 Cluster Server Administrator's Guide - Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- About application monitoring on single-node clusters
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VI. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- VCS message logging
- VCS performance considerations
- Section VII. Appendixes
Configuring application monitoring on a single-node cluster
The ConfigAppMonHB
utility lets you configure HA for applications in single-node cluster deployments, which includes the application service groups and the AppMonHB agent resources.
At the vCenter level, make sure that:
The vSphere HA > VM Monitoring > VM and Application Monitoring options are enabled.
At least one heartbeat datastore is configured for vSphere HA.
To configure application monitoring on a single-node cluster
- Using the CLI, navigate to the
$VCS_HOME/bin/AppMonHB
directory and run the ConfigAppMonHB command.The default file location is
/opt/VRTSvcs/bin/AppMonHB/ConfigAppMonHB
. - When prompted, enter E as the option to enable application monitoring on the node.
To configure monitoring for all the service groups in the cluster
- When prompted, enter A to enable application monitoring for all the service groups configured on the node.
If any required groups or resources are not present in the local cluster, the utility prompts you for further action:
To append the missing entities to the existing service groups in the cluster, enter A.
To add the missing entities as per your preference and reset the cluster, enter R.
To configure monitoring only for specific service groups in the cluster
- When prompted, enter S to enable application monitoring for a selective set of service groups configured on the node.
Note:
You can also use this option to selectively discontinue monitoring the application service groups that you specify.
- When prompted, enter the names of only those service groups that you want to monitor, separated by spaces; for example, SG1 SG2 SG3.
The utility repeats the names of the service groups that you specified and then displays the names of the service groups that may have already been configured for monitoring.
- When prompted, specify your preference:
To append to the list of existing service groups being monitored, enter A.
To reset the configuration and monitor only those service groups that you specified in the previous step, enter R.
To specify the duration after which corrective action is taken
- When the utility prompts you to update the WaitBeforeCorrectiveAction duration:
To use the default value of 300 seconds, enter N.
To specify a custom value, enter Y.
When prompted, enter the value in seconds, for example 30.
Alternatively, you can change the duration by running the following sequence of commands on the node at any later time:
# haconf -makerw
# hares -modify VCSAppMonRes WaitBeforeCorrectiveAction <integer value in seconds>
# haconf -dump -makero