BGP for Enterprise

BGP (Border Gateway Protocol) empowers enterprises with policy-driven control over Internet connectivity, multi-homing redundancy, traffic engineering, and secure peering with providers or partners. This pillar covers BGP essentials for corporate networks — from basic eBGP peering and route advertisement to advanced scaling with route reflectors, local preference manipulation, and integration with OSPF/EIGRP. Build resilient edge designs that optimize outbound paths, influence inbound traffic, and ensure failover without relying solely on default routes.

Multi-homed ISP redundancy & load balancing

Policy-based traffic engineering

Scalable iBGP without full mesh

Inbound/outbound path control

Introduction

Beginner Path - BGP Fundamentals

Grasp BGP Core Concepts

New to BGP in enterprise? Start here to understand peering, sessions, and why it’s different from IGPs.

Intermediate Path

Control Traffic & Redundancy

Implement multi-homing and influence path selection for reliable, optimized Internet access.

Advanced Path

Scale & Secure Enterprise BGP

Handle large sites, avoid full-mesh issues, and add security/policy depth for global enterprises.

Common Problems & Fast Fixes

BGP Neighbor Not Establishing

Stuck in Idle/Active/Connect → Fix: Verify neighbor IP/AS, reachability (ping), TCP 179 open, no ACL/firewall blocks, matching authentication.

Routes Missing in BGP Table

Not advertised → Fix: Check network statements, redistribute filters, next-hop reachable via IGP, no auto-summary issues.

Routes in BGP Table but Not in Routing Table

Not best path → Fix: Verify next-hop reachability (recursive lookup), lower AD (eBGP=20), clear soft-reconfig if needed.

Suboptimal Outbound Path / Traffic Blackhole

Fix: Check local preference, weight; ensure primary ISP has higher preference.

Fix: AS-path prepend on secondary, communities, or MED tweaks; verify ISP honors them.

BGP Flapping / Instability

Fix: Enable dampening, check for MTU mismatches, BFD timers, or prefix limits exceeded.

iBGP Full Mesh Scaling Issues

Too many peers → Fix: Deploy route reflectors or confederations.

Tools & Platforms Enterprises Use

Frequently Asked Questions

Why use BGP in an enterprise instead of static/default routes?

For multi-homing redundancy, automatic failover, policy control over paths, and influencing inbound/outbound traffic.

What’s the difference between eBGP and iBGP?

eBGP: Between different ASes (TTL=1 default, next-hop unchanged). iBGP: Same AS (TTL=255, next-hop preserved, requires full mesh or reflectors).

How does BGP choose the best path?

Highest weight → local preference → locally originated → shortest AS-path → lowest origin → lowest MED → eBGP over iBGP → lowest IGP metric → oldest → lowest router ID.

What is route reflection and why use it?

Route reflectors reduce iBGP peering needs (no split-horizon rule inside cluster); scales large enterprises without full mesh.

How to influence outbound traffic to prefer one ISP?

Set higher local preference on routes from primary ISP via route-map on inbound.

AS-path prepend on advertisements to secondary ISP, or use BGP communities/MED if ISP supports.

What causes BGP routes to be present but no traffic flow?

Next-hop unreachable (recursive lookup fails), IGP not advertising next-hop, or policy blackholing.

Download Your Cheat Sheet
Enter your email to get instant access to this cheat sheet. We'll also notify you when new cheat sheets are released.
No spam, ever. Your email is stored securely and never shared.