tech-invite   World Map
3GPP     Specs     Glossaries     UICC       IETF     RFCs     Groups     SIP     ABNFs       T+       Search     Home

RFC 3896

 
 
 

Definitions of Managed Objects for the DS3/E3 Interface Type

Part 3 of 3, p. 42 to 63
Prev RFC Part

 


prevText      Top      Up      ToC       Page 42 
   dsx3FarEndCurrentCSESs OBJECT-TYPE
        SYNTAX  PerfCurrentCount
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Severely Errored Seconds."
        ::= { dsx3FarEndCurrentEntry 5 }

   dsx3FarEndCurrentCCVs OBJECT-TYPE
        SYNTAX  PerfCurrentCount
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Coding Violations reported via the far end
               block error count."
        ::= { dsx3FarEndCurrentEntry 6 }

   dsx3FarEndCurrentUASs OBJECT-TYPE
        SYNTAX  PerfCurrentCount
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               "The counter associated with the number of Far End
               unavailable seconds."
        ::= { dsx3FarEndCurrentEntry 7 }

   dsx3FarEndInvalidIntervals OBJECT-TYPE
        SYNTAX  INTEGER (0..96)
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               " The number of intervals in the range from 0 to
               dsx3FarEndValidIntervals for which no data is
               available.  This object will typically be zero
               except in cases where the data for some intervals
               are not available (e.g., in proxy situations)."
        ::= { dsx3FarEndCurrentEntry 8 }

   -- The DS3 Far End Interval Table

   dsx3FarEndIntervalTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF Dsx3FarEndIntervalEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
               "The DS3 Far End Interval Table contains various

Top      Up      ToC       Page 43 
               statistics collected by each DS3 interface over
               the previous 24 hours of operation.  The past 24
               hours are broken into 96 completed 15 minute
               intervals."
        ::= { ds3 11 }

   dsx3FarEndIntervalEntry OBJECT-TYPE
        SYNTAX  Dsx3FarEndIntervalEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
               "An entry in the DS3 Far End Interval table."
        INDEX   { dsx3FarEndIntervalIndex,
                  dsx3FarEndIntervalNumber }
        ::= { dsx3FarEndIntervalTable 1 }

   Dsx3FarEndIntervalEntry ::=
        SEQUENCE {
             dsx3FarEndIntervalIndex      InterfaceIndex,
             dsx3FarEndIntervalNumber     INTEGER,
             dsx3FarEndIntervalCESs       PerfIntervalCount,
             dsx3FarEndIntervalCSESs      PerfIntervalCount,
             dsx3FarEndIntervalCCVs       PerfIntervalCount,
             dsx3FarEndIntervalUASs       PerfIntervalCount,
             dsx3FarEndIntervalValidData  TruthValue
       }

   dsx3FarEndIntervalIndex OBJECT-TYPE
        SYNTAX  InterfaceIndex
        MAX-ACCESS  read-only  -- read-only since originally an
                               -- SMIv1 index
        STATUS  current
        DESCRIPTION
               "The index value which uniquely identifies the DS3
               interface to which this entry is applicable.  The
               interface identified by a particular value of this
               index is identical to the interface identified by
               the same value of dsx3LineIndex."
        ::= { dsx3FarEndIntervalEntry 1 }

   dsx3FarEndIntervalNumber OBJECT-TYPE
       SYNTAX  INTEGER (1..96)
       MAX-ACCESS  read-only  -- read-only since originally an
                               -- SMIv1 index
       STATUS  current
       DESCRIPTION
               "A number between 1 and 96, where 1 is the most
               recently completed 15 minute interval and 96 is

Top      Up      ToC       Page 44 
               the 15 minutes interval completed 23 hours and 45
               minutes prior to interval 1."
       ::= { dsx3FarEndIntervalEntry 2 }

   dsx3FarEndIntervalCESs OBJECT-TYPE
       SYNTAX  PerfIntervalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Errored Seconds encountered by a DS3
               interface in one of the previous 96, individual 15
               minute, intervals. In the case where the agent is
               a proxy and data is not available, return
               noSuchInstance."
       ::= { dsx3FarEndIntervalEntry 3 }

   dsx3FarEndIntervalCSESs OBJECT-TYPE
       SYNTAX  PerfIntervalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Severely Errored Seconds."
        ::= { dsx3FarEndIntervalEntry 4 }

   dsx3FarEndIntervalCCVs OBJECT-TYPE
        SYNTAX  PerfIntervalCount
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Coding Violations reported via the far end
               block error count."
        ::= { dsx3FarEndIntervalEntry 5 }

   dsx3FarEndIntervalUASs OBJECT-TYPE
        SYNTAX  PerfIntervalCount
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
               "The counter associated with the number of Far End
               unavailable seconds."
        ::= { dsx3FarEndIntervalEntry 6 }

   dsx3FarEndIntervalValidData OBJECT-TYPE
        SYNTAX  TruthValue
        MAX-ACCESS  read-only

