rfc3276.txt

RFC 的详细文档！

Network Working Group                                             B. Ray
Request for Comments: 3276                        PESA Switching Systems
Category: Standards Track                                        R. Abbi
                                                                 Alcatel
                                                                May 2002


 Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation
         (HDSL2) and Single-Pair High-Speed Digital Subscriber
                           Line (SHDSL) Lines

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 (2002).  All Rights Reserved.

Abstract

   This document defines a portion of the Management Information Base
   (MIB) module for use with network management protocols in the
   Internet community.  In particular, it describes objects used for
   managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair
   High-Speed Digital Subscriber Line (SHDSL) interfaces.

Table of Contents

   1.   Introduction .............................................  2
   2.   The SNMP Network Management Framework ....................  2
   3.   Introduction .............................................  3
   3.1  Relationship of the HDSL2/SHDSL Line MIB to other MIBs ...  3
   3.2  IANA Considerations ......................................  5
   4.   Conventions used in the MIB ..............................  5
   4.1  Naming Conventions .......................................  5
   4.2  Textual Conventions ......................................  6
   4.3  Structure ................................................  7
   4.4  Counters, Interval Buckets and Thresholds ................ 10
   4.5  Profiles ................................................. 11
   4.6  Notifications ............................................ 12
   5.   Conformance and Compliance ............................... 14
   6.   Definitions .............................................. 14
   7.   Security Considerations .................................. 60



Ray & Abbi                  Standards Track                     [Page 1]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   8.   Acknowledgments .......................................... 62
   9.   References ............................................... 63
   10.  Intellectual Property Notice ............................. 65
   11.  Authors' Addresses ....................................... 65
   12.  Full Copyright Statement ................................. 66

