Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article provides brief information on monitoring a Microsoft Cluster with SNMP.
All NPM versions
SNMP is only going to get information off the active Node. It’s SNMP agent will get the requests but will only respond with its own information. There is no way to get cluster wide info, as there isn’t a cluster snmp agent.
This is the limitation with Clusters and SNMP. If you were to monitor the Virtual IP and do a MIB Walk or rediscovery, the SNMP information would be coming back from the active Server. SNMP is not a cluster resource and there is no MIB for the MS cluster service and this will return back incorrect Monitoring information.
There are some OIDs you can use to monitor the Cluster, however it is limited. You will need to set these up through Universal Device Poller:
This OID is for which node owns the resources: 22.214.171.124.126.96.36.199.188.8.131.52.5
This OID is for the overall Cluster Condition: 184.108.40.206.220.127.116.11.1.3
Monitoring Clustered servers can be difficult if not impossible, since all members of the cluster use the same layer 3 address. Since Orion relies on L3 address to identify unique nodes in its database, this becomes a potential impossibility. However, there is a work around that you may wish to consider.
If you were to utilize a different available physical port on each cluster member server, and set up an Out of Band "OOB" subnet to use for the specific purpose of polling these nodes individually, you can connect against their SNMP Services separately and thereby collect performance metrics on each server independently. The added benefit to this (of course) is that you are not introducing additional traffic onto the production network by doing so. This would in turn give you better Statistics for the overall cluster performance not only in individual Server Member status, but individual CPU, Memory, Volume and Bandwidth Collection that would help in assisting Cluster and Server issues.
Note: You may be able to use APM and VB Custom Scripting to monitor the Cluster instance. Below is the beginning of a vbs script I was working on to call the MSCluster_Resource class. Your best bet to make sure the script works is to install Script-o-matic and just pull the counters and let it write the script itself.
Sample VB Script Code:
On Error Resume Next
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\MSCluster")
Set colItems = objWMIService.ExecQuery("Select * from MSCluster_Resource",,48)
For Each objItem in colItems