Multi-Destination Traffic; Guidelines And Limitations For Vxlan Bgp Evpn - Cisco Nexus 7000 Series Configuration Manual

Multi-Destination Traffic

Mobility in a vPC scenario
In a vPC scenario where 2 ToR switches are vPC peers, whether the end host is attached to an orphan port or
has a dual homed connection, the VIP address is advertised in the control plane and data plane, and the VIP
address is carried in the (outer) source IP address field of the VXLAN packet.
Note VIP is a common, virtual VTEP IP address that is used for (unicast and multi destination) communication
to and from the two switches in the vPC setup. The VIP address represents the two switches in the vPC
setup, and is designated as the next hop address (for end hosts in the vPC domain) for reachability purposes.
Pinging from a vPC switch—If you ping from switch A in a vPC setup (comprising of switches A and B) to
a connected device or a remote end host, the common, virtual IP address (VIP) is considered the source IP
address, and a successful response to the ping will be sent either to A, or to B. If the response is sent to B,
then A (the sender) will not receive it.
As a workaround, create a loopback interface with a unique IP address for each vPC switch, and use the
loopback IP address as the source for pinging attached devices or end hosts. Also leak the unique address
between the vPC pair to ensure that the (ICMP) response is routed back to the sending vPC switch.
Also, you can use the VXLAN OAM functionality as a workaround.
Multi-Destination Traffic
Refer to the table below to know the multicast protocol(s) for your Cisco Nexus switches support::
If you are using this Nexus switch:
Cisco Nexus 7000 and 7700/F3 Series

Guidelines and Limitations for VXLAN BGP EVPN

VXLAN BGP EVPN has the following guidelines and limitations:
• VXLAN EVPN requires the LAN_ENTERPRISE_SERVICES_PKG license.
• Only spine role is supported in Cisco NX-OS Release 7.2(0)D1(1).
• VXLAN and Fabric Path features cannot be enabled on the same VDC for F3 and M3 modules.
• VXLAN BGP EVPN is supported on M3 series modules from Cisco NX-OS Release 7.3(0)DX(1)
• Following are not supported for VxLAN BGP EVPN in VDCs having M3 modules:
• Ensure that the root of a Spanning Tree Protocol (STP) domain local to the VXLAN fabric is a VTEP,
Cisco Nexus 7000 Series NX-OS VXLAN Configuration Guide
54
onwards.
◦ LISP handoff is not supported.
◦ Hosts connected behind FEX is not supported.
or placed within the fabric. The STP root should not be outside the VXLAN fabric (below the VTEPs)
since it will lead to Layer 2 loops.
Configuring VXLAN BGP EVPN
Use this option for BUM traffic
PIM ASM/SSM or PIM BiDir