draft-ietf-trunkmib-ds3-mib-03.txt   draft-ietf-trunkmib-ds3-mib-04.txt 
David Fowler email: davef@newbridge.com
Newbridge Networks Corporation voice: (613) 599-3600 ext.6559
600 March Rd, Kanata, Ontario, Canada K2K 2E6 fax: (613) 599-3669
Definitions of Managed Objects Definitions of Managed Objects
for the DS3/E3 Interface Type for the DS3/E3 Interface Type
Thu Sep 26 13:55:25 EDT 1996 Sun Oct 27 12:43:43 EST 1996
draft-ietf-trunkmib-ds3-mib-03.txt draft-ietf-trunkmib-ds3-mib-04.txt
David Fowler (editor) David Fowler (editor)
Newbridge Networks Newbridge Networks
davef@newbridge.com davef@newbridge.com
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
skipping to change at page 5, line 5 skipping to change at page 4, line 14
(12) Textual Conventions for statistics objects have (12) Textual Conventions for statistics objects have
been used. been used.
(13) A new object, dsx3LoopbackStatus has been introduced (13) A new object, dsx3LoopbackStatus has been introduced
to reflect the loopbacks established on a DS3/E3 interface to reflect the loopbacks established on a DS3/E3 interface
and the source to the requests. dsx3LoopbackConfig and the source to the requests. dsx3LoopbackConfig
continues to be the desired loopback state while continues to be the desired loopback state while
dsx3LoopbackStatus reflects the actual state. dsx3LoopbackStatus reflects the actual state.
(14) A dual loopback has been added to allow the setting of
an inward loopback and a line loopback at the same time.
3. Overview 3. Overview
These objects are used when the particular media being used to These objects are used when the particular media being used to
realize an interface is a DS3/E3 interface. At present, this applies realize an interface is a DS3/E3 interface. At present, this applies
to these values of the ifType variable in the Internet-standard MIB: to these values of the ifType variable in the Internet-standard MIB:
ds3 (30) ds3 (30)
The DS3 definitions contained herein are based on the DS3 The DS3 definitions contained herein are based on the DS3
specifications in ANSI T1.102-1987, ANSI T1.107-1988, ANSI T1.107a- specifications in ANSI T1.102-1987, ANSI T1.107-1988, ANSI T1.107a-
skipping to change at page 8, line 35 skipping to change at page 8, line 35
4 8 4 8
3.2.2. Usage of Loopbacks This section discusses the behaviour of 3.2.2. Usage of Loopbacks This section discusses the behaviour of
objects related to loopbacks. objects related to loopbacks.
The object dsx3LoopbackConfig represents the desired state of loopbacks The object dsx3LoopbackConfig represents the desired state of loopbacks
on this interface. Using this object a Manager can request: on this interface. Using this object a Manager can request:
LineLoopback LineLoopback
PayloadLoopback (if ESF framing) PayloadLoopback (if ESF framing)
InwardLoopback InwardLoopback
DualLoopback (Line + Inward)
NoLoopback NoLoopback
The remote end can also request lookbacks either through the FDL channel The remote end can also request lookbacks either through the FDL channel
if ESF or inband if D4. The loopbacks that can be request this way are: if ESF or inband if D4. The loopbacks that can be request this way are:
LineLoopback LineLoopback
PayloadLoopback (if ESF framing) PayloadLoopback (if ESF framing)
NoLoopback NoLoopback
To model the current state of loopbacks on a DS3 interface, the object To model the current state of loopbacks on a DS3 interface, the object
dsx3LoopbackStatus defines which loopback is currently applies to an dsx3LoopbackStatus defines which loopback is currently applies to an
skipping to change at page 9, line 13 skipping to change at page 9, line 13
the source of those loopbacks. the source of those loopbacks.
The following restrictions/rules apply to loopbacks: The following restrictions/rules apply to loopbacks:
The far end cannot undo loopbacks set by a manager. The far end cannot undo loopbacks set by a manager.
A manager can undo loopbacks set by the far end. A manager can undo loopbacks set by the far end.
Both a line loopback and an inward loopback can be set at the same time. Both a line loopback and an inward loopback can be set at the same time.
Only these two loopbacks can co-exist and either one may be set by the Only these two loopbacks can co-exist and either one may be set by the
manager or the far end. manager or the far end. A LineLoopback request from the far end is
incremental to an existing Inward loopback established by a manager.
When a NoLoopback is received from the far end in this case, the
InwardLoopback remains in place.
3.3. Objectives of this MIB Module 3.3. Objectives of this MIB Module
There are numerous things that could be included in a MIB for DS3/E3 There are numerous things that could be included in a MIB for DS3/E3
signals: the management of multiplexors, CSUs, DSUs, and the like. signals: the management of multiplexors, CSUs, DSUs, and the like.
The intent of this document is to facilitate the common management of The intent of this document is to facilitate the common management of
all devices with DS3/E3 interfaces. As such, a design decision was all devices with DS3/E3 interfaces. As such, a design decision was
made up front to very closely align the MIB with the set of objects made up front to very closely align the MIB with the set of objects
that can generally be read from DS3/E3 devices that are currently that can generally be read from DS3/E3 devices that are currently
deployed. deployed.
skipping to change at page 21, line 38 skipping to change at page 21, line 38
circuit identifier, for the purpose of circuit identifier, for the purpose of
facilitating troubleshooting." facilitating troubleshooting."
::= { dsx3ConfigEntry 8 } ::= { dsx3ConfigEntry 8 }
dsx3LoopbackConfig OBJECT-TYPE dsx3LoopbackConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dsx3NoLoop(1), dsx3NoLoop(1),
dsx3PayloadLoop(2), dsx3PayloadLoop(2),
dsx3LineLoop(3), dsx3LineLoop(3),
dsx3OtherLoop(4), dsx3OtherLoop(4),
dsx3InwardLoop(5) dsx3InwardLoop(5),
dsx3DualLoop(6)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents the desired loopback "This variable represents the desired loopback
configuration of the DS3/E3 interface. configuration of the DS3/E3 interface.
The values mean: The values mean:
dsx3NoLoop dsx3NoLoop
Not in the loopback state. A device that is Not in the loopback state. A device that is
skipping to change at page 22, line 24 skipping to change at page 22, line 25
dsx3LineLoop dsx3LineLoop
The received signal at this interface does not The received signal at this interface does not
go through the device (minimum penetration) but go through the device (minimum penetration) but
is looped back out. is looped back out.
dsx3OtherLoop dsx3OtherLoop
Loopbacks that are not defined here. Loopbacks that are not defined here.
dsx3InwardLoop dsx3InwardLoop
The sent signal at this interface is looped back The sent signal at this interface is looped back
through the device." through the device.
dsx3DualLoop
Both dsx1LineLoop and dsx1InwardLoop will be
active simultaneously."
::= { dsx3ConfigEntry 9 } ::= { dsx3ConfigEntry 9 }
dsx3LineStatus OBJECT-TYPE dsx3LineStatus OBJECT-TYPE
SYNTAX INTEGER (1..4095) SYNTAX INTEGER (1..4095)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the Line Status of the "This variable indicates the Line Status of the
interface. It contains loopback state information interface. It contains loopback state information
and failure state information. The dsx3LineStatus and failure state information. The dsx3LineStatus
 End of changes. 8 change blocks. 
5 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/