CloudLabBox
Try the free demo

HCIP-Datacom Core lab 6 of 14

Route import and policy-based routing

Join an OSPF domain to an IS-IS domain at two points, fix the suboptimal path that mutual import creates with tags and preference, filter what crosses the border, then override the routing table with policy-based routing.

Run this lab

It needs Standard: its 6 nodes are set to 6 vCPU and 10,240 MB in total.

In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 06 - Route import and policy-based routing

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 6 vCPU and 10,240 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 100 minutes
Nodes need
6 vCPU, 10,240 MB
Smallest plan
Standard

The scenario

Northwind's English sites run OSPF and the Scottish sites still run IS-IS. They need to share routes now, with no outage, so R2 and R3 will run both and import between them. One network, 192.168.45.0/24, is Scottish management and must never reach England. Finance also wants PC1's traffic to Scotland to pass through R3, whatever the routing table says, because that's where a new audit tap will go.

RouterRoleLoopBack0Interfaces
R1OSPF only1.1.1.1GE0/0/0 10.0.12.1/24, GE0/0/1 10.0.13.1/24, GE0/0/2 192.168.1.1/24 (PC1 .10). Static 172.16.9.0/24, already in OSPF as an external
R2Border2.2.2.2GE0/0/0 10.0.12.2/24 (OSPF), GE0/0/1 10.0.24.2/24 (IS-IS)
R3Border3.3.3.3GE0/0/0 10.0.13.3/24 (OSPF), GE0/0/1 10.0.34.3/24 (IS-IS)
R4IS-IS only4.4.4.4GE0/0/0 10.0.24.4/24, GE0/0/1 10.0.34.4/24, GE0/0/2 192.168.4.1/24 (PC2 .10), LoopBack1 192.168.45.1/24 (management)

What you’ll practise

  • Import routes between OSPF and IS-IS with a route policy
  • Explain why mutual import at two points leads to bad paths
  • Use tags to stop routes going back where they came from
  • Change a route's preference with a route policy
  • Filter advertised routes with filter-policy export
  • Redirect forwarding with a traffic policy, and redirect locally generated traffic with local PBR

The tasks

  • Task 0: Load the starting configuration
  • Concept: importing routes
  • Task 1: Import in both directions at both borders
  • Concept: tags and route policies
  • Task 2: Stop the feedback with tags
  • Concept: filter-policy on export
  • Task 3: Keep management in Scotland
  • Concept: policy-based routing
  • Task 4: Send PC1 through R3
  • Task 5: Send R1's own traffic through R2

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 Route import and policy-based routing6 nodes, 6 links. Every link is listed as text below the diagram.R1R2R3R4PC1PC2GE0/0/2eth0GE0/0/2eth0GE0/0/0GE0/0/0GE0/0/1GE0/0/0GE0/0/1GE0/0/0GE0/0/1GE0/0/1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 GE0/0/0 to R2 GE0/0/0
  • R1 GE0/0/1 to R3 GE0/0/0
  • R2 GE0/0/1 to R4 GE0/0/0
  • R3 GE0/0/1 to R4 GE0/0/1
  • R1 GE0/0/2 to PC1 eth0
  • R4 GE0/0/2 to PC2 eth0
Nodes in Route import and policy-based routing, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R2Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R3Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R4Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 HCIP-Datacom Core H12-821 guided labs.

  3. Open 06 - Route import and policy-based routing 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 HCIP-Datacom Core labs

All HCIP-Datacom Core labs

Related labs in other courses

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