- Libsmi - lists.ibr.cs.tu-bs.de

failed to locate MIB module
by Rajaram Soundararajan 16 May '02

16 May '02

Hi, Following is the example code present in the libsmi site for dumping the OID subtree for the OID given as argument. But I added some more lines to read a given configuration file and to print 'name' and 'description' of SNMPv2-SMI module. The configure file (see attached below the code) 'load's 3 modules. The smiIsLoaded() calls actually says they are loaded (return 1). But still I get the following errors: failed to locate MIB module `SNMPv2-SMI' failed to locate MIB module `SNMPv2-TC' failed to locate MIB module `SNMPv2-CONF' LOAD STATUS: 1 1 1 failed to locate MIB module `SNMPv2-SMI' 0 [main] tell 640 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 4774 [main] tell 640 open_stackdumpfile: Dumping stack trace to tell.exe.stackdump Any idea what I might be doing wrong? How can I avoid these "failed to locate MIB module" errors despite giving the SMI path so explicitly? Thanks in advance for your time. My environment is Windows NT4.0, cygwin Rajaram S. ===================================================================================== #include <stdio.h> #include <string.h> #include <smi.h> int main(int argc, char *argv[]) { SmiNode *smiNode; SmiModule *smiModule; int oidlen, first = 1; int err; if (argc != 2) { fprintf(stderr, "Usage: smisubtree oid\n"); exit(1); } smiInit(NULL); smiSetPath(".:/cygdrive/d/miblib/coslibsmi-0.2.5/mibs/ietf:/cygdrive/d/miblib/coslibsmi-0.2.5/mibs/iana:/cygdrive/d/miblib/coslibsmi-0.2.5/mibs/irtf:/cygdrive/d/miblib/coslibsmi-0.2.5/mibs/site:/cygdrive/d/miblib/coslibsmi-0.2.5/mibs/tubs"); err=smiReadConfig("./configure","smilint"); printf("LOAD STATUS: %d %d %d\n",smiIsLoaded("SNMPv2-SMI"),smiIsLoaded("SNMPv2-TC"),smiIsLoaded("SNMPv2-CONF")); smiModule = smiGetModule("SNMPv2-SMI"); printf("Module: Name %s, description %s\n",smiModule->name, smiModule->description); for((smiNode = smiGetNode(NULL, argv[1])) && (oidlen = smiNode->oidlen); smiNode && (first || smiNode->oidlen > oidlen); smiNode = smiGetNextNode(smiNode, SMI_NODEKIND_ANY), first = 0) { printf ("OIDlen = %d; Desc: %s\n",oidlen,smiNode->description); printf("%*s%-32s\n", (smiNode->oidlen - oidlen + 1) * 2, " ", smiNode->name); }; exit(0); } ===================================================================================== configure file ------------- level 1 load SNMPv2-SMI load SNMPv2-TC load SNMPv2-CONF smilint: level 1 smiint: hide namelength-32 tcpdump: load DISMAN-SCRIPT-MIB smiquery: load IF-MIB smiquery: load DISMAN-SCRIPT-MIB =====================================================================================

1 0

RE: Segmentation fault.
by Yogeshwara G 13 May '02

13 May '02

Hi, I have a mib file which when loaded causes a segmentation fault in the smi library code. To give an idea of the type of error I have attached a sample mib file. This is the standard RFC 1213 where I have edited the line system OBJECT IDENTIFIER ::= { mib-2 1 } to system OBJECT IDENTIFIER ::= { mib-2 aaa } I am presently using libsmi-0.3.1 on NT. Kindly advise me on how I can get over this problem. Thanks, Yogesh

2 1

Exception in smiparse()
by Pamela Heckmann 13 May '02

13 May '02

Hello, I am using libsmi0.3.1 on Windows NT compiling with VC 6.0. When I load our sample mib module, I get an exception in smiparse() function in the scope of the loadModule() routine. The code: if ($14) { if (((objectPtr->typePtr->export.basetype == SMI_BASETYPE_OCTETSTRING) && ($14->basetype != SMI_BASETYPE_OCTETSTRING)) || ((objectPtr->typePtr->export.basetype == SMI_BASETYPE_OBJECTIDENTIFIER) && ($14->basetype != SMI_BASETYPE_OBJECTIDENTIFIER))) { smiPrintError(thisParserPtr, ERR_DEFVAL_SYNTAX); if ($14->basetype == SMI_BASETYPE_OBJECTIDENTIFIER) { smiFree($14->value.oid); } if (($14->basetype == SMI_BASETYPE_BITS) || ($14->basetype == SMI_BASETYPE_OCTETSTRING)) { smiFree($14->value.ptr); } smiFree($14); } gets an exception because objectPtr->typePtr is NULL. I ran smilint.exe against fooTest.mib and it gets an exception also. I have included our sample mibs that I have been testing with. fooTest.mib imports fooCorp.mib. Any help would be appreciated. Pamela -- Pamela Heckmann Icon Laboratories, Inc. Pam_Heckmann(a)icon-labs.com The grand essentials to happiness in this life are something to do, something to love and something to hope for. - Joseph Addison

3 9

Segmentation fault.
by Yogeshwara G 10 May '02

10 May '02

Hi, I have a mib file which when loaded causes a segmentation fault in the smi library code. To give an idea of the type of error I have attached a sample mib file. This is the standard RFC 1213 where I have edited the line system OBJECT IDENTIFIER ::= { mib-2 1 } to system OBJECT IDENTIFIER ::= { mib-2 aaa } I am presently using libsmi-0.3.1 on NT. Kindly advise me on how I can get over this problem. Thanks, Yogesh

1 0

Not getting values in some fields of SmiNode structure.
by Shubha Simhadri 06 May '02

06 May '02

I am also experiencing the similar problem. I am trying to find the current value of a node by accessing "value" field of SmiNode but it always returns SMI_BASETYPE_UNKNOWN. Can somebody please help me to find out the current value and default values of each node. My code looks for(smiNode = smiGetFirstNode(module, SMI_NODEKIND_ANY); smiNode; smiNode = smiGetNextNode(smiNode, SMI_NODEKIND_ANY)) { SmiType * type = smiGetNodeType(smiNode); printf("%s\t", smiNode->name); printf ("%i\n", smiNode->nodekind); printf("%s\n", formatvalue(&smiNode->value, type)); }; Thanks

2 1

Not getting values in some fields of SmiNode structure.
by Yogeshwara G 02 May '02

02 May '02

Hello, I am using libsmi0.3.1 on Windows NT compiling with VC++ 6.0. When I load SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONFand SNMPv2-MIB mib modules given in the mibs\ietf folder, I am not getting correct values in the following fields of SmiNode structure: 1. format field always has a value 0x00000000"". 2. basetype and len in value field always have "SMI_BASETYPE_UNKNOWN" and 0. 3. units field always has a value 0x00000000"". 4. reference field always has a value 0x00000000"". I am getting proper values in the other fields. Can anyone suggest me what could be wrong? Thanks and Regards, Yogesh

2 1

what is the future of smilib and sming
by Mark Kaplun 02 May '02

02 May '02

Frank, Can you tell us what is the future of smilib in the sence of: - future developments - your managment of the project - Any other information And is there any adoption of the sming? , is it standartize by now? Thanks, Mark.

2 1

Smidump for JAX: strange code for AUGMENTS Index
by Caffaratti Fabrizio 30 Apr '02

30 Apr '02

Hi all I'm using the smidump for Jax output. I've dumped a MIB and it succeded. When I've seen the generate code for this object definition: -- -- support for specific status code notifications -- sipCommonStatusCodeNotifTable OBJECT-TYPE SYNTAX SEQUENCE OF SipCommonStatusCodeNotifEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains objects to control notifications related to particular status codes each SIP entity in this system has been requested to monitor. There is an entry in this table corresponding to each entry in sipCommonStatusCodeTable. Therefore, this table augments that table and utilizes the same index methodology." ::= { sipCommonStatusCode 3 } sipCommonStatusCodeNotifEntry OBJECT-TYPE SYNTAX SipCommonStatusCodeNotifEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This row contains information controlling notifications for a particular SIP status code that the SIP entity has been requested to monitor." AUGMENTS { sipCommonStatusCodeEntry } ::= { sipCommonStatusCodeNotifTable 1 } SipCommonStatusCodeNotifEntry ::= SEQUENCE { sipCommonStatusCodeNotifSend TruthValue, sipCommonStatusCodeNotifEmitMode INTEGER, sipCommonStatusCodeNotifThresh Unsigned32, sipCommonStatusCodeNotifInterval Unsigned32 } ..... I saw that it generated a SipCommonStatusCodeNotifTable and SipCommonStatusCodeNotifEntry classes. The AgentXEntry sub-class have got an empty constructor. It's strange. I supposed that AUGMENTS index type isn't right managed. How do I change dump-jax to generate code for AUGMENTES index? Is it possible? public class SipCommonStatusCodeNotifEntry extends AgentXEntry { protected int sipCommonStatusCodeNotifSend = 0; protected int undo_sipCommonStatusCodeNotifSend = 0; protected int sipCommonStatusCodeNotifEmitMode = 0; protected int undo_sipCommonStatusCodeNotifEmitMode = 0; protected long sipCommonStatusCodeNotifThresh = 0; protected long undo_sipCommonStatusCodeNotifThresh = 0; protected long sipCommonStatusCodeNotifInterval = 0; protected long undo_sipCommonStatusCodeNotifInterval = 0; public SipCommonStatusCodeNotifEntry() { } public int get_sipCommonStatusCodeNotifSend() { return sipCommonStatusCodeNotifSend; } ......................... Thank, Fabrizio

2 1

Errors reported by smilint
by Amarender K. Ganji 29 Apr '02

29 Apr '02

Hi, I'm using smilint for the first time. And getting the following error when I compile one of the MIBs (SMIv1). [1] {other} parse error, unexpected INTEGER, expecting UPPERCASE_IDENTIFIER or LOWERCASE_IDENTIFIER or NUMBER The other tools like SMIC, Parse, Mosy etc. never complained about this. Why smilint is not accepting 'INTEGER' as index part (I'm referring to IndexPart in RFC-1212) The object was defined as follows... memStatTable OBJECT-TYPE SYNTAX SEQUENCE OF MemStatEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " Information about data buffer pools. Instance is pool number. 1 - 7 is D RAM 8 is M RAM 9 - is C RAM 10 - is H RAM" ::= { sysInfo 5 } memStatEntry OBJECT-TYPE SYNTAX MemStatEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A single entry in the Memory stats table" INDEX { INTEGER } ***** Error in this line ***** ::= { memStatTable 1 } MemStatEntry ::= SEQUENCE { accMemBlkEntSize INTEGER, accMemBlkEntTotal INTEGER, accMemBlkEntMax Gauge, accMemBlkEntInUse Gauge, accMemBlkEntFails Counter, accMemBlkEntType INTEGER, accMemBlkEntAllocs Counter, accMemBlkEntInitial INTEGER } And also getting the following error. I observed that it is only complaining for the objects which are part of the index of a table. [2] {index-element-no-range} index element `oDiffServMeterInterface' of row `oDiffServMeterStatsEntry' must have a range restriction [1] {index-element-no-size} index element `oDiffServMeterIfMeterName' of row `oDiffServMeterStatsEntry' must have a size restriction My question here is why smilint should complain about range/size restriction when the standard MIBs (ifIndex in RFC1213-MIB) don't specify range of any object (Type INTEGER) which is part of index. /Amar

4 3

RE: [libsmi] failed to locate MIB module ...
by Arie Trost 26 Apr '02

26 Apr '02

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(a)newdreamnet.com [mailto:dychoi@newdreamnet.com] > Sent: Thursday, April 25, 2002 6:26 PM > To: libsmi(a)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(a)ibr.cs.tu-bs.de> > !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi. >

1 0