Step 4: Configuring Clients
In the network shown in the Basic MCT configuration, Client-201 has a three-port LACP LAG (1/1/1-1/1/3), while Client-202 has a two-port LACP LAG (1/1/1-1/1/2) towards the MCT cluster.
To configure Client-202 on RUCKUS-1 in the topology of Basic MCT configuration, enter the following steps.
- Enter global configuration mode.
- Configure a cluster name and ID.
- Assign a client name. The client name can be different on the different cluster devices.
- Configure the RBridge ID. The RBridge ID must be different from the cluster RBridge ID or the ID of any other client in the cluster.
- Configure the dynamic LAG as the client CCEP.
- Deploy the configuration.
The following example shows how to configure Client-202 on RUCKUS-2 in the topology of Basic MCT configuration.
RUCKUS-2# configure terminal RUCKUS-2(config)# cluster Building-A 200 RUCKUS-2(config-cluster-Building-A)# client client-202 RUCKUS-2(config-cluster-Building-A-client-202)# rbridge-id 202 RUCKUS-2(config-cluster-Building-A-client-202)# client-interface lag 6 RUCKUS-2(config-cluster-Building-A-client-202)# deploy
The following example shows how to configure Client-201 on RUCKUS-1 in the topology of Basic MCT configuration.
RUCKUS-1# configure terminal RUCKUS-1(config)# cluster Building-A 200 RUCKUS-1(config-cluster-Building-A)# client client-201 RUCKUS-1(config-cluster-Building-A-client-201)# rbridge-id 201 RUCKUS-1(config-cluster-Building-A-client-201)# client-interface lag 5 RUCKUS-1(config-cluster-Building-A-client-201)# deploy
The following example shows how to configure Client-201 on RUCKUS-2 in the topology of Basic MCT configuration.
RUCKUS-2# configure terminal RUCKUS-2(config)# cluster Building-A 200 RUCKUS-2(config-cluster-Building-A)# client client-201 RUCKUS-2(config-cluster-Building-A-client-201)# rbridge-id 201 RUCKUS-2(config-cluster-Building-A-client-201)# client-interface lag 5 RUCKUS-2(config-cluster-Building-A-client-201)# deploy