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 VPWS PW to Track VPNv4 Route Status

Configuring a VPWS PW to Track VPNv4 Route Status

Configuring a VPWS PW to track VPNv4 route status prevents traffic loss caused by black-hole routes.

Usage Scenario

On the network shown in Figure 10-10:
  • A PW is established between the CSG and each AGG. PW1 serves as the primary PW, and PW2 serves as the secondary PW.
  • A BGP VPNv4 peer relationship is established between AGG1 and RSG1, between AGG2 and RSG2, and between AGG1 and AGG2.
  • A VE group consisting of one L2VE interface and one L3VE interface is configured on each AGG. The L3VE interface on an AGG is bound to the VPN instance on that AGG.
Figure 10-10 Configuring a VPWS PW to track VPNv4 route status

In normal circumstances, the CSG sends traffic to RSG1 along the path CSG -> AGG1 -> RSG1. If the links between AGG1 and RSG1 and between AGG1 and AGG2 both fail, a black-hole route between AGG1 and RSG1 is generated. In this situation, the CSG cannot detect the link failures and still sends traffic to AGG1 for transmission. As a result, traffic loss occurs.

To prevent traffic loss, configure PW1 to track VPNv4 route status on AGG1. After the configuration, AGG1 instructs the CSG to switch traffic to the secondary PW if the links between AGG1 and RSG1 and between AGG1 and AGG2 both fail. The CSG then sends traffic to RSG1 along the path CSG -> AGG2 -> RSG2 -> RSG1, preventing traffic loss caused by the black-hole route.

Pre-configuration Tasks

Before configuring a VPWS PW to track VPNv4 route status, complete the following tasks:

Procedure

  • Configure each RSG to advertise the VPNv4 route configured on its loopback interface to its BGP VPNv4 peers.
    1. Run system-view

      The system view is displayed.

    2. Run interface loopback loopback-number

      The loopback interface view is displayed.

    3. Run ip binding vpn-instance vpn-instance-name

      The interface is bound to a VPN instance.

    4. Run ip address ip-address { mask | mask-length }

      An IP address is configured for the interface.

    5. Run quit

      Exit from the interface view.

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

      The BGP view is displayed.

    7. Run ipv4-family vpn-instance vpn-instance-name

      The BGP-VPN instance IPv4 address family view is displayed.

    8. Run network ipv4-address [ mask | mask-length ]

      The VPNv4 route is advertised to the RSG's BGP VPNv4 peers.

    9. Run commit

      The configuration is committed.

  • Configure PW1 to track VPNv4 route status on AGG1.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The AC interface view is displayed.

    3. Run mpls l2vpn track route ipv4-address { mask | mask-length } vpn-instance vpn-instance-name

      A VPWS PW is configured to track VPNv4 route status.

    4. Run commit

      The configuration is committed.

Checking the Configurations

After configuring VPWS PWs to track VPNv4 route status, check the configurations.

Run the display mpls l2vpn track route command on an AGG to check information about VPNv4 routes tracked by VPWS PWs.

<HUAWEI> display mpls l2vpn track route
Total route number:2    reachable :2          unreachable:0
-------------------------------------------------------------

VPN instance name : vrf1
Route             : 7.7.7.7/32
Route status      : reachable
PW number         : 1
VC ID      VC Type                Peer IP            VC State
-------------------------------------------------------------
1          VLAN                   1.1.1.1            up

VPN instance name : vrf1
Route             : 7.7.7.8/32
Route status      : reachable
PW number         : 1
VC ID      VC Type                Peer IP            VC State
-------------------------------------------------------------
2          VLAN                   1.1.1.1            up
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 30139

Downloads: 55

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