As per Relevance of the word encountered, we have this rfc below:
Network Working Group T.
Request for Comments: 1407 K.
Obsoletes: 1233 Bell Communications
January 1993
Definitions of Managed
for the DS3/E3 Interface
Status of this
This RFC specifies an IAB standards track protocol for the
community, and requests discussion and suggestions for improvements
Please refer to the current edition of the "IAB Official
Standards" for the standardization state and status of this protocol
Distribution of this memo is unlimited
This memo defines an extension to the Management Information
(MIB) for use with network management protocols in TCP/IP-
internets. In particular, it defines objects for managing DS3 and E
Interfaces. This document is a companion document with
of Managed Objects for the DS1 Interface Type
This document entirely replaces RFC 1233, which contains
fundamental error: many objects are encoded as Counters that must
encoded as INTEGERs or Gauges. The magnitude of the change
is sufficient that virtually every object changed. Therefore,
MIB documented in RFC 1233 should not be implemented
Table of
1. The Network Management Framework ...................... 2
2. Objects ............................................... 2
2.1 Format of Definitions ................................ 3
2.2 Changes from RFC 1233 ................................ 3
3. Overview .............................................. 5
3.1 Binding between ifIndex and DS3/E3 Interfaces ........ 5
3.2 Objectives of this MIB Module ........................ 7
3.3 DS3/E3 Terminology ................................... 7
3.3.1 Error Events ....................................... 7
3.3.2 Performance Parameters ............................. 8
3.3.3 Performance Defects ................................ 10
3.3.4 Other Terms ........................................ 11
4. Object Definitions .................................... 12
4.1 The DS3/E3 Near End Group ............................ 12
Trunk MIB Working Group [Page 1]
RFC 1407 DS3/E3 MIB January 1993
4.1.1 The DS3/E3 Configuration ........................... 12
4.1.2 The DS3/E3 Current ................................. 18
4.1.3 The DS3/E3 Interval ................................ 21
4.1.4 The DS3/E3 Total ................................... 25
4.2 The DS3 Far End Group ................................ 29
4.2.1 The DS3 Far End Configuration ...................... 29
4.2.2 The DS3 Far End Current ............................ 31
4.2.3 The DS3 Far End Interval ........................... 34
4.2.4 The DS3 Far End Total .............................. 36
4.3 The DS3/E3 Fractional Group .......................... 38
5. Acknowledgments ....................................... 41
6. References ............................................ 41
7. Security Considerations ............................... 43
8. Authors' Addresses .................................... 43
1. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
STD 16/RFC 1155 which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management.
16/RFC 1212 defines a more concise description mechanism, which
wholly consistent with the SMI
RFC 1156 which defines MIB-I, the core set of managed objects
the Internet suite of protocols. STD 17/RFC 1213, defines MIB-II
an evolution of MIB-I based on implementation experience and
operational requirements
STD 15/RFC 1157 which defines the SNMP, the protocol used
network access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2.
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
defined in the SMI. In particular, each object has a name, a syntax
and an encoding. The name is an object identifier,
administratively assigned name, which specifies an object type.
object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the
DESCRIPTOR, to also refer to the object type
Trunk MIB Working Group [Page 2]
RFC 1407 DS3/E3 MIB January 1993
The syntax of an object type defines the abstract data
corresponding to that object type. The ASN.1 language is used
this purpose. However, the SMI [3] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly
for simplicity
The encoding of an object type is simply how that object type
represented using the object type's syntax. Implicitly tied to
notion of an object type's syntax and encoding is how the object
is represented when being transmitted on the network. The
specifies the use of the basic encoding rules of ASN.1 [8],
to the additional requirements imposed by the SNMP
2.1. Format of
Section 4 contains contains the specification of all object
contained in this MIB module. The object types are defined using
conventions defined in the SMI, as amended by the
specified in STD 16, RFC 1212 [13].
2.2. Changes from RFC 1233
This MIB obsoletes RFC 1233. The changes from RFC 1233 are
following
-- This MIB module contains information to
an E3 interface, also
-- This MIB module contains three groups
DS3/E3 Near End Group which is mandatory
DS3 Far End Group which is optional,
DS3 Fractional Group which is optional
-- The DS3 Far End Group is a new group and
configuration information and
that are collected from the far end DS3/E3 interface
Presently, the Far End Group may only be implemented
DS3 systems that use C-bit Parity or SYNTRAN
-- The DS3 Fractional Group is a new group and
modeled after the DS1 Fractional Group
-- ds3CSUIndex has been redefined and
to dsx3LineIndex. This
is the identifier of a DS3/E3 Interface on a device
On a CSU, a single DS3/E3 data stream will cross two DS3/E
interfaces, which have separate dsx3LineIndex values
Trunk MIB Working Group [Page 3]
RFC 1407 DS3/E3 MIB January 1993
-- ds3Index has been redefined and renamed
dsx3IfIndex. This value for
object is equal to the value of ifIndex from the
table of MIB II (STD 17, RFC 1213).
-- The ACCESS for objects in the dsx3ConfigTable
been set to read-write for items that are configurable
-- The dsx3ZeroCoding has been renamed to dsx3LineCoding
-- A new object has been added called dsx3LoopbackConfig
which better describes the loopback capabilities
a DS3/E3 interface on a device
-- The dsx3SendCode object has been updated to
different types of loopback messages
-- A new object has been added called dsx3LineStatus
This object better describes the status (e.g.,
failure state and loopback state) of
DS3/E3 interface
-- A new object has been added called dsx3TransmitClockSource
This object identifies the source for the transmit clock
-- All Counters have been changed to Gauges
-- A Line Errored Seconds object has been added
all near end tables
-- Line Coding Violations are counted instead of
Violations
-- A new Coding Violation counter has been added to
coding violations reported via the C-bits of
and C-bit Parity DS3 applications
The original Coding Violation counter has been
to PCV to mean coding violations reported via the P-bits
This count is also added for symmetry with the far
statistics
-- A new Errored Second counter and Severely Errored
counter has been added to count these performance
via the C-bits of the SYNTRAN and C-bit Parity DS
applications. The original ES and SES counters have
renamed to PES and PSES to mean reported via the P-bits
These counts are also added for symmetry with the far
statistics
Trunk MIB Working Group [Page 4]
RFC 1407 DS3/E3 MIB January 1993
3.
These objects are used when the particular media being used
realize an interface is a DS3/E3 interface. At present, this
to these values of the ifType variable in the Internet-standard MIB
ds3 (30)
The DS3 definitions contained herein are based on the DS
specifications in ANSI T1.102-1987, ANSI T1.107-1988, ANSI T1.107a
1990, and ANSI T1.404-1989 [9,10,10a,11]. The E3
contained herein are based on the E3 specifications in CCITT G.751
[14].
3.1. Binding between ifIndex and DS3/E3
Different physical configurations for the support of SNMP with DS3/E
equipment exist. To accommodate these scenarios, two
indices for DS3/E3 interfaces are introduced in this MIB.
indices are dsx3IfIndex and dsx3LineIndex
External interface scenario: the SNMP Agent represents all
DS3/E3 lines as external interfaces (for example, an Agent
on the device supporting DS3/E3 interfaces directly):
For this scenario, all interfaces are assigned an integer value
to ifIndex, and the following applies
ifIndex=dsx3IfIndex=dsx3LineIndex for all interfaces
The dsx3IfIndex column of the DS3/E3 Configuration table relates
DS3/E3 interface to its corresponding interface (ifIndex) in
Internet-standard MIB (MIB-II STD 17, RFC 1213).
External&Internal interface scenario: the SNMP Agents resides on
host external from the device supporting DS3/E3 interfaces (e.g.,
router). The Agent represents both the host and the DS3/E3 device
The index dsx3LineIndex is used to not only represent the DS3/E
interfaces external from the host/DS3/E3-device combination, but
the DS3/E3 interfaces connecting the host and the DS3/E3 device.
index dsx3IfIndex is always equal to ifIndex
Example
A shelf full of CSUs connected to a Router. An SNMP Agent residing
the router proxies for itself and the CSU. The router has also
Ethernet interface
Trunk MIB Working Group [Page 5]
RFC 1407 DS3/E3 MIB January 1993
+-----+
| | |
| | | +---------------------+
|E | | 44.736 MBPS | ds3 M13 Line#A | ds3 C-bit
|t | R |---------------+ - - - - - - - - - +------>
|h | | | |
|e | O | 44.736 MBPS | ds3 M13 Line#B | ds3 C-bit
|r | |---------------+ - - - - - - - - - - +------>
|n | U | | |
|e | | 44.736 MBPS | ds3 M13 Line#C | ds3 C-bit
|t | T |---------------+ - - - -- -- - - - - +------>
| | | | |
|-----| E | 44.736 MBPS | ds3 M13 Line#D | ds3 C-bit
| | |---------------+ - - - - -- - - - - +------>
| | R | |_____________________|
| | |
| +-----+
The assignment of the index values could for example be
ifIndex (= dsx3IfIndex) dsx3
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
description of dsx3LineIndex: the dsx3LineIndex identifies a DS3/E
Interface on a managed device. If there is an ifEntry that
directly associated with this and only this DS3/E3 interface,
should have the same value as ifIndex. Otherwise, number
dsx3LineIndices with an unique identifier following the rules
choosing a number greater than ifNumber and numbering
interfaces (e.g., equipment side) with even numbers and
interfaces (e.g., network side) with odd numbers
If the CSU shelf is managed by itself by a local SNMP Agent,
situation would be
Trunk MIB Working Group [Page 6]
RFC 1407 DS3/E3 MIB January 1993
ifIndex (= dsx3IfIndex) dsx3
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
3.2. Objectives of this MIB
There are numerous things that could be included in a MIB for DS3/E
signals: the management of multiplexors, CSUs, DSUs, and the like
The intent of this document is to facilitate the common management
all devices with DS3/E3 interfaces. As such, a design decision
made up front to very closely align the MIB with the set of
that can generally be read from DS3/E3 devices that are
deployed
3.3. DS3/E3
The terminology used in this document to describe error conditions
a DS3 interface as monitored by a DS3 device are based on
definitions from the ANSI T1M1.3/92-005R1 draft standard [12].
the definition in this document does not match the definition in
ANSI T1M1.3/92-005R1 draft document, the implementer should
the definition described in this document
3.3.1. Error
Bipolar Violation (BPV) Error
A bipolar violation error event, for B3ZS(HDB3)-
signals, is the occurrence of a pulse of the same
as the previous pulse without being part of the
substitution code, B3ZS(HDB3). For B3ZS(HDB3)-
signals, a bipolar violation error event may also
other error patterns such as: three(four) or
consecutive zeros and incorrect polarity
Excessive Zeros (EXZ) Error
An EXZ is the occurrence of any zero string length
to or greater than 3 for B3ZS, or greater than 4 for HDB3.
Line Coding Violation (LCV) Error
This parameter is a count of both BPVs and
occurring over the accumulation period. An
Trunk MIB Working Group [Page 7]
RFC 1407 DS3/E3 MIB January 1993
increments the LCV by one regardless of the
of the zero string
P-bit Coding Violation (PCV) Error
For all DS3 applications, a coding violation
event is a P-
Parity Error event. A P-bit Parity Error event is
occurrence of a received P-bit code on the DS3 M-
that is not identical to the corresponding locally
calculated code
C-bit Coding Violation (CCV) Error
For C-bit Parity and SYNTRAN DS3 applications, this
the count of coding violations reported via the C-bits
For C-bit Parity, it is a count of CP-bit parity
occurring in the accumulation interval. For SYNTRAN,
is a count of CRC-9 errors occurring in the
interval
3.3.2. Performance
All performance parameters are accumulated in fifteen
intervals and up to 96 intervals (24 hours worth) are kept by
agent. Fewer than 96 intervals of data will be available if
agent has been restarted within the last 24 hours. In addition
there is a rolling 24-hour total of each performance parameter
There is no requirement for an agent to ensure fixed
between the start of a fifteen minute interval and any wall clock
however some agents may align the fifteen minute intervals
quarter hours
Line Errored Seconds (LES
A Line Errored Second is a second
which one or more CVs occurred OR one or more LOS defects
P-bit Errored Seconds (PES
An PES is a second with one or more PCVs
one or more Out of Frame defects OR a detected incoming AIS
This gauge is not incremented when UASs are counted
P-bit Severely Errored Seconds (PSES
A PSES is a second with 44 or more PCVs
one or more Out of Frame defects OR a detected incoming AIS
This gauge is not incremented when UASs are counted
C-bit Errored Seconds (CES
An CES is a second with one or more CCVs
Trunk MIB Working Group [Page 8]
RFC 1407 DS3/E3 MIB January 1993
one or more Out of Frame defects OR a detected incoming AIS
This count is only for the SYNTRAN and C-bit Parity DS
applications. This gauge is not incremented when UASs
counted
C-bit Severely Errored Seconds (CSES
A CSES is a second with 44 or more CCVs
one or more Out of Frame defects OR a detected incoming AIS
This count is only for the SYNTRAN and C-bit Parity DS
applications. This gauge is not incremented when
are counted
Severely Errored Framing Seconds (SEFS
A SEFS is a second with one or more Out of Frame
OR a detected incoming AIS
Unavailable Seconds (UAS
UAS are calculated by counting the number of seconds
the interface is unavailable. The DS3 interface is
to be unavailable from the onset of 10 contiguous PSESs,
the onset of the condition leading to a failure (see
States). If the condition leading to the failure
immediately preceded by one or more contiguous PSESs,
the DS3 interface unavailability starts from the onset
these PSESs. Once unavailable, and if no failure
present, the DS3 interface becomes available at the
of 10 contiguous seconds with no PSESs. Once unavailable
and if a failure is present, the DS3 interface
available at the onset of 10 contiguous seconds with
PSESs, if the failure clearing time is less
or equal to 10 seconds. If the failure clearing time
more than 10 seconds, the DS3 interface becomes
at the onset of 10 contiguous seconds with no PSESs,
the onset period leading to the successful
condition, whichever occurs later. With respect to
DS3 error counts, all counters are
while the DS3 interface is deemed available. While
interface is deemed unavailable, the only count that
incremented is UASs
A special case exists when the 10 or more second
crosses the 900 second statistics window boundary, as
foregoing description implies that the PSES and
counters must be adjusted when the Unavailable
State is entered. Clearly, successive GETs of
affected dsx3IntervalPSESs and dsx3IntervalUASs
will return differing values if the first GET
during the first few seconds of the window. This
Trunk MIB Working Group [Page 9]
RFC 1407 DS3/E3 MIB January 1993
viewed as an unavoidable side-effect of selecting
presently defined managed objects as a basis for
memo
3.3.3. Performance
Failure States
The Remote Alarm Indication (RAI) failure, in
applications, is declared after
the Yellow Alarm Signal on the alarm channel. See
T1.107a-1990 [10]. The Remote Alarm Indication failure
in C-bit Parity DS3 applications, is
as soon as the preqsence of either one or two alarm
are detected on then Far End Alarm Channel. See [10].
The Remote Alarm Indication failure may also be
after detecting the far-end SEF/AIS defect (aka yellow).
The Remote Alarm Indication failure is cleared as soon
the presence of the any of the above alarms are removed
Also, the incoming failure state is declared when a
persists for at least 2-10 seconds. The defects
the following: Loss of Signal (LOS), an Out of Frame (OOF
or an incoming Alarm Indication Signal (AIS).
The Failure State is cleared when the defect is
for less than or equal to 20 seconds
Far End SEF/AIS defect (aka yellow
A Far End SEF/AIS defect is the occurrence of the two X-
in a M-frame set to zero. The Far End SEF/AIS defect
terminated when the two X-bits in a M-frame are set
one
Out of Frame (OOF)
A DS3 OOF defect is detected when any three or more
in sixteen or fewer consecutive F-bits occur within a DS
M-frame. An OOF defect may also be called a
Errored Frame (SEF) defect. An OOF defect is cleared
reframe occurs. A DS3 Loss of Frame (LOF) failure
declared when the DS3 OOF defect is consistent for 2 to 10
seconds. The DS3 OOF defect ends when reframe occurs
The DS3 LOF failure is cleared when the DS3
defect is absent for 10 to 20 seconds
An E3 OOF defect is detected when four consecutive
alignment signals have been incorrectly received in
predicted positions in an E3 signal. E3 frame
occurs when the presence of three consecutive
alignment signals have been detected
Trunk MIB Working Group [Page 10]
RFC 1407 DS3/E3 MIB January 1993
Loss of Signal (LOS)
The DS3 LOS defect is declared upon observing 175 +/- 75
contiguous pulse positions with no pulses of
positive or negative polarity
The DS3 LOS defect is terminated upon observing an
pulse density of at least 33% over a period of 175 +/- 75
contiguous pulse positions starting with the receipt of
pulse
Alarm Indication Signal (AIS)
The DS3 AIS is framed with "stuck stuffing." This
that it has a valid M-subframe alignments bits, M-
alignment bits, and P bits. The information bits are
to a 1010... sequence, starting with a one (1) after
M-subframe alignment bit, M-frame alignment bit, X bit,
bit, and C bit. The C bits are all set to zero
what is called "stuck stuffing." The X bits are set
one. The DS3 AIS defect is declared after DS3 AIS
present in contiguous M-frames for a time equal to
greater than T, where 0.2 ms <= T <= 100 ms
The DS3 AIS defect is terminated after AIS is absent
contiguous M-frames for a time equal to or greater than T
The E3 binary content of the AIS is nominally a
stream of ones. AIS detection and the application
consequent actions, should be completed within a
limit of 1 ms
3.3.4. Other
Circuit
This is a character string specified by the
vendor, and is useful when communicating with the
during the troubleshooting process
Trunk MIB Working Group [Page 11]
RFC 1407 DS3/E3 MIB January 1993
4. Object
RFC1407-MIB DEFINITIONS ::=
FROM RFC1155-
DisplayString,
FROM RFC1213-
OBJECT-
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE
-- as defined in RFC 1212.
ds3 OBJECT IDENTIFIER ::= { transmission 30 }
-- The DS3/E3 Near End
-- Implementation of this group is mandatory for
-- systems that attach to a DS3/E3 Interface
-- The DS3/E3 Near End Group consists of four tables
-- DS3/E3
-- DS3/E3
-- DS3/E3
-- DS3/E3
-- the DS3/E3
dsx3ConfigTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3/E3 Configuration table."
::= { ds3 5 }
dsx3ConfigEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3/E3 Configuration table."
INDEX { dsx3LineIndex }
::= { dsx3ConfigTable 1 }
Trunk MIB Working Group [Page 12]
RFC 1407 DS3/E3 MIB January 1993
Dsx3ConfigEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
DisplayString
dsx3
INTEGER
dsx3
INTEGER
dsx3
}
dsx3LineIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"This object is the identifier of a DS3/E
Interface on a managed device. If there is
ifEntry that is directly associated with
and only this DS3/E3 interface, it should
the same value as ifIndex. Otherwise,
the dsx3LineIndices with an unique
following the rules of choosing a number
is greater than ifNumber and numbering
inside interfaces (e.g., equipment side)
even numbers and outside interfaces (e.g
network side) with odd numbers."
::= { dsx3ConfigEntry 1 }
dsx3IfIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
Trunk MIB Working Group [Page 13]
RFC 1407 DS3/E3 MIB January 1993
"This value for this object is equal to
value of ifIndex from the Interfaces table
MIB II (RFC 1213)."
::= { dsx3ConfigEntry 2 }
dsx3TimeElapsed OBJECT-
SYNTAX INTEGER (0..899)
ACCESS read-
STATUS
"The number of seconds that have elapsed
the beginning of the near end current error
measurement period."
::= { dsx3ConfigEntry 3 }
dsx3ValidIntervals OBJECT-
SYNTAX INTEGER (0..96)
ACCESS read-
STATUS
"The number of previous near end intervals
which valid data was collected. The value will
96 unless the interface was brought online
the last 24 hours, in which case the value will
the number of complete 15 minute near
intervals since the interface has been online."
::= { dsx3ConfigEntry 4 }
dsx3LineType OBJECT-
SYNTAX INTEGER {
dsx3other(1),
dsx3M23(2),
dsx3SYNTRAN(3),
dsx3CbitParity(4),
dsx3ClearChannel(5),
e3other(6),
e3Framed(7),
e3Plcp(8)
}
ACCESS read-
STATUS
"This variable indicates the variety of DS3 C-
or E3
implementing this interface. The type
interface affects the interpretation of
usage and error statistics
Trunk MIB Working Group [Page 14]
RFC 1407 DS3/E3 MIB January 1993
The rate of DS3 is 44.736 Mbps and E3
34.368 Mbps
The dsx3ClearChannel value means that the C-
are not used except for sending/
AIS
The values, in sequence, describe
TITLE: SPECIFICATION
dsx3M23 ANSI T1.107-1988
dsx3SYNTRAN ANSI T1.107-1988
dsx3CbitParity ANSI T1.107a-1989
dsx3ClearChannel ANSI T1.102-1987
e3Framed CCITT G.751
e3Plcp ETSI T/NA(91)18."
::= { dsx3ConfigEntry 5 }
dsx3LineCoding OBJECT-
SYNTAX INTEGER {
dsx3Other(1),
dsx3B3ZS(2),
e3HDB3(3)
}
ACCESS read-
STATUS
"This variable describes the variety of Zero
Suppression used on this interface, which in
affects a number of its characteristics
dsx3B3ZS and e3HDB3 refer to the use of
patterns of normal bits and bipolar
which are used to replace sequences of zero
of a specified length."
::= { dsx3ConfigEntry 6 }
dsx3SendCode OBJECT-
SYNTAX INTEGER {
dsx3SendNoCode(1),
dsx3SendLineCode(2),
dsx3SendPayloadCode(3),
dsx3SendResetCode(4),
dsx3SendDS1LoopCode(5),
dsx3SendTestPattern(6)
}
ACCESS read-
STATUS
Trunk MIB Working Group [Page 15]
RFC 1407 DS3/E3 MIB January 1993
"This variable indicates what type of code
being sent across the DS3/E3 interface by
device. (These are optional for E3 interfaces.)
The values mean
dsx3
sending looped or normal
dsx3
sending a request for a line
dsx3
sending a request for a payload
(i.e., all DS1/E1s in a DS3/E3 frame
dsx3
sending a loopback deactivation
dsx3SendDS1
requesting to loopback a particular DS1/E
within a DS3/E3
dsx3
sending a test pattern."
::= { dsx3ConfigEntry 7 }
dsx3CircuitIdentifier OBJECT-
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-
STATUS
"This variable contains the transmission vendor'
circuit identifier, for the purpose
facilitating troubleshooting."
::= { dsx3ConfigEntry 8 }
dsx3LoopbackConfig OBJECT-
SYNTAX INTEGER {
dsx3NoLoop(1),
dsx3PayloadLoop(2),
dsx3LineLoop(3),
dsx3OtherLoop(4)
}
ACCESS read-
STATUS
"This variable represents the loopback
of the DS3/E3 interface
Trunk MIB Working Group [Page 16]
RFC 1407 DS3/E3 MIB January 1993
The values mean
dsx3
Not in the loopback state. A device that
not capable of performing a loopback
the interface shall always return this
it's value
dsx3
The received signal at this interface is
through the device
Typically the received
is looped back for retransmission after it
passed through the device's framing function
dsx3
The received signal at this interface does
go through the device (minimum penetration)
is looped back out
dsx3
Loopbacks that are not defined here."
::= { dsx3ConfigEntry 9 }
dsx3LineStatus OBJECT-
SYNTAX INTEGER (1..1023)
ACCESS read-
STATUS
"This variable indicates
Line Status of the interface
It contains loopback state
and failure state information
The dsx3LineStatus is a bit map
as a sum, therefore
it can represent multiple
and a loopback (see dsx3LoopbackConfig
for the type of loopback
simultaneously
The dsx3NoAlarm should be set if and only
no other flag is set
The various bit positions are
1 dsx3NoAlarm No alarm
2 dsx3RcvRAIFailure Receiving Yellow/
Alarm
4 dsx3XmitRAIAlarm Transmitting Yellow/
Alarm
Trunk MIB Working Group [Page 17]
RFC 1407 DS3/E3 MIB January 1993
8 dsx3RcvAIS Receiving AIS failure
16 dsx3XmitAIS Transmitting
32 dsx3LOF Receiving LOF failure
64 dsx3LOS Receiving LOS failure
128 dsx3LoopbackState Looping the received
256 dsx3RcvTestCode Receiving a Test
512 dsx3OtherFailure any line status not
here
::= { dsx3ConfigEntry 10 }
dsx3TransmitClockSource OBJECT-
SYNTAX INTEGER {
loopTiming(1),
localTiming(2),
throughTiming(3)
}
ACCESS read-
STATUS
"The source of Transmit Clock
is derived from the recovered receive clock
another DS3 interface."
::= { dsx3ConfigEntry 11 }
-- the DS3/E3
-- The DS3/E3 current table contains various statistics
-- collected for the current 15 minute interval
dsx3CurrentTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3/E3 Current table."
::= { ds3 6 }
dsx3CurrentEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3/E3 Current table."
INDEX { dsx3CurrentIndex }
::= { dsx3CurrentTable 1 }
Trunk MIB Working Group [Page 18]
RFC 1407 DS3/E3 MIB January 1993
Dsx3CurrentEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
}
dsx3CurrentIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3/E3 interface to which this entry
applicable. The interface identified by
particular value of this index is the
interface as identified by the same value
dsx3LineIndex object instance."
::= { dsx3CurrentEntry 1 }
dsx3CurrentPESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds, encountered by a DS3 interface
the current 15 minute interval."
::= { dsx3CurrentEntry 2 }
Trunk MIB Working Group [Page 19]
RFC 1407 DS3/E3 MIB January 1993
dsx3CurrentPSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Severely Errored Seconds, encountered by a DS
interface in the current 15 minute interval."
::= { dsx3CurrentEntry 3 }
dsx3CurrentSEFSs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds, encountered by
DS3/E3 interface in the current 15
interval."
::= { dsx3CurrentEntry 4 }
dsx3CurrentUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds, encountered by a DS
interface in the current 15 minute interval."
::= { dsx3CurrentEntry 5 }
dsx3CurrentLCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of
Coding Violations encountered by a DS3/E
interface in the current 15 minute interval."
::= { dsx3CurrentEntry 6 }
dsx3CurrentPCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations, encountered by a DS3
Trunk MIB Working Group [Page 20]
RFC 1407 DS3/E3 MIB January 1993
in the current 15 minute interval."
::= { dsx3CurrentEntry 7 }
dsx3CurrentLESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of Line Errored Seconds encountered
a DS3/E3 interface in the current 15
interval."
::= { dsx3CurrentEntry 8 }
dsx3CurrentCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Coding Violations
by a DS3 interface in the current 15
interval."
::= { dsx3CurrentEntry 9 }
dsx3CurrentCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Errored Seconds
by a DS3 interface in the current 15
interval."
::= { dsx3CurrentEntry 10 }
dsx3CurrentCSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Severely Errored
encountered by a DS3 interface in the current 15
minute interval."
::= { dsx3CurrentEntry 11 }
-- the DS3/E3
-- The DS3/E3 Interval Table contains various
-- collected by each DS3/E3 Interface over the previous 24
Trunk MIB Working Group [Page 21]
RFC 1407 DS3/E3 MIB January 1993
-- hours of operation. The past 24 hours are broken into 96
-- completed 15 minute intervals
dsx3IntervalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3/E3 Interval table."
::= { ds3 7 }
dsx3IntervalEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3/E3 Interval table."
INDEX { dsx3IntervalIndex, dsx3IntervalNumber }
::= { dsx3IntervalTable 1 }
Dsx3IntervalEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
}
Trunk MIB Working Group [Page 22]
RFC 1407 DS3/E3 MIB January 1993
dsx3IntervalIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3/E3 interface to which this entry
applicable. The interface identified by
particular value of this index is the
interface as identified by the same value
dsx3LineIndex object instance."
::= { dsx3IntervalEntry 1 }
dsx3IntervalNumber OBJECT-
SYNTAX INTEGER (1..96)
ACCESS read-
STATUS
"A number between 1 and 96, where 1 is the
recently completed 15 minute interval and 96
the least recently completed 15 minutes
(assuming that all 96 intervals are valid)."
::= { dsx3IntervalEntry 2 }
dsx3IntervalPESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds, encountered by a DS3 interface
one of the previous 96, individual 15 minute
intervals."
::= { dsx3IntervalEntry 3 }
dsx3IntervalPSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Severely Errored Seconds, encountered by a DS
interface in one of the previous 96, individual 15
minute, intervals."
::= { dsx3IntervalEntry 4 }
dsx3IntervalSEFSs OBJECT-
SYNTAX
Trunk MIB Working Group [Page 23]
RFC 1407 DS3/E3 MIB January 1993
ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds, encountered by
DS3/E3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3IntervalEntry 5 }
dsx3IntervalUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds, encountered by a DS
interface in one of the previous 96, individual 15
minute, intervals."
::= { dsx3IntervalEntry 6 }
dsx3IntervalLCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of
Coding Violations encountered by a DS3/E
interface in one of the previous 96, individual 15
minute, intervals."
::= { dsx3IntervalEntry 7 }
dsx3IntervalPCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations, encountered by a DS3
in one of the previous 96, individual 15 minute
intervals."
::= { dsx3IntervalEntry 8 }
dsx3IntervalLESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of Line Errored Seconds (BPVs
Trunk MIB Working Group [Page 24]
RFC 1407 DS3/E3 MIB January 1993
illegal zero sequences) encountered by a DS3/E
interface in one of the previous 96,
15 minute, intervals."
::= { dsx3IntervalEntry 9 }
dsx3IntervalCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Coding Violations
by a DS3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3IntervalEntry 10 }
dsx3IntervalCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Errored Seconds
by a DS3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3IntervalEntry 11 }
dsx3IntervalCSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Severely Errored
encountered by a DS3 interface in one of
previous 96, individual 15 minute, intervals."
::= { dsx3IntervalEntry 12 }
-- the DS3/E3
-- The DS3/E3 Total Table contains the cumulative sum of
-- various statistics for the 24 hour period preceding
-- current interval
dsx3TotalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3/E3 Total table. 24 hour interval."
Trunk MIB Working Group [Page 25]
RFC 1407 DS3/E3 MIB January 1993
::= { ds3 8 }
dsx3TotalEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3/E3 Total table."
INDEX { dsx3TotalIndex }
::= { dsx3TotalTable 1 }
Dsx3TotalEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
}
dsx3TotalIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3/E3 interface to which this entry
applicable. The interface identified by
particular value of this index is the
interface as identified by the same value
dsx3LineIndex object instance."
Trunk MIB Working Group [Page 26]
RFC 1407 DS3/E3 MIB January 1993
::= { dsx3TotalEntry 1 }
dsx3TotalPESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds, encountered by a DS3 interface
the previous 24 hour interval
::= { dsx3TotalEntry 2 }
dsx3TotalPSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Severely Errored Seconds, encountered by a DS
interface in the previous 24 hour interval."
::= { dsx3TotalEntry 3 }
dsx3TotalSEFSs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds, encountered by
DS3/E3 interface in the previous 24
interval."
::= { dsx3TotalEntry 4 }
dsx3TotalUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds, encountered by a DS
interface in the previous 24 hour interval."
::= { dsx3TotalEntry 5 }
dsx3TotalLCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
Trunk MIB Working Group [Page 27]
RFC 1407 DS3/E3 MIB January 1993
"The counter associated with the number of
Coding Violations encountered by a DS3/E
interface in the previous 24 hour interval."
::= { dsx3TotalEntry 6 }
dsx3TotalPCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations, encountered by a DS3
in the previous 24 hour interval."
::= { dsx3TotalEntry 7 }
dsx3TotalLESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of Line Errored Seconds (BPVs
illegal zero sequences) encountered by a DS3/E
interface in the previous 24 hour interval."
::= { dsx3TotalEntry 8 }
dsx3TotalCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Coding Violations
by a DS3 interface in the previous 24
interval."
::= { dsx3TotalEntry 9 }
dsx3TotalCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of C-bit Errored Seconds
by a DS3 interface in the previous 24
interval."
::= { dsx3TotalEntry 10 }
dsx3TotalCSESs OBJECT-
SYNTAX
ACCESS read-
Trunk MIB Working Group [Page 28]
RFC 1407 DS3/E3 MIB January 1993
STATUS
"The number of C-bit Severely Errored
encountered by a DS3 interface in the previous 24
hour interval."
::= { dsx3TotalEntry 11 }
-- The DS3 Far End
-- Implementation of this group is optional for all
-- that attach to a DS3 Interface
-- However, only C-bit Parity and SYNTRAN DS3
-- have the capability (option) of providing this information
-- The DS3 Far End Group consists of four tables
-- DS3 Far End
-- DS3 Far End
-- DS3 Far End
-- DS3 Far End
-- The DS3 Far End Configuration Table
-- configuration
-- reported in the C-bits from the remote end
dsx3FarEndConfigTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3 Far End Configuration table."
::= { ds3 9 }
dsx3FarEndConfigEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3 Far End Configuration table."
INDEX { dsx3FarEndLineIndex }
::= { dsx3FarEndConfigTable 1 }
Dsx3FarEndConfigEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
Trunk MIB Working Group [Page 29]
RFC 1407 DS3/E3 MIB January 1993
DisplayString
dsx3
DisplayString
dsx3
DisplayString
dsx3
DisplayString
dsx3
}
dsx3FarEndLineIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3
to which this entry is applicable.
interface identified by a particular value
this index is the same interface as
by the same value an dsx3LineIndex
instance."
::= { dsx3FarEndConfigEntry 1 }
dsx3FarEndEquipCode OBJECT-
SYNTAX DisplayString (SIZE (0..10))
ACCESS read-
STATUS
"This is the Far End Equipment Identification
that describes the specific piece of equipment
It is sent within the
Identification Message."
::= { dsx3FarEndConfigEntry 2 }
dsx3FarEndLocationIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..11))
ACCESS read-
STATUS
"This is the Far End Location Identification
that describes the specific location of
equipment
It is sent within the
Identification Message."
::= { dsx3FarEndConfigEntry 3 }
Trunk MIB Working Group [Page 30]
RFC 1407 DS3/E3 MIB January 1993
dsx3FarEndFrameIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..10))
ACCESS read-
STATUS
"This is the Far End Frame Identification
that identifies where the equipment is
within a building at a given location
It is sent within the
Identification Message."
::= { dsx3FarEndConfigEntry 4 }
dsx3FarEndUnitCode OBJECT-
SYNTAX DisplayString (SIZE (0..6))
ACCESS read-
STATUS
"This is the Far End
that identifies the equipment location within a bay
It is sent within the
Identification Message."
::= { dsx3FarEndConfigEntry 5 }
dsx3FarEndFacilityIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..38))
ACCESS read-
STATUS
"This code identifies a specific Far End DS3 path
It is sent within the
Identification Message."
::= { dsx3FarEndConfigEntry 6 }
-- The DS3 Far End
-- The DS3 Far End Current table contains various
-- being collected for the current 15 minute interval
-- The statistics are collected from the far end block
-- code within the C-bits
dsx3FarEndCurrentTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3 Far End Current table."
::= { ds3 10 }
Trunk MIB Working Group [Page 31]
RFC 1407 DS3/E3 MIB January 1993
dsx3FarEndCurrentEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3 Far End Current table."
INDEX { dsx3FarEndCurrentIndex }
::= { dsx3FarEndCurrentTable 1 }
Dsx3FarEndCurrentEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
INTEGER
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
}
dsx3FarEndCurrentIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3
to which this entry is applicable. The
identified by a particular value of this index
the same interface as identified by the same
an dsx3LineIndex object instance."
::= { dsx3FarEndCurrentEntry 1 }
dsx3FarEndTimeElapsed OBJECT-
SYNTAX INTEGER (0..899)
ACCESS read-
STATUS
"The number of seconds that have elapsed since
beginning of the far end current error-
period."
Trunk MIB Working Group [Page 32]
RFC 1407 DS3/E3 MIB January 1993
::= { dsx3FarEndCurrentEntry 2 }
dsx3FarEndValidIntervals OBJECT-
SYNTAX INTEGER (0..96)
ACCESS read-
STATUS
"The number of previous far end intervals
which valid data was collected. The value will
96 unless the interface was brought online
the last 24 hours, in which case the value will
the number of complete 15 minute far end
since the interface has been online."
::= { dsx3FarEndCurrentEntry 3 }
dsx3FarEndCurrentCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of
Far End C-bit Errored Seconds encountered by a DS
interface in the current 15 minute interval."
::= { dsx3FarEndCurrentEntry 4 }
dsx3FarEndCurrentCSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End C-bit Severely Errored
encountered by a DS3 interface in the current 15
minute interval."
::= { dsx3FarEndCurrentEntry 5 }
dsx3FarEndCurrentCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End C-bit Coding Violations reported
the far end block error
encountered by
DS3 interface in the current 15 minute interval."
::= { dsx3FarEndCurrentEntry 6 }
Trunk MIB Working Group [Page 33]
RFC 1407 DS3/E3 MIB January 1993
dsx3FarEndCurrentUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End unavailable
encountered by
DS3 interface in the current 15 minute interval."
::= { dsx3FarEndCurrentEntry 7 }
-- The DS3 Far End
-- The DS3 Far End Interval Table contains various
-- collected by each DS3 interface over the previous 24
-- hours of operation. The past 24 hours are broken into 96
-- completed 15 minute intervals
dsx3FarEndIntervalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3 Far End Interval table."
::= { ds3 11 }
dsx3FarEndIntervalEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3
End Interval table."
INDEX { dsx3FarEndIntervalIndex
dsx3FarEndIntervalNumber }
::= { dsx3FarEndIntervalTable 1 }
Dsx3FarEndIntervalEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
Trunk MIB Working Group [Page 34]
RFC 1407 DS3/E3 MIB January 1993
dsx3
Gauge
dsx3
}
dsx3FarEndIntervalIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3
to which this entry is applicable.
interface identified by a particular value
this index is the same interface as
by the same value an dsx3LineIndex
instance."
::= { dsx3FarEndIntervalEntry 1 }
dsx3FarEndIntervalNumber OBJECT-
SYNTAX INTEGER (1..96)
ACCESS read-
STATUS
"A number between 1 and 96, where 1 is the
recently completed 15 minute interval and 96
the least recently completed 15
interval (assuming that all 96 intervals
valid)."
::= { dsx3FarEndIntervalEntry 2 }
dsx3FarEndIntervalCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End C-bit Errored Seconds
by a DS3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3FarEndIntervalEntry 3 }
dsx3FarEndIntervalCSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
Trunk MIB Working Group [Page 35]
RFC 1407 DS3/E3 MIB January 1993
"The counter associated with the number
Far End C-bit Severely Errored
encountered by a DS3 interface in one of
previous 96, individual 15 minute, intervals."
::= { dsx3FarEndIntervalEntry 4 }
dsx3FarEndIntervalCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End C-bit Coding Violations reported
the far end block error
encountered by
DS3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3FarEndIntervalEntry 5 }
dsx3FarEndIntervalUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End unavailable
encountered by
DS3 interface in one of the previous 96,
individual 15 minute, intervals."
::= { dsx3FarEndIntervalEntry 6 }
-- The DS3 Far End
-- The DS3 Far End Total Table contains the cumulative
-- of the various statistics for the 24 hour period
-- the current interval
dsx3FarEndTotalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3 Far End Total table. 24 hour interval."
::= { ds3 12 }
dsx3FarEndTotalEntry OBJECT-
SYNTAX Dsx3
Trunk MIB Working Group [Page 36]
RFC 1407 DS3/E3 MIB January 1993
ACCESS not-
STATUS
"An entry in the DS3 Far End Total table."
INDEX { dsx3FarEndTotalIndex }
::= { dsx3FarEndTotalTable 1 }
Dsx3FarEndTotalEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
Gauge
dsx3
Gauge
dsx3
Gauge
dsx3
}
dsx3FarEndTotalIndex OBJECT-
SYNTAX INTEGER (1..65535)
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3
to which this entry is applicable. The
identified by a particular value of this index
the same interface as identified by the same
an dsx3LineIndex object instance."
::= { dsx3FarEndTotalEntry 1 }
dsx3FarEndTotalCESs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number of
End C-bit Errored Seconds encountered by a DS
interface in the previous 24 hour interval."
::= { dsx3FarEndTotalEntry 2 }
dsx3FarEndTotalCSESs OBJECT-
SYNTAX
ACCESS read-
STATUS
Trunk MIB Working Group [Page 37]
RFC 1407 DS3/E3 MIB January 1993
"The counter associated with the number
Far End C-bit Severely Errored
encountered by a DS3 interface in the previous 24
hour interval."
::= { dsx3FarEndTotalEntry 3 }
dsx3FarEndTotalCCVs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End C-bit Coding Violations reported via
far end block error
encountered by
DS3 interface in the previous 24 hour interval."
::= { dsx3FarEndTotalEntry 4 }
dsx3FarEndTotalUASs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The counter associated with the number
Far End unavailable
encountered by
DS3 interface in the previous 24 hour interval."
::= { dsx3FarEndTotalEntry 5 }
-- the DS3/E3 Fractional
-- Implementation of this group is optional. It is
-- for those systems dividing a DS3/E3 into
-- containing different data streams that are of
-- interest
-- The DS3/E3 fractional table identifies which DS3/E
-- channels associated with a CSU are being used
-- support a logical interface, i.e., an entry in
-- interfaces table from the Internet-standard MIB
-- For example, consider a DS3 device with 4 high speed
-- carrying router traffic, a feed for voice, a feed
-- video, and a synchronous channel for a non-
-- protocol
-- We might describe the allocation of channels, in
Trunk MIB Working Group [Page 38]
RFC 1407 DS3/E3 MIB January 1993
-- 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, dsx3SYNTRAN, dsx3CbitParity,
-- 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)
-- directly to the equivalently numbered time-slots
dsx3FracTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
ACCESS not-
STATUS
"The DS3 Fractional table."
::= { ds3 13 }
dsx3FracEntry OBJECT-
SYNTAX Dsx3
ACCESS not-
STATUS
"An entry in the DS3 Fractional table."
INDEX { dsx3FracIndex, dsx3FracNumber }
::= { dsx3FracTable 1 }
Dsx3FracEntry ::=
SEQUENCE {
dsx3
INTEGER
dsx3
INTEGER
Trunk MIB Working Group [Page 39]
RFC 1407 DS3/E3 MIB January 1993
dsx3
}
dsx3FracIndex OBJECT-
SYNTAX INTEGER (1..'7fffffff'h
ACCESS read-
STATUS
"The index value which uniquely identifies
DS3 interface to which this entry is
The interface identified by a
value of this index is the same interface
identified by the same value an dsx3
object instance."
::= { dsx3FracEntry 1 }
dsx3FracNumber OBJECT-
SYNTAX INTEGER (1..31)
ACCESS read-
STATUS
"The channel number for this entry."
::= { dsx3FracEntry 2 }
dsx3FracIfIndex OBJECT-
SYNTAX INTEGER (1..'7fffffff'h
ACCESS read-
STATUS
"An index value that uniquely identifies
interface. The interface identified by a
value of this index is the same
as identified by the same value an
object instance. If no interface is currently
a channel, the value should be zero. If
single interface occupies more than one
slot, that ifIndex value will be found in
time slots."
::= { dsx3FracEntry 3 }
Trunk MIB Working Group [Page 40]
RFC 1407 DS3/E3 MIB January 1993
5.
This document was produced by the Trunk MIB Working Groups
Tracy Cox
Fred Baker Advanced Computer
James Watt
Bill Versteeg Versteeg
Steve Buchko
Greg Calmainis
Kaj Tesink
Al Bryenton Bell Northern
Tom Easterday
John Labbe Merit
Chris Sullivan Gandalf
Grant Hall Gandalf
John Guerrero Digital
Rich Bradford
Kurt Luoto Digital
Myron Hattig
Ed Pring
Larry Marks
Kurt Hall Clear Communications Corp
Jason Perreault Coral Network Corp
Paul Farah T3
George Kajos Coral Network Corp
6.
[1] Cerf, V., "IAB Recommendations for the Development of
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, Performance Systems International, Hughes LAN Systems,
1990.
[4] McCloghrie K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
Trunk MIB Working Group [Page 41]
RFC 1407 DS3/E3 MIB January 1993
[6] McCloghrie K., and M. Rose, Editors, "Management Information
for Network Management of TCP/IP-based internets", STD 17,
1213, Performance Systems International, March 1991.
[7] Information 