rfc1595.txt

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


RFC 1595                   SONET/SDH Objects                  March 1994


               A STS-Path Remote Failure Indication (RFI) failure is
               declared when the incoming STS-Path RDI defects lasts for
               2.5 +/- 0.5 seconds.  The STS-Path RFI failure is cleared
               when no STS-Path RDI defects are detected for 10 +/- 0.5
               seconds.

          VT-Path Remote Defect Indication
               VT Path RDI (aka VT Path FERF) signal shall be generated
               within 100 milliseconds by the VT PTE upon detection of a
               VT-Path AIS or LOP defect.  Transmission of the VT-Path
               RDI signal shall cease within 100 milliseconds when the
               VT PTE no longer detects VT-Path AIS or VT-Path LOP
               defect.  The VT-Path RDI  shall accurately report the
               presence or absence of VT-Path AIS or VT-Path LOP
               defects.  VT-Path RDI defect is defined in ANSI T1.105.
               The following requirements are specific to VT-Path RDI
               defect:

               --  VT-Path RDI defect is the occurrence of a "1" in bit
               4 of the VT-Path Overhead byte (V5) in five contiguous
               frames.

               --  VT-Path RDI defect is terminated when a "0" is
               detected in bit 4 of the VT-Path Overhead byte (V5) for
               five contiguous frames.

               A VT-Path Remote Failure Indication (RFI) (derived)
               failure is declared when the incoming VT-Path RDI defects
               lasts for 2.5 +/- 0.5 seconds.  The VT-Path RFI failure
               is cleared when no VT-Path RDI defects are detected for
               10 +/- 0.5 seconds.

          VT-Path Remote Failure Indication
               The VT-Path RFI signal is only required for the case of
               byte synch mapped DS1s where the DS1 frame bit is not
               mapped.  The VT-Path RFI is specified in ANSI T1.105,
               where it is currently called VT path yellow.  When
               provided, the VT-Path RFI signal is used to indicate the
               occurrence of far-end failures.  When the VT-Path RFI is
               not provided, far-end failures are derived from local
               timing of the VT-Path RDI defect.  The VT-Path RFI
               failure is declared within 5 ms of detecting the incoming
               VT-Path RFI Signal.  The VT-Path Remote Failure
               Indication (RFI) failure is cleared within 50 ms of
               detecting the removal of the incoming VT-Path RFI signal.






AToM MIB Working Group                                         [Page 13]

RFC 1595                   SONET/SDH Objects                  March 1994


          Coding Violation
               Coding Violations (CV) are Bit Interleaved Parity (BIP)
               errors that are detected in the incoming signal.  CV
               counters are incremented for each BIP error detected.
               That is, each BIP-8 can detect up to eight errors per
               STS-N frame, with each error incrementing the CV counter.
               Section CVs shall be collected using the BIP-8 in the B1
               byte located in the Section Overhead of STS-1 #1.  Line
               CVs shall be collected using the BIP-8s in B2 bytes
               located in the Line Overhead of each STS-1 (since all CVs
               on an STS-N line are counted together, this is equivalent
               to counting each error in the BIP-8*N contained in the B2
               bytes of the STS-N Line Overhead).  Thus, on an STS-N
               signal, up to 8 x N CVs may occur in each frame.  Path
               CVs shall be collected using the BIP-8 in the B3 byte of
               the STS-Path Overhead of the STS SPE.  VT CVs shall be
               collected using the BIP-2 in the V5 overhead byte of the
               floating VT.

          Errored Seconds
               At each layer, an Errored Second (ES) is a second with
               one or more Coding Violations at that layer OR one or
               more incoming defects (e.g., SEF, LOS, AIS, LOP) at that
               layer has occurred.

          Severely Errored Seconds
               At each layer, an Severely Errored Second (SES) is a
               second with x or more CVs at that layer, or a second
               during which at least one or more incoming defects at
               that layer has occurred.  Values of x vary depending on
               the line rate and the Bit Error Rate.  See Section 3.4
               for values for x.

          Severely Errored Framing Seconds
               A Severely Errored Framing Second (SEFS) is a seconds
               with containing one or more SEF events.  This counter is
               only counted at the Section Layer.

          Unavailable Seconds
               At the Line, Path, and VT layers, an unavailable second
               is calculated by counting the number of seconds that the
               interface is unavailable.  At each layer, the SONET/SDH
               interface is said to be unavailable at the onset of 10
               contiguous SESs.  The 10 SESs are included in unavailable
               time.  Once unavailable, the SONET/SDH interface becomes
               available at the onset of 10 contiguous seconds with no
               SESs.  The 10 seconds with no SESs are excluded from
               unavailable time.  With respect to the SONET/SDH error



AToM MIB Working Group                                         [Page 14]

RFC 1595                   SONET/SDH Objects                  March 1994


               counts at each layer, all counters at that layer are
               incremented while the SONET/SDH interface is deemed
               available at that layer.  While the interface is deemed
               unavailable at that layer, the only count that is
               incremented is UASs at that layer.

               A special case exists when the 10 or more second period
               crosses the 900 second statistics window boundary, as the
               foregoing description implies that the SES and UAS
               counters must be adjusted when the Unavailable Signal
               State is entered. Clearly, successive GETs of the
               affected sonetPathIntervalSES and sonetPathIntervalUAS
               (for the Line and VT also) objects will return differing
               values if the first GET occurs during the first few
               seconds of the window.  This is viewed as an unavoidable
               side-effect of selecting the presently defined managed
               objects as a basis for this memo.

          Unequipped
               If a Path or VT connection is not provisioned (idle) the
               SONET equipment will signal this state by transmitting
               the Path or VT Signal Label as follows:
               - byte C2 of the STS Path Overhead equal to 0 for an
               unequipped Path,
               - byte V5 of the VT Path Overhead equal to 0 for an
               unequipped VT.

          Signal Label Mismatch
               A Path or VT connection is not correctly provisioned if a
               received Path or VT Signal Label mismatch occurs.  A
               received Signal Label is considered mismatched if it does
               not equal either the locally provisioned value or the
               value 'equipped non-specific' (1 hex). Note that any
               received non-zero Signal Label is considered a locally
               provisioned value of 'equipped non-specific'.  Only in-
               service, provisioned Path Terminating equipment can
               detect mismatched Signal labels. It is considered
               provisioned if it has been configured for a mapping and
               has been assigned signals to and from which the mapping
               takes place.

          Circuit Identifier
               This is a character string specified by the circuit
               vendor, and is useful when communicating with the vendor
               during the troubleshooting process.






