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

libsmi test cases
by Andrew Hood 28 May '09

28 May '09

When people commit updates to SVN which change the output of the smidump would they please update the files in test/dumps to match? I've just spent a hour or so determining that the example output does not appear to have been updated since change r12250 and possibly earlier. Also, the line numbers will differ and wrap will have mucked up the format, but 'generated by smidump' can appear with an upper case G. /build/libsmi/trunk: svn diff configure.in Index: configure.in =================================================================== --- configure.in (revision 16122) +++ configure.in (working copy) @@ -214,7 +219,7 @@ AC_PATH_PROGS(DIFF, gdiff diff) $DIFF --version >/dev/null 2>&1 if test $? -eq 0 ; then - DIFF="$DIFF --ignore-matching-lines='generated by smidump' --ignore-matching-lines='\$Id.*\$' --ignore-matching-lines='@author.*smidump'" + DIFF="$DIFF --ignore-matching-lines='generated by smidump' --ignore-matching-lines='Generated by smidump' --ignore-matching-lines='\$Id.*\$' --ignore-matching-lines='@author.*smidump'" fi AC_EXEEXT -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who

1 0

Seek Help (libsmi smidump question)
by greekdu 28 May '09

28 May '09

Hi, Thanks for providing so powerful tool set "libsmi" for us to do the research. But when I use the tool "smidump", I have encountered some problems. I couldn't convert mib file(*.mib or *.txt) to schema file(*.xsd) successfully. My operation is step 1: download "libsmi" from your page step 2: decompression the tool set step 3: copy mib file (SNMPv2-SMI.txt) to the relatively path (c:\libsmi\bin) step 4: open "cmd" step 5: enter instructions c:\libsmi\bin\smidump -f xsd ./SNMPv2-SMI.txt>SNMPv2-SMI.xsd -k The result on the screen are as follows: ./SNMPv2-SMI.txt:191: range limit exceeds underlying basetype ./SNMPv2-SMI.txt:191: range limits must be `lower-bound .. upper-bound' ./SNMPv2-SMI.txt:196: range limit exceeds underlying basetype ./SNMPv2-SMI.txt:196: range limits must be `lower-bound .. upper-bound' ./SNMPv2-SMI.txt:202: range limit exceeds underlying basetype ./SNMPv2-SMI.txt:202: range limits must be `lower-bound .. upper-bound' ./SNMPv2-SMI.txt:207: range limit exceeds underlying basetype ./SNMPv2-SMI.txt:207: range limits must be `lower-bound .. upper-bound' ./SNMPv2-SMI.txt:217: number `18446744073709551615' is out of range for SPPI 64b it unsigned numbers ./SNMPv2-SMI.txt:217: range limits must be `lower-bound .. upper-bound' smidump: module `./SNMPv2-SMI.txt' contains errors, expect flawed output So, please tell me how to convert is successfully, thanks very much! Plus, if the mib file import other module like SNMPv2-MIB, please tell me how to convert is successfully. Thanks! GreekDu 2009.5.28

2 1

can not make libsmi
by Chi.Guan＠L-3Com.com 02 May '09

02 May '09

Hi I download the libsmi-0.4.8 into my local QNX machine. I try to do "make". But I got error: "make: *** No targets specified and no makefile found. Stop" I try to do "make install", I got error "make: *** No rule to make target `install'. Stop.". Is this a configure problem. Can anybody give me a example of ./configure? Thanks Chi

1 0

Query about ERR_OID_ADMIN_ZERO (last subidentifier assigned to ... may not be zero)
by Martin 18 Apr '09

18 Apr '09

Hi, Running smilint (0.4.8) over a MIB definition file I'm responsible for maintining, provoked this error output: <filename>:<linenum>: [1] last subidentifier assigned to `national' may not be zero The source file had, at that point: ::= { iso member-body(2) gb(826) national(0) eng-ltd(1) <etc> } Looking at http://www.oid-info.com/get/1.2.826.0.1 shows that this appears to be perfectly legal though. I found that by changing the source to ::= { iso member-body(2) gb(826) 0 eng-ltd(1) <etc> } the error was suppressed, but IMO this is a bug in parser-smi.c (lines 976 & following), not in my MIB. Thoughts?

