Getting started with dynamic routing

You can configure dynamic routing in the SMC Client or on the command line of the Security Engine.

Note: We recommend that you configure dynamic routing only if you have experience and knowledge of the general principles of dynamic routing and Free Range Routing (FRR) syntax. Poorly configured dynamic routing can lead to adverse effects on networks, such as packets being directed to the wrong interfaces or data being exposed to undesired networks.

The two methods for configuring dynamic routing are separate, and using both methods on the same engine is not supported.

If you configure dynamic routing for an Security Engine on the command line, that dynamic routing configuration is not shown in the SMC Client.
If you configure dynamic routing for an Security Engine in the SMC Client, the configuration overwrites the dynamic routing configuration that you configured on the command line.

In the SMC Client, you can configure dynamic routing using border gateway protocol (BGP), open shortest path first (OSPFv2), and protocol-independent multicast (PIM).

When using FRR commands and syntax on the command line of the Security Engine, the supported dynamic routing protocols are BGP, OSPFv2, OSPFv3, PIM, and routing information protocol (RIP).

Dynamic routing is supported on Single Engines, Engine Clusters, and Virtual Engines. The rules that allow dynamic routing traffic are created automatically.

Note: An antispoofing configuration is not automatically generated for routes learned through dynamic routing protocols. You must manually add hosts or networks to the Additional Networks to Automatically Add to Antispoofing table in the Engine Editor.

Before installing a policy that includes a dynamic routing configuration, you can preview and save the configuration in FRR syntax.