Introduction
Products concerned: SNS 4.8.1 and upwards
As of SNS version 4.8.1, the BIRD v2 dynamic routing engine will be supported, and replaces BIRD v1, which has become obsolete.
The aim of this document is to guide SNS firewall administrators through the configuration and operation of the built-in BIRD v2 dynamic routing module.
To migrate your BIRD v1 configuration to BIRD v2, refer to the section Migrating a dynamic routing configuration from BIRD v1 to BIRD v2
The first part of the document describes the configuration environment, and the modes of interaction with the routing engine. Next, a simple typical configuration will be presented for the BGP, RIP and OSPF routing protocols.
These examples provide the opportunity to discover the configuration structure of the protocols as well as peripheral objects, filtering and status displays. The last section will focus on a more complex configuration.
Do note that BIRD offers various configuration options, notably inter-process route exchanges, route filtering, and the pseudo-virtualization of routing instances. These advanced options, which are specific to BIRD, will not be covered in this document.
These components, as well as the detailed syntax used in the dynamic routing configuration, are provided in the BIRD v2 user guide published on the BIRD vendor website.
Restrictions
IMPORTANT
If your SNS firewall pool is managed by an SMC server, you will need SMC in version 3.6 or higher in order to manage dynamic routing on your firewalls in 4.8.1 and higher versions.
Date | Description |
---|---|
September 25, 2024 |
New document |