Cluster Server 8.0.2 Administrator's Guide - AIX
- 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
- 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 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 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
Starting VCS in a customized environment
Depending on the needs of your environment, you may want to perform a series of tasks before you start the VCS engine. For example, before you run hastart, you may want to move certain files to different locations, or you may want to perform some clean up tasks.
InfoScale Availability lets you configure the following files to customize your VCS startup environment and to customize how the VCS engine is started.
To disable the custom scripts, remove the scripts from the $VCS_HOME/bin
folder, or remove the execute permissions on those files.
pre_hastart
To define the custom code to be called before hastart, do one of the following:
Create the
pre_hastart
script in the$VCS_HOME/bin
folder.Alternatively, create a copy of the sample script file that is provided in the
$VCS_HOME/bin/sample_scripts/VRTSvcs
folder. Modify the script as appropriate and place the file in the$VCS_HOME/bin
folder.
The sample script contains sample code and return value translations. Use it as reference and modify the values to suit the needs of your environment.
Ensure that the script has executable permissions and that its file size is greater than 0 bytes. If these conditions are not met, the script is not executed before hastart.
Ensure that the custom script follows the return value specifications that are mentioned in the sample script.
Check the service logs for messages that are logged by the custom script.
custom_vcsenv
Create the custom_vcsenv
file to define custom values for the VCS environment variables and place it in the $VCS_HOME/bin
folder.
To set a variable, use the syntax that is appropriate for the shell in which VCS starts. For example, typically, VCS starts in /bin/sh
, so you can define the variables as:
VCS_GAB_TIMEOUT = 35000;export VCS_GAB_TIMEOUT
These variables are set for VCS when the hastart command is run.
custom_had_start
The hastart
script calls the custom script to start the had
binary.
To define the custom code to be called before hastart, do one of the following
Create the
custom_had_start
script in the$VCS_HOME/bin
folder.Alternatively, create a copy of the sample script file that is provided in the
$VCS_HOME/bin/sample_scripts/VRTSvcs
folder. Modify the script as appropriate and place the file in the$VCS_HOME/bin
folder.
The sample script contains sample code and return value translations. Use it as reference and modify the values to suit the needs of your environment.
Ensure that the script has executable permissions and that its file size is greater than 0 bytes. If these conditions are not met, HAD startup is performed in the default manner.
Ensure that the custom script follows the return value specifications that are mentioned in the sample script.
Check the service logs for messages that are logged by the custom script.
Define appropriate log messages to determine whether the HAD daemon is started using the $VCS_HOME/bin/custom_had_start
script.