Core issue
Static routes are seen in show running-config but not in show ip route command output.
You can display all active dynamic static routes with both the show ip route and show ip route static commands after these active routes are added in the main routing table.
A characteristic of static routes is that, by default, they use an Administrative Distance (AD) of 1. On the other hand, a directly connected route uses an AD of 0. AD is the feature used by routers in order to select the best path when there are two or more different routes to the same destination; it is a measure of the trustworthiness of the source of the routing information. This is the reason why the static route does not get installed in the Routing Information Base (RIB), because that route is already directly connected, and the static route is less reliable than the connected one.
The problem can be due to either of these reasons:
- The IP routing is disabled.
- Next-hop specified for the static route cannot be found as a directly connected host.
Resolution
In order to enable IP routing, use the ip routing global configuration command.
Make sure that the interface that points to the next-hop is UP, which can be checked with the show ip interface brief command and use a valid next-hop that points to a host directly connected to the router.
Catalyst switch
Catalyst 6000 series switches
Catalyst 6500 series switches
Device connected to switch
External router
Another Switch
Internal router module
