Upgrade MCT Clusters from the SLX-OS 20.1.1 Controlled Release

This procedure is based on the presence of Layer 2 VPN configuration. If Layer 2 VPN configuration is not present, swap steps 5 and 6 with steps 7 and 8 to minimize traffic loss.
  1. Isolate Node A from the network.
    1. On Node A, disable the MCT client interfaces and ICL interface.
      device(config-cluster-1)# shutdown all
    2. Disable the uplink to the core network.
      This command causes all CCEP traffic to switch to Node B within 10 seconds, depending on the scale and other parameters.
  2. On Node A, copy the running configuration to the startup configuration.
    device# copy running-config startup-config
  3. 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.
  4. Verify that Node A is back online after the upgrade and initialization is complete.
  5. Isolate Node B from the network.
    Important

    Important

    There is complete traffic loss at this step.
    1. On Node B, disable the MCT client interfaces and ICL interface.
      device(config-cluster-1)# shutdown all
    2. Disable the uplink to the core network.
  6. On Node B, copy the running configuration to the startup configuration.
    device# copy running-config startup-config
  7. On Node A, enable the uplink to the core network.
  8. Restore Node A to the network.
    device(config-cluster-1)# no shutdown all 
     
    This command causes all CCEP traffic to switch to Node A within 10 seconds, depending on the scale and other parameters.
  9. 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.
  10. Verify that Node B is back online after the upgrade and initialization is complete.
  11. On Node B, enable the uplink to the core network.
  12. Restore Node B to the network.
    device(config-cluster-1)# no shutdown all 
     
  13. Save the configuration changes to the respective nodes.