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'.
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).
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).
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).
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).
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).
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).
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).
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).