INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Definitions of Managed Objects
for the DS1, E1, DS2 and E2 Interface Types
Thu Feb 8 19:48:26 1996
draft-ietf-trunkmib-ds1-mib-01.txt
David Fowler (editor)
Newbridge Networks
davef@newbridge.com
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
Rim).
Abstract
This memo defines an experimental 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 DS1, E1, DS2 and E2 interfaces. This document is a
companion document with Definitions of Managed Objects for the DS3/E3
and SONET/SDH Interface Types, rfc1407 [17] and rfc1595 [18].
This memo specifies a MIB module in a manner that is both compliant
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
definitions.
Expires August 1996 [Page 1]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
This memo does not specify a standard for the Internet community.
This document entirely replaces RFC 1406.
1. The SNMPv2 Network Management Framework
The SNMP Network Management Framework presently consists of three major
components. They are:
o the SMI, described in RFC 1902 [1] - the mechanisms used for
describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed
objects for the Internet suite of protocols.
o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol
for accessing managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
Expires August 1996 [Page 2]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
2. Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to also refer to
the object type.
2.1. Changes from RFC1406
The changes from RFC1406 are the following:
(1) The Fractional Table has been deprecated
(2) This document uses SMIv2
(3) Values are given for ifTable and ifXTable
(4) Example usage of ifStackTable is included
(5) dsx1IfIndex has been deprecated
(6) Support for DS2 and E2 have been added
(7) An additional lineType for unframed E1 was added
(8) The definition of valid intervals has been clarified
for the case where the agent proxied for other
devices. In particular, the treatment of missing
intervals has been clarified.
(9) An inward loopback has been added.
(10) Additional lineStatus bits have been added for Near End
in Unavailable Signal State, Carrier Equipment Out of
Service, DS@ Payload AIS, and DS@ Performance Threshold
(11) A line Length object has been added.
(12) Signal mode of other has been added.
Expires August 1996 [Page 3]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
(13) Added a lineStatus last change, trap and enabler.
Expires August 1996 [Page 4]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
3. Overview
These objects are used when the particular media being used to
realize an interface is a DS1/E1/DS2/E2 interface. At present, this
applies to these values of the ifType variable in the Internet-
standard MIB:
ds1 (18)
The definitions contained herein are based on the AT&T T-1 Superframe
(a.k.a., D4) and Extended Superframe (ESF) formats [6, 7], the latter
of which conforms to ANSI specifications [8], and the CCITT
Recommendations [9, 10], referred to as E1 for the rest of this memo.
The various DS1 and E1 line disciplines are similar enough that
separate MIBs are unwarranted, although there are some differences.
For example, Loss of Frame is defined more rigorously in the ESF
specification than in the D4 specification, but it is defined in
both.
Where it is necessary to distinguish between the flavors of E1 with
and without CRC, E1-CRC to denotes the "with CRC" form (G.704 Table
4b) and E1-noCRC denotes the "without CRC" form (G.704 Table 4a).
3.1. Use of ifTable for DS1 Layer
Only the ifGeneralGroup needs to be supported.
ifTable Object Use for DS1 Layer
======================================================================
ifIndex Interface index.
ifDescr Textual Description of the interface
ifType ds1(18)
ifSpeed Speed of line rate
DS1 - 1544000
E1 - 2048000
DS2 - 6312000
E2 - 8448000
ifPhysAddress The value of the Circuit Identifier.
If no Circuit Identifier has been assigned
this object should have an octet string with
Expires August 1996 [Page 5]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
zero length.
ifAdminStatus Supports read-only access.
The desired administrative status of the
interface.
ifOperStatus The current operational status of the
interface.
ifLastChange sysUpTime at the last change in
ifOperStatus.
ifName Textual name of the interface or an
OCTET STRING of zero length.
ifLinkUpDownTrapEnable Set to enabled(1).
ifHighSpeed Speed of line in Mega-bits per second
(2, 6, or 8)
ifConnectorPresent Set to true(1) normally, except for
cases such as DS1/E1 over AAL1/ATM where
false(2) is appropriate
3.2. Using ifStackTable
The objects dsx1IfIndex has been deprecated. This object previously
allowed a very special proxy situation to exist for Routers and CSUs.
This section now describes how to use ifStackTable to represent this
relationship.
The paragraphs discussing dsx1IfIndex and dsx1LineIndex have been
preserved in Appendix A for informational purposes.
Expires August 1996 [Page 6]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
External&Internal interface scenario: the SNMP Agents resides on an
host external from the device supporting DS1 interfaces (e.g., a
router). The Agent represents both the host and the DS1 device.
Example:
A shelf full of CSUs connected to a Router. An SNMP Agent residing on
the router proxies for itself and the CSU. The router has also an
Ethernet interface:
+-----+
| | |
| | | +---------------------+
|E | | 1.544 MBPS | Line#A | DS1 Link
|t | R |---------------+ - - - - - - - - - +------>
|h | | | |
|e | O | 1.544 MBPS | Line#B | DS1 Link
|r | |---------------+ - - - - - - - - - - +------>
|n | U | | CSU Shelf |
|e | | 1.544 MBPS | Line#C | DS1 Link
|t | T |---------------+ - - - -- -- - - - - +------>
| | | | |
|-----| E | 1.544 MBPS | Line#D | DS1 Link
| | |---------------+ - - - - -- - - - - +------>
| | R | |_____________________|
| | |
| +-----+
The assignment of the index values could for example be:
ifIndex Description
1 Ethernet
2 Line#A Router
3 Line#B Router
4 Line#C Router
5 Line#D Router
6 Line#A CSU Router
7 Line#B CSU Router
8 Line#C CSU Router
9 Line#D CSU Router
10 Line#A CSU Network
11 Line#B CSU Network
12 Line#C CSU Network
13 Line#D CSU Network
Expires August 1996 [Page 7]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
The ifStackTable is then used to show the relationships between the
various DS1 interfaces.
ifStackTable Entries
HigherLayer LowerLayer
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, the
situation would be identical, except the Ethernet and the 4 router
interfaces are deleted. Interfaces would also be numbered from 1 to
8.
ifIndex Description
1 Line#A CSU Router
2 Line#B CSU Router
3 Line#C CSU Router
4 Line#D CSU Router
5 Line#A CSU Network
6 Line#B CSU Network
7 Line#C CSU Network
8 Line#D CSU Network
ifStackTable Entries
HigherLayer LowerLayer
1 5
2 6
3 7
4 8
3.3. Objectives of this MIB Module
There are numerous things that could be included in a MIB for DS1
signals: the management of multiplexors, CSUs, DSUs, and the like.
The intent of this document is to facilitate the common management of
all devices with DS1 interfaces. As such, a design decision was made
up front to very closely align the MIB with the set of objects that
Expires August 1996 [Page 8]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
can generally be read from DS1 devices that are currently deployed.
3.4. DS1 Terminology
The terminology used in this document to describe error conditions on
a DS1 interface as monitored by a DS1 device are based on the
definitions from the ANSI T1.231 standard [11]. If the definition in
this document does not match the definition in the ANSI T1.231
document, the implementer should follow the definition described in
this document.
3.4.1. Error Events
Bipolar Violation (BPV) Error Event
A BPV error event for an AMI-coded signal is the
occurrence of a pulse of the same polarity as the
previous pulse. A BPV error event for a B8ZS- or HDB3-
coded signal is the occurrence of a pulse of the same
polarity as the previous pulse without being a part of
the zero substitution code. (See T1.231)
Excessive Zeroes (EXZ) Error Event
An Excessive Zeroes error event for an AMI-coded signal
is the occurrence of more than fifteen contiguous zeroes.
For a B8ZS coded signal, the defect occurs when more than
seven contiguous zeroes are detected. (See T1.231)
Line Coding Violation (LCV) Error Event
A Line Coding Violation (LCV) is the occurrence of either
a Bipolar Violation (BPV) or Excessive Zeroes (EXZ) Error
Event. (
Path Coding Violation (PCV) Error Event
A Path Coding Violation error event is a frame
synchronization bit error in the D4 and E1-noCRC formats,
or a CRC error in the ESF and E1-CRC formats. (See T1.231)
Controlled Slip (CS) Error Event
A Controlled Slip is the replication or deletion of the
payload bits of a DS1 frame. A Controlled Slip may be
performed when there is a difference between the timing
of a synchronous receiving terminal and the received
signal. A Controlled Slip does not cause an Out of Frame
defect. (See T1.231)
Expires August 1996 [Page 9]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
3.4.2. Performance Defects
Out Of Frame (OOF) Defect
An OOF defect is the occurrence of a particular density
of Framing Error events. (See T1.231)
For DS1 links, an Out of Frame defect is declared when the
receiver detects two or more framing errors within a 3
msec period for ESF signals and 0.75 msec for D4 signals,
or two or more errors out of five or fewer consecutive
framing-bits.
For E1 links, an Out Of Frame defect is declared when
three consecutive frame alignment signals have been
received with an error (see G.706 Section 4.1 [15]).
For DS2 links, an Out of Frame defect is declared when
7 or more consecutive errored framing patterns (4
multiframe) are received. The LOF is cleared when 3
or more consecutive correct framing patterns are
received.
Once an Out Of Frame Defect is declared, the framer
starts searching for a correct framing pattern. The Out
of Frame defect ends when the signal is in frame.
In-frame occurs when there are fewer than two frame bit
errors within 3 msec period for ESF signals and 0.75 msec
for D4 signals.
For E1 links, in-frame occurs when a) in frame N the
frame alignment signal is correct and b) in frame N+1 the
frame alignment signal is absent (i.e., bit 2 in TS0 is a
one) and c) in frame N+2 the frame alignment signal is
present and correct.
Alarm Indication Signal (AIS) Defect
For D4 and ESF links, the 'all ones' condition is
detected at a DS1 line interface upon observing an
unframed signal with a one's density of at least 99.9%
present for a time equal to or greater than T, where 3 ms
<= T <= 75 ms. The AIS is terminated upon observing a
signal not meeting the one's density or the unframed
signal criteria for a period equal to or greater than
than T.
Expires August 1996 [Page 10]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
For E1 links, the 'all-ones' condition is detected at the
line interface as a string of 512 bits containing fewer
than three zero bits (see O.162 [12] Section 3.3.2).
For DS2 links, the DS2 AIS shall be sent from the NT1
to the user to indicate a loss of the 6,312 kbps
frame capability on the network side. The DS2 AIS is
defined as a bit array of 6,312 kbps in which all
binary bits are set to '1'.
The DS2 AIS detection and removal shall be implemented
according to ITU-T Draft Recommendation G.775[20]:
- a DS2 AIS defect is detected when the incoming signal
has two (2) or less ZEROs in a sequence of 3156 bits
(0.5 ms).
- a DS2 AIS defect is cleared when the incoming signal
has three (3) or more ZEROs ina sequence of 3156 bits
(0.5 ms).
3.4.3. Performance Parameters
All performance parameters are accumulated in fifteen minute
intervals and up to 96 intervals (24 hours worth) are kept by an
agent. Fewer than 96 intervals of data will be available if the
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 relationship
between the start of a fifteen minute interval and any wall clock;
however some agents may align the fifteen minute intervals with
quarter hours.
Performance parameters are of type Gauge32 because it is possible for
these objects to decrease. Objects may decrease when Unavailable
Seconds occurs across a fifteen minutes interval boundary. See
Unavailable Seconds discussion later in this section.
Line Errored Seconds (LES)
A Line Errored Second, according to T1.231, is a second
in which one or more Line Code Violation error events
were detected.
While many implementations are currently unable to detect
the zero strings, it is expected that interface
manufacturers will add this capability in deference to
Expires August 1996 [Page 11]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
ANSI; therefore, it will become available in time.
In the T1.231 specification, near end Line Code
Violations and far end Line Errored Seconds are counted.
For consistency, we count Line Errored Seconds at both
ends.
Controlled Slip Seconds (CSS)
A Controlled Slip Second, according to T1.231, is a
one-second interval containing one or more controlled
slips.
Errored Seconds (ES)
According to T1.231, For ESF and E1-CRC links an Errored
Second is a second with one or more Path Code Violation
OR one or more Out of Frame defects OR one or more
Controlled Slip events OR a detected AIS defect.
For D4 and E1-noCRC links, the presence of Bipolar
Violations also triggers an Errored Second.
This is not incremented during an Unavailable Second.
Bursty Errored Seconds (BES)
A Bursty Errored Second (also known as Errored Second
type B in T1.231) is a second with fewer than 320 and
more than 1 Path Coding Violation error events, no
Severely Errored Frame defects and no detected
incoming AIS defects. Controlled slips are not
included in this parameter.
This is not incremented during an Unavailable Second.
Severely Errored Seconds (SES)
According to T1.231, a Severely Errored Second for ESF
signals is a second with 320 or more Path Code
Violation Error Events OR one or more Out of Frame
defects OR a detected AIS defect.
For E1-CRC signals, a Severely Errored Second is a second
with 832 or more Path Code Violation error events OR one
or more Out of Frame defects.
For E1-noCRC signals, a Severely Errored Second is a 2048
LCVs or more.
Expires August 1996 [Page 12]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
For D4 signals, a Severely Errored Second is a count of
one-second intervals with Framing Error events, or an OOF
defect, or 1544 LCVs or more.
Controlled slips are not included in this parameter.
This is not incremented during an Unavailable Second.
Severely Errored Framing Second (SEFS)
An Severely Errored Framing Second is a second with one
or more Out of Frame defects OR a detected AIS defect,
according to T1.231
Degraded Minutes
A Degraded Minute is one in which the estimated error
rate exceeds 1E-6 but does not exceed 1E-3 (see G.821
[13]).
Degraded Minutes are determined by collecting all of the
Available Seconds, removing any Severely Errored Seconds
grouping the result in 60-second long groups and counting
a 60-second long group (a.k.a., minute) as degraded if the
cumulative errors during the seconds present in the group
exceed 1E-6. Available seconds are merely those seconds
which are not Unavailable as described below.
Unavailable Seconds (UAS)
Unavailable Seconds (UAS) are calculated by counting the
number of seconds that the interface is unavailable. The
DS1 interface is said to be unavailable from the onset of
10 contiguous SESs, or the onset of the condition leading
to a failure (see Failure States). If the condition
leading to the failure was immediately preceded by one or
more contiguous SESs, then the DS1 interface
unavailability starts from the onset of these SESs. Once
unavailable, and if no failure is present, the DS1
interface becomes available at the onset of 10 contiguous
seconds with no SESs. Once unavailable, and if a failure
is present, the DS1 interface becomes available at the
onset of 10 contiguous seconds with no SESs, if the
failure clearing time is less than or equal to 10
seconds. If the failure clearing time is more than 10
seconds, the DS1 interface becomes available at the onset
of 10 contiguous seconds with no SESs, or the onset
period leading to the successful clearing condition,
Expires August 1996 [Page 13]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
whichever occurs later. With respect to the DS1 error
counts, all counters are incremented while the DS1
interface is deemed available. While the interface is
deemed unavailable, the only count that is incremented is
UASs. (See T1.231)
A special case exists when the 10 or more second period
crosses the 900 second statistics window boundary, as the
foregoing description implies that the Severely Errored
Second and Unavailable Second counters for the PREVIOUS
interval must be adjusted when the Unavailable Signal
State is entered. Clearly, successive GETs of the
affected dsx1IntervalSESs and dsx1IntervalUASs objects
will return differing values if the first GET occurs
during the first few seconds of the window. This is
viewed as an unavoidable side-effect of selecting the
presently defined managed objects as a basis for this memo.
To summarize, when the unavialable state is entered, SES
is reduced by 10 and UAS is increased by 10. The linkDown
trap is sent at the start of the unavailable period, but
the time on the trap will be tate of the first UAS,
(i.e. 10 seconds earlier).
The UAS effect can be acheived by using a delay technique.
This is described in Appendix B.
3.4.4. Failure States
The following failure states are received, or detected failures, that
are reported in the dsx1LineStatus object. When a DS1 interface would,
if ever, produce the conditions leading to the failure state is
described in the appropriate specification.
Far End Alarm Failure
The Far End Alarm failure is also known as "Yellow Alarm"
in the DS1 case, "Distant Alarm" in the E1 case, and
"and Remote Alarm in the DS2 case." . (See T1.231)
For D4 links, the Far End Alarm failure is declared when
bit 6 of all channels has been zero for at least 335 ms
and is cleared when bit 6 of at least one channel is
non-zero for a period T, where T is usually less than one
second and always less than 5 seconds. The Far End Alarm
failure is not declared for D4 links when a Loss of
Expires August 1996 [Page 14]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Signal is detected.
For ESF links, the Far End Alarm failure is declared if
the Yellow Alarm signal pattern occurs in at least seven
out of ten contiguous 16-bit pattern intervals and is
cleared if the Yellow Alarm signal pattern does not occur
in ten contiguous 16-bit signal pattern intervals.
For E1 links, the Far End Alarm failure is declared when
bit 3 of time-slot zero is received set to one on two
consecutive occasions. The Far End Alarm failure is
cleared when bit 3 of time-slot zero is received set to
zero.
For DS2 links, if a loss of frame alignment (LOF or LOS)
and/or DS2 AIS condition, is detected, the RAI signal
shall be generated and transmitted to the remote side.
The Remote Alarm Indication(RAI) signal is defined on
m-bits as a repetition of the 16bit sequence consisting
of eight binary '1s' and eight binary '0s' in
m-bits(1111111100000000). When the RAI signal is not
sent (in normal operation),the HDLC flag pattern
(01111110) in the m-bit is sent.
The RAI failure is detected when 16 or more consecutive
RAI-patterns (1111111100000000) are received. The RAI
failure is cleared when 4 or more consecutive
incorrect-RAI-patterns are received.
Alarm Indication Signal (AIS) Failure
The Alarm Indication Signal failure is declared when an
AIS defect is detected at the input and the AIS defect
still exists after the Loss Of Frame failure (which is
caused by the unframed nature of the 'all-ones' signal)
is declared. The AIS failure is cleared when the Loss Of
Frame failure is cleared. (See T1.231)
An AIS defect at a 6312 kbit/s (G.704) interface is
detected when the incoming signal has two {2} or less
ZEROs in a sequence of 3156 bits (0.5ms).
The AIS signal defect is cleared when the incoming signal
has three {3} or more ZEROs in a sequence of 3156 bits
(0.5ms).
Expires August 1996 [Page 15]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Loss Of Frame Failure
For DS1 links, the Loss Of Frame failure is declared when
an OOF or LOS defect has persisted for T seconds, where
2 <= T <= 10. The Loss Of Frame failure is cleared when
there have been no OOF or LOS defects during a period T
where 0 <= T <= 20. Many systems will perform "hit
integration" within the period T before declaring or
clearing the failure e.g., see TR 62411 [14].
For E1 links, the Loss Of Frame Failure is declared when
an OOF defect is detected.
Loss Of Signal Failure
For DS1, the Loss Of Signal failure is declared upon
observing 175 +/- 75 contiguous pulse positions with no
pulses of either positive or negative polarity. The LOS
failure is cleared upon observing an average pulse
density of at least 12.5% over a period of 175 +/- 75
contiguous pulse positions starting with the receipt of a
pulse.
For E1 links, the Loss Of Signal failure is declared when
greater than 10 consecutive zeroes are detected (see
O.162 Section 3.4.4).
A LOS defect at 6312kbit/s interfaces is detected when
the incoming signal has "no transitions", i.e. when the
signal level is less than or equal to a signal level of
35dB below nominal, for N consecutive pulse intervals,
where 10 <=N<=255.
The LOS defect is cleared when the incoming signal has
"transitions", i.e. when the signal level is greater
than or equal to a signal level of 9dB below nominal,
for N consecutive pulse intervals, where 10<=N<=255.
A signal with "transitions" corresponds to a G.703
compliant signal.
Loopback Pseudo-Failure
The Loopback Pseudo-Failure is declared when the near end
equipment has placed a loopback (of any kind) on the DS1.
This allows a management entity to determine from one
object whether the DS1 can be considered to be in service
or not (from the point of view of the near end
Expires August 1996 [Page 16]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
equipment).
TS16 Alarm Indication Signal Failure
For E1 links, the TS16 Alarm Indication Signal failure is
declared when time-slot 16 is received as all ones for
all frames of two consecutive multiframes (see G.732
Section 4.2.6). This condition is never declared for DS1.
Loss Of MultiFrame Failure
The Loss Of MultiFrame failure is declared when two
consecutive multiframe alignment signals (bits 4 through
7 of TS16 of frame 0) have been received with an error.
The Loss Of Multiframe failure is cleared when the first
correct multiframe alignment signal is received. The
Loss Of Multiframe failure can only be declared for E1
links operating with G.732 [16] framing (sometimes called
"Channel Associated Signalling" mode).
Far End Loss Of Multiframe Failure
The Far End Loss Of Multiframe failure is declared when
bit 2 of TS16 of frame 0 is received set to one on two
consecutive occasions. The Far End Loss Of Multiframe
failure is cleared when bit 2 of TS16 of frame 0 is
received set to zero. The Far End Loss Of Multiframe
failure can only be declared for E1 links operating in
"Channel Associated Signalling" mode. (See G.732)
DS2 Payload AIS Failure
The DS2 Payload AIS is detected when the incoming signal
of the 6,312 kbps frame payload [TS1-TS96] has 2 or less
0's in a sequence of 3072 bits (0.5ms). The DS2 Payload
AIS is cleared when the incoming signal of the 6,312 kbps
frame payload [TS1-TS96] has 3 or more 0's in a sequence
of 3072 bits (0.5 ms).
DS2 Performance Threshold
DS2 Performance Threshold Failure monitors equipment
performance and is based on the CRC (Cyclic Redundancy
Check) Procedure defined in G.704.
The DS2 Performance Threshold Failure is detected when
the bit error ratio exceeds 10^-4 (Performance Threshold),
and the DS2 Performance Threshold Failure shall be cleared
when the bit error ratio decreased to less than 10^-6."
Expires August 1996 [Page 17]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
3.4.5. Other Terms
Circuit Identifier
This is a character string specified by the circuit
vendor, and is useful when communicating with the vendor
during the troubleshooting process.
Expires August 1996 [Page 18]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
4. Object Definitions
DS1-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Gauge32, NOTIFICATION-TYPE
FROM SNMPv2-SMI
DisplayString, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
transmission
FROM RFC1213-MIB;
-- This is the MIB module for the DS1, E1, DS2, and E2 Interface
-- objects.
ds1 MODULE-IDENTITY
LAST-UPDATED "9602032200Z"
ORGANIZATION "IETF Trunk MIB Working Group"
CONTACT-INFO
" David Fowler
Postal: Newbridge Networks Corporation
600 March Road
Kanata, Ontario, Canada K2K 2E6
Tel: +1 613 591 3600
Fax: +1 613 591 3680
E-mail: davef@newbridge.com"
DESCRIPTION
"The MIB module to describe
DS1 interfaces objects."
::= { transmission 18 }
-- note that this subsumes cept (19); there is no separate CEPT MIB
Expires August 1996 [Page 19]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- The DS1 Near End Group
-- Implementation of this group is mandatory for all
-- systems that attach to a DS1 Interface.
-- The DS1 Near End Group consists of four tables:
-- DS1 Configuration
-- DS1 Current
-- DS1 Interval
-- DS1 Total
-- the DS1 Configuration Table
dsx1ConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1ConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Configuration table."
::= { ds1 6 }
dsx1ConfigEntry OBJECT-TYPE
SYNTAX Dsx1ConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Configuration table."
INDEX { dsx1LineIndex }
::= { dsx1ConfigTable 1 }
Dsx1ConfigEntry ::=
SEQUENCE {
dsx1LineIndex
INTEGER,
dsx1IfIndex
INTEGER,
dsx1TimeElapsed
INTEGER,
dsx1ValidIntervals
INTEGER,
dsx1LineType
INTEGER,
dsx1LineCoding
INTEGER,
dsx1SendCode
Expires August 1996 [Page 20]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
INTEGER,
dsx1CircuitIdentifier
DisplayString,
dsx1LoopbackConfig
INTEGER,
dsx1LineStatus
INTEGER,
dsx1SignalMode
INTEGER,
dsx1TransmitClockSource
INTEGER,
dsx1Fdl
INTEGER,
dsx1InvalidIntervals
INTEGER,
dsx1LineLength
INTEGER,
dsx1LineStatusLastChange
TimeStamp,
dsx1LineStatusChangeTrapEnable
INTEGER
}
dsx1LineIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object should be made equal to ifIndex. The
next pargraph describes its previous usage.
Making the object equal to ifIndex allows proper
use of ifStackTable and ds0/ds0bundle mibs.
Previously, this object is the identifier of a DS1
Interface on a managed device. If there is an
ifEntry that is directly associated with this and
only this DS1 interface, it should have the same
value as ifIndex. Otherwise, number the
dsx3LineIndices with an unique identifier
following the rules of choosing a number that is
greater than ifNumber and numbering the inside
interfaces (e.g., equipment side) with even
numbers and outside interfaces (e.g, network side)
with odd numbers."
::= { dsx1ConfigEntry 1 }
Expires August 1996 [Page 21]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1IfIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"This value for this object is equal to the value
of ifIndex from the Interfaces table of MIB II
(RFC 1213)."
::= { dsx1ConfigEntry 2 }
dsx1TimeElapsed OBJECT-TYPE
SYNTAX INTEGER (0..899)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds that have elapsed since the
beginning of the near end current error-
measurement period."
::= { dsx1ConfigEntry 3 }
dsx1ValidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of previous near end intervals for
which valid data was collected. The value will be
96 unless the interface was brought online within
the last 24 hours, in which case the value will be
the number of complete 15 minute near end
intervals since the interface has been online. In
the case where the agent is a proxy, it is
possible that some intervals are unavailable. In
this case, this interval is the maximum interval
number for which valid data is available."
::= { dsx1ConfigEntry 4 }
dsx1LineType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
dsx1ESF(2),
dsx1D4(3),
dsx1E1(4),
dsx1E1CRC(5),
dsx1E1MF(6),
Expires August 1996 [Page 22]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1E1CRCMF(7),
dsx1Unframed(8),
dsx1E1Unframed(9)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the variety of DS1
Line implementing this circuit. The type of
circuit affects the number of bits per second
that the circuit can reasonably carry, as well
as the interpretation of the usage and error
statistics. The values, in sequence, describe:
TITLE: SPECIFICATION:
dsx1ESF Extended SuperFrame DS1
dsx1D4 AT&T D4 format DS1
dsx1E1 CCITT Recommendation G.704
(Table 4a)
dsx1E1-CRC CCITT Recommendation G.704
(Table 4b)
dsxE1-MF G.704 (Table 4a) with TS16
multiframing enabled
dsx1E1-CRC-MF G.704 (Table 4b) with TS16
multiframing enabled
dsx1Unframed No Framing performed
dsx1E1Unframed E1 with No Framing"
::= { dsx1ConfigEntry 5 }
dsx1LineCoding OBJECT-TYPE
SYNTAX INTEGER {
dsx1JBZS (1),
dsx1B8ZS (2),
dsx1HDB3 (3),
dsx1ZBTSI (4),
dsx1AMI (5),
other(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable describes the variety of Zero Code
Suppression used on this interface, which in turn
affects a number of its characteristics.
Expires August 1996 [Page 23]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1JBZS refers the Jammed Bit Zero Suppression,
in which the AT&T specification of at least one
pulse every 8 bit periods is literally implemented
by forcing a pulse in bit 8 of each channel.
Thus, only seven bits per channel, or 1.344 Mbps,
is available for data.
dsx1B8ZS refers to the use of a specified pattern
of normal bits and bipolar violations which
are used to replace a sequence of eight zero
bits.
ANSI Clear Channels may use dsx1ZBTSI, or Zero
Byte Time Slot Interchange.
E1 links, with or without CRC, use dsx1HDB3 or
dsx1AMI.
dsx1AMI refers to a mode wherein no zero code
suppression is present and the line encoding
does not solve the problem directly. In this
application, the higher layer must provide data
which meets or exceeds the pulse density
requirements, such as inverting HDLC data."
::= { dsx1ConfigEntry 6 }
dsx1SendCode OBJECT-TYPE
SYNTAX INTEGER {
dsx1SendNoCode(1),
dsx1SendLineCode(2),
dsx1SendPayloadCode(3),
dsx1SendResetCode(4),
dsx1SendQRS(5),
dsx1Send511Pattern(6),
dsx1Send3in24Pattern(7),
dsx1SendOtherTestPattern(8)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates what type of code is
being sent across the DS1 interface by the device.
Setting this variable causes the interface to send
the code requested. The values mean:
Expires August 1996 [Page 24]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1SendNoCode
sending looped or normal data
dsx1SendLineCode
sending a request for a line loopback
dsx1SendPayloadCode
sending a request for a payload loopback
dsx1SendResetCode
sending a loopback termination request
dsx1SendQRS
sending a Quasi-Random Signal (QRS) test
pattern
dsx1Send511Pattern
sending a 511 bit fixed test pattern
dsx1Send3in24Pattern
sending a fixed test pattern of 3 bits set
in 24
dsx1SendOtherTestPattern
sending a test pattern other than those
described by this object"
::= { dsx1ConfigEntry 7 }
dsx1CircuitIdentifier OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable contains the transmission vendor's
circuit identifier, for the purpose of
facilitating troubleshooting."
::= { dsx1ConfigEntry 8 }
dsx1LoopbackConfig OBJECT-TYPE
SYNTAX INTEGER {
dsx1NoLoop(1),
dsx1PayloadLoop(2),
dsx1LineLoop(3),
dsx1OtherLoop(4),
dsxInwardLoop(5)
}
Expires August 1996 [Page 25]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable represents the loopback configuration
of the DS1 interface. Agents supporting read/write
access should return badValue in response to a
requested loopback state that the interface does not
support. The values mean:
dsx1NoLoop
Not in the loopback state. A device that is
not capable of performing a loopback on
the interface shall always return this as
it's value.
dsx1PayloadLoop
The received signal at this interface is looped
through the device. Typically the received signal
is looped back for retransmission after it has
passed through the device's framing function.
dsx1LineLoop
The received signal at this interface does not
go through the device (minimum penetration) but
is looped back out.
dsx1OtherLoop
Loopbacks that are not defined here.
dsx1InwardLoop
The transmitted signal at this interface is looped
back and received by the same interface. What is
transmitted onto the line is product dependent."
::= { dsx1ConfigEntry 9 }
dsx1LineStatus OBJECT-TYPE
SYNTAX INTEGER (1..131071)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates the Line Status of the
interface. It contains loopback, failure, re-
ceived 'alarm' and transmitted 'alarms infor-
mation.
The dsx1LineStatus is a bit map represented as a sum,
Expires August 1996 [Page 26]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
therefore, it can represent multiple failures (alarms) and
a LoopbackState simultaneously.
dsx1NoAlarm should be set if and only if no other flag is
set.
If the dsx1loopbackState bit is set, the loopback in ef-
fect can be determined from the dsx1loopbackConfig object.
The various bit positions are:
1 dsx1NoAlarm No alarm present
2 dsx1RcvFarEndLOF Far end LOF (a.k.a., Yellow Alarm)
4 dsx1XmtFarEndLOF Near end sending LOF Indication
8 dsx1RcvAIS Far end sending AIS
16 dsx1XmtAIS Near end sending AIS
32 dsx1LossOfFrame Near end LOF (a.k.a., Red Alarm)
64 dsx1LossOfSignal Near end Loss Of Signal
128 dsx1LoopbackState Near end is looped
256 dsx1T16AIS E1 TS16 AIS
512 dsx1RcvFarEndLOMF Far End Sending TS16 LOMF
1024 dsx1XmtFarEndLOMF Near End Sending TS16 LOMF
2048 dsx1RcvTestCode Near End detects a test code
4096 dsx1OtherFailure any line status not defined here
8192 dsx1UnavailSigState Near End in Unavailable Signal
State
16384 dsx1NetEquipOOS Carrier Equipment Out of Service
32768 dsx1RcvPayloadAIS DS2 Payload AIS
65536 dsx1Ds2PerfThreshold DS2 Performance Threshold
Exceeded"
::= { dsx1ConfigEntry 10 }
dsx1SignalMode OBJECT-TYPE
SYNTAX INTEGER {
none (1),
robbedBit (2),
bitOriented (3),
messageOriented (4),
other (5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"'none' indicates that no bits are reserved for
signaling on this channel.
Expires August 1996 [Page 27]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
'robbedBit' indicates that DS1 Robbed Bit Sig-
naling is in use.
'bitOriented' indicates that E1 Channel Asso-
ciated Signaling is in use.
'messageOriented' indicates that Common Chan-
nel Signaling is in use either on channel 16 of
an E1 link or channel 24 of a DS1."
::= { dsx1ConfigEntry 11 }
dsx1TransmitClockSource OBJECT-TYPE
SYNTAX INTEGER {
loopTiming(1),
localTiming(2),
throughTiming(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The source of Transmit Clock.
'loopTiming' indicates that the recovered re-
ceive clock is used as the transmit clock.
'localTiming' indicates that a local clock
source is used.
'throughTiming' indicates that recovered re-
ceive clock from another interface is used as
the transmit clock."
::= { dsx1ConfigEntry 12 }
dsx1Fdl OBJECT-TYPE
SYNTAX INTEGER (1..15)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This bitmap describes the use of the facili-
ties data link, and is the sum of the capabili-
ties. Set any bits that are appropriate:
other(1),
dsx1Ansi-T1-403(2),
dsx1Att-54016(4),
dsx1Fdl-none(8)
Expires August 1996 [Page 28]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
'other' indicates that a protocol other than
one following is used.
'dsx1Ansi-T1-403' refers to the FDL exchange
recommended by ANSI.
'dsx1Att-54016' refers to ESF FDL exchanges.
'dsx1Fdl-none' indicates that the device does
not use the FDL."
::= { dsx1ConfigEntry 13 }
dsx1InvalidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of intervals for which no valid data
is
available."
::= { dsx1ConfigEntry 14 }
dsx1LineLength OBJECT-TYPE
SYNTAX INTEGER (0..64000)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The length of the ds1 line in meters."
::= { dsx1ConfigEntry 15 }
dsx1LineStatusLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of MIB II's sysUpTime
object at the
time this DS1 entered its current
line status state.
If the current state was entered
prior to the last
re-initialization of the proxy-agent,
then this
object contains a zero value."
::= { dsx1ConfigEntry 16 }
Expires August 1996 [Page 29]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1LineStatusChangeTrapEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1),
disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether dsx1LineStatusChange traps
should be generated for this interface. By
default, this object should have the value
disabled(2)."
::= { dsx1ConfigEntry 17 }
Expires August 1996 [Page 30]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- the DS1 Current Table
-- The DS1 current table contains various statistics being
-- collected for the current 15 minute interval.
dsx1CurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1CurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Current table."
::= { ds1 7 }
dsx1CurrentEntry OBJECT-TYPE
SYNTAX Dsx1CurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Current table."
INDEX { dsx1CurrentIndex }
::= { dsx1CurrentTable 1 }
Dsx1CurrentEntry ::=
SEQUENCE {
dsx1CurrentIndex
INTEGER,
dsx1CurrentESs
Gauge32,
dsx1CurrentSESs
Gauge32,
dsx1CurrentSEFSs
Gauge32,
dsx1CurrentUASs
Gauge32,
dsx1CurrentCSSs
Gauge32,
dsx1CurrentPCVs
Gauge32,
dsx1CurrentLESs
Gauge32,
dsx1CurrentBESs
Gauge32,
dsx1CurrentDMs
Gauge32,
Expires August 1996 [Page 31]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1CurrentLCVs
Gauge32
}
dsx1CurrentIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value as a dsx1LineIndex
object instance."
::= { dsx1CurrentEntry 1 }
dsx1CurrentESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Errored Seconds, encountered by
a DS1 interface in the current 15 minute inter-
val. noSuchInstance will be returned if no data
is available."
::= { dsx1CurrentEntry 2 }
dsx1CurrentSESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds encoun-
tered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1CurrentEntry 3 }
dsx1CurrentSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
Expires August 1996 [Page 32]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds
encountered by a DS1 interface in the current
15 minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1CurrentEntry 4 }
dsx1CurrentUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in the current 15 minute in-
terval. noSuchInstance will be returned if no data
is available."
::= { dsx1CurrentEntry 5 }
dsx1CurrentCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds encoun-
tered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1CurrentEntry 6 }
dsx1CurrentPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations encoun-
tered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1CurrentEntry 7 }
Expires August 1996 [Page 33]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1CurrentLESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds encountered
by a DS1 interface in the current 15 minute in-
terval. noSuchInstance will be returned if no data
is available."
::= { dsx1CurrentEntry 8 }
dsx1CurrentBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the current
15 minute interval. noSuchInstance will be returned
if no data is available."
::= {dsx1CurrentEntry 9 }
dsx1CurrentDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1CurrentEntry 10 }
dsx1CurrentLCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
Expires August 1996 [Page 34]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
::= {dsx1CurrentEntry 11 }
Expires August 1996 [Page 35]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- the DS1 Interval Table
-- The DS1 Interval Table contains various statistics
-- collected by each DS1 Interface over the previous 24 hours of
-- operation. The past 24 hours are broken into 96 completed
-- 15 minute intervals.
dsx1IntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1IntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Interval table."
::= { ds1 8 }
dsx1IntervalEntry OBJECT-TYPE
SYNTAX Dsx1IntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Interval table."
INDEX { dsx1IntervalIndex, dsx1IntervalNumber }
::= { dsx1IntervalTable 1 }
Dsx1IntervalEntry ::=
SEQUENCE {
dsx1IntervalIndex
INTEGER,
dsx1IntervalNumber
INTEGER,
dsx1IntervalESs
Gauge32,
dsx1IntervalSESs
Gauge32,
dsx1IntervalSEFSs
Gauge32,
dsx1IntervalUASs
Gauge32,
dsx1IntervalCSSs
Gauge32,
dsx1IntervalPCVs
Gauge32,
dsx1IntervalLESs
Gauge32,
Expires August 1996 [Page 36]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1IntervalBESs
Gauge32,
dsx1IntervalDMs
Gauge32,
dsx1IntervalLCVs
Gauge32,
dsx1IntervalValidData
INTEGER
}
dsx1IntervalIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value as a dsx1LineIndex
object instance."
::= { dsx1IntervalEntry 1 }
dsx1IntervalNumber OBJECT-TYPE
SYNTAX INTEGER (1..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number between 1 and 96, where 1 is the most
recently completed 15 minute interval and 96 is
the 15 minutes interval completed 23 hours and
45 minutes prior to interval 1."
::= { dsx1IntervalEntry 2 }
dsx1IntervalESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Errored Seconds encountered by a
DS1 interface in one of the previous 96, indi-
vidual 15 minute, intervals. In the case where
the agent is a proxy and valid data is not
Expires August 1996 [Page 37]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
available, return noSuchInstance."
::= { dsx1IntervalEntry 3 }
dsx1IntervalSESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1IntervalEntry 4 }
dsx1IntervalSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds
encountered by a DS1 interface in one of the
previous 96, individual 15 minute, intervals.
In the case where the agent is a proxy and
valid data is not available, return
noSuchInstance."
::= { dsx1IntervalEntry 5 }
dsx1IntervalUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in one of the previous 96,
individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance. This object may
decrease if the occurance of unavailable seconds
occurs across an inteval boundary."
::= { dsx1IntervalEntry 6 }
Expires August 1996 [Page 38]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1IntervalCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1IntervalEntry 7 }
dsx1IntervalPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1IntervalEntry 8 }
dsx1IntervalLESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds encountered
by a DS1 interface in one of the previous 96,
individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is
not available, return noSuchInstance."
::= { dsx1IntervalEntry 9 }
dsx1IntervalBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
Expires August 1996 [Page 39]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
encountered by a DS1 interface in one of the
previous 96, individual 15 minute, intervals. In
the case where the agent is a proxy and
valid data is not available, return
noSuchInstance."
::= {dsx1IntervalEntry 10 }
dsx1IntervalDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1IntervalEntry 11 }
dsx1IntervalLCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. In the case where the agent is
a proxy and valid data is not available, return
noSuchInstance."
::= {dsx1IntervalEntry 12 }
dsx1IntervalValidData OBJECT-TYPE
SYNTAX INTEGER {
true(1),
false(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates if there is valid data
for this interval. A value of true(1)
indicates the data is valid."
::= {dsx1IntervalEntry 13 }
Expires August 1996 [Page 40]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- the DS1 Total
-- The DS1 Total Table contains the cumulative sum of the
-- various statistics for the 24 hour period preceding the
-- current interval.
dsx1TotalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1TotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Total table. 24 hour interval."
::= { ds1 9 }
dsx1TotalEntry OBJECT-TYPE
SYNTAX Dsx1TotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Total table."
INDEX { dsx1TotalIndex }
::= { dsx1TotalTable 1 }
Dsx1TotalEntry ::=
SEQUENCE {
dsx1TotalIndex
INTEGER,
dsx1TotalESs
Gauge32,
dsx1TotalSESs
Gauge32,
dsx1TotalSEFSs
Gauge32,
dsx1TotalUASs
Gauge32,
dsx1TotalCSSs
Gauge32,
dsx1TotalPCVs
Gauge32,
dsx1TotalLESs
Gauge32,
dsx1TotalBESs
Gauge32,
dsx1TotalDMs
Expires August 1996 [Page 41]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Gauge32,
dsx1TotalLCVs
Gauge32
}
dsx1TotalIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value as a dsx1LineIndex
object instance."
::= { dsx1TotalEntry 1 }
dsx1TotalESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of Errored Seconds encountered by a
DS1 interface in the previous 24 hour interval.
Invalid 15 minute intervals count as 0."
::= { dsx1TotalEntry 2 }
dsx1TotalSESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Severely Errored Seconds encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1TotalEntry 3 }
dsx1TotalSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
Expires August 1996 [Page 42]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
STATUS current
DESCRIPTION
"The number of Severely Errored Framing Seconds
encountered by a DS1 interface in the previous
24 hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1TotalEntry 4 }
dsx1TotalUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in the previous 24 hour in-
terval. Invalid 15 minute intervals count as 0."
::= { dsx1TotalEntry 5 }
dsx1TotalCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Controlled Slip Seconds encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals count
as 0."
::= { dsx1TotalEntry 6 }
dsx1TotalPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Path Coding Violations encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals count
as 0."
::= { dsx1TotalEntry 7 }
dsx1TotalLESs OBJECT-TYPE
Expires August 1996 [Page 43]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Errored Seconds encountered
by a DS1 interface in the previous 24 hour in-
terval. Invalid 15 minute intervals count as 0."
::= { dsx1TotalEntry 8 }
dsx1TotalBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the previous
24 hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1TotalEntry 9 }
dsx1TotalDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals count
as 0."
::= { dsx1TotalEntry 10 }
dsx1TotalLCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. Invalid 15 minute intervals
count as 0."
::= {dsx1TotalEntry 11 }
Expires August 1996 [Page 44]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- The DS1 Far End Group
-- Implementation of this group is optional for all systems
-- that attach to a DS1 Interface.
-- The DS1 Far End Group consists of three tables:
-- DS1 Far End Current
-- DS1 Far End Interval
-- DS1 Far End Total
-- The DS1 Far End Current Table
-- The DS1 Far End Current table contains various statistics
-- being collected for the current 15 minute interval.
-- The statistics are collected from the far end messages on the
-- Facilities Data Link. The definitions are the same as
-- described for the near-end information.
dsx1FarEndCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Current table."
::= { ds1 10 }
dsx1FarEndCurrentEntry OBJECT-TYPE
SYNTAX Dsx1FarEndCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Current table."
INDEX { dsx1FarEndCurrentIndex }
::= { dsx1FarEndCurrentTable 1 }
Dsx1FarEndCurrentEntry ::=
SEQUENCE {
dsx1FarEndCurrentIndex
INTEGER,
dsx1FarEndTimeElapsed
INTEGER,
dsx1FarEndValidIntervals
INTEGER,
dsx1FarEndCurrentESs
Expires August 1996 [Page 45]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Gauge32,
dsx1FarEndCurrentSESs
Gauge32,
dsx1FarEndCurrentSEFSs
Gauge32,
dsx1FarEndCurrentUASs
Gauge32,
dsx1FarEndCurrentCSSs
Gauge32,
dsx1FarEndCurrentLESs
Gauge32,
dsx1FarEndCurrentPCVs
Gauge32,
dsx1FarEndCurrentBESs
Gauge32,
dsx1FarEndCurrentDMs
Gauge32,
dsx1FarEndInvalidIntervals
INTEGER
}
dsx1FarEndCurrentIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value an dsx1LineIndex
object instance."
::= { dsx1FarEndCurrentEntry 1 }
dsx1FarEndTimeElapsed OBJECT-TYPE
SYNTAX INTEGER (0..899)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds that have elapsed
since the beginning of the far end current
error-measurement period."
::= { dsx1FarEndCurrentEntry 2 }
Expires August 1996 [Page 46]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndValidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of previous far end intervals
for which valid data was collected. The
value will be 96 unless the interface was
brought online within the last 24 hours,
in which case the value will be the number
of complete 15 minute far end intervals
since the interface has been online."
::= { dsx1FarEndCurrentEntry 3 }
dsx1FarEndCurrentESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far Far End Errored Seconds en-
countered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1FarEndCurrentEntry 4 }
dsx1FarEndCurrentSESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Seconds
encountered by a DS1 interface in the current
15 minute interval. noSuchInstance will be
returned if no data is available."
::= { dsx1FarEndCurrentEntry 5 }
dsx1FarEndCurrentSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Framing
Expires August 1996 [Page 47]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Seconds encountered by a DS1 interface in the
current 15 minute interval. noSuchInstance will
be returned if no data is available."
::= { dsx1FarEndCurrentEntry 6 }
dsx1FarEndCurrentUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in the current 15 minute in-
terval. noSuchInstance will be returned if no data
is available."
::= { dsx1FarEndCurrentEntry 7 }
dsx1FarEndCurrentCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds
encountered by a DS1 interface in the current
15 minute interval. noSuchInstance will be
returned if no data is available."
::= { dsx1FarEndCurrentEntry 8 }
dsx1FarEndCurrentLESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds en-
countered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1FarEndCurrentEntry 9 }
dsx1FarEndCurrentPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
Expires August 1996 [Page 48]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations
reported via the far end block error count en-
countered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1FarEndCurrentEntry 10 }
dsx1FarEndCurrentBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the current
15 minute interval. noSuchInstance will be returned
if no data is available."
::= {dsx1FarEndCurrentEntry 11 }
dsx1FarEndCurrentDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in the current 15
minute interval. noSuchInstance will be returned
if no data is available."
::= { dsx1FarEndCurrentEntry 12 }
dsx1FarEndInvalidIntervals OBJECT-TYPE
SYNTAX INTEGER (0..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of intervals for which no valid
data is available."
::= { dsx1FarEndCurrentEntry 13 }
-- The DS1 Far End Interval Table
-- The DS1 Far End Interval Table contains various statistics
Expires August 1996 [Page 49]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- collected by each DS1 interface over the previous 24 hours of
-- operation. The past 24 hours are broken into 96
-- completed 15 minute intervals.
dsx1FarEndIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Interval table."
::= { ds1 11 }
dsx1FarEndIntervalEntry OBJECT-TYPE
SYNTAX Dsx1FarEndIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Interval table."
INDEX { dsx1FarEndIntervalIndex,
dsx1FarEndIntervalNumber }
::= { dsx1FarEndIntervalTable 1 }
Dsx1FarEndIntervalEntry ::=
SEQUENCE {
dsx1FarEndIntervalIndex
INTEGER,
dsx1FarEndIntervalNumber
INTEGER,
dsx1FarEndIntervalESs
Gauge32,
dsx1FarEndIntervalSESs
Gauge32,
dsx1FarEndIntervalSEFSs
Gauge32,
dsx1FarEndIntervalUASs
Gauge32,
dsx1FarEndIntervalCSSs
Gauge32,
dsx1FarEndIntervalLESs
Gauge32,
dsx1FarEndIntervalPCVs
Gauge32,
dsx1FarEndIntervalBESs
Gauge32,
Expires August 1996 [Page 50]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndIntervalDMs
Gauge32
}
dsx1FarEndIntervalIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value as a dsx1LineIndex
object instance."
::= { dsx1FarEndIntervalEntry 1 }
dsx1FarEndIntervalNumber OBJECT-TYPE
SYNTAX INTEGER (1..96)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number between 1 and 96, where 1 is the most
recently completed 15 minute interval and 96 is
the 15 minutes interval completed 23 hours and
45 minutes prior to interval 1."
::= { dsx1FarEndIntervalEntry 2 }
dsx1FarEndIntervalESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Errored Seconds encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 3 }
dsx1FarEndIntervalSESs OBJECT-TYPE
SYNTAX Gauge32
Expires August 1996 [Page 51]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Seconds
encountered by a DS1 interface in one of the
previous 96, individual 15 minute, intervals. In
the case where the agent is a proxy and valid
data is not available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 4 }
dsx1FarEndIntervalSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Framing
Seconds encountered by a DS1 interface in one
of the previous 96, individual 15 minute, in-
tervals. In the case where the agent is a proxy
and valid data is not available, return
noSuchInstance."
::= { dsx1FarEndIntervalEntry 5 }
dsx1FarEndIntervalUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in one of the previous 96,
individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 6 }
dsx1FarEndIntervalCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds
encountered by a DS1 interface in one of the
Expires August 1996 [Page 52]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
previous 96, individual 15 minute, intervals. In
the case where the agent is a proxy and valid
data is not available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 7 }
dsx1FarEndIntervalLESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds en-
countered by a DS1 interface in one of the pre-
vious 96, individual 15 minute, intervals. In
the case where the agent is a proxy and valid
data is not available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 8 }
dsx1FarEndIntervalPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations
reported via the far end block error count en-
countered by a DS1 interface in one of the pre-
vious 96, individual 15 minute, intervals. In
the case where the agent is a proxy and valid
data is not available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 9 }
dsx1FarEndIntervalBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in one of the
previous 96, individual 15 minute, intervals. In
the case where the agent is a proxy and valid
data is not available, return noSuchInstance."
::= {dsx1FarEndIntervalEntry 10 }
Expires August 1996 [Page 53]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndIntervalDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in one of the previous
96, individual 15 minute, intervals. In the case
where the agent is a proxy and valid data is not
available, return noSuchInstance."
::= { dsx1FarEndIntervalEntry 11 }
-- The DS1 Far End Total Table
-- The DS1 Far End Total Table contains the cumulative sum of the
-- various statistics for the 24 hour period preceding the
-- current interval.
dsx1FarEndTotalTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FarEndTotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DS1 Far End Total table."
::= { ds1 12 }
dsx1FarEndTotalEntry OBJECT-TYPE
SYNTAX Dsx1FarEndTotalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the DS1 Far End Total table."
INDEX { dsx1FarEndTotalIndex }
::= { dsx1FarEndTotalTable 1 }
Dsx1FarEndTotalEntry ::=
SEQUENCE {
dsx1FarEndTotalIndex
INTEGER,
dsx1FarEndTotalESs
Gauge32,
dsx1FarEndTotalSESs
Gauge32,
Expires August 1996 [Page 54]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndTotalSEFSs
Gauge32,
dsx1FarEndTotalUASs
Gauge32,
dsx1FarEndTotalCSSs
Gauge32,
dsx1FarEndTotalLESs
Gauge32,
dsx1FarEndTotalPCVs
Gauge32,
dsx1FarEndTotalBESs
Gauge32,
dsx1FarEndTotalDMs
Gauge32
}
dsx1FarEndTotalIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value an dsx1LineIndex
object instance."
::= { dsx1FarEndTotalEntry 1 }
dsx1FarEndTotalESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Errored Seconds encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 2 }
dsx1FarEndTotalSESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
Expires August 1996 [Page 55]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Seconds
encountered by a DS1 interface in the previous
24 hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 3 }
dsx1FarEndTotalSEFSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Severely Errored Framing
Seconds encountered by a DS1 interface in the
previous 24 hour interval. Invalid 15 minute
intervals count as 0."
::= { dsx1FarEndTotalEntry 4 }
dsx1FarEndTotalUASs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Unavailable Seconds encountered
by a DS1 interface in the previous 24 hour in-
terval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 5 }
dsx1FarEndTotalCSSs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Controlled Slip Seconds
encountered by a DS1 interface in the previous
24 hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 6 }
Expires August 1996 [Page 56]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndTotalLESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Line Errored Seconds en-
countered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 7 }
dsx1FarEndTotalPCVs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Far End Path Coding Violations
reported via the far end block error count en-
countered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 8 }
dsx1FarEndTotalBESs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the previous
24 hour interval. Invalid 15 minute intervals
count as 0."
::= { dsx1FarEndTotalEntry 9 }
dsx1FarEndTotalDMs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Degraded Minutes (DMs) encoun-
tered by a DS1 interface in the previous 24
hour interval. Invalid 15 minute intervals
Expires August 1996 [Page 57]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
count as 0."
::= { dsx1FarEndTotalEntry 10 }
Expires August 1996 [Page 58]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- the DS1 Fractional Group
-- This group is deprecated. It was mandatory for
-- systems dividing a DS1 into channels containing different
-- data streams that are of local interest. Systems which
-- are indifferent to data content, such as CSUs, need not
-- implement it.
-- The DS1 fractional table identifies which DS1 channels
-- associated with a CSU are being used to support a
-- logical interface, i.e., an entry in the interfaces table
-- from the Internet-standard MIB.
-- For example, consider an application managing a North
-- American ISDN Primary Rate link whose division is a 384 kbit/s
-- H1 "B" Channel for Video, a second H1 for data to a primary
-- routing peer, and 12 64 kbit/s H0 "B" Channels. Consider that
-- some subset of the H0 channels are used for voice and the
-- remainder are available for dynamic data calls.
-- we count a total of 14 interfaces multiplexed onto the DS1
-- interface. Six DS1 channels (for the sake of the example,
-- channels 1..6) are used for Video, six more (7..11 and 13)
-- are used for data, and the remaining 12 are are in channels
-- 12 and 14..24.
-- Let us further imagine that ifIndex 2 is of type DS1 and
-- refers to the DS1 interface, and that the interfaces layered
-- onto it are numbered 3..16.
-- We might describe the allocation of channels, in the
-- dsx1FracTable, as follows:
-- dsx1FracIfIndex.2. 1 = 3 dsx1FracIfIndex.2.13 = 4
-- dsx1FracIfIndex.2. 2 = 3 dsx1FracIfIndex.2.14 = 6
-- dsx1FracIfIndex.2. 3 = 3 dsx1FracIfIndex.2.15 = 7
-- dsx1FracIfIndex.2. 4 = 3 dsx1FracIfIndex.2.16 = 8
-- dsx1FracIfIndex.2. 5 = 3 dsx1FracIfIndex.2.17 = 9
-- dsx1FracIfIndex.2. 6 = 3 dsx1FracIfIndex.2.18 = 10
-- dsx1FracIfIndex.2. 7 = 4 dsx1FracIfIndex.2.19 = 11
-- dsx1FracIfIndex.2. 8 = 4 dsx1FracIfIndex.2.20 = 12
-- dsx1FracIfIndex.2. 9 = 4 dsx1FracIfIndex.2.21 = 13
-- dsx1FracIfIndex.2.10 = 4 dsx1FracIfIndex.2.22 = 14
-- dsx1FracIfIndex.2.11 = 4 dsx1FracIfIndex.2.23 = 15
-- dsx1FracIfIndex.2.12 = 5 dsx1FracIfIndex.2.24 = 16
Expires August 1996 [Page 59]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- For North American (DS1) interfaces, there are 24 legal
-- channels, numbered 1 through 24.
-- For G.704 interfaces, there are 31 legal channels,
-- numbered 1 through 31. The channels (1..31) correspond
-- directly to the equivalently numbered time-slots.
dsx1FracTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dsx1FracEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The DS1 Fractional table."
::= { ds1 13 }
dsx1FracEntry OBJECT-TYPE
SYNTAX Dsx1FracEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry in the DS1 Fractional table."
INDEX { dsx1FracIndex, dsx1FracNumber }
::= { dsx1FracTable 1 }
Dsx1FracEntry ::=
SEQUENCE {
dsx1FracIndex
INTEGER,
dsx1FracNumber
INTEGER,
dsx1FracIfIndex
INTEGER
}
dsx1FracIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The index value which uniquely identifies the
DS1 interface to which this entry is applicable
The interface identified by a particular
value of this index is the same interface as
Expires August 1996 [Page 60]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
identified by the same value an dsx1LineIndex
object instance."
::= { dsx1FracEntry 1 }
dsx1FracNumber OBJECT-TYPE
SYNTAX INTEGER (1..31)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The channel number for this entry."
::= { dsx1FracEntry 2 }
dsx1FracIfIndex OBJECT-TYPE
SYNTAX INTEGER (1..'7fffffff'h)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"An index value that uniquely identifies an
interface. The interface identified by a particular
value of this index is the same interface
as identified by the same value an ifIndex
object instance. If no interface is currently using
a channel, the value should be zero. If a
single interface occupies more than one time
slot, that ifIndex value will be found in multiple
time slots."
::= { dsx1FracEntry 3 }
Expires August 1996 [Page 61]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- conformance information
ds1Conformance OBJECT IDENTIFIER ::= { ds1 14 }
ds1Groups OBJECT IDENTIFIER ::= { ds1Conformance 1 } ds1Compliances
OBJECT IDENTIFIER ::= { ds1Conformance 2 }
-- compliance statements
ds1Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for DS1 interfaces."
MODULE -- this module
MANDATORY-GROUPS { ds1NearEndConfigGroup,
ds1NearEndCurrentGroup,
ds1NearEndIntervalGroup,
ds1NearEndTotalGroup }
GROUP ds1FarEndGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 Interface."
GROUP ds1NearEndOptionalConfigGroup
DESCRIPTION
"Implementation of this group is optional for all
systems that attach to a DS1 Interface."
GROUP ds1DS2Group
DESCRIPTION
"Implementation of this group is mandatory for all
systems that attach to a DS2 Interface."
::= { ds1Compliances 1 }
-- units of conformance
ds1NearEndConfigGroup OBJECT-GROUP
OBJECTS { dsx1TimeElapsed,
dsx1ValidIntervals,
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1CircuitIdentifier,
dsx1LoopbackConfig,
Expires August 1996 [Page 62]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1LineStatus,
dsx1SignalMode,
dsx1TransmitClockSource,
dsx1Fdl,
dsx1InvalidIntervals,
dsx1LineLength }
STATUS current
DESCRIPTION
"A collection of objects providing configuration
information applicable to all DS1 interfaces."
::= { ds1Groups 1 }
ds1NearEndCurrentGroup OBJECT-GROUP
OBJECTS { dsx1CurrentIndex,
dsx1CurrentESs,
dsx1CurrentSESs,
dsx1CurrentSEFSs,
dsx1CurrentUASs,
dsx1CurrentCSSs,
dsx1CurrentPCVs,
dsx1CurrentLESs,
dsx1CurrentBESs,
dsx1CurrentDMs,
dsx1CurrentLCVs }
STATUS current
DESCRIPTION
"A collection of objects providing statistics
information for the current interval applicable to
all DS1 interfaces."
::= { ds1Groups 2 }
ds1NearEndIntervalGroup OBJECT-GROUP
OBJECTS { dsx1IntervalIndex,
dsx1IntervalNumber,
dsx1IntervalESs,
dsx1IntervalSESs,
dsx1IntervalSEFSs,
dsx1IntervalUASs,
dsx1IntervalCSSs,
dsx1IntervalPCVs,
dsx1IntervalLESs,
dsx1IntervalBESs,
dsx1IntervalDMs,
dsx1IntervalLCVs,
dsx1IntervalValidData }
Expires August 1996 [Page 63]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
STATUS current
DESCRIPTION
"A collection of objects providing statistics
information for the last 96 intervals applicable
to all DS1 interfaces."
::= { ds1Groups 3 }
ds1NearEndTotalGroup OBJECT-GROUP
OBJECTS { dsx1TotalIndex,
dsx1TotalESs,
dsx1TotalSESs,
dsx1TotalSEFSs,
dsx1TotalUASs,
dsx1TotalCSSs,
dsx1TotalPCVs,
dsx1TotalLESs,
dsx1TotalBESs,
dsx1TotalDMs,
dsx1TotalLCVs }
STATUS current
DESCRIPTION
"A collection of objects providing statistics
information for the total of the last 96 intervals
applicable to all DS1 interfaces."
::= { ds1Groups 4 }
ds1FarEndGroup OBJECT-GROUP
OBJECTS { dsx1FarEndCurrentIndex,
dsx1FarEndTimeElapsed,
dsx1FarEndValidIntervals,
dsx1FarEndCurrentESs,
dsx1FarEndCurrentSESs,
dsx1FarEndCurrentSEFSs,
dsx1FarEndCurrentUASs,
dsx1FarEndCurrentCSSs,
dsx1FarEndCurrentLESs,
dsx1FarEndCurrentPCVs,
dsx1FarEndCurrentBESs,
dsx1FarEndCurrentDMs,
dsx1FarEndInvalidIntervals,
dsx1FarEndIntervalIndex,
dsx1FarEndIntervalNumber,
dsx1FarEndIntervalESs,
dsx1FarEndIntervalSESs,
dsx1FarEndIntervalSEFSs,
Expires August 1996 [Page 64]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndIntervalUASs,
dsx1FarEndIntervalCSSs,
dsx1FarEndIntervalLESs,
dsx1FarEndIntervalPCVs,
dsx1FarEndIntervalBESs,
dsx1FarEndIntervalDMs,
dsx1FarEndTotalIndex,
dsx1FarEndTotalESs,
dsx1FarEndTotalSESs,
dsx1FarEndTotalSEFSs,
dsx1FarEndTotalUASs,
dsx1FarEndTotalCSSs,
dsx1FarEndTotalLESs,
dsx1FarEndTotalPCVs,
dsx1FarEndTotalBESs,
dsx1FarEndTotalDMs }
STATUS current
DESCRIPTION
"A collection of objects providing remote
configuration and statistics information."
::= { ds1Groups 5 }
ds1DeprecatedGroup OBJECT-GROUP
OBJECTS { dsx1IfIndex,
dsx1FracIndex,
dsx1FracNumber,
dsx1FracIfIndex }
STATUS deprecated
DESCRIPTION
"A collection of obsolete objects that may be
implemented for backwards compatibility."
::= { ds1Groups 6 }
ds1NearEndOptionalConfigGroup OBJECT-GROUP
OBJECTS { dsx1LineStatusLastChange,
dsx1LineStatusChangeTrapEnable }
STATUS current
DESCRIPTION
"A collection of objects that may be implemented
on DS1 and DS2 interfaces."
::= { ds1Groups 7 }
ds1DS2Group OBJECT-GROUP
OBJECTS { dsx1LineIndex,
Expires August 1996 [Page 65]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1LineType,
dsx1LineCoding,
dsx1SendCode,
dsx1CircuitIdentifier,
dsx1LineStatus,
dsx1SignalMode,
dsx1TransmitClockSource }
STATUS current
DESCRIPTION
"A collection of objects providing
information about DS2 (6,312 kbps)
systems."
::= { ds1Groups 8 }
ds1TransStatsGroup OBJECT-GROUP
OBJECTS { dsx1CurrentESs,
dsx1CurrentSESs,
dsx1CurrentUASs,
dsx1IntervalESs,
dsx1IntervalSESs,
dsx1IntervalUASs,
dsx1TotalESs,
dsx1TotalSESs,
dsx1TotalUASs }
STATUS current
DESCRIPTION
"A collection of objects which are the
statistics which can be collected from a ds1
interface that is running transparent or unframed
lineType. Statistics not in this list should
return noSuchInstance."
::= { ds1Groups 9 }
Expires August 1996 [Page 66]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
-- Ds1 TRAPS
ds1Traps OBJECT IDENTIFIER ::= { ds1 15 }
dsx1LineStatusChange NOTIFICATION-TYPE
OBJECTS { dsx1LineStatus,
dsx1LineStatusLastChange }
STATUS current
DESCRIPTION
"A dsx1LineStatusChange trap is sent when the
value of an instance dsx1LineStatus changes. It
can be utilized by an NMS to trigger polls. When
the line status change results from a higher level
line status change (i.e. ds3), then no traps for
the ds1 are sent."
::= { ds1Traps 1 }
END
5. Appendix A - Use of dsx1IfIndex and dsx1LineIndex
Different physical configurations for the support of SNMP with DS1
equipment exist. To accommodate these scenarios, two different
indices for DS1 interfaces are introduced in this MIB. These indices
are dsx1IfIndex and dsx1LineIndex.
External interface scenario: the SNMP Agent represents all managed
DS1 lines as external interfaces (for example, an Agent residing on
the device supporting DS1 interfaces directly):
For this scenario, all interfaces are assigned an integer value equal
to ifIndex, and the following applies:
ifIndex=dsx1IfIndex=dsx1LineIndex for all interfaces.
The dsx1IfIndex column of the DS1 Configuration table relates each
DS1 interface to its corresponding interface (ifIndex) in the
Internet-standard MIB (MIB-II STD 17, RFC1213).
External&Internal interface scenario: the SNMP Agents resides on an
host external from the device supporting DS1 interfaces (e.g., a
Expires August 1996 [Page 67]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
router). The Agent represents both the host and the DS1 device. The
index dsx1LineIndex is used to not only represent the DS1 interfaces
external from the host/DS1-device combination, but also the DS1
interfaces connecting the host and the DS1 device. The index
dsx1IfIndex is always equal to ifIndex.
Example:
A shelf full of CSUs connected to a Router. An SNMP Agent residing on
the router proxies for itself and the CSU. The router has also an
Ethernet interface:
+-----+
| | |
| | | +---------------------+
|E | | 1.544 MBPS | Line#A | DS1 Link
|t | R |---------------+ - - - - - - - - - +------>
|h | | | |
|e | O | 1.544 MBPS | Line#B | DS1 Link
|r | |---------------+ - - - - - - - - - - +------>
|n | U | | CSU Shelf |
|e | | 1.544 MBPS | Line#C | DS1 Link
|t | T |---------------+ - - - -- -- - - - - +------>
| | | | |
|-----| E | 1.544 MBPS | Line#D | DS1 Link
| | |---------------+ - - - - -- - - - - +------>
| | R | |_____________________|
| | |
| +-----+
The assignment of the index values could for example be:
ifIndex (= dsx1IfIndex) dsx1LineIndex
1 NA NA (Ethernet)
2 Line#A Router Side 6
2 Line#A Network Side 7
3 Line#B Router Side 8
3 Line#B Network Side 9
4 Line#C Router Side 10
4 Line#C Network Side 11
5 Line#D Router Side 12
5 Line#D Network Side 13
For this example, ifNumber is equal to 5. Note the following
Expires August 1996 [Page 68]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
description of dsx1LineIndex: the dsx1LineIndex identifies a DS1
Interface on a managed device. If there is an ifEntry that is
directly associated with this and only this DS1 interface, it should
have the same value as ifIndex. Otherwise, number the
dsx1LineIndices with an unique identifier following the rules of
choosing a number greater than ifNumber and numbering inside
interfaces (e.g., equipment side) with even numbers and outside
interfaces (e.g., network side) with odd numbers.
If the CSU shelf is managed by itself by a local SNMP Agent, the
situation would be:
ifIndex (= dsx1IfIndex) dsx1LineIndex
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
6. Appendix B - The delay approach to Unavialable Seconds.
According to ANSI T1.231 unavailable time begins at the _onset_ of 10
contiguous severely errored seconds -- that is, unavailable time
starts with the _first_ of the 10 contiguous SESs. Also, while an
interface is deemed unavailable all counters for that interface are
frozen except for the UAS count. It follows that an implementation
which strictly complies with this standard must _not_ increment any
counters other than the UAS count -- even temporarily -- as a result
of anything that happens during those 10 seconds. Since changes in
the signal state lag the data to which they apply by 10 seconds, an
ANSI-compliant implementation must pass the the one-second statistics
through a 10-second delay line prior to updating any counters. That
can be done by performing the following steps at the end of each one
second interval.
i) Read near/far end CV counter and alarm status flags from the
hardware.
ii) Accumulate the CV counts for the preceding second and
compare them to the ES and SES threshold for the layer
in question. Update the signal state and shift the
one-second CV counts and ES/SES flags into the 10-element
Expires August 1996 [Page 69]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
delay line. Note that far-end one-second statistics are
to be flagged as "absent" during any second in which there
is an incoming defect at the layer in question or at any
lower layer.
iii) Update the current interval statistics using the signal
state from the _previous_ update cycle and the one-second
CV counts and ES/SES flags shifted out of the 10-element
delay line.
This procedure is illustrated below for a SONET interface. Similar
rules would apply for DS1 and DS3 interfaces. Note that the
procedure guarantees that the statistical counters will be correctly
updated at all times, although they will lag real time by 10 seconds.
Each 15 minutes one would transfer the current interval counts into
the previous interval counts and drop the oldest set of interval
counts off the cliff. Note that signal state calculations would
_not_ start afresh at each interval boundary; signal state
information _would_ be carried across interval boundaries. A scheme
similar to this one has been used at least one DS1 product I know of
-- the Tektronix/LP COM TC-2000 PCM test set. This product was first
put on the market in 1987 and featured G.821 performance statistics
collected in the manner shown below.
+--------------------------------------------------------------+
| READ COUNTERS & STATUS INFO FROM HARDWARE |
| |
|LOS OOF/ SECT LINE LINE LINE LINE PATH PATH PATH PATH PATH |
| LOF CV AIS CV RDI FEBE AIS LOP CV RDI CV |
+--------------------------------------------------------------+
| | | | | | | | | | | |
| | | | | | | | | | | |
V V V V V V V V V V V V
+--------------------------------------------------------------+
| ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE |
| |
| |
| NEAR END/FAR END NEAR END/FAR END |
|SECT SECT SECT LINE LINE LINE LINE PATH PATH PATH PATH |
|CV ES SES CV ES SES AVA/UNA CV ES SES AVA/UNA |
+--------------------------------------------------------------+
| | | | | | | | | | |
| | | | | | | | | | |
V V V V V V | V V V |
+-------------+ +-------------+ | +-------------+ |
|ONE-SEC DELAY| |ONE-SEC DELAY| | |ONE-SEC DELAY| |
Expires August 1996 [Page 70]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
| (1 OF 10) | | (1 OF 10) | | | (1 OF 10) | |
|CV ES SES| |CV ES SES| | |CV ES SES| |
+-------------+ +-------------+ | +-------------+ |
| | | | | | | | | | |
/ / / / / / / / / / /
/ / / / / / / / / / /
| | | | | | | | | | |
V V V V V V | V V V |
+-------------+ +-------------+ | +-------------+ |
|ONE-SEC DELAY| |ONE-SEC DELAY| | |ONE-SEC DELAY| |
| (10 OF 10) | | (10 OF 10) | | | (10 OF 10) | |
|CV ES SES| |CV ES SES| | |CV ES SES| |
+-------------+ +-------------+ | +-------------+ |
| | | | | | | | | | |
| | | | | | | | | | |
V V V V V V V V V V V
+--------------------------------------------------------------+
| UPDATE STATISTICS COUNTERS |
| |
| NEAR END/FAR END NEAR END/FAR END |
| SECTION LINE PATH |
| CV ES EFS SES CV ES EFS SES AS UAS CV ES EFS SES AS UAS |
+--------------------------------------------------------------+
Figure X. Accumulation of SONET/SDH performance statistics.
Adopting such a procedure would, however, raise another issue: for
the first ten seconds after a system comes up the interface is in an
unknown state. It would be necessary to allow for up to ten seconds
of dead time during the current interval. Hence the dsx1TimeElapsed,
dsx1FarEndTimeElapsed, dsx3TimeElapsed, dsx3FarEndTimeElapsed, and
sonetMediumTimeElapsed objects _would_ need to be replaced by objects
that allow for the possibility that _no_ valid data has yet been
collected for the current interval. Here are some possible
replacement objects:
dsx1NearEndElapsedTime OBJECT-TYPE
SYNTAX INTEGER (0..900)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds, including partial
seconds, that have elapsed since the beginning of
the current near-end error-measurement period."
::= { dsx1ConfigEntry xxx }
Expires August 1996 [Page 71]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
dsx1FarEndElapsedTime OBJECT-TYPE
SYNTAX INTEGER (0..900)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds, including partial
seconds, that have elapsed since the beginning of
the current far-end error-measurement period."
::= { dsx1FarEndCurrentEntry xxx }
dsx3NearEndElapsedTime OBJECT-TYPE
SYNTAX INTEGER (0..900)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds, including partial
seconds, that have elapsed since the beginning of
the current near-end error-measurement period."
::= { dsx3ConfigEntry xxx }
dsx3FarEndElapsedTime OBJECT-TYPE
SYNTAX INTEGER (0..900)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds, including partial
seconds, that have elapsed since the beginning of
the current far-end error-measurement period."
::= { dsx3FarEndCurrentEntry xxx }
sonetMediumElapsedTime OBJECT-TYPE
SYNTAX Integer32 (0..900)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of seconds, including partial
seconds, that have elapsed since the beginning of
the current error-measurement period."
::= { sonetMediumEntry xxx }
These objects should assume the value 0 whenever there are no current
interval statistics to report. That would happen if the interface
Expires August 1996 [Page 72]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
was off-line (e.g., in a disabled or testing state) and (in an
implementation which fully complies with ANSI T1.231 UAS definition)
during the initial 10-second period after the interface is brought
on-line.
7. Acknowledgments
This document was produced by the Trunk MIB Working Group:
Expires August 1996 [Page 73]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
8. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991.
[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple
Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP
Research, Performance Systems International, MIT Lab for
Computer Science, May 1990.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] McCloghrie, K. and F. Kastenholz, "Evolution of the
Interfaces Group of MIB-II", RFC 1573, Hughes LAN
Systems, FTP Software, January 1994.
[6] AT&T Information Systems, AT&T ESF DS1 Channel Service Unit
User's Manual, 999-100-305, February 1988.
[7] AT&T Technical Reference, Requirements for Interfacing Digital
Terminal Equipment to Services Employing the Extended Superframe
Format, Publication 54016, May 1988.
[8] American National Standard for Telecommunications -- Carrier-to-
Customer Installation - DS1 Metallic Interface, T1.403, February
1989.
[9] CCITT Specifications Volume III, Recommendation G.703,
Physical/Electrical Characteristics of Hierarchical Digital
Interfaces, July 1988.
[10] CCITT Specifications Volume III, Recommendation G.704,
Synchronous frame structures used at primary and secondary
hierarchical levels, July 1988.
[11] American National Standard for Telecommunications -- Digital
Expires August 1996 [Page 74]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Hierarchy -- Layer 1 In-Service Digital Transmission
Performace Monitoring, T1.231, Sept 1993.
[12] CCITT Specifications Volume IV, Recommendation O.162, Equipment
To Perform In Service Monitoring On 2048 kbit/s Signals, July
1988
[13] CCITT Specifications Volume III, Recommendation G.821, Error
Performance Of An International Digital Connection Forming Part
Of An Integrated Services Digital Network, July 1988.
[14] AT&T Technical Reference, Technical Reference 62411, ACCUNET T1.5
Service Description And Interface Specification, December 1990.
[15] CCITT Specifications Volume III, Recommendation G.706, Frame
Alignment and Cyclic Redundancy Check (CRC) Procedures Relating
to Basic Frame Structures Defined in Recommendation G.704, July
1988.
[16] CCITT Specifications Volume III, Recommendation G.732,
Characteristics Of Primary PCM Multiplex Equipment Operating at
2048 kbit/s, July 1988.
[17] Fowler, D., "Definitions of Managed Objects for the DS3/E3
Interface Types", RFCxxxx, Newbridge Networks, February 1996
[18] Brown, T., and Tesink, K., "Definitions of Managed Objects
for the SONET/SDH Interface Type", RFC1595, Bell Communications
Research, March 1994.
[19] Fowler, D., "Definitions of Managed Objects for the Ds0 and
DS0Bundle Interface Types", RFCxxxx, Newbridge Networks,
February 1996.
[20] ITU-T G.775: Loss of signal (LOS) and alarm indication
signal (AIS) defect detection and clearance criteria, May 1995.
Expires August 1996 [Page 75]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
9. Security Considerations
Security issues are not discussed in this memo.
10. Authors' Addresses
David Fowler
Newbridge Networks
600 March Road
Kanata, Ontario, Canada K2K 2E6
Phone: (613) 599-3600, ext 3538
EMail: davef@newbridge.com
Expires August 1996 [Page 76]
INTERNET-DRAFT DS1/E1/DS2/E2 MIB February 1996
Table of Contents
1 The SNMPv2 Network Management Framework ...................... 2
2 Object Definitions ........................................... 3
2.1 Changes from RFC1406 ....................................... 3
3 Overview ..................................................... 5
3.1 Use of ifTable for DS1 Layer ............................... 5
3.2 Using ifStackTable ......................................... 6
3.3 Objectives of this MIB Module .............................. 8
3.4 DS1 Terminology ............................................ 9
3.4.1 Error Events ............................................. 9
3.4.2 Performance Defects ...................................... 10
3.4.3 Performance Parameters ................................... 11
3.4.4 Failure States ........................................... 14
3.4.5 Other Terms .............................................. 18
4 Object Definitions ........................................... 19
5.1 The DS1 Near End Group ..................................... 20
5.1.1 The DS1 Configuration Table .............................. 20
5.1.2 The DS1 Current Table .................................... 31
5.1.3 The DS1 Interval Table ................................... 36
5.1.4 The DS1 Total Table ...................................... 41
5.2 The DS1 Far End Group ...................................... 45
5.2.1 The DS1 Far End Current Table ............................ 45
5.2.2 The DS1 Far End Interval Table ........................... 49
5.2.3 The DS1 Far End Total Table .............................. 54
5.3 The DS1 Fractional Group ................................... 59
5.4 Conformance Groups ......................................... 62
5.5 The DS1 Trap Group ......................................... 67
5 Appendix A - Use of dsx1IfIndex and dsx1LineIndex ............ 67
6 Appendix B - The delay approach to Unavialable Seconds. ..... 69
7 Acknowledgments .............................................. 73
8 References ................................................... 74
9 Security Considerations ...................................... 76
10 Authors' Addresses .......................................... 76
Expires August 1996 [Page 77]
