Definitions of Managed Objects for the DS3/E3 Interface Type
RFC 1407

Document Type RFC - Proposed Standard (January 1993; No errata)
Obsoleted by RFC 2496
Obsoletes RFC 1233
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1407 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             T. Cox
Request for Comments: 1407                                     K. Tesink
Obsoletes: 1233                             Bell Communications Research
                                                                 Editors
                                                            January 1993

                     Definitions of Managed Objects
                     for the DS3/E3 Interface Type

Status of this Memo

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

Abstract

   This memo defines an extension to the Management Information Base
   (MIB) for use with network management protocols in TCP/IP-based
   internets.  In particular, it defines objects for managing DS3 and E3
   Interfaces.  This document is a companion document with Definitions
   of Managed Objects for the DS1 Interface Type.

   This document entirely replaces RFC 1233, which contains a
   fundamental error: many objects are encoded as Counters that must be
   encoded as INTEGERs or Gauges.  The magnitude of the change required
   is sufficient that virtually every object changed.  Therefore, the
   MIB documented in RFC 1233 should not be implemented.

Table of Contents

   1. The Network Management Framework ......................    2
   2. Objects ...............................................    2
   2.1 Format of Definitions ................................    3
   2.2 Changes from RFC 1233 ................................    3
   3. Overview ..............................................    5
   3.1 Binding between ifIndex and DS3/E3 Interfaces ........    5
   3.2 Objectives of this MIB Module ........................    7
   3.3 DS3/E3 Terminology ...................................    7
   3.3.1 Error Events .......................................    7
   3.3.2 Performance Parameters .............................    8
   3.3.3 Performance Defects ................................   10
   3.3.4 Other Terms ........................................   11
   4. Object Definitions ....................................   12
   4.1 The DS3/E3 Near End Group ............................   12

Trunk MIB Working Group                                         [Page 1]
RFC 1407                       DS3/E3 MIB                   January 1993

   4.1.1 The DS3/E3 Configuration ...........................   12
   4.1.2 The DS3/E3 Current .................................   18
   4.1.3 The DS3/E3 Interval ................................   21
   4.1.4 The DS3/E3 Total ...................................   25
   4.2 The DS3 Far End Group ................................   29
   4.2.1 The DS3 Far End Configuration ......................   29
   4.2.2 The DS3 Far End Current ............................   31
   4.2.3 The DS3 Far End Interval ...........................   34
   4.2.4 The DS3 Far End Total ..............................   36
   4.3 The DS3/E3 Fractional Group ..........................   38
   5. Acknowledgments .......................................   41
   6. References ............................................   41
   7. Security Considerations ...............................   43
   8. Authors' Addresses ....................................   43

1.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

      STD 16/RFC 1155 which defines the SMI, the mechanisms used for
      describing and naming objects for the purpose of management.  STD
      16/RFC 1212 defines a more concise description mechanism, which is
      wholly consistent with the SMI.

      RFC 1156 which defines MIB-I, the core set of managed objects for
      the Internet suite of protocols.  STD 17/RFC 1213, defines MIB-II,
      an evolution of MIB-I based on implementation experience and new
      operational requirements.

      STD 15/RFC 1157 which defines the SNMP, the protocol used for
      network access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.  Objects

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
   defined in the SMI.  In particular, each object has a name, a syntax,
   and an encoding.  The name is an object identifier, an
   administratively assigned name, which specifies an object type.  The
   object type together with an object instance serves to uniquely
   identify a specific instantiation of the object.  For human
   convenience, we often use a textual string, termed the OBJECT
Show full document text