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

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

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).
ALM-1126002 Abnormal Bare Metal Server in Auditing

ALM-1126002 Abnormal Bare Metal Server in Auditing

Description

This alarm is generated when there are bare metal server instances in abnormal status in the result of a system audit. The alarm is cleared when there are no abnormal bare metal server instances in the audit result.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1126002

Major

Yes

Parameters

Name

Meaning

Fault Location Info

Service: specifies the name of the service for which the alarm is generated. The default value is BMS.

Additional Info

  • Service: specifies the name of the service for which the alarm is generated. The default value is BMS.
  • MicroService: specifies the name of the microservice for which the alarm is generated. The default value is ironic.
  • DetailInfo: specifies the details about the alarms generated by the bare metal server audit

Impact on the System

The abnormal bare metal server cannot be managed by the system.

Possible Causes

  • An orphan physical server exists.
  • An invalid physical server exists.
  • There are physical servers that cannot be used.
  • A stuck physical server exists.
    NOTE:

    Obtain the audit issue that caused the alarm from the alarm details and handle the issue according to the following procedure.

Procedure

  1. Obtain the value of detail_info in Additional Info in the alarm details and the name of the corresponding audit report based on Table 3-5.

    Table 3-5 Mapping between detailed information and audit reports

    Detail Information

    Audit Report

    invalid_ironic_instances

    invalid_ironic_instances.csv

    invalid_ironic_nodes

    invalid_ironic_nodes.csv

    stucking_ironic_instances

    stucking_ironic_instances.csv

  2. Determine the deployment scenario of the current environment. Obtain the audit report.

  3. Obtain "Analyzing Audit Results" based on the scenario where the current environment is deployed.Identify the handling method based on the audit report name and handle the audit items.

  4. Determine the scenario where the current environment is deployed and obtain section "Manual Audit." Start the system audit again.

    • Region Type I scenario:

      For KVM virtualization (cascaded system), see Manual Audit.

    • Region Type II and Region Type III:

      For KVM virtualization, see Manual Audit.

  5. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 6.

  6. Contact technical support for assistance.
Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47788

Downloads: 33

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