If the device is using virtual routing, the ID fields display the unique process IDs generated for the chosen virtual router.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• OSPF Process—Choose the process ID. For a device using virtual routing, the drop-down lists the unique process IDs generated for the selected virtual router.

• Area ID—Designation of the area for which routes are to be summarized.

• Area Type—Choose one of the following:

  • Normal—(Default) Standard OSPF area.

  • Stub—A stub area does not have any routers or areas beyond it. Stub areas prevent Autonomous System (AS) External LSAs (Type 5 LSAs) from being flooded into the stub area. When you create a stub area, you can prevent summary LSAs (Types 3 and 4) from being flooded into the area by NOT checking the Summary Stub check box.

  • NSSA—Makes the area a not-so-stubby area (NSSA). NSSAs accept Type 7 LSAs. You can disable route redistribution by NOT checking the Redistribute check box and checking the Default Information Originate check box. You can prevent summary LSAs from being flooded into the area by NOT checking the Summary NSSA check box.

• Metric Value—The metric used for generating the default route. The default value is 10. Valid metric values range from 0 through 16777214.

• Metric Type—The metric type is the external link type that is associated with the default route that is advertised into the OSPF routing domain. The available options are 1 for a Type 1 external route or 2 for a Type 2 external route.

• Available Network—Choose one of the available networks and click Add, or click Add () to add a new network object. See Network for the procedure for adding networks.

• Authentication—Choose the OSPF authentication:

  • None—(Default) Disables OSPF area authentication.

  • Password—Provides a clear text password for area authentication, which is not recommended where security is a concern.

  • MD5—Allows MD5 authentication.

• Default Cost—The default cost for the OSPF area, which is used to determine the shortest paths to the destination. Valid values range from 0 through 65535. The default value is 1.

• Choose one of the available networks and whether to advertise, or,

• Click Add () to add a new network object. See Network for the procedure for adding networks.

• Peer Router—Choose the IP address of the peer router. To add a new peer router, click Add (). See Network for the procedure for adding networks.

• Hello Interval—The time in seconds between the hello packets sent on an interface. The hello interval is an unsigned integer that is to be advertised in the hello packets. The value must be the same for all routers and access servers on a specific network. Valid values range from 1 through 65535. The default is 10.

  The smaller the hello interval, the faster topological changes are detected, but the more traffic is sent on the interface.

• Transmit Delay—The estimated time in seconds that is required to send an LSA packet on the interface. The integer value must be greater than zero. Valid values range from 1 through 8192. The default is 1.

  LSAs in the update packet have their own ages incremented by this amount before transmission. If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. The value assigned should take into account the transmission and propagation delays for the interface. This setting has more significance on very low-speed links.

• Retransmit Interval—The time in seconds between LSA retransmissions for adjacencies that belong to the interface. The retransmit interval is the expected round-trip delay between any two routers on the attached network. The value must be greater than the expected round-trip delay, and can range from 1 through 65535. The default is 5.

  When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message. If the router receives no acknowledgment, it resends the LSA. Be conservative when setting this value, or needless retransmission can result. The value should be larger for serial lines and virtual links.

• Dead Interval—The time in seconds that hello packets are not seen before a neighbor indicates that the router is down. The dead interval is an unsigned integer. The default is four times the hello interval, or 40 seconds. The value must be the same for all routers and access servers that are attached to a common network. Valid values range from 1 through 65535.

• Authentication—Choose the OSPF virtual link authentication from the following:

  • None—(Default) Disables virtual link area authentication.

  • Area Authentication—Enables area authentication using MD5. Click Add, and enter the key ID, key, confirm the key, and then click OK.

  • Password—Provides a clear text password for virtual link authentication, which is not recommended where security is a concern.

  • MD5—Allows MD5 authentication. Click Add, and enter the key ID, key, confirm the key, and then click OK.

    Note	Ensure to enter only numbers as the MD5 key ID.

  • Key Chain—Allows key chain authentication. Click Add, and create the key chain, and then click Save. For detailed procedure, see Creating Key Chain Objects. Use the same authentication type (MD5 or Key Chain) and key ID for the peers to establish a successful adjacency.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• OSPF Process—Choose the process ID. For a device using virtual routing, this drop-down list displays the unique process IDs generated for the selected virtual router.

