Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

Technical white paper | Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

• Configure the SG/LX cluster

• Stop the VCS cluster

• Start the SG/LX cluster

• Verify the SG/LX cluster

• Create and configure the Serviceguard Apache toolkit package

• Start the Serviceguard Apache toolkit package

• Verify the Apache toolkit package

• Remove the VCS configuration and software

Plan SG/LX heartbeat network and membership arbitration

For SG/LX cluster, it is recommended to configure at least two networks or one channel bonded network for heartbeat. In a

migration, you can also configure the network used by your VCS cluster for GAB/LLT as heartbeat network for the target

SG/LX cluster. VCS heartbeat network configuration is kept in the /etc/llttab file of each node.

A typical/etc/llttab file looks like below:

set-node node 1

set-cluster 2

link en1 /dev/dlpi/en:1 - ether - -

link en2 /dev/dlpi/en:2 - ether - -

The third field of the lines starting with the directive “link” represents the network device used for GAB/LLT by VCS. SG/LX

heartbeat is at network layer (TCP) opposed to VCS heartbeat at link layer. So you might need to configure an IP subnet or

use an existing IP subnet on these network devices for SG/LX heartbeat.

In this illustration, the VCS cluster uses a channel bonded interface for GAB/LLT. The /etc/llttab looks like this:

set-node hnode

set-cluster 26020

link bond0 bond0 - ether - -

The target SG/LX cluster can use an IP network over the “bond0” network interface as heartbeat network. If the “bond0”

interface is not configured with any IP network in the cluster nodes, configure an IP network so that SG/LX can detect and

use the same for heartbeat.

For membership arbitration in the target SG/LX cluster, you can choose to use a cluster Lock LUN or Quorum Server. When

using Quorum Server for membership arbitration, ensure that all the nodes can reach the server on the network.

If you choose to use a cluster Lock LUN, ensure that you use a new disk. Do not use any of the VCS coordination point disks

or any other disk in use with the existing VCS cluster as a cluster Lock LUN in SG/LX. You can identify the coordination point

disk being used by the VCS in the /etc/vxfentab file.

In this illustration, the /etc/vxfentab can have the following values:

/dev/sda

/dev/sdb

/dev/sdc

Excluding the above Coordination point disks, we can use a new disk /dev/sdf in the target SG/LX cluster as cluster

Lock LUN.