What Does iBGP Mean?

Imagine a large company with multiple branch offices, each having its own local manager. The CEO (representing an external network) sends a memo to one branch manager. For all branch managers to know the memo's contents, they must share it among themselves.

iBGP is like the internal memo-sharing system: it ensures every router inside the same company (autonomous system) knows about external routes learned from outside. Without iBGP, only the router that directly receives the external route would know about it, leaving others in the dark. This internal sharing is critical for consistent routing decisions and preventing traffic black holes within the organization.

iBGP (Internal Border Gateway Protocol) is a routing protocol defined in RFC 4271 that operates at the Application Layer (Layer 7) of the OSI model, though it is used to exchange network layer (Layer 3) reachability information. It runs over TCP port 179. iBGP is used to distribute BGP routes among routers within the same autonomous system (AS).

A key technical property is that iBGP does not change the AS_PATH attribute; routes learned via iBGP retain the same AS_PATH as when they were learned via eBGP. This behavior prevents routing loops because a router will not accept a route that contains its own AS number in the AS_PATH. However, it also means that iBGP requires a full mesh of TCP sessions (or the use of route reflectors or confederations) to ensure all routers receive all routes, since the BGP split-horizon rule prohibits advertising iBGP-learned routes to other iBGP neighbors.

iBGP uses the same path selection algorithm as eBGP, but the administrative distance for iBGP routes is 200 (vs. 20 for eBGP), making eBGP routes preferred. iBGP is critical for carrying Internet routes within an ISP or large enterprise, enabling policy-based routing and traffic engineering.

Understanding iBGP is crucial for IT professionals because it is the backbone of internal route distribution in BGP-based networks. Without iBGP, external routes learned by one router would not propagate to others, leading to routing black holes and inconsistent forwarding. iBGP also introduces unique challenges like the full mesh requirement and split-horizon rule, which are common exam topics and real-world design considerations.

Mastery of iBGP is essential for network engineers designing scalable ISP or enterprise networks, and it directly impacts troubleshooting scenarios involving missing routes or suboptimal path selection. On exams like CCNA and Network+, iBGP questions test your ability to distinguish it from eBGP and understand its operational constraints.

1. **Comparison Questions**: 'Which of the following is true about iBGP compared to eBGP?' Wrong answers often claim iBGP has a lower administrative distance or modifies AS_PATH. The correct answer highlights that iBGP operates within the same AS and does not change AS_PATH.

2. **Split-Horizon Questions**: 'A router learns a route via iBGP. To which of the following can it advertise this route?' Wrong answers include 'all iBGP neighbors' or 'eBGP neighbors only.'

The correct answer is 'eBGP neighbors only' because of the split-horizon rule. 3. **Design Questions**: 'What is required for iBGP to function correctly in a network with multiple routers?'

Wrong answers suggest using static routes or a single session. The correct answer is a full mesh of iBGP sessions or route reflectors. 4. **Troubleshooting Questions**: 'A router is not receiving an external route that its iBGP peer has.

What is the most likely cause?' Wrong answers include 'MTU mismatch' or 'AS_PATH loop.' The correct answer is that the next-hop IP is not reachable via an IGP.

iBGP (Internal Border Gateway Protocol) is a path-vector routing protocol used to exchange BGP routes between routers within the same autonomous system (AS). Its core purpose is to ensure that all routers in an AS have consistent knowledge of external routes learned via eBGP. Unlike eBGP, which modifies the AS_PATH by prepending its own AS number, iBGP does not change the AS_PATH.

This behavior prevents routing loops because a router will reject a route that contains its own AS number. However, it also creates a challenge: the BGP split-horizon rule states that a route learned via iBGP cannot be advertised to another iBGP neighbor. This means that for all routers to learn all routes, a full mesh of iBGP sessions is required.

In a network with n routers, this requires n(n-1)/2 sessions, which becomes unscalable. To solve this, route reflectors and confederations are used. A route reflector allows iBGP routes to be advertised to other iBGP neighbors, reducing the number of sessions.

iBGP uses TCP port 179 and typically runs between loopback interfaces for stability. The administrative distance for iBGP is 200, making it less preferred than eBGP (AD 20) and most IGPs. For iBGP to work, the next-hop IP address (often an eBGP peer) must be reachable via an IGP (like OSPF or EIGRP).

Key takeaway: iBGP is essential for internal route distribution in BGP networks, but it requires careful design to overcome its full mesh and next-hop reachability constraints.