The is the MIB module that describes DS3 and E3 interfaces objects. Copyright (c) The Internet Society (2004). This version of this MIB module is part of RFC 3896 </rfcs/rfc3896.html>; 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 <mailto:atommib@research.telcordia.com> To Subscribe: atommib-request@research.telcordia.com <mailto:atommib-request@research.telcordia.com> Editor: Orly Nicklass Postal: RAD Data Communications, Ltd. Ziv Tower, 24 Roul Walenberg Tel Aviv, Israel, 69719 Tel: +9723 765 9969 E-mail: orly_n@rad.com <mailto:orly_n@rad.com>
Revisions
2004-09-08 00:00
The RFC 3896 version of this MIB module.
The key changes made to this MIB module
since its publication in RFC 2496 are as follows:
(1) The dsx3FracIfIndex SYNTAX matches the description range.
(2) Reference was added to Circuit Identifier object.
(3) Usage of ifStackTable section was updated.
(4) Align the DESCRIPTION clauses of few statistic objects with
thenear end definition, the far end definition and with
RFC 3593 .
(5) Add new value, dsx3M13, to dsx3LineType.
1998-08-01 21:30
The RFC 2496 version of this MIB module.
The key changes made to this MIB module
since its publication in RFC 1407 are as follows:
(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) dsx3IfIndex has been deprecated.
(6) 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.
(7) An inward loopback has been added.
(8) Additional lineStatus bits have been added for Near End
in Unavailable Signal State, Carrier Equipment Out of
Service.
(9) A read-write line Length object has been added.
(10) Added a lineStatus last change, trap and enabler.
(11) Textual Conventions for statistics objects have
been used.
(12) A new object, dsx3LoopbackStatus, has been introduced to
reflect the loopbacks established on a DS3/E3 interface
and the source to the requests. dsx3LoopbackConfig
continues to be the desired loopback state while
dsx3LoopbackStatus reflects the actual state.
(13) A dual loopback has been added to allow the setting of
an inward loopback and a line loopback at the same time.
(14) An object has been added to indicated whether or not
this is a channelized DS3/E3.
(15) A new object has been added to indicate which DS1 is to
set for remote loopback.