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

BFD_1. hwBfdSessReachLimitBindIf


BFD/4/BFD_IFSESSLMT_TRAP:OID [oid] Try to build session, but the session number in the IO board with interface has reached the limit, the new session binding with interface can not be created. (ConfigurationName=[octet], InterfaceName=[octet], SessionLimitPerBoard=[integer])

The trap was generated when the number of BFD sessions bound to the interface on the interface board reached the PAF upper limit and no more BFD session bound to the interface can be set up. You can run the display bfd statistics command to view the value of BFD_IO_SESSION_NUM corresponding to the upper limit.


Alarm ID Alarm Severity Alarm Type Warning qualityOfServiceAlarm (3)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the configuration name.


Indicates the interface name.


Indicates the allowable maximum number of BFD sessions on each board.

Impact on the System

Services will not be affected.

Possible Causes

New BFD sessions bound to the interface were still set up when the number of BFD sessions bound to the interface have reached the upper limit.


  1. Run the display bfd statistics command to check whether the BFD_IO_SESSION_NUM on the board has reached the upper limit.

    • If so, go to Step 2.
    • If not, go to Step 3.

  2. Run the undo bfd session-name command in the system view to delete the useless BFD session bound to this interface. Then the BFD session about committed configuration will be set up automatically. Go to Step 4.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 74520

Downloads: 47

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next