CCNP ENARSI lab 8 of 35
OSPFv3 address families for IPv4 and IPv6
Run IPv4 and IPv6 in one OSPFv3 process with address families, make the branch area totally stubby for both, summarise each family, authenticate the backbone with IPsec, and read the new OSPFv3 LSA types.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,048 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 08 - OSPFv3 address families for IPv4 and IPv6
- Level
- Intermediate
- Time
- About 65 minutes
- Nodes need
- 4 vCPU, 2,048 MB
- Smallest plan
- Lite
The scenario
Pinecrest Logistics is rolling out IPv6 and wants one routing protocol for both address families. Instead of running OSPFv2 for IPv4 and OSPFv3 for IPv6 side by side, the design uses OSPFv3 with address families: one process, one set of adjacencies per family, one way of working. HQ (R1) and the core router R2 form area 0; the branch (R3) and warehouse (R4) are area 1, which only needs a default route out. The warehouse still has an IPv4-only scanner network that must be reachable.
| Device | Interface | IPv4 | IPv6 | Area |
|---|---|---|---|---|
| R1 | Gi0/0 | 10.0.12.1/24 | 2001:db8:0:12::1/64, fe80::1 | 0 |
| R1 | Lo1 | 10.1.1.1/24 | 2001:db8:1:1::1/64 | 0 |
| R2 | Gi0/0 / Gi0/1 | 10.0.12.2 / 10.0.23.2 /24 | 2001:db8:0:12::2, 2001:db8:0:23::2 /64, fe80::2 | 0 / 1 |
| R3 | Gi0/0 / Gi0/1 | 10.0.23.3 / 10.0.34.3 /24 | 2001:db8:0:23::3, 2001:db8:0:34::3 /64, fe80::3 | 1 |
| R3 | Lo1 | 10.3.1.1/24 | 2001:db8:3:1::1/64 | 1 |
| R4 | Gi0/0 | 10.0.34.4/24 | 2001:db8:0:34::4/64, fe80::4 | 1 |
| R4 | Lo1 | 10.3.4.1/24 | 2001:db8:3:4::1/64 | 1 |
| R4 | Lo2 | 10.3.5.1/24 | none (IPv4 only) | 1 |
| R*n* | Lo0 | 10.255.0.n/32 | 2001:db8:255::n/128 | router's area |
Topology: a chain, R1 — R2 — R3 — R4. ipv6 unicast-routing is already on; no routing protocol is configured.
What you’ll practise
- Configure router ospfv3 with IPv6 and IPv4 address families and enable them per interface
- Explain why the IPv4 address family needs IPv6 enabled on every interface
- Configure a totally stubby area and inter-area summaries per address family
- Authenticate OSPFv3 with IPsec (SPI and SHA-1 key)
- Identify OSPFv3 link (type 8) and intra-area prefix (type 9) LSAs
The tasks
- OSPFv3 for IPv6
- Add the IPv4 address family
- Make area 1 totally stubby for both families
- Summarise area 1 in each family
- Authenticate the backbone with IPsec
- Read the OSPFv3 database
- Test both families
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 - R3
Gi0/1to R4Gi0/0
| 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 |
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
08 - OSPFv3 address families 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.