Aggregators

Aggregators have access to both Quagga and, since 6.5, the dynamic routing options in bonding. If you are implementing dynamic routing on an aggregator for the first time and the aggregator is at least version 6.5, it is highly suggested to use the options in bonding instead of Quagga. Using bonding offers a more integerated experience, while also supporting more protocols.

Bonding implementation

This is identical to adding protocols (and filters) on bonders, with the only exception being that aggregator protocols have the Space field instead of Include in private WAN, as aggregators participate in multiple spaces. A protocol associated with a private WAN space will import and export routes (according to its filters) on precisely the interfaces associated with that space. If a space is selected that does not have private WAN enabled, the protocol will be disabled.

Warning

Interfaces that are added to an aggregator protocol must have the same space as the protocol.

Refer to Configuring dynamic routing in bonding for documentation on configuring dynamic routing protocols and filters in bonding.

Quagga implementation

Read AN-002 Implementing dynamic routing in quagga for full implementation details.