Chapter 37: Advanced Routing, Routing Behavior, and Path Selection
This chapter follows the topics shown in the Networking chapter menu. Work through each section in order, then use the review questions to check recall and troubleshooting reasoning.
37.1 Routing Tables
A routing table contains destination prefixes and the forwarding information used to reach them. When multiple routes match, the most specific prefix is considered before route preference and metric.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.2 Connected Routes
Connected Routes affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.3 Static Routes
Static Routes affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.4 Default Routes
A default route is the least-specific route and is used when no more-specific destination prefix matches.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.5 Longest Prefix Match
Longest-prefix match chooses the route whose prefix contains the destination and has the greatest number of matching leading bits.
Example: place Longest Prefix Match in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.6 Dynamic Routing
Dynamic Routing affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.7 Metrics
Metrics is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Metrics in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.8 Hop Count
Hop Count is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Hop Count in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.9 Convergence
Convergence is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Convergence in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.10 Routing Loops
Routing Loops affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.11 Route Summarization
Route Summarization affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.12 ECMP
ECMP is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place ECMP in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.13 Floating Static Routes
Floating Static Routes affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.14 OSPF
OSPF is a link-state interior routing protocol. Routers exchange topology information, calculate shortest paths, and converge when the network changes.
Example: place OSPF in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.15 OSPF Cost
OSPF is a link-state interior routing protocol. Routers exchange topology information, calculate shortest paths, and converge when the network changes.
Example: place OSPF Cost in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.16 OSPF Areas
OSPF is a link-state interior routing protocol. Routers exchange topology information, calculate shortest paths, and converge when the network changes.
Example: place OSPF Areas in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.17 Area 0
Area 0 is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Area 0 in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.18 OSPF Neighbors
OSPF is a link-state interior routing protocol. Routers exchange topology information, calculate shortest paths, and converge when the network changes.
Example: place OSPF Neighbors in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.19 BGP
BGP exchanges network reachability between routing domains and makes policy-based path decisions using attributes rather than only a simple shortest-path metric.
Example: place BGP in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.20 Autonomous Systems
Autonomous Systems is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Autonomous Systems in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.21 ASN
ASN is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place ASN in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.22 AS Path
PAT lets many inside hosts share one or a small number of public IPv4 addresses by tracking transport protocol and port mappings.
Example: place AS Path in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.23 IGP vs EGP
IGP vs EGP is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place IGP vs EGP in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.24 Redistribution Concepts
Redistribution Concepts is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Redistribution Concepts in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.25 Route Preference
Route Preference affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.26 Gateway Redundancy
Gateway Redundancy is one of the core topics in Advanced Routing, Routing Behavior, and Path Selection. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Gateway Redundancy in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
37.27 Missing Default Route
A default route is the least-specific route and is used when no more-specific destination prefix matches.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
37.28 Wrong Next Hop
Wrong Next Hop is a troubleshooting condition. The useful approach is to confirm symptoms, determine scope, identify the relevant layer, compare actual values with the intended design, test one theory at a time, and verify service after the fix.
Example: place Wrong Next Hop in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Confirm the symptom and determine whether the problem affects one host, one segment, one site, or many sites.
- Compare actual configuration and measurements with the intended design, baseline, or documentation.
- Change one variable at a time, verify the result, and document both the cause and the final fix.
37.29 Route Flapping
Ping is a basic reachability and round-trip-time test. A failed ping does not always prove the destination is down because policy may block ICMP.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
Command or data example
ping 192.0.2.1
37.30 Asymmetric Routing
Asymmetric Routing affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.