2 1

"internal-other" error due to invalid characters in description
by Hicks, Anthony M 09 Apr '09

09 Apr '09

I got the following "internal-other" error because of the quotes in my description text. It was easy to find the problem but would be nice if this could be handled more gracefully. Snip from Mib file: orchNBAStHcOvStatus OBJECT-TYPE SYNTAX OrchNBAStHcStateTC MAX-ACCESS read-only STATUS current DESCRIPTION " Indicates the overall health-check state for the NBA system. This may be "ok", "warning" or "fail". See the description in OrchNBAStHcStateTC for further information regarding these states. " ::= { orchNBAStHcOverall 3 } Result from libsmi: mibs/ORCHESTRIA-NBA-MIB.mib:2485: [1] {internal-other} syntax error, unexpected LOWERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL mibs/ORCHESTRIA-NBA-MIB.mib:2489: [5] {internal-flushing} warning: flushing recent incorrect declaration, see previous error(s) Additional descriptions of some error/warning messages: Error: internal-other (level 1) Message: %s Description: An unspecified error occured. Please submit a detailed bug report to the libsmi maintainer or the libsmi mailing list at . Tony Hicks CA Senior Software Engineer Tel: +44-1823-424063 Anthony.Hicks(a)ca.com <mailto:Andrew.Stickler@ca.com> <http://www.ca.com/>

1 0

Re: [libsmi] libsmi 0.4.8 XML mapping problem with fixed OctetString Default Values
by Jens Engel 30 Mar '09

30 Mar '09

On 30.03.2009, at 13:00, Juergen Schoenwaelder wrote: > On Mon, Mar 30, 2009 at 10:34:17AM +0200, Jens Engel wrote: >> >> On 30.03.2009, at 10:20, Juergen Schoenwaelder wrote: >> >>> On Sat, Mar 28, 2009 at 04:43:55PM +0100, Jens Engel wrote: >>>> RELEASE: libsmi 0.4.8 >>>> >>>> XML mapping of default value for fixed-sized binary OctetStrings is >>>> wrong now (or at least sometimes). >>>> NOTE: Was correct in libsmi 0.4.7. >>>> >>>> DLSW-MIB::dlswTConnConfigSapList: >>>> DLSW-MIB::dlswIfSapList: >>>> DEFVAL { 'aa000000000000000000000000000000'H } >>>> becomes 'ff000...'H in XML format: >>>> <default>0xff000000000000000000000000000000</default> >>>> >>>> IPSEC-SPD-MIB::spdTimeFiltDayOfMonthMask: >>>> DEFVAL { 'fffffffffffffffe'H } >>>> becomes in XML format: >>>> <default>0xffffffffffffffff</default> >>>> >>>> >>>> >>> I can't reproduce this problem using libsmi rev=13631 on a 32-bit >>> Linux system. The code compiles and produces the right output. Can >>> you >>> check again and/or provide some more details? >>> >>> /js >> >> I will try, but I have currently no easy access to Linux system. >> I discovered it on MACOSX 10.5.6. I can try it with Cygwin, too. >> It will probably take 1 day or 2. > > Revision 13631 seems to work for me on MacOS X 10.4.11 and 10.5.6. > > /js Works for me, too (FIXED on the HEAD). I also reproduced the 0.4.8 problem under Cygwin on a PC. Therefore, I assume that problem was fixed (again) sometime after the last release. ADDITIONAL REMARKS: 1. By the way, I had some problems to compile the current HEAD on my MAC. The problem appears with "parser-yang.y" when using GNU bison 1.4.1. When I used the MAC native bison 1.3, everything was fine. Therefore, I assume there might be a problem with this grammar part when using a newer bison version during the next release. 2. In addition, 3-4 tests of the testsuite are failing on MACOSX (3 for 0.4.7/0.4.8 and 4 for the HEAD). Under Cygwin, only 1 test failed for version 0.4.8. I will look into this issue probably next week. (I already looked at some diff files. It looks like only the line numbers are slightly off?!?) 3. MINOR ISSUE: On the current HEAD, "make distclean" does not cleanup all temporary files. I did not check older versions. shell> svn status ? depcomp ? missing ? install-sh ? test/dumps/yang/Makefile.in ! win/config.h ? lib/parser-yang.c ? lib/parser-yang.tab.h ? lib/scanner-yang.c M lib/parser-smi.c Ciao, Jens Engel

