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



LDP/4/LDP_PEER_DOWN:The session went down. (PeerID=[PeerID], HelloSendCount=[HelloSendCount], HelloRecvCount=[HelloRecvCount], LastHelloSendTime=[LastHelloSendTime], LastHelloRecvTime=[LastHelloRecvTime])


The reason of the LDP session Down event and help information were displayed.


Parameter Name Parameter Meaning
PeerID Peer ID
HelloSendCount Number of sent Hello messages
HelloRecvCount Number of received Hello messages
LastHelloSendTime Time when the last Hello message was sent
LastHelloRecvTime Time when the last Hello message was received

Possible Causes

  1. The Hello Hold timer of the LDP session expired.
  2. The Keepalive Hold timer of the LDP session expired.
  3. The reset mpls ldp command was run.
  4. GR was enabled for the LDP session.
  5. The value of the Keepalive Hold timer was changed.
  6. The transport address of the LDP session was changed.
  7. An LSR ID of the LDP session was changed.
  8. A Notification message was received to instruct the local LSR to reestablish the LDP session.
  9. LDP failed to establish an LDP session for a long time.
  10. An incorrect protocol message was received.
  11. An incorrect socket was received.
  12. The LDP session was deleted.
  13. The dynamic LDP advertisement capability configuration was changed.


  1. Collect trap, log, and configuration information, and then Collect log information and configuration information, and then contact technical support personnel..
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 134990

Downloads: 90

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