Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article provides fundamental information to help you work with Unix/Linux-based devices with Net-SNMP Agent installed.
If the SNMP component does not work against the assigned Unix/Linux-based device, refer to the following troubleshooting steps.
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:
snmpwalk -c STRING HOST OID
snmpwalk -v VERSION -c STRING HOST OID
Fill in the VERSION, STRING and OID accordingly:
snmpwalk -On -v 3 -u USER -l LEVEL \ -a Auth-CIPHER -A Auth-PASSWORD \ -x Priv-CIPHER -X Priv-PASSWORD HOST OID
Fill in the USER, LEVEL, CIPHER(s), PASSWORD(s) and OID accordingly
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/APM.
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.
.18.104.22.168.22.214.171.124.126.96.36.1998 = INTEGER: 925433856
.828 = PID
188.8.131.52.184.108.40.206.1.1.2 = OID
"The total amount of real system memory allocated to
so the value, 925433856 is noted to be in Kbytes, = 925.433856 GB, for used system memory by a single process.