Skip to main content

System Center Operations Manager 2012 (SCOM) - SNMP device discovery

Lately I have been working in SCOM with SNMP devices. Needless to say I have learned some new tricks I would like to share with you.

Firstly you may have run into the dreaded "No response SNMP" message in Network Devices Pending Management in the SCOM console. First thing that jumps out is network connectivity, however I have seen cases that that is not the issue. Based upon my experience the message is very generic and could have several causes:

1. Network connectivity

 Firewall (on the SCOM server or one of the SCOM servers that is a member of the resourcepool specified in the discovery rule) or between the SCOM-server and the SNMP device.
    2. SNMP-device configuration

    The target SNMP device needs to enable the whole system MIB/OID-tree to be discoverable in SCOM. If any of the following OIDs are missing, you will not be able to discover the device:
    • 1.3.6.1.2.1.1.1.0 --> system.sysDescr
    • 1.3.6.1.2.1.1.2.0 --> system.sysObjectID
    • 1.3.6.1.2.1.1.4.0 --> system.sysContact
    • 1.3.6.1.2.1.1.5.0 --> system.sysName
    • 1.3.6.1.2.1.1.6.0 --> system.sysLocation

    3. SCOM host SNMP configuration

    Please follow microsoft recommandations on how to configure your SCOM server to be able to communicate with the SNMP protocol.


    Regarding network connectivity you have a lot of options. First on your list should be to temporarily disable the firewall and verify that you are still unable to discover the device with the firewall turned off. Next step should be to verify that the device is responding to ping requests. Further you should also verify SNMP UDP connectivity on port 161. There are a number of tools available for you to use. Paessler has an SNMP test tool (http://www.paessler.com/tools/snmptester)with a GUI and a console application you can use in scripts. Very handy if you need to add many devices and check if the device is on the certified SNMP device list from Microsoft. More on this later.

    Recently I have been experiencing issues with SCOM when there are no network connectivity issues and I have verified that SCOM is able to communicate with the device via SNMP. Time to get low, dirty and bring out the bag of tricks.

    First thing is to enable SNMP device discovery debug-tracing in SCOM. This is done in the file located in:
    C:\Program Files\System Center 2012\Operations Manager\Server\NetworkMonitoring\conf\discovery 

    and is called discovery.conf. Open the file in notepad and set the following:

    DebugEnabled = TRUE
    LogDiscoveryProgress = TRUE
    enableSNMPTrace = TRUE
    enableICMPTrace = TRUE

    LogDiscoveryProgress is not in the file, you will have to add it. Save the file and restart the healthservice on the SCOM server. You may use this powershell command:
    Get-Service –name healthservice |restart-service –verbose
    To be continued…
    Labels:

    Comments

    1. AnonymousMay 6, 2016 at 6:59 PM

      Where is the "continued" post?

      ReplyDelete
    2. Tore GronengMay 6, 2016 at 9:09 PM

      Hi, sorry, it is one of the many things I have not yet been able to get to. Long overdue I admit.

      ReplyDelete
    3. UnknownJuly 20, 2018 at 12:16 PM

      Hi Tore,

      Have you forgot the continued post? :)

      ReplyDelete
      Replies
      1. Tore GronengOctober 29, 2018 at 2:35 PM

        hi, well kinda. The world have moved on to better things in the cloud. SCOM is not really something that I have been working on the last 2 years. Sorry, this will never be continued :-)

        Delete

    Post a Comment

    Popular posts from this blog

    Serialize data with PowerShell

    Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData. Other Serializing methods In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in: Export-CliXml ConvertTo-JSON Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types: (Hashdata.Object.ps1) You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate t
    Post a Comment
    Read more

    Toying with audio in powershell

    Controlling mute/unmute and the volume on you computer with powershell. Add-Type -TypeDefinition @' using System.Runtime.InteropServices; [Guid("5CDF2C82-841E-4546-9722-0CF74078229A"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IAudioEndpointVolume { // f(), g(), ... are unused COM method slots. Define these if you care int f(); int g(); int h(); int i(); int SetMasterVolumeLevelScalar(float fLevel, System.Guid pguidEventContext); int j(); int GetMasterVolumeLevelScalar(out float pfLevel); int k(); int l(); int m(); int n(); int SetMute([MarshalAs(UnmanagedType.Bool)] bool bMute, System.Guid pguidEventContext); int GetMute(out bool pbMute); } [Guid("D666063F-1587-4E43-81F1-B948E807363F"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IMMDevice { int Activate(ref System.Guid id, int clsCtx, int activationParams, out IAudioEndpointVolume aev); } [Guid("A95664D2-9614-4F35-A746-DE8DB63617E6"), Inte
    3 comments
    Read more

    Creating Menus in Powershell

    I have created another Powershell module. This time it is about Console Menus you can use to ease the usage for members of your oranization. It is available on GitHub and published to the PowershellGallery . It is called cliMenu. Puppies This is a Controller module. It uses Write-Host to create a Menu in the console. Some of you may recall that using Write-Host is bad practice. Controller scripts and modules are the exception to this rule. In addition with WMF5 Write-Host writes to the Information stream in Powershell, so it really does not matter anymore. Design goal I have seen to many crappy menus that is a mixture of controller script and business logic. It is in essence a wild west out there, hence my ultimate goal is to create something that makes it as easy as possible to create a menu and change the way it looks. Make it easy to build Menus and change them Make it as "declarative" as possible Menus The module supports multiple Men
    Post a Comment
    Read more