1. Introduction

   This document defines a portion of the Management Information Base
   (MIB) module for use with network management protocols in the
   Internet community.  In particular, it describes objects used for
   managing High Bit-Rate DSL - 2nd generation (HDSL2) [18] and Single-
   Pair High-Speed Digital Subscriber Line (SHDSL) interfaces [19].

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [1].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and is described in
      STD 16, RFC 1155 [2], STD 16, RFC 1212 [3], and RFC 1215 [4].  The
      second version, called SMIv2, is described in STD 58, RFC 2578
      [5], RFC 2579 [6], and RFC 2580 [7].

   o  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1 and is
      described in STD 15, RFC 1157 [8].  A second version of the SNMP
      message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described is in RFC 1901 [9] and
      RFC 1906 [10].  The third version of the message protocol is
      called SNMPv3 and is described in RFC 1906 [10], RFC 2572 [11],
      and RFC 2574 [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 2573 [14] and
      the view-based access control mechanism described in RFC 2575
      [15].





Ray & Abbi                  Standards Track                     [Page 2]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [16].

   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.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [17].

3.  Introduction

   This document describes an SNMP MIB for managing HDSL2/SHDSL Lines.
   These definitions are based upon the specifications for the HDSL2 and
   SHDSL Embedded Operations Channel (EOC) as defined in ANSI
   T1E1.4/2000-006 [18] and ITU G.991.2 [19].

   The MIB is located in the MIB tree under MIB 2 transmission, as
   discussed in the MIB-2 Integration (RFC 1213 [20] and RFC 2863 [21])
   section of this document.

3.1.  Relationship of the HDSL2/SHDSL Line MIB to other MIBs

   This section outlines the relationship of this MIB with other MIBs
   described in RFCs.  Specifically, IF-MIB as presented in RFC 2863
   [21] is discussed.

3.1.1  General IF-MIB Integration (RFC 2863)

   The HDSL2/SHDSL Line MIB specifies the detailed attributes of a data
   interface.  As such, it needs to integrate with RFC 2863 [21].  The
   IANA has assigned the following ifTypes to HDSL2 and SHDSL:








Ray & Abbi                  Standards Track                     [Page 3]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   IANAifType ::= TEXTUAL-CONVENTION
       ...
   SYNTAX INTEGER {
       ...
       hdsl2 (168), -- High Bit-Rate DSL, 2nd generation
       shdsl (169), -- Multirate HDSL2
       ...
       }

   Note that the ifFixedLengthGroup from RFC 2863 [21] MUST be supported
   and that the ifRcvAddressGroup does not apply to this MIB.

3.1.2  Usage of ifTable

   The MIB branch identified by this ifType contains tables appropriate
   for this interface type.  Most such tables extend the ifEntry table,
   and are indexed by ifIndex.  For interfaces in systems implementing
   this MIB, those table entries indexed by ifIndex MUST be persistent.

   The following attributes are part of the mandatory ifGeneral group in
   RFC 2863 [21], and are not duplicated in the HDSL2/SHDSL Line MIB.






























Ray & Abbi                  Standards Track                     [Page 4]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   ===================================================================
       ifIndex                  Interface index.

       ifDescr                  See interfaces MIB [21].

       ifType                   hdsl2(168) or shdsl(169).

       ifSpeed                  Set as appropriate.
                                (This is fixed at 1552000 for HDSL2
                                lines)

       ifPhysAddress            This object MUST have an octet string
                                with zero length.

       ifAdminStatus            See interfaces MIB [21].

       ifOperStatus             See interfaces MIB [21].

       ifLastChange             See interfaces MIB [21].

       ifName                   See interfaces MIB [21].

       ifLinkUpDownTrapEnable   Default to enabled(1).

       ifHighSpeed              Set as appropriate.
                                (For HDSL2 lines, this is fixed at 2)

       ifConnectorPresent       Set as appropriate.

   ===================================================================
                   Figure 1: Use of ifTable Objects

3.2 IANA Considerations

   The HDSL2-SHDSL-LINE-MIB module requires the allocation of a single
   object identifier for its MODULE-IDENTITY.  The IANA has allocated
   this object identifier in the transmission subtree (48), defined in
   the SNMPv2-SMI MIB module.

4.  Conventions used in the MIB

4.1.  Naming Conventions

   A.  xtuC refers to a central site terminal unit;
       H2TU-C for HDSL2, or STU-C for SHDSL.
   B.  xtuR refers to a remote site terminal unit;
       H2TU-R for HDSL2, or STU-R for SHDSL.
   C.  xtu refers to a terminal unit; either an xtuC or xtuR.



Ray & Abbi                  Standards Track                     [Page 5]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   D.  xru refer to a regenerator unit;
       H2RU for HDSL2, or SRU for SHDSL.
   E.  xU refers to any HDSL2/SHDSL unit; either an xtu or xru.
   F.  CRC is cyclic redundancy check [19].
   G.  ES means errored second [19].
   H.  LOSW means loss of sync word [19].
   I.  LOSWS means LOSW seconds [19].
   J.  SES means severely errored second [19].
   K.  SNR means signal-to-noise ratio [19].
   L.  UAS means unavailable second [19].

4.2.  Textual Conventions

   The following textual conventions are defined to reflect the line
   topology in the MIB (further discussed in the following section) and
   to define the behavior of the statistics to be maintained by an
   agent.

   o   Hdsl2ShdslUnitId:

   Attributes with this syntax uniquely identify each unit in a
   HDSL2/SHDSL span.  It mirrors the EOC addressing mechanism:

   xtuC(1)                - CO terminal unit
   xtuR(2)                - CPE terminal unit
   xru1(3) .. xru8(10)    - regenerators, numbered from
                             central office side
   o   Hdsl2ShdslUnitSide:

   Attributes with this syntax reference the two sides of a unit:

   networkSide(1)   - N in figure 2, below
   customerSide(2)  - C in figure 2, below

   o   Hdsl2ShdslWirePair:

   Attributes with this syntax reference the wire-pairs connecting the
   units:

   wirePair1(1)   - First pair for HDSL2/SHDSL.

   wirePair2(2)   - Optional second pair for SHDSL only.

   o   Hdsl2ShdslTransmissionModeType:

   Attributes with this syntax specify the regional setting for a SHDSL
   line.  Specified as a BITS construct, the two mode types are:




Ray & Abbi                  Standards Track                     [Page 6]

RFC 3276                  HDSL2-SHDSL-LINE MIB                  May 2002


   region1   - ITU-T G.991.2 Annex A
   region2   - ITU-T G.991.2 Annex B

   o   Hdsl2ShdslPerfCurrDayCount:

   Attributes with this syntax define the behavior of the 1-day (24
   hour) gauges found in the MIB.

   o   Hdsl2Shdsl1DayIntervalCount:

   Attributes with this syntax define the behavior of the 1-day (24
   hour) interval counters found in the MIB.

   o   Hdsl2ShdslPerfTimeElapsed:

   Attributes with this syntax define the behavior of the elapsed time
   counters found in the MIB.

   o   Hdsl2ShdslPerfIntervalThreshold:

   Attributes with this syntax define the behavior of the alarm
   thresholds found in the MIB.

   o   Hdsl2ShdslClockReferenceType

   Attributes with this syntax define the clock references for the
   HDSL2/SHDSL span.

4.3.  Structure