BFD/4/STACHG_TODWN

Message

BFD/4/STACHG_TODWN:BFD session changed to Down. (SlotNumber=[STRING], Discriminator=[ULONG], Diagnostic=[STRING], Applications=[STRING], ProcessPST=[STRING], BindInterfaceName=[STRING], InterfacePhysicalState=[STRING], InterfaceProtocolState=[STRING])

Description

The status of a BFD session on an interface board changed to Down.

Parameters

Parameter Name	Parameter Meaning
SlotNumber	indicates the slot number of an interface board.
Discriminator	indicates the discriminator of a session.
Diagnostic	Indicates the type of the Down state. The values are as follows: AdminDown: The local end proactively enters the AdminDown state. Receive AdminDown: The local end enters the Down state after receiving a BFD packet with the AdminDown state from the remote end. DetectDown: The local end enters the Down state when the detection expires because it does not receive BFD packets from the remote end. NeighborDown: The local end enters the Down state after receiving a BFD packet with the Down state from the remote end.
Applications	indicates the application that is bound to the BFD session.
ProcessPST	indicates the flag bit of the PST that is modified.
BindInterfaceName	indicates the name of the bound interface.
InterfacePhysicalState	indicates the physical status of the interface.
InterfaceProtocolState	indicates the protocol status of the interface.

Possible Causes

The BFD session was Down because a BFD session on an interface board did not receive corresponding BFD packets within a detection period.

Procedure

Run the display bfd session all command to check whether the BFD session status is restored automatically.
(1) If so, go to Step 6.

(2) If not, go to Step 2.
Run the display current-configuration configuration bfd command to check whether one end of the link is not enabled with BFD.
(1) If BFD is disabled, enable BFD and then go to Step 1.

(2) If BFD is enabled, go to Step 3.
Run the display bfd session all command on both ends to check whether the BFD session is deleted.
(1) If so, go to Step 5.

(2) If not, go to Step 4.
Run the ping ip-addr command to check whether the link detected by the BFD session fails to forward traffic.
(1) If so, go to Step 5.

(2) If not, go to Step 6.
Collect log information and configuration information, and then contact technical support personnel.
End.