Top      Up      ToC       Page 45 
        STATUS  current
        DESCRIPTION
               " This variable indicates if the data for this
               interval is valid."
        ::= { dsx3FarEndIntervalEntry 7 }

   -- The DS3 Far End Total

   dsx3FarEndTotalTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF Dsx3FarEndTotalEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
               "The DS3 Far End Total Table contains the
               cumulative sum of the various statistics for the
               24 hour period preceding the current interval."
        ::= { ds3 12 }

   dsx3FarEndTotalEntry OBJECT-TYPE
        SYNTAX  Dsx3FarEndTotalEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
               "An entry in the DS3 Far End Total table."
        INDEX   { dsx3FarEndTotalIndex }
        ::= { dsx3FarEndTotalTable 1 }

   Dsx3FarEndTotalEntry ::=
        SEQUENCE {
            dsx3FarEndTotalIndex       InterfaceIndex,
            dsx3FarEndTotalCESs        PerfTotalCount,
            dsx3FarEndTotalCSESs       PerfTotalCount,
            dsx3FarEndTotalCCVs        PerfTotalCount,
            dsx3FarEndTotalUASs        PerfTotalCount
        }

   dsx3FarEndTotalIndex OBJECT-TYPE
       SYNTAX  InterfaceIndex
       MAX-ACCESS  read-only  -- read-only since originally an
                               -- SMIv1 index
       STATUS  current
       DESCRIPTION
               "The index value which uniquely identifies the DS3
               interface to which this entry is applicable.  The
               interface identified by a particular value of this
               index is identical to the interface identified by
               the same value of dsx3LineIndex."
       ::= { dsx3FarEndTotalEntry 1 }

Top      Up      ToC       Page 46 
   dsx3FarEndTotalCESs OBJECT-TYPE
       SYNTAX  PerfTotalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Errored Seconds encountered by a DS3
               interface in the previous 24 hour interval.
               Invalid 15 minute intervals count as 0."
       ::= { dsx3FarEndTotalEntry 2 }

   dsx3FarEndTotalCSESs OBJECT-TYPE
       SYNTAX  PerfTotalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Severely Errored Seconds encountered by a
               DS3 interface in the previous 24 hour interval.
               Invalid 15 minute intervals count as 0."
       ::= { dsx3FarEndTotalEntry 3 }

   dsx3FarEndTotalCCVs OBJECT-TYPE
       SYNTAX  PerfTotalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               C-bit Coding Violations reported via the far end
               block error count encountered by a DS3 interface
               in the previous 24 hour interval. Invalid 15
               minute intervals count as 0."
       ::= { dsx3FarEndTotalEntry 4 }

   dsx3FarEndTotalUASs OBJECT-TYPE
       SYNTAX  PerfTotalCount
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
               "The counter associated with the number of Far End
               unavailable seconds encountered by a DS3 interface
               in the previous 24 hour interval.  Invalid 15
               minute intervals count as 0."
       ::= { dsx3FarEndTotalEntry 5 }

   -- the DS3/E3 Fractional Table

   -- This table is deprecated.

