Evaluating Route Trustworthiness Using Administrative Distance in Network Routing
Dynamic routing architectures often run multiple routing protocols simultaneously across enterprise network fabrics. When a router learns multiple paths to the exact same destination prefix from different sources, it requires a definitive metric to select the most reliable path. Administrative Distance (AD) serves as the fundamental tie-breaking mechanism used by modern routers to rate the trustworthiness or believability of a routing information source, ensuring only the most dependable path installs into the active routing information base (RIB).
Fundamental Operating Principles of Administrative Distance
Routers evaluate routing updates through a structured hierarchy before committing paths to hardware forwarding tables:
- Inherent Trust Rating: Administrative Distance assigns an integer value ranging from 0 to 255 to each route source, with lower numbers representing a higher degree of protocol reliability and administrative trust.
- Tie-Breaking Priority: When a router receives routes for identical network prefixes with matching subnet masks from disparate protocols, the route with the lowest AD automatically wins and populates the routing table.
- Separation from Routing Metrics: Internal protocol metrics—such as bandwidth, delay, hop count, or cost—only compare routes learned within the exact same protocol. Administrative Distance operates at a higher abstraction layer to compare routes learned between entirely different protocols.
- Unroutable Threshold (AD 255): An Administrative Distance value of 255 represents complete untrustworthiness, instructing the router to reject the route entirely and never install it into the forwarding table.
Standard Protocol Trust Hierarchies
Networking vendors implement standard default Administrative Distance ratings across primary routing sources:
- Directly Connected Interfaces (AD 0): Hardware interfaces physically connected to a local subnet represent absolute trust and take precedence over every other route source.
- Static Routes (AD 1): Manually configured route entries created by network engineers receive immediate priority over dynamic routing protocols by default.
- External BGP (eBGP - AD 20): Border Gateway Protocol routes learned from external autonomous systems carry high authority to maintain predictable inter-domain internet traffic paths.
- Internal EIGRP (AD 90): Cisco's Enhanced Interior Gateway Routing Protocol carries higher default trust than competing interior protocols due to its rapid convergence mechanics.
- Open Shortest Path First (OSPF - AD 110): The open-standard link-state protocol provides consistent path calculations across complex enterprise topologies.
- Intermediate System to Intermediate System (IS-IS - AD 115): A robust link-state protocol frequently deployed in massive service provider backbones.
- Routing Information Protocol (RIP - AD 120): A legacy distance-vector protocol carrying lower trust due to slow convergence times and reliance on basic hop counts.
- Internal BGP (iBGP - AD 200): Routes shared between routers inside the same autonomous system intentionally carry low default trust to ensure internal paths rely on interior gateway protocols (IGPs) for underlying reachability.
Strategic Engineering Applications of Administrative Distance
Engineers actively manipulate default Administrative Distance values to implement advanced traffic control and high-availability topologies:
- Floating Static Routes: By manually configuring a static route with an AD higher than the active dynamic protocol (such as AD 130 over OSPF’s AD 110), the static route stays dormant and automatically takes over traffic forwarding only if the dynamic link fails.
- Route Redistribution Control: When translating routes between disparate protocols (e.g., merging an acquired company’s OSPF network into an existing EIGRP backbone), adjusting AD prevents suboptimal routing loops and asymmetric routing paths.
- Traffic Steering Policies: Modifying AD values allows network architects to favor private leased-line circuits (like MPLS) for primary corporate traffic while keeping public VPN links as secondary, failover paths.
- Prevention of Black-Hole Routing: Tuning distance values ensures summary discard routes or default gateways do not override more specific internal enterprise paths during partial network partitions.