locked
SCOM 2012 unable to monitor SNMP traps RRS feed

Answers

  • Hello,

    I had the same problems with traps in scom 2012!

    Guess what... After disabling "snmp service" and "snmp trap" Services, rebbooted the servers and traps are working.

    Try and say something.

    I Think "snmp service" is only needed in the case of network devices managed by RMS emulator (upgrade from 2007 to 2012), but... traps in native 2012 network monitoring, only work with the 2 services disabled.


    • Edited by HermanoF Friday, May 25, 2012 10:56 AM
    • Proposed as answer by System Center guy Sunday, May 27, 2012 5:38 PM
    • Marked as answer by Yog Li Tuesday, June 5, 2012 9:06 AM
    Friday, May 25, 2012 10:37 AM

All replies

    1. Make sure that snmp Trap and snmp service are running
    2. Make sure that you can discover the snmp device
    3. check whether you snmp monitor is setup correctly.

    for detail pls refer

    configurescom as a trap receiver

    http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/13020/Default.aspx

    SNMP Trap monitor

    http://www.blackops.ca/cms/blog/?tag=snmp

    roger

    Tuesday, May 22, 2012 3:27 PM
  • Can you also make sure snmp service starts before healthservice.

    http://nocentdocent.wordpress.com/2010/07/30/are-your-snmp-traps-working/

    Thanks,

    Varun

    Tuesday, May 22, 2012 4:04 PM
  • SCOM 2012 by default disables the snmp Trap service.

    And the documentation for SCOM 2012 http://technet.microsoft.com/en-us/library/hh561709.aspx#BKMK_NetworkMonitoring indicated that the service should be disabled, otherwise the SNMP Traps will not work.


    • Edited by PashaZ Tuesday, May 22, 2012 5:58 PM
    • Proposed as answer by Alexis Yakovlev Tuesday, October 30, 2012 7:05 PM
    Tuesday, May 22, 2012 5:58 PM
  • I have to reinstall the operating system. Installed SCOM 2012. Set up a rule as written here http://startblog.hud.de/2011/12/snmp-traps-im-operations-manager-2012/
    Still does not receive SNMP Trap.
    At the same SNMP-GET request is successfully executed
    • Edited by PashaZ Wednesday, May 23, 2012 8:45 AM
    Wednesday, May 23, 2012 8:42 AM
  • Install and configurethe SNMP serviceis written in http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/13020/Default.aspx and http://www.blackops.ca/cms/blog/?tag=snmp . Configure community.
    The result - SNMP Traps do not work. Help please!


    • Edited by PashaZ Thursday, May 24, 2012 1:03 PM
    Thursday, May 24, 2012 1:02 PM
  • Did it ever work in SCOM 2007 ???

    If this is your first time installing and using SCOM, make sure the SNMP trap service is turned off and is not running.

    Then, you will need to ensure that you SCOM manager server is able to receive the trap.  Run Netmon to ensure you are receiving the trap.  Then configure the SNMP agent based monitoring.

    You will have to set up the OID, and associated rules.

    I know this is very high level, if you need specifics, let me know and I will post it.  We just got SNMP working and we are excited to retire HP Openview using SCOM 2012 production version


    hyohoonk@hotmail.com


    Thursday, May 24, 2012 7:58 PM
  • I have worked previously with SCOM 2007, no problems.
    Microsoft Trap Service is disabled, SNMP Service is set up. The server receives the trap i am checked with snmpitul. SCOM opens port 162 to listen, but does not receive traps.
    There may be a problem due to language differences SCOM and Windows Server?
    • Edited by PashaZ Friday, May 25, 2012 6:13 AM
    Friday, May 25, 2012 6:07 AM
  • HI PashaZ, I have not gone through all links in the post, but have you checked the windows firewall? http://www.bictt.com/blogs/bictt.php/2012/05/23/scom-2012-network-device-no for example.

    Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

    Friday, May 25, 2012 6:55 AM
  • I have checked the windows firewall before. These options are activated. Also I tried to include all incoming and outgoing traffic on a server. Result no.
    Friday, May 25, 2012 7:03 AM
  • Hello,

    I had the same problems with traps in scom 2012!

    Guess what... After disabling "snmp service" and "snmp trap" Services, rebbooted the servers and traps are working.

    Try and say something.

    I Think "snmp service" is only needed in the case of network devices managed by RMS emulator (upgrade from 2007 to 2012), but... traps in native 2012 network monitoring, only work with the 2 services disabled.


    • Edited by HermanoF Friday, May 25, 2012 10:56 AM
    • Proposed as answer by System Center guy Sunday, May 27, 2012 5:38 PM
    • Marked as answer by Yog Li Tuesday, June 5, 2012 9:06 AM
    Friday, May 25, 2012 10:37 AM
  • After searching for cause of the problem with SNMP Traps for a week returned to SCOM 2007.
    In SCOM 2007 SNMP Traps earned without any problems.
    Friday, May 25, 2012 10:55 AM
  • I had gone through this scenario recently as well. Was very frustrating for SCOM 2012. I detailed how I got SNMP setup on this blog post: http://scom-2012.blogspot.com/2012/07/setting-up-snmp-monitoring-in-scom-2012.html This setup has been tested at a couple of sites that I manage.
    Tuesday, July 10, 2012 1:22 AM
  • Thx a million Mr.Murphy! Good post.

    John Bradshaw

    Tuesday, July 10, 2012 11:12 AM
  • You're welcome. Another thing to consider is that the traps coming in have to match what SCOM detected it as. For example, if you test with SNMP v1 traps, but the device was detected as v2c SNMP, then it will not report on the traps coming in. Also, traps from vendors like F5 may not get picked up either, even if SNMP is functioning properly. So far, we've had good success with Cisco and Linux based devices out in the field. Definitely having a LINUX server on hand can make validation quick and easy.
    Wednesday, July 11, 2012 11:41 PM
  • D. Murphy - Thanks!
    SNMP protocol SNMP traps and Discovery must match.
    • Edited by Vlasov_SV Monday, October 8, 2012 6:16 AM
    Monday, October 8, 2012 6:13 AM
  • Hello, I tried the disabling of both services, initiated a reboot and tried sending a trap again from a Dell Storage device that has been discovered by SCOM 2012 and have correct trap destination and community string configured but nothing in SCOM. I have also uninstalled the SNMP Trap service to see if that helps, but no luck.

    Anything I am missing?

    Thanks,

    Kapil Dham


    Kapil Dham

    Tuesday, October 16, 2012 5:45 PM
  • Install netmon.exe on your system center management server, and...

    1. send snmp trap message from the client machine that you are interested in monitoring.

    2. examine the netmon data to see if you are getting the message arriving at your system center management server.




    Wednesday, October 24, 2012 9:18 PM
  • I'm confused, several posts say disable the windows SNMP & SNMP Trap services, yet others reference they should be installed, configured, and started.

    Should they be installed and running with SCOM? 


    B. Wright

    Tuesday, October 30, 2012 5:32 PM
  • Tuesday, October 30, 2012 7:20 PM
  • Also note!  If you have discovered the SNMP device with SNMP v2 then the SNMP traps need to be V2 also.  The discovery mechanism will discover SNMP v2 first and failover to V1.  but all traps must be the same version as the device was discovered with.  

    Tim M.

    Friday, April 19, 2013 3:58 PM
  • Right on Tim. That was my issue. The device was sending v1 traps to OpsMgr and so they were not being processed correctly. I configured traps on my Cisco network devices like this

    snmp-server host x.x.x.x version 2c publicstring


    • Proposed as answer by Hollisorama Wednesday, June 25, 2014 9:07 PM
    Wednesday, June 25, 2014 9:07 PM
  • Anyone know if DELL DRACs send v1, or v2??

    Thx,

    JB

    Wednesday, June 25, 2014 10:31 PM
  • I did some checking around but couldn't find what version is used.  I guess if you're not receiving traps but the device is discovered, it could indicate a mismatch.  You could always re-discover the device with a specific version and see if that helps
    Thursday, June 26, 2014 1:24 PM
  • Hollisorama, How do I rediscover the device specifying only V 1 snmp or V 2? There is only 2 options to discover network devices that I can see, v1 and v2 or v3 in SCOM 2012?
    • Edited by bmac000 Monday, November 3, 2014 5:02 AM
    Monday, November 3, 2014 5:01 AM
  • bmac000,

    You could delete the device and have OpsMgr do a rediscovery.  Also, make sure that you configure your switch to only send v2 traps.  On a Cisco switch that config is usually like this "snmp-server host x.x.x.x version 2c publicstring"

    Monday, November 3, 2014 4:06 PM
  • Thanks for the reply, sorry I should have been a little more clearer, I realize you can change it on a switch for example but is there any way of changing this in SCOM 2012 itself, so for eg can I set SCOM 2012 to use just V 2 SNMP? One of my troublesome devices that I cannot discover is a MARMS UPS so I doubt I can change the SNMP version on that. Thanks.
    Tuesday, November 4, 2014 11:05 PM
  • I believe that is a function of the trap versions being sent by the device to OpsMgr.  OpsMgr will discover via SNMP v2 if the device supports it, but if the device then sends version 1 traps, that's where there is a problem.  If OpsMgr knows the device by SNMP v2 but the device sends v1 traps, monitoring doesn't work. 

    Is the device you are trying to discover on the list of supported devices?

    Tuesday, November 4, 2014 11:10 PM
  • Tuesday, November 4, 2014 11:11 PM
  • We had the an issue where device was sending SNMP v1 traps as per Wireshark but the device was discovered as a SNMP v2 device. We forced the device to be discovered as a SNMP v1 device and that worked.

    To do so, after you add the device that needs to be discovered within the discovery rule, export the MP called Network Discovery Internal. Open this in notepad and browse to the IP address of your device that needs to be discovered. Change the value for "AutoDetect" to v1 in case you want to discover his as a V1 DEVICE. Then you will be able to receive traps from the said device that got discovered.

    <SeedSystem>
                      <SeedIPorName>10.100.x.x</SeedIPorName>
                      <Version>AUTODETECT</Version>
                      <SNMPPort>161</SNMPPort>
                    </SeedSystem>

    Hope this helps.


    Kapil Dham

    Wednesday, November 5, 2014 7:03 PM
  • No the old Riello MARMS UPS is not on the supported devices list but my netscreen SSG-140 is. Thanks for this link. I must also add that I ran wireshark on scom and its sending SNMP to the UPS using v1 and the UPS is sending traps back using v1, so the fact that its not on the supported devices list explains why I cannot discover it.
    • Edited by bmac000 Friday, November 7, 2014 12:03 AM
    Thursday, November 6, 2014 11:55 PM
  • Kapil thanks for your post, This is my problem on the Netscreen SSG-140 firewall. I ran wireshark and detected that SCOM sends out SNMP v2c to the firewall which is sending traps using V1. I will try your suggestion by forcing the firewall to be discovered using V1 only. 
    Friday, November 7, 2014 12:01 AM