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 OAM protocol packet before the timer expires. Link Fault: indicates that the physical status of this interface goes Down.
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 OAM 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 OAM protocol packet before the timer expired, do as follows:

1. Run the display efm command to check whether EFM OAM is disabled on the peer device.

2. If the peer device is enabled with EFM OAM, 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 OAM protocol packets from being sent to the CPU.

4. If there is a command prohibiting EFM OAM protocol packets from being sent to the CPU, delete this command.

5. If the device is still unable to receive EFM OAM protocol packets, disable the sending of unnecessary protocol packets.