JNCIA-Junos lab 10 of 15
Routing policy and route filters
Control exactly which routes OSPF advertises and installs. You see what the default policies do, export the depot's customer routes with a precise route filter, keep the guest network private, chain policies, and stop HQ installing a partner network while it stays in the OSPF database.
Run this lab
It needs Standard: its 3 nodes are set to 12 vCPU and 15,360 MB in total.
In your workspace: Shared, then JNCIA-Junos JN0-106 guided labs, then 10 - Routing policy and route filters
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 12 vCPU, 15,360 MB
- Smallest plan
- Standard
The scenario
OSPF is running between HQ, WH and DEPOT. DEPOT also has static routes to networks behind other routers on the depot LAN:
| Prefix | Next hop | What it is | Rule |
|---|---|---|---|
| 10.40.0.0/24, 10.40.1.0/24, 10.40.2.0/24 | 10.4.0.254 | Customer sites | Advertise to everyone, as OSPF external type 1 with metric 50 |
| 10.40.3.0/25 | 10.4.0.254 | A customer test subnet | Never advertise: only /24s from 10.40.0.0/16 go out |
| 10.41.0.0/16 | 10.4.0.253 | Partner network | Advertise (the warehouse needs it), but HQ must not install it |
| 192.168.50.0/24 | 10.4.0.250 | Depot guest Wi-Fi | Never advertise |
What you’ll practise
- Explain the default import and export policies of OSPF
- Write policy statements with terms, from and then, and apply them as import or export policies
- Use route-filter match types: exact, orlonger, longer, upto, prefix-length-range and through
- Predict how a policy chain is evaluated, including the protocol's default action
- Show the different effects of export and import policy on the database and the routing table
- Test a policy before applying it with test policy
The tasks
- What the default policies do
- Your first export policy
- A policy chain
- Import policy: in the database, not in the table
- Practise the match types
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- HQ
ge-0/0/0to DEPOTge-0/0/0 - HQ
ge-0/0/1to WHge-0/0/0 - WH
ge-0/0/1to DEPOTge-0/0/1 - HQ
ge-0/0/2to HQ-LAN (network) - WH
ge-0/0/2to WH-LAN (network) - DEPOT
ge-0/0/2to DEPOT-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| WH | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| DEPOT | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIA-Junos JN0-106 guided labs.Open
10 - Routing policy and route filtersand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More JNCIA-Junos labs
Related labs in other courses
CloudLabBox is independent of Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.