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

Announcement: View MIBs as SVG (scalable vector graphics)
by Klaus Sperner 04 Jul '05

04 Jul '05

Hi All! During my master thesis (advised by Frank Strauss) I developed a new driver to the smidump program which generates SVG diagrams from MIB modules. If you are interested in getting an overview about a MIB module before you look at the details, this tool is made for you. For a much more detailed explanation of the driver look at the libsmi website: http://www.ibr.cs.tu-bs.de/projects/libsmi/svg/index.html . There you can find information about SVG viewers, installation and invocation and the generated SVG diagrams. Furthermore a web interface to smidump is provided which enables you to generate SVG diagrams online: http://www.ibr.cs.tu-bs.de/projects/libsmi/svg/mib2svg.cgi . So I invite you to install a SVG viewer, point your browser to the MIBtoSVG web interface and play around with it. Feedback is highly welcome, mail your comments and suggestions to the libsmi mailing list or directly to me. With kind regards, Klaus Sperner

1 0

smidump to convert into xml
by Antoine Roelens 15 Jun '05

15 Jun '05

Hello, I'm a new user and I especially use the smidump tool in order to convert MIB into XML. I encountered two problems: _ 1 : if want to export into a xml file with xml Schema structure I use the command line : smidump -f xml -o result.xml mib_file The problem is that in the xml file there are both DTD and Xml schema referenced. <?xml version="1.0"?> <!DOCTYPE smi SYSTEM "http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.dtd">  <smi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.ibr.cs.tu-bs.de/projects/nmrg/smi. xsd"> If I remove the line : <!DOCTYPE smi SYSTEM "http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.dtd"> the xml file is valid. _ 2 : If I want to execute the conversion of a MIB file like ENTITY-MIB containing a NOTIFICATION and this NOTIFICATION doesn't include object, the result in XML format is : <notifications> <notification name="entConfigChange" oid="1.3.6.1.2.1.47.2.0.1" status="current"> <objects> </objects> <description> An entConfigChange ....... </description> </notification> </notifications> And this is wrong according to the DTD or the XMl schema. The tag <objects> must contain at least on tag <object>. In the MIB NOTIFCATION-TYPE objects are optional. Thank you in advance for your help and for this tool Cheers Antoine

1 0

internal-other - An unspecified error occured
by Per Jessen 05 Jun '05

05 Jun '05

