Dear Erik,
Thank you for your reply. I indeed followed Juergen's suggestion and removed RFC1158 from the set and commented away the dependency import in RFC1212. I was now able to proceed with the parsing of the MIB files I needed so all seems well for now.
I already came to the same conclusion in regards to the syntax validity of some vendor (Dell/HP) provided MIBs and have ended up correcting any syntax errors (like missing commas) and skipping ones I simply can't parse so long as I don't specifically seem to need them for the system I'm working on.
Libsmi (smilint & smidump) is proofing to cover the requirements I have quite well (bar the 2 issues which I posted to the mailinglist, of which this one is solved now). I am limited to tools which can be installed in Linux (centOS) from package (not compiled by hand) and would prefer to steer away from JAVA based tools since there is no JAVA runtime environment on the machines the system will be running on and I'd like to keep it that way.
With kind regards,
Peter Postma
-----Oorspronkelijk bericht----- Van: libsmi-bounces@ibr.cs.tu-bs.de [mailto:libsmi-bounces@ibr.cs.tu-bs.de] Namens Erik Pessers Verzonden: dinsdag 17 december 2013 11:17 Aan: libsmi@ibr.cs.tu-bs.de Onderwerp: Re: [libsmi] smidump generating invalid XML output for RFC1158 mib
Peter,
Possibly, this could be a pragmatic way out : edit your copy of RFC1212 MIB, remove IMPORT from RFC1158, and add a line reading
DisplayString ::= OCTET STRING
Note from a grey-haired person working in NMS area for a long time: you'll find other (even quite modern) MIBs is the wild from time to time (notably if you go for enterprise specific MIBSs) that contain constructs MIB compilers will struggle with. One option is to try different compilers (all are fussy, but not all necessarily in the same manner); the other option is to "correct" the MIB. Another option is to notify MIB writers or compiler developers, but experience shows this is often the (infinitely) long term way towards a solution.
On 16/12/13 15:56, Peter Postma wrote:
Hi,
The problem there is that I try to load (and parse) the dependencies. RFC1213 has a dependency (import) with RFC1212 (OBJECT-TYPE FROM RFC-1212), which in turn imports from RFC1158-MIB (DisplayString FROM RFC1158-MIB). So how would I satisfy the import dependencies when not using RFC1158? Or did HP provide a wrong version of RFC1213/RFC1212 which should not have included that depencency?
With kind regards,
Peter Postma
Cheers, Erik Pessers erik.pessers@acm.org -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to libsmi-request@ibr.cs.tu-bs.de !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.