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.


Configuration Guide - Device Management

CloudEngine 12800 and 12800E V200R003C00

This document describes the configurations of Device Management, including device status query, hardware management, Information Center Configuration, NTP, Synchronous Ethernet Configuration, Fault Management Configuration, Energy-Saving Management Configuration, Performance Management Configuration, Maintenance Assistant Configuration, and OPS Configuration.

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).
Setting the Alarm Severity

Setting the Alarm Severity


The system defines default alarm severity for each alarm. Users can change the alarm severity. When receiving alarms reported by a device, the NMS can configure filtering rules to display only alarms of a specified severity.

Alarm severities are defined as follows:
  • Critical: indicates that a fault affecting services has occurred and it must be rectified immediately. For example, a critical alarm is generated to notify users that a managed object fails to work and the fault must be rectified.

  • Major: indicates that services are being affected and related measures need to be taken urgently. For example, a major alarm is generated to notify users that performance of a managed object seriously degrades and all the capabilities of the managed object must be restored.

  • Minor: indicates that a fault occurs but does not affect services. To avoid a minor alarm from getting more severe, related measures must be immediately taken.

  • Warning: indicates that a potential or impending service-affecting fault is detected before any significant effect has been felt. Take corrective actions to diagnose and rectify the fault.

Alarms of different severities correspond to different trap severities in the information center, as shown in Table 6-3.
Table 6-3 Mapping between alarm severity and trap severity

Alarm Severity

Corresponding Trap Severity










  1. Run system-view

    The system view is displayed.

  2. Run alarm

    The alarm view is displayed.

  3. (Optional) Run display alarm information [ name alarm-name ]

    The alarm severity is displayed.

  4. Run alarm alarm-name severity severity [ instance instance-name ]

    The alarm severity is changed.

    The system has defined default alarm severity for each alarm.

  5. Run commit

    The configuration is committed.

Updated: 2019-05-05

Document ID: EDOC1100004193

Views: 71008

Downloads: 26

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next