Guidelines and Limitations for VXLAN BGP EVPN
The following are the limitations for Virtual Extensible LAN (VXLAN) Border Gateway Protocol (BGP) Ethernet VPN (EVPN) has the following:
-
Multicast over VXLAN is currently not supported.
-
show commands with the keyword internal are not supported.
-
For EBGP, it is recommended to use a single overlay EBGP EVPN session between loopbacks.
-
Bind NVE to a loopback address that is separate from other loopback addresses that are required by Layer 3 protocols. A best practice is to use a dedicated loopback address for VXLAN.
-
VXLAN BGP EVPN does not support an NVE interface in a non-default VRF.
-
It is recommended to configure a single BGP session over the loopback for an overlay BGP session.
-
The VXLAN UDP port number is used for VXLAN encapsulation. It complies with IETF standards and is not configurable.
-
VXLAN BGP EVPN currently supports only leaf switch functionality. Spine switch functionality is not supported.
-
Support is not available for any integrated underlay technologies such as route-reflector, or anycast rendezvous point , or Multicast Source Discovery Protocol (MSDP) endezvous point.
-
Border leaf functionality and interworking between BGP EVPN and traditional Layer 3 and Layer 2 overlay networks are not supported.
-
Auto route-distinguisher and auto route-target for IP VRF is not supported
-
Centralized Gateway for Layer 2 VXLAN network identifier (L2VNI) is not supported.
-
BGP EVPN Network Virtualization Overlay MIB is not supported.
-
In EVPN deployments, once a VLAN is used for a core-facing SVI, it should not be allowed in any trunk. For a core-facing SVI to function properly, the no autostate command must be configured under the SVI.