![scom snmp trap receiver scom snmp trap receiver](https://www.informaticar.net/wp-content/uploads/2017/08/SCOM_2012_HP_Management2.jpg)
And then there’s the caveat I spent my time on, the integration between OpsMgr agent and the snmp trap service: For example if the trap service is down you won’t get any error or warning message in the event log, so you better do your job right.
![scom snmp trap receiver scom snmp trap receiver](https://www.eginnovations.com/documentation/Resources/Images/Integrating-eG-Enterprise-with-Third-party-SNMP-Management-Systems-HP-OpenView/Configuring-the-SNMP-Managers.jpg)
This is all you need to do to set the SNMP environment for OpsMgr, but do not expect any help from OpsMgr itself. If you want to get snmp traps the device must be discovered and the snmp trap sender IP address must match the discovered device address.Same story for the trap configuration, no specific configuration is needed, once again is the agent duty to set it properly The snmp OS configurations are for incoming SNMP messages not for outgoing one, is the agent (in this case OpsMgr) that needs to take care of the proper settings (community, version and so on). Contrarily on what you find on the web no particular configuration is needed.As you may suspect the SNMP service must be installed and started as well as the snmp trap service.In this article I want to recap what I found, many of these points may seem obvious, but since I spent a few hours getting rid of this mess I think it is worth to nail them down: What I found is while the snmp discovery and monitor process is well documented, the documentation on snmp traps is scarce and many in the community keeps complaining about snmp traps not working. I had scarce experience in SCOM snmp modules so I had to check the documentation and other articles from the community. This week I’ve been involved in an internal project to integrate HP Procurve Manager alerts in SCOM, between the various strategy I tried one was to use snmp traps.