Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types
RFC 4805
| Document | Type |
RFC - Proposed Standard
(March 2007; No errata)
Obsoletes RFC 3895
Was draft-orly-atommib-rfc3895bis (individual in ops area)
|
|
|---|---|---|---|
| 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 4805 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Dan Romascanu | ||
| Send notices to | orly@radmail.rad.co.il | ||
Network Working Group O. Nicklass, Ed.
Request for Comments: 4805 RAD Data Communications, Ltd.
Obsoletes: 3895 March 2007
Category: Standards Track
Definitions of Managed Objects
for the DS1, J1, 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 IETF Trust (2007).
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, J1, 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 3895.
Nicklass, Ed. Standards Track [Page 1]
RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
Table of Contents
1. The Internet-Standard Management Framework ......................2
2. Conventions Used in This Document ...............................3
3. Overview ........................................................3
3.1. Use of ifTable for DS1 Layer ...............................4
3.2. Usage Guidelines ...........................................5
3.2.1. Usage of ifStackTable for Routers and DSUs ..........5
3.2.2. Usage of ifStackTable for DS1/J1/E1 on DS2/E2 .......7
3.2.3. Usage of Channelization for DS3, DS1, DS0 ...........8
3.2.4. Usage of Channelization for DS3, DS2, DS1 ...........9
3.2.5. Usage of Loopbacks .................................10
3.3. Objectives of This MIB Module .............................10
3.4. DS1 Terminology ...........................................11
3.4.1. Error Events .......................................11
3.4.2. Performance Defects ................................12
3.4.3. Performance Parameters .............................13
3.4.4. Failure States .....................................17
3.4.5. Other Terms ........................................20
4. Object Definitions .............................................20
5. Security Considerations ........................................83
6. Acknowledgments ................................................84
7. References .....................................................84
7.1. Normative References ......................................84
7.2. Informative References ....................................86
Appendix A - Use of dsx1IfIndex and dsx1LineIndex .................88
Appendix B - The Delay Approach to Unavailable Seconds ............90
Appendix C - Changes from Previous Versions .......................92
C.1. Changes from RFC 3895 .....................................92
C.2. Changes from RFC 2495 .....................................92
C.3. Changes from RFC 1406 .....................................92
C.4. Companion Documents .......................................93
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, Ed. Standards Track [Page 2]
RFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007
2. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text