RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991    dot3StatsInRangeLengthErrors OBJECT-TYPE        SYNTAX  Counter        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "A count of frames received on a particular                interface with a length field value that falls                between the minimum unpadded LLC data size and the                maximum allowed LLC data size inclusive and that                does not match the number of LLC data octets                received.                The count represented by an instance of this                object also includes frames for which the length                field value is less than the minimum unpadded LLC                data size."        ::= { dot3StatsEntry 14 }    dot3StatsOutOfRangeLengthFields OBJECT-TYPE        SYNTAX  Counter        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "A count of frames received on a particular                interface for which the length field value exceeds                the maximum allowed LLC data size.                The count represented by an instance of this                object is not incremented in implementations that                observe Ethernet encapsulation conventions (by                which the IEEE 802.3 length field is interpreted                as the Ethernet Type field)."        ::= { dot3StatsEntry 15 }    dot3StatsInternalMacReceiveErrors OBJECT-TYPE        SYNTAX  Counter        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "A count of frames for which reception on a                particular interface fails due to an internal MAC                sublayer receive error. A frame is only counted by                an instance of this object if it is not counted by                the corresponding instance of either the                dot3StatsFrameTooLongs object, the                dot3StatsAlignmentErrors object, the                dot3StatsFCSErrors object, the                dot3StatsInRangeLengthErrors object, or theTransmission MIB Working Group                                 [Page 15]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991                dot3StatsOutOfRangeLengthFields object.                The precise meaning of the count represented by an                instance of this object is implementation-                specific.  In particular, an instance of this                object may represent a count of receive errors on                a particular interface that are not otherwise                counted."        ::= { dot3StatsEntry 16 }    -- the Ethernet-like Collision Statistics group    -- Implementation of this group is optional; it is appropriate    -- for all systems which have the necessary metering    dot3CollTable OBJECT-TYPE        SYNTAX  SEQUENCE OF Dot3CollEntry        ACCESS  not-accessible        STATUS  mandatory        DESCRIPTION                "A collection of collision histograms for a                particular set of interfaces."        ::= { dot3 5 }    dot3CollEntry OBJECT-TYPE        SYNTAX  Dot3CollEntry        ACCESS  not-accessible        STATUS  mandatory        DESCRIPTION                "A cell in the histogram of per-frame collisions                for a particular interface.  An instance of this                object represents the frequency of individual MAC                frames for which the transmission (successful or                otherwise) on a particular interface is                accompanied by a particular number of media                collisions."        INDEX   { dot3CollIndex, dot3CollCount }        ::= { dot3CollTable 1 }    Dot3CollEntry ::=        SEQUENCE {            dot3CollIndex                INTEGER,            dot3CollCount                INTEGER,            dot3CollFrequencies                CounterTransmission MIB Working Group                                 [Page 16]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991        }    dot3CollIndex OBJECT-TYPE        SYNTAX  INTEGER        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "The index value that uniquely identifies the                interface to which a particular collision                histogram cell pertains.  The interface identified                by a particular value of this index is the same                interface as identified by the same value of                ifIndex."        ::= { dot3CollEntry 1 }    dot3CollCount OBJECT-TYPE        SYNTAX  INTEGER (1..16)        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "The number of per-frame media collisions for                which a particular collision histogram cell                represents the frequency on a particular                interface."        ::= { dot3CollEntry 2 }    dot3CollFrequencies OBJECT-TYPE        SYNTAX  Counter        ACCESS  read-only        STATUS  mandatory        DESCRIPTION                "A count of individual MAC frames for which the                transmission (successful or otherwise) on a                particular interface is accompanied by a                particular number of media collisions."        ::= { dot3CollEntry 3 }    --  802.3 Tests    -- The ifExtnsTestTable defined in [11] provides a common means    -- for a manager to test any interface corresponding to a value    -- of ifIndex.    -- At this time, one well known test (testFullDuplexLoopBack) is    -- defined in [11].  For ethernet-like interfaces, this test    -- configures the MAC chip and executes an internal loopback    -- test of memory and the MAC chip logic.  This loopback test canTransmission MIB Working Group                                 [Page 17]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991    -- only be executed if the interface is offline.  Once the test    -- has completed, the MAC chip should be reinitialized for network    -- operation, but it should remain offline.    -- If an error occurs during a test, the object ifExtnsTestResult    -- (defined in [11]) will be set to failed(7).  The following two    -- OBJECT IDENTIFIERs may be used to provided more information as    -- values for the object ifExtnsTestCode in [11]:    dot3Errors             OBJECT IDENTIFIER ::= { dot3 7 }                              -- couldn't initialize MAC chip for test    dot3ErrorInitError     OBJECT IDENTIFIER ::= { dot3Errors 1 }                              -- expected data not received (or not                              -- received correctly) in loopback test    dot3ErrorLoopbackError OBJECT IDENTIFIER ::= { dot3Errors 2 }    --  TDR Test    -- Another test, specific to ethernet-like interfaces,    -- is Time-domain Reflectometry (TDR) which is defined    -- as follows:    dot3Tests   OBJECT IDENTIFIER ::= { dot3 6 }    dot3TestTdr OBJECT IDENTIFIER ::= { dot3Tests 1 }    -- A TDR test returns as its result the time interval between the    -- most recent TDR test transmission and the subsequent detection    -- of a collision.  This interval is based on a 10 MHz clock and    -- should be normalized if the time base is other than 10 MHz.    -- On successful completion of a TDR test, the result is stored    -- as the value of the appropriate instance of the MIB object    -- dot3TestTdrValue, and the OBJECT IDENTIFIER of that instance    -- is stored in the corresponding instance of ifExtnsTestResult    -- (thereby indicating where the result has been stored).   --  802.3 Hardware Chipsets   -- The object ifExtnsChipSet is provided in [11] to identify the   -- MAC hardware used to communcate on an interface.  The following   -- hardware chipsets are provided for 802.3:   dot3ChipSets          OBJECT IDENTIFIER ::= { dot3 8 }   dot3ChipSetAMD        OBJECT IDENTIFIER ::= { dot3ChipSets 1 }   dot3ChipSetAMD7990    OBJECT IDENTIFIER ::= { dot3ChipSetAMD 1 }Transmission MIB Working Group                                 [Page 18]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991   dot3ChipSetAMD79900   OBJECT IDENTIFIER ::= { dot3ChipSetAMD 2 }   dot3ChipSetIntel      OBJECT IDENTIFIER ::= { dot3ChipSets 2 }   dot3ChipSetIntel82586 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 1 }   dot3ChipSetIntel82596 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 2 }   dot3ChipSetSeeq       OBJECT IDENTIFIER ::= { dot3ChipSets 3 }   dot3ChipSetSeeq8003   OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 }   dot3ChipSetNational      OBJECT IDENTIFIER ::= { dot3ChipSets 4 }   dot3ChipSetNational8390  OBJECT IDENTIFIER ::=                                             { dot3ChipSetNational 1 }   dot3ChipSetNationalSonic OBJECT IDENTIFIER ::=                                             { dot3ChipSetNational 2 }   dot3ChipSetFujitsu       OBJECT IDENTIFIER ::= { dot3ChipSets 5 }   dot3ChipSetFujitsu86950  OBJECT IDENTIFIER ::=                                            { dot3ChipSetFujitsu 1 }   -- For those chipsets not represented above, OBJECT IDENTIFIER   -- assignment is required in other documentation, e.g., assignment   -- within that part of the registration tree delegated to   -- individual enterprises (see [3]).   END6.  Acknowledgements   This document was produced by the Transmission MIB Working Group.   This document is based on a document written by Frank Kastenholz of   Interlan entitled IEEE 802.3 Layer Management Draft M compatible MIB   for TCP/IP Networks [10].  This document has been modestly reworked,   initially by the SNMP Working Group, and then by the Transmission   Working Group, to reflect the current conventions for defining   objects for MIB interfaces.  James Davin, of the MIT Laboratory for   Computer Science, and Keith McCloghrie of Hughes LAN Systems,   contributed to later drafts of this memo. Marshall Rose of   Performance Systems International, Inc. converted the document into   its current concise format.  Thanks to Frank Kastenholz of Interlan   and Louis Steinberg of IBM for their experimentation.7.  References   [1] Cerf, V., "IAB Recommendations for the Development of Internet       Network Management Standards", RFC 1052, NRI, April 1988.   [2] Cerf, V., "Report of the Second Ad Hoc Network Management ReviewTransmission MIB Working Group                                 [Page 19]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991       Group", RFC 1109, NRI, August 1989.   [3] Rose M., and K. McCloghrie, "Structure and Identification of       Management Information for TCP/IP-based internets", RFC 1155,       Performance Systems International, Hughes LAN Systems, May 1990.   [4] McCloghrie K., and M. Rose, "Management Information Base for       Network Management of TCP/IP-based internets", RFC 1156, Hughes       LAN Systems, Performance Systems International, May 1990.   [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple       Network Management Protocol", RFC 1157, SNMP Research,       Performance Systems International, Performance Systems       International, MIT Laboratory for Computer Science, May 1990.   [6] McCloghrie K., and M. Rose, Editors, "Management Information Base       for Network Management of TCP/IP-based internets", RFC 1213,       Performance Systems International, March 1991.   [7] Information processing systems - Open Systems Interconnection -       Specification of Abstract Syntax Notation One (ASN.1),       International Organization for Standardization, International       Standard 8824, December 1987.   [8] Information processing systems - Open Systems Interconnection -       Specification of Basic Encoding Rules for Abstract Notation One       (ASN.1), International Organization for Standardization,       International Standard 8825, December 1987.   [9] IEEE, "IEEE 802.3 Layer Management", November 1988.  [10] Kastenholz, F., IEEE 802.3 Layer Management Draft compatible MIB       for TCP/IP Networks, electronic mail message to mib-       wg@nnsc.nsf.net,  9 June 1989.  [11] McCloghrie, K., Editor, "Extensions to the Generic-Interface       MIB", RFC 1229, Hughes LAN Systems, Inc., May 1991.  [12] IEEE, "Carrier Sense Multiple Access with Collision Detection       (CSMA/CD) Access Method and Physical Layer Specifications",       ANSI/IEEE Std 802.3-1985.  [13] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",       RFC 1212, Performance Systems International, Hughes LAN Systems,       March 1991.Transmission MIB Working Group                                 [Page 20]RFC 1284                 ETHERNET-LIKE OBJECTS             December 1991Security Considerations   Security issues are not discussed in this memo.Author's Address   John Cook   Chipcom Corporation   118 Turnpike Road   Southborough, MA  01772   For more information, contact the chair of the Ethernet MIB working   group:   Frank Kastenholz   Clearpoint Research Inc   35 Parkwood Drive   Hopkinton Mass 01748   Phone: 508-435-2000   EMail: kasten@europa.clearpoint.comTransmission MIB Working Group                                 [Page 21]