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

Full OIDs
by Samer Vazdekis 28 Jan '09

28 Jan '09

Hi all, When I retrieve a node, with smiGetNode (), I get the suboid. Is there a way to get the full oid?. I'm trying to get the OID from a node name. Thanks. _________________________________________________________________ The new Windows Live Messenger. You don’t want to miss this. http://www.microsoft.com/windows/windowslive/messenger.aspx

2 1

smi.h : smiGetClass
by Miroslav Beranič ml. 19 Jan '09

19 Jan '09

Hi, I have checked out latest source code from SVN (revision 12468) The problem is still present in: smi.h:553 function extern SmiClass *smiGetClass(SmiModule *smiModulePtr,char *class); I am no expert in C++, but as I looked at the SVN history files: smi.c smi.h.in were updated (rev. 12455), but not smi.h. When I compile and install, the resulting smi.h has the same defect. So: I am doing something wrong, or ... I had to manually update smi.h file, to make it work. Best regards, Miroslav Beranič ml. ------------------------------------------------ miroslav.beranic(a)gmail.com http://www.mibesis.eu +386 40 814 843 (SiMobil.si)

2 3

long long
by Arndt Jonasson 12 Jan '09

12 Jan '09

In dump-xsd.c is the code case SMI_BASETYPE_UNSIGNED64: { SmiUnsigned64 min, max; min = SMI_BASETYPE_UNSIGNED64_MIN; max = SMI_BASETYPE_UNSIGNED64_MAX; fprintStdRestHead( f, smiType ); smiRange = smiGetFirstRange( smiType ); while( smiRange ) { if( smiRange->minValue.value.unsigned64 < min ) { min = smiRange->minValue.value.unsigned64; } if( smiRange->maxValue.value.unsigned64 > max ) { max = smiRange->maxValue.value.unsigned64; } smiRange = smiGetNextRange( smiRange ); } fprintSegment( f, 0, "<xsd:minInclusive value=\"%lu\"/>\n", (unsigned long)min ); fprintSegment( f, 0, "<xsd:maxInclusive value=\"%lu\"/>\n", (unsigned long)max ); fprintSegment(f, -1, "</xsd:restriction>\n"); break; } The behaviour may vary on different platforms, but at least on some, the cast (unsigned long) above needs to be (unsigned long long), or perhaps removed, otherwise only the least significant 32 bits of the constant will be used. I'm not certain whether %lu ought to be %llu.

2 1

Multiple DEFINITIONs MIB parse
by Miroslav Beranič ml. 11 Jan '09

11 Jan '09

Hi, is it possible to parse MIB file that contains multiple DEFINITIONs (SMIv1, SMIv2, SMIng) statements? Currently smiLoadModule(char* mibFile) returns name of last DEFINITION (it seems that way) in MIB file. When calling smiGetFirstNode(modile, ANY) method returns NULL. IS MIB with multiple DEFITION statements valid MIB? Any pointer? Best regards, Miroslav Beranič ml. ----------------------------------- miroslav.beranic(a)gmail.com

2 8

Corrupted node when parsing MIB with { mib-2 XXX } for MODULE-IDENTITY
by Bill Fenner 06 Jan '09

06 Jan '09

Hi, When running smidump on http://mibbinator.org/mibindex/extracted/BGP4V2-MIB-idr-08.txt and outputting in python format, the node after bgp4V2Groups has ASCII text instead of a Node data structure, causing smiGetNextNode() to crash. 1613 nodePtr = nodePtr->nextPtr; $30 = (Node *) 0x57c600 (gdb) x/s $30 0x57c600: "}, # node\n" This is the last line that was output, I think because this Node was freed and so smiVasprintf is using the same memory area for line buffering, but there were still pointers to it. I will admit to running with "-k", to ignore the "mib-2 XXX" error in this MIB; this works with -f identifiers but seems to be the killer for -f python/perl/yang. When the { mib-2 XXX } is replaced by { mib-2 9999 }, the python/ perl/yang outputs succeed. In my use case (getting python access to the structure of a MIB in an Internet Draft), I need the output to work in this case. This worked some time ago (unfortunately I didn't practice good revision control and don't know exactly which version broke this; I developed the functionality that required this behavior in mid-2007). Any ideas where to look to find out what is freeing this node? (I tried --enable-dmalloc but the dmalloc linkage didn't work) Thanks, Bill

2 6

libsmi "internal-other" error reported.
by Tony Hicks 11 Dec '08

11 Dec '08

I am compiling my MIB at level 6 using the URL: http://www.ibr.cs.tu-bs.de/bin/smitools.cgi Compilation gives the following error message: mibs/ORCHESTRIA-NBA-MIB.mib:69: [1] {internal-other} syntax error, unexpected UPPERCASE_IDENTIFIER, expecting FROM or ',' Additional descriptions of some error/warning messages: Error: internal-other (level 1) Message: %s Description: An unspecified error occured. Please submit a detailed bug report to the libsmi maintainer or the libsmi mailing list at The error synopsis is correct, the fault is due to a missing ',' in an IMPORT statement: IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Counter32 FROM SNMPv2-SMI OBJECT-GROUP, NOTIFICATION-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF TEXTUAL-CONVENTION, DisplayString, RowStatus, VariablePointer FROM SNMPv2-TC orchComponentNBA, orchComponentNBAExp, orchConformanceNBA OrchEventSeverityTC, OrchEventControlTC, OrchEventRateTC, orchEventSequenceNo, orchEventSeverity, orchEventInformation FROM ORCHESTRIA-MIB; Adding the comma after 'orchConformanceNBA' fixes the problem and no errors or warnings are then reported: The processing did not reveal any errors or warnings. Tony Hicks Senior Software Engineer Orchestria Information Protection and Control Click here <http://www.orchestria.com/dlp/DLP_Requirements_Roadmap2wtl.asp> to learn the 8 essential requirements for Data Loss Prevention Click here <http://www.orchestria.com/dlp/Classifying_Records_2adwtl.asp> to discover the best practices for classifying and controlling corporate records +44 1823 424063 (Direct) tony.hicks(a)orchestria.com <mailto:tony.hicks@orchestria.com> www.orchestria.com <http://www.orchestria.com>

