H3C Technologies H3C SecPath F1000-E User Manual
Page 803
778
Hold Time: /
# Display routes to 2001:4::0/64 on SecPath A, and you can see that SecPath A communicates
with Router B through the Layer 2 switch.
<SecPathA> display ipv6 routing-table 2001:4::0 64 verbose
Routing Table :
Summary Count : 2
Destination : 2001:4:: PrefixLength : 64
NextHop : 2001::2 Preference : 10
IpPrecedence : QosLcId :
RelayNextHop : :: Tag : 0H
Neighbor : :: ProcessID : 0
Interface : GigabitEthernet0/1 Protocol : OSPFv3
State : Active Adv Cost : 1
Tunnel ID : 0x0 Label : NULL
Age : 4538sec
Destination : 2001:4:: PrefixLength : 64
NextHop : 2001:2::2 Preference : 10
IpPrecedence : QosLcId :
RelayNextHop : :: Tag : 0H
Neighbor : :: ProcessID : 0
Interface : GigabitEthernet0/2 Protocol : OSPFv3
State : Invalid Adv Cost : 2
Tunnel ID : 0x0 Label : NULL
Age : 4515sec
# Enable BFD debugging on SecPath A.
<SecPathA> debugging bfd scm
<SecPathA> debugging bfd event
<SecPathA> debugging ospfv3 event bfd
<SecPathA> terminal debugging
# After the link between Router B and the Layer 2 switch fails, SecPath A quickly detects the change
on Router B.
%Nov 5 11:37:43:062 2009 SecPathA BFD/5/BFD_CHANGE_FSM:
Sess[FE80::20F:FF:FE00:1202/ FE80::20F:FF:FE00:1200,15/15,
GigabitEthernet0/1,Ctrl], Sta: UP->DOWN, Diag: 1
%Nov 5 11:37:43:062 2009 SecPathA OSPFV3/5/OSPFv3_NBR_CHG: OSPFv3 1 Neighbor
2.2.2.2(GigabitEthernet0/1) from Full to Down.
*Nov 5 11:37:43:062 2009 SecPathA RM/6/RMDEBUG: OSPFv3 OSPFv3-BFD: Message Type rcv
BFD down, Connect Type direct-connect, Src IP Address FE80::20F:FF:FE00:1202, Dst IP
Address FE80::20F:FF:FE00:1200.
*Nov 5 11:37:43:062 2009 SecPathA RM/6/RMDEBUG: OSPFv3 OSPFv3-BFD: Message Type
delete session, Connect Type direct-connect, Src IP Address FE80::20F:FF:FE00:1202,
Dst IP Address FE80::20F:FF:FE00:1200.
# Display the BFD information of SecPath A. You can see that SecPath A has removed its neighbor
relationship with Router B and therefore no information is output.
<SecPathA> display bfd session
# Display routes to 2001:4::0/64 on SecPath A, and you can see that SecPath A communicates
with Router B through Router C.