CloudLabBox
Try the free demo

Cisco NX-OS data centre lab 3 of 15

MP-BGP address families and tenant VRFs

Peer a Nexus switch with a carrier and a core router over IPv4, IPv6 and a tenant VRF. Each address family is switched on per neighbour, and peer templates and route policy keep the configuration tidy.

Run this lab

It needs Lite: its 4 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.

In your workspace: Shared, then Cisco Nexus NX-OS data centre guided labs, then 03 - MP-BGP address families and tenant VRFs

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
Intermediate
Time
About 70 minutes
Nodes need
5 vCPU, 7,680 MB
Smallest plan
Lite

The scenario

Hall 3 now needs real routing to the outside. R1 is the carrier's router, AS 65100. R2 is Ashgrove's core router in your own AS 65000, and it's reached over the OSPF that's already running. Tenant A wants its own routes kept apart, so it gets a VRF and its own BGP session over a VLAN-tagged subinterface. R1 and R2 are ready and waiting for you.

SessionFrom N1ToAddress family
Carrier, eBGP10.1.1.1R1 10.1.1.2, AS 65100IPv4 unicast
Carrier, eBGP2001:db8:1:1::1R1 2001:db8:1:1::2IPv6 unicast
Core, iBGPloopback0 10.255.0.1R2 loopback 10.255.0.12IPv4 unicast
Tenant A, eBGPEthernet1/1.20, 10.1.20.1 in VRF TENANT-AR1 10.1.20.2IPv4 unicast in the VRF

What should be reachable: H1 (10.10.10.11, gateway .1) reaches the carrier's 203.0.113.1. R2's 10.60.1.0/24 reaches the carrier too. The tenant's 10.20.20.0/24 (loopback20 on N1) reaches 172.16.1.1 inside the VRF, and only there.

What you’ll practise

  • Explain why NX-OS BGP needs an address family under every neighbour
  • Build eBGP and iBGP sessions, using a peer template for iBGP
  • Carry IPv6 in its own address family
  • Apply prefix-list and route-map policy and refresh it softly
  • Run a separate BGP table for a tenant VRF

The tasks

  1. Start the lab
  2. eBGP to the carrier
  3. iBGP with a peer template
  4. IPv6 in its own address family
  5. Route policy
  6. A BGP table for a tenant

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 address families and tenant VRFs4 nodes, 3 links. Every link is listed as text below the diagram.N1R1R2H1e5eth0e1Gi0/0e2Gi0/0
4 nodes, with the interface names each link uses.
Every link, as text
  • N1 e1 to R1 Gi0/0
  • N1 e2 to R2 Gi0/0
  • N1 e5 to H1 eth0
Nodes in MP-BGP address families and tenant VRFs, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
N1Cisco Nexus 9000vnxosv9k-9300v-9.3.102 vCPU, 6,144 MB
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
H1Alpine 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 Cisco Nexus NX-OS data centre guided labs.

  3. Open 03 - MP-BGP address families and tenant VRFs 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 Cisco NX-OS data centre labs

All Cisco NX-OS data centre 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.