325
Peer support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support BGP route AS4 capability
Address family IPv6 Unicast: advertised and received
Received: Total 8 messages, Update messages 1
Sent: Total 8 messages, Update messages 1
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Peer preferred value: 0
IPsec profile name: policy002
Routing policy configured:
No routing policy is configured
The output shows that IBGP and EBGP peers are established and both sent and received IPv6 BGP
packets are encapsulated by IPsec.
Troubleshooting BGP
Symptom
Display BGP peer information by using the
display bgp peer ipv4 unicast
or
display bgp peer ipv6
unicast
command. The state of the connection to a peer cannot become established.
Analysis
To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange
Open messages successfully.
Solution
1.
Use the
display current-configuration
command to verify the current configuration, and verify that
the peer's AS number is correct.
2.
Use the
display bgp peer ipv4 unicast
or
display bgp peer ipv6 unicast
command to verify that the
peer's IP address/IPv6 address is correct.
3.
If a loopback interface is used, verify that the loopback interface is specified with the
peer
connect-interface
command.
4.
If the peer is a non-direct EBGP peer, verify that the
peer ebgp-max-hop
command is configured.
5.
Verify that a valid route to the peer is available.
6.
Use the
ping
command to verify the connectivity to the peer.
7.
Use the
display tcp verbose
or
display ipv6 tcp verbose
command to verify the TCP connection.
8.
Verify that no ACL rule is applied to disable TCP port 179.