Hi everybody, We test SCOM 2012 with SNMP devices. We discovered our SNMP devices and can see them in Monitoring section of the console. We created Collection Rule (SNMP trap event) with empty OID field to gather all received SNMP traps. And we created an event view to see those traps/events as well. Then we created a SNMP trap alert rule following TechNet guide (which is like this) for one specific OID. Simply saying it doesn't work at all. We tried 2 setups (with RU2 and without). We also tried to add/remove disabled SNMP services of Windows. It seems this feature doen't work. If we changed that rule and emptied OID field in the DataSource then the rule starts generating alerts for each and every SNMP trap. So we can't say that this workflow doesn't work. But we can't make the rule filter SNMP traps by OID. However we found 2 default rules in MP named Network Management - Core Monitoring ("System.NetworkManagement.Monitoring") which use the same syntax with <OIDProps> tag. That gave us some hope. Maybe we forgot something to check/setup? Does anyone have a success doing the same kind of SNMP trap alert rule? BR, Marat

Please refer to this blog http://scom-2012.blogspot.hk/2012/07/setting-up-snmp-monitoring-in-scom-2012.html Roger

Firstly, I would like to suggest you double check the settings referring to the following document: SNMP Events http://technet.microsoft.com/en-us/library/hh563870.aspx In addition, about SNMP monitoring, please refer to the following posts: Configuring OpsMgr 2007 as an SNMP Trap Receiver http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexId/13020/Default.aspx SNMP, OIDs and SCOM: Lets start rocking! http://thoughtsonopsmgr.blogspot.com/2011/10/snmp-oids-and-scom-lets-start-rocking.html Hope this helps. Thanks.Nicholas Li TechNet Community Support

Roger and Nicholas, Thanks for your input but we've checked all above mentioned links at the very beginning. None of them helped us find the solution. I seem it'd better to report a bug to connect.microsoft.com if nobody give the good idea. Marat

From my experience, please check whether the oid value which input into the montor rule is match to the oid vlue of snmp trap. Roger

There is an issue with trap monitoring with SCOM 2012, which was not present in SCOM 2007 R2: You cannot receive SNMP v1 traps when your device has been discovered as an SNMP v2 or v3 network device. The problem is that you can only choose: 'v1 or v2' OR v3. You cannot choose to discover your v2 device as v1. The workaround I use is using snmp-gets and interpret the values.

Roger, we used Wireshark to catch/check SNMP traps. As I described in my first post we're able to get traps and even to make a trap event view in OM2012 console. The problem is that we can't make the rule work for the specific OID. And, of course, we checked OID value and event tried to use a different syntax (with dot first or numeral, i mean .1.2.3.4.5 or 1.2.3.4.5) with no lack. David, we work with SNMPv1 device. We can record traps if our rule is generic (with empty OID) as in Roger's linkdescribed. But if we use a concrete OID the rule stop working (at least it doesn't generate alerts). Marat

Can you tell us what device it is and what specific OID you used? Did your OID start with a dot or with a number?

David, we tried with a linux router, network printer, custom applications and generated traps with MIB browsers. As I mentioned before we used OID started with dot and a number. Marat

David, we trie with a linux router, network printer, custom applications and generated traps with MIB browsers. As I mentioned before we used OID started with dot and a number. Marat