draft-ietf-ccamp-lmp-mib-10.txt   rfc4327.txt 
Network Working Group Martin Dubuc Network Working Group M. Dubuc
Internet Draft Request for Comments: 4327 T. Nadeau
Category: Standards Track Sudheer Dharanikota Category: Standards Track Cisco Systems
Expires: March 2005 J. Lang
Thomas D. Nadeau Sonos, Inc.
Cisco Systems E. McGinnis
Hammerhead Systems
Jonathan P. Lang January 2006
Rincon Networks
Evan McGinnis
Calient Networks
September 2004
Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-10.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with Link Management Protocol (LMP) Management Information Base (MIB)
all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This document specifies an Internet standards track protocol for the
and may be updated, replaced, or obsoleted by other documents at any Internet community, and requests discussion and suggestions for
time. It is inappropriate to use Internet-Drafts as reference improvements. Please refer to the current edition of the "Internet
material or to cite them other than as "work in progress." Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2006).
http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Link In particular, it describes managed objects for modeling the Link
Management Protocol (LMP). Management Protocol (LMP).
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . . 2 1. The Internet-Standard Management Framework ......................2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Introduction ....................................................2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology .....................................................3
4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Feature Checklist ...............................................3
5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Outline .........................................................4
6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 6. Brief Description of MIB Objects ................................4
6.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6.1. lmpNbrTable ................................................4
6.2. lmpControlChannelTable . . . . . . . . . . . . . . . . . . . . 5 6.2. lmpControlChannelTable .....................................4
6.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 5 6.3. lmpControlChannelPerfTable .................................4
6.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 5 6.4. lmpTeLinkTable .............................................5
6.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 5 6.5. lmpLinkVerificationTable ...................................5
6.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 5 6.6. lmpTeLinkPerfTable .........................................5
6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5 6.7. lmpDataLinkTable ...........................................5
6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5 6.8. lmpDataLinkPerfTable .......................................5
7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5 7. Example of LMP Control Channel Setup ............................5
8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8 8. Application of the Interfaces Group to LMP ......................8
8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9 8.1. Support of the LMP Layer by ifTable ........................9
9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11 9. LMP MIB Module Definitions .....................................11
10. Intellectual Property Considerations . . . . . . . . . . . . . . 78 10. Security Considerations .......................................77
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 78 11. Contributors ..................................................78
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 79 12. Acknowledgements ..............................................78
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 80 13. IANA Considerations ...........................................78
13.1 IANA Considerations for lmp ifType . . . . . . . . . . . . . . 80 13.1. IANA Considerations for lmp ifType .......................78
13.2 IANA Considerations for LMP-MIB . . . . . . . . . . . . . . . . 80 13.2. IANA Considerations for LMP-MIB ..........................78
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 14. References ....................................................79
14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 80 14.1. Normative References .....................................79
14.2 Informative References . . . . . . . . . . . . . . . . . . . . 81 14.2. Informative References ...................................80
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 82
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 82
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
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
ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link
Management Protocol [LMP], which primary purpose is to manage traffic Management Protocol [RFC4204] are key components of this
engineering (TE) links, is one of the key components of this stan- standardization activity. The primary purpose of LMP is to manage
dardization activity. Primary goals of LMP are the maintenance of the traffic engineering (TE) links. Primary goals of LMP are the
control channel connectivity, correlation of link properties, verifi- maintenance of the control channel connectivity, correlation of link
cation of data-bearing links and detection and isolation of link properties, verification of data-bearing links, and detection and
faults. isolation of link faults.
We describe in this document a MIB module that can be used to manage We describe in this document a MIB module that can be used to manage
LMP implementations. This MIB module covers both configuration and LMP implementations. This MIB module covers both configuration and
performance monitoring aspects of LMP. performance monitoring aspects of LMP.
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 [RFC2119].
[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 [RFC4204]. An "LMP adjacency" is formed between
nodes that support the same capabilities, and LMP messages are two 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 anytime an LMP message needs to be transferred to a neighbor node, it
can be sent on any of the active control channels. The control can be sent on any of the active control channels. The control
channels can also be used to exchange MPLS control plane information channels can also be used to exchange MPLS control plane information
or routing information. or routing information.
LMP is designed to support aggregation of one or more data-bearing LMP is designed to support aggregation of one or more data-bearing
links into a traffic-engineering (TE) link. The data-bearing links links into a traffic-engineering (TE) link. The data-bearing links
can be either component links or ports depending on their can be either component links or ports depending on their
multiplexing capability (see [LMP] for distinction between port and multiplexing capability (see [RFC4204] for distinction between port
component link). and component link).
Each TE link is associated with an LMP adjacency, and one or more Each TE link is associated with an LMP adjacency, and one or more
control channels are used to exchange LMP messages for a particular control channels are used to exchange LMP messages for a particular
adjacency. In turn, control channels are used to manage the TE links adjacency. In turn, control channels are used to manage the TE links
associated with the LMP adjacency. associated with the LMP adjacency.
4. Feature Checklist 4. Feature Checklist
The Link Management Protocol MIB module (LMP-MIB) is designed to The Link Management Protocol MIB module (LMP-MIB) is designed to
satisfy the following requirements and constraints: satisfy the following requirements and constraints:
- The MIB module supports the enabling and disabling of LMP - The MIB module supports the enabling and disabling of LMP
capability on LMP capable interfaces of a photonic switch, capability on LMP-capable interfaces of a photonic switch, optical
optical cross-connect or router. cross-connect, or router.
- The MIB module is used provide information about LMP adjacencies. - The MIB module is used to provide information about LMP
adjacencies.
- Support is provided for configuration of the keep alive and - Support is provided for configuration of the keep alive and link
link verification parameters. verification parameters.
- The MIB module is used to express the mapping between local and - The MIB module is used to express the mapping between local and
remote TE links, as well as local and remote interface identifiers remote TE links, as well as local and remote interface identifiers
for port or component link. for port or component link.
- Performance counters are provided for measuring LMP - Performance counters are provided for measuring LMP performance on
performance on a per-control channel basis. Performance counters a per-control channel basis. Performance counters are also
are also provided for measuring LMP performance on the data- provided for measuring LMP performance on the data-bearing links.
bearing links.
Note that the LMP MIB module goes hand-in-hand with the TE Link (TE- Note that the LMP MIB module goes hand-in-hand with the TE Link
LINK-STD-MIB) MIB module [TELINK-MIB]. The TE link table, which is (TE-LINK-STD-MIB) MIB module [RFC4220]. The TE link table, which is
used to associate data-bearing links to TE links, is defined in the used to associate data-bearing links to TE links, is defined in the
TE Link MIB. The TE link table in the LMP MIB module contains TE link TE Link MIB. The TE link table in the LMP MIB module contains TE
information specific to LMP. link information specific to LMP.
5. Outline 5. Outline
Configuring LMP through an optical device involves the following Configuring LMP through an optical device involves the following
steps: steps:
- Enabling LMP on LMP capable interfaces through control channel - Enabling LMP on LMP-capable interfaces through control channel
configuration. configuration.
- Optionally specifying link verification parameters. - Optionally specifying link verification parameters.
- Configuring the data-bearing links and associating them to the - Configuring the data-bearing links and associating them to the
appropriate TE link (this association is stored in the appropriate TE link (this association is stored in the
ifStackTable of the Interfaces Group MIB). ifStackTable of the Interfaces Group MIB).
TE links are managed by the control channels that run between the TE links are managed by the control channels that run between the
same pair of nodes (LMP adjacency). same pair of nodes (LMP adjacency).
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
Sections 6.1-6.8 describe objects pertaining to LMP. The MIB objects Sections 6.1-6.8 describe objects pertaining to LMP. The MIB objects
were derived from the LMP document [LMP]. were derived from the LMP document [RFC4204].
6.1. lmpNbrTable 6.1. lmpNbrTable
The remote node table is used to identify the pair of nodes that The remote node table is used to identify the pair of nodes that
exchange LMP messages over control channels. exchange LMP messages over control channels.
6.2. lmpControlChannelTable 6.2. lmpControlChannelTable
The control channel table is used for enabling the LMP protocol on The control channel table is used for enabling the LMP protocol on
LMP-capable interfaces. A photonic switch, optical cross-connect or LMP-capable interfaces. A photonic switch, optical cross-connect, or
router creates an entry in this table for every LMP capable interface router creates an entry in this table for every LMP-capable interface
in that device. in that device.
6.3. lmpControlChannelPerfTable 6.3. lmpControlChannelPerfTable
The control channel performance table is used for collecting LMP The control channel performance table is used for collecting LMP
performance counts on a per-control channel basis. Each entry in the performance counts on a per-control channel basis. Each entry in the
lmpControlChannelTable has a corresponding entry in the lmpControlChannelTable has a corresponding entry in the
lmpControlChannelPerfTable. lmpControlChannelPerfTable.
6.4. lmpTeLinkTable 6.4. lmpTeLinkTable
skipping to change at page 5, line 44 skipping to change at page 5, line 20
6.5. lmpLinkVerificationTable 6.5. lmpLinkVerificationTable
The link verification table is used for configuring the LMP link The link verification table is used for configuring the LMP link
verification parameters of TE links. For every TE link entry in the verification parameters of TE links. For every TE link entry in the
lmpTeLinkTable that supports the link verification procedure, there lmpTeLinkTable that supports the link verification procedure, there
is a corresponding entry in the lmpLinkVerificationTable. is a corresponding entry in the lmpLinkVerificationTable.
6.6. lmpTeLinkPerfTable 6.6. lmpTeLinkPerfTable
The TE link performance table is used for collecting LMP performance The TE link performance table is used for collecting LMP performance
counts on a per-TE link basis. Each entry in the lmpTeLinkTable has a counts on a per-TE link basis. Each entry in the lmpTeLinkTable has
corresponding entry in the lmpTeLinkPerfTable. a corresponding entry in the lmpTeLinkPerfTable.
6.7. lmpDataLinkTable 6.7. lmpDataLinkTable
The data-bearing link table is used to specify the data-bearing links The data-bearing link table is used to specify the data-bearing links
that are associated with TE links. that are associated with TE links.
6.8. lmpDataLinkPerfTable 6.8. lmpDataLinkPerfTable
The data-bearing link performance table is used for collecting LMP The data-bearing link performance table is used for collecting LMP
performance counts on data-bearing links. performance counts on data-bearing links.
7. Example of LMP Control Channel Setup 7. 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 9 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 module, it is intended as an aid to understanding some of the MIB module, it is intended as an aid to understanding some of the
key concepts. It is meant to be read after going through the MIB key concepts. It is meant to be read after going through the MIB
itself. 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
nodes using two control channels. Suppose also that there are nodes using two control channels. Suppose also that there are
three data-bearing links. We also assume that the data-bearing three data-bearing links. We also assume that the data-bearing
links are ports (lambdas). We also assume that the link links are ports (lambdas). We also assume that the link
verification procedure is not enabled. The following example verification procedure is not enabled. The following example
skipping to change at page 8, line 16 skipping to change at page 7, line 40
lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 48, lmpDataLinkRemoteIfId = 48,
lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3) lmpDataLinkStorageType = nonVolatile(3)
} }
Note that the data-bearing link type (lmpDataLinkType) 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
componentLinkTable of the TE Link MIB module [TELINK-MIB]. componentLinkTable of the TE Link MIB module [RFC4220].
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 module to specify TE link information is created in the LMP MIB module to specify TE link information
specific to LMP. specific to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
skipping to change at page 8, line 49 skipping to change at page 8, line 24
lmpLinkVerifyDeadInterval = 300, lmpLinkVerifyDeadInterval = 300,
lmpLinkVerifyTransportMechanism = j0Trace(3), lmpLinkVerifyTransportMechanism = j0Trace(3),
lmpLinkVerifyAllLinks = true(2), lmpLinkVerifyAllLinks = true(2),
lmpLinkVerifyTransmissionRate = 100000, lmpLinkVerifyTransmissionRate = 100000,
lmpLinkVerifyWavelength = 0, lmpLinkVerifyWavelength = 0,
lmpLinkVerifyRowStatus = createAndGo(4), lmpLinkVerifyRowStatus = createAndGo(4),
lmpLinkVerifyStorageType = nonVolatile(3) lmpLinkVerifyStorageType = nonVolatile(3)
} }
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 [RFC2863].
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 TE Link MIB module may be created in the teLinkTable of TE Link MIB module
[TELINK-MIB]. [RFC4220].
8. Application of the Interfaces Group to LMP 8. Application of the Interfaces Group to LMP
The Interfaces Group [RFC2863] 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 [RFC2863] 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 interrelation of entries in the
ifTable is defined by Interfaces Stack Group defined in [RFC2863]. 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(227) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
In the above diagram, "Underlying Layer..." refers to the ifIndex In the above diagram, "Underlying Layer..." refers to the ifIndex
of any interface type over which the LMP interface will transmit of any interface type over which the LMP interface will transmit
its traffic. Note that if the underlying layer provides multiple its traffic. Note that if the underlying layer provides multiple
access to its media (i.e.: Ethernet), then it is possible to stack access to its media (i.e., Ethernet), then it is possible to stack
multiple LMP interfaces on top of this interface in parallel. multiple LMP interfaces on top of this interface in parallel.
Note that it is not a requirement that LMP control channels be Note that it is not a requirement that LMP control channels be
modeled as interfaces. It is acceptable that control channels modeled as interfaces. It is acceptable that control channels
simply exist as logical connections between adjacent LMP-capable simply exist as logical connections between adjacent LMP-capable
nodes. In this case, lmpCcIsIf is set to false(2) and no nodes. In this case, lmpCcIsIf is set to false(2) and no
corresponding entry is made in the ifTable. corresponding entry is made in the ifTable.
8.1. Support of the LMP Layer by ifTable 8.1. Support of the LMP Layer by ifTable
Some specific interpretations of ifTable for the LMP layer Some specific interpretations of ifTable for the LMP layer
follow. follow.
Object Use for the LMP layer Object Use for the LMP layer.
ifIndex Each LMP interface may be represented by an ifEntry. ifIndex Each LMP interface may be represented by an ifEntry.
ifDescr Description of the LMP interface. ifDescr Description of the LMP interface.
ifType The value that is allocated for LMP is TBD. ifType The value that is allocated for LMP is 227.
This number will be assigned by the IANA. This number has been 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 [RFC2863]. interface. Also see [RFC2863].
skipping to change at page 11, line 20 skipping to change at page 10, line 42
Set to false (2). Set to false (2).
ifHighSpeed See [RFC2863]. 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 [RFC2863]. 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 [RFC2863]. required by the compliance statements in [RFC2863].
ifAlias The non-volatile 'alias' name for the interface as ifAlias The nonvolatile 'alias' name for the interface as
specified by a network manager. specified by a network manager.
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [RFC2863]. See [RFC2863].
9. LMP MIB Module Definitions 9. LMP MIB Module Definitions
This MIB module IMPORTs objects from [RFC2578], [RFC2579], [RFC2580],
[RFC2863], [RFC4001], and [RFC4220], and it has REFERENCE clauses to
[RFC4204], [RFC4207], [RFC4209], [RFC3471], and [RFC2914].
LMP-MIB DEFINITIONS ::= BEGIN LMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
transmission, Unsigned32, Counter32, TimeTicks transmission, Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
TimeStamp TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB -- [RFC2863]
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- [RFC4001]
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; FROM TE-LINK-STD-MIB; -- [RFC4220]
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200409081200Z" -- 8 September 2004 12:00:00 EST LAST-UPDATED "200601110000Z" -- 11 January 2006
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@sympatico.ca Email: dubuc.consulting@sympatico.ca
Sudheer Dharanikota
Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Email: jplang@ieee.org Email: jplang@ieee.org
Evan McGinnis Evan McGinnis
Email: evan@calient.net" Email: emcginnis@hammerheadsystems.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2004 The Internet Society. This version of "Copyright (C) 2006 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC 4327; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200409081200Z" -- 8 September 2004 12:00:00 EST "200601110000Z" -- 11 January 2006
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC 4327"
Editor)" ::= { transmission 227 }
::= { transmission xxx } -- To be assigned by IANA.
-- Request to assign same number as LMP
-- ifType.
-- 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 13, line 19 skipping to change at page 12, line 42
"The retransmission interval delay in milliseconds." "The retransmission interval delay in milliseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
LmpNodeId ::= TEXTUAL-CONVENTION LmpNodeId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d" DISPLAY-HINT "1d.1d.1d.1d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a Node ID in network byte order. Node ID is an "Represents a Node ID in network byte order. Node ID is an
address of type IPv4." address of type IPv4."
REFERENCE REFERENCE
"Section 1.1 of Link Management Protocol, RFC xxx" "Section 1.1 of Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
SYNTAX OCTET STRING(SIZE(4)) SYNTAX OCTET STRING(SIZE(4))
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications -- Notifications
lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 }
-- Tables, Scalars -- Tables, Scalars
lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 }
-- Conformance -- Conformance
lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 }
lmpAdminStatus OBJECT-TYPE lmpAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP on the node. "The desired operational status of LMP on the node.
Implementations should save the value of this object in Implementations should save the value of this object in
skipping to change at page 14, line 52 skipping to change at page 14, line 27
"This is a unique index for an entry in the LmpNbrTable. "This is a unique index for an entry in the LmpNbrTable.
This value represents the remote Node ID." This value represents the remote Node ID."
::= { lmpNbrEntry 1 } ::= { lmpNbrEntry 1 }
lmpNbrRetransmitInterval OBJECT-TYPE lmpNbrRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial retransmission interval that "This object specifies the initial retransmission interval that
is used for the retransmission of messages which require is used for the retransmission of messages that require
acknowledgement. This object along with lmpNbrRetryLimit is acknowledgement. This object along with lmpNbrRetryLimit is
used to implement congestion handling mechanism as defined in used to implement congestion-handling mechanism as defined in
Section 10 of the Link Management Protocol specification, Section 10 of the Link Management Protocol specification,
which is based on RFC 2914." which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204.
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] Congestion Control Principles, RFC 2914."
DEFVAL { 500 } DEFVAL { 500 }
::= { lmpNbrEntry 2 } ::= { lmpNbrEntry 2 }
lmpNbrRetryLimit OBJECT-TYPE lmpNbrRetryLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum number of times a message "This object specifies the maximum number of times a message
is transmitted without being acknowledged. A value of 0 is used is transmitted without being acknowledged. A value of 0 is used
to indicate that a node should never stop retransmission. to indicate that a node should never stop retransmission.
This object along with lmpNbrRetransmitInterval is This object along with lmpNbrRetransmitInterval is
used to implement congestion handling mechanism as defined in used to implement congestion-handling mechanism as defined in
Section 10 of the Link Management Protocol specification, Section 10 of the Link Management Protocol specification,
which is based on RFC 2914." which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204.
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] Congestion Control Principles, RFC 2914."
DEFVAL { 3 } DEFVAL { 3 }
::= { lmpNbrEntry 3 } ::= { lmpNbrEntry 3 }
lmpNbrRetransmitDelta OBJECT-TYPE lmpNbrRetransmitDelta OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object governs the speed with which the sender increases "This object governs the speed with which the sender increases
the retransmission interval as explained in section 10 of the the retransmission interval as explained in section 10 of the
Link Management Protocol specification, which is based on Link Management Protocol specification, which is based on
RFC 2914. This value is a power used to express the RFC 2914. This value is a power used to express the
exponential backoff. The ratio of two succesive retransmission exponential backoff. The ratio of two successive retransmission
intervals is (1 + Delta)." intervals is (1 + Delta)."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204.
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] Congestion Control Principles, RFC 2914."
DEFVAL { 1 } DEFVAL { 1 }
::= { lmpNbrEntry 4 } ::= { lmpNbrEntry 4 }
lmpNbrAdminStatus OBJECT-TYPE lmpNbrAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP to this remote node." "The desired operational status of LMP to this remote node."
::= { lmpNbrEntry 5 } ::= { lmpNbrEntry 5 }
skipping to change at page 17, line 11 skipping to change at page 16, line 35
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default value for the HelloInterval "This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It parameter used in the Hello protocol keep-alive phase. It
indicates how frequently LMP Hello messages will be sent. It indicates how frequently LMP Hello messages will be sent. It
is used a the default value for lmpCcHelloInterval. is used a the default value for lmpCcHelloInterval.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpObjects 4 } ::= { lmpObjects 4 }
lmpCcHelloIntervalDefaultMin OBJECT-TYPE lmpCcHelloIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin. Implementations should save the for lmpCcHelloIntervalMin. Implementations should save the
skipping to change at page 18, line 6 skipping to change at page 17, line 28
DESCRIPTION DESCRIPTION
"This object specifies the default HelloDeadInterval parameter "This object specifies the default HelloDeadInterval parameter
to use in the Hello protocol keep-alive phase. It indicates to use in the Hello protocol keep-alive phase. It indicates
how long a device should wait before declaring the control how long a device should wait before declaring the control
channel dead. The HelloDeadInterval parameter should be at channel dead. The HelloDeadInterval parameter should be at
least three times the value of HelloInterval. It is used as least three times the value of HelloInterval. It is used as
a default value for lmpCcHelloDeadInterval. Implementations a default value for lmpCcHelloDeadInterval. Implementations
should save the value of this object in persistent memory so should save the value of this object in persistent memory so
that it survives restarts or reboot." that it survives restarts or reboot."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpObjects 7 } ::= { lmpObjects 7 }
lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin. Implementations should save for lmpCcHelloDeadIntervalMin. Implementations should save
skipping to change at page 19, line 41 skipping to change at page 19, line 13
lmpCcRowStatus RowStatus, lmpCcRowStatus RowStatus,
lmpCcStorageType StorageType lmpCcStorageType StorageType
} }
lmpCcId OBJECT-TYPE lmpCcId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the local control channel identifier. "This value represents the local control channel identifier.
The control channel identifier is a non-zero 32 bit number." The control channel identifier is a non-zero 32-bit number."
::= { lmpControlChannelEntry 1 } ::= { lmpControlChannelEntry 1 }
lmpCcUnderlyingIfIndex OBJECT-TYPE lmpCcUnderlyingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If lmpCcIsIf is set to true(1), this object carries the "If lmpCcIsIf is set to true(1), this object carries the
index into the ifTable of the entry that represents the index into the ifTable of the entry that represents the
LMP interface over which LMP will transmit its traffic. LMP interface over which LMP will transmit its traffic.
skipping to change at page 20, line 37 skipping to change at page 20, line 8
and the value of lmpCcUnderlyingIfIndex should be and the value of lmpCcUnderlyingIfIndex should be
ignored." ignored."
::= { lmpControlChannelEntry 3 } ::= { lmpControlChannelEntry 3 }
lmpCcNbrNodeId OBJECT-TYPE lmpCcNbrNodeId OBJECT-TYPE
SYNTAX LmpNodeId SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the control channel remote node. "This is the Node ID of the control channel remote node.
This value is either configured or gets created by the node This value either is configured or gets created by the node
when a Config message is received or when an outgoing Config when a Config message is received or when an outgoing Config
message is acknowledged by the remote node." message is acknowledged by the remote node."
::= { lmpControlChannelEntry 4 } ::= { lmpControlChannelEntry 4 }
lmpCcRemoteId OBJECT-TYPE lmpCcRemoteId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel identifier "This value represents the remote control channel identifier
(32 bit number). It is determined during the negotiation (32-bit number). It is determined during the negotiation
phase. A value of zero means that the remote control channel phase. A value of zero means that the remote control channel
identifier has not yet been learnt." identifier has not yet been learnt."
::= { lmpControlChannelEntry 5 } ::= { lmpControlChannelEntry 5 }
lmpCcRemoteAddressType OBJECT-TYPE lmpCcRemoteAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel IP address "This value represents the remote control channel IP address
skipping to change at page 21, line 23 skipping to change at page 20, line 42
::= { lmpControlChannelEntry 6 } ::= { lmpControlChannelEntry 6 }
lmpCcRemoteIpAddr OBJECT-TYPE lmpCcRemoteIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel Internet "This value represents the remote control channel Internet
address for numbered control channel. The type of this address for numbered control channel. The type of this
address is determined by lmpCcRemoteAddressType. address is determined by lmpCcRemoteAddressType.
Control channel must be numbered on non point-to-point Control channel must be numbered on non-point-to-point
configuration. For point-to-point configuration, the configuration. For point-to-point configuration, the
remote control channel address can be of type unknown remote control channel address can be of type unknown
in which case this object must be a zero length string. The in which case this object must be a zero-length string. The
lmpCcRemoteId object then identifies the unnumbered lmpCcRemoteId object then identifies the unnumbered
address." address."
::= { lmpControlChannelEntry 7 } ::= { lmpControlChannelEntry 7 }
lmpCcSetupRole OBJECT-TYPE lmpCcSetupRole OBJECT-TYPE
SYNTAX INTEGER { active(1), passive(2) } SYNTAX INTEGER { active(1), passive(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The role that this node should take during establishment "The role that this node should take during establishment
skipping to change at page 21, line 52 skipping to change at page 21, line 23
::= { lmpControlChannelEntry 8 } ::= { lmpControlChannelEntry 8 }
lmpCcAuthentication OBJECT-TYPE lmpCcAuthentication OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the control channel must use "This object indicates whether the control channel must use
authentication." authentication."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpControlChannelEntry 9 } ::= { lmpControlChannelEntry 9 }
lmpCcHelloInterval OBJECT-TYPE lmpCcHelloInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloInterval "This object specifies the value of the HelloInterval
parameter. The default value for this object should be parameter. The default value for this object should be
set to lmpCcHelloIntervalDefault." set to lmpCcHelloIntervalDefault."
skipping to change at page 26, line 49 skipping to change at page 26, line 19
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."
::= { lmpControlChannelPerfEntry 1 } ::= { lmpControlChannelPerfEntry 1 }
lmpCcInDiscards OBJECT-TYPE lmpCcInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of inbound packets which were chosen to be "The number of inbound packets that were chosen to be
discarded even though no errors had been detected. One discarded even though no errors had been detected. One
possible reason for discarding such a packet could be to possible reason for discarding such a packet could be to
free up buffer space." free up buffer space."
::= { lmpControlChannelPerfEntry 2 } ::= { lmpControlChannelPerfEntry 2 }
lmpCcInErrors OBJECT-TYPE lmpCcInErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 27, line 30 skipping to change at page 26, line 48
DESCRIPTION DESCRIPTION
"The total number of LMP message octets transmitted out of "The total number of LMP message octets transmitted out of
the control channel." the control channel."
::= { lmpControlChannelPerfEntry 4 } ::= { lmpControlChannelPerfEntry 4 }
lmpCcOutDiscards OBJECT-TYPE lmpCcOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outbound packets which were chosen to be "The number of outbound packets that were chosen to be
discarded even though no errors had been detected to discarded even though no errors had been detected to
prevent their being transmitted. One possible reason prevent their being transmitted. One possible reason
for discarding such a packet could be to free up buffer for discarding such a packet could be to free up buffer
space." space."
::= { lmpControlChannelPerfEntry 5 } ::= { lmpControlChannelPerfEntry 5 }
lmpCcOutErrors OBJECT-TYPE lmpCcOutErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 37, line 5 skipping to change at page 36, line 21
-- End of lmpControlChannelPerfTable -- End of lmpControlChannelPerfTable
-- LMP TE Link Table -- LMP TE Link Table
lmpTeLinkTable OBJECT-TYPE lmpTeLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkEntry SYNTAX SEQUENCE OF LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the LMP specific TE link information. "This table specifies the LMP-specific TE link information.
Overall TE link information is kept in three separate tables: Overall TE link information is kept in three separate tables:
ifTable, for interface specific information, lmpTeLinkTable ifTable for interface-specific information, lmpTeLinkTable
for LMP specific information and teLinkTable for generic for LMP specific information, and teLinkTable for generic
TE link information. ifIndex is the common index to all TE link information. ifIndex is the common index to all
tables." tables."
::= { lmpObjects 12 } ::= { lmpObjects 12 }
lmpTeLinkEntry OBJECT-TYPE lmpTeLinkEntry OBJECT-TYPE
SYNTAX LmpTeLinkEntry SYNTAX LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(200) that is managed by LMP. An ifEntry with ifType of teLink(200) that is managed by LMP. An ifEntry with
an ifIndex must exist before the corresponding lmpTeLinkEntry is an ifIndex must exist before the corresponding lmpTeLinkEntry is
created. If a TE link entry in the ifTable is destroyed, then so created. If a TE link entry in the ifTable is destroyed, then
is the corresponding entry in the lmpTeLinkTable. The so is the corresponding entry in the lmpTeLinkTable. The
administrative status value is controlled from the ifEntry. administrative status value is controlled from the ifEntry.
Setting the administrative status to testing prompts LMP to Setting the administrative status to testing prompts LMP to
start link verification on the TE link. Information about the TE start link verification on the TE link. Information about the
link that is not LMP specific is contained in teLinkTable of the TE link that is not LMP specific is contained in teLinkTable of
TE-LINK-STD-MIB MIB module." the TE-LINK-STD-MIB MIB module."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrRemoteNodeId LmpNodeId, lmpTeLinkNbrRemoteNodeId LmpNodeId,
lmpTeLinkVerification TruthValue, lmpTeLinkVerification TruthValue,
lmpTeLinkFaultManagement TruthValue, lmpTeLinkFaultManagement TruthValue,
lmpTeLinkDwdm TruthValue, lmpTeLinkDwdm TruthValue,
lmpTeLinkOperStatus INTEGER, lmpTeLinkOperStatus INTEGER,
lmpTeLinkRowStatus RowStatus, lmpTeLinkRowStatus RowStatus,
lmpTeLinkStorageType StorageType lmpTeLinkStorageType StorageType
} }
lmpTeLinkNbrRemoteNodeId OBJECT-TYPE lmpTeLinkNbrRemoteNodeId OBJECT-TYPE
SYNTAX LmpNodeId SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the TE link remote node. This value "This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation may be learned during control channel parameter negotiation
phase (in the Config message). Node ID is an address which phase (in the Config message). Node ID is an address whose
type must be IPv4." type must be IPv4."
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
lmpTeLinkVerification OBJECT-TYPE lmpTeLinkVerification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the LMP link verification procedure "This object indicates if the LMP link verification procedure
is enabled for this TE link." is enabled for this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpTeLinkEntry 2 } ::= { lmpTeLinkEntry 2 }
lmpTeLinkFaultManagement OBJECT-TYPE lmpTeLinkFaultManagement OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the LMP fault management procedure "This object indicates if the LMP fault management procedure
is enabled on this TE link." is enabled on this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpTeLinkEntry 3 } ::= { lmpTeLinkEntry 3 }
lmpTeLinkDwdm OBJECT-TYPE lmpTeLinkDwdm OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the LMP DWDM procedure is enabled "This object indicates if the LMP DWDM procedure is enabled
on this TE link." on this TE link."
REFERENCE REFERENCE
"Link Management Protocol (LMP) for Dense Wavelength Division "Link Management Protocol (LMP) for Dense Wavelength Division
Multiplexing (DWDM) Optical Line Systems, RFC xxx" Multiplexing (DWDM) Optical Line Systems, RFC 4209"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP-WDM]
::= { lmpTeLinkEntry 4 } ::= { lmpTeLinkEntry 4 }
lmpTeLinkOperStatus OBJECT-TYPE lmpTeLinkOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), down(2), testing(3), init(4), degraded(5) up(1), down(2), testing(3), init(4), degraded(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this TE link. The status "The actual operational status of this TE link. The status
is set to testing when the TE link is performing link is set to testing when the TE link is performing link
verification. A degraded state indicates that there are verification. A degraded state indicates that there is
no active control channel between the pair of nodes that no active control channel between the pair of nodes that
form the endpoints of the TE link, but yet at least one form the endpoints of the TE link, but yet at least one
data-bearing links on the TE link is allocated." data-bearing link on the TE link is allocated."
::= { lmpTeLinkEntry 5 } ::= { lmpTeLinkEntry 5 }
lmpTeLinkRowStatus OBJECT-TYPE lmpTeLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1). in a row can be changed if the status is active(1).
skipping to change at page 40, line 23 skipping to change at page 39, line 34
DESCRIPTION DESCRIPTION
"This table specifies TE link information associated with the "This table specifies TE link information associated with the
LMP verification procedure." LMP verification procedure."
::= { lmpObjects 14 } ::= { lmpObjects 14 }
lmpLinkVerificationEntry OBJECT-TYPE lmpLinkVerificationEntry OBJECT-TYPE
SYNTAX LmpLinkVerificationEntry SYNTAX LmpLinkVerificationEntry
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 an LMP-enabled device for
every TE link that supports the LMP verification every TE link that supports the LMP verification
procedure." procedure."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpLinkVerificationTable 1 } ::= { lmpLinkVerificationTable 1 }
LmpLinkVerificationEntry ::= SEQUENCE { LmpLinkVerificationEntry ::= SEQUENCE {
lmpLinkVerifyInterval LmpInterval, lmpLinkVerifyInterval LmpInterval,
lmpLinkVerifyDeadInterval LmpInterval, lmpLinkVerifyDeadInterval LmpInterval,
lmpLinkVerifyTransportMechanism BITS, lmpLinkVerifyTransportMechanism BITS,
lmpLinkVerifyAllLinks TruthValue, lmpLinkVerifyAllLinks TruthValue,
skipping to change at page 40, line 49 skipping to change at page 40, line 14
lmpLinkVerifyInterval OBJECT-TYPE lmpLinkVerifyInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyInterval parameter used "This object specifies the VerifyInterval parameter used
in the LMP link verification process. It indicates the in the LMP link verification process. It indicates the
interval at which the Test messages are sent." interval at which the Test messages are sent."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 1 } ::= { lmpLinkVerificationEntry 1 }
lmpLinkVerifyDeadInterval OBJECT-TYPE lmpLinkVerifyDeadInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyDeadInterval parameter used "This object specifies the VerifyDeadInterval parameter used
in the verification of the physical connectivity of data- in the verification of the physical connectivity of data-
bearing links. It specifies the observation period used to bearing links. It specifies the observation period used to
detect a Test message at the remote node." detect a Test message at the remote node."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 2 } ::= { lmpLinkVerificationEntry 2 }
lmpLinkVerifyTransportMechanism OBJECT-TYPE lmpLinkVerifyTransportMechanism OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
-- All encoding types: -- All encoding types:
payload(0), payload(0),
-- SONET/SDH encoding type: -- SONET/SDH encoding type:
dccSectionOverheadBytes(1), dccSectionOverheadBytes(1),
dccLineOverheadBytes(2), dccLineOverheadBytes(2),
j0Trace(3), j0Trace(3),
skipping to change at page 41, line 43 skipping to change at page 40, line 51
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This defines the transport mechanism for the Test messages. The "This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx and "Link Management Protocol, RFC 4204
SONET/SDH Encoding for Link Management Protocol (LMP) Synchronous Optical Network (SONET)/Synchronous Digital
Test Messages, RFC xxx" Hierarchy (SDH) Encoding for Link Management Protocol (LMP)
-- RFC Editor to fill in RFC number that will be assigned to Test Messages, RFC 4207"
-- [LMP] and [LMP-TEST]
::= { lmpLinkVerificationEntry 3 } ::= { lmpLinkVerificationEntry 3 }
lmpLinkVerifyAllLinks OBJECT-TYPE lmpLinkVerifyAllLinks OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of true(2) for this object indicates that the "A value of true(2) for this object indicates that the
verification process checks all unallocated links, otherwise verification process checks all unallocated links, otherwise
only the new ports or component links that have been added to only the new ports or component links that have been added to
skipping to change at page 42, line 23 skipping to change at page 41, line 30
lmpLinkVerifyTransmissionRate OBJECT-TYPE lmpLinkVerifyTransmissionRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes per second" UNITS "bytes per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the transmission rate of the data link over which "This is the transmission rate of the data link over which
the Test messages will be transmitted and is expressed in the Test messages will be transmitted and is expressed in
bytes per second." bytes per second."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 5 } ::= { lmpLinkVerificationEntry 5 }
lmpLinkVerifyWavelength OBJECT-TYPE lmpLinkVerifyWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "nanometers" UNITS "nanometers"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value corresponds to the wavelength at "This value corresponds to the wavelength at
which the Test messages will be transmitted over and is which the Test messages will be transmitted and is
measured in nanometers (nm). If each data-bearing link measured in nanometers (nm). If each data-bearing link
corresponds to a separate wavelength, than this value should corresponds to a separate wavelength, then this value should
be set to 0." be set to 0."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 6 } ::= { lmpLinkVerificationEntry 6 }
lmpLinkVerifyRowStatus OBJECT-TYPE lmpLinkVerifyRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1). in a row can be changed if the status is active(1).
skipping to change at page 43, line 38 skipping to change at page 42, line 41
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies LMP TE link performance counters." "This table specifies LMP TE link performance counters."
::= { lmpObjects 15 } ::= { lmpObjects 15 }
lmpTeLinkPerfEntry OBJECT-TYPE lmpTeLinkPerfEntry OBJECT-TYPE
SYNTAX LmpTeLinkPerfEntry SYNTAX LmpTeLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by an LMP-enabled device for
every TE link. lmpTeCounterDiscontinuityTime is used every TE link. lmpTeCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects to indicate potential discontinuity for all counter objects
in this table." in this table."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkPerfTable 1 } ::= { lmpTeLinkPerfTable 1 }
LmpTeLinkPerfEntry ::= SEQUENCE { LmpTeLinkPerfEntry ::= SEQUENCE {
lmpTeInOctets Counter32, lmpTeInOctets Counter32,
lmpTeOutOctets Counter32, lmpTeOutOctets Counter32,
lmpTeBeginVerifyReceived Counter32, lmpTeBeginVerifyReceived Counter32,
skipping to change at page 52, line 46 skipping to change at page 51, line 49
SYNTAX LmpDataLinkEntry 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 lmpDataLinkEntry 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
lmpDataLinkTable. 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 is also
used to get information in the componentLinkTable used to get information in the componentLinkTable
of the TE-LINK-STD-MIB MIB module." of the TE-LINK-STD-MIB MIB module."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataLinkTable 1 } ::= { lmpDataLinkTable 1 }
LmpDataLinkEntry ::= SEQUENCE { LmpDataLinkEntry ::= SEQUENCE {
lmpDataLinkType INTEGER, lmpDataLinkType INTEGER,
lmpDataLinkAddressType InetAddressType, lmpDataLinkAddressType InetAddressType,
lmpDataLinkIpAddr InetAddress, lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress, lmpDataLinkRemoteIpAddress InetAddress,
skipping to change at page 53, line 28 skipping to change at page 52, line 31
lmpDataLinkType 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
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 1 } ::= { lmpDataLinkEntry 1 }
lmpDataLinkAddressType OBJECT-TYPE lmpDataLinkAddressType 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)."
skipping to change at page 54, line 8 skipping to change at page 53, line 10
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local Internet address for numbered links. The type "The local Internet address for numbered links. The type
of this address is determined by the value of of this address is determined by the value of
lmpDataLinkAddressType object. lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents For IPv4 and IPv6 numbered links, this object represents
the local IP address associated with the data-bearing the local IP address associated with the data-bearing
link. For an unnumbered link, the local address is link. For an unnumbered link, the local address is
of type unknown and this object is set to the zero length of type unknown and this object is set to the zero-length
string and the ifIndex object then identifies the string and the ifIndex object then identifies the
unnumbered address." unnumbered address."
::= { lmpDataLinkEntry 3 } ::= { lmpDataLinkEntry 3 }
lmpDataLinkRemoteIpAddress OBJECT-TYPE lmpDataLinkRemoteIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote Internet address for numbered data-bearing links. "The remote Internet address for numbered data-bearing links.
The type of this address is determined by the The type of this address is determined by the
lmpDataLinkAddressType object. lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents the For IPv4 and IPv6 numbered links, this object represents the
remote IP address associated with the data-bearing link. For remote IP address associated with the data-bearing link. For
an unnumbered link, the remote address is of type unknown an unnumbered link, the remote address is of type unknown
and this object is set to the zero length string and the and this object is set to the zero-length string and the
lmpDataLinkRemoteIfId object then identifies the unnumbered lmpDataLinkRemoteIfId object then identifies the unnumbered
address. address.
This information is either configured manually or is This information is either configured manually or
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure." procedure."
::= { lmpDataLinkEntry 4 } ::= { lmpDataLinkEntry 4 }
lmpDataLinkRemoteIfId 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
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure." procedure."
::= { lmpDataLinkEntry 5 } ::= { lmpDataLinkEntry 5 }
lmpDataLinkEncodingType OBJECT-TYPE lmpDataLinkEncodingType OBJECT-TYPE
SYNTAX TeLinkEncodingType SYNTAX TeLinkEncodingType
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."
skipping to change at page 55, line 18 skipping to change at page 54, line 21
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
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 7 } ::= { lmpDataLinkEntry 7 }
lmpDataLinkPassiveOperStatus 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
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 4204"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 8 } ::= { lmpDataLinkEntry 8 }
lmpDataLinkRowStatus 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. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1). in a row can be changed if the status is active(1).
skipping to change at page 57, line 28 skipping to change at page 56, line 26
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."
::= { lmpDataLinkPerfEntry 2 } ::= { lmpDataLinkPerfEntry 2 }
lmpDataLinkActiveTestSuccess 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 tests
that were successful on the active side of this data- that were successful on the active side of this data-
bearing link." bearing link."
::= { lmpDataLinkPerfEntry 3 } ::= { lmpDataLinkPerfEntry 3 }
lmpDataLinkActiveTestFailure 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 tests
that failed on the active side of this data-bearing link." that failed on the active side of this data-bearing link."
::= { lmpDataLinkPerfEntry 4 } ::= { lmpDataLinkPerfEntry 4 }
lmpDataLinkPassiveTestSuccess 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 tests
that were successful on the passive side of this data- that were successful on the passive side of this data-
bearing link." bearing link."
::= { lmpDataLinkPerfEntry 5 } ::= { lmpDataLinkPerfEntry 5 }
lmpDataLinkPassiveTestFailure 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 tests
that failed on the passive side of this data-bearing link." that failed on the passive side of this data-bearing link."
::= { lmpDataLinkPerfEntry 6 } ::= { lmpDataLinkPerfEntry 6 }
lmpDataLinkDiscontinuityTime 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 any one or more of this data-bearing link's counters suffered
skipping to change at page 58, line 42 skipping to change at page 57, line 41
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LMP notification rate depends on the size of the network, "The LMP notification rate depends on the size of the network,
the type of links, the network configuration, the the type of links, the network configuration, the
reliability of the network, etc. reliability of the network, etc.
When designing this MIB, care has been taken to minimize the When designing this MIB, care has been taken to minimize the
amount of notifications generated for LMP purposes. Wherever amount of notifications generated for LMP purposes. Wherever
possible, notifications are state driven meaning the possible, notifications are state driven, meaning the
notification are only sent when the system changes state. notifications are sent only when the system changes state.
The only notifications that are repeated and could cause a The only notifications that are repeated and could cause a
problem as far as congestion is concerned are the ones problem as far as congestion is concerned are the ones
associated with data link verification. associated with data link verification.
Without any considerations to handling of these Without any considerations to handling of these
notifications, a problem may arise if the number of data notifications, a problem may arise if the number of data
links is high. Since the data link verification notifications links is high. Since the data link verification notifications
can happen only once per data link per link verification can happen only once per data link per link verification
interval, the notification rate should be sustainable if one interval, the notification rate should be sustainable if one
chooses an appropriate link verification interval for a given chooses an appropriate link verification interval for a given
network configuration. For instance, a network of 100 nodes network configuration. For instance, a network of 100 nodes
with 5 links of 128 wavelengths each and a link verification with 5 links of 128 wavelengths each and a link verification
of 1 minute with no more than 10% of the links failed at any of 1 minute with no more than 10% of the links failed at any
given time would have 1 notification per second sent from given time would have 1 notification per second sent from
each node, or 100 notifications per second for the whole each node, or 100 notifications per second for the whole
network. The rest of the notifications are negligeable network. The rest of the notifications are negligible
compared to this number. compared to this number.
To alleviate the congestion problem, the To alleviate the congestion problem, the
lmpNotificationMaxRate object can be used to implement a lmpNotificationMaxRate object can be used to implement a
throttling mechanism. It is also possible to enable/disable throttling mechanism. It is also possible to enable/disable
certain type of notifications. certain type of notifications.
This variable indicates the maximum number of This variable indicates the maximum number of
notifications issued per minute. If events occur notifications issued per minute. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
skipping to change at page 61, line 12 skipping to change at page 60, line 12
-- 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 the TE link is numbered or unnumbered. This notification
should not be sent unless lmpLinkPropertyNotificationsEnabled should not be sent unless lmpLinkPropertyNotificationsEnabled
is true. It is recommended that this notification be reported is true. It is recommended that this notification be reported
only the first time a mismatch is detected. Otherwise, for a only the first time a mismatch is detected. Otherwise, for a
given TE link, this notification can occur no more than once given TE link, this notification can occur no more than once
per verification interval (lmpGlobalLinkVerificationInterval)." per verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId } OBJECTS { lmpDataLinkType, 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. lmpDataLinkType property mismatch is detected on the node. lmpDataLinkType
is used to identify the local identifiers associated with is used to identify the local identifiers associated with
the data link (the data link interface index can be used the data link (the data link interface index can be used
to determine the TE link interface index as this to determine the TE link interface index as this
relationship is captured in the interface stack table). relationship is captured in the interface stack table).
The remote entity interface id is the remote entity The remote entity interface ID is the remote entity
interface id received in the LinkSummary message. interface ID received in the LinkSummary message.
This notification should not be sent unless This notification should not be sent unless
lmpLinkPropertyNotificationsEnabled is true. It is lmpLinkPropertyNotificationsEnabled is true. It is
recommended that this notification be reported only the recommended that this notification be reported only the
first time a mismatch is detected. Otherwise, for a given first time a mismatch is detected. Otherwise, for a given
data link, this notification can occur no more than once data link, this notification can occur no more than once
per verification interval (lmpGlobalLinkVerificationInterval)." per verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification -- Neighbor Notification
skipping to change at page 63, line 45 skipping to change at page 62, line 45
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices that 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 lmpCcIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices that 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 that support
the link verification procedure." the link verification procedure."
GROUP lmpNotificationGroup GROUP lmpNotificationGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
skipping to change at page 64, line 34 skipping to change at page 63, line 34
DESCRIPTION DESCRIPTION
"Support for notReady(3) and createAndWait(5) is "Support for notReady(3) and createAndWait(5) is
not required." not required."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpCcRemoteAddressType OBJECT lmpCcRemoteAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for non point-to-point configurations." supported for non-point-to-point configurations."
OBJECT lmpCcRemoteIpAddr OBJECT lmpCcRemoteIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
skipping to change at page 66, line 17 skipping to change at page 65, line 17
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices that 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 lmpCcIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices that 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 that support
the link verification procedure." the link verification procedure."
GROUP lmpNotificationGroup GROUP lmpNotificationGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
-- Scalars -- Scalars
OBJECT lmpAdminStatus OBJECT lmpAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 68, line 10 skipping to change at page 67, line 10
OBJECT lmpNbrRetransmitDelta OBJECT lmpNbrRetransmitDelta
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required, and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpNbrStorageType OBJECT lmpNbrStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpCcUnderlyingIfIndex OBJECT lmpCcUnderlyingIfIndex
skipping to change at page 68, line 40 skipping to change at page 67, line 40
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 lmpCcRemoteAddressType OBJECT lmpCcRemoteAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for non point-to-point configurations." supported for non-point-to-point configurations."
OBJECT lmpCcRemoteIpAddr OBJECT lmpCcRemoteIpAddr
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."
OBJECT lmpCcSetupRole OBJECT lmpCcSetupRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 69, line 33 skipping to change at page 68, line 33
OBJECT lmpCcHelloDeadIntervalMax OBJECT lmpCcHelloDeadIntervalMax
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required, and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpCcOperStatus OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION DESCRIPTION
"A value of configSnd(3), configRcv(4), active(5), "A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported." goingDown(6) need not be supported."
OBJECT lmpCcStorageType OBJECT lmpCcStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 70, line 48 skipping to change at page 69, line 48
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(5) } SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION DESCRIPTION
"The testing(3) and init(4) state need not be supported." "The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required, and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpTeLinkStorageType OBJECT lmpTeLinkStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpTeLinkVerificationTable -- lmpTeLinkVerificationTable
OBJECT lmpLinkVerifyTransmissionRate OBJECT lmpLinkVerifyTransmissionRate
skipping to change at page 71, line 24 skipping to change at page 70, line 24
OBJECT lmpLinkVerifyWavelength OBJECT lmpLinkVerifyWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpLinkVerifyRowStatus OBJECT lmpLinkVerifyRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required, and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpLinkVerifyStorageType OBJECT lmpLinkVerifyStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkAddressType OBJECT lmpDataLinkAddressType
skipping to change at page 71, line 49 skipping to change at page 70, line 49
supported for numbered links. For unnumbered links, the supported for numbered links. For unnumbered links, the
unknown(0) address type needs to be supported." unknown(0) address type needs to be supported."
OBJECT lmpDataLinkIpAddr 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 lmpDataLinkRemoteIpAddress 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 lmpDataLinkRemoteIfId OBJECT lmpDataLinkRemoteIfId
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 72, line 35 skipping to change at page 71, line 35
OBJECT lmpDataLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION DESCRIPTION
"A value of psvTst(4) need not be supported." "A value of psvTst(4) need not be supported."
OBJECT lmpDataLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required, and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpDataLinkStorageType OBJECT lmpDataLinkStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { lmpCompliances 2 } ::= { lmpCompliances 2 }
-- Units of conformance -- Units of conformance
skipping to change at page 73, line 51 skipping to change at page 72, line 51
lmpCcHelloDeadIntervalMin, lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax, lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated, lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus, lmpCcOperStatus,
lmpCcRowStatus, lmpCcRowStatus,
lmpCcStorageType, lmpCcStorageType,
lmpCcUpDownNotificationsEnabled lmpCcUpDownNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects which can be used to configure LMP interface." "Objects that can be used to configure LMP interface."
::= { lmpGroups 2 } ::= { lmpGroups 2 }
lmpCcIsInterfaceGroup OBJECT-GROUP lmpCcIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf } OBJECTS { lmpCcIsIf }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects which can be used to configure control channels "Objects that can be used to configure control channels
that are interfaces." that are interfaces."
::= { lmpGroups 3 } ::= { lmpGroups 3 }
lmpCcIsNotInterfaceGroup OBJECT-GROUP lmpCcIsNotInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcUnderlyingIfIndex, OBJECTS { lmpCcUnderlyingIfIndex,
lmpCcIsIf, lmpCcIsIf,
lmpCcLastChange, lmpCcLastChange,
lmpCcAdminStatus lmpCcAdminStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects which can be used to configure control channels "Objects that can be used to configure control channels
that are not interfaces." that are not interfaces."
::= { lmpGroups 4 } ::= { lmpGroups 4 }
lmpLinkPropertyCorrelationGroup OBJECT-GROUP lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyNotificationsEnabled } OBJECTS { lmpLinkPropertyNotificationsEnabled }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects used to configure the link "Collection of objects used to configure the link
property correlation procedure." property correlation procedure."
::= { lmpGroups 5 } ::= { lmpGroups 5 }
skipping to change at page 77, line 28 skipping to change at page 76, line 28
lmpTeLinkVerification, lmpTeLinkVerification,
lmpTeLinkFaultManagement, lmpTeLinkFaultManagement,
lmpTeLinkDwdm, lmpTeLinkDwdm,
lmpTeLinkOperStatus, lmpTeLinkOperStatus,
lmpTeLinkRowStatus, lmpTeLinkRowStatus,
lmpTeLinkStorageType, lmpTeLinkStorageType,
lmpTeLinkNotificationsEnabled lmpTeLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects which can be used to configure TE links." "Objects that can be used to configure TE links."
::= { lmpGroups 8 } ::= { lmpGroups 8 }
lmpDataLinkGroup OBJECT-GROUP lmpDataLinkGroup OBJECT-GROUP
OBJECTS { lmpDataLinkType, OBJECTS { lmpDataLinkType,
lmpDataLinkAddressType, lmpDataLinkAddressType,
lmpDataLinkIpAddr, lmpDataLinkIpAddr,
lmpDataLinkRemoteIpAddress, lmpDataLinkRemoteIpAddress,
lmpDataLinkRemoteIfId, lmpDataLinkRemoteIfId,
lmpDataLinkEncodingType, lmpDataLinkEncodingType,
lmpDataLinkActiveOperStatus, lmpDataLinkActiveOperStatus,
skipping to change at page 78, line 18 skipping to change at page 77, line 18
lmpTeLinkNotDegraded, lmpTeLinkNotDegraded,
lmpDataLinkVerificationFailure } lmpDataLinkVerificationFailure }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications defined in this module." "Set of notifications defined in this module."
::= { lmpGroups 10 } ::= { lmpGroups 10 }
-- End of LMP-MIB -- End of LMP-MIB
END END
10. Intellectual Property Considerations 10. Security Considerations
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
By submitting this Internet Draft, we certify that any applicable
patent or other IPR claims of which we are aware have been disclosed,
and any of which we become aware will be disclosed, in accordance
with RFC 3668.
11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with 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 environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
- Unauthorized changes to the lmpNbrTable, lmpControlChannelTable, - Unauthorized changes to the lmpNbrTable, lmpControlChannelTable,
lmpTeLinkTable and lmpDataLinkTable may disrupt allocation of lmpTeLinkTable, and lmpDataLinkTable may disrupt allocation of
resources in the network. resources in the network.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 79, line 45 skipping to change at page 78, line 18
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
12. Acknowledgments 11. Contributors
The general structure of this draft has been modeled around draft- Sudheer Dharanikota
ietf-mpls-lsr-mib-06.txt. EMail: sudheer@ieee.org
12. Acknowledgements
The general structure of this document has been modeled around the
MPLS Label Switching Router (LSR) MIB [RFC3813].
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. IANA Considerations 13. IANA Considerations
Each of the following "IANA Considerations" subsections requests IANA Each of the following "IANA Considerations" subsections requested
for a new assignment. New assignments can only be made via a IANA for new assignments. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
13.1. IANA Considerations for lmp ifType 13.1. IANA Considerations for lmp ifType
The IANA is requested to assign TBD ifType for LMP interfaces. The IANA has assigned 227 ifType for LMP interfaces.
13.2. IANA Considerations for LMP-MIB 13.2. IANA Considerations for LMP-MIB
LMP-MIB should be rooted under the transmission subtree. The IANA is The IANA has assigned { transmission 227 } to the LMP-MIB module
requested to assign { transmission TBD } to the LMP-MIB module specified in this document.
specified in this document. The IANA is requested to use same number
as the lmp ifType.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -
Revision 3", RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", RFC 2434, an IANA Considerations Section in RFCs", BCP 26, RFC
October 1998. 2434, October 1998.
[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, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Conformance "Structure of Management Information Version 2
Statements for SMIv2", STD 58, RFC 2580, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Group MIB", RFC 2863, June 2000. "Textual Conventions for SMIv2", STD 58, RFC 2579,
April 1999.
[RFC2914] Floyd, S., "Congestion Control Principles", RFC 2914, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
September 2000. "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Shoenwaelder, J., "Textual Conventions for Internet MIB", RFC 2863, June 2000.
Network Addresses", RFC 3291, May 2002.
[RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., [RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC
Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2914, September 2000.
Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, B.,
"Generalized MPLS Signaling Functional Description",
RFC 3471, January 2003.
[RFC3667] Bradner, S., "IETF Rights in Contributions", [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
RFC 3667, February 2004. (GMPLS) Signaling Functional Description", RFC 3471,
January 2003.
[RFC3668] Bradner, S., "Intellectual Property Rights in IETF [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Technology", RFC 3668, February 2004. Schoenwaelder, "Textual Conventions for Internet
Network Addresses", RFC 4001, February 2005.
[TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204,
"Traffic Engineering Link Management Information October 2005.
Base", Internet Draft
<draft-ietf-mpls-telink-mib-07.txt>, May 2004.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical
Rekhter, Y., Berger, L., Saha, S., Basak, D., Network (SONET)/Synchronous Digital Hierarchy (SDH)
Sandick, H., Zinin, A., Rajagopalan, B., and Encoding for Link Management Protocol (LMP) Test
Ramamoorthi, S., "Link Management Protocol", Messages", RFC 4207, October 2005.
Internet Draft <draft-ietf-ccamp-lmp-10.txt>,
October 2003.
[LMP-WDM] Fredette, A., Lang, J., "Link Management Protocol (LMP) [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management
for Dense Wavelength Division Multiplexing (DWDM) Protocol (LMP) for Dense Wavelength Division
Optical Line Systems", Internet Draft Multiplexing (DWDM) Optical Line Systems", RFC 4209,
<draft-ietf-ccamp-lmp-wdm-03.txt>, December 2003. October 2005.
[LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic
for Link Management (LMP) Test Messages", Internet Engineering Link Management Information Base", RFC
Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt>, 4220, November 2005.
December 2003.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Link Bundling in MPLS Traffic Engineering", "Multiprotocol Label Switching (MPLS) Traffic
Internet Draft <draft-ietf-mpls-bundle-04.txt>, Engineering (TE) Management Information Base (MIB)",
July 2002. RFC 3812, June 2004.
15. Authors' Addresses Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc
Email: dubuc.consulting@sympatico.ca Rincon Networks, Inc.
110 El Paseo
Santa Barbara, CA 93101
Email: jplang@ieee.org
Sudheer Dharanikota Evan McGinnis EMail: dubuc.consulting@sympatico.ca
Email: sudheer@ieee.org Calient Networks, Inc.
5853 Rue Ferrari
San Jose, CA 95138
Email: evan@calient.net
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 1414 Massachusetts Ave.
Chelmsford, MA 01824 Boxborough, MA 01719
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
16. Full Copyright Statement EMail: tnadeau@cisco.com
Copyright (C) The Internet Society (2004). This document is subject Jonathan P. Lang
to the rights, licenses and restrictions contained in BCP 78, and Sonos, Inc.
except as set forth therein, the authors retain all their rights. 223 E. De La Guerra St.
Santa Barbara, CA 93101
This document and translations of it may be copied and furnished to EMail: jplang@ieee.org
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Evan McGinnis
revoked by the Internet Society or its successors or assigns. This Hammerhead Systems
document and the information contained herein are provided on an "AS 640 Clyde Court
IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR Mountain View, CA 94043
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
EMail: emcginnis@hammerheadsystems.com
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 150 change blocks. 
378 lines changed or deleted 279 lines changed or added

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