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

OSN 500 550 580 V100R008C50 Alarms and Performance Events Reference 02

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).
BOOTROM_BAD

BOOTROM_BAD

Description

The BOOTROM_BAD alarm indicates that BOOTROM data check fails. During the running of board software, the system periodically checks whether BOOTROM data is damaged. This alarm is generated when the system detects that BOOTROM data is damaged.

Attribute

Alarm Severity Alarm Type

Major

Environment alarm

Parameters

When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1

Indicates the type of the BIOS damage.

  • 0x01: The basic BIOS is damaged.
  • 0x02: The extended BIOS is damaged.

Parameter 2

The value is always 0xff, and this parameter is meaningless.

Parameter 3

The value is always 0xff, and this parameter is meaningless.

Impact on the System

If the board has started, the BOOTROM_BAD alarm does not have any impact on the system and services.

If you perform a cold reset on the board after the BOOTROM_BAD alarm is generated, loading BIOS to the board fails and the board cannot start.

Possible Causes

Possible causes of this alarm are as follows:

  • The basic BIOS is damaged.
  • The extended BIOS is damaged.
  • The BOOTROM data area is damaged.
  • The system control unit is faulty.

Procedure

  1. View the BOOTROM_BAD alarm on the U2000 to determine the board that reports the alarm.
  2. Replace the board.

    If the board has started, do not replace the board because replacing the board interrupts services but the BOOTROM_BAD alarm does not have any impact on the system and services.

Related Information

None.

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020975

Views: 74803

Downloads: 136

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