[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

4473.0. "ASN encoding of MCC/SNMP message" by SCHOOL::ABIDI (It's a wild world) Mon Feb 01 1993 10:02

 Does MCC understand synonymous types ?
 For the two MIB definitions given below, will MCC generate exactly
 the same PDU to do a set of the object in the two cases ?

 reason I ask is that with the first definition, we get a type 67 in the 
 PDU; I would have expected type 2 for INTEGER.
    
    thank you,
           _Vasmi Abidi

 1.

    Timeout ::= INTEGER      -- a STP timer in units of 1/100 seconds

   dot1dStpBridgeHelloTime OBJECT-TYPE
       SYNTAX  Timeout (100..1000)
       ACCESS  read-write
       STATUS  mandatory
       DESCRIPTION
               "The value that all bridges use for HelloTime when
               this bridge is acting as the root.  The
               granularity of this timer is specified by
               802.1d/D9 to be 1 second.  An agent may return a
               badValue error if a set is attempted to a value
               which is not a whole number of seconds."
       REFERENCE
               "P802.1d/D9, July 14, 1989: Section 4.5.3.9"
       ::= { dot1dStp 13 }


 2. 

   dot1dStpBridgeHelloTime OBJECT-TYPE
       SYNTAX  INTEGER (100..1000)
       ACCESS  read-write
       STATUS  mandatory
       DESCRIPTION
               "The value that all bridges use for HelloTime when
               this bridge is acting as the root.  The
               granularity of this timer is specified by
               802.1d/D9 to be 1 second.  An agent may return a
               badValue error if a set is attempted to a value
               which is not a whole number of seconds."
       REFERENCE
               "P802.1d/D9, July 14, 1989: Section 4.5.3.9"
       ::= { dot1dStp 13 }

-------------------------------------------------------------------

    
T.RTitleUserPersonal
Name
DateLines
4473.1MOLAR::YAHEY::BOSEMon Feb 01 1993 16:2313
	Vasmi,

		DECmcc SNMP AM would generate exactly the same PDU for
	the two objects you mention. The ASN datatype in the PDU should
	be that for an INTEGER (ie 2).

		Define the logical mcc_tcpip_am_log to a value of 40 to 
	have the SNMP AM dump out the PDUs it is sending out. If you are
	seeing anything other than a datatype of 2 then you may have
	uncovered a bug.

	Rahul.