H3C Technologies H3C SecPath F1000-E - Manual (Page 400)

375
Configuring BFD for RIP (bidirectional detection in BFD control
packet mode) at the CLI
Network requirements
As shown in Figure 252 :
• SecPath A is connected to Router C through Router B. GigabitEthernet 0/2 on SecPath A,
GigabitEthernet 0/1 on Router C, and GigabitEthernet 0/1 and GigabitEthernet 0/2 on Router B
run RIP process 1.
• Configure a static route to Router C on SecPath A, and configure a static route to SecPath A on
Router C. Enable BFD on GigabitEthernet 0/2 of SecPath A and GigabitEthernet 0/1 of Router C.
• SecPath A is connected to Router C through Router D. GigabitEthernet 0/1 on SecPath A runs RIP
process 2; GigabitEthernet 0/2 on Router C, and GigabitEthernet 0/1 and GigabitEthernet 0/2
on Router D run RIP process 1.
• Enable static route redistribution into RIP on SecPath A and Router C so that SecPath A and Router
C have routes to send to each other. SecPath A learns the static route sent by Router C, the outbound
interface is the interface connected to Router B.
• When the link between Router B and Router C fails, BFD can quickly detect the link failure and
notify it to RIP, and the BFD session goes down. In response, RIP deletes the neighbor relationship
with Router C and the route information received from Router C. Then, SecPath A learns the static
route sent by Router C, and the outbound interface of the route is the interface connected to Router
D.
Figure 252 Network diagram
Configuration procedure
1. Configure RIP basic functions and enable static route redistribution into RIP so that SecPath A and
Router C have routes to send to each other:
# Configure SecPath A.
<SecPathA> system-view
[SecPathA] rip 1
[SecPathA-rip-1] network 192.168.1.0
[SecPathA-rip-1] peer 192.168.2.2
[SecPathA-rip-1] undo validate-source-address