RFC 4327
Link Management Protocol (LMP) Management Information Base (MIB)
lmpTeChannelStatusAckSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatus messages
that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 34 }
lmpTeChannelStatusReqReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusRequest messages
that have been received for this TE link."
::= { lmpTeLinkPerfEntry 35 }
lmpTeChannelStatusReqSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusRequest messages
that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 36 }
lmpTeChannelStatusReqRetransmit OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusRequest messages
that have been retransmitted for this TE link."
::= { lmpTeLinkPerfEntry 37 }
lmpTeChannelStatusRspReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusResponse messages
that have been received for this TE link."
::= { lmpTeLinkPerfEntry 38 }
lmpTeChannelStatusRspSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of ChannelStatusResponse messages
that have been sent for this TE link."
::= { lmpTeLinkPerfEntry 39 }
lmpTeCounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at which
any 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."
::= { lmpTeLinkPerfEntry 40 }
-- End of lmpTeLinkPerfTable
-- LMP Data Link Table
lmpDataLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataLinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the data-bearing links managed by the
LMP."
::= { lmpObjects 16 }
lmpDataLinkEntry OBJECT-TYPE
SYNTAX LmpDataLinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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."
INDEX { ifIndex }
::= { lmpDataLinkTable 1 }
LmpDataLinkEntry ::= SEQUENCE {
lmpDataLinkType INTEGER,
lmpDataLinkAddressType InetAddressType,
lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress,
lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataLinkEncodingType TeLinkEncodingType,
lmpDataLinkActiveOperStatus INTEGER,
lmpDataLinkPassiveOperStatus INTEGER,
lmpDataLinkRowStatus RowStatus,
lmpDataLinkStorageType StorageType
}
lmpDataLinkType OBJECT-TYPE
SYNTAX INTEGER {
port(1),
componentLink(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute specifies whether this data-bearing link is
a port or a component link. Component link are multiplex
capable, whereas ports are not multiplex capable."
REFERENCE
"Link Management Protocol, RFC 4204"
::= { lmpDataLinkEntry 1 }
lmpDataLinkAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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)."
::= { lmpDataLinkEntry 2 }
lmpDataLinkIpAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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 and the ifIndex object then identifies the
unnumbered address."
::= { lmpDataLinkEntry 3 }
lmpDataLinkRemoteIpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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 and 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."
::= { lmpDataLinkEntry 4 }
lmpDataLinkRemoteIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Interface identifier of the remote end point. This
information is either configured manually or
communicated by the remote node during the link verification
procedure."
::= { lmpDataLinkEntry 5 }
lmpDataLinkEncodingType OBJECT-TYPE
SYNTAX TeLinkEncodingType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The encoding type of the data-bearing link."
REFERENCE
"Generalized MPLS Signaling Functional Description, RFC 3471"
::= { lmpDataLinkEntry 6 }
lmpDataLinkActiveOperStatus OBJECT-TYPE
SYNTAX INTEGER {
upAlloc(1),
upFree(2),
down(3),
testing(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual operational status of this data-bearing link
(active FSM)."
REFERENCE
"Link Management Protocol, RFC 4204"
::= { lmpDataLinkEntry 7 }
lmpDataLinkPassiveOperStatus OBJECT-TYPE
SYNTAX INTEGER {
upAlloc(1),
upFree(2),
down(3),
psvTst(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The actual operational status of this data-bearing link
(passive FSM)."
REFERENCE
"Link Management Protocol, RFC 4204"
::= { lmpDataLinkEntry 8 }
lmpDataLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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."
::= { lmpDataLinkEntry 9 }
lmpDataLinkStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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."
DEFVAL { nonVolatile }
::= { lmpDataLinkEntry 10 }
-- End of lmpDataLinkTable
-- LMP Data Link Performance Table
lmpDataLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpDataLinkPerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies the data-bearing links LMP performance
counters."
::= { lmpObjects 17 }
lmpDataLinkPerfEntry OBJECT-TYPE
SYNTAX LmpDataLinkPerfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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."
INDEX { ifIndex }
::= { lmpDataLinkPerfTable 1 }
LmpDataLinkPerfEntry ::= SEQUENCE {
lmpDataLinkTestReceived Counter32,
lmpDataLinkTestSent Counter32,
lmpDataLinkActiveTestSuccess Counter32,
lmpDataLinkActiveTestFailure Counter32,
lmpDataLinkPassiveTestSuccess Counter32,
lmpDataLinkPassiveTestFailure Counter32,
lmpDataLinkDiscontinuityTime TimeStamp
}
lmpDataLinkTestReceived OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of Test messages that have
been received on this data-bearing link."
::= { lmpDataLinkPerfEntry 1 }
lmpDataLinkTestSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of Test messages that have
been sent on this data-bearing link."
::= { lmpDataLinkPerfEntry 2 }
lmpDataLinkActiveTestSuccess OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link tests
that were successful on the active side of this data-
bearing link."
::= { lmpDataLinkPerfEntry 3 }
lmpDataLinkActiveTestFailure OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link tests
that failed on the active side of this data-bearing link."
::= { lmpDataLinkPerfEntry 4 }
lmpDataLinkPassiveTestSuccess OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link tests
that were successful on the passive side of this data-
bearing link."
::= { lmpDataLinkPerfEntry 5 }
lmpDataLinkPassiveTestFailure OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object counts the number of data-bearing link tests
that failed on the passive side of this data-bearing link."
::= { lmpDataLinkPerfEntry 6 }
lmpDataLinkDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at which
any 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."
::= { lmpDataLinkPerfEntry 7 }
-- End of lmpDataLinkPerfTable
-- Notification Configuration
lmpNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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 designing this MIB, care has been taken to minimize the
amount of notifications generated for LMP purposes. Wherever
possible, notifications are state driven, meaning the
notifications are sent only when the system changes state.
The only notifications that are repeated and 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 with 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 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."
::= { lmpObjects 18 }
lmpLinkPropertyNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, 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."
DEFVAL { false }
::= { lmpObjects 19 }
lmpUnprotectedNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, 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."
DEFVAL { false }
::= { lmpObjects 20 }
lmpCcUpDownNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, 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."
DEFVAL { false }
::= { lmpObjects 21 }
lmpTeLinkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, 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."
DEFVAL { false }
::= { lmpObjects 22 }
lmpDataLinkNotificationsEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If this object is true, 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."
DEFVAL { false }
::= { lmpObjects 23 }
-- Notifications
-- Link Property Mismatch Notifications
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { teLinkRemoteIpAddr,
teLinkIncomingIfId }
STATUS current
DESCRIPTION
"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. 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)."
::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId }
STATUS current
DESCRIPTION
"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. 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)."
::= { lmpNotifications 2 }
-- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId }
STATUS current
DESCRIPTION
"This notification is generated when there are more than one
control channels 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."
::= { lmpNotifications 3 }
-- Control Channel Notifications
lmpControlChannelUp NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current
DESCRIPTION
"This notification is generated when a control
channel transitions to the up operational state. This
notification should not be sent unless
lmpCcUpDownNotificationsEnabled is true."
::= { lmpNotifications 4 }
lmpControlChannelDown NOTIFICATION-TYPE
OBJECTS { lmpCcAdminStatus, lmpCcOperStatus }
STATUS current
DESCRIPTION
"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."
::= { lmpNotifications 5 }
-- TE Link Notification
lmpTeLinkDegraded NOTIFICATION-TYPE
OBJECTS { lmpTeLinkOperStatus }
STATUS current
DESCRIPTION
"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."
::= { lmpNotifications 6 }
lmpTeLinkNotDegraded NOTIFICATION-TYPE
OBJECTS { lmpTeLinkOperStatus }
STATUS current
DESCRIPTION
"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."
::= { lmpNotifications 7 }
-- Data-bearing Link Notification
lmpDataLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus }
STATUS current
DESCRIPTION
"This notification is generated when a data-bearing
link verification fails. This notification should not be sent
unless lmpDataLinkNotificationsEnabled is true. For a given
data link, this notification can occur no more than once per
verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 8 }
-- End of notifications
-- Module compliance
lmpCompliances
OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpGroups
OBJECT IDENTIFIER ::= { lmpConformance 2 }
lmpModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that support the
configuration and monitoring of LMP MIB."
MODULE -- this module
MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup,
lmpPerfGroup,
lmpTeLinkGroup,
lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION
"This group is mandatory for devices that support
control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)."
GROUP lmpCcIsInterfaceGroup
DESCRIPTION
"This group is mandatory for devices that support
control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup
DESCRIPTION
"This group is mandatory for devices that support
the link verification procedure."
GROUP lmpNotificationGroup
DESCRIPTION
"This group is optional."
-- lmpNbrTable
OBJECT lmpNbrRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION
"Support for notReady(3) and createAndWait(5) is
not required."
-- lmpControlChannelTable
OBJECT lmpCcRemoteAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be
supported for non-point-to-point configurations."
OBJECT lmpCcRemoteIpAddr
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION
"The size of the IP address depends on the address type."
OBJECT lmpCcRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION
"Support for notReady(3) and createAndWait(5) is
not required."
OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION
"A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported."
-- lmpTeLinkTable
OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION
"The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION
"Support for notReady(3) and createAndWait(5) is
not required."
-- lmpDataLinkTable
OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION
"A value of testing(4) need not be supported."
OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION
"A value of psvTst(4) need not be supported."
OBJECT lmpDataLinkRowStatus
SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) }
DESCRIPTION
"Support for notReady(3) and createAndWait(5) is
not required."
::= { lmpCompliances 1 }
lmpModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that support the
monitoring of the LMP MIB."
MODULE -- this module
-- The mandatory groups have to be implemented
-- by all LMP-enabled devices. However, they may all be supported
-- as read-only objects in the case where manual
-- configuration is not supported.
MANDATORY-GROUPS { lmpNodeGroup,
lmpControlChannelGroup,
lmpLinkPropertyCorrelationGroup,
lmpPerfGroup,
lmpTeLinkGroup,
lmpDataLinkGroup }
GROUP lmpCcIsNotInterfaceGroup
DESCRIPTION
"This group is mandatory for devices that support
control channels that are not interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning false(1)."
GROUP lmpCcIsInterfaceGroup
DESCRIPTION
"This group is mandatory for devices that support
control channels that are interfaces, in addition to
lmpControlChannelGroup. The following constraints apply:
lmpCcIsIf must at least be read-only returning true(2)."
GROUP lmpLinkVerificationGroup
DESCRIPTION
"This group is mandatory for devices that support
the link verification procedure."
GROUP lmpNotificationGroup
DESCRIPTION
"This group is optional."
-- Scalars
OBJECT lmpAdminStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpGlobalLinkVerificationInterval
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalDefault
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalDefaultMin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalDefaultMax
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloDeadIntervalDefault
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloDeadIntervalDefaultMin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloDeadIntervalDefaultMax
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpNotificationMaxRate
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpNbrTable
OBJECT lmpNbrRetransmitInterval
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpNbrRetryLimit
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpNbrRetransmitDelta
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpNbrRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active(1) is the
only status that needs to be supported."
OBJECT lmpNbrStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpControlChannelTable
OBJECT lmpCcUnderlyingIfIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcIsIf
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcNbrNodeId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcRemoteAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be
supported for non-point-to-point configurations."
OBJECT lmpCcRemoteIpAddr
SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only
DESCRIPTION
"The size of the IP address depends on the address type."
OBJECT lmpCcSetupRole
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcAuthentication
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalMin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalMax
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloDeadIntervalMin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloDeadIntervalMax
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active(1) is the
only status that needs to be supported."
OBJECT lmpCcOperStatus
SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION
"A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported."
OBJECT lmpCcStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpLinkVerificationTable
OBJECT lmpLinkVerifyInterval
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpLinkVerifyDeadInterval
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpLinkVerifyAllLinks
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpTeLinkTable
OBJECT lmpTeLinkNbrRemoteNodeId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the link verification
procedure is enabled."
OBJECT lmpTeLinkVerification
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpTeLinkFaultManagement
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpTeLinkDwdm
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpTeLinkOperStatus
SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION
"The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active(1) is the
only status that needs to be supported."
OBJECT lmpTeLinkStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpTeLinkVerificationTable
OBJECT lmpLinkVerifyTransmissionRate
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpLinkVerifyWavelength
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpLinkVerifyRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active(1) is the
only status that needs to be supported."
OBJECT lmpLinkVerifyStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- lmpDataLinkTable
OBJECT lmpDataLinkAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only
DESCRIPTION
"Only ipv4(1) and ipv6(2) address types need to be
supported for numbered links. For unnumbered links, the
unknown(0) address type needs to be supported."
OBJECT lmpDataLinkIpAddr
SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only
DESCRIPTION
"Size of data-bearing link IP address depends on type
of data-bearing link. Data-bearing link IP address size
is zero if link is unnumbered, four if link IP address is
IPv4, and sixteen if link IP address is IPv6."
OBJECT lmpDataLinkRemoteIpAddress
SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the link verification
procedure is enabled."
OBJECT lmpDataLinkRemoteIfId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required if the link verification
procedure is enabled."
OBJECT lmpDataLinkEncodingType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpDataLinkActiveOperStatus
SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION
"A value of testing(4) need not be supported."
OBJECT lmpDataLinkPassiveOperStatus
SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) }
DESCRIPTION
"A value of psvTst(4) need not be supported."
OBJECT lmpDataLinkRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and active(1) is the
only status that needs to be supported."
OBJECT lmpDataLinkStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { lmpCompliances 2 }
-- Units of conformance
lmpNodeGroup OBJECT-GROUP
OBJECTS { lmpAdminStatus,
lmpOperStatus,
lmpNbrAdminStatus,
lmpNbrOperStatus,
lmpNbrRowStatus,
lmpNbrStorageType,
lmpUnprotectedNotificationsEnabled,
lmpNotificationMaxRate
}
STATUS current
DESCRIPTION
"Collection of objects that represent LMP node
configuration."
::= { lmpGroups 1 }
lmpControlChannelGroup OBJECT-GROUP
OBJECTS {
lmpNbrRetransmitInterval,
lmpNbrRetryLimit,
lmpNbrRetransmitDelta,
lmpNbrAdminStatus,
lmpNbrOperStatus,
lmpNbrRowStatus,
lmpNbrStorageType,
lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId,
lmpCcRemoteId,
lmpCcRemoteAddressType,
lmpCcRemoteIpAddr,
lmpCcSetupRole,
lmpCcAuthentication,
lmpCcHelloInterval,
lmpCcHelloIntervalMin,
lmpCcHelloIntervalMax,
lmpCcHelloIntervalNegotiated,
lmpCcHelloDeadInterval,
lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus,
lmpCcRowStatus,
lmpCcStorageType,
lmpCcUpDownNotificationsEnabled
}
STATUS current
DESCRIPTION
"Objects that can be used to configure LMP interface."
::= { lmpGroups 2 }
lmpCcIsInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcIsIf }
STATUS current
DESCRIPTION
"Objects that can be used to configure control channels
that are interfaces."
::= { lmpGroups 3 }
lmpCcIsNotInterfaceGroup OBJECT-GROUP
OBJECTS { lmpCcUnderlyingIfIndex,
lmpCcIsIf,
lmpCcLastChange,
lmpCcAdminStatus
}
STATUS current
DESCRIPTION
"Objects that can be used to configure control channels
that are not interfaces."
::= { lmpGroups 4 }
lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyNotificationsEnabled }
STATUS current
DESCRIPTION
"Collection of objects used to configure the link
property correlation procedure."
::= { lmpGroups 5 }
lmpLinkVerificationGroup OBJECT-GROUP
OBJECTS { lmpGlobalLinkVerificationInterval,
lmpLinkVerifyInterval,
lmpLinkVerifyDeadInterval,
lmpLinkVerifyTransportMechanism,
lmpLinkVerifyAllLinks,
lmpLinkVerifyTransmissionRate,
lmpLinkVerifyWavelength,
lmpLinkVerifyRowStatus,
lmpLinkVerifyStorageType,
lmpDataLinkNotificationsEnabled
}
STATUS current
DESCRIPTION
"Collection of objects that represent the link
verification procedure configuration."
::= { lmpGroups 6 }
lmpPerfGroup OBJECT-GROUP
OBJECTS { lmpCcInOctets,
lmpCcInDiscards,
lmpCcInErrors,
lmpCcOutOctets,
lmpCcOutDiscards,
lmpCcOutErrors,
lmpCcConfigReceived,
lmpCcConfigSent,
lmpCcConfigRetransmit,
lmpCcConfigAckReceived,
lmpCcConfigAckSent,
lmpCcConfigNackSent,
lmpCcConfigNackReceived,
lmpCcHelloReceived,
lmpCcHelloSent,
lmpCcBeginVerifyReceived,
lmpCcBeginVerifySent,
lmpCcBeginVerifyRetransmit,
lmpCcBeginVerifyAckReceived,
lmpCcBeginVerifyAckSent,
lmpCcBeginVerifyNackReceived,
lmpCcBeginVerifyNackSent,
lmpCcEndVerifyReceived,
lmpCcEndVerifySent,
lmpCcEndVerifyRetransmit,
lmpCcEndVerifyAckReceived,
lmpCcEndVerifyAckSent,
lmpCcTestStatusSuccessReceived,
lmpCcTestStatusSuccessSent,
lmpCcTestStatusSuccessRetransmit,
lmpCcTestStatusFailureReceived,
lmpCcTestStatusFailureSent,
lmpCcTestStatusFailureRetransmit,
lmpCcTestStatusAckReceived,
lmpCcTestStatusAckSent,
lmpCcLinkSummaryReceived,
lmpCcLinkSummarySent,
lmpCcLinkSummaryRetransmit,
lmpCcLinkSummaryAckReceived,
lmpCcLinkSummaryAckSent,
lmpCcLinkSummaryNackReceived,
lmpCcLinkSummaryNackSent,
lmpCcChannelStatusReceived,
lmpCcChannelStatusSent,
lmpCcChannelStatusRetransmit,
lmpCcChannelStatusAckReceived,
lmpCcChannelStatusAckSent,
lmpCcChannelStatusReqReceived,
lmpCcChannelStatusReqSent,
lmpCcChannelStatusReqRetransmit,
lmpCcChannelStatusRspReceived,
lmpCcChannelStatusRspSent,
lmpCcCounterDiscontinuityTime,
lmpTeInOctets,
lmpTeOutOctets,
lmpTeBeginVerifyReceived,
lmpTeBeginVerifySent,
lmpTeBeginVerifyRetransmit,
lmpTeBeginVerifyAckReceived,
lmpTeBeginVerifyAckSent,
lmpTeBeginVerifyNackReceived,
lmpTeBeginVerifyNackSent,
lmpTeEndVerifyReceived,
lmpTeEndVerifySent,
lmpTeEndVerifyRetransmit,
lmpTeEndVerifyAckReceived,
lmpTeEndVerifyAckSent,
lmpTeTestStatusSuccessReceived,
lmpTeTestStatusSuccessSent,
lmpTeTestStatusSuccessRetransmit,
lmpTeTestStatusFailureReceived,
lmpTeTestStatusFailureSent,
lmpTeTestStatusFailureRetransmit,
lmpTeTestStatusAckReceived,
lmpTeTestStatusAckSent,
lmpTeLinkSummaryReceived,
lmpTeLinkSummarySent,
lmpTeLinkSummaryRetransmit,
lmpTeLinkSummaryAckReceived,
lmpTeLinkSummaryAckSent,
lmpTeLinkSummaryNackReceived,
lmpTeLinkSummaryNackSent,
lmpTeChannelStatusReceived,
lmpTeChannelStatusSent,
lmpTeChannelStatusRetransmit,
lmpTeChannelStatusAckReceived,
lmpTeChannelStatusAckSent,
lmpTeChannelStatusReqReceived,
lmpTeChannelStatusReqSent,
lmpTeChannelStatusReqRetransmit,
lmpTeChannelStatusRspSent,
lmpTeChannelStatusRspReceived,
lmpTeCounterDiscontinuityTime,
lmpDataLinkTestReceived,
lmpDataLinkTestSent,
lmpDataLinkActiveTestSuccess,
lmpDataLinkActiveTestFailure,
lmpDataLinkPassiveTestSuccess,
lmpDataLinkPassiveTestFailure,
lmpDataLinkDiscontinuityTime
}
STATUS current
DESCRIPTION
"Collection of objects used to provide performance
information about LMP interfaces and data-bearing links."
::= { lmpGroups 7 }
lmpTeLinkGroup OBJECT-GROUP
OBJECTS { lmpTeLinkNbrRemoteNodeId,
lmpTeLinkVerification,
lmpTeLinkFaultManagement,
lmpTeLinkDwdm,
lmpTeLinkOperStatus,
lmpTeLinkRowStatus,
lmpTeLinkStorageType,
lmpTeLinkNotificationsEnabled
}
STATUS current
DESCRIPTION
"Objects that can be used to configure TE links."
::= { lmpGroups 8 }
lmpDataLinkGroup OBJECT-GROUP
OBJECTS { lmpDataLinkType,
lmpDataLinkAddressType,
lmpDataLinkIpAddr,
lmpDataLinkRemoteIpAddress,
lmpDataLinkRemoteIfId,
lmpDataLinkEncodingType,
lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus,
lmpDataLinkRowStatus,
lmpDataLinkStorageType
}
STATUS current
DESCRIPTION
"Collection of objects that represent data-bearing link
configuration."
::= { lmpGroups 9 }
lmpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { lmpTeLinkPropertyMismatch,
lmpDataLinkPropertyMismatch,
lmpUnprotected,
lmpControlChannelUp,
lmpControlChannelDown,
lmpTeLinkDegraded,
lmpTeLinkNotDegraded,
lmpDataLinkVerificationFailure }
STATUS current
DESCRIPTION
"Set of notifications defined in this module."
::= { lmpGroups 10 }
-- End of LMP-MIB
END
10. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
- Unauthorized changes to the lmpNbrTable, lmpControlChannelTable,
lmpTeLinkTable, and lmpDataLinkTable may disrupt allocation of
resources in the network.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
- The lmpNbrTable exposes network provider's node IP addresses.
- lmpControlChannelTable exposes network provider's control
network.
- lmpDataLinkTable exposes network provider's data network.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.11. Contributors
Sudheer Dharanikota EMail: sudheer@ieee.org12. Acknowledgements
The general structure of this document has been modeled around the MPLS Label Switching Router (LSR) MIB [RFC3813]. The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and George Wang.13. IANA Considerations
Each of the following "IANA Considerations" subsections requested IANA for new assignments. New assignments can only be made via a Standards Action as specified in [RFC2434].13.1. IANA Considerations for lmp ifType
The IANA has assigned 227 ifType for LMP interfaces.13.2. IANA Considerations for LMP-MIB
The IANA has assigned { transmission 227 } to the LMP-MIB module specified in this document.
14. References
14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC 2914, September 2000. [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204, October 2005. [RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages", RFC 4207, October 2005.
[RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems", RFC 4209, October 2005. [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering Link Management Information Base", RFC 4220, November 2005.14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004.
Authors' Addresses
Martin Dubuc EMail: dubuc.consulting@sympatico.ca Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719 EMail: tnadeau@cisco.com Jonathan P. Lang Sonos, Inc. 223 E. De La Guerra St. Santa Barbara, CA 93101 EMail: jplang@ieee.org Evan McGinnis Hammerhead Systems 640 Clyde Court Mountain View, CA 94043 EMail: emcginnis@hammerheadsystems.com
Full Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).