When a cluster-enabled NSS pool is used as a Novell Cluster Services cluster resource, special steps must be followed if you decide to rename the pool. Renaming the Pool automatically changes the Pool Resource object name in eDirectory. It does not change the virtual server name (the NCS:NCP Server object).
Because renaming involves changing information for the Pool object in eDirectory, you must ensure that the shared pool is active on a cluster node that has its NCP server object in the same context as the Pool object of the pool you are going to rename.
If necessary, use the cluster migrate command to move the shared pool to a cluster node that has a Server object in the same context as the Pool object of the pool you are going to rename.
The server must be in the resource’s list.
In iManager, select > , then select the cluster that you want to manage.
On the Cluster Manager page, select the check box next to the pool cluster resource, then click .
Select the cluster node where you want to move the resource, then click .
Wait for the resource to report a Running state on the target node before you continue.
Offline the pool cluster resource. On the Cluster Manager page, select the check box next to the pool cluster resource, then click .
Wait for the resource to report an Offline state before you continue.
Activate the pool locally on the cluster node:
In iManager, select > .
Select the server where you want to activate the pool.
Select the pool, then click Activate.
In iManager on the Pools page, select the pool, then click Rename, specify the new name, then click OK.
After the rename, the pool is in a deactive state.
Online the pool cluster resource:
In iManager, select > , then select the cluster that you want to manage.
On the Cluster Manager page, select the check box next to the pool cluster resource, then click .
The resource is brought online on a node in its Preferred Nodes list, according to availability. Wait for the resource to report a Running state before you continue.
Novell Cluster Services automatically updates the pool resource load, unload, and monitor scripts to reflect the name change.
If you previously used the cluster rename command to use a customized name for the cluster resource, you must repeat that process to return to the customized name. For information, see Section 10.13, Renaming a Cluster Resource.