Cluster Server 7.4.1 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
- 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
- Predicting VCS behavior using VCS Simulator
- 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. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. 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
- 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 VII. 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
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
VCS environment variables
See Environment variables to start and stop VCS modules.
Table: VCS environment variables
Environment Variable | Definition and Default Value |
---|---|
PERL5LIB | Root directory for Perl executables. (applicable only for Windows) Default: Install Drive:\Program Files\VERITAS\cluster server\lib\perl5. |
VCS_CONF | Root directory for VCS configuration files. Default: /etc/VRTSvcs Note: You cannot modify this variable. |
VCS_CONN_INIT_QUOTA | Maximum number of simultaneous connections accepted by the VCS engine (HAD) per client host that has not completed the handshake. |
VCS_CONN_HANDSHAKE_TIMEOUT | Timeout in seconds after which the VCS engine (HAD) closes the client connection that has not completed the handshake. |
VCS_DEBUG_LOG_TAGS | Enables debug logs for the VCS engine, VCS agents, and HA commands. You must set VCS_DEBUG_LOG_TAGS before you start HAD or before you execute HA commands. See Enabling debug logs for the VCS engine. You can also export the variable from the |
VCS_DOMAIN |
The Security domain to which the VCS users belong. The VCS Authentication Service uses this environment variable to authenticate VCS users on a remote host. Default: Fully qualified host name of the remote host as defined in the VCS_HOST environment variable or in the .vcshost file. |
VCS_DOMAINTYPE |
The type of Security domain such as unixpwd, nt, nis, nisplus, ldap, or vx. The VCS Authentication Service uses this environment variable to authenticate VCS users on a remote host. Default: unixpwd |
VCS_DIAG | Directory where VCS dumps HAD cores and FFDC data. |
VCS_ENABLE_LDF | Designates whether or not log data files (LDFs) are generated. If set to 1, LDFs are generated. If set to 0, they are not. |
VCS_HOME | Root directory for VCS executables. Default: /opt/VRTSvcs Note: You cannot modify this variable. |
VCS_HOST | VCS node on which ha commands will be run. |
VCS_GAB_PORT | GAB port to which VCS connects. Default: h |
VCS_GAB_TIMEOUT | Timeout in milliseconds for HAD to send heartbeats to GAB. Default: 30000 (denotes 30 seconds) Range: 30000 to 300000 (denotes 30 seconds to 300 seconds) If you set VCS_GAB_TIMEOUT to a value outside the range, the value is automatically reset to 30000 or 300000, depending on the proximity of the value to the lower limit or upper limit of the range. For example, the value is reset to 30000 if you specify 22000 and to 300000 if you specify 400000. Irrespective of the values set, VCS_GAB_TIMEOUT_SECS overrides VCS_GAB_TIMEOUT if both are specified. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_TIMEOUT_SECS | Timeout in seconds for HAD to send heartbeats to GAB under normal system load conditions. Default: 30 seconds Range: 30 seconds to 300 seconds If you set VCS_GAB_TIMEOUT_SECS to a value outside the range, the value is automatically reset to 30 or 300, depending on the proximity of the value to the lower limit or upper limit of the range. For example, the value is reset to 30 if you specify 22 and to 300 if you specify 400. Irrespective of the values set, VCS_GAB_TIMEOUT_SECS overrides VCS_GAB_TIMEOUT if both are specified. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_PEAKLOAD_TIMEOUT_SECS | Timeout in seconds for HAD to send heartbeats to GAB under peak system load conditions. Default: 30 seconds Range: 30 seconds to 300 seconds To set the GAB tunables in adaptive mode, you must set VCS_GAB_PEAKLOAD_TIMEOUT_SECS to a value that exceeds VCS_GAB_TIMEOUT_SECS. If you set VCS_GAB_PEAKLOAD_TIMEOUT_SECS to a value that is lower than VCS_GAB_TIMEOUT_SECS, it is reset to VCS_GAB_TIMEOUT_SECS. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_RMTIMEOUT | Timeout in milliseconds for HAD to register with GAB. Default: 200000 (denotes 200 seconds) If you set VCS_GAB_RMTIMEOUT to a value less than 200000, the value is automatically reset to 200000. |
VCS_GAB_RMACTION | Controls the GAB behavior when VCS_GAB_RMTIMEOUT exceeds. You can set the value as follows:
Default: SYSLOG |
VCS_HAD_RESTART_TIMEOUT | Set this variable to designate the amount of time the hashadow process waits (sleep time) before restarting HAD. Default: 0 |
VCS_LOG | Root directory for log files and temporary files. You must not set this variable to "" (empty string). Default: /var/VRTSvcs Note: If this variable is added or modified, you must reboot the system to apply the changes. |
VCS_SERVICE | Name of the configured VCS service. The VCS engine uses this variable to determine the external communication port for VCS. By default, the external communication port for VCS is 14141. The value for this environment variable is defined in the service file at the following location: /etc/services Default value: vcs If a new port number is not specified, the VCS engine starts with port 14141. To change the default port number, you must create a new entry in the service file at: /etc/services For example, if you want the external communication port for VCS to be set to 14555, then you must create the following entries in the services file: vcs 14555/tcp vcs 14555/udp Note: The cluster-level attribute OpenExternalCommunicationPort determines whether the port is open or not. See Cluster attributes. |
VCS_TEMP_DIR | Directory in which temporary information required by, or generated by, hacf is stored. Default: /var/VRTSvcs This directory is created in the
|
More Information