Open mroe1234 opened 4 years ago
While you realized that "SNMPv2-SMI.py doesn't have an "ObjectSyntax" definition", you neglected the fact that ARUBA-TC
itself was written in a bad way. Since it does not make use of ObjectSyntax
anywhere inside, this import should be removed. Thus, you can manually modify the ARUBA-TC
MIB document and compile again.
Similarly you will hit any issue in WLSX-SYSTEMEXT-MIB
where it mistakenly tries to import TEXTUAL-CONVENTION
from SNMPv2-SMI
.
Following one of the examples I am working on a very simple example:
I have been able to download the MIBs and I have been able to compile them successfully in to: ARUBA-MIB.py, ARUBA-TC.py, WLSX-SYSTEMEXT-MIB.py
However when I run the above code I get the follow traceback:
My best understanding of the problems is the SNMPv2-SMI.py doesn't have an "ObjectSyntax" definition which might mean it's a v1 MIB not a v2? I've tried using smidump to convert to v2, but I get error unspecified errors and when I try to use the mibdump command like so:
The output includes:
Which seems to say it is ignoring the SNMPv2-SMI because it is supplied by pysnmp and it exists in ~/.local/lib/python3.7/site-packages/pysnmp/smi/mibs/ , Any advice would be helpful. Thanks.