CCNP ENARSI lab 1 of 35
EIGRP classic and named mode for IPv4 and IPv6
Run classic-mode and named-mode EIGRP side by side in one autonomous system, for IPv4 and IPv6, and learn to read the neighbour, topology and routing tables that every later EIGRP lab relies on.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 01 - EIGRP classic and named mode for IPv4 and IPv6
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
Northwind Freight runs classic EIGRP, AS 100 at its head office (R1 and R2). The network team has just installed two routers for the new regional hub (R3 and R4), and the design standard now says every new router uses named-mode EIGRP with the instance name NWF. Both groups must share one routing domain, so the classic and named routers have to form neighbours and exchange routes. At the same time the company is switching on IPv6, which every link already has addresses for.
Your job is to bring up EIGRP for IPv4 and IPv6 on all four routers, using the mode each site's standard asks for, and to prove the two PCs can reach each other.
| Device | Interface | IPv4 | IPv6 | Connects to |
|---|---|---|---|---|
| R1 | Gi0/0 | 10.0.12.1/24 | 2001:db8:0:12::1/64, fe80::1 | R2 Gi0/0 |
| R1 | Gi0/1 | 10.0.13.1/24 | 2001:db8:0:13::1/64, fe80::1 | R3 Gi0/1 |
| R1 | Gi0/2 | 192.168.1.1/24 | 2001:db8:1::1/64 | PC1 (HQ LAN) |
| R2 | Gi0/1 | 10.0.24.2/24 | 2001:db8:0:24::2/64, fe80::2 | R4 Gi0/1 |
| R2 | Lo1 | 192.168.2.1/24 | 2001:db8:2::1/64 | HQ server LAN (simulated) |
| R3 | Gi0/0 | 10.0.34.3/24 | 2001:db8:0:34::3/64, fe80::3 | R4 Gi0/0 |
| R3 | Lo1 | 192.168.3.1/24 | 2001:db8:3::1/64 | Regional office LAN (simulated) |
| R4 | Gi0/2 | 192.168.4.1/24 | 2001:db8:4::1/64 | PC4 (regional LAN) |
| R*n* | Lo0 | 10.255.0.n/32 | 2001:db8:255::n/128 | router ID n.n.n.n |
| PC1 / PC4 | eth0 | 192.168.1.10 / 192.168.4.10 | – | gateways .1 |
Topology: a square. R1–R2 and R1–R3 from HQ, R2–R4 and R3–R4 into the region. Every interface is already addressed and up; no routing protocol is running.
What you’ll practise
- Enable classic EIGRP for IPv4 with precise network statements, a fixed router ID and a passive LAN interface
- Build the same AS in named mode with an IPv4 address family and af-interface settings
- Prove that classic and named routers form adjacencies and exchange routes
- Add IPv6: classic ipv6 router eigrp on two routers and the named-mode IPv6 address family on the others
- Interpret show ip eigrp neighbors, show ip eigrp topology, show ip protocols and show eigrp protocols
The tasks
- Check the starting point
- Classic EIGRP for IPv4 on R1 and R2
- Named-mode EIGRP for IPv4 on R3 and R4
- Read the EIGRP tables
- Classic EIGRP for IPv6 on R1 and R2
- The named-mode IPv6 address family on R3 and R4
- Test end to end
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
Gi0/0to R2Gi0/0 - R1
Gi0/1to R3Gi0/1 - R2
Gi0/1to R4Gi0/1 - R3
Gi0/0to R4Gi0/0 - R1
Gi0/2to PC1eth0 - R4
Gi0/2to PC4eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R4 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC4 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENARSI 300-410 guided labs.Open
01 - EIGRP classic and named mode for IPv4 and IPv6and 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
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.