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-S V800R010C10SPC500 Feature Description - VPN 01

This is NE20E-S V800R010C10SPC500 Feature Description - 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).
Migration from an HVPLS Network to a PBB-EVPN

Migration from an HVPLS Network to a PBB-EVPN

On the network shown in Figure 12-49, HVPLS is deployed to reduce the number of required PWs and improve bandwidth usage.

After devices have PBB-EVPN enabled, the HVPLS network can migrate to a PBB-EVPN. Because this network has large numbers of devices, migration needs to be performed step by step and HVPLS and PBB-EVPN will temporarily coexist. The implementation process is as follows:
  1. Configure a B-EVPN instance on the SPE and specify a unique B-MAC address for the B-EVPN instance.

  2. Change the existing VSI on the SPE to be an MP2MP I-VSI and bind the I-VSI to the B-EVPN instance previously configured. The I-tag for the I-VSI must be the same as the I-tag for the B-EVPN instance. Otherwise, services cannot be forwarded.

  3. Specify each UPE as an EVPN BGP peer for the SPE.

  4. Configure a B-EVPN instance on each UPE and specify the SPE as an EVPN BGP peer for each UPE. Then, UPEs will learn B-MAC addresses from their EVPN BGP peers and the SPE will learn the B-MAC addresses of the entire network.

  5. Change the existing VSI on each UPE to be an I-EVPN instance, bind the I-EVPN instance to the previously configured B-EVPN instance, and bind the AC interface on each UPE to the I-EVPN instance on that UPE. After all configurations are complete, the network becomes a PBB-EVPN.

Figure 12-49 Typical networking

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055135

Views: 10057

Downloads: 17

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