No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).



BFD/4/hwBfdSessDown: Session changes to DOWN. (Index=[Index], ConfigurationName=[ConfigurationName], PeerIp=[PeerIp], BindIfIndex=[BindIfIndex], BindIfName=[BindIfName], Diagnosis=[Diagnosis], BindVrfIndex=[BindVrfIndex], BindVpnName=[BindVpnName], SessionType=[SessionType], DefaultIp=[DefaultIp], BindType=[BindType], StaticLspName=[StaticLspName], PwSecondary=[PwSecondary], NextHop=[NextHop], VcId=[VcId], VsiName=[VsiName], VsiPeerAddress=[VsiPeerAddress], DiscrAuto=[DiscrAuto], PeerIpv6=[PeerIpv6], Ipv6NextHop=[Ipv6NextHop])


The BFD session changed from another state to the Down state.


Parameter Name Parameter Meaning


Indicates the ID of the MIB object.


Indicates the index of the BFD session.


Indicates the configuration name of the BFD session.


Indicates the bound destination IP address.


Indicates the index of the bound interface.


Indicates the name of the bound interface.


Indicates information about session diagnostic characters.


Indicates the index of the bound VPN.


Indicates the name of the bound VPN.


Indicates the type of the BFD session.

  • 1: Static, indicates the statically configured BFD session.

  • 2: Dynamic, indicates the dynamic and statically self-negotiated BFD sessions.

  • 3: Entire_Dynamic, indicates that the establishment of a BFD session is triggered entirely dynamically. This type of BFD session is created only after the function of passively creating BFD sessions is enabled on the egress router of the LSP.

  • 4: Static_Auto, indicates the static BFD session that is established with automatically negotiated discriminators.


Indicates the default multicast IP address.


Indicates the binding type.

  • 2 or 3: Peer Ip Address, detects the multi-hop IP link.

  • 1 or 4: Interface, detects the single-hop IP link.

  • 9: LDP_LSP, detects the LDP LSP.

  • 11: TE_LSP, detects the LSP bound to the TE tunnel.

  • 12: TE_TUNNEL, detects the TE tunnel.

  • 13: PW, detects the PW.

  • 15: VSI_PW, detects the VSI PW.


Indicates the name of the static LSP.


Indicates the ID of the secondary PW.


Indicates the IP address of the next hop.


Indicates the ID of the VC.


Indicates the name of the VSI.


Indicates the destination address of the VSI.


Indicates the static auto-negotiation identifier.


Indicates the bound destination IPv6 address.


Indicates the next-hop IPv6 address.

Possible Causes

  1. The session-bound interface goes down.
  2. The peer BFD session is deleted or shut down.
  3. The link went Down or was congested. Consequently, it failed to forward packets.


  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 not, go to Step 6.

  2. Check whether a message reporting alarm recovery is received.

    • If so, go to Step 6.

    • If not, go to Step 3.

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

    • If so, go to Step 6.

    • If not, go to Step 4.

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

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Collect configurations, trap messages, and log messages, and then contact technical support personnel.
  6. End.
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 180994

Downloads: 112

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next