Monthly Archives: August 2013

SCOM Tip: How to find the node name for a cluster resource

I received the question from our operation center if it is possible to find the node name for a cluster resource. They were asked to reboot the related server and only had the resource name. In this special case it was a SQL cluster network name.

I checked the discovered resources and views and saw that the standard views from the Failover Cluster Management Pack are not directly showing the relationships to the underlying node. But you still need this management pack to have all the cluster objects discovered.

Example:

SQL Cluster:
Node name: ServerA
Node name: ServerB
Clustername: SQLCluster
Resource name: SQLNetworkname

The operations team only had the SQLNetworkname.

So how can I see the relationship and find the node name?

The easiest way I found is the search. You can direclty launch it in the Monitoring view or go to My Workspace.
Select Advanced Search…

advancedsearch

In the objects to search for Managed Objects and with a specific name. Enter the resource name (in my example it would be: SQLNetworkname).

advancedsearch-details

In the results you can see the cluster resources which also have the cluster node name in the path.

managedobjects

Related to my example you would see two managed objects with the name SQL Network Name (SQLNetwork) and the path ServerA;Clustername and ServerB;Clustername.

When you select one of these managed objects you will have the task (from the Failover Cluster Management Pack) “List resource dependency“. This task shows which node holds the resource at the moment.

taskoutput

So with this information, the operations team can go on with their tasks.

If you want to have a view with a drill down from the cluster name to the nodes and resources, then you could even use another method: create a diagram view based on the Windows Cluster (internal name: Microsoft.Windows.Cluster) class.

diagram

ClusterDiagram

SCOM 2012: Sample APC management pack

With the upgrade of System Center Operations Manager to version 2012 the network monitoring has changed. The result is that the old 2007 management packs to monitor network devices still work, but no new devices can be discovered because the base class has been changed. So everyone who used management packs from the xSNMP suite before had to search for new solutions.

One of the management packs which were covered from the xSNMP suite was the xSNMP.APC.mp to monitor UPS/PDU devices from APC.

I have created a sample 2012 management pack for APC UPS and rPDU devices and published it here.

I have focused on using all already discovered information, so no discovery SNMP probes are necessary.
I added monitors for the following SNMP OIDs:

UPS:

  • upsBasicOutputStatus
  • upsBasicBatteryStatus
  • upsAdvBatteryReplaceIndicator
  • upsAdvBatteryRunTimeRemaining
  • upsAdvBatteryCapacity
  • upsAdvOutputLoad

rPDU:

  • rPDULoadStatusLoadState
  • rPDUPowerSupply1Status
  • rPDUPowerSupply2Status

Additionally the following rules collect the current status (for UPS only) of:

  • upsAdvBatteryRunTimeRemaining
  • upsBasicBatteryStatus
  • upsBasicBatteryTimeOnBattery
  • upsAdvBatteryTemperature
  • upsAdvInputLineVoltage
  • upsAdvInputFrequency
  • upsAdvBatteryCapacity
  • upsAdvOutputVoltage
  • upsAdvOutputLoad
  • upsAdvOutputFrequency
  • upsAdvOutputCurrent

The default interval for all rules and monitors is 10 minutes.

Please try it out and add comments for improvement.