draft-ietf-ccamp-lmp-mib-06.txt   draft-ietf-ccamp-lmp-mib-07.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Internet Draft
Category: Standards Track Sudheer Dharanikota Category: Standards Track Sudheer Dharanikota
Expires: October 2003 Avici Systems Expires: March 2004
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
May 2003 October 2003
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-06.txt draft-ietf-ccamp-lmp-mib-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 9 skipping to change at page 2, line 8
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Link In particular, it describes managed objects for modeling the Link
Management Protocol (LMP). Management Protocol (LMP).
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 5 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4
6.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4
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 . . . . . . . . . . . . . . . . . . . . . . 5
6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5 6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5
6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 6 6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5
7. Example of LMP Control Channel Interface Setup . . . . . . . . . 6 7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5
8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8 8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8
8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9 8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9
9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11 9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11
10. Intellectual Property Considerations . . . . . . . . . . . . . . 74 10. Intellectual Property Considerations . . . . . . . . . . . . . . 76
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 74 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 76
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 75 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 75
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 75 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 78
13.2 Informative References . . . . . . . . . . . . . . . . . . . . 76 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 79
14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 79
15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 77 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Introduction 2. Introduction
Current work is underway in the IETF to specify a suite of protocols Current work is underway in the IETF to specify a suite of protocols
to be used as a common control plane and a separate common measure- to be used as a common control plane and a separate common
ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link measurement plane. Along with Generalized MPLS (GMPLS) [RFC3471], the
Management Protocol [LMP], which primary purpose is to manage traffic Link Management Protocol [LMP], which primary purpose is to manage
engineering (TE) links, is one of the key components of this stan- traffic engineering (TE) links, is one of the key components of this
dardization activity. Primary goals of LMP are the maintenance of the standardization activity. Primary goals of LMP are the maintenance of
control channel connectivity, correlation of link properties, verifi- the control channel connectivity, correlation of link properties,
cation of data-bearing links and detection and isolation of link verification of data-bearing links and detection and isolation of
faults. link faults.
We describe in this document a MIB module that can be used to manage We describe in this document a MIB module that can be used to manage
LMP implementations. This MIB module covers both configuration and LMP implementations. This MIB module covers both configuration and
performance monitoring aspects of LMP. performance monitoring aspects of LMP.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference document are to be interpreted as described in RFC 2119, reference
[RFC2119]. [RFC2119].
3. Terminology 3. Terminology
This document uses terminology from the document describing the Link This document uses terminology from the document describing the Link
Management Protocol [LMP]. An "LMP adjacency" is formed between two Management Protocol [LMP]. An "LMP adjacency" is formed between two
nodes that support the same capabilities, and LMP messages are nodes that support the same capabilities, and LMP messages are
exchanged between the node pair over control channels that form this exchanged between the node pair over control channels that form this
adjacency. Several control channels can be active at the same time. adjacency. Several control channels can be active at the same time.
With the exception of messages related to control channel management, With the exception of messages related to control channel management,
any time a LMP message needs to be transferred to a neighbor node, it any time a LMP message needs to be transferred to a neighbor node, it
can be sent on any of the active control channels. The control chan- can be sent on any of the active control channels. The control
nels can also be used to exchange MPLS control plane information or channels can also be used to exchange MPLS control plane information
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 multiplex- can be either component links or ports depending on their
ing capability (see [LMP] for distinction between port and component multiplexing capability (see [LMP] for distinction between port and
link). 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 sat- The Link Management Protocol MIB module (LMP-MIB) is designed to
isfy the following requirements and constraints: satisfy the following requirements and constraints:
- The MIB module supports the enabling and disabling of LMP - The MIB module supports the enabling and disabling of LMP
capability on LMP capable interfaces of a photonic switch, capability on LMP capable interfaces of a photonic switch,
optical cross-connect or router. optical cross-connect or router.
- The MIB module is used provide information about LMP adjacencies. - The MIB module is used provide information about LMP adjacencies.
- Support is provided for configuration of the keep alive and - Support is provided for configuration of the keep alive and
link verification parameters. link verification parameters.
skipping to change at page 4, line 31 skipping to change at page 4, line 23
for port or component link. for port or component link.
- Performance counters are provided for measuring LMP - Performance counters are provided for measuring LMP
performance on a per-control channel basis. Performance counters performance on a per-control channel basis. Performance counters
are also provided for measuring LMP performance on the data- are also provided for measuring LMP performance on the data-
bearing links. bearing links.
Note that the LMP MIB module goes hand-in-hand with the TE Link MIB Note that the LMP MIB module goes hand-in-hand with the TE Link MIB
module [TELINK-MIB]. The TE link table, which is used to associate module [TELINK-MIB]. The TE link table, which is used to associate
data-bearing links to TE links, is defined in the TE Link MIB. The TE data-bearing links to TE links, is defined in the TE Link MIB. The TE
link table in the LMP MIB module contains TE link information spe- link table in the LMP MIB module contains TE link information
cific to LMP. 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.
skipping to change at page 5, line 24 skipping to change at page 5, line 14
6.2. lmpControlChannelTable 6.2. lmpControlChannelTable
The control channel table is used for enabling the LMP protocol on The control channel table is used for enabling the LMP protocol on
LMP-capable interfaces. A photonic switch, optical cross-connect or LMP-capable interfaces. A photonic switch, optical cross-connect or
router creates an entry in this table for every LMP capable interface router creates an entry in this table for every LMP capable interface
in that device. in that device.
6.3. lmpControlChannelPerfTable 6.3. lmpControlChannelPerfTable
The control channel performance table is used for collecting LMP per- The control channel performance table is used for collecting LMP
formance counts on a per-control channel basis. This table is an AUG- performance counts on a per-control channel basis. This table is an
MENT to the lmpControlChannelTable. AUGMENT to the lmpControlChannelTable.
6.4. lmpTeLinkTable 6.4. lmpTeLinkTable
The TE link table is used for specifying LMP information associated The TE link table is used for specifying LMP information associated
with TE links. with TE links.
6.5. lmpLinkVerificationTable 6.5. lmpLinkVerificationTable
The link verification table is used for configuring the LMP link ver- The link verification table is used for configuring the LMP link
ification parameters of TE links. This table is an AUGMENT to the verification parameters of TE links. This table is an AUGMENT to the
lmpTeLinkTable. lmpTeLinkTable.
6.6. lmpTeLinkPerfTable 6.6. lmpTeLinkPerfTable
The TE link performance table is used for collecting LMP performance The TE link performance table is used for collecting LMP performance
counts on a per-TE link basis. This table is an AUGMENT to the counts on a per-TE link basis. This table is an AUGMENT to the
lmpTeLinkTable. lmpTeLinkTable.
6.7. lmpDataLinkTable 6.7. lmpDataLinkTable
skipping to change at page 7, line 32 skipping to change at page 7, line 19
lmpCcStorageType = nonVolatile(3) lmpCcStorageType = nonVolatile(3)
} }
Next, the three data-bearing links are created. For each data- Next, the three data-bearing links are created. For each data-
bearing link, an ifEntry with the same ifIndex needs to be created bearing link, an ifEntry with the same ifIndex needs to be created
beforehand. beforehand.
In lmpDataLinkTable: In lmpDataLinkTable:
{ {
ifIndex = 41, ifIndex = 41,
lmpDataLinkAddressType = unnumbered(1), lmpDataLinkAddressType = unknown(0),
lmpDataLinkIpAddr = ''H, lmpDataLinkIpAddr = ''H,
lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 47, lmpDataLinkRemoteIfId = 47,
lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3) lmpDataLinkStorageType = nonVolatile(3)
} }
{ {
ifIndex = 43, ifIndex = 43,
lmpDataLinkAddressType = unnumbered(1), lmpDataLinkAddressType = unknown(0),
lmpDataLinkIpAddr = ''H, lmpDataLinkIpAddr = ''H,
lmpDataLinkRemoteIpAddress = ''H, lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 42, lmpDataLinkRemoteIfId = 42,
lmpDataLinkRowStatus = createAndGo(4), lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3) lmpDataLinkStorageType = nonVolatile(3)
} }
{ {
ifIndex = 44, ifIndex = 44,
lmpDataLinkAddressType = unnumbered(1), 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 to be provisioned as it is automatically populated by the not need to be provisioned as it is automatically populated by the
node. The definition of the protection role (primary or node. The definition of the protection role (primary or
skipping to change at page 8, line 31 skipping to change at page 8, line 18
Once the TE link is created in the ifTable, a TE link entry Once the TE link is created in the ifTable, a TE link entry
is created in the LMP MIB module to specify TE link information is created in the LMP MIB module to specify TE link information
specific to LMP. specific to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
ifIndex = 20, ifIndex = 20,
lmpTeLinkVerification = true(2), lmpTeLinkVerification = true(2),
lmpTeLinkFaultManagement = true(2), lmpTeLinkFaultManagement = true(2),
lmpTeLinkDwdm = false(1), lmpTeLinkDwdm = false(1),
lmpTeLinkBitRate = 100000,
lmpTeLinkWavelength = 0,
lmpTeLinkRowStatus = createAndGo(4), lmpTeLinkRowStatus = createAndGo(4),
lmpTeLinkStorageType = nonVolatile(3) lmpTeLinkStorageType = nonVolatile(3)
} }
and in lmpVerifyTable:
{
lmpVerifyInterval = 100,
lmpVerifyDeadInterval = 300,
lmpVerifyTransportMechanism = 1, -- j016OverheadBytes
lmpVerifyAllLinks = verifyAllLinks(1)
lmpVerifyTransmissionRate = 100000,
lmpVerifyWavelength = 0
}
The association between the data-bearing links and the TE links is The association between the data-bearing links and the TE links is
stored in the ifStackTable [IF-MIB]. stored in the ifStackTable [IF-MIB].
In parallel with the entry created in the lmpTeLinkTable, an entry In parallel with the entry created in the lmpTeLinkTable, an entry
may be created in the teLinkTable of TE Link MIB module may be created in the teLinkTable of TE Link MIB module
[TELINK-MIB]. [TELINK-MIB].
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
skipping to change at page 11, line 15 skipping to change at page 11, line 11
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [RFC2863]. See [RFC2863].
9. LMP MIB Module Definitions 9. LMP MIB Module Definitions
LMP-MIB DEFINITIONS ::= BEGIN LMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
mib-2, Unsigned32, Counter32, TimeTicks transmission, Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
TimeStamp TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; FROM TE-LINK-STD-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200305211200Z" -- 21 May 2003 12:00:00 EST LAST-UPDATED "200310011200Z" -- 1 October 2003 12:00:00 EST
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@rogers.com
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@avici.com Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Email: jplang@ieee.org Email: jplang@ieee.org
Evan McGinnis Evan McGinnis
Email: evan@calient.net" Email: evan@calient.net"
skipping to change at page 12, line 17 skipping to change at page 12, line 13
"Copyright (C) 2003 The Internet Society. This version of "Copyright (C) 2003 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC XXXX; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200305211200Z" -- 21 May 2003 12:00:00 EST "200310011200Z" -- 1 October 2003 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC xxxx (to be assigned by RFC
Editor)" Editor)"
::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can ::= { transmission xxx } -- To be assigned by IANA.
-- be used in the interim) -- Request to assign same number as LMP
-- ifType.
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
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
DISPLAY-HINT "1d.1d.1d.1d"
STATUS current
DESCRIPTION
"Represents a Node ID in network byte order."
REFERENCE
"Section 1.1 of Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
SYNTAX OCTET STRING(SIZE(4))
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications -- Notifications
lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 }
-- Tables, Scalars -- Tables, Scalars
lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 }
-- Conformance -- Conformance
lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 }
lmpAdminStatus OBJECT-TYPE lmpAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP on the node." "The desired operational status of LMP on the node.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
DEFVAL { up } DEFVAL { up }
::= { lmpObjects 1 } ::= { lmpObjects 1 }
lmpOperStatus OBJECT-TYPE lmpOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of LMP on the node." "The actual operational status of LMP on the node."
::= { lmpObjects 2 } ::= { lmpObjects 2 }
skipping to change at page 13, line 44 skipping to change at page 14, line 6
SYNTAX LmpNbrEntry SYNTAX LmpNbrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every pair of nodes that can establish control channels." every pair of nodes that can establish control channels."
INDEX { lmpNbrNodeId } INDEX { lmpNbrNodeId }
::= { lmpNbrTable 1 } ::= { lmpNbrTable 1 }
LmpNbrEntry ::= SEQUENCE { LmpNbrEntry ::= SEQUENCE {
lmpNbrNodeId InetAddress, lmpNbrNodeId LmpNodeId,
lmpNbrRetransmitInterval LmpRetransmitInterval, lmpNbrRetransmitInterval LmpRetransmitInterval,
lmpNbrRetryLimit Unsigned32, lmpNbrRetryLimit Unsigned32,
lmpNbrRetransmitDelta Unsigned32, lmpNbrRetransmitDelta Unsigned32,
lmpNbrAdminStatus INTEGER, lmpNbrAdminStatus INTEGER,
lmpNbrOperStatus INTEGER, lmpNbrOperStatus INTEGER,
lmpNbrRowStatus RowStatus, lmpNbrRowStatus RowStatus,
lmpNbrStorageType StorageType lmpNbrStorageType StorageType
} }
lmpNbrNodeId OBJECT-TYPE lmpNbrNodeId OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX LmpNodeId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a unique index for an entry in the LmpNbrTable. "This is a unique index for an entry in the LmpNbrTable.
This value represents the remote Node ID. The Node ID This value represents the remote Node ID."
address type must be IPv4."
::= { lmpNbrEntry 1 } ::= { lmpNbrEntry 1 }
lmpNbrRetransmitInterval OBJECT-TYPE lmpNbrRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial retransmission interval that "This object specifies the initial retransmission interval that
is used for the retransmission of messages which require is used for the retransmission of messages which require
acknowledgement." acknowledgement. This object along with lmpNbrRetryLimit is
used to implement congestion handling mechanism as defined in
Section 10 of the Link Management Protocol specification,
which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 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
used to implement congestion handling mechanism as defined in
Section 10 of the Link Management Protocol specification,
which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 3 } DEFVAL { 3 }
::= { lmpNbrEntry 7 } ::= { lmpNbrEntry 7 }
lmpNbrRetransmitDelta OBJECT-TYPE lmpNbrRetransmitDelta OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 15, line 34 skipping to change at page 15, line 49
DESCRIPTION DESCRIPTION
"The actual operational status of LMP to this remote node." "The actual operational status of LMP to this remote node."
::= { lmpNbrEntry 4 } ::= { lmpNbrEntry 4 }
lmpNbrRowStatus OBJECT-TYPE lmpNbrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. None of the writable objects
can only be changed when lmpNbrRowStatus is active." in a row can be changed if the status is active(1)."
::= { lmpNbrEntry 5 } ::= { lmpNbrEntry 5 }
lmpNbrStorageType OBJECT-TYPE lmpNbrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpNbrTable. Conceptual rows having the value lmpNbrTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
skipping to change at page 16, line 13 skipping to change at page 16, line 26
-- 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 a the default value for lmpCcHelloInterval.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpObjects 4 } ::= { lmpObjects 4 }
lmpCcHelloIntervalDefaultMin OBJECT-TYPE lmpCcHelloIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin." for lmpCcHelloIntervalMin. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."
::= { lmpObjects 5 } ::= { lmpObjects 5 }
lmpCcHelloIntervalDefaultMax OBJECT-TYPE lmpCcHelloIntervalDefaultMax 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 maximum value for the "This object specifies the default maximum value for the
HelloInterval parameter. It is used as a default value HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMax." for lmpCcHelloIntervalMax. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."
::= { lmpObjects 6 } ::= { lmpObjects 6 }
lmpCcHelloDeadIntervalDefault OBJECT-TYPE lmpCcHelloDeadIntervalDefault 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 HelloDeadInterval parameter "This object specifies the default HelloDeadInterval parameter
to use in the Hello protocol keep-alive phase. It indicates to use in the Hello protocol keep-alive phase. It indicates
how long a device should wait before declaring the control how long a device should wait before declaring the control
channel dead. The HelloDeadInterval parameter should be at channel dead. The HelloDeadInterval parameter should be at
least three times the value of HelloInterval. It is used as least three times the value of HelloInterval. It is used as
a default value for lmpCcHelloDeadInterval." a default value for lmpCcHelloDeadInterval. Implementations
should save the value of this object in persistent memory so
that it survives restarts or reboot."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpObjects 7 } ::= { lmpObjects 7 }
lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin." for lmpCcHelloDeadIntervalMin. Implementations should save
the value of this object in persistent memory so that it
survives restarts or reboot."
::= { lmpObjects 8 } ::= { lmpObjects 8 }
lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMax 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 maximum value for the "This object specifies the default maximum value for the
HelloDeadInterval parameter. It is used as a default value HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMax." for lmpCcHelloDeadIntervalMax. Implementations should save the
value of this object in persistent memory so that it survives
restarts or reboot."
::= { lmpObjects 9 } ::= { lmpObjects 9 }
-- LMP Control Channel Table -- LMP Control Channel Table
lmpControlChannelTable OBJECT-TYPE lmpControlChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpControlChannelEntry SYNTAX SEQUENCE OF LmpControlChannelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies LMP control channel information." "This table specifies LMP control channel information."
skipping to change at page 18, line 7 skipping to change at page 18, line 32
every control channel. Whenever a new entry is created with every control channel. Whenever a new entry is created with
lmpCcIsIf set to true(2), then a corresponding entry is lmpCcIsIf set to true(2), then 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 InetAddress, lmpCcNbrNodeId LmpNodeId,
lmpRemoteCcId Unsigned32, lmpRemoteCcId Unsigned32,
lmpRemoteCcAddressType InetAddressType, lmpRemoteCcAddressType InetAddressType,
lmpRemoteCcIpAddr InetAddress, lmpRemoteCcIpAddr InetAddress,
lmpCcSetupRole INTEGER, lmpCcSetupRole INTEGER,
lmpCcAuthentication TruthValue, lmpCcAuthentication TruthValue,
lmpCcHelloInterval LmpInterval, lmpCcHelloInterval LmpInterval,
lmpCcHelloIntervalMin LmpInterval, lmpCcHelloIntervalMin LmpInterval,
lmpCcHelloIntervalMax LmpInterval, lmpCcHelloIntervalMax LmpInterval,
lmpCcHelloIntervalNegotiated LmpInterval, lmpCcHelloIntervalNegotiated LmpInterval,
lmpCcHelloDeadInterval LmpInterval, lmpCcHelloDeadInterval LmpInterval,
skipping to change at page 19, line 10 skipping to change at page 19, line 36
underlying interface, the control channel's operational underlying interface, the control channel's operational
status must not be up(1), nor should the control channel status must not be up(1), nor should the control channel
forward or receive traffic." forward or receive traffic."
::= { 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
"Denotes whether or not this control channel corresponds to "In implementations where the control channels are modeled
an interface represented in the interfaces group table." as interfaces, the value of this object is true(1) and
this control channel is represented by an interface in
the interfaces group table. If control channels are not
modeled as interfaces, the value of this object is
false(2) and there are no corresponding interface for
this control channel in the interfaces group table."
::= { lmpControlChannelEntry 3 } ::= { lmpControlChannelEntry 3 }
lmpCcNbrNodeId OBJECT-TYPE lmpCcNbrNodeId OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the control channel remote node. "This is the Node ID of the control channel remote node.
This value is either configured or gets created by the node This value is either configured or gets created by the node
when a Config message is received or when an outgoing Config when a Config message is received or when an outgoing Config
message is acknowledged by the remote node. The Node ID message is acknowledged by the remote node."
address type must be IPv4."
::= { lmpControlChannelEntry 4 } ::= { lmpControlChannelEntry 4 }
lmpRemoteCcId OBJECT-TYPE lmpRemoteCcId 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
skipping to change at page 20, line 4 skipping to change at page 20, line 34
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 }
lmpRemoteCcIpAddr OBJECT-TYPE lmpRemoteCcIpAddr 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 non point-to-point configuration. For point-to- address for numbered control channel. The type of this
point configuration, the remote control channel address can address is determined by lmpRemoteCcAddressType.
be of type unknown and this object set the zero length Control channel must be numbered on non point-to-point
string. The lmpRemoteCcId object then identifies the configuration. For point-to-point configuration, the
unnumbered address." remote control channel address can be of type unknown
and this object set the zero length string. The
lmpRemoteCcId object then identifies the unnumbered
address."
::= { lmpControlChannelEntry 7 } ::= { lmpControlChannelEntry 7 }
lmpCcSetupRole OBJECT-TYPE lmpCcSetupRole OBJECT-TYPE
SYNTAX INTEGER { active(1), passive(2) } SYNTAX INTEGER { active(1), passive(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The role that this node should take during establishment "The role that this node should take during establishment
of this control channel. An active node will initiate of this control channel. An active node will initiate
establishment. A passive node will wait for the remote node establishment. A passive node will wait for the remote node
skipping to change at page 23, line 13 skipping to change at page 23, line 47
"The actual operational status of this control channel "The actual operational status of this control channel
interface." interface."
::= { lmpControlChannelEntry 22 } ::= { lmpControlChannelEntry 22 }
lmpCcRowStatus OBJECT-TYPE lmpCcRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. None of the writable objects
can only be changed when lmpCcRowStatus is active." in a row can be changed if the status is active(1)."
::= { lmpControlChannelEntry 23 } ::= { lmpControlChannelEntry 23 }
lmpCcStorageType OBJECT-TYPE lmpCcStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpControlChannelTable. Conceptual rows having the value lmpControlChannelTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
skipping to change at page 23, line 47 skipping to change at page 24, line 32
"This table specifies LMP control channel performance "This table specifies LMP control channel performance
counters." counters."
::= { lmpObjects 11 } ::= { lmpObjects 11 }
lmpControlChannelPerfEntry OBJECT-TYPE lmpControlChannelPerfEntry OBJECT-TYPE
SYNTAX LmpControlChannelPerfEntry SYNTAX LmpControlChannelPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every control channel." every control channel. lmpCcCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects
in this table."
AUGMENTS { lmpControlChannelEntry } AUGMENTS { lmpControlChannelEntry }
::= { lmpControlChannelPerfTable 1 } ::= { lmpControlChannelPerfTable 1 }
LmpControlChannelPerfEntry ::= SEQUENCE { LmpControlChannelPerfEntry ::= SEQUENCE {
lmpCcInOctets Counter32, lmpCcInOctets Counter32,
lmpCcInDiscards Counter32, lmpCcInDiscards Counter32,
lmpCcInErrors Counter32, lmpCcInErrors Counter32,
lmpCcOutOctets Counter32, lmpCcOutOctets Counter32,
lmpCcOutDiscards Counter32, lmpCcOutDiscards Counter32,
lmpCcOutErrors Counter32, lmpCcOutErrors Counter32,
skipping to change at page 35, line 29 skipping to change at page 36, line 16
-- End of lmpControlChannelPerfTable -- End of lmpControlChannelPerfTable
-- LMP TE Link Table -- LMP TE Link Table
lmpTeLinkTable OBJECT-TYPE lmpTeLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkEntry SYNTAX SEQUENCE OF LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a collection of TE link." "This table specifies the TE link information."
::= { lmpObjects 12 } ::= { lmpObjects 12 }
lmpTeLinkEntry OBJECT-TYPE lmpTeLinkEntry OBJECT-TYPE
SYNTAX LmpTeLinkEntry SYNTAX LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(200), i.e. for every TE link. An ifEntry ifType of teLink(200), i.e. for every TE link. An ifEntry
with an ifIndex must exist before the corresponding with an ifIndex must exist before the corresponding
skipping to change at page 35, line 51 skipping to change at page 36, line 38
destroyed, then so is the corresponding entry in the destroyed, then so is the corresponding entry in the
teLinkTable. The administrative status value is controlled teLinkTable. The administrative status value is controlled
from the ifEntry. Setting the administrative status to from the ifEntry. Setting the administrative status to
testing prompts LMP to start link verification on the TE link. testing prompts LMP to start link verification on the TE link.
Information about the TE link that is not LMP specific is also Information about the TE link that is not LMP specific is also
contained in teLinkTable [TELINK-MIB]." contained in teLinkTable [TELINK-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrNodeId InetAddress, lmpTeLinkNbrNodeId 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
} }
lmpTeLinkNbrNodeId OBJECT-TYPE lmpTeLinkNbrNodeId OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the TE link remote node. This value "This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation may be learned during control channel parameter negotiation
phase (in the Config message). Node ID address type must phase (in the Config message). Node ID address type must
be IPv4." be IPv4."
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
lmpTeLinkVerification OBJECT-TYPE lmpTeLinkVerification OBJECT-TYPE
skipping to change at page 37, line 35 skipping to change at page 38, line 23
form the endpoints of the TE link, but yet at least one form the endpoints of the TE link, but yet at least one
data-bearing links on the TE link is allocated." data-bearing links 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. All read-create objects delete a row in this table. None of the writable objects
can only be changed when lmpTeLinkRowStatus is active." in a row can be changed if the status is active(1)."
::= { lmpTeLinkEntry 6 } ::= { lmpTeLinkEntry 6 }
lmpTeLinkStorageType OBJECT-TYPE lmpTeLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpTeLinkTable. Conceptual rows having the value lmpTeLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
skipping to change at page 38, line 11 skipping to change at page 38, line 46
::= { lmpTeLinkEntry 7 } ::= { lmpTeLinkEntry 7 }
-- End of lmpTeLinkTable -- End of lmpTeLinkTable
lmpLinkVerificationInterval OBJECT-TYPE lmpLinkVerificationInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the link verification "This object indicates how often the link verification
procedure is executed. The interval is in milliseconds." procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link
verification procedure should not be executed. The
interval specified in this object should be large enough
to allow the verification procedure to be completed
before the start of the next interval.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
::= { lmpObjects 13 } ::= { lmpObjects 13 }
-- LMP Link Verification Table -- LMP Link Verification Table
lmpLinkVerificationTable OBJECT-TYPE lmpLinkVerificationTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpLinkVerificationEntry SYNTAX SEQUENCE OF LmpLinkVerificationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies TE link information associated with the "This table specifies TE link information associated with the
skipping to change at page 38, line 41 skipping to change at page 39, line 36
every TE link that supports the LMP verification every TE link that supports the LMP verification
procedure." procedure."
AUGMENTS { lmpTeLinkEntry } AUGMENTS { lmpTeLinkEntry }
::= { lmpLinkVerificationTable 1 } ::= { lmpLinkVerificationTable 1 }
LmpLinkVerificationEntry ::= SEQUENCE { LmpLinkVerificationEntry ::= SEQUENCE {
lmpVerifyInterval LmpInterval, lmpVerifyInterval LmpInterval,
lmpVerifyDeadInterval LmpInterval, lmpVerifyDeadInterval LmpInterval,
lmpVerifyTransportMechanism BITS, lmpVerifyTransportMechanism BITS,
lmpVerifyAllLinks INTEGER, lmpVerifyAllLinks INTEGER,
lmpTeLinkBitRate Unsigned32, lmpVerifyTransmissionRate Unsigned32,
lmpTeLinkWavelength Unsigned32 lmpVerifyWavelength Unsigned32
} }
lmpVerifyInterval OBJECT-TYPE lmpVerifyInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyInterval parameter used "This object specifies the VerifyInterval parameter used
in the LMP link verification process. It indicates the in the LMP link verification process. It indicates the
interval at which the Test messages are sent." interval at which the Test messages are sent."
skipping to change at page 39, line 29 skipping to change at page 40, line 25
detect a Test message at the remote node." detect a Test message at the remote node."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 2 } ::= { lmpLinkVerificationEntry 2 }
lmpVerifyTransportMechanism OBJECT-TYPE lmpVerifyTransportMechanism OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
-- SONET/SDH encoding type: -- SONET/SDH encoding type:
j016OverheadBytes(0), dccSectionOverheadBytes(0),
j064OverheadBytes(1), dccLineOverheadBytes(1),
dccSectionOverheadBytes(2), j0Trace(2),
dccLineOverheadBytes(3), j1Trace(3),
pos(4), j2Trace(4),
j0Trace(5) -- All encoding types:
-- GigE encoding type: TBD payload(31)
-- 10GigE encoding type: TBD
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This defines the transport mechanism for the Test messages. The "This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx and
SONET/SDH Encoding for Link Management Protocol (LMP)
Test Messages, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP] and [LMP-TEST]
::= { lmpLinkVerificationEntry 3 } ::= { lmpLinkVerificationEntry 3 }
lmpVerifyAllLinks OBJECT-TYPE lmpVerifyAllLinks OBJECT-TYPE
SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the verification process checks "This object indicates whether the verification process checks
all entities or only the new entities that have been added to all entities or only the new entities that have been added to
this TE link." this TE link."
::= { lmpLinkVerificationEntry 4 } ::= { lmpLinkVerificationEntry 4 }
lmpTeLinkBitRate OBJECT-TYPE lmpVerifyTransmissionRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the bit rate at which the Test messages will be "This is the transmission rate of the data link over which
transmitted and is expressed in bytes per second." the Test messages will be transmitted and is expressed in
bytes per second."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 5 } ::= { lmpLinkVerificationEntry 5 }
lmpTeLinkWavelength OBJECT-TYPE lmpVerifyWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value corresponds to the wavelength at "This value corresponds to the wavelength at
which the Test messages will be transmitted over and is which the Test messages will be transmitted over and is
measured in nanometers (nm). If each data-bearing link measured in nanometers (nm). If each data-bearing link
corresponds to a separate wavelength, than this value should corresponds to a separate wavelength, than this value should
be set to 0." be set to 0."
REFERENCE REFERENCE
skipping to change at page 41, line 14 skipping to change at page 42, line 13
DESCRIPTION DESCRIPTION
"This table specifies LMP TE link performance counters." "This table specifies LMP TE link performance counters."
::= { lmpObjects 15 } ::= { lmpObjects 15 }
lmpTeLinkPerfEntry OBJECT-TYPE lmpTeLinkPerfEntry OBJECT-TYPE
SYNTAX LmpTeLinkPerfEntry SYNTAX LmpTeLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every TE link." every TE link. lmpTeCounterDiscontinuityTime is used
to indicate potential discontinuity for all counter objects
in this table."
AUGMENTS { lmpTeLinkEntry } AUGMENTS { lmpTeLinkEntry }
::= { lmpTeLinkPerfTable 1 } ::= { lmpTeLinkPerfTable 1 }
LmpTeLinkPerfEntry ::= SEQUENCE { LmpTeLinkPerfEntry ::= SEQUENCE {
lmpTeInOctets Counter32, lmpTeInOctets Counter32,
lmpTeOutOctets Counter32, lmpTeOutOctets Counter32,
lmpTeBeginVerifyReceived Counter32, lmpTeBeginVerifyReceived Counter32,
lmpTeBeginVerifySent Counter32, lmpTeBeginVerifySent Counter32,
lmpTeBeginVerifyRetransmit Counter32, lmpTeBeginVerifyRetransmit Counter32,
lmpTeBeginVerifyAckReceived Counter32, lmpTeBeginVerifyAckReceived Counter32,
skipping to change at page 53, line 21 skipping to change at page 54, line 21
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpDataLinkEntry 8 } ::= { lmpDataLinkEntry 8 }
lmpDataLinkRowStatus OBJECT-TYPE lmpDataLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. None of the writable objects
can only be changed when lmpDataLinkRowStatus is active." in a row can be changed if the status is active(1)."
::= { lmpDataLinkEntry 9 } ::= { lmpDataLinkEntry 9 }
lmpDataLinkStorageType OBJECT-TYPE lmpDataLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpDataLinkTable. Conceptual rows having the value lmpDataLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
skipping to change at page 55, line 49 skipping to change at page 56, line 49
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
-- Notification Configuration -- Notification Configuration
lmpNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum number of
notifications issued per second. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period, or may
queue them until an appropriate time. A value of 0
means no throttling is applied and events may be
notified at the rate at which they occur.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
DEFVAL { 0 }
::= { lmpObjects 18 }
lmpLinkPropertyNotificationsEnabled OBJECT-TYPE lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of lmpTeLinkPropertyMismatch generation of lmpTeLinkPropertyMismatch
and lmpDataLinkPropertyMismatch notifications, and lmpDataLinkPropertyMismatch notifications,
otherwise these notifications are not emitted." otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 18 } ::= { 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, then it enables the "If this object is true, 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
persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 19 } ::= { 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, then it enables the generation of "If this object is true, 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
persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 20 } ::= { 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, then it enables the "If this object is true, then it enables the
generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
notifications, otherwise these notifications are not emitted." notifications, otherwise these notifications are not emitted.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 21 } ::= { 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, then it enables the "If this object is true, 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
persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 22 } ::= { lmpObjects 23 }
-- Notifications -- Notifications
-- The LMP notification rate depends on the size of the network, the
-- type of links, the network configuration, the reliability of the
-- network, etc.
--
-- When designing this MIB, care has been taken to minimize the
-- amount of notifications generated for LMP purposes. Wherever
-- possible, notifications are state driven meaning the notification
-- are only sent when the system changes state. The only notifications
-- that are repeated and could cause a problem as far as congestion
-- is concerned are the ones associated with data link verification.
-- Without any considerations to handling of these notifications, a
-- problem may arise if the number of data links is high. Since the
-- data link verification notifications can happen only once per data
-- link per link verification interval, the notification rate should
-- be sustainable if one chooses an appropriate link verification
-- interval for a given network configuration. For instance, a
-- network of 100 nodes 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 given time would have 1 notification per
-- second sent from each node, or 100 notifications per second for
-- the whole network. The rest of the notifications are negligeable
-- compared to this number.
--
-- To alleviate the congestion problem, the lmpNotificationMaxRate object
-- can be used to implement a throttling mechanism. It is also possible
-- to enable/disable certain type of 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." is true. It is recommended that this notification be reported
only the first time a mismatch is detected. Otherwise, for a
given TE link, this notification can occur no more than once
per verification interval."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId }
lmpDataLinkRemoteIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing link "This notification is generated when a data-bearing link
property mismatch is detected on the node. ifIndex property mismatch is detected on the node. lmpDataLinkType
is the interface index of the TE link. The remote entity is used to identify the local identifiers associated with
interface id is the remote entity interface id received in the data link (the data link interface index can be used
the LinkSummary message. This notification should to determine the TE link interface index as this
not be sent unless lmpLinkPropertyNotificationsEnabled is relationship is captured in the interface stack table).
true." The remote entity interface id is the remote entity
interface id received in the LinkSummary message.
This notification should not be sent unless
lmpLinkPropertyNotificationsEnabled is true. It is
recommended that this notification be reported only the
first time a mismatch is detected. Otherwise, for a given
data link, this notification can occur no more than once
per verification interval."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification -- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpCcNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when there are more than one "This notification is generated when there are more than one
control channels between LMP neighbors and the last redundant control channels between LMP neighbors and the last redundant
skipping to change at page 58, line 20 skipping to change at page 60, line 35
-- Control Channel Notifications -- Control Channel Notifications
lmpControlChannelUp NOTIFICATION-TYPE lmpControlChannelUp NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a control "This notification is generated when a control
channel transitions to the up operational state. This channel transitions to the up operational state. This
notification should not be sent unless notification should not be sent unless
lmpCcUpDownNotififcationsEnabled is true." lmpCcUpDownNotificationsEnabled is true."
::= { lmpNotifications 4 } ::= { lmpNotifications 4 }
lmpControlChannelDown NOTIFICATION-TYPE lmpControlChannelDown NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a control "This notification is generated when a control channel
channel transitions out of the up operational state. This transitions out of the up operational state. This
notification should not be sent unless notification should not be sent unless
lmpCcUpDownNotificationsEnabled is true." lmpCcUpDownNotificationsEnabled is true."
::= { lmpNotifications 5 } ::= { lmpNotifications 5 }
-- TE Link Notification -- TE Link Notification
lmpTeLinkDegraded NOTIFICATION-TYPE lmpTeLinkDegraded NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { lmpTeLinkOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a lmpTeLinkOperStatus "This notification is generated when a lmpTeLinkOperStatus
object for a TE link enters the degraded state. This object for a TE link enters the degraded state. This
notification should not be sent unless notification should not be sent unless
lmpTeLinkNotificationsEnabled is true." lmpTeLinkNotificationsEnabled is true."
::= { lmpNotifications 6 } ::= { lmpNotifications 6 }
lmpTeLinkNotDegraded NOTIFICATION-TYPE lmpTeLinkNotDegraded NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { lmpTeLinkOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a lmpTeLinkOperStatus "This notification is generated when a lmpTeLinkOperStatus
object for a TE link leaves the degraded state. This object for a TE link leaves the degraded state. This
notification should not be sent unless notification should not be sent unless
lmpTeLinkNotificationsEnabled is true." lmpTeLinkNotificationsEnabled is true."
::= { lmpNotifications 7 } ::= { lmpNotifications 7 }
-- Data-bearing Link Notification -- Data-bearing Link Notification
lmpDataLinkVerificationFailure NOTIFICATION-TYPE lmpDataLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing "This notification is generated when a data-bearing
link verification fails. This notification should not be sent link verification fails. This notification should not be sent
unless lmpDataLinkNotificationsEnabled is true." unless lmpDataLinkNotificationsEnabled is true. For a given
data link, this notification can occur no more than once per
verification interval."
::= { lmpNotifications 8 } ::= { lmpNotifications 8 }
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
lmpGroups lmpCompliances
OBJECT IDENTIFIER ::= { lmpConformance 1 } OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpCompliances lmpGroups
OBJECT IDENTIFIER ::= { lmpConformance 2 } OBJECT IDENTIFIER ::= { lmpConformance 2 }
lmpModuleFullCompliance MODULE-COMPLIANCE lmpModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
configuration and monitoring of LMP MIB." configuration and monitoring of LMP MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
skipping to change at page 60, line 21 skipping to change at page 62, line 39
"This group is mandatory for devices which support "This group is mandatory for devices which support
the link verification procedure." the link verification procedure."
GROUP lmpNotificationGroup GROUP lmpNotificationGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Support for notReady(3) and createAndWait(5) is
not be supported." not required."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpRemoteCcAddressType OBJECT lmpRemoteCcAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for non point-to-point configurations." supported for non point-to-point configurations."
OBJECT lmpRemoteCcIpAddr OBJECT lmpRemoteCcIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Support for notReady(3) and createAndWait(5) is
not be supported." not required."
OBJECT lmpCcOperStatus OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION DESCRIPTION
"A value of active(3), configuring(4), goingDown(5) "A value of configSnd(3), configRcv(4), active(5),
need not be supported." goingDown(6) need not be supported."
-- lmpTeLinkTable -- lmpTeLinkTable
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION DESCRIPTION
"The testing(3) state need not be supported." "The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Support for notReady(3) and createAndWait(5) is
not be supported." not required."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkActiveOperStatus OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(4) need not be supported."
OBJECT lmpDataLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of psvTst(4) need not be supported."
OBJECT lmpDataLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Support for notReady(3) and createAndWait(5) is
not be supported." not required."
::= { lmpCompliances 1 } ::= { lmpCompliances 1 }
lmpModuleReadOnlyCompliance MODULE-COMPLIANCE lmpModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
monitoring of the LMP MIB." monitoring of the LMP MIB."
MODULE -- this module MODULE -- this module
skipping to change at page 63, line 28 skipping to change at page 65, line 50
OBJECT lmpCcHelloDeadIntervalDefaultMin OBJECT lmpCcHelloDeadIntervalDefaultMin
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcHelloDeadIntervalDefaultMax OBJECT lmpCcHelloDeadIntervalDefaultMax
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNotificationMaxRate
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRetransmitInterval OBJECT lmpNbrRetransmitInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRetryLimit OBJECT lmpNbrRetryLimit
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRetransmitDelta OBJECT lmpNbrRetransmitDelta
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1) }
createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Write access is not required and active(1) is the
not be supported." only status that needs to be supported."
OBJECT lmpNbrStorageType OBJECT lmpNbrStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpCcUnderlyingIfIndex OBJECT lmpCcUnderlyingIfIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 65, line 22 skipping to change at page 67, line 48
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcHelloDeadIntervalMax OBJECT lmpCcHelloDeadIntervalMax
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1) }
createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Write access is not required and active(1) is the
not 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) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of active(3), configuring(4), goingDown(5) "A value of configSnd(3), configRcv(4), active(5),
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 lmpVerifyInterval OBJECT lmpVerifyInterval
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 66, line 26 skipping to change at page 69, line 4
OBJECT lmpTeLinkVerification OBJECT lmpTeLinkVerification
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkFaultManagement OBJECT lmpTeLinkFaultManagement
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkDwdm OBJECT lmpTeLinkDwdm
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(5) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The testing(3) state need not be supported." "The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1) }
createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Write access is not required and active(1) is the
not be supported." only status that needs to be supported."
OBJECT lmpTeLinkStorageType OBJECT lmpTeLinkStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpTeLinkVerificationTable -- lmpTeLinkVerificationTable
OBJECT lmpTeLinkBitRate
OBJECT lmpVerifyTransmissionRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkWavelength OBJECT lmpVerifyWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkAddressType OBJECT lmpDataLinkAddressType
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
skipping to change at page 68, line 4 skipping to change at page 70, line 28
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 lmpDataLinkEncodingType OBJECT lmpDataLinkEncodingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpDataLinkActiveOperStatus OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(4) need not be supported."
OBJECT lmpDataLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of psvTst(3) need not be supported." "A value of psvTst(4) need not be supported."
OBJECT lmpDataLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX RowStatus { active(1) }
createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "Write access is not required and active(1) is the
not be supported." only status that needs to be supported."
OBJECT lmpDataLinkStorageType OBJECT lmpDataLinkStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { lmpCompliances 2 } ::= { lmpCompliances 2 }
-- Units of conformance -- Units of conformance
lmpNodeGroup OBJECT-GROUP lmpNodeGroup OBJECT-GROUP
OBJECTS { lmpAdminStatus, OBJECTS { lmpAdminStatus,
lmpOperStatus, lmpOperStatus,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpUnprotectedNotificationsEnabled lmpUnprotectedNotificationsEnabled,
lmpNotificationMaxRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP node configuration." "Collection of objects needed for LMP node configuration."
::= { lmpGroups 1 } ::= { lmpGroups 1 }
lmpControlChannelGroup OBJECT-GROUP lmpControlChannelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lmpNbrRetransmitInterval, lmpNbrRetransmitInterval,
lmpNbrRetryLimit, lmpNbrRetryLimit,
skipping to change at page 69, line 47 skipping to change at page 72, line 20
lmpCcIsInterfaceGroup OBJECT-GROUP lmpCcIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf } OBJECTS { lmpCcIsIf }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are "Objects needed to implement control channels that are
interfaces." interfaces."
::= { lmpGroups 3 } ::= { lmpGroups 3 }
lmpCcIsNotInterfaceGroup OBJECT-GROUP lmpCcIsNotInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS { lmpCcUnderlyingIfIndex,
lmpCcUnderlyingIfIndex,
lmpCcIsIf, lmpCcIsIf,
lmpCcLastChange, lmpCcLastChange,
lmpCcAdminStatus lmpCcAdminStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are not "Objects needed to implement control channels that are not
interfaces." interfaces."
::= { lmpGroups 4 } ::= { lmpGroups 4 }
skipping to change at page 70, line 25 skipping to change at page 72, line 45
"Collection of objects needed to implement the link "Collection of objects needed to implement the link
property correlation procedure." property correlation procedure."
::= { lmpGroups 5 } ::= { lmpGroups 5 }
lmpLinkVerificationGroup OBJECT-GROUP lmpLinkVerificationGroup OBJECT-GROUP
OBJECTS { lmpLinkVerificationInterval, OBJECTS { lmpLinkVerificationInterval,
lmpVerifyInterval, lmpVerifyInterval,
lmpVerifyDeadInterval, lmpVerifyDeadInterval,
lmpVerifyTransportMechanism, lmpVerifyTransportMechanism,
lmpVerifyAllLinks, lmpVerifyAllLinks,
lmpTeLinkBitRate, lmpVerifyTransmissionRate,
lmpTeLinkWavelength, lmpVerifyWavelength,
lmpDataLinkNotificationsEnabled lmpDataLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects needed to implement the link
verification procedure." verification procedure."
::= { lmpGroups 6 } ::= { lmpGroups 6 }
lmpPerfGroup OBJECT-GROUP lmpPerfGroup OBJECT-GROUP
OBJECTS { lmpCcInOctets, OBJECTS { lmpCcInOctets,
skipping to change at page 74, line 8 skipping to change at page 76, line 26
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { lmpGroups 10 } ::= { lmpGroups 10 }
-- End of LMP-MIB -- End of LMP-MIB
END END
10. Intellectual Property Considerations 10. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per- intellectual property or other rights that might be claimed to
tain to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might this document or the extent to which any license under such rights
or might not be available; neither does it represent that it has made might or might not be available; neither does it represent that it
any effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and standards- IETF's procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards-related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses claims of rights made available for publication and any assurances of
to be made available, or the result of an attempt made to obtain a licenses to be made available, or the result of an attempt made to
general license or permission for the use of such proprietary rights obtain a general license or permission for the use of such
by implementers or users of this specification can be obtained from proprietary rights by implementers or users of this specification can
the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure envi- environments. The support for SET operations in a non-secure
ronment without proper protection can have a negative effect on net- environment without proper protection can have a negative effect on
work operations. These are the tables and objects and their sensi- network operations. These are the tables and objects and their
tivity/vulnerability: sensitivity/vulnerability:
- Unauthorized changes to the lmpNbrTable, lmpControlChannelTable,
lmpTeLinkTable and lmpDataLinkTable may disrupt allocation of
resources in the network.
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
- The lmpNbrTable exposes network provider's node IP addresses. - The lmpNbrTable exposes network provider's node IP addresses.
- lmpControlChannelTable exposes network provider's control - lmpControlChannelTable exposes network provider's control
network. network.
- lmpDataLinkTable exposes network provider's data network. - lmpDataLinkTable exposes network provider's data network.
- Unauthorized changes to the lmpControlChannelTable,
lmpTeLinkTable and lmpDataLinkTable may disrupt allocation of
resources in the 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), includ- provided by the SNMPv3 framework (see [RFC3410], section 8),
ing full support for the SNMPv3 cryptographic mechanisms (for authen- including full support for the SNMPv3 cryptographic mechanisms (for
tication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOM- Further, deployment of SNMP versions prior to SNMPv3 is NOT
MENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
cryptographic security. It is then a customer/operator responsibil- enable cryptographic security. It is then a customer/operator
ity to ensure that the SNMP entity giving access to an instance of responsibility to ensure that the SNMP entity giving access to an
this MIB module is properly configured to give access to the objects instance of this MIB module is properly configured to give access to
only to those principals (users) that have legitimate rights to the objects only to those principals (users) that have legitimate
indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
12. Acknowledgments 12. Acknowledgments
The general structure of this draft has been modeled around draft- The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt. ietf-mpls-lsr-mib-06.txt.
The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and
George Wang. George Wang.
13. References 13. References
skipping to change at page 76, line 21 skipping to change at page 78, line 47
RFC 3471, January 2003. RFC 3471, January 2003.
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering", "Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>, Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002. July 2002.
[TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., [TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Traffic Engineering Link Management Information "Traffic Engineering Link Management Information
Base", Internet Draft Base", Internet Draft
<draft-ietf-mpls-telink-mib-02.txt>, May 2003. <draft-ietf-mpls-telink-mib-04.txt>, September 2003.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D., Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., Rajagopalan, B., and Sandick, H., Zinin, A., Rajagopalan, B., and
Ramamoorthi, S., "Link Management Protocol", Ramamoorthi, S., "Link Management Protocol",
Internet Draft <draft-ietf-ccamp-lmp-08.txt>, Internet Draft <draft-ietf-ccamp-lmp-08.txt>,
March 2003. March 2003.
[LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding
for Link Management (LMP) Test Messages", Internet
Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-03.txt>,
May 2003.
13.2. Informative References 13.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Email: dubuc.consulting@rogers.com Rincon Networks, Inc. Email: dubuc.consulting@rogers.com Rincon Networks, Inc.
110 El Paseo 110 El Paseo
Santa Barbara, CA 93101 Santa Barbara, CA 93101
Email: jplang@ieee.org Email: jplang@ieee.org
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Avici Systems, Inc. Calient Networks, Inc. Email: sudheer@ieee.org Calient Networks, Inc.
101 Billerica Avenue 5853 Rue Ferrari 5853 Rue Ferrari
N Billerica, MA 08162 San Jose, CA 95138 San Jose, CA 95138
Email: sudheer@avici.com Email: evan@calient.net Email: evan@calient.net
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
skipping to change at page 77, line 20 skipping to change at page 79, line 50
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu- included on all such copies and derivative works. However, this
ment itself may not be modified in any way, such as by removing the document itself may not be modified in any way, such as by removing
copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop- Internet organizations, except as needed for the purpose of
ing Internet standards in which case the procedures for copyrights developing Internet standards in which case the procedures for
defined in the Internet Standards process must be followed, or as copyrights defined in the Internet Standards process must be
required to translate it into languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. This revoked by the Internet Society or its successors or assigns. This
document and the information contained herein is provided on an "AS document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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