The IS-IS Client for BFD C-Bit Support feature provides BFD with a way to signal to its peers whether the BFD implementation shares the same status as the control plane. When a neighboring router’s control plane restarts, a BFD session failure may occur, which does not actually represent a true forwarding failure. If this happens, you do not want the neighbors of the restarting router to react to the BFD session failure.
IS-IS does not have protocol extensions that allow it to signal in advance that it will be restarting. This means that the system cannot distinguish between a real forwarding failure and a restart. The IS-IS Client for BFD C-Bit Support feature allows you to configure the device to ignore control-plane related BFD session failures. We recommend that you configure this feature on the neighbors of a restarting device just prior to the planned restart of that device and that you remove the configuration after the restart has been completed.
The table below shows how the control plane independent failure status received from BFD on a session down event impacts IS-IS handling of that event.
Table 1 Control Plane Failure and Session Down Events|
IS-IS Check Control Plane Failure
|
BFD Control Plane Independent Failure Status
|
IS-IS Action on BFD session 'DOWN' Event
|
|
Enabled
|
True
|
Accept session DOWN
|
|
Enabled
|
False
|
Ignore session DOWN
|
|
Disabled
|
True
|
Accept session DOWN
|
|
Disabled
|
False
|
Accept session DOWN
|