The Wayback Machine - [Link]

blacksheepnetwork…

Veritas Cluster Cheat sheet

LLT and GAB Commands |  Port Membership | Daemons | Log Files | Dynamic Configuration | Users |
Resources | Resource Agents | Service Groups | Clusters | Cluster Status | System Operations | Sevice
Group Operations | Resource Operations | Agent Operations | Starting and Stopping

LLT and GRAB

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 system admin configures the LLT by
LLT 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 synchronised state among the
GAB 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).

LLT and GAB files

/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/[Link] The VCS configuration file. The file contains the information that
defines the cluster and its systems.

Gabtab Entries

/sbin/gabdiskconf - i /dev/dsk/c1t2d0s2 -s 16 -S 1123

/sbin/gabdiskconf - i /dev/dsk/c1t2d0s2 -s 144 -S 1124
/sbin/gabdiskhb -a /dev/dsk/c1t2d0s2 -s 16 -p a -s 1123
/sbin/gabdiskhb -a /dev/dsk/c1t2d0s2 -s 144 -p h -s 1124
/sbin/gabconfig -c -n2

gabdiskconf
-i   Initialises the disk region
 -s   Start Block
-S   Signature

-a   Add a gab disk heartbeat resource

gabdiskhb -s   Start Block
(heartbeat disks) -p   Port
-S   Signature

-c   Configure the driver for use

gabconfig
-n   Number of systems in the cluster.

LLT and GAB Commands

Verifying that links are active for LLT lltstat -n

verbose output of the lltstat command lltstat -nvv | more
open ports for LLT lltstat -p
display the values of LLT
lltstat -c
configuration directives
lists information about each
lltstat -l
configured LLT link
List all MAC addresses in the cluster lltconfig -a list
stop the LLT running lltconfig -U
start the LLT lltconfig -c

gabconfig -a
verify that GAB is operating Note: port a indicates that GAB is communicating, port h
indicates that VCS is started

stop GAB running gabconfig -U

start the GAB gabconfig -c -n <number of nodes>
override the seed values in the gabtab
gabconfig -c -x
file

GAB Port Memberbership

List Membership gabconfig -a

Unregister port f /opt/VRTS/bin/fsclustadm cfsdeinit

Port Function a   gab driver
b   I/O fencing (designed to guarantee data integrity)
d   ODM (Oracle Disk Manager)
f   CFS (Cluster File System)
h   VCS (VERITAS Cluster Server: high availability daemon)
o   VCSMM driver (kernel module needed for Oracle and VCS
interface)
q   QuickLog daemon
 v   CVM (Cluster Volume Manager)
w   vxconfigd (module for cvm)

Cluster daemons

High Availability Daemon had

Companion Daemon hashadow
Resource Agent daemon <resource>Agent
Web Console cluster managerment
CmdServer
daemon

Cluster Log Files

Log Directory /var/VRTSvcs/log

primary log file (engine log file) /var/VRTSvcs/log/engine_A.log

Starting and Stopping the cluster

"-stale" instructs the engine to treat the local config as stale

"-force" instructs the engine to treat a stale config as a valid hastart [-stale|-force]
one

Bring the cluster into running mode from a stale state using
hasys -force <server_name>
the configuration file from a particular server

stop the cluster on the local server but leave the

hastop -local
application/s running, do not failover the application/s
stop cluster on local server but evacuate (failover) the
hastop -local -evacuate
application/s to another node within the cluster

stop the cluster on all nodes but leave the application/s

hastop -all -force
running

Cluster Status

display cluster summary hastatus -summary

continually monitor cluster hastatus
verify the cluster is operating hasys -display

Cluster Details

information about a cluster haclus -display

value for a specific cluster attribute haclus -value <attribute>
modify a cluster attribute haclus -modify <attribute name> <new>
Enable LinkMonitoring haclus -enable LinkMonitoring
Disable LinkMonitoring haclus -disable LinkMonitoring

Users
add a user hauser -add <username>
modify a user hauser -update <username>
delete a user hauser -delete <username>
display all users hauser -display

System Operations

add a system to the cluster hasys -add <sys>

