Redistributing Static Routes into OSPF: Pitfalls and Progress
When working with dynamic routing protocols like OSPF, it’s often necessary to inject static routes into the OSPF domain. This is common when connecting stub networks, using floating static routes, or implementing policy-based routing strategies.
While the task appears simple, redistribution behavior has changed significantly across Cisco software generations—sometimes leading to confusing or silent failures.
Background on OSPF: Open Shortest Path First
The Basics: OSPF and Static Routes
OSPF is a link-state routing protocol that calculates the shortest path tree using Dijkstra’s algorithm. To extend reachability beyond dynamically learned routes, OSPF allows redistribution of static routes.
Once redistributed, static routes appear as external LSAs (Type 5 or Type 7) and become reachable across the OSPF domain.
The Classic Problem
Consider the following static routes:
ip route 192.168.10.0 255.255.255.0 172.22.1.4
ip route 172.24.1.0 255.255.255.0 172.22.1.4
ip route 10.100.1.0 255.255.255.0 172.22.1.4
And a basic OSPF redistribution:
router ospf 55
redistribute static
On older software, the router may respond:
% Only classful networks will be redistributed
This means none of the subnetted static routes will enter OSPF.
Why This Happens
This behavior originates from early classful routing assumptions. If subnet information is not explicitly permitted, OSPF assumes only major classful networks are eligible for redistribution.
Without the subnets keyword, the router refuses to inject subnetted static routes.
How Modern Software Handles It
Modern Cisco platforms fully embrace classless routing. Redistribution works as expected when configured explicitly:
router ospf 55
redistribute static subnets
This ensures all static routes—regardless of subnet mask—are injected properly.
Interactive Redistribution Diagram
Hover over elements below to see how static routes are injected into the OSPF domain.
subnets keyword, the static routes on the
left never make it into the OSPF domain.
Best Practices
-
Always include
subnets:redistribute static subnets -
Filter redistributed routes:
redistribute static route-map FILTER-STATIC -
Verify with:
show ip route ospf
Final Thoughts
Redistributing static routes into OSPF is a deceptively simple task that can fail silently if defaults are trusted. Understanding historical behavior—and how modern software fixes it—ensures predictable and stable routing.
Be explicit. Use filters. Verify everything.
No comments:
Post a Comment