Top      Up      ToC       Page 47 
   dsx3FracTable OBJECT-TYPE
       SYNTAX  SEQUENCE OF Dsx3FracEntry
       MAX-ACCESS  not-accessible
       STATUS  deprecated
       DESCRIPTION
               "This table is deprecated in favour of using
               ifStackTable.

               Implementation of this table was optional.  It was
               designed for those systems dividing a DS3/E3 into
               channels containing different data streams that
               are of local interest.

               The DS3/E3 fractional table identifies which
               DS3/E3 channels associated with a CSU are being
               used to support a logical interface, i.e., an
               entry in the interfaces table from the Internet-
               standard MIB.

               For example, consider a DS3 device with 4 high
               speed links carrying router traffic, a feed for
               voice, a feed for video, and a synchronous channel
               for a non-routed protocol.  We might describe the
               allocation of channels, in the dsx3FracTable, as
               follows:
               dsx3FracIfIndex.2. 1 = 3  dsx3FracIfIndex.2.15 = 4
               dsx3FracIfIndex.2. 2 = 3  dsx3FracIfIndex.2.16 = 6
               dsx3FracIfIndex.2. 3 = 3  dsx3FracIfIndex.2.17 = 6
               dsx3FracIfIndex.2. 4 = 3  dsx3FracIfIndex.2.18 = 6
               dsx3FracIfIndex.2. 5 = 3  dsx3FracIfIndex.2.19 = 6
               dsx3FracIfIndex.2. 6 = 3  dsx3FracIfIndex.2.20 = 6
               dsx3FracIfIndex.2. 7 = 4  dsx3FracIfIndex.2.21 = 6
               dsx3FracIfIndex.2. 8 = 4  dsx3FracIfIndex.2.22 = 6
               dsx3FracIfIndex.2. 9 = 4  dsx3FracIfIndex.2.23 = 6
               dsx3FracIfIndex.2.10 = 4  dsx3FracIfIndex.2.24 = 6
               dsx3FracIfIndex.2.11 = 4  dsx3FracIfIndex.2.25 = 6
               dsx3FracIfIndex.2.12 = 5  dsx3FracIfIndex.2.26 = 6
               dsx3FracIfIndex.2.13 = 5  dsx3FracIfIndex.2.27 = 6
               dsx3FracIfIndex.2.14 = 5  dsx3FracIfIndex.2.28 = 6
               For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and
               dsx3ClearChannel  there are 28 legal channels,
               numbered 1 through 28.

               For e3Framed there are 16 legal channels, numbered
               1 through 16.  The channels (1..16) correspond
               directly to the equivalently numbered time-slots."
        ::= { ds3 13 }

Top      Up      ToC       Page 48 
   dsx3FracEntry OBJECT-TYPE
        SYNTAX  Dsx3FracEntry
        MAX-ACCESS  not-accessible
        STATUS  deprecated
        DESCRIPTION
                       "An entry in the DS3 Fractional table."
       INDEX   { dsx3FracIndex, dsx3FracNumber }
       ::= { dsx3FracTable 1 }

   Dsx3FracEntry ::=
        SEQUENCE {
            dsx3FracIndex     INTEGER,
            dsx3FracNumber    INTEGER,
            dsx3FracIfIndex   INTEGER
       }

   dsx3FracIndex OBJECT-TYPE
       SYNTAX  INTEGER (1..'7fffffff'h)
       MAX-ACCESS  read-only -- read-only since originally an
                                 -- SMIv1 index
       STATUS  deprecated
       DESCRIPTION
               "The index value which uniquely identifies  the
               DS3  interface  to which this entry is applicable
               The interface identified by a  particular value
               of  this  index is the same interface as
               identified by the same value  an  dsx3LineIndex
               object instance."
       ::= { dsx3FracEntry 1 }

   dsx3FracNumber OBJECT-TYPE
       SYNTAX  INTEGER (1..31)
       MAX-ACCESS  read-only  -- read-only since originally an
                               -- SMIv1 index
       STATUS  deprecated
       DESCRIPTION
               "The channel number for this entry."
      ::= { dsx3FracEntry 2 }

   dsx3FracIfIndex OBJECT-TYPE
      SYNTAX  INTEGER (0..'7fffffff'h)
      MAX-ACCESS  read-write
      STATUS  deprecated
      DESCRIPTION
              "An index value that uniquely identifies an
              interface.  The interface identified by a
              particular value of this index is the same
              interface as  identified by the same value an

Top      Up      ToC       Page 49 
              ifIndex object instance. If no interface is
              currently using a channel, the value should be
              zero.  If a single interface occupies more  than
              one  time slot,  that ifIndex value will be found
              in multiple time slots."
      ::= { dsx3FracEntry 3 }

    -- DS3 TRAPS

   ds3Traps OBJECT IDENTIFIER ::= { ds3 15 }

   dsx3LineStatusChange NOTIFICATION-TYPE
       OBJECTS { dsx3LineStatus,
                 dsx3LineStatusLastChange }
       STATUS  current
       DESCRIPTION
               "A dsx3LineStatusChange trap is sent when the
               value of an instance of dsx3LineStatus changes. It
               can be utilized by an NMS to trigger polls.  When
               the line status change results in a lower level
               line status change (i.e., ds1), then no traps for
               the lower level are sent."
        ::= { ds3Traps 0 1 }

   -- conformance information

   ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 }
   ds3Groups      OBJECT IDENTIFIER ::= { ds3Conformance 1 }
   ds3Compliances OBJECT IDENTIFIER ::= { ds3Conformance 2 }

   -- compliance statements

   ds3Compliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
               "The compliance statement for DS3/E3 interfaces."
       MODULE  -- this module
           MANDATORY-GROUPS { ds3NearEndConfigGroup,
                              ds3NearEndStatisticsGroup }

           GROUP       ds3FarEndGroup
           DESCRIPTION
               "Implementation of this group is optional for all
               systems that attach to a DS3 Interface.  However,
               only C-bit Parity and SYNTRAN DS3 applications
               have the capability (option) of providing this
               information."
           GROUP       ds3NearEndOptionalTrapGroup

