BGP Routing Protocol
So what is BGP? In this series of posts I will be explaining the main principles of BGP. BGP–Border Gateway Protocol–is the de facto core…
Read moreBGP (Border Gateway Protocol) is a path-vector routing protocol that enables autonomous systems to exchange reachability information and manage internet routing through policy-based route selection rather than shortest-path metrics. Organizations including internet service providers, cloud providers, and enterprises rely on BGP to announce address prefixes, control traffic flow, and implement multihoming strategies across interconnected networks. Proper BGP management requires careful attention to prefix filters, route origin validation, and session monitoring to prevent outages, route leaks, and traffic misdirection that can result from misconfigurations or policy errors.
BGP routers form sessions with configured neighbors, exchange the prefixes they can reach, and each router chooses a best path per prefix based on attributes and local policy.
BGP sends incremental updates after the initial exchange instead of periodically resending the full table. If a session fails or the hold timer expires, the router withdraws the routes learned from that peer.
A neighbor that cycles between Active and Idle usually points to a failed TCP connection on port 179. Common causes are a firewall or ACL blocking the port, a wrong neighbor address, or a source interface mismatch on the peer.
Without inbound and outbound prefix filters, a multihomed network can re-advertise one provider's routes to another and attract transit traffic it cannot carry. The symptom is saturated links and sudden latency changes after a policy change.
Sessions that drop with a hold timer expired notification often reflect packet loss, CPU starvation or an MTU problem that stalls large UPDATE messages. Each flap withdraws and re-announces prefixes, which causes churn for downstream peers.
A route can appear in the BGP table but never become the best path when its next hop cannot be resolved. This often occurs with internal BGP when the next hop is an external peer address that is not carried in the interior routing protocol.
Traffic may take a longer or more expensive path because attributes such as local preference are evaluated before AS path length. Engineers often expect the shortest AS path to win and misread the decision order.