Veritas Cluster Cheat Sheet Page 2
ADVERTISEMENT
1
2
3
4
5
6gabconfig -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 file
gabconfig -c -x
GAB Port Memberbership
List Membership
gabconfig -a
Unregister port f
/opt/VRTS/bin/fsclustadm cfsdeinit
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)
Port Function
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 daemon
CmdServer
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
hastart [-stale|-force]
"-force" instructs the engine to treat a stale
config as a valid one
Bring the cluster into running mode from a
stale state using the configuration file from a
hasys -force <server_name>
particular server
stop the cluster on the local server but leave
the application/s running, do not failover the
hastop -local
application/s
stop cluster on local server but evacuate
(failover) the application/s to another node
hastop -local -evacuate
within the cluster
stop the cluster on all nodes but leave the
hastop -all -force
application/s running
Cluster Status
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Education