Libsmi April 2003

libsmi@ibr.cs.tu-bs.de

8 participants
9 discussions

order of declaration of table objects....
by Vivekanandan V 30 Apr '03

30 Apr '03

Hi, In my mib, the declaration of objects in the <Table>Entry and in the below definition part are not in the same order. No warning is given by the libsmi tool. I just want to confirm, whether this is legally allowed or it shud not be done. TestEntry ::= SEQUENCE { Index1, Index2, object1 } Index2 OBJECT-TYPE . . ::= {TestEntry 2} Index1 OBJECT-TYPE . . ::= {TestEntry 1} Whether the declaration and definition parts need not have the objects in the same order??? 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

SMIv2 pretty print
by Andy Bierman 30 Apr '03

30 Apr '03

Hi, I haven't looked at the code yet, but... I wanted to check with the smidump authors about the feasibility of modifying the smidump source code to act as an SMIv2 pretty print tool. I realize the complexity of such a tool depends on how configurable it is. I don't need any user configuration. I noticed that smidump -f smiv2 will do some pretty printing, such as changing {foo 2} to { foo 2 }. I need this tool to format MIBs as they usually appear in RFCs: - preserve ASN.1 comments - one enum per line in INTEGER objects or TCs - one descriptor and type per line in SEQUENCEs - one descriptor per line in OBJECTS and OBJECT-GROUP clauses - uniform indentation and whitespace - smart reformat to deal with lines > 72 chars - many more details such as these? I would be willing to work on the code, but I wanted to check first with this group if this is possible or if anyone else has thought about such a tool. thanks, Andy

2 1

[Fwd: [libsmi] problem restricting TimeTicks - bad error message???]
by Pete Flugstad 30 Apr '03

30 Apr '03

I didn't see any response from this? In summary: A) is restricting TimeTicks like the below, legal SMIv2? testInteger OBJECT-TYPE SYNTAX TimeTicks (500..12000) B) even if it's not, the error message libsmi spits out when it sees this is totally wrong and misleading: the SPPI construct/keyword `MAX-ACCESS' may not be used in a MIB Pete Flugstad Icon Labs

3 3

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

Re: smidump -f smiv1 output
by Kristine Adamson 02 Apr '03

02 Apr '03

Frank/Juergen, Thanks for the explanation. We had been using a different program to convert our SMIv2 MIB module to SMIv1 prior to using smidump. This other program used to put the SMIv1 definition of the textual conventions inline in the SMIv1 output, so we expected libsmi to do the same. Thanks for clearing up our confusion, Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com

1 0

Re: [libsmi] Re: smidump -f smiv1 output
by Kristine Adamson 02 Apr '03

02 Apr '03

Hi! Frank Strauss writes: Frank>Such a change is not necessary. The SMIv1 output as it is produced now Frank>is valid and reflects more closely what the original SMIv2 defines. What was produced as output was the same definition as existed in the SMIv2 MIB module. Will a MIB browser that only understands SMIv1 know what an InetAddressType SYNTAX is? Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com

3 2

Re: smidump -f smiv1 output
by Kristine Adamson 02 Apr '03

02 Apr '03

Hi and thanks for the feedback. For example, we have the following SMIv2 MIB object: ibmMvsTcpListenerLocalAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address type of the ibmMvsTcpListenerLocalAddr object." ::= { ibmTcpipMvsTcpListenerEntry 2 } In the SMIv1 output from smidump, we thought this object would have been defined as: ibmMvsTcpListenerLocalAddrType OBJECT-TYPE SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) } ACCESS read-only STATUS mandatory DESCRIPTION "The IP address type of the ibmMvsTcpListenerLocalAddr object." ::= { ibmTcpipMvsTcpListenerEntry 2 } Thanks, Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com

2 1

smidump -f smiv1 output
by Kristine Adamson 02 Apr '03

02 Apr '03

Hello, We are trying to use the -f smiv1 option of smidump to create an SMIv1 version of an SMIv2 MIB module. In the SMIv1 output version, we expected that the SYNTAX of those MIB objects defined with textual conventions, would have been changed from the textual convention to the corresponding base SMIv1 syntax type. But none of the textual conventions were updated in the SMIv1 output version. Is our understanding correct of the -f smiv1 option on smidump? Thanks, Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com

2 1

(no subject)
by Steve Bucknam 01 Apr '03

01 Apr '03

Is there a reason why the folloing line is commented out for the indexes in the dump-xsd.c file? Now most infomation is missing, such as oid. fprintAnnotationElem( f, smiNode ); Steve

2 1

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 April 2003