CloudLabBox
Try the free demo

JNCIP-ENT lab 3 of 19

Routing policy in depth

Control what leaves an OSPF network with match types, prefix lists, policy chains and subroutines, and prove each one with test policy before you apply it.

Run this lab

It needs Standard: its 3 nodes are set to 9 vCPU and 10,752 MB in total.

In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 03 - Routing policy in depth

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 9 vCPU and 10,752 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 80 minutes
Nodes need
9 vCPU, 10,752 MB
Smallest plan
Standard

The scenario

R1 is Northmere's edge router. It holds static routes for partners, customers and a test network, and none of them are in OSPF yet. You'll write the policies that decide which ones go out, and how. Everything here is a tool you'll use again in the BGP labs: match types, prefix lists, chains, subroutines, expressions and test policy. The same policy language works for every protocol, and only the default action changes.

DeviceInterfaceAddress
R1ge-0/0/0, lo010.0.12.1/30, 10.255.0.1/32
R2ge-0/0/0, ge-0/0/1, lo010.0.12.2/30, 10.0.23.1/30, 10.255.0.2/32
R3Gi0/0, Lo010.0.23.2/30, 10.255.0.3/32

OSPF area 0 already runs across all three. R1's static discard routes:

GroupRoutes
Partners172.20.1.0/24, 172.20.2.0/24, 172.20.16.0/20, 172.20.17.0/25, 172.20.32.0/20
Customers192.168.50.0/24, 192.168.51.0/24
Test network10.99.1.0/24, 10.99.2.0/24

The rules: partners get out as /20 or shorter only. Customers get out with metric 200. The test network never gets out.

What you’ll practise

  • Choose between route-filter match types
  • Use prefix lists, prefix-list-filter and apply-path
  • Work out how a policy chain ends, and fix one that breaks
  • Use a policy as a subroutine
  • Set OSPF external types and tags
  • Explain what an OSPF import policy can and can't do

The tasks

  1. Choose the right match type
  2. Use a prefix list
  3. Build a policy chain
  4. Call a policy as a subroutine
  5. Set the external type and a tag
  6. Filter with an OSPF import policy

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.

Topology of Routing policy in depth3 nodes, 2 links. Every link is listed as text below the diagram.R1R2R3ge-0/0/0ge-0/0/0ge-0/0/1Gi0/0
3 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 ge-0/0/0 to R2 ge-0/0/0
  • R2 ge-0/0/1 to R3 Gi0/0
Nodes in Routing policy in depth, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
R2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
R3Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder JNCIP-ENT JN0-650 guided labs.

  3. Open 03 - Routing policy in depth and 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 JNCIP-ENT labs

All JNCIP-ENT labs

Related labs in other courses

CloudLabBox is independent of Cisco and Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.