• Route Type—Choose one of the following types:

  • Static—Redistributes static routes to the OSPF routing process.

  • Connected—Redistributes connected routes (routes established automatically by virtue of having the IP address enabled on the interface) to the OSPF routing process. Connected routes are redistributed as external to the device. You can select whether to use subnets under the Optional list.

  • OSPF—Redistributes routes from another OSPF routing process, for example, internal, external 1 and 2, NSSA external 1 and 2, or whether to use subnets. You can select these options under the Optional list.

  • BGP—Redistribute routes from the BGP routing process. Add the AS number and whether to use subnets.

  • RIP—Redistributes routes from the RIP routing process. You can select whether to use subnets under the Optional list.

    Note	As a user-defined virtual router does not support RIP, you cannot redistribute routes from RIP.

  • EIGRP—Redistribute routes from the EIGRP routing process. Add the AS number and whether to use subnets.

• Metric Value—Metric value for the routes being distributed. The default value is 10. Valid values range from 0 to 16777214.

  When redistributing from one OSPF process to another OSPF process on the same device, the metric will be carried through from one process to the other if no metric value is specified. When redistributing other processes to an OSPF process, the default metric is 20 when no metric value is specified.

• Metric Type—The metric type is the external link type that is associated with the default route that is advertised into the OSPF routing domain. The available options are 1 for a Type 1 external route or 2 for a Type 2 external route.

• Tag Value—Tag specifies the 32-bit decimal value attached to each external route that is not used by OSPF itself, but which may be used to communicate information between ASBRs. If none is specified, then the remote autonomous system number is used for routes from BGP and EGP. For other protocols, zero is used. Valid values are from 0 to 4294967295.

• RouteMap—Checks for filtering the importing of routes from the source routing protocol to the current routing protocol. If this parameter is not specified, all routes are redistributed. If this parameter is specified, but no route map tags are listed, no routes are imported. Or you can add a new route map by clicking Add (). See Configure Route Map Entry to add a new route map.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete inter-areas.

• OSPF Process—For a device using virtual routing, the drop-down lists the unique process IDs generated for the selected virtual router.

• Area ID—The area for which routes are to be summarized.

• PrefixList—The name of the prefix. To add a new prefix list object, see Step 5.

• Traffic Direction—Inbound or outbound. Choose Inbound to filter LSAs coming into an OSPF area, or Outbound to filter LSAs coming out of an OSPF area. If you are editing an existing filter entry, you cannot modify this setting.

You must configure a prefix list before you can configure a prefix rule.

• Action—Select Block or Allow for the redistribution access.

• Sequence No—The routing sequence number. By default, sequence numbers are automatically generated in increments of 5, beginning with 5.

• IP Address—Specify the prefix number in the format of IP address/mask length.

• Min Prefix Length—(Optional) The minimum prefix length.

• Max Prefix Length—(Optional) The maximum prefix length.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete filter rules.

• OSPF Process— For a device using virtual routing, the drop-down lists the unique process IDs generated for the selected virtual router.

• Access List—The access list for this OSPF process. To add a new standard access list object, click Add () and see Configure Standard ACL Objects.

• Traffic Direction—Choose In or Out for the traffic direction being filtered. Choose In to filter LSAs coming into an OSPF area, or Out to filter LSAs coming out of an OSPF area. If you are editing an existing filter entry, you cannot modify this setting.

• Interface—The interface for this filter rule.

You can click Edit () to edit, or use the right-click menu to cut, copy, past, insert, and delete summary addresses.

• OSPF Process— For a device using virtual routing, the drop-down lists the unique process IDs generated for the selected virtual router.

• Available Network—The IP address of the summary address. Select one from the Available networks list and click Add, or to add a new network, click Add (). See Network for the procedure for adding networks.

• Tag—A 32-bit decimal value that is attached to each external route. This value is not used by OSPF itself, but may be used to communicate information between ASBRs.

