MIBs Depot

LMP-MIB

Registered at
1.3.6.1.2.1.10.227
Last updated
2006-08-14 00:00
Organization
Common Control and Measurement Protocols (CCAMP) Working Group
Revisions
2006-08-14 00:00, 2006-01-11 00:00
Namespace
standard
Source file
LMP-MIB
Digest
sha256:cfbe3287e63c34ae96327657c3d1c98b91d838239264db74f04f241166f47f97

Description

Copyright (C) 2006 The Internet Society. This version of the MIB module is part of RFC 4631; see the RFC itself for full legal notices. This MIB module contains managed object definitions for the Link Management Protocol (LMP) as defined in 'Link Management Protocol'.

Contact

Martin Dubuc Email: dubuc.consulting@sympatico.ca Thomas D. Nadeau Email: tnadeau@cisco.com Jonathan P. Lang Email: jplang@ieee.org Evan McGinnis Email: emcginnis@hammerheadsystems.com Adrian Farrel Email: adrian@olddog.co.uk

Imports

FromSymbols
IF-MIBInterfaceIndexOrZero, ifIndex
INET-ADDRESS-MIBInetAddress, InetAddressType
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso, transmission
SNMPv2-TCDisplayString, RowStatus, StorageType, TEXTUAL-CONVENTION, TimeStamp, TruthValue
TE-LINK-STD-MIBTeLinkEncodingType, teLinkIncomingIfId, teLinkRemoteIpAddr

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

IANAifType-MIB
IF-MIB
INET-ADDRESS-MIB
LMP-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC
TE-LINK-STD-MIB

Textual conventions

NameOIDSyntaxAccessStatus
LmpInterval
TEXTUAL-CONVENTION
The interval delay, in milliseconds.
current
LmpNodeId
TEXTUAL-CONVENTION
Represents a Node ID in network byte order. Node ID is an address of type IPv4.
current
LmpRetransmitInterval
TEXTUAL-CONVENTION
The retransmission interval delay in milliseconds.
current

Objects

