How to Add a Static Route Cisco

Static routing is a foundational networking skill for controlling IP traffic across enterprise routers and Layer 3 switches. Unlike dynamic routing protocols that automatically calculate paths using periodic advertisements, a static route defines an explicit, manually configured path through which network traffic must travel to reach a specific destination prefix. Whether establishing a deterministic path to a remote branch, creating a gateway of last resort, or engineering backup failover links, mastering static route configuration in Cisco IOS and IOS-XE ensures predictable packet delivery and optimal bandwidth utilization.

This comprehensive guide covers everything from command syntax mechanics and step-by-step CLI implementation to production-ready deployment templates, architectural comparisons, troubleshooting workflows, and official Cisco documentation specifications.

Understanding Cisco ip route Command Syntax and Parameters

Configuring a static route in Cisco IOS relies on the ip route command. Understanding how each argument functions within the forwarding information base (FIB) prevents routing loops, recursive lookup failures, and unnecessary Address Resolution Protocol (ARP) storms.

The base syntax for an IPv4 static route is:

Router(config)# ip route <destination-prefix> <subnet-mask> {<next-hop-ip> | <exit-interface>} [distance] [permanent] [name <description>] [tag <tag-value>]

To configure routing effectively, review the role of each argument in sequence:

1. Destination Prefix and Subnet Mask (<destination-prefix> <subnet-mask>)
   These arguments define the target network. The router compares the packet’s destination IP against this prefix using the longest prefix match rule. Destination prefixes can range from an individual host route (/32 or 255.255.255.255) and standard subnetted networks to a default route (0.0.0.0 0.0.0.0).

2. Forwarding Path Selection: Next-Hop IP vs. Outgoing Exit Interface
   Cisco IOS allows you to define the forwarding path using an IP address, a local interface, or both:

3. Next-Hop IP Address: The IP address of the adjacent router’s ingress interface. This triggers a recursive route lookup, where the local router checks its routing table to find the exit interface connected to that next-hop IP. This is the industry standard for multi-access networks such as Ethernet.
4. Directly Attached Exit Interface: Specifies the local egress interface (for example, GigabitEthernet0/0/1). This method should be reserved for point-to-point connections (such as Serial or GRE tunnels). Specifying only an Ethernet exit interface forces the router to consider the destination subnet directly connected, prompting it to generate ARP requests for every destination host IP, which can exhaust the ARP cache.

5. Fully Specified Static Route: Combines both the egress interface and the next-hop IP (e.g., ip route 10.1.0.0 255.255.0.0 GigabitEthernet0/0/1 192.168.1.2). This eliminates recursive lookups while avoiding excessive ARP requests on broadcast media.

6. Administrative Distance ([distance])
   Administrative Distance (AD) measures the trustworthiness of a routing information source on a scale from 1 to 255 (lower values are preferred). In Cisco IOS, a static route defaults to an AD of 1. By supplying a value between 2 and 255, you can create a floating static route that remains inactive in the routing table until a primary route (such as OSPF with an AD of 110 or EIGRP with an AD of 90) goes down.

7. Operational Modifiers ([permanent], [name], [tag])

8. permanent: Retains the route in the routing table even if the associated exit interface is down or unreachable.
9. name <description>: Assigns a human-readable label (up to 32 characters) to document the route’s purpose in the running configuration.
10. tag <tag-value>: Attaches a 32-bit numeric tag used by route maps to control route redistribution into dynamic protocols.

With these parameters defined, you can proceed to configure and commit persistent static routes in the Cisco command-line interface.

Step-by-Step Guide: Configuring a Static Route on Cisco Routers and Layer 3 Switches

Implementing a static route follows a strict CLI progression. The following steps guide you through privileged mode access, Layer 3 forwarding validation, route instantiation, and non-volatile storage persistence.

Step 1: Enter Privileged EXEC and Global Configuration Mode

