Part 1: Core Concepts (2 Marks)
- Link-State Routing: A class of dynamic routing protocols (such as OSPF and IS-IS) where every router constructs a comprehensive topological map (Link-State Database / LSDB) of the network by flooding Link-State Advertisements (LSAs) and computing the shortest path using Dijkstra’s Shortest Path First (SPF) algorithm.
- OSPF LSA Taxonomy:
- Type 1 (Router LSA): Generated by every internal router to describe its directly connected links within an area.
- Type 2 (Network LSA): Generated by the Designated Router (DR) on multi-access broadcast segments.
- Type 3 (Summary LSA): Generated by Area Border Routers (ABRs) to summarize routes between OSPF areas.
- Type 4 (ASBR Summary LSA): Injected by ABRs to announce the path to an Autonomous System Boundary Router (ASBR).
- Type 5 (AS External LSA): Injected by ASBRs to advertise routes redistributed from external autonomous systems.
- Type 7 (NSSA External LSA): Injected within a Not-So-Stubby Area (NSSA) and converted to Type 5 by the ABR.
- Autonomous System (AS): A collection of IP networks and routers under a single administrative domain operating a common interior gateway routing policy (identified by a globally unique 16-bit or 32-bit ASN assigned by IANA/APNIC).
- Border Gateway Protocol (BGP-4): The de facto inter-domain path-vector routing protocol (RFC 4271) that exchanges Network Layer Reachability Information (NLRI) over reliable TCP connections (port 179) between independent Autonomous Systems.
- BGP Path Attributes:
- Well-Known Mandatory: AS_PATH, NEXT_HOP, ORIGIN (must be present in every BGP UPDATE message).
- Well-Known Discretionary: LOCAL_PREF, ATOMIC_AGGREGATE (recognized by all implementations; presence is optional).
- Optional Transitive: COMMUNITY, AGGREGATOR (passed to downstream peers even if unrecognized).
- Optional Non-Transitive: Multi-Exit Discriminator (MED / metric) (evaluated locally; stripped when crossing AS boundaries).
Part 2: Structural Frameworks (10 Marks)
1. Multi-Area OSPF vs. Autonomous System Inter-Domain Architecture
AUTONOMOUS SYSTEM (AS 100)
- +--------------------+ +--------------------+
- | Stub Area 1 | | NSSA Area 2 |
- | Internal Routers | | ASBR -> External |
- +---------+----------+ +---------+----------+
- | (Type 3 LSA) | (Type 7 LSA)
- v v
- +---------+-------------------------------+----------+
- | Backbone Area 0 (Transit Core) |
- | ABR 1 ABR 2 |
- +-------------------------+---------------------------+
- | (Edge eBGP Session)
- TCP Port 179
- v
- AS 200 (Upstream ISP / NPIX Peering Exchange)
2. Complete 8-Step BGP Best Path Selection Decision Process
When a BGP router receives multiple paths toward the same NLRI prefix, it executes the following deterministic elimination ladder:
- Highest Weight: Cisco/vendor-proprietary local parameter (0-65535, default 32768 for locally generated routes).
- Highest LOCAL_PREF: Standard attribute (default 100) evaluated across the entire iBGP domain to choose outbound exit point.
- Locally Originated: Prefer routes originated locally via
networkoraggregate-addressstatements over redistributed routes. - Shortest AS_PATH: Path with the lowest number of AS hops (AS prepending increases length to discourage inbound traffic).
- Lowest ORIGIN Code: Prefer IGP (
i) over EGP (e), and EGP over Incomplete (?). - Lowest MED: Influences inbound traffic from neighboring AS (only compared if neighbor AS is identical).
- eBGP over iBGP: Prefer external eBGP path over internal iBGP learned path.
- Lowest IGP Metric to BGP NEXT_HOP: Path reachable via the closest internal IGP next hop.
- Tie-Breakers: Lowest BGP Router ID, oldest eBGP route, and lowest neighbor IP address.
Part 3: Distinction Tables
| Basis of Comparison | Interior Gateway Protocol (OSPFv2 / OSPFv3) | Exterior Gateway Protocol (BGP-4) |
|---|---|---|
| Protocol Class | Hierarchical Link-State Protocol | Path-Vector Inter-Domain Protocol |
| Operational Scope | Inside a single administrative domain (IGP) | Between disparate Autonomous Systems (EGP) |
| Transport Layer Protocol | Raw IP protocol number 89 | TCP connection over port 179 |
| Metric / Decision Basis | Cost (inversely proportional to interface bandwidth) | Policy-driven multi-attribute decision vector (AS_PATH, LOCAL_PREF, MED) |
| Convergence Speed | Rapid sub-second to low-second SPF convergence | Deliberately dampened (MRAI timer) to prevent global internet route flapping |
| Scalability Limit | Tens of thousands of internal routes (limited by LSDB) | Over 950,000+ full internet DFZ routing table entries |
| Split-Horizon Rule | Not applicable (uses SPF loop-free graph) | iBGP mesh requires full-mesh or Route Reflectors to prevent routing loops |
Part 4: Worked Problems & Exam Traps
Problem Archetype: Calculating OSPF Cost and Resolving iBGP Full-Mesh Scaling
Question: An enterprise network has a 10 Gbps core link and a 1 Gbps branch link. Using default reference bandwidth (
- Default OSPF Cost Formula:
- For 1 Gbps (
bps): (minimum integer cost is 1). - For 10 Gbps (
bps): . - Problem: Both 1 Gbps and 10 Gbps links receive cost 1!
- Remedy: Reconfigure reference bandwidth on all routers:
auto-cost reference-bandwidth 100000(100 Gbps), yielding Cost 100 for 1 Gbps and Cost 10 for 10 Gbps.
- For 1 Gbps (
- iBGP Full-Mesh Formula:
- Scaling Remedy: Deploy BGP Route Reflectors (RR) or BGP Confederations to reduce peering complexity from
to .
- Scaling Remedy: Deploy BGP Route Reflectors (RR) or BGP Confederations to reduce peering complexity from
TU Exam Trap: In BGP exam questions, students frequently claim that BGP uses hop count like RIP because it uses
AS_PATH. This is mathematically false:AS_PATHcounts autonomous system boundaries traversed, not individual router hops. A route with 1 AS hop through 50 core routers is strictly preferred over 2 AS hops through 2 routers! Furthermore, remember thatLOCAL_PREFexits your AS (outbound traffic control), whileAS_PATHprepending influences external traffic entering your AS (inbound traffic control).