asked on
MS SCOM 2012 R2 group showing red but no system in the group is showing red
Hi,
We have been having some issues surrounding monitors.
I have a group that contains 4 clusters (Server 2003 - 6 nodes in this cluster group) (yes, server 2003)
Up until Sunday evening, everything had been monitoring fine but since then the group is showing up as critical but no system below it is showing critical at all. Not even the nodes.
Any ideas where I could start looking to find out why SCOM thinks this cluster is in a critical state?
We have been having some issues surrounding monitors.
I have a group that contains 4 clusters (Server 2003 - 6 nodes in this cluster group) (yes, server 2003)
Up until Sunday evening, everything had been monitoring fine but since then the group is showing up as critical but no system below it is showing critical at all. Not even the nodes.
Any ideas where I could start looking to find out why SCOM thinks this cluster is in a critical state?
* scomWindows Server 2003
Last Comment
ukkaapie
If I understand your question -- have you tried putting the group in maintenance mode, with a five minute duration? (Then wait the five minutes.)
ASKER
Hi Rich,
Yes, I tried that. I also tried putting each of the nodes into maintenance mode and then removing but no go.
If I take all the cluster names out of the group then the group goes green (without a tick) but the moment I add just one of any of the cluster names the group goes critical. None of the nodes or cluster names themselves show any critical or warning at all anywhere.
Yes, I tried that. I also tried putting each of the nodes into maintenance mode and then removing but no go.
If I take all the cluster names out of the group then the group goes green (without a tick) but the moment I add just one of any of the cluster names the group goes critical. None of the nodes or cluster names themselves show any critical or warning at all anywhere.
ASKER
What's also interesting is I have another group with just the node names in and all is green. It is something to do with the cluster names themselves.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Not clear in the end what isn't reporting healthy, and stopped receiving feedback from the original requester. MOST issues where rollups don't clear when their subordinate monitors/rules report healthy would be set the system for a short maintenance in SCOM. That didn't clear the state in this case, but brought up that it was a group rather than system that was reporting unhealthy.
ASKER
Just to inform all that I removed all members from the group, deleted and recreated the group and monitor exactly the same and all is good.
Maybe a corruption of the group?
Maybe a corruption of the group?