CCNA lab 22 of 46
Single-area OSPFv3 for IPv6
Route an IPv6-only network with OSPFv3: set 32-bit router IDs on routers with no IPv4 at all, enable OSPF per interface, make the links point-to-point, keep the LANs passive and originate an IPv6 default route.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 5,120 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 22 - Single-area OSPFv3 for IPv6
- Level
- Intermediate
- Time
- About 45 minutes
- Nodes need
- 5 vCPU, 5,120 MB
- Smallest plan
- Lite
The scenario
Cobalt Games is building a greenfield studio network that is IPv6 only: there's no IPv4 address anywhere on the routers. The three routers form a triangle; the artists' LAN is behind R1, the build servers' LAN behind R3, and R3 also connects to the IPv6 Internet. You'll route it all with OSPFv3, area 0.
| Router | Interfaces | Router ID |
|---|---|---|
| R1 | Gi0/0 2001:db8:0:12::1 (R2), Gi0/1 2001:db8:0:13::1 (R3), Gi0/2 2001:db8:22:1::1/64 (LAN), link-local fe80::1 | 1.1.1.1 |
| R2 | Gi0/0 2001:db8:0:12::2 (R1), Gi0/1 2001:db8:0:23::2 (R3), link-local fe80::2 | 2.2.2.2 |
| R3 | Gi0/0 2001:db8:0:23::3 (R2), Gi0/1 2001:db8:0:13::3 (R1), Gi0/2 2001:db8:22:3::1/64 (LAN), Lo0 2001:db8:ffff::1 (Internet), link-local fe80::3 | 3.3.3.3 |
All /64s. R3 has a static IPv6 default route to Null0 standing in for its ISP. PC1 and PC2 use SLAAC.
What you’ll practise
- Compare OSPFv3 with OSPFv2
- Configure router IDs on IPv6-only routers
- Enable OSPFv3 per interface and make LAN interfaces passive
- Use the point-to-point network type and read link-local next hops in the IPv6 routing table
- Originate a default route into OSPFv3
The tasks
- Know what changes in OSPFv3
- Start the process with a router ID
- Enable OSPFv3 on the interfaces
- Make the links point-to-point
- Read the IPv6 routes
- Originate a default route
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 - R2
Gi0/1to R3Gi0/0 - R1
Gi0/1to R3Gi0/1 - R1
Gi0/2to PC1eth0 - R3
Gi0/2to 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 |
| R3 | 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 |
| 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
22 - Single-area OSPFv3 for 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 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.