Skip to main content

Cluster members disappear and do not regenerate after renaming a node on a dynamic cluster


Technote (troubleshooting)


Problem(Abstract)

Renaming a node on a dynamic cluster using the renameNode script causes the cluster members to disappear and not regenerate.

Symptom

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.


Cause

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

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

WebSphere Virtual Enterprise

General


Software version:
6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.3, 6.1.1.4, 6.1.1.5, 7.0, 7.0.0.1, 7.0.0.2


Operating system(s):
AIX, IBM i, Linux, Solaris, Windows, z/OS


Reference #:
1612220


Modified date:
2012-10-25

Translate my page

Content navigation