To use the OSPFv3 dynamic routing protocol with Fireware, you must type OSPFv3 configuration commands or import a configuration file on the Network > Dynamic Routing page.
This topic includes a sample configuration file for Free Range Routing (FRR), which is the routing daemon in Fireware v12.9 or higher. To use this configuration file as a starting point for your OSPFv3 configuration, copy the text into a text editor application and edit the parameters to meet your business requirements.
For information about OSPFv3 requirements and how to configure BGP, go to Configure IPv6 Routing with OSPFv3.
For a list of OSPFv3 commands, go to OSPFv3 Commands (FRR).
In Fireware v12.8.x or lower, Fireware uses the Quagga routing engine. For a sample routing configuration file for Fireware v12.8.x or lower, go to Sample OSPFv3 Routing Configuration File (Quagga). For a list of Quagga commands, go to OSPFv3 Commands (Quagga).
The OSPFv3 area, access-list, and default-information originate commands are not supported.
Example OSPFv3 Commands (FRR in Fireware v12.9 or Higher)
This list includes example FRR commands that you might include in your OSPFv3 configuration. For a complete list of FRR commands, go to the FRRouting User Guide.
The sections must appear in the configuration file in the same order they appear in this table.
Configure Interface Properties
|interface eth[N]||Begin section to set properties for interface|
|ipv6 ospf6 cost [1-65535]||Set link cost for the interface (go to OSPF Interface Cost Table)|
|ipv6 ospf6 dead-interval [1-65535]||Set interval after last hello from a neighbor before declaring it down; default is 40 seconds|
|ipv6 ospf6 hello-interval [1-65535]||Set interval to send hello packets; default is 10 seconds|
|ipv6 ospf6 passive||Disable OSPF announcement for the interface|
|ipv6 ospf6 priority [0-255]||Set the router priority for the interface. A high value increases eligibility to become the designated router (DR). Default value is 1.|
|ipv6 ospf6 retransmit-interval [1-65535]||Set interval between link-state advertisements (LSA) retransmissions; default is 5 seconds|
|ipv6 ospf6 transmit-delay [1-3600]||Set time required to send LSA update; default is 1 second|
|Configure OSPFv3 Routing Daemon and Redistribute Properites|
|Enable OSPF6 daemon|
|ospf6 router-id [A.B.C.D]||
Set router ID for OSPF6 manually; router determines its own ID if not set.
If your configuration includes the Quagga command router-id [A.B.C.D], this command automatically converts to the FRR command ospf6 router-id [A.B.C.D] if you upgrade from Fireware v12.8.x or lower to Fireware v12.9 or higher.
|redistribute connected||Redistribute routes from all interfaces to OSPFv3|
|redistribute connected route-map [MAPNAME]||
Redistribute routes from all interfaces to OSPFv3, with a route map filter (mapname)
|redistribute static||Redistribute firewall static routes to OSPFv3|
|default-information originate||Share route of last resort (default route) with OSPF|
|default-information originate metric [0-16777214]||Share route of last resort (default route) with OSPF, and add a metric used to generate the default route|
|default-information originate always||Always share the route of last resort (default route)|
|default-information originate always metric [0-16777214]||Always share the route of last resort (default route), and add a metric used to generate the default route|
|Set OSPF Network and Area Properties|
|interface eth[N] area [W.X.Y.Z]||Bind interface to area and send OSPFv3 packets. The area variable can be typed in two formats: [W.X.Y.Z]; or as an integer [Z].|
|Redistribute OSPF Routes|
|Configure Route Redistribution with Access Lists and Route Maps|
|ipv6 prefix-list [LISTNAME] [PERMIT|DENY] [A,B,C,D/M | ANY]||Create a prefix list to allow or deny route redistribution|
|route-map [MAPNAME] permit [N]||Create a route map with name [MAPNAME] and allow with a priority of [N]|
|match ipv6 address prefix-list [LISTNAME]||
Match the specified prefix-list
|Enable SNMP Queries (Fireware v12.10 and higher)|
|agentx||Enable SNMP queries for dynamic routing. SNMP queries can result in high CPU usage if there is a large number of routes.