Guidelines and Limitations

As discussed above, the user should follow these basic guidelines to avoid connectivity issues:

• A local subnet must be present on all leaf nodes within the pod, which can be achieved by using fabric scope in the subnet creation command. (See the Configuring VXLAN chapter for configuration details.)
• Subnets’ L2 VNIs and prefix lengths must be configured consistently across all pods.
• VRFs’ L3 VNIs must be configured consistently across all pods.
• Create fabric scoped VLANs associated to VNIs by using the auto-vxlan <vni-id> keyword to automatically map them to tunnels (no need to manually configure them with the vtep-vxlan-add command)   
• For high availability enable the evpn-border option on both of the clustered border gateway nodes. Only one pair of border gateway nodes is supported in a fabric pod.
• Data center gateways should be connected to the border gateways for routing of North-South traffic.

In addition, the following limitations currently exist:

• Multiple vNETs are not supported in conjunction with the EVPN border gateway configuration.
• Bridge domains and the vSG feature are only supported within a pod, i.e., they do not span across EVPN pods.

EVPN’s Route Distinguisher and Route Target fields are currently propagated but are not used for filtering or other purposes.