Over the last two weeks I said a few things:
- The management pack for Windows Server 2008 Failover Clustering was available.
- You really need to install the pre-requisite updates before installing the management packs.
MS’s System Center teams have been reminding people about the need to apply updates. I guess PSS must’ve had a few phone calls on the issues the updates resolve.
There’s also an issue with the clustering management pack on clusters that have large numbers of resources, e.g. 60+. That’s not your typical Exchange or SQL cluster … but it could easily be a Hyper-V cluster. The issue is that a “Resource State Monitor” monitor is checking resource availability every 60 seconds and is clobbering the CPU. You can override this by setting it to something larger. I’m probably going with every 10 or 15 minutes. My VMM integration will instantly let me know if a VM goes offline so that covers the disappearing resource issue. MS is internally updating the management pack to fix this monitor.
People know I’m an OpsMgr junkie. Honestly, I’m not impressed. Wouldn’t the dog food tests in MS find this on their large Hyper-V farms? Also, there’s no sign of a “Resource State Monitor”. There is a “Resource Group State Monitor”. Is this what they are referring to? Who knows! If anyone does then please share.
EDIT #1:
The mystery deepens! I did some research and found this. This would seem to say that the "Resource State Monitor" is in a "Cluster Resource" target in "Windows Cluster Management Monitoring Version 6.0.6277.1". Huh!? First, my management packs were brand new and downloaded from the catalog after the RTM announcement. The version of that library is 6.0.6505.0 on my system. No previous edition of the management pack were installed. Next, the "Cluster Resource" target does not exist on my RMS. I’ve double checked and all components were installed. Something smells very fishy to me on this management pack release.