Libsmi March 2010

libsmi@ibr.cs.tu-bs.de

5 participants
4 discussions

libsmi/smidump 0.4.8 problem: SYSAPPL-MIB::sysApplPastRunMaxRows SYNTAX Upper Bound
by Jens Engel 18 Mar '11

18 Mar '11

smidump 0.4.8 (up to rev13631 and maybe never) have a problem with the following SMI construct: -- FROM libsmi distributed SYSAPPL-MIB: sysApplPastRunMaxRows OBJECT-TYPE SYNTAX Unsigned32 (0..'ffffffff'h) ... NOTE: 0xFFFFFFFF = 2^32-1 = 4 294 967 295 when you try to convert the provided MIB via: smidump --format=smiv2 SYSAPPL-MIB ... you get the following output for libsmi 0.4.7 and 0.4.8. NOTE: Upper syntax bound is wrong in both cases. === modified file 'IETF/mibs/SYSAPPL-MIB.mib' --- IETF/mibs/SYSAPPL-MIB.mib 2009-03-28 19:03:48 +0000 +++ IETF/mibs/SYSAPPL-MIB.mib 2009-05-04 16:57:29 +0000 @@ -1038,7 +1038,7 @@ ::= { sysApplElmtPastRunEntry 11 } sysApplPastRunMaxRows OBJECT-TYPE - SYNTAX Unsigned32 (0..1134880) -- smidump 0.4.7 output + SYNTAX Unsigned32 (0..1134864) -- smidump 0.4.8 rev13631 (post-release) NOTE: Output of SYNTAX upper bound varies. WEIRD: The conversion to format=python leads to the correct result. Without looking at the source code, I assume that the hex-string to integer conversion has a problem. Ciao, Jens Engel Jens Engel mailto:jens_engel@t-online.de mailto:jens.engel

2 1

"A scalar should have one instance sub-id this one has none"
by Oskar Svadkovskey 30 Mar '10

30 Mar '10

Hi I was referred to you from Wireshark. Wireshark does not parse our V2 traps. Recently I noticed that it does not parse Veritas Cluster traps either. The error I see is "A scalar should have one instance sub-id this one has none" Indeed if the varbind is suffixed with .0 or .whatever, then wireshark can parse the varbind correctly. I see that traps sent manually with snmptrap do have SNMPv2-MIB::sysUpTime.0 and SNMPv2-MIB::snmpTrapOID.0 If I add this .0 to our varbinds manually, everything is fine My question is if this failure to parse indeed comes from libsmi. I should notice that everything worked perfect with Ethereal that uses the previous version of libsmi. Thanks for your time NB ________________________________ DISCLAIMER: This e-mail message and its attachments contain information that may be privileged or confidential and is the property of Flash networks Ltd. This message is only intended for the person to whom it is addressed, therefore if you are not the intended recipient, please note that you are not authorized to read, print, retain, copy disseminate, distribute, or use this message or any part thereof. If you received this message in error, please notify the sender immediately and delete all copies of this message. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Flash Networks Ltd.

2 1

smilib: memory leaks?
by Raymond Mercier 24 Mar '10

24 Mar '10

Hi, I am using libsmi in a Win32 project. I have troubles to compile the last version of the SVN depot (but I can compile the last release package 0.4.8). When do you plan to officially release a new version of libsmi? Furthermore, I am suspecting memory leaks in the libsmi code. o smiInit() o Use of smi calls to load a MIB file and do my job o smiExit() There are still memory blocks not released probably allocated by smilib. I would like to add a module to smilib to track memory usages and dump memory blocks not released at the end. The main problem I see in the current code is that there is no central point to manage malloc(), free() and others. What do you think of it? o Should I create my own module for this purpose and uses it for my own usage and that's all? o Or do you think it could be a good idea to add such a module into the official branch of libsmi? Any feedback is welcome :-) Raymond

2 1

smilint - missed syntax error?
by Kristine Adamson 08 Mar '10

08 Mar '10

Hello! We have been using the smilint function of libsmi for a while to validate changes to our enterprise-specific MIB modules. A MIB browser recently raised a syntax error when processing one of our MIB modules. The error applied to this definition: ibmProd1Compliances OBJECT IDENTIFIER ::= { ibmProd1Conformance 1 } The MIB browser required all the parts of this definition to be on one line in the MIB module. But smilint did not flag this definition as a syntax error. Should MIB browsers be able to process this definition successfully? I have read "Understanding SNMP MIBs" by Perkins and McGinnis, and they seem to indicate that white space includes line terminators. Thanks for your time on this question, Kristine Adamson IBM z/OS Communications Server: TCP/IP Development Internet e-mail:adamson@us.ibm.com

3 3

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 March 2010