Dell Servers - Disk Hardware Health via SNMP

Since hardware health monitoring was introduced in SAM, a lot of users have had to choose between WMI and SNMP for monitoring Dell servers due to a simple reason that the disk and storage controller health status is only exposed in SNMP but WMI is clearly the preferred protocol for Windows monitoring. Not anymore with this template. You can add your Dell servers as a WMI node in Orion, and monitor the storage health via SNMP! A couple of things to note

- This relies on a 3rd party software called NetCmdlets from /n software (www.netcmdlets.com) and is not free. However, it is very inexpensive.

- NetCmdlets software must be installed on the SAM server and any Additional Polling Engine that need to use this template

- The template only works with SNMP v2 and the community string must be passed as a Script Argument

- NetCmdlets itself does support SNMP v3, but I am assuming its a non-issue since Windows doesn't support SNMP v3 anyway

- Thresholds have been defined to set warning and critical status

Huge thanks to micheal100 for putting together bulk of the script. The end-result looks like the belowDell HH SNMP.PNG

UPDATE: antonis.athanasiou has come up with a version that is based on a free SNMP plugin hereDell Server - Storage Hardware Health v1.2

Anonymous
  • Dang it!  Service restart on Orion like you suggested fixed it.  Thank you for all your help!

    Now to get it going on the 130 other systems....

    -Brent

  • I suppose you tried clicking 'poll now' already. It is normal for it to be in a 'initial poll in progress' for a few minutes but certainly not for hours. You can try deleting the application monitor, and then re-assigning the template from the SAM settings > manage templates page. Extreme step would be stop and start all services from the Orion Service Manager utility.

  • OK - I've learned a bit about templates today...

    I can get the SAM server to get proper info from running the script hardcoded (for testing) for itself and one other server from the powershell cmd prompt.  The un-altered template with the proper community arguement comes back successfully.  Any ideas?

    Successful command line fetch with hardcoded remote IP and community name:

    ps_cmd.PNG

    Successful template test:

    Template_test_success.PNG

    Fail at populating same server as above:

    SAM_fail.PNG

    it will sit here for hours, while testing successfully in the 'component test' area.  The SAM server is running powershell 4 and the working remote is running powershell 2 - my assumption is that it is PS 2+ for compatibility... 

    Thanks for your time and help, by the way!

    -Brent

  • Gotcha - I'll give it a go.  Thanks for the quick reply.  -Brent

  • You shouldn't have to change anything in the script body. Just supply the community string to the script argument field. Assign the template to the Dell server, and the script will take care of making the SNMP query to the dell server you assigned the template to. The SNMP host you refer to in the script is not the npm server. Instead, it is the Dell server that needs to be monitored. Again, you don't need to modify these 2 lines at all.