This document describes how to troubleshoot common issues with Border Gateway Protocol (BGP).
There are no specific requirements for this document.
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
This document provides flowcharts for several options to troubleshoot BGP issues.
If you have the output of a show ip bgp, show ip bgp neighbors, show ip bgp summary, or show tech-support command from your Cisco device, you can use Cisco CLI Analyzer to display potential issues and fixes. To use Cisco CLI Analyzer, you must be a registered Cisco user.
BGP Main Flowchart

This is a sample log message that must be checked when the neighbor does not come up:
BGP_SESSION-5-ADJCHANGE: neighbor[ip address] IPv4 Unicast topology base removed from session Peer closed the session BGP_SESSION-5-ADJCHANGE: neighbor[ip address] IPv4 Unicast topology base removed from session Unknown path error
This is an example of ping with packet size, and enable does not contain fragment bit in the IP header:
Router#ping 10.10.10.2 size 1400 df-bit Type escape sequence to abort. Sending 5, 1400-byte ICMP Echos to 10.10.10.2, timeout is 2 seconds: Packet sent with the DF bit set !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/37/84 ms
If flapping occurs due to high CPU, refer to Troubleshooting High CPU Utilization on Cisco Routers.




| Revision | Publish Date | Comments |
|---|---|---|
4.0 |
26-Aug-2025
|
Recertification |
3.0 |
25-Oct-2022
|
Update and Recertification |
1.0 |
31-Mar-2002
|
Initial Release |