Skip to content
7LayerX

Routing / Field note

A layered checklist for BGP neighbor troubleshooting

Separate BGP transport, session, policy, and route-advertisement problems with a repeatable peer checklist.

7LayerX Editorialupdated 2 min readBGPTCP

BGP troubleshooting benefits from separating the transport connection from the BGP session and the routes exchanged over that session. A peer can be reachable while the session is down, and a session can be established while no useful routes are accepted.

The commands below use Cisco IOS-style examples. Check your platform's command reference before applying them to production equipment.

Check peer reachability

Confirm that the peer address is reachable using the source address configured for BGP. For eBGP peers that are not directly connected, verify the intended multihop behavior and route to the remote peer.

show ip route 192.0.2.2
ping 192.0.2.2 source 192.0.2.1
show ip interface brief

Remember that BGP uses TCP port 179. A firewall or control-plane policy can block the session even when ICMP succeeds.

Read the session state

show ip bgp summary
show ip bgp neighbors 192.0.2.2

An Idle or Active state often points to connection establishment, peer configuration, or reachability. An established session with zero accepted prefixes points toward address-family activation, policy, or the remote advertisement rather than basic transport.

Compare peer configuration

Check the local and remote autonomous system numbers, peer address, update source, address-family activation, and authentication settings. When a loopback is used, verify that the update source and reachability path match the design on both routers.

show running-config | section router bgp
show ip bgp neighbors 192.0.2.2

Follow routes through policy

For an established session, inspect received and advertised routes using the commands supported by the platform. Compare prefix filters, route maps, communities, and next-hop handling. A route visible in a received view may still be rejected from the local routing table by policy or best-path selection.

show ip bgp neighbors 192.0.2.2 routes
show ip bgp neighbors 192.0.2.2 advertised-routes
show ip route bgp

Change one variable at a time

Record the session state and route counts before and after a change. Verify both control-plane status and the intended data-plane reachability; an established BGP session alone does not prove that application traffic will follow the expected path.

Key takeaway

Work from transport, to session configuration, to address-family and policy, then to route selection and forwarding. Each stage gives a narrower set of causes to investigate.

Pass it along

Found this useful? Share it.

Choose a platform or copy the direct link.

LinkedInXFacebook

Continue reading

Reader signal

Was this useful?

Your feedback helps shape the next field note and lab.

… views

Views count when this page opens. You can change or remove your vote during this tab session.