SNMP discovery fails in SCOM 2012

Last month we have discovered a funny situation which I would like to share with you. We have monitored some custom Linux-based hardware appliances with SCOM 2007R2, this was working quite fine for some years. Some months ago we have decided to migrate them to SCOM 2012 as would like to shut down the old system – but the discovery was not working the devices got only the status: No Response SNMP


What was the problem?

The SNMP device discovery and monitoring has improved very much in SCOM 2012 – many well known vendors and devices will be automatically discovered and monitored with some basic counters. As our appliances were fully custom hardware boxes, the problem was a missing OID response:

103:          OBJ-ID (0x06), 8 bytes == “.”
113:          Exception (IMPLICIT NULL) (0x80), 0 bytes == <noSuchObject>

After clarification with Microsoft we now know that the following OID’s MUST exist and appropriate values must be visible:

  • . (sysDescr)
  • . (sysObjectID)
  • . (sysContact)
  • . (sysName)
  • . (sysLocation)

If only one of them is missing your discovery will fail 🙁

5 thoughts on “SNMP discovery fails in SCOM 2012

  1. CypherBit

    I understand the must requirement, but are there any workarounds? Can a device without these OID’s have any kind of SNMP monitoring through SCOM?

  2. Dave

    It would be nice to have a KB article to point to.

    Also,sysObjectID and perhaps sysName should be the only necesary OID’s. The other’s shouldn’t really matter. I’ve come accross various devices that partially implement MIB-II, skipping sysContact or sysLocation and thus failing to be discovered. It is disapointing, because I could write up an MP to monitor these devices otherwise, but need the initial discovery to suceed!

    Anyway, thanks for your information. I suppose, if there is are any other details from the ticked raised with Microsoft that you could share, that would be nice.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.