In the JNCIA-JUNOS exam domain 'Routing Fundamentals', you must understand how a router makes forwarding decisions without relying on dynamic routing protocols. This is protocol-independent routing: the art of manually telling a router where to send packets, which forms the bedrock of even the most complex networks.
Jump to a section
A simple way to picture Protocol-Independent Routing (Static Routes and Defaults)
Have you ever been the first person to move into a brand-new housing estate, where the streets don't even appear on your phone's sat-nav yet?
The estate has one main entrance road that connects to the main highway, and then a maze of smaller cul-de-sacs branching off it. You know exactly where you want to go (your friend's new house on 'Cypress Close'), but your GPS keeps saying 'unknown road'. You have two choices. First, you can manually program your GPS with every single turn: 'Turn left at the entrance, drive 200 metres, turn right at the red post-box, then first left into Cypress Close.' That is a static route -- you are telling the navigation system exactly which path to take, and it will use that instruction every single time, even if a better road is built later. Second, you can tell your GPS something simpler: 'If I don't have a specific map for a street, just take me to the main highway and let me figure it out from there.' That is your default route. In this analogy, your GPS is the routing table inside a Juniper router. Every street name is a destination network. The manually typed directions are static routes. The 'just get me to the highway' fallback is the default route.
A router's primary job is to look at a packet's destination IP address and decide where to send it next. It makes this decision by consulting its routing table, which is a list of known destinations (called prefixes or networks) and the corresponding instructions for reaching them (the next hop).
The routing table can be populated in two fundamental ways. One way is through dynamic routing protocols, where routers talk to each other and automatically learn about networks. The other way, and the focus of this chapter, is through static routing. 'Static' means 'unchanging' -- a network administrator manually enters a route into the configuration. Because this route is not learned from another router, it is called 'protocol-independent'. It does not matter if you are running OSPF, BGP, or no routing protocol at all; a static route works the same way.
How a Static Route is Constructed
Every static route has two mandatory components: the destination prefix and the next hop. The destination prefix tells the router *which network* you are trying to reach (for example, 192.168.2.0/24 -- where the /24 is the subnet mask indicating the size of the network). The next hop tells the router *where to send the packet* to get there (for example, 10.0.0.1 -- the IP address of the neighbouring router).
The command structure on a Juniper Junos device looks like this:
routing-options static route 192.168.2.0/24 next-hop 10.0.0.1This is the simplest form. You can also add a 'preference' value (also called administrative distance) to influence which route is chosen if there are multiple routes to the same destination. A lower preference number means a more preferred route. The default preference for a static route is 5.
The Default Route (The 'Gateway of Last Resort')
A default route is a special kind of static route. Its destination prefix is 0.0.0.0/0, which in IP routing means 'every possible IP address not otherwise listed in the routing table'. It is the catch-all instruction. When a router receives a packet destined for a network it does not specifically know about, it checks for this default route. If it exists, the router forwards the packet there. If it does not exist, the router drops the packet and sends an ICMP 'Destination Unreachable' message back to the sender.
The command for a default route on Junos is:
routing-options static route 0.0.0.0/0 next-hop 10.0.0.1This is critical in almost every network. Without a default route, each router would need a specific route to every public IP address on the internet -- an impossible task.
Why Use Static Routes?
Static routes are simple, secure, and predictable. They do not consume bandwidth for routing protocol updates, they do not introduce security vulnerabilities associated with routing protocols, and they do not change unless a human changes them. They are ideal for small networks, stub networks (networks with only one connection to the outside world), and for creating backup paths with a higher preference value.
Why Not Always Use Static Routes?
The big disadvantage is administrative overhead. In a large network with dozens of routers and hundreds of networks, manually entering every route is error-prone and unsustainable. If a link fails, a static route does not automatically adjust -- the router still tries to send traffic out the broken link, causing a black hole. Dynamic protocols detect changes and reroute around failures automatically.
Access the Junos device
Connect to your Juniper device via SSH or console cable and log in. You enter the CLI (command-line interface) where you will type configuration commands. This is the starting point for any routing configuration.
Enter configuration mode
In Junos, you cannot make changes directly in operational mode. You must type `configure` (or `edit`) to enter configuration mode. The prompt changes to indicate you are editing the active configuration. This prevents accidental changes that could disrupt the network.
Define the static route
Type the command: `set routing-options static route 10.0.0.0/24 next-hop 192.168.1.1`. Replace '10.0.0.0/24' with the destination network you want to reach, and '192.168.1.1' with the IP address of the next-hop router. This instructs the router to send all traffic destined for the 10.0.0.0/24 network to the neighbour at 192.168.1.1.
Define the default route (if needed)
For internet access, add a default route: `set routing-options static route 0.0.0.0/0 next-hop 203.0.113.1`. This tells the router, 'If you do not know where a packet goes, send it to this ISP router'. Without this step, traffic to unknown networks is dropped.
Commit the configuration
Type `commit` to apply your changes. Junos does not apply changes automatically; you must commit them. This is a safety feature that allows you to verify your configuration before making it active. After committing, you exit configuration mode with `exit`.
Verify the routes
Use `show route` to see the routing table, or `show route 10.0.0.0/24` to check a specific route. Look for the next hop and the preference value. This confirms your static route is correctly installed and active.
Imagine you are the new IT administrator for a small law firm called 'Smith & Associates'. The firm has a single office with one internet connection provided by a local ISP. Inside the office, you have a Juniper SRX firewall (which is a router/firewall hybrid) connecting the internal network (192.168.1.0/24) to the internet.
Your first task is to configure internet access. The internal network has about 50 devices: computers, printers, and a server. The ISP has given you a router at the edge of their network with an IP address of 203.0.113.1. Your Juniper device connects to that ISP router on its own interface (ge-0/0/0) with IP address 203.0.113.2.
Step-by-step, here is what you actually do:
Configure the default route: You need to tell your Juniper device, 'If you receive traffic destined for any public IP address (the internet), send it to the ISP router at 203.0.113.1.' This is the default route (0.0.0.0/0 next-hop 203.0.113.1). Without this, internal users could reach each other but could not browse the web.
Configure a static route for the server: The firm has a private web server hosted at a cloud provider. That server's public IP is 198.51.100.50. You want to ensure that traffic to that specific IP is also forwarded to the ISP, but you might also want a specific route for management. You add a static route: set routing-options static route 198.51.100.50/32 next-hop 203.0.113.1. The /32 means 'this single host'.
Testing and verification: After committing the configuration (the Junos way of applying changes), you run show route to confirm the routes are in the routing table. You see a line for 0.0.0.0/0 and one for 198.51.100.50/32. You then perform a traceroute from an internal PC to a public website like 8.8.8.8. You watch the packets leave the Juniper device out to the ISP. The network works.
Later, the firm gets a secondary internet connection (a 4G backup) for redundancy. You now configure two default routes: one to the primary ISP (preference 5) and one to the 4G router (preference 10). The lower preference (5) is active; if the primary link fails, the router automatically switches to the backup route because it is the only one left (static routes do not dynamically fail over, but the router removes the unreachable next hop from the table).
The JNCIA-JUNOS exam is heavy on configuration syntax, verification commands, and understanding the behaviour of static vs. dynamic routes. Here is exactly what you need to know for the exam.
Exam Topics for Protocol-Independent Routing
Configuring a static route: You must know the exact command structure: set routing-options static route <destination-prefix> next-hop <ip-address>. They will ask you to identify the correct syntax from multiple choices.
Configuring a default route: Same syntax, but with destination 0.0.0.0/0. They may present a scenario where a company needs internet access, and you must select the correct default route configuration.
Preference (administrative distance): You must remember that the default preference for a static route is 5. A lower preference is preferred. The exam will give you two routes to the same destination (one static with preference 10, one static with preference 5, or one static vs. an OSPF route with default preference 10). You must identify which route is active.
Verification commands: You must know show route (displays all routes), show route <destination-prefix> (shows route to a specific network), and show route protocol static (shows only static routes). They may present command output and ask you to interpret it.
Static route with 'discard' or 'reject': You may be asked about a static route pointing to 'discard' (silently drops packets) or 'reject' (drops and sends ICMP unreachable). These are used for security or to create 'blackhole' routes.
Common Traps
Forgetting the /0 on the default route: A default route is always 0.0.0.0/0. Putting 0.0.0.0 alone is incomplete in Junos.
Confusing preference with metric: 'Metric' is a dynamic routing protocol term (e.g., hop count in RIP). Junos uses 'preference' for static routes. They are not the same.
Assuming static routes are dynamic: They are not. The exam may describe a link failure and ask what happens. The answer: traffic to the static route's next hop will fail unless there is a backup static route with a higher preference.
Thinking a default route replaces all routes: A default route is only used when no more specific route exists. The router always prefers the most specific (longest prefix length) match first.
Key Definitions to Memorise
Static route: A manually configured route.
Default route: A static route to 0.0.0.0/0.
Next hop: The IP address of the neighbouring device where the router sends packets.
Preference: A value (lower is better) that determines which route is active when multiple routes to the same destination exist.
Routing table: The database of all known routes on the router.
A static route is manually configured and will never change unless a human changes it or the next-hop interface goes down.
The default route (0.0.0.0/0) is the catch-all instruction used when no more specific route matches the destination.
Junos uses the 'preference' value to choose between multiple routes to the same destination; lower preference wins.
The default preference for a static route in Junos is 5, which is lower than most dynamic protocols, making static routes preferred by default.
A static route requires both a destination prefix and a next-hop IP address in the configuration.
Static routes do not automatically reroute around a failed remote network; they only remove the route if the directly connected next-hop interface is down.
These come up on the exam all the time. Here's how to tell them apart.
Static Route
Manually configured for a specific destination prefix
Has a destination like 192.168.1.0/24
Multiple static routes can exist for different networks
Default Route
A specific type of static route with destination 0.0.0.0/0
Catches all traffic not matched by other routes
Only one default route is typically active at a time
Static Route
Configured manually by an administrator
Does not change unless edited by a human
Has a default preference of 5
Dynamic Route (OSPF)
Learned automatically via neighbour routers
Updates dynamically when the network changes
Has a default preference of 10 (OSPF internal)
Preference (Junos)
Used when comparing routes from different protocols
Lower number means more preferred route
Static route default preference is 5
Metric (OSPF cost)
Used within a single routing protocol (e.g., OSPF)
Lower number means better path (e.g., lower cost)
Metric does not cross protocol boundaries
Mistake
A static route automatically switches to a backup next hop if the primary next hop fails.
Correct
Junos does not automatically switch static routes without additional configuration. If the next hop becomes unreachable (the interface goes down), the route is removed from the routing table. But if the next hop is reachable but the remote network goes down (e.g., a router behind it fails), the static route remains in the table and traffic is blackholed.
Beginners confuse static routes with dynamic protocols that have built-in failover. They assume 'static' still somehow adapts to failures, but its whole purpose is to be manually managed and unchanging.
Mistake
The default route (0.0.0.0/0) overrides all other routes.
Correct
The default route is the least preferred route. The router always uses the most specific match (longest prefix length) in the routing table. The default route is only used when no specific route matches the destination IP.
The word 'default' sounds like a primary choice. Beginners think it is the go-to route, not the last resort. They need to understand longest-prefix-match routing logic.
Mistake
A static route only needs a destination IP address; the next hop is optional.
Correct
Every static route must have both a destination prefix and a next hop (or an interface, in some configurations). Without a next hop, the router does not know where to send the traffic.
In some simplified network diagrams, a static route is represented as a single arrow. Beginners assume that is enough, but the configuration requires an explicit next-hop IP address.
Mistake
Junos uses the word 'metric' for static route preference.
Correct
Junos uses the term 'preference' for what other vendors call 'administrative distance'. Metric is a different concept used within dynamic routing protocols (like OSPF cost or RIP hop count). They are not interchangeable.
Vendor terminology varies. Beginners coming from a CCNA background (Cisco) are used to 'administrative distance' and 'metric'. Junos uses 'preference' for the former and 'metric' only in the context of dynamic protocols.
Mistake
Configuring a static route with a higher preference makes it active immediately as a backup.
Correct
A higher preference number means the route is less preferred. It will only become active if the lower-preference route disappears from the routing table. Simply configuring a higher preference does not make it 'standby' — it is simply the less preferred option.
Beginners think 'backup' implies some kind of active standby or monitoring. In static routing, the router just picks the route with the lowest preference value that exists in the table. No 'failover' logic exists unless you add additional features like 'qualified-next-hop' or BFD.
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. A default route is a special static route that matches all traffic not matched by other routes. It is the 'catch-all' or 'gateway of last resort'.
Use the command `set routing-options static route 0.0.0.0/0 next-hop <ip-address>`. The '0.0.0.0/0' means all IPv4 addresses, and you replace `<ip-address>` with the IP of your upstream router.
Check that the next-hop IP is reachable (the interface is up and IP is configured). If the next-hop interface is down, Junos removes the static route from the table. Also ensure you committed the configuration with `commit`.
The default preference for a static route in Junos is 5. A lower preference value means the route is more preferred. You can change it with the `preference` option in the route configuration.
Yes. If you configure two static routes to the same destination with different next hops, the router uses the one with the lowest preference. If they have the same preference, Junos uses both for load balancing (ECMP).
If the directly connected interface to the next-hop router goes down, Junos removes the static route from the routing table. If the interface stays up but the remote router fails, the static route remains and traffic is blackholed (lost) until the route is manually removed or a backup route is available.
You've finished Protocol-Independent Routing (Static Routes and Defaults). Continue through the JNCIA-JUNOS study guide to build a complete picture of the exam.
Done with this chapter?