Libsmi July 2003

libsmi@ibr.cs.tu-bs.de

2 participants
3 discussions

Problem solved!
by Garth R Conrad 02 Jul '03

02 Jul '03

I figured out the problem that was causing my SNMP-COMMUNITY-MIB to not get loaded via a load statement in my .smirc file. The previous load statement was telling libsmi to load a module that contained a couple of syntax errors, which was probably putting libsmi into a messed up state. When I fixed the syntax errors in the previous MIB module, the problem went away, and now the SNMP-COMMUNITY-MIB is being properly loaded. Thanks, Garth Conrad garthc(a)us.ibm.com

1 0

Strange behavior when loading a module
by Garth R Conrad 02 Jul '03

02 Jul '03

Hi, I'm seeing some unexpected behavior in libsmi 0.4.1. I'm using a .smirc config file that contains one "level" statement, one "path" statement, then a big section of about 45 or 50 "load" statements. One of the load statements is: load SNMP-COMMUNITY-MIB I do have a file by that name in the search path, and I've verified that its syntax is OK by using smilint. Now when I run the following code: smiInit(); /* some code omitted here */ node = smiGetNode(NULL,"snmpCommunityMIB"); then node is NULL, i.e. libsmi can't seem to find the node named snmpCommunityMIB even though it's defined in my SNMP-COMMUNITY-MIB. In fact, libsmi can't find any of the nodes defined in SNMP-COMMUNITY-MIB. BUT... if I comment out all of the other load statements from my .smirc file except the one that loads SNMP-COMMUNITY-MIB, then when my code runs, libsmi seems to be able to find the node snmpCommunityMIB, because the variable "node" is not NULL. In fact, libsmi is able to find all of the nodes defined in SNMP-COMMUNITY-MIB. Is this a libsmi bug? If not, any ideas what could be causing it and how I can fix it? I need to load all of my MIB modules, so it's not acceptable for me to leave the other load statements commented out. Thanks, Garth Conrad garthc(a)us.ibm.com

1 0

XSD min & max length
by Steve Bucknam 02 Jul '03

02 Jul '03

The following definition: DateAndTime ::= TEXTUAL-CONVENTION DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d" STATUS current DESCRIPTION "A date-time specification. For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present." SYNTAX OCTET STRING (SIZE (8 | 11)) Gets converted to: <xsd:simpleType name="DateAndTime"> <xsd:annotation> <xsd:documentation> A date-time specification. For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. </xsd:documentation> <xsd:appinfo> <displayHint>2d-1d-1d,1d:1d:1d.1d,1a1d:1d</displayHint> </xsd:appinfo> </xsd:annotation> <xsd:restriction base="xsd:string"> <xsd:pattern value="((0|[1-9](([0-9]){0,4}))-(0|[1-9](([0-9]){0,2}))-(0|[1-9](([0-9]) {0,2})),(0|[1-9](([0-9]){0,2})):(0|[1-9](([0-9]){0,2})):(0|[1-9](([0-9]) {0,2})).(0|[1-9](([0-9]){0,2})))|((0|[1-9](([0-9]){0,4}))-(0|[1-9](([0-9 ]){0,2}))-(0|[1-9](([0-9]){0,2})),(0|[1-9](([0-9]){0,2})):(0|[1-9](([0-9 ]){0,2})):(0|[1-9](([0-9]){0,2})).(0|[1-9](([0-9]){0,2})),((\p{IsBasicLa tin}){1})(0|[1-9](([0-9]){0,2})):((0|[1-9](([0-9]){0,2})))"/> <xsd:minLength value="8"/> <xsd:maxLength value="8"/> </xsd:restriction> </xsd:simpleType> The display hint shows the value is 11 chars long. The minLength and maxLength fields are both set to "8". There really should be two min and max length restrictions (8 and 11). What happens if there are more? 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 July 2003