Cluster Client Automatic Configuration

Client configuration includes setting the client name, client RBridge ID (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 FastIron 07.0.40 and later releases.
  • When hash collisions occur (RBridge ID collisions), 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 switches must 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.