- Libsmi - lists.ibr.cs.tu-bs.de

lwip
by Volker Goller 06 Nov '10

06 Nov '10

Hi, new to libsmi, asking propably an old question: Anyone working on lwip (Light Weight IP Stack) support for smidump? Mit freundlichen Grüßen, Best Regards, Cordialement, Volker Goller -- * mocom software GmbH & Co KG, Tel: +49-241-902238 * Jülicher Strasse 250 Fax: +49-241-902563 * D52070 Aachen, Germany info(a)mocom-software.de * www.mocom-software.de * * HRA 4221, Registergericht Aachen * Komplementär & Geschäftsführung: * Mocom Software Bet. u. Verw. GmbH, * HRB. 7024, Registergericht Aachen, * Geschäftsführer Volker Goller * Gerichtsstand: Aachen * USt. Id. : DE189 470 867 * * Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte * Informationen. Wenn Sie nicht der richtige Adressat sind oder diese * E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den * Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren, die * unbefugte Weitergabe oder Nutzung von Informationen aus dieser Mail * ist nicht gestattet. * * This e-mail may contain confidential and/or privileged information. * If you are not the intended recipient (or have received this e-mail * in error) please notify the sender immediately and destroy this e- * mail. Any unauthorized copying, disclosure, distribution or use of the * material in this e-mail is strictly forbidden. * * $Author: Volker $ * $Date: 2008-11-08 14:32:11 +0100 (Sa, 08 Nov 2008) $ * $Revision: 160 $ *

2 1

smilint from Windows XP
by Matt Jones 01 Oct '10

01 Oct '10

