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

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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).
Limitations for EVPN-NE08E

Limitations for EVPN-NE08E

Restrictions

Guidelines

Impact

EVPN BUM traffic forwarding supports only the ingress replication mode rather than the P2MP tunnel mode.

Plan configurations properly.

A Huawei device with the BUM traffic model being ingress replication cannot communicate with a non-Huawei device with the BUM traffic model being P2MP tunnel.

The EVPN public network interface does not support MF classification.

Configure MF classification for the traffic inbound interface before the EVPN public network interface.

MF classification configured for the EVPN public network interface does not take effect.

If an EVPN instance is bound to a BD that has been bound to a VSI for an existing VPLS service, services may be interrupted. After the EVPN instance is bound to the BD, services are restored.

Manually set the VPLS PW to Down. In master/backup E-Trunk scenarios, bind an EVPN instance to a BD on the backup E-Trunk first and then perform the binding on the master E-Trunk.

If an EVPN instance is bound to a BD that has been bound to a VSI for an existing VPLS service, services may be interrupted.

The MAC addresses learned by a BD are cleared, and then the BD relearns the MAC addresses. The unicast mode is changed to broadcast mode.

For a BD bound to both an EVPN instance and a VPLS VSI, the VPLS PWs cannot be set to be in Spoken mode.

None

If a VPLS PW is set to be in Spoken mode, loops may occur.

When a VSI is bound to multiple BDs, if an EVPN instance is bound to one of the BDs, the VSI's PW is set to Down. As a result, services in the other BDs that are not bound to EVPN instances are interrupted.

When a VSI is bound to multiple BDs, unbind the BDs to be bound to EVPN instances from the VSI.

If the BDs to be bound to EVPN instances are not removed from the VSI, services in the other BDs are interrupted.

When the Kompella VPLS and MPLS EVPN coexist, they must be both configured on devices at both ends.

Plan a proper configuration.

The PW on the side where the Kompella VPLS and MPLS EVPN do not coexist cannot be set to Down.

An EVPN instance and a VSI are bound to the same BD. If the BD receives a MAC Withdraw packet for a PW from the remote VSI, the BD deletes the MAC address learned from the AC interface but does not clear the MAC address learned from the EVPN instance.

None

Deleting the MAC address learned from the AC interface triggers MAC address deletion on the EVPN. After the BD relearns a MAC address from the AC interface, the BD broadcasts the MAC address on the EVPN.

When VPLS and MPLS EVPN coexist, PE1 functions as a converged node, establishes an EVPN peer relationship with PE2, and establishes a VPLS PW with PE3.

The host on the PE2 AC side can be migrated to the PE3 AC side for access, or the host on the PE3 AC side can be migrated to the PE2 AC side for access. This migration can be performed only once.

None

Currently, multiple migrations are not supported unless MAC addresses are aged.

If the PE at one end of a VPLS has only one VSI and the PE at the other end has multiple VSIs, the VPLS network cannot be reconstructed into an EVPN.

Re-plan the network deployment.

Some services are interrupted during the network reconstruction.

The EVPN switch to which a user device is connected is replaced with a VPLS network switch. Before the MAC entry aging time expires, the user device is reconnected to the EVPN switch. As a result, services are interrupted until the VPLS network ages the MAC entry for the user device.

When the VPLS network is reconstructed into the EVPN, manually shut down the network device interface connecting to the switch and then re-enable the interface after the network reconstruction.

If the VPLS network is reconstructed into the EVPN before the MAC entry for the user device is aged, user services are interrupted until the VPLS network ages the MAC entry for the user device.

When a VLL accesses an EVPN, only non-BD EVPN (MPLS EVPN) is supported.

None

None

Regarding EVPN E-Line:

The EVPN single-active mode blocks traffic on an AC interface. If the master/backup E-Trunk status is determined, the backup E-Trunk interface is set Down. Therefore, EVPN single-active services and active-active or Layer 3 services cannot be transmitted through the same link for dual-homing access.

If an EVPN works in single-active mode, the EVPN single-active services and active-active or Layer 3 services cannot be transmitted through the same link.

Traffic for other services may not be forwarded properly.

In an inter-AS Option B scenario, MPLS EVPN IRB routes cannot be processed (both Layer 2 and Layer 3 labels are re-allocated).

Inter-AS distributed gateways use prefix routes to transmit host routes for Layer 3 forwarding. ARP routes are used to transmit MAC-IP information for host migration.

MPLS EVPN IRB does not support Option B.

In full-mesh networking, a loop occurs in either of the following scenarios:
  • An EVPN is connected to a VPLS whose PWs are configured to be in Spoken mode. (A VPLS PW should be configured to be in Hub mode.)
  • The E-Trunks through which a CE is dual-homed to PEs work in active-active mode.

Configure a VPLS PW to be in Hub or Spoken mode as required.

An incorrect configuration results in a loop.

Regarding EVPN active-active:

1. Dual-homed devices cannot reside in different ASs.

2. DCI and VXLAN anycast active-active are mutually exclusive.

3. Non-anycast VXLAN active-active is not supported.

4. ESIs on different dual-homed interfaces cannot be the same.

5. In active-active scenarios, a CE must be directly accessed to a PE, without any intermediate device.

None

Traffic switching performance in case of a link failure is affected.

In an EVPN active-active scenario, if the bfd bfd-name bind peer-ip ip-address track-interface interface Eth-Trunk number and es track bfd commands are not run, packet loss duration cannot be ensured to be less than 1 second in case of a link, board, or node fault.

In the EVPN active-active scenario, run the bfd bfd-name bind peer-ip ip-address track-interface interface Eth-Trunk number and es track bfd commands.

In an EVPN active-active scenario, if the bfd bfd-name bind peer-ip ip-address track-interface interface Eth-Trunk number and es track bfd commands are not run, packet loss duration may exceed 1 second in case of a link, board, or node fault.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27871

Downloads: 53

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