Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
156 VCS infrastructure and support agents RemoteGroup agent Table 7-15 RemoteGroup agent optional attributes (continued) Optional Attribute ReturnIntOffline Description Select one of the following values for RemoteGroup to return IntentionalOffline: ■ ■ ■ RemotePartial.Indicates that the RemoteGroup resource returns an IntentionalOffline if the remote service group is in an ONLINE|PARTIAL state. RemoteOffline.Indicates that the RemoteGroup resource returns an IntentionalOffline if the remote service group is in an OFFLINE state. RemoteFaulted.Indicates that the RemoteGroup resource returns an IntentionalOffline if the remote service group is OFFLINE|FAULTED. You can use these values in combinations with each other. You must set the IntentionalOffline attribute of the RemoteGroup resource type to 1 for this attribute to work properly. Default: "" Type and Dimension: string-vector OfflineMonitoringN ode Defines the cluster node that performs the offline monitoring of the remote service group. This is an internal attribute. Do not modify. About the ControlMode attribute In the ControlMode attribute, you can use these values, depending on your needs: OnOff, MonitorOnly, and OnlineOnly. OnOff Select the OnOff value of this attribute when you want the RemoteGroup resource to manage the remote service group completely. The username provided in the Username attribute should have administrator privileges for the service group on the remote cluster. In case of one-to-one mapping, set the value of the AutoFailover attribute of the remote service group to 0. This avoids unnecessary onlining or offlining of the remote service group. MonitorOnly
VCS infrastructure and support agents RemoteGroup agent 157 Select the MonitorOnly value of this attribute when you want to monitor the state of the remote service group. When you choose the MonitorOnly attribute, the RemoteGroup agent does not have control over the remote service group and cannot bring it online nor take it offline. The remote service group should be in an ONLINE state before you bring the RemoteGroup resource online. Symantec recommends that you set the AutoFailover attribute of the remote service group to 1. OnlineOnly Select the OnlineOnly value of this attribute when the remote service group takes a long time to come online or to go offline. When you use OnlineOnly for the ControlMode attribute, a switch or fail over of the local service group with VCSSysName set to ANY does not cause the remote service group to be taken offline and brought online. The username provided in the Username attribute needs to have administrator privileges for the remote service group. The Offline of the RemoteGroup resource does not offline the remote service group. If you are choosing one-to-one mapping between the local nodes and remote nodes, then the value of the AutoFailover attribute of the remote service group must be 0. Note: When you set the value of ControlMode to OnlineOnly or to MonitorOnly, the recommended value of the VCSSysName attribute of the RemoteGroup resource is ANY. If you want one-to-one mapping between the local nodes and the remote nodes, then a switch or fail over of local service group is impossible. It is important to note that in both these configurations the RemoteGroup agent does not take the remote service group offline. 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.
- Page 105 and 106: Services and applications agents In
- Page 107 and 108: Services and applications agents In
- Page 109 and 110: Services and applications agents In
- Page 111 and 112: Services and applications agents Ge
- Page 113 and 114: Services and applications agents Ge
- Page 115 and 116: Services and applications agents Se
- Page 117 and 118: Services and applications agents Se
- Page 119 and 120: Services and applications agents Pr
- Page 121 and 122: Services and applications agents Pr
- Page 123 and 124: Services and applications agents Pr
- Page 125 and 126: Services and applications agents MS
- Page 127 and 128: Services and applications agents MS
- Page 129 and 130: Chapter 7 VCS infrastructure and su
- Page 131 and 132: VCS infrastructure and support agen
- Page 133 and 134: VCS infrastructure and support agen
- Page 135 and 136: VCS infrastructure and support agen
- Page 137 and 138: VCS infrastructure and support agen
- Page 139 and 140: VCS infrastructure and support agen
- Page 141 and 142: VCS infrastructure and support agen
- Page 143 and 144: VCS infrastructure and support agen
- Page 145 and 146: VCS infrastructure and support agen
- Page 147 and 148: VCS infrastructure and support agen
- Page 149 and 150: VCS infrastructure and support agen
- Page 151 and 152: VCS infrastructure and support agen
- Page 153 and 154: VCS infrastructure and support agen
- Page 155: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
- Page 165 and 166: VCS hardware replication agent for
- Page 167 and 168: VCS hardware replication agent for
- Page 169 and 170: VCS hardware replication agent for
- Page 171 and 172: Chapter 9 Troubleshooting bundled a
- Page 173 and 174: Troubleshooting bundled agents Trou
- Page 175 and 176: Troubleshooting bundled agents Trou
- Page 177 and 178: Troubleshooting bundled agents Trou
- Page 179 and 180: Troubleshooting bundled agents Trou
- Page 181 and 182: Troubleshooting bundled agents Trou
- Page 183 and 184: Troubleshooting bundled agents Trou
- Page 185 and 186: Troubleshooting bundled agents Trou
- Page 187 and 188: Troubleshooting bundled agents Trou
- Page 189 and 190: Troubleshooting bundled agents Trou
- Page 191 and 192: Troubleshooting bundled agents Trou
- Page 193 and 194: Troubleshooting bundled agents Trou
- Page 195 and 196: Troubleshooting bundled agents Trou
- Page 197 and 198: Troubleshooting bundled agents Trou
- Page 199 and 200: Troubleshooting bundled agents Trou
- Page 201 and 202: Troubleshooting bundled agents Trou
- Page 203 and 204: Troubleshooting bundled agents Trou
- Page 205 and 206: Troubleshooting bundled agents Trou
156<br />
VCS infrastructure and support agents<br />
RemoteGroup agent<br />
Table 7-15<br />
RemoteGroup agent optional attributes (continued)<br />
Optional Attribute<br />
ReturnIntOffline<br />
Description<br />
Select one of the following values for RemoteGroup to return<br />
IntentionalOffline:<br />
■<br />
■<br />
■<br />
RemotePartial.Indicates that the RemoteGroup resource<br />
returns an IntentionalOffline if the remote service group<br />
is in an ONLINE|PARTIAL state.<br />
RemoteOffline.Indicates that the RemoteGroup resource<br />
returns an IntentionalOffline if the remote service group<br />
is in an OFFLINE state.<br />
RemoteFaulted.Indicates that the RemoteGroup resource<br />
returns an IntentionalOffline if the remote service group<br />
is OFFLINE|FAULTED.<br />
You can use these values in combinations with each other.<br />
You must set the IntentionalOffline attribute of the<br />
RemoteGroup resource type to 1 for this attribute to work<br />
properly.<br />
Default: ""<br />
Type and Dimension: string-vector<br />
OfflineMonitoringN ode<br />
Defines the cluster node that performs the offline monitoring<br />
of the remote service group.<br />
This is an internal attribute. Do not modify.<br />
About the ControlMode attribute<br />
In the ControlMode attribute, you can use these values, depending on your needs:<br />
OnOff, MonitorOnly, and OnlineOnly.<br />
OnOff<br />
Select the OnOff value of this attribute when you want the RemoteGroup resource<br />
to manage the remote service group completely.<br />
The username provided in the Username attribute should have administrator<br />
privileges for the service group on the remote cluster.<br />
In case of one-to-one mapping, set the value of the AutoFailover attribute of the<br />
remote service group to 0. This avoids unnecessary onlining or offlining of the<br />
remote service group.<br />
MonitorOnly