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.


CLI-based Configuration Guide - IP Unicast Routing

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

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

On a network, you can accurately control route selection by configuring static routes. If other static route functions are required, configure them according to reference sections.

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 working of simple networks and bandwidth for important network applications.

Configuring other protocols for static routes

In actual networking, static routes are associated with other 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 handle it. BFD for static routes enables a BFD session to detect the link status of the static route and performs fault detection at millisecond level.

  • Network Quality Analysis (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. ARP and BFD are used to detect link status. In addition, IGP convergence can also be used. However, the preceding solutions are not applicable to the following special scenarios:
    • If only one link rather than links of every user on the network needs to be detected, ARP detection is not applicable.
    • If any device on the network does not support BFD, BFD detection cannot be implemented.
    • If either end of the 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. The preceding problems are solved. 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.
Updated: 2019-05-17

Document ID: EDOC1000174069

Views: 140585

Downloads: 280

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