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 VPN instances on PEs

Configuring VPN instances on PEs

Context

In a BGP/MPLS IPv6 VPN application, each VPN has an instance to maintain forwarding information of the local VPN. Such an instance is called a VPN instance or a VPN routing and forwarding (VRF) table.

VPN instances isolate VPN routes from routes on the public network and isolate the routes of different VPN instances. IPv6 VPN instances must be configured in all types of BGP/MPLS IPv6 VPN networking.

Perform the following steps on the PEs:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ip vpn-instance vpn-instance-name

    A VPN instance is created, and its view is displayed.

    NOTE:

    A VPN instance name is case sensitive. For example, vpn1 and VPN1 are different VPN instances.

  3. (Optional) Run description description-information

    A description is configured for the VPN instance.

  4. Run ipv6-family

    The IPv6 address family is enabled for the VPN instance, and the VPN instance IPv6 address family view is displayed.

  5. Run route-distinguisher route-distinguisher

    An RD is configured for the VPN instance IPv6 address family.

    A VPN instance IPv6 address family takes effect only after being configured with an RD. The RDs of different VPN instances on a PE must be different.

    NOTE:

    After RDs are configured, they cannot be modified but can be deleted. When an RD is deleted, all configurations in the VPN instance IPv6 address family of the corresponding VPN instance will also be deleted.

  6. Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]

    A VPN target is configured for the VPN instance IPv6 address family.

    A VPN target is a BGP extended community attribute. It is used to control the receiving and advertisement of VPN routing information. A maximum of eight VPN targets can be configured using the vpn-target command.

  7. (Optional) Run prefix limit number { alert-percent [ route-unchanged ] | simply-alert }

    The allowed maximum number of route prefixes is set for the VPN instance IPv6 address family.

    NOTE:
    • The prefix limit command enables the system to display a message when the number of route prefixes added to the routing table of the VPN instance IPv6 address family exceeds the limit. If you run the prefix limit command to increase the maximum number of route prefixes in the VPN instance IPv6 address family or run the undo prefix limit command to cancel the limit, the system adds the excess route prefixes to the VPN IP routing table.

    • When the number of route prefixes exceeds the limit, direct routes and static routes can still be added to the routing table of the VPN instance IPv6 address family.

  8. (Optional) Configure a routing policy for the VPN instance.

    In addition to using VPN targets to control VPN route advertisement and reception, you can configure a routing policy for the VPN instance to better control VPN routes.
    • An import routing policy filters routes before they are imported into the VPN instance IPv6 address family.
    • An export routing policy filters routes before they are advertised to other PEs.
    NOTE:

    Create a routing policy before applying it to a VPN instance.

    Run the following commands as required:
    • Run import route-policy policy-name

      An import routing policy is configured for the VPN instance IPv6 address family.

    • Run export route-policy policy-name [ add-ert-first ]

      An export routing policy is configured for the VPN instance IPv6 address family.

  9. (Optional) Run apply-label { per-instance | per-route }

    A label distribution mode is configured in the VPN instance IPv6 address family.

    • The label per instance mode conserves label resources on the PE and lowers the requirement for the PE capacity. This mode is ideal if a large number of VPN routes on the PE exhaust MPLS label resources.
    • The label per route mode improves system security and allows downstream devices to load balance VPN traffic based on the inner labels of packets. This mode is ideal if only a small number of VPN routes exists on the PE and MPLS label resources are sufficient.

    By default, the label distribution mode is label per instance.

  10. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14084

Downloads: 25

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