NameOIDSyntaxAccessStatus
lmpNotifications
OBJECT-IDENTITY
1.3.6.1.2.1.10.227.0
lmpObjects
OBJECT-IDENTITY
1.3.6.1.2.1.10.227.1
lmpAdminStatus
OBJECT-TYPE
The desired operational status of LMP on the node. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.1INTEGER {up(1), down(2)}read-writecurrent
lmpOperStatus
OBJECT-TYPE
The actual operational status of LMP on the node.
1.3.6.1.2.1.10.227.1.2INTEGER {up(1), down(2)}read-onlycurrent
lmpNbrTable
OBJECT-TYPE
This table specifies the neighbor node(s) to which control channels may be established.
1.3.6.1.2.1.10.227.1.3not-accessiblecurrent
lmpNbrEntry
OBJECT-TYPE
An entry in this table is created by a LMP-enabled device for every pair of nodes that can establish control channels.
1.3.6.1.2.1.10.227.1.3.1not-accessiblecurrent
lmpNbrNodeId
OBJECT-TYPE
This is a unique index for an entry in the LmpNbrTable. This value represents the remote Node ID.
1.3.6.1.2.1.10.227.1.3.1.1LmpNodeIdnot-accessiblecurrent
lmpNbrRetransmitInterval
OBJECT-TYPE
This object specifies the initial retransmission interval that is used for the retransmission of messages that require acknowledgement. This object, along with lmpNbrRetryLimit, is used to implement the congestion-handling mechanism defined in Section 10 of the Link Management Protocol specification, which is based on RFC 2914.
1.3.6.1.2.1.10.227.1.3.1.2LmpRetransmitIntervalread-createcurrent
lmpNbrRetryLimit
OBJECT-TYPE
This object specifies the maximum number of times a message is transmitted without being acknowledged. A value of 0 is used to indicate that a node should never stop retransmission. This object, along with lmpNbrRetransmitInterval, is used to implement the congestion-handling mechanism as defined in Section 10 of the Link Management Protocol specification, which is based on RFC 2914.
1.3.6.1.2.1.10.227.1.3.1.3Unsigned32read-createcurrent
lmpNbrRetransmitDelta
OBJECT-TYPE
This object governs the speed with which the sender increases the retransmission interval, as explained in Section 10 of the Link Management Protocol specification, which is based on RFC 2914. This value is a power used to express the exponential backoff. The ratio of two successive retransmission intervals is (1 + Delta).
1.3.6.1.2.1.10.227.1.3.1.4Unsigned32read-createcurrent
lmpNbrAdminStatus
OBJECT-TYPE
The desired operational status of LMP to this remote node.
1.3.6.1.2.1.10.227.1.3.1.5INTEGER {up(1), down(2)}read-createcurrent
lmpNbrOperStatus
OBJECT-TYPE
The actual operational status of LMP to this remote node.
1.3.6.1.2.1.10.227.1.3.1.6INTEGER {up(1), down(2)}read-onlycurrent
lmpNbrRowStatus
OBJECT-TYPE
This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
1.3.6.1.2.1.10.227.1.3.1.7RowStatusread-createcurrent
lmpNbrStorageType
OBJECT-TYPE
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.
1.3.6.1.2.1.10.227.1.3.1.8StorageTyperead-createcurrent
lmpCcHelloIntervalDefault
OBJECT-TYPE
This object specifies the default value for the HelloInterval parameter used in the Hello protocol keep-alive phase. It indicates how frequently LMP Hello messages will be sent. It is used as the default value for lmpCcHelloInterval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.4LmpIntervalread-writecurrent
lmpCcHelloIntervalDefaultMin
OBJECT-TYPE
This object specifies the default minimum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloIntervalMin. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.5LmpIntervalread-writecurrent
lmpCcHelloIntervalDefaultMax
OBJECT-TYPE
This object specifies the default maximum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloIntervalMax. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.6LmpIntervalread-writecurrent
lmpCcHelloDeadIntervalDefault
OBJECT-TYPE
This object specifies the default HelloDeadInterval parameter to use in the Hello protocol keep-alive phase. It indicates how long a device should wait before declaring the control channel dead. The HelloDeadInterval parameter should be at least three times the value of HelloInterval. It is used as a default value for lmpCcHelloDeadInterval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.7LmpIntervalread-writecurrent
lmpCcHelloDeadIntervalDefaultMin
OBJECT-TYPE
This object specifies the default minimum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHelloDeadIntervalMin. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.8LmpIntervalread-writecurrent
lmpCcHelloDeadIntervalDefaultMax
OBJECT-TYPE
This object specifies the default maximum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHelloDeadIntervalMax. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.9LmpIntervalread-writecurrent
lmpControlChannelTable
OBJECT-TYPE
This table specifies LMP control channel information.
1.3.6.1.2.1.10.227.1.10not-accessiblecurrent
lmpControlChannelEntry
OBJECT-TYPE
An entry in this table is created by an LMP-enabled device for every control channel. Whenever a new entry is created with lmpCcIsIf set to true(1), a corresponding entry is created in ifTable as well (see RFC 2863).
1.3.6.1.2.1.10.227.1.10.1not-accessiblecurrent
lmpCcId
OBJECT-TYPE
This value represents the local control channel identifier. The control channel identifier is a non-zero 32-bit number.
1.3.6.1.2.1.10.227.1.10.1.1Unsigned32 (1..4294967295)not-accessiblecurrent
lmpCcUnderlyingIfIndex
OBJECT-TYPE
If lmpCcIsIf is set to true(1), this object carries the index into the ifTable of the entry that represents the LMP interface over which LMP will transmit its traffic. If this object is set to zero but lmpCcIsIf is set to true(1), the control channel is not currently associated with any underlying interface, and the control channel's operational status must not be up(1); nor should the control channel forward or receive traffic. If lmpCcIsIf is set to false(2), this object should be set to zero and ignored.
1.3.6.1.2.1.10.227.1.10.1.2InterfaceIndexOrZeroread-createcurrent
lmpCcIsIf
OBJECT-TYPE
In implementations where the control channels are modeled as interfaces, the value of this object is true(1), and this control channel is represented by an interface in the interfaces group table as indicated by the value of lmpCcUnderlyingIfIndex. If control channels are not modeled as interfaces, the value of this object is false(2), and there is no corresponding interface for this control channel in the interfaces group table; the value of lmpCcUnderlyingIfIndex should be ignored.
1.3.6.1.2.1.10.227.1.10.1.3TruthValueread-createcurrent
lmpCcNbrNodeId
OBJECT-TYPE
This is the Node ID of the control channel remote node. This value either is configured or gets created by the node when a Config message is received or when an outgoing Config message is acknowledged by the remote node.
1.3.6.1.2.1.10.227.1.10.1.4LmpNodeIdread-createcurrent
lmpCcRemoteId
OBJECT-TYPE
This value represents the remote control channel identifier (32-bit number). It is determined during the negotiation phase. A value of zero means that the remote control channel identifier has not yet been learned.
1.3.6.1.2.1.10.227.1.10.1.5Unsigned32read-onlycurrent
lmpCcRemoteAddressType
OBJECT-TYPE
This value represents the remote control channel IP address type. In point-to-point configuration, this value can be set to unknown(0).
1.3.6.1.2.1.10.227.1.10.1.6InetAddressTyperead-createcurrent
lmpCcRemoteIpAddr
OBJECT-TYPE
This value represents the remote control channel Internet address for numbered control channel. The type of this address is determined by lmpCcRemoteAddressType. The control channel must be numbered on non-point-to-point configuration. For point-to-point configuration, the remote control channel address can be of type unknown, in which case this object must be a zero-length string. The lmpCcRemoteId object then identifies the unnumbered address.
1.3.6.1.2.1.10.227.1.10.1.7InetAddressread-createcurrent
lmpCcSetupRole
OBJECT-TYPE
The role that this node should take during establishment of this control channel. An active node will initiate establishment. A passive node will wait for the remote node to initiate. A pair of nodes that both take the passive role will never establish communications.
1.3.6.1.2.1.10.227.1.10.1.8INTEGER {active(1), passive(2)}read-createcurrent
lmpCcAuthentication
OBJECT-TYPE
This object indicates whether the control channel must use authentication.
1.3.6.1.2.1.10.227.1.10.1.9TruthValueread-createcurrent
lmpCcHelloInterval
OBJECT-TYPE
This object specifies the value of the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalDefault.
1.3.6.1.2.1.10.227.1.10.1.10LmpIntervalread-createcurrent
lmpCcHelloIntervalMin
OBJECT-TYPE
This object specifies the minimum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMinDefault.
1.3.6.1.2.1.10.227.1.10.1.11LmpIntervalread-createcurrent
lmpCcHelloIntervalMax
OBJECT-TYPE
This object specifies the maximum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.
1.3.6.1.2.1.10.227.1.10.1.12LmpIntervalread-createcurrent
lmpCcHelloIntervalNegotiated
OBJECT-TYPE
Once the control channel is active, this object represents the negotiated HelloInterval value.
1.3.6.1.2.1.10.227.1.10.1.13LmpIntervalread-onlycurrent
lmpCcHelloDeadInterval
OBJECT-TYPE
This object specifies the value of the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalDefault.
1.3.6.1.2.1.10.227.1.10.1.14LmpIntervalread-createcurrent
lmpCcHelloDeadIntervalMin
OBJECT-TYPE
This object specifies the minimum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalMinDefault.
1.3.6.1.2.1.10.227.1.10.1.15LmpIntervalread-createcurrent
lmpCcHelloDeadIntervalMax
OBJECT-TYPE
This object specifies the maximum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.
1.3.6.1.2.1.10.227.1.10.1.16LmpIntervalread-createcurrent
lmpCcHelloDeadIntervalNegotiated
OBJECT-TYPE
Once the control channel is active, this object represents the negotiated HelloDeadInterval value.
1.3.6.1.2.1.10.227.1.10.1.17LmpIntervalread-onlycurrent
lmpCcLastChange
OBJECT-TYPE
The value of sysUpTime at the time the control channel entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
1.3.6.1.2.1.10.227.1.10.1.18TimeTicksread-onlycurrent
lmpCcAdminStatus
OBJECT-TYPE
The desired operational status of this control channel.
1.3.6.1.2.1.10.227.1.10.1.19INTEGER {up(1), down(2)}read-createcurrent
lmpCcOperStatus
OBJECT-TYPE
The actual operational status of this control channel.
1.3.6.1.2.1.10.227.1.10.1.20INTEGER {up(1), down(2), configSnd(3), configRcv(4), active(5), goingDown(6)}read-onlycurrent
lmpCcRowStatus
OBJECT-TYPE
This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
1.3.6.1.2.1.10.227.1.10.1.21RowStatusread-createcurrent
lmpCcStorageType
OBJECT-TYPE
The storage type for this conceptual row in the lmpControlChannelTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
1.3.6.1.2.1.10.227.1.10.1.22StorageTyperead-createcurrent
lmpControlChannelPerfTable
OBJECT-TYPE
This table specifies LMP control channel performance counters.
1.3.6.1.2.1.10.227.1.11not-accessiblecurrent
lmpControlChannelPerfEntry
OBJECT-TYPE
An entry in this table is created by a LMP-enabled device for every control channel. lmpCcCounterDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
1.3.6.1.2.1.10.227.1.11.1not-accessiblecurrent
lmpCcInOctets
OBJECT-TYPE
The total number of LMP message octets received on the control channel.
1.3.6.1.2.1.10.227.1.11.1.1Counter32read-onlycurrent
lmpCcInDiscards
OBJECT-TYPE
The number of inbound packets that were chosen to be discarded even though no errors had been detected. One possible reason for discarding such a packet could be to free up buffer space.
1.3.6.1.2.1.10.227.1.11.1.2Counter32read-onlycurrent
lmpCcInErrors
OBJECT-TYPE
The number of inbound packets that contained errors preventing them from being processed by LMP.
1.3.6.1.2.1.10.227.1.11.1.3Counter32read-onlycurrent
lmpCcOutOctets
OBJECT-TYPE
The total number of LMP message octets transmitted out of the control channel.
1.3.6.1.2.1.10.227.1.11.1.4Counter32read-onlycurrent
lmpCcOutDiscards
OBJECT-TYPE
The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.
1.3.6.1.2.1.10.227.1.11.1.5Counter32read-onlycurrent
lmpCcOutErrors
OBJECT-TYPE
The number of outbound packets that could not be transmitted because of errors.
1.3.6.1.2.1.10.227.1.11.1.6Counter32read-onlycurrent
lmpCcConfigReceived
OBJECT-TYPE
This object counts the number of Config messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.7Counter32read-onlycurrent
lmpCcConfigSent
OBJECT-TYPE
This object counts the number of Config messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.8Counter32read-onlycurrent
lmpCcConfigRetransmit
OBJECT-TYPE
This object counts the number of Config messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.9Counter32read-onlycurrent
lmpCcConfigAckReceived
OBJECT-TYPE
This object counts the number of ConfigAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.10Counter32read-onlycurrent
lmpCcConfigAckSent
OBJECT-TYPE
This object counts the number of ConfigAck messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.11Counter32read-onlycurrent
lmpCcConfigNackReceived
OBJECT-TYPE
This object counts the number of ConfigNack messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.12Counter32read-onlycurrent
lmpCcConfigNackSent
OBJECT-TYPE
This object counts the number of ConfigNack messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.13Counter32read-onlycurrent
lmpCcHelloReceived
OBJECT-TYPE
This object counts the number of Hello messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.14Counter32read-onlycurrent
lmpCcHelloSent
OBJECT-TYPE
This object counts the number of Hello messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.15Counter32read-onlycurrent
lmpCcBeginVerifyReceived
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.16Counter32read-onlycurrent
lmpCcBeginVerifySent
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.17Counter32read-onlycurrent
lmpCcBeginVerifyRetransmit
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.18Counter32read-onlycurrent
lmpCcBeginVerifyAckReceived
OBJECT-TYPE
This object counts the number of BeginVerifyAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.19Counter32read-onlycurrent
lmpCcBeginVerifyAckSent
OBJECT-TYPE
This object counts the number of BeginVerifyAck messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.20Counter32read-onlycurrent
lmpCcBeginVerifyNackReceived
OBJECT-TYPE
This object counts the number of BeginVerifyNack messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.21Counter32read-onlycurrent
lmpCcBeginVerifyNackSent
OBJECT-TYPE
This object counts the number of BeginVerifyNack messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.22Counter32read-onlycurrent
lmpCcEndVerifyReceived
OBJECT-TYPE
This object counts the number of EndVerify messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.23Counter32read-onlycurrent
lmpCcEndVerifySent
OBJECT-TYPE
This object counts the number of EndVerify messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.24Counter32read-onlycurrent
lmpCcEndVerifyRetransmit
OBJECT-TYPE
This object counts the number of EndVerify messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.25Counter32read-onlycurrent
lmpCcEndVerifyAckReceived
OBJECT-TYPE
This object counts the number of EndVerifyAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.26Counter32read-onlycurrent
lmpCcEndVerifyAckSent
OBJECT-TYPE
This object counts the number of EndVerifyAck messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.27Counter32read-onlycurrent
lmpCcTestStatusSuccessReceived
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.28Counter32read-onlycurrent
lmpCcTestStatusSuccessSent
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.29Counter32read-onlycurrent
lmpCcTestStatusSuccessRetransmit
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.30Counter32read-onlycurrent
lmpCcTestStatusFailureReceived
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.31Counter32read-onlycurrent
lmpCcTestStatusFailureSent
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.32Counter32read-onlycurrent
lmpCcTestStatusFailureRetransmit
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.33Counter32read-onlycurrent
lmpCcTestStatusAckReceived
OBJECT-TYPE
This object counts the number of TestStatusAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.34Counter32read-onlycurrent
lmpCcTestStatusAckSent
OBJECT-TYPE
This object counts the number of TestStatusAck messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.35Counter32read-onlycurrent
lmpCcLinkSummaryReceived
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.36Counter32read-onlycurrent
lmpCcLinkSummarySent
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.37Counter32read-onlycurrent
lmpCcLinkSummaryRetransmit
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.11.1.38Counter32read-onlycurrent
lmpCcLinkSummaryAckReceived
OBJECT-TYPE
This object counts the number of LinkSummaryAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.39Counter32read-onlycurrent
lmpCcLinkSummaryAckSent
OBJECT-TYPE
This object counts the number of LinkSummaryAck messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.40Counter32read-onlycurrent
lmpCcLinkSummaryNackReceived
OBJECT-TYPE
This object counts the number of LinkSummaryNack messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.41Counter32read-onlycurrent
lmpCcLinkSummaryNackSent
OBJECT-TYPE
This object counts the number of LinkSummaryNack messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.42Counter32read-onlycurrent
lmpCcChannelStatusReceived
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.43Counter32read-onlycurrent
lmpCcChannelStatusSent
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.44Counter32read-onlycurrent
lmpCcChannelStatusRetransmit
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been retransmitted on this control channel.
1.3.6.1.2.1.10.227.1.11.1.45Counter32read-onlycurrent
lmpCcChannelStatusAckReceived
OBJECT-TYPE
This object counts the number of ChannelStatusAck messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.46Counter32read-onlycurrent
lmpCcChannelStatusAckSent
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.47Counter32read-onlycurrent
lmpCcChannelStatusReqReceived
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.48Counter32read-onlycurrent
lmpCcChannelStatusReqSent
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.49Counter32read-onlycurrent
lmpCcChannelStatusReqRetransmit
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been retransmitted on this control channel.
1.3.6.1.2.1.10.227.1.11.1.50Counter32read-onlycurrent
lmpCcChannelStatusRspReceived
OBJECT-TYPE
This object counts the number of ChannelStatusResponse messages that have been received on this control channel.
1.3.6.1.2.1.10.227.1.11.1.51Counter32read-onlycurrent
lmpCcChannelStatusRspSent
OBJECT-TYPE
This object counts the number of ChannelStatusResponse messages that have been sent on this control channel.
1.3.6.1.2.1.10.227.1.11.1.52Counter32read-onlycurrent
lmpCcCounterDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which one or more of this control channel's counters suffered a discontinuity. The relevant counters are the specific instances associated with this control channel of any Counter32 object contained in the lmpControlChannelPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
1.3.6.1.2.1.10.227.1.11.1.53TimeStampread-onlycurrent
lmpTeLinkTable
OBJECT-TYPE
This table specifies the LMP-specific TE link information. Overall TE link information is kept in three separate tables: ifTable for interface-specific information, lmpTeLinkTable for LMP specific information, and teLinkTable for generic TE link information. ifIndex is the common index to all tables.
1.3.6.1.2.1.10.227.1.12not-accessiblecurrent
lmpTeLinkEntry
OBJECT-TYPE
An entry in this table exists for each ifEntry with an ifType of teLink(200) that is managed by LMP. An ifEntry with an ifIndex must exist before the corresponding lmpTeLinkEntry is created. If a TE link entry in the ifTable is destroyed, then so is the corresponding entry in the lmpTeLinkTable. The administrative status value is controlled from the ifEntry. Setting the administrative status to testing prompts LMP to start link verification on the TE link. Information about the TE link that is not LMP specific is contained in the teLinkTable of the TE-LINK-STD-MIB MIB module.
1.3.6.1.2.1.10.227.1.12.1not-accessiblecurrent
lmpTeLinkNbrRemoteNodeId
OBJECT-TYPE
This is the Node ID of the TE link remote node. This value may be learned during the control channel parameter negotiation phase (in the Config message). Node ID is an address whose type must be IPv4.
1.3.6.1.2.1.10.227.1.12.1.1LmpNodeIdread-createcurrent
lmpTeLinkVerification
OBJECT-TYPE
This object indicates whether the LMP link verification procedure is enabled for this TE link.
1.3.6.1.2.1.10.227.1.12.1.2TruthValueread-createcurrent
lmpTeLinkFaultManagement
OBJECT-TYPE
This object indicates whether the LMP fault management procedure is enabled on this TE link.
1.3.6.1.2.1.10.227.1.12.1.3TruthValueread-createcurrent
lmpTeLinkDwdm
OBJECT-TYPE
This object indicates whether the LMP DWDM procedure is enabled on this TE link.
1.3.6.1.2.1.10.227.1.12.1.4TruthValueread-createcurrent
lmpTeLinkOperStatus
OBJECT-TYPE
The actual operational status of this TE link. The status is set to testing when the TE link is performing link verification. A degraded state indicates that there is no active control channel between the pair of nodes that form the endpoints of the TE link, but that at least one data-bearing link on the TE link is allocated.
1.3.6.1.2.1.10.227.1.12.1.5INTEGER {up(1), down(2), testing(3), init(4), degraded(5)}read-onlycurrent
lmpTeLinkRowStatus
OBJECT-TYPE
This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
1.3.6.1.2.1.10.227.1.12.1.6RowStatusread-createcurrent
lmpTeLinkStorageType
OBJECT-TYPE
The storage type for this conceptual row in the lmpTeLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
1.3.6.1.2.1.10.227.1.12.1.7StorageTyperead-createcurrent
lmpGlobalLinkVerificationInterval
OBJECT-TYPE
This object indicates how often the link verification procedure is executed. The interval is in milliseconds. A value of 0 is used to indicate that the link verification procedure should not be executed. The interval specified in this object should be large enough to allow the verification procedure to be completed before the start of the next interval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.13Unsigned32read-writecurrent
lmpLinkVerificationTable
OBJECT-TYPE
This table specifies TE link information associated with the LMP verification procedure.
1.3.6.1.2.1.10.227.1.14not-accessiblecurrent
lmpLinkVerificationEntry
OBJECT-TYPE
An entry in this table is created by an LMP-enabled device for every TE link that supports the LMP verification procedure.
1.3.6.1.2.1.10.227.1.14.1not-accessiblecurrent
lmpLinkVerifyInterval
OBJECT-TYPE
This object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent.
1.3.6.1.2.1.10.227.1.14.1.1LmpIntervalread-createcurrent
lmpLinkVerifyDeadInterval
OBJECT-TYPE
This object specifies the VerifyDeadInterval parameter used in the verification of the physical connectivity of data- bearing links. It specifies the observation period used to detect a Test message at the remote node.
1.3.6.1.2.1.10.227.1.14.1.2LmpIntervalread-createcurrent
lmpLinkVerifyTransportMechanism
OBJECT-TYPE
This defines the transport mechanism for the Test messages. The scope of this bit mask is restricted to each link encoding type. The local node will set the bits corresponding to the various mechanisms it can support for transmitting LMP Test messages. The receiver chooses the appropriate mechanism in the BeginVerifyAck message.
1.3.6.1.2.1.10.227.1.14.1.3Bits {payload(0), dccSectionOverheadBytes(1), dccLineOverheadBytes(2), j0Trace(3), j1Trace(4), j2Trace(5)}read-createcurrent
lmpLinkVerifyTransmissionRate
OBJECT-TYPE
This is the transmission rate of the data link over which the Test messages will be transmitted and is expressed in bytes per second.
1.3.6.1.2.1.10.227.1.14.1.5Unsigned32read-createcurrent
lmpLinkVerifyWavelength
OBJECT-TYPE
This value corresponds to the wavelength at which the Test messages will be transmitted and is measured in nanometers (nm). If each data-bearing link corresponds to a separate wavelength, then this value should be set to 0.
1.3.6.1.2.1.10.227.1.14.1.6Unsigned32read-createcurrent
lmpLinkVerifyRowStatus
OBJECT-TYPE
This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
1.3.6.1.2.1.10.227.1.14.1.7RowStatusread-createcurrent
lmpLinkVerifyStorageType
OBJECT-TYPE
The storage type for this conceptual row in the lmpLinkVerificationTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
1.3.6.1.2.1.10.227.1.14.1.8StorageTyperead-createcurrent
lmpTeLinkPerfTable
OBJECT-TYPE
This table specifies LMP TE link performance counters.
1.3.6.1.2.1.10.227.1.15not-accessiblecurrent
lmpTeLinkPerfEntry
OBJECT-TYPE
An entry in this table is created by an LMP-enabled device for every TE link. lmpTeCounterDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
1.3.6.1.2.1.10.227.1.15.1not-accessiblecurrent
lmpTeInOctets
OBJECT-TYPE
The total number of LMP message octets received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.1Counter32read-onlycurrent
lmpTeOutOctets
OBJECT-TYPE
The total number of LMP message octets transmitted out for this TE link.
1.3.6.1.2.1.10.227.1.15.1.2Counter32read-onlycurrent
lmpTeBeginVerifyReceived
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.3Counter32read-onlycurrent
lmpTeBeginVerifySent
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.4Counter32read-onlycurrent
lmpTeBeginVerifyRetransmit
OBJECT-TYPE
This object counts the number of BeginVerify messages that have been retransmitted for this TE link.
1.3.6.1.2.1.10.227.1.15.1.5Counter32read-onlycurrent
lmpTeBeginVerifyAckReceived
OBJECT-TYPE
This object counts the number of BeginVerifyAck messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.6Counter32read-onlycurrent
lmpTeBeginVerifyAckSent
OBJECT-TYPE
This object counts the number of BeginVerifyAck messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.7Counter32read-onlycurrent
lmpTeBeginVerifyNackReceived
OBJECT-TYPE
This object counts the number of BeginVerifyNack messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.8Counter32read-onlycurrent
lmpTeBeginVerifyNackSent
OBJECT-TYPE
This object counts the number of BeginVerifyNack messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.9Counter32read-onlycurrent
lmpTeEndVerifyReceived
OBJECT-TYPE
This object counts the number of EndVerify messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.10Counter32read-onlycurrent
lmpTeEndVerifySent
OBJECT-TYPE
This object counts the number of EndVerify messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.11Counter32read-onlycurrent
lmpTeEndVerifyRetransmit
OBJECT-TYPE
This object counts the number of EndVerify messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.15.1.12Counter32read-onlycurrent
lmpTeEndVerifyAckReceived
OBJECT-TYPE
This object counts the number of EndVerifyAck messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.13Counter32read-onlycurrent
lmpTeEndVerifyAckSent
OBJECT-TYPE
This object counts the number of EndVerifyAck messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.14Counter32read-onlycurrent
lmpTeTestStatusSuccessReceived
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.15Counter32read-onlycurrent
lmpTeTestStatusSuccessSent
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.16Counter32read-onlycurrent
lmpTeTestStatusSuccessRetransmit
OBJECT-TYPE
This object counts the number of TestStatusSuccess messages that have been retransmitted for this TE link.
1.3.6.1.2.1.10.227.1.15.1.17Counter32read-onlycurrent
lmpTeTestStatusFailureReceived
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.18Counter32read-onlycurrent
lmpTeTestStatusFailureSent
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.19Counter32read-onlycurrent
lmpTeTestStatusFailureRetransmit
OBJECT-TYPE
This object counts the number of TestStatusFailure messages that have been retransmitted on this TE link.
1.3.6.1.2.1.10.227.1.15.1.20Counter32read-onlycurrent
lmpTeTestStatusAckReceived
OBJECT-TYPE
This object counts the number of TestStatusAck messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.21Counter32read-onlycurrent
lmpTeTestStatusAckSent
OBJECT-TYPE
This object counts the number of TestStatusAck messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.22Counter32read-onlycurrent
lmpTeLinkSummaryReceived
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.23Counter32read-onlycurrent
lmpTeLinkSummarySent
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.24Counter32read-onlycurrent
lmpTeLinkSummaryRetransmit
OBJECT-TYPE
This object counts the number of LinkSummary messages that have been retransmitted over this control channel.
1.3.6.1.2.1.10.227.1.15.1.25Counter32read-onlycurrent
lmpTeLinkSummaryAckReceived
OBJECT-TYPE
This object counts the number of LinkSummaryAck messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.26Counter32read-onlycurrent
lmpTeLinkSummaryAckSent
OBJECT-TYPE
This object counts the number of LinkSummaryAck messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.27Counter32read-onlycurrent
lmpTeLinkSummaryNackReceived
OBJECT-TYPE
This object counts the number of LinkSummaryNack messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.28Counter32read-onlycurrent
lmpTeLinkSummaryNackSent
OBJECT-TYPE
This object counts the number of LinkSummaryNack messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.29Counter32read-onlycurrent
lmpTeChannelStatusReceived
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.30Counter32read-onlycurrent
lmpTeChannelStatusSent
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.31Counter32read-onlycurrent
lmpTeChannelStatusRetransmit
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been retransmitted for this TE link.
1.3.6.1.2.1.10.227.1.15.1.32Counter32read-onlycurrent
lmpTeChannelStatusAckReceived
OBJECT-TYPE
This object counts the number of ChannelStatusAck messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.33Counter32read-onlycurrent
lmpTeChannelStatusAckSent
OBJECT-TYPE
This object counts the number of ChannelStatus messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.34Counter32read-onlycurrent
lmpTeChannelStatusReqReceived
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.35Counter32read-onlycurrent
lmpTeChannelStatusReqSent
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.36Counter32read-onlycurrent
lmpTeChannelStatusReqRetransmit
OBJECT-TYPE
This object counts the number of ChannelStatusRequest messages that have been retransmitted for this TE link.
1.3.6.1.2.1.10.227.1.15.1.37Counter32read-onlycurrent
lmpTeChannelStatusRspReceived
OBJECT-TYPE
This object counts the number of ChannelStatusResponse messages that have been received for this TE link.
1.3.6.1.2.1.10.227.1.15.1.38Counter32read-onlycurrent
lmpTeChannelStatusRspSent
OBJECT-TYPE
This object counts the number of ChannelStatusResponse messages that have been sent for this TE link.
1.3.6.1.2.1.10.227.1.15.1.39Counter32read-onlycurrent
lmpTeCounterDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which one or more of this TE link's counters suffered a discontinuity. The relevant counters are the specific instances associated with this TE link of any Counter32 object contained in the lmpTeLinkPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
1.3.6.1.2.1.10.227.1.15.1.40TimeStampread-onlycurrent
lmpDataLinkTable
OBJECT-TYPE
This table specifies the data-bearing links managed by the LMP.
1.3.6.1.2.1.10.227.1.16not-accessiblecurrent
lmpDataLinkEntry
OBJECT-TYPE
An entry in this table exists for each ifEntry that represents a data-bearing link. An ifEntry with an ifIndex must exist before the corresponding lmpDataLinkEntry is created. If an entry representing the data-bearing link is destroyed in the ifTable, then so is the corresponding entry in the lmpDataLinkTable. The administrative status value is controlled from the ifEntry. The index to this table is also used to get information in the componentLinkTable of the TE-LINK-STD-MIB MIB module.
1.3.6.1.2.1.10.227.1.16.1not-accessiblecurrent
lmpDataLinkType
OBJECT-TYPE
This attribute specifies whether this data-bearing link is a port or a component link. Component links are multiplex capable, whereas ports are not multiplex capable.
1.3.6.1.2.1.10.227.1.16.1.1INTEGER {port(1), componentLink(2)}read-onlycurrent
lmpDataLinkAddressType
OBJECT-TYPE
This attribute specifies the data-bearing link IP address type. If the data-bearing link is unnumbered, the address type must be set to unknown(0).
1.3.6.1.2.1.10.227.1.16.1.2InetAddressTyperead-createcurrent
lmpDataLinkIpAddr
OBJECT-TYPE
The local Internet address for numbered links. The type of this address is determined by the value of lmpDataLinkAddressType object. For IPv4 and IPv6 numbered links, this object represents the local IP address associated with the data-bearing link. For an unnumbered link, the local address is of type unknown, and this object is set to the zero-length string; the ifIndex object then identifies the unnumbered address.
1.3.6.1.2.1.10.227.1.16.1.3InetAddressread-createcurrent
lmpDataLinkRemoteIpAddress
OBJECT-TYPE
The remote Internet address for numbered data-bearing links. The type of this address is determined by the lmpDataLinkAddressType object. For IPv4 and IPv6 numbered links, this object represents the remote IP address associated with the data-bearing link. For an unnumbered link, the remote address is of type unknown, and this object is set to the zero-length string; the lmpDataLinkRemoteIfId object then identifies the unnumbered address. This information is either configured manually or communicated by the remote node during the link verification procedure.
1.3.6.1.2.1.10.227.1.16.1.4InetAddressread-createcurrent
lmpDataLinkRemoteIfId
OBJECT-TYPE
Interface identifier of the remote end point. This information is either configured manually or communicated by the remote node during the link verification procedure.
1.3.6.1.2.1.10.227.1.16.1.5InterfaceIndexOrZeroread-createcurrent
lmpDataLinkEncodingType
OBJECT-TYPE
The encoding type of the data-bearing link.
1.3.6.1.2.1.10.227.1.16.1.6TeLinkEncodingTyperead-createcurrent
lmpDataLinkActiveOperStatus
OBJECT-TYPE
The actual operational status of this data-bearing link (active FSM).
1.3.6.1.2.1.10.227.1.16.1.7INTEGER {upAlloc(1), upFree(2), down(3), testing(4)}read-onlycurrent
lmpDataLinkPassiveOperStatus
OBJECT-TYPE
The actual operational status of this data-bearing link (passive FSM).
1.3.6.1.2.1.10.227.1.16.1.8INTEGER {upAlloc(1), upFree(2), down(3), psvTst(4)}read-onlycurrent
lmpDataLinkRowStatus
OBJECT-TYPE
This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
1.3.6.1.2.1.10.227.1.16.1.9RowStatusread-createcurrent
lmpDataLinkStorageType
OBJECT-TYPE
The storage type for this conceptual row in the lmpDataLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
1.3.6.1.2.1.10.227.1.16.1.10StorageTyperead-createcurrent
lmpDataLinkPerfTable
OBJECT-TYPE
This table specifies the data-bearing links LMP performance counters.
1.3.6.1.2.1.10.227.1.17not-accessiblecurrent
lmpDataLinkPerfEntry
OBJECT-TYPE
An entry in this table contains information about the LMP performance counters for the data-bearing links. lmpDataLinkDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
1.3.6.1.2.1.10.227.1.17.1not-accessiblecurrent
lmpDataLinkTestReceived
OBJECT-TYPE
This object counts the number of Test messages that have been received on this data-bearing link.
1.3.6.1.2.1.10.227.1.17.1.1Counter32read-onlycurrent
lmpDataLinkTestSent
OBJECT-TYPE
This object counts the number of Test messages that have been sent on this data-bearing link.
1.3.6.1.2.1.10.227.1.17.1.2Counter32read-onlycurrent
lmpDataLinkActiveTestSuccess
OBJECT-TYPE
This object counts the number of data-bearing link tests that were successful on the active side of this data- bearing link.
1.3.6.1.2.1.10.227.1.17.1.3Counter32read-onlycurrent
lmpDataLinkActiveTestFailure
OBJECT-TYPE
This object counts the number of data-bearing link tests that failed on the active side of this data-bearing link.
1.3.6.1.2.1.10.227.1.17.1.4Counter32read-onlycurrent
lmpDataLinkPassiveTestSuccess
OBJECT-TYPE
This object counts the number of data-bearing link tests that were successful on the passive side of this data- bearing link.
1.3.6.1.2.1.10.227.1.17.1.5Counter32read-onlycurrent
lmpDataLinkPassiveTestFailure
OBJECT-TYPE
This object counts the number of data-bearing link tests that failed on the passive side of this data-bearing link.
1.3.6.1.2.1.10.227.1.17.1.6Counter32read-onlycurrent
lmpDataLinkDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which one or more of this data-bearing link's counters suffered a discontinuity. The relevant counters are the specific instances associated with this data-bearing link of any Counter32 object contained in the lmpDataLinkPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
1.3.6.1.2.1.10.227.1.17.1.7TimeStampread-onlycurrent
lmpNotificationMaxRate
OBJECT-TYPE
The LMP notification rate depends on the size of the network, the type of links, the network configuration, the reliability of the network, etc. When this MIB was designed, care was taken to minimize the amount of notifications generated for LMP purposes. Wherever possible, notifications are state driven, meaning that the notifications are sent only when the system changes state. The only notifications that are repeated and that could cause a problem as far as congestion is concerned are the ones associated with data link verification. Without any considerations to handling of these notifications, a problem may arise if the number of data links is high. Since the data link verification notifications can happen only once per data link per link verification interval, the notification rate should be sustainable if one chooses an appropriate link verification interval for a given network configuration. For instance, a network of 100 nodes with 5 links of 128 wavelengths each and a link verification of 1 minute, where no more than 10% of the links failed at any given time, would have 1 notification per second sent from each node, or 100 notifications per second for the whole network. The rest of the notifications are negligible compared to this number. To alleviate the congestion problem, the lmpNotificationMaxRate object can be used to implement a throttling mechanism. It is also possible to enable/disable certain type of notifications. This variable indicates the maximum number of notifications issued per minute. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period or may queue them until an appropriate time. A value of 0 means that no throttling is applied and events may be notified at the rate at which they occur. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.18Unsigned32read-writecurrent
lmpLinkPropertyNotificationsEnabled
OBJECT-TYPE
If this object is true(1), then it enables the generation of lmpTeLinkPropertyMismatch and lmpDataLinkPropertyMismatch notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.19TruthValueread-writecurrent
lmpUnprotectedNotificationsEnabled
OBJECT-TYPE
If this object is true(1), then it enables the generation of lmpUnprotected notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.20TruthValueread-writecurrent
lmpCcUpDownNotificationsEnabled
OBJECT-TYPE
If this object is true(1), then it enables the generation of lmpControlChannelUp and lmpControlChannelDown notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.21TruthValueread-writecurrent
lmpTeLinkNotificationsEnabled
OBJECT-TYPE
If this object is true(1), then it enables the generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.22TruthValueread-writecurrent
lmpDataLinkNotificationsEnabled
OBJECT-TYPE
If this object is true(1), then it enables the generation of lmpDataLinkVerificationFailure notification; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
1.3.6.1.2.1.10.227.1.23TruthValueread-writecurrent
lmpConformance
OBJECT-IDENTITY
1.3.6.1.2.1.10.227.2
lmpCompliances
OBJECT-IDENTITY
1.3.6.1.2.1.10.227.2.1
lmpGroups
OBJECT-IDENTITY
1.3.6.1.2.1.10.227.2.2

