Global cluster management

VCS enables you to perform operations (online, offline, switch) on global service groups from any system in any cluster. You must log on with adequate privileges for cluster operations.

See User privileges in global clusters.

You can bring service groups online or switch them to any system in any cluster. If you do not specify a target system, VCS uses the FailOverPolicy to determine the system.

See "Defining failover policies" on page 366.

Management of remote cluster objects is aided by inter-cluster communication enabled by the wide-area connector (wac) process.

Wide-area connector process

The wide-area connector (wac) is a failover Application resource that ensures communication between clusters.

Click the thumbnail above to view full-sized image.

The wac process runs on one system in each cluster and connects with peers in remote clusters. It receives and transmits information about the status of the cluster, service groups, and systems. This communication enables VCS to create a consolidated view of the status of all the clusters configured as part of the global cluster. The process also manages wide-area heartbeating to determine the health of remote clusters. The process also transmits commands between clusters and returns the result to the originating cluster.

VCS provides the option of securing the communication between the wide-area connectors.

See Secure communication in global clusters.

Wide-area heartbeats

The wide-area Heartbeat agent manages the inter-cluster heartbeat. Heartbeats are used to monitor the health of remote clusters.

See Heartbeat attributes (for global clusters).

You can change the default values of the heartbeat agents using the command

hahb -modify


Sample configuration

Heartbeat Icmp (

ClusterList = {C1, C2}

AYAInterval@C1 = 20

AYAInterval@C1 = 30

Arguments@c1 = {"192.168.10.10"}

Arguments@c2 = {"64.203.10.12"}

)