Virtual Private LAN Services
7750 SR OS Services Guide Page 467
Figure 69: MC-EP with B-VPLS
Multiple I-VPLS instances may be used to represent in the gateway PEs the customer VPLS
instances using PBB-VPLS M:1 model described in the PBB section. A backbone VPLS (B-
VPLS) is used in this example to administer the resiliency for all customer VPLS instances at the
domain borders. Just one MC-EP is required to be configured in the B-VPLS to address 100s or
even 1000s of customers VPLS instances. If load balancing is required, multiple B-VPLS
instances may be used to ensure even distribution of the customers across all the pseudowires
interconnecting the two domains. In this example, four B-VPLS will be able to loadshare the
customers across all four possible pseudowire paths.
The use of MC-EP with B-VPLS is strictly limited to cases where VPLS mesh exists on both sides
of a B-VPLS. For example, active/standby pseudowires resiliency in the I-VPLS context where
PE3, PE3’ are PErs cannot be used because there is no way to synchronize the active/standby
selection between the two domains.
For a similar reason, MC-LAG resiliency in the I-VPLS context on the gateway PEs participating
in the MC-EP (PE3, PE3) should not be used.
Note that for the PBB topology described in Figure 69, block-on-mesh-failure in the I-VPLS
domain will not have any effect on the B-VPLS MC-EP side. That is because mesh failure in one
I-VPLS should not affect other I-VPLS sharing the same B-VPLS.
To Next Page
Loading...
