Create OSPF Routing Profiles

1. Create an OSPF Global Timer Profile.
   1. Select NetworkRoutingRouting ProfilesOSPF.
   2. Add an OSPF Global Timer Profile by Name (a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
   3. Enter the LSA min-arrival, which is the minimum length time (in seconds) between transmissions of two instances of the same LSA (same advertising router ID, same LSA type, and same LSA ID). If the same LSA arrives sooner than the configured interval, the LSA is dropped. Range is 1 to 10; default is 5. The LSA min-arrival is equivalent to MinLSInterval in RFC 2328. Lower values can be used to reduce re-convergence times when topology changes occur.
   4. In the SPF area, enter the Initial delay (in seconds) from when the logical router receives a topology change until it performs the Shortest Path First (SPF) calculation; range is 0 to 600; default is 5. Lower values enable faster OSPF re-convergence. Routers peering with the firewall should use the same delay value to optimize convergence times.
   5. Enter the Initial hold time (in seconds) between consecutive SPF calculations; range is 0 to 600; default is 5.
   6. Enter the Maximum hold time (in seconds), which is the largest value that the hold time throttles to until remaining steady; range is 0 to 600; default is 5.

   7. Click OK.
2. Create an OSPF Interface Authentication Profile.
   1. Select NetworkRoutingRouting ProfilesOSPF.
   2. Add an OSPF Auth Profile by Name (a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.
   3. Select the Type of authentication: Password or MD5.
      • If you choose Password, enter the Password (maximum of eight characters) and Confirm Password.

      • If you choose MD5, Add an MD5 key ID (range is 0 to 255) and a Key (a maximum of 16 alphanumeric characters). Select Preferred to prefer an MD5 key over other MD5 keys. During the commit, the firewall goes through the list of keys from the top down and the Preferred key is moved to the top of the list; the top Preferred key is used. (In other words, if you select more than one Preferred MD5 key, the last one chosen as Preferred is the Preferred key.)

   4. Click OK.
3. Create an OSPF Interface Timer Profile.
   1. Select NetworkRoutingRouting ProfilesOSPF.
   2. Add an OSPF Interface Timer Profile by Name (a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.

   3. Enter the Hello Interval, the interval (in seconds) between Hello packets that the firewall sends out an interface to maintain neighbor relationships; range is 1 to 3600; default is 10.
   4. Enter the Dead Count, the number of times the Hello Interval can occur for a neighbor without OSPF receiving a hello packet from the neighbor, before OSPF considers that neighbor down; range is 3 to 20; default is 4.
   5. Enter the Retransmit Interval, the number of seconds between LSA retransmissions to adjacent routers; range is 1 to 1800; default is 5.
   6. Enter the Transmit Delay, the number of seconds required to transmit a Link State Update Packet over the interface. Link State Advertisements in the update packet have their age incremented by this number before they are transmitted; range is 1 to 1800; default is 1.
   7. Enter the Graceful Restart Hello Delay (sec) in seconds, which applies to an OSPF interface when Active/Passive High Availability is configured. Graceful Restart Hello Delay is the length of time during which the firewall sends Grace LSA packets at 1-second intervals. During this time, no hello packets are sent from the restarting firewall. During the restart, the dead timer (which is the Hello Interval multiplied by the Dead Count) is also counting down. If the dead timer is too short, the adjacency will go down during the graceful restart because of the hello delay. Therefore, it is recommended that the dead timer be at least four times the value of the Graceful Restart Hello Delay. For example, a Hello Interval of 10 seconds and a Dead Count of 4 yield a dead timer of 40 seconds. If the Graceful Restart Hello Delay is set to 10 seconds, that 10-second delay of hello packets is comfortably within the 40-second dead timer, so the adjacency will not time out during a graceful restart. Range is 1 to 10; default is 10.
   8. Click OK.
4. Create an OSPF Redistribution Profile to specify any combination of IPv4 static routes, connected routes, BGP IPv4 routes, RIPv2 routes, and default IPv4 route to redistribute to OSPF.
   1. Select NetworkRoutingRouting ProfilesOSPF.
   2. Add an OSPF Redistribution Profile by Name (a maximum of 63 characters). The name must start with an alphanumeric character, underscore (_), or hyphen (-), and can contain a combination of alphanumeric characters, underscore, or hyphen. No dot (.) or space is allowed.

   3. Select IPv4 Static to allow configuration of this portion of the profile.
      • Enable the IPv4 Static portion of the profile.
      • Specify the Metric to apply to the static routes being redistributed into OSPF (range is 1 to 65,535).
      • Specify the Metric-Type: Type 1 (OSPF costs) or Type 2 (default). If there are two static routes to a destination and they have the same cost, a Type 2 route is preferred over a Type 1 route.
      • Select a Redistribute Route-Map or create a new Redistribute Route Map whose match criteria control which IPv4 static routes to redistribute into OSPF. Default is None. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route. Likewise, the Metric Type in the route map Set configuration takes precedence over the Metric Type configured in this redistribution profile.
   4. Select Connected to allow configuration of this portion of the profile.
      • Enable the Connected portion of the profile.
      • Specify the Metric to apply to the connected routes being redistributed into OSPF (range is 1 to 65,535).
      • Specify the Metric-Type: Type 1 or Type 2 (default). Type E1 cost is the sum of the external cost plus the internal cost to reach that route. Type E2 is only the external cost of that route. This can be useful when you want to load-balance the same external route, for example.
      • Select a Redistribute Route-Map or create a new Redistribute Route Map whose match criteria control which connected routes to redistribute into OSPF. Default is None. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route. Likewise, the Metric Type in the route map Set configuration takes precedence over the Metric Type configured in this redistribution profile.
   5. Select RIPv2 to allow configuration of this portion of the profile.
      • Enable the RIPv2 portion of the profile.
      • Specify the Metric to apply to the RIPv2 routes being redistributed into OSPF (range is 0 to 4,294,967,295).
      • Specify the Metric-Type: Type 1 or Type 2 (default).
      • Select a Redistribute Route-Map or create a new Redistribute Route Map whose match criteria control which RIPv2 routes to redistribute into OSPF. Default is None. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route. Likewise, the Metric Type in the route map Set configuration takes precedence over the Metric Type configured in this redistribution profile.
   6. Select BGP AFI IPv4 to allow configuration of this portion of the profile.
      • Enable the BGP AFI IPv4 portion of the profile.
      • Specify the Metric to apply to the BGP routes being redistributed into OSPF (range is 0 to 4,294,967,295).
      • Specify the Metric-Type: Type 1 or Type 2 (default).
      • Select a Redistribute Route-Map or create a new Redistribute Route Map whose match criteria control which BGP IPv4 routes to redistribute into OSPF. Default is None. If the route map Set configuration includes a Metric Action and Metric Value, they are applied to the redistributed route. Otherwise, the Metric configured on this redistribution profile is applied to the redistributed route. Likewise, the Metric Type in the route map Set configuration takes precedence over the Metric Type configured in this redistribution profile.
   7. Select IPv4 Default Route to allow configuration of this portion of the profile.
      • Select Always to always redistribute the IPv4 default route to OSPF; default is enabled.
      • Enable the IPv4 Default Route portion of the profile.
      • Specify the Metric to apply to the default route being redistributed into OSPF (range is 0 to 4,294,967,295).
      • Specify the Metric-Type: Type 1 or Type 2 (default).
   8. Click OK.
5. Commit.