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.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

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_1. hwBfdSessDown

BFD_1. hwBfdSessDown


BFD/2/BFD_DOWN_TRAP:OID [oid] Session changes to DOWN. (Index=[integer], ConfigurationName=[octet], PeerIp=[ipaddr], BindIfIndex=[integer], BindIfName=[octet], Diagnosis=[integer], BindVrfIndex=[integer], BindVpnName=[octet], SessionType=[integer], DefaultIp=[integer], BindType=[integer], StaticLspName=[octet], PwSecondary=[integer], NextHop=[ipaddr], VcId=[integer], VsiName=[octet], VsiPeerAddress=[ipaddr], DiscrAuto=[integer], PeerIpv6=[ipv6addr], Ipv6NextHop=[ipv6addr])

The trap was generated when the BFD session changed from another state to the Down state.

The statuses of the BFD session include: Up, Init, Down, and AdmDown.


Alarm ID Alarm Severity Alarm Type Major qualityOfServiceAlarm(3)


Name Meaning
oid Indicates the MIB object ID of the alarm.
Index Indicates the index of the BFD session.
ConfigurationName Indicates the configuration name of the BFD session.
PeerIP Indicates the bound destination IP address.
BindIfIndex Indicates the index of the bound interface.
BindIfName Indicates the name of the bound interface.
Diagnosis Indicates information about session diagnostic characters.
BindVrfIndex Indicates the index of the bound VPN.
BindVpnName Indicates the name of the bound VPN.
SessionType Indicates the type of the BFD session.
  • 1: Static, indicates the statically configured BFD session.

  • 2: Dynamic, indicates the dynamically established BFD session.

  • 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.

DefaultIP Indicates the default multicast IP address.
BindType Indicates the binding type.
  • 1: interfaceIp, detects the Interface, and peer IP address, the single hop IP link.
  • 2: peerIp, detects the peer IP, the multi-hop IP link.
  • 3: sourceIp, detects the peer IP source address.
  • 4: ifAndSourceIp, detects the Interface, peer IP and source IP address.
  • 7: ospf, detects the OSPF.
  • 8: isis, detects the ISIS.
  • 9: ldpLsp, detects the LDP LSP.
  • 10: staticLsp, detects the static LSP.
  • 11: teLsp, detects the LSP bound to the TE tunnel.
  • 12: teTunnel, detects the TE tunnel.
  • 13: pw, detects the PW.
  • 15: vsiPw, detects the VSI PW.
  • 21: ldpTunnel, detects the LDP tunnel.
  • 22: bgpTunnel, detects BGP tunnel.
StaticLspName Indicates the name of the static LSP.
PwSecondary Indicates the ID of the secondary PW.
NextHop Indicates the IP address of the next hop.
VcId Indicates the ID of the VC.
VsiName Indicates the name of the VSI.
VsiPeerAddress Indicates the destination address of the VSI.
DiscrAuto Indicates the static auto-negotiation identifier.
PeerIpv6 Indicates the bound destination IPv6 address.
Ipv6NextHop Indicates the next-hop IPv6 address.

Impact on the System

If the alarm function is enabled and a large number of BFD sessions flap, more CPU resources are consumed. Except for this, no service will be affected.

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, 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 alarm information and configuration information, and then contact technical support personnel.
  6. End.
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 107660

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next