Hi All, I am a new libsmi user. I have downloaded the win32 binaries from ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/WIN32/libsmi-0.4.6.zip. I can get the smilint application to check my MIB modules, only when I have placed the smi directory in the C:\smi path. When I try to execute smilint from another directory, such as D:\usefulutils\smi then it fails to locate the other MIB's I am importing. This occurs even when I use a configuration file. I am using the example smi.conf I found in the source distribution of the library (which I modified to point to the correct paths and use semicolons instead of colons). Whatever I do, I can't seem to get smilint to find the additional MIB's when outside the C:\smi directory. I execute the following command which will fail: D:\usefulutils\smi\bin>smilint.exe -c smi.conf -l 3 BASIC-MIB.txt BASIC-MIB.txt:5: failed to locate MIB module `SNMPv2-TC' BASIC-MIB.txt:12: failed to locate MIB module `SNMPv2-SMI' I execute the same command from C:\smi and it works. C:\smi\bin>smilint.exe -c smi.conf -l 3 BASIC-MIB.txt The smi.conf file includes the following path reference: path ;D:\usefulutils\smi\mibs I am assuming I am going wrong somewhere with the smi.conf, but just don't know where. If I have the C:\smi directory intact when I execute the command "D:\usefulutils\smi\bin>smilint.exe -c smi.conf -l 3 BASIC-MIB.txt" it also works. Does anyone have any suggestions? Regards. Matt Jones.

1 0

smidump bug: MACROS lost?
by Claus Klein 04 Sep '10

04 Sep '10

Hi, what goes wrong with SNMPv2-CONF and SNMPv2-SMI MIBs? The mibs are the mibs installed with libsmi. Should thy be fixed or is it a bug at libsmi? I tested with version 0.4.8 and current head. claus-kleins-macbook-pro:mibs clausklein$ /usr/local/bin/smidump -f smiv2 -m -s -l 3 /usr/local/share/mibs/ietf/SNMPv2-{SMI,CONF} > /dev/ null /usr/local/share/mibs/ietf/SNMPv2-SMI:191: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:191: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:196: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:196: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:202: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:202: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:207: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:207: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:217: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' smidump: module `/usr/local/share/mibs/ietf/SNMPv2-SMI' contains errors, expect flawed output /usr/local/share/mibs/ietf/SNMPv2-CONF:4: [2] {import-failed} identifier `ObjectSyntax' cannot be imported from module `SNMPv2-SMI' smidump: module `/usr/local/share/mibs/ietf/SNMPv2-CONF' contains errors, expect flawed output smidump: aborting due to severe parsing errors smidump: use the -k option to force continuation claus-kleins-macbook-pro:mibs clausklein$ ########################################### I cannot fix the SNMPV2-SMI mib because it the range is OK: -- this wraps Counter32 ::= [APPLICATION 1] IMPLICIT INTEGER (0..4294967295) -- this doesn't wrap Gauge32 ::= [APPLICATION 2] IMPLICIT INTEGER (0..4294967295) -- an unsigned 32-bit quantity -- indistinguishable from Gauge32 Unsigned32 ::= [APPLICATION 2] IMPLICIT INTEGER (0..4294967295) -- hundredths of seconds since an epoch TimeTicks ::= [APPLICATION 3] IMPLICIT INTEGER (0..4294967295) ################################# When I fix this {import-failed} identifier `ObjectSyntax' cannot be imported from module `SNMPv2-SMI' the result is shown below: claus-kleins-macbook-pro:mibs clausklein$ /usr/local/bin/smidump -f smiv2 -m -s -l 8 ./SNMPv2-CONF | diff -uwB - ./SNMPv2-CONF /usr/local/share/mibs/ietf/SNMPv2-SMI:155: [5] {identifier-basetype- redefined} warning: definition of identifier `Integer32' which is already a SMI or SPPI basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:191: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:191: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:196: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:196: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:202: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:202: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:200: [5] {identifier-basetype- redefined} warning: definition of identifier `Unsigned32' which is already a SMI or SPPI basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:207: [2] {range-bounds} range limit exceeds underlying basetype /usr/local/share/mibs/ietf/SNMPv2-SMI:207: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:217: [2] {range-exchanged} range limits must be `lower-bound .. upper-bound' /usr/local/share/mibs/ietf/SNMPv2-SMI:350: [5] {node-implicit} warning: implicit node definition /usr/local/share/mibs/ietf/SNMPv2-SMI:37: [5] {type-without-format} warning: type `ExtUTCTime' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:155: [5] {type-without-format} warning: type `Integer32' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:184: [5] {type-without-format} warning: type `IpAddress' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:189: [5] {type-without-format} warning: type `Counter32' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:194: [5] {type-without-format} warning: type `Gauge32' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:200: [5] {type-without-format} warning: type `Unsigned32' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:205: [5] {type-without-format} warning: type `TimeTicks' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:210: [5] {type-without-format} warning: type `Opaque' has no format specification /usr/local/share/mibs/ietf/SNMPv2-SMI:215: [5] {type-without-format} warning: type `Counter64' has no format specification --- - 2010-09-03 21:52:59.000000000 +0200 +++ ./SNMPv2-CONF 2010-09-03 21:48:40.000000000 +0200 @@ -1,11 +1,319 @@ --- --- This SMIv2 module has been generated by smidump 0.4.8. Do not edit. --- - SNMPv2-CONF DEFINITIONS ::= BEGIN -IMPORTS - NotificationName, ObjectName +IMPORTS ObjectName, NotificationName +-- , ObjectSyntax FROM SNMPv2-SMI; -END -- end of module SNMPv2-CONF. +-- definitions for conformance groups + +OBJECT-GROUP MACRO ::= +BEGIN + TYPE NOTATION ::= + ObjectsPart + "STATUS" Status + "DESCRIPTION" Text + ReferPart + + VALUE NOTATION ::= + value(VALUE OBJECT IDENTIFIER) + + ObjectsPart ::= + "OBJECTS" "{" Objects "}" + Objects ::= + Object + | Objects "," Object + Object ::= + value(ObjectName) + + Status ::= + "current" + | "deprecated" + | "obsolete" + + ReferPart ::= + "REFERENCE" Text + | empty + + -- a character string as defined in [2] + Text ::= value(IA5String) +END + +-- more definitions for conformance groups + +NOTIFICATION-GROUP MACRO ::= +BEGIN + TYPE NOTATION ::= + NotificationsPart + "STATUS" Status + "DESCRIPTION" Text + ReferPart + + VALUE NOTATION ::= + value(VALUE OBJECT IDENTIFIER) + + NotificationsPart ::= + "NOTIFICATIONS" "{" Notifications "}" + Notifications ::= + Notification + | Notifications "," Notification + Notification ::= + value(NotificationName) + + Status ::= + "current" + | "deprecated" + | "obsolete" + + ReferPart ::= + "REFERENCE" Text + | empty + + -- a character string as defined in [2] + Text ::= value(IA5String) +END + +-- definitions for compliance statements + +MODULE-COMPLIANCE MACRO ::= +BEGIN + TYPE NOTATION ::= + "STATUS" Status + "DESCRIPTION" Text + ReferPart + ModulePart + + VALUE NOTATION ::= + value(VALUE OBJECT IDENTIFIER) + + Status ::= + "current" + | "deprecated" + | "obsolete" + + ReferPart ::= + "REFERENCE" Text + | empty + + ModulePart ::= + Modules + Modules ::= + Module + | Modules Module + Module ::= + -- name of module -- + "MODULE" ModuleName + MandatoryPart + CompliancePart + + ModuleName ::= + -- identifier must start with uppercase letter + identifier ModuleIdentifier + -- must not be empty unless contained + -- in MIB Module + | empty + ModuleIdentifier ::= + value(OBJECT IDENTIFIER) + | empty + + MandatoryPart ::= + "MANDATORY-GROUPS" "{" Groups "}" + | empty + + Groups ::= + Group + | Groups "," Group + Group ::= + value(OBJECT IDENTIFIER) + + CompliancePart ::= + Compliances + | empty + + Compliances ::= + Compliance + | Compliances Compliance + Compliance ::= + ComplianceGroup + | Object + + ComplianceGroup ::= + "GROUP" value(OBJECT IDENTIFIER) + "DESCRIPTION" Text + + Object ::= + "OBJECT" value(ObjectName) + SyntaxPart + WriteSyntaxPart + AccessPart + "DESCRIPTION" Text + + -- must be a refinement for object's SYNTAX clause + SyntaxPart ::= "SYNTAX" Syntax + | empty + + -- must be a refinement for object's SYNTAX clause + WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax + | empty + + Syntax ::= -- Must be one of the following: + -- a base type (or its refinement), + -- a textual convention (or its refinement), or + -- a BITS pseudo-type + type + | "BITS" "{" NamedBits "}" + + NamedBits ::= NamedBit + | NamedBits "," NamedBit + + NamedBit ::= identifier "(" number ")" -- number is nonnegative + + AccessPart ::= + "MIN-ACCESS" Access + | empty + Access ::= + "not-accessible" + | "accessible-for-notify" + | "read-only" + | "read-write" + | "read-create" + + -- a character string as defined in [2] + Text ::= value(IA5String) +END + +-- definitions for capabilities statements + +AGENT-CAPABILITIES MACRO ::= +BEGIN + TYPE NOTATION ::= + "PRODUCT-RELEASE" Text + "STATUS" Status + "DESCRIPTION" Text + ReferPart + ModulePart + + VALUE NOTATION ::= + value(VALUE OBJECT IDENTIFIER) + + Status ::= + "current" + | "obsolete" + + ReferPart ::= + "REFERENCE" Text + | empty + + ModulePart ::= + Modules + | empty + Modules ::= + Module + | Modules Module + Module ::= + -- name of module -- + "SUPPORTS" ModuleName + "INCLUDES" "{" Groups "}" + VariationPart + + ModuleName ::= + -- identifier must start with uppercase letter + identifier ModuleIdentifier + ModuleIdentifier ::= + value(OBJECT IDENTIFIER) + | empty + + Groups ::= + Group + | Groups "," Group + Group ::= + value(OBJECT IDENTIFIER) + + VariationPart ::= + Variations + | empty + Variations ::= + Variation + | Variations Variation + + Variation ::= + ObjectVariation + | NotificationVariation + + NotificationVariation ::= + "VARIATION" value(NotificationName) + AccessPart + "DESCRIPTION" Text + + ObjectVariation ::= + "VARIATION" value(ObjectName) + SyntaxPart + WriteSyntaxPart + AccessPart + CreationPart + DefValPart + "DESCRIPTION" Text + + -- must be a refinement for object's SYNTAX clause + SyntaxPart ::= "SYNTAX" Syntax + | empty + + WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax + | empty + + Syntax ::= -- Must be one of the following: + -- a base type (or its refinement), + -- a textual convention (or its refinement), or + -- a BITS pseudo-type + type + | "BITS" "{" NamedBits "}" + + NamedBits ::= NamedBit + | NamedBits "," NamedBit + + NamedBit ::= identifier "(" number ")" -- number is nonnegative + + AccessPart ::= + "ACCESS" Access + | empty + + Access ::= + "not-implemented" + -- only "not-implemented" for notifications + | "accessible-for-notify" + | "read-only" + | "read-write" + | "read-create" + -- following is for backward-compatibility only + | "write-only" + + CreationPart ::= + "CREATION-REQUIRES" "{" Cells "}" + | empty + Cells ::= + Cell + | Cells "," Cell + Cell ::= + value(ObjectName) + + DefValPart ::= "DEFVAL" "{" Defvalue "}" + | empty + + Defvalue ::= -- must be valid for the object's syntax + -- in this macro's SYNTAX clause, if present, + -- or if not, in object's OBJECT-TYPE macro + value(ObjectSyntax) + | "{" BitsValue "}" + + BitsValue ::= BitNames + | empty + + BitNames ::= BitName + | BitNames "," BitName + + BitName ::= identifier + + -- a character string as defined in [2] + Text ::= value(IA5String) +END + +END claus-kleins-macbook-pro:mibs clausklein$

