What Is Administrative Distance Manipulation in Networking?

Imagine you are the manager of a busy post office. Mail comes in from three different delivery services: USPS, FedEx, and a local courier. To keep things organized, you assign each service a trust level.

USPS gets a trust level of 1, FedEx gets a trust level of 2, and the local courier gets a trust level of 3. When two services bring mail for the same address, you always go with the service that has the lower trust level number. That is exactly what a router does with administrative distance.

Each routing protocol like OSPF or EIGRP has a default trust rating. OSPF has a default administrative distance (AD) of 110. EIGRP has a default AD of 90. Since 90 is lower than 110, the router will trust the EIGRP route over the OSPF route for the same destination network.

Now, what if you want the router to prefer OSPF instead? You can manipulate the administrative distance. You would change the AD of OSPF to something lower than 90, or change the AD of EIGRP to something higher than 110.

This is called administrative distance manipulation. It is like walking up to the post office manager and saying, from now on, treat the local courier as the most trusted service. By adjusting these numbers, network engineers tell the router which source of information it should trust most when there is a conflict.

This is very useful when you have a backup link that should only be used if the primary link fails. The manipulation is done through router configuration commands. It does not change the actual path or the speed of the link.

It only changes the router's decision-making process about which route to install in its routing table. Think of it as writing new rules for a traffic cop. The cop still sees all the cars, but now they follow a different set of instructions about which car gets to go first.

Administrative distance is a number from 0 to 255. The lower the number, the more trustworthy the source. A directly connected network has an AD of 0, meaning it is the most trusted.

A static route has an AD of 1. Then come various dynamic routing protocols. If you manipulate the distance, you are essentially changing the hierarchy of trust. This is a very precise tool and must be used carefully because changing the trust can cause routing loops or black holes if not done correctly.

In a certification exam, you will be expected to know the default AD values and how to change them using the distance command in router configuration mode. It is a fundamental skill for any network engineer working with multiple routing protocols.

Administrative distance (AD) is a numerical value between 0 and 255 that Cisco routers use to rate the trustworthiness of a routing information source. The lower the AD, the more reliable the source. By default, each routing protocol is assigned a standard AD. For example, directly connected routes have an AD of 0, static routes have an AD of 1, EIGRP summary routes have an AD of 5, external BGP has an AD of 20, internal EIGRP has an AD of 90, OSPF has an AD of 110, RIP has an AD of 120, and external EIGRP has an AD of 170. These defaults ensure that when a router learns about the same prefix from multiple protocols, it consistently selects the one with the lowest AD. Administrative distance manipulation refers to the deliberate alteration of these default values to influence route selection.

The manipulation is achieved through the distance command in Cisco IOS. The command can be applied in router configuration mode for a specific protocol. For instance, the command distance 95 under router eigrp 100 changes the AD for all EIGRP-learned routes to 95. This is a global change for that protocol. A more granular approach uses the distance prefix mask [access-list] command. This allows the network engineer to change the AD only for specific networks that match a given access list. For example, distance 130 10.0.0.0 0.255.255.255 can be used to change the AD for routes within the 10.0.0.0/8 range only. This selective manipulation is powerful in complex network topologies where different trust levels are needed for different parts of the network.

The manipulation primarily affects the Routing Information Base (RIB). When a routing protocol learns a new route, it compares the AD of that route with the AD of any existing route for the same network. If the new route has a lower AD, it replaces the old route in the RIB. If the new route has a higher AD, it is kept as a candidate but not installed. By manipulating AD, an engineer can force a protocol that normally would be less trusted to become the primary source of routing information. This is commonly used in dual-homed or multi-homed environments where different service providers connect via different routing protocols. It is also used in redistribution scenarios where routes from one protocol are injected into another. Without manipulation, the router might choose a suboptimal path based on the default AD values.

It is critical to understand that AD manipulation does not affect the metrics within a single routing protocol. For example, within OSPF, route selection is based on cost, not AD. Only when comparing routes from different protocols does AD matter. Additionally, AD is a Cisco property. Other vendors use similar concepts with different names, such as the route preference in Juniper JunOS. In multi-vendor environments, the network engineer must understand the equivalent parameters. The implementation of AD manipulation is a Layer 3 routing concept and is tested extensively in the Cisco CCNP Enterprise (350-401 ENCOR) exam, which is a core requirement for the CCNP certification. Mastery of this topic ensures the engineer can design resilient, policy-based routing architectures.

In real IT work, networks rarely run a single routing protocol. Large enterprises often run OSPF as the interior gateway protocol (IGP) and use BGP for connections to multiple internet service providers. Redistribution between these protocols is common. Without administrative distance manipulation, the router will always prefer the route with the lower default AD. But the default AD might not reflect the real-world reliability of each path. For example, an OSPF-learned route across a congested satellite link might have a default AD of 110, while an EIGRP-learned route across a fast fiber link has a default AD of 90. The router will choose the EIGRP route simply because of the lower AD, but that may be the wrong choice if the satellite link is actually more stable. By manipulating AD, the engineer can force the router to prefer the OSPF route.

Another critical use case is in failover designs. A network might use BGP as the primary path to the internet and a static default route as a backup. By default, a static route has an AD of 1, which is much lower than BGP's AD of 20. This means the static route will always be preferred, which defeats the purpose of having a primary BGP connection. The engineer must manipulate the AD of the static route to a higher value, such as 200, so that it only becomes active when the BGP route disappears. This is called floating static route and is a direct application of AD manipulation.

