JNCIS-ENT lab 17 of 17
Routing capstone troubleshooting
The final routing exam: a dual-homed site with OSPF, IBGP between loopbacks, EBGP to a provider, export and import policy and a VRRP gateway, broken in six places that hide behind each other. Restore it to the design from five trouble tickets.
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 JNCIS-ENT JN0-352 guided labs, then 17 - Routing capstone troubleshooting
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 12 vCPU, 15,360 MB
- Smallest plan
- Standard
The scenario
Ashby Freight's dual-homed site was rebuilt during a weekend change. On Monday morning there are five tickets. The ISP router is correct and is not yours to change. The site contains six faults.
The design
| Item | Design |
|---|---|
| AS numbers | Ashby 65010, ISP 64500 |
| IGP | OSPF area 0 between EDGE1 and EDGE2 (ge-0/0/1, point-to-point), plus the user LAN and loopbacks as passive |
| IBGP | Between loopbacks 192.168.255.21 and 192.168.255.22, with local-address; each edge sends IBGP routes with next-hop self (policy NHS) |
| EBGP | EDGE1 to 198.51.100.1, EDGE2 to 198.51.100.5, peer AS 64500, MD5 key Ashby-BGP-2026 |
| Outbound | Both edges advertise only the aggregate 10.65.0.0/16 with community 65010:100; EDGE2 prepends 65010 65010 |
| Exit path | EDGE1 sets local preference 200 on routes from the ISP, so all outbound traffic leaves through EDGE1 |
| Gateway | VRRP group 1, address 10.65.0.1: EDGE1 master (priority 200, pre-empts), EDGE2 backup (priority 100) |
The tickets
- "EDGE1 has no BGP session to the ISP."
- "The IBGP session between the edge routers is down."
- "EDGE2 is sending its internet traffic out of the backup link."
- "The ISP sees our address block from only one router."
- "The VRRP master is the wrong router."
The test PC is the routing instance PC on EDGE2 (10.65.0.100, default route to 10.65.0.1): run its tests on EDGE2 with routing-instance PC.
What you’ll practise
- Troubleshoot an IGP adjacency that BGP depends on
- Diagnose IBGP and EBGP session failures from show bgp neighbor and the logs
- Find missing next-hop self and export policy problems from the receive and advertising views
- Diagnose a VRRP master that contradicts the design
- Verify a repaired network against its design end to end
The tasks
- Ticket 1: EDGE1 and the ISP
- Ticket 2: IBGP
- Ticket 3: EDGE2 uses the backup link
- Ticket 4: only one router advertises the block
- Ticket 5: VRRP
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
- EDGE1
ge-0/0/0to ISPge-0/0/0 - EDGE2
ge-0/0/0to ISPge-0/0/1 - EDGE1
ge-0/0/1to EDGE2ge-0/0/1 - EDGE1
ge-0/0/2to User-LAN (network) - EDGE2
ge-0/0/2to User-LAN (network) - EDGE2
ge-0/0/3to User-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| EDGE1 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| EDGE2 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| ISP | 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
JNCIS-ENT JN0-352 guided labs.Open
17 - Routing capstone troubleshootingand 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-ENT 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.