CloudLabBox
Try the free demo

CCNP ENARSI lab 35 of 35

Capstone 2: the Monday morning trouble tickets

The Merganser WAN from capstone 1 is broken after a weekend of changes: eight faults across OSPF, EIGRP, redistribution, BGP, DMVPN with IPsec and DHCP. Work the tickets like an on-call engineer: gather facts, isolate the domain, fix the root cause, and prove the service.

Run this lab

It needs Standard: its 8 nodes are set to 8 vCPU and 4,608 MB in total.

In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 35 - Capstone 2 - the Monday morning trouble tickets

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 4,608 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 120 minutes
Nodes need
8 vCPU, 4,608 MB
Smallest plan
Standard

The scenario

Merganser Group's WAN (capstone 1) was "tidied up" over the weekend by three different engineers. The design is exactly as it was: OSPF area 0 between HQ1, HQ2 and EDGE (point-to-point links); EIGRP named mode DC, AS 100, between DC and both HQ routers; mutual redistribution on HQ1 and HQ2 with tags 90/110, subnets and seed metric 1000000 10 255 1 1500; eBGP from EDGE (AS 64500) to the ISP (AS 64501) with password Merg-Bgp-Key, originating 203.0.113.0/24 and a default route into OSPF; phase 3 DMVPN with IKEv2/IPsec (key Merg-Dmvpn-Psk) and OSPF area 10 point-to-multipoint to BR1 and BR2, summarised as 10.10.0.0/16; DHCP for PC1 on BR1 (10.10.1.10 onwards).

The service desk has logged these tickets:

  1. "HQ2 has lost its link to EDGE." (OSPF alarm)
  2. "The data centre only has one path to head office."
  3. "Nobody outside the data centre can reach the data centre servers 172.20.0.0/16."
  4. "No Internet anywhere."
  5. "Branch 2 is completely offline."
  6. "PC1 at branch 1 can't get an IP address."

Some tickets have more than one cause, and some faults hide behind others. The ISP router is correct and belongs to the provider.

What you’ll practise

  • Apply a structured, layered troubleshooting method across several routing domains
  • Find faults in OSPF areas, EIGRP named mode, redistribution route maps and route-map names
  • Find BGP authentication and default-route origination faults
  • Find IKEv2 and DHCP faults
  • Verify a complex network end to end after the fix

The tasks

  1. Gather facts across the network
  2. Fix the core and the data centre (tickets 1–3)
  3. Fix the Internet (ticket 4)
  4. Fix the branches (tickets 5 and 6)
  5. Prove the whole service

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 Capstone 2 - the Monday morning trouble tickets8 nodes, 9 links. Every link is listed as text below the diagram.HQ1HQ2EDGEDCISPBR1BR2PC1Gi0/1eth0Gi0/1Gi0/1Gi0/2Gi0/0Gi0/1Gi0/0Gi0/2Gi0/0Gi0/0Gi0/0Gi0/0Gi0/1Gi0/2Gi0/0Gi0/2Gi0/1
8 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • HQ1 Gi0/0 to DC Gi0/0
  • HQ2 Gi0/0 to DC Gi0/1
  • HQ1 Gi0/1 to HQ2 Gi0/1
  • HQ1 Gi0/2 to EDGE Gi0/0
  • HQ2 Gi0/2 to EDGE Gi0/1
  • EDGE Gi0/2 to ISP Gi0/0
  • ISP Gi0/1 to BR1 Gi0/0
  • ISP Gi0/2 to BR2 Gi0/0
  • BR1 Gi0/1 to PC1 eth0
Nodes in Capstone 2: the Monday morning trouble tickets, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQ1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
HQ2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
EDGECisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
DCCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
BR1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
BR2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PC1VPCS 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 CCNP ENARSI 300-410 guided labs.

  3. Open 35 - Capstone 2 - the Monday morning trouble tickets 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 CCNP ENARSI labs

All CCNP ENARSI labs

Related labs in other courses

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