delete a system from the cluster hasys -delete <sys>
Modify a system attributes hasys -modify <sys> <modify options>
list a system state hasys -state
Force a system to start hasys -force
Display the systems attributes hasys -display [-sys]
List all the systems in the cluster hasys -list
Change the load attribute of a system hasys -load <system> <value>
Display the value of a systems nodeid
hasys -nodeid
(/etc/llthosts)

hasys -freeze [-persistent][-evacuate]

Freeze a system (No offlining system,
No groups onlining)
Note: [Link] must be in write mode

hasys -unfreeze [-persistent]

Unfreeze a system ( reenable groups
and resource back online) Note: [Link] must be in write mode

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.

Change configuration to
haconf -makerw
read/write mode
Change configuration to read-
haconf -dump -makero
only mode

haclus -display |grep -i 'readonly'

Check what mode cluster is
running in 0 = write mode
1 = read only mode

hacf -verify /etc/VRTS/conf/config

Check the configuration file Note: you can point to any directory as long as it has [Link] and
[Link]
convert a [Link] file into hacf -cftocmd /etc/VRTS/conf/config -dest /tmp
cluster commands
convert a command file into a
hacf -cmdtocf /tmp -dest /etc/VRTS/conf/config
[Link] file

Service Groups

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

Note: use the "hagrp -display <group>" to list attributes

list the service groups hagrp -list

list the groups dependencies hagrp -dep <group>
list the parameters of a group hagrp -display <group>
display a service group's resource hagrp -resources <group>
display the current state of the
hagrp -state <group>
service group
clear a faulted non-persistent
hagrp -clear <group> [-sys] <host> <sys>
resource in a specific grp

# remove the host

hagrp -modify grp_zlnrssd SystemList -delete <hostname>

# add the new host (don't forget to state its position)

Change the system list in a cluster
hagrp -modify grp_zlnrssd SystemList -add <hostname> 1

# update the autostart list

hagrp -modify grp_zlnrssd AutoStartList <host> <host>

Service Group Operations

Start a service group and bring its

hagrp -online <group> -sys <sys>
resources online
Stop a service group and takes its
hagrp -offline <group> -sys <sys>
resources offline
Switch a service group from system to
hagrp -switch <group> to <sys>
another
Enable all the resources in a group hagrp -enableresources <group>
Disable all the resources in a group hagrp -disableresources <group>
Freeze a service group (disable hagrp -freeze <group> [-persistent]
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 haconf -dump -makero
groups can only be brought online
Note to check run the following command "hagrp -display | grep
Enabled"

haconf -makerw
  hagrp -disable <group> [-sys]
Disable a service group. Stop from haconf -dump -makero
bringing online
Note to check run the following command "hagrp -display | grep
Enabled"

Flush a service group and enable

hagrp -flush <group> -sys <system>
corrective action.

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

haconf -makerw
  hares -modify appDG Enabled 1
change a resource haconf -dump -makero

Note: list parameters "hares -display <resource>"

change a resource attribute to

hares -global <resource> <attribute> <value>
be globally wide
change a resource attribute to
hares -local <resource> <attribute> <value>
be locally wide
list the parameters of a
hares -display <resource>
resource
list the resources hares -list  
list the resource dependencies hares -dep

Resource Operations

Online a resource hares -online <resource> [-sys]

Offline a resource hares -offline <resource> [-sys]
display the state of a resource( offline,
hares -state
online, etc)
display the parameters of a resource hares -display <resource>
Offline a resource and propagate the
hares -offprop <resource> -sys <sys>
command to its children
Cause a resource agent to
hares -probe <resource> -sys <sys>
immediately monitor the resource
Clearing a resource (automatically
hares -clear <resource> [-sys]
initiates the onlining)

Resource Types

Add a resource type hatype -add <type>

Remove a resource type hatype -delete <type>
List all resource types hatype -list
Display a resource type hatype -display <type>
List a partitcular resource type hatype -resources <type>
Change a particular resource types
hatype -value <type> <attr>
attributes

Resource Agents

add a agent pkgadd -d . <agent package>

remove a agent pkgrm <agent package>
change a agent n/a
list all ha agents haagent -list  
Display agents run-time information
haagent -display <agent_name>  
i.e has it started, is it running ?
Display agents faults haagent -display |grep Faults

Resource Agent Operations

Start an agent haagent -start <agent_name>[-sys]

Stop an agent haagent -stop <agent_name>[-sys]