draft-ietf-trunkmib-ds3-mib-06.txt   draft-ietf-trunkmib-ds3-mib-07.txt 
Definitions of Managed Objects Definitions of Managed Objects
for the DS3/E3 Interface Type for the DS3/E3 Interface Type
Sun Jan 25 16:39:58 EST 1998 Wed Feb 11 19:26:27 EST 1998
draft-ietf-trunkmib-ds3-mib-06.txt draft-ietf-trunkmib-ds3-mib-07.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 3, line 47 skipping to change at page 3, line 47
(7) An inward loopback has been added. (7) An inward loopback has been added.
(8) Additional lineStatus bits have been added for Near End (8) Additional lineStatus bits have been added for Near End
in Unavailable Signal State, Carrier Equipment Out of in Unavailable Signal State, Carrier Equipment Out of
Service, DS@ Payload AIS, and DS@ Performance Threshold Service, DS@ Payload AIS, and DS@ Performance Threshold
(9) A read-write line Length object has been added. (9) A read-write line Length object has been added.
(10) Added a lineStatus last change, trap and enabler. (10) Added a lineStatus last change, trap and enabler.
(11) dsx3CircuitIdentifier has been deprecated since the (11) Textual Conventions for statistics objects have
object ifPhysAddress is available for all levels
through interface stacking.
(12) Textual Conventions for statistics objects have
been used. been used.
(13) A new object, dsx3LoopbackStatus, has been introduced (12) 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 (13) A dual loopback has been added to allow the setting of
an inward loopback and a line loopback at the same time. an inward loopback and a line loopback at the same time.
(15) An object has been added to indicated whether or not this (14) An object has been added to indicated whether or not this
is a channelized DS3/E3. is a channelized DS3/E3.
(16) A new object has been added to indicate which DS1 is to (15) A new object has been added to indicate which DS1 is to
set for remote loopback. set for remote loopback.
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)
skipping to change at page 8, line 27 skipping to change at page 8, line 27
8 Line#D CSU Network 8 Line#D CSU Network
ifStackTable Entries ifStackTable Entries
HigherLayer LowerLayer HigherLayer LowerLayer
1 5 1 5
2 6 2 6
3 7 3 7
4 8 4 8
3.2.2. Usage of Loopbacks This section discusses the behaviour of 3.2.2. Usage of Channelization for DS3, DS1, DS0
objects related to loopbacks.
An example is given here to explain the channelization objects in the
DS3, DS1, and DS0 MIBs to help the implementor use the objects
correctly.
Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (without
DS2s). The object dsx3Channelization is set to enabledDs1. There will
be 28 DS1s in the ifTable. Assume the entries in the ifTable for the
DS1s are created in channel order and the ifIndex values are 2 through
29. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable
for each ds1. The entries will be as follows:
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
1 1 2
1 2 3
......
1 28 29
In addition, the DS1s are channelized into DS0s. The object
dsx1Channelization is set to enabledDS0 for each DS1. There will be 24
DS0s in the ifTable for each DS1. Assume the entries in the ifTable are
created in channel order and the ifIndex values for the DS0s in the
first DS1 are 30 through 53. In the DS0 MIB, there will be an entry in
the dsx0ChanMappingTable for each DS0. The entries will be as follows:
dsx0ChanMappingTable Entries
ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex
2 1 30
2 2 31
......
2 24 53
3.2.3. Usage of Channelization for DS3, DS2, DS1
An example is given here to explain the channelization objects in the
DS3 and DS1 MIBs to help the implementor use the objects correctly.
Assume that a DS3 (with ifIndex 1) is Channelized into DS2s. The object
dsx3Channelization is set to enabledDs2. There will be 7 DS2s (ifType
of DS1) in the ifTable. Assume the entries in the ifTable for the DS2s
are created in channel order and the ifIndex values are 2 through 8. In
the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each
DS2. The entries will be as follows:
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
1 1 2
1 2 3
......
1 7 8
In addition, the DS2s are channelized into DS1s. The object
dsx1Channelization is set to enabledDS1 for each DS2. There will be
4 DS1s in the ifTable for each DS2. Assume the entries in the ifTable
are created in channel order and the ifIndex values for the DS1s in
the first DS2 are 9 through 12, then 13 through 16 for the second DS2,
and so on. In the DS1 MIB, there will be an
entry in the dsx1ChanMappingTable for each DS1. The entries will
be as follows:
dsx1ChanMappingTable Entries
ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
2 1 9
2 2 10
2 3 11
2 4 12
3 1 13
3 2 14
...
8 4 36
3.2.4. Usage of Loopbacks
This section discusses the behaviour of 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) 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
skipping to change at page 16, line 20 skipping to change at page 18, line 20
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI
DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB
PerfCurrentCount, PerfIntervalCount, PerfCurrentCount, PerfIntervalCount,
PerfTotalCount FROM PerfHist-TC-MIB; PerfTotalCount FROM PerfHist-TC-MIB;
ds3 MODULE-IDENTITY ds3 MODULE-IDENTITY
LAST-UPDATED "9801252100Z" LAST-UPDATED "9802112330Z"
ORGANIZATION "IETF Trunk MIB Working Group" ORGANIZATION "IETF Trunk MIB Working Group"
CONTACT-INFO CONTACT-INFO
" David Fowler " David Fowler
Postal: Newbridge Networks Corporation Postal: Newbridge Networks Corporation
600 March Road 600 March Road
Kanata, Ontario, Canada K2K 2E6 Kanata, Ontario, Canada K2K 2E6
Tel: +1 613 591 3600 Tel: +1 613 591 3600
Fax: +1 613 599 3669 Fax: +1 613 599 3667
E-mail: davef@newbridge.com" E-mail: davef@newbridge.com"
DESCRIPTION DESCRIPTION
"The is the MIB module that describes "The is the MIB module that describes
DS3 and E3 interfaces objects." DS3 and E3 interfaces objects."
::= { transmission 30 } ::= { transmission 30 }
-- The DS3/E3 Near End Group -- The DS3/E3 Near End Group
-- The DS3/E3 Near End Group consists of four tables: -- The DS3/E3 Near End Group consists of four tables:
skipping to change at page 25, line 31 skipping to change at page 27, line 31
4 dsx3NearEndLineLoopback 4 dsx3NearEndLineLoopback
8 dsx3NearEndOtherLoopback 8 dsx3NearEndOtherLoopback
16 dsx3NearEndInwardLoopback 16 dsx3NearEndInwardLoopback
32 dsx3FarEndPayloadLoopback 32 dsx3FarEndPayloadLoopback
64 dsx3FarEndLineLoopback" 64 dsx3FarEndLineLoopback"
::= { dsx3ConfigEntry 16 } ::= { dsx3ConfigEntry 16 }
dsx3Channelization OBJECT-TYPE dsx3Channelization OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), disabled(1),
disabled(2) enabledDs1(2),
enabledDs2(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether this ds3/e3 is channelized or "Indicates whether this ds3/e3 is channelized or
unchannelized. The value of enabled indicates unchannelized. The value of enabledDs1 indicates
channelized. " that this is a DS3 channelized into DS1s. The
DEFVAL { enabled } ::= { dsx3ConfigEntry 17 } value of enabledDs3 indicated that this is a DS3
channelized into DS2s "
::= { dsx3ConfigEntry 17 }
dsx3Ds1ForRemoteLoop OBJECT-TYPE dsx3Ds1ForRemoteLoop OBJECT-TYPE
SYNTAX INTEGER (0..29) SYNTAX INTEGER (0..29)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates which ds1/e1 on this ds3/e3 will be "Indicates which ds1/e1 on this ds3/e3 will be
indicated in the remote ds1 loopback request. A indicated in the remote ds1 loopback request. A
value of 0 means no DS1 will be looped. A value value of 0 means no DS1 will be looped. A value
of 29 means all ds1s/e1s will be looped." of 29 means all ds1s/e1s will be looped."
skipping to change at page 54, line 11 skipping to change at page 56, line 11
DESCRIPTION DESCRIPTION
"Implementation of this group is optional for all "Implementation of this group is optional for all
systems that attach to a DS3 Interface. However, systems that attach to a DS3 Interface. However,
only C-bit Parity and SYNTRAN DS3 applications only C-bit Parity and SYNTRAN DS3 applications
have the capability (option) of providing this have the capability (option) of providing this
information." information."
GROUP ds3NearEndOptionalConfigGroup GROUP ds3NearEndOptionalConfigGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional for all "Implementation of this group is optional for all
systems that attach to a DS3 interface." systems that attach to a DS3 interface."
OBJECT dsx3LineType
MIN-ACCESS read-only
DESCRIPTION
"Write access for the line type is not required."
OBJECT dsx3LineCoding
MIN-ACCESS read-only
DESCRIPTION
"Write access for the line coding is not
required."
OBJECT dsx3SendCode
MIN-ACCESS read-only
DESCRIPTION
"Write access for the send code is not required."
OBJECT dsx3LoopbackConfig
MIN-ACCESS read-only
DESCRIPTION
"Write access for loopbacks is not required."
OBJECT dsx3TransmitClockSource
MIN-ACCESS read-only
DESCRIPTION
"Write access for the transmit clock source is not
required."
OBJECT dsx3LineLength
MIN-ACCESS read-only
DESCRIPTION
"Write access for the line length is not
required."
OBJECT dsx3Channelization
MIN-ACCESS read-only
DESCRIPTION
"Write access for the channelization is not
required."
::= { ds3Compliances 1 } ::= { ds3Compliances 1 }
-- units of conformance -- units of conformance
ds3NearEndConfigGroup OBJECT-GROUP ds3NearEndConfigGroup OBJECT-GROUP
OBJECTS { dsx3LineIndex, OBJECTS { dsx3LineIndex,
dsx3TimeElapsed, dsx3TimeElapsed,
dsx3ValidIntervals, dsx3ValidIntervals,
dsx3LineType, dsx3LineType,
dsx3LineCoding, dsx3LineCoding,
skipping to change at page 64, line 16 skipping to change at page 67, line 16
This MIB adds no security issues that are not raised by SNMP itself. This MIB adds no security issues that are not raised by SNMP itself.
As a Network Management Protocol, SNMP is capable of changing the As a Network Management Protocol, SNMP is capable of changing the
configuration of a system, of denial of service attacks through configuration of a system, of denial of service attacks through
requiring the agent to respond to its messages, and displaying values requiring the agent to respond to its messages, and displaying values
of system counters and configuration settings in the clear where an of system counters and configuration settings in the clear where an
adversary might read them. This, however, is not in itself a threat: adversary might read them. This, however, is not in itself a threat:
this is the function of the protocol, but could be misused. Such this is the function of the protocol, but could be misused. Such
misuse can be avoided or minimized through SNMP Security. misuse can be avoided or minimized through SNMP Security.
Setting any of the following objects to an inappropriate value can
cause loss of traffic. The definition of inappropriate varies for
each object. In the case of dsx3LineType, for example, both ends of
a ds3/e3 must have the same value in order for traffic to flow. In
the case of dsx3SendCode and dsx3LoopbackConfig, for another example,
traffic may stop transmitting when particular loopbacks are applied.
dsx3LineType
dsx3LineCoding
dsx3SendCode
dsx3LoopbackConfig
dsx3TransmitClockSource
dsx3LineLength
dsx3Channelization
Setting the following object is mischevious, but not harmful to
traffic
dsx3CircuitIdentifier
Setting the following object can cause an increase in the number of
traps received by the network management station.
dsx3LineStatusChangeTrabEnable
10. Author's Address 10. Author's Address
David Fowler David Fowler
Newbridge Networks Newbridge Networks
600 March Road 600 March Road
Kanata, Ontario, Canada K2K 2E6 Kanata, Ontario, Canada K2K 2E6
Phone: (613) 599-3600, ext 6559 Phone: (613) 599-3600, ext 6559
EMail: davef@newbridge.com EMail: davef@newbridge.com
Table of Contents Table of Contents
1 The SNMPv2 Network Management Framework ...................... 2 1 The SNMPv2 Network Management Framework ...................... 2
2 Object Definitions ........................................... 3 2 Object Definitions ........................................... 3
2.1 Changes from RFC1407 ....................................... 3 2.1 Changes from RFC1407 ....................................... 3
3 Overview ..................................................... 5 3 Overview ..................................................... 5
3.1 Use of ifTable for DS3 Layer ............................... 5 3.1 Use of ifTable for DS3 Layer ............................... 5
3.2 Usage Guidelines ........................................... 6 3.2 Usage Guidelines ........................................... 6
3.2.1 Usage of ifStackTable .................................... 6 3.2.1 Usage of ifStackTable .................................... 6
3.2.2 Usage of Loopbacks ....................................... 8 3.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 8
3.3 Objectives of this MIB Module .............................. 9 3.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 9
3.4 DS3/E3 Terminology ......................................... 9 3.2.4 Usage of Loopbacks ....................................... 10
3.4.1 Error Events ............................................. 9 3.3 Objectives of this MIB Module .............................. 11
3.4.2 Performance Parameters ................................... 10 3.4 DS3/E3 Terminology ......................................... 11
3.4.3 Performance Defects ...................................... 13 3.4.1 Error Events ............................................. 11
3.4.4 Other Terms .............................................. 15 3.4.2 Performance Parameters ................................... 12
4 Object Definitions ........................................... 16 3.4.3 Performance Defects ...................................... 15
4.1 The DS3/E3 Near End Group .................................. 17 3.4.4 Other Terms .............................................. 17
4.1.1 The DS3/E3 Configuration Table ........................... 17 4 Object Definitions ........................................... 18
4.1.2 The DS3/E3 Current Table ................................. 27 4.1 The DS3/E3 Near End Group .................................. 19
4.1.3 The DS3/E3 Interval Table ................................ 31 4.1.1 The DS3/E3 Configuration Table ........................... 19
4.1.4 The DS3/E3 Total ......................................... 36 4.1.2 The DS3/E3 Current Table ................................. 29
4.2 The DS3 Far End Group ...................................... 40 4.1.3 The DS3/E3 Interval Table ................................ 33
4.2.1 The DS3 Far End Configuration ............................ 40 4.1.4 The DS3/E3 Total ......................................... 38
4.2.2 The DS3 Far End Current .................................. 42 4.2 The DS3 Far End Group ...................................... 42
4.2.3 The DS3 Far End Interval Table ........................... 45 4.2.1 The DS3 Far End Configuration ............................ 42
4.2.4 The DS3 Far End Total .................................... 47 4.2.2 The DS3 Far End Current .................................. 44
4.3 The DS3/E3 Fractional Table ................................ 50 4.2.3 The DS3 Far End Interval Table ........................... 47
4.4 The DS3 Trap Group ......................................... 53 4.2.4 The DS3 Far End Total .................................... 49
4.5 Conformance Groups ......................................... 53 4.3 The DS3/E3 Fractional Table ................................ 52
5 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 57 4.4 The DS3 Trap Group ......................................... 55
6 Appendix B - The delay approach to Unavialable Seconds. ..... 59 4.5 Conformance Groups ......................................... 55
7 Acknowledgments .............................................. 61 5 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 60
8 References ................................................... 62 6 Appendix B - The delay approach to Unavialable Seconds. ..... 62
9 Security Considerations ...................................... 64 7 Acknowledgments .............................................. 64
10 Author's Address ............................................ 64 8 References ................................................... 65
9 Security Considerations ...................................... 67
10 Author's Address ............................................ 67
 End of changes. 16 change blocks. 
21 lines changed or deleted 160 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/