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

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

"smiGetNodeType" on a node from type "DisplayString"
by Heiko.Eichberger＠RSBICK.rohde-schwarz.com 29 Jan '03

29 Jan '03

Hi, when I call "smiGetNodeType" on a node from type "DisplayString" (defined in RFC-1213 from OCTET STRING) the name in the SmiType structure is empty! Why isn't the name "DisplayString" set? Regards, Heiko

2 1

xsd format with imported BITS Textual Conventions error
by Steve Bucknam 28 Jan '03

28 Jan '03

First, sorry for the last post and it's attempted recall. Next, I have a file (test_tc.mi2 attaced) with a "BITS" TextualConvention declaration "LocationCategory". I also have an object "myGoodLocation" declared as being of type "LocationCategory". The resulting xsd file is correct. It contains the TC definition, the object definition and a new TC declaration "myGoodLocationBits". I also import the TC in a file (test.mi2) and declare an object "myBadLocation" declared as being of type "LocationCategory". The resulting xsd file is NOT correct. The file contains "myBadLocation" declared as being of type "myBadLocationCategoryBits". However, the declaration of the "myBadLocationCategoryBits" TC is not present. Steve

2 1

Recall: imported "Bits" syntax problem
by Steve Bucknam 27 Jan '03

27 Jan '03

Steve Bucknam would like to recall the message, "imported "Bits" syntax problem".

1 0

imported "Bits" syntax problem
by Steve Bucknam 27 Jan '03

27 Jan '03

I have one file with the following TextualConvention:

1 0

libsmi 0.4.1: specfile
by Jose Pedro Oliveira 18 Jan '03

18 Jan '03

Hi, I have just made a specfile for libsmi version 0.4.1. The specfile generates two binary RPMS * libsmi which contains the command line tools, the shared lib, the MIB files, and respective documentation * libsmi-devel which contains the static lib, the header file, and the respective man pages (section 3) Questions: * Is there already an active maintainer for a RedHat package? * Does anyone find it useful to have RPM packages? I don't mind posting the specfile. Regards, jpo -- José Pedro Oliveira mailto: jpo(a)di.uminho.pt * http://gsd.di.uminho.pt/~jpo Departamento de Informática, Universidade do Minho

2 1

smistrip - incorrectly matches MACROs within a comment
by Steve Bucknam 13 Jan '03

13 Jan '03

I modified smistrip to match the MACRO statement with more a explicit regexp so that it doesn't match a commented out MACRO statement. The line I changed the line from: / *MACRO *::=/ { to: /^[ \t]*[A-Za-z0-9-]* *MACRO *::=/ { Can this be added to CVS? Steve

2 1

smiquery problems
by Michael Katz 06 Jan '03

06 Jan '03

Hi. I am attempting to use the smiquery tool. I have dowloaded, and fully compiled libsmi-0.4.1. I am using Solaris 2.8 (sparc platform) and the compiler is gcc (version 2.95.2) I have experienced the folowing problems: problem 1: no output for the following command: # smiquery node DS1-MIB_rfc2495.mib::1.3.6.1.2.1.10.18 (DS1-MIB_rfc2495.mib is the standard RFC2495. I have attached it). problem 2: segmentation fault for the following input: # smiquery node HDSL2-SHDSL-LINE-MIB_rfc3276.mib::1.3.6.1.2.1.10.48 (HDSL2-SHDSL-LINE-MIB_rfc3276.mib is the standard RFC3276. I have attached it. I can also send the core if requested.). Perhaps someone can advise. <<mibs.tar.gz>> Thanks in advance, Michael Katz Orckit Communications Ltd. E-mail: michaelkz(a)orckit.com

2 1

walk from iso node - failing....
by Vivekanandan V 30 Dec '02

30 Dec '02

Hi, When Iam giving a walk on iso node, it is failing. I found that the Manager (both Scotty & MGSoft Mib Browser) are sending a request with OID 1.0. Because of this it's failing in the agent side. Questions: ======== 1. Whether we can give a walk from iso ??? 2. If we can do that, then whether the Manager sending the request OID as 1.0 is correct or wrong??? 3. Since there is no node 1.0 registered with our Agent, should we return Failure or fetch the next registered node (1.3) and return to the Manager. Please help me to sort this issue. Thanks & Regards, Vivekanandan.V *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************

2 1