Virtual Private LAN Services
7750 SR OS Services Guide Page 469
For consistency, a similar procedure is used for the BVPLS case as depicted in Figure 71.
Figure 71: MC-EP with B-VPLS Mac Flush Solution
In this example, the MC-EP activates B-VPLS PW4 because of either a link/node failure or
because of an MC-EP selection re-run that affected the previously active PW1. As a result, the
endpoint on PE3 containing PW1 goes down.
The following steps apply:
• PE3 sends in the local I-VPLS context a LDP flush-all-from-me (marked with F1) to PE A
and to the other regular VPLS PEs, including PE3’. The following command enables this
behavior on a per I-VPLS basis: configure>service>vpls ivpls>send-flush-on-bvpls-
failure .
→ Result: PEA, PE3 and the other local VPLS PEs in the metro clear the VPLS FIB
entries associated to PW to PE3.
• PE3 clears the entries associated to PW1 and sends in the B-VPLS context an LDP flush-
all-but-mine (marked with F2) towards PE2 on the active PW4.
→ Result: PE2 clears the BVPLS FIB entries not associated with PW4.
• PE2 propagates the MAC flush-all-but-mine (marked with F3) from B-VPLS in the
related I-VPLS context(s) towards all participating VPLS PEs – for example, in the blue
IVPLS to PE B, PE1. It also clears all the CMAC entries associated with IVPLS
pseudowires.
The following command enables this behavior on a per I-VPLS basis:
OSSG320
WANMetro Region
Resilient Inter-domain Handoff
VPLS
(Mesh)
VPLS
(Mesh)
PE3
F1
F3
PEA
PEB
CMAC X
CMAC Y
PE3’
PE1
PE2
MC
EP
B
B
B
B
PW1
PW4
X
-
>SAP2
Y
-
>SAP1
X
-
>PWtoA
Y
-
>PWtoB
X
-
>PWtoA
Y
-
>PWtoB