Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > SAM and Net-SNMP

SAM and Net-SNMP

Table of contents
Created by Mariusz Handke, last modified by Caroline Juszczak on Aug 16, 2018

Views: 1,681 Votes: 2 Revisions: 7


This article provides fundamental information to help you work with Unix/Linux-based devices with Net-SNMP Agent installed.


  • All SAM versions
  • All Unix/Linux based devices
  • All Net-SNMP versions


If the SNMP component does not work against the assigned Unix/Linux-based device, refer to the following troubleshooting steps.

Note: In most cases, the issue is related to the missing snmpget used in many SAM templates. In this case, check if the snmpget is available on the device using below command:

find / -name snmpget -print 2>/dev/null

Some of the components also use snmpwalk to collect and process a wider range of resultsr. Hence if the snmpwalk does not exist component would fail. Again to find the snmpwalk simply use below command:

find / -name snmpwalk -print 2>/dev/null

Use the following commands to perform SNMP Walk on the device:

SNMP v1/v2

snmpwalk -c STRING HOST OID



Fill in the VERSION, STRING and OID accordingly:


snmpwalk -On -v 3 -u USER -l LEVEL \

Fill in the USER, LEVEL, CIPHER(s), PASSWORD(s) and OID accordingly

  • As a host you can use localhost, HOSTNAME or IP address
  • You can apply relevant OID, for full tree use 1
  • You can use  the O option (output format)
  • (SNMP v3) LEVEL can have the following values: noAuthNoPriv, authNoPriv, authPriv 
  • (SNMP v3) Auth-CIPHER can have the following values: MD5, SHA
  • (SNMP v3) Priv-CIPHER can have the following values: DES, AES


Added Notes:

SNMPv2c / 3 returning incorrect values from the host system...

In some cases we have seen OID values that are returned from the polled system that reflect outrageous values

and do not reflect with what is returned from a 'top' view. Normally this can be seen from the SAM/APM 'Processes and Services' view, and from the 'Component Details'.  And this value can trigger a critical alert. When working with Unix/Linux system that may be reporting incorrect values from what is observed from the local system 'Top' view, or possibly 'VMstat', it is best to run an snmpwalk outside of SAM.


You will need the process ID from the local system... And with that we suggest to run snmpwalk tool from the Orion server from the following directory: C:\Program Files (x86)\SolarWinds\Orion\snmpwalk . Once the file is saved locally,

we can either analyze this from a GTM session from the customer, or have them upload this using LeapFile. Attempt

to find the offending process, and search the document using the assigned PID... by searching for the process name.

Once we are able to search by the PID, we will be able to get back OIDs that return Integer values, and check those OIDs via an OID repository. If the values are found to be memory statistics from the OID repository then the next best path for the user is to consult their vendors, I.E. RHEL support and the software developers.


an Example:

. = INTEGER: 925433856

.828 = PID = OID

UNITS "KBytes"
MAX-ACCESS read-only
STATUS current
"The total amount of real system memory allocated to
this process."


so the value, 925433856 is noted to be in Kbytes, = 925.433856 GB, for used system memory by a single process.



Last modified