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

S1720, S2700, S5700, and S6720 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).
Configuring an H-VPN

Configuring an H-VPN

Context

In addition to basic BGP/MPLS IP VPN configuration, you need to specify UPE devices on the SPE device and advertise default routes of VPN instances to the UPE devices.

When VPN services need to be transmitted over TE tunnels or when multiple tunnels need to perform load balancing to fully use network resources, you also need to configure tunnel policies. For details, see Configuring Tunnel Policies.

Perform the following steps on the SPE device.

On an H-VPN, superstratum provider edge devices (SPEs) function as route reflectors (RRs) and user-end provider edge devices (UPEs) function as RR clients. UPEs receive specific routes from SPEs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    bgp as-number

    The BGP view is displayed.

  3. Run:

    ipv4-family vpnv4

    The BGP-VPNv4 address family view is displayed.

  4. Run:

    peer { ipv4-address | group-name } reflect-client

    The SPE is configured as an RR and the UPEs are configured as RR clients.

  5. Run:

    peer { ipv4-address | group-name } next-hop-local

    The SPE is configured to use its own IP address as the next hops of routes when advertising these routes.

    To enable an SPE to use its own IP address as the next hops of routes when advertising these routes to UPEs and NPEs, run the peer next-hop-local command twice with different parameters specified on the SPE.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141944

Views: 91440

Downloads: 527

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