CloudLabBox
Try the free demo

JNCIS-SP lab 14 of 16

Troubleshooting IGP and BGP

Seven faults stand between a customer and the internet, in OSPF, IS-IS and BGP. Work up from the link, using the evidence, and fix only what's wrong.

Run this lab

It needs Standard: its 5 nodes are set to 8 vCPU and 13,824 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 14 - Troubleshooting IGP and BGP

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 8 vCPU and 13,824 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 90 minutes
Nodes need
8 vCPU, 13,824 MB
Smallest plan
Standard

The scenario

A contractor made "small tidying changes" to Skerry's Whitby path over the weekend and left no notes. On Monday the customer on R1 can't reach the upstream network behind PEER. There are seven faults on R1, R2 and R3, one behind another: fixing one uncovers the next. PEER is the upstream's router and is correct. Use the design sheet, work from the bottom up, and change only what's wrong.

Design sheetValue
R1 to R2OSPF area 0, point-to-point, default timers, link 10.0.12.0/30
R2 to R3IS-IS Level 2, point-to-point, link 10.0.23.0/30
R2Exports OSPF into IS-IS and IS-IS into OSPF, so the loopbacks reach each other
LoopbacksR1 10.255.0.1, R2 10.255.0.2, R3 10.255.0.3
IBGPAS 64510, a full mesh of R1, R2 and R3, between loopbacks. R3 sets next-hop self on external routes
R1Advertises the customer LAN, 198.19.1.0/24, in IBGP
EBGPR3 192.0.2.2 to PEER 192.0.2.1, AS 64496
PEERAnnounces 198.18.0.0/24
H1198.19.1.10/24, gateway 198.19.1.1

The goal: ping 198.18.0.1 -c 3 from H1 works, and you have changed nothing that the design sheet doesn't justify.

What you’ll practise

  • Work through neighbour and session problems from the bottom up
  • Recognise timer, area and family mismatches
  • Follow a BGP route through receive, hidden and advertise
  • Find a policy that never matches

The tasks

  1. OSPF between R1 and R2
  2. IS-IS between R2 and R3
  3. BGP sessions
  4. BGP routes and 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 Troubleshooting IGP and BGP5 nodes, 4 links. Every link is listed as text below the diagram.H1R1R2R3PEERge-0/0/1Gi0/0eth0ge-0/0/1ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • H1 eth0 to R1 ge-0/0/1
  • R1 ge-0/0/0 to R2 ge-0/0/0
  • R2 ge-0/0/1 to R3 ge-0/0/0
  • R3 ge-0/0/1 to PEER Gi0/0
Nodes in Troubleshooting IGP and BGP, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
R1Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R2Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R3Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
PEERCisco 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 JNCIS-SP JN0-364 guided labs.

  3. Open 14 - Troubleshooting IGP and BGP 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 JNCIS-SP labs

All JNCIS-SP 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.