Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Problems in SAM with SNMP Process Monitors failing

Problems in SAM with SNMP Process Monitors failing

Created by Erin Stenzel, last modified by carolyn.mazenko on Aug 16, 2018

Views: 1,950 Votes: 0 Revisions: 3

Updated August 16, 2018

Overview


SNMP Process Monitors in SolarWinds SAM fail due to the large number of SNMP requests they are generating.

Environment

  • SAM 6.2 and later

Resolution

You can change how the SNMP Process Monitor gets information about processes from remote nodes. This may reduce the number of SNMP requests that the SNMP Process Monitor is generating, thereby resolving the issue of the monitors failing. 

  1. To change the settings for how the SNMP Process Monitor gets information about processes from remote nodes, open one of these files in a text editor, depending on which platform you're using. Here are the default paths:
    • c:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config
    • c:\Program Files\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config 
  2. Locate the following section:

<snmpprocessprobesettings/> <snmpprocessprobesettings/> 

         BulkSize="10"

         PollMethod="None"

         MaxProcessCount="30000"

         RetryCount="2"

         Timeout="2500"

  1. Modify the following values, as necessary:
  • BulkSize – Specifies how many rows to retrieve using a single SNMP request. (It is set to the SNMP Max-Repetitions value). Using a value that is too large may not be supported by some clients or firewalls.
  • PollMethod – Specifies the method to use for reading data from SNMP. The default value None uses getNext in the SNMP request. In some environments, it may be beneficial to set this value to  either BulkRow or BulkColumn. In either case, SNMP requests will be using getBulkand this should improve performance. The difference between using BulkRow versus BulkColumn is in the way data is read. That is, whether you are reading SNMP tables by rows or by columns.
  • RetryCount – Specifies how many times Orion APM repeats the SNMP request if an error is returned.
  • Timeout – Specifies the  timeout for SNMP requests (in milliseconds).
  1. Save the config file after you make changes.
  2. Restart Orion Services.

If experiencing random issues with SNMP Process Monitors, try changing the default setting for PollMethod to  BulkColumn or BulkRow. Using either setting should significantly reduce the number of SNMP requests that the monitor is generating, thereby resolving the issue of the monitors failing.

 

Last modified

Tags

Classifications

Public