CCNP ENARSI lab 19 of 35
BGP route reflectors and MP-BGP for IPv4 and IPv6
Replace an iBGP full mesh with a route reflector, run separate IPv4 and IPv6 address families over native sessions, and follow the originator ID and cluster list that keep reflected routes loop-free.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 19 - BGP route reflectors and MP-BGP for IPv4 and IPv6
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 5 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
Ospreyline Retail (AS 64500) is growing from three sites to thirty. A full iBGP mesh would need n×(n−1)/2 sessions (435 for 30 routers), so the design uses the core router R1 as a route reflector and every other router as a client with a single session to R1. The network is dual-stack: IPv4 and IPv6 routes must both be carried, each in its own BGP address family over its own native session. R4 connects to the ISP (R5, AS 64501) over IPv4 and IPv6.
The OSPFv3 underlay (both address families) is already running, so every loopback is reachable.
| Device | Interface | IPv4 | IPv6 | Role |
|---|---|---|---|---|
| R1 | Lo0 | 10.255.0.1/32 | 2001:db8:255::1/128 | route reflector |
| R2 | Lo0 / Lo1 | 10.255.0.2/32 / 10.2.2.1/24 | 2001:db8:255::2/128 / 2001:db8:2::1/64 | client, branch 2 |
| R3 | Lo0 / Lo1 | 10.255.0.3/32 / 10.3.3.1/24 | 2001:db8:255::3/128 / 2001:db8:3::1/64 | client, branch 3 |
| R4 | Lo0 | 10.255.0.4/32 | 2001:db8:255::4/128 | client, Internet edge |
| R4 | Gi0/1 | 203.0.113.1/30 | 2001:db8:45::4/64 | eBGP to R5 (203.0.113.2, 2001:db8:45::5) |
| R5 (AS 64501) | Lo1 | 192.0.2.1/24 | 2001:db8:c0de::1/48 | Internet content |
What you’ll practise
- Explain the iBGP split-horizon rule and why route reflectors remove the full mesh
- Configure a route reflector and clients in the IPv4 and IPv6 address families
- Use no bgp default ipv4-unicast and activate neighbours per address family
- Peer eBGP for IPv4 and IPv6 and set next-hop-self per family
- Read originator ID and cluster list on reflected routes
The tasks
- Prepare the BGP processes for two address families
- Build the route reflector and its clients
- Advertise the branch LANs
- Connect the Internet edge for both families
- Test
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 R3Gi0/0 - R1
Gi0/2to R4Gi0/0 - R4
Gi0/1to R5Gi0/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 |
| R5 | 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
19 - BGP route reflectors and MP-BGP 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.