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

Reminder

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

upgrade

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).
EFM/2/CRITICALLINKEVENT

EFM/2/CRITICALLINKEVENT

Message

EFM/2/CRITICALLINKEVENT:The critical link event occurred. (InterfaceName=[InterfaceName], EventType=[EventType], Location=[Location], CpuUsage=[CpuUsage])

Description

A critical link event occurred in the EFM module.

Parameters

Parameter Name Parameter Meaning
InterfaceName Interface name
EventType Event type:
  • Lost Link: indicates that the local device fails to receive an EFM protocol packet before the timer expires.

  • Link Fault: indicates that the physical status of this interface goes Down.

  • Dying Gasp: indicates that the board is reset or the device is restarted.

Location Location (local end or peer end) of the event
CpuUsage Usage of CPU

Possible Causes

Cause 1:

The physical status of the local or remote interface became Down.

Cause 2:

The software of the local or peer device restarted.

Cause 3:

The local device failed to receive an EFM protocol packet before the timer expired.

Procedure

  • If the log was generated because the physical status of an interface became Down, run the undo shutdown command to start the interface.
  • If the log was generated because the software of the local or peer device restarted, check why the device restarts.
  • If the local device failed to receive an EFM protocol packet before the timer expired, do as follows:
    1. Run the display efm command to check whether EFM is disabled on the peer device.
    2. If the peer device is enabled with EFM, run the debugging efm command to enable the debugging function to check whether packets are received.
    3. If no packet is received, check whether the interface is configured with a command that prohibits EFM protocol packets from being sent to the CPU.
    4. If there is a command prohibiting EFM protocol packets from being sent to the CPU, delete this command.
    5. If the device is still unable to receive EFM protocol packets, disable the sending of unnecessary protocol packets.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115443

Downloads: 85

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