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 - Reliability

S9300, S9300E, and S9300X V200R013C00

This document describes the configurations of Reliability, including BFD Configuration, VRRP Configuration, NSR Configuration, DLDP Configuration, Smart Link and Monitor Link Configuration, MAC Swap Loopback Configuration, EFM Configuration, CFM Configuration, Y.1731 Configuration.
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).
Understanding NSR

Understanding NSR

Basic Concepts

  • High availability (HA): supports a backup channel between the active and standby MPUs.
  • Non-stop forwarding (NSF): enables uninterrupted traffic forwarding.
  • Non-stop routing (NSR): enables the device to use the standby control plane to restore services immediately if an active control plane fails, whereas the control planes of neighboring nodes do not detect the fault.
  • Line interface processing unit (LPU): implements forwarding plane processes.

NSR Procedure

The NSR process on the network shown in Figure 4-1 consists of the following phases:
  1. Batch backup: NSR is automatically enabled after the standby MPU starts. The active MPU sends routing and forwarding information in batches to the standby MPU. A batch backup is performed before a real-time backup. NSR does not perform a switchover of active and standby MPUs during the batch backup.
  2. Real-time backup: After the batch backup is complete, any updates to the control and forwarding planes can be backed up to the standby MPU in real time. NSR is ready to perform a switchover of active and standby MPUs to allow the standby MPU to take over traffic from the active MPU if a fault occurs.
  3. Switchover of active and standby MPUs: If the active MPU fails, the standby MPU detects the failure and becomes the new active MPU. The standby MPU instructs LPUs to send packets to the standby MPU itself. The switchover of active and standby MPUs is complete rapidly so that the routes between the local node and its neighboring nodes remain reachable.
Figure 4-1  NSR procedure

Figure 4-2  Batch backup process

After the NSR is enabled, the standby MPU starts and sends a message about its in-service status to the active MPU. After receiving the message, the active MPU backs up its data in batches to the standby MPU.

  • If the active MPU fails after the batch backup is complete, the standby MPU can become a new active MPU and restore data.

  • If the active MPU fails before the batch backup is complete, the standby MPU cannot become a new active MPU. The device then restarts automatically.

Figure 4-3  Real-time backup process

After the batch backup is complete, if the neighbor status or routing information changes on the active MPU, the active MPU immediately sends updated information to the standby MPU.

Figure 4-4  Switchover of active and standby MPUs

If software or hardware of the active MPU fails, the standby MPU detects the failure and automatically becomes the new active MPU. The new active MPU uses the backed up data to forward traffic. LPUs send the new active MPU their information, including the information that has been updated during the switchover of active and standby MPUs. Routes are reachable and traffic forwarding is uninterrupted during the switchover.

Differences Between NSF (GR) and NSR

NSF and NSR are two HA solutions. Table 4-1 describes the differences between NSF (GR) and NSR.

Table 4-1  Differences between NSF (GR) and NSR

Different

NSF (GR)

NSR

Implementation

The forwarding plane is not interrupted, that is, services are not interrupted.

The control and forwarding planes are not interrupted, that is, route processing and services are not interrupted.

Whether Other Nodes Are Dependent

Neighboring nodes need to support NSF. NSF needs to be deployed on the entire network.

Neighboring nodes do not need to support NSR.

Convergence Speed

The convergence speed is slow. When the fault is rectified, the device needs to learn the network topology and routing again.

The convergence speed is fast. During switching, the neighbor and topology information is not lost and the neighbor relationship is not terminated.

Impact on the System

The load is small.

The load is large.

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065868

Views: 21964

Downloads: 13

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