[HECnet] SNMP MIBs and smidump

[Paul_Koning at Dell.com]

I think you need some more switches to point smidump to the place where the standard MIB files (the ones complained about at the start) can be found.   Actually, it looks like you can just supply those files as additional command line arguments.

Try the attached, I fixed some of the errors.   I can't figure out why it's complaining about ifIndex, but I do see the same message for some other MIBs I tried -- including a copy of the standard RFC 1156 MIB...

However, the output looks fine if you use -k with that.

	paul


On Jan 10, 2013, at 4:59 PM, Brian Hechinger wrote:

Anyone ever mess with this?

wonko at fred$ smidump -f python OLD-CISCO-DECNET-MIB.my
OLD-CISCO-DECNET-MIB.my:15: failed to locate MIB module `RFC-1212'
OLD-CISCO-DECNET-MIB.my:17: failed to locate MIB module `RFC1213-MIB'
OLD-CISCO-DECNET-MIB.my:19: failed to locate MIB module `CISCO-SMI'
OLD-CISCO-DECNET-MIB.my:21: unknown object identifier label `temporary'
OLD-CISCO-DECNET-MIB.my:283: index element `dnArea' of row `dnAreaTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:443: index element `dnHIdx1' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:451: index element `dnHIdx2' of row `dnHostTableEntry' must have a range restriction
OLD-CISCO-DECNET-MIB.my:476: unknown object identifier label `ifIndex'
smidump: module `OLD-CISCO-DECNET-MIB.my' contains errors, expect flawed output
smidump: aborting due to severe parsing errors
smidump: use the -k option to force continuation
wonko at fred$

I need to do that so I can convert it into whatever nonsense PySNMP needs.

-brian