Imagine building a road network and having to manually draw every single route on a map — that's static routing. In the CCNA 200-301 exam (Objective 3.2: IP Connectivity), static routing is the foundational skill for understanding how routers forward packets. Real network engineers use static routes for simple networks, stub links, and backup paths. Mastering static routing means you can build small-to-medium networks from scratch and troubleshoot routing issues at the packet level.
Jump to a section
Think of a large office building with multiple floors and departments. The mailroom receives all incoming packages. But the mailroom doesn't automatically know where every employee sits — someone must tell them. The building manager creates a "static route" by writing a note: 'All packages for Accounting go to Floor 3, Room 305.' This note is permanent until the manager changes it. If Accounting moves to Floor 2, the note must be manually updated. The mailroom clerk doesn't learn from experience; they follow the note every time. If the note says 'Accounting → Floor 3' but Accounting is now on Floor 2, the package goes to the wrong place — a routing black hole. In networking, a static route is exactly that: a manually configured path in the routing table. The router uses it until you remove it. It never adapts to network changes, so if a link goes down, the static route remains — potentially sending traffic into a black hole unless you configure a floating static route with a higher administrative distance. The mailroom analogy captures the essence: static routes are simple, reliable, and require human intervention to change.
What is Static Routing?
Static routing is the process of manually adding routes to a router's routing table. Unlike dynamic routing protocols (OSPF, EIGRP), static routes do not automatically adjust when the network topology changes. They are configured by a network administrator using the ip route command in global configuration mode.
Why Use Static Routes?
Static routes are used in several scenarios:
- Stub networks: A network with only one exit path (e.g., a branch office connected to HQ via a single WAN link).
- Default routes: A catch-all route (0.0.0.0/0) for internet-bound traffic.
- Backup routes: A floating static route with a higher administrative distance (AD) that kicks in when the primary dynamic route fails.
- Small networks: Where the overhead of a dynamic routing protocol is unnecessary.
How Static Routes Work
When a router receives a packet destined for a network not directly connected, it consults its routing table. If a matching static route exists, the router forwards the packet to the specified next-hop IP address or out the specified exit interface. The router performs a recursive lookup: it must find a route to the next-hop IP address (usually a directly connected network) before it can forward the packet.
IOS Configuration Syntax
The basic command is:
ip route <destination-network> <subnet-mask> <next-hop-ip | exit-interface> [administrative-distance] [permanent]destination-network: The target network (e.g., 192.168.2.0)
subnet-mask: The subnet mask for that network (e.g., 255.255.255.0)
next-hop-ip: The IP address of the neighboring router
exit-interface: The local interface to use (e.g., GigabitEthernet0/0)
administrative-distance: Default is 1; you can set a higher value (e.g., 5) to create a floating static route.
permanent: Keeps the route even if the interface goes down (use with caution).
Example: To reach network 10.1.1.0/24 via next-hop 192.168.1.2:
R1(config)# ip route 10.1.1.0 255.255.255.0 192.168.1.2Verification Commands
`show ip route`: Displays the full routing table. Static routes are marked with S.
`show ip route static`: Shows only static routes.
`show ip route <network>`: Shows detailed information about a specific route.
`traceroute <destination>`: Traces the path taken by packets.
`ping <destination>`: Tests connectivity.
Example output:
R1# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, GigabitEthernet0/0
S 10.2.2.0 [1/0] via 192.168.1.2Here, S indicates a static route. [1/0] means administrative distance 1 and metric 0.
A default route is a special static route that matches all packets. It is used when no specific route exists. Configured as:
ip route 0.0.0.0 0.0.0.0 <next-hop-ip | exit-interface>Floating Static Route
A floating static route is a backup route with a higher administrative distance (e.g., 5 for OSPF, 90 for EIGRP). It only appears in the routing table when the primary dynamic route fails.
Example: If OSPF learns 10.2.2.0/24 with AD 110, a floating static route with AD 120 would be used only if OSPF goes down.
ip route 10.2.2.0 255.255.255.0 192.168.2.2 120Interaction with Dynamic Routing
Static routes have an administrative distance of 1 by default, which is lower than any dynamic protocol (OSPF AD 110, EIGRP AD 90). This means static routes are preferred over dynamic routes unless you manually increase the AD. This can be used to override dynamic routes for policy routing.
Troubleshooting
Common issues: - Wrong next-hop IP: The router cannot reach the next hop, so the route is not installed (shown as "hidden"). - Missing return route: A router sends packets to the next hop, but the next hop has no route back. - Incorrect subnet mask: The route does not match the intended network. - Routing loop: Two static routes point to each other.
Use debug ip routing to see routing table changes (use with caution in production).
Plan the IP addressing
Before configuring static routes, you need a clear network diagram. Identify all networks (subnets) that are not directly connected to each router. For each such network, determine the next-hop IP address (the IP of the neighbor router's interface that is on a common subnet) or the local exit interface. Document the subnet mask and any administrative distance if you plan to use floating static routes. For example, in a network with R1 (192.168.1.0/24) and R2 (10.1.1.0/24) connected via a serial link (10.0.0.0/30), R1 needs a static route to 10.1.1.0/24 via next-hop 10.0.0.2.
Enter global configuration mode
On the router, enter privileged EXEC mode and then global configuration mode using the commands: ``` R1> enable R1# configure terminal ``` You are now in global configuration mode, indicated by the prompt `R1(config)#`. This is where you will enter the `ip route` commands.
Configure the static route
Use the `ip route` command to add the static route. For a simple static route to network 10.1.1.0/24 via next-hop 10.0.0.2: ``` R1(config)# ip route 10.1.1.0 255.255.255.0 10.0.0.2 ``` If you want to use an exit interface instead of a next-hop IP, you can specify the local interface: ``` R1(config)# ip route 10.1.1.0 255.255.255.0 Serial0/0/0 ``` Using an exit interface is common for point-to-point links because it avoids recursive lookup. However, on multi-access networks, specifying the next-hop IP is more reliable.
Configure a default route if needed
If the router should send all unknown traffic to a specific next-hop, configure a default route: ``` R1(config)# ip route 0.0.0.0 0.0.0.0 10.0.0.2 ``` This route matches any destination IP address. It is often used on edge routers to point to the internet gateway. The default route has the lowest prefix length (0), so it is only used when no more specific route matches.
Verify the routing table
Exit configuration mode and use `show ip route` to verify the static route appears: ``` R1(config)# end R1# show ip route ``` Look for the line starting with `S` for the static route. Also check that the next-hop IP is reachable (the route should be in the routing table). If the next-hop is not reachable, the static route will not be installed (it will be hidden). Use `ping` to test connectivity to the next-hop IP.
Test end-to-end connectivity
Use `ping` and `traceroute` to verify that packets are forwarded correctly across the network. For example, from R1, ping a host on the remote network: ``` R1# ping 10.1.1.1 ``` If successful, the static route is working. If not, check the return route on the remote router — it must have a route back to the source network. Also check for ACLs that might be blocking traffic.
In enterprise networks, static routes are commonly used for stub networks where a branch office has a single WAN link to the main office. For example, a retail store with one router connected to headquarters via a T1 line. The branch router needs only a default route pointing to the HQ router, and the HQ router needs a static route for the branch's LAN subnet. This is simple, secure, and requires no dynamic routing protocol overhead.
Another scenario is when an organization has multiple internet connections for redundancy. A network engineer might configure a primary default route with AD 1 pointing to the primary ISP, and a floating static default route with AD 2 pointing to the backup ISP. If the primary link fails, the backup route automatically takes over. This is a cost-effective alternative to BGP.
Static routes are also used for policy-based routing, such as forcing traffic from a specific source network to use a particular path. For example, a company might want all VoIP traffic to go through a dedicated MPLS link while data traffic uses the internet. This can be achieved with static routes and policy-based routing (PBR).
However, static routes have limitations. In large networks with many subnets, maintaining static routes becomes error-prone and time-consuming. A misconfigured static route can cause a routing black hole or a loop. For example, if a static route points to a next-hop that is no longer reachable, traffic is dropped silently. That's why network engineers often combine static routes with dynamic protocols or use them only for specific, stable paths.
When misconfigured, static routes can cause asymmetric routing, where packets take one path forward and a different path back, which can break firewall stateful inspection. Also, if you forget to add a return route, communication is one-way only. Always verify bidirectional reachability with traceroute.
The CCNA 200-301 exam tests static routing under Objective 3.2: IP Connectivity. You must be able to configure, verify, and troubleshoot static and default routes. The exam will present scenarios where you need to choose the correct ip route command syntax, including the destination network, subnet mask, and next-hop or exit interface.
Common wrong answers:
1. Using the wrong subnet mask format: Candidates often write ip route 192.168.1.0 /24 10.0.0.1 — but IOS does not accept CIDR notation in the ip route command; you must use dotted decimal (255.255.255.0).
2. Confusing next-hop and exit interface: For a multi-access network (e.g., Ethernet), specifying only the exit interface without a next-hop IP can cause the router to use proxy ARP, which may fail. The exam expects you to use the next-hop IP on Ethernet links.
3. Forgetting the administrative distance for floating routes: A floating static route must have a higher AD than the dynamic route it backs up. Many candidates set AD to 1 (default) and wonder why the static route overrides the dynamic route.
4. Misunderstanding route preference: Static routes (AD 1) are preferred over OSPF (AD 110) and EIGRP (AD 90). But an EIGRP route (AD 90) is preferred over a static route with AD 120 (floating).
Calculation traps: The exam may ask you to identify the correct static route to reach a specific subnet. Be careful with subnet masks — for example, 10.0.0.0/8 is not the same as 10.0.0.0/16. Also, the next-hop must be on a directly connected network. If the next-hop IP is not directly connected, the static route is invalid (the router will not install it).
Decision rule: When given a scenario with multiple routers, draw the network and identify which routers need static routes. For each router, list the networks it does not know about. Then write the ip route command with the correct next-hop (the IP of the neighbor's interface that is on the same subnet as the router's interface).
Static routes have a default administrative distance of 1, making them preferred over all dynamic routes unless overridden.
The `ip route` command syntax is: `ip route <network> <mask> <next-hop | exit-interface> [AD]`.
A default route is a static route to 0.0.0.0/0.
Floating static routes use a higher AD (e.g., 5, 10, 120) to act as backup for dynamic routes.
Use `show ip route static` to display only static routes.
Static routes require a reachable next-hop; otherwise, they are not installed in the routing table.
On point-to-point links, specifying the exit interface is efficient; on multi-access links, use the next-hop IP.
These come up on the exam all the time. Here's how to tell them apart.
Static Route
Manually configured by administrator
Default AD = 1
No overhead or bandwidth usage
Does not adapt to network changes
Best for small or stub networks
Dynamic Route (OSPF)
Automatically learned via routing protocol
Default AD = 110
Uses hello packets and LSA updates
Adapts to topology changes (convergence)
Best for large, redundant networks
Mistake
Static routes are automatically updated when a link goes down.
Correct
Static routes remain in the routing table even if the next-hop becomes unreachable, unless the exit interface goes down. They do not adapt to topology changes.
Candidates confuse static routes with dynamic routing protocols that have built-in convergence mechanisms.
Mistake
The administrative distance of a static route is always 1.
Correct
The default AD for a static route is 1, but you can set any value from 0 to 255. For example, a floating static route might have AD 120.
Many candidates think AD is fixed, but it is configurable per route.
Mistake
You can use CIDR notation in the `ip route` command, e.g., `ip route 192.168.1.0/24 10.0.0.1`.
Correct
IOS requires the subnet mask in dotted decimal format, e.g., `ip route 192.168.1.0 255.255.255.0 10.0.0.1`.
Candidates are used to CIDR notation from subnetting questions and assume it works in IOS commands.
Mistake
A static route with an exit interface does not need a next-hop IP on Ethernet links.
Correct
On Ethernet (multi-access) links, specifying only the exit interface causes the router to use proxy ARP, which may fail. It is best practice to include the next-hop IP for Ethernet interfaces.
Candidates see examples with point-to-point serial links and assume the same applies to Ethernet.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A static route is a manually configured route to a specific network (e.g., `ip route 10.1.1.0 255.255.255.0 192.168.1.2`). A default route is a special static route to 0.0.0.0/0 that matches all destinations not in the routing table. The default route is often used on edge routers to send all internet-bound traffic to an ISP. Both are configured with the `ip route` command, but the default route uses the network 0.0.0.0 with mask 0.0.0.0.
Yes, you can have multiple static routes to the same network, but only the route with the lowest administrative distance (or best metric) will be installed in the routing table. If you want load balancing, you can configure multiple static routes with the same AD and metric; IOS will then load balance per destination. For example: `ip route 10.1.1.0 255.255.255.0 192.168.1.2` and `ip route 10.1.1.0 255.255.255.0 192.168.1.3` will both be installed and traffic will be load-balanced.
The `permanent` keyword prevents the static route from being removed from the routing table even if the interface associated with the route goes down. This is useful for routes that should always be present, but it can cause black holes if the next-hop becomes unreachable. Use with caution. Without `permanent`, if the exit interface goes down, the route is removed from the routing table.
A static route will not appear in the routing table if the next-hop IP address is not reachable (i.e., there is no route to the next-hop network). The router must have a directly connected or static route to the next-hop network. Also, if you specify an exit interface that is down, the route will not be installed. Use `show ip route` and check for the route; if missing, verify connectivity to the next-hop.
A floating static route is a backup route that only becomes active when the primary route (usually learned via a dynamic protocol) fails. You configure it by setting a higher administrative distance than the dynamic route. For example, if you have an OSPF route with AD 110, you can add a static route with AD 120: `ip route 10.1.1.0 255.255.255.0 192.168.1.2 120`. This route will not appear in the routing table as long as the OSPF route exists.
No, the next-hop IP address must be directly connected to the router. If the next-hop is not directly connected, the router cannot forward packets to it because it would need to perform a recursive lookup that would fail. The router will not install the static route. Always ensure the next-hop is on a subnet that is directly connected to the router.
Use `show ip route` to see if the static route is present. Then ping a destination on the remote network. If ping fails, use `traceroute` to see where packets stop. Also verify that the remote router has a return route to the source network. Check for ACLs that might be blocking traffic. Use `debug ip routing` to see if the route is being used (caution: debug can be CPU-intensive).
You've just covered Static Routing — now see how well it sticks with free CCNA 200-301 practice questions. Full explanations included, no account needed.
Done with this chapter?