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-70300 Volume Audit Alarm

ALM-70300 Volume Audit Alarm

Description

This alarm is generated when there are abnormal volumes in the result of a system audit.

Attribute

Alarm ID

Alarm Severity

Auto Clear

70300

Major

Yes

Parameters

Name

Meaning

Fault Location Info

  • servicename: specifies the name of the service for which the alarm is generated.

Additional Info

  • detail_info: provides detailed information about the alarm generated during volume audit.

Impact on the System

  • The volumes in abnormal status exist in the system, which adversely affects volume management.
  • The orphan volume cannot be queried on OpenStack, but occupies the storage backend space.
  • The invalid volume is unavailable in the OpenStack system and occupies system resources.
  • The residual volume occupies the storage space.
  • The stuck volume becomes unavailable in the OpenStack system and occupies system resources.
  • If the volume-VM attachment information is inconsistent, the volume usage is adversely affected.
  • If an orphan volume exists in the cascading system, the volumes in the cascaded systems cannot be managed in the cascading system, which results in a waste of volume resources in the cascaded systems.
  • If an invalid volume exists in the cascading system, the volume obtained using the cinder command does not exist in the cascaded systems.
  • If a volume kept in a transition state exists in the cascading system, the volume is unavailable and occupies system resources in both cascading and cascaded systems.
  • If the volume status recorded in the cascading system is inconsistent with that in the cascaded systems, the internal data in the system is inconsistent and users' operation rights on the volume are restricted.
  • If the volume attachment information recorded in the cascading system is inconsistent with that in the cascaded systems, the volume attachment information resides on the host and users' operations for the volume are adversely affected.
  • If an orphan replication pair exists in the system, the replication pair does not exist in the DRExtend database, and the volumes in the replication pair cannot be used to create replication pairs.
  • If an invalid replication pair exists in the system, residual replication pair records reside in the DRExtend database.
  • If a replication pair is stuck in a transition state, the replication pair becomes unavailable.
  • If the status of a replication pair recorded in the DRExtend database is inconsistent with that in the disk array, the statuses of the primary and secondary replication pairs are inconsistent and the usage of the replication pairs is adversely affected.
  • An orphan remote replication consistency group does not exist in the DRExtend database, and the replication pairs in the group cannot be added to other remote replication consistency groups.
  • If an invalid remote replication consistency group exists in the system, residual remote replication consistency group records reside in the DRExtend database.
  • If a remote replication consistency group stuck in the transition states exists in the system, the remote replication consistency group becomes unavailable.
  • If the state of a remote replication consistency group in the DRExtend database is different from that in the disk array, the statuses of the primary and secondary remote replication consistency groups are inconsistent, adversely affecting the usage of the remote replication consistency group.
  • If the replication pairs of the remote replication consistency group in the database and those in the disk array are different, the usage of the consistency replication group is adversely affected.
  • If an orphan HyperMetro pair exists in the system, the HyperMetro pair does not exist in the DRExtend database, and the volumes in the orphan HyperMetro pair cannot be used to create HyperMetro pairs.
  • If an invalid HyperMetro pair exists in the system, HyperMetro pair records reside in the DRExtend database.
  • If a HyperMetro pair kept stuck in a transition state exists in the system, the HyperMetro pair is unavailable.
  • If a HyperMetro consistency group is orphaned in system, the orphan HyperMetro consistency group does not exist in the DRExtend database, and the HyperMetro pairs in the group cannot be added to other HyperMetro consistency groups.
  • If an invalid HyperMetro consistency group exists in the system, the HyperMetro consistency group records reside in the DRExtend database.
  • If a HyperMetro consistency group kept stuck in a transition state exists in the system, the HyperMetro consistency groups are unavailable.

Possible Causes

  • An orphan volume exists in the system.
  • An invalid volume exists in the system.
  • A residual volume exists in the system.
  • A volume kept stuck in a transition state exists in the system.
  • A volume in abnormal mounting status exists in the system.
  • An orphan volume exists in the cascading system.
  • An invalid volume exists in the cascading system.
  • The volume status recorded in the cascading system is inconsistent with that in the cascaded systems.
  • A volume kept stuck in a transition state exists in the cascading system.
  • The volume attachment information recorded in the cascading system is inconsistent with that in the cascaded systems.
  • An orphan replication pair exists in the system.
  • An invalid replication pair exists in the system.
  • A replication pair stuck in a transition state exists in the system.
  • The status of a replication pair recorded in the DRExtend database is inconsistent with that in the disk array.
  • An orphan remote replication consistency group exists in the system.
  • An invalid remote replication consistency group exists in the system.
  • A remote replication consistency group stuck in the transition states exists in the system.
  • The state of a remote replication consistency group in the DRExtend database is different from that in the disk array.
  • The replication pairs of the remote replication consistency group in the database and those in the disk array are different.
  • An orphan HyperMetro pair exists in the system.
  • An invalid HyperMetro pair exists in the system.
  • A HyperMetro pair kept stuck in a transition state exists in the system.
  • A HyperMetro consistency group is orphaned in system.
  • An invalid HyperMetro consistency group exists in the system.
  • A HyperMetro consistency group kept stuck in a transition state exists in the system.
NOTE:

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

Procedure

NOTE:

If the audit alarm is generated in a cascaded FusionSphere OpenStack system, the alarm must be handled regardless of whether it is also generated in the cascading system. After the alarm is cleared, audit the cascading system (manually or using the automatic routine audit by the cascading system) to ensure data consistency between the cascading and cascaded systems.

  1. Obtain the value of Details in Additional Info in the alarm details and add .csv to the end of the value to generate the audit report name.
  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:
    • Region Type II and Region Type III scenarios:

  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.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45047

Downloads: 33

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