draft-ietf-ccamp-lmp-mib-05.txt   draft-ietf-ccamp-lmp-mib-06.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
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
April 2003 May 2003
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-05.txt draft-ietf-ccamp-lmp-mib-06.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 8 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 4 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 5 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 5
6.1. Summary of LMP MIB . . . . . . . . . . . . . . . . . . . . . . 6 6.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Brief Description of MIB Objects . . . . . . . . . . . . . . . 6 6.2. lmpControlChannelTable . . . . . . . . . . . . . . . . . . . . 5
7.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 5
7.2. lmpControlChannelTable . . . . . . . . . . . . . . . . . . . . 6 6.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 5
7.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 7 6.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 5
7.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 7 6.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 5
7.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 7 6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5
7.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 7 6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 6
7.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 7 7. Example of LMP Control Channel Interface Setup . . . . . . . . . 6
7.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 7 8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8
8. Example of LMP Control Channel Interface Setup . . . . . . . . 7 8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9
9. Application of the Interfaces Group to LMP . . . . . . . . . . 10 9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11
9.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 10 10. Intellectual Property Considerations . . . . . . . . . . . . . . 74
10. Link Management Protocol MIB Definitions . . . . . . . . . . . 12 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 74
11. Intellectual Property Considerations . . . . . . . . . . . . . 75 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 75
12. Security Considerations . . . . . . . . . . . . . . . . . . . . 75 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 76 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 75
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 76 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 76
14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 76 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76
14.2 Informative References . . . . . . . . . . . . . . . . . . . . 78 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 77
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 79
16. 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).
skipping to change at page 3, line 17 skipping to change at page 3, line 17
Current work is underway in the IETF to specify a suite of protocols Current work is underway in the IETF to specify a suite of protocols
to be used as a common control plane and a separate common measure- to be used as a common control plane and a separate common measure-
ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link
Management Protocol [LMP], which primary purpose is to manage traffic Management Protocol [LMP], which primary purpose is to manage traffic
engineering (TE) links, is one of the key components of this stan- engineering (TE) links, is one of the key components of this stan-
dardization activity. Primary goals of LMP are the maintenance of the dardization activity. Primary goals of LMP are the maintenance of the
control channel connectivity, correlation of link properties, verifi- control channel connectivity, correlation of link properties, verifi-
cation of data-bearing links and detection and isolation of link cation of data-bearing links and detection and isolation of link
faults. faults.
We describe in this document a MIB that can be used to manage LMP We describe in this document a MIB module that can be used to manage
implementations. This MIB covers both configuration and performance LMP implementations. This MIB module covers both configuration and
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
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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 multiplex-
ing capability (see [LMP] for distinction between port and component ing capability (see [LMP] for distinction between port and component
link). 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. The SNMP Management Framework 4. Feature Checklist
The SNMP Management Framework presently consists of five major compo-
nents:
- An overall architecture, described in RFC 2571 [RFC2571].
- Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
- Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
- A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
5. Feature Checklist
The Link Management protocol MIB (LMP-MIB) is designed to satisfy the The Link Management Protocol MIB module (LMP-MIB) is designed to sat-
following requirements and constraints: isfy the following requirements and constraints:
- The MIB supports the enabling and disabling of LMP capability - The MIB module supports the enabling and disabling of LMP
on LMP capable interfaces of a photonic switch, optical capability on LMP capable interfaces of a photonic switch,
cross-connect or router. optical cross-connect or router.
- The MIB 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.
- The MIB is used to express the mapping between local and remote - The MIB module is used to express the mapping between local and
TE links, as well as local and remote interface identifiers for remote TE links, as well as local and remote interface identifiers
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 goes hand-in-hand with the TE Link MIB [TELINK- Note that the LMP MIB module goes hand-in-hand with the TE Link MIB
MIB]. The TE link table, which is used to associate data-bearing module [TELINK-MIB]. The TE link table, which is used to associate
links to TE links, is defined in the TE Link MIB. The TE link table data-bearing links to TE links, is defined in the TE Link MIB. The TE
in the LMP MIB contains TE link information specific to LMP. link table in the LMP MIB module contains TE link information spe-
cific to LMP.
6. Outline 5. Outline
Configuring LMP through an optical device involves the following Configuring LMP through an optical device involves the following
steps: steps:
- Enabling LMP on LMP capable interfaces through control channel - Enabling LMP on LMP capable interfaces through control channel
configuration. configuration.
- Optionally specifying link verification parameters. - Optionally specifying link verification parameters.
- Configuring the data-bearing links and associating them to the - Configuring the data-bearing links and associating them to the
appropriate TE link (this association is stored in the appropriate TE link (this association is stored in the
ifStackTable of the Interfaces Group MIB). ifStackTable of the Interfaces Group MIB).
TE links are managed by the control channels that run between the TE links are managed by the control channels that run between the
same pair of nodes (LMP adjacency). same pair of nodes (LMP adjacency).
6.1. Summary of LMP MIB 6. Brief Description of MIB Objects
The MIB objects for performing these actions consist of the following
tables:
- The remote node table (lmpNbrTable) is used to identify the pair
of nodes that exchange LMP messages over control channels.
- The control channel table (lmpControlChannelTable) is used
for enabling the LMP protocol on LMP-capable interfaces.
- The control channel performance table
(lmpControlChannelPerfTable) is used for collecting
LMP performance counts on a per-control channel basis.
- The TE link table (lmpTeLinkTable) is used for
specifying LMP information associated with TE links.
- The link verification table (lmpLinkVerificationTable) is used for
configuring the LMP link verification parameters of TE links.
- The TE link performance table (lmpTeLinkPerfTable) is used for
collecting LMP performance counts on a per-TE link basis.
- The data-bearing link table (lmpDataLinkTable) is used to
specify the data-bearing links that are associated with TE links.
- The data-bearing link performance table
(lmpDataLinkPerfTable) is used for collecting LMP
performance counts on data-bearing links.
These tables are described in the subsequent sections.
7. Brief Description of MIB Objects
Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- Sections 6.1-6.8 describe objects pertaining to LMP. The MIB objects
faces. Section 7.4 to 7.7 describes objects for specifying TE links were derived from the LMP document [LMP].
and data-bearing links. The MIB objects were derived from the LMP
document [LMP].
7.1. lmpNbrTable 6.1. lmpNbrTable
This table identifies the pairs of nodes on which LMP is enabled. The remote node table is used to identify the pair of nodes that
exchange LMP messages over control channels.
7.2. lmpControlChannelTable 6.2. lmpControlChannelTable
This table represents the interfaces that are LMP capable (i.e. capa- The control channel table is used for enabling the LMP protocol on
ble of transmitting LMP messages). A photonic switch, optical cross- LMP-capable interfaces. A photonic switch, optical cross-connect or
connect, or router creates an entry in this table for every LMP capa- router creates an entry in this table for every LMP capable interface
ble interface on that device. in that device.
7.3. lmpControlChannelPerfTable 6.3. lmpControlChannelPerfTable
This table contains the objects to measure the LMP performance of LMP The control channel performance table is used for collecting LMP per-
capable interfaces and is an AUGMENT to the lmpControlChannelTable. formance counts on a per-control channel basis. This table is an AUG-
MENT to the lmpControlChannelTable.
7.4. lmpTeLinkTable 6.4. lmpTeLinkTable
This table represents the TE link information specific to LMP. The TE link table is used for specifying LMP information associated
with TE links.
7.5. lmpLinkVerificationTable 6.5. lmpLinkVerificationTable
This table augments the lmpTeLinkTable and represents the link veri- The link verification table is used for configuring the LMP link ver-
fication parameters associated with the TE links. ification parameters of TE links. This table is an AUGMENT to the
lmpTeLinkTable.
7.6. lmpTeLinkPerfTable 6.6. lmpTeLinkPerfTable
This table contains the objects to measure the LMP performance of LMP The TE link performance table is used for collecting LMP performance
capable interfaces and is an AUGMENT to the lmpTeLinkTable. counts on a per-TE link basis. This table is an AUGMENT to the
lmpTeLinkTable.
7.7. lmpDataLinkTable 6.7. lmpDataLinkTable
The data-bearing link table enumerates the data-bearing links that The data-bearing link table is used to specify the data-bearing links
are associated with each TE link. that are associated with TE links.
7.8. lmpDataLinkPerfTable 6.8. lmpDataLinkPerfTable
This table augments the lmpDataLinkTable. It contains the objects to The data-bearing link performance table is used for collecting LMP
measure the LMP performance of data-bearing links. performance counts on data-bearing links.
8. Example of LMP Control Channel Setup 7. Example of LMP Control Channel Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in section 10 to set up an LMP control channel. objects described in section 10 to set up an LMP control channel.
While this example is not meant to illustrate every nuance of the While this example is not meant to illustrate every nuance of the
MIB, it is intended as an aid to understanding some of the key MIB module, it is intended as an aid to understanding some of the
concepts. It is meant to be read after going through the MIB itself. key concepts. It is meant to be read after going through the MIB
itself.
Suppose that one would like to form an LMP adjacency between two Suppose that one would like to form an LMP adjacency between two
nodes using two control channels. Suppose also that there are nodes using two control channels. Suppose also that there are
three data-bearing links. We also assume that the data-bearing three data-bearing links. We also assume that the data-bearing
links are ports (lambdas). We also assume that the link links are ports (lambdas). We also assume that the link
verification procedure is not enabled. The following example verification procedure is not enabled. The following example
illustrates which rows and corresponding objects might be created illustrates which rows and corresponding objects might be created
to accomplish this. to accomplish this.
First, LMP must be enabled between the pair of nodes. First, LMP must be enabled between the pair of nodes.
In lmpNbrTable: In lmpNbrTable:
{ {
lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1
lmpNbrAdminStatus = up(1), lmpNbrAdminStatus = up(1),
lmpNbrRowStatus = createAndGo(4) lmpNbrRowStatus = createAndGo(4),
lmpNbrStorageType = nonVolatile(3)
} }
Then, the control channels must be set up. These are created in Then, the control channels must be set up. These are created in
the lmpControlChannelTable. the lmpControlChannelTable.
In lmpControlChannelTable: In lmpControlChannelTable:
{ {
lmpCcId = 1, lmpCcId = 1,
lmpCcUnderlyingIfIndex = 1, lmpCcUnderlyingIfIndex = 1,
lmCcIsIf = false(1), lmCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4),
lmpCcStorageType = nonVolatile(3)
} }
{ {
lmpCcId = 2, lmpCcId = 2,
lmpCcUnderlyingIfIndex = 2, lmpCcUnderlyingIfIndex = 2,
lmCcIsIf = false(1), lmCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4),
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,
lmpDataLinkNumberingType = unnumbered(1), lmpDataLinkAddressType = unnumbered(1),
lmpDataLinkIpAddr = ''H,
lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 47, lmpDataLinkRemoteIfId = 47,
lmpDataLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3)
} }
{ {
ifIndex = 43, ifIndex = 43,
lmpDataLinkNumberingType = unnumbered(1), lmpDataLinkAddressType = unnumbered(1),
lmpDataLinkIpAddr = ''H,
lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 42, lmpDataLinkRemoteIfId = 42,
lmpDataLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3)
} }
{ {
ifIndex = 44, ifIndex = 44,
lmpDataLinkNumberingType = unnumbered(1), lmpDataLinkAddressType = unnumbered(1),
lmpDataLinkIpAddr = ''H,
lmpDataLinkRemoteIpAddress = ''H,
lmpDataLinkRemoteIfId = 48, lmpDataLinkRemoteIfId = 48,
lmpDataLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4),
lmpDataLinkStorageType = nonVolatile(3)
} }
Note that the data-bearing link type (lmpDataLinkType) does Note that the data-bearing link type (lmpDataLinkType) does
not need to be provisioned as it is automatically populated by the not need to be provisioned as it is automatically populated by the
node. The definition of the protection role (primary or node. The definition of the protection role (primary or
secondary) for the data-bearing links is stored in the secondary) for the data-bearing links is stored in the
componentLinkTable of the TE Link MIB [TELINK-MIB]. componentLinkTable of the TE Link MIB module [TELINK-MIB].
Then, a TE link is created as an ifEntry with ifType teLink in Then, a TE link is created as an ifEntry with ifType teLink in
the ifTable. the ifTable.
Once the TE link is created in the ifTable, a TE link entry Once the TE link is created in the ifTable, a TE link entry
is created in the LMP MIB to specify TE link information specific is created in the LMP MIB module to specify TE link information
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, lmpTeLinkBitRate = 100000,
lmpTeLinkWavelength = 0, lmpTeLinkWavelength = 0,
lmpTeLinkRowStatus = createAndGo(4) lmpTeLinkRowStatus = createAndGo(4),
lmpTeLinkStorageType = nonVolatile(3)
} }
The association between the data-bearing links and the TE links is The association between the data-bearing links and the TE links is
stored in the ifStackTable [IF-MIB]. stored in the ifStackTable [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 may be created in the teLinkTable of TE Link MIB module
[TELINK-MIB]. [TELINK-MIB].
9. Application of the Interfaces Group to LMP 8. Application of the Interfaces Group to LMP
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing LMP control channels extensions to the Interfaces Group for managing LMP control channels
that are modeled as interfaces. If the control channel as defined in that are modeled as interfaces. If the control channel as defined in
the lmpControlChannelTable is modeled as an ifEntry, then the the lmpControlChannelTable is modeled as an ifEntry, then the
following definition applies. An lmpControlChannelTable entry is following definition applies. An lmpControlChannelTable entry is
designated as being represented as an Interfaces MIB ifEntry if the designated as being represented as an Interfaces MIB ifEntry if the
lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this
case, the control channel SHOULD be modeled as an ifEntry and case, the control channel SHOULD be modeled as an ifEntry and
skipping to change at page 10, line 48 skipping to change at page 9, line 35
+----------------------------------------+ +----------------------------------------+
| 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.
9.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 12, line 22 skipping to change at page 11, line 9
ifHCOutOctets The 64-bit version of ifOutOctets; supported if ifHCOutOctets The 64-bit version of ifOutOctets; supported if
required by the compliance statements in [RFC2863]. required by the compliance statements in [RFC2863].
ifAlias The non-volatile 'alias' name for the interface as ifAlias The non-volatile 'alias' name for the interface as
specified by a network manager. specified by a network manager.
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [RFC2863]. See [RFC2863].
10. LMP MIB 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 mib-2, 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
skipping to change at page 12, line 44 skipping to change at page 11, line 31
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 teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-MIB; FROM TE-LINK-STD-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200304181200Z" -- 18 April 2003 12:00:00 EST LAST-UPDATED "200305211200Z" -- 21 May 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@avici.com
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
"This MIB contains managed object definitions for the "Copyright (C) 2003 The Internet Society. This version of
Link Management Protocol (LMP) as the MIB module is part of RFC XXXX; see the RFC itself
defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., for full legal notices.
Rekhter, Y., Berger, L., Saha, D., Basak, D.,
Sandick, H., Zinin, A.,Rajagopalan, B., and This MIB module contains managed object definitions for
Ramamoorthi, S., Link Management Protocol, the Link Management Protocol (LMP) as
Internet Draft <draft-ietf-ccamp-lmp-08.txt>, defined in 'Link Management Protocol'."
March 2003."
-- Revision history. -- Revision history.
REVISION REVISION
"200304181200Z" -- 18 April 2003 12:00:00 EST "200305211200Z" -- 21 May 2003 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC Editor)" "Initial version published as RFC xxxx (to be assigned by RFC
::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can be used Editor)"
-- in the interim) ::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can
-- be used in the interim)
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 14, line 39 skipping to change at page 13, line 29
"The actual operational status of LMP on the node." "The actual operational status of LMP on the node."
::= { lmpObjects 2 } ::= { lmpObjects 2 }
-- LMP Neighbor Table -- LMP Neighbor Table
lmpNbrTable OBJECT-TYPE lmpNbrTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpNbrEntry SYNTAX SEQUENCE OF LmpNbrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the neighbor node(s) to which control channels "This table specifies the neighbor node(s) to which control
may be established." channels may be established."
::= { lmpObjects 3 } ::= { lmpObjects 3 }
lmpNbrEntry OBJECT-TYPE lmpNbrEntry OBJECT-TYPE
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 }
skipping to change at page 15, line 38 skipping to change at page 14, line 26
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."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [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."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [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
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."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP to this remote node." "The desired operational status of LMP to this remote node."
::= { lmpNbrEntry 3 } ::= { lmpNbrEntry 3 }
skipping to change at page 17, line 20 skipping to change at page 16, line 15
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."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpObjects 4 } ::= { lmpObjects 4 }
lmpCcHelloIntervalDefaultMin OBJECT-TYPE lmpCcHelloIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin." for lmpCcHelloIntervalMin."
skipping to change at page 17, line 48 skipping to change at page 16, line 45
"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."
::= { 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 to "This object specifies the default HelloDeadInterval parameter
use in the Hello protocol keep-alive phase. It indicates how long to use in the Hello protocol keep-alive phase. It indicates
a device should wait before declaring the control channel dead. how long a device should wait before declaring the control
channel dead. The HelloDeadInterval parameter should be at
The HelloDeadInterval parameter should be at least three times the least three times the value of HelloInterval. It is used as
value of HelloInterval. It is used as a default value for a default value for lmpCcHelloDeadInterval."
lmpCcHelloDeadInterval."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpObjects 7 } ::= { lmpObjects 7 }
lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin." for lmpCcHelloDeadIntervalMin."
skipping to change at page 18, line 48 skipping to change at page 17, line 44
DESCRIPTION DESCRIPTION
"This table specifies LMP control channel information." "This table specifies LMP control channel information."
::= { lmpObjects 10 } ::= { lmpObjects 10 }
lmpControlChannelEntry OBJECT-TYPE lmpControlChannelEntry OBJECT-TYPE
SYNTAX LmpControlChannelEntry SYNTAX LmpControlChannelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every control channel. Whenever a new entry is created with lmpCcIsIf every control channel. Whenever a new entry is created with
set to true(2), then a corresponding entry is created in ifTable as lmpCcIsIf set to true(2), then a corresponding entry is
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 InetAddress,
lmpRemoteCcId Unsigned32, lmpRemoteCcId Unsigned32,
lmpRemoteCcIpAddrType 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,
lmpCcHelloDeadIntervalMin LmpInterval, lmpCcHelloDeadIntervalMin LmpInterval,
lmpCcHelloDeadIntervalMax LmpInterval, lmpCcHelloDeadIntervalMax LmpInterval,
lmpCcHelloDeadIntervalNegotiated LmpInterval, lmpCcHelloDeadIntervalNegotiated LmpInterval,
lmpCcLastChange TimeTicks, lmpCcLastChange TimeTicks,
lmpCcAdminStatus INTEGER, lmpCcAdminStatus INTEGER,
lmpCcOperStatus INTEGER, lmpCcOperStatus INTEGER,
lmpCcRowStatus RowStatus, lmpCcRowStatus RowStatus,
lmpCcStorageType StorageType lmpCcStorageType StorageType
} }
lmpCcId OBJECT-TYPE lmpCcId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the local control channel identifier." "This value represents the local control channel identifier.
The control channel identifier is a non-zero 32 bit number."
::= { 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. the "This value represents the underlying interface index, i.e.
interface index of the interface over which the LMP interface the interface index of the interface over which the LMP
will transmit its traffic. If set to 0, then the control channel interface will transmit its traffic. If set to 0, then the
is not associated with any underlying interface. If the control control channel is not associated with any underlying
channel is not associated with an underlying interface, the control interface. If the control channel is not associated with an
channel's operational status must not be up(1), nor should the underlying interface, the control channel's operational
control channel forward or receive traffic." status must not be up(1), nor should the control channel
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 "Denotes whether or not this control channel corresponds to
an interface represented in the interfaces group table." an interface represented in the interfaces group table."
::= { lmpControlChannelEntry 3 } ::= { lmpControlChannelEntry 3 }
skipping to change at page 20, line 31 skipping to change at page 19, line 31
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. The Node ID
address type must be IPv4." 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. It is "This value represents the remote control channel identifier
determined during the negotiation phase. A value (32 bit number). It is determined during the negotiation
of zero means that the remote control channel identifier has not phase. A value of zero means that the remote control channel
yet been learnt." identifier has not yet been learnt."
::= { lmpControlChannelEntry 5 } ::= { lmpControlChannelEntry 5 }
lmpRemoteCcIpAddrType OBJECT-TYPE lmpRemoteCcAddressType 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 type. "This value represents the remote control channel IP address
In point-to-point configuration, this value can be set to type. In point-to-point configuration, this value can be set
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 IP address for "This value represents the remote control channel Internet
non point-to-point configuration. For point-to-point configuration, address for non point-to-point configuration. For point-to-
this value can be set to null." point configuration, the 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 of this "The role that this node should take during establishment
control channel. An active node will initiate establishment. A of this control channel. An active node will initiate
passive node will wait for the remote node to initiate. A pair establishment. A passive node will wait for the remote node
of nodes that both take the passive role will never establish to initiate. A pair of nodes that both take the passive role
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 should use
authentication." authentication."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpControlChannelEntry 9 } ::= { lmpControlChannelEntry 9 }
lmpCcHelloInterval OBJECT-TYPE lmpCcHelloInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloInterval "This object specifies the value of the HelloInterval
parameter. The default value for this object should be parameter. The default value for this object should be
set to lmpCcHelloIntervalDefault." set to lmpCcHelloIntervalDefault."
skipping to change at page 24, line 31 skipping to change at page 23, line 37
-- 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
"This table specifies LMP control channel performance counters." "This table specifies LMP control channel performance
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."
AUGMENTS { lmpControlChannelEntry } AUGMENTS { lmpControlChannelEntry }
skipping to change at page 26, line 49 skipping to change at page 26, line 8
"The total number of LMP message octets transmitted out of "The total number of LMP message octets transmitted out of
the control channel." the control channel."
::= { lmpControlChannelPerfEntry 4 } ::= { lmpControlChannelPerfEntry 4 }
lmpCcOutDiscards OBJECT-TYPE lmpCcOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outbound packets which were chosen to be "The number of outbound packets which were chosen to be
discarded even though no errors had been detected to prevent discarded even though no errors had been detected to
their being transmitted. One possible reason for discarding prevent their being transmitted. One possible reason
such a packet could be to free up buffer space." for discarding such a packet could be to free up buffer
space."
::= { lmpControlChannelPerfEntry 5 } ::= { lmpControlChannelPerfEntry 5 }
lmpCcOutErrors OBJECT-TYPE lmpCcOutErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outbound packets that could not be "The number of outbound packets that could not be
transmitted because of errors." transmitted because of errors."
::= { lmpControlChannelPerfEntry 6 } ::= { lmpControlChannelPerfEntry 6 }
skipping to change at page 29, line 30 skipping to change at page 28, line 40
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerify messages that "This object counts the number of BeginVerify messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 18 } ::= { lmpControlChannelPerfEntry 18 }
lmpCcBeginVerifyAckReceived OBJECT-TYPE lmpCcBeginVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that
been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 19 } ::= { lmpControlChannelPerfEntry 19 }
lmpCcBeginVerifyAckSent OBJECT-TYPE lmpCcBeginVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that
been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 20 } ::= { lmpControlChannelPerfEntry 20 }
lmpCcBeginVerifyNackReceived OBJECT-TYPE lmpCcBeginVerifyNackReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that
been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 21 } ::= { lmpControlChannelPerfEntry 21 }
lmpCcBeginVerifyNackSent OBJECT-TYPE lmpCcBeginVerifyNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that
been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 22 } ::= { lmpControlChannelPerfEntry 22 }
lmpCcEndVerifyReceived OBJECT-TYPE lmpCcEndVerifyReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that have "This object counts the number of EndVerify messages that have
been received on this control channel." been received on this control channel."
::= { lmpControlChannelPerfEntry 23 } ::= { lmpControlChannelPerfEntry 23 }
skipping to change at page 30, line 46 skipping to change at page 30, line 6
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that "This object counts the number of EndVerify messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 25 } ::= { lmpControlChannelPerfEntry 25 }
lmpCcEndVerifyAckReceived OBJECT-TYPE lmpCcEndVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that
been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 26 } ::= { lmpControlChannelPerfEntry 26 }
lmpCcEndVerifyAckSent OBJECT-TYPE lmpCcEndVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that
been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 27 } ::= { lmpControlChannelPerfEntry 27 }
lmpCcTestStatusSuccessReceived OBJECT-TYPE lmpCcTestStatusSuccessReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 28 } ::= { lmpControlChannelPerfEntry 28 }
lmpCcTestStatusSuccessSent OBJECT-TYPE lmpCcTestStatusSuccessSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 29 } ::= { lmpControlChannelPerfEntry 29 }
lmpCcTestStatusSuccessRetransmit OBJECT-TYPE lmpCcTestStatusSuccessRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that "This object counts the number of TestStatusSuccess messages
have been retransmitted over this control channel." that have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 30 } ::= { lmpControlChannelPerfEntry 30 }
lmpCcTestStatusFailureReceived OBJECT-TYPE lmpCcTestStatusFailureReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 31 } ::= { lmpControlChannelPerfEntry 31 }
lmpCcTestStatusFailureSent OBJECT-TYPE lmpCcTestStatusFailureSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 32 } ::= { lmpControlChannelPerfEntry 32 }
lmpCcTestStatusFailureRetransmit OBJECT-TYPE lmpCcTestStatusFailureRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that "This object counts the number of TestStatusFailure messages
have been retransmitted over this control channel." that have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 33 } ::= { lmpControlChannelPerfEntry 33 }
lmpCcTestStatusAckReceived OBJECT-TYPE lmpCcTestStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 34 } ::= { lmpControlChannelPerfEntry 34 }
lmpCcTestStatusAckSent OBJECT-TYPE lmpCcTestStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 35 } ::= { lmpControlChannelPerfEntry 35 }
lmpCcLinkSummaryReceived OBJECT-TYPE lmpCcLinkSummaryReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that have "This object counts the number of LinkSummary messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 36 } ::= { lmpControlChannelPerfEntry 36 }
lmpCcLinkSummarySent OBJECT-TYPE lmpCcLinkSummarySent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that have "This object counts the number of LinkSummary messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 37 } ::= { lmpControlChannelPerfEntry 37 }
lmpCcLinkSummaryRetransmit OBJECT-TYPE lmpCcLinkSummaryRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that "This object counts the number of LinkSummary messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 38 } ::= { lmpControlChannelPerfEntry 38 }
lmpCcLinkSummaryAckReceived OBJECT-TYPE lmpCcLinkSummaryAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have "This object counts the number of LinkSummaryAck messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 39 } ::= { lmpControlChannelPerfEntry 39 }
lmpCcLinkSummaryAckSent OBJECT-TYPE lmpCcLinkSummaryAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have "This object counts the number of LinkSummaryAck messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 40 } ::= { lmpControlChannelPerfEntry 40 }
lmpCcLinkSummaryNackReceived OBJECT-TYPE lmpCcLinkSummaryNackReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have "This object counts the number of LinkSummaryNack messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 41 } ::= { lmpControlChannelPerfEntry 41 }
lmpCcLinkSummaryNackSent OBJECT-TYPE lmpCcLinkSummaryNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have "This object counts the number of LinkSummaryNack messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 42 } ::= { lmpControlChannelPerfEntry 42 }
lmpCcChannelStatusReceived OBJECT-TYPE lmpCcChannelStatusReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 43 } ::= { lmpControlChannelPerfEntry 43 }
lmpCcChannelStatusSent OBJECT-TYPE lmpCcChannelStatusSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 44 } ::= { lmpControlChannelPerfEntry 44 }
lmpCcChannelStatusRetransmit OBJECT-TYPE lmpCcChannelStatusRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages
been retransmitted on this control channel." that have been retransmitted on this control channel."
::= { lmpControlChannelPerfEntry 45 } ::= { lmpControlChannelPerfEntry 45 }
lmpCcChannelStatusAckReceived OBJECT-TYPE lmpCcChannelStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusAck messages that have "This object counts the number of ChannelStatusAck messages
been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 46 } ::= { lmpControlChannelPerfEntry 46 }
lmpCcChannelStatusAckSent OBJECT-TYPE lmpCcChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages
been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 47 } ::= { lmpControlChannelPerfEntry 47 }
lmpCcChannelStatusReqReceived OBJECT-TYPE lmpCcChannelStatusReqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 48 } ::= { lmpControlChannelPerfEntry 48 }
lmpCcChannelStatusReqSent OBJECT-TYPE lmpCcChannelStatusReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 49 } ::= { lmpControlChannelPerfEntry 49 }
lmpCcChannelStatusReqRetransmit OBJECT-TYPE lmpCcChannelStatusReqRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been retransmitted on this control channel." that have been retransmitted on this control channel."
::= { lmpControlChannelPerfEntry 50 } ::= { lmpControlChannelPerfEntry 50 }
lmpCcChannelStatusRspReceived OBJECT-TYPE lmpCcChannelStatusRspReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages
have been received on this control channel." that have been received on this control channel."
::= { lmpControlChannelPerfEntry 51 } ::= { lmpControlChannelPerfEntry 51 }
lmpCcChannelStatusRspSent OBJECT-TYPE lmpCcChannelStatusRspSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages
have been sent on this control channel." that have been sent on this control channel."
::= { lmpControlChannelPerfEntry 52 } ::= { lmpControlChannelPerfEntry 52 }
lmpCcCounterDiscontinuityTime OBJECT-TYPE lmpCcCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this control channel's counters suffered a any one or more of this control channel's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this control channel of any Counter32 instances associated with this control channel of any
object contained in the lmpControlChannelPerfTable. If Counter32 object contained in the lmpControlChannelPerfTable.
no such discontinuities have occurred since the last re- If no such discontinuities have occurred since the last re-
initialization of the local management subsystem, then this initialization of the local management subsystem, then this
object contains a zero value." object contains a zero value."
::= { lmpControlChannelPerfEntry 53 } ::= { lmpControlChannelPerfEntry 53 }
-- End of lmpControlChannelPerfTable -- End of lmpControlChannelPerfTable
-- LMP TE Link Table -- LMP TE Link Table
lmpTeLinkTable OBJECT-TYPE lmpTeLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkEntry SYNTAX SEQUENCE OF LmpTeLinkEntry
skipping to change at page 37, line 22 skipping to change at page 36, line 31
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
lmpTeLinkVerification OBJECT-TYPE lmpTeLinkVerification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP link verification "This object indicates if the extended LMP link verification
procedure is enabled for this TE link." procedure is enabled for this TE link."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpTeLinkEntry 2 } ::= { lmpTeLinkEntry 2 }
lmpTeLinkFaultManagement OBJECT-TYPE lmpTeLinkFaultManagement OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP fault management "This object indicates if the extended LMP fault management
procedure is enabled on this TE link." procedure is enabled on this TE link."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpTeLinkEntry 3 } ::= { lmpTeLinkEntry 3 }
lmpTeLinkDwdm OBJECT-TYPE lmpTeLinkDwdm OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP DWDM procedure "This object indicates if the extended LMP DWDM procedure
is enabled on this TE link." is enabled on this TE link."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpTeLinkEntry 4 } ::= { lmpTeLinkEntry 4 }
lmpTeLinkOperStatus OBJECT-TYPE lmpTeLinkOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2), testing(3), init(4), degraded(5) } SYNTAX INTEGER {
up(1), down(2), testing(3), init(4), degraded(5)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this TE link. The status "The actual operational status of this TE link. The status
is set to testing when the TE link is performing link is set to testing when the TE link is performing link
verification. A degraded state indicates that there are verification. A degraded state indicates that there are
no active control channel between the pair of nodes that no active control channel between the pair of nodes that
form the endpoints of the TE link, but yet at least one form the endpoints of the TE link, but yet at least one
data-bearing links on the TE link is allocated." data-bearing links on the TE link is allocated."
::= { lmpTeLinkEntry 5 } ::= { lmpTeLinkEntry 5 }
skipping to change at page 38, line 40 skipping to change at page 38, line 10
columnar object in the row." columnar object in the row."
::= { 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 procedure "This object indicates how often the link verification
is executed. The interval is in milliseconds." procedure is executed. The interval is in milliseconds."
::= { 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 39, line 35 skipping to change at page 38, line 51
lmpTeLinkBitRate Unsigned32, lmpTeLinkBitRate Unsigned32,
lmpTeLinkWavelength Unsigned32 lmpTeLinkWavelength 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 interval in the LMP link verification process. It indicates the
at which the Test messages are sent." interval at which the Test messages are sent."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 1 } ::= { lmpLinkVerificationEntry 1 }
lmpVerifyDeadInterval OBJECT-TYPE lmpVerifyDeadInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyDeadInterval parameter used "This object specifies the VerifyDeadInterval parameter used
in the verification of the physical connectivity of data-bearing in the verification of the physical connectivity of data-
links. It specifies the observation period used to detect a Test bearing links. It specifies the observation period used to
message at the remote node." detect a Test message at the remote node."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [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), j016OverheadBytes(0),
j064OverheadBytes(1), j064OverheadBytes(1),
dccSectionOverheadBytes(2), dccSectionOverheadBytes(2),
dccLineOverheadBytes(3), dccLineOverheadBytes(3),
pos(4), pos(4),
skipping to change at page 40, line 28 skipping to change at page 39, line 48
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
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { 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 lmpTeLinkBitRate 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 bit rate at which the Test messages will be
transmitted and is expressed in bytes per second." transmitted and is expressed in bytes per second."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 5 } ::= { lmpLinkVerificationEntry 5 }
lmpTeLinkWavelength OBJECT-TYPE lmpTeLinkWavelength 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 be corresponds to a separate wavelength, than this value should
set to 0." be set to 0."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpLinkVerificationEntry 6 } ::= { lmpLinkVerificationEntry 6 }
-- End of lmpLinkVerificationTable -- End of lmpLinkVerificationTable
-- LMP TE Link Performance Table -- LMP TE Link Performance Table
lmpTeLinkPerfTable OBJECT-TYPE lmpTeLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkPerfEntry SYNTAX SEQUENCE OF LmpTeLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 43, line 38 skipping to change at page 43, line 15
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerify messages that "This object counts the number of BeginVerify messages that
have been retransmitted for this TE link." have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 5 } ::= { lmpTeLinkPerfEntry 5 }
lmpTeBeginVerifyAckReceived OBJECT-TYPE lmpTeBeginVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 6 } ::= { lmpTeLinkPerfEntry 6 }
lmpTeBeginVerifyAckSent OBJECT-TYPE lmpTeBeginVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have "This object counts the number of BeginVerifyAck messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 7 } ::= { lmpTeLinkPerfEntry 7 }
lmpTeBeginVerifyNackReceived OBJECT-TYPE lmpTeBeginVerifyNackReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 8 } ::= { lmpTeLinkPerfEntry 8 }
lmpTeBeginVerifyNackSent OBJECT-TYPE lmpTeBeginVerifyNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have "This object counts the number of BeginVerifyNack messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 9 } ::= { lmpTeLinkPerfEntry 9 }
lmpTeEndVerifyReceived OBJECT-TYPE lmpTeEndVerifyReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that have "This object counts the number of EndVerify messages that have
been received for this TE link." been received for this TE link."
::= { lmpTeLinkPerfEntry 10 } ::= { lmpTeLinkPerfEntry 10 }
skipping to change at page 45, line 5 skipping to change at page 44, line 30
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerify messages that "This object counts the number of EndVerify messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpTeLinkPerfEntry 12 } ::= { lmpTeLinkPerfEntry 12 }
lmpTeEndVerifyAckReceived OBJECT-TYPE lmpTeEndVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 13 } ::= { lmpTeLinkPerfEntry 13 }
lmpTeEndVerifyAckSent OBJECT-TYPE lmpTeEndVerifyAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of EndVerifyAck messages that have "This object counts the number of EndVerifyAck messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 14 } ::= { lmpTeLinkPerfEntry 14 }
lmpTeTestStatusSuccessReceived OBJECT-TYPE lmpTeTestStatusSuccessReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages
been received for this TE link." that have been received for this TE link."
::= { lmpTeLinkPerfEntry 15 } ::= { lmpTeLinkPerfEntry 15 }
lmpTeTestStatusSuccessSent OBJECT-TYPE lmpTeTestStatusSuccessSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have "This object counts the number of TestStatusSuccess messages
been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 16 } ::= { lmpTeLinkPerfEntry 16 }
lmpTeTestStatusSuccessRetransmit OBJECT-TYPE lmpTeTestStatusSuccessRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusSuccess messages that "This object counts the number of TestStatusSuccess messages
have been retransmitted for this TE link." that have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 17 } ::= { lmpTeLinkPerfEntry 17 }
lmpTeTestStatusFailureReceived OBJECT-TYPE lmpTeTestStatusFailureReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages
been received for this TE link." that have been received for this TE link."
::= { lmpTeLinkPerfEntry 18 } ::= { lmpTeLinkPerfEntry 18 }
lmpTeTestStatusFailureSent OBJECT-TYPE lmpTeTestStatusFailureSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that have "This object counts the number of TestStatusFailure messages
been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 19 } ::= { lmpTeLinkPerfEntry 19 }
lmpTeTestStatusFailureRetransmit OBJECT-TYPE lmpTeTestStatusFailureRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusFailure messages that "This object counts the number of TestStatusFailure messages
have been retransmitted on this TE link." that have been retransmitted on this TE link."
::= { lmpTeLinkPerfEntry 20 } ::= { lmpTeLinkPerfEntry 20 }
lmpTeTestStatusAckReceived OBJECT-TYPE lmpTeTestStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 21 } ::= { lmpTeLinkPerfEntry 21 }
lmpTeTestStatusAckSent OBJECT-TYPE lmpTeTestStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of TestStatusAck messages that have "This object counts the number of TestStatusAck messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 22 } ::= { lmpTeLinkPerfEntry 22 }
lmpTeLinkSummaryReceived OBJECT-TYPE lmpTeLinkSummaryReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that have "This object counts the number of LinkSummary messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 23 } ::= { lmpTeLinkPerfEntry 23 }
lmpTeLinkSummarySent OBJECT-TYPE lmpTeLinkSummarySent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that have "This object counts the number of LinkSummary messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 24 } ::= { lmpTeLinkPerfEntry 24 }
lmpTeLinkSummaryRetransmit OBJECT-TYPE lmpTeLinkSummaryRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummary messages that "This object counts the number of LinkSummary messages that
have been retransmitted over this control channel." have been retransmitted over this control channel."
::= { lmpTeLinkPerfEntry 25 } ::= { lmpTeLinkPerfEntry 25 }
lmpTeLinkSummaryAckReceived OBJECT-TYPE lmpTeLinkSummaryAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have "This object counts the number of LinkSummaryAck messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 26 } ::= { lmpTeLinkPerfEntry 26 }
lmpTeLinkSummaryAckSent OBJECT-TYPE lmpTeLinkSummaryAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have "This object counts the number of LinkSummaryAck messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 27 } ::= { lmpTeLinkPerfEntry 27 }
lmpTeLinkSummaryNackReceived OBJECT-TYPE lmpTeLinkSummaryNackReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have "This object counts the number of LinkSummaryNack messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 28 } ::= { lmpTeLinkPerfEntry 28 }
lmpTeLinkSummaryNackSent OBJECT-TYPE lmpTeLinkSummaryNackSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have "This object counts the number of LinkSummaryNack messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 29 } ::= { lmpTeLinkPerfEntry 29 }
lmpTeChannelStatusReceived OBJECT-TYPE lmpTeChannelStatusReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that
been received for this TE link." have been received for this TE link."
::= { lmpTeLinkPerfEntry 30 } ::= { lmpTeLinkPerfEntry 30 }
lmpTeChannelStatusSent OBJECT-TYPE lmpTeChannelStatusSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that
been sent for this TE link." have been sent for this TE link."
::= { lmpTeLinkPerfEntry 31 } ::= { lmpTeLinkPerfEntry 31 }
lmpTeChannelStatusRetransmit OBJECT-TYPE lmpTeChannelStatusRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages that
been retransmitted for this TE link." have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 32 } ::= { lmpTeLinkPerfEntry 32 }
lmpTeChannelStatusAckReceived OBJECT-TYPE lmpTeChannelStatusAckReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusAck messages that have "This object counts the number of ChannelStatusAck messages
been received for this TE link." that have been received for this TE link."
::= { lmpTeLinkPerfEntry 33 } ::= { lmpTeLinkPerfEntry 33 }
lmpTeChannelStatusAckSent OBJECT-TYPE lmpTeChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatus messages that have "This object counts the number of ChannelStatus messages
been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 34 } ::= { lmpTeLinkPerfEntry 34 }
lmpTeChannelStatusReqReceived OBJECT-TYPE lmpTeChannelStatusReqReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been received for this TE link." that have been received for this TE link."
::= { lmpTeLinkPerfEntry 35 } ::= { lmpTeLinkPerfEntry 35 }
lmpTeChannelStatusReqSent OBJECT-TYPE lmpTeChannelStatusReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 36 } ::= { lmpTeLinkPerfEntry 36 }
lmpTeChannelStatusReqRetransmit OBJECT-TYPE lmpTeChannelStatusReqRetransmit OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that "This object counts the number of ChannelStatusRequest messages
have been retransmitted for this TE link." that have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 37 } ::= { lmpTeLinkPerfEntry 37 }
lmpTeChannelStatusRspReceived OBJECT-TYPE lmpTeChannelStatusRspReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages
have been received for this TE link." that have been received for this TE link."
::= { lmpTeLinkPerfEntry 38 } ::= { lmpTeLinkPerfEntry 38 }
lmpTeChannelStatusRspSent OBJECT-TYPE lmpTeChannelStatusRspSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of ChannelStatusResponse messages that "This object counts the number of ChannelStatusResponse messages
have been sent for this TE link." that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 39 } ::= { lmpTeLinkPerfEntry 39 }
lmpTeCounterDiscontinuityTime OBJECT-TYPE lmpTeCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this TE link's counters suffered a any one or more of this TE link's counters suffered a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
skipping to change at page 50, line 50 skipping to change at page 50, line 28
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]." [TELINK-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataLinkTable 1 } ::= { lmpDataLinkTable 1 }
LmpDataLinkEntry ::= SEQUENCE { LmpDataLinkEntry ::= SEQUENCE {
lmpDataLinkType INTEGER, lmpDataLinkType INTEGER,
lmpDataLinkIpAddrType InetAddressType, lmpDataLinkAddressType InetAddressType,
lmpDataLinkIpAddr InetAddress, lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress, lmpDataLinkRemoteIpAddress InetAddress,
lmpDataLinkRemoteIfId InterfaceIndexOrZero, lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataLinkEncodingType INTEGER, lmpDataLinkEncodingType TeLinkEncodingType,
lmpDataLinkActiveOperStatus INTEGER, lmpDataLinkActiveOperStatus INTEGER,
lmpDataLinkPassiveOperStatus INTEGER, lmpDataLinkPassiveOperStatus INTEGER,
lmpDataLinkRowStatus RowStatus, lmpDataLinkRowStatus RowStatus,
lmpDataLinkStorageType StorageType lmpDataLinkStorageType StorageType
} }
lmpDataLinkType OBJECT-TYPE lmpDataLinkType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
port(1), port(1),
componentLink(2) componentLink(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this data-bearing link is "This attribute specifies whether this data-bearing link is
a port or a component link. Component link are multiplex a port or a component link. Component link are multiplex
capable whereas, ports are not multiplex capable." capable whereas, ports are not multiplex capable."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 1 } ::= { lmpDataLinkEntry 1 }
lmpDataLinkIpAddrType OBJECT-TYPE lmpDataLinkAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the data-bearing link IP address "This attribute specifies the data-bearing link IP address
type. If the data-bearing link is unnumbered, the address type. If the data-bearing link is unnumbered, the address
type must be set to unknown(0)." type must be set to unknown(0)."
::= { lmpDataLinkEntry 2 } ::= { lmpDataLinkEntry 2 }
lmpDataLinkIpAddr OBJECT-TYPE lmpDataLinkIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP address of the data-bearing link. This "The local Internet address for numbered links. The type
If the data-bearing link is unnumbered, then the of this address is determined by the value of
IP address must be null." lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents
the local IP address associated with the data-bearing
link. For an unnumbered link, the local address is
of type unknown and this object is set to the zero length
string and the ifIndex object then identifies the
unnumbered address."
::= { lmpDataLinkEntry 3 } ::= { lmpDataLinkEntry 3 }
lmpDataLinkRemoteIpAddress OBJECT-TYPE lmpDataLinkRemoteIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP address of the remote end point. This "The remote Internet address for numbered data-bearing links.
information is either configured manually or is The type of this address is determined by the
lmpDataLinkAddressType object.
For IPv4 and IPv6 numbered links, this object represents the
remote IP address associated with the data-bearing link. For
an unnumbered link, the remote address is of type unknown
and this object is set to the zero length string and the
lmpDataLinkRemoteIfId object then identifies the unnumbered
address.
This information is either configured manually or is
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure. If the data-bearing link is unnumbered, then the procedure."
remote IP address must be null."
::= { lmpDataLinkEntry 4 } ::= { lmpDataLinkEntry 4 }
lmpDataLinkRemoteIfId OBJECT-TYPE lmpDataLinkRemoteIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Interface identifier of the remote end point. This "Interface identifier of the remote end point. This
information is either configured manually or is information is either configured manually or is
communicated by the remote node during the link verification communicated by the remote node during the link verification
procedure." procedure."
::= { lmpDataLinkEntry 5 } ::= { lmpDataLinkEntry 5 }
lmpDataLinkEncodingType OBJECT-TYPE lmpDataLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TeLinkEncodingType
packet(1),
ethernet(2),
ansiEtsiPdh(3),
sdhItuSonetAnsi(5),
digitalWrapper(7),
lambda(8),
fiber(9),
fiberChannel(11)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The encoding type of the data-bearing link." "The encoding type of the data-bearing link."
REFERENCE REFERENCE
"[RFC3471]" "Generalized MPLS Signaling Functional Description, RFC 3471"
::= { lmpDataLinkEntry 6 } ::= { lmpDataLinkEntry 6 }
lmpDataLinkActiveOperStatus OBJECT-TYPE lmpDataLinkActiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
testing(4) } testing(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(active FSM)." (active FSM)."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 7 } ::= { lmpDataLinkEntry 7 }
lmpDataLinkPassiveOperStatus OBJECT-TYPE lmpDataLinkPassiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
psvTst(4) } psvTst(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(passive FSM)." (passive FSM)."
REFERENCE REFERENCE
"[LMP]" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [LMP]
::= { lmpDataLinkEntry 8 } ::= { lmpDataLinkEntry 8 }
lmpDataLinkRowStatus OBJECT-TYPE lmpDataLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when lmpDataLinkRowStatus is active." can only be changed when lmpDataLinkRowStatus is active."
skipping to change at page 55, line 46 skipping to change at page 55, line 36
"This object counts the number of data-bearing link test "This object counts the number of data-bearing link test
that failed on the passive side of this data-bearing link." that failed on the passive side of this data-bearing link."
::= { lmpDataLinkPerfEntry 6 } ::= { lmpDataLinkPerfEntry 6 }
lmpDataLinkDiscontinuityTime OBJECT-TYPE lmpDataLinkDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime on the most recent occasion at which "The value of sysUpTime on the most recent occasion at which
any one or more of this data-bearing link's counters suffered a any one or more of this data-bearing link's counters suffered
discontinuity. The relevant counters are the specific a discontinuity. The relevant counters are the specific
instances associated with this data-bearing link of any Counter32 instances associated with this data-bearing link of any
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
lmpLinkPropertyNotifEnable 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."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 18 } ::= { lmpObjects 18 }
lmpUnprotectedNotifEnable 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."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 19 } ::= { lmpObjects 19 }
lmpCcUpDownNotifEnable 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."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 20 } ::= { lmpObjects 20 }
lmpTeLinkNotifEnable 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."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 21 } ::= { lmpObjects 21 }
lmpDataLinkNotifEnable 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."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 22 } ::= { lmpObjects 22 }
skipping to change at page 57, line 33 skipping to change at page 57, line 23
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { teLinkRemoteIpAddr, OBJECTS { teLinkRemoteIpAddr,
teLinkIncomingIfId } teLinkIncomingIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a TE link property "This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link mismatch is detected on the node. The received remote TE link
id of the misconfigured TE link is represented by either id of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
the TE link is numbered or unnumbered. This notification should the TE link is numbered or unnumbered. This notification
not be sent unless lmpLinkPropertyNotifEnable is true." should not be sent unless lmpLinkPropertyNotificationsEnabled
is true."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { ifIndex,
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. ifIndex
is the interface index of the TE link. The remote entity is the interface index of the TE link. The remote entity
interface id is the remote entity interface id received in the interface id is the remote entity interface id received in
LinkSummary message. This notification should the LinkSummary message. This notification should
not be sent unless lmpLinkPropertyNotifEnable is true." not be sent unless lmpLinkPropertyNotificationsEnabled is
true."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification -- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpCcNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when there are more than one "This notification is generated when there are more than one
control channels between LMP neighbors and the last redundant control channels between LMP neighbors and the last redundant
control channel has failed. If the remaining operational control control channel has failed. If the remaining operational
channel fails, then there will be no more control channels control channel fails, then there will be no more control
between the pair of nodes and all the TE links between the pair channels between the pair of nodes and all the TE links
of nodes will go to degraded state. This notification should not between the pair of nodes will go to degraded state. This
be sent unless lmpUnprotectedNotifEnable is set to true." notification should not be sent unless
lmpUnprotectedNotificationsEnabled is set to true."
::= { lmpNotifications 3 } ::= { lmpNotifications 3 }
-- Control Channel Notifications -- Control Channel Notifications
lmpControlChannelUp NOTIFICATION-TYPE lmpControlChannelUp NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 lmpCcUpDownNotifEnable notification should not be sent unless
is true." lmpCcUpDownNotififcationsEnabled 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 transitions out of the up operational state. This channel transitions out of the up operational state. This
notification should not be sent unless lmpCcUpDownNotifEnable notification should not be sent unless
is true." lmpCcUpDownNotificationsEnabled is true."
::= { lmpNotifications 5 } ::= { lmpNotifications 5 }
-- TE Link Notification -- TE Link Notification
lmpTeLinkDegraded NOTIFICATION-TYPE lmpTeLinkDegraded NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { ifIndex }
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 lmpTeLinkNotifEnable notification should not be sent unless
is true." lmpTeLinkNotificationsEnabled is true."
::= { lmpNotifications 6 } ::= { lmpNotifications 6 }
lmpTeLinkNotDegraded NOTIFICATION-TYPE lmpTeLinkNotDegraded NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { ifIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a lmpTeLinkOperStatus "This notification is generated when a lmpTeLinkOperStatus
object for a TE link leaves the degraded state. This object for a TE link leaves the degraded state. This
notification should not be sent unless lmpTeLinkNotifEnable notification should not be sent unless
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 { ifIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing "This notification is generated when a data-bearing
link verification fails. This notification should not be sent link verification fails. This notification should not be sent
unless lmpDataLinkNotifEnable is true." unless lmpDataLinkNotificationsEnabled is true."
::= { lmpNotifications 8 } ::= { lmpNotifications 8 }
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
lmpGroups lmpGroups
OBJECT IDENTIFIER ::= { lmpConformance 1 } OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpCompliances lmpCompliances
OBJECT IDENTIFIER ::= { lmpConformance 2 } OBJECT IDENTIFIER ::= { lmpConformance 2 }
lmpFullModuleCompliance 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
-- The mandatory groups have to be implemented
-- by all LMP-enabled devices. However, they may all be supported
-- as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
skipping to change at page 60, line 39 skipping to change at page 60, line 28
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpNbrStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpControlChannelTable -- lmpControlChannelTable
OBJECT lmpRemoteCcIpAddrType OBJECT lmpRemoteCcAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) adress type needs not be supported. For "Only ipv4(1) and ipv6(2) address types need to be
point-to-point configuration, this object MIN-ACCESS supported for non point-to-point configurations."
is read-create."
OBJECT lmpRemoteCcIpAddr OBJECT lmpRemoteCcIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
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."
For point-to-point configuration, this object MIN-ACCESS is
read-create."
OBJECT lmpCcRowStatus OBJECT lmpCcRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { 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 "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
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 active(3), configuring(4), goingDown(5)
need not be supported." need not be supported."
OBJECT lmpCcStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpTeLinkTable -- lmpTeLinkTable
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"The testing(3) state need not be supported." "The testing(3) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpTeLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkActiveOperStatus OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataLinkPassiveOperStatus OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpDataLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only
DESCRIPTION
"Only other(1) needs to be supported."
::= { lmpCompliances 1 } ::= { lmpCompliances 1 }
lmpMonitoringModuleCompliance 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
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all LMP-enabled devices. However, they may all be supported -- by all LMP-enabled devices. However, they may all be supported
-- as read-only objects in the case where manual -- as read-only objects in the case where manual
-- configuration is unsupported. -- configuration is not supported.
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
lmpPerfGroup, lmpPerfGroup,
lmpTeLinkGroup, lmpTeLinkGroup,
lmpDataLinkGroup } lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION DESCRIPTION
skipping to change at page 64, line 48 skipping to change at page 64, line 4
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpNbrStorageType OBJECT lmpNbrStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Write access is not required."
-- lmpControlChannelTable -- lmpControlChannelTable
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 lmpRemoteCcIpAddrType OBJECT lmpRemoteCcAddressType
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
"The dns(16) adress type needs not be supported." "Only ipv4(1) and ipv6(2) address types need to be
supported for non point-to-point configurations."
OBJECT lmpRemoteCcIpAddr OBJECT lmpRemoteCcIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The size of the IP address depends on the address type." "The size of the IP address depends on the address type."
OBJECT lmpCcSetupRole OBJECT lmpCcSetupRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 66, line 34 skipping to change at page 65, line 37
not be supported." not be supported."
OBJECT lmpCcOperStatus OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of active(3), configuring(4), goingDown(5) "A value of active(3), configuring(4), goingDown(5)
need not be supported." need not be supported."
OBJECT lmpCcStorageType OBJECT lmpCcStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Write access is not required."
-- lmpLinkVerificationTable -- lmpLinkVerificationTable
OBJECT lmpVerifyInterval OBJECT lmpVerifyInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpVerifyDeadInterval OBJECT lmpVerifyDeadInterval
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 67, line 46 skipping to change at page 66, line 47
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpTeLinkStorageType OBJECT lmpTeLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Write access is not required."
-- lmpTeLinkVerificationTable -- lmpTeLinkVerificationTable
OBJECT lmpTeLinkBitRate OBJECT lmpTeLinkBitRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkWavelength OBJECT lmpTeLinkWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkIpAddrType 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
"The dns(16) address type need not be supported. "Only ipv4(1) and ipv6(2) address types need to be
The ipv4(1) and ipv6(2) address types need not be supported for numbered links. For unnumbered links, the
supported if numbered links are not supported. The unknown(0) address type needs to be supported."
unknown(0) address type needs not be supported if
unnumbered links are not supported."
OBJECT lmpDataLinkIpAddr OBJECT lmpDataLinkIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Size of data-bearing link IP address depends on type "Size of data-bearing link IP address depends on type
of data-bearing link. Data-bearing link IP address size of data-bearing link. Data-bearing link IP address size
is zero if link is unnumbered, four if link IP address is is zero if link is unnumbered, four if link IP address is
IPv4 and sixteen if link IP address is IPv6." IPv4 and sixteen if link IP address is IPv6."
skipping to change at page 69, line 25 skipping to change at page 68, line 24
OBJECT lmpDataLinkRowStatus OBJECT lmpDataLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT lmpDataLinkStorageType OBJECT lmpDataLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "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,
lmpUnprotectedNotifEnable lmpUnprotectedNotificationsEnabled
} }
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 70, line 17 skipping to change at page 69, line 15
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpCcHelloIntervalDefault, lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin, lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax, lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault, lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin, lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax, lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId, lmpCcNbrNodeId,
lmpRemoteCcId, lmpRemoteCcId,
lmpRemoteCcIpAddrType, lmpRemoteCcAddressType,
lmpRemoteCcIpAddr, lmpRemoteCcIpAddr,
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,
lmpCcUpDownNotifEnable lmpCcUpDownNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP interface "Collection of objects needed for LMP interface
configuration." configuration."
::= { lmpGroups 2 } ::= { lmpGroups 2 }
lmpCcIsInterfaceGroup OBJECT-GROUP lmpCcIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf } OBJECTS { lmpCcIsIf }
STATUS current STATUS current
skipping to change at page 71, line 14 skipping to change at page 70, line 12
lmpCcLastChange, lmpCcLastChange,
lmpCcAdminStatus lmpCcAdminStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement control channels that are not "Objects needed to implement control channels that are not
interfaces." interfaces."
::= { lmpGroups 4 } ::= { lmpGroups 4 }
lmpLinkPropertyCorrelationGroup OBJECT-GROUP lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyNotifEnable } OBJECTS { lmpLinkPropertyNotificationsEnabled }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement the link "Collection of objects needed to implement the link
property correlation procedure." property correlation procedure."
::= { lmpGroups 5 } ::= { lmpGroups 5 }
lmpLinkVerificationGroup OBJECT-GROUP lmpLinkVerificationGroup OBJECT-GROUP
OBJECTS { lmpLinkVerificationInterval, OBJECTS { lmpLinkVerificationInterval,
lmpVerifyInterval, lmpVerifyInterval,
lmpVerifyDeadInterval, lmpVerifyDeadInterval,
lmpVerifyTransportMechanism, lmpVerifyTransportMechanism,
lmpVerifyAllLinks, lmpVerifyAllLinks,
lmpTeLinkBitRate, lmpTeLinkBitRate,
lmpTeLinkWavelength, lmpTeLinkWavelength,
lmpDataLinkNotifEnable 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,
lmpCcInDiscards, lmpCcInDiscards,
skipping to change at page 74, line 9 skipping to change at page 73, line 7
::= { lmpGroups 7 } ::= { lmpGroups 7 }
lmpTeLinkGroup OBJECT-GROUP lmpTeLinkGroup OBJECT-GROUP
OBJECTS { lmpTeLinkNbrNodeId, OBJECTS { lmpTeLinkNbrNodeId,
lmpTeLinkVerification, lmpTeLinkVerification,
lmpTeLinkFaultManagement, lmpTeLinkFaultManagement,
lmpTeLinkDwdm, lmpTeLinkDwdm,
lmpTeLinkOperStatus, lmpTeLinkOperStatus,
lmpTeLinkRowStatus, lmpTeLinkRowStatus,
lmpTeLinkStorageType, lmpTeLinkStorageType,
lmpTeLinkNotifEnable lmpTeLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for TE link configuration." "Collection of objects needed for TE link configuration."
::= { lmpGroups 8 } ::= { lmpGroups 8 }
lmpDataLinkGroup OBJECT-GROUP lmpDataLinkGroup OBJECT-GROUP
OBJECTS { lmpDataLinkType, OBJECTS { lmpDataLinkType,
lmpDataLinkIpAddrType, lmpDataLinkAddressType,
lmpDataLinkIpAddr, lmpDataLinkIpAddr,
lmpDataLinkRemoteIpAddress, lmpDataLinkRemoteIpAddress,
lmpDataLinkRemoteIfId, lmpDataLinkRemoteIfId,
lmpDataLinkEncodingType, lmpDataLinkEncodingType,
lmpDataLinkActiveOperStatus, lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus, lmpDataLinkPassiveOperStatus,
lmpDataLinkRowStatus, lmpDataLinkRowStatus,
lmpDataLinkStorageType lmpDataLinkStorageType
} }
STATUS current STATUS current
skipping to change at page 75, line 5 skipping to change at page 74, line 5
lmpDataLinkVerificationFailure } lmpDataLinkVerificationFailure }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { lmpGroups 10 } ::= { lmpGroups 10 }
-- End of LMP-MIB -- End of LMP-MIB
END END
11. 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 per-
tain to the implementation or use of the technology described in this tain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might document or the extent to which any license under such rights might
or might not be available; neither does it represent that it has made or might not be available; neither does it represent that it has made
any effort to identify any such rights. Information on the IETF's any effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards- procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses rights made available for publication and any assurances of licenses
skipping to change at page 75, line 27 skipping to change at page 74, line 27
general license or permission for the use of such proprietary rights general license or permission for the use of such proprietary rights
by implementers or users of this specification can be obtained from by implementers or users of this specification can be obtained from
the IETF Secretariat. 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.
12. Security Considerations 11. Security Considerations
It is clear that this MIB is potentially useful for monitoring of LMP There are a number of management objects defined in this MIB module
enabled devices. This MIB can also be used for configuration of cer- with a MAX-ACCESS clause of read-write and/or read-create. Such
tain objects, and anything that can be configured can be incorrectly objects may be considered sensitive or vulnerable in some network
configured, with potentially disastrous results. environments. The support for SET operations in a non-secure envi-
ronment without proper protection can have a negative effect on net-
work operations. These are the tables and objects and their sensi-
tivity/vulnerability:
At this writing, no security holes have been identified beyond those - The lmpNbrTable exposes network provider's node IP addresses.
that SNMP Security [RFC2571] is itself intended to address. These
relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera-
tor error, which is beyond the scope of any security architecture.
There are a number of management objects defined in this MIB which - lmpControlChannelTable exposes network provider's control
have a MAX-ACCESS clause of read-write and/or read-create. Such network.
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network
operations. The use of SNMP Version 3 is recommended over prior ver-
sions, for configuration control, as its security model is improved.
SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if - lmpDataLinkTable exposes network provider's data network.
the network itself is secure (for example by using IPSec [RFC2401]),
there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this
MIB. It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [RFC2574] and the View-based Access
Control [RFC2575] is recommended. It is then a customer/user respon-
sibility to ensure that the SNMP entity giving access to an instance
of this MIB is properly configured to give access to the objects only
to those principals (users) that have legitimate rights to indeed GET
or SET (change/create/delete) them.
There are a number of managed objects in this MIB that may contain - Unauthorized changes to the lmpControlChannelTable,
information that may be sensitive from a business perspective, in lmpTeLinkTable and lmpDataLinkTable may disrupt allocation of
that they can be used to derive the network topology, e.g. list of resources in the network.
nodes and their IP address (lmpNbrTable) and list of data-bearing
links (lmpDataLinkTable). Allowing uncontrolled access to these
objects could result in malicious and unwanted disruptions of network
traffic, incorrect network configurations or theft of competitive
business information. There are no objects that are particularly sen-
sitive in their own right, such as passwords or monetary amounts.
13. Acknowledgments SNMP versions prior to SNMPv3 did not include adequate security.
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
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), includ-
ing full support for the SNMPv3 cryptographic mechanisms (for authen-
tication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOM-
MENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable
cryptographic security. It is then a customer/operator responsibil-
ity to ensure that the SNMP entity giving access to an instance of
this MIB module is properly configured to give access to the objects
only to those principals (users) that have legitimate rights to
indeed GET or SET (change/create/delete) them.
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.
14. References 13. References
14.1. Normative References 13.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.
[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,
J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and
Shoenwaelder, J., "Textual Conventions for Internet
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 Function Description", "Generalized MPLS Signaling Functional Description",
RFC 3471, January 2003. RFC 3471, January 2003.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[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-00.txt>, April 2003. <draft-ietf-mpls-telink-mib-02.txt>, May 2003.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS. See also:
http://www.iana.org/assignments/address-family-numbers
For MIB see: http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib
[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.
14.2. Informative References 13.2. Informative References
[RFC1155] Rose, M., and McCloghrie, K., "Structure and
Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M., and McCloghrie, K., "Concise MIB Defini-
tions",
STD 16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[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.
15. 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. Avici Systems, Inc. Calient Networks, Inc.
101 Billerica Avenue 5853 Rue Ferrari 101 Billerica Avenue 5853 Rue Ferrari
skipping to change at page 79, line 22 skipping to change at page 77, line 4
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. Avici Systems, Inc. Calient Networks, Inc.
101 Billerica Avenue 5853 Rue Ferrari 101 Billerica Avenue 5853 Rue Ferrari
N Billerica, MA 08162 San Jose, CA 95138 N Billerica, MA 08162 San Jose, CA 95138
Email: sudheer@avici.com Email: evan@calient.net Email: sudheer@avici.com 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
16. 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 docu-
ment itself may not be modified in any way, such as by removing the ment itself may not be modified in any way, such as by removing the
 End of changes. 

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