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