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

S9300, S9300E, and S9300X V200R010C00

This document describes the VPN configuration procedures and provides configuration examples.
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).
(Optional) Enabling Next-Hop-based Label Allocation on the ASBR

(Optional) Enabling Next-Hop-based Label Allocation on the ASBR

Context

In an inter-AS VPN Option B scenario, ASBRs can be enabled to allocate labels to VPN routes based on next hops. This saves labels on the ASBRs.

Next-hop-based label allocation means to allocate the same label for the routes with the same forwarding behavior. In other words, VPN routes with the same forwarding path and outbound label are assigned the same label. Different from the prefix-based label allocation mode that is used by default, next-hop-based label allocation enrich the label allocation modes and allows for flexible label allocation. In addition, when an ASBR functions as a PE device, next-hop-based label allocation can be used together with one label per instance mode to save labels on the ASBR.

As shown in Figure 2-44, the inter-AS VPN Option B networking is established; two VPN instances, VPN1 and VPN2, are configured on PE1; the label allocation mode is one label per VPN instance. CE1 in VPN1 and CE2 in VPN2 are respectively imported with 1 thousand VPN routes. When the next-hop-based label allocation feature is not enabled for VPN routes on ASBRs, the 2 thousand routes of PE1 advertised by ASBR1 to ASBR2 use 2 thousand labels; after the next-hop-based label allocation feature is enabled for VPN routes on ASBR1, ASBR1 only assigns one label for VPN routes of the same next hop and outgoing label. As a result, ASBR1 needs to allocate only two labels for 2 thousands routes.
Figure 2-44  Next-hop-based label allocation for VPN routes on ASBR

After next-hop-based label allocation is enabled or disabled, the label allocated by the ASBR for a route changes, which leads to packet loss.

Perform the following steps on the ASBR.

Procedure

  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:

    ipv4-family vpnv4

    The BGP-VPNv4 view is displayed.

  4. Run:

    apply-label per-nexthop

    The next-hop-based label allocation for IPv4 VPN routes is enabled on the ASBR.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142068

Views: 111499

Downloads: 204

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