Routing is the process of selecting paths in a network along which to send traffic. It’s the backbone of all data communication in IP networks, enabling devices to exchange data across different networks. Routers forward packets based on the destination IP address, and they learn about remote networks through two primary methods: static routing and dynamic routing protocols. This guide, aimed at CCNA and CCNP study, covers both in depth: configuration, advantages, disadvantages, real-world use cases, and exam-prep pointers.
What Is Static Routing?
Static routing means manually configuring routes in a router’s routing table. Unlike dynamic protocols, static routes don’t adapt to network changes on their own — they need manual updates, which makes them a deliberate choice rather than a default one.
Router(config)# ip route 192.168.2.0 255.255.255.0 192.168.1.2This command adds a static route to the 192.168.2.0/24 network via next-hop address 192.168.1.2.
When to Use Static Routing
- Small or stub networks — ideal for setups with a single exit path, such as branch offices.
- High-security environments — no route advertisements means less exposure to route-hijacking or spoofing attacks.
- Predictable traffic — well suited to management interfaces or fixed paths, such as in CCNA labs.
What Is Dynamic Routing?
Dynamic routing protocols let routers automatically discover and maintain routes to remote networks. Protocols like RIP, OSPF, EIGRP, and BGP exchange routing information with neighbors and adapt to topology changes through a process called convergence, without requiring manual reconfiguration once they’re set up.
Key Dynamic Protocols
Dynamic protocols are classified as distance-vector (RIP, EIGRP) or link-state (OSPF):
- RIP (Routing Information Protocol) — a simple distance-vector protocol using hop count as its metric, capped at 15 hops. Fine for small networks, but its slow convergence makes it a poor fit for modern enterprises. CCNA study generally focuses on RIPv2 for classless routing support.
- OSPF (Open Shortest Path First) — a link-state protocol using Dijkstra’s Shortest Path First algorithm to build a topology map. It supports hierarchical areas, converges quickly, and supports equal-cost load balancing. As an open standard, OSPF works well in multi-vendor environments. Key mechanisms include Link-State Advertisements (LSAs), Designated Routers on multi-access networks, and IPv6 support via OSPFv3.
- EIGRP (Enhanced Interior Gateway Routing Protocol) — a Cisco-proprietary hybrid protocol combining distance-vector and link-state characteristics, using the Diffusing Update Algorithm (DUAL) for loop-free paths and feasible successors. It converges rapidly, supports unequal-cost load balancing, and allows summarization at any point in the network — a strong fit for Cisco-only environments.
- BGP (Border Gateway Protocol) — a path-vector protocol used for routing between autonomous systems, driven by policy rather than simple metrics. For CCNP-level understanding, know the distinction between eBGP (between different autonomous systems) and iBGP (within the same autonomous system), along with attributes like AS-Path.
Using Static and Dynamic Routing Together
Routers can combine static and dynamic routing for flexibility. Static routes, with an Administrative Distance (AD) of 1, take precedence over dynamic routes by default — for example, over OSPF’s AD of 110. Two common patterns:
- Floating static routes — backup routes configured with an AD higher than the primary dynamic protocol’s, so they only activate if the dynamic route fails.
- Default routes — a static default for internet access, e.g.
ip route 0.0.0.0 0.0.0.0 [next-hop].
Router(config)# ip route 10.0.0.0 255.0.0.0 172.16.1.1 200This configures a floating static route to 10.0.0.0/8 with an AD of 200 — deliberately set higher than the common IGP defaults (EIGRP 90, OSPF 110, RIP 120) — so it’s only used if the dynamic route to that destination becomes unavailable.
When to Use Each
- Static routing fits small networks, stub areas, high-security zones, CCNA labs with predictable paths, and simple single-uplink edge deployments.
- Dynamic routing fits large, changing networks. Use OSPF for multi-vendor environments; use EIGRP where the network is Cisco-only and fast convergence matters most. CCNP-level study should cover both in depth.
Comparison Table
| Aspect | Static Routing | Dynamic Routing |
|---|---|---|
| Configuration | Manual | Automatic via protocols |
| Scalability | Low (small networks) | High (large networks) |
| Overhead | Low CPU and bandwidth usage | Higher, due to route updates |
| Adaptability | None | High (convergence) |
| Security | Higher (no route advertisements) | Lower by default, mitigated with authentication |
| Failure recovery | Requires manual intervention | Automatic rerouting |
Administrative Distance (AD)
Administrative Distance determines which route a router prefers when it learns about the same destination from more than one source. Lower values win:
| Source | Administrative Distance |
|---|---|
| Connected | 0 |
| Static | 1 |
| External BGP (eBGP) | 20 |
| Internal EIGRP | 90 |
| OSPF | 110 |
| RIP | 120 |
| External EIGRP | 170 |
| Internal BGP (iBGP) | 200 |
A commonly tested distinction: eBGP (between routers in different autonomous systems) has an AD of 20, while iBGP (between routers in the same autonomous system) has an AD of 200 — a full order of magnitude higher. That gap reflects that eBGP-learned routes are generally trusted more readily than iBGP-learned routes during path selection. Mixing up these two values is one of the most common AD-related mistakes in CCNA/CCNP study, so it’s worth memorizing this pair specifically rather than treating “BGP” as a single AD value.
Use show ip route to verify active routes, and ip route ... [distance] to adjust AD manually if a conflict needs resolving.
Advantages and Disadvantages
Advantages of static routing
- Enhanced security — no route advertisements to intercept or spoof.
- Low resource use — minimal CPU and bandwidth overhead.
- Predictable paths — consistent, known traffic flow.
Disadvantages of static routing
- Manual maintenance — every change needs administrator time and care.
- No fault tolerance — failures require manual intervention to route around.
- Complexity grows fast — misconfiguration risk climbs as the network grows.
Advantages of dynamic routing
- Fast initial setup with automated ongoing maintenance.
- Automatic adaptation to topology changes, no manual input needed.
- Scales efficiently as the network grows.
Disadvantages of dynamic routing
- Route advertisements are a potential attack surface — mitigate with MD5 authentication.
- Continuous neighbor handshakes add bandwidth overhead.
- Path selection is less predictable than a fixed static route.
Redistributing Static Routes into a Dynamic Protocol
Beyond running static and dynamic routing side by side, routers can also inject static routes into a dynamic protocol’s advertisements, so other routers in the domain learn about them automatically instead of needing their own static entries. This is called redistribution, and it’s a common CCNP-level task — for example, advertising a static default route for internet access out through OSPF so every router in the OSPF domain learns it without manual configuration on each one.
Router(config)# router ospf 1
Router(config-router)# default-information originateFor redistributing static routes generally, rather than just a default route:
Router(config)# router eigrp 100
Router(config-router)# redistribute staticRedistribution needs care. Metrics don’t translate directly between protocols — OSPF uses cost, EIGRP uses a composite metric based on bandwidth and delay, and a redistributed route needs a seed metric assigned or it may not be advertised at all. Redistributing between two dynamic protocols, or redistributing static routes into more than one dynamic protocol at the same boundary, also creates a real risk of routing loops if it isn’t filtered carefully with route maps or distribute lists. For CCNP study, understand redistribution as a tool for connecting routing domains — not something to reach for by default when a simpler design would do.
CCNP-Level Considerations
Troubleshooting
- Use
show ip routeto view the routing table, andpingortracerouteto test reachability. debug ip routinggives real-time updates, but use it cautiously on production devices and always follow withundebug all.- Check for AD conflicts or misconfigured next-hops as a first troubleshooting step.
IPv6 Considerations
- Static:
ipv6 route 2001:db8::/32 2001:db8:1::1 - Dynamic: use OSPFv3 or EIGRP for IPv6 routing.
Security Enhancements
- Enable MD5 authentication in OSPF with
ip ospf authentication message-digest. - Apply access control lists to filter which routes get advertised or accepted.
Case Studies
- Small office — a 10-user network relies on a single static route for its one internet uplink, keeping configuration and resource use minimal.
- Enterprise campus — a 500-user site runs OSPF for internal routing, backed by static default routes for redundancy at the network edge.
Example Topology
[See Topology Diagram: Static Default Route Backing Up an OSPF Core]
A practical lab combines both approaches: an OSPF-enabled core connects distribution routers dynamically, while each edge router also holds a static default route pointing toward the internet uplink. Configure OSPF as the primary path for internal routes, then add a floating static route with an AD higher than OSPF’s 110 as a backup for the default route. Break the OSPF adjacency deliberately and confirm the static route activates — this is one of the most common redundancy patterns tested at CCNA and CCNP level.
Conclusion
For CCNA study, master static routing basics and simple dynamic setups like RIP to build a solid foundation. For CCNP, go deeper into OSPF, EIGRP, and BGP, including AD adjustments and security measures — and be precise about the eBGP (20) vs. iBGP (200) Administrative Distance distinction specifically, since it’s frequently tested. Practice with Packet Tracer or GNS3 to reinforce these concepts hands-on.
Frequently Asked Questions
When is dynamic routing preferred over static routes?
Dynamic routing protocols such as OSPF, BGP, and EIGRP are generally preferred in large or expanding networks, where manually configuring and maintaining static routes across many routers and subnets becomes time-consuming, error-prone, and hard to scale. In environments with frequent topology changes — redundant links, branch additions, link failures — dynamic routing detects the change and converges on an alternate path automatically, often within seconds, which static routes simply cannot do without manual intervention. Dynamic protocols also calculate best paths using metrics like cost, bandwidth, and delay, and can load-balance across equal-cost paths, while static routes stay fixed regardless of changing conditions.
What is the difference between static and dynamic routing?
Static routing uses manually configured paths that stay fixed until an administrator changes them, while dynamic routing automatically discovers and adjusts routes using protocols like OSPF, EIGRP, and BGP. Static routing is simpler and more secure by default, since it advertises no routing information for an attacker to intercept or spoof, while dynamic routing is more scalable and adaptive, rerouting around failures without manual work. Most production networks use both together: dynamic protocols in the core for adaptability and scale, with static routes at the edge or as backups where simplicity and predictability matter more.
What is the Administrative Distance for BGP?
BGP has two different Administrative Distance values depending on the relationship type, and mixing them up is a common mistake. External BGP (eBGP), used between routers in different autonomous systems, has an AD of 20. Internal BGP (iBGP), used between routers within the same autonomous system, has a much higher AD of 200. That gap reflects that eBGP-learned routes are generally given more trust during path selection than iBGP-learned routes, and this specific eBGP-versus-iBGP distinction shows up frequently in CCNA and CCNP exam questions.
How do floating static routes work?
A floating static route is a static route deliberately configured with a higher Administrative Distance than a network’s primary dynamic routing protocol, so it sits inactive in the routing table under normal conditions and only becomes active if the dynamic route to that destination is lost. For example, a floating static route with an AD of 200 stays out of the routing table as long as OSPF (AD 110) or EIGRP (AD 90) is successfully providing a route to the same destination, activating automatically as a backup only once that dynamic route disappears. This gives a network simple, low-maintenance redundancy without needing a second dynamic routing protocol.
