NSR is introduced to solve the problem. It backs up IS-IS link state information from the master device to
the slave device. After a master/slave switchover, NSR can complete link state recovery and route
re-generation without requiring the cooperation of other devices.
Follow these steps to configure IS-IS NSR:
To do...
Enter system view
Enter IS-IS view
Enable IS-IS NSR
Set the NSR interval
Configuring IS-IS FRR
NOTE:
Do not use FRR and BFD at the same time. Otherwise, FRR may fail to take effect.
•
The automatic backup next hop calculation of FRR and that of TE are mutually exclusive.
•
Introduction
When a link fails, the packets on the path are discarded, or a routing loop occurs until IS-IS completes
the routing convergence based on the new network topology.
You can enable IS-IS fast reroute (FRR) to reduce traffic recovery time.
Figure 62 Network diagram for IS-IS FRR
In
Figure
62, after you enable FRR on Router B, IS-IS automatically calculates or designates a backup next
hop when a link failure is detected. In this way, packets are directed to the backup next hop to reduce
traffic recovery time. Meanwhile, IS-IS calculates the shortest path based on the new network topology,
and forwards packets over the path after network convergence.
You can either enable IS-IS FRR to calculate a backup next hop automatically, or to designate a backup
next hop with a routing policy for routes matching specific criteria.
Configuration prerequisites
Before configuring IS-IS FRR, complete the following tasks:
Configure network layer addresses for interfaces to make the neighboring nodes reachable at the
•
network layer
Use the command...
system-view
isis [ process-id ] [ vpn-instance
vpn-instance-name ]
non-stop-routing
non-stop-routing interval
interval-value
161
Remarks
—
—
Required
Disabled by default
Required
0 seconds by default, that is, no NSR interval
is configured.