Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

Technical white paper | Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux
The cmquerycl command can automatically detect the network topology between the nodes and configure the eligible
networks for heartbeat. The command can setup the cluster Lock LUN using the disk passed through –L option. When using
a Quorum Server, use the -q <Quorum Server name> option instead.
You can refer to cluster attributes comparison table VCS cluster attributes and SG/LX cluster attributes
and section
Plan SG/LX heartbeat network and membership arbitration, to modify other SG/LX cluster attributes to match you VCS
cluster behavior.
cmquerycl can automatically specify the name of the cluster as the name of the node on which cmquerycl is run with a
suffix: “_cluster”. In this illustration, the cluster name is specified as “apache_cluster”, by modifying the cluster_name
attribute in the generated cluster.ascii file.
• Execute the following command to apply the cluster ASCII file as root user:
– cmapplyconf –C /cluster.ascii
GUI (Serviceguard Manager)
• You can also configure an SG/LX cluster using Serviceguard Manager. Please refer the section “Configure the Cluster” of
“HP SG/LX Deployment Guide” (
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03393068/
c03393068.pdf) and follow the steps mentioned there to configure an SG/LX cluster using Serviceguard Manager. You
can refer to cluster attributes comparison table VCS cluster attributes and SG/LX cluster attributes and section
Plan SG/LX heartbeat network and membership arbitration to modify other SG/LX cluster attributes to match you
VCS cluster behavior.
Stop the VCS cluster
Log in as root user and execute the following commands:
• Bring down the Apache agent service group on the hnode (assuming it was running on the hnode).
– hagrp -offline apache_agent_servicegroup -sys hnode
• Check the status of Apache agent service group. It should be “offline”.
– hagrp -state apache_agent_servicegroup
• Stop VCS on both nodes (hnode and pnode), and execute the following command on the both nodes.
– hastop –local
• Verify that the VCS engine port h is closed.
– gabconfig –a
• Stop I/O fencing if you have configured it. Stop GAB and then LLT using following commands:
– /etc/init.d/vxfen stop
– /etc/init.d/gab stop
– /etc/init.d/llt stop
Start the SG/LX cluster
CLI
Execute the following command to start the cluster:
cmruncl
cmruncl: Validating network configuration...
cmruncl: Network validation complete
Waiting for cluster to form... done
Cluster successfully formed.
Check the syslog files on all nodes in the cluster to verify that no warnings occurred during startup.
24