Libsmi June 2002

libsmi@ibr.cs.tu-bs.de

8 participants
8 discussions

libsmi-0.4 announcement
by Frank Strauss 25 Jun '02

25 Jun '02

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.4 is available for download. Copyright (c) 1999-2002 Frank Strauss, Technical University of Braunschweig. Libsmi is a C library that allows network management applications and MIB and PIB authoring tools to access SMI MIB module information and SPPI PIB module information through a well defined API that hides the nasty details of locating and parsing MIB or PIB modules. Libsmi supports exact and iterative retrieval functions for all major SMIv1/v2 and SPPI constructs. There are four tools on top of the library and a sh/awk-script: - Smiquery allows simple queries for single MIB/PIB module items. - Smilint allows to increase the verbosity of the parser(s), so that module files can be checked for syntax and semantic errors. - Smidump can be used to dump MIB and PIBmodules 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 dump SPPI PIBs, 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 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 and SPPI 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 2002-06-21, as well as some other modules, some SPPI PIBs that are taken from Internet Drafts, 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 changes since the previous 0.3.x releases is the addition of the SPPI parser (which is integrated into the SMI parser), the addition of an SPPI dump driver (both supplied by Moritz Bunkus), and major enhancements of the XML Schema dump driver (supplied by Torsten Klie). Furthermore, a number of bugs have been fixed and many Standard MIB modules and PIB modules have been updated and added. 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>

3 3

Re: [libsmi] Access violation in data.c
by Frank Strauss 19 Jun '02

19 Jun '02

Hi! >>> I have a very rough idea and I hope that this bug has just been >>> repaired last week when I fixed a bug with forward references >>> enumeration types. The fix is in the anonymous CVS. Could you >>> please give it a try? undergrid> Thanks for your response Frank, I've just checked the CVS undergrid> against the source files I have compiled and found no undergrid> updates since I checked them out late Friday night (BST) so undergrid> I guess I already have these updates. I should have said undergrid> when I got the source files out, which was a few hours undergrid> before emailing the list. Frank> Ok. I'll try to examine the problem sometime soon... Ok, second attempt... :-) Although I could not reconstruct the problem, I found an illegal reference of non-local types, that could have been freed in a previous step of the module loop in smiFreeData(). So, could you please give the latest snapshot from the anonymous CVS repository a try... -frank

1 0

Segmentation fault.
by Yogeshwara G 10 Jun '02

10 Jun '02

Hi, I am presently using libsmi-0.3.1 on Windows NT. I have the following code which is resulting in a Segmentation fault. smiSetPath("E:\\Test"); // In Test folder only SNMPv2-MIB, SNMPv2-CONF and SNMPv2-TC files is present. strModuleResult = smiLoadModule("SNMPv2-MIB"); strModuleResult = smiLoadModule("SNMPv2-SMI"); Kindly advise me on how I can get over this problem. Thanks, Yogesh

2 1

smidump output
by Nitin Pingle 09 Jun '02

09 Jun '02

-- hi by using smidump -f xml the output is on the screen. Is there a way where i can specify that the output goes to a file ? - Nitin Pingle

2 1

is libsmi open source
by Nitin Pingle 05 Jun '02

05 Jun '02

hi is this libsmi a open source free for all library or is there any licensing issue. --

2 1

Not able to retrieve all the Oid's after loading a private MIB
by Yogeshwara G 05 Jun '02

05 Jun '02

Hello, I am presently using libsmi-0.3.1 on Windows NT. I am using the following code given below: for((smiNode = smiGetNode(NULL, "1.3")) && (oidlen = smiNode->oidlen); smiNode && (first || smiNode->oidlen > oidlen); smiNode = smiGetNextNode(smiNode, SMI_NODEKIND_ANY), first = 0) { printf("%*s%-32s\n", (smiNode->oidlen - oidlen + 1) * 2, " ", smiNode->name); }; When I load the standard mib files distributed along with the libsmi like SNMPv2-MIB and SNMPv2-SMI. The above code prints the values till snmpObsoleteGroup. But when I load any private mib file. The above code prints the values till the private mibs and doesn't print anything from security onwards. Kindly advise me on what could be wrong here. Thanks, Yogesh

2 1

preserving comments
by Mark Kaplun 03 Jun '02

03 Jun '02

Hi Frank, My understanding is that in the current implementation comments are not being preserved at any data structure in libsmi. If I'm right, I would like to suggest that a code will be added to do this. The advantages of preserving comments are that utilities like dumpsmi will be able to regenerate the exact contents of the original MIB module, and that there are some places, like enum values definition, were it is more convinient to use a comment near the definition. Mark.

5 10

Access violation in data.c
by nick-smi＠undergrid.org.uk 03 Jun '02

03 Jun '02

I've compiled the latest cvs version if libsmi with VS .NET under windows XP. I've come across an access violation when running the smiquery application (with no modifications) when requestin node information on any item in the IF- MIB mib (for example IF-IB::ifNumber.0). The error occurs in data.c line 3511 which is this if statment: if ((objectPtr->typePtr->export.basetype == SMI_BASETYPE_OCTETSTRING || objectPtr->typePtr->export.basetype == SMI_BASETYPE_BITS)) The objectPtr->typePtr->export address does appear to be valid, but VC++ reports that objectPtr->typePtr->export.basetype cannot be evaluated. I've not modified any of the source and I've also tried the packaged files available on the web site with the same result. I've tries other MIB entries including ones in SNMPv2-MIB, RFC1213-MIB, IP-MIB, TCP-MIB and UDP-MIB without any problems, it just appears to occur ith IF-MIB. Anyone got any ideas on this one? Many Thanks. Nick Thomson.

3 2

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 June 2002