Libsmi September 2001

libsmi@ibr.cs.tu-bs.de

7 participants
4 discussions

Default Values on Object Identifiers
by Alberto Olalla 19 Sep '01

19 Sep '01

Hi ! I am having a problem with smidump with producing xml. Default values in oid objects are not well produced: Input: -------- svConnLocalEndPt OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "The object identifier of the 1st attribute of the end point in the associated protocol specific end point table." DEFVAL { { 1 3 6 } } ::= { svConnEntry 2 } Output: ----------- <column name="svConnLocalEndPt" oid="1.3.6.1.4.1.351.1.101.1.3.1.2" status="current"> <syntax> <type module="" name="ObjectIdentifier"/> </syntax> <access>readwrite</access> <default>0.0</default> ??????????????????????? <description> The object identifier of the 1st attribute of the end point in the associated protocol specific end point table. </description> </column> However, this value is well produced with "smiv2" output format: svConnLocalEndPt OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The object identifier of the 1st attribute of the end point in the associated protocol specific end point table." DEFVAL { ccitt } OK ::= { svConnEntry 2 } Does anyone know how I could fix this problem? Thanks Alberto Olalla

3 2

[PATCH] some prototypes
by Harrie Hazewinkel 17 Sep '01

17 Sep '01

Hi all, I have attached a patch (tested for 0.2.17) that deals with proper function prototype definitions. I also discovered some error with 'smiExit' which had one time even an argument when used. (See patch) Cheers, Harrie

1 0

bug in libsmi-0.2.17
by Damian Gilmurray 16 Sep '01

16 Sep '01

Hi, The following code and MIB results in a SIGSEGV from libsmi if the IMPORTed MIBs are unavailable. The offending code is check.c:933 which attempts to dereference object->typePtr which is NULL. I don't know the code well enough to produce a sensible patch. Regards, Damian.

2 1

problem with mib parsing
by mayagarwal＠hss.hns.com 03 Sep '01

03 Sep '01

Hi! I have a problem parsing a mib that uses the UNITS definition for an object. eg. mem-avail OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current UNITS MB DESCRIPTION "Physical memory available" ::= { memory-usage 1 } This node is parsed fine if I remove the line "UNITS MB". Is there any way to make this work? The documentation for the tool generating this MIB says that it is ASN.1 compliant. Thanks and regards, Mayank. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

3 2

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 September 2001