draft-ietf-ccamp-lmp-mib-07.txt   draft-ietf-ccamp-lmp-mib-08.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: March 2004 Expires: September 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
October 2003 March 2004
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-07.txt draft-ietf-ccamp-lmp-mib-08.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 25 skipping to change at page 2, line 25
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 . . . . . . . . . . . . . . . . . . . . . 5 6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5
7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5 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 . . . . . . . . . . . . . . 76 10. Intellectual Property Considerations . . . . . . . . . . . . . . 77
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 76 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 77
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 75 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 78
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 79
13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 78 13.1 IANA Considerations for lmp ifType . . . . . . . . . . . . . . 79
13.2 Informative References . . . . . . . . . . . . . . . . . . . . 79 13.2 IANA Considerations for LMP-MIB . . . . . . . . . . . . . . . . 79
14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 79 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 79 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 79
14.2 Informative References . . . . . . . . . . . . . . . . . . . . 80
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 81
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 to be used as a common control plane and a separate common measure-
measurement plane. Along with Generalized MPLS (GMPLS) [RFC3471], the ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link
Link Management Protocol [LMP], which primary purpose is to manage Management Protocol [LMP], which primary purpose is to manage traffic
traffic engineering (TE) links, is one of the key components of this engineering (TE) links, is one of the key components of this stan-
standardization activity. Primary goals of LMP are the maintenance of dardization activity. Primary goals of LMP are the maintenance of the
the control channel connectivity, correlation of link properties, control channel connectivity, correlation of link properties, verifi-
verification of data-bearing links and detection and isolation of cation of data-bearing links and detection and isolation of link
link faults. 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].
skipping to change at page 4, line 20 skipping to change at page 4, line 28
- The MIB module is used to express the mapping between local and - The MIB module is used to express the mapping between local and
remote TE links, as well as local and remote interface identifiers remote TE links, as well as local and remote interface identifiers
for port or component link. for port or component link.
- Performance counters are provided for measuring LMP - Performance counters are provided for measuring LMP
performance on 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 (TE-
module [TELINK-MIB]. The TE link table, which is used to associate LINK-STD-MIB) MIB module [TELINK-MIB]. The TE link table, which is
data-bearing links to TE links, is defined in the TE Link MIB. The TE used to associate data-bearing links to TE links, is defined in the
link table in the LMP MIB module contains TE link information TE Link MIB. The TE link table in the LMP MIB module contains TE link
specific to LMP. information specific to LMP.
5. Outline 5. Outline
Configuring LMP through an optical device involves the following Configuring LMP through an optical device involves the following
steps: steps:
- Enabling LMP on LMP capable interfaces through control channel - Enabling LMP on LMP capable interfaces through control channel
configuration. configuration.
- Optionally specifying link verification parameters. - Optionally specifying link verification parameters.
skipping to change at page 8, line 26 skipping to change at page 8, line 39
lmpTeLinkFaultManagement = true(2), lmpTeLinkFaultManagement = true(2),
lmpTeLinkDwdm = false(1), lmpTeLinkDwdm = false(1),
lmpTeLinkRowStatus = createAndGo(4), lmpTeLinkRowStatus = createAndGo(4),
lmpTeLinkStorageType = nonVolatile(3) lmpTeLinkStorageType = nonVolatile(3)
} }
and in lmpVerifyTable: and in lmpVerifyTable:
{ {
lmpVerifyInterval = 100, lmpVerifyInterval = 100,
lmpVerifyDeadInterval = 300, lmpVerifyDeadInterval = 300,
lmpVerifyTransportMechanism = 1, -- j016OverheadBytes lmpVerifyTransportMechanism = j0Trace(3),
lmpVerifyAllLinks = verifyAllLinks(1) lmpVerifyAllLinks = true(2),
lmpVerifyTransmissionRate = 100000, lmpVerifyTransmissionRate = 100000,
lmpVerifyWavelength = 0 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].
skipping to change at page 9, line 29 skipping to change at page 9, line 44
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
In the above diagram, "Underlying Layer..." refers to the ifIndex In the above diagram, "Underlying Layer..." refers to the ifIndex
of any interface type over which the LMP interface will transmit of any interface type over which the LMP interface will transmit
its traffic. Note that if the underlying layer provides multiple its traffic. Note that if the underlying layer provides multiple
access to its media (i.e.: Ethernet), then it is possible to stack access to its media (i.e.: Ethernet), then it is possible to stack
multiple LMP interfaces on top of this interface in parallel. multiple LMP interfaces on top of this interface in parallel.
Note that it is not a requirement that LMP control channels be
modeled as interfaces. It is acceptable that control channels
simply exist as logical connections between adjacent LMP-capable
nodes. In this case, lmpCcIsIf is set to false(2) and no
corresponding entry is made in the ifTable.
8.1. Support of the LMP Layer by ifTable 8.1. Support of the LMP Layer by ifTable
Some specific interpretations of ifTable for the LMP layer Some specific interpretations of ifTable for the LMP layer
follow. follow.
Object Use for the LMP layer Object Use for the LMP layer
ifIndex Each LMP interface may be represented by an ifEntry. ifIndex Each LMP interface may be represented by an ifEntry.
ifDescr Description of the LMP interface. ifDescr Description of the LMP interface.
skipping to change at page 11, line 31 skipping to change at page 12, line 4
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; FROM TE-LINK-STD-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200310011200Z" -- 1 October 2003 12:00:00 EST LAST-UPDATED "200403031200Z" -- 3 March 2004 12:00:00 EST
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@rogers.com
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@ieee.org Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Email: jplang@ieee.org Email: jplang@ieee.org
Evan McGinnis Evan McGinnis
Email: evan@calient.net" Email: evan@calient.net"
DESCRIPTION DESCRIPTION
"Copyright (C) 2003 The Internet Society. This version of "Copyright (C) 2004 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC XXXX; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200310011200Z" -- 1 October 2003 12:00:00 EST "200403031200Z" -- 3 March 2004 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC xxxx (to be assigned by RFC
Editor)" Editor)"
::= { transmission xxx } -- To be assigned by IANA. ::= { transmission xxx } -- To be assigned by IANA.
-- Request to assign same number as LMP -- Request to assign same number as LMP
-- ifType. -- ifType.
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
skipping to change at page 15, line 15 skipping to change at page 15, line 36
which is based on RFC 2914." which is based on RFC 2914."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 3 } DEFVAL { 3 }
::= { lmpNbrEntry 7 } ::= { lmpNbrEntry 7 }
lmpNbrRetransmitDelta OBJECT-TYPE lmpNbrRetransmitDelta OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object governs the speed with which the sender increases "This object governs the speed with which the sender increases
the retransmission interval." the retransmission interval as explained in section 10 of the
Link Management Protocol specification, which is based on
RFC 2914. This value is a power used to express the
exponential backoff. The ratio of two succesive retransmission
intervals is (1 + Delta)."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
DEFVAL { 1 } DEFVAL { 1 }
::= { lmpNbrEntry 8 } ::= { lmpNbrEntry 8 }
lmpNbrAdminStatus OBJECT-TYPE lmpNbrAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 15, line 50 skipping to change at page 16, line 28
"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. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1)." in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."
::= { 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
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile }
::= { lmpNbrEntry 6 } ::= { lmpNbrEntry 6 }
-- 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
skipping to change at page 18, line 33 skipping to change at page 19, line 15
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 LmpNodeId, lmpCcNbrNodeId LmpNodeId,
lmpRemoteCcId Unsigned32, lmpCcRemoteId Unsigned32,
lmpRemoteCcAddressType InetAddressType, lmpCcRemoteAddressType InetAddressType,
lmpRemoteCcIpAddr InetAddress, lmpCcRemoteIpAddr 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,
lmpCcHelloDeadIntervalMin LmpInterval, lmpCcHelloDeadIntervalMin LmpInterval,
lmpCcHelloDeadIntervalMax LmpInterval, lmpCcHelloDeadIntervalMax LmpInterval,
lmpCcHelloDeadIntervalNegotiated LmpInterval, lmpCcHelloDeadIntervalNegotiated LmpInterval,
skipping to change at page 19, line 21 skipping to change at page 19, line 49
DESCRIPTION DESCRIPTION
"This value represents the local control channel identifier. "This value represents the local control channel identifier.
The control channel identifier is a non-zero 32 bit number." The control channel identifier is a non-zero 32 bit number."
::= { lmpControlChannelEntry 1 } ::= { lmpControlChannelEntry 1 }
lmpCcUnderlyingIfIndex OBJECT-TYPE lmpCcUnderlyingIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the underlying interface index, i.e. "If lmpCcIsIf is set to true(1), this object carries the
the interface index of the interface over which the LMP index into the ifTable of the entry that represents the
interface will transmit its traffic. If set to 0, then the LMP interface over which LMP will transmit its traffic.
control channel is not associated with any underlying
interface. If the control channel is not associated with an If this object is set to zero, but lmpCcIsIf is set to
underlying interface, the control channel's operational true(1), the control channel is not currently associated
status must not be up(1), nor should the control channel with any underlying interface and the control channel's
forward or receive traffic." operational status must not be up(1), nor should the
control channel forward or receive traffic.
If lmpCcIsIf is set to false(2), this object should be set
to zero and should be ignored."
::= { lmpControlChannelEntry 2 } ::= { lmpControlChannelEntry 2 }
lmpCcIsIf OBJECT-TYPE lmpCcIsIf OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In implementations where the control channels are modeled "In implementations where the control channels are modeled
as interfaces, the value of this object is true(1) and as interfaces, the value of this object is true(1) and
this control channel is represented by an interface in this control channel is represented by an interface in
the interfaces group table. If control channels are not the interfaces group table as indicated by the value of
lmpCcUnderlyingIfIndex. If control channels are not
modeled as interfaces, the value of this object is modeled as interfaces, the value of this object is
false(2) and there are no corresponding interface for false(2) and there is no corresponding interface for
this control channel in the interfaces group table." this control channel in the interfaces group table,
and the value of lmpCcUnderlyingIfIndex should be
ignored."
::= { lmpControlChannelEntry 3 } ::= { lmpControlChannelEntry 3 }
lmpCcNbrNodeId OBJECT-TYPE lmpCcNbrNodeId OBJECT-TYPE
SYNTAX LmpNodeId SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the control channel remote node. "This is the Node ID of the control channel remote node.
This value is either configured or gets created by the node This value 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." message is acknowledged by the remote node."
::= { lmpControlChannelEntry 4 } ::= { lmpControlChannelEntry 4 }
lmpRemoteCcId OBJECT-TYPE lmpCcRemoteId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel identifier "This value represents the remote control channel identifier
(32 bit number). It is determined during the negotiation (32 bit number). It is determined during the negotiation
phase. A value of zero means that the remote control channel phase. A value of zero means that the remote control channel
identifier has not yet been learnt." identifier has not yet been learnt."
::= { lmpControlChannelEntry 5 } ::= { lmpControlChannelEntry 5 }
lmpRemoteCcAddressType OBJECT-TYPE lmpCcRemoteAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel IP address "This value represents the remote control channel IP address
type. In point-to-point configuration, this value can be set type. In point-to-point configuration, this value can be set
to unknown(0)." to unknown(0)."
::= { lmpControlChannelEntry 6 } ::= { lmpControlChannelEntry 6 }
lmpRemoteCcIpAddr OBJECT-TYPE lmpCcRemoteIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the remote control channel Internet "This value represents the remote control channel Internet
address for numbered control channel. The type of this address for numbered control channel. The type of this
address is determined by lmpRemoteCcAddressType. address is determined by lmpCcRemoteAddressType.
Control channel must be numbered on non point-to-point Control channel must be numbered on non point-to-point
configuration. For point-to-point configuration, the configuration. For point-to-point configuration, the
remote control channel address can be of type unknown remote control channel address can be of type unknown
and this object set the zero length string. The in which case this object must be a zero length string. The
lmpRemoteCcId object then identifies the unnumbered lmpCcRemoteId object then identifies the unnumbered
address." address."
::= { lmpControlChannelEntry 7 } ::= { lmpControlChannelEntry 7 }
lmpCcSetupRole OBJECT-TYPE lmpCcSetupRole OBJECT-TYPE
SYNTAX INTEGER { active(1), passive(2) } SYNTAX INTEGER { active(1), passive(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The role that this node should take during establishment "The role that this node should take during establishment
of this control channel. An active node will initiate of this control channel. An active node will initiate
skipping to change at page 21, line 14 skipping to change at page 21, line 49
to initiate. A pair of nodes that both take the passive role to initiate. A pair of nodes that both take the passive role
will never establish communications." will never establish communications."
DEFVAL { active } DEFVAL { active }
::= { lmpControlChannelEntry 8 } ::= { lmpControlChannelEntry 8 }
lmpCcAuthentication OBJECT-TYPE lmpCcAuthentication OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the control channel should use "This object indicates whether the control channel must use
authentication." authentication."
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]
::= { lmpControlChannelEntry 9 } ::= { lmpControlChannelEntry 9 }
lmpCcHelloInterval OBJECT-TYPE lmpCcHelloInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloInterval "This object specifies the value of the HelloInterval
parameter. The default value for this object should be parameter. The default value for this object should be
set to lmpCcHelloIntervalDefault." set to lmpCcHelloIntervalDefault."
::= { lmpControlChannelEntry 12 } ::= { lmpControlChannelEntry 10 }
lmpCcHelloIntervalMin OBJECT-TYPE lmpCcHelloIntervalMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum value for the "This object specifies the minimum value for the
HelloInterval parameter. The default value for this HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMinDefault." object should be set to lmpCcHelloIntervalMinDefault."
::= { lmpControlChannelEntry 13 } ::= { lmpControlChannelEntry 11 }
lmpCcHelloIntervalMax OBJECT-TYPE lmpCcHelloIntervalMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum value for the "This object specifies the maximum value for the
HelloInterval parameter. The default value for this HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMaxDefault." object should be set to lmpCcHelloIntervalMaxDefault."
::= { lmpControlChannelEntry 14 } ::= { lmpControlChannelEntry 12 }
lmpCcHelloIntervalNegotiated OBJECT-TYPE lmpCcHelloIntervalNegotiated OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Once the control channel is active, this object represents "Once the control channel is active, this object represents
the negotiated HelloInterval value." the negotiated HelloInterval value."
::= { lmpControlChannelEntry 15 } ::= { lmpControlChannelEntry 13 }
lmpCcHelloDeadInterval OBJECT-TYPE lmpCcHelloDeadInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloDeadInterval "This object specifies the value of the HelloDeadInterval
parameter. The default value for this object should be parameter. The default value for this object should be
set to lmpCcHelloDeadIntervalDefault." set to lmpCcHelloDeadIntervalDefault."
::= { lmpControlChannelEntry 16 } ::= { lmpControlChannelEntry 14 }
lmpCcHelloDeadIntervalMin OBJECT-TYPE lmpCcHelloDeadIntervalMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum value for the "This object specifies the minimum value for the
HelloDeadInterval parameter. The default value for this HelloDeadInterval parameter. The default value for this
object should be set to lmpCcHelloDeadIntervalMinDefault." object should be set to lmpCcHelloDeadIntervalMinDefault."
::= { lmpControlChannelEntry 17 } ::= { lmpControlChannelEntry 15 }
lmpCcHelloDeadIntervalMax OBJECT-TYPE lmpCcHelloDeadIntervalMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum value for the "This object specifies the maximum value for the
HelloDeadInterval parameter. The default value for this HelloDeadInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMaxDefault." object should be set to lmpCcHelloIntervalMaxDefault."
::= { lmpControlChannelEntry 18 } ::= { lmpControlChannelEntry 16 }
lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Once the control channel is active, this object represents "Once the control channel is active, this object represents
the negotiated HelloDeadInterval value." the negotiated HelloDeadInterval value."
::= { lmpControlChannelEntry 19 } ::= { lmpControlChannelEntry 17 }
lmpCcLastChange OBJECT-TYPE lmpCcLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the control channel entered "The value of sysUpTime at the time the control channel entered
its current operational state. If the current state was its current operational state. If the current state was
entered prior to the last re-initialization of the local entered prior to the last re-initialization of the local
network management subsystem, then this object contains a network management subsystem, then this object contains a
zero value." zero value."
::= { lmpControlChannelEntry 20 } ::= { lmpControlChannelEntry 18 }
lmpCcAdminStatus OBJECT-TYPE lmpCcAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of this control channel." "The desired operational status of this control channel."
::= { lmpControlChannelEntry 21 } ::= { lmpControlChannelEntry 19 }
lmpCcOperStatus OBJECT-TYPE lmpCcOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
configSnd(3), configSnd(3),
configRcv(4), configRcv(4),
active(5), active(5),
goingDown(6) goingDown(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this control channel "The actual operational status of this control channel."
interface." ::= { lmpControlChannelEntry 20 }
::= { 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. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1)." in a row can be changed if the status is active(1).
::= { lmpControlChannelEntry 23 } All read-create objects must have valid and consistent
values before the row can be activated."
::= { lmpControlChannelEntry 21 }
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
columnar object in the row." columnar object in the row."
::= { lmpControlChannelEntry 24 } DEFVAL { nonVolatile }
::= { lmpControlChannelEntry 22 }
-- End of lmpControlChannelTable -- End of lmpControlChannelTable
-- LMP Control Channel Performance Table -- LMP Control Channel Performance Table
lmpControlChannelPerfTable OBJECT-TYPE lmpControlChannelPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpControlChannelPerfEntry SYNTAX SEQUENCE OF LmpControlChannelPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 36, line 16 skipping to change at page 37, line 5
-- End of lmpControlChannelPerfTable -- End of lmpControlChannelPerfTable
-- LMP TE Link Table -- LMP TE Link Table
lmpTeLinkTable OBJECT-TYPE lmpTeLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkEntry SYNTAX SEQUENCE OF LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the TE link information." "This table specifies the LMP specific TE link information.
Overall TE link information is kept in three separate tables:
ifTable, for interface specific information, lmpTeLinkTable
for LMP specific information and teLinkTable for generic
TE link information. ifIndex is the common index to all
tables."
::= { lmpObjects 12 } ::= { lmpObjects 12 }
lmpTeLinkEntry OBJECT-TYPE lmpTeLinkEntry OBJECT-TYPE
SYNTAX LmpTeLinkEntry SYNTAX LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(200), 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
teLinkEntry is created. If a TE link entry in the ifTable is lmpTeLinkEntry is created. If a TE link entry in the ifTable
destroyed, then so is the corresponding entry in the is destroyed, then so is the corresponding entry in the
teLinkTable. The administrative status value is controlled lmpTeLinkTable. 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
contained in teLinkTable [TELINK-MIB]." contained in teLinkTable of the TE-LINK-STD-MIB MIB module."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrNodeId LmpNodeId, lmpTeLinkNbrRemoteNodeId LmpNodeId,
lmpTeLinkVerification TruthValue, lmpTeLinkVerification TruthValue,
lmpTeLinkFaultManagement TruthValue, lmpTeLinkFaultManagement TruthValue,
lmpTeLinkDwdm TruthValue, lmpTeLinkDwdm TruthValue,
lmpTeLinkOperStatus INTEGER, lmpTeLinkOperStatus INTEGER,
lmpTeLinkRowStatus RowStatus, lmpTeLinkRowStatus RowStatus,
lmpTeLinkStorageType StorageType lmpTeLinkStorageType StorageType
} }
lmpTeLinkNbrNodeId OBJECT-TYPE lmpTeLinkNbrRemoteNodeId OBJECT-TYPE
SYNTAX LmpNodeId SYNTAX LmpNodeId
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the TE link remote node. This value "This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation may be learned during control channel parameter negotiation
phase (in the Config message). Node ID address type must phase (in the Config message). Node ID address type must
be IPv4." be IPv4."
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
skipping to change at page 38, line 24 skipping to change at page 39, line 17
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. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1)." in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."
::= { 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
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile }
::= { lmpTeLinkEntry 7 } ::= { lmpTeLinkEntry 7 }
-- End of lmpTeLinkTable -- End of lmpTeLinkTable
lmpLinkVerificationInterval OBJECT-TYPE lmpLinkVerificationInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "ms"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the link verification "This object indicates how often the link verification
procedure is executed. The interval is in milliseconds. procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link A value of 0 is used to indicate that the link
verification procedure should not be executed. The verification procedure should not be executed. The
interval specified in this object should be large enough interval specified in this object should be large enough
to allow the verification procedure to be completed to allow the verification procedure to be completed
before the start of the next interval. before the start of the next interval.
skipping to change at page 39, line 35 skipping to change at page 40, line 32
"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 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 TruthValue,
lmpVerifyTransmissionRate Unsigned32, lmpVerifyTransmissionRate Unsigned32,
lmpVerifyWavelength 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
skipping to change at page 40, line 24 skipping to change at page 41, line 22
bearing links. It specifies the observation period used to bearing links. It specifies the observation period used to
detect a Test message at the remote node." detect a Test message at the remote node."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 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:
dccSectionOverheadBytes(0),
dccLineOverheadBytes(1),
j0Trace(2),
j1Trace(3),
j2Trace(4),
-- All encoding types: -- All encoding types:
payload(31) payload(0),
-- SONET/SDH encoding type:
dccSectionOverheadBytes(1),
dccLineOverheadBytes(2),
j0Trace(3),
j1Trace(4),
j2Trace(5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This defines the transport mechanism for the Test messages. The "This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx and "Link Management Protocol, RFC xxx and
SONET/SDH Encoding for Link Management Protocol (LMP) SONET/SDH Encoding for Link Management Protocol (LMP)
Test Messages, RFC xxx" 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] and [LMP-TEST] -- [LMP] and [LMP-TEST]
::= { lmpLinkVerificationEntry 3 } ::= { lmpLinkVerificationEntry 3 }
lmpVerifyAllLinks OBJECT-TYPE lmpVerifyAllLinks OBJECT-TYPE
SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the verification process checks "A value of true(2) for this object indicates that the
all entities or only the new entities that have been added to verification process checks all unallocated links, otherwise
this TE link." only the new ports or component links that have been added to
this TE link are verified."
::= { lmpLinkVerificationEntry 4 } ::= { lmpLinkVerificationEntry 4 }
lmpVerifyTransmissionRate OBJECT-TYPE lmpVerifyTransmissionRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the transmission rate of the data link over which "This is the transmission rate of the data link over which
the Test messages will be transmitted and is expressed in the Test messages will be transmitted and is expressed in
bytes per second." bytes per second."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC 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 }
lmpVerifyWavelength OBJECT-TYPE lmpVerifyWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "nm"
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
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
skipping to change at page 51, line 22 skipping to change at page 52, line 22
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a data-bearing link. An ifEntry with an ifIndex must exist a data-bearing link. An ifEntry with an ifIndex must exist
before the corresponding lmpDataLinkEntry is created. before the corresponding lmpDataLinkEntry is created.
If an entry representing the data-bearing link is destroyed in If an entry representing the data-bearing link is destroyed in
the ifTable, then so is the corresponding entry in the the ifTable, then so is the corresponding entry in the
lmpDataLinkTable. The administrative status value is lmpDataLinkTable. The administrative status value is
controlled from the ifEntry. The index to this table also controlled from the ifEntry. The index to this table also
used to get information in the componentLinkTable used to get information in the componentLinkTable
[TELINK-MIB]." of the TE-LINK-STD-MIB MIB module."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataLinkTable 1 } ::= { lmpDataLinkTable 1 }
LmpDataLinkEntry ::= SEQUENCE { LmpDataLinkEntry ::= SEQUENCE {
lmpDataLinkType INTEGER, lmpDataLinkType INTEGER,
lmpDataLinkAddressType InetAddressType, lmpDataLinkAddressType InetAddressType,
lmpDataLinkIpAddr InetAddress, lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress, lmpDataLinkRemoteIpAddress InetAddress,
lmpDataLinkRemoteIfId InterfaceIndexOrZero, lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataLinkEncodingType TeLinkEncodingType, lmpDataLinkEncodingType TeLinkEncodingType,
skipping to change at page 54, line 22 skipping to change at page 55, line 22
-- [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. None of the writable objects delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1)." in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."
::= { 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
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile }
::= { lmpDataLinkEntry 10 } ::= { lmpDataLinkEntry 10 }
-- End of lmpDataLinkTable -- End of lmpDataLinkTable
-- LMP Data Link Performance Table -- LMP Data Link Performance Table
lmpDataLinkPerfTable OBJECT-TYPE lmpDataLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataLinkPerfEntry SYNTAX SEQUENCE OF LmpDataLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 55, line 8 skipping to change at page 56, line 11
"This table specifies the data-bearing links LMP performance "This table specifies the data-bearing links LMP performance
counters." counters."
::= { lmpObjects 17 } ::= { lmpObjects 17 }
lmpDataLinkPerfEntry OBJECT-TYPE lmpDataLinkPerfEntry OBJECT-TYPE
SYNTAX LmpDataLinkPerfEntry SYNTAX LmpDataLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about "An entry in this table contains information about
the LMP performance counters for the data-bearing links." the LMP performance counters for the data-bearing links.
lmpDataLinkDiscontinuityTime is used to indicate potential
discontinuity for all counter objects in this table."
AUGMENTS { lmpDataLinkEntry } AUGMENTS { lmpDataLinkEntry }
::= { lmpDataLinkPerfTable 1 } ::= { lmpDataLinkPerfTable 1 }
LmpDataLinkPerfEntry ::= SEQUENCE { LmpDataLinkPerfEntry ::= SEQUENCE {
lmpDataLinkTestReceived Counter32, lmpDataLinkTestReceived Counter32,
lmpDataLinkTestSent Counter32, lmpDataLinkTestSent Counter32,
lmpDataLinkActiveTestSuccess Counter32, lmpDataLinkActiveTestSuccess Counter32,
lmpDataLinkActiveTestFailure Counter32, lmpDataLinkActiveTestFailure Counter32,
lmpDataLinkPassiveTestSuccess Counter32, lmpDataLinkPassiveTestSuccess Counter32,
lmpDataLinkPassiveTestFailure Counter32, lmpDataLinkPassiveTestFailure Counter32,
skipping to change at page 57, line 7 skipping to change at page 58, line 12
-- End of lmpDataLinkPerfTable -- End of lmpDataLinkPerfTable
-- Notification Configuration -- Notification Configuration
lmpNotificationMaxRate OBJECT-TYPE lmpNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the maximum number of "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.
This variable indicates the maximum number of
notifications issued per second. If events occur notifications issued per second. If events occur
more rapidly, the implementation may simply fail to more rapidly, the implementation may simply fail to
emit these notifications during that period, or may emit these notifications during that period, or may
queue them until an appropriate time. A value of 0 queue them until an appropriate time. A value of 0
means no throttling is applied and events may be means no throttling is applied and events may be
notified at the rate at which they occur. notified at the rate at which they occur.
Implementations should save the value of this object in Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { 0 } DEFVAL { 0 }
::= { lmpObjects 18 } ::= { lmpObjects 18 }
skipping to change at page 58, line 39 skipping to change at page 60, line 25
"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 Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot." persistent memory so that it survives restarts or reboot."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 23 } ::= { lmpObjects 23 }
-- Notifications -- Notifications
-- Link Property Mismatch Notifications -- Link Property Mismatch Notifications
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { teLinkRemoteIpAddr, OBJECTS { teLinkRemoteIpAddr,
teLinkIncomingIfId } teLinkIncomingIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a TE link property "This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link mismatch is detected on the node. The received remote TE link
id of the misconfigured TE link is represented by either id of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
the TE link is numbered or unnumbered. This notification the TE link is numbered or unnumbered. This notification
should not be sent unless lmpLinkPropertyNotificationsEnabled should not be sent unless lmpLinkPropertyNotificationsEnabled
is true. It is recommended that this notification be reported is true. It is recommended that this notification be reported
only the first time a mismatch is detected. Otherwise, for a only the first time a mismatch is detected. Otherwise, for a
given TE link, this notification can occur no more than once given TE link, this notification can occur no more than once
per verification interval." per verification interval (lmpLinkVerificationInterval)."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId } OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing link "This notification is generated when a data-bearing link
property mismatch is detected on the node. lmpDataLinkType property mismatch is detected on the node. lmpDataLinkType
is used to identify the local identifiers associated with is used to identify the local identifiers associated with
the data link (the data link interface index can be used the data link (the data link interface index can be used
to determine the TE link interface index as this to determine the TE link interface index as this
relationship is captured in the interface stack table). relationship is captured in the interface stack table).
The remote entity interface id is the remote entity The remote entity interface id is the remote entity
interface id received in the LinkSummary message. interface id received in the LinkSummary message.
This notification should not be sent unless This notification should not be sent unless
lmpLinkPropertyNotificationsEnabled is true. It is lmpLinkPropertyNotificationsEnabled is true. It is
recommended that this notification be reported only the recommended that this notification be reported only the
first time a mismatch is detected. Otherwise, for a given first time a mismatch is detected. Otherwise, for a given
data link, this notification can occur no more than once data link, this notification can occur no more than once
per verification interval." per verification interval (lmpLinkVerificationInterval)."
::= { 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 61, line 33 skipping to change at page 62, line 39
lmpDataLinkVerificationFailure NOTIFICATION-TYPE lmpDataLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { lmpDataLinkActiveOperStatus, OBJECTS { lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus } 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. For a given unless lmpDataLinkNotificationsEnabled is true. For a given
data link, this notification can occur no more than once per data link, this notification can occur no more than once per
verification interval." verification interval (lmpLinkVerificationInterval)."
::= { lmpNotifications 8 } ::= { lmpNotifications 8 }
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
lmpCompliances lmpCompliances
OBJECT IDENTIFIER ::= { lmpConformance 1 } OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpGroups lmpGroups
skipping to change at page 62, line 47 skipping to change at page 64, line 4
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"Support for notReady(3) and createAndWait(5) is "Support for notReady(3) and createAndWait(5) is
not required." not required."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpCcRemoteAddressType
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 lmpCcRemoteIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"Support for notReady(3) and createAndWait(5) is "Support for notReady(3) and createAndWait(5) is
skipping to change at page 66, line 47 skipping to change at page 68, line 4
OBJECT lmpCcUnderlyingIfIndex OBJECT lmpCcUnderlyingIfIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcIsIf OBJECT lmpCcIsIf
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcNbrNodeId OBJECT lmpCcNbrNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpRemoteCcAddressType
OBJECT lmpCcRemoteAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be "Only ipv4(1) and ipv6(2) address types need to be
supported for non point-to-point configurations." supported for non point-to-point configurations."
OBJECT lmpRemoteCcIpAddr OBJECT lmpCcRemoteIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
OBJECT lmpCcSetupRole OBJECT lmpCcSetupRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 68, line 36 skipping to change at page 69, line 41
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpVerifyAllLinks OBJECT lmpVerifyAllLinks
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpTeLinkTable -- lmpTeLinkTable
OBJECT lmpTeLinkNbrNodeId OBJECT lmpTeLinkNbrRemoteNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
procedure is enabled." procedure is enabled."
OBJECT 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(5) } SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION DESCRIPTION
"The testing(3) and init(4) state need not be supported." "The testing(3) and init(4) state need not be supported."
skipping to change at page 71, line 17 skipping to change at page 72, line 20
lmpOperStatus, lmpOperStatus,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpUnprotectedNotificationsEnabled, lmpUnprotectedNotificationsEnabled,
lmpNotificationMaxRate lmpNotificationMaxRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP node configuration." "Collection of objects that represent LMP node
configuration."
::= { lmpGroups 1 } ::= { lmpGroups 1 }
lmpControlChannelGroup OBJECT-GROUP lmpControlChannelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lmpNbrRetransmitInterval, lmpNbrRetransmitInterval,
lmpNbrRetryLimit, lmpNbrRetryLimit,
lmpNbrRetransmitDelta, lmpNbrRetransmitDelta,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpCcHelloIntervalDefault, lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin, lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax, lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault, lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin, lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax, lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId, lmpCcNbrNodeId,
lmpRemoteCcId, lmpCcRemoteId,
lmpRemoteCcAddressType, lmpCcRemoteAddressType,
lmpRemoteCcIpAddr, lmpCcRemoteIpAddr,
lmpCcSetupRole, lmpCcSetupRole,
lmpCcAuthentication, lmpCcAuthentication,
lmpCcHelloInterval, lmpCcHelloInterval,
lmpCcHelloIntervalMin, lmpCcHelloIntervalMin,
lmpCcHelloIntervalMax, lmpCcHelloIntervalMax,
lmpCcHelloIntervalNegotiated, lmpCcHelloIntervalNegotiated,
lmpCcHelloDeadInterval, lmpCcHelloDeadInterval,
lmpCcHelloDeadIntervalMin, lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax, lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated, lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus, lmpCcOperStatus,
lmpCcRowStatus, lmpCcRowStatus,
lmpCcStorageType, lmpCcStorageType,
lmpCcUpDownNotificationsEnabled lmpCcUpDownNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP interface "Objects which can be used to configure LMP interface."
configuration."
::= { lmpGroups 2 } ::= { lmpGroups 2 }
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 which can be used to configure control channels
interfaces." that are interfaces."
::= { lmpGroups 3 } ::= { lmpGroups 3 }
lmpCcIsNotInterfaceGroup OBJECT-GROUP lmpCcIsNotInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcUnderlyingIfIndex, OBJECTS { lmpCcUnderlyingIfIndex,
lmpCcIsIf, lmpCcIsIf,
lmpCcLastChange, lmpCcLastChange,
lmpCcAdminStatus lmpCcAdminStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are not "Objects which can be used to configure control channels
interfaces." that are not interfaces."
::= { lmpGroups 4 } ::= { lmpGroups 4 }
lmpLinkPropertyCorrelationGroup OBJECT-GROUP lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyNotificationsEnabled } OBJECTS { lmpLinkPropertyNotificationsEnabled }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects used to configure 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,
lmpVerifyTransmissionRate, lmpVerifyTransmissionRate,
lmpVerifyWavelength, lmpVerifyWavelength,
lmpDataLinkNotificationsEnabled lmpDataLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects that represent the link
verification procedure." verification procedure configuration."
::= { lmpGroups 6 } ::= { lmpGroups 6 }
lmpPerfGroup OBJECT-GROUP lmpPerfGroup OBJECT-GROUP
OBJECTS { lmpCcInOctets, OBJECTS { lmpCcInOctets,
lmpCcInDiscards, lmpCcInDiscards,
lmpCcInErrors, lmpCcInErrors,
lmpCcOutOctets, lmpCcOutOctets,
lmpCcOutDiscards, lmpCcOutDiscards,
lmpCcOutErrors, lmpCcOutErrors,
lmpCcConfigReceived, lmpCcConfigReceived,
skipping to change at page 75, line 15 skipping to change at page 76, line 19
lmpDataLinkTestReceived, lmpDataLinkTestReceived,
lmpDataLinkTestSent, lmpDataLinkTestSent,
lmpDataLinkActiveTestSuccess, lmpDataLinkActiveTestSuccess,
lmpDataLinkActiveTestFailure, lmpDataLinkActiveTestFailure,
lmpDataLinkPassiveTestSuccess, lmpDataLinkPassiveTestSuccess,
lmpDataLinkPassiveTestFailure, lmpDataLinkPassiveTestFailure,
lmpDataLinkDiscontinuityTime lmpDataLinkDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for providing performance "Collection of objects used to provide performance
information about LMP interfaces and data-bearing links." information about LMP interfaces and data-bearing links."
::= { lmpGroups 7 } ::= { lmpGroups 7 }
lmpTeLinkGroup OBJECT-GROUP lmpTeLinkGroup OBJECT-GROUP
OBJECTS { lmpTeLinkNbrNodeId, OBJECTS { lmpTeLinkNbrRemoteNodeId,
lmpTeLinkVerification, lmpTeLinkVerification,
lmpTeLinkFaultManagement, lmpTeLinkFaultManagement,
lmpTeLinkDwdm, lmpTeLinkDwdm,
lmpTeLinkOperStatus, lmpTeLinkOperStatus,
lmpTeLinkRowStatus, lmpTeLinkRowStatus,
lmpTeLinkStorageType, lmpTeLinkStorageType,
lmpTeLinkNotificationsEnabled lmpTeLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for TE link configuration." "Objects which can be used to configure TE links."
::= { lmpGroups 8 } ::= { lmpGroups 8 }
lmpDataLinkGroup OBJECT-GROUP lmpDataLinkGroup OBJECT-GROUP
OBJECTS { lmpDataLinkType, OBJECTS { lmpDataLinkType,
lmpDataLinkAddressType, lmpDataLinkAddressType,
lmpDataLinkIpAddr, lmpDataLinkIpAddr,
lmpDataLinkRemoteIpAddress, lmpDataLinkRemoteIpAddress,
lmpDataLinkRemoteIfId, lmpDataLinkRemoteIfId,
lmpDataLinkEncodingType, lmpDataLinkEncodingType,
lmpDataLinkActiveOperStatus, lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus, lmpDataLinkPassiveOperStatus,
lmpDataLinkRowStatus, lmpDataLinkRowStatus,
lmpDataLinkStorageType lmpDataLinkStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for data-bearing link "Collection of objects that represent data-bearing link
configuration." configuration."
::= { lmpGroups 9 } ::= { lmpGroups 9 }
lmpNotificationGroup NOTIFICATION-GROUP lmpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { lmpTeLinkPropertyMismatch, NOTIFICATIONS { lmpTeLinkPropertyMismatch,
lmpDataLinkPropertyMismatch, lmpDataLinkPropertyMismatch,
lmpUnprotected, lmpUnprotected,
lmpControlChannelUp, lmpControlChannelUp,
lmpControlChannelDown, lmpControlChannelDown,
lmpTeLinkDegraded, lmpTeLinkDegraded,
lmpTeLinkNotDegraded, lmpTeLinkNotDegraded,
lmpDataLinkVerificationFailure } lmpDataLinkVerificationFailure }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications defined in this module."
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 intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
skipping to change at page 76, line 45 skipping to change at page 77, line 47
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can proprietary rights by implementers or users of this specification can
be obtained from 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.
By submitting this Internet Draft, we certify that any applicable
patent or other IPR claims of which we are aware have been disclosed,
in accordance with RFC 3667.
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 environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 78, line 5 skipping to change at page 79, line 13
rights to 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. IANA Considerations
13.1. Normative References Each of the following "IANA Considerations" subsections requests IANA
for a new assignment. New assignments can only be made via a
Standards Action as specified in [RFC2434].
13.1. IANA Considerations for lmp ifType
The IANA is requested to assign TBD ifType for LMP interfaces.
13.2. IANA Considerations for LMP-MIB
LMP-MIB should be rooted under the transmission subtree. The IANA is
requested to assign { transmission TBD } to the LMP-MIB module
specified in this document. The IANA is requested to use same number
as the lmp ifType.
14. References
14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing
an IANA Considerations Section in RFCs", RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
skipping to change at page 78, line 39 skipping to change at page 80, line 23
Shoenwaelder, J., "Textual Conventions for Internet Shoenwaelder, J., "Textual Conventions for Internet
Network Addresses", RFC 3291, May 2002. Network Addresses", RFC 3291, May 2002.
[RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K., Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y., Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, B., Saha, D., Sharma, V., Swallow, G., and Tang, B.,
"Generalized MPLS Signaling Functional Description", "Generalized MPLS Signaling Functional Description",
RFC 3471, January 2003. RFC 3471, January 2003.
[RFC3667] Bradner, S., "IETF Rights in Contributions",
RFC 3667, February 2004.
[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-04.txt>, September 2003. <draft-ietf-mpls-telink-mib-06.txt>, February 2004.
[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-10.txt>,
March 2003. October 2003.
[LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding [LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding
for Link Management (LMP) Test Messages", Internet for Link Management (LMP) Test Messages", Internet
Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-03.txt>, Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt>,
May 2003. December 2003.
13.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
14. Authors' Addresses 15. 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
Email: sudheer@ieee.org Calient Networks, Inc. Email: sudheer@ieee.org Calient Networks, Inc.
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Email: evan@calient.net Email: evan@calient.net
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 16. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and 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 included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the 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 Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. 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 are provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
OR FITNESS FOR A PARTICULAR PURPOSE. INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY 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/