< draft-ietf-trunkmib-ds3-mib-07.txt		draft-ietf-trunkmib-ds3-mib-08.txt >
	INTERNET-DRAFT DS3/E3 MIB February 1998		INTERNET-DRAFT DS3/E3 MIB February 1998
	Definitions of Managed Objects		Definitions of Managed Objects
	for the DS3/E3 Interface Type		for the DS3/E3 Interface Type
	Wed Feb 11 19:26:27 EST 1998		Tue Feb 24 09:53:17 EST 1998
	draft-ietf-trunkmib-ds3-mib-07.txt		draft-ietf-trunkmib-ds3-mib-08.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 8, line 32 ¶		skipping to change at page 8, line 32 ¶
	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 Channelization for DS3, DS1, DS0		3.2.2. Usage of Channelization for DS3, DS1, DS0
	An example is given here to explain the channelization objects in the		An example is given here to explain the channelization objects in the
	DS3, DS1, and DS0 MIBs to help the implementor use the objects		DS3, DS1, and DS0 MIBs to help the implementor use the objects
	correctly.		correctly. Treatment of E3 and E1 would be similar, with the number of
			DS0s being different depending on the framing of the E1.
	Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (without		Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (without
	DS2s). The object dsx3Channelization is set to enabledDs1. There will		DS2s). The object dsx3Channelization is set to enabledDs1. When this
	be 28 DS1s in the ifTable. Assume the entries in the ifTable for the		object is set to enabledDS1, 28 ifEntries of type DS1 will be created by
	DS1s are created in channel order and the ifIndex values are 2 through		the agent. If dsx3Channelization is set to disabled, then the DS1s are
	29. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable		destroyed.
	for each ds1. The entries will be as follows:
			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		dsx1ChanMappingTable Entries
	ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex		ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex
	1 1 2		1 1 2
	1 2 3		1 2 3
	......		......
	1 28 29		1 28 29
	In addition, the DS1s are channelized into DS0s. The object		In addition, the DS1s are channelized into DS0s. The object
	skipping to change at page 27, line 43 ¶		skipping to change at page 27, line 43 ¶
	enabledDs1(2),		enabledDs1(2),
	enabledDs2(3)		enabledDs2(3)
	}		}
	MAX-ACCESS read-write		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 enabledDs1 indicates		unchannelized. The value of enabledDs1 indicates
	that this is a DS3 channelized into DS1s. The		that this is a DS3 channelized into DS1s. The
	value of enabledDs3 indicated that this is a DS3		value of enabledDs3 indicated that this is a DS3
	channelized into DS2s "		channelized into DS2s. Setting this object will
			cause the creation or deletion of DS2 or DS1
			entries in the ifTable. "
	::= { dsx3ConfigEntry 17 }		::= { 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
	skipping to change at page 55, line 15 ¶		skipping to change at page 55, line 15 ¶
	-- Ds3 TRAPS		-- Ds3 TRAPS
	ds3Traps OBJECT IDENTIFIER ::= { ds3 15 }		ds3Traps OBJECT IDENTIFIER ::= { ds3 15 }
	dsx3LineStatusChange NOTIFICATION-TYPE		dsx3LineStatusChange NOTIFICATION-TYPE
	OBJECTS { dsx3LineStatus,		OBJECTS { dsx3LineStatus,
	dsx3LineStatusLastChange }		dsx3LineStatusLastChange }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A dsx3LineStatusChange trap is sent when the		"A dsx3LineStatusChange trap is sent when the
	value of an instance dsx1LineStatus changes. It		value of an instance of dsx3LineStatus changes. It
	can be utilized by an NMS to trigger polls. When		can be utilized by an NMS to trigger polls. When
	the line status change results in a lower level		the line status change results in a lower level
	line status change (i.e. ds1), then no traps for		line status change (i.e. ds1), then no traps for
	the lower level are sent."		the lower level are sent."
	::= { ds3Traps 0 1 }		::= { ds3Traps 0 1 }
	-- conformance information		-- conformance information
	ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 }		ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 }
End of changes. 6 change blocks.
	10 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/