...
- When deploying VXLAN, peer link should not be the outcoming interface of VXLAN tunnel for routing VXLAN traffic, otherwise packet loss may occur.
- In MLAG with VXLAN network, it is not supported to use set vxlans vni <text> interface <port> command to set VNI mapping to port, which may cause MLAG network flapping.
- Untagged packets do not support VNI mapping to the PVID of a port by using command set vxlans vni <text> interface <port> <text> vlan <vlan-id>.
- In MLAG with VXLAN network, configuring static MAC address entries on VXLAN tunnel interfaces is not supported, so the command set vxlans vni<text> flood vtep <ipv4-addr> mac-address <macaddr> is useless.
- Traffic from the single-homed port cannot be sent from the peer spine's network side port of VXLAN because of the limitation that the traffic from the peer link will not be forwarded through the VXLAN network side ports.
- Only one VLAN can be configured for one VNI when you use the command set vxlans vni <text> interface <port> > vlan <vlan-id> to configure the VLAN permitted to pass through the VXLAN tunnel.
- If the local VXLAN access port status is Down, packets from the VXLAN network side will be discarded on the local MLAG peer-link port if they become packets without a VLAN tag after VXLAN decapsulation.
- The single-homed port is not supported as VXLAN access port, only dual-homed MLAG member port can be configured as VXLAN access port.
...