In cybersecurity contexts, AD manipulation can be used to steer traffic through inspection devices. By advertising a route with a lower AD from a security appliance, all traffic can be forced through that appliance for filtering. It also helps in traffic engineering and load balancing. When two protocols provide equal-cost paths, AD manipulation is not directly involved, but it can break ties when the protocols differ. Network engineers must also be aware that misconfiguration can cause routing black holes. For instance, if you change the AD of a legitimate OSPF route to a very high value, the router might prefer a less desirable route from another protocol, causing traffic to be dropped or delayed. Therefore, AD manipulation is a powerful but precise tool. It matters because it gives the engineer control over route selection in multi-protocol environments, which are the norm in modern enterprise and service provider networks. It is a fundamental skill for CCNP-level engineers who design and troubleshoot complex routing architectures.

In certification exams, administrative distance manipulation appears in several distinct question formats. The most common is the direct knowledge question. This type asks you to recall the default AD for a specific protocol. For example, What is the administrative distance of OSPF? The answer is 110. Another variant is the comparative question: A router receives the same route from OSPF (AD 110) and a static route (AD 1). Which route will be installed in the routing table? The answer is the static route because 1 is lower. These questions test your memorization of the default values.

Scenario-based questions are more complex. You are given a network topology with multiple routers running different protocols. The scenario might describe that the network engineer wants to ensure that a specific path is preferred, and you need to choose the correct configuration to manipulate the AD. For example, a router is running OSPF and EIGRP. The engineer wants the OSPF route to be preferred for a specific network. The correct answer would be to use the distance command under router ospf to set a lower AD, such as 85, for that network only. The question might provide a configuration snippet with the distance command and an access list, and you must identify which access list entry matches the intended network.

Troubleshooting questions present a problem. The routing table shows an unexpected path. You are given the running configuration of the router. You might see that a distance command has been applied incorrectly. For instance, the engineer used the command distance 200 under router eigrp, which made all EIGRP routes have a higher AD than OSPF. As a result, the router chooses the OSPF path even though the EIGRP path was intended to be primary. You must identify the misconfiguration and propose the fix. These questions require you to analyze the effect of the AD change on the routing table.

Design questions ask you to choose the best approach for a specific requirement. For example, a company has two internet connections. One is a fast fiber link learned via eBGP, and the other is a slower DSL link with a static default route. The requirement is that the fiber link should be primary. You need to configure a floating static route. The question might give you four configuration options, and you must select the one that sets the AD of the static route to a value higher than 20 (eBGP default AD), such as 25 or 200. These questions test your practical application of manipulation.

Finally, there are multi-choice questions with multiple correct answers. For instance, Which of the following can affect the administrative distance of a route? Options may include the distance command, the redistribution process, the network statement, and the metric. The correct answers are the distance command and, in some cases, the redistribution process can indirectly affect AD if the route type changes. These questions require a deep understanding of how AD is set and changed.

Administrative distance manipulation is a configuration technique that every Cisco network engineer must master, especially when working toward CCNP certification. The concept is straightforward on the surface but carries significant nuance in practice. At its core, you are changing the trust score that a router assigns to a routing protocol. This score, a number from 0 to 255, determines which route gets installed in the routing table when multiple protocols advertise the same prefix. The lower the score, the more the router trusts that source. The default scores are designed to give a sensible hierarchy, but real-world networks often require deviation from that hierarchy.

To implement AD manipulation, you use the distance command. The basic syntax under router configuration mode is distance AD-value. For example, router ospf 1 and then distance 95 changes the AD for all OSPF-learned routes to 95. This makes OSPF routes more preferred than EIGRP internal routes, which have a default AD of 90. But this is a global change. It affects every route learned by OSPF. That might be fine in a simple network, but in a complex network, you often need to change the AD for only a specific set of prefixes. For that, you use the extended syntax: distance AD-value source-ip wildcard-mask [access-list]. The source-ip and wildcard-mask define which router the update came from, and the access list matches the specific prefix. This gives you surgical precision. You can make a particular network learned from a particular neighbor more or less trustworthy without affecting other routes.

What can go wrong? The most common problem is creating a routing loop. Imagine you have two routers that both run OSPF and EIGRP, and they redistribute routes into each other. If you manipulate AD on one router without considering the effect on the other, you could cause a situation where Router A prefers an OSPF route to a network, and Router B prefers an EIGRP route to the same network. If they both think they have the best path, traffic can ping-pong between them. Another problem is creating a black hole. If you set the AD of a valid route too high, the router will ignore it in favor of a less reliable path, potentially dropping traffic. Always test changes in a lab or during a maintenance window.

From a broader IT perspective, AD manipulation fits into the larger discipline of traffic engineering. It works alongside route maps, prefix lists, and policy-based routing to give you complete control over traffic flow. In service provider networks, AD manipulation is used to influence which routes are preferred from different peers. In enterprise networks, it is the foundation of floating static routes for backup connectivity. Professionals working with Cisco devices should also be aware that the show ip route command displays the AD of each route. Regularly reviewing this output helps catch unexpected changes. In summary, AD manipulation is not just an exam topic, it is a daily tool for ensuring that your network behaves exactly as you intend, even when multiple routing protocols are at play.