Hi!
Sam Mohan writes:
Sam> I just installed libsmi-0.2.16 in my solaris server. I get this Sam> following error message when I try to generate the oid tree:
Sam> smidump -f tree NICKEL-GLOBAL-REGISTRY.mib > ./treeOut
Sam> NICKEL-GLOBAL-REGISTRY.mib:17: identifier `MODULE-IDENTITY' cannot be Sam> imported from module `SNMPv2-SMI' Sam> NICKEL-GLOBAL-REGISTRY.mib:17: identifier `OBJECT-IDENTITY' cannot be Sam> imported from module `SNMPv2-SMI' Sam> NICKEL-GLOBAL-REGISTRY.mib:49: invalid STATUS `current' in SMIv1 MIB Sam> NICKEL-GLOBAL-REGISTRY.mib:58: invalid STATUS `current' in SMIv1 MIB Sam> NICKEL-GLOBAL-REGISTRY.mib:67: invalid STATUS `current' in SMIv1 MIB
Sam> I would like to get rid of these errors. (This mib file compiles without Sam> errors in SMICng and other mib compilers and the generated also tree Sam> appears to be correct.)
Most probably you don't have the whole bunch of ietf MIBs in your libsmi search path. You need at least SNMPv2-SMI since your NICKEL-GLOBAL-REGISTRY is importing from it. If you configure, compile and install libsmi with the default settings, everything should be fine.
See the smi_config man page for the different ways to control the search path.
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.