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

EFM_1. hwDot3ahEfmRemoteDyingGaspEvent


EFM/3/DYINGGASP: OID [oid] Remote DyingGasp Event occurred. (IfIndex=[INTEGER], RemoteMacAddress=[OCTET], IfName=[OCTET])

An unrecoverable event occurs, for example, the system or a board restarts, or the device is powered off.


Alarm ID Alarm Severity Alarm Type Minor processingErrorAlarm (4)


Name Meaning


Indicates the MIB object ID of the alarm.


Interface index of the peer device received by the local device


MAC address of the remote device


Interface name of the peer device received by the local device

Impact on the System

Services on the remote device are unavailable.

Possible Causes

Cause 1:

The remote device restarts.

Cause 2:

The board on the remote device restarts.

Cause 3:

The remote device is powered off.


  1. After the remote device or the board on the remote device restarts, run the display efm session command to check whether EFM State is Detect or Discovery.

    • If EFM State is Detect, go to Step 3.
    • If EFM State is Discovery, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 103196

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next