• Advertise—Advertises the summary route. Uncheck this check box to suppress routes that fall under the summary address. By default, this check box is checked.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• Interface—The interface you are configuring.

  Note	If the device is using virtual routing, this drop-down list displays only those interfaces that belong to the router.

• Default Cost—The cost of sending a packet through the interface. The default value is 10.

• Priority—The designated router for a network. Valid values range from 0 to 255. The default value is 1. Entering 0 for this setting makes the router ineligible to become the designated router or backup designated router.

  When two routers connect to a network, both attempt to become the designated router. The device with the higher router priority becomes the designated router. If there is a tie, the router with the higher router ID becomes the designated router. This setting does not apply to interfaces that are configured as point-to-point interfaces.

• MTU Ignore—OSPF checks whether neighbors are using the same MTU on a common interface. This check is performed when neighbors exchange DBD packets. If the receiving MTU in the DBD packet is higher than the IP MTU configured on the incoming interface, OSPF adjacency is not established.

• Database Filter—Use this setting to filter the outgoing LSA interface during synchronization and flooding. By default, OSPF floods new LSAs over all interfaces in the same area, except the interface on which the LSA arrives. In a fully meshed topology, this flooding can waste bandwidth and lead to excessive link and CPU usage. Checking this check box prevents OSPF flooding of the LSA on the selected interface.

• Hello Interval—Specifies the interval, in seconds, between hello packets sent on an interface. Valid values range 1–8192 seconds. The default value is 10 seconds.

  The smaller the hello interval, the faster topological changes are detected, but more traffic is sent on the interface. This value must be the same for all routers and access servers on a specific interface.

• Transmit Delay—Estimated time in seconds to send an LSA packet on the interface. Valid values range 1–65535 seconds. The default is 1 second.

  LSAs in the update packet have their ages increased by the amount specified by this field before transmission. If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. The value assigned should take into account the transmission and propagation delays for the interface. This setting has more significance on very low-speed links.

• Retransmit Interval—Time in seconds between LSA retransmissions for adjacencies that belong to the interface. The time must be greater than the expected round-trip delay between any two routers on the attached network. Valid values range from 1 to 65535 seconds. The default is 5 seconds.

  When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message. If the router receives no acknowledgment, it resends the LSA. Be conservative when setting this value, or needless retransmission can result. The value should be larger for serial lines and virtual links.

• Dead Interval—Time period in seconds for which hello packets must not be seen before neighbors indicate that the router is down. The value must be the same for all nodes on the network and can range 1–65535.

• Hello Multiplier—Specifies the number of Hello packets to be sent per second. Valid values are 3–20.

• Point-to-Point—Lets you transmit OSPF routes over VPN tunnels.

• Authentication—Choose the OSPF interface authentication from the following:

  • None—(Default) Disables interface authentication.

  • Area Authentication—Enables interface authentication using MD5. Click Add, and enter the key ID, key, confirm the key, and then click OK.

  • Password—Provides a clear text password for virtual link authentication, which is not recommended where security is a concern.

  • MD5—Allows MD5 authentication. Click Add, and enter the key ID, key, confirm the key, and then click OK.

    Note	Ensure to enter only numbers as the MD5 key ID.

  • Key Chain—Allows key chain authentication. Click Add, and create the key chain, and then click Save. For detailed procedure, see Creating Key Chain Objects. Use the same authentication type (MD5 or Key Chain) and key ID for the peers to establish a successful adjacency.

• Enter Password—The password you configure if you choose Password as the type of authentication.

• Confirm Password—Confirm the password that you chose.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• OSPF Process—Choose 1 or 2.

• Neighbor—Choose one of the neighbors in the drop-down list, or click Add () to add a new neighbor; enter the name, description, network, whether to allow overrides, and then click Save.

• Interface—Choose the interface associated with the neighbor.

• Router ID—Choose Automatic or IP Address (appears for non-cluster and a cluster in spanned etherchannel mode) or Cluster Pool (appears for a cluster in individual interface mode) for the router ID. If you choose IP address, enter the IP address in the adjacent field. If you choose Cluster Pool, choose the IPv4 cluster pool value in the adjacent drop-down field. For information on creating the cluster pool address, see Address Pools.

