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).
Configuring Level 1 Carrier CE to Access Level 1 Carrier PE (Inter-AS)

Configuring Level 1 Carrier CE to Access Level 1 Carrier PE (Inter-AS)

When the Level 1 carrier and the Level 2 carrier are in different ASs, the Level 1 carrier takes the Level 2 carrier as its VPN user.

Procedure

  • Creating a VPN instance on the Level 1 carrier PE
    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

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

    3. Run ipv4-family

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

    4. Run route-distinguisher route-distinguisher

      The RD of the VPN instance IPv4 address family is configured.

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

      The VPN target for the VPN instance IPv4 address family is configured.

    6. Run quit

      Return to the system view.

    7. Run interface interface-type interface-number

      The view of the interface connected to the Level 1 carrier CE.

    8. Run ip binding vpn-instance vpn-instance-name

      The interface is bound with the VPN instance.

    9. Run ip address ip-address { mask | mask-length }

      The IP address of the interface is configured.

    10. Run mpls

      The MPLS capability is enabled on the interface.

    11. Run commit

      The configuration is committed.

  • Configure labeled BGP on the Level 1 carrier PE.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number1

      The BGP view is displayed.

    3. Run vpn-instance vpn-instance-name

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

    4. Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }

      The Level 1 carrier CE is configured as the EBGP peer of the Level 1 carrier PE in the BGP-VPN instance view.

    5. Run quit

      Return to the BGP view.

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

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

    7. Run import-rib vpn-instance vpn-instance-name labeled-unicast [ valid-route ] { route-policy route-policy-name | route-filter route-filter-name }

      The device is enabled to import BGP-labeled VPN routes to the BGP-VPN instance.

    8. Run quit

      Return to the BGP view.

    9. Run ipv4-labeled-unicast vpn-instance vpn-instance-name

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

    10. Run peer ipv4-address enable

      The BGP peer relationship is enabled in the BGP-labeled-VPN instance IPv4 address family view, and the Level 1 carrier PE and Level 1 carrier CE can exchange BGP-labeled routes with each other.

    11. Run import-rib vpn-instance vpn-instance-name include-label-route [ valid-route ] [ route-policy route-policy-name | route-filter route-filter-name ]

      The device is enabled to import BGP-labeled routes that have been imported to a VPN instance to the routing table of the BGP-labeled-VPN instance IPv4 address family.

    12. Run commit

      The configuration is committed.

  • On the Level 1 carrier CE, configure labeled BGP between the Level 1 Carrier CE and the Level 1 carrier PE.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The view of the interface connected to the Level 1 carrier PE.

    3. Run ip address ip-address { mask | mask-length }

      The IP address of the interface is configured.

    4. Run mpls

      MPLS is enabled on the interface.

    5. Run quit

      Return to the system view.

    6. Run bgp { as-number-plain2 | as-number-dot2 }

      The BGP view is displayed.

    7. Run peer ipv4-address as-number { as-number-plain1 | as-number-dot1 }

      The Level 1 carrier PE is configured as the EBGP peer of the Level 1 carrier CE.

    8. Run import-rib public labeled-unicast [ valid-route ] { route-policy route-policy-name }

      The device is enabled to import BGP-labeled VPN routes to the public BGP routing table.

    9. Run ipv4-family labeled-unicast

      The BGP-labeled address family view is displayed.

    10. Run peer ipv4-address enable

      The BGP peer relationship is enabled in the BGP-labeled address family view, and the Level 1 carrier CE and Level 1 carrier PE can exchange BGP-labeled routes with each other.

    11. (Optional) Run peer ip-address allow-as-loop [ number ]

      Route loops are allowed.

      NOTE:
      Perform this step if the Level 1 carrier and Level 2 carriers belong to different ASs and Level 2 carriers belong to the same AS.

    12. Run commit

      The configuration is committed.

  • On a Level 1 carrier CE, configure labeled BGP between the Level 1 carrier CE and the Level 2 carrier PE.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain2 | as-number-dot2 }

      The BGP view is displayed.

    3. Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }

      The Level 2 carrier PE is configured as the IBGP peer of the Level 1 carrier CE.

    4. Run peer ipv4-address connect-interface loopback interface-number

      The interface is used to set up a TCP connection with the IBGP peer.

    5. Run ipv4-family labeled-unicast

      The BGP-labeled address family view is displayed.

    6. Run peer ipv4-address enable

      The BGP peer relationship is enabled in the BGP-labeled address family view, and the Level 1 carrier CE and Level 2 carrier PE can exchange BGP-labeled routes with each other.

    7. Run import-route protocol [ process-id ]

      The device is enabled to import routes from the Level 2 carrier network.

    8. Run commit

      The configuration is committed.

  • Configure labeled BGP on the Level 2 carrier PE.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain2 | as-number-dot2 }

      The BGP view is displayed.

    3. Run peer ipv4-address as-number { as-number-plain2 | as-number-dot2 }

      The Level 1 carrier CE is configured as the IBGP peer of the Level 2 carrier PE.

    4. Run peer ipv4-address connect-interface loopback interface-number

      The interface is used to set up a TCP connection with the IBGP peer.

    5. Run ipv4-family labeled-unicast

      The BGP-labeled address family view is displayed.

    6. Run peer ipv4-address enable

      The BGP peer relationship is enabled in the BGP-labeled address family view, and the Level 2 carrier PE and Level 1 carrier CE can exchange BGP-labeled routes with each other.

    7. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33113

Downloads: 59

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