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

498
Total number of peers : 2 Peers in established state : 2
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2.0.1.1 200 7 10 0 0 00:01:05 Established
3.0.1.1 200 7 10 0 0 00:01:34 Established
# Display route 1.1.1.0/24 on Router C, and you can see that SecPath A and Router C
communicate through Router B.
<RouterC> display ip routing-table 1.1.1.0 24 verbose
Routing Table : Public
Summary Count : 2
Destination: 1.1.1.0/24
Protocol: BGP Process ID: 0
Preference: 0 Cost: 50
NextHop: 3.0.1.1 Interface: GigabitEthernet0/1
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 3.0.2.1 Neighbor : 3.0.1.1
Tunnel ID: 0x0 Label: NULL
State: Active Adv Age: 00h08m54s
Tag: 0
Destination: 1.1.1.0/24
Protocol: BGP Process ID: 0
Preference: 0 Cost: 100
NextHop: 2.0.1.1 Interface: GigabitEthernet0/2
BkNextHop: 0.0.0.0 BkInterface:
RelyNextHop: 2.0.2.1 Neighbor : 2.0.1.1
Tunnel ID: 0x0 Label: NULL
State: Invalid Adv Age: 00h08m54s
Tag: 0
The output shows that Router C has two routes to reach network 1.1.1.0/24: Router C<—>Router
B<—>SecPath A, which is the currently active route; Router C<—>Router D<—>SecPath A, which
is the backup route.
# Enable BFD debugging on Router C.
<RouterC> debugging bfd scm
<RouterC> debugging bfd event
<RouterC> debugging bgp bfd
<RouterC> terminal monitor
<RouterC> terminal debugging
# The following debugging information shows that: when the link between SecPath A and Router
B fails, Router C can quickly detect the link failure.
%Nov 5 11:42:24:172 2009 RouterC BFD/5/BFD_CHANGE_FSM:
Sess[3.0.2.2/3.0.1.1,13/17,GigabitEthernet0/1,Ctrl], Sta: UP->DOWN, Diag: 1
%Nov 5 11:42:24:172 2009 RouterC BGP/5/BGP_STATE_CHANGED: 3.0.1.1 state is changed
from ESTABLISHED to IDLE.
*Nov 5 11:42:24:187 2009 RouterC RM/6/RMDEBUG: BGP_BFD: Recv BFD DOWN msg, Src IP
3.0.2.2, Dst IP 3.0.1.1, Instance ID 0.