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


To have a better experience, please upgrade your IE browser.


Configuration Guide - IP Unicast Routing

S7700 and S9700 V200R011C10

This document describes IP Unicast Routing configurations supported by the switch, including the principle and configuration procedures of IP Routing Overview, Static Route, RIP, RIPng, OSPF, OSPFv3, IS-IS(IPv4), IS-IS(IPv6), BGP, Routing Policy ,and PBR, 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).


Graceful restart (GR) is a high availability (HA) technology used to ensure normal traffic forwarding when a routing protocol restarts and guarantee that key services are not affected in the process.

GR comprises a series of comprehensive technologies including fault-tolerant redundancy, link protection, faulty node recovery, and traffic engineering. As a redundancy technology, GR is widely used to ensure uninterrupted forwarding of key data during active/standby switchovers and system upgrades.

If GR is not enabled, an active/standby switchover leads to intermittent interruption of data forwarding. As a result, route flapping occurs on the whole network. This is unacceptable on a large-scale network, especially on a carrier network.

If GR is enabled, the forwarding plane continues to direct data forwarding when a restart occurs. Then actions on the control plane, such as reestablishment of neighbor relationships and route calculation, do not affect the forwarding plane. Service interruption caused by route flapping is therefore prevented, which improves network reliability.

Basic Concepts

  • Grace-LSA

    • OSPFv3 supports GR by flooding Grace-LSAs on the link.

    • Grace-LSAs are used when GR starts and ends to inform neighbors of the GR time, cause, and interface instance ID.

  • Router role

    • A router can function as a GR restarter, which has the GR capability and restarts in GR mode.

    • A router can function as a GR helper, which also has the GR capability and helps the GR restarter to complete the GR process.

  • GR implementation

    • Planned GR: This refers to a graceful restart of OSPFv3 through the reset ospfv3 graceful-restart command. In this mode, a Grace-LSA is sent to the neighbor before the restart.

    • Unplanned GR: This refers to an active/standby switchover triggered by router faults, such as loss of power, dead loops, exceptions, or master resets.

      Unlike planned GR, a Grace-LSA is not sent before the active/standby switchover. Instead, the switchover is performed directly. When the standby board becomes Up, a Grace-LSA is sent, and the GR process starts.

GR Process

Figure 6-3  OSPFv3 planned GR process (reset ospfv3 graceful-restart)

Figure 6-4  OSPFv3 unplanned GR process (active/standby switchover)

  • On the GR restarter:

  1. In planned GR mode, the GR restarter sends a Grace-LSA to all neighbors to inform them of the restart of a GR process and the duration and cause of this process.

    In unplanned GR mode, a Grace-LSA is sent to each neighbor immediately after the standby board is Up. This informs the neighbors of the restart of a GR process and the duration and cause of this process.

  2. The GR restarter sets up new neighbor relationships by negotiating with neighbors again.

  3. When all neighbor relationships between the GR restarter and the original neighbors enter the Full state:

    • The GR restarter exits the GR process and OSPFv3 recalculates routes.

    • The GR restarter updates its routing table on the main control board and the forwarding information bases (FIBs) on interface boards. It also deletes invalid routing entries.

    • The GR restarter sends a Grace-LSA with an aging time of 3600 seconds to instruct the GR helper to exit the GR process.

    The GR process is now complete.

  4. If errors occur during a GR process, the GR timer expires, or a neighbor relationship fails to enter the Full state during the GR process, the GR restarter exits the process and OSPFv3 is restarted in non-GR mode. This causes packets loss.

  • On the GR helper:

  1. A router that is configured to support the GR process on its neighbor enters the helper mode after receiving a Grace-LSA.

  2. The GR helper maintains its neighbor relationship with the GR restarter, and the status of the neighbor relationship does not change.

  3. If the GR helper continues to receive Grace-LSAs whose GR period differs from its own GR period, the GR helper updates its GR period to match that of the received Grace-LSAs.

  4. After the GR restarter informs the helper of the success of the GR process through a Grace-LSA with an aging time of 3600 seconds, the GR helper exits the GR process.

  5. If errors occur during the GR process, the GR helper exits the helper state and deletes invalid routes after route calculation.

Comparison of OSPFv3 GR and Non-GR Modes

Table 6-5  Comparison of OSPFv3 GR and non-GR modes

Active/Standby Switchover in Non-GR Mode

Active/Standby Switchover in GR Mode

  • OSPFv3 neighbor relationships are reestablished.

  • Routes are recalculated.

  • The forwarding table changes.

  • Route changes are sensed on the network and route flapping occurs over a short period of time.

  • Packets are lost during forwarding, and services are interrupted.

  • OSPFv3 neighbor relationships are reestablished.

  • Routes are recalculated.

  • The forwarding table does not change.

  • Route changes are not sensed, except on the neighbor of the device where the active/standby switchover occurs.

  • Packets are not lost during forwarding, and services are not affected.

Updated: 2019-10-18

Document ID: EDOC1000178324

Views: 276623

Downloads: 223

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next