[tkined] MIB loading question(s) for Scotty

Jeff Choate (jchoate@fore.com)
Thu, 6 Nov 1997 10:49:06 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_01A5_01BCEAA1.9AF82840
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I am relatively new to Scotty, so please forgive me if these are obvious =
questions!

I am running on Solaris with Scotty2.1.7. I am trying to load the =
ATM-TC-MIB into Scotty, and I am having a couple of problems that I hope =
this group may be able to help me out with.

My first question concerns deprecated OBJECT-GROUP and OBJECT-IDENTITY =
objects. Deprecated OBJECT-TYPE objects are read and parsed correctly, =
but when a deprecated OBJECT-GROUP or OBJECT-IDENTITY object is read, =
Scotty gives back the error message:
105 --> deprecated
atm2TC05.mib:169 bad format in OBJECT-GROUP

Is this because of an SNMP rule that OBJECT-GROUP objects may not be =
deprecated or something like that?

My next question concerns reading in the indexes in MIB definitions. In =
the ATM-TC-MIB, the mib identity is specified as:
atmTCMIB MODULE-IDENTITY
LAST-UPDATED "9610220200Z"
ORGANIZATION "IETF AToMMIB Working Group"
CONTACT-INFO " Michael Noto"
::=3D { mib-2 37 3 }

also, within the mib, an object identity is created as follows:
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=3D {mib-2 37 1 1}

the problem is when I try to read this mib in, the definition for =
atmTrafficDescriptorTypes is never assigned. I try to do the "mib oid" =
command on it, but it is not seen. I got the mib oid on the atmTCMIB =
and got the following for the oid:

% mib oid atmTCMIB
1.3.6.1.2.1.37
% mib oid atmTrafficDescriptorTypes
no object "atmTrafficDescriptorTypes"

There are 2 things that I noticed here:
1) the atmTrafficDescriptorTypes isn't seen, but more importantly,=20
2) Only the mib-2 37 index is printed (and perhaps parsed) by Scotty? =
I am theorizing that Scotty is only reading in the parent and then a =
single index for the node, in this case for the MIB identifier. When =
it parses the next object with a compound identity, it is already =
allocated to another object and so is skipped. =20

I tested this by changing the index to something different for the =
atmTrafficDescriptorTypes object. I changed it to have an index =
definition of:
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=3D {mib-2 39 1 1}

When I repeated the test, I got predicted results:
% mib oid atmTCMIB
1.3.6.1.2.1.37
% mib oid atmTrafficDescriptorTypes
1.3.6.1.2.1.39

So it worked that time - still only reading the parent and one index =
though; so it didn't really work.

Do you have any thoughts on this? Does Scotty only read in a parent and =
then a single index? =20

Thanks for any feedback on either of these questions!

-Jeff

***************************************************
* Jeff Choate Phone: (508) 689-2400 x165 *
* FORE Systems Inc. FAX: (508) 689-2446 *
* One Corporate Center *
* Andover, MA 01810 email: jchoate@fore.com *
***************************************************

------=_NextPart_000_01A5_01BCEAA1.9AF82840
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

Hello,
 
I am relatively new to Scotty, so please forgive me = if these=20 are obvious questions!
 
I am running on Solaris with Scotty2.1.7.  I am = trying to=20 load the ATM-TC-MIB into Scotty, and I am having a couple of problems = that I=20 hope this group may be able to help me out with.
 
My first question concerns deprecated OBJECT-GROUP = and=20 OBJECT-IDENTITY objects.  Deprecated OBJECT-TYPE objects are read = and=20 parsed correctly, but when a deprecated OBJECT-GROUP or OBJECT-IDENTITY = object=20 is read, Scotty gives back the error message:
105 --> deprecated 
atm2TC05.mib:169 bad format in = OBJECT-GROUP 
 
Is this because of an SNMP rule that OBJECT-GROUP = objects may=20 not be deprecated or something like that?
 
My next question concerns reading in the indexes in = MIB=20 definitions.  In the ATM-TC-MIB, the mib identity is specified=20 as:
atmTCMIB=20 MODULE-IDENTITY
         = LAST-UPDATED=20 "9610220200Z"
       &nbs= p;=20 ORGANIZATION "IETF AToMMIB Working=20 Group"
         = CONTACT-INFO=20 "          Michael=20 Noto"
    ::=3D { mib-2 37 3 } 

 
also, within the mib, an object identity is created as = follows:
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=3D {mib-2 37 1=20 1}
 
the problem is when I try to read = this mib in,=20 the definition for atmTrafficDescriptorTypes is never assigned.  I = try to=20 do the "mib oid" command on it, but it is not seen.  I = got=20 the  mib oid on the atmTCMIB and got the following for the=20 oid:
 
% mib oid atmTCMIB
1.3.6.1.2.1.37
% mib oid=20 atmTrafficDescriptorTypes
no object=20 "atmTrafficDescriptorTypes"
 
 
There are 2 things that I noticed=20 here:
1) the = atmTrafficDescriptorTypes isn't=20 seen, but more importantly,  
2) Only the mib-2 37 index is printed  (and perhaps parsed) by = Scotty?  I am theorizing that Scotty is only reading in the parent = and then=20 a single index for  the node, in this case for the MIB = identifier. =20 When it parses the next object with a compound identity, it is  = already=20 allocated to another object and so is skipped. 
 
I tested this by changing the index to something different for the=20 atmTrafficDescriptorTypes object.  I changed it to have an index = definition=20 of:
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=3D {mib-2 39 1=20 1}
 
When I repeated the test, I got predicted results:
% mib oid atmTCMIB
1.3.6.1.2.1.37
% mib oid=20 atmTrafficDescriptorTypes
1.3.6.1.2.1.39

So it worked that = time -=20 still only reading the parent and one index though; so it didn't really=20 work.

Do you have any thoughts on this?  Does Scotty only = read in a=20 parent and then a single index?   
 
Thanks for any feedback on either of = these=20 questions!
 
-Jeff
 
***************************************************
*  = Jeff=20 Choate        Phone: (508) 689-2400=20 x165  *
*  FORE Systems Inc.   FAX:   = (508)=20 689-2446      *
*  One Corporate=20 Center           &= nbsp;           &n= bsp;  =20 *
*  Andover, MA 01810   email: jchoate@fore.com   =20 *
***************************************************  ------=_NextPart_000_01A5_01BCEAA1.9AF82840-- -- !! 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 . !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.