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

Multi-Service IronWare Switching Configuration Guide 595
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
• MCT VLANs: VLANs on which MCT clients are operating. These VLANs are explicitly configured
in the MCT configuration by the user. NOTE: For MCT VLANs, MAC learning is disabled on ICL
ports, while MAC learning is enabled on ICL port for non-MCT VLANs.
• MCT Session VLANs: The VLAN used by the cluster for control operations. CCP protocol runs
over this VLAN. The interface can be a single link or LAG port. If it is LAG port, it should be the
primary port of the LAG. Note: MCT session VLAN's subnet will not be distributed in routing
protocols using redistribute commands
• RBridge ID: RBridge ID is a value assigned to MCT nodes and clients to uniquely identify them,
and helps in associating Source MAC with a MCT node.
• MDUP: MAC Database Update Protocol
• CL: Cluster Local MACs
• CCL: Cluster Client Local MACs
• CR: Cluster Remote MACs
• CCR: Cluster Client Remote MACs
• CCRR: Cluster Client RBridge Reachability
• MDB: MAC Database. The MDB can have multiple MAC entries for the same address
• FDB: Forwarding MAC Database. The FDM will have the best MAC only installed
Dynamic LAGs
MCT Client creates a single dynamic LAG towards the MCT nodes. For MCT nodes the dynamic Lag
consists of two LAGs, each is configured on one of the MCT devices. A dynamic LAG runs Link
Aggregation Control Protocol (LACP).
For the two dynamic LAGs of the MCT to behave as a single LAG from the MCT client’s perspective,
both of the dynamic LAGs should have the same LACP system ID and key, referred to as the MCT
system ID and MCT key.
The MCT system ID and MCT key is uniquely defined for one MCT. They have the following
attributes:
• MCT base system id = 0180.c200.0000
• MCT system id = MCT base system ID + cluster ID
• The cluster ID is user configurable on each MCT peer and unique across the MCT system
• MCT base key = 30000
• MCT LAG Group ID = MCT base key + client bridge ID
NOTE
Each MCT node has a unique cluster ID, and one MCT client ID.