BFD/4/STACHG_TODWN

Message

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

Description

The BFD session went Down.

Parameters

Parameter Name	Parameter Meaning
SlotNumber	Slot ID.
Discriminator	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. ReceiveAdminDown: 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	Application that is bound to the BFD session.
ProcessPST	Flag bit of the PST that is modified.
BindInterfaceName	Name of the bound interface.
InterfacePhysicalState	Physical status of the interface.
InterfaceProtocolState	Protocol status of the interface.
TunnelName	Name of the tunnel.
DownReason	Reason why the session goes down.
NpDownTime	Date and time when the BFD session goes down.
PeerIp	Destination IP address

Possible Causes

Cause 1: The session bound interface goes down.

Cause 2: The peer BFD session is deleted or shut down.

Cause 3: The link went Down or was congested. Consequently, packet forwarding fails.

Procedure

1. Run the display interface command to check whether the physical status of the interface where the session resides is Up.

If so, go to Step 2.
If no, go to Step 6.

2. Check whether the session status is automatically restored.

If yes, go to Step 6.
If no, go to Step 3.

3. Run the display bfd session all command to check whether the BFD sessions at both ends are deleted.

If yes, go to Step 6.
If no, go to Step 5.

4. Run the ping ip-address command to check whether the link detected by the BFD session fails to forward packets.

If yes, go to Step 6.
If no, go to Step 5.

5. Collect log and configuration information, and contact technical support personnel.

6. End.