Configuration Guide User guide

FastIron Configuration Guide 829
53-1002494-02
Multi-Chassis Trunking Overview
22
• Traffic received from non-ICL ports is forwarded the same way as non-MCT devices.
• Known unicast, multicast, and broadcast traffic received on Cluster Edge Ports (CEP) or ICL
ports is forwarded to the destination port.
• For unknown unicast, multicast, and broadcast traffic received on ICL ports, the forwarding
behavior depends on the peer MCT device’s ability to reach the same client.
• Unknown unicast, multicast, and broadcast traffic received from CCEP is forwarded as usual,
with the default behavior to flood the entire VLAN.
MCT terminology
• MCT cluster: A pair of devices (switches) that is clustered together using MCT to appear as a
single logical device. The devices are connected as peers through an Inter-Chassis Link (ICL).
• MCT cluster device: One of the two devices in an MCT cluster.
• MCT peer device: From the perspective of an MCT cluster device, the other device in the MCT
cluster.
• MCT cluster client: A device that connects with MCT cluster devices through static or dynamic
trunks. It can be a switch or an endpoint server host in the single-level MCT topology or another
pair of MCT devices in a multi-tier MCT topology.
• Inter-Chassis Link (ICL): A single-port or multi-port 1 GbE or 10 GbE interface between the two
MCT cluster devices. It provides the control path for CCP for the cluster and also serves as the
data path between the two devices.
• MCT VLANs: VLANs on which MCT cluster clients are operating. Any VLAN that has an ICL port
is an MCT VLAN, even though it does not have any clients.
• MCT session VLANs: The VLAN used by the MCT cluster for control operations. CCP protocol
runs over this VLAN. The interface can be a single link or a trunk group port. If it is a trunk
group port, it should be the primary port of the trunk group. The MCT session VLAN subnet is
not distributed in routing protocols using redistribute commands.
• MCT keep-alive VLAN: The VLAN that provides a backup control path in the event that ICL goes
down.
• Cluster Communication Protocol (CCP): A Brocade proprietary protocol that provides reliable,
point-to-point transport to synchronize information between MCT cluster devices. It is the
default MCT control path between the two peer devices. CCP comprises two main components:
CCP peer management and CCP client management. CCP peer management deals with
establishing, and maintaining a TCP transport session between peers, while CCP client
management provides event-based, reliable packet transport to CCP peers.
• Cluster Client Edge Port (CCEP): A physical port or trunk group interface on an MCT cluster
device that is connected to client devices.
• Cluster Edge Port (CEP): A port on an MCT cluster device that belongs to the MCT VLAN and
connects to an upstream core switch/router, but is neither a CCEP not an ICL.
• RBridgeID: RBridgeID is a value assigned to MCT cluster devices and clients to uniquely
identify them, and helps in associating the source MAC address with an MCT device.