Menu
Quagga - The open source router. Copyright 1996-2005 Kunihiro Ishiguro, et al. Quagga-router# If you want to run a Quagga command from the Linux shell:. Quagga uses an advanced software architecture to provide you with a high quality, multi server routing engine. Quagga has an interactive user interface for each routing protocol and supports common client commands. Due to this design, you can add new protocol daemons to Quagga easily. You can use Quagga library as your program’s client user.
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
or 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 will continue to work until you upgrade to FRR. Once you perform the following upgrade steps, your automation must reference FRR instead of Quagga.![Commands Commands](/uploads/1/2/5/7/125738342/202971717.gif)
Upgrading to Cumulus Linux 3.4 will result in both
quagga.service
and 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 will automatically stop the other, as they cannot run in tandem.- Run the following commands to begin the upgrade process:At the end of the
apt-get upgrade
process, the output will show details of the upgrade process, in regards to the Quagga -> FRR switchover.
Once the upgrade process is completed, the switch will be in the following state:
The output below shows the FRR / Quagga package status:
Cumulus 3.4 and later releases do not support or implement
python-clcmd
. While the package remains, the related commands have been removed.To complete the transition to FRR:
- Migrate all
/etc/quagga/*
files to/etc/frr/*
.Thevtysh.conf
file 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/etc/frr/vtysh.conf
. - Merge the current
Quagga.conf
file with the newfrr.conf
file. Keep the default configuration forfrr.conf
in place, and add the additional configuration sections fromQuagga.conf
. - Enable the daemons needed for your installation in
/etc/frr/daemons
. - Manually update the log file locations to
/var/log/frr
orsyslog
. - Remove the compatibility package:This step stops the Quagga compatibility mode, causing routing to go down.The
/etc/quagga
directory is not removed in this step, as it is left in place for reference. - Start FRR without Quagga compatibility mode:
Troubleshooting
If the
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:
Removing Quagga
Once the FRR migration is complete, and you are satisfied that the configuration is performing the same with FRR as Quagga, remove the
quagga
and quagga-compat
packages:Removing the
quagga-compat
package also removes quagga.service
.Cumulus Networks does not recommend reinstalling the
quagga
and quagga-compat
packages once they have been removed. While they can be reinstalled to continue migration iterations, limited testing has taken place, and configuration issues may occur.