enterprises.ucdavis.dskTable broken in SLC6.7

Sergei Dubrov <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
G'day all!

After upgrading from SLC6.6 to SLC6.7 we got broken one subtree in OID-tree enterprises.ucdavis.dskTable (.1.3.6.1.4.1.2021.9):

[[email protected] ~]# snmpwalk -m all -v 2c -c public localhost .1.3.6.1.4.1.2021.9
UCD-SNMP-MIB::dskTable = No Such Object available on this agent at this OID
...

[[email protected] ~]# snmpwalk -m all -v 2c -c public localhost .1.3.6.1.4.1.2021.9
UCD-SNMP-MIB::dskIndex.1 = INTEGER: 1
UCD-SNMP-MIB::dskIndex.2 = INTEGER: 2
...
UCD-SNMP-MIB::dskErrorMsg.1 = STRING:
UCD-SNMP-MIB::dskErrorMsg.2 = STRING:
...

[[email protected] ~]# cat /etc/redhat-release
Scientific Linux CERN SLC release 6.7 (Carbon) (2.6.32-573.3.1.el6.x86_64)

[[email protected] ~]# cat /etc/redhat-release
Scientific Linux CERN SLC release 6.6 (Carbon) (2.6.32-504.30.3.el6.x86_64)
...

Other subtrees - e.g., .4, .11 from the enterprises.ucdavis - works perfectly. Does not work only .9 subtree. SNMP config absolutely the same in SLC6.6 and in SLC6.7.

After some investigations we found:


       | net-snmp-5.5-50.el6_6.1.x86_64 | net-snmp-5.5-54.el6_7.1.x86_64 |
-------+--------------------------------+--------------------------------+
SLC6.6 | ucdavis.dskTable WORKS         |   ucdavis.dskTable WORKS       |
-------+--------------------------------+--------------------------------+
SLC6.7 | ucdavis.dskTable WORKS         |   ucdavis.dskTable NOT WORKING |
-------+--------------------------------+--------------------------------+


I.e., does not works latest SLC6x with latest net-snmp 5.5.


---
Sergei DUBROV

------------------------------------------------------------------------------

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.