locked
SCOM 2012 R2: Cluster Monitoring no longer discovering new cluster resources RRS feed

  • Question

  • We've got a couple of clusters that are monitored by SCOM 2012 R2. Two of these clusters consist of Windows Server 2012 and Windows Server 2012 R2 (each cluster contains either 2012 or 2012 R2). New resource groups have been added to both clusters. SCOM detects the resources as Windows Computers, but fails to do so as Windows Server 2012 (R2) Cluster Resource Groups. Previously discovered resources are monitored

    We already checked if the proxy is enabled on all of the cluster nodes (which is) and we made sure there were no orphaned object entries in the ClusterHive registry (https://blogs.technet.microsoft.com/momteam/2014/05/06/support-tip-some-or-all-cluster-resources-are-not-discovered-by-the-opsmgr-agent/). Triggering the discovery by using the Windows Cluster Service Task "Discover the Windows Server 2012 (R2) Cluster Components" doesn't seem to do anything (http://thoughtsonopsmgr.blogspot.nl/2011/06/cluster-mp-one-or-more-clusters-not.html), even though it tells me it runs successfully.

    As part of our troubleshooting we already updated the Windows Server Operating System MP to 6.0.7316.0 and the Windows Cluster MP to 6.0.7291.0, which are the same versions available in the online catalog.  We also rebooted all the SCOM Management Servers (3 of them) and cleared the Health State of the cluster nodes to force reloading the MP's but nothing seemed to help.

    We're kind of running out of options here... Does anybody else have some more idea's?

    Monday, August 22, 2016 3:06 PM

Answers

  • We created a temporary setup with the exact same MP's and multi-homed the corresponding servers. This setup didn't have the same issue as our live setup.

    So out of desperation we decided to completely remove all the cluster MP's and their dependencies, waited a few days and imported the exact same ones. Now the resources are being discovered yet again.

    The whole 'waiting a few days' is something we came across when attempting to remove a MP and importing it again immediately after, which caused all kinds of issues like rollups not working and stuff not being monitored.

    • Marked as answer by E van Hulsel Friday, September 16, 2016 7:24 AM
    Friday, September 16, 2016 7:24 AM

All replies

  • Hi,

    I want to know what cluster resources were added into that cluster ?

    PAUL

    Wednesday, August 24, 2016 10:46 AM
  • One cluster contains SQL 2012 instances and is built as a Windows Server 2012 cluster. The other cluster hosts file resources and is built as a Windows Server 2012 R2 cluster. Both resource types are already there in said cluster, same version and all.

    No specific run as accounts have been configured and the default run as account has full privileges on the nodes. All of the nodes are appearing in the agent managed section in the SCOM console and the cluster resources are present in the Agentless Managed section. All discoveries are enabled by default and there are no overrides for these clusters.

    Furthermore, the SQL 2012 instances are being discovered as SQL computers and Database Engines, including the containing SQL Agents and Databases. Since these are discovered by a different MP, my thoughts are there's something wrong with the Cluster MP or the configuration of it.



    Wednesday, August 24, 2016 1:45 PM
  • We created a temporary setup with the exact same MP's and multi-homed the corresponding servers. This setup didn't have the same issue as our live setup.

    So out of desperation we decided to completely remove all the cluster MP's and their dependencies, waited a few days and imported the exact same ones. Now the resources are being discovered yet again.

    The whole 'waiting a few days' is something we came across when attempting to remove a MP and importing it again immediately after, which caused all kinds of issues like rollups not working and stuff not being monitored.

    • Marked as answer by E van Hulsel Friday, September 16, 2016 7:24 AM
    Friday, September 16, 2016 7:24 AM