Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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

Problems in SAM with SNMP Process Monitors failing

Created by Erin Stenzel, last modified by MindTouch on Jun 23, 2016

Views: 186 Votes: 0 Revisions: 2

Overview


SNMP Process Monitors in Orion APM are failing due to the large number of SNMP requests they are generating.

Environment

  • Server & Application Monitor (SAM)

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. 

To change the settings for how the SNMP Process Monitor gets information about processes from remote nodes:

Edit the file c:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config or c:\Program Files\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config (depending on your platform) using Notepad and locate the following section:<snmpprocessprobesettings/> <snmpprocessprobesettings/> 

 

         BulkSize="10"

         PollMethod="None"

         MaxProcessCount="30000"

         RetryCount="2"

         Timeout="2500"

 

Note: If you installed Orion APM to a different location than the default, then the path to the configuration file shown above will be different to match your installation location.

 


You can modify the following values as described below:
 

  • 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).

 

Remember to save the config file after you have made your changes. Then you need to restart Orion Services.

 

Recommendations:
APM customers who are experiencing random issues with SNMP Process Monitors should 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
03:00, 23 Jun 2016

Tags

Classifications

Public