draft-ietf-ccamp-lmp-mib-00.txt   draft-ietf-ccamp-lmp-mib-01.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft edgeflow, Inc. Internet Draft Meriton Networks
Expires: April 2002 Expires: August 2002
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks, Inc. Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Evan McGinnis Evan McGinnis
Calient Networks, Inc. Calient Networks
Link Management Protocol Management Information Base Using SMIv2 February 2002
draft-ietf-ccamp-lmp-mib-00.txt Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-01.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 1, line 46 skipping to change at page 2, line 4
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Table of Contents Table of Contents
1. Abstract ..................................................... 2 1. Abstract ..................................................... 2
2. Introduction ................................................. 2 2. Introduction ................................................. 2
3. Terminology .................................................. 3 3. Terminology .................................................. 3
4. The SNMP Management Framework ................................ 3 4. The SNMP Management Framework ................................ 3
4.1. Object Definitions ........................................... 4
5. Feature Checklist ............................................ 4
5. Feature Checklist ............................................ 4
6. Outline ...................................................... 5 6. Outline ...................................................... 5
6.1. Summary of LMP MIB ........................................... 6 6.1. Summary of LMP MIB ........................................... 5
7. Brief Description of MIB Objects ............................. 6 7. Brief Description of MIB Objects ............................. 6
7.1. lmpNbrTable .................................................. 6 7.1. lmpNbrTable .................................................. 6
7.2. lmpControlChannelTable ....................................... 6 7.2. lmpControlChannelTable ....................................... 6
7.3. lmpControlChannelPerfTable ................................... 6 7.3. lmpControlChannelPerfTable ................................... 6
7.4. lmpTeLinkTable ............................................... 7 7.4. lmpTeLinkTable ............................................... 7
7.5. lmpLinkVerificationTable ..................................... 7 7.5. lmpLinkVerificationTable ..................................... 7
7.6. lmpDataBearingLinkTable ...................................... 7 7.6. lmpDataBearingLinkTable ...................................... 7
7.7. lmpDataBearingLinkPerfTable .................................. 7 7.7. lmpDataBearingLinkPerfTable .................................. 7
8. Example of LMP Control Channel Interface Setup ............... 7 8. Example of LMP Control Channel Interface Setup ............... 7
9. Application of the Interface Group to LMP .................... 10 9. Application of the Interfaces Group to LMP ................... 9
9.1. Support of the LMP Layer by ifTable .......................... 10 9.1. Support of the LMP Layer by ifTable .......................... 10
10. Link Management Protocol MIB Definitions ..................... 12 10. Link Management Protocol MIB Definitions ..................... 12
11. Security Considerations ...................................... 51 11. Security Considerations ...................................... 66
12. Acknowledgments .............................................. 52 12. Acknowledgments .............................................. 67
13. References ................................................... 52 13. References ................................................... 67
14. Authors' Addresses ........................................... 55 14. Authors' Addresses ........................................... 69
15. Full Copyright Statement ..................................... 55 15. Full Copyright Statement ..................................... 70
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Informa- This memo defines an experimental portion of the Management Informa-
tion Base (MIB) for use with network management protocols in the tion Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes managed objects for Internet community. In particular, it describes managed objects for
modeling the Link Management Protocol (LMP) [LMP]. modeling the Link Management Protocol (LMP) [LMP].
2. Introduction 2. Introduction
This memo defines an experimental portion of the Management Informa- Current work is underway in the IETF to specify a suite of protocols
tion Base (MIB) for use with network management protocols in the to be used as a common control plane and a separate common measure-
Internet community. In particular, it describes managed objects for ment plane. The Link Management Protocol, which primary purpose is to
modeling the Link Management Protocol (LMP) [LMP]. manage traffic engineering (TE) links, is one of the key components
of this standardization activity. Primary goals of LMP are the
maintenance of the control channel connectivity, correlation of link
properties, verification of data-bearing links and detection and iso-
lation of link faults.
We describe in this document a MIB that can be used to manage LMP
implementations. This MIB covers both configuration and performance
monitoring aspects of LMP.
Comments should be made directly to the ccamp mailing list at Comments should be made directly to the ccamp mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
This memo does not, in its draft form, specify a standard for the This memo does not, in its draft form, specify a standard for the
Internet community. Internet community.
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
skipping to change at page 3, line 22 skipping to change at page 3, line 30
With the exception of messages related to control channel management, With the exception of messages related to control channel management,
any time a LMP message needs to be transferred to a neighbor node, it any time a LMP message needs to be transferred to a neighbor node, it
can be sent on any of the active control channels. The control chan- can be sent on any of the active control channels. The control chan-
nels can also be used to exchange MPLS control plane information or nels can also be used to exchange MPLS control plane information or
routing information. routing information.
LMP is designed to support aggregation of one or more data-bearing LMP is designed to support aggregation of one or more data-bearing
links into a traffic-engineering (TE) link. The data-bearing links links into a traffic-engineering (TE) link. The data-bearing links
can be either component links or ports depending on their multiplex- can be either component links or ports depending on their multiplex-
ing capability (see [LMP] for distinction between port and component ing capability (see [LMP] for distinction between port and component
link). Furthermore, the data-bearing links may be defined as primary link).
or secondary data-bearing links, where a secondary data-bearing link
is used to protect a primary data-bearing link, i.e. if a primary
data-bearing link fails, data traffic is switched over to one of the
secondary data-bearing links.
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. In turn, control control channels are used to exchange LMP messages for a particular
channels are used to manage one or more TE links. adjacency. In turn, control channels are used to manage the TE links
associated with the LMP adjacency.
4. The SNMP Management Framework 4. The SNMP Management Framework
The SNMP Management Framework presently consists of five major com- The SNMP Management Framework presently consists of five major com-
ponents: ponents:
- An overall architecture, described in RFC 2571 [SNMPArch]. - An overall architecture, described in RFC 2571 [RFC2571].
- Mechanisms for describing and naming objects and events for the Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
[SNMPv1Traps]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
in RFC 2578 [SMIv2], RFC 2579 [SNMPv2TC] and RFC 2580 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
[SNMPv2Conf]. STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management information. The - Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 first version of the SNMP message protocol is called SNMPv1 and
and described in RFC 1157 [SNMPv1]. A second version of the described in STD 15, RFC 1157 [RFC1157]. A second version of
SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the [RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906 message protocol is called SNMPv3 and described in RFC 1906
[SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
- Protocol operations for accessing management information. The - Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [SNMPv1]. A second set of protocol described in STD 15, RFC 1157 [RFC1157]. A second set of
operations and associated PDU formats is described in RFC 1905 protocol operations and associated PDU formats is described in
[SNMPv2PO]. RFC 1905 [RFC1905].
- A set of fundamental applications described in RFC 2273
[SNMPv3App] and the view-based access control mechanism
described in RFC 2575 [SNMPv3VACM].
Managed objects are accessed via a virtual information store, termed - A set of fundamental applications described in RFC 2573
the Management Information Base or MIB. Objects in the MIB are [RFC2573] and the view-based access control mechanism described
defined using the mechanisms defined in the SMI. This memo specifies in RFC 2575 [RFC2575].
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 possi-
ble (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 informa-
tion is not considered to change the semantics of the MIB.
4.1. Object Definitions 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 Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) defined using the mechanisms defined in the SMI.
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object This memo specifies a MIB module that is compliant to the SMIv2. A
type together with an object instance serves to uniquely identify a MIB conforming to the SMIv1 can be produced through the appropriate
specific instantiation of the object. For human convenience, we often translations. The resulting translated MIB must be semantically
use a textual string, termed the descriptor, to also refer to the equivalent, except where objects or events are omitted because no
object type. 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 5. Feature Checklist
The Link Management protocol MIB (LMP-MIB) is designed to satisfy the The Link Management protocol MIB (LMP-MIB) is designed to satisfy the
following requirements and constraints: following requirements and constraints:
- The MIB supports the enabling and disabling of LMP capability - The MIB supports the enabling and disabling of LMP capability
on LMP capable interfaces of a photonic switch, optical on LMP capable interfaces of a photonic switch, optical
cross-connect or router. cross-connect or router.
skipping to change at page 5, line 16 skipping to change at page 5, line 14
- 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 is used to express the mapping between local and remote
TE links, as well as local and remote interface identifiers for TE links, as well as local and remote interface identifiers for
port or component link. 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 are also provided for measuring LMP performance on the data-
also provided for measuring LMP performance on the data-bearing bearing links.
links.
Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB
[BUNDLE-MIB]. The TE link table, which is used to associate data- [BUNDLE-MIB]. The TE link table, which is used to associate data-
bearing links to TE links, is defined in the Link Bundling MIB. The bearing links to TE links, is defined in the Link Bundling MIB. The
TE link table in the LMP MIB contains TE link information specific to TE link table in the LMP MIB contains TE link information specific to
LMP. LMP.
6. Outline 6. Outline
Configuring LMP through an optical device involves the following Configuring LMP through an optical device involves the following
skipping to change at page 5, line 40 skipping to change at page 5, line 37
- 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).
- Identifying which control channels manage the TE link. TE links are managed by the control channels that run between the
same pair of nodes (LMP adjacency).
6.1. Summary of LMP MIB 6.1. Summary of LMP MIB
The MIB objects for performing these actions consist of the following The MIB objects for performing these actions consist of the following
tables: tables:
- The remote node table is used to identify the pair - The remote node table (lmpNbrTable) is used to identify the pair
of nodes that exchange LMP messages over control channels. of nodes that exchange LMP messages over control channels.
- The control channel table (lmpControlChannelTable) is used - The control channel table (lmpControlChannelTable) is used
for enabling the LMP protocol on LMP-capable interfaces. for enabling the LMP protocol on LMP-capable interfaces.
- The control channel performance table - The control channel performance table
(lmpControlChannelPerfTable) is used for collecting (lmpControlChannelPerfTable) is used for collecting
LMP performance counts on a per-control channel basis. LMP performance counts on a per-control channel basis.
- The TE link table (lmpTeLinkTable) is used for - The TE link table (lmpTeLinkTable) is used for
skipping to change at page 7, line 12 skipping to change at page 7, line 11
capable interfaces and is an AUGMENT to the lmpControlChannelTable. capable interfaces and is an AUGMENT to the lmpControlChannelTable.
High capacity counters are provided for objects that are likely to High capacity counters are provided for objects that are likely to
wrap around quickly. wrap around quickly.
7.4. lmpTeLinkTable 7.4. lmpTeLinkTable
This table represents the TE link information specific to LMP. This table represents the TE link information specific to LMP.
7.5. lmpLinkVerificationTable 7.5. lmpLinkVerificationTable
This table represents the link verification parameters associated This table augments the lmpTeLinkTable and represents the link verif-
with the TE links. ication parameters associated with the TE links.
7.6. lmpDataBearingLinkTable 7.6. lmpDataBearingLinkTable
The data-bearing link table enumerates the data-bearing links that The data-bearing link table enumerates the data-bearing links that
are associated with each TE link. are associated with each TE link.
7.7. lmpDataBearingLinkPerfTable 7.7. lmpDataBearingLinkPerfTable
This table contains the objects to measure the LMP performance of This table augments the lmpDataBearingLinkTable. It contains the
data-bearing links and is an AUGMENT to the lmpDataBearingLinkTable. objects to measure the LMP performance of data-bearing links.
8. Example of LMP Control Channel Setup 8. 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 11 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, it is intended as an aid to understanding some of the key
concepts. It is meant to be read after going through the MIB itself. 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
lmpNbrRetransmitInterval = 10, lmpNbrRetransmitInterval = 10,
lmpNbrRetransmitTimeoutInterval = 0,
lmpNbrAdminStatus = up(1), lmpNbrAdminStatus = up(1),
lmpNbrRowStatus = createAndGo(4) lmpNbrRowStatus = createAndGo(4)
} }
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:
{ {
ifIndex = 1, lmpCcId = 1,
lmpCcUnderlyingIfIndex = 1, lmpCcUnderlyingIfIndex = 1,
lmCcIsIf = false(1), lmCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcConfigRetransmitInterval = 10, lmpCcConfigRetransmitInterval = 10,
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
skipping to change at page 8, line 51 skipping to change at page 8, line 49
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4)
} }
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 lmpDataBearingLinkTable: In lmpDataBearingLinkTable:
{ {
ifIndex = 41, ifIndex = 41,
lmpDataBearingLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 47, lmpDataBearingLinkRemoteIfId = 47,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataBearingLinkRowStatus = createAndGo(4)
} }
{ {
ifIndex = 43, ifIndex = 43,
lmpDataBearingLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 42, lmpDataBearingLinkRemoteIfId = 42,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataBearingLinkRowStatus = createAndGo(4)
} }
{ {
ifIndex = 44, ifIndex = 44,
lmpDataBearingLinkNumberingType = unnumbered(1),
lmpDataBearingLinkRemoteIfId = 48, lmpDataBearingLinkRemoteIfId = 48,
lmpDataBearingLinkRowStatus = createAndGo(4) lmpDataBearingLinkRowStatus = createAndGo(4)
} }
Note that the data-bearing link type (lmpDataBearingLinkType) does Note that the data-bearing link type (lmpDataBearingLinkType) 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
dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB]. dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB].
skipping to change at page 9, line 36 skipping to change at page 9, line 37
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 to specify TE link information specific
to LMP. to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
ifIndex = 20, ifIndex = 20,
lmpTeLinkVerification = true(2), lmpTeLinkVerification = true(2),
lmpTeLinkFaultIsolation = 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)
} }
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 Link Bundling MIB may be created in the teLinkTable of Link Bundling MIB
[BUNDLE-MIB]. [BUNDLE-MIB].
9. Application of the Interface Group to LMP 9. Application of the Interfaces Group to LMP
The Interfaces Group of MIB II defines generic managed objects for The Interfaces Group [IFMIB] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing LMP control channels extensions to the Interfaces Group for managing LMP control channels
that are modeled as interfaces. If the control channel as defined in that are modeled as interfaces. If the control channel as defined in
the lmpControlChannelTable is modeled as an ifEntry, then the the lmpControlChannelTable is modeled as an ifEntry, then the
following definition applies. An lmpControlChannelTable entry is following definition applies. An lmpControlChannelTable entry is
designated as being represented as an Interfaces MIB ifEntry if the designated as being represented as an Interfaces MIB ifEntry if the
lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this
case, the control channel SHOULD be modeled as an ifEntry and case, the control channel SHOULD be modeled as an ifEntry and
provide appropriate interface stacking as defined below. provide appropriate interface stacking as defined below.
skipping to change at page 11, line 26 skipping to change at page 11, line 26
as to whether LMP should be enabled, disabled, or as to whether LMP should be enabled, disabled, or
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. Also see [IFMIB]. interface. Also see [IFMIB].
ifOperStatus This value reflects the actual or operational ifOperStatus This value reflects the actual or operational
status of LMP on this interface. status of LMP on this interface.
ifLastChange See [IFMIB]. ifLastChange See [IFMIB].
ifInOctets The number of received octets over the interface, ifInOctets The number of received octets over the interface,
i.e., the number of received, octets received as i.e., the number of octets received as LMP
labeled packets. packets.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the
interface, i.e., the number of octets transmitted interface, i.e., the number of octets transmitted
as labeled packets. as LMP packets.
ifInErrors The number of labeled packets dropped due to ifInErrors The number of LMP packets dropped due to
uncorrectable errors. uncorrectable errors.
ifInUnknownProtos ifInUnknownProtos
The number of received packets discarded during The number of received packets discarded during
packet header validation, including packets with packet header validation, including packets with
unrecognized label values. unrecognized label values.
ifOutErrors See [IFMIB]. ifOutErrors See [IFMIB].
ifName Textual name (unique on this system) of the ifName Textual name (unique on this system) of the
skipping to change at page 12, line 23 skipping to change at page 12, line 23
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [IFMIB]. See [IFMIB].
10. LMP MIB Definitions 10. LMP MIB Definitions
LMP-MIB DEFINITIONS ::= BEGIN LMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Integer32, Unsigned32, Counter32, Counter64, experimental, Integer32, Unsigned32, Counter32, TimeTicks
TimeTicks, IpAddress
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
RowPointer, TimeStamp RowPointer, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndex, InterfaceIndexOrZero, ifIndex, ifStackHigherLayer InterfaceIndex, InterfaceIndexOrZero, ifIndex, ifStackHigherLayer
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId teLinkRemoteIpAddr, teLinkIncomingIfId
FROM LINK-BUNDLING-MIB; FROM LINK-BUNDLING-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200110181200Z" -- 18 October 2001 12:00:00 EST LAST-UPDATED "200202261200Z" -- 26 February 2002 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
Postal: edgeflow, Inc. Postal: Meriton Networks
329 March Rd. 3026 Solandt Road
Kanata, ON, CANADA K2K 2E1 Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253 Tel: +1-613-270-9279 x253
Email: martin.dubuc@edgeflow.com Email: martin.dubuc@meriton.com
Sudheer Dharanikota Sudheer Dharanikota
Postal: Nayna Networks, Inc. Postal: Nayna Networks, Inc.
157 Topaz Street 157 Topaz Street
Milipitas, CA 95035 Milipitas, CA 95035
Tel: +1-408-956-8000 x357 Tel: +1-408-956-8000 x357
Email: sudheer@nayna.com Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
skipping to change at page 13, line 37 skipping to change at page 13, line 39
San Jose, CA 95138 San Jose, CA 95138
Email: evan@calient.net" Email: evan@calient.net"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for the "This MIB contains managed object definitions for the
Link Management Protocol (LMP) as Link Management Protocol (LMP) as
defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., defined in: Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, D., Rekhter, Y., Berger, L., Saha, D.,
Basak, D., Sandick, H., Zinin, A., and Basak, D., Sandick, H., Zinin, A., and
Rajagopalan, B., Link Management Protocol, Rajagopalan, B., Link Management Protocol,
Internet Draft <draft-ietf-ccamp-lmp-01.txt>, Internet Draft <draft-ietf-ccamp-lmp-02.txt>,
September 2001." November 2001."
-- Revision history. -- Revision history.
REVISION REVISION
"200110181200Z" -- 18 October 2001 12:00:00 EST "200202261200Z" -- 26 February 2002 12:00:00 EST
DESCRIPTION
"- Used latest MIB boiler plate.
- Added lmpFullModuleCompliance conformance statement.
- Replaced IpAddress with InetAddress.
- Added lmpOperStatus.
- Added lmpCcHelloIntervalNegotiated and
lmpCcHelloDeadIntervalNegotiated.
- Converted all 64-bit counters to 32-bit counters.
- Added counters for all LMP message types.
- Added counters to monitor data-bearing link tests.
- Reintroduced lmpNbrRetransmitTimeout.
- Added lmpDataBearingLinkNumberingType and
lmpDataBearingLinkRemoteIpAddress.
- Split data-bearing link operational status into active and
passive operational status.
- Updated description of all row status and storage type objects.
- Updated references."
REVISION
"200110211200Z" -- 21 October 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"- Minor syntax fixes. "- Minor syntax fixes.
- Added lmpCcId. Changed type of lmpRemoteCcId. - Added lmpCcId. Changed type of lmpRemoteCcId.
- Updated lmpTeLinkEncodingType. - Updated lmpTeLinkEncodingType.
- Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their - Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their
content can be derived from LINK-BUNDLING-MIB). content can be derived from LINK-BUNDLING-MIB).
- Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and - Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and
lmpDataBearingLinkCounterDiscontinuityTime. lmpDataBearingLinkCounterDiscontinuityTime.
- Moved lmpTeLinkBitRate and lmpTeLinkWavelength to - Moved lmpTeLinkBitRate and lmpTeLinkWavelength to
lmpLinkVerificationTable. lmpLinkVerificationTable.
- Updated lmpDataBearingLinkOperStatus. - Updated lmpDataBearingLinkOperStatus.
- Modified performance counters to account for changes in - Modified performance counters to account for changes in
channel status message types. channel status message types.
- Changed indices for lmpTeLinkPropertyMismatch and - Changed indices for lmpTeLinkPropertyMismatch and
lmpDataBearingLinkPropertyMismatch traps. lmpDataBearingLinkPropertyMismatch notifications.
- Renamed lmpNbrLinkSumRetransmitInterval. Removed - Renamed lmpNbrLinkSumRetransmitInterval. Removed
lmpNbrRetransmitTimeout. lmpNbrRetransmitTimeout.
- Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole." - Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole."
REVISION REVISION
"200105221200Z" -- 22 May 2001 12:00:00 EST "200105221200Z" -- 22 May 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Updates based on IETF-50 feedback. Aligned with "Updates based on IETF-50 feedback. Aligned with
upcoming version of LMP draft." upcoming version of LMP draft."
REVISION REVISION
"200102221200Z" -- 22 February 2001 12:00:00 EST "200102221200Z" -- 22 February 2001 12:00:00 EST
skipping to change at page 14, line 36 skipping to change at page 15, line 9
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial draft version."
::= { experimental 113 } ::= { experimental 113 }
-- Textual Conventions -- Textual Conventions
NodeID ::= TEXTUAL-CONVENTION NodeID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents a Node ID." "This value represents a Node ID."
SYNTAX IpAddress SYNTAX InetAddress
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
LmpRetransmitInterval ::= TEXTUAL-CONVENTION LmpRetransmitInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The retransmission interval delay in milliseconds." "The retransmission interval delay in milliseconds."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications
lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 }
-- Tables, Scalars -- Tables, Scalars
lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 }
-- Conformance -- Conformance
lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 }
lmpAdminStatus OBJECT-TYPE lmpAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP on the node." "The desired operational status of LMP on the node."
DEFVAL { up } DEFVAL { up }
::= { lmpObjects 1 } ::= { lmpObjects 1 }
lmpOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual operational status of LMP on the node."
::= { 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 to which control channels "This table specifies the neighbor node(s) to which control channels
may be established." may be established."
::= { lmpObjects 2 } ::= { 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 }
::= { lmpNbrTable 1 } ::= { lmpNbrTable 1 }
LmpNbrEntry ::= SEQUENCE { LmpNbrEntry ::= SEQUENCE {
lmpNbrNodeId NodeID, lmpNbrNodeId NodeID,
lmpNbrRetransmitInterval LmpRetransmitInterval, lmpNbrRetransmitInterval LmpRetransmitInterval,
lmpNbrRetransmitTimeout Unsigned32,
lmpNbrAdminStatus INTEGER, lmpNbrAdminStatus INTEGER,
lmpNbrOperStatus INTEGER, lmpNbrOperStatus INTEGER,
lmpNbrRowStatus RowStatus, lmpNbrRowStatus RowStatus,
lmpNbrStorageType StorageType lmpNbrStorageType StorageType
} }
lmpNbrNodeId OBJECT-TYPE lmpNbrNodeId OBJECT-TYPE
SYNTAX NodeID SYNTAX NodeID
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a unique index for an entry in the "This is a unique index for an entry in the LmpNbrTable.
LmpNbrTable. This value represents the This value represents the remote Node ID."
remote Node ID."
::= { lmpNbrEntry 1 } ::= { lmpNbrEntry 1 }
lmpNbrRetransmitInterval OBJECT-TYPE lmpNbrRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the interval that is used for the "This object specifies the interval that is used for the
retransmission of LinkSummary, BeginVerify and EndVerify messages." retransmission of LinkSummary, BeginVerify and EndVerify messages."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpNbrEntry 2 } ::= { lmpNbrEntry 2 }
lmpNbrRetransmitTimeout OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the LinkSummary, BeginVerify and EndVerify
retransmission timeout period. If the specified timeout expires
and the LinkSummary, BeginVerify and EndVerify message has not yet
been acknowledged with a LinkSummaryAck, BeginVerifyAck or
EndVerifyAck message, a node can stop retransmitting the LinkSummary,
BeginVerify or EndVerify messages. A value of 0 is used to indicate
that a node should never stop retransmission."
REFERENCE
"draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, November 2001."
DEFVAL { 0 }
::= { lmpNbrEntry 7 }
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 }
lmpNbrOperStatus OBJECT-TYPE lmpNbrOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
skipping to change at page 17, line 4 skipping to change at page 18, line 4
DESCRIPTION DESCRIPTION
"The actual operational status of LMP to this remote node." "The actual operational status of LMP to this remote node."
::= { lmpNbrEntry 4 } ::= { lmpNbrEntry 4 }
lmpNbrRowStatus OBJECT-TYPE lmpNbrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when lmpNbrRowStatus is active."
::= { lmpNbrEntry 5 } ::= { lmpNbrEntry 5 }
lmpNbrStorageType OBJECT-TYPE lmpNbrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this entry." "The storage type for this conceptual row in the
lmpNbrTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { lmpNbrEntry 6 } ::= { lmpNbrEntry 6 }
-- End of lmpNbrTable -- End of lmpNbrTable
lmpCcHelloIntervalDefault OBJECT-TYPE lmpCcHelloIntervalDefault OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default value for the HelloInterval "This object specifies the default value for the HelloInterval
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." indicates how frequently LMP Hello messages will be sent. It
is used a the default value for lmpCcHelloInterval."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpObjects 3 } ::= { 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." HelloInterval parameter. It is used as a default value
::= { lmpObjects 4 } for lmpCcHelloIntervalMin."
::= { lmpObjects 5 }
lmpCcHelloIntervalDefaultMax OBJECT-TYPE lmpCcHelloIntervalDefaultMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default maximum value for the "This object specifies the default maximum value for the
HelloInterval parameter." HelloInterval parameter. It is used as a default value
::= { lmpObjects 5 } for lmpCcHelloIntervalMax."
::= { 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 to
use in the Hello protocol keep-alive phase. It indicates how long use in the Hello protocol keep-alive phase. It indicates how long
a device should wait before declaring the control channel dead. a device should wait before declaring the control channel dead.
The HelloDeadInterval parameter must be greater than the The HelloDeadInterval parameter should be at least three times the
HelloInterval parameter and should be at least three times the value of HelloInterval. It is used a a default value for
value of HelloInterval." lmpCcHelloDeadInterval."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpObjects 6 } ::= { 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." HelloDeadInterval parameter. It is used as a default value
::= { lmpObjects 7 } for lmpCcHelloDeadIntervalMin."
::= { lmpObjects 8 }
lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default maximum value for the "This object specifies the default maximum value for the
HelloDeadInterval parameter." HelloDeadInterval parameter. It is used as a default value
::= { lmpObjects 8 } for lmpCcHelloDeadIntervalMax."
::= { lmpObjects 9 }
-- LMP Control Channel Table -- LMP Control Channel Table
lmpControlChannelTable OBJECT-TYPE lmpControlChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpControlChannelEntry SYNTAX SEQUENCE OF LmpControlChannelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies LMP control channel information." "This table specifies LMP control channel information."
::= { lmpObjects 9 } ::= { 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 lmpCcIsIf
set to true(2), then a corresponding entry is created in ifTable as set to true(2), then a corresponding entry is created in ifTable as
well (see RFC 2863)." well (see RFC 2863)."
skipping to change at page 19, line 27 skipping to change at page 20, line 36
lmpCcIsIf TruthValue, lmpCcIsIf TruthValue,
lmpCcNbrNodeId NodeID, lmpCcNbrNodeId NodeID,
lmpRemoteCcId Unsigned32, lmpRemoteCcId Unsigned32,
lmpCcSetupRole INTEGER, lmpCcSetupRole INTEGER,
lmpCcAuthentication TruthValue, lmpCcAuthentication TruthValue,
lmpCcConfigRetransmitInterval LmpRetransmitInterval, lmpCcConfigRetransmitInterval LmpRetransmitInterval,
lmpCcConfigRetransmitTimeout Unsigned32, lmpCcConfigRetransmitTimeout Unsigned32,
lmpCcHelloInterval LmpInterval, lmpCcHelloInterval LmpInterval,
lmpCcHelloIntervalMin LmpInterval, lmpCcHelloIntervalMin LmpInterval,
lmpCcHelloIntervalMax LmpInterval, lmpCcHelloIntervalMax LmpInterval,
lmpCcHelloIntervalNegotiated LmpInterval,
lmpCcHelloDeadInterval LmpInterval, lmpCcHelloDeadInterval LmpInterval,
lmpCcHelloDeadIntervalMin LmpInterval, lmpCcHelloDeadIntervalMin LmpInterval,
lmpCcHelloDeadIntervalMax LmpInterval, lmpCcHelloDeadIntervalMax 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
MAX-ACCESS read-create MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the local control channel identifier." "This value represents the local control channel identifier."
::= { 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. If set to 0, "This value represents the underlying interface index, i.e. the
then the control channel is not associated with any underlying interface index of the interface over which the LMP interface
interface. If the control channel is not associated with an will transmit its traffic. If set to 0, then the control channel
underlying interface, the control channel's operational status is not associated with any underlying interface. If the control
must not be up(1), nor should the control channel forward or channel is not associated with an underlying interface, the control
receive traffic." channel's operational 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 }
lmpCcNbrNodeId OBJECT-TYPE lmpCcNbrNodeId OBJECT-TYPE
SYNTAX NodeID SYNTAX NodeID
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the control channel remote node. "This is the Node ID of the control channel remote node.
This value gets created by the node when a Config message This value is either configured or gets created by the node
is received or when an outgoing Config message is acknowledged when a Config message is received or when an outgoing Config
by the remote node." message is acknowledged by the remote node."
::= { 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. It is
determined during the negotiation phase. A value determined during the negotiation phase. A value
of zero means that the remote control channel identifier has not of zero means that the remote control channel identifier has not
yet been assigned." yet been learnt."
::= { lmpControlChannelEntry 5 } ::= { lmpControlChannelEntry 5 }
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 of this
control channel. An active node will initiate establishment. A control channel. An active node will initiate establishment. A
passive node will wait for the remote node to initiate. A pair passive node will wait for the remote node to initiate. A pair
skipping to change at page 21, line 14 skipping to change at page 22, line 26
::= { lmpControlChannelEntry 6 } ::= { lmpControlChannelEntry 6 }
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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpControlChannelEntry 7 } ::= { lmpControlChannelEntry 7 }
lmpCcConfigRetransmitInterval OBJECT-TYPE lmpCcConfigRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the interval that is used for the "This object specifies the interval that is used for the
retransmission of Config messages during the parameter retransmission of Config messages during the parameter
negotiation phase." negotiation phase."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpControlChannelEntry 8 } ::= { lmpControlChannelEntry 8 }
lmpCcConfigRetransmitTimeout OBJECT-TYPE lmpCcConfigRetransmitTimeout OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Config retransmission timeout "This object specifies the Config retransmission timeout
period. If the specified timeout expires and no Config, period. If the specified timeout expires and no Config,
ConfigAck or ConfigNack message has been received, a node ConfigAck or ConfigNack message has been received, a node
can stop retransmitting Config messages on the control can stop retransmitting Config messages on the control
channel. A value of 0 is used to indicate that a node should channel. A value of 0 is used to indicate that a node should
never stop retransmission." never stop retransmission. This parameter (if non-zero)
should be greater than lmpCcConfigRetransmitInterval."
REFERENCE REFERENCE
"draft-ccamp-ietf-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
DEFVAL { 0 } DEFVAL { 0 }
::= { 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. Once the control channel is active, it represents parameter. The default value for this object should be
the negotiated value of the HelloInterval." set to lmpCcHelloIntervalDefault."
::= { lmpControlChannelEntry 10 } ::= { lmpControlChannelEntry 10 }
lmpCcHelloIntervalMin OBJECT-TYPE lmpCcHelloIntervalMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum value for the "This object specifies the minimum value for the
HelloInterval parameter." HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMinDefault."
::= { lmpControlChannelEntry 11 } ::= { lmpControlChannelEntry 11 }
lmpCcHelloIntervalMax OBJECT-TYPE lmpCcHelloIntervalMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum value for the "This object specifies the maximum value for the
HelloInterval parameter." HelloInterval parameter. The default value for this
object should be set to lmpCcHelloIntervalMaxDefault."
::= { lmpControlChannelEntry 12 } ::= { lmpControlChannelEntry 12 }
lmpCcHelloIntervalNegotiated OBJECT-TYPE
SYNTAX LmpInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Once the control channel is active, this object represents
the negotiated HelloInterval value."
::= { lmpControlChannelEntry 13 }
lmpCcHelloDeadInterval OBJECT-TYPE lmpCcHelloDeadInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloDeadInterval "This object specifies the value of the HelloDeadInterval
parameter. Once the control channel is active, it represents parameter. The default value for this object should be
the negotiated value of the HelloDeadInterval." set to lmpCcHelloDeadIntervalDefault."
::= { lmpControlChannelEntry 13 } ::= { lmpControlChannelEntry 14 }
lmpCcHelloDeadIntervalMin OBJECT-TYPE lmpCcHelloDeadIntervalMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the minimum value for the "This object specifies the minimum value for the
HelloDeadInterval parameter." HelloDeadInterval parameter. The default value for this
::= { lmpControlChannelEntry 14 } object should be set to lmpCcHelloDeadIntervalMinDefault."
::= { lmpControlChannelEntry 15 }
lmpCcHelloDeadIntervalMax OBJECT-TYPE lmpCcHelloDeadIntervalMax OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum value for the "This object specifies the maximum value for the
HelloDeadInterval parameter." HelloDeadInterval parameter. The default value for this
::= { lmpControlChannelEntry 15 } object should be set to lmpCcHelloIntervalMaxDefault."
::= { lmpControlChannelEntry 16 }
lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE
SYNTAX LmpInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Once the control channel is active, this object represents
the negotiated HelloDeadInterval value."
::= { lmpControlChannelEntry 17 }
lmpCcLastChange OBJECT-TYPE lmpCcLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the control channel entered "The value of sysUpTime at the time the control channel entered
its current operational state. If the current state was its current operational state. If the current state was
entered prior to the last re-initialization of the local entered prior to the last re-initialization of the local
network management subsystem, then this object contains a network management subsystem, then this object contains a
zero value." zero value."
::= { lmpControlChannelEntry 16 } ::= { lmpControlChannelEntry 18 }
lmpCcAdminStatus OBJECT-TYPE lmpCcAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of this control channel." "The desired operational status of this control channel."
::= { lmpControlChannelEntry 17 } ::= { lmpControlChannelEntry 19 }
lmpCcOperStatus OBJECT-TYPE lmpCcOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
configSnd(3), configSnd(3),
configRcv(4), configRcv(4),
active(5), active(5),
goingDown(6) goingDown(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this control channel "The actual operational status of this control channel
interface." interface."
::= { lmpControlChannelEntry 18 } ::= { lmpControlChannelEntry 20 }
lmpCcRowStatus OBJECT-TYPE lmpCcRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
::= { lmpControlChannelEntry 19 } can be changed when lmpCcRowStatus is active."
::= { lmpControlChannelEntry 21 }
lmpCcStorageType OBJECT-TYPE lmpCcStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this entry." "The storage type for this conceptual row in the
::= { lmpControlChannelEntry 20 } lmpControlChannelTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { lmpControlChannelEntry 22 }
-- End of lmpControlChannelTable -- End of lmpControlChannelTable
-- LMP Control Channel Performance Table -- LMP Control Channel Performance Table
lmpControlChannelPerfTable OBJECT-TYPE lmpControlChannelPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpControlChannelPerfEntry SYNTAX SEQUENCE OF LmpControlChannelPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies LMP control channel performance counters." "This table specifies LMP control channel performance counters."
::= { lmpObjects 10 } ::= { 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 }
::= { lmpControlChannelPerfTable 1 } ::= { lmpControlChannelPerfTable 1 }
LmpControlChannelPerfEntry ::= SEQUENCE { LmpControlChannelPerfEntry ::= SEQUENCE {
lmpCcHCInOctets Counter64, lmpCcInOctets Counter32,
lmpCcInDiscards Counter32, lmpCcInDiscards Counter32,
lmpCcInErrors Counter32, lmpCcInErrors Counter32,
lmpCcHCOutOctets Counter64, lmpCcOutOctets Counter32,
lmpCcOutDiscards Counter32, lmpCcOutDiscards Counter32,
lmpCcOutErrors Counter32, lmpCcOutErrors Counter32,
lmpCcHCHelloReceived Counter64,
lmpCcHCHelloSent Counter64,
lmpCcConfigReceived Counter32, lmpCcConfigReceived Counter32,
lmpCcConfigSent Counter32, lmpCcConfigSent Counter32,
lmpCcConfigRetransmit Counter32, lmpCcConfigRetransmit Counter32,
lmpCcConfigAckReceived Counter32,
lmpCcConfigAckSent Counter32,
lmpCcConfigNackReceived Counter32,
lmpCcConfigNackSent Counter32,
lmpCcHelloReceived Counter32,
lmpCcHelloSent Counter32,
lmpCcBeginVerifyReceived Counter32,
lmpCcBeginVerifySent Counter32,
lmpCcBeginVerifyRetransmit Counter32,
lmpCcBeginVerifyAckReceived Counter32,
lmpCcBeginVerifyAckSent Counter32,
lmpCcBeginVerifyNackReceived Counter32,
lmpCcBeginVerifyNackSent Counter32,
lmpCcEndVerifyReceived Counter32,
lmpCcEndVerifySent Counter32,
lmpCcEndVerifyRetransmit Counter32,
lmpCcEndVerifyAckReceived Counter32,
lmpCcEndVerifyAckSent Counter32,
lmpCcTestStatusSuccessReceived Counter32,
lmpCcTestStatusSuccessSent Counter32,
lmpCcTestStatusSuccessRetransmit Counter32,
lmpCcTestStatusFailureReceived Counter32,
lmpCcTestStatusFailureSent Counter32,
lmpCcTestStatusFailureRetransmit Counter32,
lmpCcTestStatusAckReceived Counter32,
lmpCcTestStatusAckSent Counter32,
lmpCcLinkSummaryReceived Counter32, lmpCcLinkSummaryReceived Counter32,
lmpCcLinkSummarySent Counter32, lmpCcLinkSummarySent Counter32,
lmpCcLinkSummaryRetransmit Counter32, lmpCcLinkSummaryRetransmit Counter32,
lmpCcLinkSummaryAckReceived Counter32,
lmpCcLinkSummaryAckSent Counter32,
lmpCcLinkSummaryNackReceived Counter32,
lmpCcLinkSummaryNackSent Counter32,
lmpCcChannelStatusReceived Counter32, lmpCcChannelStatusReceived Counter32,
lmpCcChannelStatusSent Counter32, lmpCcChannelStatusSent Counter32,
lmpCcChannelStatusRetransmit Counter32,
lmpCcChannelStatusAckReceived Counter32,
lmpCcChannelStatusAckSent Counter32,
lmpCcChannelStatusRequestReceived Counter32, lmpCcChannelStatusRequestReceived Counter32,
lmpCcChannelStatusRequestSent Counter32, lmpCcChannelStatusRequestSent Counter32,
lmpCcChannelStatusResponseReceived Counter32, lmpCcChannelStatusRequestRetransmit Counter32,
lmpCcChannelStatusResponseSent Counter32, lmpCcChannelStatusResponseSent Counter32,
lmpCcChannelStatusResponseReceived Counter32,
lmpCcCounterDiscontinuityTime TimeStamp lmpCcCounterDiscontinuityTime TimeStamp
} }
lmpCcHCInOctets OBJECT-TYPE lmpCcInOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of LMP message octets received on the "The total number of LMP message octets received on the
control channel." control channel."
::= { lmpControlChannelPerfEntry 1 } ::= { lmpControlChannelPerfEntry 1 }
lmpCcInDiscards OBJECT-TYPE lmpCcInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 25, line 46 skipping to change at page 28, line 21
lmpCcInErrors OBJECT-TYPE lmpCcInErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of inbound packets that contained errors "The number of inbound packets that contained errors
preventing them from being processed by LMP." preventing them from being processed by LMP."
::= { lmpControlChannelPerfEntry 3 } ::= { lmpControlChannelPerfEntry 3 }
lmpCcHCOutOctets OBJECT-TYPE lmpCcOutOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of LMP message octets transmitted out of "The total number of LMP message octets transmitted out of
the control channel." the control channel."
::= { lmpControlChannelPerfEntry 4 } ::= { lmpControlChannelPerfEntry 4 }
lmpCcOutDiscards OBJECT-TYPE lmpCcOutDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 26, line 27 skipping to change at page 28, line 50
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 }
lmpCcHCHelloReceived OBJECT-TYPE lmpCcConfigReceived OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Hello messages that have "This object counts the number of Config messages that have
been received on this control channel." been received on this control channel."
::= { lmpControlChannelPerfEntry 7 } ::= { lmpControlChannelPerfEntry 7 }
lmpCcHCHelloSent OBJECT-TYPE lmpCcConfigSent OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of Hello messages that have "This object counts the number of Config messages that have
been sent on this control channel." been sent on this control channel."
::= { lmpControlChannelPerfEntry 8 } ::= { lmpControlChannelPerfEntry 8 }
lmpCcConfigReceived OBJECT-TYPE lmpCcConfigRetransmit 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 Config messages that have "This object counts the number of Config messages that
been received on this control channel." have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 9 } ::= { lmpControlChannelPerfEntry 9 }
lmpCcConfigSent OBJECT-TYPE lmpCcConfigAckReceived 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 Config messages that have "This object counts the number of ConfigAck messages that have
been sent on this control channel." been received on this control channel."
::= { lmpControlChannelPerfEntry 10 } ::= { lmpControlChannelPerfEntry 10 }
lmpCcConfigRetransmit OBJECT-TYPE lmpCcConfigAckSent 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 Config messages that "This object counts the number of ConfigAck messages that have
have been retransmitted over this interface." been sent on this control channel."
::= { lmpControlChannelPerfEntry 11 } ::= { lmpControlChannelPerfEntry 11 }
lmpCcConfigNackReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ConfigNack messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 12 }
lmpCcConfigNackSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ConfigNack messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 13 }
lmpCcHelloReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of Hello messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 14 }
lmpCcHelloSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of Hello messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 15 }
lmpCcBeginVerifyReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerify messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 16 }
lmpCcBeginVerifySent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerify messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 17 }
lmpCcBeginVerifyRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerify messages that
have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 18 }
lmpCcBeginVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 19 }
lmpCcBeginVerifyAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerifyAck messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 20 }
lmpCcBeginVerifyNackReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 21 }
lmpCcBeginVerifyNackSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of BeginVerifyNack messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 22 }
lmpCcEndVerifyReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of EndVerify messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 23 }
lmpCcEndVerifySent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of EndVerify messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 24 }
lmpCcEndVerifyRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of EndVerify messages that
have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 25 }
lmpCcEndVerifyAckReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of EndVerifyAck messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 26 }
lmpCcEndVerifyAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of EndVerifyAck messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 27 }
lmpCcTestStatusSuccessReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 28 }
lmpCcTestStatusSuccessSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusSuccess messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 29 }
lmpCcTestStatusSuccessRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusSuccess messages that
have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 30 }
lmpCcTestStatusFailureReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusFailure messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 31 }
lmpCcTestStatusFailureSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusFailure messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 32 }
lmpCcTestStatusFailureRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusFailure messages that
have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 33 }
lmpCcTestStatusAckReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusAck messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 34 }
lmpCcTestStatusAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of TestStatusAck messages that have
been sent on this control channel."
::= { 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 that have
been received on this control channel." been received on this control channel."
::= { lmpControlChannelPerfEntry 12 } ::= { 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 that have
been sent on this control channel." been sent on this control channel."
::= { lmpControlChannelPerfEntry 13 } ::= { 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 interface." have been retransmitted over this control channel."
::= { lmpControlChannelPerfEntry 14 } ::= { lmpControlChannelPerfEntry 38 }
lmpCcLinkSummaryAckReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 39 }
lmpCcLinkSummaryAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of LinkSummaryAck messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 40 }
lmpCcLinkSummaryNackReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 41 }
lmpCcLinkSummaryNackSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of LinkSummaryNack messages that have
been sent on this control channel."
::= { 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 that have
been received on this control channel." been received on this control channel."
::= { lmpControlChannelPerfEntry 15 } ::= { 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 that have
been sent on this control channel." been sent on this control channel."
::= { lmpControlChannelPerfEntry 16 } ::= { lmpControlChannelPerfEntry 44 }
lmpCcChannelStatusRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatus messages that have
been retransmitted on this control channel."
::= { lmpControlChannelPerfEntry 45 }
lmpCcChannelStatusAckReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusAck messages that have
been received on this control channel."
::= { lmpControlChannelPerfEntry 46 }
lmpCcChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatus messages that have
been sent on this control channel."
::= { lmpControlChannelPerfEntry 47 }
lmpCcChannelStatusRequestReceived OBJECT-TYPE lmpCcChannelStatusRequestReceived 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 that
have been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 17 } ::= { lmpControlChannelPerfEntry 48 }
lmpCcChannelStatusRequestSent OBJECT-TYPE lmpCcChannelStatusRequestSent 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 that
have been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 18 } ::= { lmpControlChannelPerfEntry 49 }
lmpCcChannelStatusRequestRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusRequest messages that
have been retransmitted on this control channel."
::= { lmpControlChannelPerfEntry 50 }
lmpCcChannelStatusResponseReceived OBJECT-TYPE lmpCcChannelStatusResponseReceived 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 that
have been received on this control channel." have been received on this control channel."
::= { lmpControlChannelPerfEntry 19 } ::= { lmpControlChannelPerfEntry 51 }
lmpCcChannelStatusResponseSent OBJECT-TYPE lmpCcChannelStatusResponseSent 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 that
have been sent on this control channel." have been sent on this control channel."
::= { lmpControlChannelPerfEntry 20 } ::= { 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 or instances associated with this control channel of any Counter32 or
Counter64 object contained in the lmpControlChannelPerfTable. If Counter64 object contained in the lmpControlChannelPerfTable. 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."
::= { lmpControlChannelPerfEntry 21 } ::= { 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
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a collection of TE link." "This table contains a collection of TE link."
::= { lmpObjects 11 } ::= { lmpObjects 12 }
lmpTeLinkEntry OBJECT-TYPE lmpTeLinkEntry OBJECT-TYPE
SYNTAX LmpTeLinkEntry SYNTAX LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(TBD), i.e. for every TE link. An ifEntry ifType of teLink(TBD), i.e. for every TE link. An ifEntry
with an ifIndex must exist before the corresponding with an ifIndex must exist before the corresponding
teLinkEntry is created. If a TE link entry in the ifTable is teLinkEntry is created. If a TE link entry in the ifTable is
skipping to change at page 30, line 10 skipping to change at page 38, line 32
from the ifEntry. Setting the administrative status to from the ifEntry. Setting the administrative status to
testing prompts LMP to start link verification on the TE link. testing prompts LMP to start link verification on the TE link.
Information about the TE link that is not LMP specific is also Information about the TE link that is not LMP specific is also
contained in teLinkTable [BUNDLE-MIB]." contained in teLinkTable [BUNDLE-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrNodeId NodeID, lmpTeLinkNbrNodeId NodeID,
lmpTeLinkVerification TruthValue, lmpTeLinkVerification TruthValue,
lmpTeLinkFaultIsolation TruthValue, lmpTeLinkFaultManagement TruthValue,
lmpTeLinkDwdm TruthValue, lmpTeLinkDwdm TruthValue,
lmpTeLinkOperStatus INTEGER, lmpTeLinkOperStatus INTEGER,
lmpTeLinkRowStatus RowStatus, lmpTeLinkRowStatus RowStatus,
lmpTeLinkStorageType StorageType lmpTeLinkStorageType StorageType
} }
lmpTeLinkNbrNodeId OBJECT-TYPE lmpTeLinkNbrNodeId OBJECT-TYPE
SYNTAX NodeID SYNTAX NodeID
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the Node ID of the TE link remote node." "This is the Node ID of the TE link remote node. This value
may be learned during control channel parameter negotiation
phase (in the Config message)."
::= { 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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpTeLinkEntry 2 } ::= { lmpTeLinkEntry 2 }
lmpTeLinkFaultIsolation 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 isolation "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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { 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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpTeLinkEntry 4 } ::= { lmpTeLinkEntry 4 }
lmpTeLinkOperStatus OBJECT-TYPE lmpTeLinkOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2), testing(3), degraded(4) } 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 status indicates that the TE link verification. A degraded state indicates that there are
cannot provide the provisioned protection level, but yet, no active control channel between the pair of nodes that
there is no disruption of service. For instance, if the form the endpoints of the TE link, but yet at least one
protection type is 1+1 and one link is down, the TE link data-bearing links on the TE link is allocated."
still carries the requested amount of data traffic, but
this traffic is not protected anymore."
::= { lmpTeLinkEntry 5 } ::= { lmpTeLinkEntry 5 }
lmpTeLinkRowStatus OBJECT-TYPE lmpTeLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when lmpTeLinkRowStatus is active."
::= { lmpTeLinkEntry 6 } ::= { lmpTeLinkEntry 6 }
lmpTeLinkStorageType OBJECT-TYPE lmpTeLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." lmpTeLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any
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 procedure
is executed. The interval is in milliseconds." is executed. The interval is in milliseconds."
::= { lmpObjects 12 } ::= { 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 "This table specifies TE link information associated with the
associated with the LMP verification procedure." LMP verification procedure."
::= { lmpObjects 13 } ::= { lmpObjects 14 }
lmpLinkVerificationEntry OBJECT-TYPE lmpLinkVerificationEntry OBJECT-TYPE
SYNTAX LmpLinkVerificationEntry SYNTAX LmpLinkVerificationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every TE link that supports the LMP verification every TE link that supports the LMP verification
procedure." procedure."
AUGMENTS { lmpTeLinkEntry } AUGMENTS { lmpTeLinkEntry }
skipping to change at page 33, line 6 skipping to change at page 41, line 34
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 interval
at which the Test messages are sent." at which the Test messages are sent."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { 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-bearing
links. It specifies the observation period used to detect a Test links. It specifies the observation period used to detect a Test
message at the remote node." message at the remote node."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpLinkVerificationEntry 2 } ::= { lmpLinkVerificationEntry 2 }
lmpVerifyTransportMechanism OBJECT-TYPE lmpVerifyTransportMechanism OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
-- SONET/SDH encoding type: -- SONET/SDH encoding type:
j0OverheadBytes(0), j016OverheadBytes(1),
dccSectionOverheadBytes(1), j064OverheadBytes(2),
dccLineOverheadBytes(2), dccSectionOverheadBytes(3),
pos(3) dccLineOverheadBytes(4),
pos(5)
-- GigE encoding type: TBD -- GigE encoding type: TBD
-- 10GigE encoding type: TBD -- 10GigE encoding type: TBD
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This defines the transport mechanism for the Test messages. The "This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { 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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { 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 be
set to 0." set to 0."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpLinkVerificationEntry 6 } ::= { lmpLinkVerificationEntry 6 }
-- End of lmpLinkVerificationTable -- End of lmpLinkVerificationTable
-- LMP Data Bearing Link Table -- LMP Data Bearing Link Table
lmpDataBearingLinkTable OBJECT-TYPE lmpDataBearingLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataBearingLinkEntry SYNTAX SEQUENCE OF LmpDataBearingLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the data-bearing links managed by the "This table specifies the data-bearing links managed by the
LMP." LMP."
::= { lmpObjects 14 } ::= { lmpObjects 15 }
lmpDataBearingLinkEntry OBJECT-TYPE lmpDataBearingLinkEntry OBJECT-TYPE
SYNTAX LmpDataBearingLinkEntry SYNTAX LmpDataBearingLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a data-bearing link. An ifEntry with an ifIndex must exist a data-bearing link. An ifEntry with an ifIndex must exist
before the corresponding lmpDataBearingLinkEntry is created. before the corresponding lmpDataBearingLinkEntry is created.
If an entry representing the data-bearing link is destroyed in If an entry representing the data-bearing link is destroyed in
the ifTable, then so is the corresponding entry in the the ifTable, then so is the corresponding entry in the
lmpDataBearingLinkTable. The administrative status value is lmpDataBearingLinkTable. 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 dataBearingChannelTable used to get information in the dataBearingChannelTable
[BUNDLE-MIB]." [BUNDLE-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataBearingLinkTable 1 } ::= { lmpDataBearingLinkTable 1 }
LmpDataBearingLinkEntry ::= SEQUENCE { LmpDataBearingLinkEntry ::= SEQUENCE {
lmpDataBearingLinkType INTEGER, lmpDataBearingLinkType INTEGER,
lmpDataBearingLinkNumberingType INTEGER,
lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero,
lmpDataBearingLinkRemoteIpAddress InetAddress,
lmpDataBearingLinkEncodingType INTEGER, lmpDataBearingLinkEncodingType INTEGER,
lmpDataBearingLinkOperStatus INTEGER, lmpDataBearingLinkActiveOperStatus INTEGER,
lmpDataBearingLinkPassiveOperStatus INTEGER,
lmpDataBearingLinkRowStatus RowStatus, lmpDataBearingLinkRowStatus RowStatus,
lmpDataBearingLinkStorageType StorageType lmpDataBearingLinkStorageType StorageType
} }
lmpDataBearingLinkType OBJECT-TYPE lmpDataBearingLinkType 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
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpDataBearingLinkEntry 1 } ::= { lmpDataBearingLinkEntry 1 }
lmpDataBearingLinkNumberingType OBJECT-TYPE
SYNTAX INTEGER {
unnumbered(1),
ipV4(2),
ipV6(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This attribute specifies the data-bearing link numbering
type."
::= { lmpDataBearingLinkEntry 2 }
lmpDataBearingLinkRemoteIfId OBJECT-TYPE lmpDataBearingLinkRemoteIfId 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."
::= { lmpDataBearingLinkEntry 2 } ::= { lmpDataBearingLinkEntry 3 }
lmpDataBearingLinkRemoteIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"IP address of the remote end point. This
information is either configured manually or is
communicated by the remote node during the link verification
procedure."
::= { lmpDataBearingLinkEntry 4 }
lmpDataBearingLinkEncodingType OBJECT-TYPE lmpDataBearingLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packet(1), packet(1),
ethernetV2(2), ethernetV2Dix(2),
ansiPdh(3), ansiPdh(3),
etsiPdh(4), etsiPdh(4),
sdhItu1996(5), sdhItuG707(5),
sonetAnsi1995(6), sonetAnsiT1105(6),
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
ethernet8023(10), ethernet8023(10),
sdhItu2000(11), fiberChannel(11)
sonetAnsi2000(12)
} }
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
"draft-ietf-mpls-generalized-signaling-05.txt - Generalized "draft-ietf-mpls-generalized-signaling-07.txt - Generalized
MPLS Signaling Functional Description, P. Ashwood-Smith, MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, July 2001." V. Sharma, G. Swallow, Z. Tang, November 2001."
::= { lmpDataBearingLinkEntry 3 } ::= { lmpDataBearingLinkEntry 5 }
lmpDataBearingLinkOperStatus OBJECT-TYPE lmpDataBearingLinkActiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
testing(4), testing(4) }
psvTst(5),
degraded(6) }
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
A data-bearing link is in the degraded state if the (active FSM)."
control channel and associated backup control channel(s) are
down but the data-bearing link is still operational."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, September 2001." B. Rajagopalan, November 2001."
::= { lmpDataBearingLinkEntry 4 } ::= { lmpDataBearingLinkEntry 6 }
lmpDataBearingLinkPassiveOperStatus OBJECT-TYPE
SYNTAX INTEGER {
upAlloc(1),
upFree(2),
down(3),
psvTst(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual operational status of this data-bearing link
(passive FSM)."
REFERENCE
"draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, November 2001."
::= { lmpDataBearingLinkEntry 7 }
lmpDataBearingLinkRowStatus OBJECT-TYPE lmpDataBearingLinkRowStatus 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." delete a row in this table. All read-create objects
::= { lmpDataBearingLinkEntry 5 } can be changed when lmpDataBearingLinkRowStatus is active."
::= { lmpDataBearingLinkEntry 8 }
lmpDataBearingLinkStorageType OBJECT-TYPE lmpDataBearingLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." lmpDataBearingLinkTable. Conceptual rows having the value
::= { lmpDataBearingLinkEntry 6 } 'permanent' need not allow write-access to any
columnar object in the row."
::= { lmpDataBearingLinkEntry 9 }
-- End of lmpDataBearingLinkTable -- End of lmpDataBearingLinkTable
-- LMP Data Bearing Link Performance Table -- LMP Data Bearing Link Performance Table
lmpDataBearingLinkPerfTable OBJECT-TYPE lmpDataBearingLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the data-bearing links LMP performance "This table specifies the data-bearing links LMP performance
counters." counters."
::= { lmpObjects 15 } ::= { lmpObjects 16 }
lmpDataBearingLinkPerfEntry OBJECT-TYPE lmpDataBearingLinkPerfEntry OBJECT-TYPE
SYNTAX LmpDataBearingLinkPerfEntry SYNTAX LmpDataBearingLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about "An entry in this table contains information about
the LMP performance counters for the data-bearing links." the LMP performance counters for the data-bearing links."
AUGMENTS { lmpDataBearingLinkEntry } AUGMENTS { lmpDataBearingLinkEntry }
::= { lmpDataBearingLinkPerfTable 1 } ::= { lmpDataBearingLinkPerfTable 1 }
LmpDataBearingLinkPerfEntry ::= SEQUENCE { LmpDataBearingLinkPerfEntry ::= SEQUENCE {
lmpDataBearingLinkTestReceived Counter32, lmpDataBearingLinkTestReceived Counter32,
lmpDataBearingLinkTestSent Counter32, lmpDataBearingLinkTestSent Counter32,
lmpDataBearingLinkActiveTestSuccess Counter32,
lmpDataBearingLinkActiveTestFailure Counter32,
lmpDataBearingLinkPassiveTestSuccess Counter32,
lmpDataBearingLinkPassiveTestFailure Counter32,
lmpDataBearingLinkCounterDiscontinuityTime TimeStamp lmpDataBearingLinkCounterDiscontinuityTime TimeStamp
} }
lmpDataBearingLinkTestReceived OBJECT-TYPE lmpDataBearingLinkTestReceived 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 Test messages that have "This object counts the number of Test messages that have
been received on this control channel." been received on this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 1 } ::= { lmpDataBearingLinkPerfEntry 1 }
lmpDataBearingLinkTestSent OBJECT-TYPE lmpDataBearingLinkTestSent 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 Test messages that have "This object counts the number of Test messages that have
been sent on this control channel." been sent on this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 2 } ::= { lmpDataBearingLinkPerfEntry 2 }
lmpDataBearingLinkActiveTestSuccess OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link test
that were successful on the active side of this data-
bearing link."
::= { lmpDataBearingLinkPerfEntry 3 }
lmpDataBearingLinkActiveTestFailure OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link test
that failed on the active side of this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 4 }
lmpDataBearingLinkPassiveTestSuccess OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link test
that were successful on the passive side of this data-
bearing link."
::= { lmpDataBearingLinkPerfEntry 5 }
lmpDataBearingLinkPassiveTestFailure OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link test
that failed on the passive side of this data-bearing link."
::= { lmpDataBearingLinkPerfEntry 6 }
lmpDataBearingLinkCounterDiscontinuityTime OBJECT-TYPE lmpDataBearingLinkCounterDiscontinuityTime 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 a
discontinuity. The relevant counters are the specific discontinuity. The relevant counters are the specific
instances associated with this data-bearing link of any Counter32 or instances associated with this data-bearing link of any Counter32 or
Counter64 object contained in the lmpDataBearingLinkPerfTable. If Counter64 object contained in the lmpDataBearingLinkPerfTable. 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."
::= { lmpDataBearingLinkPerfEntry 3 } ::= { lmpDataBearingLinkPerfEntry 7 }
-- End of lmpDataBearingLinkPerfTable -- End of lmpDataBearingLinkPerfTable
-- Notification Configuration -- Notification Configuration
lmpLinkPropertyMismatchTrapEnable OBJECT-TYPE lmpLinkPropertyMismatchNotifEnable 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 lmpDataBearingLinkPropertyMismatch traps, and lmpDataBearingLinkPropertyMismatch notifications,
otherwise these traps are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 16 } ::= { lmpObjects 17 }
lmpUnprotectedTrapEnable OBJECT-TYPE lmpUnprotectedNotifEnable 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 trap, generation of lmpUnprotected notifications,
otherwise these traps are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 17 } ::= { lmpObjects 18 }
lmpCcUpDownTrapEnable OBJECT-TYPE lmpCcUpDownNotifEnable 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 traps, lmpControlChannelUp and lmpControlChannelDown notifications,
otherwise these traps are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 18 } ::= { lmpObjects 19 }
lmpTeLinkTrapEnable OBJECT-TYPE lmpTeLinkNotifEnable 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 trap, generation of lmpTeLinkDegraded notification,
otherwise these traps are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { lmpObjects 19 } ::= { lmpObjects 20 }
lmpDataBearingLinkNotifEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, then it enables the
generation of lmpDataBearingLinkVerificationFailure
notification, otherwise these notifications are not emitted."
DEFVAL { false }
::= { lmpObjects 21 }
-- Notifications -- Notifications
-- Link Property Mismatch Notifications
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { teLinkRemoteIpAddr,
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. ifIndex is the mismatch is detected on the node. The received remote TE link
interface index of the misconfigured TE link. The received remote id of the misconfigured TE link is represented by either
TE link id is represented by either teLinkRemoteIpAddr teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
or teLinkIncomingIfId depending on whether the TE link is the TE link is numbered or unnumbered."
numbered or unnumbered."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { ifStackHigherLayer, OBJECTS { ifStackHigherLayer,
ifIndex,
lmpDataBearingLinkRemoteIfId } lmpDataBearingLinkRemoteIfId }
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. ifStackHigherLayer property mismatch is detected on the node. ifStackHigherLayer
is the interface index of the TE link. The second ifIndex is is the interface index of the TE link. The remote entity
the interface index of the data-bearing 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 the
LinkSummary message." LinkSummary message."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when all but one control channel "This notification is generated when all but one control channel
is operational. If the only operational control channel fails, is operational. If the only operational control channel fails,
then there will be no more control channels between the pair of then there will be no more control channels between the pair of
nodes and all the data-bearing links between the pair of nodes nodes and all the data-bearing links between the pair of nodes
will go to degraded state." will go to degraded state."
::= { lmpNotifications 3 } ::= { lmpNotifications 3 }
-- Control Channel Notifications
lmpControlChannelUp NOTIFICATION-TYPE lmpControlChannelUp NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { lmpCcId }
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." channel transitions to the up operational state."
::= { lmpNotifications 4 } ::= { lmpNotifications 4 }
lmpControlChannelDown NOTIFICATION-TYPE lmpControlChannelDown NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { lmpCcId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a control "This notification is generated when a control
channel transitions to the down operational state." channel transitions to the down operational state."
::= { lmpNotifications 5 } ::= { lmpNotifications 5 }
-- 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." object for a TE link enters the degraded state."
::= { lmpNotifications 6 } ::= { lmpNotifications 6 }
-- Data-bearing Link Notification
lmpDataBearingLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { ifIndex }
STATUS current
DESCRIPTION
"This notification is generated when a data-bearing
link verification fails."
::= { lmpNotifications 7 }
-- 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 }
lmpModuleCompliance MODULE-COMPLIANCE lmpFullModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
LMP MIB." configuration and monitoring of 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 unsupported.
MANDATORY-GROUPS { lmpNodeGroup, MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup, lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup, lmpLinkPropertyCorrelationGroup,
skipping to change at page 42, line 33 skipping to change at page 53, line 20
"This group is mandatory for devices which support "This group is mandatory for devices which support
control channels that are interfaces, in addition to control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply: lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)." lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup GROUP lmpLinkVerificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
the link verification procedure." the link verification procedure."
-- lmpNbrTable
OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT lmpNbrStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpControlChannelTable
OBJECT lmpCcRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) }
MIN-ACCESS read-only
DESCRIPTION
"A value of active(3), configuring(4), goingDown(5)
need not be supported."
OBJECT lmpCcStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpTeLinkTable
OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only
DESCRIPTION
"The testing(3) state need not be supported."
OBJECT lmpTeLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT lmpTeLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- lmpDataBearingLinkTable
OBJECT lmpDataBearingLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only
DESCRIPTION
"A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only
DESCRIPTION
"A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-only
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT lmpDataBearingLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
::= { lmpCompliances 1 }
lmpMonitoringModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that support the
monitoring of the LMP MIB."
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,
lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup,
lmpPerfGroup,
lmpTeLinkGroup,
lmpDataBearingLinkGroup }
GROUP lmpControlChannelIsNotInterfaceGroup
DESCRIPTION
"This group is mandatory for devices which support
control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)."
GROUP lmpControlChannelIsInterfaceGroup
DESCRIPTION
"This group is mandatory for devices which support
control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup
DESCRIPTION
"This group is mandatory for devices which support
the link verification procedure."
-- Scalars -- Scalars
OBJECT lmpAdminStatus OBJECT lmpAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpLinkVerificationInterval OBJECT lmpLinkVerificationInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 43, line 33 skipping to change at page 57, line 4
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRetransmitInterval OBJECT lmpNbrRetransmitInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRetransmitTimeout
MIN-ACCESS read-only
DESCRIPTION
"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
skipping to change at page 44, line 12 skipping to change at page 57, line 35
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
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcSetupRole OBJECT lmpCcSetupRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcAuthentication OBJECT lmpCcAuthentication
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 46, line 7 skipping to change at page 59, line 34
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
procedure is enabled." procedure is enabled."
OBJECT lmpTeLinkVerification OBJECT lmpTeLinkVerification
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkFaultIsolation OBJECT lmpTeLinkFaultManagement
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkDwdm OBJECT lmpTeLinkDwdm
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpTeLinkOperStatus OBJECT lmpTeLinkOperStatus
skipping to change at page 46, line 51 skipping to change at page 60, line 31
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."
-- lmpDataBearingLinkTable -- lmpDataBearingLinkTable
OBJECT lmpDataBearingLinkNumberingType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the link verification
procedure is enabled."
OBJECT lmpDataBearingLinkRemoteIfId OBJECT lmpDataBearingLinkRemoteIfId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
procedure is enabled." procedure is enabled."
OBJECT lmpDataBearingLinkRemoteIpAddress
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the link verification
procedure is enabled."
OBJECT lmpDataBearingLinkEncodingType OBJECT lmpDataBearingLinkEncodingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpDataBearingLinkOperStatus OBJECT lmpDataBearingLinkActiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) } SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"A value of testing(3) need not be supported." "A value of testing(3) need not be supported."
OBJECT lmpDataBearingLinkPassiveOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(4) }
MIN-ACCESS read-only
DESCRIPTION
"A value of psvTst(3) need not be supported."
OBJECT lmpDataBearingLinkRowStatus OBJECT lmpDataBearingLinkRowStatus
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 lmpDataBearingLinkStorageType OBJECT lmpDataBearingLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
::= { lmpCompliances 1 } ::= { lmpCompliances 2 }
-- Units of conformance -- Units of conformance
lmpNodeGroup OBJECT-GROUP lmpNodeGroup OBJECT-GROUP
OBJECTS { lmpAdminStatus, OBJECTS { lmpAdminStatus,
lmpOperStatus,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpUnprotectedTrapEnable lmpUnprotectedNotifEnable
} }
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 {
lmpNbrNodeId, lmpNbrNodeId,
lmpNbrRetransmitInterval, lmpNbrRetransmitInterval,
lmpNbrRetransmitTimeout,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpCcHelloIntervalDefault, lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin, lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax, lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault, lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin, lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax, lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId, lmpCcNbrNodeId,
lmpCcId, lmpCcId,
lmpRemoteCcId, lmpRemoteCcId,
lmpCcSetupRole, lmpCcSetupRole,
lmpCcAuthentication, lmpCcAuthentication,
lmpCcConfigRetransmitInterval, lmpCcConfigRetransmitInterval,
lmpCcConfigRetransmitTimeout, lmpCcConfigRetransmitTimeout,
lmpCcHelloInterval, lmpCcHelloInterval,
lmpCcHelloIntervalMin, lmpCcHelloIntervalMin,
lmpCcHelloIntervalMax, lmpCcHelloIntervalMax,
lmpCcHelloIntervalNegotiated,
lmpCcHelloDeadInterval, lmpCcHelloDeadInterval,
lmpCcHelloDeadIntervalMin, lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax, lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus, lmpCcOperStatus,
lmpCcRowStatus, lmpCcRowStatus,
lmpCcStorageType, lmpCcStorageType,
lmpCcUpDownTrapEnable lmpCcUpDownNotifEnable
} }
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 }
lmpControlChannelIsInterfaceGroup OBJECT-GROUP lmpControlChannelIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf } OBJECTS { lmpCcIsIf }
STATUS current STATUS current
skipping to change at page 49, line 15 skipping to change at page 63, line 17
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 { lmpLinkPropertyMismatchTrapEnable } OBJECTS { lmpLinkPropertyMismatchNotifEnable }
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,
lmpDataBearingLinkNotifEnable
} }
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 { lmpCcHCInOctets, OBJECTS { lmpCcInOctets,
lmpCcInDiscards, lmpCcInDiscards,
lmpCcInErrors, lmpCcInErrors,
lmpCcHCOutOctets, lmpCcOutOctets,
lmpCcOutDiscards, lmpCcOutDiscards,
lmpCcOutErrors, lmpCcOutErrors,
lmpCcHCHelloReceived,
lmpCcHCHelloSent,
lmpCcConfigReceived, lmpCcConfigReceived,
lmpCcConfigSent, lmpCcConfigSent,
lmpCcConfigRetransmit, lmpCcConfigRetransmit,
lmpCcConfigAckReceived,
lmpCcConfigAckSent,
lmpCcConfigNackSent,
lmpCcConfigNackReceived,
lmpCcHelloReceived,
lmpCcHelloSent,
lmpCcBeginVerifyReceived,
lmpCcBeginVerifySent,
lmpCcBeginVerifyReceived,
lmpCcBeginVerifyAckReceived,
lmpCcBeginVerifyAckSent,
lmpCcBeginVerifyNackReceived,
lmpCcBeginVerifyNackSent,
lmpCcEndVerifyReceived,
lmpCcEndVerifySent,
lmpCcEndVerifyReceived,
lmpCcEndVerifyAckReceived,
lmpCcEndVerifyAckSent,
lmpCcTestStatusSuccessReceived,
lmpCcTestStatusSuccessSent,
lmpCcTestStatusSuccessReceived,
lmpCcTestStatusFailureReceived,
lmpCcTestStatusFailureSent,
lmpCcTestStatusFailureReceived,
lmpCcLinkSummaryReceived, lmpCcLinkSummaryReceived,
lmpCcLinkSummarySent, lmpCcLinkSummarySent,
lmpCcLinkSummaryRetransmit, lmpCcLinkSummaryRetransmit,
lmpCcLinkSummaryAckReceived,
lmpCcLinkSummaryAckSent,
lmpCcLinkSummaryNackReceived,
lmpCcLinkSummaryNackSent,
lmpCcChannelStatusReceived, lmpCcChannelStatusReceived,
lmpCcChannelStatusSent, lmpCcChannelStatusSent,
lmpCcChannelStatusRetransmit,
lmpCcChannelStatusAckReceived,
lmpCcChannelStatusAckSent,
lmpCcChannelStatusRequestReceived, lmpCcChannelStatusRequestReceived,
lmpCcChannelStatusRequestSent, lmpCcChannelStatusRequestSent,
lmpCcChannelStatusRequestRetransmit,
lmpCcChannelStatusResponseReceived, lmpCcChannelStatusResponseReceived,
lmpCcChannelStatusResponseSent, lmpCcChannelStatusResponseSent,
lmpCcCounterDiscontinuityTime, lmpCcCounterDiscontinuityTime,
lmpDataBearingLinkTestReceived, lmpDataBearingLinkTestReceived,
lmpDataBearingLinkTestSent, lmpDataBearingLinkTestSent,
lmpDataBearingLinkActiveTestSuccess,
lmpDataBearingLinkActiveTestFailure,
lmpDataBearingLinkPassiveTestSuccess,
lmpDataBearingLinkPassiveTestFailure,
lmpDataBearingLinkCounterDiscontinuityTime lmpDataBearingLinkCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for providing performance "Collection of objects needed for providing performance
information about LMP interfaces and data-bearing links." information about LMP interfaces and data-bearing links."
::= { lmpGroups 7 } ::= { lmpGroups 7 }
lmpTeLinkGroup OBJECT-GROUP lmpTeLinkGroup OBJECT-GROUP
OBJECTS { lmpTeLinkNbrNodeId, OBJECTS { lmpTeLinkNbrNodeId,
lmpTeLinkVerification, lmpTeLinkVerification,
lmpTeLinkFaultIsolation, lmpTeLinkFaultManagement,
lmpTeLinkDwdm, lmpTeLinkDwdm,
lmpTeLinkOperStatus, lmpTeLinkOperStatus,
lmpTeLinkRowStatus, lmpTeLinkRowStatus,
lmpTeLinkStorageType, lmpTeLinkStorageType,
lmpTeLinkTrapEnable lmpTeLinkNotifEnable
} }
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 }
lmpDataBearingLinkGroup OBJECT-GROUP lmpDataBearingLinkGroup OBJECT-GROUP
OBJECTS { lmpDataBearingLinkType, OBJECTS { lmpDataBearingLinkType,
lmpDataBearingLinkNumberingType,
lmpDataBearingLinkRemoteIfId, lmpDataBearingLinkRemoteIfId,
lmpDataBearingLinkRemoteIpAddress,
lmpDataBearingLinkEncodingType, lmpDataBearingLinkEncodingType,
lmpDataBearingLinkOperStatus, lmpDataBearingLinkActiveOperStatus,
lmpDataBearingLinkPassiveOperStatus,
lmpDataBearingLinkRowStatus, lmpDataBearingLinkRowStatus,
lmpDataBearingLinkStorageType lmpDataBearingLinkStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for data-bearing link "Collection of objects needed for data-bearing link
configuration." configuration."
::= { lmpGroups 9 } ::= { lmpGroups 9 }
lmpNotificationGroup NOTIFICATION-GROUP lmpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { lmpTeLinkPropertyMismatch, NOTIFICATIONS { lmpTeLinkPropertyMismatch,
lmpDataBearingLinkPropertyMismatch, lmpDataBearingLinkPropertyMismatch,
lmpUnprotected, lmpUnprotected,
lmpControlChannelUp, lmpControlChannelUp,
lmpControlChannelDown, lmpControlChannelDown,
lmpTeLinkDegraded } lmpTeLinkDegraded,
lmpDataBearingLinkVerificationFailure }
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. Security Considerations 11. Security Considerations
It is clear that this MIB is potentially useful for monitoring of LMP It is clear that this MIB is potentially useful for monitoring of LMP
enabled devices. This MIB can also be used for configuration of cer- enabled devices. This MIB can also be used for configuration of cer-
tain objects, and anything that can be configured can be incorrectly tain objects, and anything that can be configured can be incorrectly
configured, with potentially disastrous results. configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond those At this writing, no security holes have been identified beyond those
that SNMP Security [SNMPArch] is itself intended to address. These that SNMP Security [RFC2571] is itself intended to address. These
relate to primarily controlled access to sensitive information and relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera- the ability to configure a device - or which might result from opera-
tor error, which is beyond the scope of any security architecture. tor error, which is beyond the scope of any security architecture.
There are a number of management objects defined in this MIB which There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ- environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network ment without proper protection can have a negative effect on network
operations. The use of SNMP Version 3 is recommended over prior ver- operations. The use of SNMP Version 3 is recommended over prior ver-
sions, for configuration control, as its security model is improved. sions, for configuration control, as its security model is improved.
SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if
the network itself is secure (for example by using IPSec [IPSEC]), the network itself is secure (for example by using IPSec [IPSEC]),
there is no control as to who on the secure network is allowed to 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 access and GET/SET (read/change/create/delete) the objects in this
MIB. It is recommended that the implementers consider the security MIB. It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [SNMPv3USM] and the View-based of the User-based Security Model [RFC2574] and the View-based Access
Access Control [SNMPv3VACM] is recommended. It is then a Control [RFC2575] is recommended. It is then a customer/user respon-
customer/user responsibility to ensure that the SNMP entity giving sibility to ensure that the SNMP entity giving access to an instance
access to an instance of this MIB is properly configured to give of this MIB is properly configured to give access to the objects only
access to the objects only to those principals (users) that have leg- to those principals (users) that have legitimate rights to indeed GET
itimate rights to indeed GET or SET (change/create/delete) them. or SET (change/create/delete) them.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in information that may be sensitive from a business perspective, in
that they represent a customer's interface to the G-MPLS network. that they can be used to derive the network topology, e.g. list of
Allowing uncontrolled access to these objects could result in mali- nodes and their IP address (lmpNbrTable) and list of data-bearing
cious and unwanted disruptions of network traffic or incorrect confi- links (lmpDataBearingLinkTable). Allowing uncontrolled access to
gurations for these customers. There are no objects that are particu- these objects could result in malicious and unwanted disruptions of
network traffic, incorrect network configurations or theft of com-
petitive business information. There are no objects that are particu-
larly sensitive in their own right, such as passwords or monetary larly sensitive in their own right, such as passwords or monetary
amounts. amounts.
12. Acknowledgments 12. Acknowledgments
The general structure of this draft has been modeled around draft- The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt. ietf-mpls-lsr-mib-06.txt.
The authors wish to thank Dmitry Ryumkin. The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and
George Wang.
13. References 13. References
[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., and Rajagopalan, B., Sandick, H., Zinin, A., and Rajagopalan, B.,
"Link Management Protocol", Internet Draft "Link Management Protocol", Internet Draft
<draft-ietf-ccamp-lmp-01.txt>, September 2001. <draft-ietf-ccamp-lmp-02.txt>, November 2001.
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K., Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z., Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Function Description", "Generalized MPLS Signaling Function Description",
Internet Draft Internet Draft
<draft-ietf-mpls-generalized-signaling-05.txt>, <draft-ietf-mpls-generalized-signaling-07.txt>,
July 2001. November 2001.
[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-kompella-mpls-bundle-05.txt>, Internet Draft <draft-ietf-mpls-bundle-01.txt>,
February 2001. November 2001.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., [BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base using "Link Bundling Management Information Base",
SMIv2", Internet Draft <draft-ietf-mpls-bundle-mib-01.txt>,
Internet Draft <draft-dubuc-mpls-bundle-mib-01.txt>, January 2002.
May 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also: RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi- http://www.isi.edu/in-notes/iana/assignments/smi-
numbers numbers
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in- FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers), notes/iana/assignements/address-family-numbers),
for MIB see: for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999. Frameworks", RFC 2571, April 1999.
[SMIv1] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", RFC 1155, May 1990. based Internets", STD 16, RFC 1155, May 1990.
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
Definitions", RFC 1212, March 1991. STD 16, RFC 1212, March 1991.
[SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use [RFC1215] M. Rose, "A Convention for Defining Traps for use with
with the SNMP", RFC 1215, March 1991. the SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
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.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, Network Management Protocol (SNMP)", RFC 2572, April
April 1999. 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April Management Protocol (SNMPv3)", RFC 2574, April 1999.
1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Waldbusser, "Protocol Operations for Version 2 of "Protocol Operations for Version 2 of the Simple
the Simple Network Management Protocol (SNMPv2)", Network Management Protocol (SNMPv2)", RFC 1905,
RFC 1905, January 1996. January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
based Access Control Model (VACM) for the Simple Access Control Model (VACM) for the Simple Network
Network Management Protocol (SNMP)", RFC 2575, Management Protocol (SNMP)", RFC 2575, April 1999.
April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April Network Management Framework", RFC 2570, April 1999.
1999.
[SMIv2] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Structure of Management Information
Version 2 (SMIv2)", RFC 2578, April 1999.
[SNMPv2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Textual Conventions for SMIv2",
RFC 2579, April 1999.
[SNMPv2Conf] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Conformance Statements for SMIv2",
RFC 2580, April 1999.
[SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", RFC 1157, May
1990.
[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based
SNMPv2", RFC 1901, January 1996.
[SNMPv2TM] 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.
[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2272,
January 1998.
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April
1999.
[SNMPv2PO] 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.
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2273, January 1998.
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)", RFC 2575,
April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture [IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November for the Internet Protocol", RFC 2401, November
1998. 1998.
[IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [BCP14] 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.
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
edgeflow, Inc. Calient Networks, Inc. Meriton Networks Calient Networks, Inc.
329 March Rd. 25 Castilian Drive 3026 Solandt Road 25 Castilian Drive
Kanata, ON, CANADA K2K 2E1 Goleta, CA 93117 Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117
Phone: +1-613-270-9279 x253 Email: jplang@calient.net Phone: +1-613-270-9279 x253 Email: jplang@calient.net
Email: martin.dubuc@edgeflow.com Email: martin.dubuc@meriton.com
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Nayna Networks, Inc. Calient Networks, Inc. Nayna Networks, Inc. Calient Networks, Inc.
157 Topaz Street 5853 Rue Ferrari 157 Topaz Street 5853 Rue Ferrari
Milipitas, CA 95035 San Jose, CA 95138 Milipitas, CA 95035 San Jose, CA 95138
Phone: +1-408-956-8000 x357 Email: evan@calient.net Phone: +1-408-956-8000 x357 Email: evan@calient.net
Email: sudheer@nayna.com Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
copyright notice or references to the Internet Society or other copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop- Internet organizations, except as needed for the purpose of develop-
 End of changes. 

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