Skip to content

Administrative Distance

A router-local preference assigned to a route source so the routing information base can choose among candidate routes to the same prefix learned by otherwise incomparable mechanisms.

Version
v2 · 2026-09-07 · History
Domain-specific #
1244
Origin domain
computer networking
Subdomain
route selection and routing information bases
Aliases
Route preference, Route-source preference, Administrative route distance

Core Idea

Administrative distance is a router-local preference attached to the source of a route. It lets a routing information base choose among candidate routes to the same destination prefix when those routes were learned through mechanisms whose native metrics are not directly comparable—for example, a static route, OSPF, RIP, or BGP.

The recurring operation is:

same-prefix candidate routes + source-specific local preference + lower-is-better comparison + platform tie rules → active route or route set in the local routing table.

Cisco calls the value administrative distance; Junos documentation commonly calls it route preference and explicitly identifies that as administrative distance. The number is not a measured geographic distance, hop count, latency, or universal probability of truth.

Scope of Application

Administrative distance applies to IP routing implementations that maintain multiple candidate sources for a routing table. It appears in enterprise routing, service-provider routers, virtual routing and forwarding instances, network migrations, route redistribution, static/dynamic coexistence, and controlled failover designs.

The abstraction includes default source preferences, protocol-wide overrides, and finer-grained source or prefix adjustments where the platform supports them. It includes the use of a high-distance static route as a standby for a dynamically learned route. It also includes operational inspection of RIB entries that display both source distance and protocol metric.

Clarity

Use this diagnostic sequence:

  1. Confirm that the candidates are for the same routing table and destination prefix. 2. Identify how each route was learned and whether each source has already run its own best-path logic. 3. Read the effective local administrative distance or route preference after all policy overrides. 4. Prefer the lower value under the platform's documented comparison order. 5. If values tie, follow the platform's explicit tie or multipath rules rather than inventing a universal rule.

Manages Complexity

A router running several routing protocols receives claims produced by different algorithms and measurement units. Administrative distance reduces this heterogeneous arbitration problem to a small local ordering over sources. The router need not translate OSPF cost into RIP hops or BGP attributes into EIGRP composite metric.

Abstract Reasoning

Administrative distance licenses ordinal predictions. If two valid same-prefix candidates reach a RIB from different sources and all earlier eligibility checks pass, lowering one candidate's effective distance below the other normally makes it the preferred source. Raising a static route's distance above a dynamic source can make the static route float; withdrawal of the preferred route then triggers reevaluation and possible standby installation.

Knowledge Transfer

Within networking, the abstraction transfers across vendors as a role pattern: source label, local ordinal preference, same-prefix arbitration, active installation, and reevaluation. Literal commands and numbers must be remapped to the target operating system.

The portable skeleton is Prioritization: competing claims receive an ordering that determines which proceeds under a constraint. Selection describes the resulting survivor set. Fallback Path explains one engineered use when a secondary route is intentionally given a worse preference. These primes do not carry routing-specific separation among protocol metrics, RIB source arbitration, and forwarding lookup.

Relationships to Other Abstractions

Local relationship map for Administrative DistanceParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.AdministrativeDistanceDOMAINPrime abstraction: Prioritization — is a kind ofPrioritizationPRIME

Current abstraction Administrative Distance Domain-specific

Parents (1) — more general patterns this builds on

  • Administrative Distance is a kind of Prioritization Prime

    The minimal prospective parent is Prioritization.

Hierarchy paths (3) — routes to 3 parentless roots

Neighborhood in Abstraction Space

Administrative Distance sits in a sparse region of the domain-specific corpus (89th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08