I ran smilint on the ZyXEL MIB which produces quite a few errors - but also a ton of these: ZYXEL-MIB.txt:74: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:77: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:85: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:89: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:97: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:101: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:109: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:112: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:122: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:133: {internal-other} syntax error, unexpected ACCESS ZYXEL-MIB.txt:141: {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER ZYXEL-MIB.txt:144: {internal-other} syntax error, unexpected ACCESS The explanation of 'internal-other' asked that I submit a report. An unmodified version of what appears to be the most recent ZyXEL MIB is available here: http://jessen.ch/files/Zyxel.mib -- /Per Jessen, Zürich

1 1

Detailed change log
by Arkadiusz Gabriel 06 May '05

06 May '05

Hi, All! I have looked through the libsmi website and the svn repository, but I have found only rough change log. Is there a detailed change log for smilib? Especially for bug fixes? Regards Arek ps. Sorry if it's not the right place to ask, but seems to be the only one...

2 1

smidump/mosy problem
by Allen McIntosh 04 May '05

04 May '05

Happens with latest source. Input: FOO DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY FROM SNMPv2-SMI; fooMIB MODULE-IDENTITY LAST-UPDATED "200006270000Z" ORGANIZATION "Carrots Inc." CONTACT-INFO "Bugs Bunny" DESCRIPTION "Testing" REVISION "200006270000Z" DESCRIPTION "1 2 3" ::= {iso(1) member-body(2) us(840) 802dot3(10006) snmpmibs(300) 43 } fooObjects OBJECT IDENTIFIER ::= { fooMIB 1 } Output (smidump --format=mosy FOO.my): fooMIB snmpmibs.43 %n0 fooMIB module-identity fooObjects fooMIB.1 %n0 fooObjects object-id The ancestry of snmpmibs is clearly stated in the input, but does not appear in the output. I have access to a mosy descendent (still called mosy) that outputs fooMIB 1.2.840.802.10006.300.43 (Rest of output is the same) I don't think that smidump should necessarily produce identical output, but it ought to be possible to re-create the object ID.

2 1

Unsigned64
by Allen McIntosh 03 May '05

03 May '05

"the SPPI construct/keyword `Unsigned64' may not be used in a MIB" Why? When did SMI disallow it? I agree that it might not be wise, but making this a fatal error in smidump --format=mosy CISCO-CLASS-BASED-QOS-MIB.my seems a little extreme.

2 1

Libsmi 0.4.3 memory fault (Linux/gcc)
by Allen McIntosh 03 May '05

03 May '05

The libsmi parser memory faults when parsing mibs/ietf/DOT12-RPTR-MIB. Repeat by running smilint mibs/ietf/DOT12-RPTR-MIB after installing libsmi. This happened to me under RedHat 9 (gcc 3.2.2/x86) and RedHat 7.3 (gcc 2.96/x86). The parser usually runs off the rails thus: $ gdb /usr/local/bin/smilint [stuff omitted] (gdb) run mibs/ietf/DOT12-RPTR-MIB Starting program: /usr/local/bin/smilint mibs/ietf/DOT12-RPTR-MIB mibs/ietf/DOT12-RPTR-MIB:36: revision for last update is missing mibs/ietf/DOT12-RPTR-MIB:151: warning: use Integer32 instead of INTEGER in SMIv2 Program received signal SIGSEGV, Segmentation fault. 0x40037b15 in checkObjects (parserPtr=0xbffff5f0, modulePtr=0x80559a0) at parser-smi.y:220 220 if (objectPtr->nodePtr->parentPtr && (gdb) where #0 0x40037b15 in checkObjects (parserPtr=0xbffff5f0, modulePtr=0x80559a0) at parser-smi.y:220 #1 0x4003a26c in smiparse (parserPtr=0xbffff5f0) at parser-smi.y:1641 #2 0x40031021 in loadModule ( modulename=0xbffff841 "mibs/ietf/DOT12-RPTR-MIB", parserPtr=0x0) at data.c:3792 #3 0x40035110 in smiLoadModule (module=0xbffff841 "mibs/ietf/DOT12-RPTR-MIB") at smi.c:416 #4 0x080492f2 in main (argc=2, argv=0xbffff6f4) at smilint.c:314 #5 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 (gdb) print objectPtr->nodePtr->parentPtr $1 = (struct Node *) 0x62696d2f Running with ElectricFence and EF_PROTECT_BELOW on turns up a problem, if that helps. I can provide details if that would help.

2 2

smidump perl output module naive about backslashes
by Allen McIntosh 26 Apr '05

26 Apr '05

The "perl" output module in smidump seems to be a little naive about backslashes. (Given the output language, I can understand a little difficulty in getting all the special characters escaped correctly.) Rather than trust the offending string to a mailer, I've included it as an attachment. It's taken from CISCO-SLB-EXT-MIB.my, which is part of the CISCO MIB collection. The perl output won't compile, and the problem seems to be that '\' gets rendered as \'\\' (the backslash in the middle isn't being doubled). This problem was found with version 0.4.3, running on Linux/x86. [I may wind up fixing this one myself while fixing another problem. Look for a post about the joys :-) of HP-UX in a few days.] SlbRegularExpression ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "A regular expression of length 0 to 255. Regular expressions are typically used for matching fields in Layer 7 data streams, such as URLs or Cookies in HTTP. The following syntax is based on the file name matching algorithm commonly employed in UNIX : '*' matches zero or more characters; '?' matches exactly one character; '\' means escaped character, e.g., '\*' matches the character '*'; a bracketed range matches any single character from the range, e.g. [0-9] matches '0', '2', and '9', but not 'a'; a leading ^ in a range means don't match any in the range; '+' matches any sequence of one or more characters; '.' matches any single character; All other characters represent themselves. '\a' matches alert (ASCII 7); '\b' matches backspace (ASCII 8); '\f' matches form-feed (ASCII 12); '\n' matches newline (ASCII 10); '\r' matches carriage return (ASCII 13); '\t' matches tab (ASCII 9); '\v' matches vertical tab (ASCII 11); '\0' matches null (ASCII 0); '\\' matches backslash; '\x##' matches the ASCII character whose hexadecimal representation is ##. " SYNTAX OCTET STRING (SIZE (0..255))

2 4

Doubts regarding smidump data structures
by Pamidipati Suresh-G20238 22 Apr '05

22 Apr '05

Hi, Smidump uses the data structures Module, Object, Type, List for storing the information as defined in the ASN.1 MIB/SMI files. I have a doubt how the List pointer of the Type structure is assigned a value. I have seen that for Syntax like xyzTableEntry (which is a SEQUENCE containing all the columns of xyzTable), Type structure is created and List pointer contained in this structure points to linked list of nodes, each node corresponding to a column of the table. I mean to say if there are 'n' elements present in the SEQUENCE xyzTableEntry, ListPtr points to 'n' number of nodes. Also if there is any object having the syntax like INTEGER {1,2,3,4} (enumeration), then for this syntax also, Type structure contains List ptr pointing to list of 4 nodes. Now I have the questions. 1.The Type structure for Syntax like Guage, Integer, IpAddress, and others also contains List pointer pointing to one node. 2. And there is a Textual convention RouterId defined in OSPF-MIB whose syntax is defined as IpAddress. But the Type structure built for this RouterId contains List ptr pointing to NULL (0x0). Why is this so..? Any information explaining this will be greatly appreciated. Regards, suresh.

1 0

Does not smiInit() read config ?
by KUBOTA Takaya 08 Mar '05

08 Mar '05

Hi all, I'm a newbe and using libsmi for parsing COPS PIB files. I have a question about smiInit(). manual smi_config(3) says: The smiInit() function should be the first SMI function called in an application. It initializes its internal structures. If tag is not NULL, the global configuration file and (on UNIX systems) a user configuration file are read implicitly, if existent. All global statements and those statements with a tag (a ``tag: '' prefix) that matches the tag argument are executed. (see also CONFIGUュ RATION FILES below). smiInit() returns zero on success, or otherwise a negative value. However, source code smi.c (smiInit()) dose not seem to read a global configuration file when tag is NULL. Should I call smiReadConfig() by myself or did I some mistakes ? Thanks in advance for your time. regards -- KUBOTA,Takaya@NTT SOFTAWARE CORPORATION <takaya(a)po.ntts.co.jp>

1 0