draft-ietf-ccamp-lmp-mib-09.txt   draft-ietf-ccamp-lmp-mib-10.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Internet Draft
Category: Standards Track Sudheer Dharanikota Category: Standards Track Sudheer Dharanikota
Expires: November 2004 Expires: March 2005
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
May 2004 September 2004
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-09.txt draft-ietf-ccamp-lmp-mib-10.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 5, line 25 skipping to change at page 5, line 25
6.2. lmpControlChannelTable 6.2. lmpControlChannelTable
The control channel table is used for enabling the LMP protocol on The control channel table is used for enabling the LMP protocol on
LMP-capable interfaces. A photonic switch, optical cross-connect or LMP-capable interfaces. A photonic switch, optical cross-connect or
router creates an entry in this table for every LMP capable interface router creates an entry in this table for every LMP capable interface
in that device. in that device.
6.3. lmpControlChannelPerfTable 6.3. lmpControlChannelPerfTable
The control channel performance table is used for collecting LMP The control channel performance table is used for collecting LMP
performance counts on a per-control channel basis. This table is an performance counts on a per-control channel basis. Each entry in the
AUGMENT to the lmpControlChannelTable. lmpControlChannelTable has a corresponding entry in the
lmpControlChannelPerfTable.
6.4. lmpTeLinkTable 6.4. lmpTeLinkTable
The TE link table is used for specifying LMP information associated The TE link table is used for specifying LMP information associated
with TE links. with TE links.
6.5. lmpLinkVerificationTable 6.5. lmpLinkVerificationTable
The link verification table is used for configuring the LMP link The link verification table is used for configuring the LMP link
verification parameters of TE links. This table is an AUGMENT to the verification parameters of TE links. For every TE link entry in the
lmpTeLinkTable. lmpTeLinkTable that supports the link verification procedure, there
is a corresponding entry in the lmpLinkVerificationTable.
6.6. lmpTeLinkPerfTable 6.6. lmpTeLinkPerfTable
The TE link performance table is used for collecting LMP performance The TE link performance table is used for collecting LMP performance
counts on a per-TE link basis. This table is an AUGMENT to the counts on a per-TE link basis. Each entry in the lmpTeLinkTable has a
lmpTeLinkTable. corresponding entry in the lmpTeLinkPerfTable.
6.7. lmpDataLinkTable 6.7. lmpDataLinkTable
The data-bearing link table is used to specify the data-bearing links The data-bearing link table is used to specify the data-bearing links
that are associated with TE links. that are associated with TE links.
6.8. lmpDataLinkPerfTable 6.8. lmpDataLinkPerfTable
The data-bearing link performance table is used for collecting LMP The data-bearing link performance table is used for collecting LMP
performance counts on data-bearing links. performance counts on data-bearing links.
skipping to change at page 6, line 31 skipping to change at page 6, line 31
three data-bearing links. We also assume that the data-bearing three data-bearing links. We also assume that the data-bearing
links are ports (lambdas). We also assume that the link links are ports (lambdas). We also assume that the link
verification procedure is not enabled. The following example verification procedure is not enabled. The following example
illustrates which rows and corresponding objects might be created illustrates which rows and corresponding objects might be created
to accomplish this. to accomplish this.
First, LMP must be enabled between the pair of nodes. First, LMP must be enabled between the pair of nodes.
In lmpNbrTable: In lmpNbrTable:
{ {
lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1
lmpNbrAdminStatus = up(1), lmpNbrAdminStatus = up(1),
lmpNbrRowStatus = createAndGo(4), lmpNbrRowStatus = createAndGo(4),
lmpNbrStorageType = nonVolatile(3) lmpNbrStorageType = nonVolatile(3)
} }
Then, the control channels must be set up. These are created in Then, the control channels must be set up. These are created in
the lmpControlChannelTable. the lmpControlChannelTable.
In lmpControlChannelTable: In lmpControlChannelTable:
{ {
lmpCcId = 1, lmpCcId = 1,
lmpCcUnderlyingIfIndex = 1, lmpCcUnderlyingIfIndex = 1,
lmCcIsIf = false(1), lmpCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4), lmpCcRowStatus = createAndGo(4),
lmpCcStorageType = nonVolatile(3) lmpCcStorageType = nonVolatile(3)
} }
{ {
lmpCcId = 2, lmpCcId = 2,
lmpCcUnderlyingIfIndex = 2, lmpCcUnderlyingIfIndex = 2,
lmCcIsIf = false(1), lmpCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4), lmpCcRowStatus = createAndGo(4),
lmpCcStorageType = nonVolatile(3) lmpCcStorageType = nonVolatile(3)
skipping to change at page 12, line 4 skipping to change at page 12, line 4
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; FROM TE-LINK-STD-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200405241200Z" -- 24 May 2004 12:00:00 EST LAST-UPDATED "200409081200Z" -- 8 September 2004 12:00:00 EST
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@sympatico.ca
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@ieee.org Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Email: jplang@ieee.org Email: jplang@ieee.org
skipping to change at page 12, line 34 skipping to change at page 12, line 34
"Copyright (C) 2004 The Internet Society. This version of "Copyright (C) 2004 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC XXXX; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200405241200Z" -- 24 May 2004 12:00:00 EST "200409081200Z" -- 8 September 2004 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC xxxx (to be assigned by RFC
Editor)" Editor)"
::= { transmission xxx } -- To be assigned by IANA. ::= { transmission xxx } -- To be assigned by IANA.
-- Request to assign same number as LMP -- Request to assign same number as LMP
-- ifType. -- ifType.
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
skipping to change at page 13, line 16 skipping to change at page 13, line 16
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The retransmission interval delay in milliseconds." "The retransmission interval delay in milliseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
LmpNodeId ::= TEXTUAL-CONVENTION LmpNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d" DISPLAY-HINT "1d.1d.1d.1d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Node ID in network byte order." "Represents a Node ID in network byte order. Node ID is an
address of type IPv4."
REFERENCE REFERENCE
"Section 1.1 of Link Management Protocol, RFC xxx" "Section 1.1 of Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
SYNTAX OCTET STRING(SIZE(4)) SYNTAX OCTET STRING(SIZE(4))
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications -- Notifications
lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 }
skipping to change at page 15, line 32 skipping to change at page 15, line 32
to indicate that a node should never stop retransmission. to indicate that a node should never stop retransmission.
This object along with lmpNbrRetransmitInterval is This object along with lmpNbrRetransmitInterval is
used to implement congestion handling mechanism as defined in used to implement congestion handling mechanism as defined in
Section 10 of the Link Management Protocol specification, Section 10 of the Link Management Protocol specification,
which is based on RFC 2914." which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 3 } DEFVAL { 3 }
::= { lmpNbrEntry 7 } ::= { lmpNbrEntry 3 }
lmpNbrRetransmitDelta OBJECT-TYPE lmpNbrRetransmitDelta OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object governs the speed with which the sender increases "This object governs the speed with which the sender increases
the retransmission interval as explained in section 10 of the the retransmission interval as explained in section 10 of the
Link Management Protocol specification, which is based on Link Management Protocol specification, which is based on
RFC 2914. This value is a power used to express the RFC 2914. This value is a power used to express the
exponential backoff. The ratio of two succesive retransmission exponential backoff. The ratio of two succesive retransmission
intervals is (1 + Delta)." intervals is (1 + Delta)."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 1 } DEFVAL { 1 }
::= { lmpNbrEntry 8 } ::= { lmpNbrEntry 4 }
lmpNbrAdminStatus OBJECT-TYPE lmpNbrAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP to this remote node." "The desired operational status of LMP to this remote node."
::= { lmpNbrEntry 3 } ::= { lmpNbrEntry 5 }
lmpNbrOperStatus OBJECT-TYPE lmpNbrOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of LMP to this remote node." "The actual operational status of LMP to this remote node."
::= { lmpNbrEntry 4 } ::= { lmpNbrEntry 6 }
lmpNbrRowStatus OBJECT-TYPE lmpNbrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1). in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent All read-create objects must have valid and consistent
values before the row can be activated." values before the row can be activated."
::= { lmpNbrEntry 5 } ::= { lmpNbrEntry 7 }
lmpNbrStorageType OBJECT-TYPE lmpNbrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpNbrTable. Conceptual rows having the value lmpNbrTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { lmpNbrEntry 6 } ::= { lmpNbrEntry 8 }
-- End of lmpNbrTable -- End of lmpNbrTable
lmpCcHelloIntervalDefault OBJECT-TYPE lmpCcHelloIntervalDefault OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default value for the HelloInterval "This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It parameter used in the Hello protocol keep-alive phase. It
skipping to change at page 25, line 25 skipping to change at page 25, line 25
lmpControlChannelPerfEntry OBJECT-TYPE lmpControlChannelPerfEntry OBJECT-TYPE
SYNTAX LmpControlChannelPerfEntry SYNTAX LmpControlChannelPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every control channel. lmpCcCounterDiscontinuityTime is used every control channel. lmpCcCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects to indicate potential discontinuity for all counter objects
in this table." in this table."
AUGMENTS { lmpControlChannelEntry } INDEX { lmpCcId }
::= { lmpControlChannelPerfTable 1 } ::= { lmpControlChannelPerfTable 1 }
LmpControlChannelPerfEntry ::= SEQUENCE { LmpControlChannelPerfEntry ::= SEQUENCE {
lmpCcInOctets Counter32, lmpCcInOctets Counter32,
lmpCcInDiscards Counter32, lmpCcInDiscards Counter32,
lmpCcInErrors Counter32, lmpCcInErrors Counter32,
lmpCcOutOctets Counter32, lmpCcOutOctets Counter32,
lmpCcOutDiscards Counter32, lmpCcOutDiscards Counter32,
lmpCcOutErrors Counter32, lmpCcOutErrors Counter32,
lmpCcConfigReceived Counter32, lmpCcConfigReceived Counter32,
skipping to change at page 26, line 30 skipping to change at page 26, line 30
lmpCcLinkSummaryNackReceived Counter32, lmpCcLinkSummaryNackReceived Counter32,
lmpCcLinkSummaryNackSent Counter32, lmpCcLinkSummaryNackSent Counter32,
lmpCcChannelStatusReceived Counter32, lmpCcChannelStatusReceived Counter32,
lmpCcChannelStatusSent Counter32, lmpCcChannelStatusSent Counter32,
lmpCcChannelStatusRetransmit Counter32, lmpCcChannelStatusRetransmit Counter32,
lmpCcChannelStatusAckReceived Counter32, lmpCcChannelStatusAckReceived Counter32,
lmpCcChannelStatusAckSent Counter32, lmpCcChannelStatusAckSent Counter32,
lmpCcChannelStatusReqReceived Counter32, lmpCcChannelStatusReqReceived Counter32,
lmpCcChannelStatusReqSent Counter32, lmpCcChannelStatusReqSent Counter32,
lmpCcChannelStatusReqRetransmit Counter32, lmpCcChannelStatusReqRetransmit Counter32,
lmpCcChannelStatusRspSent Counter32,
lmpCcChannelStatusRspReceived Counter32, lmpCcChannelStatusRspReceived Counter32,
lmpCcChannelStatusRspSent Counter32,
lmpCcCounterDiscontinuityTime TimeStamp lmpCcCounterDiscontinuityTime TimeStamp
} }
lmpCcInOctets OBJECT-TYPE lmpCcInOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of LMP message octets received on the "The total number of LMP message octets received on the
control channel." control channel."
skipping to change at page 37, line 48 skipping to change at page 37, line 48
lmpTeLinkStorageType StorageType lmpTeLinkStorageType StorageType
} }
lmpTeLinkNbrRemoteNodeId OBJECT-TYPE lmpTeLinkNbrRemoteNodeId OBJECT-TYPE
SYNTAX LmpNodeId SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the TE link remote node. This value "This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation may be learned during control channel parameter negotiation
phase (in the Config message). Node ID address type must phase (in the Config message). Node ID is an address which
be IPv4." type must be IPv4."
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
lmpTeLinkVerification OBJECT-TYPE lmpTeLinkVerification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the LMP link verification procedure "This object indicates if the LMP link verification procedure
is enabled for this TE link." is enabled for this TE link."
REFERENCE REFERENCE
skipping to change at page 39, line 39 skipping to change at page 39, line 39
lmpTeLinkTable. Conceptual rows having the value lmpTeLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { lmpTeLinkEntry 7 } ::= { lmpTeLinkEntry 7 }
-- End of lmpTeLinkTable -- End of lmpTeLinkTable
lmpGlobalLinkVerificationInterval OBJECT-TYPE lmpGlobalLinkVerificationInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "ms" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the link verification "This object indicates how often the link verification
procedure is executed. The interval is in milliseconds. procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link A value of 0 is used to indicate that the link
verification procedure should not be executed. The verification procedure should not be executed. The
interval specified in this object should be large enough interval specified in this object should be large enough
to allow the verification procedure to be completed to allow the verification procedure to be completed
before the start of the next interval. before the start of the next interval.
skipping to change at page 43, line 42 skipping to change at page 43, line 42
lmpTeLinkPerfEntry OBJECT-TYPE lmpTeLinkPerfEntry OBJECT-TYPE
SYNTAX LmpTeLinkPerfEntry SYNTAX LmpTeLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every TE link. lmpTeCounterDiscontinuityTime is used every TE link. lmpTeCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects to indicate potential discontinuity for all counter objects
in this table." in this table."
AUGMENTS { lmpTeLinkEntry } INDEX { ifIndex }
::= { lmpTeLinkPerfTable 1 } ::= { lmpTeLinkPerfTable 1 }
LmpTeLinkPerfEntry ::= SEQUENCE { LmpTeLinkPerfEntry ::= SEQUENCE {
lmpTeInOctets Counter32, lmpTeInOctets Counter32,
lmpTeOutOctets Counter32, lmpTeOutOctets Counter32,
lmpTeBeginVerifyReceived Counter32, lmpTeBeginVerifyReceived Counter32,
lmpTeBeginVerifySent Counter32, lmpTeBeginVerifySent Counter32,
lmpTeBeginVerifyRetransmit Counter32, lmpTeBeginVerifyRetransmit Counter32,
lmpTeBeginVerifyAckReceived Counter32, lmpTeBeginVerifyAckReceived Counter32,
lmpTeBeginVerifyAckSent Counter32, lmpTeBeginVerifyAckSent Counter32,
skipping to change at page 44, line 36 skipping to change at page 44, line 36
lmpTeLinkSummaryNackReceived Counter32, lmpTeLinkSummaryNackReceived Counter32,
lmpTeLinkSummaryNackSent Counter32, lmpTeLinkSummaryNackSent Counter32,
lmpTeChannelStatusReceived Counter32, lmpTeChannelStatusReceived Counter32,
lmpTeChannelStatusSent Counter32, lmpTeChannelStatusSent Counter32,
lmpTeChannelStatusRetransmit Counter32, lmpTeChannelStatusRetransmit Counter32,
lmpTeChannelStatusAckReceived Counter32, lmpTeChannelStatusAckReceived Counter32,
lmpTeChannelStatusAckSent Counter32, lmpTeChannelStatusAckSent Counter32,
lmpTeChannelStatusReqReceived Counter32, lmpTeChannelStatusReqReceived Counter32,
lmpTeChannelStatusReqSent Counter32, lmpTeChannelStatusReqSent Counter32,
lmpTeChannelStatusReqRetransmit Counter32, lmpTeChannelStatusReqRetransmit Counter32,
lmpTeChannelStatusRspSent Counter32,
lmpTeChannelStatusRspReceived Counter32, lmpTeChannelStatusRspReceived Counter32,
lmpTeChannelStatusRspSent Counter32,
lmpTeCounterDiscontinuityTime TimeStamp lmpTeCounterDiscontinuityTime TimeStamp
} }
lmpTeInOctets OBJECT-TYPE lmpTeInOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of LMP message octets received for "The total number of LMP message octets received for
this TE link." this TE link."
skipping to change at page 56, line 39 skipping to change at page 56, line 39
lmpDataLinkPerfEntry OBJECT-TYPE lmpDataLinkPerfEntry OBJECT-TYPE
SYNTAX LmpDataLinkPerfEntry SYNTAX LmpDataLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about "An entry in this table contains information about
the LMP performance counters for the data-bearing links. the LMP performance counters for the data-bearing links.
lmpDataLinkDiscontinuityTime is used to indicate potential lmpDataLinkDiscontinuityTime is used to indicate potential
discontinuity for all counter objects in this table." discontinuity for all counter objects in this table."
AUGMENTS { lmpDataLinkEntry } INDEX { ifIndex }
::= { lmpDataLinkPerfTable 1 } ::= { lmpDataLinkPerfTable 1 }
LmpDataLinkPerfEntry ::= SEQUENCE { LmpDataLinkPerfEntry ::= SEQUENCE {
lmpDataLinkTestReceived Counter32, lmpDataLinkTestReceived Counter32,
lmpDataLinkTestSent Counter32, lmpDataLinkTestSent Counter32,
lmpDataLinkActiveTestSuccess Counter32, lmpDataLinkActiveTestSuccess Counter32,
lmpDataLinkActiveTestFailure Counter32, lmpDataLinkActiveTestFailure Counter32,
lmpDataLinkPassiveTestSuccess Counter32, lmpDataLinkPassiveTestSuccess Counter32,
lmpDataLinkPassiveTestFailure Counter32, lmpDataLinkPassiveTestFailure Counter32,
lmpDataLinkDiscontinuityTime TimeStamp lmpDataLinkDiscontinuityTime TimeStamp
skipping to change at page 59, line 20 skipping to change at page 59, line 20
each node, or 100 notifications per second for the whole each node, or 100 notifications per second for the whole
network. The rest of the notifications are negligeable network. The rest of the notifications are negligeable
compared to this number. compared to this number.
To alleviate the congestion problem, the To alleviate the congestion problem, the
lmpNotificationMaxRate object can be used to implement a lmpNotificationMaxRate object can be used to implement a
throttling mechanism. It is also possible to enable/disable throttling mechanism. It is also possible to enable/disable
certain type of notifications. certain type of notifications.
This variable indicates the maximum number of This variable indicates the maximum number of
notifications issued per second. If events occur notifications issued per minute. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
emit these notifications during that period, or may emit these notifications during that period, or may
queue them until an appropriate time. A value of 0 queue them until an appropriate time. A value of 0
means no throttling is applied and events may be means no throttling is applied and events may be
notified at the rate at which they occur. notified at the rate at which they occur.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { 0 }
::= { lmpObjects 18 } ::= { lmpObjects 18 }
lmpLinkPropertyNotificationsEnabled OBJECT-TYPE lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of lmpTeLinkPropertyMismatch generation of lmpTeLinkPropertyMismatch
and lmpDataLinkPropertyMismatch notifications, and lmpDataLinkPropertyMismatch notifications,
skipping to change at page 82, line 15 skipping to change at page 82, line 15
December 2002. December 2002.
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering", "Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>, Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002. July 2002.
15. Authors' Addresses 15. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Email: mdubuc@ncf.ca Rincon Networks, Inc. Email: dubuc.consulting@sympatico.ca Rincon Networks, Inc.
110 El Paseo 110 El Paseo
Santa Barbara, CA 93101 Santa Barbara, CA 93101
Email: jplang@ieee.org Email: jplang@ieee.org
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Email: sudheer@ieee.org Calient Networks, Inc. Email: sudheer@ieee.org Calient Networks, Inc.
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Email: evan@calient.net Email: evan@calient.net
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/