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

817
# Display route 1200::0/64 on Router C, and you can see that SecPath A and Router C
communicate through Router B.
display ipv6 routing-table 1200::0 64 verbose
Routing Table :
Summary Count : 2
Destination : 1200:: PrefixLength : 64
NextHop : 3001::1 Preference : 255
RelayNextHop : 3002::1 Tag : 0H
Neighbor : 3001::1 ProcessID : 0
Interface : GigabitEthernet0/1 Protocol : BGP4+
State : Active Adv Cost : 50
Tunnel ID : 0x0 Label : NULL
Age : 4538sec
Destination : 1200:: PrefixLength : 64
NextHop : 2001::1 Preference : 255
RelayNextHop : 2002::1 Tag : 0H
Neighbor : 2001::1 ProcessID : 0
Interface : GigabitEthernet0/2 Protocol : BGP4+
State : Invalid Adv Cost : 100
Tunnel ID : 0x0 Label : NULL
Age : 4515sec
The output shows that Router C has two routes to reach network 1200::0/64: 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.
debugging bfd scm
debugging bfd event
debugging bgp bfd
terminal monitor
terminal debugging
# The following debugging information shows that Router C can quickly detect the failure on
Router B.
%Nov 5 11:42:24:172 2009 RouterC BFD/5/BFD_CHANGE_FSM:
Sess[3002::2/3001::1,13/17,GigabitEthernet0/1,Ctrl], Sta: UP->DOWN, Diag: 1
%Nov 5 11:42:24:172 2009 RouterC BGP/5/BGP_STATE_CHANGED: 3001::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
3002::2, Dst IP 3001::1, Instance ID 0.
*Nov 5 11:42:24:187 2009 RouterC RM/6/RMDEBUG: BGP_BFD: Reset BGP session 3001::1
for BFD session down.
*Nov 5 11:42:24:187 2009 RouterC RM/6/RMDEBUG: BGP_BFD: Send DELETE msg to BFD,
Connection type DIRECT, Src IP 3002::2, Dst IP 3001::1, Instance ID 0.
# Display route 1200::0/64 on Router C, and you can see that SecPath A and Router C
communicate through Router D.
display ipv6 routing-table 1200::0 64 verbose
Routing Table :