Top      Up      ToC       Page 50 
           DESCRIPTION
               "Implementation of this group is optional for all
               systems that attach to a DS3 Interface.  If it is
               implemented then ds3NearEndOptionalConfigGroup
               should also be implemented."
           GROUP       ds3NearEndOptionalConfigGroup
           DESCRIPTION
               "Implementation of this group is optional for all
               systems that attach to a DS3 interface."

           OBJECT      dsx3LineType
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the line type is not required."

           OBJECT      dsx3LineCoding
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the line coding is not
               required."

           OBJECT      dsx3SendCode
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the send code is not required."

           OBJECT      dsx3LoopbackConfig
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for loopbacks is not required."

           OBJECT      dsx3TransmitClockSource
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the transmit clock source is not
               required."

           OBJECT      dsx3LineLength
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the line length is not
               required."

           OBJECT      dsx3Channelization
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access for the channelization is not
               required."

Top      Up      ToC       Page 51 
       ::= { ds3Compliances 1 }

   -- units of conformance

   ds3NearEndConfigGroup  OBJECT-GROUP
       OBJECTS { dsx3LineIndex,
                 dsx3TimeElapsed,
                 dsx3ValidIntervals,
                 dsx3LineType,
                 dsx3LineCoding,
                 dsx3SendCode,
                 dsx3CircuitIdentifier,
                 dsx3LoopbackConfig,
                 dsx3LineStatus,
                 dsx3TransmitClockSource,
                 dsx3InvalidIntervals,
                 dsx3LineLength,
                 dsx3LoopbackStatus,
                 dsx3Channelization,
                 dsx3Ds1ForRemoteLoop}
       STATUS  current
       DESCRIPTION
               "A collection of objects providing configuration
               information applicable to all DS3/E3 interfaces."
       ::= { ds3Groups 1 }

   ds3NearEndStatisticsGroup OBJECT-GROUP
       OBJECTS { dsx3CurrentIndex,
                 dsx3CurrentPESs,
                 dsx3CurrentPSESs,
                 dsx3CurrentSEFSs,
                 dsx3CurrentUASs,
                 dsx3CurrentLCVs,
                 dsx3CurrentPCVs,
                 dsx3CurrentLESs,
                 dsx3CurrentCCVs,
                 dsx3CurrentCESs,
                 dsx3CurrentCSESs,
                 dsx3IntervalIndex,
                 dsx3IntervalNumber,
                 dsx3IntervalPESs,
                 dsx3IntervalPSESs,
                 dsx3IntervalSEFSs,
                 dsx3IntervalUASs,
                 dsx3IntervalLCVs,
                 dsx3IntervalPCVs,
                 dsx3IntervalLESs,
                 dsx3IntervalCCVs,

Top      Up      ToC       Page 52 
                 dsx3IntervalCESs,
                 dsx3IntervalCSESs,
                 dsx3IntervalValidData,
                 dsx3TotalIndex,
                 dsx3TotalPESs,
                 dsx3TotalPSESs,
                 dsx3TotalSEFSs,
                 dsx3TotalUASs,
                 dsx3TotalLCVs,
                 dsx3TotalPCVs,
                 dsx3TotalLESs,
                 dsx3TotalCCVs,
                 dsx3TotalCESs,
                 dsx3TotalCSESs }
       STATUS  current
       DESCRIPTION
               "A collection of objects providing statistics
               information applicable to all DS3/E3 interfaces."
       ::= { ds3Groups 2 }

   ds3FarEndGroup  OBJECT-GROUP
       OBJECTS { dsx3FarEndLineIndex,
                 dsx3FarEndEquipCode,
                 dsx3FarEndLocationIDCode,
                 dsx3FarEndFrameIDCode,
                 dsx3FarEndUnitCode,
                 dsx3FarEndFacilityIDCode,
                 dsx3FarEndCurrentIndex,
                 dsx3FarEndTimeElapsed,
                 dsx3FarEndValidIntervals,
                 dsx3FarEndCurrentCESs,
                 dsx3FarEndCurrentCSESs,
                 dsx3FarEndCurrentCCVs,
                 dsx3FarEndCurrentUASs,
                 dsx3FarEndInvalidIntervals,
                 dsx3FarEndIntervalIndex,
                 dsx3FarEndIntervalNumber,
                 dsx3FarEndIntervalCESs,
                 dsx3FarEndIntervalCSESs,
                 dsx3FarEndIntervalCCVs,
                 dsx3FarEndIntervalUASs,
                 dsx3FarEndIntervalValidData,
                 dsx3FarEndTotalIndex,
                 dsx3FarEndTotalCESs,
                 dsx3FarEndTotalCSESs,
                 dsx3FarEndTotalCCVs,
                 dsx3FarEndTotalUASs }
       STATUS  current

