Storage System does not agree

[Aaron Weller]

I recently removed a storage not from a management group via the console on the server (not via the CMC).

I did this so I could re-add it, and check what the rebuild time was between the nodes.

However now after I have done this, the Management Group is still reporting the node as part of the cluster/management group. I try to remove it, but I get the error message from the CMC:

"The following management groups report that they contain this storage system, but the storage system does not agree:

san2 ([IP REMOVED]) - [MANAGEMENT GROUP REMOVED]

To resolve this problem, contact Technical Support (Support Portal: http://www.itrc.hp.com)."

The node is also showing in available systems, however I cannot add it to a management group or cluster as it does not give me an option to do so.

I've got a ticket with ITRC, but wondering if anyone in the meantime has encountered this error knows how to fix it??

[Jitun]

Have you tried
Config Management -> Remove from Management Group ?

[Jitun]

Screenshot Attached

[crucialx]

Yep, that's how I got the storage node/management group in the state it is in now. I tried to remove it again in the same way with no luck.

[Aaron Weller]

Note: That last reply was actually me, seems I accidentally created 2 accounts on different computers!

Yep, that's how I got the storage node/management group in the state it is in now. I tried to remove it again in the same way with no luck.

[Jitun]

Sorry I did not see the 1st line.

The above is always the Last option.
Always Recommended making changing through CMC.

Would recommend putting the node into Repair Mode from CMC.
Then Add it back to the Management Group and then Cluster.

Once back in the Cluster.

You can remove the Node from the Cluster using CMC.

[Aaron Weller]

Jitun, this is pretty much what we did after speaking with LH support.

Basically we did the following:

1. Put the node into repair mode.
2. Modify the cluster, and exchange the node that was removed for the one that is in repair mode.
3. Let the node rebuild.

Once the node had rebuilt, the error went away and everything was back to normal.