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

• Cluster client automatic configuration is designed for generating new clients, not for updating an
existing client.
• A single client span across multiple devices is not supported (cascading MCT). For example, the
configuration of cascading MCT through cluster client automatic configuration is not supported.
• Multiple clients on the same device are not supported.
• LACP client interface auto-detection is supported only for devices running release 7.4 software and
later on FastIron platforms.
• RBridgeID collision: When hash collisions occur, cluster client automatic configuration reports errors,
and manual intervention is required.
For cluster client automatic configuration to work, the following prerequisites are required on the cluster
side:
• The cluster must be configured on both MCT cluster devices.
• An MCT VLAN must be configured on both MCT cluster devices.
• The trunk group configuration must be removed from the client interfaces.
• The client interfaces must be up and operational.
• The cluster ID must be unique when there are multiple clusters interconnected in a topology. For
example, in a cascaded Stage 2 MCT cluster, the cluster ID on a stage 1 pair of switch should be
different from the cluster ID on a stage 2 pair of switches.
The following prerequisites are required on the client side:
• VLAN and trunk group configuration must be completed.
• Link Level Discovery Protocol (LLDP) must be enabled.
Refer to Setting up cluster client automatic configuration on page 169 for detailed instructions on the
cluster client automatic configuration process.
MCT feature interaction
The following FastIron features are supported with MCT. All security features are locally significant and
are not synchronized across an MCT cluster.
• LACP on the CCEP.
• VRRP on the CCEP.
• MRP and MRP II, with the restriction that the ICL port cannot be the secondary port of the MRP ring.
• Flooding features (such as VLAN CPU protection and multicast flooding) on MCT VLANs.
• Unidirectional Link Detection (UDLD) as independent boxes (configured independently).
• ARP as independent boxes (configured independently).
• STP and RSTP.
• Ingress ACLs on all MCT ports. Egress ACLs are supported only on MCT CEPs or ICL ports. Egress
ACLs are not supported on MCT CCEPs.
• QoS and MAC filters and profiles with the same configuration on both cluster devices.
• IPv4 ACLs and rate limits. If the rules are applied on the CCEPs, the same rules must be applied to
the CCEP ports on both cluster devices.
• Layer 3 Routing. VE with IP address assignment is supported on CCEPs for VRRP. However, routing
protocols are not enabled on CCEPs.
• Static multi-port MAC.
• Port MAC security, multi-port authentication, and 802.1X, only on CEPs.
• Static MAC address configuration. Static MAC addresses are programmed on both local and remote
peers as static entries.
• DAI and DHCP snooping for clients connected through CEPs. They must be configured
independently on both cluster devices.
MCT feature interaction
FastIron Ethernet Switch Platform and Layer 2 Switching Configuration Guide 163
53-1003086-04