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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 V800R010C10SPC500 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 OSPFv3 IP FRR

Configuring OSPFv3 IP FRR

If a link fails, an OSPFv3 IP FRR-capable device can fast switch traffic to a backup link, which protects traffic and improves OSPFv3 network reliability.

Usage Scenario

As networks develop, services such as Voice over IP (VoIP) and on-line video services require high-quality real-time transmission. Nevertheless, if an OSPFv3 fault occurs, traffic can be switched to a new link only after the fault detection that lasts milliseconds, fault notification to the routing control plane that lasts milliseconds, new topology information generation and flooding that lasts milliseconds, Shortest Path First (SPF) calculation that lasts tens of milliseconds, and new route notification and adding that lasts hundreds of milliseconds. As a result, it takes much more than 50 ms, the maximum convergence time tolerable for VoIP and on-line video services, which cannot meet the requirement for real-time services on the network.

With OSPFv3 IP FRR that calculates a backup link in advance, devices can fast switch traffic to the backup link without interrupting traffic if the primary link fails, which protects traffic and improves OSPFv3 network reliability.

OSPFv3 IP FRR is applicable to services that are sensitive to the packet delay and packet loss.

OSPFv3 LFA FRR uses the SPF algorithm to calculate the shortest path from each neighbor (root node) that provides a backup link to the destination node and store the node-based backup next hop, which applies to single-source routing scenarios. As networks are increasingly diversified, two ABRs or ASBRs are deployed to improve network reliability. In this case, OSPFv3 FRR in a multi-source routing scenario is needed. In Figure 6-3, Device B and Device C function as ABRs to forward area 0 and area 1 routes. Device E advertises an intra-area route. Upon receipt of the route, Device B and Device C translate it to a Type 3 LSA and flood the LSA to area 0. After OSPFv3 FRR is enabled on Device A, Device A considers Device B and Device C as its neighbors. Without a fixed neighbor as the root node, Device A fails to calculate FRR backup next hop. To address this problem, a virtual node is simulated between Device B and Device C and used as the root node of Device A, and Device A uses the LFA algorithm to calculate the backup next hop. This solution converts multi-source routing into single-source routing.
Figure 6-3 OSPFv3 FRR in a multi-route source scenario

After OSPFv3 IP FRR is configured, the lower layer needs to fast respond to a link change so that traffic can be fast switched to the backup link. After FRR and BFD are bound, link failures can be detected rapidly so that traffic is rapidly switched to the backup link if the primary link fails.

Pre-configuration Tasks

Before configuring OSPFv3 IP FRR, complete the following tasks:

  • Configure a link layer protocol.

  • Configure IP addresses for interfaces to ensure that neighboring nodes are reachable at the network layer.

  • Configure basic OSPFv3 functions.

Configuration Procedures

Figure 6-4 Flowchart for configuring OSPFv3 IP FRR

Enabling OSPFv3 IP FRR

With OSPFv3 IP FRR and loop-free backup links, a device can switch traffic to a backup link immediately if the primary link fails.

Context

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ] [ vpn-instance vpn-instance-name ]

    An OSPFv3 process is enabled, and the OSPFv3 view is displayed.

  3. Run frr

    The OSPFv3 IP FRR view is displayed.

  4. Run loop-free-alternate

    OSPFv3 IP FRR is enabled, and a loop-free backup link is generated.

    NOTE:

    OSPFv3 can generate a loop-free backup link only when the OSPFv3 IP FRR traffic protection inequality is met.

  5. (Optional) Run frr-policy route { route-policy route-policy-name | route-filter route-filter-name }

    An OSPFv3 IP FRR filtering policy is configured.

    After the OSPFv3 IP FRR filtering policy is configured, only the OSPFv3 backup routes that match the filtering conditions of the policy can be added to the forwarding table.

  6. (Optional) Run tiebreaker { node-protecting | lowest-cost } preference preference

    The solution of selecting a backup path for OSPFv3 IP FRR is set.

    By default, the solution of selecting a backup path for OSPFv3 IP FRR is node-protection path first. In some cases, the solution needs to be changed to smallest-cost path first because of data forwarding capacity or link cost consideration. In Figure 6-5, the primary path is Link-1 (Device S -> Device E -> Device D), and Link-2 and Link-3 (Device S -> Device N -> Device D) are backup path candidates. By default, Link-3 is selected as the backup path. To change the solution of selecting a backup path for OSPFv3 IP FRR to smallest-cost path first, run the tiebreaker command. After the command is run, Link-2 is selected as the backup path.
    Figure 6-5 Solution of selecting a backup path for OSPFv3 IP FRR

  7. Run commit

    The configuration is committed.

