Session Parameters Commands
7450 ESS MPLS Guide Page 675
pe-id-mac-flush-interop
Syntax [no] pe-id-mac-flush-interop
Context config>router>ldp>session-parameters>peer
Description This command enables the addition of the PE-ID TLV in the LDP MAC withdrawal (mac-flush)
message, under certain conditions, and modifies the mac-flush behavior for interoperability with
other vendors that do not support the flush-all-from-me vendor-specific TLV. This flag can be enabled
on a per LDP peer basis and allows the flush-all-from-me interoperability with other vendors. When
the pe-id-mac-flush-interop flag is enabled for a given peer, the current mac-flush behavior is
modified in terms of mac-flush generation, mac-flush propagation and behavior upon receiving a
mac-flush.
The mac-flush generation will be changed depending on the type of event and according to the
following rules:
• Any all-from-me mac-flush event will trigger a mac-flush all-but-mine message
(RFC 4762 compliant format) with the addition of a PE-ID TLV. The PE-ID TLV
contains the IP address of the sending PE.
• Any all-but-mine mac-flush event will trigger a mac-flush all-but-mine message
WITHOUT the addition of the PE-ID TLV, as long as the source spoke-sdp is not
part of an end-point.
• Any all-but-mine mac-flush event will trigger a mac-flush all-but-mine message
WITH the addition of the PE-ID TLV, if the source spoke-sdp is part of an end-point
and the spoke-sdp goes from down/standby state to active state. In this case, the PE-
ID TLV will contain the IP address of the PE to which the previous active spoke-sdp
was connected to.
Any other case will follow the existing mac-flush procedures.
When the pe-id-mac-flush-interop flag is enabled for a given LDP peer, the mac-flush ingress
processing is modified according to the following rules:
• Any received all-from-me mac-flush will follow the existing mac-flush all-from-me
rules regardless of the existence of the PE-ID.
• Any received all-but-mine mac-flush will take into account the received PE-ID, i.e.
all the mac addresses associated to the PE-ID will be flushed. If the PE-ID is not
included, the mac addresses associated to the sending PE will be flushed.
• Any other case will follow the existing mac-flush procedures.
When a mac-flush message has to be propagated (for an ingress sdp-binding to an egress sdp-binding)
and the pe-id-mac-flush-interop flag is enabled for the ingress and egress TLDP peers, the following
behavior is observed:
• If the ingress and egress bindings are spoke-sdp, the PE will propagate the mac-
flush message with its own PE-ID.
To Next Page
Loading...
