Cisco & Networking · Lesson 12
Routing Concepts & Dynamic Protocol Awareness
Learn how Cisco routers compare route sources, how RIP, OSPF, and EIGRP learn remote networks, and how to troubleshoot dynamic routing without replacing the design with random static routes.
The goal is protocol awareness, route-reading skill, and safe troubleshooting. You do not need to become an advanced routing engineer to recognize why a competition topology is not converging.
Lesson Snapshot
Learning objectives
Read the routing process before changing it
Explain how routers learn, compare, and select routes.
Distinguish connected, static, and dynamically learned routes.
Understand administrative distance, metric, and longest-prefix match at a practical competition level.
Recognize the purpose and basic behavior of RIP, OSPF, and EIGRP without overconfiguring a network blindly.
Inspect routing-protocol state safely before making changes.
Troubleshoot route-learning problems by separating neighbor, network, metric, and policy evidence.
Core idea
Routing protocols learn paths; the routing table chooses what to use
A router can know several possible paths, but only the best usable routes become active forwarding entries.
Competition warning
A missing dynamic route is evidence
Do not immediately replace it with a static route. The missing route may reveal an adjacency, area, AS, passive-interface, or advertisement problem that still needs to be fixed.
Core concepts
Six ideas behind route learning and selection
Routing table
The router's current collection of known destination networks and the paths it can use to reach them.
Route source
The mechanism that taught the router about a network, such as a connected interface, static configuration, RIP, OSPF, or EIGRP.
Administrative distance
A local preference value Cisco IOS uses when the same destination prefix is learned from different routing sources.
Metric
A value used by a routing protocol to compare multiple paths learned by that same protocol.
Longest prefix match
The forwarding rule that chooses the most specific matching destination route.
Convergence
The process by which routers learn about topology changes and settle on a consistent set of routes.
Route sources
Recognize where a route came from
| Source | Code | Learned by | Typical AD | Purpose |
|---|---|---|---|---|
| Connected | C | Operational Layer 3 interface | 0 | Represents a directly attached network. |
| Static | S | Manual ip route configuration | 1 | Provides an administrator-defined path. |
| EIGRP internal | D | EIGRP neighbor exchange | 90 | Learns internal routes dynamically on supported Cisco IOS devices. |
| OSPF | O | OSPF link-state routing | 110 | Learns routes through OSPF topology information and cost. |
| RIP | R | RIP distance-vector updates | 120 | Learns routes using hop count. |
These are common Cisco administrative-distance defaults. Exact behavior can be changed by configuration, so always inspect the actual device instead of relying only on memorized values.
Forwarding decision
How a router chooses one path
Find all matching routes
The router compares the destination IP against entries in the routing table.
Choose the longest prefix
The most specific matching network wins before administrative distance is considered.
Compare route sources if needed
If the same prefix is learned from different sources, administrative distance helps choose which source is preferred.
Compare metrics within the same protocol
If one routing protocol has multiple candidate paths to the same prefix, that protocol's metric helps choose the better path.
Resolve the next hop
The router determines the outgoing interface and next-hop reachability.
Forward the packet
The packet is sent toward the selected path if policy and interface state permit it.
Administrative distance
Compare route sources only after prefix length matches
Connected vs Static
Preferred: Connected
Connected routes normally have AD 0 while static routes default to AD 1.
Static vs OSPF
Preferred: Static
A normal static route with AD 1 is preferred over OSPF AD 110 for the same prefix.
EIGRP internal vs OSPF
Preferred: EIGRP internal
EIGRP internal commonly uses AD 90, lower than OSPF 110.
OSPF vs RIP
Preferred: OSPF
OSPF commonly uses AD 110 while RIP uses 120.
Metrics
Each routing protocol compares paths differently
RIP
Metric: Hop count
Preferred: Lower hop count
15 hops maximum usable; 16 represents unreachable.
OSPF
Metric: Cost
Preferred: Lower total cost
Cost is commonly derived from interface bandwidth using a reference bandwidth.
EIGRP
Metric: Composite metric
Preferred: Lower metric
Bandwidth and delay are major default inputs; exact calculation is more advanced than this lesson requires.
Protocol comparison
RIP, OSPF, and EIGRP at competition depth
RIP
Distance vector
Update style
Periodic routing updates
Strength
Simple and easy to understand.
Limitation
Slow convergence and a small hop-count ceiling make it unsuitable for many larger modern networks.
Competition focus
Recognize configuration, version, passive-interface, hop count, and missing network statements.
OSPF
Link state
Update style
Builds a topology database and exchanges link-state information.
Strength
Scales well and converges efficiently when configured correctly.
Limitation
More concepts are involved, including areas, neighbor states, router IDs, and cost.
Competition focus
Recognize areas, network participation, neighbor adjacency, interface cost, and route codes.
EIGRP
Advanced distance-vector / hybrid terminology
Update style
Forms neighbors and exchanges route information efficiently.
Strength
Fast convergence and strong Cisco integration on supported platforms.
Limitation
Historically Cisco-centric and uses protocol-specific concepts.
Competition focus
Recognize autonomous-system configuration, neighbors, passive interfaces, and route code D.
Cisco inspection
Read the protocol state before changing it
show ip routeReview the active IPv4 routing table and identify route sources.
show ip protocolsSummarize active routing protocols, network statements, passive interfaces, timers, and routing information sources where supported.
show running-config | section routerReview configured routing-process sections.
show ip interface briefConfirm Layer 3 interfaces are up and correctly addressed.
show ip ospf neighborReview OSPF neighbor adjacencies where OSPF is configured.
show ip ospf interface briefSummarize OSPF-enabled interfaces and areas on supported IOS versions.
show ip eigrp neighborsReview EIGRP neighbors where the feature is available.
show ip rip databaseReview RIP-learned routing information where supported.
show cdp neighbors detailCompare Layer 3 routing expectations with the actual Cisco neighbor topology.
Feature support varies
Packet Tracer devices do not always support the complete IOS routing feature set. Use the nearest available verification command and focus on neighbor state, route source, and end-to-end behavior.
RIP awareness
Simple distance-vector routing
Distance-vector behavior
RIP learns routes from neighboring routers and uses hop count as its metric.
Hop-count limit
RIP considers routes with 16 hops unreachable, which limits its scalability.
RIPv2
RIPv2 supports classless routing information and is the relevant modern RIP version for most labs.
Network statements
RIP configuration identifies directly connected networks whose interfaces participate in RIP.
Passive interfaces
A passive interface can advertise its connected network without sending routing updates out that interface, depending on protocol behavior.
Auto-summary awareness
Older classful summarization behavior can create confusing routes; labs often use no auto-summary where supported.
RIP configuration pattern
Inspect first, advertise only required networks
Inspect first
show ip routeshow ip protocolsshow running-config | section router ripEnter RIP process
configure terminalrouter ripversion 2Advertise connected networks
network 10.0.0.0network 192.168.10.0Disable classful auto-summary if supported and appropriate
no auto-summaryendVerify
show ip protocolsshow ip routeOSPF awareness
Link-state routing and neighbor adjacencies
Link-state protocol
OSPF shares information about links so routers can build a topology view and calculate shortest paths.
Area
OSPF organizes interfaces into areas. Area 0 is the backbone area in standard multi-area designs.
Router ID
A 32-bit value used to identify an OSPF router. It may be chosen automatically or configured deliberately.
Neighbor adjacency
OSPF routers must form compatible neighbor relationships before exchanging full routing information.
Cost
OSPF compares paths using cumulative interface cost.
Passive interface
An interface can advertise its connected network into OSPF while suppressing neighbor formation on that interface.
OSPF configuration pattern
Use areas and wildcard masks deliberately
Inspect current OSPF state
show ip protocolsshow ip ospf neighborshow running-config | section router ospfEnter an OSPF process
configure terminalrouter ospf 1Advertise a transit network
network 10.0.0.0 0.0.0.3 area 0Advertise a LAN
network 192.168.10.0 0.0.0.255 area 0endVerify adjacency and routes
show ip ospf neighborshow ip route ospfWildcard masks
Invert the subnet mask for common OSPF network statements
| Subnet | Subnet mask | Wildcard mask |
|---|---|---|
| 192.168.10.0/24 | 255.255.255.0 | 0.0.0.255 |
| 10.0.0.0/30 | 255.255.255.252 | 0.0.0.3 |
| 172.16.4.0/26 | 255.255.255.192 | 0.0.0.63 |
| 10.10.0.0/16 | 255.255.0.0 | 0.0.255.255 |
Wildcard masks are also used in ACLs, but there they match addresses rather than enabling a routing protocol on interfaces. Context matters.
EIGRP awareness
Neighbor-driven Cisco routing behavior
Neighbor-based learning
EIGRP forms neighbor relationships with compatible routers before exchanging route information.
Autonomous-system number
Classic EIGRP configurations use an autonomous-system number that must match between intended neighbors.
Composite metric
EIGRP commonly considers bandwidth and delay by default when calculating route metrics.
Successor
The current best next-hop path to a destination in EIGRP terminology.
Feasible successor
A loop-free backup path that can be used quickly when certain feasibility conditions are met.
Passive interface
Used to suppress neighbor formation on interfaces where routing updates should not be sent.
EIGRP configuration pattern
Verify AS number and network participation
Inspect
show ip protocolsshow ip eigrp neighborsshow running-config | section router eigrpEnter EIGRP
configure terminalrouter eigrp 100Advertise connected networks
network 10.0.0.0 0.0.0.3network 192.168.10.0 0.0.0.255Disable classful auto-summary where supported and appropriate
no auto-summaryendVerify
show ip eigrp neighborsshow ip route eigrpNeighbor requirements
Dynamic routing starts with compatible peers
RIP
Correct interfaces participate, compatible version, reachable local link, and updates are not blocked.
OSPF
Matching area on the shared link, compatible timers/network behavior, unique router IDs, matching subnet, and working Layer 2/3 connectivity.
EIGRP
Matching AS number in classic configurations, compatible K-values on traditional implementations, shared subnet, and working local connectivity.
Passive-interface reasoning
Advertise networks without forming unnecessary neighbors
User LAN
Likely: Often passive
The connected network may need advertisement, but end-user devices do not need routing-protocol neighbor relationships.
Router-to-router transit link
Likely: Usually not passive
Dynamic neighbors normally need to form across the transit link.
Management-only network
Likely: Depends on topology
Advertise the network only if required, and avoid unnecessary routing protocol exposure.
Unused interface
Likely: No routing participation
An unused interface should not normally advertise or attempt neighbor formation.
Route preference
Prefix length before source preference
192.168.50.0/24 via OSPF and 192.168.50.0/24 static
Static route preferred
Same prefix length, so route source preference matters; normal static AD is lower.
192.168.0.0/16 static and 192.168.50.0/24 OSPF
OSPF /24 preferred for 192.168.50.x
Longest prefix match happens before administrative distance comparison.
0.0.0.0/0 static and 10.0.0.0/8 RIP
RIP /8 preferred for 10.x destinations
The /8 is more specific than the default route.
Two OSPF routes to the same prefix
Lower OSPF cost preferred
Same routing protocol and same prefix, so the protocol's metric decides.
Troubleshooting
Match the symptom to the routing layer
No OSPF neighbors appear
Interface state, IP subnet, area, timers, router ID conflict, passive-interface, network statements, ACLs.
OSPF neighbor exists but route is missing
Remote advertisement, route filtering, network statement/interface participation, more preferred route source, route table specificity.
RIP route appears with unexpected hop count
Topology, alternate paths, route source, summarization, and whether the route is being learned through an unintended neighbor.
EIGRP neighbors are missing
AS number, local subnet, interface state, passive-interface, protocol configuration, and platform support.
Static route wins over OSPF
Expected behavior if both describe the same prefix because static AD 1 is lower than OSPF 110.
Default route is used instead of an expected dynamic route
The dynamic route may be missing, withdrawn, filtered, or not installed. Investigate rather than assuming the default is correct.
Redistribution awareness
Powerful, but not a quick fix
Redistribution connects routing domains
A router can inject routes from one source or protocol into another routing protocol.
It increases complexity
Redistribution can create loops, unexpected preferences, or incomplete reachability if implemented without a clear design.
Do not add it as a quick fix
If one route is missing, first determine whether ordinary advertisement or neighbor formation is broken.
Recognize it when reviewing configs
Commands beginning with redistribute inside a routing process deserve careful review because they influence route propagation.
Default-route propagation
One default can influence many routers
Local default route
A router may have its own 0.0.0.0/0 route toward an upstream path.
Advertising a default
Some routing protocols can inject or originate a default route for downstream routers.
Do not assume every router should originate one
Multiple unexpected default origins can send traffic toward the wrong edge.
Verify upstream reachability
A propagated default is useful only if the advertising router actually has a valid path for unknown destinations.
Evidence-based reasoning
Understand why a route is missing or preferred
A static and OSPF route exist for the same /24
Weak response
OSPF should win because dynamic routing is smarter.
Better reasoning
For the same prefix, the normal static route is preferred because its administrative distance is lower.
An OSPF /24 and static /16 both match the destination
Weak response
Static always wins because AD 1 is lower.
Better reasoning
Longest prefix match happens first. The /24 is more specific and wins for destinations inside it.
OSPF neighbors disappear after an interface becomes passive
Weak response
Add static routes immediately.
Better reasoning
A passive interface suppresses neighbor formation. Confirm whether that transit interface was intended to be passive.
RIP reaches a network in 4 hops
Weak response
Four hops means the route is invalid.
Better reasoning
RIP permits up to 15 usable hops. The important question is whether 4 hops matches the intended topology.
EIGRP routers use different AS numbers
Weak response
They should still exchange routes because they share a subnet.
Better reasoning
Classic EIGRP neighbors normally require matching AS numbers.
A router has a default route and an OSPF route to the same destination's subnet
Weak response
The default route should take precedence because it is static.
Better reasoning
The OSPF subnet route is more specific and wins before administrative distance matters.
Unsafe shortcuts
Routing changes that can hide the actual failure
Enabling a routing protocol on every interface
Creates unnecessary neighbor exposure and route advertisement.
Removing passive-interface from all interfaces
Can start routing-protocol communication on user or management networks where it is not needed.
Adding static routes whenever a dynamic route disappears
Hides the broken routing-protocol condition instead of fixing adjacency or advertisement.
Redistributing protocols to fix one missing network
Can introduce route loops and broad unintended propagation.
Changing administrative distance without a clear design reason
Can silently change which path the router prefers.
Saving before convergence is verified
A transient or incorrect routing state can become the persistent configuration.
Practice scenarios
Choose the safest next routing check
A static /16 and an OSPF /24 both match 192.168.10.25.
The OSPF /24 wins because longest prefix match is evaluated before administrative distance.
OSPF is configured, but show ip ospf neighbor is empty on the transit link.
Check interface state, subnet, area, passive-interface, timers, router ID, and whether OSPF is actually enabled on that interface.
A RIP-learned route shows metric 16.
RIP treats 16 as unreachable. Investigate the route or topology instead of relying on it.
EIGRP neighbors are absent even though interfaces can ping each other.
Compare EIGRP AS numbers, passive-interface settings, network participation, and platform support.
A static route suddenly replaces an OSPF route to the same prefix.
That is expected with default administrative distances. Decide whether the static route is intentional.
A teammate wants to redistribute OSPF into RIP because one route is missing.
Do not redistribute yet. First find the broken advertisement or neighbor condition that caused the missing route.
Verification
Prove the routing domain is stable before saving
Interfaces
Required Layer 3 interfaces are operational and correctly addressed.
Protocol process
The intended routing protocol is configured and only on required networks.
Neighbors
Expected OSPF or EIGRP neighbors form on router-to-router links.
Route source
Routes appear with the expected source code in show ip route.
Preference
Longest-prefix, administrative-distance, and metric behavior match the intended path.
Passive interfaces
User-facing interfaces are not forming unnecessary routing neighbors.
Return path
Remote networks learn or possess a route back to the source.
End-to-end traffic
Required applications work after route convergence.
Defensive lab
Build and troubleshoot a fictional OSPF routing domain
Build a fictional three-router topology with R1, R2, and R3 connected in a line and one LAN behind each router.
Verify all directly connected networks and router-to-router links before enabling any dynamic protocol.
Configure OSPF area 0 across the three routers using only the required transit and LAN networks.
Make user LAN interfaces passive while preserving advertisement of those connected networks.
Verify OSPF neighbors on transit links and OSPF routes to remote LANs.
Introduce one fault such as a wrong OSPF area, missing network statement, or passive transit interface.
Use show ip protocols, show ip ospf neighbor, and show ip route to isolate the exact failure.
Correct only the confirmed issue, verify convergence and end-to-end traffic, then document the route-source changes.
Lesson checklist
Before moving on
I can distinguish connected, static, and dynamically learned routes.
I understand longest prefix match.
I understand administrative distance at a practical level.
I understand that routing-protocol metrics compare paths within the same protocol.
I can recognize RIP, OSPF, and EIGRP route codes and basic behavior.
I know that RIP uses hop count and treats 16 as unreachable.
I understand OSPF areas, neighbors, cost, and router IDs at a basic troubleshooting level.
I understand EIGRP neighbor and AS-number awareness.
I know why passive interfaces are useful.
I inspect show ip protocols before changing routing processes.
I avoid using static routes or redistribution to hide dynamic-routing failures.
I verify convergence, route source, return path, and application traffic before saving.
Reflection
Check your reasoning
Question 1
Why does longest prefix match happen before administrative distance?
Question 2
What is the difference between administrative distance and a routing protocol metric?
Question 3
Why might a user LAN be advertised by OSPF while still being configured as passive?
Question 4
Why does RIP's hop-count limit matter?
Question 5
What should you check when two OSPF routers can ping each other but do not become neighbors?
Question 6
Why can adding a static route hide a dynamic-routing problem instead of solving it?
Carry this forward
Dynamic routing is not magic. Routers still depend on working interfaces, compatible neighbors, correct network participation, route preference, return paths, and policy. Inspect those pieces before adding replacement routes.