Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SNMP Question: HOST-RESOURCES-MIB::hrProcessorLoad = No Such Instance currently exists at this OID

216 views
Skip to first unread message

Stephen Chaddock

unread,
Feb 28, 2006, 11:18:05 AM2/28/06
to
All,
Our client uses the Solarwinds Orion 7.8.2 NMS (Network Management
Software) for SNMP monitoring. Their Windows systems are fine but their
Linux systems are not reporting CPU idle and some memory stats correctly.

Upgrading to use latest SLES9 net-snmp-5.1.3.1-0.6 package improved the
memory reporting but the CPU idle monitoring remains a problem.

After scouring the internet and net-snmp mailing list the problem is
observed by many but with no solutions forthcoming.

The Solarwinds technical support have not been particularly helpful. The
two reported OID's used for the CPU information are:

HOST-RESOURCES-MIB::hrProcessorLoad
UCD-SNMP-MIB::ssCpuIdle (deprecated since 20020905 = net-snmp-5.0.4)

Ignoring the deprecated "ssCpuIdle", attempting to use "hrProcessorLoad"
results in no information being presented:

snmpwalk -v 2c -c 'private' hrProcessorLoad
snmpwalk -v 2c -c 'private' 127.0.0.1 1.3.6.1.2.1.25.3.3.1.2
HOST-RESOURCES-MIB::hrProcessorLoad = No Such Instance currently exists
at this OID


Does anyone know why this OID is not working on SLES 9 and how to get
this OID/information presented via SNMP?

Any help would be much appreciated.

Regards

Stephen Chaddock

Stephen Chaddock

unread,
May 9, 2006, 12:31:36 PM5/9/06
to

As an update (prompted by a query):

Our problem was specific to using Solarwinds Orion 7.8.2 NMS (Network
Management Software).

The solution in the end was to not use a Solarwinds NMS for the linux
systems, as replacements we looked at Nagios and Zabbix.

www.nagios.org
www.zabbix.com

By our clients preference we have used Zabbix with their systems which
they have so far been impressed with. Zabbix is free with the ability to
purchase support options.

The crux of our problem appears to be Solarwinds use of the deprecated
OID's e.g. "ssCpuIdle" OID instead of "ssCpuRawIdle". They were not
particularly helpful in trying to address the problem or find a solution.

Hope this helps.

Regards,

Stephen Chaddock

0 new messages