Administrative Distance Explained: Managing Routing Protocol Priorities

🌐 Administrative Distance (AD) – The Hidden Decision Maker in Routing

Imagine multiple people giving you directions to the same place—but who do you trust more?

That’s exactly what Administrative Distance (AD) does in networking.

It helps routers decide which route source is more reliable.

---

📚 Table of Contents

• What is Administrative Distance?
• Math Behind AD (Simple)
• RIP Configuration
• EIGRP Configuration
• OSPF Configuration
• BGP Configuration
• CLI Outputs
• Modern Improvements
• Best Practices
• Key Takeaways

---

🧠 What is Administrative Distance?

Administrative Distance is a value that represents trust.

Lower value = more trusted route

Basic Rule:

\[ Best\ Route = \min(AD) \]

👉 Router always selects the route with the lowest AD.

---

📐 Simple Math Logic

Let’s say we have three routes:

Protocol	AD
RIP	120
OSPF	110
EIGRP	90

\[ Selected = \min(120, 110, 90) = 90 \]

✅ EIGRP wins.

---

📡 RIP Configuration

Router(config)#router rip Router(config-router)#network 192.168.15.0 Router(config-router)#distance 15 192.168.15.1 0.0.0.0 Router(config-router)#distance 200 192.168.15.0 0.0.0.255 Router(config-router)#distance 255

💡 Explanation

Different AD values are assigned based on source IP and network range.

---

⚡ EIGRP Configuration

Router(config)#router eigrp 111 Router(config-router)#network 192.168.16.0 Router(config-router)#distance eigrp 55 200

💡 Explanation

First value = internal routes, second = external routes.

---

🔄 OSPF Configuration

Router(config)#router ospf 66 Router(config-router)#distance ospf intra-area 105 Router(config-router)#distance ospf inter-area 115 Router(config-router)#distance ospf external 125

💡 Explanation

• Intra-area → same area
• Inter-area → different area
• External → outside OSPF

---

🌍 BGP Configuration

Router(config)#router bgp 65520 Router(config-router)#distance bgp 115 220 50

💡 Explanation

• External BGP
• Internal BGP
• Local routes

---

🖥️ CLI Output

Click to Expand

Router#show ip route

R 192.168.1.0 [120/1]
O 192.168.1.0 [110/2]
D 192.168.1.0 [90/3]

Selected Route: EIGRP (AD 90) 

---

🚀 Modern Improvements

• Support for prefix-lists
• Route-map integration
• Better debugging tools
• Granular AD control

---

🛠️ Best Practices

• Always test before deployment
• Use specific filters instead of global changes
• Avoid setting AD too low unless necessary
• Monitor routing behavior after changes

---

💡 Key Takeaways

• AD decides trust between routing protocols
• Lower AD = higher priority
• Math helps predict routing decisions
• Modern tools allow precise control

---

🎯 Final Thought

Administrative Distance is not just a number—it’s a decision-making system.

Master it, and you control how your network thinks.

Enhanced Static Route Tracking in Cisco ASA (Post-9.7): Configuration and Best Practices

🔥 Cisco ASA Route Tracking (Post 9.7) – Deep Dive Guide

Static route tracking in Cisco ASA has evolved significantly after version 9.7. What used to be manual and limited is now smarter, faster, and more scalable.

This guide explains not just configuration—but the logic, math, and real-world behavior behind it.

---

📚 Table of Contents

• Introduction
• What’s New in ASA 9.7+
• Failover Logic (Math Made Simple)
• Configuration Steps
• CLI Verification
• Practical Impact
• Key Takeaways
• Related Articles

---

📡 Introduction

Static route tracking ensures that when a primary path fails, a backup path automatically takes over—without manual intervention.

Before ASA 9.7, this required heavy SLA + tracking configuration.

Now? It's smarter.

---

🚀 What’s New in ASA 9.7+

• Support for TCP & HTTP monitoring
• Faster failover detection
• Simplified configuration
• Up to 255 tracking objects
• Continuous health monitoring

---

📐 Failover Logic Explained (Simple Math)

1. SLA Detection Timing

\[ Detection\ Time = Frequency \times Missed\ Probes \]

Example:

\[ 10s \times 3 = 30s \]

👉 If 3 probes fail, route is considered down after 30 seconds.

---

2. Route Preference (Administrative Distance)

\[ Primary\ Route\ AD < Backup\ Route\ AD \]

Example:

\[ 1 < 10 \]

👉 Lower AD = higher priority

---

3. Failover Decision Rule

\[ If\ SLA = Down \Rightarrow Use\ Backup\ Route \]

\[ If\ SLA = Up \Rightarrow Use\ Primary\ Route \]

---

4. Stability Logic

\[ Failover\ occurs\ only\ if\ consecutive\ failures > Threshold \]

Prevents false alarms due to temporary packet loss.

---

⚙️ Configuration Steps

Step 1: SLA Monitor

sla monitor 1 type echo protocol ipIcmpEcho 8.8.8.8 interface outside frequency 10 exit sla monitor schedule 1 life forever start-time now ---

Step 2: Tracking Object

track 1 rtr 1 reachability ---

Step 3: Primary Route

route outside 0.0.0.0 0.0.0.0 192.168.1.1 track 1 ---

Step 4: Backup Route

route outside 0.0.0.0 0.0.0.0 192.168.1.2 10

---

🖥️ CLI Verification

Click to Expand

show sla monitor statistics 1
show track
show route

---

🌍 Real-World Impact

Before	After
Slow failover	Fast failover ⚡
ICMP-only checks	TCP/HTTP checks 🌐
Manual configs	Simplified configs 🧠

---

💡 Key Takeaways

• ASA 9.7+ improves reliability significantly
• Math helps predict failover timing
• Tracking + SLA = intelligent routing
• Proper AD ensures correct backup usage

---

🎯 Final Thoughts

With ASA 9.7+, route tracking is no longer just configuration—it’s controlled, predictable network behavior powered by logic and timing.

Master the math, and you master the network.