Configuring the Interval for Detecting IS-IS Neighboring Device Failures

To minimize the effects caused by neighboring device failures on an IS-IS network, accelerate the speed of detecting IS-IS neighboring device failures.

Context

Connection status between an IS-IS device and its neighboring devices can be monitored by exchanging Hello packets at intervals. If a device does not receive any Hello packets from a neighboring device within a specified period (holdtime), the neighboring device is considered down, and LSP flooding and SPF calculation are triggered, implementing IS-IS route reconvergence.

To adjust the fault detection speed, use the following methods to accelerate the speed of detecting IS-IS neighboring device failures:

Configure the interval at which Hello packets are sent.
Configure the number of Hello packets that are sent before the local device considers the neighbor Down.

Holdtime of neighboring devices = Interval at which Hello packets are sent x Number of Hello packets that are sent before the local device considers the neighbor Down. The maximum value of the holdtime is 65535s.
Configure dynamic IPv6 BFD for IS-IS.

Dynamic IPv6 BFD is recommended for faster neighbor fault detection.

Procedure

Set an interval at which Hello packets are sent.
1. Run system-view
  The system view is displayed.
2. Run interface interface-type interface-number
  The interface view is displayed.
3. Run isis timer hello hello-interval [ level-1 | level-2 ] [ conservative ]
  The interval at which Hello packets are sent is set.
  If the conservative parameter is specified in the command, the conservative mode is enabled for the holdtime of the IS-IS neighbor relationship.
  - If the parameter is specified and the holdtime of the IS-IS neighbor relationship is less than 20s, the IS-IS neighbor relationship is disconnected when the hold time elapses.
  - If the parameter is not specified and the holdtime of the IS-IS neighbor relationship is less than 20s, the IS-IS neighbor relationship is disconnected when the period of the hold time and a delay elapses.
  A broadcast link can transmit both Level-1 and Level-2 Hello packets. You can set different intervals for these two types of Hello packets. By default, both Level-1 and Level-2 Hello packets are sent.
  
  A P2P link can transmit only one type of Hello packets. Therefore, neither level-1 or level-2 needs to be specified if a P2P link is used.
4. Run commit
  The configuration is committed.
Configure the number of Hello packets that are sent before the local device considers the neighbor Down.
1. Run system-view
  The system view is displayed.
2. Run interface interface-type interface-number
  The interface view is displayed.
3. Run isis timer holding-multiplier number [ level-1 | level-2 ]
  The number of Hello packets that are sent before the local device considers the neighbor Down is configured.
  
  A broadcast link can transmit both Level-1 and Level-2 Hello packets. You can set different intervals for these two types of Hello packets. By default, both Level-1 and Level-2 Hello packets are sent.
  
  A P2P link can transmit only one type of Hello packets. Therefore, neither level-1 or level-2 needs to be specified if a P2P link is used.
4. Run commit
  The configuration is committed.