SFHA Solutions 6.0.1: Starting Veritas Cluster Server

Veritas Cluster Server (VCS) startup depends on the kernel-space modules and other user-space modules starting in a specific order. You can start VCS using the installvcs –start command, or by manually starting VCS either on a single-node cluster or on each node of a cluster. The command to start VCS is typically initiated at system startup. When you start VCS, it checks the state of its local configuration file and registers with GAB for cluster membership. If the local configuration is valid, and if no other system is running VCS, it builds its state from the local configuration file and enters the RUNNING state.

To start VCS using the installvcs -start command, perform the following steps on any node in the cluster:

1. Log in as the root user.  
2. Enable password-less communication (rsh Remote Shell or ssh Secure Shell). For information on how to set up password-less communication, see:

• How to setup passwordless SSH
• Enabling rsh for Linux
• Manually configuring passwordless ssh

3. Run the following command:
   # /opt/VRTS/install/installvcs –start

To start VCS manually on a single-node cluster:

1. Log in as the root user.  
2. Start the VCS engine by running the following command: 
   # hastart –onenode

To start VCS manually on each node of a cluster:

1. Log in as the root user.
2. Start the Low Latency Transport (LLT) and Group Atomic and Broadcast (GAB). Start I/O fencing if you have configured it. The LLT, GAB, I/O fencing, and AMF (optional) processes must be started before manually starting the VCS engine.
   To start LLT:
   # /etc/init.d/llt.rc start
   To start GAB:
   # /etc/init.d/gab.rc start
   To start I/O fencing:
   # /etc/init.d/vxfen.rc start
   Optionally, you can start Asynchronous Monitoring Framework (AMF) if you want to enable intelligent monitoring.
   To start AMF:
   # /etc/init.d/amf.rc start
3. Start the VCS engine:
   # hastart

• Reconfiguring VCS on the existing node
• Adding the node to the existing cluster
• Creating a single-node cluster manually
• Migrating from non-secure to secure setup for CP server and VCS cluster communication
• Configuring the VXFEN module parameters
• Setting up disk-based I/O fencing manually
• Applying or backing out VCS patches
• You manually remove any resource types or modify attributes on a local node, and then you stop VCS on all the nodes and start VCS first on the local node where the configuration is edited.

For more information on how to start VCS, see:

• Starting VCS
• About the Veritas Cluster Server (VCS) startup sequence
• Starting the VCS engine (HAD) and related processes

hastart (1M) manual pages:

• AIX
• HP-UX
• Linux
• Solaris

Veritas Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.