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 - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - IP Routing
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 FRR for IPv4 Static Routes

Configuring FRR for IPv4 Static Routes

Fast reroute (FRR) is applicable to services that are sensitive to packet delay and packet loss. FRR can be configured for IPv4 static routes to protect traffic using backup links.

Usage Scenario

FRR is applicable to IP services that are sensitive to delay and packet loss. FRR minimizes the impact of link faults on services.

You can specify different priorities for different static routes to implement FRR for static routes. Routes with the same destination IP address but different priorities can back up each other.

Pre-configuration Tasks

Before configuring FRR for IPv4 static routes, complete the following tasks:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ip route-static frr [ vpn-instance vpn-instance-name ]

    FRR is enabled for public or VPN IPv4 static routes.

    NOTE:

    To implement route backup by configuring FRR for static routes, specify different priorities for these static routes.

    If FRR for static routes and BFD are both configured and a static route has an Ethernet interface as its outbound interface but has no next hop address, FRR cannot be implemented between this static route and those with next hop addresses. To implement FRR between them, specify a next hop address for this route.

  3. (Optional) Enable IP FRR poison reverse.
    1. Run interface interface-type interface-number

      The interface or sub-interface view is displayed.

    2. Run poison-reverse enable

      IP FRR poison reverse is enabled.

      On an IP ring network configured with IP FRR, the poison-reverse enable command is used to prevent instantaneous traffic storms caused by route convergence.

      In a load balancing scenario, poison reverse does not take effect.

  4. Run commit

    The configuration is committed.

Checking the Configurations

Run the following commands to check the previous configuration.

  • Run the display ip routing-table verbose command to check detailed information about the backup outbound interface and the backup next hop in the routing table.

  • Run the display ip routing-table ip-address [ mask | mask-length ] [ longer-match ] verbose command to check detailed information about the backup outbound interface and the backup next hop in the routing table.

  • Run the display ip routing-table ip-address1 { mask1 | mask-length1 } ip-address2 { mask2 | mask-length2 } verbose command to check detailed information about the backup outbound interface and the backup next hop in the routing table.

# Run the display ip routing-table verbose command to view detailed information about the backup outbound interface and the backup next hop in the routing table.

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

Destination: 172.17.1.0/24
     Protocol: OSPF          Process ID: 1
   Preference: 60                    Cost: 0
      NextHop: 192.168.10.2     Neighbour: 0.0.0.0
        State: Active Adv             Age: 00h00m06s
          Tag: 0                 Priority: 0
        Label: NULL               QoSInfo: 0x0
 RelayNextHop: 0.0.0.0          Interface: GigabitEthernet0/2/0
     TunnelID: 0x0                  Flags:  D
    BkNextHop: 192.168.20.2   BkInterface: GigabitEthernet0/3/0
      BkLabel: 0              SecTunnelID: 0x0
 BkPETunnelID: 0x0        BkPESecTunnelID: 0x0
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 34341

Downloads: 51

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