BGP in depth lab 9 of 14
MP-BGP for IPv6
Kestrel Fibre is turning on IPv6 for two customers. Bring up IPv6 address families on IOS, EOS and RouterOS, fall into the classic trap of IPv6 routes over an IPv4 session, fix the next hop, filter what customers send, and prove it with a ping between two hosts.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 4,352 MB in total. That fits the free demo too.
In your workspace: Shared, then BGP in depth guided labs, then 09 - MP-BGP for IPv6
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 6 vCPU, 4,352 MB
- Smallest plan
- Lite
The scenario
Two Kestrel Fibre customers want IPv6. Each has been given a /48 and has one host on a /64 inside it. You'll carry their prefixes across Kestrel's AS and prove that the hosts can reach each other.
| Device | AS | Announces |
|---|---|---|
| R1 | 64500 | 2001:db8:100::/48 |
| EOS1 | 64510 | 2001:db8:10::/48 |
| CHR1 | 64520 | 2001:db8:20::/48, and by mistake 2001:db8:20:99::/64 |
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Loopback0 | 10.255.0.1/32, 2001:db8:ffff::1/128 | |
| R1 | Loopback1 | 2001:db8:100::1/48 | |
| R1 | Gi0/0 | 10.0.12.1/30, 2001:db8:12::1/64 | R2 Gi0/0 |
| R1 | Gi0/1 | 2001:db8:1::1/64 | EOS1 Ethernet1 |
| R2 | Loopback0 | 10.255.0.2/32, 2001:db8:ffff::2/128 | |
| R2 | Gi0/0 | 10.0.12.2/30, 2001:db8:12::2/64 | R1 Gi0/0 |
| R2 | Gi0/1 | 2001:db8:2::1/64 | CHR1 ether1 |
| EOS1 | Ethernet1 | 2001:db8:1::2/64 | R1 Gi0/1 |
| EOS1 | Ethernet2 | 2001:db8:10::1/64 | H1 eth0 |
| EOS1 | Loopback0 | 10.255.0.10/32 | |
| CHR1 | ether1 | 2001:db8:2::2/64 | R2 Gi0/1 |
| CHR1 | ether2 | 2001:db8:20::1/64 | H2 eth0 |
| CHR1 | test64 | 2001:db8:20:99::1/64 | |
| H1 | eth0 | 2001:db8:10::10/64 | EOS1 Ethernet2 |
| H2 | eth0 | 2001:db8:20::10/64 | CHR1 ether2 |
What you’ll practise
- Explain address families, and why the transport of a session is separate from what it carries
- Configure IPv6 unicast on IOS, EOS and RouterOS
- Explain why IPv6 routes over an IPv4 session get an unreachable mapped next hop, and fix it
- Filter IPv6 prefixes by length from a customer
- Read IPv6 BGP tables on three vendors, and prove them end to end
The tasks
- Give the hosts their addresses
- One protocol, several families
- Native IPv6 eBGP between IOS and EOS
- RouterOS
- IPv6 routes over an IPv4 session
- Filter the customer
- Prove it
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 EOS1Ethernet1 - R2
Gi0/1to CHR1ether1 - EOS1
Ethernet2to 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 |
| 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 |
| 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
BGP in depth guided labs.Open
09 - MP-BGP 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 BGP in depth labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, 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.