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

RE: [libsmi] DEFVAL in xsd output
by Steve Bucknam 17 Mar '03

17 Mar '03

Will this show up in the TODO (http://www.ibr.cs.tu-bs.de/projects/libsmi/TODO.html) section of the site so I watch for this support? Steve -----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Saturday, March 15, 2003 5:58 AM To: Steve Bucknam Cc: libsmi Mailinglist Subject: Re: [libsmi] DEFVAL in xsd output Hi! Steve> Is DEFVAL supported in smidump with xsd format? I have many Steve> defvals defined for different syntax types. The default values Steve> do not show up in the xsd output (at least, not in a way that is Steve> obvious to me). Ack. We'll have to add a <default> element to the <appinfo> element in those cases. Thanks for this hint. -frank

2 1

DEFVAL in xsd output
by Steve Bucknam 15 Mar '03

15 Mar '03

Is DEFVAL supported in smidump with xsd format? I have many defvals defined for different syntax types. The default values do not show up in the xsd output (at least, not in a way that is obvious to me). For example: tsPartnerImportInitiate OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "initiate the import operation for this tsPartner." DEFVAL { false } ::= { tsPartnerEntry 4 } Results in XSD output of: <xsd:element name="tsPartnerImportInitiate" minOccurs="0"> <xsd:annotation> <xsd:appinfo> <maxAccess>read-write</maxAccess> <oid>1.3.6.1.4.1.2500.1.1.8.1.2.1.1.4</oid> <status>current</status> </xsd:appinfo> <xsd:documentation> initiate the import operation for this tsPartner. </xsd:documentation> </xsd:annotation> <xsd:simpleType> <xsd:restriction base="xsd:NMTOKEN"> <xsd:enumeration value="true"> <xsd:annotation> <xsd:appinfo> <intVal>1</intVal> </xsd:appinfo> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="false"> <xsd:annotation> <xsd:appinfo> <intVal>2</intVal> </xsd:appinfo> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleType> </xsd:element>

2 1

New libsmi Web Pages
by Kristine Adamson 12 Mar '03

12 Mar '03

Hi, I have been using the libsmi web site pages for a while now and appreciate all the detailed information that has been provided on the web site. I have been using the web site via MS Windows 2000 Netscape and had no problems. Since the change to the web site pages, I can't view the information well anymore. The frame(??) with the list of Home, Library, Tools, etc. takes up the whole window and I have to scroll far to the right to see the actual text. I realize fewer people are using Netscape these days but if anyone knows how to fix this, I would appreciate the information. So then I switched to using MS Windows 2000 IE. Most of the pages look fine with IE but when I select any of the _man_ pages I have to scroll to the right to view all the text. This is much less convenient that it used to be when the full text was displayed within the window without having to scroll. Is there a way to correct this in IE? I tried changing the text size to "smallest" but I still have to scroll to the right to view all the text. We usually use the online documentation instead of printing pages from the web site. That way we ensure we have the latest information on a function. While we appreciate that the web site is well maintained, the recent changes make it more cumbersome to use the online documentation. Thanks, Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com

3 2

SmiType handling
by Pete Flugstad 12 Mar '03

12 Mar '03

I'm having some issues with the SmiType handling. Specifically, when is the name parameter NULL, and when isn't it? If I load rfc1907, and get the node for sysDescr then get the type for that node, the name field is NULL. If I then get the parent type, there I see that the name field has "DisplayString" in it. However, if I load a test mib I wrote, which imports DisplayString, and has a variable of syntax DisplayString, the type structure for that variable has DisplayString in the name (without having to look at the parent). I don't see what distinguishes these two cases? Why in one case do I have to go the parent type to find the DisplayString "name" while in the other case I don't? Both import DisplayString from SNMPv2-TC. Also, rfc1907 imports TimeStamp from SNMPv2-TC, but sysORLastChange has TimeStamp directly in the name field of it's type. Again, why is DisplayString part of the parent type, while TimeStamp is not? Can someone explain this seeming inconsistency? Thanks, Pete Flugstad

2 2

New libsmi Web Pages
by Frank Strauss 11 Mar '03

11 Mar '03

Hi! I've just updated the libsmi web site. This was done primarily to ease future web site maintenance (we replaced WML by system of XML/XSL stuff some months ago, so since then the libsmi pages were quite static). The content changed only in minor aspects: I've added a few words on the smilint mail service, on our efforts on mappings of MIBs to XML Schema definitions, and I felt the need to say thanks to all contributors I'm aware of. The outdated list of MIBs and MIB errors and patches has gone, since the lists provided by Bill Fenner (http://www.icir.org/fenner/mibs/) are better and well maintained. -frank PS: A colleague had problems with his MS Windows IE, that could not present some of the new pages. I don't care a lot, because I verified that it's valid HTML 4.01 and CSS, but if anyone has a good explaination and fix, I would appriciate any hints.

1 0

imported object not found
by Steve Bucknam 07 Mar '03

07 Mar '03

The following does not work: barMib Imports fooObject, from fooMib barObj OBJECT-TYPE ... ::= {fooObject 2} To make it work, I (re)defined 'fooObject' locally in barMib (by importing fooObject's parent). Steve

2 1

SmiNode's format field
by Randy Rizun 25 Feb '03

25 Feb '03

Is the the 'format' field of the SmiNode structure ever used in libsmi? ===== "Aurora Borealis? At this time of year? At this time of day? In this part of the country? Localized entirely within your kitchen?" __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/

3 4

esoteric error level
by Juergen Schoenwaelder 20 Feb '03

20 Feb '03

On the <mreview(a)ops.ietf.org> list, I suggested to add a new error level 7 for "esoteric notices". The idea is to change the default error to level 7 for those warnings which the IETF MIB review guidelines document considers to be not important or noise (such as namelength-32 or case-redefinitions). This means that MIB reviewers following the IETF guidelines can simply run `smilint -c /dev/null -l 6' to get the right amount of warnings produced. Frank, do you agree with this chance? Is there anyone against introducing level 7 as described above? Let me know quickly so that I can put this in place next week. /js -- Juergen Schoenwaelder <http://www.informatik.uni-osnabrueck.de/schoenw/>

3 5

RE: [libsmi] esoteric error level
by HOOD, Andy 20 Feb '03

20 Feb '03

> -----Original Message----- > From: Frank Strauss -- snip -- > Another idea that came to my mind, is to add a much more verbose > description to errors, since for errors like "index element `%s::%s' > of row `%s' should but cannot have a size restriction" I would wonder > if people get this error and do NOT ask what it means. :-) If you could persuade Cisco, HP, IBM, Intel, etc. to put range restrictions in MIBs I might stop suppressing that warning. Are some of the warnings not relevant to SMIv1 MIBs, or SMIv2 ones converted to SMIv2 by, say, smidump? While we're here, what is the correct way to do these (taken from INTELCORPORATIONBASEBOARD-MIB which is SMIv1): 1) DmiInteger64X ::= INTEGER (-18446744073709551615..18446744073709551615) ./INTELCORPORATIONBASEBOARD-MIB:20: {} number `-18446744073709551615' is out of SMIv1/SMIv2 signed number range Whether those values are sensible is irrelevant. They will not fit in 64 bits. 2) DmiComponentIndex ::= INTEGER eComponentid OBJECT-TYPE SYNTAX SComponentid ACCESS not-accessible STATUS mandatory DESCRIPTION "" INDEX {DmiComponentIndex} ::= {tComponentid 1} ./INTELCORPORATIONBASEBOARD-MIB:57: {bad-identifier-case} `DmiComponentIndex' sh ould start with a lower case letter The other way I've seen this done would use INTEGER instead of DmiComponentIndex as the index, and that causes most of the same errors. Regards, Andrew Hood A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable. -- Leslie Lamport, as quoted in CACM, June 1992

3 2

Newbie question: windows executable
by zelig bagir 09 Feb '03

09 Feb '03

Hi all, I want to use smidump under windows (2k) but do not have the capabilities to create an executable. Can someone advise me as to where I can get a windows executable of libsmi? Thanks, Z.B __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 1