There are two issues with the recently released cluster Management Pack that you should be aware of.
One of the Windows Clustering hotfixes required as a prerequisite for the Management Pack has been removed from the download site because it introduced problems for customers managing clusters with System Center Virtual Machine Manager. The hotfix is KB article 958807 “Windows Server 2008 Failover Clustering WMI provider does not correctly handle invalid characters in the private property names causing WMI queries to fail”. The clustering team is working on re-releasing that hotfix. The impact for customers is that they are not able to implement the cluster Management Pack until the re-released hotfix is available. Note that customers that are not managing clusters through VMM and have already downloaded the hotfix and Management Pack are not affected by this issue. It is however likely that they will need to re-apply the updated hotfix.
We will post information here when the updated hotfix is available.
Another issue is that the Management Pack may cause high CPU utilization on clusters with large numbers of resources (we’ve seen this on clusters with 60 and 80 resources). We are working on an updated Management Pack which will resolve this issue. The issue is with the “Resource State Monitor” which by default checks status of all cluster resources every minute. To mitigate, affected customers can override the frequency of this monitor. There is a fix being tested at the moment. Note that customers that are looking to implement the cluster Management Pack will also need the updated hotfix mentioned above.
Just an FYI that the Operations Manager product team published a couple known issues regarding the latest
Where exactly is the “Resource State Monitor”? I can't find it. I can find a "Resource Group State Monitor”
Authoring Console\ Mangement Pack Objects\ Monitors\
Target: cluster ressource\Entity Health\Availability\ Ressource State Monitor
Just disable it with an override. That should be sufficient to prevent the nodes from high cpu usage.
To the entry with the "dog food". I think you are absolutely right. We are very frustrated as well.
Hey All, If you were planning on installing the newly released cluster management pack, you want to read
Is the issue outlined in KB article 958807 pretty much guaranteed to appear in any Ops Manager environment?
Our procedures for creating clusters won't allow for invalid characters on anything that is user created.
Are there some specific MS apps or poorly written third part party apps that introduce illegal characters in the resource private property names?
An updated cluster Management Pack is now released . It fixes problems with resource utilization on cluster