Cluster members disappear and do not regenerate after renaming a node on a dynamic cluster
Renaming a node on a dynamic cluster using the renameNode script causes the cluster members to disappear and not regenerate.
After the renameNode script is completed successfully, the Dynamic Cluster displays the new node name, but previous cluster members are missing and no cluster members are defined.
The renameNode script does not update the node name in the membership policy. If the dynamic cluster was created with the node_name = "oldNodeName", the old node name will not exist so cluster members can not be created since it violates the membership policy.
Diagnosing the problem
Check the membership policy for the dynamic cluster
Resolving the problem
Update the membership policy to reflect the new node name
More support for:
WebSphere Virtual Enterprise
Software version: 6.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 7.0, 220.127.116.11, 18.104.22.168
Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS
Reference #: 1612220
Modified date: 2012-10-25