rfc2558.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

Network Working Group                                       K. Tesink
Request for Comments: 2558                     Telcordia Technologies
Obsoletes: 1595                                            March 1999
Category: Standards Track


                     Definitions of Managed Objects
                    for the SONET/SDH Interface Type

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

1.  Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing Synchronous Optical
   Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces.  This
   document is a companion to the documents that define Managed Objects
   for the DS1/E1/DS2/E2 and DS3/E3 Interface Types [24][25].

   Textual Conventions used in this MIB are defined in [6] and [36].

   This memo replaces RFC 1595 [30]. Changes relative to RFC 1595 are
   summarized in the MIB module's REVISION clause.

Table of Contents

   1 Abstract ..............................................    1
   2 The SNMP Network Management Framework .................    2
   3 Overview ..............................................    3
   3.1 Use of the ifTable ..................................    4
   3.2 Use of ifTable for  SONET/SDH  Medium/Section/Line
       Layer ...............................................    5
   3.3 Use of ifTable for SONET/SDH Paths ..................    6
   3.4 Use of ifTable for SONET/SDH VTs/VCs ................    7
   3.5 SONET/SDH Terminology ...............................    8
   4 Object Definitions ....................................   16
   4.1 The SONET/SDH Medium Group ..........................   19



Tesink                      Standards Track                     [Page 1]

RFC 2558                   SONET/SDH Objects                  March 1999


   4.2 The SONET/SDH Section Group .........................   23
   4.2.1 The SONET/SDH Section Current Group ...............   23
   4.2.2 The SONET/SDH Section Interval Group ..............   26
   4.3 The SONET/SDH Line Group ............................   28
   4.3.1 The SONET/SDH Line Current Group ..................   28
   4.3.2 The SONET/SDH Line Interval Group .................   30
   4.4 The SONET/SDH Far End Line Group ....................   32
   4.4.1 The SONET/SDH Far End Line Current Group ..........   33
   4.4.2 The SONET/SDH Far End Line Interval Group .........   34
   4.5 The SONET/SDH Path Group ............................   37
   4.5.1 The SONET/SDH Path Current Group ..................   37
   4.5.2 The SONET/SDH Path Interval Group .................   39
   4.6 The SONET/SDH Far End Path Group ....................   42
   4.6.1 The SONET/SDH Far End Path Current Group ..........   42
   4.6.2 The SONET/SDH Far End Path Interval Group .........   44
   4.7 The SONET/SDH Virtual Tributary Group ...............   46
   4.7.1 The SONET/SDH VT Current Group ....................   46
   4.7.2 The SONET/SDH VT Interval Group ...................   49
   4.8 The SONET/SDH Far End VT Group ......................   51
   4.8.1 The SONET/SDH Far End VT Current Group ............   51
   4.8.2 The SONET/SDH Far End VT Interval Group ...........   53
   4.9 Conformance Information .............................   55
   4.10 Compliance Statements ..............................   56
   5 Acknowledgments .......................................   65
   6 Security Considerations ...............................   65
   7 References ............................................   66
   8 Author's Address ......................................   69
   9 Intellectual Property .................................   69
   Appendix A ..............................................   70
   Appendix B ..............................................   72
   Full Copyright Statement ................................   74

2.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   0    An overall architecture, described in RFC 2271 [1].

   0    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 described in
        STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
        The second version, called SMIv2, is described in RFC 1902 [5],
        RFC 1903 [6] and RFC 1904 [7].






Tesink                      Standards Track                     [Page 2]