2 1

[patch] for fix signed/unsigned problem at smidump
by Claus Klein 03 Sep '10

03 Sep '10

Hi, there is a problem with smidump to xml for octet strings with negative values. For example 0xd0 will be printed as 0xff. This patch fix it: Index: tools/dump-xml.c =================================================================== --- tools/dump-xml.c (Revision 28966) +++ tools/dump-xml.c (Arbeitskopie) @@ -244,7 +244,7 @@ } else { sprintf(s, "0x%*s", 2 * valuePtr->len, ""); for (i=0; i < valuePtr->len; i++) { - sprintf(ss, "%02x", valuePtr->value.ptr[i]); + sprintf(ss, "%02x", (unsigned char)(valuePtr- >value.ptr[i])); strncpy(&s[2+2*i], ss, 2); } } With regards, Claus Klein

2 1

validating mib implementation
by Joao Ferreira gmail 14 Jun '10

14 Jun '10

Hello all, I'm not sure if this could be considered off-topic. I'm sorry if it is... I've been using smilint to check my new MIB as I add content to it. But I'm now searching for some tool that actually allows me to validate SNMP agents that are supposed to implement that MIB... My question is: how do I make sure that a given device correctly implements my MIB ? how do I get warnings or errors saying that a given SNMP agent deviates more or less from the MIB definitions ? Thanks Joao

