BFD_1.3.6.1.4.1.2011.5.25.38.3.13 hwBfdIPv6SessDown

Trap Buffer Description

Session changes to DOWN. (Index=[Index], ConfigurationName=[ConfigurationName], BindIfIndex=[BindIfIndex], BindIfName=[BindIfName], Diagnosis=[Diagnosis], BindVrfIndex=[BindVrfIndex], BindVpnName=[BindVpnName], SessionType=[SessionType], BindType=[BindType], StaticLspName=[StaticLspName], PwSecondary=[PwSecondary], VcId=[VcId], VsiName=[VsiName], VsiPeerAddress=[VsiPeerAddress], DiscrAuto=[DiscrAuto], PeerIpv6=[PeerIpv6], Ipv6NextHop=[Ipv6NextHop])

The BFD IPv6 session went Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	hwBfdIPv6SessDown
Trap OID	1.3.6.1.4.1.2011.5.25.38.3.13
MIB	HUAWEI-BFD-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
Index	BFD session ID.
ConfigurationName	BFD session name.
BindIfIndex	Bound interface index.
BindIfName	Bound interface name.
Diagnosis	Session diagnostic word 0: No diagnostic word 1: Detection time Down 2: Echo detection Down 3: Neighbor advertisement Down 4: Forwarding plane reset 5: Path Down 6: Cascading path Down 7: Administratively Down 8: Reverse cascading path Down 9: Peer administratively Down 25: IP error code stop 26: IP error code start 27: Section error code stop 28: Section error code start 29: LSP error code stop 30: LSP ingress error code start 31: LSP transit error code start.
BindVrfIndex	Index of the bound VPN instance.
BindVpnName	Name of the bound VPN instance.
SessionType	Indicates the type of a session. 1: static, which indicates that the BFD session is statically configured. 2: Dynamic, which indicates that the BFD session is dynamically triggered. 3: Entire_Dynamic: indicates that a BFD session is dynamically triggered. After the function of passively creating a BFD session is enabled on the egress of the LSP, the BFD session is created. 4: Static_Auto: indicates a static BFD session with automatically negotiated discriminators.
BindType	Bound type: 2 or 3: Peer IP address (multi-hop IP link detection). 1 or 4: Interface (single-hop IP link detection). 9: LDP_LSP (LDP LSP detection). 11: TE_LSP (detection of the LSP bound to a TE tunnel). 12: TE_TUNNEL (TE tunnel detection). 13: PW (PW link detection). 15: VSI_PW (VSI PW link detection).
StaticLspName	Static LSP name The value is always -.
PwSecondary	Secondary PW flag. 1: primary PW. 2: secondary PW. 3: non-PW link.
VcId	VC ID.
VsiName	VSI name.
VsiPeerAddress	VSI peer address.
DiscrAuto	Static auto-negotiation discriminator.
PeerIpv6	Bound destination IPv6 address.
Ipv6NextHop	Next hop IPv6 address.

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.6	hwBfdSessBindIfIndex	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.18	hwBfdSessDiag	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.20	hwBfdSessVrfIndex	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.22	hwBfdSessType	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.26	hwBfdSessBindType	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.28	hwBfdSessStaticLspName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.30	hwBfdSessPWSecondaryFlag	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.32	hwBfdSessVcId	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.33	hwBfdSessVsiName	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.34	hwBfdSessVsiPeerAddr	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.35	hwBfdSessDiscrAuto	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.36	hwBfdSessPeerIpv6Addr	hwBfdSessIndex
1.3.6.1.4.1.2011.5.25.38.2.3.1.38	hwBfdSessIpv6NextHop	hwBfdSessIndex

Impact on the System

Services bound to the BFD session will be adversely affected if the BFD session goes down.

Possible Causes

Cause 1: The interface to which the session is bound went Down.

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

Cause 3: The link went Down or was blocked, which Cause s a forwarding failure.

Procedure

1. Run the display interface command to check whether the physical state of the interface bound to the session is Up.

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

2. Check whether the session state 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 are deleted on the two ends.

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

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

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

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

6. End.