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

Switching from CVS to Subversion
by Frank Strauß 29 Jul '04

29 Jul '04

Motivated by a note from Jürgen some weeks ago and by an article in a german computer magazine I have looked at Subversion and the quite comprehensive free documentation. I would like to switch the libsmi project from CVS to Subversion some time soon. Subversion has quite some real advantages compared to CVS (that I don't want to enumerate here). One thing is that it allows to access the repository via HTTP/DAV and HTTPS/DAV (besides others). The problem that occured most often when people wanted to have access to the libsmi source code were very strict firewalls (on the client side) that disallowed to access our CVS server. If you have any concerns (or if you would like to see libsmi being managed with Subversion), please let me know.

3 7

Help Needed in resolving errors
by Balasubramanian Pitchandi 27 Jul '04

27 Jul '04

Hello List, I get the following errors when I compile the attached MIB. Would anyone explain me what the severity 1 errors are? Thanks, Bala smilint -m -s -l 6 -i namelength-32 mailbody mailbody:155: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:156: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:509: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:515: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:799: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:808: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:848: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:868: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:1265: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT mailbody:1266: [5] {} warning: flushing recent incorrect declaration, see previous error(s) mailbody:200: [1] {} unknown object identifier label `medGwyConfiguration' mailbody:525: [1] {} unknown object identifier label `medGwyGatewayControllerTable' mailbody:517: [2] {parent-row} row's parent node must be a table node mailbody:818: [1] {} unknown object identifier label `medGwyTermIdTable' mailbody:810: [2] {parent-row} row's parent node must be a table node mailbody:878: [1] {} unknown object identifier label `medGwyTerminationsTable' mailbody:870: [2] {parent-row} row's parent node must be a table node mailbody:1176: [3] {notification-object-access} object `medGwyTerminationId' of notification `medGwyInvalidTerminationId' must not be `not-accessible' mailbody:1211: [3] {notification-object-access} object `medGwyGatewayId' of notification `medGwyGatewayHandoff' must not be `not-accessible' mailbody:1211: [3] {notification-object-access} object `medGwyGatewayControllerId' of notification `medGwyGatewayHandoff' must not be `not-accessible' mailbody:1223: [3] {notification-object-access} object `medGwyTerminationId' of notification `medGwyProtocolError' must not be `not-accessible' mailbody:1304: [1] {} unknown object identifier label `medGwyCompliances' mailbody:456: [4] {group-membership} warning: node `medGwyGatewayRowStatus' must be contained in at least one conformance group mailbody:901: [4] {group-membership} warning: node `medGwyTerminationName' must be contained in at least one conformance group mailbody:911: [4] {group-membership} warning: node `medGwyTerminationAdminStatus' must be contained in at least one conformance group mailbody:936: [4] {group-membership} warning: node `medGwyTerminationOperStatus' must be contained in at least one conformance group mailbody:960: [4] {group-membership} warning: node `medGwyTerminationInterfaceIdentifier' must be contained in at least one conformance group mailbody:971: [4] {group-membership} warning: node `medGwyTerminationPropertyProfileId' must be contained in at least one conformance group mailbody:982: [4] {group-membership} warning: node `medGwyTerminationRowStatus' must be contained in at least one conformance group mailbody:1074: [4] {group-membership} warning: node `medGwyPropertyProfileProperty' must be contained in at least one conformance group mailbody:1084: [4] {group-membership} warning: node `medGwyTermPropertyProfileStatus' must be contained in at least one conformance group mailbody:1145: [4] {group-membership} warning: node `medGwyReceivedElement' must be contained in at least one conformance group mailbody:85: [5] {type-without-format} warning: type `MediaGatewayId' has no format specification mailbody:92: [5] {type-without-format} warning: type `MediaGatewayLinkId' has no format specification mailbody:99: [5] {type-without-format} warning: type `MediaGatewayTermId' has no format specification

2 1

Custom MIBs
by James Dabbs 27 Jun '04

27 Jun '04

I'm looking through libsmi man pages, but I have 2 very fundamental go/no-go questions that could probably be easily addressed here. 1. Can libsmi be used to look at agents with custom MIBs? 2. If so, how are these MIBs 'compiled' into the application code? Thanks.

2 1

Using smidump
by Volker Goebbels 09 Jun '04

09 Jun '04

Hello, although I'm very new to this list I have a question ... ;) I'm trying to dump a MIB file in xml format using smidump. When doing this I get some error outpur like this: QUANTE-MIB-V1.txt:135: macro `OBJECT-TYPE' has not been imported from module `RFC-1212' QUANTE-MIB-V1.txt:143: macro `OBJECT-TYPE' has not been imported from module `RFC-1212' ... QUANTE-MIB-V1.txt:366: macro `TRAP-TYPE' has not been imported from module `RFC-1215' QUANTE-MIB-V1.txt:367: syntax error, unexpected '{', expecting UPPERCASE_IDENTIFIER or LOWERCASE_IDENTIFIER or NUMBER QUANTE-MIB-V1.txt:368: syntax error, unexpected VARIABLES QUANTE-MIB-V1.txt:369: syntax error, unexpected DESCRIPTION QUANTE-MIB-V1.txt:375: syntax error, unexpected VARIABLES ... and so on. Does anyone know what's going on there? BTW: I'm using libsmi-0.4.2. Best regards and thanks in advance, Volker Göbbels -- Arachnion GmbH & Co. KG Dr. Volker Göbbels Business Communication vmg(a)arachnion.de Sandkaulbach 4 Tel. +49 (0) 241-55911-06 52062 Aachen Fax +49 (0) 241-55911-07

4 3

libsmi thread safe?
by Les Smithson 20 May '04

20 May '04

Are the smiGet* functions thread safe? By inspection, it looks like they are. Does anyone know any different? Thanks.

1 0

Conceptual Model
by Pablo Gestido (INCO) 04 May '04

04 May '04

Hi everyone: I am new to the list and I have a question about smidump. I saw you can "export" a conceptual model of a MIB in dia format. Is it posible to import this conceptual model from Rational Rose ? Has anyone done this ? Thanks in advance Pablo

2 1

Documentation Error
by Fredrick Paul Eisele 30 Mar '04

30 Mar '04

In the man page for "smi_node"... "The smiGetFirstElement() and smiGetNextElement() functions are used to iteratively retrieve struct SmiElements that represent elements of index clauses or notification object lists, groups of object types or notification types, and mandatory groups of module compliance statements. The node to which the list belongs has to be specified by smiNodePtr. To retrieve the node that is represented by a struct SmiElement, the smiGetOptionNode() function has to be called." I believe that should be "smiGetElementNode()" rather than "smiGetOptionNode()".

2 1

smi.xsd import
by Steve Bucknam 29 Mar '04

29 Mar '04

I am running smidump on "RFC1213-MIB" as follows: smidump.exe --xsd-container --xsd-schema-url="http://localhost:8080/snmp-gw/xsd" -f xsd -o RFC1213-MIB.xsd RFC1213-MIB The result is the following XML: <xsd:schema targetNamespace="http://localhost:8080/snmp-gw/xsd/RFC1213-MIB" xmlns="http://localhost:8080/snmp-gw/xsd/RFC1213-MIB" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:smi="http://localhost:8080/snmp-gw/xsd/smi" xmlns:RFC1155-SMI="http://localhost:8080/snmp-gw/xsd/RFC1155-SMI" xmlns:SNMPv2-TC="http://localhost:8080/snmp-gw/xsd/SNMPv2-TC" xmlns:RFC-1212="http://localhost:8080/snmp-gw/xsd/RFC-1212" xml:lang="en" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xsd:import namespace="http://www.ibr.cs.tu-bs.de/projects/libsmi/xsd/smi" schemaLocation="http://www.ibr.cs.tu-bs.de/projects/libsmi/xsd/smi.xsd"/ > <xsd:import namespace="http://localhost:8080/snmp-gw/xsd/RFC1155-SMI" schemaLocation="http://localhost:8080/snmp-gw/xs d/RFC1155-SMI.xsd"/> <xsd:import namespace="http://localhost:8080/snmp-gw/xsd/SNMPv2-TC" schemaLocation="http://localhost:8080/snmp-gw/xsd/ SNMPv2-TC.xsd"/> <xsd:import namespace="http://localhost:8080/snmp-gw/xsd/RFC-1212" schemaLocation="http://localhost:8080/snmp-gw/xsd/R FC-1212.xsd"/> ... Note the the namespace generated for smi ("http://localhost:8080/snmp-gw/xsd/smi") does not match the import ("http://www.ibr.cs.tu-bs.de/projects/libsmi/xsd/smi.xsd"). The import statement seems to be hardcoded in dump-xsd.c, but the xmlns is uses the specified commandline url prefix. Am I missing something? I am trying to use the snmp-xml gateway code and it is choking on this import. When I manually change the xmlns to reference www.ibr.cs.tu-bs.de, everything works fine. Steve

2 1

RE: [libsmi] SOAP <-> SNMP
by Steve Bucknam 25 Mar '04

25 Mar '04

I realized my carelessness after sending my previous message. I know that the SNMP/XML gateway has nothing to do with lynx. I would like information in obtaining a copy of the gateway or any other code that might help translate a soap call to an SNMP call. Steve -----Original Message----- From: libsmi-admin(a)ibr.cs.tu-bs.de [mailto:libsmi-admin@ibr.cs.tu-bs.de] On Behalf Of Steve Bucknam Sent: Tuesday, March 23, 2004 2:16 PM To: libsmi(a)ibr.cs.tu-bs.de Subject: [libsmi] SOAP <-> SNMP I am looking to write a servlet to receive SOAP requests and proxy them as SNMP requests. I noticed the lynx gateway on the libsmi site and wanted to get more information. I am currently generating Java web applications using the libsmi-generated XSD files, if that helps. Can I get more information about lynx or any other application that may exist. I could possibly use a C or C++ program as well. Thanks, Steve -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de> !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.

2 1

Recall: SOAP <-> SNMP
by Steve Bucknam 23 Mar '04

23 Mar '04

Steve Bucknam would like to recall the message, "SOAP <-> SNMP".

1 0