locked
Custom device SNMP discovery error RRS feed

  • Question

  • Hi, i'm having an issue to discover a custom device that monitor temperature in the datacenter with SCOM 2012 R2

    The device measures the temperature and expose it in a OID. When I run the discovery it gets stucked in "pending management", I runned a wireshark to view the network activity and I get the following result:

    • 2 get request (snmp v2 and v1)
    • both got a null error when quering the OID: 1.3.6.1.2.1.1.6.0.0 (sysLocation)
    • Communication stops after the 2 get request

    is this a terminal error for the discovery? I verified that the device does not have that OID configured (tried to set it..)

    Can i override that oid for the discovery?

    Thanks!!

    Monday, April 4, 2016 4:02 PM

Answers

  • Hi guys, just to confirm you, the SysLocation OID 1.3.6.1.2.1.1.6.0.0 IS REQUIRED TO EXIST IN THE DEVICE MIB (Null is accepted). 

    The manufacturer add to the firmware the OID1.3.6.1.2.1.1.6.0.0 variable and the discovery went through!

    Soooo bottom line, if the OID1.3.6.1.2.1.1.6.0.0 SysLocation variable does not exist, the discovery will hang

    • Marked as answer by JoaquinGomez Tuesday, May 31, 2016 4:40 PM
    Tuesday, May 31, 2016 4:40 PM
  • Actually you need to confirm to rfc1213 (mib-II sys). I think only the sysid is really needed, but the network discovery process is really fuzzy (as in a hardcoded blackbox without much info out there).

    However you can enable some extra logging:C:\Program Files\System Center Operations Manager 2012\Server\NetworkMonitoring\conf\discovery\discovery.conf              

    Change from:

    DebugEnabled = FALSE

    #LogDiscoveryProgress = TRUE

    #enableICMPTrace = TRUE

    #enableSNMPTrace = TRUE

                   To

    DebugEnabled = TRUE

    LogDiscoveryProgress = TRUE

    enableICMPTrace = TRUE

    enableSNMPTrace = TRUE

    In windows\temp for each individual device should get a logfile.


    Rob Korving
    http://jama00.wordpress.com/

    • Proposed as answer by Yan Li_ Thursday, April 14, 2016 2:04 AM
    • Marked as answer by Yan Li_ Wednesday, April 20, 2016 5:36 AM
    Thursday, April 7, 2016 12:21 PM

All replies

  • Hello,

    Here is the list of supported network devices that can be discovered by SCOM 2012:

    https://blogs.technet.microsoft.com/jonathanalmquist/2011/08/11/list-of-supported-network-devices-in-operations-manager-2012/

    Please check whether your device is listed in it.

    In addition, you can also refer to the article below to troubleshoot network discovery:

    http://www.code4ward.net/2011/08/11/troubleshooting-network-discovery-in-scom-2012/

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Yan Li_ Tuesday, April 5, 2016 6:45 AM
    Tuesday, April 5, 2016 6:41 AM
  • Hi Yan!

    No it is NOT listed as supported network device. I have troubleshoted the issue to this problem: my SNMP device does not have configured the OID 1.3.6.1.2.1.1.6.0.0 (sysLocation).

    Please, someone Knows if the OID  sysLocation is a required OID for the discovery to happen? 

    Is there a way to add this device to SCOM?

    If i can get it out of pending devices, i can then create the custom SNMP monitoring. But I need to know if it is possible or am I just wasting my time?

    Thanks!!

    Tuesday, April 5, 2016 5:45 PM
  •  I run the discovery it gets stucked in "pending management".
    Please refer to Kevin Holman's System Center Blog on how to discovery a network device. Especially the runas account and SNMP version.
    https://blogs.technet.microsoft.com/kevinholman/2011/07/20/opsmgr-2012-discovering-a-network-device/
    Roger
    Wednesday, April 6, 2016 4:01 AM
  • Hi,

    >if the OID  sysLocation is a required OID for the discovery to happen?

    No, it's not required to be non-null.

     >But I need to know if it is possible or am I just wasting my time?

    If your device supports SNMP (V1\2\3) - it's possible to discover a device. For any 'unsupported' device you'll get only ICMP Ping\SNMP "ping" monitors, if you want to monitor anything else - you'll have to find a management pack or create your own.

     For troubleshooting you can download something like Net-SNMP tools and check if your device "answer" properly for requests (using community and version you have in your discovery rule).


    http://OpsMgr.ru/

    • Proposed as answer by Yan Li_ Thursday, April 14, 2016 2:03 AM
    • Marked as answer by Yan Li_ Wednesday, April 20, 2016 5:36 AM
    • Unmarked as answer by JoaquinGomez Tuesday, May 31, 2016 4:37 PM
    Wednesday, April 6, 2016 4:27 AM
  • Actually you need to confirm to rfc1213 (mib-II sys). I think only the sysid is really needed, but the network discovery process is really fuzzy (as in a hardcoded blackbox without much info out there).

    However you can enable some extra logging:C:\Program Files\System Center Operations Manager 2012\Server\NetworkMonitoring\conf\discovery\discovery.conf              

    Change from:

    DebugEnabled = FALSE

    #LogDiscoveryProgress = TRUE

    #enableICMPTrace = TRUE

    #enableSNMPTrace = TRUE

                   To

    DebugEnabled = TRUE

    LogDiscoveryProgress = TRUE

    enableICMPTrace = TRUE

    enableSNMPTrace = TRUE

    In windows\temp for each individual device should get a logfile.


    Rob Korving
    http://jama00.wordpress.com/

    • Proposed as answer by Yan Li_ Thursday, April 14, 2016 2:04 AM
    • Marked as answer by Yan Li_ Wednesday, April 20, 2016 5:36 AM
    Thursday, April 7, 2016 12:21 PM
  • Hi guys, just to confirm you, the SysLocation OID 1.3.6.1.2.1.1.6.0.0 IS REQUIRED TO EXIST IN THE DEVICE MIB (Null is accepted). 

    The manufacturer add to the firmware the OID1.3.6.1.2.1.1.6.0.0 variable and the discovery went through!

    Soooo bottom line, if the OID1.3.6.1.2.1.1.6.0.0 SysLocation variable does not exist, the discovery will hang

    • Marked as answer by JoaquinGomez Tuesday, May 31, 2016 4:40 PM
    Tuesday, May 31, 2016 4:40 PM
  • very nice feedback, thanks

    Rob Korving
    http://jama00.wordpress.com/

    Wednesday, June 1, 2016 10:39 AM