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 IP+VPNv4 Hybrid FRR

Configuring IP+VPNv4 Hybrid FRR

This section describes how to configure IP+VPNv4 hybrid FRR. On a network where a CE is dual-homed to two PEs, if the link between the master PE and the CE is unreachable, the master PE switches traffic to the link between the backup PE and the CE for transmission. IP+VPNv4 hybrid FRR improves network reliability.

Usage Scenario

IP+VPNv4 hybrid FRR can quickly switch traffic from a PE to another PE that serves as the backup next hop if the primary route to a CE is unreachable.

A PE learns VPN routes with the same prefix from a CE and other PEs. In this situation, IP+VPNv4 hybrid FRR can be configured on the PE. After being enabled with IP+VPNv4 hybrid FRR, the PE generates a primary route and a backup route to the VPN prefix. If the link between the PE and CE fails, the traffic quickly switches to the backup next hop (backup PE).

On the network shown in Figure 5-16, in normal situations, PE1 selects Link_A to forward traffic to the CE and uses Link_B as the backup link. If PE2 detects that the route to the CE is unreachable, it will immediately switch traffic to Link_B and private network routes will be converged. This implementation minimizes the impact on VPN services.

Figure 5-16 IP+VPNv4 hybrid FRR

At present, the NE supports the following IP+VPNv4 hybrid FRR modes:

  • Private network IP FRR: applies to the networking where a non-BGP routing protocol runs between the PEs and CE.

  • Private network BGP auto FRR: applies to the networking where BGP runs between the PEs and CE.

Pre-configuration Tasks

Before configuring IP+VPNv4 hybrid FRR, complete the following tasks:

  • Configure a BGP/MPLS IP VPN.

  • Configure a PE to learn IP routes with the same prefix from a CE and other VPNv4 peers.

Procedure

  • Configure private network IP FRR.
    1. Run system-view

      The system view is displayed.

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

      The VPN instance view is displayed.

    3. Run ipv4-family

      The VPN instance IPv4 address family view is displayed.

    4. Run ip frr

      Private network IP FRR is enabled.

    5. Run commit

      The configuration is committed.

  • Configure private network BGP auto FRR.
    1. Run system-view

      The system view is displayed.

    2. Run bgp as-number

      The BGP view is displayed.

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

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

    4. Run auto-frr

      Private network BGP auto FRR is enabled.

    5. (Optional) Run route-select delay delay-value

      A delay for selecting a route to the intermediate device on the primary path is configured. After the primary path recovers, an appropriate delay ensures that traffic switches back to the primary path after the intermediate device completes refreshing forwarding entries.

      The delay-value value is an integer ranging from 0 to 3600, in seconds. The default delay-value value is 0, indicating that the device on which FRR is configured selects a route to the intermediate device on the primary path without a delay.

    6. Run commit

      The configuration is committed.

Example

Run the display ip routing-table vpn-instance vpn-instance-name [ ipv4-address ] verbose command to check the backup outbound interface and backup next hop of the IP route in the routing table.

Run the display ip routing-table vpn-instance vpn-instance-name verbose command on the PE. The command output shows that the route has a backup outbound interface and a backup next hop, and the backup next hop is on a tunnel, such as an LDP LSP.

<HUAWEI> display ip routing-table vpn-instance vpna 22.22.22.22 verbose 
Route Flags: R - relay, D - download
to fib, T - to vpn-instance, B - black hole route
------------------------------------------------------------------------------
Routing Table : vpna
Summary Count : 1

Destination: 22.22.22.22/32          
     Protocol: IBGP            Process ID: 0              
   Preference: 255                   Cost: 0              
      NextHop: 192.168.2.2      Neighbour: 0.0.0.0        
        State: Active Adv Relied      Age: 00h00m31s           
          Tag: 0                 Priority: low            
        Label: NULL               QoSInfo: 0x0            
   IndirectID: 0xa9          
 RelayNextHop: 192.168.2.2      Interface: GigabitEthernet0/2/0
     TunnelID: 0x0                  Flags: RD             
    BkNextHop: 10.1.1.2       BkInterface: GigabitEthernet0/1/0
      BkLabel: 0x27           SecTunnelID: 0x5000098        
 BkPETunnelID: 0x0        BkPESecTunnelID: 0x0              
 BkIndirectID: 0xaa
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33352

Downloads: 59

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