Notifications

NameOIDStatus
lmpTeLinkPropertyMismatch
NOTIFICATION-TYPE
This notification is generated when a TE link property mismatch is detected on the node. The received remote TE link ID of the misconfigured TE link is represented by either teLinkRemoteIpAddr or teLinkIncomingIfId, depending on whether the TE link is numbered or unnumbered. This notification should not be sent unless lmpLinkPropertyNotificationsEnabled is true(1). It is recommended that this notification be reported only the first time a mismatch is detected. Otherwise, for a given TE link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
1.3.6.1.2.1.10.227.0.1current
lmpDataLinkPropertyMismatch
NOTIFICATION-TYPE
This notification is generated when a data-bearing link property mismatch is detected on the node. lmpDataLinkType is used to identify the local identifiers associated with the data link. (The data link interface index can be used to determine the TE link interface index, as this relationship is captured in the interface stack table.) The remote entity interface ID is the remote entity interface ID received in the LinkSummary message. This notification should not be sent unless lmpLinkPropertyNotificationsEnabled is true(1). It is recommended that this notification be reported only the first time a mismatch is detected. Otherwise, for a given data link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
1.3.6.1.2.1.10.227.0.2current
lmpUnprotected
NOTIFICATION-TYPE
This notification is generated when there is more than one control channel between LMP neighbors and the last redundant control channel has failed. If the remaining operational control channel fails, then there will be no more control channels between the pair of nodes and all the TE links between the pair of nodes, will go to degraded state. This notification should not be sent unless lmpUnprotectedNotificationsEnabled is set to true(1).
1.3.6.1.2.1.10.227.0.3current
lmpControlChannelUp
NOTIFICATION-TYPE
This notification is generated when a control channel transitions to the up operational state. This notification should not be sent unless lmpCcUpDownNotificationsEnabled is true(1).
1.3.6.1.2.1.10.227.0.4current
lmpControlChannelDown
NOTIFICATION-TYPE
This notification is generated when a control channel transitions out of the up operational state. This notification should not be sent unless lmpCcUpDownNotificationsEnabled is true(1).
1.3.6.1.2.1.10.227.0.5current
lmpTeLinkDegraded
NOTIFICATION-TYPE
This notification is generated when a lmpTeLinkOperStatus object for a TE link enters the degraded state. This notification should not be sent unless lmpTeLinkNotificationsEnabled is true(1).
1.3.6.1.2.1.10.227.0.6current
lmpTeLinkNotDegraded
NOTIFICATION-TYPE
This notification is generated when a lmpTeLinkOperStatus object for a TE link leaves the degraded state. This notification should not be sent unless lmpTeLinkNotificationsEnabled is true(1).
1.3.6.1.2.1.10.227.0.7current
lmpDataLinkVerificationFailure
NOTIFICATION-TYPE
This notification is generated when a data-bearing link verification fails. This notification should not be sent unless lmpDataLinkNotificationsEnabled is true(1). For a given data link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
1.3.6.1.2.1.10.227.0.8current

Conformance

NameOIDStatus
lmpModuleFullCompliance
MODULE-COMPLIANCE
Compliance statement for agents that support the configuration and monitoring of LMP MIB.
1.3.6.1.2.1.10.227.2.1.1current
lmpModuleReadOnlyCompliance
MODULE-COMPLIANCE
Compliance statement for agents that support the monitoring of the LMP MIB.
1.3.6.1.2.1.10.227.2.1.2current
lmpNodeGroup
OBJECT-GROUP
Collection of objects that represent LMP node configuration.
1.3.6.1.2.1.10.227.2.2.1current
lmpControlChannelGroup
OBJECT-GROUP
Objects that can be used to configure LMP interface.
1.3.6.1.2.1.10.227.2.2.2current
lmpCcIsInterfaceGroup
OBJECT-GROUP
Objects that can be used to configure control channels that are interfaces.
1.3.6.1.2.1.10.227.2.2.3current
lmpCcIsNotInterfaceGroup
OBJECT-GROUP
Objects that can be used to configure control channels that are not interfaces.
1.3.6.1.2.1.10.227.2.2.4current
lmpLinkPropertyCorrelationGroup
OBJECT-GROUP
Collection of objects used to configure the link property correlation procedure.
1.3.6.1.2.1.10.227.2.2.5current
lmpLinkVerificationGroup
OBJECT-GROUP
Collection of objects that represent the link verification procedure configuration.
1.3.6.1.2.1.10.227.2.2.6current
lmpPerfGroup
OBJECT-GROUP
Collection of objects used to provide performance information about LMP interfaces and data-bearing links.
1.3.6.1.2.1.10.227.2.2.7current
lmpTeLinkGroup
OBJECT-GROUP
Objects that can be used to configure TE links.
1.3.6.1.2.1.10.227.2.2.8current
lmpDataLinkGroup
OBJECT-GROUP
Collection of objects that represent data-bearing link configuration.
1.3.6.1.2.1.10.227.2.2.9current
lmpNotificationGroup
NOTIFICATION-GROUP
Set of notifications defined in this module.
1.3.6.1.2.1.10.227.2.2.10current