So you’ve built your Windows 2008 Cluster, and you did it sensibly with good logical names like
It’s been running quite happily, you’ve extended it and upgraded it. But now you’ve got a problem, a resource won’t start up when it’s moved to a new node. So you’ve followed the instructions to get the last 5 minutes of Cluster logs by running:
C:\>cluster log /gen /span:5
And you’ve found that the error is something to do with:
00000790.0000545c::2012/01/09-11:16:15.778 ERR [RCM]s_RcmRpcGetResourceState: ERROR_CLUSTER_GROUP_MOVING(5908)' because of ''Cluster Disk 3' is owned by node 4, not 6.'
But wait a second, what’s this node 4 and 6 business? And which node is the one causing the problem?
The simplest way to find out which node is which is to simply drop to a cmd prompt on one of the nodes and:
C:\>cluster node /status Listing status for all available nodes: Node Node ID Status -------------- ------- --------------------- cluster-node-04 1 Up cluster-node-02 4 Up cluster-node-01 5 Up cluster-node-03 6 Up C:\>
And there you have a nice little lookup table for you.
But why aren’t they aren’t the in nice logical order you installed them in? Well, remember that time you had to evict cluster-node-01 because of the main board fault and rebuilt it on new hardware? Or when you upgraded the hardware by adding in a new ‘better’ node and then removed/replaced the nodes 1 by 1.
Every time the Cluster sees a ‘new’ node it assigns it a shiny new Node number. So when you first built the cluster it was a nice correlation. But the good news is that as it’s going to change fairly infrequently it’s pretty easy to keep a track of it.