IPv6 in practice lab 10 of 12
Troubleshooting 1: a Monday of IPv6 tickets
Six faults from a weekend change window sit across IOS and RouterOS. Work through three tickets from the host upwards: no address, no gateway, no routes, and then a route that goes nowhere.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,304 MB in total. That fits the free demo too.
In your workspace: Shared, then IPv6 in practice across vendors guided labs, then 10 - Troubleshooting 1 - a Monday of IPv6 tickets
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 2,304 MB
- Smallest plan
- Lite
The scenario
It's Monday morning at Kestrel Freight, and the weekend's IPv6 change window has gone badly. The engineer who made the changes is away. Three tickets are waiting. Nothing about the design has changed: the network below is what it should be, and your job is to make it match. There are six faults, and some hide behind others.
| Segment | Prefix | Addresses |
|---|---|---|
| Office LAN | 2001:db8:100:10::/64 | R1 Gi0/0 ::1 and fe80::1, H1 by SLAAC |
| R1 to R2 | 2001:db8:100:a::/64 | R1 Gi0/1 ::1, R2 Gi0/0 ::2 |
| R2 to CHR1 | 2001:db8:100:b::/64 | R2 Gi0/1 ::2, CHR1 ether1 ::3 |
| Depot LAN | 2001:db8:100:20::/64 | CHR1 ether2 ::1, H2 by SLAAC |
| Loopbacks | 2001:db8:100:ffff::1, ::2, ::3 | R1, R2, CHR1 |
The design: both LANs use SLAAC. OSPFv3 area 0 runs on every router, with point-to-point links. The ACL LAN-IN on R1 is there to let office PCs send TCP, UDP and ping from the office prefix, and nothing else, and it should stay.
Tickets:
- A. "No PC at the office has an IPv6 address."
- B. "Even once PCs have addresses, the office can't reach the depot."
- C. "No PC at the depot has an IPv6 address."
| Device | Runs | How to log in |
|---|---|---|
| R1, R2 | Cisco IOSv 15.9 | The console opens at >; enable has no password. |
| CHR1 | MikroTik RouterOS 7.14 | admin / Lab-admin1 |
| H1, H2 | Alpine Linux | root, no password. |
What you’ll practise
- Troubleshoot IPv6 from the host upwards: address, gateway, neighbours, routes, path
- Find a suppressed RA and an ACL that breaks Neighbor Discovery
- Find an OSPFv3 adjacency stuck on an MTU mismatch, and one blocked by a passive interface
- Recognise a static route that overrides a routing protocol
- Fix a RouterOS LAN that isn't advertising its prefix
The tasks
- Start the Linux hosts
- Ticket A: work from the host upwards
- Ticket B: find what's between the sites
- Ticket C: the depot LAN
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/1to R2Gi0/0 - R2
Gi0/1to CHR1ether1 - R1
Gi0/0to H1eth0 - CHR1
ether2to H2eth0
| 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 |
| CHR1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
IPv6 in practice across vendors guided labs.Open
10 - Troubleshooting 1 - a Monday of IPv6 ticketsand 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 IPv6 in practice labs
Related labs in other courses
CloudLabBox is independent of Cisco, CompTIA, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.