Peder> The problem (which I reported on this list in February 1998, at
Peder> which time the RFC was an Internet-draft) is in the parsing of
Peder> what tnm/snmp/tnmMibParser.c calls Node Lists, i.e. ASN.1
Peder> object identifiers that are sligthly more complex than usual:
Peder> atmTCMIB MODULE-IDENTITY .... ::= { mib-2 37 3 } and
Peder> atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
This is a know problem in the MIB parser. Work is underway on a new
MIB parser which will solve this problem. So I all I can do is send
you a work around which seems to work fine. Below is the patch for the
ATM-TC-MIB module.
Juergen
--- ATM-TC-MIB.orig Mon Feb 8 16:43:56 1999
+++ ATM-TC-MIB Mon Feb 8 16:41:13 1999
@@ -41,7 +41,7 @@
"This MIB Module provides Textual Conventions
and OBJECT-IDENTITY Objects to be used by
ATM systems."
- ::= { mib-2 37 3 } -- atmMIB 3 (see [3])
+ ::= { mib-2 atmMIB(37) 3 } -- atmMIB 3 (see [3])
-- The Textual Conventions defined below are organized
-- alphabetically
@@ -350,9 +350,13 @@
-- from RFC1695 and no longer appear in the revision of
-- RFC1695[3].
-atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
+-- atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
-- atmMIBObjects
-- See [3].
+
+atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1}
+atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {atmMIBObjects 1}
+
-- All other and new OBJECT IDENTITIES
-- are defined under the following subtree:
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.