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

Clarification in smilint.......
by Vivekanandan V 04 Dec '01

04 Dec '01

Hello, When Iam compiling Ip-forward.mib (Rfc:2096), using smilint 0.2.6, I get the following error message: --> index element 'ipCidrRouteTos' of row 'ipCidrRouteEntry' must have a range restriction. Whether it is mandatory to impose a range restriction on all index elements of a table ??? If so, can you please let me know where this has been mentioned in any Rfc. Thanking you in advance, Regards, Vivekanandan.V P.S: zip file of ip-forward.mib attached with this mail.

3 2

Re: [libsmi] libsmi-0.3 announcement
by Bill Fenner 27 Nov '01

27 Nov '01

>Is there available a set of test MIB modules that demonstrate the >operation of Smidiff? http://www.aciri.org/fenner/mibs/extracted/ contains somewhere around 2 years' worth of all (most) MIBs published in RFCs and Internet-Drafts; you could probably find some good changes there to try smidiff on. Bill -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

libsmi anonymous CVS repository
by Frank Strauss 26 Nov '01

26 Nov '01

Hi! I just want to point out the libsmi anonymous CVS repository, which is updated every night to contain the most recent bug fixes and enhancements (and sometimes the latest invented bugs). In fact, today C.M. Heard helped us to fix two bugs in the 0.3.0 release (an off-by-one error in the check for exceeding OID lengths of tabled indexing constructs, and the check for InetAddressType/InetAddress groupings when these types are implicitly sub-typed). These bugs are already fixed in the anonymous CVS repository and they will be fixed in the next libsmi release. But new releases will not be made after each and every bug fix. So, people who want to use the most recent stuff, should consider using CVS. -frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

libsmi-0.3 announcement
by Frank Strauss 26 Nov '01

26 Nov '01

The following message is a courtesy copy of an article that has been posted to comp.protocols.snmp,comp.dcom.net-management as well. Libsmi 0.3 is available for download. Copyright (c) 1999-2001 Frank Strauss, Technical University of Braunschweig. Libsmi is a C library that allows network management applications and MIB authoring tools to access SMI MIB module information through a well defined API that hides the nasty details of locating and parsing SMIv1/v2 MIB modules. Libsmi supports exact and iterative retrieval functions for all major SMIv1 and SMIv2 constructs. There are four tools on top of the library and a sh/awk-script: - Smiquery allows simple queries for single MIB module items. Smilint allows to increase the verbosity of the parser(s), so that MIB module files can be checked for syntax and semantic errors. - Smidump can be used to dump MIB modules in various formats. The current output backends allow to dump trees of OIDs, type definitions and recursive imports, to convert modules between SMIv1 and SMIv2, to produce JIDM compliant CORBA-IDL files, UCD-SNMP code stubs, MOSY style output, JAX Java AgentX sub-agent templates, XML and XML-Schema MIB representations, Perl and Python representations, graphical conceptual MIB models, and SCLI code stubs. - Smidiff allows MIB authors, MIB reviewers and implementors to compare two revisions of the same MIB for legal and illegal changes. - Finally, smistrip allows to strip SMIv1/v2 modules from documents like RFCs and Internet-Drafts. Enclosed with the libsmi package, there are all (bug fixed) current IETF standard MIB modules as of 2001-11-23, as well as some other modules, man pages for all library functions and tools, and a small libsmi test suite. The software comes with automake/autoconf and libtool support. Hence it should compile and build with or without shared libraries on most UNIX style platforms, as well as on W32/cygwin, though it's just developed on Sun Solaris 2.5.x and Linux. However, questions about all platforms can be discussed on the libsmi mailinglist. For those familiar with recent libsmi development: The most significant change since the previous 0.2.x releases is the addition of the smidiff tool for MIB revision comparison. It has been developed during the past three months primarily by Torsten Klie. Online information on libsmi together with download and CVS access information, the (free) license terms, manual pages, and the mailing list is available at: http://www.ibr.cs.tu-bs.de/projects/libsmi/ Enjoy! Frank Strauss <strauss(a)ibr.cs.tu-bs.de> -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

