RFC 2495 (rfc2495) - Page 3 of 75

Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types

RFC 2495                   DS1/E1/DS2/E2 MIB                January 1999


        called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and
        RFC 2274 [12].

    o   Protocol operations for accessing management information. The
        first set of protocol operations and associated PDU formats is
        described in STD 15, RFC 1157 [8]. A second set of protocol
        operations and associated PDU formats is described in RFC 1905
        [13].

    o   A set of fundamental applications described in RFC 2273 [14] and
        the view-based access control mechanism described in RFC 2275
        [15].  Managed objects are accessed via a virtual information
        store, termed the Management Information Base or MIB.  Objects
        in the MIB are defined using the mechanisms defined in the SMI.
        This memo specifies a MIB module that is compliant to the SMIv2.
        A MIB conforming to the SMIv1 can be produced through the
        appropriate translations. The resulting translated MIB must be
        semantically equivalent, except where objects or events are
        omitted because no translation is possible (use of Counter64).
        Some machine readable information in SMIv2 will be converted
        into textual descriptions in SMIv1 during the translation
        process. However, this loss of machine readable information is
        not considered to change the semantics of the MIB.

1.1.  Changes from RFC 1406

   The changes from RFC 1406 are the following:

        (1)  The Fractional Table has been deprecated.

        (2)  This document uses SMIv2.

        (3)  Usage is given for ifTable and ifXTable.

        (4)  Example usage of ifStackTable is included.

        (5)  dsx1IfIndex has been deprecated.

        (6)  Support for DS2 and E2 have been added.

        (7)  Additional lineTypes for DS2, E2, and unframed E1
             were added.

        (8)  The definition of valid intervals has been clarified
             for the case where the agent proxied for other devices.  In
             particular, the treatment of missing intervals has been
             clarified.




Fowler, Ed.                 Standards Track