MCT configuration considerations
- Configuring flow-based MAC address learning and MCT on the same device is not supported.
- When running STP, the STP state must be the same on both cluster devices. For additional information on running STP with MCT, refer to MCT Layer 2 Protocols and to related configuration examples.
- Management VLAN configuration is not supported on MCT cluster devices running a switch image. MCT is not supported on switches with the management VLAN enabled.
- One ICL can be configured per device, and a device can be in only one cluster.
- The software version in both cluster devices must be exactly the same for the cluster to function.
- An ICL port must not be an untagged member of any VLAN.
- It is recommended that you set up ICL as a static LAG with at least two ports. This provides port-level redundancy and higher bandwidth for cluster communication.
- ICL ports must be part of MCT VLANs and session VLANs.
- An ICL cannot be a regular port link or an LACP trunk. It must be a single or multiple port static LAG.
- MAC learning is disabled on ICL ports for all VLANs.
- MDUP synchronizes all MAC entries for VLANs served by an ICL link.
- In any MCT configuration, there are two different cluster-related IDs, the Cluster ID and the Cluster RBridge ID. The Cluster ID uniquely identifies a cluster. All cluster devices in the same MCT cluster have the same Cluster ID. The Cluster RBridge ID uniquely identifies a cluster device within the cluster. To avoid conflicts, ensure that the Cluster ID and the Cluster RBridge ID are unique within an MCT configuration and cannot be confused with each other.
- The cluster ID must be the same on both cluster devices.
- The Cluster RBridge ID must not conflict with any Client RBridge ID or with the peer RBridge ID.
- The Client RBridge ID is unique and must be the same on cluster devices.
- RUCKUS recommends keeping only ICL ports in the session VLAN during operation.
- MCT supports all the ports configured in a LAG. The maximum number of ports supported per LAG is 16 on all ICX devices, except ICX 7150 which supports a maximum of 8 ports per LAG.
- An ICL interface cannot be configured as the CCEP in any client.
- BPDU guard and root guard configurations must be identical on both cluster devices.
- RUCKUS recommends that you configure a keep-alive VLAN as a separate link (not ICL). The keep-alive VLAN provides a backup control path when CCP goes down.