IS-IS GR configuration example

Network requirements

As shown in Figure 44, Switch A, Switch B, and Switch C belong to the same IS-IS routing domain.

Figure 44: Network diagram

Configuration procedure

  1. Configure IP addresses and subnet masks for interfaces. (Details not shown.)

  2. Configure IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at layer 3 and dynamic route update can be implemented among them with IS-IS. (Details not shown.)

  3. Enable IS-IS GR on Switch A.

    <SwitchA> system-view
    [SwitchA] isis 1
    [SwitchA-isis-1] graceful-restart
    [SwitchA-isis-1] return
    

Verifying the configuration

After Switch A establishes adjacencies with Switch B and Switch C, they begin to exchange routing information.

# Restart the IS-IS process on Switch A.

<SwitchA> reset isis all 1 graceful-restart
Reset IS-IS process? [Y/N]:y

Switch A enters the restart state and sends connection requests to its neighbors through the GR mechanism to synchronize the LSDB.

# Check the GR status of IS-IS on Switch A.

<SwitchA> display isis graceful-restart status

                        Restart information for IS-IS(1)
                        --------------------------------
Restart status: COMPLETE
Restart phase: Finish
Restart t1: 3, count 10; Restart t2: 60; Restart t3: 300
SA Bit: supported

                          Level-1 restart information
                          ---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0

                          Level-2 restart information
                          ---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0