1 0

smidump -f svg and problem with wrong mixed scalar and table group?
by Claus Klein 21 Apr '10

21 Apr '10

Hi, If have worked with LLDP-MIB (IEEE) and saw, that some scalars are wrongly shown as members of a Table Entry? The same can be found with the IF-MIB (only the ifNumber is ok) and NOTIFICATION-LOG-MIB. Is this a bug or what is the reason for this strange grouping? I used smidump V0.4.8. Regards Claus

1 0

Building 0.4.8 on fresh install of Solaris 10 10/09
by Root, Paul 13 Apr '10

13 Apr '10

I'm trying to build libsmi-0.4.8 to use with wireshark 1.0.8 on Solaris 10 10/09 The machine is a fresh install, with packages from sunfreeware.com The library configures and builds without complaint, but when I run "gmake check", I get 7 failed tests. I'm trying to figure out what fails, but am not getting too far. If the failure is do to a compare of output, the only differences are trailing blank characters on a number test output files. I installed the libs, and moved on to build wireshark. Which builds fine. Try to run it however, and I get a core dump, when its trying to open ~/.wireshark/smi_paths. Has anybody gone through anything like this? Google searches have lead to nothing useful. Thanks, Paul. Paul Root Lead Internet Systems Eng Network Services This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

1 0

+Hi+
by Patty Ackermann 09 Apr '10

09 Apr '10

http://sites.google.com/site/asdf32rweft/oblk3c

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