Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IEEE8023-LAG-MIB OID mismatch between .my and .py

See original GitHub issue

I have IEEE8023-LAG-MIB.my in /usr/share/snmp/mibs/ieee. The MIB gets loaded:

2017-10-11 21:30:35,038 pysnmp: loadModule: trying IEEE8023-LAG-MIB at DirMibSource('/root/.pysnmp/mibs')
2017-10-11 21:30:35,038 pysnmp [DEBUG] loadModule: trying IEEE8023-LAG-MIB at DirMibSource('/root/.pysnmp/mibs')
2017-10-11 21:30:35,039 pysnmp: file IEEE8023-LAG-MIB.pyc mtime 1507753662
2017-10-11 21:30:35,039 pysnmp [DEBUG] file IEEE8023-LAG-MIB.pyc mtime 1507753662
2017-10-11 21:30:35,039 pysnmp: file IEEE8023-LAG-MIB.py mtime 1507753662
2017-10-11 21:30:35,039 pysnmp [DEBUG] file IEEE8023-LAG-MIB.py mtime 1507753662
2017-10-11 21:30:35,040 pysnmp: loadModule: seen /root/.pysnmp/mibs/IEEE8023-LAG-MIB.pyc
2017-10-11 21:30:35,040 pysnmp [DEBUG] loadModule: seen /root/.pysnmp/mibs/IEEE8023-LAG-MIB.pyc

However, the resolution failed for OID 1.2.840.10006.300.43.1.2.1 dot3adAggPortTable.

2017-10-11 21:37:33,110 pysnmp: resolving ('1', '2', '840', '10006', '300', '43', '1', '2', '1') as OID or label
2017-10-11 21:37:33,110 pysnmp [DEBUG] resolving ('1', '2', '840', '10006', '300', '43', '1', '2', '1') as OID or label
2017-10-11 21:37:33,112 pysnmp: getNodeNameByOid: resolved :1.2.840.10006.300.43.1.2.1 -> ('iso',).2.840.10006.300.43.1.2.1
2017-10-11 21:37:33,112 pysnmp [DEBUG] getNodeNameByOid: resolved :1.2.840.10006.300.43.1.2.1 -> ('iso',).2.840.10006.300.43.1.2.1
2017-10-11 21:37:33,112 pysnmp: resolved (('1', '2', '840', '10006', '300', '43', '1', '2', '1'),) into prefix ObjectName('1') and suffix ObjectName('2.840.10006.300.43.1.2.1')
2017-10-11 21:37:33,112 pysnmp [DEBUG] resolved (('1', '2', '840', '10006', '300', '43', '1', '2', '1'),) into prefix ObjectName('1') and suffix ObjectName('2.840.10006.300.43.1.2.1')
2017-10-11 21:37:33,112 pysnmp: getNodeNameByOid: resolved :1 -> ('iso',).()
2017-10-11 21:37:33,112 pysnmp [DEBUG] getNodeNameByOid: resolved :1 -> ('iso',).()
2017-10-11 21:37:33,113 pysnmp: resolved prefix ObjectName('1') into MIB node MibTree((1,), None)
2017-10-11 21:37:33,113 pysnmp [DEBUG] resolved prefix ObjectName('1') into MIB node MibTree((1,), None)
2017-10-11 21:37:33,113 pysnmp: resolved indices are (ObjectName('2.840.10006.300.43.1.2.1'),)
2017-10-11 21:37:33,113 pysnmp [DEBUG] resolved indices are (ObjectName('2.840.10006.300.43.1.2.1'),)

I checked in /root/.pysnmp/mibs/IEEE8023-LAG-MIB.my and see the following lines for

dot3adAggPortTable = MibTable((1, 2, 840, 802, 10006, 300, 43, 1, 2, 1), )
if mibBuilder.loadTexts: dot3adAggPortTable.setReference('6.3.2')
if mibBuilder.loadTexts: dot3adAggPortTable.setStatus('current')
dot3adAggPortEntry = MibTableRow((1, 2, 840, 802, 10006, 300, 43, 1, 2, 1, 1), ).setIndexNames((0, "IEEE8023-LAG-MIB", "dot3adAggPortIndex"))
if mibBuilder.loadTexts: dot3adAggPortEntry.setStatus('current')
dot3adAggPortIndex = MibTableColumn((1, 2, 840, 802, 10006, 300, 43, 1, 2, 1, 1, 1), InterfaceIndex())

The MIB speaks about 840.10006. In the IEEE8023-LAG-MIB.my, there is 840, 802, 10006.

Any ideas how 802 got there?

Issue Analytics

State:
Created 6 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

etingofcommented, Oct 14, 2017

Released pysmi 0.1.4 on PyPI and updated MIBs at http://mibs.snmplabs.com/asn1/

0reactions

greenpaucommented, Oct 13, 2017

OK, commit 2e6b9e8a0b8b379c1faed034ad1300441f0b0341 should fix this.

@etingof , kudos for the fix! 👍 For now, I manually fixed it. Will wait for the next release in pypi 😄

Thank you very much! Спасибо что посмотрел! Удач!

Top Results From Across the Web

MIB files repository

www.circitor.fr: MIB files repository. ... ARUBAWIRED-NETWORKING-OID · ARUBAWIRED-POE-MIB ... IEEE8023-LAG-MIB · IEEE802dot11-MIB · IF-CAP-STACK-MIB

SNMP - Cisco

(This defines MIB objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network [LAN] segments.) 2819. RMON ...

IEEE 802.3 LAG MIB - Palo Alto Networks

Use the IEEE 802.3 LAG MIB to monitor the status of aggregate groups that have Link Aggregation Control Protocol (LACP) enabled.

Supported MIBs | Cumulus Linux 4.2

You must uncomment the bridge_pp.py pass_persist script in /etc/snmp/snmpd.conf . IEEE8023-LAG-MIB, Implementation of the IEEE 8023-LAG-MIB includes the ...

Network OS MIB Reference, 3.0.0

Chapter 9, “IEEE 802.3 LAG MIB Objects,” provides information on IEEE 802.3 LAG MIB object ... The OID is the sequence of numeric...