Configuring Bfd For Rip (Bidirectional Detection In Bfd Control Packet Mode) - 3Com S7906E Configuration Manual

NextHop: 192.168.2.2
BkNextHop: 0.0.0.0
RelyNextHop: 0.0.0.0
Tunnel ID: 0x0
State: Inactive Adv
Tag: 0
# Enable RIP event debugging on Switch A.
<SwitchA> debugging rip 1 event
<SwitchA> terminal debugging
# When the link between Switch C and the Layer 2 switch fails, you can see that Switch A can quickly
detect the change.
%Jan 19 10:41:51:203 2008 SwitchA BFD/4/LOG:Sess[192.168.1.1/192.168.1.2, Vlan-interface
100,Ctrl], Sta: UP->DOWN, Diag: 1
*Jan 19 10:33:12:813 2008 SwitchA RM/6/RMDEBUG: RIP-BFD: Message Type Disable, Connect Type
Direct-connect, Pkt Type Echo, Src IP Address 192.168.1.1, Src IFIndex4, Nbr IP Address
192.168.1.2.
# Display the BFD information of Switch A.
You can see that Switch A has deleted the neighbor relationship with Switch C and thus no output
information is displayed.
<SwitchA> display bfd session
# Display the RIP routes of RIP process 1 on Switch A.
The RIP route learned from Switch C is no longer existent.
<SwitchA> display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
----------------------------------------------------------------------------
# Display the RIP route 100.1.1.0/24 learned on Switch A.
<SwitchA> display ip routing-table 100.1.1.0 24 verbose
Routing Table : Public
Summary Count : 1
Destination: 100.1.1.0/24
Protocol: RIP
Preference: 100
NextHop: 192.168.2.2
BkNextHop: 0.0.0.0
RelyNextHop: 0.0.0.0
Tunnel ID: 0x0
State: Active Adv
Tag: 0

Configuring BFD for RIP (Bidirectional Detection in BFD Control Packet Mode)

Network requirements
As shown in the following figure:
Interface: vlan-interface 200
BkInterface:
Neighbor : 192.168.2.2
Label: NULL
Age: 00h12m50s
Process ID: 2
Cost: 2
Interface: vlan-interface 200
BkInterface:
Neighbor : 192.168.2.2
Label: NULL
Age: 00h18m40s
1-29