1 0

libsmi 0.4.8 XML mapping problem with fixed OctetString Default Values
by Jens Engel 30 Mar '09

30 Mar '09

RELEASE: libsmi 0.4.8 XML mapping of default value for fixed-sized binary OctetStrings is wrong now (or at least sometimes). NOTE: Was correct in libsmi 0.4.7. DLSW-MIB::dlswTConnConfigSapList: DLSW-MIB::dlswIfSapList: DEFVAL { 'aa000000000000000000000000000000'H } becomes 'ff000...'H in XML format: <default>0xff000000000000000000000000000000</default> IPSEC-SPD-MIB::spdTimeFiltDayOfMonthMask: DEFVAL { 'fffffffffffffffe'H } becomes in XML format: <default>0xffffffffffffffff</default> I just discovered that when I compared the XML mapping of libsmi with a number of SNMP-MIBs (My "project" should contain most public MIBs that are also distributed wtih libsmi). NOTE: Other mappings may also be affected. I tried to checkout and use the current Subversion HEAD (rev=13629). But it is currently in an unusable state, probably due to the announced changes (a few days ago). Ciao, Jens Engel

2 1

libsmi function naming conventions
by Juergen Schoenwaelder 16 Mar '09

16 Mar '09

Hi, we are implementing support for an additional data modeling language and it seems that the feature set of the language we are currently working on is pretty different from the classic SMI/SPPI/SMIng languages libsmi supports. So the question was raised to what extend it makes sense to try to retrofit things into existing data structures and APIs or whether we should have a separate set of data structures and API functions. We believe, the later approach makes more sense and API usage simpler. It will also make it clearer at the API level that you have to call explicit conversion functions if you want to convert a module between different languages. So in a nutshell, functions with the smi prefix or data types with the Smi prefix would be SMI/SPPI/SMIng specific while functions with some other prefix would be specific to other data modeling languages. Now, there are a bunch of API functions that are really not specific to the SMI/SPPI/SMIng languages but to the library as a whole. I am talking about the functions documented in the smi_config(3) manual page essentially. If the follow the path that the API function prefixes indicate the "framework" they should be used with, then these library infrastructure functions should actually have a "libsmi" prefix, so you would write libsmiInit() or libsmiSetSeverity() or libsmiSetErrorHandler(). Providing ABI backward compatibility should be easy; I think this is more a question how we envision the evolution of this library. Comments? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>

2 1

MIB load limit
by Miroslav Beranič ml. 23 Feb '09

23 Feb '09

Hi, I am trying to load multiple MIB files (about 50 of them) in one process. I get a segment fault when calling method extern SmiNode *smiGetFirstNode(SmiModule *smiModulePtr, SmiNodekind nodekind); I managed to trace it to method static Object *getNextChildObject(Node *startNodePtr, Module *modulePtr, SmiNodekind nodekind) in smi.c:159 (in TRUNK) There is an if statement: if (((!modulePtr) || (objectPtr->modulePtr == modulePtr)) && ((nodekind == SMI_NODEKIND_ANY) || (nodekind & objectPtr->export.nodekind))) { break; } Statement: objectPtr->export seems to point to invalid memory address. As I debuged it looks like properties - export - flags - line point to invalid memory, as by accessing it, it signals SIGSEGV. So my question: Is there any limit on loading MIBs or any other reason this can happen? And next: what would be good way to load multiple MIB-s -- lets say any MIB in specific directory... description of how to do this or some pointers would be great. Best regards, Miroslav Beranič ml.

2 2

Loading MIBs
by Samer Vazdekis 29 Jan '09

29 Jan '09

I configured libsmi to where my mibs are using --with-mibdir option. I noticed though after calling smiInit() that MIBs are not loaded by default. Is there a way to let libsmi load my mibs in my mibs dir on startup?. Do MIB files need to be on special extention?. mine are of .txt type. _________________________________________________________________ So many new options, so little time. Windows Live Messenger. http://www.microsoft.com/windows/windowslive/messenger.aspx

2 1