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

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
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 Route Exchange Between PE and CE Devices

Configuring Route Exchange Between PE and CE Devices

Context

The Hub-PEs and Hub-CEs can use IGP or EBGP to exchange routing information. If they use EBGP, you must configure the Hub-PEs to allow repeated local AS numbers.

As shown in Figure 3-2, the routing information advertised by a Spoke-CE is forwarded to the Hub-CE and Hub-PE before being transmitted to other Spoke-PEs. If EBGP runs between the Hub-PE and Hub-CE devices, the Hub-PE performs AS-Loop detection on the route. If the Hub-PE detects its own AS number in the route, it discards the route. In this case, to implement Hub and Spoke networking, the Hub-PE must be configured to permit the existence of repeated local AS numbers.
Figure 3-2 EBGP running between the Hub-CE and Hub-PE devices

Procedure

  • Configuring EBGP between the Hub-PE and Hub-CE devices

    For detailed configuration procedures, see Configuring a Routing Protocol Between PE and CE.

    In this way, EBGP, IGP, or static routes can be adopted between the Spoke-PE and the Spoke-CE.

    To set up the EBGP peer between the Hub-PE and the Hub-CE and between the Spoke-PE and Spoke-CE, perform the following steps on the Hub-PE:

    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

    4. Run peer ipv6-address allow-as-loop [ number ]

      The Hub-PE is configured to allow the routing loop.

      Here, the value of number is set as 1, which means the route with the AS number repeated once can be sent.

    5. Run commit

      The configuration is committed.

  • Configuring an IGP between the Hub-PE and Hub-CE devices

    For detailed configuration procedures, see Configuring a Routing Protocol Between PE and CE.

    Only IGP or static routes can be used between the Spoke-PE and Spoke-CE. BGP can cause route flapping between them.

  • Configuring static routes between the Hub-PE and the Hub-CE devices

    For detailed configuration procedures, see Configuring a Routing Protocol Between PE and CE.

    In this way, EBGP, IGP, or static routes can be adopted between the Spoke-PE and the Spoke-CE.

    If the Hub-CE uses the default route to access the Hub-PE, to advertise the default route to all the Spoke-PEs, perform the following steps on the Hub-PE:

    1. Run system-view

      The system view is displayed.

    2. Run ipv6 route-static vpn-instance vpn-instance-name :: 0 nexthop-ipv6-address [ tag tag ] [ description text ]

      The default route is configured.

      Here, vpn-instance-name refers to the VPN-out. nexthop-ipv6-address is the IPv6 address of the Hub-CE interface that is connected to the PE interface bound with the VPN-out.

    3. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    4. Run ipv6-family vpn-instance vpn-instance-name

      The BGP VPN instance IPv6 address family view is displayed.

      vpn-instance-name refers to the VPN-out.

    5. Run network ::0 0

      The default routes to all the Spoke-PEs through MP-BGP are advertised.

    6. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14329

Downloads: 25

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