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

Index elements should be not-accessible.....
by Vivekanandan V 17 May '02

17 May '02

Hello, Iam using smilint 0.3.1. For Index elements (of Tables) having a MAX-ACCESS as read-only, an error is given in severity level 5 as, " index element should be not-accessible in SMIv2 MIB" So, does it mean that Index elements cannot be read-only?? If so, can you please let me know whether is it mentioned in any standard Rfc?? Thanks & Regards, Vivekanandan.V *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************

4 7

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

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

failed to locate MIB module ...
by 최대영 26 Apr '02

26 Apr '02

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)

1 0

Re: [libsmi] Error report when there is a failure to import a file
by Bill Fenner 22 Apr '02

22 Apr '02

I did this in parser-smi.y to get the line numbers: --- parser-smi.y 20 Mar 2002 16:49:49 -0000 1.169 +++ parser-smi.y 21 Apr 2002 17:38:11 -0000 @@ -1339,6 +1340,10 @@ modulePtr = findModuleByName($3); if (!modulePtr) { modulePtr = loadModule($3); + /*XXX duplicate error, but with line # */ + if (!modulePtr) + smiPrintError(parserPtr, + ERR_MODULE_NOT_FOUND, $3); } checkImports(modulePtr, thisParserPtr); It doesn't suppress the error that loadModule prints, so you get two copies of the MODULE_NOT_FOUND error, but it at least gives you the info. [This patch will not apply directly due to whitespace corruption - just add the 3 or 4 lines by hand] Bill

3 2

RE: [libsmi] Errors while accessing it in DLL
by Hills, Steve 16 Apr '02

16 Apr '02

Are you including the header file in a C++ file? If so then do extern "C" { #include "smi.h" } This will force the included header file to keep the C export names (and not do C++ name mangling). Also, I'm assuming your building this on Windows (Win32)? I am also and the libsmi code crashes on the call to smiExit(). If you run into this and find the fix please forward it to me. Steve Hills -----Original Message----- From: Save, Amit Prabhakar (Amit) [mailto:save@agere.com] Sent: Tuesday, April 16, 2002 4:39 AM To: Salam, Abdul Cc: libsmi(a)ibr.cs.tu-bs.de Subject: RE: [libsmi] Errors while accessing it in DLL Hi, I have cerated a lib from LibSmi say smiDump.lib. I'm making a call to smiDumpMain() inside this smiDump.lib from my code. Now I'm creating a DLL of my code. Similalrly, when I used to create an EXE of my code, I never faced this problem. Here too I was making a call to smiDumpMain() inside this smiDump.lib Thanks & regards, Amit Save -----Original Message----- From: Salam, Abdul [mailto:Abdul.Salam@barconet.com] Sent: Tuesday, April 16, 2002 5:02 PM To: 'Save, Amit Prabhakar (Amit)' Subject: RE: [libsmi] Errors while accessing it in DLL Of course You are linking the wrong dll. -----Original Message----- From: Save, Amit Prabhakar (Amit) [mailto:save@agere.com] Sent: Tuesday, April 16, 2002 4:52 PM To: libsmi(a)ibr.cs.tu-bs.de Subject: [libsmi] Errors while accessing it in DLL Hi, I have created one lib instead of creating smidump.exe. The main fn. in smidump.c was renamed to smiDumpMain(). So that I could access it inside my code as a Library rather than to run it as a command. I hope till this everything is fine? When I try to use it in my code, at the time of linking I get errors as Mibcompiler.obj : error LNK2001: unresolved external symbol __imp__smiDumpMain When I was building an EXE of my code making a call to smiDumpMain(), everything used to work fine. I have ran the code also & it works fine. But if I build a DLL of my code making a call to smiDumpMain(), the above error comes up. Regards, Amit Save -- !! 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. -- !! 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

RE: [libsmi] Errors while accessing it in DLL
by Save, Amit Prabhakar (Amit) 16 Apr '02

16 Apr '02

Hi, I have cerated a lib from LibSmi say smiDump.lib. I'm making a call to smiDumpMain() inside this smiDump.lib from my code. Now I'm creating a DLL of my code. Similalrly, when I used to create an EXE of my code, I never faced this problem. Here too I was making a call to smiDumpMain() inside this smiDump.lib Thanks & regards, Amit Save -----Original Message----- From: Salam, Abdul [mailto:Abdul.Salam@barconet.com] Sent: Tuesday, April 16, 2002 5:02 PM To: 'Save, Amit Prabhakar (Amit)' Subject: RE: [libsmi] Errors while accessing it in DLL Of course You are linking the wrong dll. -----Original Message----- From: Save, Amit Prabhakar (Amit) [mailto:save@agere.com] Sent: Tuesday, April 16, 2002 4:52 PM To: libsmi(a)ibr.cs.tu-bs.de Subject: [libsmi] Errors while accessing it in DLL Hi, I have created one lib instead of creating smidump.exe. The main fn. in smidump.c was renamed to smiDumpMain(). So that I could access it inside my code as a Library rather than to run it as a command. I hope till this everything is fine? When I try to use it in my code, at the time of linking I get errors as Mibcompiler.obj : error LNK2001: unresolved external symbol __imp__smiDumpMain When I was building an EXE of my code making a call to smiDumpMain(), everything used to work fine. I have ran the code also & it works fine. But if I build a DLL of my code making a call to smiDumpMain(), the above error comes up. Regards, Amit Save -- !! 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