Top      Up      ToC       Page 53 
       DESCRIPTION
               "A collection of objects providing remote
               configuration and statistics information
               applicable to C-bit Parity and SYNTRAN DS3
               interfaces."
       ::= { ds3Groups 3 }

   ds3DeprecatedGroup OBJECT-GROUP

       OBJECTS { dsx3IfIndex,
                 dsx3FracIndex,
                 dsx3FracNumber,
                 dsx3FracIfIndex }
       STATUS  deprecated
       DESCRIPTION
               "A collection of obsolete objects that may be
               implemented for backwards compatibility."
       ::= { ds3Groups 4 }

   ds3NearEndOptionalConfigGroup OBJECT-GROUP
       OBJECTS { dsx3LineStatusLastChange,
                 dsx3LineStatusChangeTrapEnable }

       STATUS    current
       DESCRIPTION
               "A collection of objects that may be implemented
               on DS3/E3 interfaces."
       ::= { ds3Groups 5 }

   ds3NearEndOptionalTrapGroup NOTIFICATION-GROUP
       NOTIFICATIONS { dsx3LineStatusChange }
       STATUS    current
       DESCRIPTION
               "A collection of notifications that may be
               implemented on DS3/E3 interfaces."
       ::= { ds3Groups 6 }

   END

Top      Up      ToC       Page 54 
4.  Appendix A - Use of dsx3IfIndex and dsx3LineIndex

   This Appendix exists to document the previous use if dsx3IfIndex and
   dsx3LineIndex and to clarify the relationship of dsx3LineIndex as
   defined in RFC 1407 with the dsx3LineIndex as defined in this
   document.

   The following shows the old and new definitions and the relationship:

   [New Definition]: "This object should be made equal to ifIndex.  The
   next paragraph describes its previous usage.  Making the object equal
   to ifIndex allows proper use of ifStackTable.

   [Old Definition]: "this object is the identifier of a DS3/E3
   Interface on a managed device.  If there is an ifEntry that is
   directly associated with this and only this DS3/E3 interface, it
   should have the same value as ifIndex.  Otherwise, number the
   dsx3LineIndices with an unique identifier following the rules of
   choosing a number that is greater than ifNumber and numbering the
   inside interfaces (e.g., equipment side) with even numbers and
   outside interfaces (e.g, network side) with odd numbers."

   When the "Old Definition" was created, it was described this way to
   allow a manager to treat the value _as if_ it were an ifIndex, i.e.,
   the value would either be:  1) an ifIndex value or 2) a value that
   was guaranteed to be different from all valid ifIndex values.

   The new definition is a subset of that definition, i.e., the value is
   always an ifIndex value.

   The following is Section 3.1 from [RFC1407]:

   Different physical configurations for the support of SNMP with DS3/E3
   equipment exist.  To accommodate these scenarios, two different
   indices for DS3/E3 interfaces are introduced in this MIB.  These
   indices are dsx3IfIndex and dsx3LineIndex.

   External interface scenario: the SNMP Agent represents all managed
   DS3/E3 lines as external interfaces (for example, an Agent residing
   on the device supporting DS3/E3 interfaces directly):

