Veritas Cluster Cheat Sheet
Veritas Cluster Cheat Sheet
Veritas Cluster Cheat Sheet
VCS uses two components, LLT and GAB to share data over the private networks among systems.
These components provide the performance and reliability required by VCS.
LLT (Low Latency Transport) provides fast, kernel-to-kernel comms and monitors network connections. The
LLT system admin configures the LLT by creating a configuration file (llttab) that describes the systems in the cluster
and private network links among them. The LLT runs in layer 2 of the network stack
GAB (Group membership and Atomic Broadcast) provides the global message order required to maintain a
GAB synchronised state among the systems, and monitors disk comms such as that required by the VCS heartbeat utility.
The system admin configures GAB driver by creating a configuration file ( gabtab).
/etc/llthosts The file is a database, containing one entry per system, that links the LLT system ID with the hosts name. The file
is identical on each server in the cluster.
/etc/llttab The file contains information that is derived during installation and is used by the utility lltconfig.
/etc/gabtab The file contains the information needed to configure the GAB driver. This file is used by the gabconfig utility.
/etc/VRTSvcs/conf/config/main.cf The VCS configuration file. The file contains the information that defines the cluster and its systems.
Gabtab Entries
-s Start Block
-p Port
-S Signature
-c Configure the driver for use
gabconfig
-n Number of systems in the cluster.
Cluster daemons
stop the cluster on all nodes but leave the application/s running hastop -all -force
Cluster Status
Cluster Details
Users
System Operations
Dynamic Configuration
The VCS configuration must be in read/write mode in order to make changes. When in read/write mode the
configuration becomes stale, a .stale file is created in $VCS_CONF/conf/config. When the configuration is put
back into read only mode the .stale file is removed.
Service Groups
Veritas Cluster Cheat sheet
haconf -makerw
hagrp -add groupw
add a service group hagrp -modify groupw SystemList sun1 1 sun2 2
hagrp -autoenable groupw -sys sun1
haconf -dump -makero
haconf -makerw
delete a service group hagrp -delete groupw
haconf -dump -makero
haconf -makerw
hagrp -modify groupw SystemList sun1 1 sun2 2 sun3 3
change a service group haconf -dump -makero
Start a service group and bring its resources online hagrp -online <group> -sys <sys>
Stop a service group and takes its resources offline hagrp -offline <group> -sys <sys>
Veritas Cluster Cheat sheet
Switch a service group from system to another hagrp -switch <group> to <sys>
Enable all the resources in a group hagrp -enableresources <group>
Disable all the resources in a group hagrp -disableresources <group>
hagrp -freeze <group> [-persistent]
Freeze a service group (disable onlining and offlining)
note: use the following to check "hagrp -display <group> | grep TFrozen"
hagrp -unfreeze <group> [-persistent]
Unfreeze a service group (enable onlining and offlining)
note: use the following to check "hagrp -display <group> | grep TFrozen"
haconf -makerw
hagrp -enable <group> [-sys]
Enable a service group. Enabled groups can only be brought online haconf -dump -makero
Note to check run the following command "hagrp -display | grep Enabled"
haconf -makerw
hagrp -disable <group> [-sys]
Disable a service group. Stop from bringing online haconf -dump -makero
Note to check run the following command "hagrp -display | grep Enabled"
Flush a service group and enable corrective action. hagrp -flush <group> -sys <system>
Resources
haconf -makerw
hares -add appDG DiskGroup groupw
hares -modify appDG Enabled 1
add a resource
hares -modify appDG DiskGroup appdg
hares -modify appDG StartVolumes 0
haconf -dump -makero
haconf -makerw
delete a resource hares -delete <resource>
haconf -dump -makero
Veritas Cluster Cheat sheet
haconf -makerw
hares -modify appDG Enabled 1
change a resource haconf -dump -makero
Resource Operations
Resource Types
Resource Agents