• Ignore LSA MOSPF—Suppresses syslog messages when the route receives unsupported LSA Type 6 multicast OSPF (MOSPF) packets.

• RFC 1583 Compatible—Configures RFC 1583 compatibility as the method used to calculate summary route costs. Routing loops can occur with RFC 1583 compatibility enabled. Disable it to prevent routing loops. All OSPF routers in an OSPF routing domain should have RFC compatibility set identically.

• Adjacency Changes—Defines the adjacency changes that cause syslog messages to be sent.

  By default, a syslog message is generated when an OSPF neighbor goes up or down. You can configure the router to send a syslog message when an OSPF neighbor goes down and also a syslog for each state.

  • Log Adjacency Changes—Causes the threat defense device to send a syslog message whenever an OSPF neighbor goes up or down. This setting is checked by default.

  • Log Adjacency Change Details—Causes the threat defense device to send a syslog message whenever any state change occurs, not just when a neighbor goes up or down. This setting is unchecked by default.

• Administrative Route Distance—Allows you to modify the settings that were used to configure administrative route distances for inter-area, intra-area, and external IPv6 routes. The administrative route distance is an integer from 1 to 254. The default is 110.

• LSA Group Pacing—Specifies the interval in seconds at which LSAs are collected into a group and refreshed, check summed, or aged. Valid values range from 10 to 1800. The default value is 240.

• Enable Default Information Originate—Check the Enable check box to generate a default external route into an OSPF routing domain and configure the following options:

  • Always advertise the default route—Ensures that the default route is always advertised.

  • Metric Value—Metric used for generating the default route. Valid metric values range from 0 to 16777214. The default value is 10.

  • Metric Type—The external link type that is associated with the default route that is advertised into the OSPFv3 routing domain. Valid values are 1 (Type 1 external route) and 2 (Type 2 external route). The default is Type 2 external route.

  • RouteMap—Choose the routing process that generates the default route if the route map is satisfied or click Add () to add a new one. See Configure Route Map Entry to add a new route map.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• Area ID—The area for which routes are to be summarized.

• Cost—The metric or cost for the summary route, which is used during OSPF SPF calculations to determine the shortest paths to the destination. Valid values range from 0 to 16777215.

• Type—Specifies Normal, NSSA, or Stub. If you select Normal, there are no other parameters to configure. If you select Stub, you can choose to send summary LSAs in the area. If you select NSSA, you can configure the next three options:

  • Allow Sending summary LSA into this area—Allows the sending of summary LSAs into the area.

  • Imports routes to normal and NSSA area—Allows redistribution to import routes to normal and not to stubby areas.

  • Defaults information originate—Generates a default external route into an OSPFv3 routing domain.

• Metric—Metric used for generating the default route. The default value is 10. Valid metric values range from 0 to 16777214.

• Metric Type—The metric type is the external link type that is associated with the default route that is advertised into the OSPFv3 routing domain. The available options are 1 for a Type 1 external route or 2 for a Type 2 external route.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete route summaries.

• IPv6 Prefix/Length—The IPv6 prefix. To add a new network object, click Add (). See Network for the procedure for adding networks.

• Cost—The metric or cost for the summary route, which is used during OSPF SPF calculations to determine the shortest paths to the destination. Valid values range from 0 to 16777215.

• Advertise—Advertises the summary route. Uncheck this check box to suppress routes that fall under the summary address. By default, this check box is checked.

• Peer RouterID—Choose the IP address of the peer router. To add a new network object, click Add (). See Network for the procedure for adding networks.

• TTL Security—Enables TTL security check. The value for the hop-count is a number from 1 to 254. The default is 1.

  OSPF sends outgoing packets with an IP header Time to Live (TTL) value of 255 and discards incoming packets that have TTL values less than a configurable threshold. Because each device that forwards an IP packet decrements the TTL, packets received via a direct (one-hop) connection have a value of 255. Packets that cross two hops have a value of 254, and so on. The receive threshold is configured in terms of the maximum number of hops that a packet may have traveled.

