Brocade FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide - Manual (Page 158)

Broadcast, unknown unicast, and multicast (BUM) traffic from a client through a CCEP
1. Traffic originates at the client.
2. Because the link between the client switch and the MCT cluster is a trunk, the traffic travels over
one physical link. In the example shown in the following figure, the traffic travels over the link toward
cluster device 2. The traffic enters the MCT cluster through the CCEP of cluster device 2.
3. The traffic is sent to any local CEPs and CCEPs. It passes to the peer cluster device over the ICL
link, where it is sent to the peer device’s local CEPs.
4. Traffic does not pass back down to the client through the CCEP.
FIGURE 26 MCT data flow - BUM traffic from CCEP
Unicast traffic from a client through a CCEP to a CEP
1. Traffic originates at the client.
2. Because the link between the client switch and the MCT cluster is a trunk, the traffic travels over
one physical link. As shown in the following figure, the traffic travels over the link toward cluster
device 2. The traffic enters the MCT cluster through the CCEP of cluster device 2.
3. Depending on the destination, the traffic may pass over the ICL link to the other cluster device. In
the following figure, the destination is on cluster device 1, so the traffic is forwarded out to the ICL
port.
4. The traffic passes out to the destination.
Multi-Chassis Trunking
158 FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide
53-1003086-04