Is-Is Nsr Configuration Example - HPE 5800 Series Configuration Manual

IS-IS NSR configuration example

Network requirements
As shown in
Switch S is an IRF fabric, which is connected to Switch A and Switch B over aggregated links. Enable
IS-IS NSR on Switch S to ensure correct routing when a master/slave switchover occurs on Switch
S.
Figure 53 Network diagram
Configuration procedure
Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
1.
Configure IS-IS on the switches to make sure Switch S, Switch A, and Switch B can
2.
communicate with each other at Layer 3, and dynamic route update can be implemented
among them with IS-IS. (Details not shown.)
Enable IS-IS NSR on Switch S.
3.
<SwitchS> system-view
[SwitchS] isis 1
[SwitchS-isis-1] non-stop-routing
[SwitchS-isis-1] non-stop-routing interval 30
[SwitchS-isis-1] return
Verify the configuration:
4.
After Switch S establishes neighbor relationships with Switch A and Switch B, they start to
exchange routing information. After network convergence, perform a master/slave switchover
on Switch S. During the switchover period, use the display isis peer command to check the
neighbor relationship between Switch A and Switch S and between Switch B and Switch S; use
the display isis route command to check if routes from Switch A to the loopback interface on
Switch B and from Switch B to the loopback interface on Switch A exist.
# Display IS-IS neighbors and routes on Switch A when a master/slave switchover occurs on
Switch S.
<SwitchA> display isis peer
System Id: 0000.0000.0001
Interface: vlan100
State: Up
System Id: 0000.0000.0001
Interface: vlan100
State: Up
<SwitchA> display isis route
Route information for ISIS(1)
Figure 53, Switch S, Switch A, and Switch B belong to the same IS-IS routing domain.
Peer information for ISIS(1)
HoldTime: 25s
HoldTime: 27s
----------------------------
Circuit Id: 0000.0000.0001.01
Type: L1(L1L2)
Circuit Id: 0000.0000.0001.01
Type: L2(L1L2)
-----------------------------
158
PRI: 64
PRI: 64