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

818
Summary Count : 1
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 : Active Adv Cost : 100
Tunnel ID : 0x0 Label : NULL
Age : 4635sec
The output shows that Router C has one route to reach network 1200::0/64, that is, Router
C<—>Router D<—>SecPath A.
Troubleshooting IPv6 BGP configuration
IPv6 BGP peer relationship not established
Symptom
Display BGP peer information by using the display bgp ipv6 peer command. The state of the connection
to the peer cannot become established.
Analysis
To become IPv6 BGP peers, any two routers need to establish a TCP session using port 179 and
exchange open messages successfully.
Solution
1. Use the display current-configuration command to check that the peer's AS number is correct.
2. Use the display bgp ipv6 peer command to check that the peer's IPv6 address is correct.
3. If a loopback interface is used, check that the loopback interface is specified with the peer
connect-interface command.
4. If the peer is not directly connected, check that the peer ebgp-max-hop command is configured.
5. If the peer ttl-security hops command is configured, check that the command is configured on the
peer, and the hop-count values configured on them are greater than the number of hops between
them.
6. Check that a valid route to the peer is available.
7. Use the ping command to check the connectivity to the peer.
8. Use the display tcp ipv6 status command to check the TCP connection.
9. Check whether an ACL for disabling TCP port 179 is configured.