CCNA lab 5 of 46
IPv6 address types with EUI-64 and SLAAC
Bring IPv6 to a small firm: write addresses in short form, configure global, unique local, link-local and EUI-64 addresses, watch hosts address themselves with SLAAC, and route between three IPv6 LANs.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 4,608 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 05 - IPv6 address types with EUI-64 and SLAAC
- Level
- Beginner
- Time
- About 55 minutes
- Nodes need
- 5 vCPU, 4,608 MB
- Smallest plan
- Lite
The scenario
Quayside Architects' Internet provider has given them 2001:db8:5::/48, and the partners want the office ready for IPv6 before the new cloud services arrive. The head office router (R1) has two LANs: LAN A with a desktop (PC1) and LAN B with a Linux file server (H1). The studio router (R2) has LAN C with PC2. The routers are connected and their interfaces are up, but nothing has an IPv6 address.
| Device | Interface | IPv6 address | Notes |
|---|---|---|---|
| R1 | Gi0/1 | 2001:db8:5:10::1/64, link-local fe80::1 | LAN A |
| R1 | Gi0/2 | 2001:db8:5:11::1/64, link-local fe80::1 | LAN B |
| R1 | Gi0/0 | 2001:db8:0:12::/64 EUI-64, link-local fe80::1 | WAN |
| R1 | Loopback0 | fd00:5:0:1::1/64 (unique local) | internal services |
| R2 | Gi0/0 | 2001:db8:0:12::/64 EUI-64, link-local fe80::2 | WAN |
| R2 | Gi0/1 | 2001:db8:5:20::1/64, link-local fe80::2 | LAN C |
| PC1, PC2 | eth0 | SLAAC | |
| H1 | eth0 | SLAAC plus static 2001:db8:5:11::50/64 | file server |
Topology: PC1 — R1 Gi0/1 · H1 — R1 Gi0/2 · R1 Gi0/0 — R2 Gi0/0 · R2 Gi0/1 — PC2.
What you’ll practise
- Compress and expand IPv6 addresses correctly
- Configure global unicast, unique local, link-local, EUI-64 and anycast addresses on IOS
- Calculate a modified EUI-64 interface ID by hand
- Identify the multicast groups an IPv6 router joins and why
- Let hosts configure themselves with SLAAC and route IPv6 with static and default routes
The tasks
- Read and write IPv6 addresses
- Configure global and unique local addresses
- Use modified EUI-64 on the WAN link
- Set memorable link-local addresses
- Explore multicast and anycast
- Let the hosts address themselves (SLAAC)
- Route between the LANs
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 PC1eth0 - R1
Gi0/2to H1eth0 - R2
Gi0/1to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 1,024 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| PC2 | 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
CCNA 200-301 guided labs.Open
05 - IPv6 address types with EUI-64 and SLAACand 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 CCNA 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.