Extreme SLX-OS Layer 2 Switching Configuration Guide, 20.6.1

Configuring MCT

Ensure that the following configurations exist:

Layer 3 interface for the cluster peer interface
VLANs and bridge domains function as the MCT members
Port channel for Link Aggregation or an Ethernet interface as a client interface

Perform the following steps.

In privileged EXEC mode, enter global configuration mode.
```
device# configure terminal
```
Create a cluster on the device.
```
device(config)# cluster leaf1_2
```
Configure the peer IP address.
```
device(config-cluster-leaf1_2)# peer 40.1.1.2
```
The peer IP address is the IP address configured on the peer switch for the peer-interface.
Configure the peer interface.
```
device(config-cluster-leaf1_2)# peer-interface port-channel 40
```
The peer interface should be a valid Layer 3 interface.

Configure the port channel interface.

device(config-cluster-leaf1_2)# exit
device(config)# int port-channel 40

Configure port-channel IP address.

device(config-port-channel-40)# ip address 40.1.1.1/24

Configure the port channel range.

device(config-Port-channel-40)# exit
device(config)# cluster leaf1_2
device(config-cluster-leaf1_2)# int port-channel 1-2,5

This allows you to replicate a single command across multiple interfaces.

Set the cluster client ID for the port-channel (auto allocated ID in this case).
```
device(config-Port-channel-1-2,5)# cluster-client auto
```

The following example is the steps in the previous configuration.

device# configure terminal
Entering configuration mode terminal
device(config)# cluster leaf1_2
device(config-cluster-leaf1_2)# peer 40.1.1.2
device(config-cluster-leaf1_2)# peer-interface port-channel 40
device(config-cluster-leaf1_2)# int port-channel 40
device(config-port-channel-40)# ip address 40.1.1.1/24
device(config-cluster-leaf1_2)# int port-channel 1-2,5
device(config-Port-channel-1-2,5)# cluster-client auto
device(config-Port-channel-1-2,5)# exit
device(config)#

Taking the MCT node offline for maintenance

If you need to take an MCT device offline for maintenance or an upgrade, perform the following steps to minimize traffic loss.

Verify the state of the MCT node and it's peer using show cluster.

device# show cluster MCT
Cluster MCT 
==============
Cluster State: Active
Bringup Delay: 90 seconds
Configured Member Vlan Range: All
Active Member Vlan Range: 1-4090
Configured Member BD Range: All
Active Member BD Range: 10,1001-3000
No. of Clients: 4

 Peer Info:
 ==========
 Peer IP: 15.1.1.1, State: Up  
 Peer Interface: Port-channel 256, Source IP: 15.1.1.2 

 Keep-Alive:
 ==========
 IP: 10.20.232.52, State: Up  
 Interface: Management 0 (mgmt-vrf), Source IP: 10.20.233.224
 Client-Isolation Role: Primary

 Client Info:
 ============
 Interface               Id               Description          Local/Remote State   Exceptions          
 ---------               --               -----------          ------------------   ----------          
 Port-channel 1          1001                                  Up   / Up                                 
 Port-channel 2          1002                                  Up   / Up                                 
 Tunnel 32771            42.42.42.42      VxLAN                Up   / Up                                 
 PW                      34816            VPLS/VLL             Down / Down           Client Down

Enter config mode and enable system maintenance.

device# config 
device(config)# system maintenance 
device(config-system-maintenance)# enable

Note

Do not write the configuration changes made in the previous steps to the startup-configuration file.

To bring the MCT node back online, perform one of the following actions.

If you upgraded or downgraded the device, select the coldboot option under the firmware download menu.
For any other reason, execute the reload system command. Since the changed configuration was not saved, the reload reverts the configuration changes that had taken the MCT node offline.