You can just set environment variable named SMIPATH to point to you MIB repository (..\mibs\ietf if you use libSMI's one).
Arie.
-----Original Message----- From: dychoi@newdreamnet.com [mailto:dychoi@newdreamnet.com] Sent: Thursday, April 25, 2002 6:26 PM To: libsmi@ibr.cs.tu-bs.de Subject: [libsmi] failed to locate MIB module ...
Hi, all.
This is the first time for me to use libsmi mailinglist.
I'm elementary in using this tool.
I installed libsmi as documentation.
When I try to test some commands, some problems occurred.
I think these problems occurred because of missing mib path.
I want to know how to locate mib modules path.
Should I modify smi.conf ? Or, simply should I set environment variable 'mibdir' ?
$ smidump ./IF-MIB failed to locate MIB module `SNMPv2-SMI' failed to locate MIB module `SNMPv2-TC' failed to locate MIB module `SNMPv2-CONF' failed to locate MIB module `SNMPv2-MIB' failed to locate MIB module `IANAifType-MIB' ./IF-MIB:81: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:95: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:110: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:111: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:118: unknown type `TimeTicks' ./IF-MIB:119: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:120: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:140: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:141: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:149: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:150: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:163: unknown type `Gauge32' ./IF-MIB:167: unknown type `TimeTicks' ./IF-MIB:168: unknown type `Counter32' ./IF-MIB:169: unknown type `Counter32' ./IF-MIB:170: unknown type `Counter32' ./IF-MIB:171: unknown type `Counter32' ./IF-MIB:172: unknown type `Counter32' ./IF-MIB:173: unknown type `Counter32' ./IF-MIB:174: unknown type `Counter32' ./IF-MIB:175: unknown type `Counter32' ./IF-MIB:176: unknown type `Counter32' ./IF-MIB:177: unknown type `Counter32' ./IF-MIB:178: unknown type `Counter32' ./IF-MIB:179: unknown type `Gauge32' ./IF-MIB:187: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:188: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:199: illegal size restriction for non-octet-string parent type `Display String' ./IF-MIB:200: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:201: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:207: type of `ifDescr' in sequence and object type definition do not ma tch ./IF-MIB:211: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:212: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:222: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:223: invalid STATUS `current' in SMIv1 MIB ./IF-MIB:236: unknown type `Gauge32' ./IF-MIB:236: MAX-ACCESS is SMIv2 style, use ACCESS in SMIv1 MIBs instead ./IF-MIB:237: invalid STATUS `current' in SMIv1 MIB 0 [main] smidump 1012 handle_exceptions: Exception: STATUS_ACCESS_VIOLATIO N 36374 [main] smidump 1012 stackdump: Dumping stack trace to smidump.exe.stackd ump Segmentation fault (core dumped) -- !! 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.