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).
Splicing a Common L3VPN with an EVPN L3VPN

Splicing a Common L3VPN with an EVPN L3VPN

When an L3VPN is being reconstructed into an EVPN L3VPN, co-existence of the EVPN L3VPN and L3VPN occurs. To prevent network reconstruction from compromising communication, configure splicing between L3VPN and EVPN L3VPN so that the EVPN L3VPN and L3VPN can communicate with each other.

Context

On the network shown in Figure 11-8, an L3VPN is already deployed. If a user wants to deploy an EVPN L3VPN over the network, co-existence of the EVPN L3VPN and L3VPN occurs during reconstruction. To ensure communication between the two VPNs, the user must configure splicing between L3VPN and EVPN L3VPN on NPE1.

Figure 11-8 Splicing between L3VPN and EVPN L3VPN

Pre-configuration Tasks

Before configuring splicing between L3VPN and EVPN L3VPN, complete the following tasks:

  • Configure basic MPLS functions on the UPE, NPE1, and NPE2.

  • Configure an IGP on the UPE, NPE1, and NPE2 to implement route reachability.

  • Configure EVPN instances in BD mode on NPE1 and NPE2. For configuration details, see Configuring a BGP EVPN Peer Relationship.

  • Configure an L3VPN between NPE1 and the UPE. For configuration details, see Configuring a Basic BGP/MPLS IP VPN.

Procedure

  • Configure NPE1 and NPE2 to generate and advertise IP prefix routes.
    1. Run ip vpn-instance vpn-instance-name

      A VPN instance is created, and the VPN instance view is displayed.

    2. Run ipv4-family

      The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family view is displayed.

    3. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ] evpn

      VPN targets are configured for the VPN instance IPv4 address family to mutually import routes with the local EVPN instance.

    4. Run evpn mpls routing-enable

      EVPN is enabled to generate and advertise IP prefix routes and IRB routes.

    5. (Optional) Run tnl-policy policy-name evpn

      EVPN routes that can be imported into the VPN instance IPv4 address family are associated with a tunnel policy.

      This configuration allows Layer 3 service between hosts in different DCs to be transmitted through a TE tunnel between the NPEs.

    6. Run quit

      Exit from the VPN instance IPv4 address family view.

    7. Run quit

      Exit from the VPN instance view.

    8. Run commit

      The configuration is committed.

  • Configure NPE1 to advertise routes regenerated by the EVPN address family to the BGP VPNv4 peer (UPE).
    1. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    2. Run l2vpn-family evpn

      The BGP-EVPN address family view is displayed.

    3. Run peer { ipv4-address | group-name } import reoriginate

      The BGP device is enabled to add the regeneration flag to the routes received from the BGP EVPN peer.

    4. Run quit

      Return to the BGP view.

    5. Run ipv4-family vpnv4

      The BGP-VPNv4 address family view is displayed.

    6. Run peer { ipv4-address | group-name } reflect-client

      NPE1 is configured as an RR, and the UPE is specified as the RR client to reflect BGP VPNv4 routes into which EVPN routes are re-encapsulated.

    7. Run peer { ipv4-address | group-name } advertise route-reoriginated evpn { mac-ip | ip }

      NPE1 is configured to advertise routes regenerated by the EVPN address family to the BGP VPNv4 peer (UPE).

      After the peer { ipv4-address | group-name } advertise route-reoriginated evpn { mac-ip | ip } command is run, NPE1 uses MPLS to re-encapsulate the EVPN routes received from NPE2 into BGP VPNv4 routes and then sends them to the UPE.

    8. Run quit

      Return to the BGP view.

    9. Run quit

      Exit from the BGP view.

    10. Run commit

      The configuration is committed.

  • Configure NPE1 to advertise routes regenerated by the VPNv4 address family to the BGP EVPN peer (NPE2).
    1. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    2. Run ipv4-family vpnv4

      The BGP-VPNv4 address family view is displayed.

    3. Run peer { ipv4-address | group-name } import reoriginate

      The BGP device is enabled to add the regeneration flag to the routes received from the BGP VPNv4 peer.

    4. Run quit

      Return to the BGP view.

    5. Run l2vpn-family evpn

      The BGP-EVPN address family view is displayed.

    6. Run peer { ipv4-address | group-name } reflect-client

      NPE1 is configured as an RR, and NPE2 is specified as the RR client to reflect BGP EVPN routes into which BGP VPNv4 routes are re-encapsulated.

    7. Run peer { ipv4-address | group-name } advertise route-reoriginated vpnv4

      NPE1 is configured to advertise routes regenerated by the VPNv4 address family to the BGP EVPN peer (NPE2).

      After the peer { ipv4-address | group-name } advertise route-reoriginated vpnv4 command is run, NPE1 re-encapsulates the MPLS-encapsulated VPNv4 routes received from the UPE into EVPN routes and then sends them to NPE2.

    8. Run quit

      Return to the BGP view.

    9. Run ipv4-family vpn-instance vpn-instance-name

      The BGP-VPN instance IPv4 address family view is displayed.

    10. Run advertise l2vpn evpn

      The BGP device is enabled to advertise IP prefix routes to the BGP peer. This configuration allows the BGP device to advertise both host IP routes and routes of the network segment where the host resides.

    11. Run quit

      Return to the BGP view.

    12. Run quit

      Exit from the BGP view.

    13. Run commit

      The configuration is committed.

Checking the Configurations

  • Run the display bgp evpn all routing-table command on NPE2 to check information about EVPN routes received from the UPE.
  • Run the display ip routing-table vpn-instance vpn-instance-name command on NPE2 or the UPE to check information about VPN routes received from each other.
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27957

Downloads: 53

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