Deployment Guide

● Does not perform VXLAN encapsulation or decapsulation.
The BGP EVPN running on each VTEP listens to the exchange of route information in the local overlay, encodes the learned
routes as BGP EVPN routes, and injects them into BGP to advertise to the peers. Tunnel endpoints advertise as Type 3 EVPN
routes. MAC/IP addresses advertise as Type 2 EVPN routes.
EVPN instance
An EVPN instance (EVI) spans across the VTEPs that participate in an Ethernet VPN. Each virtual-network tenant segment,
that is advertised using EVPN, must associate with an EVI. In OS10, configure EVIs in auto-EVI or manual configuration mode.
● Auto-EVI — After you configure a virtual network on a VTEP, auto-EVI mode automatically creates an EVPN instance. The
route distinguisher (RD) and route target (RT) values automatically generate:
○ The EVI ID autogenerates with the same value as the virtual-network ID (VNID) configured on the VTEP and associates
with the VXLAN network ID (VNI).
○ A Route Distinguisher autogenerates for each EVI ID. A Route Distinguisher maintains the uniqueness of an EVPN route
between different EVPN instances.
○ A Route Target import and export value autogenerates for each EVI ID. A Route Target determines how EVPN routes
distribute among EVPN instances.
● Manual EVI configuration — To specify the RD and RT values, manually configure EVPN instances and associate each EVI
with the overlay virtual network using the VXLAN VNI. The EVI activates only when you configure the virtual network, RD,
and RT values.
In manual EVI configuration, you can either manually configure the RD and RT or have them autoconfigured.
NOTE: Dell Technologies recommends using manual EVI for interoperability with network equipment vendors.
Route distinguisher
The RD is an 8-byte identifier that uniquely identifies an EVI. Each EVPN route is prefixed with a unique RD and exchanged
between BGP peers, making the tenant route unique across the network. In this way, overlapping address spaces among
tenants are supported.
You can autogenerate or manually configure a RD for each EVI. In auto-EVI mode, the RD is autogenerated. In manual EVI
configuration mode, you can autogenerate or manually configure the RD.
As specified in RFC 7432, a manually configured RD is encoded in the format: 4-octet-ipv4-address:2-octet-number.
An autogenerated RD has the format: vtep-ip-address:evi.
Route target
While a RD maintains the uniqueness of an EVPN route among different EVIs, a RT controls the way the EVPN routes are
distributed among EVIs. Each EVI is configured with an import and export RT value. BGP EVPN routes advertise for an EVI carry
the export RT associated with the EVI. A receiving VTEP downloads information in the BGP EVPN route to EVIs that have a
matching import RT value.
You can autogenerate or manually configure the RT import and export for each EVI. In auto-EVI mode, RT autogenerates. In
manual EVI configuration mode, you can autogenerate or manually configure the RT.
The RT consists of a 2-octet type and a 6-octet value. If you autoconfigure a RT, the encoding format is different for a 2-byte
and 4-byte AS number (ASN):
● For a 2-byte ASN, the RT type is set to 0200 (Type 0 in RFC 4364). The RT value is encoded in the format that is described
in section 5.1.2.1 of RFC 8365: 2-octet-ASN: 4-octet-number, where the following values are used in the 4-octet-number
field:
○ Type: 1
○ D-ID: 0
○ Service-ID: VNI
● For a 4-byte ASN, the RT type is set to 0202 (Type 2 in RFC 4364). The RT value is encoded in the format: 4-octet-ASN: 2-
octet-number, where the 2-octet-number field contains the EVI ID. In auto-EVI mode, the EVI ID is the same as the virtual
network ID (VNID). In 4-byte ASN deployment, OS10 supports RT autoconfiguration if the VNID-to-VNI mapping is the same
on all VTEPs.
NOTE: Dell Technologies recommends using manual route-target for interoperability with network equipment vendors.
VXLAN 51