• Dead Interval—The time in seconds that hello packets are not seen before a neighbor indicates that the router is down. The default is four times the hello interval, or 40 seconds. Valid values range from 1 to 65535.

  The dead interval is an unsigned integer. The value must be the same for all routers and access servers that are attached to a common network.

• Hello Interval—The time in seconds between the hello packets sent on an interface. Valid values range from 1 to 65535. The default is 10.

  The hello interval is an unsigned integer that is to be advertised in the hello packets. The value must be the same for all routers and access servers on a specific network. The smaller the hello interval, the faster topological changes are detected, but the more traffic is sent on the interface.

• Retransmit Interval—The time in seconds between LSA retransmissions for adjacencies that belong to the interface. The retransmit interval is the expected round-trip delay between any two routers on the attached network. The value must be greater than the expected round-trip delay, and can range from 1 to 65535. The default is 5.

  When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message. If the router receives no acknowledgment, it resends the LSA. Be conservative when setting this value, or needless retransmission can result. The value should be larger for serial lines and virtual links.

• Transmit Delay—The estimated time in seconds that is required to send an LSA packet on the interface. The integer value must be greater than zero. Valid values range from 1 to 8192. The default is 1.

  LSAs in the update packet have their own ages incremented by this amount before transmission. If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. The value assigned should take into account the transmission and propagation delays for the interface. This setting has more significance on very low-speed links.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete areas.

• Source Protocol—The source protocol from which routes are being redistributed. The supported protocols are connected, OSPF, Static, EIGRP, and BGP. If you choose OSPF, you must enter the Process ID in the Process ID field. If you choose BGP, you must add the AS number in the AS Number field.

• Metric —Metric value for the routes being distributed. The default value is 10. Valid values range from 0 to 16777214.

  When redistributing from one OSPF process to another OSPF process on the same device, the metric will be carried through from one process to the other if no metric value is specified. When redistributing other processes to an OSPF process, the default metric is 20 when no metric value is specified.

• Metric Type—The metric type is the external link type that is associated with the default route that is advertised into the OSPF routing domain. The available options are 1 for a Type 1 external route or 2 for a Type 2 external route.

• Tag —Tag specifies the 32-bit decimal value attached to each external route that is not used by OSPF itself, but which may be used to communicate information between ASBRs. If none is specified, then the remote autonomous system number is used for routes from BGP and EGP. For other protocols, zero is used. Valid values are from 0 to 4294967295.

• Route Map—Checks for filtering the importing of routes from the source routing protocol to the current routing protocol. If this parameter is not specified, all routes are redistributed. If this parameter is specified, but no route map tags are listed, no routes are imported. Or you can add a new route map by clicking Add (). See Route Map for the procedure to add a new route map.

• Process ID—The OSPF process ID, either 1 or 2.

  Note	The Process ID is enabled the OSPFv3 process is redistributing a route learned by another OSPFv3 process.

• Match—Enables OSPF routes to be redistributed into other routing domains:

  • Internal for routes that are internal to a specific autonomous system.

  • External 1 for routes that are external to the autonomous system, but are imported into OSPFv3 as Type 1 external routes.

  • External 2 for routes that are external to the autonomous system, but are imported into OSPFv3 as Type 2 external routes.

  • NSSA External 1 for routes that are external to the autonomous system, but are imported into OSPFv3 in an NSSA for IPv6 as Type 1 external routes.

  • NSSA External 2 for routes that are external to the autonomous system, but are imported into OSPFv3 in an NSSA for IPv6 as Type 2 external routes.

You can click Edit (), or use the right-click menu to cut, copy, past, insert, and delete summary prefixes.

• IPv6 Prefix/Length—The IPv6 prefix and prefix length label. Select one from the list or click Add () to add a new network object. See Network for the procedure for adding networks.

• Advertise— Advertises routes that match the specified prefix and mask pair. Uncheck this check box to suppress routes that match the specified prefix and mask pair.

• (Optional) Tag—A value that you can use as a match value for controlling redistribution through route maps.

You can click Edit to edit, or use the right-click menu to cut, copy, past, insert, and delete areas.

• Interface—The interface you are configuring.

