Preparing a Zone Cluster for Partner Membership

Language:

To enable a zone cluster to function as a member of a Disaster Recovery framework partnership, the common agent container must be manually configured within the zone cluster.

How to Prepare a Zone Cluster for Partner Membership

This procedure configures common agent container security in a zone cluster to prepare the zone cluster for use in a cluster partnership.

Before You Begin

Ensure that the following conditions are met:

The zone cluster is created. See Creating and Configuring a Zone Cluster in Installing and Configuring an Oracle Solaris Cluster 4.4 Environment.
You have read the requirements for using a zone cluster in a cluster partnership. See Zone Clusters.
Disaster recovery framework software is installed in the global cluster that supports the zone cluster you are configuring.

Assume the root role on a node of the global cluster that supports the zone cluster you are configuring.

Set up the network address for the zone cluster.

phys-schost# clzonecluster configure zone-cluster-name
clzc:zone-cluster-name> add net
clzc:zone-cluster-name:net> set address=zone-cluster-name
clzc:zone-cluster-name:net> end

clzc:zone-cluster-name> verify
clzc:zone-cluster-name> commit
clzc:zone-cluster-name> exit

Copy the security files for the common agent container to all zone cluster nodes.
This step ensures that security files for the common agent container are identical on all cluster nodes and that the copied files retain the correct file permissions.

Perform all steps in the zone cluster.
1. Log in to each node of the zone cluster.
```
phys-schost# zlogin zone-cluster-name
zcname#
```
2. On each node, stop the common agent container.
```
zcname# /usr/sbin/cacaoadm stop
```
3. On one node, create the security keys.
```
zcname# cacaoadm create-keys --force
```
4. Create a tar file of the /etc/cacao/instances/default/security directory.
```
zcname# cd /etc/cacao/instances/default
zcname# tar cf /tmp/SECURITY.tar ./security
```
5. Copy the /tmp/SECURITY.tar file to each of the other cluster nodes.
6. On each node to which you copied the /tmp/SECURITY.tar file, extract the security files.
  Any security files that already exist in the /etc/cacao/instances/default/security directory are overwritten.
```
zcname# cd /etc/cacao/instances/default
zcname# tar xf /tmp/SECURITY.tar
```
7. Delete the /tmp/SECURITY.tar file from each node in the cluster.
  You must delete each copy of the tar file to avoid security risks.
```
zcname# rm /tmp/SECURITY.tar
```
8. On each node, set the common agent container network-bin address.
```
zcname# cacaoadm set-param network-bind-address=0.0.0.0
```
9. On each node, enable and start the common agent container.
```
zcname# /usr/sbin/cacaoadm enable
zcname# /usr/sbin/cacaoadm start
```

Verify that the Disaster Recovery framework modules are loaded on the zone cluster node.

phys-schost# cacaoadm status com.sun.cluster.geocontrol
phys-schost# cacaoadm status com.sun.cluster.geoutilities
phys-schost# cacaoadm status com.sun.cluster.notifier

If a module is loaded, command output would be similar to the following. You can safely ignore the message Module is not in good health.
```
Operational State:ENABLED
Administrative State:LOCKED
Availability Status:[]
Module is not in good health.
```
If a module is not loaded, command output would be similar to the following.
```
Module com.sun.cluster.geocontrol has not been loaded.
Cause of the problem:[DEPENDENCY]
```
See the Troubleshooting section at the end of this procedure.

Exit the zone cluster node.
```
zcname# exit
phys-schost#
```

Troubleshooting

If a Disaster Recovery framework module is not loaded, check that the zone cluster configuration is correct.

After you have verified that the configuration is complete and correct, and you have fixed any errors, do one of the following:

On each zone cluster node, restart the common agent container.
```
zcnode# /usr/sbin/cacaoadm restart
```

From a global-cluster node, reboot the zone cluster.

phys-schost# clzonecluster reboot zone-cluster-name

After processing is complete on all zone cluster nodes, check that the Disaster Recovery framework modules are now loaded. If any modules are still not loaded, contact your Oracle service representative for assistance.

Next Steps

Go to Enabling the Disaster Recovery Framework Infrastructure.