Configuration Guide User guide

FastIron Configuration Guide 835
53-1002494-02
Multi-Chassis Trunking Overview
22
Cluster client automatic configuration
Client configuration includes setting the client name, client RBridgeID (unique identification for
each client), client interface (CCEP), and deployment settings on both MCT cluster devices. With up
to 150 clients per cluster, manual configuration can take a considerable amount of time.
Cluster client automatic configuration saves the time that would be required to complete the entire
configuration manually.
The following limitations apply to cluster client automatic configuration:
• 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 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 841 for detailed instructions on
the cluster client automatic configuration process.
MCT feature interaction
The following FastIron features are supported with MCT. Note that 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 (VLAN CPU protection, multicast flooding, and so on) on MCT VLANs.
• Unidirectional Link Detection (UDLD) as independent boxes (configured independently).
• ARP as independent boxes (configured independently).
• STP and RSTP.