• Enable OSPFv3—Enables OSPFv3.

• OSPF Process—Choose 1 or 2.

• Area—The area ID for this process.

• Instance —Specifies the area instance ID to be assigned to the interface. An interface can have only one OSPFv3 area. You can use the same area on multiple interfaces, and each interface can use a different area instance ID.

• Filter Outgoing Link Status Advertisements—Filters outgoing LSAs to an OSPFv3 interface. All outgoing LSAs are flooded to the interface by default.

• Disable MTU mismatch detection—Disables the OSPF MTU mismatch detection when DBD packets are received. OSPF MTU mismatch detection is enabled by default.

• Flood Reduction—Changes normal LSAs into Do Not Age LSAs, so that they don't get flooded every 3600 seconds across areas.

  OSPF LSAs are refreshed every 3600 seconds. In large OSPF networks, this can lead to large amounts of unnecessary LSA flooding from area to area.

• Point-to-Point Network—Lets you transmit OSPF routes over VPN tunnels. When an interface is configured as point-to-point, non-broadcast, the following restrictions apply:

  • You can define only one neighbor for the interface.

  • You need to manually configure the neighbor.

  • You need to define a static route pointing to the crypto endpoint.

  • If OSPF over a tunnel is running on the interface, regular OSPF with an upstream router cannot be run on the same interface.

  • You should bind the crypto map to the interface before specifying the OSPF neighbor to ensure that the OSPF updates are passed through the VPN tunnel. If you bind the crypto map to the interface after specifying the OSPF neighbor, use the clear local-host all command to clear OSPF connections so that the OSPF adjacencies can be established over the VPN tunnel.

• Broadcast— Specifies that the interface is a broadcast interface. By default, this check box is checked for Ethernet interfaces. Uncheck this check box to designate the interface as a point-to-point, nonbroadcast interface. Specifying an interface as point-to-point, nonbroadcast lets you transmit OSPF routes over VPN tunnels.

• Cost—Specifies the cost of sending a packet on the interface. Valid values for this setting range from 0 to 255. The default value is 1. Entering 0 for this setting makes the router ineligible to become the designated router or backup designated router. This setting does not apply to interfaces that are configured as point-to-point, nonbroadcast interfaces.

  When two routers connect to a network, both attempt to become the designated router. The device with the higher router priority becomes the designated router. If there is a tie, the router with the higher router ID becomes the designated router.

• Priority—Determines the designated router for a network. Valid values range from 0 to 255.

• Dead Interval—Time period in seconds for which hello packets must not be seen before neighbors indicate that the router is down. The value must be the same for all nodes on the network and can range from 1 to 65535.

• Hello Interval— Time period in seconds between OSPF packets that the router will send before adjacency is established with a neighbor. Once the routing device detects an active neighbor, the hello packet interval changes from the time specified in the poll interval to the time specified in the hello interval. Valid values range from 1 to 65535 seconds.

• Retransmit Interval—Time in seconds between LSA retransmissions for adjacencies that belong to the interface. The time must be greater than the expected round-trip delay between any two routers on the attached network. Valid values range from 1 to 65535 seconds. The default is 5 seconds.

• Transmit Delay—Estimated time in seconds to send a link-state update packet on the interface. Valid values range from 1 to 65535 seconds. The default is 1 second.

• Type—Type of authentication. The available options are Area, Interface, and None. The None option indicates that no authentication is used.

• Security Parameters Index— A number from 256 to 4294967295. Configure this if you chose Interface as the type.

• Authentication—Type of authentication algorithm. Supported values are SHA-1 and MD5. Configure this if you chose Interface as the type.

• Authentication Key— When MD5 authentication is used, the key must be 32 hexadecimal digits (16 bytes) long. When SHA-1 authentication is used, the key must be 40 hexadecimal digits (20 bytes) long.

• Encrypt Authentication Key—Enables encryption of the authentication key.

• Include Encryption— Enables encryption.

• Encryption Algorithm—Type of encryption algorithm. Supported value is DES. The NULL entry indicates no encryption. Configure this if you chose Include Encryption.

