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

Configuring a Routing Policy to Control Label Distribution

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

Procedure

  • 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 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 allocated.

    3. Run if-match mpls-label

      The IPv4 routes with labels are matched.

    4. Run apply mpls-label

      A label is allocated to the IPv4 routes.

    5. Run quit

      Return to the system view.

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

      The routing policy 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 allocated.

    7. Run apply mpls-label

      A label is allocated to the IPv4 routes.

    8. Run commit

      The configuration is committed.

  • Apply a routing policy.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

    3. Run peer ipv4-address route-policy policy-name1 export

      The routing policy used when routes are advertised to the local PE is applied.

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

      The routing policy used when routes are advertised to the peer ASBR is applied.

    5. Run commit

      The configuration is committed.

  • (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 | route-filter route-filter-name }

      The system is configured to create ingress LSPs for labeled BGP routes based on routing policies or route-filters.

      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, excessive ingress LSPs are created, wasting network resources. In this case, you can run the ingress-lsp trigger command to create ingress LSPs based on a routing policy or route-filter to save network resources.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 32687

Downloads: 59

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