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

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).
Alarm Overview

Alarm Overview

When a fault occurs, the system generates logs and an alarm based on the faulty module. When the universal server manager (USM) is configured, the alarm is reported to the USM over the Simple Network Management Protocol (SNMP). The sensors on the device monitor the operating environment and generate alarms if the environmental conditions do not meet device operating requirements.

Alarm Classification

The E9000 server uses the MM910 to manage all hardware devices in the chassis. The alarms generated for the component are reported to the MM910. You can obtain the alarm information about the components through the Hyper Management Module (HMM) command-line interface (CLI) or web interface (WebUI). The MM910 is also referred to as HMM.

Based on the impact on the system, the hardware alarms of an E9000 server can be classified into the following types:

  • Event alarms

    An event alarm is used to inform users of the occurrence of a key operation. It has no adverse impact on the system operating.

  • Fault alarms

    A fault alarm indicates a fault that may affect system operating. Measures must be taken immediately to rectify the fault.

This document describes the E9000 alarms and how to handle the alarms.

Viewing Alarm Information

You can use any of the following methods to view alarm information:

  • View alarms on the HMM WebUI.
  • View alarms on the HMM CLI.
  • Obtain alarm information from the SNMP trap packets obtained by using the upper-layer gateway software.
    NOTE:

    For details about the operations on the HMM WebUI and CLI, see the MM910 User Guide.

Alarm Severity

The hardware alarms reported by the HMM and baseboard management controller (BMC) of the E9000 and the hardware alarms reported to the network management system (NMS) using SNMP trap are classified into the following types by alarm severity:

  • Info

    This type of alarms does not affect the normal running of the server and does not need to be handled.

  • Minor

    A minor alarm has a minor impact on the system, but you need to take corrective action as soon as possible to prevent a more severe alarm.

  • Major

    A major alarm has a major impact on the system. It affects the normal operating of the system or may cause service interruption.

  • Critical

    A critical alarm may power off the server, and even interrupt system services. You must take corrective action immediately.

The switching system alarms reported to the NMS from switch modules using SNMP trap are classified into the following types by alarm severity:

  • Minor

    A minor alarm has a minor impact on the system, but you need to take corrective action as soon as possible to prevent a more severe alarm.

  • Major

    A major alarm has a major impact on the system. It affects the normal operating of the system or may cause service interruption.

  • Critical

    A critical alarm may power off the server, and even interrupt system services. You must take corrective action immediately.

  • Warning:

    A warning indicates an error that may affect the system performance. The measures to be taken vary depending on the actual situation or the error.

  • Indeterminate

    The impact of an indeterminate alarm varies depending on the actual situation.

  • Cleared

    The cleared severity indicates the clearing of one or more alarms. This alarm clears all alarms for this managed object that have the same Alarm type, Probable cause and Specific problems. Multiple associated notifications may be cleared by using the Correlated notifications parameter.

Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 192442

Downloads: 1565

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