• Encryption Key—Enter the encryption key. Configure this if you chose Include Encryption.

• Encrypt Key—Enables the key to be encrypted.

• Link Local Address—The IPv6 address of the static neighbor.

• Cost—Enables cost. Enter the cost in the Cost field, and check the Filter Outgoing Link State Advertisements if you want to advertise.

• (Optional) Poll Interval—Enables the poll interval. Enter the Priority level and the Poll Interval in seconds.

• Adjacency Changes—Defines the adjacency changes that cause syslog messages to be sent.

  By default, a syslog message is generated when an OSPF neighbor goes up or down. You can configure the router to send a syslog message when an OSPF neighbor goes down and also a syslog for each state.

  • Adjacency Changes—Causes the threat defense device to send a syslog message whenever an OSPF neighbor goes up or down. This setting is checked by default.

  • Include Details—Causes the threat defense device to send a syslog message whenever any state change occurs, not just when a neighbor goes up or down. This setting is unchecked by default.

• Administrative Route Distances—Allows you to modify the settings that were used to configure administrative route distances for inter-area, intra-area, and external IPv6 routes. The administrative route distance is an integer from 1 to 254. The default is 110.

• Default Information Originate—Check the Enable check box to generate a default external route into an OSPFv3 routing domain and configure the following options:

  • Always Advertise—Will always advertise the default route whether or not one exists.

  • Metric—Metric used for generating the default route. Valid metric values range from 0 to 16777214. The default value is 10.

  • Metric Type—The external link type that is associated with the default route that is advertised into the OSPFv3 routing domain. Valid values are 1 (Type 1 external route) and 2 (Type 2 external route). The default is Type 2 external route.

  • Route Map—Choose the routing process that generates the default route if the route map is satisfied or click Add () to add a new one. See Route Map to add a new route map.

Passive routing assists in controlling the advertisement of OSPFv3 routing information and disables the sending and receiving of OSPFv3 routing updates on an interface.

• Arrival—Specifies the minimum delay in milliseconds that must pass between acceptance of the same LSA arriving from neighbors. The range is from 0 to 6000,000 milliseconds. The default is 1000 milliseconds.

• Flood Pacing—Specifies the time in milliseconds at which LSAs in the flooding queue are paced in between updates. The configurable range is from 5 to 100 milliseconds. The default value is 33 milliseconds.

• Group Pacing—Specifies the interval in seconds at which LSAs are collected into a group and refreshed, check summed, or aged. Valid values range from 10 to 1800. The default value is 240.

• Retransmission Pacing—Specifies the time in milliseconds at which LSAs in the retransmission queue are paced. The configurable range is from 5 to 200 milliseconds. The default value is 66 milliseconds.

• LSA Throttle—Specifics the delay in milliseconds to generate the first occurrence of the LSA. The default value is 0 millisecond. The minimum specifies the minimum delay in milliseconds to originate the same LSA. The default value is 5000 milliseconds. The maximum specifies the maximum delay in milliseconds to originate the same LSA. The default value is 5000 milliseconds.

  Note	For LSA throttling, if the minimum or maximum time is less than the first occurrence value, then OSPFv3 automatically corrects to the first occurrence value. Similarly, if the maximum delay specified is less than the minimum delay, then OSPFv3 automatically corrects to the minimum delay value.

• SPF Throttle—Specifies the delay in milliseconds to receive a change to the SPF calculation. The default value is 5000 milliseconds. The minimum specifies the delay in milliseconds between the first and second SPF calculations. The default value is 10000 milliseconds. The maximum specifies the maximum wait time in milliseconds for SPF calculations. The default value is 10000 milliseconds.

  Note	For SPF throttling, if the minimum or maximum time is less than the first occurrence value, then OSPFv3 automatically corrects to the first occurrence value. Similarly, if the maximum delay specified is less than the minimum delay, then OSPFv3 automatically corrects to the minimum delay value.

When enabled, it indicates that the helper router will terminate the process of restarting the router if it detects that there is a change to a LSA that would be flooded to the restarting router, or if there is a changed LSA on the retransmission list of the restarting router when the graceful restart process is initiated.