draft-ietf-ccamp-lmp-mib-02.txt   draft-ietf-ccamp-lmp-mib-03.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Meriton Networks Internet Draft Meriton Networks
Expires: November 2002 Expires: December 2002
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
May 2002 June 2002
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-02.txt draft-ietf-ccamp-lmp-mib-03.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 2, line 15 skipping to change at page 2, line 15
5. Feature Checklist ............................................ 4 5. Feature Checklist ............................................ 4
6. Outline ...................................................... 5 6. Outline ...................................................... 5
6.1. Summary of LMP MIB ........................................... 5 6.1. Summary of LMP MIB ........................................... 5
7. Brief Description of MIB Objects ............................. 6 7. Brief Description of MIB Objects ............................. 6
7.1. lmpNbrTable .................................................. 6 7.1. lmpNbrTable .................................................. 6
7.2. lmpControlChannelTable ....................................... 6 7.2. lmpControlChannelTable ....................................... 6
7.3. lmpControlChannelPerfTable ................................... 6 7.3. lmpControlChannelPerfTable ................................... 6
7.4. lmpTeLinkTable ............................................... 7 7.4. lmpTeLinkTable ............................................... 7
7.5. lmpLinkVerificationTable ..................................... 7 7.5. lmpLinkVerificationTable ..................................... 7
7.6. lmpTeLinkPerfTable ........................................... 7 7.6. lmpTeLinkPerfTable ........................................... 7
7.7. lmpDataBearingLinkTable ...................................... 7 7.7. lmpDataLinkTable ............................................. 7
7.8. lmpDataBearingLinkPerfTable .................................. 7 7.8. lmpDataLinkPerfTable ......................................... 7
8. Example of LMP Control Channel Interface Setup ............... 7 8. Example of LMP Control Channel Interface Setup ............... 7
9. Application of the Interfaces Group to LMP ................... 10 9. Application of the Interfaces Group to LMP ................... 10
9.1. Support of the LMP Layer by ifTable .......................... 10 9.1. Support of the LMP Layer by ifTable .......................... 10
10. Link Management Protocol MIB Definitions ..................... 12 10. Link Management Protocol MIB Definitions ..................... 12
11. Security Considerations ...................................... 78 11. Security Considerations ...................................... 78
12. Acknowledgments .............................................. 79 12. Acknowledgments .............................................. 79
13. References ................................................... 79 13. References ................................................... 79
14. Authors' Addresses ........................................... 82 14. Authors' Addresses ........................................... 82
15. Full Copyright Statement ..................................... 82 15. Full Copyright Statement ..................................... 82
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Informa- This memo defines a portion of the Management Information Base (MIB)
tion Base (MIB) for use with network management protocols in the for use with network management protocols in the Internet community.
Internet community. In particular, it describes managed objects for In particular, it describes managed objects for modeling the Link
modeling the Link Management Protocol (LMP) [LMP]. Management Protocol (LMP).
2. Introduction 2. Introduction
Current work is underway in the IETF to specify a suite of protocols Current work is underway in the IETF to specify a suite of protocols
to be used as a common control plane and a separate common measure- to be used as a common control plane and a separate common measure-
ment plane. The Link Management Protocol, which primary purpose is to ment plane. Along with Generalized MPLS (GMPLS) [GMPLS], the Link
manage traffic engineering (TE) links, is one of the key components Management Protocol [LMP], which primary purpose is to manage traffic
of this standardization activity. Primary goals of LMP are the engineering (TE) links, is one of the key components of this stan-
maintenance of the control channel connectivity, correlation of link dardization activity. Primary goals of LMP are the maintenance of the
properties, verification of data-bearing links and detection and iso- control channel connectivity, correlation of link properties, verifi-
lation of link faults. cation of data-bearing links and detection and isolation of link
faults.
We describe in this document a MIB that can be used to manage LMP We describe in this document a MIB that can be used to manage LMP
implementations. This MIB covers both configuration and performance implementations. This MIB covers both configuration and performance
monitoring aspects of LMP. monitoring aspects of LMP.
Comments should be made directly to the ccamp mailing list at
ccamp@ops.ietf.org.
This memo does not, in its draft form, specify a standard for the
Internet community.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference document are to be interpreted as described in RFC 2119, reference
[BCP14]. [RFC2119].
3. Terminology 3. Terminology
This document uses terminology from the document describing the Link This document uses terminology from the document describing the Link
Management Protocol [LMP]. An "LMP adjacency" is formed between two Management Protocol [LMP]. An "LMP adjacency" is formed between two
nodes that support the same capabilities, and LMP messages are nodes that support the same capabilities, and LMP messages are
exchanged between the node pair over control channels that form this exchanged between the node pair over control channels that form this
adjacency. Several control channels can be active at the same time. adjacency. Several control channels can be active at the same time.
With the exception of messages related to control channel management, With the exception of messages related to control channel management,
any time a LMP message needs to be transferred to a neighbor node, it any time a LMP message needs to be transferred to a neighbor node, it
skipping to change at page 6, line 16 skipping to change at page 6, line 14
- The TE link table (lmpTeLinkTable) is used for - The TE link table (lmpTeLinkTable) is used for
specifying LMP information associated with TE links. specifying LMP information associated with TE links.
- The link verification table (lmpLinkVerificationTable) is used for - The link verification table (lmpLinkVerificationTable) is used for
configuring the LMP link verification parameters of TE links. configuring the LMP link verification parameters of TE links.
- The TE link performance table (lmpTeLinkPerfTable) is used for - The TE link performance table (lmpTeLinkPerfTable) is used for
collecting LMP performance counts on a per-TE link basis. collecting LMP performance counts on a per-TE link basis.
- The data-bearing link table (lmpDataBearingLinkTable) is used to - The data-bearing link table (lmpDataLinkTable) is used to
specify the data-bearing links that are associated with TE links. specify the data-bearing links that are associated with TE links.
- The data-bearing link performance table - The data-bearing link performance table
(lmpDataBearingLinkPerfTable) is used for collecting LMP (lmpDataLinkPerfTable) is used for collecting LMP
performance counts on data-bearing links. performance counts on data-bearing links.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
7. Brief Description of MIB Objects 7. Brief Description of MIB Objects
Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- Sections 7.1-7.3 describe objects pertaining to LMP-capable inter-
faces. Section 7.4 to 7.7 describes objects for specifying TE links faces. Section 7.4 to 7.7 describes objects for specifying TE links
and data-bearing links. The MIB objects were derived from the LMP and data-bearing links. The MIB objects were derived from the LMP
document [LMP]. document [LMP].
skipping to change at page 7, line 19 skipping to change at page 7, line 19
7.5. lmpLinkVerificationTable 7.5. lmpLinkVerificationTable
This table augments the lmpTeLinkTable and represents the link verif- This table augments the lmpTeLinkTable and represents the link verif-
ication parameters associated with the TE links. ication parameters associated with the TE links.
7.6. lmpTeLinkPerfTable 7.6. lmpTeLinkPerfTable
This table contains the objects to measure the LMP performance of LMP This table contains the objects to measure the LMP performance of LMP
capable interfaces and is an AUGMENT to the lmpTeLinkTable. capable interfaces and is an AUGMENT to the lmpTeLinkTable.
7.7. lmpDataBearingLinkTable 7.7. lmpDataLinkTable
The data-bearing link table enumerates the data-bearing links that The data-bearing link table enumerates the data-bearing links that
are associated with each TE link. are associated with each TE link.
7.8. lmpDataBearingLinkPerfTable 7.8. lmpDataLinkPerfTable
This table augments the lmpDataBearingLinkTable. It contains the This table augments the lmpDataLinkTable. It contains the objects to
objects to measure the LMP performance of data-bearing links. measure the LMP performance of data-bearing links.
8. Example of LMP Control Channel Setup 8. Example of LMP Control Channel Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in section 10 to set up an LMP control channel. objects described in section 10 to set up an LMP control channel.
While this example is not meant to illustrate every nuance of the While this example is not meant to illustrate every nuance of the
MIB, it is intended as an aid to understanding some of the key MIB, it is intended as an aid to understanding some of the key
concepts. It is meant to be read after going through the MIB itself. concepts. It is meant to be read after going through the MIB itself.
Suppose that one would like to form an LMP adjacency between two Suppose that one would like to form an LMP adjacency between two
skipping to change at page 9, line 5 skipping to change at page 9, line 5
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4)
} }
Next, the three data-bearing links are created. For each data- Next, the three data-bearing links are created. For each data-
bearing link, an ifEntry with the same ifIndex needs to be created bearing link, an ifEntry with the same ifIndex needs to be created
beforehand. beforehand.
In lmpDataBearingLinkTable: In lmpDataLinkTable:
{ {
ifIndex = 41, ifIndex = 41,
lmpDataBearingLinkNumberingType = unnumbered(1), lmpDataLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 47, lmpDataLinkRemoteIfId = 47,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4)
} }
{ {
ifIndex = 43, ifIndex = 43,
lmpDataBearingLinkNumberingType = unnumbered(1), lmpDataLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 42, lmpDataLinkRemoteIfId = 42,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4)
} }
{ {
ifIndex = 44, ifIndex = 44,
lmpDataBearingLinkNumberingType = unnumbered(1), lmpDataLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 48, lmpDataLinkRemoteIfId = 48,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4)
} }
Note that the data-bearing link type (lmpDataBearingLinkType) does Note that the data-bearing link type (lmpDataLinkType) does
not need to be provisioned as it is automatically populated by the not need to be provisioned as it is automatically populated by the
node. The definition of the protection role (primary or node. The definition of the protection role (primary or
secondary) for the data-bearing links is stored in the secondary) for the data-bearing links is stored in the
dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB]. componentLinkTable of the Link Bundling MIB [BUNDLE-MIB].
Then, a TE link is created as an ifEntry with ifType teLink in Then, a TE link is created as an ifEntry with ifType teLink in
the ifTable. the ifTable.
Once the TE link is created in the ifTable, a TE link entry Once the TE link is created in the ifTable, a TE link entry
is created in the LMP MIB to specify TE link information specific is created in the LMP MIB to specify TE link information specific
to LMP. to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
skipping to change at page 10, line 11 skipping to change at page 10, line 11
The association between the data-bearing links and the TE links is The association between the data-bearing links and the TE links is
stored in the ifStackTable [IF-MIB]. stored in the ifStackTable [IF-MIB].
In parallel with the entry created in the lmpTeLinkTable, an entry In parallel with the entry created in the lmpTeLinkTable, an entry
may be created in the teLinkTable of Link Bundling MIB may be created in the teLinkTable of Link Bundling MIB
[BUNDLE-MIB]. [BUNDLE-MIB].
9. Application of the Interfaces Group to LMP 9. Application of the Interfaces Group to LMP
The Interfaces Group [IFMIB] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing LMP control channels extensions to the Interfaces Group for managing LMP control channels
that are modeled as interfaces. If the control channel as defined in that are modeled as interfaces. If the control channel as defined in
the lmpControlChannelTable is modeled as an ifEntry, then the the lmpControlChannelTable is modeled as an ifEntry, then the
following definition applies. An lmpControlChannelTable entry is following definition applies. An lmpControlChannelTable entry is
designated as being represented as an Interfaces MIB ifEntry if the designated as being represented as an Interfaces MIB ifEntry if the
lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this
case, the control channel SHOULD be modeled as an ifEntry and case, the control channel SHOULD be modeled as an ifEntry and
provide appropriate interface stacking as defined below. provide appropriate interface stacking as defined below.
This memo assumes the interpretation of the Interfaces Group to be This memo assumes the interpretation of the Interfaces Group to be
in accordance with [IFMIB] which states that the interfaces table in accordance with [RFC2863] which states that the interfaces table
(ifTable) contains information on the managed resource's (ifTable) contains information on the managed resource's
interfaces and that each sub-layer below the internetwork layer of interfaces and that each sub-layer below the internetwork layer of
a network interface is considered an interface. Since the LMP a network interface is considered an interface. Since the LMP
interface only carries control traffic, it is considered to be below interface only carries control traffic, it is considered to be below
the internetwork layer. Thus, the LMP interface may be represented the internetwork layer. Thus, the LMP interface may be represented
as an entry in the ifTable. The inter-relation of entries in the as an entry in the ifTable. The inter-relation of entries in the
ifTable is defined by Interfaces Stack Group defined in [IFMIB]. ifTable is defined by Interfaces Stack Group defined in [RFC2863].
When LMP control channels are modeled as interfaces, the interface When LMP control channels are modeled as interfaces, the interface
stack table must appear as follows for the LMP control channel stack table must appear as follows for the LMP control channel
interfaces: interfaces:
+----------------------------------------+ +----------------------------------------+
| LMP-interface ifType = lmp(TBD) + | LMP-interface ifType = lmp(TBD) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
skipping to change at page 11, line 23 skipping to change at page 11, line 23
This number will be assigned by the IANA. This number will be assigned by the IANA.
ifSpeed The total bandwidth in bits per second for use by ifSpeed The total bandwidth in bits per second for use by
the LMP layer. the LMP layer.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus This variable indicates the administrator's intent ifAdminStatus This variable indicates the administrator's intent
as to whether LMP should be enabled, disabled, or as to whether LMP should be enabled, disabled, or
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. Also see [IFMIB]. interface. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational ifOperStatus This value reflects the actual or operational
status of LMP on this interface. status of LMP on this interface.
ifLastChange See [IFMIB]. ifLastChange See [RFC2863].
ifInOctets The number of received octets over the interface, ifInOctets The number of received octets over the interface,
i.e., the number of octets received as LMP i.e., the number of octets received as LMP
packets. packets.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the
interface, i.e., the number of octets transmitted interface, i.e., the number of octets transmitted
as LMP packets. as LMP packets.
ifInErrors The number of LMP packets dropped due to ifInErrors The number of LMP packets dropped due to
uncorrectable errors. uncorrectable errors.
ifInUnknownProtos ifInUnknownProtos
The number of received packets discarded during The number of received packets discarded during
packet header validation, including packets with packet header validation, including packets with
unrecognized label values. unrecognized label values.
ifOutErrors See [IFMIB]. ifOutErrors See [RFC2863].
ifName Textual name (unique on this system) of the ifName Textual name (unique on this system) of the
interface or an octet string of zero length. interface or an octet string of zero length.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Default is disabled (2). Default is disabled (2).
ifConnectorPresent ifConnectorPresent
Set to false (2). Set to false (2).
ifHighSpeed See [IFMIB]. ifHighSpeed See [RFC2863].
ifHCInOctets The 64-bit version of ifInOctets; supported if ifHCInOctets The 64-bit version of ifInOctets; supported if
required by the compliance statements in [IFMIB]. required by the compliance statements in [RFC2863].
ifHCOutOctets The 64-bit version of ifOutOctets; supported if ifHCOutOctets The 64-bit version of ifOutOctets; supported if
required by the compliance statements in [IFMIB]. required by the compliance statements in [RFC2863].
ifAlias The non-volatile 'alias' name for the interface as ifAlias The non-volatile 'alias' name for the interface as
specified by a network manager. specified by a network manager.
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [IFMIB]. See [RFC2863].
10. LMP MIB Definitions 10. LMP MIB Definitions
LMP-MIB DEFINITIONS ::= BEGIN LMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32, Counter32, TimeTicks experimental, Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 12, line 49 skipping to change at page 12, line 49
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId teLinkRemoteIpAddr, teLinkIncomingIfId
FROM LINK-BUNDLING-MIB; FROM LINK-BUNDLING-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200205291200Z" -- 29 May 2002 12:00:00 EST LAST-UPDATED "200206251200Z" -- 25 June 2002 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
Postal: Meriton Networks Postal: Meriton Networks
3026 Solandt Road 3026 Solandt Road
Kanata, ON, CANADA K2K 2A5 Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253 Tel: +1-613-270-9279 x253
Email: martin.dubuc@meriton.com Email: martin.dubuc@meriton.com
skipping to change at page 14, line 4 skipping to change at page 14, line 4
Link Management Protocol (LMP) as Link Management Protocol (LMP) as
defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., defined in: Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, D., Rekhter, Y., Berger, L., Saha, D.,
Basak, D., Sandick, H., Zinin, A., and Basak, D., Sandick, H., Zinin, A., and
Rajagopalan, B., Link Management Protocol, Rajagopalan, B., Link Management Protocol,
Internet Draft <draft-ietf-ccamp-lmp-03.txt>, Internet Draft <draft-ietf-ccamp-lmp-03.txt>,
March 2002." March 2002."
-- Revision history. -- Revision history.
REVISION REVISION
"200206251200Z" -- June 25 2002 12:00:00 EST
DESCRIPTION
"- Shorten long identifiers length."
REVISION
"200205291200Z" -- 29 May 2002 12:00:00 EST "200205291200Z" -- 29 May 2002 12:00:00 EST
DESCRIPTION DESCRIPTION
"Addresses Last Call comments. "Addresses Last Call comments.
- Fixed syntax problems reported by SMICng and smilint. - Fixed syntax problems reported by SMICng and smilint.
- Added lmpRemoteCcIpAddrType and lmpRemoteCcIpAddr. - Added lmpRemoteCcIpAddrType and lmpRemoteCcIpAddr.
- Added lmpTeLinkPerfTable. - Added lmpTeLinkPerfTable.
- Added lmpDataBearingLinkIpAddr. - Added lmpDataBearingLinkIpAddr.
- Added lmpTeLinkNotDegraded notification." - Added lmpTeLinkNotDegraded notification."
REVISION REVISION
"200202261200Z" -- 26 February 2002 12:00:00 EST "200202261200Z" -- 26 February 2002 12:00:00 EST
skipping to change at page 15, line 16 skipping to change at page 15, line 21
"Updates based on IETF-50 feedback. Aligned with "Updates based on IETF-50 feedback. Aligned with
upcoming version of LMP draft." upcoming version of LMP draft."
REVISION REVISION
"200102221200Z" -- 22 February 2001 12:00:00 EST "200102221200Z" -- 22 February 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Updates based on MPLS mailing list feedback." "Updates based on MPLS mailing list feedback."
REVISION REVISION
"200101261200Z" -- 26 January 2001 12:00:00 EST "200101261200Z" -- 26 January 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial draft version."
::= { experimental 113 } ::= { experimental 113 } -- See [Assigned]
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 28, line 22 skipping to change at page 28, line 24
lmpCcLinkSummaryRetransmit Counter32, lmpCcLinkSummaryRetransmit Counter32,
lmpCcLinkSummaryAckReceived Counter32, lmpCcLinkSummaryAckReceived Counter32,
lmpCcLinkSummaryAckSent Counter32, lmpCcLinkSummaryAckSent Counter32,
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,
lmpCcChannelStatusRequestReceived Counter32, lmpCcChannelStatusReqReceived Counter32,
lmpCcChannelStatusRequestSent Counter32, lmpCcChannelStatusReqSent Counter32,
lmpCcChannelStatusRequestRetransmit Counter32, lmpCcChannelStatusReqRetransmit Counter32,
lmpCcChannelStatusResponseSent Counter32, lmpCcChannelStatusRspSent Counter32,
lmpCcChannelStatusResponseReceived Counter32, lmpCcChannelStatusRspReceived 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 25 skipping to change at page 37, line 27
lmpCcChannelStatusAckSent OBJECT-TYPE lmpCcChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that have
been sent on this control channel." been sent on this control channel."
::= { lmpControlChannelPerfEntry 47 } ::= { lmpControlChannelPerfEntry 47 }
lmpCcChannelStatusRequestReceived OBJECT-TYPE lmpCcChannelStatusReqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 48 } ::= { lmpControlChannelPerfEntry 48 }
lmpCcChannelStatusRequestSent OBJECT-TYPE lmpCcChannelStatusReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 49 } ::= { lmpControlChannelPerfEntry 49 }
lmpCcChannelStatusRequestRetransmit OBJECT-TYPE lmpCcChannelStatusReqRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been retransmitted on this control channel." have been retransmitted on this control channel."
::= { lmpControlChannelPerfEntry 50 } ::= { lmpControlChannelPerfEntry 50 }
lmpCcChannelStatusResponseReceived OBJECT-TYPE lmpCcChannelStatusRspReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages that
have been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 51 } ::= { lmpControlChannelPerfEntry 51 }
lmpCcChannelStatusResponseSent OBJECT-TYPE lmpCcChannelStatusRspSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages that
have been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 52 } ::= { lmpControlChannelPerfEntry 52 }
lmpCcCounterDiscontinuityTime OBJECT-TYPE lmpCcCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
skipping to change at page 44, line 45 skipping to change at page 44, line 46
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." every TE link."
AUGMENTS { lmpTeLinkEntry } AUGMENTS { lmpTeLinkEntry }
::= { lmpTeLinkPerfTable 1 } ::= { lmpTeLinkPerfTable 1 }
LmpTeLinkPerfEntry ::= SEQUENCE { LmpTeLinkPerfEntry ::= SEQUENCE {
lmpTeLinkInOctets Counter32, lmpTeInOctets Counter32,
lmpTeLinkOutOctets Counter32, lmpTeOutOctets Counter32,
lmpTeLinkBeginVerifyReceived Counter32, lmpTeBeginVerifyReceived Counter32,
lmpTeLinkBeginVerifySent Counter32, lmpTeBeginVerifySent Counter32,
lmpTeLinkBeginVerifyRetransmit Counter32, lmpTeBeginVerifyRetransmit Counter32,
lmpTeLinkBeginVerifyAckReceived Counter32, lmpTeBeginVerifyAckReceived Counter32,
lmpTeLinkBeginVerifyAckSent Counter32, lmpTeBeginVerifyAckSent Counter32,
lmpTeLinkBeginVerifyNackReceived Counter32, lmpTeBeginVerifyNackReceived Counter32,
lmpTeLinkBeginVerifyNackSent Counter32, lmpTeBeginVerifyNackSent Counter32,
lmpTeLinkEndVerifyReceived Counter32, lmpTeEndVerifyReceived Counter32,
lmpTeLinkEndVerifySent Counter32, lmpTeEndVerifySent Counter32,
lmpTeLinkEndVerifyRetransmit Counter32, lmpTeEndVerifyRetransmit Counter32,
lmpTeLinkEndVerifyAckReceived Counter32, lmpTeEndVerifyAckReceived Counter32,
lmpTeLinkEndVerifyAckSent Counter32, lmpTeEndVerifyAckSent Counter32,
lmpTeLinkTestStatusSuccessReceived Counter32, lmpTeTestStatusSuccessReceived Counter32,
lmpTeLinkTestStatusSuccessSent Counter32, lmpTeTestStatusSuccessSent Counter32,
lmpTeLinkTestStatusSuccessRetransmit Counter32, lmpTeTestStatusSuccessRetransmit Counter32,
lmpTeLinkTestStatusFailureReceived Counter32, lmpTeTestStatusFailureReceived Counter32,
lmpTeLinkTestStatusFailureSent Counter32, lmpTeTestStatusFailureSent Counter32,
lmpTeLinkTestStatusFailureRetransmit Counter32, lmpTeTestStatusFailureRetransmit Counter32,
lmpTeLinkTestStatusAckReceived Counter32, lmpTeTestStatusAckReceived Counter32,
lmpTeLinkTestStatusAckSent Counter32, lmpTeTestStatusAckSent Counter32,
lmpTeLinkSummaryReceived Counter32, lmpTeLinkSummaryReceived Counter32,
lmpTeLinkSummarySent Counter32, lmpTeLinkSummarySent Counter32,
lmpTeLinkSummaryRetransmit Counter32, lmpTeLinkSummaryRetransmit Counter32,
lmpTeLinkSummaryAckReceived Counter32, lmpTeLinkSummaryAckReceived Counter32,
lmpTeLinkSummaryAckSent Counter32, lmpTeLinkSummaryAckSent Counter32,
lmpTeLinkSummaryNackReceived Counter32, lmpTeLinkSummaryNackReceived Counter32,
lmpTeLinkSummaryNackSent Counter32, lmpTeLinkSummaryNackSent Counter32,
lmpTeLinkChannelStatusReceived Counter32, lmpTeChannelStatusReceived Counter32,
lmpTeLinkChannelStatusSent Counter32, lmpTeChannelStatusSent Counter32,
lmpTeLinkChannelStatusRetransmit Counter32, lmpTeChannelStatusRetransmit Counter32,
lmpTeLinkChannelStatusAckReceived Counter32, lmpTeChannelStatusAckReceived Counter32,
lmpTeLinkChannelStatusAckSent Counter32, lmpTeChannelStatusAckSent Counter32,
lmpTeLinkChannelStatusRequestReceived Counter32, lmpTeChannelStatusReqReceived Counter32,
lmpTeLinkChannelStatusRequestSent Counter32, lmpTeChannelStatusReqSent Counter32,
lmpTeLinkChannelStatusRequestRetransmit Counter32, lmpTeChannelStatusReqRetransmit Counter32,
lmpTeLinkChannelStatusResponseSent Counter32, lmpTeChannelStatusRspSent Counter32,
lmpTeLinkChannelStatusResponseReceived Counter32, lmpTeChannelStatusRspReceived Counter32,
lmpTeLinkCounterDiscontinuityTime TimeStamp lmpTeCounterDiscontinuityTime TimeStamp
} }
lmpTeLinkInOctets 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."
::= { lmpTeLinkPerfEntry 1 } ::= { lmpTeLinkPerfEntry 1 }
lmpTeLinkOutOctets OBJECT-TYPE lmpTeOutOctets 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 transmitted out "The total number of LMP message octets transmitted out
for this TE link." for this TE link."
::= { lmpTeLinkPerfEntry 2 } ::= { lmpTeLinkPerfEntry 2 }
lmpTeLinkBeginVerifyReceived OBJECT-TYPE lmpTeBeginVerifyReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerify messages that have "This object counts the number of BeginVerify messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 3 } ::= { lmpTeLinkPerfEntry 3 }
lmpTeLinkBeginVerifySent OBJECT-TYPE lmpTeBeginVerifySent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerify messages that have "This object counts the number of BeginVerify messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 4 } ::= { lmpTeLinkPerfEntry 4 }
lmpTeLinkBeginVerifyRetransmit OBJECT-TYPE lmpTeBeginVerifyRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerify messages that "This object counts the number of BeginVerify messages that
have been retransmitted for this TE link." have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 5 } ::= { lmpTeLinkPerfEntry 5 }
lmpTeLinkBeginVerifyAckReceived OBJECT-TYPE lmpTeBeginVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 6 } ::= { lmpTeLinkPerfEntry 6 }
lmpTeLinkBeginVerifyAckSent OBJECT-TYPE lmpTeBeginVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 7 } ::= { lmpTeLinkPerfEntry 7 }
lmpTeLinkBeginVerifyNackReceived OBJECT-TYPE lmpTeBeginVerifyNackReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 8 } ::= { lmpTeLinkPerfEntry 8 }
lmpTeLinkBeginVerifyNackSent OBJECT-TYPE lmpTeBeginVerifyNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 9 } ::= { lmpTeLinkPerfEntry 9 }
lmpTeLinkEndVerifyReceived OBJECT-TYPE lmpTeEndVerifyReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that have "This object counts the number of EndVerify messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 10 } ::= { lmpTeLinkPerfEntry 10 }
lmpTeLinkEndVerifySent OBJECT-TYPE lmpTeEndVerifySent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that have "This object counts the number of EndVerify messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 11 } ::= { lmpTeLinkPerfEntry 11 }
lmpTeLinkEndVerifyRetransmit OBJECT-TYPE lmpTeEndVerifyRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that "This object counts the number of EndVerify messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpTeLinkPerfEntry 12 } ::= { lmpTeLinkPerfEntry 12 }
lmpTeLinkEndVerifyAckReceived OBJECT-TYPE lmpTeEndVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 13 } ::= { lmpTeLinkPerfEntry 13 }
lmpTeLinkEndVerifyAckSent OBJECT-TYPE lmpTeEndVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 14 } ::= { lmpTeLinkPerfEntry 14 }
lmpTeLinkTestStatusSuccessReceived OBJECT-TYPE lmpTeTestStatusSuccessReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 15 } ::= { lmpTeLinkPerfEntry 15 }
lmpTeLinkTestStatusSuccessSent OBJECT-TYPE lmpTeTestStatusSuccessSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 16 } ::= { lmpTeLinkPerfEntry 16 }
lmpTeLinkTestStatusSuccessRetransmit OBJECT-TYPE lmpTeTestStatusSuccessRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that "This object counts the number of TestStatusSuccess messages that
have been retransmitted for this TE link." have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 17 } ::= { lmpTeLinkPerfEntry 17 }
lmpTeLinkTestStatusFailureReceived OBJECT-TYPE lmpTeTestStatusFailureReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 18 } ::= { lmpTeLinkPerfEntry 18 }
lmpTeLinkTestStatusFailureSent OBJECT-TYPE lmpTeTestStatusFailureSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 19 } ::= { lmpTeLinkPerfEntry 19 }
lmpTeLinkTestStatusFailureRetransmit OBJECT-TYPE lmpTeTestStatusFailureRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that "This object counts the number of TestStatusFailure messages that
have been retransmitted on this TE link." have been retransmitted on this TE link."
::= { lmpTeLinkPerfEntry 20 } ::= { lmpTeLinkPerfEntry 20 }
lmpTeLinkTestStatusAckReceived OBJECT-TYPE lmpTeTestStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 21 } ::= { lmpTeLinkPerfEntry 21 }
lmpTeLinkTestStatusAckSent OBJECT-TYPE lmpTeTestStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 22 } ::= { lmpTeLinkPerfEntry 22 }
lmpTeLinkSummaryReceived OBJECT-TYPE lmpTeLinkSummaryReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 51, line 12 skipping to change at page 51, line 14
lmpTeLinkSummaryNackSent OBJECT-TYPE lmpTeLinkSummaryNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have "This object counts the number of LinkSummaryNack messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 29 } ::= { lmpTeLinkPerfEntry 29 }
lmpTeLinkChannelStatusReceived OBJECT-TYPE lmpTeChannelStatusReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 30 } ::= { lmpTeLinkPerfEntry 30 }
lmpTeLinkChannelStatusSent OBJECT-TYPE lmpTeChannelStatusSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 31 } ::= { lmpTeLinkPerfEntry 31 }
lmpTeLinkChannelStatusRetransmit OBJECT-TYPE lmpTeChannelStatusRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that have
been retransmitted for this TE link." been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 32 } ::= { lmpTeLinkPerfEntry 32 }
lmpTeLinkChannelStatusAckReceived OBJECT-TYPE lmpTeChannelStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusAck messages that have "This object counts the number of ChannelStatusAck messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 33 } ::= { lmpTeLinkPerfEntry 33 }
lmpTeLinkChannelStatusAckSent OBJECT-TYPE lmpTeChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that have
been sent for this TE link." been sent for this TE link."
::= { lmpTeLinkPerfEntry 34 } ::= { lmpTeLinkPerfEntry 34 }
lmpTeLinkChannelStatusRequestReceived OBJECT-TYPE lmpTeChannelStatusReqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 35 } ::= { lmpTeLinkPerfEntry 35 }
lmpTeLinkChannelStatusRequestSent OBJECT-TYPE lmpTeChannelStatusReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 36 } ::= { lmpTeLinkPerfEntry 36 }
lmpTeLinkChannelStatusRequestRetransmit OBJECT-TYPE lmpTeChannelStatusReqRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages that
have been retransmitted for this TE link." have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 37 } ::= { lmpTeLinkPerfEntry 37 }
lmpTeLinkChannelStatusResponseReceived OBJECT-TYPE lmpTeChannelStatusRspReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages that
have been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 38 } ::= { lmpTeLinkPerfEntry 38 }
lmpTeLinkChannelStatusResponseSent OBJECT-TYPE lmpTeChannelStatusRspSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages that
have been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 39 } ::= { lmpTeLinkPerfEntry 39 }
lmpTeLinkCounterDiscontinuityTime OBJECT-TYPE lmpTeCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this TE link's counters suffered a any one or more of this TE link's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this TE link of any Counter32 instances associated with this TE link of any Counter32
object contained in the lmpTeLinkPerfTable. If object contained in the lmpTeLinkPerfTable. If
no such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpTeLinkPerfEntry 40 } ::= { lmpTeLinkPerfEntry 40 }
-- End of lmpTeLinkPerfTable -- End of lmpTeLinkPerfTable
-- LMP Data Link Table
lmpDataBearingLinkTable OBJECT-TYPE lmpDataLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataBearingLinkEntry SYNTAX SEQUENCE OF LmpDataLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the data-bearing links managed by the "This table specifies the data-bearing links managed by the
LMP." LMP."
::= { lmpObjects 16 } ::= { lmpObjects 16 }
lmpDataBearingLinkEntry OBJECT-TYPE lmpDataLinkEntry OBJECT-TYPE
SYNTAX LmpDataBearingLinkEntry SYNTAX LmpDataLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a data-bearing link. An ifEntry with an ifIndex must exist a data-bearing link. An ifEntry with an ifIndex must exist
before the corresponding lmpDataBearingLinkEntry is created. before the corresponding lmpDataLinkEntry is created.
If an entry representing the data-bearing link is destroyed in If an entry representing the data-bearing link is destroyed in
the ifTable, then so is the corresponding entry in the the ifTable, then so is the corresponding entry in the
lmpDataBearingLinkTable. The administrative status value is lmpDataLinkTable. The administrative status value is
controlled from the ifEntry. The index to this table also controlled from the ifEntry. The index to this table also
used to get information in the dataBearingChannelTable used to get information in the componentLinkTable
[BUNDLE-MIB]." [BUNDLE-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataBearingLinkTable 1 } ::= { lmpDataLinkTable 1 }
LmpDataBearingLinkEntry ::= SEQUENCE { LmpDataLinkEntry ::= SEQUENCE {
lmpDataBearingLinkType INTEGER, lmpDataLinkType INTEGER,
lmpDataBearingLinkIpAddrType InetAddressType, lmpDataLinkIpAddrType InetAddressType,
lmpDataBearingLinkIpAddr InetAddress, lmpDataLinkIpAddr InetAddress,
lmpDataBearingLinkRemoteIpAddress InetAddress, lmpDataLinkRemoteIpAddress InetAddress,
lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataBearingLinkEncodingType INTEGER, lmpDataLinkEncodingType INTEGER,
lmpDataBearingLinkActiveOperStatus INTEGER, lmpDataLinkActiveOperStatus INTEGER,
lmpDataBearingLinkPassiveOperStatus INTEGER, lmpDataLinkPassiveOperStatus INTEGER,
lmpDataBearingLinkRowStatus RowStatus, lmpDataLinkRowStatus RowStatus,
lmpDataBearingLinkStorageType StorageType lmpDataLinkStorageType StorageType
} }
lmpDataBearingLinkType OBJECT-TYPE lmpDataLinkType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
port(1), port(1),
componentLink(2) componentLink(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this data-bearing link is "This attribute specifies whether this data-bearing link is
a port or a component link. Component link are multiplex a port or a component link. Component link are multiplex
capable whereas, ports are not multiplex capable." capable whereas, ports are not multiplex capable."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002." B. Rajagopalan, March 2002."
::= { lmpDataBearingLinkEntry 1 } ::= { lmpDataLinkEntry 1 }
lmpDataBearingLinkIpAddrType OBJECT-TYPE lmpDataLinkIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the data-bearing link IP address "This attribute specifies the data-bearing link IP address
type. If the data-bearing link is unnumbered, the address type. If the data-bearing link is unnumbered, the address
type must be set to unknown(0)." type must be set to unknown(0)."
::= { lmpDataBearingLinkEntry 2 } ::= { lmpDataLinkEntry 2 }
lmpDataBearingLinkIpAddr OBJECT-TYPE lmpDataLinkIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP address of the data-bearing link. This "IP address of the data-bearing link. This
If the data-bearing link is unnumbered, then the If the data-bearing link is unnumbered, then the
IP address must be null." IP address must be null."
::= { lmpDataBearingLinkEntry 3 } ::= { lmpDataLinkEntry 3 }
lmpDataBearingLinkRemoteIpAddress OBJECT-TYPE lmpDataLinkRemoteIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP address of the remote end point. This "IP address of the remote end point. This
information is either configured manually or is information is either configured manually or is
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure. If the data-bearing link is unnumbered, then the procedure. If the data-bearing link is unnumbered, then the
remote IP address must be null." remote IP address must be null."
::= { lmpDataBearingLinkEntry 4 } ::= { lmpDataLinkEntry 4 }
lmpDataBearingLinkRemoteIfId OBJECT-TYPE lmpDataLinkRemoteIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Interface identifier of the remote end point. This "Interface identifier of the remote end point. This
information is either configured manually or is information is either configured manually or is
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure." procedure."
::= { lmpDataBearingLinkEntry 5 } ::= { lmpDataLinkEntry 5 }
lmpDataBearingLinkEncodingType OBJECT-TYPE lmpDataLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packet(1), packet(1),
ethernet(2), ethernet(2),
ansiEtsiPdh(3), ansiEtsiPdh(3),
sdhItuSonetAnsi(5), sdhItuSonetAnsi(5),
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The encoding type of the data-bearing link." "The encoding type of the data-bearing link."
REFERENCE REFERENCE
"draft-ietf-mpls-generalized-signaling-08.txt - Generalized "draft-ietf-mpls-generalized-signaling-08.txt - Generalized
MPLS Signaling Functional Description, P. Ashwood-Smith, MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, April 2002." V. Sharma, G. Swallow, Z. Tang, April 2002."
::= { lmpDataBearingLinkEntry 6 } ::= { lmpDataLinkEntry 6 }
lmpDataBearingLinkActiveOperStatus OBJECT-TYPE lmpDataLinkActiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
testing(4) } testing(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(active FSM)." (active FSM)."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002." B. Rajagopalan, March 2002."
::= { lmpDataBearingLinkEntry 7 } ::= { lmpDataLinkEntry 7 }
lmpDataBearingLinkPassiveOperStatus OBJECT-TYPE lmpDataLinkPassiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
psvTst(4) } psvTst(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(passive FSM)." (passive FSM)."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002." B. Rajagopalan, March 2002."
::= { lmpDataBearingLinkEntry 8 } ::= { lmpDataLinkEntry 8 }
lmpDataBearingLinkRowStatus OBJECT-TYPE lmpDataLinkRowStatus 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. All read-create objects delete a row in this table. All read-create objects
can only be changed when lmpDataBearingLinkRowStatus is active." can only be changed when lmpDataLinkRowStatus is active."
::= { lmpDataBearingLinkEntry 9 } ::= { lmpDataLinkEntry 9 }
lmpDataBearingLinkStorageType OBJECT-TYPE lmpDataLinkStorageType 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
lmpDataBearingLinkTable. Conceptual rows having the value lmpDataLinkTable. 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."
::= { lmpDataBearingLinkEntry 10 } ::= { lmpDataLinkEntry 10 }
-- End of lmpDataLinkTable
-- LMP Data Link Performance Table
lmpDataBearingLinkPerfTable OBJECT-TYPE lmpDataLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry SYNTAX SEQUENCE OF LmpDataLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the data-bearing links LMP performance "This table specifies the data-bearing links LMP performance
counters." counters."
::= { lmpObjects 17 } ::= { lmpObjects 17 }
lmpDataBearingLinkPerfEntry OBJECT-TYPE lmpDataLinkPerfEntry OBJECT-TYPE
SYNTAX LmpDataBearingLinkPerfEntry 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."
AUGMENTS { lmpDataBearingLinkEntry } AUGMENTS { lmpDataLinkEntry }
::= { lmpDataBearingLinkPerfTable 1 } ::= { lmpDataLinkPerfTable 1 }
LmpDataBearingLinkPerfEntry ::= SEQUENCE { LmpDataLinkPerfEntry ::= SEQUENCE {
lmpDataBearingLinkTestReceived Counter32, lmpDataLinkTestReceived Counter32,
lmpDataBearingLinkTestSent Counter32, lmpDataLinkTestSent Counter32,
lmpDataBearingLinkActiveTestSuccess Counter32, lmpDataLinkActiveTestSuccess Counter32,
lmpDataBearingLinkActiveTestFailure Counter32, lmpDataLinkActiveTestFailure Counter32,
lmpDataBearingLinkPassiveTestSuccess Counter32, lmpDataLinkPassiveTestSuccess Counter32,
lmpDataBearingLinkPassiveTestFailure Counter32, lmpDataLinkPassiveTestFailure Counter32,
lmpDataBearingLinkCounterDiscontinuityTime TimeStamp lmpDataLinkDiscontinuityTime TimeStamp
} }
lmpDataBearingLinkTestReceived OBJECT-TYPE lmpDataLinkTestReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Test messages that have "This object counts the number of Test messages that have
been received on this data-bearing link." been received on this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 1 } ::= { lmpDataLinkPerfEntry 1 }
lmpDataBearingLinkTestSent OBJECT-TYPE lmpDataLinkTestSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Test messages that have "This object counts the number of Test messages that have
been sent on this data-bearing link." been sent on this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 2 } ::= { lmpDataLinkPerfEntry 2 }
lmpDataBearingLinkActiveTestSuccess OBJECT-TYPE lmpDataLinkActiveTestSuccess OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of data-bearing link test "This object counts the number of data-bearing link test
that were successful on the active side of this data- that were successful on the active side of this data-
bearing link." bearing link."
::= { lmpDataBearingLinkPerfEntry 3 } ::= { lmpDataLinkPerfEntry 3 }
lmpDataBearingLinkActiveTestFailure OBJECT-TYPE lmpDataLinkActiveTestFailure OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of data-bearing link test "This object counts the number of data-bearing link test
that failed on the active side of this data-bearing link." that failed on the active side of this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 4 } ::= { lmpDataLinkPerfEntry 4 }
lmpDataBearingLinkPassiveTestSuccess OBJECT-TYPE lmpDataLinkPassiveTestSuccess OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of data-bearing link test "This object counts the number of data-bearing link test
that were successful on the passive side of this data- that were successful on the passive side of this data-
bearing link." bearing link."
::= { lmpDataBearingLinkPerfEntry 5 } ::= { lmpDataLinkPerfEntry 5 }
lmpDataBearingLinkPassiveTestFailure OBJECT-TYPE lmpDataLinkPassiveTestFailure OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of data-bearing link test "This object counts the number of data-bearing link test
that failed on the passive side of this data-bearing link." that failed on the passive side of this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 6 } ::= { lmpDataLinkPerfEntry 6 }
lmpDataBearingLinkCounterDiscontinuityTime OBJECT-TYPE lmpDataLinkDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this data-bearing link's counters suffered a any one or more of this data-bearing link's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this data-bearing link of any Counter32 instances associated with this data-bearing link of any Counter32
object contained in the lmpDataBearingLinkPerfTable. If object contained in the lmpDataLinkPerfTable. If
no such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpDataBearingLinkPerfEntry 7 } ::= { lmpDataLinkPerfEntry 7 }
-- End of lmpDataLinkPerfTable
-- Notification Configuration -- Notification Configuration
lmpLinkPropertyMismatchNotifEnable OBJECT-TYPE lmpLinkPropertyNotifEnable 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 lmpDataBearingLinkPropertyMismatch notifications, and lmpDataLinkPropertyMismatch notifications,
otherwise these notifications are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 18 } ::= { lmpObjects 18 }
lmpUnprotectedNotifEnable OBJECT-TYPE lmpUnprotectedNotifEnable 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
skipping to change at page 60, line 24 skipping to change at page 60, line 24
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 lmpTeLinkDegraded and lmpTeLinkNotDegraded generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
notifications, otherwise these notifications are not emitted." notifications, otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 21 } ::= { lmpObjects 21 }
lmpDataBearingLinkNotifEnable OBJECT-TYPE lmpDataLinkNotifEnable 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 lmpDataBearingLinkVerificationFailure generation of lmpDataLinkVerificationFailure
notification, otherwise these notifications are not emitted." notification, otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 22 } ::= { lmpObjects 22 }
-- Notifications -- Notifications
-- Link Property Mismatch Notifications -- Link Property Mismatch Notifications
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { teLinkRemoteIpAddr, OBJECTS { teLinkRemoteIpAddr,
teLinkIncomingIfId } teLinkIncomingIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a TE link property "This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link mismatch is detected on the node. The received remote TE link
id of the misconfigured TE link is represented by either id of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
the TE link is numbered or unnumbered. This notification should the TE link is numbered or unnumbered. This notification should
not be sent unless lmpLinkPropertyMismatchNotifEnable is not be sent unless lmpLinkPropertyNotifEnable is true."
true."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { ifIndex,
lmpDataBearingLinkRemoteIfId } lmpDataLinkRemoteIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing link "This notification is generated when a data-bearing link
property mismatch is detected on the node. ifIndex property mismatch is detected on the node. ifIndex
is the interface index of the TE link. The remote entity is the interface index of the TE link. The remote entity
interface id is the remote entity interface id received in the interface id is the remote entity interface id received in the
LinkSummary message. This notification should LinkSummary message. This notification should
not be sent unless lmpLinkPropertyMismatchNotifEnable is not be sent unless lmpLinkPropertyNotifEnable is true."
true."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification -- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpCcNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when there are more than one "This notification is generated when there are more than one
control channels between LMP neighbors and the last redundant control channels between LMP neighbors and the last redundant
skipping to change at page 62, line 33 skipping to change at page 62, line 30
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a lmpTeLinkOperStatus "This notification is generated when a lmpTeLinkOperStatus
object for a TE link leaves the degraded state. This object for a TE link leaves the degraded state. This
notification should not be sent unless lmpTeLinkNotifEnable notification should not be sent unless lmpTeLinkNotifEnable
is true." is true."
::= { lmpNotifications 7 } ::= { lmpNotifications 7 }
-- Data-bearing Link Notification -- Data-bearing Link Notification
lmpDataBearingLinkVerificationFailure NOTIFICATION-TYPE lmpDataLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { ifIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing "This notification is generated when a data-bearing
link verification fails. This notification should not be sent link verification fails. This notification should not be sent
unless lmpDataBearingLinkNotifEnable is true." unless lmpDataLinkNotifEnable is true."
::= { lmpNotifications 8 } ::= { lmpNotifications 8 }
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
lmpGroups lmpGroups
OBJECT IDENTIFIER ::= { lmpConformance 1 } OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpCompliances lmpCompliances
skipping to change at page 63, line 22 skipping to change at page 63, line 19
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all LMP-enabled devices. However, they may all be supported -- by all LMP-enabled devices. However, they may all be supported
-- as read-only objects in the case where manual -- as read-only objects in the case where manual
-- configuration is unsupported. -- configuration is unsupported.
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataBearingLinkGroup } lmpDataLinkGroup }
GROUP lmpControlChannelIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
control channels that are not interfaces, in addition to control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply: lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)." lmpCcIsIf must at least be read-only returning false(1)."
GROUP lmpControlChannelIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
control channels that are interfaces, in addition to control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply: lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)." lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup GROUP lmpLinkVerificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
the link verification procedure." the link verification procedure."
skipping to change at page 64, line 17 skipping to change at page 64, line 15
OBJECT lmpNbrStorageType OBJECT lmpNbrStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpRemoteCcIpAddrType OBJECT lmpRemoteCcIpAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) adress type needs not be supported. For "The dns(16) adress type needs not be supported. For
point-to-point configuration, this object MIN-ACCESS point-to-point configuration, this object MIN-ACCESS
is read-create." is read-create."
OBJECT lmpRemoteCcIpAddr OBJECT lmpRemoteCcIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 65, line 4 skipping to change at page 64, line 49
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION DESCRIPTION
"A value of active(3), configuring(4), goingDown(5) "A value of active(3), configuring(4), goingDown(5)
need not be supported." need not be supported."
OBJECT lmpCcStorageType OBJECT lmpCcStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- lmpTeLinkTable
-- lmpTeLinkTable
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"The testing(3) state need not be supported." "The testing(3) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpTeLinkStorageType OBJECT lmpTeLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- lmpDataBearingLinkTable -- lmpDataLinkTable
OBJECT lmpDataBearingLinkActiveOperStatus OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpDataBearingLinkStorageType OBJECT lmpDataLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
::= { lmpCompliances 1 } ::= { lmpCompliances 1 }
lmpMonitoringModuleCompliance MODULE-COMPLIANCE lmpMonitoringModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 66, line 22 skipping to change at page 66, line 20
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all LMP-enabled devices. However, they may all be supported -- by all LMP-enabled devices. However, they may all be supported
-- as read-only objects in the case where manual -- as read-only objects in the case where manual
-- configuration is unsupported. -- configuration is unsupported.
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataBearingLinkGroup } lmpDataLinkGroup }
GROUP lmpControlChannelIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
control channels that are not interfaces, in addition to control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply: lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)." lmpCcIsIf must at least be read-only returning false(1)."
GROUP lmpControlChannelIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
control channels that are interfaces, in addition to control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply: lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)." lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup GROUP lmpLinkVerificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
the link verification procedure." the link verification procedure."
skipping to change at page 68, line 35 skipping to change at page 68, line 35
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcNbrNodeId OBJECT lmpCcNbrNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpRemoteCcIpAddrType OBJECT lmpRemoteCcIpAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) adress type needs not be supported." "The dns(16) adress type needs not be supported."
OBJECT lmpRemoteCcIpAddr OBJECT lmpRemoteCcIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
skipping to change at page 71, line 34 skipping to change at page 71, line 34
OBJECT lmpTeLinkBitRate OBJECT lmpTeLinkBitRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkWavelength OBJECT lmpTeLinkWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpDataBearingLinkTable -- lmpDataLinkTable
OBJECT lmpDataBearingLinkIpAddrType OBJECT lmpDataLinkIpAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) address type need not be supported. "The dns(16) address type need not be supported.
The ipv4(1) and ipv6(2) address types need not be The ipv4(1) and ipv6(2) address types need not be
supported if numbered links are not supported. The supported if numbered links are not supported. The
unknown(0) address type needs not be supported if unknown(0) address type needs not be supported if
unnumbered links are not supported." unnumbered links are not supported."
OBJECT lmpDataBearingLinkIpAddr OBJECT lmpDataLinkIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Size of data-bearing link IP address depends on type "Size of data-bearing link IP address depends on type
of data-bearing link. Data-bearing link IP address size of data-bearing link. Data-bearing link IP address size
is zero if link is unnumbered, four if link IP address is is zero if link is unnumbered, four if link IP address is
IPv4 and sixteen if link IP address is IPv6." IPv4 and sixteen if link IP address is IPv6."
OBJECT lmpDataBearingLinkRemoteIpAddress OBJECT lmpDataLinkRemoteIpAddress
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
procedure is enabled." procedure is enabled."
OBJECT lmpDataBearingLinkRemoteIfId OBJECT lmpDataLinkRemoteIfId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
procedure is enabled." procedure is enabled."
OBJECT lmpDataBearingLinkEncodingType OBJECT lmpDataLinkEncodingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpDataBearingLinkActiveOperStatus OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of psvTst(3) need not be supported." "A value of psvTst(3) need not be supported."
OBJECT lmpDataBearingLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpDataBearingLinkStorageType OBJECT lmpDataLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
::= { lmpCompliances 2 } ::= { lmpCompliances 2 }
-- Units of conformance -- Units of conformance
lmpNodeGroup OBJECT-GROUP lmpNodeGroup OBJECT-GROUP
skipping to change at page 74, line 13 skipping to change at page 74, line 13
lmpCcRowStatus, lmpCcRowStatus,
lmpCcStorageType, lmpCcStorageType,
lmpCcUpDownNotifEnable lmpCcUpDownNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP interface "Collection of objects needed for LMP interface
configuration." configuration."
::= { lmpGroups 2 } ::= { lmpGroups 2 }
lmpControlChannelIsInterfaceGroup OBJECT-GROUP lmpCcIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf } OBJECTS { lmpCcIsIf }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are "Objects needed to implement control channels that are
interfaces." interfaces."
::= { lmpGroups 3 } ::= { lmpGroups 3 }
lmpControlChannelIsNotInterfaceGroup OBJECT-GROUP lmpCcIsNotInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lmpCcUnderlyingIfIndex, lmpCcUnderlyingIfIndex,
lmpCcIsIf, lmpCcIsIf,
lmpCcLastChange, lmpCcLastChange,
lmpCcAdminStatus lmpCcAdminStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are not "Objects needed to implement control channels that are not
interfaces." interfaces."
::= { lmpGroups 4 } ::= { lmpGroups 4 }
lmpLinkPropertyCorrelationGroup OBJECT-GROUP lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyMismatchNotifEnable } OBJECTS { lmpLinkPropertyNotifEnable }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects needed to implement the link
property correlation procedure." property correlation procedure."
::= { lmpGroups 5 } ::= { lmpGroups 5 }
lmpLinkVerificationGroup OBJECT-GROUP lmpLinkVerificationGroup OBJECT-GROUP
OBJECTS { lmpLinkVerificationInterval, OBJECTS { lmpLinkVerificationInterval,
lmpVerifyInterval, lmpVerifyInterval,
lmpVerifyDeadInterval, lmpVerifyDeadInterval,
lmpVerifyTransportMechanism, lmpVerifyTransportMechanism,
lmpVerifyAllLinks, lmpVerifyAllLinks,
lmpTeLinkBitRate, lmpTeLinkBitRate,
lmpTeLinkWavelength, lmpTeLinkWavelength,
lmpDataBearingLinkNotifEnable lmpDataLinkNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects needed to implement the link
verification procedure." verification procedure."
::= { lmpGroups 6 } ::= { lmpGroups 6 }
lmpPerfGroup OBJECT-GROUP lmpPerfGroup OBJECT-GROUP
OBJECTS { lmpCcInOctets, OBJECTS { lmpCcInOctets,
lmpCcInDiscards, lmpCcInDiscards,
skipping to change at page 76, line 10 skipping to change at page 76, line 10
lmpCcLinkSummaryRetransmit, lmpCcLinkSummaryRetransmit,
lmpCcLinkSummaryAckReceived, lmpCcLinkSummaryAckReceived,
lmpCcLinkSummaryAckSent, lmpCcLinkSummaryAckSent,
lmpCcLinkSummaryNackReceived, lmpCcLinkSummaryNackReceived,
lmpCcLinkSummaryNackSent, lmpCcLinkSummaryNackSent,
lmpCcChannelStatusReceived, lmpCcChannelStatusReceived,
lmpCcChannelStatusSent, lmpCcChannelStatusSent,
lmpCcChannelStatusRetransmit, lmpCcChannelStatusRetransmit,
lmpCcChannelStatusAckReceived, lmpCcChannelStatusAckReceived,
lmpCcChannelStatusAckSent, lmpCcChannelStatusAckSent,
lmpCcChannelStatusRequestReceived, lmpCcChannelStatusReqReceived,
lmpCcChannelStatusRequestSent, lmpCcChannelStatusReqSent,
lmpCcChannelStatusRequestRetransmit, lmpCcChannelStatusReqRetransmit,
lmpCcChannelStatusResponseReceived, lmpCcChannelStatusRspReceived,
lmpCcChannelStatusResponseSent, lmpCcChannelStatusRspSent,
lmpCcCounterDiscontinuityTime, lmpCcCounterDiscontinuityTime,
lmpTeLinkInOctets, lmpTeInOctets,
lmpTeLinkOutOctets, lmpTeOutOctets,
lmpTeLinkBeginVerifyReceived, lmpTeBeginVerifyReceived,
lmpTeLinkBeginVerifySent, lmpTeBeginVerifySent,
lmpTeLinkBeginVerifyRetransmit, lmpTeBeginVerifyRetransmit,
lmpTeLinkBeginVerifyAckReceived, lmpTeBeginVerifyAckReceived,
lmpTeLinkBeginVerifyAckSent, lmpTeBeginVerifyAckSent,
lmpTeLinkBeginVerifyNackReceived, lmpTeBeginVerifyNackReceived,
lmpTeLinkBeginVerifyNackSent, lmpTeBeginVerifyNackSent,
lmpTeLinkEndVerifyReceived, lmpTeEndVerifyReceived,
lmpTeLinkEndVerifySent, lmpTeEndVerifySent,
lmpTeLinkEndVerifyRetransmit, lmpTeEndVerifyRetransmit,
lmpTeLinkEndVerifyAckReceived, lmpTeEndVerifyAckReceived,
lmpTeLinkEndVerifyAckSent, lmpTeEndVerifyAckSent,
lmpTeLinkTestStatusSuccessReceived, lmpTeTestStatusSuccessReceived,
lmpTeLinkTestStatusSuccessSent, lmpTeTestStatusSuccessSent,
lmpTeLinkTestStatusSuccessRetransmit, lmpTeTestStatusSuccessRetransmit,
lmpTeLinkTestStatusFailureReceived, lmpTeTestStatusFailureReceived,
lmpTeLinkTestStatusFailureSent, lmpTeTestStatusFailureSent,
lmpTeLinkTestStatusFailureRetransmit, lmpTeTestStatusFailureRetransmit,
lmpTeLinkTestStatusAckReceived, lmpTeTestStatusAckReceived,
lmpTeLinkTestStatusAckSent, lmpTeTestStatusAckSent,
lmpTeLinkSummaryReceived, lmpTeLinkSummaryReceived,
lmpTeLinkSummarySent, lmpTeLinkSummarySent,
lmpTeLinkSummaryRetransmit, lmpTeLinkSummaryRetransmit,
lmpTeLinkSummaryAckReceived, lmpTeLinkSummaryAckReceived,
lmpTeLinkSummaryAckSent, lmpTeLinkSummaryAckSent,
lmpTeLinkSummaryNackReceived, lmpTeLinkSummaryNackReceived,
lmpTeLinkSummaryNackSent, lmpTeLinkSummaryNackSent,
lmpTeLinkChannelStatusReceived, lmpTeChannelStatusReceived,
lmpTeLinkChannelStatusSent, lmpTeChannelStatusSent,
lmpTeLinkChannelStatusRetransmit, lmpTeChannelStatusRetransmit,
lmpTeLinkChannelStatusAckReceived, lmpTeChannelStatusAckReceived,
lmpTeLinkChannelStatusAckSent, lmpTeChannelStatusAckSent,
lmpTeLinkChannelStatusRequestReceived, lmpTeChannelStatusReqReceived,
lmpTeLinkChannelStatusRequestSent, lmpTeChannelStatusReqSent,
lmpTeLinkChannelStatusRequestRetransmit, lmpTeChannelStatusReqRetransmit,
lmpTeLinkChannelStatusResponseSent, lmpTeChannelStatusRspSent,
lmpTeLinkChannelStatusResponseReceived, lmpTeChannelStatusRspReceived,
lmpTeLinkCounterDiscontinuityTime, lmpTeCounterDiscontinuityTime,
lmpDataBearingLinkTestReceived, lmpDataLinkTestReceived,
lmpDataBearingLinkTestSent, lmpDataLinkTestSent,
lmpDataBearingLinkActiveTestSuccess, lmpDataLinkActiveTestSuccess,
lmpDataBearingLinkActiveTestFailure, lmpDataLinkActiveTestFailure,
lmpDataBearingLinkPassiveTestSuccess, lmpDataLinkPassiveTestSuccess,
lmpDataBearingLinkPassiveTestFailure, lmpDataLinkPassiveTestFailure,
lmpDataBearingLinkCounterDiscontinuityTime lmpDataLinkDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for providing performance "Collection of objects needed for providing performance
information about LMP interfaces and data-bearing links." information about LMP interfaces and data-bearing links."
::= { lmpGroups 7 } ::= { lmpGroups 7 }
lmpTeLinkGroup OBJECT-GROUP lmpTeLinkGroup OBJECT-GROUP
OBJECTS { lmpTeLinkNbrNodeId, OBJECTS { lmpTeLinkNbrNodeId,
lmpTeLinkVerification, lmpTeLinkVerification,
skipping to change at page 77, line 37 skipping to change at page 77, line 37
lmpTeLinkOperStatus, lmpTeLinkOperStatus,
lmpTeLinkRowStatus, lmpTeLinkRowStatus,
lmpTeLinkStorageType, lmpTeLinkStorageType,
lmpTeLinkNotifEnable lmpTeLinkNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for TE link configuration." "Collection of objects needed for TE link configuration."
::= { lmpGroups 8 } ::= { lmpGroups 8 }
lmpDataBearingLinkGroup OBJECT-GROUP lmpDataLinkGroup OBJECT-GROUP
OBJECTS { lmpDataBearingLinkType, OBJECTS { lmpDataLinkType,
lmpDataBearingLinkIpAddrType, lmpDataLinkIpAddrType,
lmpDataBearingLinkIpAddr, lmpDataLinkIpAddr,
lmpDataBearingLinkRemoteIpAddress, lmpDataLinkRemoteIpAddress,
lmpDataBearingLinkRemoteIfId, lmpDataLinkRemoteIfId,
lmpDataBearingLinkEncodingType, lmpDataLinkEncodingType,
lmpDataBearingLinkActiveOperStatus, lmpDataLinkActiveOperStatus,
lmpDataBearingLinkPassiveOperStatus, lmpDataLinkPassiveOperStatus,
lmpDataBearingLinkRowStatus, lmpDataLinkRowStatus,
lmpDataBearingLinkStorageType lmpDataLinkStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for data-bearing link "Collection of objects needed for data-bearing link
configuration." configuration."
::= { lmpGroups 9 } ::= { lmpGroups 9 }
lmpNotificationGroup NOTIFICATION-GROUP lmpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { lmpTeLinkPropertyMismatch, NOTIFICATIONS { lmpTeLinkPropertyMismatch,
lmpDataBearingLinkPropertyMismatch, lmpDataLinkPropertyMismatch,
lmpUnprotected, lmpUnprotected,
lmpControlChannelUp, lmpControlChannelUp,
lmpControlChannelDown, lmpControlChannelDown,
lmpTeLinkDegraded, lmpTeLinkDegraded,
lmpTeLinkNotDegraded, lmpTeLinkNotDegraded,
lmpDataBearingLinkVerificationFailure } lmpDataLinkVerificationFailure }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { lmpGroups 10 } ::= { lmpGroups 10 }
-- End of LMP-MIB -- End of LMP-MIB
END END
11. Security Considerations 11. Security Considerations
skipping to change at page 78, line 47 skipping to change at page 78, line 47
There are a number of management objects defined in this MIB which There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ- environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network ment without proper protection can have a negative effect on network
operations. The use of SNMP Version 3 is recommended over prior ver- operations. The use of SNMP Version 3 is recommended over prior ver-
sions, for configuration control, as its security model is improved. sions, for configuration control, as its security model is improved.
SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if
the network itself is secure (for example by using IPSec [IPSEC]), the network itself is secure (for example by using IPSec [RFC2401]),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB. It is recommended that the implementers consider the security MIB. It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [RFC2574] and the View-based Access of the User-based Security Model [RFC2574] and the View-based Access
Control [RFC2575] is recommended. It is then a customer/user respon- Control [RFC2575] is recommended. It is then a customer/user respon-
sibility to ensure that the SNMP entity giving access to an instance sibility to ensure that the SNMP entity giving access to an instance
of this MIB is properly configured to give access to the objects only of this MIB is properly configured to give access to the objects only
to those principals (users) that have legitimate rights to indeed GET to those principals (users) that have legitimate rights to indeed GET
or SET (change/create/delete) them. or SET (change/create/delete) them.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in information that may be sensitive from a business perspective, in
that they can be used to derive the network topology, e.g. list of that they can be used to derive the network topology, e.g. list of
nodes and their IP address (lmpNbrTable) and list of data-bearing nodes and their IP address (lmpNbrTable) and list of data-bearing
links (lmpDataBearingLinkTable). Allowing uncontrolled access to links (lmpDataLinkTable). Allowing uncontrolled access to these
these objects could result in malicious and unwanted disruptions of objects could result in malicious and unwanted disruptions of network
network traffic, incorrect network configurations or theft of com- traffic, incorrect network configurations or theft of competitive
petitive business information. There are no objects that are particu- business information. There are no objects that are particularly sen-
larly sensitive in their own right, such as passwords or monetary sitive in their own right, such as passwords or monetary amounts.
amounts.
12. Acknowledgments 12. Acknowledgments
The general structure of this draft has been modeled around draft- The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt. ietf-mpls-lsr-mib-06.txt.
The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and
George Wang. George Wang.
13. References 13. References
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., and Rajagopalan, B.,
"Link Management Protocol", Internet Draft
<draft-ietf-ccamp-lmp-03.txt>, March 2002.
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Function Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-08.txt>,
April 2002.
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-03.txt>,
May 2002.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base",
Internet Draft <draft-ietf-mpls-bundle-mib-02.txt>,
May 2002.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi-
numbers
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990. based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991. STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with [RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991. the SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996. January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April Network Management Protocol (SNMP)", RFC 2572, April
1999. 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999. Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
"Introduction to Version 3 of the Internet-standard J., Rose, M., and S. Waldbusser, "Structure of
Network Management Framework", RFC 2570, April 1999. Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November for the Internet Protocol", RFC 2401, November
1998. 1998.
[IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
Requirement Levels", BCP 14, RFC 2119, March 1997. RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-03.txt>,
May 2002.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base",
Internet Draft <draft-ietf-mpls-bundle-mib-03.txt>,
June 2002.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS. See also:
http://www.iana.org/assignments/address-family-numbers
For MIB see: http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Function Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-08.txt>,
April 2002.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., and Rajagopalan, B.,
"Link Management Protocol", Internet Draft
<draft-ietf-ccamp-lmp-03.txt>, March 2002.
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Meriton Networks Calient Networks, Inc. Meriton Networks Calient Networks, Inc.
3026 Solandt Road 25 Castilian Drive 3026 Solandt Road 25 Castilian Drive
Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117 Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117
Phone: +1-613-270-9279 x253 Email: jplang@calient.net Phone: +1-613-270-9279 x253 Email: jplang@calient.net
Email: martin.dubuc@meriton.com Email: martin.dubuc@meriton.com
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Nayna Networks, Inc. Calient Networks, Inc. Nayna Networks, Inc. Calient Networks, Inc.
157 Topaz Street 5853 Rue Ferrari 157 Topaz Street 5853 Rue Ferrari
Milipitas, CA 95035 San Jose, CA 95138 Milipitas, CA 95035 San Jose, CA 95138
Phone: +1-408-956-8000 x357 Email: evan@calient.net Phone: +1-408-956-8000 x357 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/