Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 701)

Multi-Service IronWare Switching Configuration Guide 671
53-1003036-02
MCT for VPLS
18
vpls MCT_VPLS1 101
vpls-peer 3.3.3.3 4.4.4.4 5.5.5.5 6.6.6.6
[vpls-pw-redundancy-active]
vlan 101
tagged eth 3/1
MCT for VPLS
MCT helps organizations build scalable and resilient network infrastructures. MCT is an
enhancement over the link aggregation standard, which allows multiple switches to appear as
single logical switch connecting to another switch using a standard LAG. MCT is designed to
achieve the desired active-active topology and efficient Layer 2 multipathing, while ensuring that
the network scales effectively.
You can connect a customer edge device to an MCT, such as two Brocade MLX's, and then run it
over a VPLS network. This is ideal for inter-data center connectivity, or within a campus
environment for extending across a backbone. One of the benefits of this is to simplify VM mobility
and eliminate single point of failures. For any customers looking to inter-connect multiple data
centers and offer new cloud based services, such as disaster recovery, MCT can help you achieve
that. In a metro network, MCT helps providers offer their customers enhanced end to end resiliency
for business services.
This feature supports dual-homing connectivity of CE devices to PE devices. Dual-homing enables
link level and node level redundancy for CE's connected to PE's.
Figure 183 is a typical topology with MCT end-points for VPLS.
• PE11 and PE12 are the two nodes of the MCT Cluster.
• CE12 is connected to the two MCT nodes of the cluster using a LAG. From MCT nodes point of
view, the links connected to CE12 are called CCEP end-points.
• CE11 and CE13 are single homed to PE11 and PE12 respectively. These are called the CEP
end-points.
FIGURE 183 Sample topology with MCT end-points for VPLS