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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.
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).
Summary of Static Route Configuration Tasks

Summary of Static Route Configuration Tasks

Table 2-1 describes the static route configuration tasks.

Table 2-1 Static route configuration tasks




Configuring static routes

Static routes are manually configured by the administrator to ensure normal operation of simple networks and bandwidth for important network applications.

Configuring fault detection protocols for static routes

In actual networking, static routes are associated with fault detection protocols to improve network performance.

  • BFD for static routes: Unlike dynamic routing protocols, static routes do not have the detection mechanism. If a fault occurs on the network, the administrator needs to rectify it. BFD for static routes enables a BFD session to detect the link status of the static route and performs millisecond-level fault detection.

  • NQA for static routes: In actual networking, link status must be detected in real time to ensure network stability, and a link switchover can be performed according to link status changes. In most cases, ARP and BFD are used to detect link status. IGP convergence can also be used. However, the preceding solutions are not applicable to the following scenarios:
    • If only one link rather than links of every user on the network needs to be detected, ARP probing is not applicable.
    • If any device on the network does not support BFD, BFD detection cannot be implemented.
    • If either end of a link is a Layer 2 device, dynamic routing protocols cannot be configured and therefore IGP convergence cannot be implemented.
    NQA for static routes only requires one end of the interconnected devices to support NQA and can be used even if there are Layer 2 devices. In this case, the preceding issues are resolved. When a link is faulty, an NQA test instance can immediately detect the link change and delete the static route associated with the NQA test instance from the IP routing table, affecting traffic forwarding.

Configuring FRR for static routes

On traditional IP networks, it takes the routing system several seconds to complete route convergence after a link fault is detected. For services that require low delay and low packet loss rate, the second-level convergence time is unacceptable as it may lead to a service interruption. For example, VoIP services can tolerate only millisecond-level network interruption. When a fault is detected at the physical layer or link layer, FRR for static routes implements millisecond-level convergence, reducing the impact on services.

Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 48026

Downloads: 58

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