Nagios Support Forum

CPU usage shows Can't find CPU usage information : UNKNOWN for SLES 10 and SLES 9, other parameters including disk and SWAP are working fine

What client are you using? NCPA, NRPE, another one ? Please provide the full command that is being used to check the CPU as well as the common.cfg and nrpe.cfg if the NRPE agent is being used.

We are using Linux snmp. Below is the command I see in the core config manager.

$USER1$/check_snmp_load_wizard.pl -H $HOSTADDRESS$ $ARG1$

-C camops --v2c -w 80 -c 90 -f

Error shows:- No answer from host

The command will query OID 1.3.6.1.2.1.25.3.3.1 by default. Does the following return anything?

snmpget -v 2c -c camops SLES_IP 1.3.6.1.2.1.25.3.3.1

below is the error I'm getting. Should i need to specifically add this OID in the SLES server? If yes, please give me the complete line to be added to the snmpd.conf file.

ohcinxnagiosxi1 libexec]# snmpget -v 2c -c camops 10.162.28.34 1.3.6.1.2.1.25.3.3.1
HOST-RESOURCES-MIB::hrProcessorEntry = No Such Object available on this agent at this OID

You shouldn't have to specificy this OID specifically but you may have other config in the snmpd.conf that prevents access. You'll also want to make sure the remote machines have net-snmp installed and HOST-RESOURCES-MIB installed.

I see net-snmp installed in the server, you mean HOST-RESOURCES-MIB is a seperate package that needs to be installed in SLES 9 and SLES 10 servers?
Below is the snmpd.conf file, please let me know if any of the entry which preventing cpu usage to send.

in2s0ws002:~ # cat /etc/snmp/snmpd.conf
# Following entries were added by HP Insight Management Agents at
# Wed Mar 21 12:16:29 EDT 2012
dlmod cmaX /usr/lib64/libcmaX64.so
rwcommunity keys 127.0.0.1
rocommunity view 127.0.0.1
rwcommunity keys 10.160.20.162
rocommunity view 10.160.0.0/11
rocommunity camops 10.160.0.0/11
rocommunity camops 140.244.0.0/17
trapcommunity camops
trapsink 10.160.20.162 view
syscontact gale.ene.alerts@cengage.com
syslocation KDC, Independence, KY

# ---------------------- END --------------------

# Setting storageUseNFS to 1 causes all NFS and NFS-like file systems to be
# marked as 'Network Disks' in the hrStorageTable. This is in accordance
# with RFC 2790. Unfortunately, it's not the default in older versions of
# net-snmp, including that shipped with SLES10.

storageUseNFS 1

# Custom SNMP OIDs for reporting system information from dmidecode
# OIDs are owned by PlumStreet, LLC.
# (This company is associated with Mick Isiminger.)
#
# 1.3.6.1.4.1.19158.1.x.x.x - SNMP
# 1.3.6.1.4.1.19158.1.1.x.x - System Related
# 1.3.6.1.4.1.19158.1.1.1.x - dmidecode commands

exec .1.3.6.1.4.1.19158.1.1.1.1 bios-vendor /usr/sbin/dmidecode --string bios-vendor
exec .1.3.6.1.4.1.19158.1.1.1.2 bios-version /usr/sbin/dmidecode --string bios-version
exec .1.3.6.1.4.1.19158.1.1.1.3 bios-release-date /usr/sbin/dmidecode --string bios-release-date
exec .1.3.6.1.4.1.19158.1.1.1.4 system-manufacturer /usr/sbin/dmidecode --string system-manufacturer
exec .1.3.6.1.4.1.19158.1.1.1.5 system-product-name /usr/sbin/dmidecode --string system-product-name
exec .1.3.6.1.4.1.19158.1.1.1.6 system-version /usr/sbin/dmidecode --string system-version
exec .1.3.6.1.4.1.19158.1.1.1.7 system-serial-number /usr/sbin/dmidecode --string system-serial-number
exec .1.3.6.1.4.1.19158.1.1.1.8 system-uuid /usr/sbin/dmidecode --string system-uuid
exec .1.3.6.1.4.1.19158.1.1.1.9 baseboard-manufacturer /usr/sbin/dmidecode --string baseboard-manufacturer
exec .1.3.6.1.4.1.19158.1.1.1.10 baseboard-product-name /usr/sbin/dmidecode --string baseboard-product-name
exec .1.3.6.1.4.1.19158.1.1.1.11 baseboard-version /usr/sbin/dmidecode --string baseboard-version
exec .1.3.6.1.4.1.19158.1.1.1.12 baseboard-serial-number /usr/sbin/dmidecode --string baseboard-serial-number
exec .1.3.6.1.4.1.19158.1.1.1.13 baseboard-asset-tag /usr/sbin/dmidecode --string baseboard-asset-tag
exec .1.3.6.1.4.1.19158.1.1.1.14 chassis-manufacturer /usr/sbin/dmidecode --string chassis-manufacturer
exec .1.3.6.1.4.1.19158.1.1.1.15 chassis-type /usr/sbin/dmidecode --string chassis-type
exec .1.3.6.1.4.1.19158.1.1.1.16 chassis-version /usr/sbin/dmidecode --string chassis-version
exec .1.3.6.1.4.1.19158.1.1.1.17 chassis-serial-number /usr/sbin/dmidecode --string chassis-serial-number
exec .1.3.6.1.4.1.19158.1.1.1.18 chassis-asset-tag /usr/sbin/dmidecode --string chassis-asset-tag
exec .1.3.6.1.4.1.19158.1.1.1.19 processor-family /usr/sbin/dmidecode --string processor-family
exec .1.3.6.1.4.1.19158.1.1.1.20 processor-manufacturer /usr/sbin/dmidecode --string processor-manufacturer
exec .1.3.6.1.4.1.19158.1.1.1.21 processor-version /usr/sbin/dmidecode --string processor-version
exec .1.3.6.1.4.1.19158.1.1.1.22 processor-frequency /usr/sbin/dmidecode --string processor-frequency

On my test system the HOST-RESOURCES-MIB.txt can be found in /usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt.

There was a mistake in the previous command. Try running:

snmpwalk -v 2c -c public 192.168.4.77 1.3.6.1.2.1.25.3.3.1

I can see the host resources MIB file in the server.

in2s0ws002:~ # ls -l /usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt
-rw-r--r-- 1 root root 52544 Sep 5 2009 /usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt

Below is the output from snmpwalk command

ohcinxnagiosxi1 ~]# snmpwalk -v2c -c camops 10.162.28.34 1.3.6.1.2.1.25.3.3.1
HOST-RESOURCES-MIB::hrProcessorFrwID.768 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.769 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.770 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.771 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.772 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.773 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.774 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.775 = OID: SNMPv2-SMI::zeroDotZero

ganeshsambandam wrote:

Code: Select all

ohcinxnagiosxi1 ~]# snmpwalk -v2c -c camops 10.162.28.34 1.3.6.1.2.1.25.3.3.1
HOST-RESOURCES-MIB::hrProcessorFrwID.768 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.769 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.770 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.771 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.772 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.773 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.774 = OID: SNMPv2-SMI::zeroDotZero
HOST-RESOURCES-MIB::hrProcessorFrwID.775 = OID: SNMPv2-SMI::zeroDotZero

If this is the response you received then your SLES server is not configured to report load via SNMP, if it was you would have also received the hrProcessorLoad entries that correspond to each ID listed in your output.

I found others with the same issue on SLES9 & 10 here
https://forums.cacti.net/about38898.html