Cisco Nexus EVPN VXLAN Fabric

In this post, I will outline the configuration for a VXLAN fabric using BGP EVPN and OSPF as the underlay. This is similar to my previous Arista project and VXLAN project.

The topology of this post will be four switches and six clients.

  • Nexus 9000v version 9.3(1)
  • OSPF will be running as point to point between the routed ports Eth1/1 and Eth1/2
  • BGP will be between loopback0
  • Loopback1 on the Spine switches is the multicast rendezvous point
  • Loopback1 on the Leaf switches is for the NVE (VTEP)

For the configuration, I will go section by section for each device to get the full working config.

Interfaces

All physical interfaces that are part of the underlay fabric will have the MTU set to 9216 that will support jumbo frames for VXLAN. The ports will also be routed.

In this section, I am also configuring PIM sparse mode on the interfaces.

OSPF

OSPF will be used as the underlay protocol. All the loopbacks and physical Ethernet ports needs to be taking part in OSPF for all switches to heave learnt the complete fabric that will be used later for the overlay. The Ethernet ports are configured as point-to-point which reduces the amount of LSAs required.

PIM

PIM as always is for the multicast. Each spine has the rendezvous point Anycast IP of 1.1.1.1 for redundancy.

VLANs

These are the VLANs that will be used in the single tenant. The VLANs will be able to have traffic routed between them via VLAN 10, VNI 10000. This is also mapping the VLANs to the VNIs.

VLAN Interfaces

These are the VLAN interfaces that contain the Anycast gateways and are mapped to the VRF for Tenant-1. VLAN 10 is here as a way to forward intervals traffic.

Tenant

This is the single tenant on the fabric. Tenants are the customers or separate business unit. The tenants should not communicate with one another. There can be a shared services tenant for things like; DHCP, DNS, NTP, etc. But generally tenants do not communicate and can contain overlapping network addresses.

BGP

This is the MP-BGP EVPN overlay. EVPN is used as the control plane for the VXLAN data plane. EVPN will distribute the IP/MAC addresses of the endpoint hosts between the two leaf switches. By default, VXLAN operates on a flood and learn model. This is an enhancement to that behaviour, reducing the flood and learn.

The spines are acting as a route reflector as this is forming iBGP adjacencies.

NVE Interface

This is the Network Virtual Endpoint, also known as the VTEP (Virtual Tunnel Endpoint). It is loopback1 in this topology that will form the VXLAN tunnel. The NVE is responsible for VXLAN encapsulation/decapsulation.

Show Commands

As there are multiple stages to this configuration, there are lots of show commands. Some of them overlap by showing the same information.

OSPF

OSPF is configured as point to point networks between each physical interface. All Ethernet and loopback interfaces are taking part in OSPF.

Spine1
Leaf1

PIM

PIM is active on all interfaces on the fabric, and each switch will have two PIM neighbours.

Spine1
Leaf1

Tenant

The tenant is the single business unit, organisation or customer that will reside in this single overlay. There can be multiple overlay networks for multiple tenants. All of them can have overlapping networks, but no communication between them.
The tenants will only be on the leaf switches.

Leaf1

NVE

The NVE will only be on the leaf switches. It is the virtual interface that is responsible for the VXLAN encaps/decaps. The idea of BGP EVPN is that when the leaf switch that is connected to the endpoints learns of the client, it will forward that over to the other leaf switches, Leaf2 in this case.

The output below shows the MAC addresses for the endpoint that have been learnt on the network. This will only work if traffic has been received by the leaf switch the endpoints are connected to.

The next command is similar to the previous, but contains the IP and MAC of the endpoints.

BGP

BGP or iBGP to be precise is the overlay network. It is responsible for the leaf switches to be able to form the VXLAN tunnels between one another, which allows the endpoints learnt on each leaf switch to be shared.

Leave a Comment

Your email address will not be published. Required fields are marked *