Connect to your Cisco device via console, SSH, or Telnet. Transition from User EXEC mode (>) to Privileged EXEC mode (#), then enter Global Configuration mode:

Router> enable
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

Step 2: Enable IP Routing (Layer 3 Switches Only)

If you are configuring a Cisco Catalyst or Nexus Layer 3 switch, IP unicast routing is often disabled by default. Verify and activate global Layer 3 forwarding before defining routes:

Switch(config)# ip routing

(Note: On dedicated Cisco routers, IP unicast routing is active by default and this command can be bypassed.)

Step 3: Configure the Static Route

Execute the ip route command with your target subnet, mask, next-hop address or exit interface, and an optional name identifier:

Router(config)# ip route 172.16.10.0 255.255.255.0 192.168.1.2 name TO-BRANCH-OFFICE

To configure a default route (gateway of last resort) directed to an ISP or core upstream router, use quad-zero syntax:

Router(config)# ip route 0.0.0.0 0.0.0.0 192.0.2.1 name DEFAULT-INTERNET

Step 4: Verify the Route Installation

Return to Privileged EXEC mode and inspect the routing table to confirm that the static route was installed:

Router(config)# end
Router# show ip route static

An entry matching your configuration should appear with the code S:

S    172.16.10.0/24 [1/0] via 192.168.1.2
S*   0.0.0.0/0 [1/0] via 192.0.2.1

Step 5: Save the Configuration to NVRAM

Changes made in Global Configuration mode are stored in volatile RAM (running-config). Commit the configuration to NVRAM to ensure it persists across reboots:

Router# copy running-config startup-config
Destination filename [startup-config]? [Enter]
Building configuration...
[OK]

Alternatively, execute the shortcut write memory.

Cisco Static Route Configuration Templates and CLI Snippets

The following templates and copy-paste snippets can be tailored for common enterprise production scenarios.

Generic Fill-in-the-Blank IPv4 Template

configure terminal
 ip route <DESTINATION_IP> <SUBNET_MASK> <NEXT_HOP_IP> name <ROUTE_NAME>
end
copy running-config startup-config

Production IPv4 Scenarios

! 1. Standard Static Route via Next-Hop IP (Ethernet multi-access)
configure terminal
 ip route 10.50.0.0 255.255.0.0 192.168.10.2 name HQ-DATA-CENTER
end

! 2. Fully Specified Static Route (Interface + Next-Hop)
configure terminal
 ip route 10.60.0.0 255.255.0.0 GigabitEthernet0/0/1 192.168.20.2 name WAN-LINK-PRIMARY
end

! 3. Host Route (/32) for a Single Server or Loopback
configure terminal
 ip route 10.100.1.50 255.255.255.255 192.168.10.254 name TACACS-AUTHENTICATION-SERVER
end

! 4. Floating Static Route for Backup WAN Failover (AD = 200)
configure terminal
 ip route 0.0.0.0 0.0.0.0 198.51.100.1 200 name BACKUP-CELLULAR-GATEWAY
end

Production IPv6 Static Route Template

! Enable IPv6 routing globally prior to adding IPv6 static routes
configure terminal
 ipv6 unicast-routing
 ! IPv6 Static Route via Global Unicast Address
 ipv6 route 2001:db8:acad:1::/64 2001:db8:feed:1::2
 ! IPv6 Default Route (::/0)
 ipv6 route ::/0 2001:db8:feed:1::1
end
copy running-config startup-config

Comparing Static Routes, Default Routes, and Dynamic Routing

Selecting 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.

Troubleshooting Static Routes in Cisco IOS: FAQs and Verification

When 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.

Why is my configured static route not showing up in show ip route?

For 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 operational state.
– If you configured ip route 10.0.0.0 255.0.0.0 GigabitEthernet0/1 and the cable is unplugged, the interface state drops to down/down or administratively down, suppressing the route.
– If you pointed to a next-hop IP (e.g., 192.168.1.1), 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 and show ip route <next-hop-ip> to verify link status and reachability.

What causes a recursive routing failure, and how do I fix it?

A 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:

Router(config)# ip route 10.10.0.0 255.255.0.0 172.16.5.1

The router must consult its routing table to find how to reach 172.16.5.1. If no connected interface, static route, or dynamic entry matches 172.16.5.1, 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 or change the next-hop to an address on an active, directly connected subnet.

How do I verify whether a static route is installed and working?

Use the following verification commands in Privileged EXEC mode:

! View all static routes installed in the active RIB
Router# show ip route static

! Inspect the specific forwarding path for a destination prefix
Router# show ip route 172.16.10.0

! Validate Layer 3 reachability to the next hop and remote destination
Router# ping 172.16.10.1
Router# traceroute 172.16.10.1

If the route is present in show running-config but missing from show ip route, run show ip route repair-cache or check interface status with show ip interface brief.

How do I delete an incorrect or obsolete static route?

To remove a static route, prepend no to the exact command string used to create it:

Router(config)# no ip route 172.16.10.0 255.255.255.0 192.168.1.2

Caution: You must match the destination prefix, mask, and next-hop parameter exactly. If the original route included a next-hop IP, issuing no ip route 172.16.10.0 255.255.255.0 GigabitEthernet0/1 will not remove it.

Why is an Ethernet exit interface causing high CPU usage or ARP table exhaustion?

When you define a static route using only an Ethernet exit interface without a next-hop IP (e.g., ip route 10.0.0.0 255.0.0.0 GigabitEthernet0/0), the router considers the entire 10.0.0.0/8 network directly connected to that broadcast segment.

For every new host IP a packet targets within that network, the router broadcasts an ARP request. If the adjacent router has Proxy ARP enabled, it responds to every request, quickly filling the local ARP cache and causing high CPU utilization. To prevent this, always specify the next-hop IP address on multi-access Ethernet segments.

Cisco IOS and IOS-XE ip route Command Reference Specification

This section provides technical reference specifications for the IPv4 static routing facility in Cisco IOS and IOS-XE platforms.

Command Syntax

ip route prefix mask {ip-address | interface-type interface-number [ip-address]} [distance] [name name] [permanent] [tag tag] [track number]

Parameter Descriptions

• prefix: Destination IP network, subnetwork, or host address using standard dotted-decimal notation.
• mask: Subnet mask corresponding to the destination network prefix.
• ip-address: IPv4 address of the next hop that can be used to reach the destination network. Does not need to be on a directly connected network if recursive resolution is possible.
• interface-type interface-number: Local egress interface type and identity (e.g., GigabitEthernet0/0/0, Serial0/1/0, Tunnel10).
• distance: (Optional) Integer value ranging from 1 to 255 establishing the administrative distance.
• name name: (Optional) Alphanumeric string tag identifying the route in running configurations (maximum 32 characters).
• permanent: (Optional) Keyword specifying that the route will not be removed from the routing table even if all matching interfaces are down.
• tag tag: (Optional) 32-bit unsigned integer value (1 to 4294967295) appended to the route to enable filtering via route-maps.
• track number: (Optional) Associates the static route with a Cisco IOS IP SLA tracking object (values 1 to 1000). If the tracking object state is Down, the route is removed from the routing table, enabling automated failover.

Command Defaults and Modes

• Default Administrative Distance: 1
• Default State: Disabled (no static routes configured by default)
• Command Mode: Global Configuration (Router(config)#)
• Platform Scope: Cisco 800, 1000, 4000 Series Integrated Services Routers (ISRs); Catalyst 8000 Edge Platforms; Catalyst 2960-X (LAN Base with Lite routing), 3650, 3850, 9200, 9300, 9500 Series Switches; ASR 900 and 1000 Series Aggregation Services Routers.
• Software Compatibility: Cisco IOS Software Releases 12.0 through 15.x; Cisco IOS-XE Software Releases 16.x and 17.x (Bengaluru, Cupertino, Dublin, and Gibraltar trains).

Configuring a static route in Cisco IOS is an essential networking technique that provides precise, manual control over path selection. By selecting the correct destination prefix, utilizing next-hop IP addresses over multi-access links, and leveraging administrative distance for backup paths, engineers can build resilient and predictable network architectures. For edge environments and stub connections, static routing remains an efficient, secure, and low-overhead solution when configured and maintained according to Cisco standards.

Please follow and like us: