All MIBs › LMP-MIB
Organization: Common Control and Measurement Protocols (CCAMP) Working Group
Last Updated: 2006-08-14
Category: MPLS and Traffic Engineering, Optical and WDM
Description: Defines managed objects for the Link Management Protocol (LMP), supporting control channel connectivity maintenance and fault isolation in optical networks.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring LMP-MIB with a free 30-day trial of IPNetwork Monitor.
What Is LMP-MIB?
LMP-MIB is a vendor-neutral IETF standards-track module (RFC 4631) defining managed objects for the Link Management Protocol (LMP), used in optical/GMPLS networks to maintain control-channel connectivity, verify data-link mapping, and isolate faults between adjacent nodes. It exposes administrative and operational status for LMP itself and for each LMP neighbor relationship, along with per-neighbor retransmission timers, retry limits, and row-status/storage-type control for provisioning entries, plus a notifications group for LMP-related traps. Its monitoring value is centered on control-plane and link-level fault status rather than general device hardware: lmpOperStatus and lmpNbrOperStatus reveal whether the LMP control channel and specific neighbor adjacencies are up, which is critical for detecting a broken control channel before it causes misrouted optical traffic. As an RFC 4631 module it depends on and is typically deployed alongside GMPLS/optical-network signaling standards on nodes that support LMP. It's used in service-provider optical transport and GMPLS-enabled router/switch deployments to monitor control-channel and neighbor adjacency health. Engineers can download the LMP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in LMP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- GMPLS/optical-network router or optical switch supporting LMP
Monitoring Examples
An admin would poll lmpAdminStatus/lmpOperStatus to confirm LMP is administratively enabled and operationally up on a node, then walk lmpNbrTable/lmpNbrEntry (keyed by lmpNbrNodeId) to check lmpNbrOperStatus for each neighbor adjacency and lmpNbrRetransmitInterval/lmpNbrRetryLimit/lmpNbrRetransmitDelta to assess control-channel retransmission behavior. A neighbor whose lmpNbrOperStatus drops to down while lmpNbrRetransmitDelta climbs would indicate a degrading or failed control channel to that adjacent optical node, warranting fault isolation via LMP's link-verification procedures. lmpNbrRowStatus/lmpNbrStorageType are used when provisioning or removing neighbor entries via SNMP SET operations.
What Can Be Monitored
- LMP admin/operational status
- per-neighbor operational status
- neighbor retransmit interval/delta
- neighbor retry limit
- neighbor row status/storage type
This MIB depends on
Related MIBs
Imported Objects
From IF-MIB
| InterfaceIndexOrZero | |
| ifIndex | OBJECT-TYPE |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| TimeTicks | |
| Unsigned32 | |
| transmission |
From SNMPv2-TC
| RowStatus | |
| StorageType | |
| TEXTUAL-CONVENTION | |
| TimeStamp | |
| TruthValue |
From TE-LINK-STD-MIB
| TeLinkEncodingType | |
| teLinkIncomingIfId | OBJECT-TYPE |
| teLinkRemoteIpAddr | OBJECT-TYPE |
How to Use in IPNetwork Monitor
Example using lmpCcInOctets OID:
Select a device implementing LMP-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type lmpCcInOctets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of LMP message octets received on the control channel. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| lmpMIB | 1.3.6.1.2.1.10.227 | 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'. | ||
| lmpNotifications | 1.3.6.1.2.1.10.227.0 | |||
| NTF lmpTeLinkPropertyMismatch | 1.3.6.1.2.1.10.227.0.1 | 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). | ||
| NTF lmpDataLinkPropertyMismatch | 1.3.6.1.2.1.10.227.0.2 | 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). | ||
| NTF lmpUnprotected | 1.3.6.1.2.1.10.227.0.3 | 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). | ||
| NTF lmpControlChannelUp | 1.3.6.1.2.1.10.227.0.4 | 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). | ||
| NTF lmpControlChannelDown | 1.3.6.1.2.1.10.227.0.5 | 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). | ||
| NTF lmpTeLinkDegraded | 1.3.6.1.2.1.10.227.0.6 | 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). | ||
| NTF lmpTeLinkNotDegraded | 1.3.6.1.2.1.10.227.0.7 | 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). | ||
| NTF lmpDataLinkVerificationFailure | 1.3.6.1.2.1.10.227.0.8 | 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). | ||
| lmpObjects | 1.3.6.1.2.1.10.227.1 | |||
| INT lmpAdminStatus | 1.3.6.1.2.1.10.227.1.1 | INTEGER | read-write | 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. |
| INT lmpOperStatus | 1.3.6.1.2.1.10.227.1.2 | INTEGER | read-only | The actual operational status of LMP on the node. |
| lmpNbrTable | 1.3.6.1.2.1.10.227.1.3 | not-accessible | This table specifies the neighbor node(s) to which control channels may be established. | |
| lmpNbrEntry | 1.3.6.1.2.1.10.227.1.3.1 | not-accessible | An entry in this table is created by a LMP-enabled device for every pair of nodes that can establish control channels. | |
| LMP lmpNbrNodeId | 1.3.6.1.2.1.10.227.1.3.1.1 | LmpNodeId | not-accessible | This is a unique index for an entry in the LmpNbrTable. This value represents the remote Node ID. |
| NUM lmpNbrRetransmitInterval | 1.3.6.1.2.1.10.227.1.3.1.2 | LmpRetransmitInterval | read-create | 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. |
| U32 lmpNbrRetryLimit | 1.3.6.1.2.1.10.227.1.3.1.3 | Unsigned32 | read-create | 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. |
| U32 lmpNbrRetransmitDelta | 1.3.6.1.2.1.10.227.1.3.1.4 | Unsigned32 | read-create | 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). |
| INT lmpNbrAdminStatus | 1.3.6.1.2.1.10.227.1.3.1.5 | INTEGER | read-create | The desired operational status of LMP to this remote node. |
| INT lmpNbrOperStatus | 1.3.6.1.2.1.10.227.1.3.1.6 | INTEGER | read-only | The actual operational status of LMP to this remote node. |
| ROW lmpNbrRowStatus | 1.3.6.1.2.1.10.227.1.3.1.7 | RowStatus | read-create | 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. |
| STO lmpNbrStorageType | 1.3.6.1.2.1.10.227.1.3.1.8 | StorageType | read-create | 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. |
| NUM lmpCcHelloIntervalDefault | 1.3.6.1.2.1.10.227.1.4 | LmpInterval | read-write | 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. |
| NUM lmpCcHelloIntervalDefaultMin | 1.3.6.1.2.1.10.227.1.5 | LmpInterval | read-write | 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. |
| NUM lmpCcHelloIntervalDefaultMax | 1.3.6.1.2.1.10.227.1.6 | LmpInterval | read-write | 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. |
| NUM lmpCcHelloDeadIntervalDefault | 1.3.6.1.2.1.10.227.1.7 | LmpInterval | read-write | 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. |
| NUM lmpCcHelloDeadIntervalDefaultMin | 1.3.6.1.2.1.10.227.1.8 | LmpInterval | read-write | 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. |
| NUM lmpCcHelloDeadIntervalDefaultMax | 1.3.6.1.2.1.10.227.1.9 | LmpInterval | read-write | 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. |
| lmpControlChannelTable | 1.3.6.1.2.1.10.227.1.10 | not-accessible | This table specifies LMP control channel information. | |
| lmpControlChannelEntry | 1.3.6.1.2.1.10.227.1.10.1 | not-accessible | 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). | |
| U32 lmpCcId | 1.3.6.1.2.1.10.227.1.10.1.1 | Unsigned32 | not-accessible | This value represents the local control channel identifier. The control channel identifier is a non-zero 32-bit number. |
| NUM lmpCcUnderlyingIfIndex | 1.3.6.1.2.1.10.227.1.10.1.2 | InterfaceIndexOrZero | read-create | 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. |
| T/F lmpCcIsIf | 1.3.6.1.2.1.10.227.1.10.1.3 | TruthValue | read-create | 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. |
| LMP lmpCcNbrNodeId | 1.3.6.1.2.1.10.227.1.10.1.4 | LmpNodeId | read-create | 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. |
| U32 lmpCcRemoteId | 1.3.6.1.2.1.10.227.1.10.1.5 | Unsigned32 | read-only | 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. |
| IPt lmpCcRemoteAddressType | 1.3.6.1.2.1.10.227.1.10.1.6 | InetAddressType | read-create | This value represents the remote control channel IP address type. In point-to-point configuration, this value can be set to unknown(0). |
| IP lmpCcRemoteIpAddr | 1.3.6.1.2.1.10.227.1.10.1.7 | InetAddress | read-create | 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. |
| INT lmpCcSetupRole | 1.3.6.1.2.1.10.227.1.10.1.8 | INTEGER | read-create | 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. |
| T/F lmpCcAuthentication | 1.3.6.1.2.1.10.227.1.10.1.9 | TruthValue | read-create | This object indicates whether the control channel must use authentication. |
| NUM lmpCcHelloInterval | 1.3.6.1.2.1.10.227.1.10.1.10 | LmpInterval | read-create | This object specifies the value of the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalDefault. |
| NUM lmpCcHelloIntervalMin | 1.3.6.1.2.1.10.227.1.10.1.11 | LmpInterval | read-create | This object specifies the minimum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMinDefault. |
| NUM lmpCcHelloIntervalMax | 1.3.6.1.2.1.10.227.1.10.1.12 | LmpInterval | read-create | This object specifies the maximum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault. |
| NUM lmpCcHelloIntervalNegotiated | 1.3.6.1.2.1.10.227.1.10.1.13 | LmpInterval | read-only | Once the control channel is active, this object represents the negotiated HelloInterval value. |
| NUM lmpCcHelloDeadInterval | 1.3.6.1.2.1.10.227.1.10.1.14 | LmpInterval | read-create | This object specifies the value of the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalDefault. |
| NUM lmpCcHelloDeadIntervalMin | 1.3.6.1.2.1.10.227.1.10.1.15 | LmpInterval | read-create | This object specifies the minimum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalMinDefault. |
| NUM lmpCcHelloDeadIntervalMax | 1.3.6.1.2.1.10.227.1.10.1.16 | LmpInterval | read-create | This object specifies the maximum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault. |
| NUM lmpCcHelloDeadIntervalNegotiated | 1.3.6.1.2.1.10.227.1.10.1.17 | LmpInterval | read-only | Once the control channel is active, this object represents the negotiated HelloDeadInterval value. |
| TIK lmpCcLastChange | 1.3.6.1.2.1.10.227.1.10.1.18 | TimeTicks | read-only | 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. |
| INT lmpCcAdminStatus | 1.3.6.1.2.1.10.227.1.10.1.19 | INTEGER | read-create | The desired operational status of this control channel. |
| INT lmpCcOperStatus | 1.3.6.1.2.1.10.227.1.10.1.20 | INTEGER | read-only | The actual operational status of this control channel. |
| ROW lmpCcRowStatus | 1.3.6.1.2.1.10.227.1.10.1.21 | RowStatus | read-create | 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. |
| STO lmpCcStorageType | 1.3.6.1.2.1.10.227.1.10.1.22 | StorageType | read-create | 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. |
| lmpControlChannelPerfTable | 1.3.6.1.2.1.10.227.1.11 | not-accessible | This table specifies LMP control channel performance counters. | |
| lmpControlChannelPerfEntry | 1.3.6.1.2.1.10.227.1.11.1 | not-accessible | 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. | |
| C32 lmpCcInOctetsEx | 1.3.6.1.2.1.10.227.1.11.1.1 | Counter32 | read-only | The total number of LMP message octets received on the control channel. |
| C32 lmpCcInDiscards | 1.3.6.1.2.1.10.227.1.11.1.2 | Counter32 | read-only | 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. |
| C32 lmpCcInErrors | 1.3.6.1.2.1.10.227.1.11.1.3 | Counter32 | read-only | The number of inbound packets that contained errors preventing them from being processed by LMP. |
| C32 lmpCcOutOctets | 1.3.6.1.2.1.10.227.1.11.1.4 | Counter32 | read-only | The total number of LMP message octets transmitted out of the control channel. |
| C32 lmpCcOutDiscards | 1.3.6.1.2.1.10.227.1.11.1.5 | Counter32 | read-only | 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. |
| C32 lmpCcOutErrors | 1.3.6.1.2.1.10.227.1.11.1.6 | Counter32 | read-only | The number of outbound packets that could not be transmitted because of errors. |
| C32 lmpCcConfigReceived | 1.3.6.1.2.1.10.227.1.11.1.7 | Counter32 | read-only | This object counts the number of Config messages that have been received on this control channel. |
| C32 lmpCcConfigSent | 1.3.6.1.2.1.10.227.1.11.1.8 | Counter32 | read-only | This object counts the number of Config messages that have been sent on this control channel. |
| C32 lmpCcConfigRetransmit | 1.3.6.1.2.1.10.227.1.11.1.9 | Counter32 | read-only | This object counts the number of Config messages that have been retransmitted over this control channel. |
| C32 lmpCcConfigAckReceived | 1.3.6.1.2.1.10.227.1.11.1.10 | Counter32 | read-only | This object counts the number of ConfigAck messages that have been received on this control channel. |
| C32 lmpCcConfigAckSent | 1.3.6.1.2.1.10.227.1.11.1.11 | Counter32 | read-only | This object counts the number of ConfigAck messages that have been sent on this control channel. |
| C32 lmpCcConfigNackReceived | 1.3.6.1.2.1.10.227.1.11.1.12 | Counter32 | read-only | This object counts the number of ConfigNack messages that have been received on this control channel. |
| C32 lmpCcConfigNackSent | 1.3.6.1.2.1.10.227.1.11.1.13 | Counter32 | read-only | This object counts the number of ConfigNack messages that have been sent on this control channel. |
| C32 lmpCcHelloReceived | 1.3.6.1.2.1.10.227.1.11.1.14 | Counter32 | read-only | This object counts the number of Hello messages that have been received on this control channel. |
| C32 lmpCcHelloSent | 1.3.6.1.2.1.10.227.1.11.1.15 | Counter32 | read-only | This object counts the number of Hello messages that have been sent on this control channel. |
| C32 lmpCcBeginVerifyReceived | 1.3.6.1.2.1.10.227.1.11.1.16 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been received on this control channel. |
| C32 lmpCcBeginVerifySent | 1.3.6.1.2.1.10.227.1.11.1.17 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been sent on this control channel. |
| C32 lmpCcBeginVerifyRetransmit | 1.3.6.1.2.1.10.227.1.11.1.18 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been retransmitted over this control channel. |
| C32 lmpCcBeginVerifyAckReceived | 1.3.6.1.2.1.10.227.1.11.1.19 | Counter32 | read-only | This object counts the number of BeginVerifyAck messages that have been received on this control channel. |
| C32 lmpCcBeginVerifyAckSent | 1.3.6.1.2.1.10.227.1.11.1.20 | Counter32 | read-only | This object counts the number of BeginVerifyAck messages that have been sent on this control channel. |
| C32 lmpCcBeginVerifyNackReceived | 1.3.6.1.2.1.10.227.1.11.1.21 | Counter32 | read-only | This object counts the number of BeginVerifyNack messages that have been received on this control channel. |
| C32 lmpCcBeginVerifyNackSent | 1.3.6.1.2.1.10.227.1.11.1.22 | Counter32 | read-only | This object counts the number of BeginVerifyNack messages that have been sent on this control channel. |
| C32 lmpCcEndVerifyReceived | 1.3.6.1.2.1.10.227.1.11.1.23 | Counter32 | read-only | This object counts the number of EndVerify messages that have been received on this control channel. |
| C32 lmpCcEndVerifySent | 1.3.6.1.2.1.10.227.1.11.1.24 | Counter32 | read-only | This object counts the number of EndVerify messages that have been sent on this control channel. |
| C32 lmpCcEndVerifyRetransmit | 1.3.6.1.2.1.10.227.1.11.1.25 | Counter32 | read-only | This object counts the number of EndVerify messages that have been retransmitted over this control channel. |
| C32 lmpCcEndVerifyAckReceived | 1.3.6.1.2.1.10.227.1.11.1.26 | Counter32 | read-only | This object counts the number of EndVerifyAck messages that have been received on this control channel. |
| C32 lmpCcEndVerifyAckSent | 1.3.6.1.2.1.10.227.1.11.1.27 | Counter32 | read-only | This object counts the number of EndVerifyAck messages that have been sent on this control channel. |
| C32 lmpCcTestStatusSuccessReceived | 1.3.6.1.2.1.10.227.1.11.1.28 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been received on this control channel. |
| C32 lmpCcTestStatusSuccessSent | 1.3.6.1.2.1.10.227.1.11.1.29 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been sent on this control channel. |
| C32 lmpCcTestStatusSuccessRetransmit | 1.3.6.1.2.1.10.227.1.11.1.30 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been retransmitted over this control channel. |
| C32 lmpCcTestStatusFailureReceived | 1.3.6.1.2.1.10.227.1.11.1.31 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been received on this control channel. |
| C32 lmpCcTestStatusFailureSent | 1.3.6.1.2.1.10.227.1.11.1.32 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been sent on this control channel. |
| C32 lmpCcTestStatusFailureRetransmit | 1.3.6.1.2.1.10.227.1.11.1.33 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been retransmitted over this control channel. |
| C32 lmpCcTestStatusAckReceived | 1.3.6.1.2.1.10.227.1.11.1.34 | Counter32 | read-only | This object counts the number of TestStatusAck messages that have been received on this control channel. |
| C32 lmpCcTestStatusAckSent | 1.3.6.1.2.1.10.227.1.11.1.35 | Counter32 | read-only | This object counts the number of TestStatusAck messages that have been sent on this control channel. |
| C32 lmpCcLinkSummaryReceived | 1.3.6.1.2.1.10.227.1.11.1.36 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been received on this control channel. |
| C32 lmpCcLinkSummarySent | 1.3.6.1.2.1.10.227.1.11.1.37 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been sent on this control channel. |
| C32 lmpCcLinkSummaryRetransmit | 1.3.6.1.2.1.10.227.1.11.1.38 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been retransmitted over this control channel. |
| C32 lmpCcLinkSummaryAckReceived | 1.3.6.1.2.1.10.227.1.11.1.39 | Counter32 | read-only | This object counts the number of LinkSummaryAck messages that have been received on this control channel. |
| C32 lmpCcLinkSummaryAckSent | 1.3.6.1.2.1.10.227.1.11.1.40 | Counter32 | read-only | This object counts the number of LinkSummaryAck messages that have been sent on this control channel. |
| C32 lmpCcLinkSummaryNackReceived | 1.3.6.1.2.1.10.227.1.11.1.41 | Counter32 | read-only | This object counts the number of LinkSummaryNack messages that have been received on this control channel. |
| C32 lmpCcLinkSummaryNackSent | 1.3.6.1.2.1.10.227.1.11.1.42 | Counter32 | read-only | This object counts the number of LinkSummaryNack messages that have been sent on this control channel. |
| C32 lmpCcChannelStatusReceived | 1.3.6.1.2.1.10.227.1.11.1.43 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been received on this control channel. |
| C32 lmpCcChannelStatusSent | 1.3.6.1.2.1.10.227.1.11.1.44 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been sent on this control channel. |
| C32 lmpCcChannelStatusRetransmit | 1.3.6.1.2.1.10.227.1.11.1.45 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been retransmitted on this control channel. |
| C32 lmpCcChannelStatusAckReceived | 1.3.6.1.2.1.10.227.1.11.1.46 | Counter32 | read-only | This object counts the number of ChannelStatusAck messages that have been received on this control channel. |
| C32 lmpCcChannelStatusAckSent | 1.3.6.1.2.1.10.227.1.11.1.47 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been sent on this control channel. |
| C32 lmpCcChannelStatusReqReceived | 1.3.6.1.2.1.10.227.1.11.1.48 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been received on this control channel. |
| C32 lmpCcChannelStatusReqSent | 1.3.6.1.2.1.10.227.1.11.1.49 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been sent on this control channel. |
| C32 lmpCcChannelStatusReqRetransmit | 1.3.6.1.2.1.10.227.1.11.1.50 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been retransmitted on this control channel. |
| C32 lmpCcChannelStatusRspReceived | 1.3.6.1.2.1.10.227.1.11.1.51 | Counter32 | read-only | This object counts the number of ChannelStatusResponse messages that have been received on this control channel. |
| C32 lmpCcChannelStatusRspSent | 1.3.6.1.2.1.10.227.1.11.1.52 | Counter32 | read-only | This object counts the number of ChannelStatusResponse messages that have been sent on this control channel. |
| TIM lmpCcCounterDiscontinuityTime | 1.3.6.1.2.1.10.227.1.11.1.53 | TimeStamp | read-only | 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. |
| lmpTeLinkTable | 1.3.6.1.2.1.10.227.1.12 | not-accessible | 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. | |
| lmpTeLinkEntry | 1.3.6.1.2.1.10.227.1.12.1 | not-accessible | 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. | |
| LMP lmpTeLinkNbrRemoteNodeId | 1.3.6.1.2.1.10.227.1.12.1.1 | LmpNodeId | read-create | 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. |
| T/F lmpTeLinkVerification | 1.3.6.1.2.1.10.227.1.12.1.2 | TruthValue | read-create | This object indicates whether the LMP link verification procedure is enabled for this TE link. |
| T/F lmpTeLinkFaultManagement | 1.3.6.1.2.1.10.227.1.12.1.3 | TruthValue | read-create | This object indicates whether the LMP fault management procedure is enabled on this TE link. |
| T/F lmpTeLinkDwdm | 1.3.6.1.2.1.10.227.1.12.1.4 | TruthValue | read-create | This object indicates whether the LMP DWDM procedure is enabled on this TE link. |
| INT lmpTeLinkOperStatus | 1.3.6.1.2.1.10.227.1.12.1.5 | INTEGER | read-only | 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. |
| ROW lmpTeLinkRowStatus | 1.3.6.1.2.1.10.227.1.12.1.6 | RowStatus | read-create | 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. |
| STO lmpTeLinkStorageType | 1.3.6.1.2.1.10.227.1.12.1.7 | StorageType | read-create | 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. |
| U32 lmpGlobalLinkVerificationInterval | 1.3.6.1.2.1.10.227.1.13 | Unsigned32 | read-write | 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. |
| lmpLinkVerificationTable | 1.3.6.1.2.1.10.227.1.14 | not-accessible | This table specifies TE link information associated with the LMP verification procedure. | |
| lmpLinkVerificationEntry | 1.3.6.1.2.1.10.227.1.14.1 | not-accessible | An entry in this table is created by an LMP-enabled device for every TE link that supports the LMP verification procedure. | |
| NUM lmpLinkVerifyInterval | 1.3.6.1.2.1.10.227.1.14.1.1 | LmpInterval | read-create | This object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent. |
| NUM lmpLinkVerifyDeadInterval | 1.3.6.1.2.1.10.227.1.14.1.2 | LmpInterval | read-create | 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. |
| BIT lmpLinkVerifyTransportMechanism | 1.3.6.1.2.1.10.227.1.14.1.3 | Bits | read-create | 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. |
| T/F lmpLinkVerifyAllLinks | 1.3.6.1.2.1.10.227.1.14.1.4 | TruthValue | read-create | A value of true(1) for this object indicates that the verification process checks all unallocated links; otherwise, only the new ports or component links that have been added to this TE link are verified. |
| U32 lmpLinkVerifyTransmissionRate | 1.3.6.1.2.1.10.227.1.14.1.5 | Unsigned32 | read-create | This is the transmission rate of the data link over which the Test messages will be transmitted and is expressed in bytes per second. |
| U32 lmpLinkVerifyWavelength | 1.3.6.1.2.1.10.227.1.14.1.6 | Unsigned32 | read-create | 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. |
| ROW lmpLinkVerifyRowStatus | 1.3.6.1.2.1.10.227.1.14.1.7 | RowStatus | read-create | 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. |
| STO lmpLinkVerifyStorageType | 1.3.6.1.2.1.10.227.1.14.1.8 | StorageType | read-create | 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. |
| lmpTeLinkPerfTable | 1.3.6.1.2.1.10.227.1.15 | not-accessible | This table specifies LMP TE link performance counters. | |
| lmpTeLinkPerfEntry | 1.3.6.1.2.1.10.227.1.15.1 | not-accessible | 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. | |
| C32 lmpTeInOctets | 1.3.6.1.2.1.10.227.1.15.1.1 | Counter32 | read-only | The total number of LMP message octets received for this TE link. |
| C32 lmpTeOutOctets | 1.3.6.1.2.1.10.227.1.15.1.2 | Counter32 | read-only | The total number of LMP message octets transmitted out for this TE link. |
| C32 lmpTeBeginVerifyReceived | 1.3.6.1.2.1.10.227.1.15.1.3 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been received for this TE link. |
| C32 lmpTeBeginVerifySent | 1.3.6.1.2.1.10.227.1.15.1.4 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been sent for this TE link. |
| C32 lmpTeBeginVerifyRetransmit | 1.3.6.1.2.1.10.227.1.15.1.5 | Counter32 | read-only | This object counts the number of BeginVerify messages that have been retransmitted for this TE link. |
| C32 lmpTeBeginVerifyAckReceived | 1.3.6.1.2.1.10.227.1.15.1.6 | Counter32 | read-only | This object counts the number of BeginVerifyAck messages that have been received for this TE link. |
| C32 lmpTeBeginVerifyAckSent | 1.3.6.1.2.1.10.227.1.15.1.7 | Counter32 | read-only | This object counts the number of BeginVerifyAck messages that have been sent for this TE link. |
| C32 lmpTeBeginVerifyNackReceived | 1.3.6.1.2.1.10.227.1.15.1.8 | Counter32 | read-only | This object counts the number of BeginVerifyNack messages that have been received for this TE link. |
| C32 lmpTeBeginVerifyNackSent | 1.3.6.1.2.1.10.227.1.15.1.9 | Counter32 | read-only | This object counts the number of BeginVerifyNack messages that have been sent for this TE link. |
| C32 lmpTeEndVerifyReceived | 1.3.6.1.2.1.10.227.1.15.1.10 | Counter32 | read-only | This object counts the number of EndVerify messages that have been received for this TE link. |
| C32 lmpTeEndVerifySent | 1.3.6.1.2.1.10.227.1.15.1.11 | Counter32 | read-only | This object counts the number of EndVerify messages that have been sent for this TE link. |
| C32 lmpTeEndVerifyRetransmit | 1.3.6.1.2.1.10.227.1.15.1.12 | Counter32 | read-only | This object counts the number of EndVerify messages that have been retransmitted over this control channel. |
| C32 lmpTeEndVerifyAckReceived | 1.3.6.1.2.1.10.227.1.15.1.13 | Counter32 | read-only | This object counts the number of EndVerifyAck messages that have been received for this TE link. |
| C32 lmpTeEndVerifyAckSent | 1.3.6.1.2.1.10.227.1.15.1.14 | Counter32 | read-only | This object counts the number of EndVerifyAck messages that have been sent for this TE link. |
| C32 lmpTeTestStatusSuccessReceived | 1.3.6.1.2.1.10.227.1.15.1.15 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been received for this TE link. |
| C32 lmpTeTestStatusSuccessSent | 1.3.6.1.2.1.10.227.1.15.1.16 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been sent for this TE link. |
| C32 lmpTeTestStatusSuccessRetransmit | 1.3.6.1.2.1.10.227.1.15.1.17 | Counter32 | read-only | This object counts the number of TestStatusSuccess messages that have been retransmitted for this TE link. |
| C32 lmpTeTestStatusFailureReceived | 1.3.6.1.2.1.10.227.1.15.1.18 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been received for this TE link. |
| C32 lmpTeTestStatusFailureSent | 1.3.6.1.2.1.10.227.1.15.1.19 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been sent for this TE link. |
| C32 lmpTeTestStatusFailureRetransmit | 1.3.6.1.2.1.10.227.1.15.1.20 | Counter32 | read-only | This object counts the number of TestStatusFailure messages that have been retransmitted on this TE link. |
| C32 lmpTeTestStatusAckReceived | 1.3.6.1.2.1.10.227.1.15.1.21 | Counter32 | read-only | This object counts the number of TestStatusAck messages that have been received for this TE link. |
| C32 lmpTeTestStatusAckSent | 1.3.6.1.2.1.10.227.1.15.1.22 | Counter32 | read-only | This object counts the number of TestStatusAck messages that have been sent for this TE link. |
| C32 lmpTeLinkSummaryReceived | 1.3.6.1.2.1.10.227.1.15.1.23 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been received for this TE link. |
| C32 lmpTeLinkSummarySent | 1.3.6.1.2.1.10.227.1.15.1.24 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been sent for this TE link. |
| C32 lmpTeLinkSummaryRetransmit | 1.3.6.1.2.1.10.227.1.15.1.25 | Counter32 | read-only | This object counts the number of LinkSummary messages that have been retransmitted over this control channel. |
| C32 lmpTeLinkSummaryAckReceived | 1.3.6.1.2.1.10.227.1.15.1.26 | Counter32 | read-only | This object counts the number of LinkSummaryAck messages that have been received for this TE link. |
| C32 lmpTeLinkSummaryAckSent | 1.3.6.1.2.1.10.227.1.15.1.27 | Counter32 | read-only | This object counts the number of LinkSummaryAck messages that have been sent for this TE link. |
| C32 lmpTeLinkSummaryNackReceived | 1.3.6.1.2.1.10.227.1.15.1.28 | Counter32 | read-only | This object counts the number of LinkSummaryNack messages that have been received for this TE link. |
| C32 lmpTeLinkSummaryNackSent | 1.3.6.1.2.1.10.227.1.15.1.29 | Counter32 | read-only | This object counts the number of LinkSummaryNack messages that have been sent for this TE link. |
| C32 lmpTeChannelStatusReceived | 1.3.6.1.2.1.10.227.1.15.1.30 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been received for this TE link. |
| C32 lmpTeChannelStatusSent | 1.3.6.1.2.1.10.227.1.15.1.31 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been sent for this TE link. |
| C32 lmpTeChannelStatusRetransmit | 1.3.6.1.2.1.10.227.1.15.1.32 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been retransmitted for this TE link. |
| C32 lmpTeChannelStatusAckReceived | 1.3.6.1.2.1.10.227.1.15.1.33 | Counter32 | read-only | This object counts the number of ChannelStatusAck messages that have been received for this TE link. |
| C32 lmpTeChannelStatusAckSent | 1.3.6.1.2.1.10.227.1.15.1.34 | Counter32 | read-only | This object counts the number of ChannelStatus messages that have been sent for this TE link. |
| C32 lmpTeChannelStatusReqReceived | 1.3.6.1.2.1.10.227.1.15.1.35 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been received for this TE link. |
| C32 lmpTeChannelStatusReqSent | 1.3.6.1.2.1.10.227.1.15.1.36 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been sent for this TE link. |
| C32 lmpTeChannelStatusReqRetransmit | 1.3.6.1.2.1.10.227.1.15.1.37 | Counter32 | read-only | This object counts the number of ChannelStatusRequest messages that have been retransmitted for this TE link. |
| C32 lmpTeChannelStatusRspReceived | 1.3.6.1.2.1.10.227.1.15.1.38 | Counter32 | read-only | This object counts the number of ChannelStatusResponse messages that have been received for this TE link. |
| C32 lmpTeChannelStatusRspSent | 1.3.6.1.2.1.10.227.1.15.1.39 | Counter32 | read-only | This object counts the number of ChannelStatusResponse messages that have been sent for this TE link. |
| TIM lmpTeCounterDiscontinuityTime | 1.3.6.1.2.1.10.227.1.15.1.40 | TimeStamp | read-only | 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. |
| lmpDataLinkTable | 1.3.6.1.2.1.10.227.1.16 | not-accessible | This table specifies the data-bearing links managed by the LMP. | |
| lmpDataLinkEntry | 1.3.6.1.2.1.10.227.1.16.1 | not-accessible | 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. | |
| INT lmpDataLinkType | 1.3.6.1.2.1.10.227.1.16.1.1 | INTEGER | read-only | 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. |
| IPt lmpDataLinkAddressType | 1.3.6.1.2.1.10.227.1.16.1.2 | InetAddressType | read-create | 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). |
| IP lmpDataLinkIpAddr | 1.3.6.1.2.1.10.227.1.16.1.3 | InetAddress | read-create | 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. |
| IP lmpDataLinkRemoteIpAddress | 1.3.6.1.2.1.10.227.1.16.1.4 | InetAddress | read-create | 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. |
| NUM lmpDataLinkRemoteIfId | 1.3.6.1.2.1.10.227.1.16.1.5 | InterfaceIndexOrZero | read-create | Interface identifier of the remote end point. This information is either configured manually or communicated by the remote node during the link verification procedure. |
| TEL lmpDataLinkEncodingType | 1.3.6.1.2.1.10.227.1.16.1.6 | TeLinkEncodingType | read-create | The encoding type of the data-bearing link. |
| INT lmpDataLinkActiveOperStatus | 1.3.6.1.2.1.10.227.1.16.1.7 | INTEGER | read-only | The actual operational status of this data-bearing link (active FSM). |
| INT lmpDataLinkPassiveOperStatus | 1.3.6.1.2.1.10.227.1.16.1.8 | INTEGER | read-only | The actual operational status of this data-bearing link (passive FSM). |
| ROW lmpDataLinkRowStatus | 1.3.6.1.2.1.10.227.1.16.1.9 | RowStatus | read-create | 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. |
| STO lmpDataLinkStorageType | 1.3.6.1.2.1.10.227.1.16.1.10 | StorageType | read-create | 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. |
| lmpDataLinkPerfTable | 1.3.6.1.2.1.10.227.1.17 | not-accessible | This table specifies the data-bearing links LMP performance counters. | |
| lmpDataLinkPerfEntry | 1.3.6.1.2.1.10.227.1.17.1 | not-accessible | 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. | |
| C32 lmpDataLinkTestReceived | 1.3.6.1.2.1.10.227.1.17.1.1 | Counter32 | read-only | This object counts the number of Test messages that have been received on this data-bearing link. |
| C32 lmpDataLinkTestSent | 1.3.6.1.2.1.10.227.1.17.1.2 | Counter32 | read-only | This object counts the number of Test messages that have been sent on this data-bearing link. |
| C32 lmpDataLinkActiveTestSuccess | 1.3.6.1.2.1.10.227.1.17.1.3 | Counter32 | read-only | This object counts the number of data-bearing link tests that were successful on the active side of this data- bearing link. |
| C32 lmpDataLinkActiveTestFailure | 1.3.6.1.2.1.10.227.1.17.1.4 | Counter32 | read-only | This object counts the number of data-bearing link tests that failed on the active side of this data-bearing link. |
| C32 lmpDataLinkPassiveTestSuccess | 1.3.6.1.2.1.10.227.1.17.1.5 | Counter32 | read-only | This object counts the number of data-bearing link tests that were successful on the passive side of this data- bearing link. |
| C32 lmpDataLinkPassiveTestFailure | 1.3.6.1.2.1.10.227.1.17.1.6 | Counter32 | read-only | This object counts the number of data-bearing link tests that failed on the passive side of this data-bearing link. |
| TIM lmpDataLinkDiscontinuityTime | 1.3.6.1.2.1.10.227.1.17.1.7 | TimeStamp | read-only | 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. |
| U32 lmpNotificationMaxRate | 1.3.6.1.2.1.10.227.1.18 | Unsigned32 | read-write | 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. |
| T/F lmpLinkPropertyNotificationsEnabled | 1.3.6.1.2.1.10.227.1.19 | TruthValue | read-write | 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. |
| T/F lmpUnprotectedNotificationsEnabled | 1.3.6.1.2.1.10.227.1.20 | TruthValue | read-write | 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. |
| T/F lmpCcUpDownNotificationsEnabled | 1.3.6.1.2.1.10.227.1.21 | TruthValue | read-write | 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. |
| T/F lmpTeLinkNotificationsEnabled | 1.3.6.1.2.1.10.227.1.22 | TruthValue | read-write | 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. |
| T/F lmpDataLinkNotificationsEnabled | 1.3.6.1.2.1.10.227.1.23 | TruthValue | read-write | 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. |
| lmpConformance | 1.3.6.1.2.1.10.227.2 | |||
| lmpCompliances | 1.3.6.1.2.1.10.227.2.1 | |||
| lmpModuleFullCompliance | 1.3.6.1.2.1.10.227.2.1.1 | Compliance statement for agents that support the configuration and monitoring of LMP MIB. | ||
| lmpModuleReadOnlyCompliance | 1.3.6.1.2.1.10.227.2.1.2 | Compliance statement for agents that support the monitoring of the LMP MIB. | ||
| lmpGroups | 1.3.6.1.2.1.10.227.2.2 | |||
| lmpNodeGroup | 1.3.6.1.2.1.10.227.2.2.1 | Collection of objects that represent LMP node configuration. | ||
| lmpControlChannelGroup | 1.3.6.1.2.1.10.227.2.2.2 | Objects that can be used to configure LMP interface. | ||
| lmpCcIsInterfaceGroup | 1.3.6.1.2.1.10.227.2.2.3 | Objects that can be used to configure control channels that are interfaces. | ||
| lmpCcIsNotInterfaceGroup | 1.3.6.1.2.1.10.227.2.2.4 | Objects that can be used to configure control channels that are not interfaces. | ||
| lmpLinkPropertyCorrelationGroup | 1.3.6.1.2.1.10.227.2.2.5 | Collection of objects used to configure the link property correlation procedure. | ||
| lmpLinkVerificationGroup | 1.3.6.1.2.1.10.227.2.2.6 | Collection of objects that represent the link verification procedure configuration. | ||
| lmpPerfGroup | 1.3.6.1.2.1.10.227.2.2.7 | Collection of objects used to provide performance information about LMP interfaces and data-bearing links. | ||
| lmpTeLinkGroup | 1.3.6.1.2.1.10.227.2.2.8 | Objects that can be used to configure TE links. | ||
| lmpDataLinkGroup | 1.3.6.1.2.1.10.227.2.2.9 | Collection of objects that represent data-bearing link configuration. | ||
| lmpNotificationGroup | 1.3.6.1.2.1.10.227.2.2.10 | Set of notifications defined in this module. |
RFC description
Manages Link Management Protocol for optical transport network link discovery and fault verification.
Start monitoring Vendor-neutral IETF standard, RFC 4631 (GMPLS/optical-network router or switch) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.