JNCIP-ENT lab 4 of 19
BGP route selection and next hops
Find why iBGP routes are hidden, fix next hop resolution, read why Junos chose each path, and steer traffic with local preference, prepending and MED.
Run this lab
It needs Standard: its 5 nodes are set to 11 vCPU and 11,776 MB in total.
In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 04 - BGP route selection and next hops
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 11 vCPU, 11,776 MB
- Smallest plan
- Standard
The scenario
Northmere (AS 64500) has two border routers with one ISP each. R3 is an internal router with the head office LAN. All the BGP sessions are configured and up, and OSPF runs inside the network, but something is wrong: routes from the other border router aren't being used. You'll find out why, then read how Junos picks a best path, and then bend that choice in both directions.
The ISPs use these prefixes to give you something to compare. Both ISPs originate the shared ones:
| Prefix | Who originates it | What's different |
|---|---|---|
| 203.0.113.0/24 | ISP-A | Its own |
| 198.51.100.0/24 | ISP-B | Its own |
| 192.0.2.0/24 | Both | Nothing |
| 100.64.1.0/24 | Both | ISP-A sends origin incomplete |
| 100.64.2.0/24 | Both | ISP-A sends MED 50, ISP-B sends MED 20 |
| Device | Interface | Address |
|---|---|---|
| R1 | ge-0/0/0, ge-0/0/2, lo0 | 10.0.12.1/30, 10.0.13.1/30, 10.255.0.1/32 |
| R1 | ge-0/0/1 | 198.18.1.1/30, to ISP-A at .2 |
| R2 | ge-0/0/0, ge-0/0/2, lo0 | 10.0.12.2/30, 10.0.23.1/30, 10.255.0.2/32 |
| R2 | ge-0/0/1 | 198.18.2.1/30, to ISP-B at .2 |
| R3 | Gi0/0, Gi0/1, Lo0, Lo10 | 10.0.13.2/30, 10.0.23.2/30, 10.255.0.3/32, 10.60.1.1/24 |
This course uses AS numbers from the range set aside for documentation, so that private AS numbers can mean something in a later lab.
What you’ll practise
- Diagnose an unresolved protocol next hop
- Fix it with next-hop self
- Work through the BGP selection steps from show route detail
- Steer outbound traffic with local preference
- Steer inbound traffic with AS path prepending
- Stop your AS from carrying transit traffic
- Compare MED across neighbouring ASs
The tasks
- Find the hidden routes
- Fix next hop resolution
- Read how Junos chose
- Steer outbound traffic with local preference
- Advertise your network and steer inbound traffic
- Compare MED between different ISPs
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
- R1
ge-0/0/0to R2ge-0/0/0 - R1
ge-0/0/1to ISP-AGi0/0 - R2
ge-0/0/1to ISP-BGi0/0 - R1
ge-0/0/2to R3Gi0/0 - R2
ge-0/0/2to R3Gi0/1 - ISP-A
Gi0/1to ISP-BGi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R2 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISP-A | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISP-B | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIP-ENT JN0-650 guided labs.Open
04 - BGP route selection and next hopsand 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
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.