Setting Up Cluster Client Automatic Configuration

Need to add CLI examples ot the steps in this procedure

Complete the following steps to configure cluster client automatic configuration.

  1. Configure and deploy the MCT cluster.
    Refer to Configuring MCT.
  2. Enable an LLDP on MCT cluster and client devices. 
    RUCKUS-1(config-cluster-SW)# lldp run
RUCKUS-1(config-cluster-SW)# lldp enable ports ethernet 1/1/1 to 1/1/3
  3. After you make sure the cluster has been correctly deployed and it is in up state, enable the client auto-detect ports on both MCT devices. 
    RUCKUS-1(config-cluster-SW)# client-auto-detect ethernet 1/1/1 to 1/1/3
    In the port list, specify all the CCEPs for all potential clients.
  4. Start the client auto-detect process on both cluster devices.
    Per Orlando — Add the confirmation message seen in CLI when running this command:

    RUCKUS-1(config-cluster-SW)#client-auto-detect start

    CLUSTER AUTOCONFIG INFO - Cluster 4000 client auto-config process started

    RUCKUS-1(config-cluster-SW)# client-auto-detect start
CLUSTER AUTOCONFIG INFO - Cluster 4000 client auto-config process started
    Within one minute, the system reports information and errors (if there are mismatches such as an LACP configuration mismatch). You can fix the mismatch while the process is running.
  5. Use the show cluster <cluster-name> client-auto-detect command to verify the auto-detected client information including the auto-assigned client rbridge ID and the client interface through which it was discovered.
    RUCKUS-1(config-cluster-SW)# show cluster cluster-SW client-auto-detect 

cluster cluster-SW 4000 
 rbridge-id 3
 session-vlan 3000 
 icl ICL lag 2
peer 10.1.1.2 rbridge-id 2 icl ICL
client-auto-config ethe 1/1/1 to 1/1/3 
 client-auto-config start
deploy 
 client AUTO-Router002438769e00 
  rbridge-id 3593 
  client-interface enternet 1/1/1
!
    Note: At this point, the client configuration does not appear in the running configuration and cannot be modified. Any LAG configurations toward the clients have not been created yet.
  6. Use the client-auto-detect config deploy-all command to push the automatically discovered clients into the running configuration
    RUCKUS-1(config-cluster-SW)#client-auto-detect config deploy-all
LAG MCT-CCAC-LAG_2 deployed successfully!
CLUSTER AUTOCONFIG INFO - Port 1/1/1 is successfully programmed as client interface. Removing from autoconfig port list.
CLUSTER AUTOCONFIG INFO - Cluster 4000 client auto-config process stopped

    All automatically detected client information is now published into the running configuration, and the dynamic LAG configuration is generated, created, and deployed. LACP is started. Ports that are successfully programmed as CCEPs are removed from the auto-configuration-enabled port list. If the port list is empty, which means all ports are configured into clients successfully, the automatic configuration process stops. Otherwise, the automatic configuration process continues only on the ports still left in the list.

Parent topic: Cluster Client Automatic Configuration