BFD_1.3.6.1.4.1.2011.5.25.38.3.8 hwBfdSessFaultDown

Trap Buffer Description

The BFD session went Down. (Index=[Index], SessName=[ConfigurationName], LocalDiscriminator=[LocalDiscriminator], Diagnosis=[Diagnosis], BindIfName=[BindIfName], Description=[Description], FeNodeID=[FeNodeID], PeerIp=[PeerIp], LinkType=[LinkType], BindVpnName=[BindVpnName], TunnelName=[TunnelName], DownReason=[DownReason])

The status of a BFD session changed to Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwBfdSessFaultDown
Trap OID	1.3.6.1.4.1.2011.5.25.38.3.8
MIB	HUAWEI-BFD-MIB
Alarm ID	0x00F102ce
Alarm Name	hwBfdSessFaultDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	BFD_1.3.6.1.4.1.2011.5.25.38.3.9 hwBfdSessResume

Trap Buffer Parameters

Parameter	Description
Index	Index
ConfigurationName	Session Configuration Name
LocalDiscriminator	Local Discriminator
Diagnosis	Diagnosis
BindIfName	Interface Name
Description	BFD Session Description
FeNodeID	Board ID of the session
PeerIp	Destination address of a session
LinkType	Session type
BindVpnName	Bound VPN Name
TunnelName	Tunnel Name
DownReason	Down reason

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.38.2.3.1.4	hwBfdSessCfgName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.8	hwBfdSessLocalDiscr	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.18	hwBfdSessDiag	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.7	hwBfdSessBindIfName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.62	hwBfdSessDescription	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.63	hwBfdSessFeNodeID	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.56	hwBfdSessPeerInetAddr	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.64	hwBfdSessLinkType	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.21	hwBfdSessVPNName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.65	hwBfdSessTunnelName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.66	hwBfdSessDownReason	hwBfdSessIndex

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

1. Run the display bfd session all command to check whether the BFD session recovers.

If the BFD session recovers, go to Step 6.
If the BFD session does not recover, go to Step 2.

2. Run the display current-configuration configuration bfd command to check whether BFD is disabled on either of both ends.

If BFD is disabled on either end, enable BFD and go to Step 1.
If BFD is enabled on both ends, go to Step 3.

3. Run the display bfd session all command to check whether the BFD sessions are deleted on either end.

If the BFD sessions are deleted on either end, go to Step 5.
If the BFD sessions are not deleted on either end, go to Step 4.

4. Run the ping ip-address command to check whether the link monitored by the BFD session is working properly.

If the link monitored by the BFD session is not working properly, go to Step 5.
If the link monitored by the BFD session is working properly, go to Step 6.

5. Contact Huawei technical support personnel.

6. End.