Veritas Storage Foundation 5.1 SP1 Cluster File System Installation Guide (5900-1510, April 2011)
■ Validates the ability of the current configuration to support a global cluster
environment.
■ Creates the components that enable the separate clusters, each of which
contains a different set of GAB memberships, to connect and operate as a
single unit.
■ Creates the ClusterService group, or updates an existing ClusterService group.
Run the global clustering configuration wizard on each of the clusters; you must
have the global clustering license in place on each node in the cluster.
To modify the ClusterService group for global clusters using the global clustering
wizard
1
On the primary cluster, start the GCO Configuration wizard:
# /opt/VRTSvcs/bin/gcoconfig
2
The wizard discovers the NIC devices on the local system and prompts you
to enter the device to be used for the global cluster. Specify the name of the
device and press Enter.
3
If you do not have NIC resources in your configuration, the wizard asks you
whether the specified NIC will be the public NIC used by all the systems. Enter
y if it is the public NIC; otherwise enter n. If you entered n, the wizard prompts
you to enter the names of NICs on all systems.
4
Enter the virtual IP address for the local cluster.
5
If you do not have IP resources in your configuration, the wizard prompts
you for the netmask associated with the virtual IP. The wizard detects the
netmask; you can accept the suggested value or enter another one.
The wizard starts running commands to create or update the ClusterService
group. Various messages indicate the status of these commands. After running
these commands, the wizard brings the ClusterService group online.
Defining the remote cluster and heartbeat objects
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.
Setting up a replicated global cluster
Defining the remote cluster and heartbeat objects
318