Connectivity Guide

BGP EVPN compared to static VXLAN
OS10 supports two types of VXLAN NVO overlay networks:
• Static VXLAN
• BGP EVPN
Static VXLAN and BGP EVPN for VXLAN are congured and operate in the same ways:
• The overlay and underlay networks are manually congured.
• Each virtual network and VNI are manually congured.
• Access port membership in a virtual network is manually congured.
• Underlay reachability to VTEP peers is provisioned or learned using existing routing protocols.
Static VXLAN and BGP EVPN for VXLAN conguration and operation dier as described in the following table.
Table 7. Dierences between Static VXLAN and VXLAN BGP EVPN
Static VXLAN VXLAN BGP EVPN
To start sending and receiving virtual-network trac to and from a
remote VTEP, you must manually congure the VTEP as a member
of the virtual network.
No manual conguration is required. Each remote VTEP is
automatically learned as a member of a virtual network from the
EVPN routes received from the remote VTEP. After a remote
VTEP's address is learned, VXLAN trac is sent to, and received
from, the VTEP.
Remote host MAC addresses are learned from data packets after
decapsulation of the VXLAN header in the data plane.
Remote host MAC addresses are learned in the control plane using
BGP EVPN Type 2 routes.
VXLAN BGP EVPN operation
The EVPN address family allows VXLAN to carry EVPN routes in eBGP and iBGP sessions. In a data center network, you can use eBGP or
iBGP for route exchange in both the IP underlay network and EVPN.
This sample BGP EVPN topology shows a typical data center (leaf-spine) network in which eBGP is used for exchanging IP routes in the IP
underlay network, and EVPN routes in the VXLAN overlay network. All spine nodes are in one autonomous system (AS 65535). All leaf
nodes are in another autonomous system (AS 65000).
550
VXLAN