Top      Up      ToC       Page 55 
   For this scenario, all interfaces are assigned an integer value equal
   to ifIndex, and the following applies:

      ifIndex=dsx3IfIndex=dsx3LineIndex for all interfaces.

   The dsx3IfIndex column of the DS3/E3 Configuration table relates each
   DS3/E3 interface to its corresponding interface (ifIndex) in the
   Internet-standard MIB (MIB-II STD 17, [RFC1213]).

   External&Internal interface scenario: the SNMP Agents resides on an
   host external from the device supporting DS3/E3 interfaces (e.g., a
   router).  The Agent represents both the host and the DS3/E3 device.
   The index dsx3LineIndex is used to not only represent the DS3/E3
   interfaces external from the host/DS3/E3-device combination, but also
   the DS3/E3 interfaces connecting the host and the DS3/E3 device.  The
   index dsx3IfIndex is always equal to ifIndex.

   Example:

   A shelf full of CSUs connected to a Router.  An SNMP Agent residing
   on the router proxies for itself and the CSU.  The router has also an
   Ethernet interface:

         +-----+
   |     |     |
   |     |     |               +---------------------+
   |E    |     |  44.736 MBPS  |   ds3 M13    Line#A | ds3 C-bit Parity
   |t    |  R  |---------------+ - - - - -  - - -  - +------>
   |h    |     |               |                     |
   |e    |  O  |  44.736 MBPS  |   ds3 M13    Line#B | ds3 C-bit Parity
   |r    |     |---------------+ - - - - - - - - - - +------>
   |n    |  U  |               |                     |
   |e    |     |  44.736 MBPS  |   ds3 M13    Line#C | ds3 C-bit Parity
   |t    |  T  |---------------+ - - - -- -- - - - - +------>
   |     |     |               |                     |
   |-----|  E  |  44.736 MBPS  |   ds3 M13    Line#D | ds3 C-bit Parity
   |     |     |---------------+ -  - - - -- - - - - +------>
   |     |  R  |               |_____________________|
   |     |     |
   |     +-----+

Top      Up      ToC       Page 56 
   The assignment of the index values could for example be:

           ifIndex (= dsx3IfIndex)                     dsx3LineIndex

                   1                   NA                  NA (Ethernet)
                   2      Line#A   Router Side             6
                   2      Line#A   Network Side            7
                   3      Line#B   Router Side             8
                   3      Line#B   Network Side            9
                   4      Line#C   Router Side            10
                   4      Line#C   Network Side           11
                   5      Line#D   Router Side            12
                   5      Line#D   Network Side           13

   For this example, ifNumber is equal to 5.  Note the following
   description of dsx3LineIndex:  the dsx3LineIndex identifies a DS3/E3
   Interface on a managed device.  If there is an ifEntry that is
   directly associated with this and only this DS3/E3 interface, it
   should have the same value as ifIndex.  Otherwise, number the
   dsx3LineIndices with an unique identifier following the rules of
   choosing a number greater than ifNumber and numbering inside
   interfaces (e.g., equipment side) with even numbers and outside
   interfaces (e.g., network side) with odd numbers.

   If the CSU shelf is managed by itself by a local SNMP Agent, the
   situation would be:

           ifIndex (= dsx3IfIndex)                      dsx3LineIndex

                   1      Line#A     Network Side            1
                   2      Line#A     RouterSide              2
                   3      Line#B     Network Side            3
                   4      Line#B     RouterSide              4
                   5      Line#C     Network Side            5
                   6      Line#C     Router Side             6
                   7      Line#D     Network Side            7
                   8      Line#D     Router Side             8

5.  Appendix B - The delay approach to Unavialable Seconds.

   This procedure is illustrated below for a DS3 C-Bit parity
   application.  Similar rules would apply for other interfaces covered
   by this MIB.  The procedure guarantees that the statistical counters
   are correctly updated at all times, although they lag real time by 10
   seconds.  At the end of each 15 minutes interval the current interval
   counts are transferred to the most recent interval entry and each
   interval is shifted up by one position, with the oldest being
   discarded if necessary in order to make room.  The current interval

