Cumulus Linux 3.4 and later releases replace Quagga with FRRouting. This section outlines the upgrade process for users currently using Quagga.
These instructions only apply to upgrading to Cumulus Linux 3.4 or later from releases earlier than 3.4. New image installations contain
frr instead of
quagga-compat. If you are using any automation tools to configure your network and are installing a new Cumulus Linux image, make sure your automation tools refer to FRR and not to Quagga.
If you are upgrading Cumulus Linux using
apt-get upgrade, existing automation that references Quagga continues to work until you upgrade to FRR. Once you perform the following upgrade steps, your automation must reference FRR instead of Quagga.
Upgrading to Cumulus Linux 3.4 or later results in both
frr.service being present on the system, until
quagga.service is removed. These services have been configured to conflict with each other; starting one service automatically stops the other, as they cannot run concurrently.
Run the following commands to begin the upgrade process:
At the end of the
apt-get upgradeprocess, the output shows details of the upgrade process, regarding the Quagga to FRR switchover.
Once the upgrade process is completed, the switch is in the following state:
The output below shows the FRR / Quagga package status:
python-clcmd. While the package remains, the related commands have been removed.
To complete the transition to FRR:
vtysh.conffile should not be moved, as it is unlikely any configuration is in the file. However, if there is necessary configuration in place, copy the contents into
Merge the current
Quagga.conffile with the new
frr.conffile. Keep the default configuration for
frr.confin place, and add the additional configuration sections from
- Enable the daemons needed for your installation in
- Manually update the log file locations to
Remove the compatibility package:
This step stops the Quagga compatibility mode, causing routing to go down.
quagga-compatpackage also removes
/etc/quaggadirectory is not removed in this step, as it is left in place for reference.
Purge the Quagga packages:
This step deletes all Quagga configuration files. Please ensure you back up your configuration.
Cumulus Networks does not recommend reinstalling the
quagga-compatpackages once they have been removed. While they can be reinstalled to continue migration iterations, limited testing has taken place, and configuration issues may occur.
Start FRR without Quagga compatibility mode:
systemctl -l status frr output shows an issue, edit the configuration files to correct it, and repeat the process. If issues persist, you can return to Quagga compatibility mode for further testing:
Several configuration migration iterations may be necessary to ensure the configuration is behaving the same in both Quagga and FRR.
Once further testing is complete, run the following commands to reset the FRR installation, and then repeat the steps from the beginning of this section to upgrade to FRR: