Feature Requirements |
Series |
Models |
|---|---|---|
Restrictions on VXLAN packet fragmentation: VXLAN tunnels do not support the MTU configuration, and packets entering VXLAN tunnels do not support fragmentation. In VXLAN networking, the MTU of a non-VXLAN device is set to be 1500 or a smaller value, and the lengths of the packets are limited within 1500 bytes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Restrictions of EVPN control plane of VXLAN networks are as follows: 1, The BD, VNI, and EVPN support only 1:1 binding mode. 2, After a BD is bound to a VNI, the BD can be bound to an EVPN. 3, Traffic statistics on VNI+peer and VNIs are using the same statistical resource. As a result, the two commands are mutually exclusive. Traffic statistics on VNI+peer support only the split-horizon-mode mode of VNIs, and do not support common VNIs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Restrictions for the VXLAN dual-active function are as follows: 1, Only Eth-Trunk access is supported. 2, The shutdown state of sub-interfaces is not supported. 3, Scenarios where BDs are shut down are not supported. 4, Scenarios where sub-interfaces are unbound from BDs are not supported. (Two interfaces where VXLAN dual-active is configured should have the same configuration.) 5, Dynamic ESIs and dynamic VXLAN tunnels are not supported. 6, When MAC FRR is enabled, FRR for MAC addresses need to be learnt, which deletes MAC addresses. 7, A BD should be bound to an EVPN to advertise MAC routes before being bound to an EVC interface or static VXLAN. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the scenario where a VXLAN tunnel is bound to a VNI, the VNI is bound to a BD, and a VBDIF interface serves as a Layer 3 gateway, the VXLAN tunnel does not support the multicast function on the VBDIF interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VNI-based HQoS supports only level-3 scheduling (GQ, SQ, and FQ), and does not support DP and VI level scheduling. Configuring HQoS based on interfaces is recommended. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Only two VXLANv4 packet fragments can reassembled on the same board. Inter-board reassembly is not supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
IPv4 VXLAN and IPv6 VXLAN cannot coexist. If IPv4 and IPv6 VXLAN tunnels coexist between two devices: 1. Packets preferentially take the IPv4 VXLAN tunnel. 2. Packet loss or redundancy may occur during switching between the two types of tunnels. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
IPv6 VXLAN tunnels do not support packet redundancy avoidance during BUM traffic switchback. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After a BD accesses a VSI or VXLAN, Layer 2 sub-interfaces cannot be bound to the BD. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VXLAN does not support DHCP snooping. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After a BD accesses a VSI or VXLAN, a VBDIF interface cannot be created. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If an EVPN instance has been bound to a BD, the binding relationship between the EVPN instance and VNI cannot be modified or deleted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the number of VXLAN tunnels exceeds the upper limit, new tunnels cannot be created, and an alarm is generated to notify the user of the tunnel creation failure cause. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After a distributed gateway is configured, you need to specify the non-gateway IP address of the local device as the source IP address of ICMP Echo Request packets to be sent when pinging the host address from the gateway. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A VNI can be bound to only one service instance (BD/VRF/EVPL). |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |