Primary Use Cases<\/strong><\/td>\n| Stub networks, default gateways, out-of-band management, floating backups<\/td>\n | Enterprise campus networks, internal data center fabrics<\/td>\n | Service provider backbones, multi-homed internet edges, data center interconnects<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Section Takeaway:<\/strong> Static routing excels in simple, deterministic topologies such as stub connections and out-of-band management networks, whereas dynamic protocols are necessary when topology changes demand automated failover and scalable path discovery.<\/p>\n<\/span>Cisco IP Route Command Syntax and Step-by-Step Configuration<\/span><\/h2>\nTo configure a static route in Cisco IOS or IOS-XE, administrators use the ip route<\/code> command in global configuration mode for IPv4, or ipv6 route<\/code> for IPv6. Understanding how the router resolves the destination parameter dictates whether you should specify a next-hop IP, an exit interface, or both.<\/p>\n<\/span>Route Forwarding Types<\/span><\/h3>\n\n- Next-Hop Static Route:<\/strong> Specifies only the next-hop IP address. The router performs a recursive lookup in the routing table to verify which local interface can reach that next-hop IP. This is the standard best practice on multi-access broadcast networks such as Ethernet.<\/li>\n
- Directly Attached Static Route:<\/strong> Specifies only the local exit interface. The router assumes that the destination network is directly attached to this interface and initiates Address Resolution Protocol (ARP) requests for every unique destination IP traversing the link. On broadcast Ethernet interfaces, this can flood the network and exhaust router memory through ARP table bloat; it should only be used on point-to-point links (e.g., serial or GRE tunnels).<\/li>\n
- Fully Specified Static Route:<\/strong> Specifies both the local exit interface and the next-hop IP. This eliminates recursive routing lookups while preventing excessive ARP generation on broadcast networks.<\/li>\n<\/ol>\n
<\/span>Step-by-Step Configuration Procedure<\/span><\/h3>\nFollow these sequential steps to configure a static route on a Cisco router or Layer 3 switch:<\/p>\n \n- \n
Enter Privileged EXEC and Global Configuration Mode:<\/strong>
\n Access the privileged command hierarchy and open the running configuration for editing.
\n text
\n Router> enable
\n Router# configure terminal<\/code><\/p>\n<\/li>\n- \n
Verify IP Routing State (Layer 3 Switches):<\/strong>
\n If configuring a multi-layer switch (such as a Cisco Catalyst 3850, 9200, or 9300), ensure that routing is globally activated. On dedicated routers, this is enabled by default.
\n text
\n Router(config)# ip routing
\n Router(config)# ipv6 unicast-routing<\/code><\/p>\n<\/li>\n- \n
Configure the Static Route:<\/strong>
\n Apply the ip route<\/code> command by specifying the target destination network, subnet mask, and next-hop parameter.<\/p>\n<\/li>\n- IPv4 Next-Hop Configuration:<\/em>
\n text
\n Router(config)# ip route 192.168.20.0 255.255.255.0 10.1.1.2<\/code><\/li>\n- IPv4 Fully Specified Configuration (Recommended for Ethernet):<\/em>
\n text
\n Router(config)# ip route 192.168.20.0 255.255.255.0 GigabitEthernet0\/0\/1 10.1.1.2 name TO-BRANCH-OFFICE<\/code><\/li>\n- \n
IPv6 Static Route Configuration:<\/em>
\n text
\n Router(config)# ipv6 route 2001:db8:acad:2::\/64 2001:db8:acad:1::2<\/code><\/p>\n<\/li>\n- \n
Commit the Configuration:<\/strong>
\n Exit global configuration mode and write the running configuration changes to the non-volatile random-access memory (NVRAM).
\n text
\n Router(config)# end
\n Router# copy running-config startup-config<\/code><\/p>\n<\/li>\n<\/ol>\nSection Takeaway:<\/strong> Always supply a next-hop IP address rather than an egress interface alone on Ethernet segments to avoid recursive lookup overhead and ARP table exhaustion.<\/p>\n<\/span>Configuring a Default Static Route (Gateway of Last Resort)<\/span><\/h2>\nA default static route acts as a catch-all mechanism. When a router looks up a destination address that does not match any specific entry in its Routing Information Base (RIB), it forwards the packet to the gateway specified by the default route. In Cisco networking, this entry establishes the “Gateway of Last Resort.”<\/p>\n A default route uses an all-zeros address and mask (0.0.0.0 0.0.0.0<\/code> for IPv4, and ::\/0<\/code> for IPv6), representing the shortest possible prefix length (prefix \/0<\/code>), making it the route of last choice under longest-prefix-match rules.<\/p>\n<\/span>Step-by-Step Implementation<\/span><\/h3>\n\n- \n
Identify the Egress Parameters:<\/strong>
\n Determine the IP address assigned to the upstream provider router or the local WAN edge interface connecting to the Internet Service Provider (ISP).<\/p>\n<\/li>\n- \n
Apply the IPv4 Default Route:<\/strong>
\n Enter global configuration mode and define the default quad-zero route targeting the upstream gateway:
\n text
\n Router# configure terminal
\n Router(config)# ip route 0.0.0.0 0.0.0.0 203.0.113.1<\/code><\/p>\n<\/li>\n- \n
Apply the IPv6 Default Route:<\/strong>
\n Define the IPv6 counterpart using the unspecified prefix notation:
\n text
\n Router(config)# ipv6 route ::\/0 2001:db8:feed:1::1<\/code><\/p>\n<\/li>\n- \n
Confirm Gateway Establishment:<\/strong>
\n Validate that the route has taken effect and that the system has recognized the gateway:
\n text
\n Router(config)# end
\n Router# show ip route | include Gateway
\n Gateway of last resort is 203.0.113.1 to network 0.0.0.0<\/code><\/p>\n<\/li>\n<\/ol>\nSection Takeaway:<\/strong> A default route provides an edge router with an egress path for all unmapped outbound internet traffic by leveraging a \/0<\/code> wildcard prefix match.<\/p>\n<\/span>Implementing Floating Static Routes for Redundancy<\/span><\/h2>\nA floating static route serves as a backup path that installs into the routing table only when the primary path fails. This mechanism relies on Administrative Distance (AD), which Cisco IOS uses to rate the trustworthiness of routing information from 0 (most trusted) to 255 (untrusted\/inactive).<\/p>\n By default, a standard static route has an Administrative Distance of 1<\/code>, making it more preferred than dynamic routing protocols such as OSPF (AD 110<\/code>) or internal BGP (AD 200<\/code>). To create a floating static route, you assign the static route an AD higher than that of the primary route covering the same destination prefix.<\/p>\n<\/span>Step-by-Step Floating Route Deployment<\/span><\/h3>\n\n- Identify the Primary Route AD:<\/strong>
\n Determine the administrative distance of your primary forwarding mechanism:<\/li>\n- Primary Static Route: AD =
1<\/code><\/li>\n- Primary OSPF Route: AD =
110<\/code><\/li>\n- \n
Primary EIGRP Route: AD = 90<\/code><\/p>\n<\/li>\n- \n
Configure the Primary and Secondary Routes:<\/strong>
\n Configure the primary path normally, and assign an explicit administrative distance value to the backup static route.<\/p>\n<\/li>\n- Example 1: Backing up a primary static route (AD 1):<\/em>
\n text
\n Router(config)# ip route 172.16.0.0 255.255.0.0 10.1.1.1 name PRIMARY-FIBER
\n Router(config)# ip route 172.16.0.0 255.255.0.0 10.2.2.1 10 name BACKUP-LTE<\/code><\/li>\n- \n
Example 2: Backing up an OSPF routing protocol (AD 110):<\/em>
\n text
\n Router(config)# ip route 10.50.0.0 255.255.0.0 198.51.100.2 115 name BACKUP-TO-OSPF<\/code><\/p>\n<\/li>\n- \n
Verify Route Inactivity in the Routing Table:<\/strong>
\n Run show ip route<\/code> while the primary link is healthy. The backup route will not appear in the active routing table because the lower-AD primary route takes precedence.<\/p>\n<\/li>\n- \n
Test Failover Behavior:<\/strong>
\n Simulate an outage by administratively shutting down the primary interface:
\n text
\n Router(config)# interface GigabitEthernet0\/0\/1
\n Router(config-if)# shutdown
\n Router(config-if)# end
\n Router# show ip route 172.16.0.0<\/code>
\n The router immediately installs the secondary route with metric\/AD 10<\/code> into the active routing table. When the primary interface is brought back up (no shutdown<\/code>), the router reinstalls the primary route and floats the backup out of the active forwarding table.<\/p>\n<\/li>\n<\/ol>\nSection Takeaway:<\/strong> Floating static routes provide deterministic link redundancy by assigning a higher administrative distance than the primary route, automatically installing only when the preferred path becomes unreachable.<\/p>\n<\/span>Verifying and Troubleshooting Missing Static Routes<\/span><\/h2>\nA common administrative issue occurs when a static route is successfully entered into configuration mode but does not appear in show ip route<\/code>. Cisco IOS validates specific operational conditions before it admits a static route into the active Routing Information Base (RIB) and Forwarding Information Base (FIB).<\/p>\n<\/span>Diagnostic Progression Flow<\/span><\/h3>\nFollow these troubleshooting checks sequentially when an expected static route is missing:<\/p>\n \n- \n
Verify Interface Line Protocol Status:<\/strong>
\n If a static route specifies an exit interface or depends on an interface to reach the next-hop address, that interface must be in the up\/up<\/code> operational state.
\n text
\n Router# show ip interface brief<\/code>
\n Action:<\/em> If the interface is administratively down<\/code>, execute no shutdown<\/code> within the interface configuration. If it is down\/down<\/code>, verify physical cabling, transceivers, and carrier handoffs.<\/p>\n<\/li>\n- \n
Validate Next-Hop Reachability:<\/strong>
\n If using a next-hop IP address, the router must have an existing route to that IP. If recursive resolution fails, the static route is withheld from the table.
\n text
\n Router# show ip route <next-hop-ip><\/code>
\n Action:<\/em> Ensure the next hop resides within a directly connected subnet or can be resolved through another valid routing entry.<\/p>\n<\/li>\n- \n
Inspect the Active Routing Table for Specific Routes:<\/strong>
\n Confirm whether the static route is installed, and inspect its associated administrative distance and metric:
\n text
\n Router# show ip route static<\/code>
\n To drill down into a specific subnet:
\n text
\n Router# show ip route 192.168.20.0<\/code>
\n Output Analysis:<\/em> Look for the [1\/0]<\/code> prefix tag. The first number indicates the Administrative Distance (1<\/code>), and the second indicates the route metric (0<\/code>).<\/p>\n<\/li>\n- \n
Verify Layer 3 Routing Activation:<\/strong>
\n On multi-layer Catalyst switches, commands may save without errors even when IP routing is disabled globally.
\n text
\n Router# show running-config | include ip routing<\/code>
\n Action:<\/em> If empty, enter configuration mode and enable routing using ip routing<\/code>.<\/p>\n<\/li>\n- \n
Identify Prefix and Subnet Mask Typos:<\/strong>
\n Compare the running configuration against your network diagram to ensure the network address matches the mask (e.g., using 192.168.1.1 255.255.255.0<\/code> instead of 192.168.1.0 255.255.255.0<\/code> will produce an error or misdirect traffic).
\n text
\n Router# show run | section ip route<\/code><\/p>\n<\/li>\n<\/ol>\nSection Takeaway:<\/strong> A static route only enters the active routing table if its exit interface is in an up\/up<\/code> state and its next-hop IP can be recursively resolved.<\/p>\n<\/span>Cisco Static Route Configuration Templates and CLI Cheat Sheet<\/span><\/h2>\nUse the following syntax templates and production-ready snippets for direct deployment across Cisco IOS and IOS-XE command-line environments.<\/p>\n ! ===================================================================\n! CISCO IOS \/ IOS-XE STATIC ROUTING CLI CHEAT SHEET & CONFIG TEMPLATES\n! ===================================================================\n\n! --- Basic IPv4 Static Route (Next-Hop) ---\nconfigure terminal\n ip route <destination_network> <subnet_mask> <next_hop_ip>\n exit\n\n! --- Basic IPv6 Static Route (Next-Hop) ---\nconfigure terminal\n ipv6 unicast-routing\n ipv6 route <destination_prefix>\/<prefix_length> <next_hop_ipv6>\n exit\n\n! --- Default Route (Gateway of Last Resort) ---\nconfigure terminal\n ip route 0.0.0.0 0.0.0.0 <next_hop_ip_or_exit_interface>\n ipv6 route ::\/0 <next_hop_ipv6_or_exit_interface>\n exit\n\n! --- Point-to-Point Direct Interface Route ---\n! (Use ONLY on Serial, GRE, or P2P interfaces; NOT on Ethernet)\nconfigure terminal\n ip route <destination_network> <subnet_mask> <interface_type><interface_number>\n exit\n\n! --- Fully Specified Static Route (Best Practice for Ethernet) ---\nconfigure terminal\n ip route 192.168.50.0 255.255.255.0 GigabitEthernet0\/0\/0 10.10.10.2 name CORPORATE-LAN\n exit\n\n! --- Floating Static Route (Backup with Custom Administrative Distance) ---\nconfigure terminal\n ip route <destination_network> <subnet_mask> <backup_next_hop_ip> <administrative_distance>\n ! Example (AD = 200, floating behind OSPF):\n ip route 10.0.0.0 255.0.0.0 192.168.100.1 200 name BACKUP-PATH\n exit\n\n! --- Permanent Static Route (Retains entry in RIB even if link goes down) ---\nconfigure terminal\n ip route <destination_network> <subnet_mask> <next_hop_ip> permanent\n exit\n\n! --- IP SLA Tracked Static Route Template (Automated Next-Hop Health Checking) ---\nconfigure terminal\n ip sla 1\n icmp-echo <target_ip_to_ping> source-interface <local_exit_interface>\n frequency 5\n ip sla schedule 1 life forever start-time now\n !\n track 10 ip sla 1 reachability\n !\n ! Primary route tied to IP SLA track object:\n ip route 0.0.0.0 0.0.0.0 <primary_isp_gateway> track 10\n ! Floating backup route installed automatically if track 10 fails:\n ip route 0.0.0.0 0.0.0.0 <secondary_isp_gateway> 250\n exit\n\n! --- Route Deletion \/ Removal Syntax ---\nconfigure terminal\n no ip route <destination_network> <subnet_mask> <next_hop_ip>\n no ipv6 route <destination_prefix>\/<prefix_length> <next_hop_ipv6>\n exit\n\n! --- Essential Verification Commands ---\nshow ip route\nshow ip route static\nshow ip route <destination_network>\nshow ipv6 route static\nshow ip interface brief\n<\/code><\/pre>\nSection Takeaway:<\/strong> Standardized templates reduce deployment errors; always pair complex backup static routes with IP SLA tracking when physical link state alone cannot detect upstream forwarding failures.<\/p>\n<\/span>Official Cisco IOS Static Routing Reference and Technical Standards<\/span><\/h2>\nCisco\u2019s authoritative architecture standards for protocol-independent routing govern how the Cisco IOS and IOS-XE kernels evaluate, install, and enforce static routing logic.<\/p>\n <\/span>Command Reference: ip route<\/code><\/span><\/h3>\nip route prefix mask {ip-address | interface-type interface-number [ip-address]} [distance] [name name] [permanent] [tag tag] [track number]\n<\/code><\/pre>\n
|