As per Relevance of the word associated, we have this rfc below:
Network Working Group D. Fowler,
Request for Comments: 2496 Newbridge
Obsoletes: 1407 January 1999
Category: Standards
Definitions of Managed Objects for the DS3/E3 Interface
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes objects used for managing DS3 and E
interfaces. This document is a companion document with
of Managed Objects for the DS0 (RFC 2494 [25]), DS1/E1/DS2/E2 (
2495 [17]), and the work in progress SONET/SDH Interface Types
This memo specifies a MIB module in a manner that is both
to the SNMPv2 SMI, and semantically identical to the peer SNMPv
definitions
Table of
1 The SNMP Management Framework ................................ 2
1.1 Changes from RFC1407 ....................................... 3
2 Overview ..................................................... 4
2.1 Use of ifTable for DS3 Layer ............................... 5
2.2 Usage Guidelines ........................................... 5
2.2.1 Usage of ifStackTable .................................... 5
2.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 7
2.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 7
2.2.4 Usage of Loopbacks ....................................... 8
2.3 Objectives of this MIB Module .............................. 9
2.4 DS3/E3 Terminology ......................................... 9
2.4.1 Error Events ............................................. 10
2.4.2 Performance Parameters ................................... 10
Fowler, Ed. Standards Track [Page 1]
RFC 2496 DS3/E3 MIB January 1999
2.4.3 Performance Defects ...................................... 13
2.4.4 Other Terms .............................................. 15
3 Object Definitions ........................................... 15
3.1 The DS3/E3 Near End Group .................................. 16
3.1.1 The DS3/E3 Configuration Table ........................... 16
3.1.2 The DS3/E3 Current Table ................................. 25
3.1.3 The DS3/E3 Interval Table ................................ 28
3.1.4 The DS3/E3 Total ......................................... 31
3.2 The DS3 Far End Group ...................................... 34
3.2.1 The DS3 Far End Configuration ............................ 35
3.2.2 The DS3 Far End Current .................................. 37
3.2.3 The DS3 Far End Interval Table ........................... 39
3.2.4 The DS3 Far End Total .................................... 41
3.3 The DS3/E3 Fractional Table ................................ 43
3.4 The DS3 Trap Group ......................................... 46
3.5 Conformance Groups ......................................... 46
4 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 51
5 Appendix B - The delay approach to Unavialable Seconds. ..... 54
6 Intellectual Property ........................................ 56
7 Acknowledgments .............................................. 56
8 References ................................................... 56
9 Security Considerations ...................................... 58
10 Author's Address ............................................ 59
11 Full Copyright Statement .................................... 60
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in RFC 1902 [5],
1903 [6] and RFC 1904 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9]
RFC 1906 [10]. The third version of the message protocol
called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11]
RFC 2274 [12].
Fowler, Ed. Standards Track [Page 2]
RFC 2496 DS3/E3 MIB January 1999
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14]
the view-based access control mechanism described in RFC 2275
[15]. Managed objects are accessed via a virtual
store, termed the Management Information Base or MIB.
in the MIB are defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
A MIB conforming to the SMIv1 can be produced through
appropriate translations. The resulting translated MIB must
semantically equivalent, except where objects or events
omitted because no translation is possible (use of Counter64).
Some machine readable information in SMIv2 will be
into textual descriptions in SMIv1 during the
process. However, this loss of machine readable information
not considered to change the semantics of the MIB
1.1. Changes from RFC1407
This MIB obsoletes RFC1407. The changes from RFC1407 are
following
(1) The Fractional Table has been
(2) This document uses SMIv
(3) Values are given for ifTable and
(4) Example usage of ifStackTable is
(5) dsx3IfIndex has been
(6) The definition of valid intervals has been
for the case where the agent proxied for other devices.
particular, the treatment of missing intervals has
clarified
(7) An inward loopback has been added
(8) Additional lineStatus bits have been added for Near
in Unavailable Signal State, Carrier Equipment Out
Service, DS@ Payload AIS, and DS@ Performance
Fowler, Ed. Standards Track [Page 3]
RFC 2496 DS3/E3 MIB January 1999
(9) A read-write line Length object has been added
(10) Added a lineStatus last change, trap and enabler
(11) Textual Conventions for statistics objects
been used
(12) A new object, dsx3LoopbackStatus, has been introduced
reflect the loopbacks established on a DS3/E3 interface
the source to the requests. dsx3LoopbackConfig
to be the desired loopback state while dsx3
reflects the actual state
(13) A dual loopback has been added to allow the setting of
inward loopback and a line loopback at the same time
(14) An object has been added to indicated whether or not
is a channelized DS3/E3.
(15) A new object has been added to indicate which DS1 is to
for remote loopback
2.
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 [8,9,9a,10]. The E3 definitions
herein are based on the E3 specifications in CCITT G.751 [12].
Fowler, Ed. Standards Track [Page 4]
RFC 2496 DS3/E3 MIB January 1999
2.1. Use of ifTable for DS3
Only the ifGeneralGroup needs to be supported
ifTable Object Use for DS3
======================================================================
ifIndex Interface index
ifDescr See interfaces MIB [5]
ifType ds3(30)
ifSpeed Speed of line
DS3 - 44736000
E3 - 34368000
ifPhysAddress The value of the Circuit Identifier
If no Circuit Identifier has been
this object should have an octet
with zero length
ifAdminStatus See interfaces MIB [5]
ifOperStatus See interfaces MIB [5]
ifLastChange See interfaces MIB [5]
ifName See interfaces MIB [5]
ifLinkUpDownTrapEnable Set to enabled(1).
ifHighSpeed Speed of line in Mega-bits per
(either 45 or 34)
ifConnectorPresent Set to true(1) normally, except
cases such as DS3/E3 over AAL1/ATM
false(2) is
2.2. Usage
2.2.1. Usage of
The assignment of the index values could for example be
ifIndex
1
2 Line#A
3 Line#B
Fowler, Ed. Standards Track [Page 5]
RFC 2496 DS3/E3 MIB January 1999
4 Line#C
5 Line#D
6 Line#A CSU
7 Line#B CSU
8 Line#C CSU
9 Line#D CSU
10 Line#A CSU
11 Line#B CSU
12 Line#C CSU
13 Line#D CSU
The ifStackTable is then used to show the relationships between
various DS3 interfaces
ifStackTable
HigherLayer
2 6
3 7
4 8
5 9
6 10
7 11
8 12
9 13
If the CSU shelf is managed by itself by a local SNMP Agent,
situation would be identical, except the Ethernet and the 4
interfaces are deleted. Interfaces would also be numbered from 1
8.
ifIndex
1 Line#A CSU
2 Line#B CSU
3 Line#C CSU
4 Line#D CSU
5 Line#A CSU
6 Line#B CSU
7 Line#C CSU
8 Line#D CSU
ifStackTable
HigherLayer
1 5
2 6
3 7
4 8
Fowler, Ed. Standards Track [Page 6]
RFC 2496 DS3/E3 MIB January 1999
2.2.2. Usage of Channelization for DS3, DS1, DS
An example is given here to explain the channelization objects in
DS3, DS1, and DS0 MIBs to help the implementor use the
correctly. Treatment of E3 and E1 would be similar, with the
of DS0s being different depending on the framing of the E1.
Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (
DS2s). The object dsx3Channelization is set to enabledDs1.
this object is set to enabledDS1, 28 ifEntries of type DS1 will
created by the agent. If dsx3Channelization is set to disabled,
the DS1s are destroyed
Assume the entries in the ifTable for the DS1s are created in
order and the ifIndex values are 2 through 29. In the DS1 MIB,
will be an entry in the dsx1ChanMappingTable for each ds1.
entries will be as follows
dsx1ChanMappingTable
ifIndex dsx1Ds1ChannelNumber dsx1
1 1 2
1 2 3
......
1 28 29
In addition, the DS1s are channelized into DS0s. The
dsx1Channelization is set to enabledDS0 for each DS1. There will
24 DS0s in the ifTable for each DS1. Assume the entries in
ifTable are created in channel order and the ifIndex values for
DS0s in the first DS1 are 30 through 53. In the DS0 MIB, there
be an entry in the dsx0ChanMappingTable for each DS0. The
will be as follows
dsx0ChanMappingTable
ifIndex dsx0Ds0ChannelNumber dsx0
2 1 30
2 2 31
......
2 24 53
2.2.3. Usage of Channelization for DS3, DS2, DS
An example is given here to explain the channelization objects in
DS3 and DS1 MIBs to help the implementor use the objects correctly
Fowler, Ed. Standards Track [Page 7]
RFC 2496 DS3/E3 MIB January 1999
Assume that a DS3 (with ifIndex 1) is Channelized into DS2s.
object dsx3Channelization is set to enabledDs2. There will be 7 DS2
(ifType of DS1) in the ifTable. Assume the entries in the
for the DS2s are created in channel order and the ifIndex values
2 through 8. In the DS1 MIB, there will be an entry in
dsx1ChanMappingTable for each DS2. The entries will be as follows
dsx1ChanMappingTable
ifIndex dsx1Ds1ChannelNumber dsx1
1 1 2
1 2 3
......
1 7 8
In addition, the DS2s are channelized into DS1s. The
dsx1Channelization is set to enabledDS1 for each DS2. There will
4 DS1s in the ifTable for each DS2. Assume the entries in
ifTable are created in channel order and the ifIndex values for
DS1s in the first DS2 are 9 through 12, then 13 through 16 for
second DS2, and so on. In the DS1 MIB, there will be an entry in
dsx1ChanMappingTable for each DS1. The entries will be as follows
dsx1ChanMappingTable
ifIndex dsx1Ds1ChannelNumber dsx1
2 1 9
2 2 10
2 3 11
2 4 12
3 1 13
3 2 14
...
8 4 36
2.2.4. Usage of
This section discusses the behaviour of objects related to loopbacks
The object dsx3LoopbackConfig represents the desired state
loopbacks on this interface. Using this object a Manager
request
PayloadLoopback (if ESF framing
DualLoopback (Line + Inward
Fowler, Ed. Standards Track [Page 8]
RFC 2496 DS3/E3 MIB January 1999
The remote end can also request lookbacks either through the
channel if ESF or inband if D4. The loopbacks that can be
this way are
PayloadLoopback (if ESF framing
To model the current state of loopbacks on a DS3 interface,
object dsx3LoopbackStatus defines which loopback is currently
to an interface. This objects, which is a bitmap, will have
turned on which reflect the currently active loopbacks on
interface as well as the source of those loopbacks
The following restrictions/rules apply to loopbacks
The far end cannot undo loopbacks set by a manager
A manager can undo loopbacks set by the far end
Both a line loopback and an inward loopback can be set at the
time. Only these two loopbacks can co-exist and either one may
set by the manager or the far end. A LineLoopback request from
far end is incremental to an existing Inward loopback established
a manager. When a NoLoopback is received from the far end in
case, the InwardLoopback remains in place
2.3. 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
2.4. DS3/E3
The terminology used in this document to describe error conditions
a DS3 interface as monitored by a DS3 device are based on the
but not final draft of what became the ANSI T1.231 standard [11].
the definition in this document does not match the definition in
ANSI T1.231 document, the implementer should follow the
described in this document
Fowler, Ed. Standards Track [Page 9]
RFC 2496 DS3/E3 MIB January 1999
2.4.1. Error
Bipolar Violation (BPV) Error
A bipolar violation error event, for B3ZS(HDB3)-coded signals
is the occurrence of a pulse of the same polarity as
previous pulse without being part of the zero
code, B3ZS(HDB3). For B3ZS(HDB3)-coded signals, a
violation error event may also include other error
such as: three(four) or more consecutive zeros and
polarity. (See T1.231 section 7.1.1.1.1)
Excessive Zeros (EXZ) Error
An EXZ is the occurrence of any zero string length equal to
greater than 3 for B3ZS, or greater than 4 for HDB3. (
T1.231 section 7.1.1.1.2)
Line Coding Violation (LCV) Error
This parameter is a count of both BPVs and EXZs occurring
the accumulation period. An EXZ increments the LCV by
regardless of the length of the zero string. (Also known
CV-L. See T1.231 section 7.4.1.1)
P-bit Coding Violation (PCV) Error
For all DS3 applications, a coding violation error event is
P-bit Parity Error event. A P-bit Parity Error event is
occurrence of a received P-bit code on the DS3 M-frame that
not identical to the corresponding locally- calculated code
(See T1.231 section 7.1.1.2.1)
C-bit Coding Violation (CCV) Error
For C-bit Parity and SYNTRAN DS3 applications, this is
count of coding violations reported via the C-bits. For C-
Parity, it is a count of CP-bit parity errors occurring in
accumulation interval. For SYNTRAN, it is a count of CRC-9
errors occurring in the accumulation interval. (See T1.231
section 7.1.1.2.2)
2.4.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
Fowler, Ed. Standards Track [Page 10]
RFC 2496 DS3/E3 MIB January 1999
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
Performance parameters are of types PerfCurrentCount
PerfIntervalCount and PerfTotalCount. These textual conventions
all Gauge32, and they are used because it is possible for
objects to decrease. Objects may decrease when Unavailable
occurs across a fifteen minutes interval boundary. See
Seconds discussion later in this section
Line Errored Seconds (LES
A Line Errored Second is a second in which one or more
occurred OR one or more LOS defects. (Also known as ES-L.
T1.231 section 7.4.1.2)
P-bit Errored Seconds (PES
An PES is a second with one or more PCVs OR one or more Out
Frame defects OR a detected incoming AIS. This gauge is
incremented when UASs are counted. (Also known as ESP-P.
T1.231 section 7.4.2.2)
P-bit Severely Errored Seconds (PSES
A PSES is a second with 44 or more PCVs OR one or more Out
Frame defects OR a detected incoming AIS. This gauge is
incremented when UASs are counted. (Also known as SESP-P.
T1.231 section 7.4.2.5)
C-bit Errored Seconds (CES
An CES is a second with one or more CCVs OR one or more Out
Frame defects OR a detected incoming AIS. This count is
for the SYNTRAN and C-bit Parity DS3 applications. This
is not incremented when UASs are counted. (Also known
ESCP-P. See T1.231 section 7.4.2.2)
C-bit Severely Errored Seconds (CSES
A CSES is a second with 44 or more CCVs OR one or more Out
Frame defects OR a detected incoming AIS. This count is
for the SYNTRAN and C-bit Parity DS3 applications. This
is not incremented when UASs are counted. (Also known
SESCP-P. See T1.231 section 7.4.2.5)
Severely Errored Framing Seconds (SEFS
A SEFS is a second with one or more Out of Frame defects OR
detected incoming AIS. This item is not incremented
unavailable seconds. (Also known as SAS-P. See T1.231
7.4.2.6)
Fowler, Ed. Standards Track [Page 11]
RFC 2496 DS3/E3 MIB January 1999
Unavailable Seconds (UAS
UAS are calculated by counting the number of seconds that
interface is unavailable. The DS3 interface is said to
unavailable from the onset of 10 contiguous PSESs, or
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, then
DS3 interface unavailability starts from the onset of
PSESs. Once unavailable, and if no failure is present,
DS3 interface becomes available at the onset of 10
seconds with no PSESs. Once unavailable, and if a failure
present, the DS3 interface becomes available at the onset
10 contiguous seconds with no PSESs, if the failure
time is less than or equal to 10 seconds. If the
clearing time is more than 10 seconds, the DS3
becomes available at the onset of 10 contiguous seconds
no PSESs, or the onset period leading to the
clearing condition, whichever occurs later. With respect
the DS3 error counts, all counters are incremented while
DS3 interface is deemed available. While the interface
deemed unavailable, the only count that is incremented
UASs
Note that this definition implies that the agent
determine until after a ten second interval has passed
a given one-second interval belongs to available
unavailable time. If the agent chooses to update the
performance statistics in real time then it must be
to retroactively reduce the PES, PSES, CES, and CSES counts
10 and increase the UAS count by 10 when it determines
available time has been entered. It must also be prepared
adjust the PCV, CCV, and SEFS count as necessary since
parameters are not accumulated during unavailable time.
must be similarly prepared to retroactively decrease the
count by 10 and increase the PES, CES, PCV, and CCV counts
necessary upon entering available time. A special case
when the 10 second period leading to available or
time crosses a 900 second statistics window boundary, as
foregoing description implies that the PCV, CCV, PES, CES
PSES, CSEC, SEFS, and UAS counts for the PREVIOUS
must be adjusted. In this case successive GETs of
affected dsx3IntervalPSESs and dsx3IntervalUASs objects
return differing values if the first GET occurs during
first few seconds of the window
Fowler, Ed. Standards Track [Page 12]
RFC 2496 DS3/E3 MIB January 1999
The agent may instead choose to delay updates to the
statistics by 10 seconds in order to avoid
adjustments to the counters. A way to do this is sketched
Appendix B
In any case, a linkDown trap shall be sent only after
agent has determined for certain that the unavailable
has been entered, but the time on the trap will be that of
first UAS (i.e., 10 seconds earlier). A linkUp trap shall
handled similarly
According to ANSI T1.231 unavailable time begins at
_onset_ of 10 contiguous severely errored seconds -- that is
unavailable time starts with the _first_ of the 10
SESs. Also, while an interface is deemed unavailable
counters for that interface are frozen except for the
count. It follows that an implementation which
complies with this standard must _not_ increment any
other than the UAS count -- even temporarily -- as a result
anything that happens during those 10 seconds. Since
in the signal state lag the data to which they apply by 10
seconds, an ANSI-compliant implementation must pass the
one-second statistics through a 10-second delay line prior
updating any counters. That can be done by performing
following steps at the end of each one second interval
i) Read near/far end CV counter and alarm status flags from
hardware
ii) Accumulate the CV counts for the preceding second and
them to the ES and SES threshold for the layer in question
Update the signal state and shift the one-second CV counts
ES/SES flags into the 10-element delay line. Note that far-
one-second statistics are to be flagged as "absent" during
second in which there is an incoming defect at the layer
question or at any lower layer
iii) Update the current interval statistics using the signal
from the _previous_ update cycle and the one-second CV
and ES/SES flags shifted out of the 10-element delay line
This approach is further described in Appendix B
2.4.3. Performance
Failure States
The Remote Alarm Indication (RAI) failure, in
applications, is declared after detecting the Yellow
Fowler, Ed. Standards Track [Page 13]
RFC 2496 DS3/E3 MIB January 1999
Signal on the alarm channel. See ANSI T1.107a-1990 [9a].
Remote Alarm Indication failure, in C-bit Parity DS
applications, is declared as soon as the presence of
one or two alarm signals are detected on the Far End
Channel. See [9]. The Remote Alarm Indication failure
also be declared after detecting the far-end SEF/AIS
(aka yellow). The Remote Alarm Indication failure is
as soon as the presence of the any of the above alarms
removed
Also, the incoming failure state is declared when a
persists for at least 2-10 seconds. The defects are
following: Loss of Signal (LOS), an Out of Frame (OOF) or
incoming Alarm Indication Signal (AIS). The Failure State
cleared when the defect is absent 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 to one
(Also known as SASCP-PFE. See T1.231 section 7.4.4.2.6)
Out of Frame (OOF)
A DS3 OOF defect is detected when any three or more errors
sixteen or fewer consecutive F-bits occur within a DS3 M
frame. An OOF defect may also be called a Severely
Frame (SEF) defect. An OOF defect is cleared when
occurs. A DS3 Loss of Frame (LOF) failure is declared
the DS3 OOF defect is consistent for 2 to 10 seconds. The DS
OOF defect ends when reframe occurs. The DS3 LOF failure
cleared when the DS3 OOF defect is absent for 10 to 20
seconds. (See T1.231 section 7.1.2.2.1)
An E3 OOF defect is detected when four consecutive
alignment signals have been incorrectly received in
predicted positions in an E3 signal. E3 frame alignment
when the presence of three consecutive frame alignment
have been detected
Loss of Signal (LOS)
The DS3 LOS defect is declared upon observing 175 +/- 75
contiguous pulse positions with no pulses of either
or negative polarity. The DS3 LOS defect is terminated
observing an average pulse density of at least 33% over
period of 175 +/- 75 contiguous pulse positions starting
the receipt of a pulse. (See T1.231 section 7.1.2.1.1)
Fowler, Ed. Standards Track [Page 14]
RFC 2496 DS3/E3 MIB January 1999
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 set to
1010... sequence, starting with a one (1) after each M
subframe alignment bit, M-frame alignment bit, X bit, P bit
and C bit. The C bits are all set to zero giving what
called "stuck stuffing." The X bits are set to one. The DS
AIS defect is declared after DS3 AIS is present in
M-frames for a time equal to or greater than T, where 0.2
<= T <= 100 ms. The DS3 AIS defect is terminated after AIS
absent in contiguous M-frames for a time equal to or
than T. (See T1.231 section 7.1.2.2.3)
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 time limit
1 ms
2.4.4. Other
Circuit
This is a character string specified by the circuit vendor
and is useful when communicating with the vendor during
troubleshooting process
In this document, the word proxy is meant to indicate
application which receives SNMP messages and replies to
on behalf of the devices which implement the actual DS3/E
interfaces. The proxy may have already collected
information about the DS3/E3 interfaces into its
database and may not necessarily forward the requests to
actual DS3/E3 interface. It is expected in such
application that there are periods of time where the proxy
not communicating with the DS3/E3 interfaces. In
instances the proxy will not necessarily have up-to-
configuration information and will most likely have missed
collection of some statistics data. Missed statistics
collection will result in invalid data in the interval table
3. Object
DS3-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
NOTIFICATION-TYPE, transmission FROM SNMPv2-
Fowler, Ed. Standards Track [Page 15]
RFC 2496 DS3/E3 MIB January 1999
DisplayString, TimeStamp, TruthValue FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-
InterfaceIndex FROM IF-
PerfCurrentCount, PerfIntervalCount
PerfTotalCount FROM PerfHist-TC-MIB
ds3 MODULE-
LAST-UPDATED "9808012130Z
ORGANIZATION "IETF Trunk MIB Working Group
CONTACT-
" David
Postal: Newbridge Networks
600 March
Kanata, Ontario, Canada K2K 2E
Tel: +1 613 591 3600
Fax: +1 613 599 3667
E-mail: davef@newbridge.com
"The is the MIB module that
DS3 and E3 interfaces objects."
::= { transmission 30 }
-- The DS3/E3 Near End
-- The DS3/E3 Near End Group consists of four tables
-- DS3/E3
-- DS3/E3
-- DS3/E3
-- DS3/E3
-- the DS3/E3 Configuration
dsx3ConfigTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3/E3 Configuration table."
::= { ds3 5 }
dsx3ConfigEntry OBJECT-
SYNTAX Dsx3
Fowler, Ed. Standards Track [Page 16]
RFC 2496 DS3/E3 MIB January 1999
MAX-ACCESS not-
STATUS
"An entry in the DS3/E3 Configuration table."
INDEX { dsx3LineIndex }
::= { dsx3ConfigTable 1 }
Dsx3ConfigEntry ::=
SEQUENCE {
dsx3LineIndex InterfaceIndex
dsx3IfIndex InterfaceIndex
dsx3TimeElapsed INTEGER
dsx3ValidIntervals INTEGER
dsx3LineType INTEGER
dsx3LineCoding INTEGER
dsx3SendCode INTEGER
dsx3CircuitIdentifier DisplayString
dsx3LoopbackConfig INTEGER
dsx3LineStatus INTEGER
dsx3TransmitClockSource INTEGER
dsx3InvalidIntervals INTEGER
dsx3LineLength INTEGER
dsx3LineStatusLastChange TimeStamp
dsx3LineStatusChangeTrapEnable INTEGER
dsx3LoopbackStatus INTEGER
dsx3Channelization INTEGER
dsx3Ds1ForRemoteLoop
}
dsx3LineIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object should be made equal to ifIndex.
next paragraph describes its previous usage
Making the object equal to ifIndex allows
use of ifStackTable
Previously, this object was the identifier of
DS3/E3 Interface on a managed device. If there
an ifEntry that is directly associated with
and only this DS3/E3 interface, it should have
same value as ifIndex. Otherwise, number
dsx3LineIndices with an unique
following the rules of choosing a number that
greater than ifNumber and numbering the
interfaces (e.g., equipment side) with
Fowler, Ed. Standards Track [Page 17]
RFC 2496 DS3/E3 MIB January 1999
numbers and outside interfaces (e.g, network side
with odd numbers."
::= { dsx3ConfigEntry 1 }
dsx3IfIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This value for this object is equal to the
of ifIndex from the Interfaces table of MIB
(RFC 1213)."
::= { dsx3ConfigEntry 2 }
dsx3TimeElapsed OBJECT-
SYNTAX INTEGER (0..899)
MAX-ACCESS read-
STATUS
"The number of seconds that have elapsed since
beginning of the near end current error
measurement period. If, for some reason, such
an adjustment in the system's time-of-day clock
the current interval exceeds the maximum value
the agent will return the maximum value."
::= { dsx3ConfigEntry 3 }
dsx3ValidIntervals OBJECT-
SYNTAX INTEGER (0..96)
MAX-ACCESS read-
STATUS
"The number of previous near end intervals
which 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.
the case where the agent is a proxy, it
possible that some intervals are unavailable.
this case, this interval is the maximum
number for which data is available."
::= { dsx3ConfigEntry 4 }
dsx3LineType OBJECT-
SYNTAX INTEGER {
dsx3other(1),
Fowler, Ed. Standards Track [Page 18]
RFC 2496 DS3/E3 MIB January 1999
dsx3M23(2),
dsx3SYNTRAN(3),
dsx3CbitParity(4),
dsx3ClearChannel(5),
e3other(6),
e3Framed(7),
e3Plcp(8)
}
MAX-ACCESS read-
STATUS
"This variable indicates the variety of DS3 C-
or E3 application implementing this interface.
type of interface affects the interpretation
the usage and error statistics. The rate of DS
is 44.736 Mbps and E3 is 34.368 Mbps.
dsx3ClearChannel value means that the C-bits
not used except for sending/receiving AIS
The values, in sequence, describe
TITLE: SPECIFICATION
dsx3M23 ANSI T1.107-1988 [9]
dsx3SYNTRAN ANSI T1.107-1988 [9]
dsx3CbitParity ANSI T1.107a-1990 [9a
dsx3ClearChannel ANSI T1.102-1987 [8]
e3Framed CCITT G.751 [12]
e3Plcp ETSI T/NA(91)18 [13]."
::= { dsx3ConfigEntry 5 }
dsx3LineCoding OBJECT-
SYNTAX INTEGER {
dsx3Other(1),
dsx3B3ZS(2),
e3HDB3(3)
}
MAX-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 }
Fowler, Ed. Standards Track [Page 19]
RFC 2496 DS3/E3 MIB January 1999
dsx3SendCode OBJECT-
SYNTAX INTEGER {
dsx3SendNoCode(1),
dsx3SendLineCode(2),
dsx3SendPayloadCode(3),
dsx3SendResetCode(4),
dsx3SendDS1LoopCode(5),
dsx3SendTestPattern(6)
}
MAX-ACCESS read-
STATUS
"This variable indicates what type of code
being sent across the DS3/E3 interface by
device. (These are optional for E3 interfaces.)
Setting this variable causes the interface
begin sending the code requested
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 frame. The DS1/E1
indicated in dsx3Ds1ForRemoteLoop
dsx3
sending a test pattern."
::= { dsx3ConfigEntry 7 }
dsx3CircuitIdentifier OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"This variable contains the transmission vendor'
circuit identifier, for the purpose
Fowler, Ed. Standards Track [Page 20]
RFC 2496 DS3/E3 MIB January 1999
facilitating troubleshooting."
::= { dsx3ConfigEntry 8 }
dsx3LoopbackConfig OBJECT-
SYNTAX INTEGER {
dsx3NoLoop(1),
dsx3PayloadLoop(2),
dsx3LineLoop(3),
dsx3OtherLoop(4),
dsx3InwardLoop(5),
dsx3DualLoop(6)
}
MAX-ACCESS read-
STATUS
"This variable represents the desired
configuration of the DS3/E3 interface
The values mean
dsx3
Not in the loopback state. A device that
not capable of performing a loopback
the interface shall always return this
its 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
dsx3
The sent signal at this interface is looped
through the device
dsx3
Both dsx1LineLoop and dsx1InwardLoop will
active simultaneously."
::= { dsx3ConfigEntry 9 }
Fowler, Ed. Standards Track [Page 21]
RFC 2496 DS3/E3 MIB January 1999
dsx3LineStatus OBJECT-
SYNTAX INTEGER (1..4095)
MAX-ACCESS read-
STATUS
"This variable indicates the Line Status of
interface. It contains loopback state
and failure state information. The dsx3
is a bit map represented as a sum, therefore,
can represent multiple failures and a
(see dsx3LoopbackConfig object for the type
loopback) simultaneously. The dsx3NoAlarm must
set if and only if no other flag is set
If the dsx3loopbackState bit is set, the
in effect can be determined from
dsx3loopbackConfig object
The various bit positions are
1 dsx3NoAlarm No alarm
2 dsx3RcvRAIFailure Receiving Yellow/
Alarm
4 dsx3XmitRAIAlarm Transmitting Yellow/
Alarm
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
1024 dsx3UnavailSigState Near End in Unavailable
2048 dsx3NetEquipOOS Carrier Equipment Out of Service
::= { dsx3ConfigEntry 10 }
dsx3TransmitClockSource OBJECT-
SYNTAX INTEGER {
loopTiming(1),
localTiming(2),
throughTiming(3)
}
MAX-ACCESS read-
STATUS
"The source of Transmit Clock
loopTiming indicates that the recovered receive
Fowler, Ed. Standards Track [Page 22]
RFC 2496 DS3/E3 MIB January 1999
is used as the transmit clock
localTiming indicates that a local clock source is
or that an external clock is attached to the
containing the interface
throughTiming indicates that transmit clock is
from the recovered receive clock of another DS
interface."
::= { dsx3ConfigEntry 11 }
dsx3InvalidIntervals OBJECT-
SYNTAX INTEGER (0..96)
MAX-ACCESS read-
STATUS
"The number of intervals in the range from 0
dsx3ValidIntervals for which no data
available. This object will typically be
except in cases where the data for some
are not available (e.g., in proxy situations)."
::= { dsx3ConfigEntry 12 }
dsx3LineLength OBJECT-
SYNTAX INTEGER (0..64000)
UNITS "meters
MAX-ACCESS read-
STATUS
"The length of the ds3 line in meters.
object provides information for line build
circuitry if it exists and can use this object
adjust the line build out."
::= { dsx3ConfigEntry 13 }
dsx3LineStatusLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of MIB II's sysUpTime object at
time this DS3/E3 entered its current line
state. If the current state was entered prior
the last re-initialization of the proxy-agent
then this object contains a zero value."
::= { dsx3ConfigEntry 14 }
dsx3LineStatusChangeTrapEnable OBJECT-
Fowler, Ed. Standards Track [Page 23]
RFC 2496 DS3/E3 MIB January 1999
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-
STATUS
"Indicates whether dsx3LineStatusChange
should be generated for this interface."
DEFVAL { disabled }
::= { dsx3ConfigEntry 15 }
dsx3LoopbackStatus OBJECT-
SYNTAX INTEGER (1..127)
MAX-ACCESS read-
STATUS
"This variable represents the current state of
loopback on the DS3 interface. It
information about loopbacks established by
manager and remotely from the far end
The dsx3LoopbackStatus is a bit map represented
a sum, therefore is can represent
loopbacks simultaneously
The various bit positions are
1 dsx3
2 dsx3
4 dsx3
8 dsx3
16 dsx3
32 dsx3
64 dsx3FarEndLineLoopback
::= { dsx3ConfigEntry 16 }
dsx3Channelization OBJECT-
SYNTAX INTEGER {
disabled(1),
enabledDs1(2),
enabledDs2(3)
}
MAX-ACCESS read-
STATUS
"Indicates whether this ds3/e3 is channelized
unchannelized. The value of enabledDs1
Fowler, Ed. Standards Track [Page 24]
RFC 2496 DS3/E3 MIB January 1999
that this is a DS3 channelized into DS1s.
value of enabledDs3 indicated that this is a DS
channelized into DS2s. Setting this object
cause the creation or deletion of DS2 or DS
entries in the ifTable. "
::= { dsx3ConfigEntry 17 }
dsx3Ds1ForRemoteLoop OBJECT-
SYNTAX INTEGER (0..29)
MAX-ACCESS read-
STATUS
"Indicates which ds1/e1 on this ds3/e3 will
indicated in the remote ds1 loopback request.
value of 0 means no DS1 will be looped. A
of 29 means all ds1s/e1s will be looped."
::= { dsx3ConfigEntry 18 }
-- the DS3/E3 Current
dsx3CurrentTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3/E3 current table contains
statistics being collected for the current 15
minute interval."
::= { ds3 6 }
dsx3CurrentEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"An entry in the DS3/E3 Current table."
INDEX { dsx3CurrentIndex }
::= { dsx3CurrentTable 1 }
Dsx3CurrentEntry ::=
SEQUENCE {
dsx3CurrentIndex InterfaceIndex
dsx3CurrentPESs PerfCurrentCount
dsx3CurrentPSESs PerfCurrentCount
dsx3CurrentSEFSs PerfCurrentCount
Fowler, Ed. Standards Track [Page 25]
RFC 2496 DS3/E3 MIB January 1999
dsx3CurrentUASs PerfCurrentCount
dsx3CurrentLCVs PerfCurrentCount
dsx3CurrentPCVs PerfCurrentCount
dsx3CurrentLESs PerfCurrentCount
dsx3CurrentCCVs PerfCurrentCount
dsx3CurrentCESs PerfCurrentCount
dsx3CurrentCSESs
}
dsx3CurrentIndex OBJECT-
SYNTAX
MAX-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
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds."
::= { dsx3CurrentEntry 2 }
dsx3CurrentPSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Severely Errored Seconds."
::= { dsx3CurrentEntry 3 }
dsx3CurrentSEFSs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds."
::= { dsx3CurrentEntry 4 }
Fowler, Ed. Standards Track [Page 26]
RFC 2496 DS3/E3 MIB January 1999
dsx3CurrentUASs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds."
::= { dsx3CurrentEntry 5 }
dsx3CurrentLCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of
Coding Violations."
::= { dsx3CurrentEntry 6 }
dsx3CurrentPCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations."
::= { dsx3CurrentEntry 7 }
dsx3CurrentLESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of Line Errored Seconds."
::= { dsx3CurrentEntry 8 }
dsx3CurrentCCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Coding Violations."
::= { dsx3CurrentEntry 9 }
dsx3CurrentCESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Fowler, Ed. Standards Track [Page 27]
RFC 2496 DS3/E3 MIB January 1999
"The number of C-bit Errored Seconds."
::= { dsx3CurrentEntry 10 }
dsx3CurrentCSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Severely Errored Seconds."
::= { dsx3CurrentEntry 11 }
-- the DS3/E3 Interval
dsx3IntervalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3/E3 Interval Table contains
statistics collected by each DS3/E3 Interface
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15
intervals. Each row in this table represents
such interval (identified by dsx3IntervalNumber
and for one specific interface (identifed
dsx3IntervalIndex)."
::= { ds3 7 }
dsx3IntervalEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"An entry in the DS3/E3 Interval table."
INDEX { dsx3IntervalIndex, dsx3IntervalNumber }
::= { dsx3IntervalTable 1 }
Dsx3IntervalEntry ::=
SEQUENCE {
dsx3IntervalIndex InterfaceIndex
dsx3IntervalNumber INTEGER
dsx3IntervalPESs PerfIntervalCount
dsx3IntervalPSESs PerfIntervalCount
dsx3IntervalSEFSs PerfIntervalCount
dsx3IntervalUASs PerfIntervalCount
dsx3IntervalLCVs PerfIntervalCount
dsx3IntervalPCVs PerfIntervalCount
Fowler, Ed. Standards Track [Page 28]
RFC 2496 DS3/E3 MIB January 1999
dsx3IntervalLESs PerfIntervalCount
dsx3IntervalCCVs PerfIntervalCount
dsx3IntervalCESs PerfIntervalCount
dsx3IntervalCSESs PerfIntervalCount
dsx3IntervalValidData
}
dsx3IntervalIndex OBJECT-
SYNTAX
MAX-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)
MAX-ACCESS read-
STATUS
"A number between 1 and 96, where 1 is the
recently completed 15 minute interval and 96
the 15 minutes interval completed 23 hours and 45
minutes prior to interval 1."
::= { dsx3IntervalEntry 2 }
dsx3IntervalPESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds."
::= { dsx3IntervalEntry 3 }
dsx3IntervalPSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Severely Errored Seconds."
::= { dsx3IntervalEntry 4 }
Fowler, Ed. Standards Track [Page 29]
RFC 2496 DS3/E3 MIB January 1999
dsx3IntervalSEFSs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds."
::= { dsx3IntervalEntry 5 }
dsx3IntervalUASs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds. This object may decrease
the occurance of unavailable seconds occurs
an inteval boundary."
::= { dsx3IntervalEntry 6 }
dsx3IntervalLCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of
Coding Violations."
::= { dsx3IntervalEntry 7 }
dsx3IntervalPCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations."
::= { dsx3IntervalEntry 8 }
dsx3IntervalLESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of Line Errored Seconds (BPVs
illegal zero sequences)."
::= { dsx3IntervalEntry 9 }
dsx3IntervalCCVs OBJECT-
Fowler, Ed. Standards Track [Page 30]
RFC 2496 DS3/E3 MIB January 1999
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Coding Violations."
::= { dsx3IntervalEntry 10 }
dsx3IntervalCESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Errored Seconds."
::= { dsx3IntervalEntry 11 }
dsx3IntervalCSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Severely Errored Seconds."
::= { dsx3IntervalEntry 12 }
dsx3IntervalValidData OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable indicates if the data for
interval is valid."
::= { dsx3IntervalEntry 13 }
-- the DS3/E3
dsx3TotalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3/E3 Total Table contains the
sum of the various statistics for the 24
period preceding the current interval."
::= { ds3 8 }
dsx3TotalEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
Fowler, Ed. Standards Track [Page 31]
RFC 2496 DS3/E3 MIB January 1999
"An entry in the DS3/E3 Total table."
INDEX { dsx3TotalIndex }
::= { dsx3TotalTable 1 }
Dsx3TotalEntry ::=
SEQUENCE {
dsx3TotalIndex InterfaceIndex
dsx3TotalPESs PerfTotalCount
dsx3TotalPSESs PerfTotalCount
dsx3TotalSEFSs PerfTotalCount
dsx3TotalUASs PerfTotalCount
dsx3TotalLCVs PerfTotalCount
dsx3TotalPCVs PerfTotalCount
dsx3TotalLESs PerfTotalCount
dsx3TotalCCVs PerfTotalCount
dsx3TotalCESs PerfTotalCount
dsx3TotalCSESs
}
dsx3TotalIndex OBJECT-
SYNTAX
MAX-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."
::= { dsx3TotalEntry 1 }
dsx3TotalPESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Errored Seconds, encountered by a DS3 interface
the previous 24 hour interval. Invalid 15
intervals count as 0."
::= { dsx3TotalEntry 2 }
dsx3TotalPSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Fowler, Ed. Standards Track [Page 32]
RFC 2496 DS3/E3 MIB January 1999
"The counter associated with the number of P-
Severely Errored Seconds, encountered by a DS
interface in the previous 24 hour interval
Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 3 }
dsx3TotalSEFSs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Severely Errored Framing Seconds, encountered by
DS3/E3 interface in the previous 24 hour interval
Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 4 }
dsx3TotalUASs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number
Unavailable Seconds, encountered by a DS
interface in the previous 24 hour interval
Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 5 }
dsx3TotalLCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of
Coding Violations encountered by a DS3/E
interface in the previous 24 hour interval
Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 6 }
dsx3TotalPCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of P-
Coding Violations, encountered by a DS3
Fowler, Ed. Standards Track [Page 33]
RFC 2496 DS3/E3 MIB January 1999
in the previous 24 hour interval. Invalid 15
minute intervals count as 0."
::= { dsx3TotalEntry 7 }
dsx3TotalLESs OBJECT-
SYNTAX
MAX-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
Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 8 }
dsx3TotalCCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Coding Violations
by a DS3 interface in the previous 24
interval. Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 9 }
dsx3TotalCESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Errored Seconds
by a DS3 interface in the previous 24
interval. Invalid 15 minute intervals count as 0."
::= { dsx3TotalEntry 10 }
dsx3TotalCSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of C-bit Severely Errored
encountered by a DS3 interface in the previous 24
hour interval. Invalid 15 minute intervals
as 0."
::= { dsx3TotalEntry 11 }
-- The DS3 Far End
Fowler, Ed. Standards Track [Page 34]
RFC 2496 DS3/E3 MIB January 1999
-- 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
dsx3FarEndConfigTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3 Far End Configuration Table
configuration information reported in the C-
from the remote end."
::= { ds3 9 }
dsx3FarEndConfigEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"An entry in the DS3 Far End Configuration table."
INDEX { dsx3FarEndLineIndex }
::= { dsx3FarEndConfigTable 1 }
Dsx3FarEndConfigEntry ::=
SEQUENCE {
dsx3FarEndLineIndex InterfaceIndex
dsx3FarEndEquipCode DisplayString
dsx3FarEndLocationIDCode DisplayString
dsx3FarEndFrameIDCode DisplayString
dsx3FarEndUnitCode DisplayString
dsx3FarEndFacilityIDCode
}
dsx3FarEndLineIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The index value which uniquely identifies the DS
interface to which this entry is applicable.
interface identified by a particular value of
index is the same interface as identified by
same value an dsx3LineIndex object instance."
Fowler, Ed. Standards Track [Page 35]
RFC 2496 DS3/E3 MIB January 1999
::= { dsx3FarEndConfigEntry 1 }
dsx3FarEndEquipCode OBJECT-
SYNTAX DisplayString (SIZE (0..10))
MAX-ACCESS read-
STATUS
"This is the Far End Equipment Identification
that describes the specific piece of equipment
It is sent within the Path
Message."
::= { dsx3FarEndConfigEntry 2 }
dsx3FarEndLocationIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..11))
MAX-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 }
dsx3FarEndFrameIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..10))
MAX-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
within the Path Identification Message."
::= { dsx3FarEndConfigEntry 4 }
dsx3FarEndUnitCode OBJECT-
SYNTAX DisplayString (SIZE (0..6))
MAX-ACCESS read-
STATUS
"This is the Far End code that identifies
equipment location within a bay. It is
within the Path Identification Message."
::= { dsx3FarEndConfigEntry 5 }
dsx3FarEndFacilityIDCode OBJECT-
SYNTAX DisplayString (SIZE (0..38))
MAX-ACCESS read-
Fowler, Ed. Standards Track [Page 36]
RFC 2496 DS3/E3 MIB January 1999
STATUS
"This code identifies a specific Far End DS3 path
It is sent within the Path
Message."
::= { dsx3FarEndConfigEntry 6 }
-- The DS3 Far End
dsx3FarEndCurrentTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3 Far End Current table contains
statistics being collected for the current 15
minute interval. The statistics are
from the far end block error code within the C
bits."
::= { ds3 10 }
dsx3FarEndCurrentEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"An entry in the DS3 Far End Current table."
INDEX { dsx3FarEndCurrentIndex }
::= { dsx3FarEndCurrentTable 1 }
Dsx3FarEndCurrentEntry ::=
SEQUENCE {
dsx3FarEndCurrentIndex InterfaceIndex
dsx3FarEndTimeElapsed INTEGER
dsx3FarEndValidIntervals INTEGER
dsx3FarEndCurrentCESs PerfCurrentCount
dsx3FarEndCurrentCSESs PerfCurrentCount
dsx3FarEndCurrentCCVs PerfCurrentCount
dsx3FarEndCurrentUASs PerfCurrentCount
dsx3FarEndInvalidIntervals
}
dsx3FarEndCurrentIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The index value which uniquely identifies the DS
Fowler, Ed. Standards Track [Page 37]
RFC 2496 DS3/E3 MIB January 1999
interface to which this entry is applicable.
interface identified by a particular value of
index is identical to the interface identified
the same value of dsx3LineIndex."
::= { dsx3FarEndCurrentEntry 1 }
dsx3FarEndTimeElapsed OBJECT-
SYNTAX INTEGER (0..899)
MAX-ACCESS read-
STATUS
"The number of seconds that have elapsed since
beginning of the far end current error-
period. If, for some reason, such as
adjustment in the system's time-of-day clock,
current interval exceeds the maximum value,
agent will return the maximum value."
::= { dsx3FarEndCurrentEntry 2 }
dsx3FarEndValidIntervals OBJECT-
SYNTAX INTEGER (0..96)
MAX-ACCESS read-
STATUS
"The number of previous far end intervals
which 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
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
End C-bit Errored Seconds."
::= { dsx3FarEndCurrentEntry 4 }
dsx3FarEndCurrentCSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
C-bit Severely Errored Seconds."
Fowler, Ed. Standards Track [Page 38]
RFC 2496 DS3/E3 MIB January 1999
::= { dsx3FarEndCurrentEntry 5 }
dsx3FarEndCurrentCCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
C-bit Coding Violations reported via the far
block error count."
::= { dsx3FarEndCurrentEntry 6 }
dsx3FarEndCurrentUASs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
unavailable seconds."
::= { dsx3FarEndCurrentEntry 7 }
dsx3FarEndInvalidIntervals OBJECT-
SYNTAX INTEGER (0..96)
MAX-ACCESS read-
STATUS
"The number of intervals in the range from 0
dsx3FarEndValidIntervals for which no data
available. This object will typically be
except in cases where the data for some
are not available (e.g., in proxy situations)."
::= { dsx3FarEndCurrentEntry 8 }
-- The DS3 Far End Interval
dsx3FarEndIntervalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3 Far End Interval Table contains
statistics collected by each DS3 interface
the previous 24 hours of operation. The past 24
hours are broken into 96 completed 15
intervals."
::= { ds3 11 }
dsx3FarEndIntervalEntry OBJECT-
Fowler, Ed. Standards Track [Page 39]
RFC 2496 DS3/E3 MIB January 1999
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"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
}
dsx3FarEndIntervalIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The index value which uniquely identifies the DS
interface to which this entry is applicable.
interface identified by a particular value of
index is identical to the interface identified
the same value of dsx3LineIndex."
::= { dsx3FarEndIntervalEntry 1 }
dsx3FarEndIntervalNumber OBJECT-
SYNTAX INTEGER (1..96)
MAX-ACCESS read-
STATUS
"A number between 1 and 96, where 1 is the
recently completed 15 minute interval and 96
the 15 minutes interval completed 23 hours and 45
minutes prior to interval 1."
::= { dsx3FarEndIntervalEntry 2 }
dsx3FarEndIntervalCESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Fowler, Ed. Standards Track [Page 40]
RFC 2496 DS3/E3 MIB January 1999
"The counter associated with the number of Far
C-bit Errored Seconds encountered by a DS
interface in one of the previous 96, individual 15
minute, intervals. In the case where the agent
a proxy and data is not available,
noSuchInstance."
::= { dsx3FarEndIntervalEntry 3 }
dsx3FarEndIntervalCSESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
C-bit Severely Errored Seconds."
::= { dsx3FarEndIntervalEntry 4 }
dsx3FarEndIntervalCCVs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
C-bit Coding Violations reported via the far
block error count."
::= { dsx3FarEndIntervalEntry 5 }
dsx3FarEndIntervalUASs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
unavailable seconds."
::= { dsx3FarEndIntervalEntry 6 }
dsx3FarEndIntervalValidData OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable indicates if the data for
interval is valid."
::= { dsx3FarEndIntervalEntry 7 }
-- The DS3 Far End
Fowler, Ed. Standards Track [Page 41]
RFC 2496 DS3/E3 MIB January 1999
dsx3FarEndTotalTable OBJECT-
SYNTAX SEQUENCE OF Dsx3
MAX-ACCESS not-
STATUS
"The DS3 Far End Total Table contains
cumulative sum of the various statistics for
24 hour period preceding the current interval."
::= { ds3 12 }
dsx3FarEndTotalEntry OBJECT-
SYNTAX Dsx3
MAX-ACCESS not-
STATUS
"An entry in the DS3 Far End Total table."
INDEX { dsx3FarEndTotalIndex }
::= { dsx3FarEndTotalTable 1 }
Dsx3FarEndTotalEntry ::=
SEQUENCE {
dsx3FarEndTotalIndex InterfaceIndex
dsx3FarEndTotalCESs PerfTotalCount
dsx3FarEndTotalCSESs PerfTotalCount
dsx3FarEndTotalCCVs PerfTotalCount
dsx3FarEndTotalUASs
}
dsx3FarEndTotalIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The index value which uniquely identifies the DS
interface to which this entry is applicable.
interface identified by a particular value of
index is identical to the interface identified
the same value of dsx3LineIndex."
::= { dsx3FarEndTotalEntry 1 }
dsx3FarEndTotalCESs OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The counter associated with the number of Far
C-bit Errored Seconds encountered by a DS
interface in the previous 24 hour 