VCS

vs Solaris Cluster
=======================
________________________________________________________________________________
________________________________________________________________________________
____
- max nodes in a cluster: 64 vs 16
________________________________________________________________________________
________________________________________________________________________________
____
- max no. of interconnect interfaces: 8 vs 6
________________________________________________________________________________
________________________________________________________________________________
____
- for certain services, VCS can identify when an application has been intentiona
lly shut down outside of VCS control. VCS sets the service group state as offlin
e
or partial. This feature allows administrators to stop applications that do not
cause a failover
| |
- clrg suspend automated recovery of resource group. Only after that, the servic
es can be shut down outside of Solaris Cluster control. After you are finished >
clrg resume automated recovery
________________________________________________________________________________
________________________________________________________________________________
____
Config Files
============
VCS: main.cf - Defines the cluster, including services groups and resources.
types.cf - Defines the resource types.
By default, both files reside in the following directory: /etc/VRTSvcs/conf/conf
ig/
Solaris Cluster : The cluster framework files are located in /etc/cluster/ccr/
________________________________________________________________________________
________________________________________________________________________________
____
LOG files
=========
VCS: VCS_LOG=/var/VRTSvcs/* : many files (the engine log is the most complete of
all logs, you can find anything inside it)
: agent specific logs (info
is also included in the 'engine' log)
Solaris Cluster: /var/adm/messages
________________________________________________________________________________
________________________________________________________________________________
____
Heartbeat
=========
VCS: VCS_GAB_TIMEOUT - Default: 30000 (denotes 30 seconds); Values (30 seconds t
o 300 seconds)
Solaris Cluster: heartbeat_timeout - Default: 10000 (denotes 10 seconds); Values
(2,5 seconds to 60 seconds);
heartbeat_timeout >= (5*heartbeat_quantum) ; he
artbeat_quantum - Defines how often to send heartbeats, in milliseconds
________________________________________________________________________________
________________________________________________________________________________
____

Volume agent clean may forcibly stop volume resources

When the attribute FaultOnMonitorTimeouts calls the Volume agent clean entry
point after a monitor time-out, the vxvol -f stop command is also issued. This
command forcibly stops all volumes, even if they are still mounted.
________________________________________________________________________________
________________________________________________________________________________
____
Ping - Pong SG/RG
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
Announcement for VOM 6.0: http://www.symantec.com/connect/blogs/new-release-intr
oducing-veritas-operations-manager-60
VOM 6.0 Product guides (many guides): https://sort.symantec.com/documents/doc_de
tails/vom/6.0/Windows%20and%20UNIX/ProductGuides/
Link to VCS Simulator (and to many other goodies): https://www4.symantec.com/Vrt
/offer?a_id=89446
It is a direct link and it requires only a free and simple registration
If you prefer, I downloaded it for you and put it in NortonZone
Here you find the link to the VCS Simulator only (no other VEA, Java GUI or simi
lar)
https://www.nortonzone.com/pickup/85602?key=9RUaCi4Q6bESVtR7rEhZCQ2KqmMH42u4b5T4
pYJcj9f8KQEqRXP6uVa7iVZWig2T&src=url
About Rolling Upgrades: https://sort.symantec.com/public/documents/vcs/6.0/linux
/productguides/html/vcs_install/ch23s01.htm
Performing a rolling upgrade using the script-based installer: https://sort.syma
ntec.com/public/documents/vcs/6.0/linux/productguides/html/vcs_install/ch23s02s0
1.htm
Rough info about lock directory:
http://clientui-kb.symantec.com/resources/sites/BUSINESS/content/live/DOCUMENTAT
ION/4000/DOC4040/en_US/WP_Stateless_Linux_with_VCS.pdf
https://sort.symantec.com/public/documents/sfha/6.0/linux/productguides/html/vcs
_bundled_agents/ch02s03s02.htm
Document that provides more info about I/O Fencing: http://www.mauriziolancia.co
m/public/VCSIOFencing.pdf
________________________________________________________________________________
________________________________________________________________________________
____
LLT (Low Latency Transport) provides fast kernel-to-kernel communications, and
monitors network connections.
GAB (Group Membership and Atomic Broadcast) provides globally ordered message

that is required to maintain a synchronized state among the nodes

________________________________________________________________________________
________________________________________________________________________________
____
==> To avoid data corruption due to splitbrain in CFS environment, I/O Fencing
has to be enabled.
!!!!!! get veritas licenses !!!!!!
________________________________________________________________________________
________________________________________________________________________________
____
In a multi-CPU system configure an adequately high value for the ShutdownTimeout
attribute. This ensures that when a system panics, its service groups successfu
lly
fail over to other systems.
________________________________________________________________________________
________________________________________________________________________________
____
List resource types:
SC:
VCS: hatype -list; grep ^type /etc/VRTSvcs/conf/config/types.cf (not a complete
list)
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
________________________________________________________________________________
________________________________________________________________________________
____
read registr/reserv keys
registrsion keys
# vxfenadm -s all -f /etc/vxfentab
|| vxfenadm -s /dev/vx/rdmp/dis
k
reservation keys
# vxfenadm -r all -f /etc/vxfentab
|| vxfenadm -r /dev/vx/rdmp/dis
k
________________________________________________________________________________
________________________________________________________________________________
____
Veritas
clear import flags
# vxdg -C import <dg_name>\
Display fencing status
# vxfenadm -d

haclus -modify HacliUserLevel COMMANDROOT