Switch(config)# ip routing\n<\/code><\/pre>\n(Note: On dedicated Cisco routers, IP unicast routing is active by default and this command can be bypassed.)<\/em><\/p>\n<\/span>Step 3: Configure the Static Route<\/span><\/h3>\nExecute the ip route<\/code> command with your target subnet, mask, next-hop address or exit interface, and an optional name identifier:<\/p>\nRouter(config)# ip route 172.16.10.0 255.255.255.0 192.168.1.2 name TO-BRANCH-OFFICE\n<\/code><\/pre>\nTo configure a default route (gateway of last resort) directed to an ISP or core upstream router, use quad-zero syntax:<\/p>\n
Router(config)# ip route 0.0.0.0 0.0.0.0 192.0.2.1 name DEFAULT-INTERNET\n<\/code><\/pre>\n<\/span>Step 4: Verify the Route Installation<\/span><\/h3>\nReturn to Privileged EXEC mode and inspect the routing table to confirm that the static route was installed:<\/p>\n
Router(config)# end\nRouter# show ip route static\n<\/code><\/pre>\nAn entry matching your configuration should appear with the code S<\/code>:<\/p>\nS 172.16.10.0\/24 [1\/0] via 192.168.1.2\nS* 0.0.0.0\/0 [1\/0] via 192.0.2.1\n<\/code><\/pre>\n<\/span>Step 5: Save the Configuration to NVRAM<\/span><\/h3>\nChanges made in Global Configuration mode are stored in volatile RAM (running-config<\/code>). Commit the configuration to NVRAM to ensure it persists across reboots:<\/p>\nRouter# copy running-config startup-config\nDestination filename [startup-config]? [Enter]\nBuilding configuration...\n[OK]\n<\/code><\/pre>\nAlternatively, execute the shortcut write memory<\/code>.<\/p>\n
\n<\/span>Cisco Static Route Configuration Templates and CLI Snippets<\/span><\/h2>\nThe following templates and copy-paste snippets can be tailored for common enterprise production scenarios.<\/p>\n
<\/span>Generic Fill-in-the-Blank IPv4 Template<\/span><\/h3>\nconfigure terminal\n ip route <DESTINATION_IP> <SUBNET_MASK> <NEXT_HOP_IP> name <ROUTE_NAME>\nend\ncopy running-config startup-config\n<\/code><\/pre>\n<\/span>Production IPv4 Scenarios<\/span><\/h3>\n! 1. Standard Static Route via Next-Hop IP (Ethernet multi-access)\nconfigure terminal\n ip route 10.50.0.0 255.255.0.0 192.168.10.2 name HQ-DATA-CENTER\nend\n\n! 2. Fully Specified Static Route (Interface + Next-Hop)\nconfigure terminal\n ip route 10.60.0.0 255.255.0.0 GigabitEthernet0\/0\/1 192.168.20.2 name WAN-LINK-PRIMARY\nend\n\n! 3. Host Route (\/32) for a Single Server or Loopback\nconfigure terminal\n ip route 10.100.1.50 255.255.255.255 192.168.10.254 name TACACS-AUTHENTICATION-SERVER\nend\n\n! 4. Floating Static Route for Backup WAN Failover (AD = 200)\nconfigure terminal\n ip route 0.0.0.0 0.0.0.0 198.51.100.1 200 name BACKUP-CELLULAR-GATEWAY\nend\n<\/code><\/pre>\n<\/span>Production IPv6 Static Route Template<\/span><\/h3>\n! Enable IPv6 routing globally prior to adding IPv6 static routes\nconfigure terminal\n ipv6 unicast-routing\n ! IPv6 Static Route via Global Unicast Address\n ipv6 route 2001:db8:acad:1::\/64 2001:db8:feed:1::2\n ! IPv6 Default Route (::\/0)\n ipv6 route ::\/0 2001:db8:feed:1::1\nend\ncopy running-config startup-config\n<\/code><\/pre>\n
\n<\/span>Comparing Static Routes, Default Routes, and Dynamic Routing<\/span><\/h2>\nSelecting the appropriate routing mechanism depends on network size, topology stability, hardware resources, and path redundancy requirements. The table below details how static routing compares to default routes and dynamic interior gateway protocols (IGPs) such as OSPF and EIGRP.<\/p>\n
\n\n\n| Architectural Metric<\/th>\n | Static Route<\/th>\n | Default Route (0.0.0.0\/0<\/code>)<\/th>\n| Dynamic Routing (OSPF \/ EIGRP)<\/th>\n<\/tr>\n<\/thead>\n | \n\nPath Definition<\/strong><\/td>\n| Manually configured destination prefix and next-hop.<\/td>\n | Wildcard catch-all for unknown destinations.<\/td>\n | Automatically computed using link-state or distance-vector algorithms.<\/td>\n<\/tr>\n | \nDefault Administrative Distance (AD)<\/strong><\/td>\n1<\/code> (via IP or interface in Cisco IOS).<\/td>\n1<\/code> (if statically configured).<\/td>\nOSPF: 110<\/code>; EIGRP: 90<\/code> (Internal), 170<\/code> (External).<\/td>\n<\/tr>\n\nCPU and Memory Overhead<\/strong><\/td>\n| Extremely low; minimal routing table maintenance.<\/td>\n | Negligible; single FIB lookup table entry.<\/td>\n | Moderate to high; algorithm processing (Dijkstra\/DUAL) and state databases.<\/td>\n<\/tr>\n | \nTopology Change Adaptability<\/strong><\/td>\n| Manual intervention required; cannot dynamically reroute unless paired with IP SLA tracking.<\/td>\n | Static failover requires floating distance or tracking.<\/td>\n | Immediate, automated convergence and alternate path selection upon link loss.<\/td>\n<\/tr>\n | \nBandwidth Consumption<\/strong><\/td>\n| Zero control plane overhead; no periodic hellos or advertisements.<\/td>\n | Zero control plane overhead.<\/td>\n | Low to moderate bandwidth consumption from neighbor hellos, LSUs, and updates.<\/td>\n<\/tr>\n | \nConfiguration Complexity<\/strong><\/td>\n| Increases exponentially with network size ($O(N^2)$ paths).<\/td>\n | Minimal; single command at network edge\/stub router.<\/td>\n | Initial protocol design and tuning require intermediate-to-advanced expertise.<\/td>\n<\/tr>\n | \nSecurity Risk Profile<\/strong><\/td>\n| High security; no route leaks, injection attacks, or unauthorized advertisements.<\/td>\n | Minimal exposure; controlled egress path.<\/td>\n | Requires cryptographic authentication (MD5\/SHA) to prevent rogue neighbor adjacencies.<\/td>\n<\/tr>\n | \nPrimary Use Case<\/strong><\/td>\n| Stub networks, out-of-band management, hub-and-spoke topologies, predictable traffic redirection.<\/td>\n | Edge router gateway to ISP, branch office to single hub router.<\/td>\n | Medium to large enterprise core, campus distribution, and multi-homed meshes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n<\/span>Troubleshooting Static Routes in Cisco IOS: FAQs and Verification<\/span><\/h2>\nWhen a static route does not forward traffic as expected or fails to appear in the routing table, common issues like interface states, next-hop reachability, or administrative distance conflicts are often the cause. Below are direct solutions to frequent operational challenges.<\/p>\n <\/span>Why is my configured static route not showing up in show ip route<\/code>?<\/span><\/h3>\nFor Cisco IOS to install a static route into the routing table (RIB), the next-hop IP must be reachable, or the specified exit interface must be in an up\/up<\/code> operational state.
\n– If you configured ip route 10.0.0.0 255.0.0.0 GigabitEthernet0\/1<\/code> and the cable is unplugged, the interface state drops to down\/down<\/code> or administratively down<\/code>, suppressing the route.
\n– If you pointed to a next-hop IP (e.g., 192.168.1.1<\/code>), the router must have an active interface on that subnet or an existing valid path in its routing table to reach that IP. Run show ip interface brief<\/code> and show ip route <next-hop-ip><\/code> to verify link status and reachability.<\/p>\n<\/span>What causes a recursive routing failure, and how do I fix it?<\/span><\/h3>\nA recursive lookup failure occurs when a router cannot resolve the exit interface for a static route’s next-hop IP address. For instance, if you configure:<\/p>\n Router(config)# ip route 10.10.0.0 255.255.0.0 172.16.5.1\n<\/code><\/pre>\nThe router must consult its routing table to find how to reach 172.16.5.1<\/code>. If no connected interface, static route, or dynamic entry matches 172.16.5.1<\/code>, the static route is considered invalid and will not be installed in the forwarding table. To resolve this, configure a route that resolves 172.16.5.1<\/code> or change the next-hop to an address on an active, directly connected subnet.<\/p>\n<\/span>How do I verify whether a static route is installed and working?<\/span><\/h3>\nUse the following verification commands in Privileged EXEC mode:<\/p>\n ! View all static routes installed in the active RIB\nRouter# show ip route static\n\n! Inspect the specific forwarding path for a destination prefix\nRouter# show ip route 172.16.10.0\n\n! Validate Layer 3 reachability to the next hop and remote destination\nRouter# ping 172.16.10.1\nRouter# traceroute 172.16.10.1\n<\/code><\/pre>\nIf the route is present in show running-config<\/code> but missing from show ip route<\/code>, run show ip route repair-cache<\/code> or check interface status with show ip interface brief<\/code>.<\/p>\n<\/span>How do I delete an incorrect or obsolete static route?<\/span><\/h3>\nTo remove a static route, prepend no<\/code> to the exact command string used to create it:<\/p>\nRouter(config)# no ip route 172.16.10.0 255.255.255.0 192.168.1.2\n<\/code><\/pre>\n
| | | | | | | | | | | | |