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

FusionServer Pro Rack Server iBMC Alarm Handling 30

This document describes iBMC alarms in terms of the meaning, impact on the system, possible causes, and handling suggestions.
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).
Before You Start

Before You Start

Alarm Modes

The iBMC provides the following alarm modes:

  • Alarms by component

    The alarm contains event code + event description. The event description contains information about the faulty component. Users can locate the faulty component based on the alarm.

    Figure 1-1 shows an example of the alarms generated in this mode on the iBMC WebUI.

    Figure 1-1 Alarms by component (WebUI)

    The component-based alarms displayed on the iBMC CLI are similar to the following:
    iBMC:/->ipmcget -d healthevents
    Event Num  | Event Time           | Alarm Level  | Event Code   | Event Description 
    1          | 2016-10-17 06:27:14  | Minor        | 0x01000021   | Failed to obtain data of the CPU 1 DIMM VDDQ2 voltage. 
    2          | 2016-10-17 10:24:43  | Critical     | 0x01000015   |  DIMM020 DIMM  configuration error or training failed. 
    3          | 2016-10-17 10:24:43  | Major        | 0x01000017   |  DIMM012 DIMM  triggered an uncorrectable error, . 
    
  • Alarms by sensor

    The alarm contains sensor name + event description + alarm severity. Users need to locate the faulty component based on the location of the sensor.

    Figure 1-2 shows an example of the alarms generated in this mode on the iBMC WebUI.

    Figure 1-2 Alarms by sensor (WebUI)

    The sensor-based alarms displayed on the iBMC CLI are similar to the following:
    iBMC:/->ipmcget -d healthevents
    Event Num  | Event Time                     | Entity Name          | Sensor Name          | Alarm level  | Event Desc 
    1          | 2013-11-11 Monday 16:53:11     | MainBoard            | HDD Backplane        | Major        | Incorrect cable connected/Incorrect interconnection 
    2          | 2013-11-11 Monday 16:53:12     | MainBoard            | FAN1 F Presence      | Major        | Device Removed / Device Absent 
    3          | 2013-11-11 Monday 16:53:12     | MainBoard            | FAN1 R Presence      | Major        | Device Removed / Device Absent 
    

Version Difference

The alarms provided by the iBMC vary with the iBMC version:

  • RH2288H V3 and RH8100 V3:
    • The iBMC earlier than V222 provides alarms by sensor.
    • The iBMC V222 or later provides alarms by component.
  • RH1288A V2, RH2288A V2, RH1288 V3, RH2288 V3, RH5885 V3, RH5885H V3, 1288H V5, 2288H V5, 2488 V5, 2488H V5, and 5885H V5:
    • The iBMC earlier than V250 provides alarms by sensor.
    • The iBMC V250 or later provides alarms by component.
  • 8100 V5 and 9008 V5:
    • The iBMC earlier than V260 provides alarms by sensor.
    • The iBMC V260 or later provides alarms by component.
Download
Updated: 2019-08-05

Document ID: EDOC1000054724

Views: 328348

Downloads: 3058

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