AToM MIB Working Group                                         [Page 15]

RFC 1595                   SONET/SDH Objects                  March 1994


3.6.  Values for x for the Section, Line, Path, and VT Layers

                    Value for x for SONET/SDH Section SES Definition

               Rate            x               Minimum Bit Error Rate
               =======================================================
               OC-1             9                      1.5 x 10^-7
               0C-3            16                        1 x 10^-7
               OC-9            47                        1 x 10^-7
               OC-12           63                        1 x 10^-7
               OC-18           94                        1 x 10^-7
               OC-24          125                        1 x 10^-7
               OC-36          187                        1 x 10^-7
               OC-48          249                        1 x 10^-7


                    Value for x for SONET/SDH Line SES Definition

               Rate            x               Minimum Bit Error Rate
               =======================================================
               OC-1            12                       2 x 10^-7
               0C-3            32                       2 x 10^-7
               OC-9            94                       2 x 10^-7
               OC-12          124                       2 x 10^-7
               OC-18          186                       2 x 10^-7
               OC-24          248                       2 x 10^-7
               OC-36          370                       2 x 10^-7
               OC-48          494                       2 x 10^-7


                    Value for x for SONET/SDH STS-Path SES Definition

               Rate            x               Minimum Bit Error Rate
               =======================================================
               STS-1            9                       1.5 x 10^-7
               STS-3           16                         1 x 10^-7


                    Value for x for SONET/SDH VT-Path SES Definition

               Rate            x               Minimum Bit Error Rate
               =======================================================
               VT1.5            4                       2 x 10^-6
               VT2              6                       2 x 10^-6
               VT3              8                       2 x 10^-6
               VT6             14                       2 x 10^-6





AToM MIB Working Group                                         [Page 16]

RFC 1595                   SONET/SDH Objects                  March 1994


4.  Object Definitions

          SONET-MIB DEFINITIONS ::= BEGIN


          IMPORTS
              MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
              Integer32,
                    FROM SNMPv2-SMI
              TEXTUAL-CONVENTION, DisplayString
                    FROM SNMPv2-TC
              MODULE-COMPLIANCE, OBJECT-GROUP
                    FROM SNMPv2-CONF
              ifIndex, transmission
                    FROM RFC-1213;

          --  This is the MIB module for the SMDS Interface objects.


          sonetMIB MODULE-IDENTITY
              LAST-UPDATED "9401030000Z"
              ORGANIZATION "IETF AToM MIB Working Group"
              CONTACT-INFO
                "        Tracy Brown

                 Postal: Bell Communications Research
                         331 Newman Springs Road
                         P.O. Box 7020
                         Red Bank, NJ  07701-7020
                         US

                    Tel: [phone]
                    Fax: [phone]

                 E-mail: [e-mail]


                         Kaj Tesink

                 Postal: Bell Communications Research
                         331 Newman Springs Road
                         P.O. Box 7020
                         Red Bank, NJ  07701-7020
                         US

                    Tel: [phone]
                    Fax: [phone]




AToM MIB Working Group                                         [Page 17]

RFC 1595                   SONET/SDH Objects                  March 1994


                 E-mail: [e-mail]"
              DESCRIPTION
                   "The MIB module to describe
                   SONET/SDH interfaces objects."
              ::= { transmission 39 }


          --  This is the MIB module for the SONET/SDH objects

          sonetObjects      OBJECT IDENTIFIER ::= { sonetMIB 1 }

          sonetObjectsPath  OBJECT IDENTIFIER ::= { sonetMIB 2 }

          sonetObjectsVT    OBJECT IDENTIFIER ::= { sonetMIB 3 }


          -- groups in the SONET/SDH MIB module

          sonetMedium       OBJECT IDENTIFIER ::= { sonetObjects 1 }

          sonetSection      OBJECT IDENTIFIER ::= { sonetObjects 2 }

          sonetLine         OBJECT IDENTIFIER ::= { sonetObjects 3 }

          sonetFarEndLine   OBJECT IDENTIFIER ::= { sonetObjects 4 }

          sonetPath         OBJECT IDENTIFIER ::= { sonetObjectsPath 1 }

          sonetFarEndPath   OBJECT IDENTIFIER ::= { sonetObjectsPath 2 }

          sonetVT           OBJECT IDENTIFIER ::= { sonetObjectsVT 1 }

          sonetFarEndVT     OBJECT IDENTIFIER ::= { sonetObjectsVT 2 }


          -- the SONET/SDH Medium group

          -- SONET/SDH interfaces for some applications may be
          -- electrical interfaces and not optical interfaces.
          -- This group handles the configuration information for
          -- both optical SONET/SDH interfaces and electrical
          -- SONET/SDH interfaces.

          sonetMediumTable OBJECT-TYPE
              SYNTAX  SEQUENCE OF SonetMediumEntry
              MAX-ACCESS  not-accessible
              STATUS  current
              DESCRIPTION



AToM MIB Working Group                                         [Page 18]