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 a Routing Policy to Control Label Distribution

Configuring a Routing Policy to Control Label Distribution

Context

To control label allocation for each inter-AS BGP LSP, you can configure a routing policy. If labeled IPv4 routes are advertised to a PE of the local AS, re-distribute MPLS labels to these routes. If routes sent by a PE of the local AS are advertised to the peer ASBR, distribute MPLS labels to these routes.

Procedure

  1. Create a routing policy.

    Perform the following steps on the ASBR.

    1. Run system-view

      The system view is displayed.

    2. Run route-policy policy-name1 permit node node

      The routing policy to be applied to the local PE is created.

      For the labeled IPv4 routes received from peer ASBRs, and sent to the PEs in the same AS, this policy ensures that a new MPLS label is distributed.

    3. Run if-match mpls-label

      An IPv4 route with a label is matched.

    4. Run apply mpls-label

      A label is distributed to the IPv4 route.

    5. Run quit

      Return to the system view.

    6. Run route-policy policy-name2 permit node node

      The routing policy to be applied to the peer ASBR is created.

      For the labeled IPv4 routes received from PE in the local AS, and sent to the remote ASBR, this policy ensures that a new MPLS label is distributed.

    7. Run apply mpls-label

      A label is distributed to the IPv4 route.

    8. Run commit

      The configuration is committed.

  2. Apply the routing policy.

    Perform the following steps on the ASBR.

    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 peer ipv4-address route-policy policy-name1 export

      The routing policy is applied when the route is advertised to the local PE.

    4. Run peer ipv4-address route-policy policy-name2 export

      The routing policy is applied when the route is advertised to the peer ASBR.

    5. Run commit

      The configuration is committed.

  3. (Optional) Control the creation of ingress LSPs for labeled BGP routes based on routing policies.

    Perform the following steps on each 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 ingress-lsp trigger route-policy route-policy-name

      The switch is enabled to create ingress LSPs for labeled BGP routes based on routing policies.

      On a MAN where the hybrid access mode is used, a large number of labeled BGP routes are used to establish end-to-end LSPs. On certain intermediate nodes where VPN services do not need to be supported, an excessive number of ingress LSPs are created, wasting network resources. In this case, you can run this command to create ingress LSPs based on routing policies to conserve network resources.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14444

Downloads: 25

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