Step 4: Configuring Clients

Configuring cluster clients requires the client name, RBridge ID, and CCEP.
This task describes how to configure clients manually. For instructions on automatic client configuration, see Setting Up Cluster Client Automatic Configuration.

In the network shown in the Basic MCT configuration, Client-1 has a three-port LACP trunk (1/1/1-1/1/3), while Client-2 has a two-port static trunk (1/1/1-1/1/2) towards the MCT cluster.

To configure Client-2 on Ruckus-1 in the topology of Basic MCT configuration, enter the following steps.

  1. Enter global configuration mode. 
    RUCKUS-1# configure terminal
  2. Configure a cluster name and ID. 
    RUCKUS-1(config)# cluster SW 4000
  3. Assign a client name. 
    RUCKUS-1(config-cluster-SW)# client client-2
    The client name can be different on the different cluster devices.
  4. Configure the RBridge ID. 
    RUCKUS-1(config-cluster-SW-client-2)# rbridge-id 200
    The RBridge ID must be different from the cluster RBridge ID or the ID of any other client in the cluster.
  5. Configure the dynamic lag as the client CCEP. 
    RUCKUS-1(config-cluster-SW-client-2)# client-interface lag 6
  6. Deploy the configuration. 
    RUCKUS-1(config-cluster-SW-client-2)# deploy

The following example shows how to configure Client-2 on RUCKUS-2 in the topology of Basic MCT configuration. 

RUCKUS-2# configure terminal
RUCKUS-2(config)# cluster SW 4000
RUCKUS-2(config-cluster-SW)# client client-2
RUCKUS-2(config-cluster-SW-client-2)# rbridge-id 200
RUCKUS-2(config-cluster-SW-client-2)# client-interface lag 6
RUCKUS-2(config-cluster-SW-client-2)# deploy

The following example shows how to configure Client-1 on RUCKUS-1 in the topology of Basic MCT configuration. 

RUCKUS-1# configure terminal
RUCKUS-1(config)# cluster SW 4000
RUCKUS-1(config-cluster-SW)# client client-1
RUCKUS-1(config-cluster-SW-client-1)# rbridge-id 300
RUCKUS-1(config-cluster-SW-client-1)# client-interface lag 5
RUCKUS-1(config-cluster-SW-client-1)# deploy

The following example shows how to configure Client-1 on RUCKUS-2 in the topology of Basic MCT configuration. 

RUCKUS-2# configure terminal
RUCKUS-2(config)# cluster SW 4000
RUCKUS-2(config-cluster-SW)# client client-1
RUCKUS-2(config-cluster-SW-client-1)# rbridge-id 300
RUCKUS-2(config-cluster-SW-client-1)# client-interface lag 5
RUCKUS-2(config-cluster-SW-client-1)# deploy
Parent topic: Configuring MCT