Home/Catalog/LMP-MIB

LMP-MIB

AI MIB Summary

The LMP-MIB manages Link Management Protocol (LMP) operations for GMPLS-controlled optical networks, monitoring link verification status, link property attributes, and fault isolation states to ensure the integrity of label-switched paths.

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'.
Main OID:
lmpMIB.1.3.6.1.2.1.10.227
212
Objects
Active
Status
6
Dependencies

Imported Objects

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

Objects

212 total
Object Name
lmpMIBCopyright (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'.
MODULE-IDENTITY
.1.3.6.1.2.1.10.227
lmpNotifications
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.227.0
lmpTeLinkPropertyMismatchThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.1
lmpDataLinkPropertyMismatchThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.2
lmpUnprotectedThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.3
lmpControlChannelUpThis notification is generated when a control channel transitions to the up operational state. This notification should not be sent unless lmpCcUpDownNotificationsEnabled is true(1).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.4
lmpControlChannelDownThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.5
lmpTeLinkDegradedThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.6
lmpTeLinkNotDegradedThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.7
lmpDataLinkVerificationFailureThis 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).
NOTIFICATION-TYPE
.1.3.6.1.2.1.10.227.0.8
lmpObjects
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.227.1
lmpAdminStatusThe 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.rw
Enumeration
.1.3.6.1.2.1.10.227.1.1
lmpOperStatusThe actual operational status of LMP on the node.ro
Enumeration
.1.3.6.1.2.1.10.227.1.2
lmpNbrTableThis table specifies the neighbor node(s) to which control channels may be established.
SEQUENCE OF LmpNbrEntry
.1.3.6.1.2.1.10.227.1.3
lmpNbrEntryAn entry in this table is created by a LMP-enabled device for every pair of nodes that can establish control channels.
LmpNbrEntry
.1.3.6.1.2.1.10.227.1.3.1
lmpNbrNodeIdThis is a unique index for an entry in the LmpNbrTable. This value represents the remote Node ID.
LmpNodeId
.1.3.6.1.2.1.10.227.1.3.1.1
lmpNbrRetransmitIntervalThis 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.rw
LmpRetransmitInterval
.1.3.6.1.2.1.10.227.1.3.1.2
lmpNbrRetryLimitThis 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.rw
Unsigned32
.1.3.6.1.2.1.10.227.1.3.1.3
lmpNbrRetransmitDeltaThis 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).rw
Unsigned32
.1.3.6.1.2.1.10.227.1.3.1.4
lmpNbrAdminStatusThe desired operational status of LMP to this remote node.rw
Enumeration
.1.3.6.1.2.1.10.227.1.3.1.5
lmpNbrOperStatusThe actual operational status of LMP to this remote node.ro
Enumeration
.1.3.6.1.2.1.10.227.1.3.1.6
lmpNbrRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.3.1.7
lmpNbrStorageTypeThe 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.rw
StorageType (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.3.1.8
lmpCcHelloIntervalDefaultThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.4
lmpCcHelloIntervalDefaultMinThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.5
lmpCcHelloIntervalDefaultMaxThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.6
lmpCcHelloDeadIntervalDefaultThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.7
lmpCcHelloDeadIntervalDefaultMinThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.8
lmpCcHelloDeadIntervalDefaultMaxThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.9
lmpControlChannelTableThis table specifies LMP control channel information.
SEQUENCE OF LmpControlChannelEntry
.1.3.6.1.2.1.10.227.1.10
lmpControlChannelEntryAn 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).
LmpControlChannelEntry
.1.3.6.1.2.1.10.227.1.10.1
lmpCcIdThis value represents the local control channel identifier. The control channel identifier is a non-zero 32-bit number.
Unsigned32
.1.3.6.1.2.1.10.227.1.10.1.1
lmpCcUnderlyingIfIndexIf 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.rw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.2.1.10.227.1.10.1.2
lmpCcIsIfIn 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.10.1.3
lmpCcNbrNodeIdThis 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.rw
LmpNodeId
.1.3.6.1.2.1.10.227.1.10.1.4
lmpCcRemoteIdThis 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.ro
Unsigned32
.1.3.6.1.2.1.10.227.1.10.1.5
lmpCcRemoteAddressTypeThis value represents the remote control channel IP address type. In point-to-point configuration, this value can be set to unknown(0).rw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.2.1.10.227.1.10.1.6
lmpCcRemoteIpAddrThis 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.rw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.2.1.10.227.1.10.1.7
lmpCcSetupRoleThe 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.rw
Enumeration
.1.3.6.1.2.1.10.227.1.10.1.8
lmpCcAuthenticationThis object indicates whether the control channel must use authentication.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.10.1.9
lmpCcHelloIntervalThis object specifies the value of the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.10
lmpCcHelloIntervalMinThis object specifies the minimum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMinDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.11
lmpCcHelloIntervalMaxThis object specifies the maximum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.12
lmpCcHelloIntervalNegotiatedOnce the control channel is active, this object represents the negotiated HelloInterval value.ro
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.13
lmpCcHelloDeadIntervalThis object specifies the value of the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.14
lmpCcHelloDeadIntervalMinThis object specifies the minimum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalMinDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.15
lmpCcHelloDeadIntervalMaxThis object specifies the maximum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.16
lmpCcHelloDeadIntervalNegotiatedOnce the control channel is active, this object represents the negotiated HelloDeadInterval value.ro
LmpInterval
.1.3.6.1.2.1.10.227.1.10.1.17
lmpCcLastChangeThe 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.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.2.1.10.227.1.10.1.18
lmpCcAdminStatusThe desired operational status of this control channel.rw
Enumeration
.1.3.6.1.2.1.10.227.1.10.1.19
lmpCcOperStatusThe actual operational status of this control channel.ro
Enumeration
.1.3.6.1.2.1.10.227.1.10.1.20
lmpCcRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.10.1.21
lmpCcStorageTypeThe 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.rw
StorageType (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.10.1.22
lmpControlChannelPerfTableThis table specifies LMP control channel performance counters.
SEQUENCE OF LmpControlChannelPerfEntry
.1.3.6.1.2.1.10.227.1.11
lmpControlChannelPerfEntryAn 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.
LmpControlChannelPerfEntry
.1.3.6.1.2.1.10.227.1.11.1
lmpCcInOctetsThe total number of LMP message octets received on the control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.1
lmpCcInDiscardsThe 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.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.2
lmpCcInErrorsThe number of inbound packets that contained errors preventing them from being processed by LMP.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.3
lmpCcOutOctetsThe total number of LMP message octets transmitted out of the control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.4
lmpCcOutDiscardsThe 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.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.5
lmpCcOutErrorsThe number of outbound packets that could not be transmitted because of errors.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.6
lmpCcConfigReceivedThis object counts the number of Config messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.7
lmpCcConfigSentThis object counts the number of Config messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.8
lmpCcConfigRetransmitThis object counts the number of Config messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.9
lmpCcConfigAckReceivedThis object counts the number of ConfigAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.10
lmpCcConfigAckSentThis object counts the number of ConfigAck messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.11
lmpCcConfigNackReceivedThis object counts the number of ConfigNack messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.12
lmpCcConfigNackSentThis object counts the number of ConfigNack messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.13
lmpCcHelloReceivedThis object counts the number of Hello messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.14
lmpCcHelloSentThis object counts the number of Hello messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.15
lmpCcBeginVerifyReceivedThis object counts the number of BeginVerify messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.16
lmpCcBeginVerifySentThis object counts the number of BeginVerify messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.17
lmpCcBeginVerifyRetransmitThis object counts the number of BeginVerify messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.18
lmpCcBeginVerifyAckReceivedThis object counts the number of BeginVerifyAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.19
lmpCcBeginVerifyAckSentThis object counts the number of BeginVerifyAck messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.20
lmpCcBeginVerifyNackReceivedThis object counts the number of BeginVerifyNack messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.21
lmpCcBeginVerifyNackSentThis object counts the number of BeginVerifyNack messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.22
lmpCcEndVerifyReceivedThis object counts the number of EndVerify messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.23
lmpCcEndVerifySentThis object counts the number of EndVerify messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.24
lmpCcEndVerifyRetransmitThis object counts the number of EndVerify messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.25
lmpCcEndVerifyAckReceivedThis object counts the number of EndVerifyAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.26
lmpCcEndVerifyAckSentThis object counts the number of EndVerifyAck messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.27
lmpCcTestStatusSuccessReceivedThis object counts the number of TestStatusSuccess messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.28
lmpCcTestStatusSuccessSentThis object counts the number of TestStatusSuccess messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.29
lmpCcTestStatusSuccessRetransmitThis object counts the number of TestStatusSuccess messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.30
lmpCcTestStatusFailureReceivedThis object counts the number of TestStatusFailure messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.31
lmpCcTestStatusFailureSentThis object counts the number of TestStatusFailure messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.32
lmpCcTestStatusFailureRetransmitThis object counts the number of TestStatusFailure messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.33
lmpCcTestStatusAckReceivedThis object counts the number of TestStatusAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.34
lmpCcTestStatusAckSentThis object counts the number of TestStatusAck messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.35
lmpCcLinkSummaryReceivedThis object counts the number of LinkSummary messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.36
lmpCcLinkSummarySentThis object counts the number of LinkSummary messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.37
lmpCcLinkSummaryRetransmitThis object counts the number of LinkSummary messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.38
lmpCcLinkSummaryAckReceivedThis object counts the number of LinkSummaryAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.39
lmpCcLinkSummaryAckSentThis object counts the number of LinkSummaryAck messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.40
lmpCcLinkSummaryNackReceivedThis object counts the number of LinkSummaryNack messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.41
lmpCcLinkSummaryNackSentThis object counts the number of LinkSummaryNack messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.42
lmpCcChannelStatusReceivedThis object counts the number of ChannelStatus messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.43
lmpCcChannelStatusSentThis object counts the number of ChannelStatus messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.44
lmpCcChannelStatusRetransmitThis object counts the number of ChannelStatus messages that have been retransmitted on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.45
lmpCcChannelStatusAckReceivedThis object counts the number of ChannelStatusAck messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.46
lmpCcChannelStatusAckSentThis object counts the number of ChannelStatus messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.47
lmpCcChannelStatusReqReceivedThis object counts the number of ChannelStatusRequest messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.48
lmpCcChannelStatusReqSentThis object counts the number of ChannelStatusRequest messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.49
lmpCcChannelStatusReqRetransmitThis object counts the number of ChannelStatusRequest messages that have been retransmitted on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.50
lmpCcChannelStatusRspReceivedThis object counts the number of ChannelStatusResponse messages that have been received on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.51
lmpCcChannelStatusRspSentThis object counts the number of ChannelStatusResponse messages that have been sent on this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.11.1.52
lmpCcCounterDiscontinuityTimeThe 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.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.11.1.53
lmpTeLinkTableThis 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.
SEQUENCE OF LmpTeLinkEntry
.1.3.6.1.2.1.10.227.1.12
lmpTeLinkEntryAn 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.
LmpTeLinkEntry
.1.3.6.1.2.1.10.227.1.12.1
lmpTeLinkNbrRemoteNodeIdThis 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.rw
LmpNodeId
.1.3.6.1.2.1.10.227.1.12.1.1
lmpTeLinkVerificationThis object indicates whether the LMP link verification procedure is enabled for this TE link.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.12.1.2
lmpTeLinkFaultManagementThis object indicates whether the LMP fault management procedure is enabled on this TE link.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.12.1.3
lmpTeLinkDwdmThis object indicates whether the LMP DWDM procedure is enabled on this TE link.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.12.1.4
lmpTeLinkOperStatusThe 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.ro
Enumeration
.1.3.6.1.2.1.10.227.1.12.1.5
lmpTeLinkRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.12.1.6
lmpTeLinkStorageTypeThe 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.rw
StorageType (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.12.1.7
lmpGlobalLinkVerificationIntervalThis 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.rw
Unsigned32 UNITS "milliseconds"
.1.3.6.1.2.1.10.227.1.13
lmpLinkVerificationTableThis table specifies TE link information associated with the LMP verification procedure.
SEQUENCE OF LmpLinkVerificationEntry
.1.3.6.1.2.1.10.227.1.14
lmpLinkVerificationEntryAn entry in this table is created by an LMP-enabled device for every TE link that supports the LMP verification procedure.
LmpLinkVerificationEntry
.1.3.6.1.2.1.10.227.1.14.1
lmpLinkVerifyIntervalThis object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.14.1.1
lmpLinkVerifyDeadIntervalThis 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.rw
LmpInterval
.1.3.6.1.2.1.10.227.1.14.1.2
lmpLinkVerifyTransportMechanismThis 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.rw
Bits
.1.3.6.1.2.1.10.227.1.14.1.3
lmpLinkVerifyTransmissionRateThis is the transmission rate of the data link over which the Test messages will be transmitted and is expressed in bytes per second.rw
Unsigned32 UNITS "bytes per second"
.1.3.6.1.2.1.10.227.1.14.1.5
lmpLinkVerifyWavelengthThis 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.rw
Unsigned32 UNITS "nanometers"
.1.3.6.1.2.1.10.227.1.14.1.6
lmpLinkVerifyRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.14.1.7
lmpLinkVerifyStorageTypeThe 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.rw
StorageType (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.14.1.8
lmpTeLinkPerfTableThis table specifies LMP TE link performance counters.
SEQUENCE OF LmpTeLinkPerfEntry
.1.3.6.1.2.1.10.227.1.15
lmpTeLinkPerfEntryAn 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.
LmpTeLinkPerfEntry
.1.3.6.1.2.1.10.227.1.15.1
lmpTeInOctetsThe total number of LMP message octets received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.1
lmpTeOutOctetsThe total number of LMP message octets transmitted out for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.2
lmpTeBeginVerifyReceivedThis object counts the number of BeginVerify messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.3
lmpTeBeginVerifySentThis object counts the number of BeginVerify messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.4
lmpTeBeginVerifyRetransmitThis object counts the number of BeginVerify messages that have been retransmitted for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.5
lmpTeBeginVerifyAckReceivedThis object counts the number of BeginVerifyAck messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.6
lmpTeBeginVerifyAckSentThis object counts the number of BeginVerifyAck messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.7
lmpTeBeginVerifyNackReceivedThis object counts the number of BeginVerifyNack messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.8
lmpTeBeginVerifyNackSentThis object counts the number of BeginVerifyNack messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.9
lmpTeEndVerifyReceivedThis object counts the number of EndVerify messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.10
lmpTeEndVerifySentThis object counts the number of EndVerify messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.11
lmpTeEndVerifyRetransmitThis object counts the number of EndVerify messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.12
lmpTeEndVerifyAckReceivedThis object counts the number of EndVerifyAck messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.13
lmpTeEndVerifyAckSentThis object counts the number of EndVerifyAck messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.14
lmpTeTestStatusSuccessReceivedThis object counts the number of TestStatusSuccess messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.15
lmpTeTestStatusSuccessSentThis object counts the number of TestStatusSuccess messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.16
lmpTeTestStatusSuccessRetransmitThis object counts the number of TestStatusSuccess messages that have been retransmitted for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.17
lmpTeTestStatusFailureReceivedThis object counts the number of TestStatusFailure messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.18
lmpTeTestStatusFailureSentThis object counts the number of TestStatusFailure messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.19
lmpTeTestStatusFailureRetransmitThis object counts the number of TestStatusFailure messages that have been retransmitted on this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.20
lmpTeTestStatusAckReceivedThis object counts the number of TestStatusAck messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.21
lmpTeTestStatusAckSentThis object counts the number of TestStatusAck messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.22
lmpTeLinkSummaryReceivedThis object counts the number of LinkSummary messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.23
lmpTeLinkSummarySentThis object counts the number of LinkSummary messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.24
lmpTeLinkSummaryRetransmitThis object counts the number of LinkSummary messages that have been retransmitted over this control channel.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.25
lmpTeLinkSummaryAckReceivedThis object counts the number of LinkSummaryAck messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.26
lmpTeLinkSummaryAckSentThis object counts the number of LinkSummaryAck messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.27
lmpTeLinkSummaryNackReceivedThis object counts the number of LinkSummaryNack messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.28
lmpTeLinkSummaryNackSentThis object counts the number of LinkSummaryNack messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.29
lmpTeChannelStatusReceivedThis object counts the number of ChannelStatus messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.30
lmpTeChannelStatusSentThis object counts the number of ChannelStatus messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.31
lmpTeChannelStatusRetransmitThis object counts the number of ChannelStatus messages that have been retransmitted for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.32
lmpTeChannelStatusAckReceivedThis object counts the number of ChannelStatusAck messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.33
lmpTeChannelStatusAckSentThis object counts the number of ChannelStatus messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.34
lmpTeChannelStatusReqReceivedThis object counts the number of ChannelStatusRequest messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.35
lmpTeChannelStatusReqSentThis object counts the number of ChannelStatusRequest messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.36
lmpTeChannelStatusReqRetransmitThis object counts the number of ChannelStatusRequest messages that have been retransmitted for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.37
lmpTeChannelStatusRspReceivedThis object counts the number of ChannelStatusResponse messages that have been received for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.38
lmpTeChannelStatusRspSentThis object counts the number of ChannelStatusResponse messages that have been sent for this TE link.ro
Counter32
.1.3.6.1.2.1.10.227.1.15.1.39
lmpTeCounterDiscontinuityTimeThe 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.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.15.1.40
lmpDataLinkTableThis table specifies the data-bearing links managed by the LMP.
SEQUENCE OF LmpDataLinkEntry
.1.3.6.1.2.1.10.227.1.16
lmpDataLinkEntryAn 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.
LmpDataLinkEntry
.1.3.6.1.2.1.10.227.1.16.1
lmpDataLinkTypeThis 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.ro
Enumeration
.1.3.6.1.2.1.10.227.1.16.1.1
lmpDataLinkAddressTypeThis 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).rw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.2.1.10.227.1.16.1.2
lmpDataLinkIpAddrThe 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.rw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.2.1.10.227.1.16.1.3
lmpDataLinkRemoteIpAddressThe 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.rw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.2.1.10.227.1.16.1.4
lmpDataLinkRemoteIfIdInterface identifier of the remote end point. This information is either configured manually or communicated by the remote node during the link verification procedure.rw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.2.1.10.227.1.16.1.5
lmpDataLinkEncodingTypeThe encoding type of the data-bearing link.rw
TeLinkEncodingType (TE-LINK-STD-MIB)
.1.3.6.1.2.1.10.227.1.16.1.6
lmpDataLinkActiveOperStatusThe actual operational status of this data-bearing link (active FSM).ro
Enumeration
.1.3.6.1.2.1.10.227.1.16.1.7
lmpDataLinkPassiveOperStatusThe actual operational status of this data-bearing link (passive FSM).ro
Enumeration
.1.3.6.1.2.1.10.227.1.16.1.8
lmpDataLinkRowStatusThis 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.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.16.1.9
lmpDataLinkStorageTypeThe 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.rw
StorageType (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.16.1.10
lmpDataLinkPerfTableThis table specifies the data-bearing links LMP performance counters.
SEQUENCE OF LmpDataLinkPerfEntry
.1.3.6.1.2.1.10.227.1.17
lmpDataLinkPerfEntryAn 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.
LmpDataLinkPerfEntry
.1.3.6.1.2.1.10.227.1.17.1
lmpDataLinkTestReceivedThis object counts the number of Test messages that have been received on this data-bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.1
lmpDataLinkTestSentThis object counts the number of Test messages that have been sent on this data-bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.2
lmpDataLinkActiveTestSuccessThis object counts the number of data-bearing link tests that were successful on the active side of this data- bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.3
lmpDataLinkActiveTestFailureThis object counts the number of data-bearing link tests that failed on the active side of this data-bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.4
lmpDataLinkPassiveTestSuccessThis object counts the number of data-bearing link tests that were successful on the passive side of this data- bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.5
lmpDataLinkPassiveTestFailureThis object counts the number of data-bearing link tests that failed on the passive side of this data-bearing link.ro
Counter32
.1.3.6.1.2.1.10.227.1.17.1.6
lmpDataLinkDiscontinuityTimeThe 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.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.17.1.7
lmpNotificationMaxRateThe 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.rw
Unsigned32
.1.3.6.1.2.1.10.227.1.18
lmpLinkPropertyNotificationsEnabledIf 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.19
lmpUnprotectedNotificationsEnabledIf 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.20
lmpCcUpDownNotificationsEnabledIf 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.21
lmpTeLinkNotificationsEnabledIf 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.22
lmpDataLinkNotificationsEnabledIf 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.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.2.1.10.227.1.23
lmpConformance
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.227.2
lmpCompliances
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.227.2.1
lmpModuleFullComplianceCompliance statement for agents that support the configuration and monitoring of LMP MIB.
Unknown
.1.3.6.1.2.1.10.227.2.1.1
lmpModuleReadOnlyComplianceCompliance statement for agents that support the monitoring of the LMP MIB.
Unknown
.1.3.6.1.2.1.10.227.2.1.2
lmpGroups
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.227.2.2
lmpNodeGroupCollection of objects that represent LMP node configuration.
Unknown
.1.3.6.1.2.1.10.227.2.2.1
lmpControlChannelGroupObjects that can be used to configure LMP interface.
Unknown
.1.3.6.1.2.1.10.227.2.2.2
lmpCcIsInterfaceGroupObjects that can be used to configure control channels that are interfaces.
Unknown
.1.3.6.1.2.1.10.227.2.2.3
lmpCcIsNotInterfaceGroupObjects that can be used to configure control channels that are not interfaces.
Unknown
.1.3.6.1.2.1.10.227.2.2.4
lmpLinkPropertyCorrelationGroupCollection of objects used to configure the link property correlation procedure.
Unknown
.1.3.6.1.2.1.10.227.2.2.5
lmpLinkVerificationGroupCollection of objects that represent the link verification procedure configuration.
Unknown
.1.3.6.1.2.1.10.227.2.2.6
lmpPerfGroupCollection of objects used to provide performance information about LMP interfaces and data-bearing links.
Unknown
.1.3.6.1.2.1.10.227.2.2.7
lmpTeLinkGroupObjects that can be used to configure TE links.
Unknown
.1.3.6.1.2.1.10.227.2.2.8
lmpDataLinkGroupCollection of objects that represent data-bearing link configuration.
Unknown
.1.3.6.1.2.1.10.227.2.2.9
lmpNotificationGroupSet of notifications defined in this module.
Unknown
.1.3.6.1.2.1.10.227.2.2.10
LMP-MIB - SNMP MIB Reference | MIBs Explorer