3 3

smidump - f netsnmp problem
by Var P 02 Nov '01

02 Nov '01

hi, I am using libsmi-0.2.17 version. When I use "smidump" to generate netsnmp code (smidump -f netsnmp), for the write_method routine (ex: write_ustSSSimpleString_stub), it is generating empty function definition. Is it always like that (I mean, shall I have write the code for switch(), case: RESERVE1, RESERVE2 etc...) or it is supposed to generate the function definition. Thanks, __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Data Type Issue
by Raj Sohal 26 Oct '01

26 Oct '01

Hello, I am using "smidump.exe -s -f ez" (smidump version 0.2.13) command to parse my mibs and get a formatted output. The output comes in this format system|1.3.6.1.2.1.1|GP|NA sysDescr|1.3.6.1.2.1.1.1|S|RO sysObjectID|1.3.6.1.2.1.1.2|OI|RO sysUpTime|1.3.6.1.2.1.1.3|C[0,-1]|RO sysContact|1.3.6.1.2.1.1.4|S|RW sysName|1.3.6.1.2.1.1.5|S|RW snmpInTooBigs|1.3.6.1.2.1.11.8|C[0,-1]|RO snmpInNoSuchNames|1.3.6.1.2.1.11.9|C[0,-1]|RO snmpInBadValues|1.3.6.1.2.1.11.10|C[0,-1]|RO If you look at the output, there's character 'C' for TimeTicks, Counter32, Gauge32 & Unsigned32 datatypes. Is there a way I can get a specific character for each datatype so that I can distinguish between the data types. Thanking in advance for your help. Regards, Raj Sohal Software Eng. Dorado Software, Inc. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 3

MIB filename requirements
by Becky Phaneuf 23 Oct '01

23 Oct '01

smidump requires that a MIB's filename be the same as its module name. While I have no issue with this I have heard others complain about having to change their file names. I am hoping to get an explanation/opinion that I can pass along as to why this is required and what problem(s) it prevents. Thank you -Becky

3 2

Status field?
by Matthew Love 23 Oct '01

23 Oct '01

Hi Does anyone know why all my node->status fields are set to SMI_STATUS_NOT_IMPLEMENTED? Matthew Love Software Engineer NETWORK HARMONi, Inc. matthew(a)networkharmoni.com Ph +61 8 92133412 -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Default Values on Object Identifiers
by Alberto Olalla 19 Sep '01

19 Sep '01

Hi ! I am having a problem with smidump with producing xml. Default values in oid objects are not well produced: Input: -------- svConnLocalEndPt OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "The object identifier of the 1st attribute of the end point in the associated protocol specific end point table." DEFVAL { { 1 3 6 } } ::= { svConnEntry 2 } Output: ----------- <column name="svConnLocalEndPt" oid="1.3.6.1.4.1.351.1.101.1.3.1.2" status="current"> <syntax> <type module="" name="ObjectIdentifier"/> </syntax> <access>readwrite</access> <default>0.0</default> ??????????????????????? <description> The object identifier of the 1st attribute of the end point in the associated protocol specific end point table. </description> </column> However, this value is well produced with "smiv2" output format: svConnLocalEndPt OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The object identifier of the 1st attribute of the end point in the associated protocol specific end point table." DEFVAL { ccitt } OK ::= { svConnEntry 2 } Does anyone know how I could fix this problem? Thanks Alberto Olalla

3 2

[PATCH] some prototypes
by Harrie Hazewinkel 17 Sep '01

17 Sep '01

Hi all, I have attached a patch (tested for 0.2.17) that deals with proper function prototype definitions. I also discovered some error with 'smiExit' which had one time even an argument when used. (See patch) Cheers, Harrie

1 0