Page 470 7750 SR OS Services Guide
configure>service>vpls ivpls>propagate-mac-flush-from-bvpls
→ Result: PE B, PE1 and the other local VPLS PEs in the WAN clear the VPLS FIB
entries associated to PW to PE2.
→ This command does not control though the propagation in the related IVPLS of the
BVPLS LDP MAC flush containing a PBB TLV (BMAC and ISID –list).
• Similar to regular VPLS, LDP signaling of the MAC flush will follow the active topology:
for example, no MAC flush will be generated on standby PWs.
Other failure scenarios are addressed using the same or a subset of the above steps:
• If the pseudowire (PW2) in the same endpoint with PW1 becomes active instead of PW4,
there will be no MAC flush of F1 type.
• If the pseudowire (PW3) in the same endpoint becomes active instead of PW4, the same
procedure applies.
Note that for an SC/MC endpoint configured in a BVPLS, failure/de-activation of the active
pseudowire member always generates a local MAC flush of all the BMAC associated with the
pseudowire. It never generates a MAC move to the newly active pseudowire even if the endpoint
stays up. That is because in SC-EP/MC-EP topology, the remote PE might be the terminating PBB
PE and may not be able to reach the BMAC of the other remote PE. In other words, connectivity
between them exists only over the regular VPLS Mesh.
For the same reasons, it is recommended that static BMAC not be used on SC/MC endpoints.
To Next Page
Loading...
