topic net-snmp problems on DL145G2 running CentOS 4.5 in Operating System - Linux

net-snmp problems on DL145G2 running CentOS 4.5

Isochron — Fri, 09 Nov 2007 17:13:18 GMT

UNAME:
Linux hostname 2.6.9-5.EL #1 Wed Jan 5 19:21:57 EST 2005 x86_64 x86_64 x86_64 GNU/Linux

Per "rpm -qi net-snmp":

Name: net-snmp Version:5.1.2
Vendor: Red Hat, Inc.
Release: 11
Build Date: Fri 15 Oct 2004 04:27:26 AM CDT
Install Date: Wed 04 Oct 2006 08:15:57 PM Source RPM: net-snmp-5.1.2-11.src.rpm

I can't seem to snag things like CPU usage, memory usage, etc. Anything that lives on the .1.3.6.1.4.1.2021 OID branch. When I browse the mib on this host and hit the 2021 area I just get errors back. snmpwalk says the end of the MIB has been reached.
I also have net-snmp on a SunFire v210 and I can pull all of the values I need down that 2021 branch. I have tried this via cacti, and OPManager. Its all the same SNMP MIBs so they all fail. Specifically I seem to be having problems with the UCD MIB.
Has anyone gotten cacti (or any other snmp-centric tool) working against a Proliant Dl145G2 running CentOS 4.5 or RHEL4?
Is it that I am running 5.1.2 instead of the 5.4.x current release?

Re: net-snmp problems on DL145G2 running CentOS 4.5

Luis Cardenas Perez — Fri, 09 Nov 2007 23:27:08 GMT

Did you configure "/etc/snmp/snmpd.conf"?

It seems like by default it would restrict UCDavis mib objects.

Re: net-snmp problems on DL145G2 running CentOS 4.5

Isochron — Mon, 12 Nov 2007 16:57:34 GMT

Well, I'm not sure what I would add. Nothing seems to be commented out for UCD specifically and I didn't see anything, like an example, of what should be added.

When I try a simple snmpwalk I get:

[myUser@myHost ~]# snmpwalk -v 1 localhost -c backup .1.3.6.1.4.1.2021.10
End of MIB

The UCD mib file is on the server. Do I need to do something specific to load up the MIB?

Re: net-snmp problems on DL145G2 running CentOS 4.5

Luis Cardenas Perez — Tue, 13 Nov 2007 17:22:32 GMT

Hello,

An extract from /etc/snmp/snmpd.conf:
# As shipped, the snmpd demon will only respond to queries on the
# system mib group until this file is replaced or modified for
# security purposes. Examples are shown below about how to increase the
# level of access.

I would add a line like this one:
view systemview included .1.3.6.1.4.1.2021

Where "systemview" should be the view that you assigned to the group you may be using and that uses "backup" as comm. name.

Hope it helps.