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

602 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
• MAC Database Update Protocol ( MUDP) will synchronize all MAC entries for VLANs served
by ICL link
• Cluster ID should be same on both cluster switches
• Cluster RBridgeID should not conflict with any client RBridge ID or the peer RBridge ID
• Client RBridge ID is unique and it should be same on the cluster switches
• You can add any ports to the session VLAN (For the purpose of adding a port to a LAG), but
Brocade recommends keeping only ICL ports as tagged members for the session VLAN during
operation.
• MCT clients may support 16 members per LAG.
• An ICL interface cannot be configured as the CCEP port in any client
• CCEP ports on MCT node can be single port or LAG
• If ICL or client interfaces need to be configured as LAG interface then only the primary port of
the LAG needs to be specified in the ICL or client configuration.
• Once the cluster is deployed, only the cluster member VLANs and client isolation mode can be
modified. Other configurations are not allowed to change.
• Once the client is deployed, any configuration under client is not allowed to change.
• Clients can be added or deleted even if the cluster is deployed.
• When the cluster is undeployed all the clients in the cluster becomes inactive.
• As soon as a port is configured as an ICL port it is removed from default VLAN.
• If an ICL or CCEP is a LAG interface, the LAG has to be configured separately on each node.
Configure Active-Active MCT
The following basic steps are required to build an MCT scenerio. See “Single level MCT example” for
detailed instructions.
1. Create and deploy a LAG that will be used as ICL.
2. Create and deploy the LAGs facing the clients.
3. Enable Layer 2 switching (no route-only) either globally or on specific interfaces.
4. Create and add ports to a client/member VLAN that they will be using for communication.
a. At the (CCEP or CCP) these may be tagged or untagged into the VLAN.
b. At the ICL ports these may only be tagged into the VLAN. The ICL ports cannot be untagged
in any VLAN.
5. Create a dedicated session VLAN for the ICL interfaces for CCP communication. ICL ports will
be tagged into the session VLAN. It is recommended to use a high VLAN number that would not
be touched by data VLANs.
6. Create a virtual routing interface and associate this with the session VLAN. This will be used to
address the link between the MCT peers.
7. Configure the MCT cluster.
a. Create a cluster with any name but with a matching cluster ID as the MCT peer.
b. Configure a unique RBridge ID for this peer. The RBridge ID must be unique across all MCT
peers and CCEPs.