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).
(Optional) Configuring Routing Policies to Control VPN Route Advertisement and Acceptance

(Optional) Configuring Routing Policies to Control VPN Route Advertisement and Acceptance

Context

The ASBRs accept all VPNv4 routes after they are configured not to filter VPNv4 routes based on VPN targets. When there are many VPN routes on the network, the ASBRs are overburdened.

If only some VPNs or sites need to communicate across ASs, you can configure routing policies on the ASBRs to control advertisement and acceptance of the VPNv4 routes. This reduces the load on the ASBRs.

This section describes how to configure the following filtering policies to control VPNv4 route advertisement and acceptance:
  • Filtering policy based VPN targets
  • Filtering policy based on RDs

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run either of the following commands to configure a route filter.

    • Perform either of the following operations as required to configure an extended community filter.
      • To configure a basic extended community filter, run the ip extcommunity-filter { basic-extcomm-filter-num | basic basic-extcomm-filter-name } [ index index-number ] { deny | permit } { rt { as-number:nn | 4as-number:nn | ipv4-address:nn } } &<1-16> command.

      • To configure an advanced extended community filter, run the ip extcommunity-filter { advanced-extcomm-filter-num | advanced advanced-extcomm-filter-name } [ index index-number ] { deny | permit } regular-expression command.

    • Run the ip rd-filter rd-filter-number { deny | permit } route-distinguisher &<1-10> command to configure an RD filter.

  3. Run route-policy route-policy-name { permit | deny } node node

    A routing policy is configured.

  4. Run either of the following commands to configure an if-match clause in the configured route filter:
    1. If you have configured an extended community filter in 2, run the if-match extcommunity-filter { { basic-extcomm-filter-num | adv-extcomm-filter-num } &<1-16> | extcomm-filter-name } command to configure an if-match clause for the extended community filter in the routing policy.
    2. If you have configured an RD filter in 2, run the if-match rd-filter rd-filter-number command to configure an if-match clause for the RD filter in the routing policy.
  5. Run quit

    Return to the system view.

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

    The BGP view is displayed.

  7. Run ipv4-family vpnv4 [ unicast ]

    The BGP-VPNv4 address family is displayed.

  8. Run peer ipv4-address route-policy route-policy-name { export | import }

    The routing policy is applied to control advertisement and acceptance of VPNv4 routes.

  9. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14476

Downloads: 25

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