Problem: Private traces can fail, but
network gadgets may not detect it. This can result in statistics getting stuck
because it can't be rerouted.
Reason: Traditional routing protocols rely
on timers, which may be sluggish to come across disasters.
Solution: BFD protocol acts like a quick
heartbeat test between routers. If one router would not respond fast
sufficient, the issue is detected, and site visitors can be rerouted to the
backup line.
Benefit: BFD allows avoid "facts
forwarding black holes" by way of quickly switching to backup paths,
improving community balance.
__________
CONFIGURATION
Configured
Loopback And Assign Ip Address on Router 1
R1(config)#inter
lo 0
R1(config-if-Loopback
0) #ip add 1.1.1.1 32
R1(config-if-Loopback 0) #inter g0/0
R1(config-if-GigabitEthernet
0/0)#ip add 12.0.0.1 30
Configured
Loopback And Assign Ip Address on Router 2
R2(config)#inter lo 0
R2(config-if-Loopback
0)#ip add 2.2.2.2 32
R2(config-if-Loopback 0)#inter g0/0
R2(config-if-GigabitEthernet 0/0)#ip add
12.0.0.2 30
2. Complete OSPF basic configurations.
R1(config)#router
ospf 1
R1(config-router)#router-id 1.1.1.1
R1(config-router)#network
1.1.1.1 0.0.0.0 area 0
R1(config-router)#network
12.0.0.1 0.0.0.0 area 0
R2(config)#router
ospf 1
R2(config-router)#router-id 2.2.2.2
R2(config-router)#network
2.2.2.2 0.0.0.0 area 0
R2(config-router)#network
12.0.0.2 0.0.0.0 area 0
3.
Complete interface BFD configuration and associate BFD with OSPF.
R1(config)#interface
gigabitEthernet 0/0
R1(config-if-GigabitEthernet
0/0)#bfd interval 100 min_rx 100 multiplier 3
R1(config-if-GigabitEthernet
0/0)#ip ospf bfd
R2(config)#interface
gigabitEthernet 0/0
R2(config-if-GigabitEthernet
0/0)#bfd interval 100 min_rx 100 multiplier 3
R2(config-if-GigabitEthernet
0/0)#ip ospf bfd
Comments
Post a Comment