Configuring IPv6 OSPFv3 Interfaces in Gaia Portal
|
Important - In a Cluster |
-
From the left navigation tree, click Advanced Routing > IPv6 OSPF.
-
In the Interfaces section, click Add.
-
In the Interface field, select the applicable interface.
-
In the Area field, select the area to assign to this interface.
Note - An entry for the Backbone area appears even if it is disabled.
-
In the Hello Interval field, enter the time.
Description
Configures the delay time between Hello packets on this interface.
The OSPFv3 Hello Protocol is responsible for establishing and maintaining adjacencies (i.e. connections) between neighboring OSPFv3 routers.
For broadcast networks, the Hello is also used to dynamically discover neighbors.
Important - For a given link, this value must be the same for all OSPFv3 routers.
Range: 1-65535 seconds
Default: 10 seconds for broadcast networks, 30 seconds for point-to-point networks
-
In the Router Dead Interval field, enter the time.
Description
Configures the time after receipt of the last Hello packet, at which a neighbor is declared dead.
Typically this is four times the Hello interval.
Important - For a given link, this value must be the same for all OSPFv3 routers.
Range: 1-65535 seconds
Default: 40 seconds for broadcast networks, 120 seconds for point-to-point networks
-
In the Retransmit Interval field, enter the time.
Description
Configures the time between LSA retransmissions for this interface.
This value is also used when retransmitting database description and link state request packets.
This value should be much higher than the expected round-trip delay between any two routers on the network.
Being conservative helps avoid unnecessary retransmissions.
Important - For a given link, this value must be the same for all OSPFv3 routers.
Range: 1-65535 seconds
Default: 5 seconds
-
In the Link Cost field, enter the cost of using the given interface for a route.
Description
The higher the cost, the less preferred the interface.
This is overridden by routing policy - Route Redistribution Rules and Route Maps.
Range: 1-65535
Default: 1
-
In the Election Priority field, enter the priority used in the Designated Router (DR) election on the link.
Description
When two routers attempt to become the DR, the one with the higher priority is elected.
However, if there is already an elected DR, then it continues as the DR regardless of priority.
This prevents frequent changes in the DR state.
The priority is only applicable to shared-media like Ethernet.
A DR is not elected on point-to-point interfaces.
A router with priority 0 is not eligible to become the DR.
Range: 0-255
Default: 1
-
The Passive option controls the passive mode for this interface.
Description
When passive mode is enabled, the OSPFv3 interface does not send Hello packets.
This means that the link does not form any adjacencies.
Passive mode enables the network associated with the interface to be included in the intra-area route calculation rather than redistributing the network into OSPFv3 and having it as an Autonomous System External (ASE) route.
In passive mode, all interface configuration information, with the exception of the associated area and the cost, is ignored.
Range: Selected, or Cleared
Default: Cleared (The interface sends Hello packets)
-
The Use Virtual Address option controls the VRRP mode for this interface.
Description
Important:
-
Configure this option on VRRP Cluster Members when the given interface is configured as a VRRP interface.
-
Do not configure this option on ClusterXL Cluster Members.
When this option is enabled, OSPFv3 uses the VRRP Virtual IP Address associated with the VRRP interface instead of the physical IP address.
In addition, OSPFv3 only runs when this router is the VRRP Master for the given interface.
Range: Selected, or Cleared
Default: Cleared
-
-
The IP Reachability Detection option controls BFD (Bidirectional Forwarding Detection) for each neighbor, from which it hears on this interface.
Description
Directs OSPFv3 to start BFD (Bidirectional Forwarding Detection) for each neighbor, from which it hears on this interface.
The BFD session is started only after OSPFv3 transitions to 'Full' state with the neighbor.
Once the BFD session is up, OSPFv3 responds to changes in BFD state.
If a neighbor does not have BFD configured or it does not respond to BFD control packets, it does not impact OSPFv3 operation. OSPFv3 can operate with both BFD and non-BFD neighbors on the same interface.
Before you enable this option, see IP Reachability Detection.
-
Make sure the Firewall policy allows traffic to the UDP port 3784 in both directions.
-
Make sure the SmartConsole
Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on. topology is correct (issues with incorrect Firewall topology can cause anti-spoofing to interfere with BFD traffic).
Range: Selected, or Cleared
Default: Selected
-
-
In the Security field, select the applicable option.
Description
To use IPsec Routing:
-
In the Security field, select IPsec
-
In the Security Association field, select the applicable Security Association SPI. See IPsec Routing.
Range: None, or IPsec
Default: None
-
-
Click Save.