Libsmi February 2008

libsmi@ibr.cs.tu-bs.de

6 participants
4 discussions

libsmi numeric constraints convertion bug
by Ilya Etingof 24 Nov '08

24 Nov '08

I've run into a possible problem in SVN version of libsmi. I have not done any debugging, so this is just a bug report: When I do: smidump -f python TCP-MIB.txt for the following MIB text: tcpMaxConn OBJECT-TYPE SYNTAX Integer32 (-1 | 0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1." ::= { tcp 4 } smidump generates: "tcpMaxConn" : { "nodetype" : "scalar", "moduleName" : "TCP-MIB", "oid" : "1.3.6.1.2.1.6.4", "status" : "current", "syntax" : { "type" : { "basetype" : "Integer32", "ranges" : [ { "min" : "-1", "max" : "2147483647" }, ], "range" : { "min" : "4294967295", "max" : "2147483647" }, }, }, "access" : "readonly", "description" : """ [skipped] """, }, # scalar Where range constraints seem to be broken at: 1. Range minimum (0) gets converted into 4294967295. 2. Single value constraint (-1) gets translated into a value range constraint with wildly inflated upper range (2147483647). Current stable release (0.4.5) behaves differently (yet, incorrectly) in this respect: "tcpMaxConn" : { "nodetype" : "scalar", "moduleName" : "TCP-MIB", "oid" : "1.3.6.1.2.1.6.4", "status" : "current", "syntax" : { "type" : { "basetype" : "Integer32", "range" : { "min" : "-1", "max" : "2147483647" }, }, }, "access" : "readonly", "description" : """ [skipped] """, }, # scalar Is there currently a fix for this issue? Thanks, ilya

2 17

libsmi 0.4.6 released
by Juergen Schoenwaelder 01 Mar '08

01 Mar '08

Hi, we have just released version 0.4.6 of libsmi. Despite the usual number of bug fixes, this release contains some new code: - An implementation of RFC 3780 (the SMIng core) replacing the now historic SMIng parser together with an extended API to support SMIng. - An smidump backend which turns SMIv1/SMIv2 modules into YANG modules. It might take some while until package maintainers switch to the new version. As usual, you can get the source from ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/libsmi-0.4.6.tar.gz or the subversion directory directly. /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 2

smicache utility
by Marcin Cieslak 27 Feb '08

27 Feb '08

Hello, What's the purpose of the smicache utility? I have tried to fetch SNMP-REPEATER-MIB and some strange HTML with frames has been downloaded from the URL: http://www.inotech.com/mibs/vendor/baynetworks/rfc1516-mib.txt Is http://www.ibr.cs.tu-bs.de/projects/libsmi/smicache/ is going to be a purl.org-like one-stop shop to fetch all MIBs? Which MIBs are included there? How do I know if there is an error fetching a MIB or the file contains non-MIB garbage? -- << Marcin Cieslak // saper(a)saper.info >>

2 1

missing annotation
by Arndt Jonasson 22 Feb '08

22 Feb '08

In dump-xsd.c, in the function fprintElement, these lines occur: fprintAnnotationElem( f, smiNode ); if( ! hint ) { fprintTypedef( f, smiType, NULL ); } else { fprintTypeWithHint( f, smiNode, smiType, hint ); } In the function fprintIndexAttr, we instead find if( ! hint ) { fprintAnnotationElem( f, smiNode ); fprintTypedef( f, smiType, NULL ); } else { fprintTypeWithHint( f, smiNode, smiType, hint ); } I think that also in the latter case should fprintAnnotationElem be called before the test. What happens otherwise is that the description of an index element will not be output if the element has a display hint. MIB for testing: TEST-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, enterprises, Integer32, OBJECT-TYPE, IpAddress, Unsigned32 FROM SNMPv2-SMI DisplayString, TruthValue, RowStatus FROM SNMPv2-TC; testMib MODULE-IDENTITY LAST-UPDATED "200801140000Z" ORGANIZATION "org" CONTACT-INFO "here" DESCRIPTION "desc" REVISION "200801140000Z" DESCRIPTION "desc" ::= { enterprises 100 } testObjects OBJECT IDENTIFIER ::= { testMib 1 } testTable OBJECT-TYPE SYNTAX SEQUENCE OF TestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "desc Table" ::= { testObjects 1 } testEntry OBJECT-TYPE SYNTAX TestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "desc Entry" INDEX { testProgramId } ::= {testTable 1 } TestEntry ::= SEQUENCE { testProgramId DisplayString, testMajorName DisplayString } testProgramId OBJECT-TYPE SYNTAX DisplayString(SIZE(0..12)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "desc ProgramId" ::= { testEntry 1 } testMajorName OBJECT-TYPE SYNTAX DisplayString(SIZE(0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "desc MajorName" ::= { testEntry 2 } END

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi February 2008