OSPF Hellos
Last updated
Last updated
Load base.ipv4.and.ipv6.cfg
Configure OSPFv2 on R5, R6 and XR1 as follows:
Use a hello/dead timer of .333/1 on R5 and R6
Use a hello/dead timer of 1/3 on XR1
Configure OSPFv3 on R5, R6 and XR1 as follows:
Use a hello/dead timer of 2/6 on R5 and R6
Use a hello/dead timer of 3/9 on XR1
Enable OSPFv2/v3 on the following interfaces:
R5-R6
R6-XR1
Will all adjacencies come up?
Before we explore BFD, we should have a deep understanding how of the basic Hello timers work for each protocol.
In OSPF, the hello/dead timers must match between neighbors. This is one of the few protocols that requires this. For this reason, only the R5-R6 OSPFv2/v3 adjacency will come up in this lab.
If we use debug ip ospf hello on R6, we can see why the adjacency with XR1 will not form. The received (R) dead interval is 3 but the configured (C) interval is 1. Also, the (R) hello interval is 1 but the (C) hello interval is 0. XR1 does not support the sub-second hello. (This is because when the code for IOS-XR was being written, BFD already existed).
We can see this on XR as well with debug ospf 1 hello
The OSPF dead interval is by default 4x the Hello interval. If we only set the hello interval, the dead interval will automatically be calculated as 4x the Hello. For example, change XR1’s OSPF hello to 2 seconds and delete the dead-interval.
Interestingly, OSPFv3 does not support the sub-second hello for either IOS-XE or IOS-XR. By this time, BFD was already available, which is a better solution.
We can see that the OSPFv3 adj between XR1 and R6 also does not come up due to mismatched timers using debug ospfv3 hello