Cluster Server 8.0 Bundled Agents Reference Guide - Windows
- Introducing VCS bundled agents
- Storage agents
- Network agents
- FileShare agents
- Services and applications agents
- VCS infrastructure and support agents
- VCS hardware replication agent for NetApp
- Troubleshooting bundled agents
Sample scenario
In this example, a local VCS cluster (front-end cluster) provides high availability for Web-services and a remote VCS cluster (back-end cluster) provides high availability for the database required by the Web-services. The cluster setup is as follows:
The local cluster is a two-node cluster, where local1 and local2 are the names of the two local nodes.
The remote cluster is a two-node cluster, where remote1 and remote2 are the names of the two remote nodes.
LocGrp is the local service group that contains the WebRes resource (for example: Apache, etc.) configured for the Web-server that runs in the local cluster.
RemGrp is the remote service group that contains the DBRes resource (for example: MySQL or Oracle, etc.) configured for the database in the remote cluster.
The database resource (DBRes) needs to come online before the Web server resource (WebRes) comes online. You can use the RemoteGroup agent to establish this inter-cluster application dependency.
To configure the remotegroup agent for this setup
- Create a RemoteGroup resource (RGRes) in the local service group (LocGrp) for monitoring or managing the DBRes resource in the remote cluster.
- Link the resources such that the WebRes resource depends on the RGRes resource.
- Set the attributes for the RemoteGroup resource (RGRes) as follows:
IpAddress - Set to the IP address or DNS name of a node in the remote cluster. For this example, the value is remote1. You can also set this value as remote2 (second node in the remote cluster).
The RemoteGroup agent keeps a list of remote nodes (remote1, remote2) on the local node. The IP address that you specify should be reachable the first time the RemoteGroup agent tries to communicate to the remote cluster. In case the specified IP address is not reachable after the first communication, the RemoteGroup agent talks to the second remote node to retrieve the state of RemGrp.
GroupName - Set the value to RemGrp (the remote service group).
VCSSysName - Set appropriate values so as to establish a one-to-one mapping between the systems in the local and remote clusters. RGRes will completely manage the remote service group (RemGrp) that contains the DBRes resource. Make this a local attribute for the RGRes.
ControlMode - Set the value to OnOff.
Username - Set the value to user_admin. The user needs to have administrative privileges for RemGrp.
Password - Password for user_admin. You must encrypt the password using the VCS Encrypt command. See the Cluster Server Administrator's Guide for more information on the VCS Encrypt utility.
VCSSysName@local1 - Set this value to remote1.
VCSSysName@local2 - Set this value to remote2.
You have to set the value of BrokerIp for a remote cluster that has the VCS Authentication Service enabled.
- Set the value of the AutoFailover attribute of the RemGrp to 0. This avoids unnecessary online or offline of the remote service group in case of a fail over. If the value of the VCSSysName attribute is ANY, then the value of the AutoFailover attribute of RemGrp should be 1.