Ethernet Virtual Private Network (EVPN) Type 5 Routes

For Ethernet Virtual Private Network (EVPN), Type 5 Routes are now supported as a demonstration feature, except for on the default VR.

Important

Demo Feature: EVPN Type 5 Routes is a demonstration feature that is provided for testing purposes. Demonstration features are for lab use only and are not for use in a production environment. Please work with your Extreme Networks sales team to request a demonstration.

Table 1. EVPN Route Type 5 Information
Route Type	Route Type Name	Usage	ExtremeXOS Support
5	IP prefix route	Advertise IP prefixes	Only as demonstration feature (see Ethernet Virtual Private Network (EVPN) Type 5 Routes). Yes, except on Default VR. Type 5 routes in non-VPN VRF is also supported. The tenant VLANs have to be created and associated with a non-VPN VRF. The non-VPN VRF should be a child of the Default VR For example: create vr "vr1" type vrf vr "VR-Default"

Supported Platforms

ExtremeSwitching X465, X590, X690, X695 series switches.

Limitations

The following is not supported:

Switching through a VXLAN tunnel to a remote L3 Anycast gateway.
Default VRs.

EVPN Type 5 Route Commands

To configure a Layer 3 virtual network identifier (VNI) and bind it to a VPN VRF, use the following command:

configure bgp evpn l3vni [vni_value | none] vr vr_name

To export direct, static, and BGP routes from a VRF into BGP, running on the specified VR, as EVPN routes to be advertised by BGP as Type 5 routes, use the following command:

enable bgp export [static | direct] {address-family address_family} l2vpn-evpn {vr vr_name}

To stop exporting direct, static, and BGP routes from a VRF into BGP, running on the specified VR, as EVPN routes to be advertised by BGP as Type 5 routes, use the following command:

disable bgp export [static | direct] {address-family address_family} l2vpn-evpn {vr vr_name}

To show the L3 VNI entries from the EVPN MAC/IP table, use the following command:

show bgp evpn l3vni {vr vr_name}}