1 0

Invalid use of 2nd arg to setAttributeList() in lib/parser-sming.y from 0.4.8
by Albert Chin 30 Nov '08

30 Nov '08

In lib/parser-sming.y from 0.4.8: bitsOrEnumerationSpec { List *p; $$ = duplicateTypeToAttribute(smiHandle->typeBitsPtr, classPtr, thisParserPtr); setAttributeParentType($$, smiHandle->typeBitsPtr); if ($1) { setAttributeList($$, $1); for (p = $1; p; p = p->nextPtr) ((NamedNumber *)(p->ptr))->typePtr = (Type*)$$; } bitsFlag = 0; /* reset flag */ } } In lib/parser-sming.c, this expands to: typedef union YYSTYPE { char *id; /* identifier name */ int rc; /* >=0: ok, <0: error */ ... } ... { List *p; (yyval.attributePtr) = duplicateTypeToAttribute(smiHandle->typeBitsPtr, classPtr, thisParserPtr); setAttributeParentType((yyval.attributePtr), smiHandle->typeBitsPtr); if ((yyvsp[(1) - (3)].rc)) { setAttributeList((yyval.attributePtr), (yyvsp[(1) - (3)].rc)); for (p = (yyvsp[(1) - (3)].rc); p; p = p->nextPtr) ((NamedNumber *)(p->ptr))->typePtr = (Type*)(yyval.attributePtr); } bitsFlag = 0; /* reset flag */ ;} break; yyvsp is of type YYVSP so (yyvsp[(1) - (3)].rc) is of type int. But, the prototype of setAttributeList() according to data.h is: extern void setAttributeList(Attribute *attributePtr, List *listPtr); So, how is the above code expected to work? -- albert chin (china(a)thewrittenword.com)

1 0

Correct way to handle import error
by Vincent Bernat 29 Nov '08

29 Nov '08

Hi! When importing a MIB requesting another MIB and when this later MIB is not available, the first MIB is imported but nodes information are then incomplete. For example, they contain empty OID or even random OID. Is there a way to forbid the import of MIB when OID information would be incomplete? Thanks. -- BOFH excuse #142: new guy cross-connected phone lines with ac power bus.

1 0

libsmi numeric constraints convertion bug
by Ilya Etingof 24 Nov '08

24 Nov '08

I've run into a possible problem in SVN version of libsmi. I have not done any debugging, so this is just a bug report: When I do: smidump -f python TCP-MIB.txt for the following MIB text: tcpMaxConn OBJECT-TYPE SYNTAX Integer32 (-1 | 0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1." ::= { tcp 4 } smidump generates: "tcpMaxConn" : { "nodetype" : "scalar", "moduleName" : "TCP-MIB", "oid" : "1.3.6.1.2.1.6.4", "status" : "current", "syntax" : { "type" : { "basetype" : "Integer32", "ranges" : [ { "min" : "-1", "max" : "2147483647" }, ], "range" : { "min" : "4294967295", "max" : "2147483647" }, }, }, "access" : "readonly", "description" : """ [skipped] """, }, # scalar Where range constraints seem to be broken at: 1. Range minimum (0) gets converted into 4294967295. 2. Single value constraint (-1) gets translated into a value range constraint with wildly inflated upper range (2147483647). Current stable release (0.4.5) behaves differently (yet, incorrectly) in this respect: "tcpMaxConn" : { "nodetype" : "scalar", "moduleName" : "TCP-MIB", "oid" : "1.3.6.1.2.1.6.4", "status" : "current", "syntax" : { "type" : { "basetype" : "Integer32", "range" : { "min" : "-1", "max" : "2147483647" }, }, }, "access" : "readonly", "description" : """ [skipped] """, }, # scalar Is there currently a fix for this issue? Thanks, ilya

2 17

HOST-RESOURCES-MIB
by Delbert Martin 20 Nov '08

20 Nov '08

While, going through the XML version of this that I Downloaded from Simpleweb: http://www.simpleweb.org/ietf/mibs/modules/IETF/xmlv2/HOST-RESOURCES-MIB.xml This may be just an issue with my understanding of this rfc, but the Module Identifier / identity node is listed as hostResourcesMibModule is found in the Document as hrAdmininfo.1 which would make the OID of the Module Identifier be { 1.3.6.1.2.1.25.7.1 } when the Logical OID for the Module Identifier (for me at least) would be { 1.3.6.1.2.1.25 } thus giving you the Base OID of this module which all other OIDs in the module are sub-interfaces of. what am I doing wrong?

2 1