Step 3: Configuring the Cluster

Configuring a local cluster requires the cluster ID and RBridge ID for the local switch or router.
Configuration of the peer device involves the peer's IP address, RBridge ID, and ICL specification.

The following task steps configure device RUCKUS-1 for the cluster in the topology of Basic MCT Configuration. The peer device, RUCKUS-2 configuration is shown in the Example section below the task.

  1. Enter global configuration mode. 
    RUCKUS-1# configure terminal
  2. Configure a cluster name and ID. 
    RUCKUS-1(config)# cluster SW 4000
    If you do not specify a cluster name, the device will automatically generate the cluster name as CLUSTER-X.
  3. Configure the RBridge ID. 
    Ruckus-1(config-cluster-SW)# rbridge-id 3
    The RBridge ID must be different from the other cluster RBridge and any other client in the cluster.
  4. Assign a VLAN to the session. 
    RUCKUS-1(config-cluster-SW)# session-vlan 3000
    The MCT member VLAN is defined as any VLAN of which the ICL is a member.
  5. Configure the keep alive for the VLAN. 
    RUCKUS-1(config-cluster-SW)# keep-alive-vlan 3001
  6. Configure the ICL. 
    Ruckus-1(config-cluster-SW)# icl ICL lag 2
  7. Configure the peer ICL parameters. 
    RUCKUS-1(config-cluster-SW)# peer 10.1.1.2 rbridge-id 2 icl ICL
  8. Deploy the configuration. 
    RUCKUS-1(config-cluster-SW)# deploy

The following example configures device Ruckus-2 for the cluster in the topology of Basic MCT Configuration. 

RUCKUS-2# configure terminal
RUCKUS-2(config)# cluster SW 4000    
RUCKUS-2(config-cluster-SW)# rbridge-id 2  
RUCKUS-2(config-cluster-SW)# session-vlan 3000
RUCKUS-2(config-cluster-SW)# keep-alive-vlan 3001
RUCKUS-2(config-cluster-SW)# icl ICL lag 2
RUCKUS-2(config-cluster-SW)# peer 10.1.1.3 rbridge-id 3 icl ICL 
RUCKUS-2(config-cluster-SW)# deploy
Proceed to the next task.
Parent topic: Configuring MCT