Top      Up      ToC       Page 57 
   counts then start over from zero.  Note, however, that the signal
   state calculation does not start afresh at each interval boundary;
   rather, signal state information is retained across interval
   boundaries.

   +----------------------------------------------------------------+
   |           READ COUNTERS & STATUS INFO FROM HARDWARE            |
   |                                                                |
   |BPV EXZ LOS     PCV CCV AIS SEF OOF LOF         FEBE  RAI       |
   +----------------------------------------------------------------+
     |   |   |       |   |   |   |   |   |            |    |
     |   |   |       |   |   |   |   |   |            |    |
     V   V   V       V   V   V   V   V   V            V    V
   +----------------------------------------------------------------+
   | ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE   |
   |                                                                |
   |<------------- NEAR END ---------------->| |<---- FAR END ----->|
   |                                                                |
   |LCV LES PCV CCV PES CES PSES CSES SEFS A/U CCV CES CSES SEFS A/U|
   +----------------------------------------------------------------+
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     V   V   V   V   V   V    V    V    V   |   V   V    V    V   |
   +--------------------------------------+ | +-----------------+ |
   |            ONE-SEC DELAY             | | | ONE-SEC DELAY   | |
   |              (1 OF 10)               | | |   (1 OF 10)     | |
   +--------------------------------------+ | +-----------------+ |
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     /   /   /   /   /   /    /    /    /   /   /   /    /    /   /
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     V   V   V   V   V   V    V    V    V   |   V   V    V    V   |
   +--------------------------------------+ | +-----------------+ |
   |            ONE-SEC DELAY             | | | ONE-SEC DELAY   | |
   |             (10 OF 10)               | | |  (10 OF 10)     | |
   +--------------------------------------+ | +-----------------+ |
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     |   |   |   |   |   |    |    |    |   |   |   |    |    |   |
     V   V   V   V   V   V    V    V    V   V   V   V    V    V   V
   +----------------------------------------------------------------+
   |               UPDATE STATISTICS COUNTERS                       |
   |                                                                |
   |<------------- NEAR END ---------------->| |<---- FAR END ----->|
   |                                                                |
   |LCV LES PCV CCV PES CES PSES CSES SEFS UAS CCV CES CSES SEFS UAS|
   +----------------------------------------------------------------+

   Note that if such a procedure is adopted there is no current interval
   data for the first ten seconds after a system comes up.

Top      Up      ToC       Page 58 
   noSuchInstance must be returned if a management station attempts to
   access the current interval counters during this time.

   It is an implementation-specific matter whether an agent assumes that
   the initial state of the interface is available or unavailable.

6.  Acknowledgments

   This document was produced by the AToM MIB Working Group.  The Editor
   would like to dedicate a special thanks to C. Mike Heard for
   providing a top notch doctor review and many helpful suggestions, and
   to acknowledge D. Fowler, Editor of RFC 2496, T. Cox and K. Tesink
   Editors of RFC 1407.

7.  References

7.1.  Normative References

   [RFC2578]          McCloghrie, K., Perkins, D., and J. Schoenwaelder,
                      "Structure of Management Information Version 2
                      (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC2579]          McCloghrie, K., Perkins, D., and J. Schoenwaelder,
                      "Textual Conventions for SMIv2", STD 58, RFC 2579,
                      April 1999.

   [RFC2580]          McCloghrie, K., Perkins, D., and J. Schoenwaelder,
                      "Conformance Statements for SMIv2", STD 58, RFC
                      2580, April 1999.

   [RFC2863]          McCloghrie, K. and F. Kastenholz, "The Interfaces
                      Group MIB", RFC 2863, June 2000.

   [ANSI-T1.102]      American National Standard for telecommunications
                      - digital hierarchy - electrical interfaces, ANSI
                      T1.102-1987.

   [ANSI-T1.107]      American National Standard for telecommunications
                      - digital hierarchy - formats specification, ANSI
                      T1.107- 1988.

   [ANSI-T1.107a]     ANSI T1.107a-1990.

   [ANSI-T1.404]      American National Standard for telecommunications
                      - Carrier-to-Customer Installation - DS3 Metallic
                      Interface, ANSI T1.404-1989.

Top      Up      ToC       Page 59 
   [ANSI-T1.231]      American National Standard for Telecommunications
                      -- Layer 1 In- Service Digital Transmission
                      Performance Monitoring T1.231, Sept 1993.

   [CCITT-G.751]      CCITT - Digital Multiplex Equipment Operating at
                      the Third Order Bit Rate of 34 368 Kbit/s and the
                      Forth Order Bit Rate of 139 264 Kbit/s and Using
                      Positive Justification, G.751

   [ETSI-T/NA(91)18]  European Telecommunications Standards Institute --
                      ETS "34M" -- Metropolitan Area Network Physical
                      Convergence Layer Procedure for 34.368 Megabits
                      per Second, T/NA(91)18, May 1991.

   [RFC3593]          Tesink, K., "Textual Conventions for MIB Modules
                      Using Performance History Based on 15 Minute
                      Intervals", RFC 3593, September 2003.

   [ITU-T-M.1400]     ITU-T M.1400: Designation For Interconnections
                      Among Network Operators, October 2001.

