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 7-5 describes the static route configuration tasks.
Table 7-5 Static route configuration tasks
Scenario
|
Description
|
Task
|
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.
|
|
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 convergence time of several seconds is
unacceptable as it may lead to 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 convergence at
the millisecond level, reducing the impact on services.
|
|
Previous
