Resolving BGP Neighbors Stuck in ACTIVE State

One of the most common issues network engineers face when standing up new WAN links is a BGP peering session that refuses to move past the ACTIVE state.

1. The Meaning of ACTIVE

In the BGP finite state machine, ACTIVE means the router is actively trying to establish a TCP connection on port 179 to the peer, but is failing.

This is almost always a TCP connectivity issue.

Verifying Neighbor Status

Let's check the BGP summary on a Juniper router:

user@router> show bgp summary
Groups: 1 Peers: 1 Down peers: 1
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0

0          0          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
10.0.0.2              65001          0          0       0       0        5:20 Active

2. Common Culprits

Missing Route to Peer

If you are peering over loopbacks (eBGP multihop), your router must have an IGP or static route to the remote loopback address.

TCP Port 179 Blocked

Ensure there are no firewall filters dropping TCP/179.

Asymmetric Routing / Source IP Mismatch

If the peer expects packets from 192.168.1.1, but your router is sending them from its physical interface IP 172.16.0.1, the remote side will silently drop them.

You must specify the update-source!

By ensuring Layer 3 reachability and matching source IPs, your BGP state should quickly transition from ACTIVE to ESTABLISHED.

Designing Robust BGP Routing Policies

To mitigate BGP peering issues and ensure high stability across WAN and enterprise edge routers:

1. BGP Keepalive and Hold Timers: Optimize BGP timers based on your network environment. For rapid detection of physical link failures, implement Bidirectional Forwarding Detection (BFD) instead of aggressive BGP timers to protect CPU resources.
2. Route Dampening: Configure BGP route dampening on internet-facing routers to prevent routing table instability caused by flapping external links.
3. Prefix-List Filtering: Implement strict prefix limits on your eBGP peers to prevent routing table exhaustion if a peer accidentally advertises their entire global routing table to your router.

Applying these industry standard policies protects your routing engines from external anomalies and guarantees high uptime for critical business transit paths.