Environment
Novell NetWare 6.0
Novell NetWare 6.5
Novell Clustering Services 1.6
Novell Clustering Services 1.7
Novell NetWare 6.5
Novell Clustering Services 1.6
Novell Clustering Services 1.7
Situation
The Cluster Panning ID number was changed because installing a new node with updated software changed it.
Error: "Join Retry, Some Other Node Acquired the Cluster Lock"
When a node leaves, it cannot rejoin. Other nodes are still working just fine.
Communcations have been checked and are not an issue.
Tried adding another node that had earlier crashed using NWDEPLOY.
Error: "Join Retry, Some Other Node Acquired the Cluster Lock"
When a node leaves, it cannot rejoin. Other nodes are still working just fine.
Communcations have been checked and are not an issue.
Tried adding another node that had earlier crashed using NWDEPLOY.
Resolution
All nodes must be re-booted to use the new Cluster Panning ID number instead of what is cached. When all remaining nodes are re-booted, nodes that could not join before are fine.
Additional Information
The Cluster Panning ID has changed. New nodes trying to join are looking at the SBD, trying to join with the new Cluster Panning ID number. The current Master node has the old Cluster Panning ID number cached and is what the SBD is reporting as what cluster owns the SBD partition.
Formerly known as TID# 10097325
Formerly known as TID# 10097325