Multi-vendor troubleshooting lab 9 of 12
IPv6 interoperability with RA flags DHCPv6 and OSPFv3
Larkfield turns on IPv6 and two sites stay dark. OSPFv3 needs matching instance IDs and a firewall that lets it in, one LAN's router advertisements tell hosts to use a DHCPv6 service that can't be reached, and another advertises no prefix at all. Fix each one and read the flags from the host's side.
Run this lab
It needs Lite: its 5 nodes are set to 6 vCPU and 7,424 MB in total. That fits the free demo too.
In your workspace: Shared, then Multi-vendor interoperability and troubleshooting guided labs, then 09 - IPv6 interoperability with RA flags DHCPv6 and OSPFv3
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 6 vCPU, 7,424 MB
- Smallest plan
- Lite
The scenario
Larkfield is turning on IPv6 between its sites, and OSPFv3 should carry every prefix. H1 is a test PC with one network card on each access LAN. LAN A has an Arista gateway, and hosts there must get their addresses from the central DHCPv6 server on R1. LAN B has a MikroTik gateway, and hosts there use SLAAC. Today neither LAN gets a global address it can use, and half the routers can't see each other.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Gi0/0 | 2001:db8:12::1/64 | SRX1 ge-0/0/0 |
| R1 | Gi0/1 | 2001:db8:14::1/64 | CHR1 ether2 |
| R1 | Loopback0 | 2001:db8:ff::1/128 | DHCPv6 server |
| SRX1 | ge-0/0/0.0 | 2001:db8:12::2/64 | R1 |
| SRX1 | ge-0/0/1.0 | 2001:db8:23::1/64 | EOS1 |
| SRX1 | lo0.0 | 2001:db8:ff::2/128 | Router ID 10.255.0.2 |
| EOS1 | Ethernet1 | 2001:db8:23::2/64 | SRX1 |
| EOS1 | Ethernet2 | 2001:db8:a::1/64 | LAN A, H1 eth0 |
| EOS1 | Loopback0 | 2001:db8:ff::3/128 | Router ID 10.255.0.3 |
| CHR1 | ether2 | 2001:db8:14::2/64 | R1 |
| CHR1 | ether3 | 2001:db8:b::1/64 | LAN B, H1 eth1 |
| CHR1 | loopback | 2001:db8:ff::4/128 | Router ID 10.255.0.4 |
| Design standard | Value |
|---|---|
| OSPFv3 | Area 0, instance ID 0, point-to-point between routers |
| LAN A | M flag set, A flag clear: addresses from DHCPv6 through a relay on EOS1 |
| LAN B | SLAAC: prefix advertised with the A flag set |
What you’ll practise
- Read OSPFv3 state on IOS, Junos, EOS and RouterOS
- Match OSPFv3 instance IDs between vendors
- Allow OSPFv3 through a vSRX zone
- Read M, O and A flags, and predict what a host will do
- Relay DHCPv6 from one vendor to a server on another
- Fix a RouterOS LAN that sends router advertisements with no prefix
The tasks
- Prepare H1
- Read the state
- The OSPFv3 instance ID
- OSPFv3 through a zone
- LAN B, advertisements with no prefix
- LAN A, a promise nobody keeps
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 SRX1ge-0/0/0 - SRX1
ge-0/0/1to EOS1Ethernet1 - R1
Gi0/1to CHR1ether2 - EOS1
Ethernet2to H1eth0 - CHR1
ether3to H1eth1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| SRX1 | Juniper vSRX NextGen template | vsrxng-23.4R2-S3.9 | 2 vCPU, 4,096 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 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 |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Multi-vendor interoperability and troubleshooting guided labs.Open
09 - IPv6 interoperability with RA flags DHCPv6 and OSPFv3and 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 Multi-vendor troubleshooting labs
All Multi-vendor troubleshooting labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, CompTIA, Fortinet, HPE, 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.