RFC 2558                   SONET/SDH Objects                  March 1999


   0    Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        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 in RFC 1901 [9] and
        RFC 1906 [10].  The third version of the message protocol is
        called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and
        RFC 2274 [12].

   0    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].

   0    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 (e.g., 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.

3.  Overview

   These objects are used when the particular media being used to
   realize an interface is a SONET/SDH interface.  At present, this
   applies to these values of the ifType variable in the Internet-
   standard MIB:

        sonet (39), sonetPath (50), sonetVT (51)

   The definitions contained herein are based on the SONET/SDH
   specifications in ANSI T1.105 and T1.106-1988 [19][20][21] and CCITT
   G.707, 708, 709, and G.783 [26][27][28][29].






Tesink                      Standards Track                     [Page 3]

RFC 2558                   SONET/SDH Objects                  March 1999


3.1.  Use of the ifTable

   This section specifies how the MIB II interfaces group, as defined in
   [23], is used for SONET/SDH interfaces.  The SONET/SDH layers support
   several multiplexing possibilities.

   For example in SONET, an Synchronous Transport Signal 3 (STS-3) has 3
   SONET Paths, and a STS-3c has 1 SONET Path. Another example could be
   a STS-12 having 4 SONET STS-3c Paths.  Similarly, a SONET Synchronous
   Payload Envelope (SPE) can carry many Virtual Tributaries (VTs), for
   example, one SONET SPE can carry 28 VT1.5s.  It is important to note
   that an SPE and a VT in SONET is collectively referred to as a
   Virtual Container (VC) in SDH.  Also, an STS is called Synchronous
   Transport Module (STM) in SDH.

   Not all SONET/SDH equipment terminates all SONET/SDH layers.  For
   example, a SONET/SDH STE regenerator terminates SONET/SDH Sections
   only, and is transparent for all layers above that.  SONET/SDH Add-
   Drop multiplexers and Digital Cross Connect Systems terminate
   SONET/SDH Lines. SONET/SDH Terminal Multiplexers may also terminate
   SONET/SDH Paths and VTs/VCs.

   MIB II [16], as extended by [23], accommodates these cases by
   appropriate use of the MIB II system group, and the interfaces group.
   The system group can name and describe the type of managed resource.
   The interfaces group defines which SONET/SDH layers apply, how these
   layers are configured and multiplexed.  This is achieved by proper
   representation of SONET/SDH Layers by ifEntries as defined in [23],
   as follows:






















Tesink                      Standards Track                     [Page 4]

RFC 2558                   SONET/SDH Objects                  March 1999


                 _____________________________
                |             |          |    |  >
                |             |          |    |  |
                |    VT 1     |..........|VT K|   > K ifEntries
                |             |          |    |  |
                |_____________|__________|____|  >
                |               |      |      |  >
                |               |      |      |  |
                |    Path 1     |......|Path L|   > L ifEntries
                |               |      |      |  |
                |_______________|______|______|  >
                |                             |  >
                |                             |  |
                |    Line                     |  |
                |                             |  |
                |_____________________________|  |
                |                             |  |
                |                             |  |
                |    Section Layer            |   > 1 ifEntry
                |                             |  |
                |_____________________________|  |
                |                             |  |
                |                             |  |
                |    Physical Medium Layer    |  |
                |                             |  |
                |_____________________________|  >

                Use of ifTable for a SONET/SDH port

   The exact configuration and multiplexing of the layers is maintained
   in the ifStackTable [23].

3.2.  Use of ifTable for SONET/SDH Medium/Section/Line Layer

   Only the ifGeneralInformationGroup needs to be supported.

   ifTable Object    Use for combined SONET/SDH
                     Medium/Section/Line Layer
   ======================================================================
    ifIndex           Interface index.

    ifDescr           SONET/SDH Medium/Section/Line

    ifType            sonet(39)

    ifSpeed           Speed of line rate for SONET/SDH,
                      (e.g., 155520000 bps).




Tesink                      Standards Track                     [Page 5]

RFC 2558                   SONET/SDH Objects                  March 1999


    ifPhysAddress     The value of the Circuit Identifier.
                      If no Circuit Identifier has been assigned
                      this object should have an octet string with
                      zero length.

    ifAdminStatus     Supports read-only access.
                      The desired administrative status of the
                      interface.

    ifOperStatus      The value testing(3) is not used.
                      This object assumes the value down(2),
                      if the objects sonetSectionCurrentStatus
                      and sonetLineCurrentStatus have
                      any other value than sonetSectionNoDefect(1)
                      and sonetLineNoDefect(1), respectively.

    ifLastChange      sysUpTime at the last change in ifOperStatus.

    ifName            Textual name of the interface or an OCTET STRING
                      of zero length.

    ifLinkUpDownTrapEnable   Default value is enabled(1).
                             Just read-only access may be supported.

    ifHighSpeed       Speed of line in Mega-bits per second
                      (e.g., 155 Mbps)

    ifConnectorPresent Set to true(1).

    ifAlias            The (non-volatile) alias name for this interface
                       as assigned by the network manager.

3.3.  Use of ifTable for SONET/SDH Paths

   Only the ifGeneralInformationGroup needs to be supported.

   ifTable Object    Use for SONET/SDH Paths
   =========================================
    ifIndex           Interface index.

    ifDescr           SONET/SDH Path

    ifType            sonetPath(50)

    ifSpeed           set to speed of SONET/SDH path
                      (e.g., an STS-1 path has a
                      rate of 50112000 bps.)




Tesink                      Standards Track                     [Page 6]

RFC 2558                   SONET/SDH Objects                  March 1999


    ifPhysAddress     Circuit Identifier or OCTET STRING of zero length.

    ifAdminStatus     Supports read-only access.
                      The desired administrative status of the
                      interface.

    ifOperStatus      This object assumes the value down(2),
                      if the object sonetPathCurrentStatus has
                      any other value than sonetPathNoDefect(1).

    ifLastChange      sysUpTime at the last change in ifOperStatus.

    ifName            Textual name of the interface or an OCTET STRING
                      of zero length.

    ifLinkUpDownTrapEnable   Default value is disabled(2).
                             Just read-only access may be supported.

    ifHighSpeed       Set to rate of SONET/SDH path
                      in Mega-bits per second.