Once static routes are configured, how do you verify them — and why does show running-config reveal routes the routing table hides?
show ip route (or show ipv6 route) lists the routes actually installed; show ip route static filters to just the static ones; show running-config | section ip route shows every configured route — including a floating static that isn't installed; ping and traceroute then test real reachability.
The distinction that trips people up: the routing table shows only the winning (installed) routes, while the running-config shows everything you typed. A floating static route (higher AD) sits in the config but never appears in show ip route until the primary drops — so to confirm a backup route is even configured, you read the running-config, not the table.
| Command | What it shows |
|---|---|
show ip route / show ipv6 route |
All installed routes (connected, static, dynamic) |
show ip route static |
Only static routes — the candidate-default S* stands out |
show ip route 172.16.1.0 |
The detailed entry for one specific network |
show running-config | section ip route |
Every configured static route, installed or not |
ping / traceroute |
End-to-end reachability and the actual path taken |
(Swap ip for ipv6 to get the IPv6 versions of each command.)
Tip: "Configured ≠ installed." If a route exists in the config but traffic isn't using it, check the routing table — a more-specific route or one with a lower AD may be winning instead.
Go deeper:
Routing table (Wikipedia) — the structure these showcommands display: each entry's destination, next hop, interface, and metric.