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

current vs. mandatory as status values
by Björn Koseler 29 Nov '02

29 Nov '02

Hi! I am rather new to this whole smi and mib stuff, so this question might be stupid: When converting RFC1213-MIB to xml with smidump (libsmi 0.4.1), the status attribute values in the resulting xml file are always equal to "current", though they should equal "mandatory" since RFC-1213 refers to SMIv1 (RFC1155) and not to SMIv2 (RFC2578). And why is status an attribute while access is a child node? Have I gotten something completely wrong? Regards Björn

3 2

errors compiling RFC1213-MIB
by Björn Koseler 27 Nov '02

27 Nov '02

Hi! I am new to libsmi and I am using version 0.4.1 under Windows XP. Why is it that http://www.ibr.cs.tu-bs.de/projects/libsmi/mibs.html says RFC1213-MIB compiles without warnings or errors while in fact compiling it with "smidump -f xml -c smi.cfg ..\mibs\ietf\RFC1213-MIB -o tmp.xml" results in the following errors: ..\mibs\ietf\RFC1213-MIB:262: index element `ifIndex' of row `ifEntry' must have a range restriction ..\mibs\ietf\RFC1213-MIB:609: index element `atIfIndex' of row `atEntry' must ha ve a range restriction ..\mibs\ietf\RFC1213-MIB:1301: index element `ipNetToMediaIfIndex' of row `ipNet ToMediaEntry' must have a range restriction smidump: module `..\mibs\ietf\RFC1213-MIB' contains errors, expect flawed output May I simply ignore these reported errors or do I have to rearrange any kind of settings in order to make the compiler run without errors? Thanks in advance Björn

2 1

libsmi release 0.4.1
by Frank Strauss 18 Nov '02

18 Nov '02

Hi! Due to a number of minor bug fixes, added parser checks, modifications in some smidump drivers, and updated Standard MIBs, I've bundled a new release: 0.4.1. As usual, you can find it at http://www.ibr.cs.tu-bs.de/projects/libsmi/ ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/ Enjoy,

1 0

Question: Configuring libsmi
by Gerardo Garcia de Blas 31 Oct '02

31 Oct '02

My name is Gerardo. I would like to use the smidump and smilint tools, but I don't know what I must configure for using it. The help given is difficult for me to understand, so I would be grateful if somebody tells me how I can start quickly to use the tools. I would like to know also what more I can do with the libsmi: other utilities (not just tools),... Thank you very much.

2 1

Exception when calling 'smiparse'
by Heiko.Eichberger＠RSBICK.rohde-schwarz.com 30 Oct '02

30 Oct '02

Hi, I get an exception when calling "smiparse" on a few MIB modules (I call "smiLoadModule" and the debugger steps into the catch-block when calling "smiparse"). Do you have any hints (because I don't have the source of the "parse")? When I try to step into the "smiparse" I'm asked for the module "BISON.SIMPLE"!? Regards, Heiko

2 1

RE: [libsmi] xsd output
by Steve Bucknam 24 Oct '02

24 Oct '02

I have also noticed that all of the generated namespaces include: xmlns:xml="http://www.w3.org/XML/1998/namespace" Both the crimson parser + IE barf on the use of "xml" as a ns prefix. I think it's actually a bug in crimson. Can the prefix be changed rather than waiting for for patches from several companies. Crimson and IE are very popular, so this could be a significant issue. Steve -----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Wednesday, October 23, 2002 11:47 AM To: Steve Bucknam Cc: libsmi(a)ibr.cs.tu-bs.de Subject: Re: [libsmi] xsd output Hi! Steve> I am generating the xsd for the version of RCF1213 retrieved from Steve> mibcentral. I get no errors or warnings, yet "ifTable" has no Steve> entry. The "ifEntry" is present and contains the sequence of OIDs Steve> that should appear under "IfEntry". "IfEntry" is also missing. Steve> Is this a design feature to minimize unnecessary nodes, or a bug? Well, RFC 1213 is a bug. :-) We don't care a lot about obsolete SMIv1 MIBs. The ifTable is defined in the current Standards Track version of the IF-MIB which is published in RFC 2863. If you use the IF-MIB (it also comes with libsmi), then `smilint -f xsd' should produce a better result. -frank

3 2

RE: [libsmi] xsd output
by Steve Bucknam 23 Oct '02

23 Oct '02

I assume you mean "smidump -f xsd" on the rfc2863 mib (after running it through smistrip) and not really "smilint -f xsd". I did this and the parses generated an error: /IF-MIB:1134: index element `ifRcvAddressAddress' of row `ifRcvAddressEntry' must have a size restriction So I added a size restriction to the mib and ran smidump -f xsd again and there were no errors. But, when I opened the xsd, there was no "ifTable" or "IfEntry", just the "ifEntry". If fact, the xsd output never seems to include tables, just the entries. Is this intentional? I am using libsmi from cvs. Steve -----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Wednesday, October 23, 2002 11:47 AM To: Steve Bucknam Cc: libsmi(a)ibr.cs.tu-bs.de Subject: Re: [libsmi] xsd output Hi! Steve> I am generating the xsd for the version of RCF1213 retrieved from Steve> mibcentral. I get no errors or warnings, yet "ifTable" has no Steve> entry. The "ifEntry" is present and contains the sequence of OIDs Steve> that should appear under "IfEntry". "IfEntry" is also missing. Steve> Is this a design feature to minimize unnecessary nodes, or a bug? Well, RFC 1213 is a bug. :-) We don't care a lot about obsolete SMIv1 MIBs. The ifTable is defined in the current Standards Track version of the IF-MIB which is published in RFC 2863. If you use the IF-MIB (it also comes with libsmi), then `smilint -f xsd' should produce a better result. -frank

2 1

RE: [libsmi] xsd output
by Steve Bucknam 23 Oct '02

23 Oct '02

I am generating the xsd for the version of RCF1213 retrieved from mibcentral. I get no errors or warnings, yet "ifTable" has no entry. The "ifEntry" is present and contains the sequence of OIDs that should appear under "IfEntry". "IfEntry" is also missing. Is this a design feature to minimize unnecessary nodes, or a bug? Steve -----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Wednesday, October 23, 2002 8:47 AM To: Steve Bucknam Cc: libsmi(a)ibr.cs.tu-bs.de Subject: Re: [libsmi] xsd output Hi! Steve> Is anyone working on the XSD output? It appears that there are Steve> many missing elements in the generated xsd files. I'd like to Steve> help finish this functionality. Which version of libsmi do you use? We (well, Torsten Klie in fact does most of the work) are continously working on the XSD MIB representation, its implementation and an additional tool (mibdump) to get instance documents via SNMP retrieval. If you want to keep up with our current work, please use the CVS repository and get the `libsmi' CVS module (see http://www.ibr.cs.tu-bs.de/projects/libsmi/download.html). We would be happy to have further dicussion about improvements of the XML Schema format on the mailinglist. -frank

2 1

xsd output
by Steve Bucknam 23 Oct '02

23 Oct '02

Is anyone working on the XSD output? It appears that there are many missing elements in the generated xsd files. I'd like to help finish this functionality. Steve

2 1

query
by g.g 16 Oct '02

16 Oct '02

Hi All, I have mib files X-MIB which has linkage to Y-MIB within it. Both files X-MIb and Y-MIB are present in the same directory. when i do smidump -f xml -o test.xml ./X-MIB it gives an error failed to locate MIB module `Y-MIB' How to get rid of the error. Rgds RamanGG --------------------------------- Do you Yahoo!? Faith Hill - Exclusive Performances, Videos, & more faith.yahoo.com

2 1