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

Document Type RFC - Proposed Standard (September 2004; No errata)
Obsoleted by RFC 4805
Obsoletes RFC 2495
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3895 (Proposed Standard)
Telechat date
Responsible AD Bert Wijnen
Send notices to <orly_n@rad.com>, <faye@pedestalnetworks.com>,<hklam@lucent.com>
Network Working Group                                   O. Nicklass, Ed.
Request for Comments: 3895                 RAD Data Communications, Ltd.
Obsoletes: 2495                                           September 2004
Category: Standards Track

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

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes objects used for managing DS1, E1, DS2
   and E2 interfaces.  This document is a companion to the documents
   that define Managed Objects for the DS0, DS3/E3 and Synchronous
   Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
   Types.  This document obsoletes RFC 2495.

Nicklass                    Standards Track                     [Page 1]
RFC 3895                   DS1/E1/DS2/E2 MIB              September 2004

Table of Contents

   1.  The Internet-Standard Management Framework . . . . . . . . . .  2
       1.1.  Changes from RFC 2495. . . . . . . . . . . . . . . . . .  3
       1.2.  Changes from RFC 1406. . . . . . . . . . . . . . . . . .  3
       1.3.  Companion Documents. . . . . . . . . . . . . . . . . . .  4
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
       2.1.  Use of ifTable for DS1 Layer . . . . . . . . . . . . . .  5
       2.2.  Usage Guidelines . . . . . . . . . . . . . . . . . . . .  6
             2.2.1. Usage of ifStackTable for Routers and DSUs. . . .  6
             2.2.2. Usage of ifStackTable for DS1/E1 on DS2/E2. . . .  8
             2.2.3. Usage of Channelization for DS3, DS1, DS0 . . . .  9
             2.2.4. Usage of Channelization for DS3, DS2, DS1 . . . . 10
             2.2.5. Usage of Loopbacks. . . . . . . . . . . . . . . . 11
       2.3.  Objectives of this MIB Module. . . . . . . . . . . . . . 11
       2.4.  DS1 Terminology. . . . . . . . . . . . . . . . . . . . . 12
             2.4.1. Error Events. . . . . . . . . . . . . . . . . . . 12
             2.4.2. Performance Defects . . . . . . . . . . . . . . . 13
             2.4.3. Performance Parameters. . . . . . . . . . . . . . 14
             2.4.4. Failure States. . . . . . . . . . . . . . . . . . 18
             2.4.5. Other Terms . . . . . . . . . . . . . . . . . . . 21
   3.  Object Definitions . . . . . . . . . . . . . . . . . . . . . . 21
   4.  Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 74
   5.  Security Considerations. . . . . . . . . . . . . . . . . . . . 74
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 76
       6.1.  Normative References . . . . . . . . . . . . . . . . . . 76
       6.2.  Informative References . . . . . . . . . . . . . . . . . 78
   Appendix A - Use of dsx1IfIndex and dsx1LineIndex. . . . . . . . . 79
   Appendix B - The delay approach to Unavailable Seconds . . . . . . 81
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 83
   Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 84

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

Nicklass                    Standards Track                     [Page 2]
RFC 3895                   DS1/E1/DS2/E2 MIB              September 2004

1.1.  Changes from RFC 2495

   The changes from [RFC2495] are the following:

   (1)  The dsx1FracIfIndex SYNTAX matches the description range.

   (2)  A value was added to dsx1TransmitClockSource.

   (3)  Values were added to dsx1LineType.

   (4)  Two objects were added, dsx1LineMode and dsx1LineBuildOut to
Show full document text