7.2.  Informative References

   [RFC1213]          McCloghrie, K. and M. Rose, "Management
                      Information Base for Network Management of
                      TCP/IP-based internets:MIB-II", STD 17, RFC 1213,
                      March 1991.

   [RFC1407]          Cox, T. and K. Tesink, "Definitions of Managed
                      Objects for the DS3/E3 Interface Type", RFC 1407,
                      January 1993.

   [RFC2496]          Fowler, D., "Definitions of Managed Object for the
                      DS3/E3 Interface Type", RFC 2496, January 1999.

   [RFC3895]          Nicklass, O., Ed., "Definitions of Managed Objects
                      for the DS1, E1, DS2, and E2 Interface Types", RFC
                      3895, September 2004.

   [RFC3592]          Tesink, K., "Definitions of Managed Objects for
                      the Synchronous Optical Network/Synchronous
                      Digital Hierarchy (SONET/SDH) Interface Type", RFC
                      3592, September 2003.

   [RFC2494]          Fowler, D., "Definitions of Managed Objects for
                      the DS0 and DS0 Bundle Interface Type", RFC 2494,
                      January 1999.

Top      Up      ToC       Page 60 
   [RFC3410]          Case, J., Mundy, R., Partain, D., and B. Stewart,
                      "Introduction and Applicability Statements for
                      Internet-Standard Management Framework", RFC 3410,
                      December 2002.

8.  Security Considerations

   There are a number of management objects defined in this MIB module
   with a MAX-ACCESS clause of read-write.  Such objects may be
   considered sensitive or vulnerable in some network environments.  The
   support for SET operations in a non-secure environment without proper
   protection can have a negative effect on network operations.  The
   specific the objects and their sensitivities/vulnerabilities are as
   follows.

   Setting the following objects to incorrect values may result in
   traffic interruptions:

      dsx3LineType
      dsx3LineCoding
      dsx3SendCode
      dsx3LoopbackConfig
      dsx3TransmitClockSource
      dsx3LineLength
      dsx3Channelization
      dsx3Ds1ForRemoteLoop

   In the case of dsx3LineType, for example, both ends of a DS3/E3 must
   have the same value in order for traffic to flow.  In the case of
   dsx3SendCode and dsx3LoopbackConfig, for another example, traffic may
   stop transmitting when particular loopbacks are applied.

   Setting the following objects to an incorrect value will result in
   the remote end receiving an incorrect Path Identification message,
   which may result in a connectivity inconsistency:

      dsx3FarEndEquipCode
      dsx3FarEndLocationIDCode
      dsx3FarEndFrameIDCode
      dsx3FarEndUnitCode
      dsx3FarEndFacilityIDCode

Top      Up      ToC       Page 61 
   Setting the following object to an incorrect value will not harm the
   traffic, but it may cause a circuit to be mis-identified and thereby
   create difficulties for service personnel when attempting to
   troubleshoot a problem:

      dsx3CircuitIdentifier

   Setting the following object can cause an increase in the number of
   traps received by the network management station:

      dsx3LineStatusChangeTrapEnable

   The readable objects in this MIB module (i.e., the objects with a
   MAX-ACCESS other than not-accessible) may be considered sensitive in
   some environments since, collectively, they provide extensive
   information about the performance of interfaces in DS3/E3 equipment
   or networks and can reveal some aspects of their configuration.  In
   such environments it is important to control even GET and NOTIFY
   access to these objects and possibly to encrypt the values of these
   objects when sending them over the network via SNMP.

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPSec),
   even then, there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the objects
   in this MIB module.

   It is RECOMMENDED that implementers consider the security features as
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module is properly configured to give access to
   the objects only to those principals (users) that have legitimate
   rights to indeed GET or SET (change/create/delete) them.

Top      Up      ToC       Page 62 
9.  Author's Address

   Orly Nicklass (editor)
   RAD Data Communications, Ltd.
   Ziv Tower, 24 Roul Walenberg
   Tel Aviv, Israel, 69719

   Phone: 9723-765-9969
   EMail: orly_n@rad.com

Top      Up      ToC       Page 63 
10.  Full Copyright Statement

   Copyright (C) The Internet Society (2004).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
   REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
   INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
   IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the IETF's procedures with respect to rights in IETF Documents can
   be found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.