The MIB module to describe SONET/SDH interface objects. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3592; see the RFC itself for full legal notices.
WG charter: http://www.ietf.org/html.charters/atommib-charter.html Mailing Lists: General Discussion: atommib@research.telcordia.com To Subscribe: atommib-request@research.telcordia.com Kaj Tesink Telcordia Technologies Tel: (732) 758-5254 Fax: (732) 758-2269 E-mail: kaj@research.telcordia.com.
Revisions
2003-08-11 00:00
The key changes made to this MIB module
since its publication in RFC 2558
are as follows.
(1) Corrected typographical error
(bellcore1991(2) in sonetSESthresholdSet)
(2) Added support for sts192cSTM64(6) and
sts768cSTM256(7) in sonetPathCurrentWidth
(3) Corrected description of the applicability
of VTs for SDH for improved accuracy
(4) Added clarification in the SES description that
CV counts should be frozen during SESs
(5) Corrected typographical errors:
- Line Alarm Indication Signal description of the
Terminology section (20.5 --> 2.5 seconds)
- In the Terminology section
sonetSESThresholdSet --> sonetSESthresholdSet
1998-10-19 00:00
The RFC 2558 version of this MIB module.
The key changes made to this MIB module
since its initial publication in RFC 1595
are as follows.
(1) The MODULE-IDENTITY has been updated to reflect the
changes to the MIB.
(2) Where applicable, the textual conventions
PerfCurrentCount and PerfIntervalCount from
PerfHist-TC-MIB have been used in place of Gauge32.
(3) An agent now has the option to delay updates to
the various performance counts in lieu of performing
retroactive adjustments upon entering into or exiting
from unavailable time. This implementation option is
described in Appendix A of this memo.
(4) In order to make the SONET-MIB more useful for
circuit provisioning, the formerly read-only objects
sonetMediumType, sonetMediumLineCoding,
sonetMediumLineType, and sonetMediumCircuitIdentifier
have been given a MAX-ACCESS of read-write. The
MIN-ACCESS remains read-only.
(5) The DESCRIPTION clause for sonetMediumTimeElapsed has
been updated to describe its behaviour if the duration
of the current interval exceeds the maximum value.
(6) The DESCRIPTION clause for sonetMediumValidIntervals
has been updated to describe its behaviour when some
intervals may be unavailable, and the object
sonetMediumInvalidIntervals has been added to keep
count of the number of missing intervals (if any).
(7) The object sonetMediumLoopbackConfig has been added
to enable or disable loopback configurations.
(8) Because the error count thresholds for declaring
severely errored seconds that are specified in ANSI
T1.231-1993, ITU-T G.826-1995, and ANSI T1.231-1997
are all different from each other and from the thresholds
specified in RFC 1595, an enumerated INTEGER object
sonetSESthresholdSet has been added to allow an agent
to specify which threshold set is in use. Text has
been added to Section 3 stating that if this object is
not implemented the thresholds specified in RFC 1595
should be assumed, and the table containing those
thresholds has been moved to Appendix B of this memo.
(9) A column with SYNTAX TruthValue has been added to each
interval table. The purpose of the additional column
is to indicate, for each interval, whether the data
is valid in the sense intended by ANSI T1.231 clause
9.1.2.2 [T1.231a][T1.231b]. The objects in question are:
sonetSectionIntervalValidData
sonetLineIntervalValidData
sonetFarEndLineIntervalValidData
sonetPathIntervalValidData
sonetFarEndPathIntervalValidData
sonetVTIntervalValidData
sonetFarEndVTIntervalValidData
(10) The ranges for sonetPathCurrentStatus and
sonetVTCurrentStatus have been made consistent
with the DESCRIPTION clauses.
(11) The conformance information has been updated. Previous
conformance information from RFC 1595 has been
deprecated. Some typographical errors in the deprecated
section have been corrected in order to prevent
MIB compilation errors.