(Optional) Binding IP FRR and BFD

Binding IP FRR and BFD enables the lower layer to fast respond to a link change so that traffic can be rapidly switched to the backup link if the primary link fails.

Context

Binding the BFD session status to the link status of an interface ensures that link failures are detected rapidly and that traffic is rapidly switched to the backup link.

  • If IP FRR of an OSPFv3 process is bound to BFD, IP FRR on all interfaces in the OSPFv3 process is bound to BFD.
  • If only a small number of interfaces need to have IP FRR bound to BFD, bind IP FRR on each interface to BFD one by one.

Perform the following steps on the ME device where IP FRR and BFD need to be associated:

Procedure

  • Bind IP FRR and BFD in an OSPFv3 process.
    1. Run system-view

      The system view is displayed.

    2. Run ospfv3

      An OSPFv3 process is enabled, and the OSPFv3 view is displayed.

    3. Run bfd all-interfaces frr-binding

      IP FRR and BFD are bound in the OSPFv3 process.

    4. Run commit

      The configuration is committed.

  • Bind IP FRR and BFD on a specified OSPFv3 interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      An interface view is displayed.

    3. Run ospfv3 bfd frr-binding

      IP FRR and BFD are bound on the interface.

    4. Run commit

      The configuration is committed.

Follow-up Procedure

The BFD configuration on an interface takes precedence over that in an OSPFv3 process. If BFD is enabled on an interface, a BFD session is established based on the BFD parameters set on the interface.

(Optional) Blocking FRR on an OSPFv3 Interface

If FRR is not required on certain OSPFv3 interfaces, FRR needs to be blocked on these interfaces.

Context

If an interface runs key services, ensure that the backup path does not pass through this interface so that services will not be affected after FRR calculation.

Perform the following steps on the interfaces of the device where OSPFv3 IP FRR has been configured:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The view of the OSPFv3 interface running FRR is displayed.

  3. Run ospfv3 frr block

    FRR is blocked on the OSPFv3 interface.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of OSPFv3 IP FRR

After configuring OSPFv3 IP FRR, you can view information about the primary and backup links.

Prerequisites

OSPFv3 IP FRR has been configured.

Procedure

  • Run the display ospfv3 [ process-id ] routing verbose command to view the primary and backup links after OSPFv3 IP FRR is enabled.

Example

Run the display ospfv3 [ process-id ] routing command on the device running OSPFv3 to view information about the backup next hop.

<HUAWEI> display ospfv3 routing verbose
   OSPFv3 Process (1)
    Destination   :34::                           Prefix Length    :64
    Metric        :1                              Type             :INTRA-AREA
    Nexthop       :::                             Nexthop Interface:Eth3/0/0
    Priority      :Low
 
    Destination   :44::                           Prefix Length    :64
    Metric        :2                              Type             :INTRA-AREA
    Nexthop       :FE80:ABCD:ABCD:ABCD::ABCD      Nexthop Interface:Eth3/0/0
    Backup Nexthop:FE80::2200:10FF:FE03:0         Backup Interface :Eth3/0/0.1 
    Backup Type   :LINK PROTECT
    Priority      :Low
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 22430

Downloads: 15

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