SNMP Series: Part 4 – Configuring OpsMgr 2007 as an SNMP Trap Receiver

This article is going to address another question I get pretty frequently in the community and the classroom: How do I configure Operations Manager or Essentials 2007 as an SNMP Trap Receiver? The configuration steps are not really well documented, so this can take some trial-and-error in practice. In this post, we will configure Operations Manager 2007 as an SNMP Trap Receiver, discover SNMP-enabled network devices, and configure a alert-generating SNMP-trap-based rule to raise alerts when traps are received from network devices.

Previous Posts

 

This questions sometimes takes other forms like “Why is OpsMgr ignoring the SNMP traps from my network devices?”. At the end of the day, trap-based SNMP monitoring in OpsMgr can be configured in 4 steps:

  1. Configure OpsMgr as an SNMP Trap Receiver
  2. Configure your SNMP-enabled device to communicate with the OpsMgr Mgmt Server
  3. Configure one or more Event-based Trap Rules or Monitors
  4. Discover your SNMP-enabled Network Devices in OpsMgr
 
The following are the detailed steps in configuring a rudimentary SNMP-trap based monitoring scenario to collect all traps sent from monitored devices.
 

1. Configure OpsMgr as an SNMP Trap Receiver

Install the SNMP Service

  • In the Control Panel, select Add Remove Programs
  • Click on Add/Remove Windows Components
  • Scroll down and select Management and Monitoring Tools, click Details.
  • Click on the checkboxes for Simple Network Management Protocol and WMI SNMP Provider and click OK.
  • Click Next and click Finish.
 

Configure the SNMP Service

  • Close Add or Remove Programs.
  • Click Start, Run, type services.msc, and then click Enter.
  • Scroll down and select SNMP Service. Right click the service and select Properties.
 
 
 
  • Select the Security tab.
  • Check the Send Authentication Traps checkbox. In the Accepted Community Names list, type “public” and click the Add to list button. Rights should be set to READ CREATE.
  • Select the Accept SNMP packets from these hosts radio button. Use the add button to add the IP addreesses of the managed devices that will forward SNMP traps to the OpsMgr server. Alternatively, you could select the Accept SNMP packets from any host option.
  • Restart the SNMP Service.

 

IMPORTANT: SNMP community strings are case sensitive!

 

2. Configure your SNMP-enabled device to communicate with the OpsMgr Mgmt Server

This process will vary for each device. However, the common thread here is that the device must be configured to accept SNMP requests from teh Mgmt Server (and proxy agent, if you designated one for device availability monitoring). You must also configure the device to use the same SNMP community string you configured in the Accepted community names in the SNMP Service properties on your OpsMgr server.

3. Configure one or more Alert-generating SNMP-Trap-based Rules

  • Create a unsealed management pack to store your SNMP-based monitoring rules.
  • In the Operations console, start the Create Rule Wizard.
  • On the Select a Rule Type page, do the following:
  • Expand Alert Generating Rules –> Event Based –> SNMP Trap (Alert).
  • Select your unsealed management pack from the list. Click Next.
  • On the Rule Name and Description page, do the following:
  • Type the Rule name, such as Default Trap Alert Collection Rule. Optionally, type a Description for the rule.
  • Click Select, select View all targets, click a target, such as SNMP Network Device, and then click OK.
  • Leave Rule is enabled selected to have the rule take affect at the completion of the wizard, or clear the check box to enable the rule at a later time, and then click Next.
  • On the Configure the trap OIDs to collect page, leave Use discovery community string selected.
  • Click to place the cursor in the Object Identifier Properties section and type the object identifier (OID) of each property of the network devices that you want to monitor, or select All Traps to monitor all targeted objects of the community, and then click Next.
 
For this example, simply select All Traps, which will raise an alert for any trap received from an SNMP-enabled device you have discovered with the Add Monitoring Wizard.
 
  • On the Configure Alerts page, set the properties of the alert, for example:
  • Type the Name for the alert, such as Routers Traps Alert.
  • Optionally, type the Alert description. You can also click the (…) button and select Target and Data variables to include in the description, such as IP Address.
  • Select a Priority from the list, such as High.
  • Select a Severity from the list, such as Error.
  • Optionally, click Custom alert fields and type values, or click the (…) button and insert variables in the custom fields, and then click OK.
  • Optionally, click Alert suppression, and then select one or more Fields of the alert. Alert suppression is useful when there are multiple alerts for the same issue.
  • Click Create.
 

4. Discover your SNMP-enabled Network Devices in OpsMgr

Network device discovery works differently than server, discovery. You can find a detailed explanation of the behind-the-scenes processes HERE.
 
  • In the Administration space, right click and launch the Discovery Wizard.
  • On the Auto or Advanced page, select Advanced discovery.
  • In the Computer & Device Types list, select Network Devices.
  • In the Management Server list, select the Management Server you will use to discover objects. Click Next.
  • On the Discovery Method page, enter the Start and End of the IP address range that you want to scan.
  • Type the SNMP community of the objects that you want to manage.
  • Click Discover to display the Discovery Progress page.
 
Discovery for even a single device will run for a couple of minutes by default. If you specify an IP range, it will take a little longer.
 
  • On the Select Objects to Manage page, select the devices desired for management.
  • Click Change, and then click the desired computerto serve as the proxy agent for the devices selected for monitoring.
  • The proxy agent can be any agent-managed computer or Mgmt Server. (SNMP should be installed on this computer)
  • On the Summary page, click Finish. The objects will display in the Network Devices node of the Operations Console Administration space.
 
At this point, SNMP-enabled device availability monitoring will start automatically, as described HERE. Any traps received from the target devices will be raised as alerts in the Operations console.
 

Conclusion

This is a rudimentary, but hopefully adequately detailed walkthrough. If you have any questions or feedback, simply post them as a comment to this article.

4 thoughts on “SNMP Series: Part 4 – Configuring OpsMgr 2007 as an SNMP Trap Receiver

  1. Profile photo of RTMRTM

    Hi!

    I’m using SCOM 2007 R2, followed your steps, but I don’t see any alerts on SCOM. (by the way, the discovery wizard is litle bit different on R2).
    I checked with wireshark, and the traps are received on the server.
    I have SNMP Trap service running, it is necessary, correct?
    Do I need to configure a Monitor to view the Traps?
    Thanks and best regards,
    RTM

  2. Profile photo of JBJB

    Hi, Thx for the series.

    One question though…

    I did not think that the SNMP service actually needed to be turned on.

    OpsMgr is just receiving traps so that is taken care of by the SNMP Trap service.

    Can u pls verify at your end as I get traps OK without the SNMP service being on.

    Thx,

    John Bradshaw

  3. Profile photo of Albert JohnAlbert John

    For snmp devices that are discovered with snmp version, 1 I’m not able to receive any alerts or traps. I ran wireshark and I can see the traps going through.

Leave a Reply