Upgrade MCT Clusters from SLX-OS 18r.2.00b

You can upgrade MCT clusters from SLX-OS 18r.2.00b to SLX-OS 20.1.1 or later with minimal traffic loss. This topic applies only to SLX 9540 and SLX 9640 devices.

About this task

Perform the following steps to upgrade your MCT clusters while preserving your startup configuration after upgrade.

Important

Do not change startup-config after you run the mct_config_convert.py tool. Changes made after the tool runs are not reflected after the upgrade to SLX-OS 20.1.1 or later.

1. On Node A and Node B, download the mct_config_convert.py tool from github.extremenetworks.com.
2. On Node A and Node B, copy the tool to the flash:// path.
   

   device# copy scp://<username>:<password>@<hostname>//<path to file>/mct_config_convert.py  flash://mct_config_convert.py

3. On Node A and Node B, configure client isolation mode to be loose.
   

   device(config)# cluster <cluster-name> <cluster-id>
   device(config-cluster-1)# client-isolation loose
   

4. Isolate Node A from the network.
   1. On Node A, disable the MCT client interfaces.
      

      device(config-cluster-1)# client-interfaces-shutdown

   2. Disable the uplink to the core network.
   3. Shut the link connected to the MCT peer node (ICL interface).
      At this point, all CCEP traffic is switched to Node B within 30 seconds, depending on the scale and other parameters.
5. On Node A, copy the running configuration to the startup configuration.
   

   device# copy running-config startup-config

6. On Node A, run the tool from privileged EXEC mode using the following syntax: python mct_config_convert.py -–peer_ip <MCT peer-ip-address> --peer_int <MCT peer interface>.
   For example:

   

   device# python mct_config_convert.py --peer_ip "10.x.x.x" --peer_int "Port-Channel 64"

   This step converts your existing MCT configuration to the format required for SLX-OS 20.1.1 and later.
7. Upgrade Node A to the 20.1.1 or later image using the firmware download command with the fullinstall option.
   During the upgrade on Node A, traffic passes through Node B.
8. Verify that Node A is back online after the upgrade and initialization is complete.
9. Isolate Node B from the network.
   

   Important

   There is complete traffic loss at this step.
   1. On Node B, disable the MCT client interfaces.
      

      device(config-cluster-1)# client-interfaces-shutdown

   2. Disable the uplink to the core network.
   3. Shut the link connected to the MCT peer node (ICL interface).
10. On Node B, copy the running configuration to the startup configuration.
    

    device# copy running-config startup-config

11. On Node A, enable the uplink to the core network and the link connected to the MCT peer node (ICL interface).
12. Restore Node A to the network.
    

    device(config-cluster-1)# no shutdown clients 
     

    All CCEP traffic switches to Node A within 30 seconds, depending on the scale and other parameters.
13. On Node B, run the tool from privileged EXEC mode using the following syntax: python mct_config_convert.py -–peer_ip <MCT peer-ip-address> --peer_int <MCT peer interface>. For example:
    

    device# python mct_config_convert.py --peer_ip "10.x.x.x" --peer_int "Port-Channel 63"

14. Upgrade Node B to the 20.1.1 or later image using the firmware download command with the fullinstall option.
    During the upgrade on Node B, traffic passes through Node A.
15. On Node B, enable the uplink to the core network and the link connected to the MCT peer node (ICL interface).
16. When the cluster peer is up, restore Node B to the network.
    

    device(config-cluster-1)# no shutdown clients 
     

17. Save the configuration changes to the respective nodes.