No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Licensing Requirements and Limitations for VXLAN--S2E

Licensing Requirements and Limitations for VXLAN--S2E

Licensing Requirements

BOM

License Control Item

Description

Minimum Version Requirement

81400678

NE20E-S2 Series VxLan Function License

Controllable feature:

This license controls VXLAN.

V800R007

Restrictions and Guidelines

Restrictions

Guidelines

Impact

If the system is downgraded to an earlier version, the specifications may change and some functions may become unavailable. If the VXLAN license is invalid, original VXLAN-related service configurations may fail to be restored.

None

The original VXLAN-related service configurations may fail to be restored.

A UNI can be bound to only one service instance (BD/VRF/EVPL).

Plan a proper configuration.

None

If the number of existing VXLAN tunnels exceeds the upper threshold, subsequent VXLAN tunnels cannot be established, and an alarm message is sent to prompt users the cause for the establishment failure.

Delete the unwanted VXLAN tunnels.

None

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.

None

Multicast packets are discarded.

After a BD accesses a VSI and a VXLAN network, no VBDIF interface can be created.

Plan a proper configuration.

VBDIF interfaces are not supported in the scenario.

After a BD accesses a VSI and a VXLAN network, the BD cannot be bound to any Layer 2 sub-interface.

Plan a proper configuration.

Layer 2 sub-interfaces are not supported in the scenario.

Only two VXLANv4 packet fragments can reassembled on the same board. Inter-board reassembly is not supported.

Prevent inter-board reassembly during service planning.

Error packets may exist.

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.

Fragmented packets cannot be transmitted over the VXLAN tunnel.

When a distributed gateway is configured to a ping a host address, the source address of the ICMP echo-request packet to be sent should be set to a non-gateway IP address of the device.

Set the source address of the ICMP echo-request packet to a non-gateway IP address of the device.

The ping fails.

Restrictions of EVPN control plane of VXLAN networks are as follows:
  • The BD, VNI, and EVPN support only 1:1 binding mode.
  • 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.

None

None

If an EVPN instance has been bound to a BD, the binding of the EVPN instance and the corresponding VNI cannot be modified or deleted.

Plan a proper configuration.

None

VXLAN does not support DHCP snooping.

Plan a proper configuration.

DHCP snooping is not supported by VXLAN.

Restrictions for VXLAN dual-active access are as follows:
  • Only Eth-Trunk interfaces are supported.
  • The shutdown state of sub-interfaces are not supported.
  • Shutdown BD is not supported.
  • Sub-interfaces that are bound to BDs are not supported to be detached. (Two interfaces where VXLAN dual-active is configured should have the same configuration.)
  • Dynamic ESI and dynamic VXLAN tunnel are not supported.
  • When MAC FRR is enabled, FRR for MAC addresses need to be learnt, which deletes MAC addresses.

    7,A BD should be first bound to a EVPN to advertise MAC routes, and then the BD is bound to the EVC interface.

None

None

VXLAN and virtual access are mutually exclusive.

None

None

VNI-based HQoS supports only level-3 scheduling (GQ, SQ, and FQ), and does not support DP and VI level scheduling.

Configure HQoS based on interfaces.

Traffic control model is incomplete.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055378

Views: 17040

Downloads: 35

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next