Ok, the thing is though, we have a few hundred commercial MIBs to import, many of them throw errors. I won't argue the validity of their syntax, but net-snmp has no problem parsing them, and that is what we currently use. Is there some way to configure libsmi to be less strict with its parsing, or skip imports or definitions that have errors?
Jae Muzzin Netmon Technical Support jae@netmon.ca 1-800-944-4511 ext 223
libsmi-request@ibr.cs.tu-bs.de wrote:
Send Libsmi mailing list submissions to libsmi@ibr.cs.tu-bs.de
To subscribe or unsubscribe via the World Wide Web, visit https://mail.ibr.cs.tu-bs.de/mailman/listinfo/libsmi or, via email, send a message with subject or body 'help' to libsmi-request@ibr.cs.tu-bs.de
You can reach the person managing the list at libsmi-owner@ibr.cs.tu-bs.de
When replying, please edit your Subject line so it is more specific than "Re: Contents of Libsmi digest..."
Today's Topics:
- libsmi not parsing MIB (Jae Muzzin)
- Re: libsmi not parsing MIB (Andrew Hood)
Message: 1 Date: Thu, 12 Apr 2007 15:10:12 -0400 From: Jae Muzzin jae@netmon.ca Subject: [libsmi] libsmi not parsing MIB To: libsmi@ibr.cs.tu-bs.de Message-ID: 461E8414.3000402@netmon.ca Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Hello,
I'm using PYSNMP which uses smidump to convert MIBs into python modules. I have a MIB from a manufacturer, which works with net-snmp, but smidump throws a parsing error. Any ideas?
Here is the error: /usr/local/share/mibs/site/enviromux-mini.mib:7: parse error, unexpected DISPLAY_HINT
And here is the part of the mib that is throwing the error:
NETWORK-TECHNOLOGIES-GLOBAL-REG DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, enterprises FROM SNMPv2-SMI DisplayString, TEXTUAL-CONVENTION, DISPLAY-HINT FROM SNMPv2-TC;