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/BfdSessReachLimitBindIf: 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=[ConfigurationName], InterfaceName=[InterfaceName], SessionLimitPerBoard=[SessionLimitPerBoard])


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.


Parameter Name Parameter Meaning


indicates the configuration name.


indicates the interface name.


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

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

    • If so, go to Step2.
    • If not, go to Step3.

  2. Delete the useless BFD session which bound to this interface, and then the BFD session about committed configuration will be set up. Go to step4.
  3. Collect configurations, trap messages, and log messages, and then contact technical support personnel.
  4. End.
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 170302

Downloads: 110

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next