BFD_1.3.6.1.4.1.2011.5.25.38.3.8 hwBfdSessFaultDown

Description

BFD/3/BFD_FAULT_TRAP: "OID [OID] The BFD session went Down. (Index=[integer], SessName=[octet], LocalDiscriminator=[integer], Diagnosis=[integer], BindIfName=[octet])"

The status of a BFD session changed to Down.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.38.3.8	Minor	communicationsAlarm

Parameters

Name	Meaning
oid	Indicates the ID of a MIB object.
Index	Indicates the index of a BFD session.
SessName	Indicates the name of a BFD session.
LocalDiscriminator	Indicates the local discriminator.
Diagnosis	Indicates session diagnosis information.
BindIfName	Indicates the name of the bound interface.

Impact on the System

Service traffic bound to the BFD session is switched.

Possible Causes

Cause 1: The BFD session was terminated on the local or remote end.
Cause 2: The BFD session was deleted on the remote end.
Cause 3: Traffic forwarding fails because the link is congested.

Procedure

Run the display bfd session all command to check whether the BFD session recovers.
- If so, go to Step 6.
- If not, go to Step 2.
Run the display current-configuration configuration | include bfd command to check whether BFD is disabled on the local or remote end.
- If so, enable BFD and go to Step 1.
- If not, go to Step 3.
Run the display bfd session all command to check whether the BFD session is deleted or shut down on the local or remote end.
- If so, go to Step 5.
- If not, go to Step 4.
Run the ping command to check whether the link monitored by the BFD session is working properly.
- If so, go to Step 6.
- If not, go to Step 5.
Collect alarm and configuration information, and contact technical support personnel.
End.