CloudLabBox
Try the free demo

CCNP ENARSI lab 4 of 35

Troubleshooting EIGRP

Six faults were introduced during a weekend change window in a mixed classic and named-mode EIGRP network. Work through the tickets with a structured method, find each root cause and fix it without breaking anything else.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 2,560 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 04 - Troubleshooting EIGRP

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
5 vCPU, 2,560 MB
Smallest plan
Lite

The scenario

Harbourline Shipping changed its WAN over the weekend. HQ (R1) connects through two WAN routers (R2 and R3, still classic EIGRP) to the regional hub (R4), which serves the regional server LAN 10.4.4.0/24 and the branch router (R5). Everyone runs AS 100; R1, R4 and R5 use named mode HSL. On Monday morning the service desk logged these tickets:

  1. "R4 only sees one of the two WAN routers." (network team)
  2. "R3 keeps logging neighbour changes about K-values." (network monitoring)
  3. "The branch router R5 has no EIGRP neighbours at all." (branch manager)
  4. "HQ can't reach the regional servers on 10.4.4.0/24." (application team)
  5. "Even when the branch link is up, HQ can't reach the branch PCs (10.5.5.0/24)." (service desk)
  6. "Branch phones (10.5.6.0/24) can't register with the HQ call server." (voice team)

The design documents say: all routers in AS 100 with default K-values; the R4–R5 link uses MD5 key chain HSL-KEYS, key 1, key string Harb0ur-Key (with a zero); R5 is the only stub router (connected and summary); R1 accepts every EIGRP route. Some tickets may share a cause, and some symptoms only appear after an earlier fault is fixed.

DeviceInterfaceAddressConnects to
R1Gi0/0 / Gi0/110.0.12.1/24 / 10.0.13.1/24R2 / R3
R1Lo110.1.1.1/24HQ LAN
R2Gi0/110.0.24.2/24R4 Gi0/0
R3Gi0/110.0.34.3/24R4 Gi0/1
R4Gi0/210.0.45.4/24R5 Gi0/0 10.0.45.5
R4Lo110.4.4.1/24regional servers
R5Lo1 / Lo210.5.5.1/24 / 10.5.6.1/24branch users / branch voice
R*n*Lo010.255.0.n/32router ID n.n.n.n

What you’ll practise

  • Use a layered method: interfaces, neighbours, topology table, routing table, then filters
  • Diagnose missing adjacencies caused by network statements, K-values and authentication
  • Diagnose missing routes caused by af-interface shutdown, distribute lists and stub misconfiguration
  • Tell a real fault from a harmless difference such as unequal hello timers

The tasks

  1. Gather facts before you change anything
  2. Fix the missing adjacencies (tickets 1–3)
  3. Fix the missing routes (tickets 4–6)
  4. Prove the service is restored

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 EIGRP5 nodes, 5 links. Every link is listed as text below the diagram.R1R2R3R4R5Gi0/2Gi0/0Gi0/0Gi0/0Gi0/1Gi0/0Gi0/1Gi0/0Gi0/1Gi0/1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to R2 Gi0/0
  • R1 Gi0/1 to R3 Gi0/0
  • R2 Gi0/1 to R4 Gi0/0
  • R3 Gi0/1 to R4 Gi0/1
  • R4 Gi0/2 to R5 Gi0/0
Nodes in Troubleshooting EIGRP, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R3Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R4Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R5Cisco 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 CCNP ENARSI 300-410 guided labs.

  3. Open 04 - Troubleshooting EIGRP 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.