mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-05-27 22:12:14 +00:00
da78f4fe92
The tests work with the default settings of BFD meaning that bfdd
is able to recognize a 'down' link after ~900ms so a route
recovery should be visible in the RIB after 1 second.
The following topology is used:
+---------+
| |
eth-rt2 (.1) | RT1 | eth-rt3 (.1)
+----------+ 1.1.1.1 +----------+
| | | |
| +---------+ |
| |
| 10.0.2.0/24 |
| |
| eth-rt1 | (.2)
| 10.0.1.0/24 +----+----+
| | |
| | RT3 |
| | 3.3.3.3 |
| | |
(.2) | eth-rt1 +----+----+
+----+----+ eth-rt4 | (.1)
| | |
| RT2 | |
| 2.2.2.2 | 10.0.4.0/24 |
| | |
+----+----+ |
(.1) | eth-rt5 eth-rt3 | (.2)
| +----+----+
| | |
| | RT4 |
| | 4.4.4.4 |
| | |
| +----+----+
| 10.0.3.0/24 eth-rt5 | (.1)
| |
| |
| 10.0.5.0/24 |
| |
| +---------+ |
| | | |
+----------+ RT5 +----------+
eth-rt2 (.2) | 5.5.5.5 | eth-rt4 (.2)
| |
+---------+
Route recovery is tested on RT1. The focus here lies on the two
different routes to RT5. Link failures are generated by taking
down interfaces via the mininet Python interface on RT2 and RT3.
Hence routes are supposed to be adjusted to use RT3 when a link
failure happens on RT2 or vice versa.
Note that only failure recognition and recovery is "fast". BFD
does not monitor a link becoming available again.
Signed-off-by: GalaxyGorilla <sascha@netdef.org>
20 lines
294 B
Plaintext
20 lines
294 B
Plaintext
log file ospf6d.log
|
|
!
|
|
hostname rt2
|
|
!
|
|
password 1
|
|
!
|
|
interface eth-rt1
|
|
ipv6 ospf6 network broadcast
|
|
ipv6 ospf6 bfd
|
|
!
|
|
interface eth-rt5
|
|
ipv6 ospf6 network broadcast
|
|
!
|
|
router ospf6
|
|
ospf6 router-id 2.2.2.2
|
|
interface eth-rt1 area 0.0.0.0
|
|
interface eth-rt5 area 0.0.0.0
|
|
redistribute connected
|
|
!
|