draft-ietf-ccamp-rfc4327bis-01.txt   rfc4631.txt 
Network Working Group M. Dubuc Network Working Group M. Dubuc
Internet Draft T. Nadeau Request for Comments: 4631 T. Nadeau
Obsoletes RFC 4327 Cisco Systems Obsoletes: 4327 Cisco Systems
Category: Standard Track J. Lang Category: Standards Track J. Lang
Sonos, Inc. Sonos, Inc.
E. McGinnis E. McGinnis
Hammerhead Systems Hammerhead Systems
A. Farrel A. Farrel
Old Dog Consulting Old Dog Consulting
September 2006
February 2006
Link Management Protocol (LMP) Management Information Base (MIB) Link Management Protocol (LMP) Management Information Base (MIB)
draft-ietf-ccamp-rfc4327bis-01.txt
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any This document specifies an Internet standards track protocol for the
applicable patent or other IPR claims of which he or she is aware Internet community, and requests discussion and suggestions for
have been or will be disclosed, and any of which he or she becomes improvements. Please refer to the current edition of the "Internet
aware will be disclosed, in accordance with Section 6 of BCP 79. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are working documents of the Internet Engineering
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 and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document provides minor corrections to and obsoletes RFC 4327. This document provides minor corrections to and obsoletes RFC 4327.
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
skipping to change at page 2, line 18 skipping to change at page 2, line 18
2. Introduction ....................................................3 2. Introduction ....................................................3
3. Terminology .....................................................3 3. Terminology .....................................................3
4. Feature Checklist ...............................................4 4. Feature Checklist ...............................................4
5. Outline .........................................................4 5. Outline .........................................................4
6. Brief Description of MIB Objects ................................5 6. Brief Description of MIB Objects ................................5
6.1. lmpNbrTable ................................................5 6.1. lmpNbrTable ................................................5
6.2. lmpControlChannelTable .....................................5 6.2. lmpControlChannelTable .....................................5
6.3. lmpControlChannelPerfTable .................................5 6.3. lmpControlChannelPerfTable .................................5
6.4. lmpTeLinkTable .............................................5 6.4. lmpTeLinkTable .............................................5
6.5. lmpLinkVerificationTable ...................................5 6.5. lmpLinkVerificationTable ...................................5
6.6. lmpTeLinkPerfTable .........................................5 6.6. lmpTeLinkPerfTable .........................................6
6.7. lmpDataLinkTable ...........................................6 6.7. lmpDataLinkTable ...........................................6
6.8. lmpDataLinkPerfTable .......................................6 6.8. lmpDataLinkPerfTable .......................................6
7. Example of LMP Control Channel Setup ............................6 7. Example of LMP Control Channel Setup ............................6
8. Application of the Interfaces Group to LMP ......................9 8. Application of the Interfaces Group to LMP ......................9
8.1. Support of the LMP Layer by ifTable .......................10 8.1. Support of the LMP Layer by ifTable .......................10
9. LMP MIB Module Definitions .....................................12 9. LMP MIB Module Definitions .....................................11
10. Security Considerations .......................................76 10. Security Considerations .......................................78
11. Contributors ..................................................77 11. Contributors ..................................................79
12. Acknowledgements ..............................................77 12. Acknowledgements ..............................................79
13. IANA Considerations ...........................................77 13. IANA Considerations ...........................................79
13.1. IANA Considerations for lmp ifType .......................77 13.1. IANA Considerations for LMP ifType .......................79
13.2. IANA Considerations for LMP-MIB ..........................77 13.2. IANA Considerations for LMP-MIB ..........................79
14. Changes from RFC 4327 to RFC XXXX .............................78 14. Changes from RFC 4327 to RFC 4631 .............................79
15. References ....................................................78 15. References ....................................................80
15.1. Normative References .....................................78 15.1. Normative References .....................................80
15.2. Informative References ...................................79 15.2. Informative References ...................................81
16. Authors' Addresses ............................................79
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).
skipping to change at page 3, line 34 skipping to change at page 3, line 34
measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link
Management Protocol [RFC4204] are key components of this Management Protocol [RFC4204] are key components of this
standardization activity. The primary purpose of LMP is to manage standardization activity. The primary purpose of LMP is to manage
traffic engineering (TE) links. Primary goals of LMP are the traffic engineering (TE) links. Primary goals of LMP are the
maintenance of the control channel connectivity, correlation of link maintenance of the control channel connectivity, correlation of link
properties, verification of data-bearing links, and detection and properties, verification of data-bearing links, and detection and
isolation of link 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 [RFC2119]. document are to be interpreted as described in RFC 2119 [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 [RFC4204]. An "LMP adjacency" is formed between Management Protocol [RFC4204]. An "LMP adjacency" is formed between
two 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,
anytime an 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 [RFC4204] for distinction between port multiplexing capability (see [RFC4204] for the distinction between
and component link). port 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, optical capability on LMP-capable interfaces of a photonic switch, optical
cross-connect, or router. cross-connect, or router.
- The MIB module is used to provide information about LMP - The MIB module is used to provide information about LMP
adjacencies. adjacencies.
- Support is provided for configuration of the keep alive and link - Support is provided for configuration of the keep-alive and 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 on - Performance counters are provided for measuring LMP performance on
a per-control channel basis. Performance counters are also a per-control channel basis. Performance counters are also
provided for measuring LMP performance on the data-bearing links. provided for measuring LMP performance on the data-bearing links.
Note that the LMP MIB module goes hand-in-hand with the TE Link Note that the LMP MIB module goes hand-in-hand with the TE Link (TE-
(TE-LINK-STD-MIB) MIB module [RFC4220]. The TE link table, which is LINK-STD-MIB) MIB module [RFC4220]. The TE link table, which is used
used to associate data-bearing links to TE links, is defined in the to associate data-bearing links to TE links, is defined in the TE
TE Link MIB. The TE link table in the LMP MIB module contains TE Link MIB. The TE link table in the LMP MIB module contains TE link
link information specific to LMP. 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
were derived from the LMP document [RFC4204]. objects 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
skipping to change at page 6, line 17 skipping to change at page 6, line 23
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
objects described in section 9 to set up an LMP control channel. described in Section 9 to set up an LMP control channel. This
While this example is not meant to illustrate every nuance of the example is not meant to illustrate every nuance of the MIB module,
MIB module, it is intended as an aid to understanding some of the but it is intended as an aid to understanding some of the key
key concepts. It is meant to be read after going through the MIB concepts. It is meant to be read after one goes 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
three data-bearing links. We also assume that the data-bearing data-bearing links. We also assume that the data-bearing links are
links are ports (lambdas). We also assume that the link ports (lambdas) and that the link verification procedure is not
verification procedure is not enabled. The following example enabled. The following example illustrates which rows and
illustrates which rows and corresponding objects might be created corresponding objects might be created to accomplish this.
to accomplish this.
First, LMP must be enabled between the pair of nodes. First, LMP must be enabled between the pair of nodes.
In lmpNbrTable: In lmpNbrTable:
{ {
lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1 lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1
lmpNbrAdminStatus = up(1), lmpNbrAdminStatus = up(1),
lmpNbrRowStatus = createAndGo(4), lmpNbrRowStatus = createAndGo(4),
lmpNbrStorageType = nonVolatile(3) lmpNbrStorageType = nonVolatile(3)
} }
skipping to change at page 8, line 12 skipping to change at page 8, line 20
{ {
ifIndex = 44, ifIndex = 44,
lmpDataLinkAddressType = unknown(0), lmpDataLinkAddressType = unknown(0),
lmpDataLinkIpAddr = ''H, lmpDataLinkIpAddr = ''H,
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
not need to be provisioned as it is automatically populated by the to be provisioned, as it is automatically populated by the node. The
node. The definition of the protection role (primary or definition of the protection role (primary or secondary) for the
secondary) for the data-bearing links is stored in the data-bearing links is stored in the componentLinkTable of the TE Link
componentLinkTable of the TE Link MIB module [RFC4220]. 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
the ifTable. 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
is created in the LMP MIB module to specify TE link information created in the LMP MIB module to specify TE link information specific
specific to LMP. to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
ifIndex = 20, ifIndex = 20,
lmpTeLinkVerification = true(1), lmpTeLinkVerification = true(1),
lmpTeLinkFaultManagement = true(1), lmpTeLinkFaultManagement = true(1),
lmpTeLinkDwdm = false(2), lmpTeLinkDwdm = false(2),
lmpTeLinkRowStatus = createAndGo(4), lmpTeLinkRowStatus = createAndGo(4),
lmpTeLinkStorageType = nonVolatile(3) lmpTeLinkStorageType = nonVolatile(3)
} }
skipping to change at page 8, line 52 skipping to change at page 9, line 12
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 [RFC2863]. 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 the TE Link MIB module
[RFC4220]. [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 (1). In this lmpControlChannelEntry object lmpCcIsIf is set to true (1). 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
provide appropriate interface stacking as defined below. 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
in accordance with [RFC2863], which states that the interfaces table 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
interfaces and that each sub-layer below the internetwork layer of and that each sub-layer below the internetwork layer of a network
a network interface is considered an interface. Since the LMP interface is considered an interface. Since the LMP interface only
interface only carries control traffic, it is considered to be below carries control traffic, it is considered to be below the
the internetwork layer. Thus, the LMP interface may be represented internetwork layer. Thus, the LMP interface may be represented as an
as an entry in the ifTable. The interrelation of entries in the entry in the ifTable. The interrelation of entries in the ifTable is
ifTable is defined by Interfaces Stack Group defined in [RFC2863]. 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(227) + | 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
of any interface type over which the LMP interface will transmit any interface type over which the LMP interface will transmit its
its traffic. Note that if the underlying layer provides multiple traffic. Note that if the underlying layer provides multiple access
access to its media (i.e., Ethernet), then it is possible to stack to its media (i.e., Ethernet), then it is possible to stack multiple
multiple LMP interfaces on top of this interface in parallel. 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
simply exist as logical connections between adjacent LMP-capable exist as logical connections between adjacent LMP-capable nodes. In
nodes. In this case, lmpCcIsIf is set to false(2) and no this case, lmpCcIsIf is set to false(2), and no corresponding entry
corresponding entry is made in the ifTable. 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 227. ifType The value that is allocated for LMP is 227. This
This number has been assigned by the IANA. 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
the LMP layer. LMP layer.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus This variable indicates the administrator's intent ifAdminStatus This variable indicates the administrator's intent as
as to whether LMP should be enabled, disabled, or to whether LMP should be enabled, disabled, or running
running in some diagnostic testing mode on this in some diagnostic testing mode on this interface.
interface. Also see [RFC2863]. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational ifOperStatus This value reflects the actual or operational status of
status of LMP on this interface. LMP on this interface.
ifLastChange See [RFC2863]. ifLastChange See [RFC2863].
ifInOctets The number of received octets over the interface, ifInOctets The number of received octets over the interface; i.e.,
i.e., the number of octets received as LMP the number of octets received as LMP packets.
packets.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the interface;
interface, i.e., the number of octets transmitted i.e., the number of octets transmitted as LMP packets.
as LMP packets.
ifInErrors The number of LMP packets dropped due to ifInErrors The number of LMP packets dropped due to uncorrectable
uncorrectable errors. errors.
ifInUnknownProtos ifInUnknownProtos
The number of received packets discarded during The number of received packets discarded during packet
packet header validation, including packets with header validation, including packets with unrecognized
unrecognized label values. label values.
ifOutErrors See [RFC2863]. ifOutErrors See [RFC2863].
ifName Textual name (unique on this system) of the ifName Textual name (unique on this system) of the interface
interface or an octet string of zero length. or an octet string of zero length.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Default is disabled (2). Default is disabled (2).
ifConnectorPresent ifConnectorPresent
Set to false (2). Set to false (2).
ifHighSpeed See [RFC2863]. ifHighSpeed See [RFC2863].
ifHCInOctets The 64-bit version of ifInOctets; supported if ifHCInOctets The 64-bit version of ifInOctets; supported if required
required by the compliance statements in [RFC2863]. 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 nonvolatile '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], This MIB module IMPORTs objects from [RFC2578], [RFC2579], [RFC2580],
[RFC2863], [RFC4001], and [RFC4220], and it has REFERENCE clauses to [RFC2863], [RFC4001], and [RFC4220], and it has REFERENCE clauses to
[RFC4204], [RFC4207], [RFC4209], [RFC3471], and [RFC2914]. [RFC4204], [RFC4207], [RFC4209], [RFC3471], and [RFC2914].
skipping to change at page 12, line 35 skipping to change at page 12, line 16
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; -- RFC 4220 FROM TE-LINK-STD-MIB; -- RFC 4220
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200602190000Z" -- 19 February 2006 LAST-UPDATED "200608140000Z" -- 14 August 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
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
skipping to change at page 13, line 4 skipping to change at page 12, line 34
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: emcginnis@hammerheadsystems.com Email: emcginnis@hammerheadsystems.com
Adrian Farrel Adrian Farrel
Email: adrian@olddog.co.uk" Email: adrian@olddog.co.uk"
DESCRIPTION DESCRIPTION
"Copyright (C) 2006 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 4631; 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
"200602190000Z" -- 19 February 2006 "200608140000Z" -- 14 August 2006
DESCRIPTION DESCRIPTION
"Revised version to: "Revised version:
- fix textual descriptions of TruthValue settings such that True - Fixes textual descriptions of TruthValue settings such that
is always 1, and False is always 2. True is always 1 and False is always 2.
- add punctuation to REFERENCE clauses. - Adds punctuation to REFERENCE clauses.
This revision published as RFC XXXX" This revision published as RFC 4631"
REVISION REVISION
"200601110000Z" -- 11 January 2006 "200601110000Z" -- 11 January 2006
DESCRIPTION DESCRIPTION
"Initial version published as RFC 4327" "Initial version published as RFC 4327"
::= { transmission 227 } ::= { transmission 227 }
-- 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)
LmpRetransmitInterval ::= TEXTUAL-CONVENTION LmpRetransmitInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The retransmission interval delay in milliseconds." "The retransmission interval delay in milliseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
LmpNodeId ::= TEXTUAL-CONVENTION LmpNodeId ::= TEXTUAL-CONVENTION
skipping to change at page 15, line 35 skipping to change at page 15, line 18
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 that require is used for the retransmission of messages that require
acknowledgement. This object along with lmpNbrRetryLimit is acknowledgement. This object, along with lmpNbrRetryLimit,
used to implement congestion-handling mechanism as defined in is used to implement the congestion-handling mechanism defined
Section 10 of the Link Management Protocol specification, in 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 4204. "Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914." 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 the congestion-handling mechanism as defined
used to implement congestion-handling mechanism as defined in 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 4204. "Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914." 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 successive retransmission exponential backoff. The ratio of two successive retransmission
intervals is (1 + Delta)." intervals is (1 + Delta)."
REFERENCE REFERENCE
"Link Management Protocol, RFC 4204. "Link Management Protocol, RFC 4204.
Congestion Control Principles, RFC 2914." Congestion Control Principles, RFC 2914."
DEFVAL { 1 } DEFVAL { 1 }
::= { lmpNbrEntry 4 } ::= { lmpNbrEntry 4 }
skipping to change at page 17, line 31 skipping to change at page 17, line 18
-- End of lmpNbrTable -- End of lmpNbrTable
lmpCcHelloIntervalDefault OBJECT-TYPE lmpCcHelloIntervalDefault OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default value for the HelloInterval "This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It parameter used in the Hello protocol keep-alive phase. It
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 as 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 4204." "Link Management Protocol, RFC 4204."
::= { 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
skipping to change at page 19, line 20 skipping to change at page 19, line 10
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies LMP control channel information." "This table specifies LMP control channel information."
::= { lmpObjects 10 } ::= { lmpObjects 10 }
lmpControlChannelEntry OBJECT-TYPE lmpControlChannelEntry OBJECT-TYPE
SYNTAX LmpControlChannelEntry SYNTAX LmpControlChannelEntry
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 control channel. Whenever a new entry is created with every control channel. Whenever a new entry is created with
lmpCcIsIf set to true(1), then a corresponding entry is lmpCcIsIf set to true(1), a corresponding entry is
created in ifTable as well (see RFC 2863)." created in ifTable as well (see RFC 2863)."
INDEX { lmpCcId } INDEX { lmpCcId }
::= { lmpControlChannelTable 1 } ::= { lmpControlChannelTable 1 }
LmpControlChannelEntry ::= SEQUENCE { LmpControlChannelEntry ::= SEQUENCE {
lmpCcId Unsigned32, lmpCcId Unsigned32,
lmpCcUnderlyingIfIndex InterfaceIndexOrZero, lmpCcUnderlyingIfIndex InterfaceIndexOrZero,
lmpCcIsIf TruthValue, lmpCcIsIf TruthValue,
lmpCcNbrNodeId LmpNodeId, lmpCcNbrNodeId LmpNodeId,
lmpCcRemoteId Unsigned32, lmpCcRemoteId Unsigned32,
skipping to change at page 20, line 22 skipping to change at page 20, line 10
::= { 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.
If this object is set to zero, but lmpCcIsIf is set to If this object is set to zero but lmpCcIsIf is set to
true(1), the control channel is not currently associated true(1), the control channel is not currently associated
with any underlying interface and the control channel's with any underlying interface, and the control channel's
operational status must not be up(1), nor should the operational status must not be up(1); nor should the
control channel forward or receive traffic. control channel forward or receive traffic.
If lmpCcIsIf is set to false(2), this object should be set If lmpCcIsIf is set to false(2), this object should be set
to zero and should be ignored." to zero and ignored."
::= { lmpControlChannelEntry 2 } ::= { lmpControlChannelEntry 2 }
lmpCcIsIf OBJECT-TYPE lmpCcIsIf OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In implementations where the control channels are modeled "In implementations where the control channels are modeled
as interfaces, the value of this object is true(1) and as interfaces, the value of this object is true(1), and
this control channel is represented by an interface in this control channel is represented by an interface in
the interfaces group table as indicated by the value of the interfaces group table as indicated by the value of
lmpCcUnderlyingIfIndex. If control channels are not lmpCcUnderlyingIfIndex. If control channels are not
modeled as interfaces, the value of this object is modeled as interfaces, the value of this object is
false(2) and there is no corresponding interface for false(2), and there is no corresponding interface for
this control channel in the interfaces group table, this control channel in the interfaces group table;
and the value of lmpCcUnderlyingIfIndex should be 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 either is configured or gets created by the node This value either is configured or gets created by the node
skipping to change at page 21, line 16 skipping to change at page 21, line 7
::= { 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 learned."
::= { 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
type. In point-to-point configuration, this value can be set type. In point-to-point configuration, this value can be set
to unknown(0)." to unknown(0)."
::= { 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 The 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
skipping to change at page 36, line 24 skipping to change at page 36, line 39
"This object counts the number of ChannelStatusResponse messages "This object counts the number of ChannelStatusResponse messages
that have been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 52 } ::= { lmpControlChannelPerfEntry 52 }
lmpCcCounterDiscontinuityTime OBJECT-TYPE lmpCcCounterDiscontinuityTime 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 control channel's counters suffered a one or more of this control channel's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this control channel of any instances associated with this control channel of any
Counter32 object contained in the lmpControlChannelPerfTable. Counter32 object contained in the lmpControlChannelPerfTable.
If no such discontinuities have occurred since the last re- If no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpControlChannelPerfEntry 53 } ::= { lmpControlChannelPerfEntry 53 }
-- End of lmpControlChannelPerfTable -- End of lmpControlChannelPerfTable
skipping to change at page 37, line 13 skipping to change at page 37, line 31
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 created. If a TE link entry in the ifTable is destroyed, then
so 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 start link verification on the TE link. Information about the
TE link that is not LMP specific is contained in teLinkTable of TE link that is not LMP specific is contained in the
the TE-LINK-STD-MIB MIB module." teLinkTable of 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 the control channel parameter negotiation
phase (in the Config message). Node ID is an address whose 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 whether the LMP link verification
is enabled for this TE link." procedure is enabled for this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC 4204." "Link Management Protocol, RFC 4204."
::= { 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 whether the LMP fault management procedure
is enabled on this TE link." is enabled on this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC 4204." "Link Management Protocol, RFC 4204."
::= { 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 whether 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 4209." Multiplexing (DWDM) Optical Line Systems, RFC 4209."
::= { 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 is 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 that at least one
data-bearing link 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
skipping to change at page 41, line 24 skipping to change at page 41, line 47
Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Hierarchy (SDH) Encoding for Link Management Protocol (LMP)
Test Messages, RFC 4207." Test Messages, RFC 4207."
::= { 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(1) for this object indicates that the "A value of true(1) 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
this TE link are verified." this TE link are verified."
::= { lmpLinkVerificationEntry 4 } ::= { lmpLinkVerificationEntry 4 }
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
skipping to change at page 51, line 11 skipping to change at page 51, line 49
"This object counts the number of ChannelStatusResponse messages "This object counts the number of ChannelStatusResponse messages
that have been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 39 } ::= { lmpTeLinkPerfEntry 39 }
lmpTeCounterDiscontinuityTime OBJECT-TYPE lmpTeCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this TE link's counters suffered a one or more of this TE link's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this TE link of any Counter32 instances associated with this TE link of any Counter32
object contained in the lmpTeLinkPerfTable. If object contained in the lmpTeLinkPerfTable. If
no such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpTeLinkPerfEntry 40 } ::= { lmpTeLinkPerfEntry 40 }
-- End of lmpTeLinkPerfTable -- End of lmpTeLinkPerfTable
skipping to change at page 52, line 22 skipping to change at page 53, line 16
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 links are multiplex
capable, whereas ports are not multiplex capable." capable, whereas ports are not multiplex capable."
REFERENCE REFERENCE
"Link Management Protocol, RFC 4204." "Link Management Protocol, RFC 4204."
::= { 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
skipping to change at page 52, line 50 skipping to change at page 53, line 44
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; 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; the
lmpDataLinkRemoteIfId object then identifies the unnumbered lmpDataLinkRemoteIfId object then identifies the unnumbered
address. address.
This information is either configured manually or 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
skipping to change at page 56, line 49 skipping to change at page 57, line 49
"This object counts the number of data-bearing link tests "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 one or more of this data-bearing link's counters suffered
a discontinuity. The relevant counters are the specific a discontinuity. The relevant counters are the specific
instances associated with this data-bearing link of any instances associated with this data-bearing link of any
Counter32 object contained in the lmpDataLinkPerfTable. If Counter32 object contained in the lmpDataLinkPerfTable. If
no such discontinuities have occurred since the last re- no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpDataLinkPerfEntry 7 } ::= { lmpDataLinkPerfEntry 7 }
-- End of lmpDataLinkPerfTable -- End of lmpDataLinkPerfTable
skipping to change at page 57, line 20 skipping to change at page 58, line 22
lmpNotificationMaxRate OBJECT-TYPE lmpNotificationMaxRate OBJECT-TYPE
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 this MIB was designed, care was 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 that the
notifications are sent only 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 that 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, where 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 negligible 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
emit these notifications during that period, or may emit these notifications during that period or may
queue them until an appropriate time. A value of 0 queue them until an appropriate time. A value of 0
means no throttling is applied and events may be means that no throttling is applied and events may be
notified at the rate at which they occur. notified at the rate at which they occur.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
::= { lmpObjects 18 } ::= { lmpObjects 18 }
lmpLinkPropertyNotificationsEnabled OBJECT-TYPE lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the "If this object is true(1), then it enables the
skipping to change at page 58, line 16 skipping to change at page 59, line 19
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
::= { lmpObjects 18 } ::= { lmpObjects 18 }
lmpLinkPropertyNotificationsEnabled OBJECT-TYPE lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the "If this object is true(1), then it enables the
generation of lmpTeLinkPropertyMismatch generation of lmpTeLinkPropertyMismatch
and lmpDataLinkPropertyMismatch notifications, and lmpDataLinkPropertyMismatch notifications;
otherwise these notifications are not emitted. otherwise, these notifications are not emitted.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 19 } ::= { lmpObjects 19 }
lmpUnprotectedNotificationsEnabled OBJECT-TYPE lmpUnprotectedNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the "If this object is true(1), then it enables the
generation of lmpUnprotected notifications, generation of lmpUnprotected notifications;
otherwise these notifications are not emitted. otherwise, these notifications are not emitted.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 20 } ::= { lmpObjects 20 }
lmpCcUpDownNotificationsEnabled OBJECT-TYPE lmpCcUpDownNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the generation of "If this object is true(1), then it enables the generation of
lmpControlChannelUp and lmpControlChannelDown notifications, lmpControlChannelUp and lmpControlChannelDown notifications;
otherwise these notifications are not emitted. otherwise, these notifications are not emitted.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 21 } ::= { lmpObjects 21 }
lmpTeLinkNotificationsEnabled OBJECT-TYPE lmpTeLinkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the "If this object is true(1), then it enables the
generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
notifications, otherwise these notifications are not emitted. notifications; otherwise, these notifications are not emitted.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 22 } ::= { lmpObjects 22 }
lmpDataLinkNotificationsEnabled OBJECT-TYPE lmpDataLinkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true(1), then it enables the "If this object is true(1), then it enables the
generation of lmpDataLinkVerificationFailure generation of lmpDataLinkVerificationFailure
notification, otherwise these notifications are not emitted. notification; otherwise, these notifications are not emitted.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 23 } ::= { lmpObjects 23 }
-- Notifications -- Notifications
-- Link Property Mismatch Notifications -- Link Property Mismatch Notifications
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { teLinkRemoteIpAddr, OBJECTS { teLinkRemoteIpAddr,
teLinkIncomingIfId } teLinkIncomingIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a TE link property "This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link mismatch is detected on the node. The received remote TE link
ID of the misconfigured TE link is represented by either ID of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether teLinkRemoteIpAddr or teLinkIncomingIfId, depending on whether
the TE link is numbered or unnumbered. This notification the TE link is numbered or unnumbered. This notification
should not be sent unless lmpLinkPropertyNotificationsEnabled should not be sent unless lmpLinkPropertyNotificationsEnabled
is true(1). It is recommended that this notification be reported is true(1). It is recommended that this notification be
only the first time a mismatch is detected. Otherwise, for a reported only the first time a mismatch is detected.
given TE link, this notification can occur no more than once Otherwise, for a given TE link, this notification can occur
per verification interval (lmpGlobalLinkVerificationInterval)." no more than once 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(1). It is lmpLinkPropertyNotificationsEnabled is true(1). 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
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpCcNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when there are more than one "This notification is generated when there is more than one
control channels between LMP neighbors and the last redundant control channel between LMP neighbors and the last redundant
control channel has failed. If the remaining operational control channel has failed. If the remaining operational
control channel fails, then there will be no more control control channel fails, then there will be no more control
channels between the pair of nodes and all the TE links channels between the pair of nodes and all the TE links
between the pair of nodes will go to degraded state. This between the pair of nodes, will go to degraded state. This
notification should not be sent unless notification should not be sent unless
lmpUnprotectedNotificationsEnabled is set to true(1)." lmpUnprotectedNotificationsEnabled is set to true(1)."
::= { lmpNotifications 3 } ::= { lmpNotifications 3 }
-- Control Channel Notifications -- Control Channel Notifications
lmpControlChannelUp NOTIFICATION-TYPE lmpControlChannelUp NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 62, line 23 skipping to change at page 63, line 31
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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 constraint applies:
lmpCcIsIf must at least be read-only returning false(2)." lmpCcIsIf must at least be read-only, returning false(2)."
GROUP lmpCcIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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 constraint applies:
lmpCcIsIf must at least be read-only returning true(1)." lmpCcIsIf must at least be read-only, returning true(1)."
GROUP lmpLinkVerificationGroup GROUP lmpLinkVerificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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."
skipping to change at page 63, line 28 skipping to change at page 64, line 35
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) }
DESCRIPTION DESCRIPTION
"Support for notReady(3) and createAndWait(5) is "Support for notReady(3) and createAndWait(5) is
not required." not required."
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), or
goingDown(6) need not be supported." goingDown(6) need not be supported."
-- lmpTeLinkTable -- lmpTeLinkTable
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
skipping to change at page 64, line 42 skipping to change at page 65, line 48
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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 constraint applies:
lmpCcIsIf must at least be read-only returning false(2)." lmpCcIsIf must at least be read-only, returning false(2)."
GROUP lmpCcIsInterfaceGroup GROUP lmpCcIsInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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 constraint applies:
lmpCcIsIf must at least be read-only returning true(1)." lmpCcIsIf must at least be read-only, returning true(1)."
GROUP lmpLinkVerificationGroup GROUP lmpLinkVerificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices that 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
skipping to change at page 68, line 4 skipping to change at page 69, line 17
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), or
goingDown(6) need not be supported." goingDown(6) need not be supported."
OBJECT lmpCcStorageType OBJECT lmpCcStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpLinkVerificationTable -- lmpLinkVerificationTable
OBJECT lmpLinkVerifyInterval OBJECT lmpLinkVerifyInterval
skipping to change at page 70, line 4 skipping to change at page 71, line 23
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkAddressType OBJECT lmpDataLinkAddressType
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 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 "The size of the data-bearing link IP address depends on
of data-bearing link. Data-bearing link IP address size the type of data-bearing link. Data-bearing link IP
is zero if link is unnumbered, four if link IP address is address size is zero if the link is unnumbered, four if
IPv4, and sixteen if link IP address is IPv6." the link IP address is IPv4, and sixteen if the 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 76, line 37 skipping to change at page 78, line 27
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:
- The lmpNbrTable exposes network provider's node IP addresses. - The lmpNbrTable exposes the network provider's node IP addresses.
- lmpControlChannelTable exposes network provider's control - lmpControlChannelTable exposes the network provider's control
network. network.
- lmpDataLinkTable exposes network provider's data network. - lmpDataLinkTable exposes the network provider's data network.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
skipping to change at page 77, line 37 skipping to change at page 79, line 30
Bert Wijnen for document review. Bert Wijnen for document review.
13. IANA Considerations 13. IANA Considerations
No new IANA actions are requested in this document. All IANA actions No new IANA actions are requested in this document. All IANA actions
from RFC 4327 still hold and are reproduced here for information. from RFC 4327 still hold and are reproduced here for information.
Note that new assignments can only be made via a Standards Action as Note that new assignments can only be made via a Standards Action as
specified in [RFC2434]. specified in [RFC2434].
13.1. IANA Considerations for lmp ifType 13.1. IANA Considerations for LMP ifType
The IANA has assigned 227 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
The IANA has assigned { transmission 227 } to the LMP-MIB module The IANA has assigned { transmission 227 } to the LMP-MIB module
specified in this document. specified in this document.
14. Changes from RFC 4327 to RFC XXXX 14. Changes from RFC 4327 to RFC 4631
The following changes have been made relative to RFC 4327. The following changes have been made relative to RFC 4327.
a. Show that this document obsoletes RFC 4327. a. Show that this document obsoletes RFC 4327.
b. Indicate in Abstract that this document provides minor corrections b. Indicate in Abstract that this document provides minor
to RFC 4327. corrections to RFC 4327.
c. Correct use of TruthValue settings such that True is always 1, and c. Correct use of TruthValue settings such that True is always 1,
False is always 2. and False is always 2.
d. Update to acknowledgements section. d. Update to acknowledgements section.
e. Note in IANA section to show no further action required. e. Note in IANA section to show no further action required.
f. Remove identification of RFC 4327 and request RFC Editor to insert f. Remove identification of RFC 4327 and request RFC Editor to
new RFC number. insert new RFC number.
g. Update timestamps. g. Update timestamps.
h. Update author information. h. Update author information.
i. Added punctuation to REFERENCE clauses. i. Added punctuation to REFERENCE clauses.
j. Update Revision History clause. j. Update Revision History clause.
k. Add this section. k. Add this section.
l. Remove square braces from references to external documents from l. Remove square braces from references to external documents from
within the MIB module itself. within the MIB module itself.
m. Minor editorial corrections to text and DESCRIPTIONS clauses.
15. References 15. References
15.1. Normative References 15.1. Normative References
[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. and H. Alvestrand, "Guidelines for Writing [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
an IANA Considerations Section in RFCs", BCP 26, RFC IANA Considerations Section in RFCs", BCP 26, RFC 2434,
2434, October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Structure of Management Information Version 2 Rose, M., and S. Waldbusser, "Structure of Management
(SMIv2)", STD 58, RFC 2578, April 1999. Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Textual Conventions for SMIv2", STD 58, RFC 2579, Rose, M., and S. Waldbusser, "Textual Conventions for
April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Conformance Statements for SMIv2", STD 58, RFC 2580, Rose, M., and S. Waldbusser, "Conformance Statements for
April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC [RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC
2914, September 2000. 2914, September 2000.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Schoenwaelder, "Textual Conventions for Internet Network
Network Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204, [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204,
October 2005. October 2005.
[RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical [RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical
Network (SONET)/Synchronous Digital Hierarchy (SDH) Network (SONET)/Synchronous Digital Hierarchy (SDH)
Encoding for Link Management Protocol (LMP) Test Encoding for Link Management Protocol (LMP) Test
Messages", RFC 4207, October 2005. Messages", RFC 4207, October 2005.
[RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management [RFC4209] Fredette, A. and J. Lang, "Link Management Protocol (LMP)
Protocol (LMP) for Dense Wavelength Division for Dense Wavelength Division Multiplexing (DWDM) Optical
Multiplexing (DWDM) Optical Line Systems", RFC 4209, Line Systems", RFC 4209, October 2005.
October 2005.
[RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering
Engineering Link Management Information Base", RFC Link Management Information Base", RFC 4220, November
4220, November 2005. 2005.
15.2. Informative References 15.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-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Label Switching
Engineering (TE) Management Information Base (MIB)", Router (LSR) Management Information Base (MIB)", RFC 3813,
RFC 3812, June 2004. June 2004.
16. Authors' Addresses Authors' Addresses
Martin Dubuc Martin Dubuc
EMail: dubuc.consulting@sympatico.ca EMail: dubuc.consulting@sympatico.ca
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
EMail: tnadeau@cisco.com EMail: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Sonos, Inc. Sonos, Inc.
223 E. De La Guerra St. 223 E. De La Guerra St.
skipping to change at page 80, line 28 skipping to change at page 82, line 35
Evan McGinnis Evan McGinnis
Hammerhead Systems Hammerhead Systems
640 Clyde Court 640 Clyde Court
Mountain View, CA 94043 Mountain View, CA 94043
EMail: emcginnis@hammerheadsystems.com EMail: emcginnis@hammerheadsystems.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk EMail: adrian@olddog.co.uk
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 116 change blocks. 
252 lines changed or deleted 236 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/