Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

Technical white paper | Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux
Install Serviceguard and Apache toolkit software, and prepare the nodes
Install Serviceguard and Apache toolkit software on each node of the cluster. The Apache toolkit software is a part of the
Serviceguard Contributed Toolkit which is free of cost. Serviceguard provides a utility “cmeasyinstall” that simplifies the
installation process. It installs the Serviceguard components RPMs and list all prerequisite RPMs required for the
Serviceguard components RPM installation. Please refer the section “Gather Required Software “of” SG/LX Deployment
Guide” (http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03393068/c03393068.pdf
) to get details
about Serviceguard software installation.
Please refer sections “Preparing the Servers”, “Serviceguard System Configuration Automation script”, “Allowing Root
Access to an unconfigured Node”, and “Configuring Name Resolution” of “SG/LX Deployment Guide”
(http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03393068/c03393068.pdf) to get details about
preparing nodes for the SG/LX cluster.
The Apache application should not be reinstalled or reconfigured on the nodes. The same Apache application installation
and configuration used in the VCS cluster can be used in the SG/LX cluster.
Create the shared storage for application data
As in VCS cluster, the application data that can change must be kept in a shared storage accessible from all the cluster
nodes. Application binaries and any application data that is smaller in size and don’t change can be kept locally in each
cluster node.
If the filesystem or volume manager used by the application to store its data in the VCS cluster is also supported by SG/LX,
then the same storage layout can be used as is in an SG/LX cluster also. If the filesystem or volume manager used by the
application to store data in the VCS cluster is not supported with SG/LX, then it is required to create a fresh storage layout
for application data using filesystem or volume managers supported by SG/LX.
For more recent list of SG/LX supported filesystems and volume managers please refer to the “HP SG/LX Certification
Matrix.” (http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03398707/c03398707.pdf
)
Configure the SG/LX cluster
CLI
• Execute the following command to create the cluster ASCII file from either of the nodes as root user.
cmquerycl -L /dev/sdf –n hnode –n pnode –C cluster.ascii
Some important attributes of the cluster.ascii file are listed below:
CLUSTER_NAME
hnode_cluster
NODE_NAME
hnode
NETWORK_INTERFACE
eth0
STATIONARY_IP
192.168.4.230
NETWORK_INTERFACE
bond0
HEARTBEAT_IP
10.25.1.1
CLUSTER_LOCK_LUN
/dev/sdf
NODE_NAME
pnode
NETWORK_INTERFACE
eth0
STATIONARY_IP
192.168.4.231
NETWORK_INTERFACE bond0
HEARTBEAT_IP
10.25.1.2
CLUSTER_LOCK_LUN
/dev/sdf
MEMBER_TIMEOUT
14000000 (default value)
23