Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Enable SNMP monitoring in SCOM

Enable SNMP monitoring in SCOM

Overview

This article provides detailed steps to enable SNMP monitoring in System Center Operations Manager (SCOM) and configure a rudimentary SNMP-trap receiver to collect all messages sent from DPA alerts.

Environment

All DPA versions

Steps

Task 1: Configure OpsMgr as an SNMP Trap Receiver

  1. On the SCOM Server, install the SNMP Service if it is not already installed:
    1. In the Control Panel, select Add Remove Programs.
    2. Click on Add/Remove Windows Components.
    3. Scroll down and select Management and Monitoring Tools, click Details.
    4. Click on the checkboxes for Simple Network Management Protocol and WMI SNMP Provider and click OK.
    5. Click Next and click Finish.
  2. Configure the SNMP Service on the SCOM server:
    1. Close Add or Remove Programs.
    2. Click Start, Run, type services.msc, and then click Enter.
    3. Scroll down and select SNMP Service. Right-click the service and select Properties.
    4. Select the Security tab.
    5. 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.
      IMPORTANT: SNMP community strings are case sensitive!
    6. Select the Accept SNMP packets from any host option.
    7. Restart the SNMP Service.

Task 2: Configure the DPA Server to communicate with the OpsMgr Mgmt Server

The DPA server must be configured to accept SNMP requests from the Mgmt Server. You must also configure the DPA Server SNMP service to use the same SNMP community string you configured in the Accepted community names in the SNMP Service properties on your OpsMgr server.

  1. In DPA, click Options > Administration tab > Contacts and Contact Groups.
  2. On the Contact Management page, click Create SNMP Contact.
  3. Complete the dialog. Enter the SCOM host IP and Port (usually 162). Enter the community string that was set up on the SNMP Service on the SCOM Host.
  4. On the application server, make sure the SNMP service is running and the community string is set to the correct community string. In the above example, ‘public’ is the community string. This string is case sensitive.

Task 3: In SCOM, configure one or more Alert-generating SNMP-Trap-based Rules

  1. Create a unsealed management pack to store your SNMP-based monitoring rules.
  2. In the Operations console, start the Create Rule Wizard.
  3. On the Select a Rule Type page, do the following:
  4. Expand Alert Generating Rules > Event Based > SNMP Trap (Alert).
  5. Select your unsealed management pack from the list. Click Next.
  6. On the Rule Name and Description page, do the following:
    1. Type the Rule name, such as DPA Alert Collection Rule. Optionally, type a Description for the rule.
    2. Click Select, then check the ‘select View all targets’ box, choose the SNMP Network Device, and then click OK.
    3. Leave the ‘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.
  7. On the Configure the trap OIDs to collect page, leave Use discovery community string selected.
  8. 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.

Configure the DPA trap OID to collect (.1.3.6.1.4.1.22980) or select All Traps, which will raise an alert for any trap received from the Ignite server which you will discover with the Add Monitoring Wizard. You can also check the ‘use custom community string’ and enter the specific string.

  1. On the Configure Alerts page, set the properties of the alert, for example:
    1. Type the Name for the alert, such as Routers Traps Alert.
    2. 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.
    3. Select a Priority from the list, such as High.
    4. Select a Severity from the list, such as Error.
    5. Optionally, click Custom alert fields and type values, or click the (…) button and insert variables in the custom fields, and then click OK.
    6. 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.
  2. Click Create.

Task 4: Discover the DPA Server in OpsMgr

  1. In the Administration space, right-click and launch the Discovery Wizard.
  2. On the Auto or Advanced page, select Advanced discovery.
  3. In the Computer & Device Types list, select Network Devices.
  4. In the Management Server list, select the Management Server you will use to discover objects. Click Next.
  5. On the Discovery Method page, enter the Start and End of the IP address range that you want to scan.
  6. Type the SNMP community of the objects that you want to manage.
  7. 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 Ignite server for management. Click Change.
  • 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.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified

Tags

Classifications

Public