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

smilint bug for AGENT-CAPABILITIES
by Andy Bierman 29 Apr '03

29 Apr '03

Hi, I am getting the following error message for a valid AGENT-CAPABILITIES file, related to a DEFVAL clause: ./CISCO-CAS-IF-CAPABILITY.my.1.0:74: [2] default value syntax does not match object syntax snippet from source file: VARIATION ccasVoiceCfgNonLinearProcEnable DEFVAL { true } DESCRIPTION "The initial value is 'true'." The object is defined in the CISCO-CAS-IF-MIB as SYNTAX TruthValue. program version: smilint 0.4.1 Andy

2 2

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

RE: [libsmi] IMPLIED keyword for indices in xsd output
by Steve Bucknam 06 Feb '03

06 Feb '03

I checked out todays source. It appears that scalars from the SNMPv2-MIB no longer contain much of the appinfo attributes: <xsd:element name="sysName" minOccurs="0"> <xsd:simpleType> <xsd:annotation> <xsd:appinfo> <displayHint>255a</displayHint> </xsd:appinfo> </xsd:annotation> <xsd:restriction base="xsd:string"> <xsd:pattern value="((((\p{IsBasicLatin})){0,255})){0,1}"/> <xsd:minLength value="0"/> <xsd:maxLength value="255"/> </xsd:restriction> </xsd:simpleType> </xsd:element> The following fields are missing: oid, status, maxAccess Steve -----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Tuesday, February 04, 2003 10:51 AM To: Torsten Klie Cc: Gerry Buteau; libsmi(a)ibr.cs.tu-bs.de Subject: Re: [libsmi] IMPLIED keyword for indices in xsd output Hi! Torsten> OK. Furthermore, I have moved some appinfos. The appinfos for Torsten> rows do not belong to the <complexType> definition anymore. Torsten> They are now part of the <element> declaration. Great. I've just updated the anonymous CVS repository accordingly. -frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de> !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.

2 1

IMPLIED keyword for indices in xsd output
by Gerry Buteau 04 Feb '03

04 Feb '03

Hello all, In the following example mib, it seems as though the parser is ignoring the "IMPLIED" keyword. I can not find any reference to it in the .xsd output. Any thoughts? Thanks, Gerry tradiusSvrAuthClientEntry OBJECT-TYPE SYNTAX TradiusSvrAuthClientEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing the information of a server in a a different realm to which this server proxy forwards authentication requests." INDEX { IMPLIED tradiusSvrAuthClientName } ::= { tradiusSvrAuthClientTable 1 } TradiusSvrAuthClientEntry ::= SEQUENCE { tradiusSvrAuthClientName DisplayString, tradiusSvrAuthClientRowStatus RowStatus, tradiusSvrAuthClientOperState TradiusRowOperState, } tradiusSvrAuthClientName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS not-accessible STATUS current DESCRIPTION "The DNS name or IP address of the client" ::= { tradiusSvrAuthClientEntry 1 }

3 5