Upgrading Cumulus Linux when MLAG Is Configured

Follow

If you are using MLAG to dual connect two Cumulus Linux switches in your environment, you should follow the appropriate steps below to ensure a smooth upgrade.

Upgrading from Cumulus Linux 3.y.z to a Later 3.y.z Release

If you are using MLAG to dual connect two switches running an earlier version of Cumulus Linux 3.y.z, follow these steps to ensure a smooth upgrade:

  1. Verify the switch is in the secondary role:
    cumulus@switch:~$ clagctl status
  2. Update the Cumulus Linux repositories:
    cumulus@switch:~$ sudo apt-get update
  3. Shut down the core uplink L3 interfaces:
    cumulus@switch:~$ ip link set swpX down
  4. Shut down the peerlink:
    cumulus@switch:~$ ip link set peerlink down
  5. Update the Cumulus Linux image and packages:
    cumulus@switch:~$ sudo apt-get upgrade
  6. Reboot the switch:
    cumulus@switch:~$ sudo reboot
  7. Verify STP convergence across both switches:
    cumulus@switch:~$ mstpctl showall
  8. Verify core uplinks and peerlinks are UP:
    cumulus@switch:~$ net show interface
  9. Verify MLAG convergence:
    cumulus@switch:~$ clagctl status
  10. Make this secondary switch the primary:
    cumulus@switch:~$ clagctl priority 2048
  11. Verify the other switch is now in the secondary role.
  12. Repeat steps 2-9 on the new secondary switch.
  13. Remove the priority 2048 and restore the priority back to 32768 on the current primary switch:
    cumulus@switch:~$ clagctl priority 32768

Upgrading from Cumulus Linux 2.y.z to Version 3.y.z

If you are using MLAG to dual connect two switches running Cumulus Linux 2.5 ESR or any other release earlier than 3.0.0, the switches will not be dual-connected after you upgrade the first switch. To ensure a smooth upgrade, follow these steps:

  1. Run cl-img-select -fr to boot the switch in the secondary role into ONIE, then reboot the switch.
  2. Install Cumulus Linux 3.2.1 onto the secondary switch using ONIE. At this time, all traffic is going to the switch in the primary role.
  3. After the install, copy the license file and all the configuration files you backed up, then restart the switchd, networking and Quagga services. All traffic is still going to the primary switch.
    cumulus@switch:~$ sudo systemctl restart switchd.service
    cumulus@switch:~$ sudo systemctl restart networking.service
    cumulus@switch:~$ sudo systemctl restart quagga.service
  4. Run cl-img-select -fr to boot the switch in the primary role into ONIE, then reboot the switch. Now, all traffic is going to the switch in the secondary role that you just upgraded to version 3.2.1.
  5. Install Cumulus Linux 3.2.1 onto the primary switch using ONIE. 
  6. After the install, copy the license file and all the configuration files you backed up.
  7. Disable clagd in the /etc/network/interfaces file (set clagd-enable to no), then restart the switchd, networking and Quagga services.
    cumulus@switch:~$ sudo systemctl restart switchd.service
    cumulus@switch:~$ sudo systemctl restart networking.service
    cumulus@switch:~$ sudo systemctl restart quagga.service
  8. Enable clagd again in the /etc/network/interfaces file (set clagd-enable to yes), then run ifreload -a.
    cumulus@switch:~$ sudo ifreload -a
  9. Now the two switches are dual-connected again and traffic flows to both switches.
Have more questions? Submit a request

Comments

Powered by Zendesk