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.


E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
Trap Overview

Trap Overview

Trap Introduction

When faults occur or the system operates abnormally, alarms and events are triggered to help users fast detect and locate faults quickly.

  • Alarm

    When the system operates abnormally, alarms are triggered to inform maintenance personnel the device operating status.

    When a fault occurs, an alarm is triggered and the alarm trap is sent. After the fault is rectified, the alarm status changes from active to cleared and the clear alarm trap is sent. If an alarm trap is generated, a corresponding clear alarm trap will be generated after the fault is rectified.

  • Event

    Events are triggered by specific occurrences, and indicate anything that takes place on a managed object in the system. For example, an object is added, deleted, or modified.

    Certain events will trigger event traps. An event trap does not have a match trap.


By default, alarms and events are defined by the Huawei NMS. Alarms and events may be defined differently on third-party NMSs, but can be redefined as required.

As shown in Figure 4-1, alarm and event traps are stored in the following paths:

  • If an NMS is configured, the system sends the traps to the NMS by the Simple Network Management Protocol (SNMP).
  • The trap buffer size can be determined as required.
  • Device operating information recorded in information files is the same as the information displayed in the buffer area.
  • The information is saved as files on the syslog server for future reference.
Figure 4-1 Input and output of the alarm and event traps

Descriptions of Traps in the Trap Buffer

The output format of a trap on a CLI terminal is as follows:

May 22 2012 17:23:26 HUAWEI %%01STANDARD/5/linkup(t):VS=Admin-VS-CID=0x807a271a- 
OID=;The interface status changes. (ifName=10GE1/17/1, Adm 
inStatus=UP, OperStatus=UP, Reason=Interface physical link is Up.)
Figure 4-2 Output format of traps






Date and time when a trap is output.

Date and time when a trap is output, in the format "mm dd yyyy hh:mm:ss". There is a space between the timestamp and the host name. The format of the trap timestamp is configurable.

  • "mm dd yyyy"stands for the date.
  • "hh:mm:ss" stands for the time, and "hh" (hour) is specified in the 24-hour format.


Host name

The default name is HUAWEI.


Huawei identifier

Indicates that the trap is output by a Huawei device.


Version number

Indicates the version of the trap format.


Module name

Indicates the name of the module by which traps are output.


Trap level

Indicates the severity of a trap.

Trap levels are classified into eight levels. The lower the value of the trap level, the higher the severity is.

  • 0: emergency

    A fatal fault, such as a abnormal program or a memory error, occurs on the device. The system must restart.

  • 1: alert

    A major fault occurs, such as the device memory threshold reaches the upper limit. The fault needs to be rectified immediately.

  • 2: critical

    A critical fault occurs, such as the device memory threshold reaches the lower limit, the temperature reaches the lower limit, the BFD device is unreachable, or an internal fault generated by the device itself. The fault needs to be analyzed and rectified.

  • 3: error

    A fault caused by an incorrect operation or wrong process occurs, such as an incorrect user password or a wrong protocol packet is received from another device. The fault needs to be addressed.

  • 4: warning

    An abnormal situation occurs, such as the user disables the routing process, BFD detects the packet loss, or a wrong protocol packet is received. The fault needs to be addressed.

  • 5: notice

    Indicates the key operations that are used to keep the device functioning properly, such as the shutdown command, neighbor discovery, or the state machine.

  • 6: informational

    Indicates the common operations that are used to keep the device functioning properly, such as the display command.

  • 7: debugging

    Indicates that a routine operation is performed, and no action is required.



Indicates the information type.


Information type

Indicates the trap information.


Virtual system, system component ID, and trap OID.

Indicates the virtual system, system component ID, and trap OID to which a trap belongs.

"X" indicates the virtual system ID.

"ZZZ" indicates the system component ID.

"fff" indicates the trap OID.


Information about details

Indicates the detail information about the system component output. Each time before the trap is output, the module fills up its contents.

Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 210868

Downloads: 1591

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