Libsmi May 2013

libsmi@ibr.cs.tu-bs.de

3 participants
3 discussions

crash on attempt to traverse mib nodes
by Jonathan Walker 06 Jun '13

06 Jun '13

Hello, I'm finding that libsmi crashes when I remove every "RFC" mib from "mibs/ietf" directory, and then execute a program which performs the following: 1. Add each directory under "mibs" to the smi path (smiSetPath). 2. Traverse each directory under "mibs", and for each mib found get the module and traverse each node in the module. It tends to crash at attempt to traverse nodes of a mib which uses IMPORTS of an RFC- prefixed mib. Though I understand how missing dependencies could cause problems loading/traversing a mib, I'm not sure I understand why it's crashing and no error logs are present. Thanks, Jonathan ________________________________ This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.

2 5

smidump --format=smiv2 output contains some errors in compliance SYNTAX/WRITE-SYNTAX clauses.
by Jens Engel 06 Jun '13

06 Jun '13

Hello, I just stumbled over the following problem in libsmi 0.4.8 and development trunk-tip rev34557 (as of today). The problem resides in the SYNTAX/WRITE-SYNTAX clauses in COMPLIANCE statements. Instead of a "type" the invalid term "(null)" is present. AFFECTED-MIBS (at least): - BRIDGE-MIB - SNMP-VIEW-BASED-ACM-MIB - ... => grep "(null)" *-MIB EXAMPLE: smidump --format=smiv2 BRIDGE-MIB ... OBJECT dot1dStpPriority SYNTAX (null) (0 | 4096 | 8192 | 12288 | 16384 | 20480 | 24576 | 28672 | 32768 | 36864 | 40960 | 45056 | 49152 | 53248 | 57344 | 61440) ... OBJECT dot1dStpPortPriority SYNTAX (null) (0 | 16 | 32 | 48 | 64 | 80 | 96 | 112 | 128 | 144 | 160 | 176 | 192 | 208 | 224 | 240) BUT: Original BRIDGE-MIB that is distributed w/ libsmi contains: OBJECT dot1dStpPriority SYNTAX Integer32 (0 | 4096 | 8192 | 12288 | 16384 | 20480 | 24576 | 28672 | 32768 | 36864 | 40960 | 45056 | 49152 | 53248 | 57344 | 61440) ... OBJECT dot1dStpPortPriority SYNTAX Integer32 (0 | 16 | 32 | 48 | 64 | 80 | 96 | 112 | 128 | 144 | 160 | 176 | 192 | 208 | 224 | 240) smidump --format=smiv2 SNMP-VIEW-BASED-ACM-MIB ... OBJECT vacmViewTreeFamilyMask WRITE-SYNTAX (null) (SIZE(0)) ... SHOULD-BE (as in original MIB distributed with libsmi): ... OBJECT vacmViewTreeFamilyMask WRITE-SYNTAX OCTET STRING (SIZE(0)) I assume that smidump does not have the info (only a NULL pointer) and just dumps it as textual info. NOTE: "smidiff <ORIGINAL-MIB> <SMIDUMPED-MIB>" does not seem to show a difference (except warnings, ...). Ciao, Jens

3 2

Segfault on quering type SNMPv2-TC::RowStatus
by Luiz Angelo Daros de Luca 28 May '13

28 May '13

Hello, This simple command: smiquery type SNMPv2-TC::RowStatus is crashing smiquery. $ smiquery --version smiquery 0.4.8 $ smiquery type SNMPv2-TC::RowStatus Type: SNMPv2-TC::RowStatus Basetype: Enumeration Parent Type: Enumeration Numbers: active(1) notInService(2) notReady(3) createAndGo(4) createAndWait(5) destroy(6) Declaration: TEXTUAL-CONVENTION Status: current Segmentation Fault Is this a known problem? Regards, --- Luiz Angelo Daros de Luca, Me. luizluca(a)gmail.com

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 May 2013