After configuring global clustering, add the remote cluster object to define the IP address of the cluster on the secondary site, and the heartbeat object to define the cluster-to-cluster heartbeat.
Heartbeats monitor the health of remote clusters. VCS can communicate with the remote cluster only after you set up the heartbeat resource on both clusters.
To define the remote cluster and heartbeat
# haconf -makerw
In this example, the remote cluster is clus2 and its IP address is 10.11.10.102:
# haclus -add clus2 10.11.10.102
In this example, the primary cluster is clus1 and its IP address is 10.10.10.101:
# haclus -add clus1 10.10.10.101
# hahb -add Icmp
Define the following attributes for the heartbeat resource:
ClusterList lists the remote cluster.
Arguments enable you to define the virtual IP address for the remote cluster.
# hahb -modify Icmp ClusterList clus2 # hahb -modify Icmp Arguments 10.11.10.102 -clus clus2
# haconf -dump -makero
# hastatus -sum
# haclus -list clus1 clus2
Example of heartbeat additions to the main.cf file on the primary site:
. . remotecluster clus2 ( Cluster Address = "10.11.10.102" ) heartbeat Icmp ( ClusterList = { clus2 } Arguments @clus2 = { "10.11.10.102" } ) system galaxy ( ) . .
Example heartbeat additions to the main.cf file on the secondary site:
. . remotecluster clus1 ( Cluster Address = "10.10.10.101" ) heartbeat Icmp ( ClusterList = { clus1 } Arguments @clus1 = { "10.10.10.101" } ) system mercury ( ) . .
See the Veritas Cluster Server Administrator's Guide for details for configuring the required and optional attributes of the heartbeat object.