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

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

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.

DeviceASAnnounces
R1645002001:db8:100::/48
EOS1645102001:db8:10::/48
CHR1645202001:db8:20::/48, and by mistake 2001:db8:20:99::/64
DeviceInterfaceAddressConnects to
R1Loopback010.255.0.1/32, 2001:db8:ffff::1/128
R1Loopback12001:db8:100::1/48
R1Gi0/010.0.12.1/30, 2001:db8:12::1/64R2 Gi0/0
R1Gi0/12001:db8:1::1/64EOS1 Ethernet1
R2Loopback010.255.0.2/32, 2001:db8:ffff::2/128
R2Gi0/010.0.12.2/30, 2001:db8:12::2/64R1 Gi0/0
R2Gi0/12001:db8:2::1/64CHR1 ether1
EOS1Ethernet12001:db8:1::2/64R1 Gi0/1
EOS1Ethernet22001:db8:10::1/64H1 eth0
EOS1Loopback010.255.0.10/32
CHR1ether12001:db8:2::2/64R2 Gi0/1
CHR1ether22001:db8:20::1/64H2 eth0
CHR1test642001:db8:20:99::1/64
H1eth02001:db8:10::10/64EOS1 Ethernet2
H2eth02001:db8:20::10/64CHR1 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

  1. Give the hosts their addresses
  2. One protocol, several families
  3. Native IPv6 eBGP between IOS and EOS
  4. RouterOS
  5. IPv6 routes over an IPv4 session
  6. Filter the customer
  7. 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.

Topology of MP-BGP for IPv66 nodes, 5 links. Every link is listed as text below the diagram.R1R2EOS1CHR1H1H2Ethernet2eth0ether2eth0Gi0/0Gi0/0Gi0/1Ethernet1Gi0/1ether1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in MP-BGP for IPv6, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
EOS1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
CHR1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder BGP in depth guided labs.

  3. Open 09 - MP-BGP for IPv6 and 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

All 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.