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

Alarm Reference

0x3230014 Backup Failed

Description

System configuration data fails to be backed up to an SFTP server.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230014

Warning

Yes

Parameters

Name

Meaning

0

Server IP address

1

System UUID

Impact on the System

System configuration data cannot be automatically backed up.

Possible Causes

  • The network between the management server and the SFTP server is abnormal.
  • The username and password for accessing the SFTP server are incorrectly configured.
  • The user does not have the permission to access the SFTP server.
  • The SFTP server does not have sufficient space remaining for configuration data in the backup system.

Procedure

  1. Use the server IP address displayed in the alarm details to log in to BCManager service management page (login link: https://IP address:9443/, where 9443 is the default port number), choose Settings > Data Maintenance > System Configuration Data, and obtain the SFTP IP address, user name, and port number.
  2. Use PuTTY to log in to the node using the server IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  3. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  4. Based on the SFTP IP address obtained in 1, run the ping SFTP IP address command to check whether the SFTP IP address can be pinged.

    • If yes, go to 5.
    • If no, recover the network connection between the active and standby nodes. Manually perform backup on the System Configuration Data page mentioned in 1. Check whether the alarm is cleared. If yes, no further action is required. If no, go to 5.

  5. Check whether packet loss occurs based on the result in 4.

    • If yes, ask the administrator to improve network performance and quality and ensure stable communication between the BCManager server and the SFTP server, no further action is required.
    • If no, go to 6.

  6. Use the FTP client tool to log in to the SFTP server using the user name and password to check whether the user name and password are correct.

    • If yes, go to 7.
    • If no, reconfigure a user name and password for accessing the SFTP server. For details, refer to the instructions in the System Configuration Data page mentioned in 1. After the configuration is complete, manually perform backup on the System Configuration Data page mentioned in 1. Check whether the alarm is cleared. If yes, no further action is required. If no, go to 7.

  7. Use the FTP client to upload a file and check whether the file is successfully uploaded.

    • If yes, go to 8.
    • If no, log in to the SFTP server and reconfigure the user's read and write permissions as well as system configuration data space. After the configuration is complete, manually perform backup on the System Configuration Data page mentioned in 1. Check whether the alarm is cleared. If yes, no further action is required. If no, go to 8.

  8. Contact technical support engineers.

Related Information

None

0x3230024 Certificate Has Expired

Description

The certificate of the NE (IP address: {0}) has expired.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230024

Warning

Yes

Parameters

Name

Meaning

0

IP address of the NE

Impact on the System

The resources connected to BCManager may be forged.

Possible Causes

  • The certificate has expired.
  • The time on the DR management server and the NE is inconsistent.

Procedure

  1. Check whether the certificate on the NE has expired. For details, see the documents of the NE.

    • If yes, replace the certificate on the NE. If the alarm persists, go to 2.
    • If no, go to 2.

  2. Log in to the DR management server and NE server respectively. Run the date command to query the current time of the servers and compare the time to check whether the time of the DR management server is the same as that of the NE.

    • If yes, go to 3.
    • If no, Synchronize the time on the DR management server and the NE. If the alarm persists, go to 3.

  3. Contact technical support engineers.

Related Information

None

0x3230025 Certificate Verification Failed

Description

The certificate of the NE (IP address: {0}) is not trusted.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230025

Warning

Yes

Parameters

Name

Meaning

0

IP address of the NE

Impact on the System

The resources connected to BCManager may be forged.

Possible Causes

  • The root CA certificate has not been imported.
  • The root CA certificate of the NE's certificate has been changed.

Procedure

  1. Check whether the root CA certificate has been imported.

  2. Check whether the root CA certificate of the NE has been changed.

  3. Contact technical support engineers.

Related Information

None

0x323002C The Placeholder VM Does Not Exist

Description

The placeholder VM for VM (name: {3}) where service instance (name: {2}) resides does not exist.

Attribute

ID

Alarm Level

Automatically Cleared

0x323002C

Major

Yes

Parameters

Name

Meaning

0

Service instance ID

1

VM UUID

2

Service instance name

3

VM name

Impact on the System

The fault recovery or planned migration fails, and the service cannot be restored.

Possible Causes

The placeholder VM is deleted.

Procedure

  1. Check whether the instance needs to be deleted. For details about how to delete an instance, see Cloud Server High Availability (CSHA) > Deleting a Service Instance in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The method of deleting an instance for Cloud Server DR Service (CSDR) is the same. After deleting the instance, check whether the alarm is automatically cleared.

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

  2. Contact technical support engineers.

Related Information

None

0x323002D The Placeholder VM Is Not Configured

Description

The placeholder VM for VM (name: {3}) where service instance (name: {2}) resides is not configured.

Attribute

ID

Alarm Level

Automatically Cleared

0x323002D

Major

Yes

Parameters

Name

Meaning

0

Service instance ID

1

VM UUID

2

Service instance name

3

VM name

Impact on the System

The fault recovery or planned migration fails, and the service cannot be restored.

Possible Causes

None

Procedure

  1. Check whether the instance needs to be deleted. For details about how to delete an instance, see Cloud Server High Availability (CSHA) > Deleting a Service Instance in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The method of deleting an instance for Cloud Server DR Service (CSDR) is the same. After deleting the instance, check whether the alarm is automatically cleared.

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

  2. Contact technical support engineers.

Related Information

None

0x323002F The Consistency Groups Status Is Abnormal

Description

In the service instance (name: {1}), the consistency group (ID: {2}) does not meet status requirements.

Attribute

ID

Alarm Level

Automatically Cleared

0x323002F

Critical

Yes

Parameters

Name

Meaning

0

Service instance ID

1

Service instance name

2

Consistency group ID

Impact on the System

The service instance cannot use the protection, so the data may by inconsistent.

Possible Causes

consistency groups status are in abnormal status.

Procedure

  1. Log in to the ManageOne operation plane and update abnormal service instances. For details, see Volume High Availability (VHA) > Updating Instances in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The method of updating instances for Cloud Server DR Service (CSDR) and Cloud Server High Availability (CSHA) is the same. Check whether the alarm is cleared.

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

  2. Obtain the consistency group ID and contact technical support engineers.

Related Information

None

0x3230030 HA Heartbeat Disconnection

Description

The primary or secondary node has not received heartbeat messages from the peer node during a period (heartbeat interruption period configured by keepalive).

Attribute

ID

Alarm Level

Automatically Cleared

0x3230030

Major

Yes

Parameters

Name

Meaning

0

Local node name

1

Local link IP address

2

Peer node name

Impact on the System

Arbitration may be performed, which may result in a switchover.

Possible Causes

  • The primary or secondary node is abnormal (reset or power-off).
  • Heartbeat links are interrupted due to abnormal network connection.
  • Heartbeat links are interrupted due to network configuration changes.

Procedure

  1. Use PuTTY to log in to the node using the server IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  2. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  3. Then, run the export LD_LIBRARY_PATH=/opt/BCManager/Runtime/ha/libs; cd /opt/BCManager/Runtime/ha/module/hacom/script;sh config_ha.sh -a command to obtain the IP address of the peer BCManager server. In the command output, the second value in the HaArbLK line is the IP address of the peer BCManager server.
  4. Run the ping IP address of the peer BCManager server command if the IP address of the peer BCManager server is an IPv4 address or ping6 IP address of the peer BCManager server if the IP address of the peer BCManager server is an IPv6 address to check whether the peer BCManager server is reachable.

    • If yes, go to 5.
    • If no, restore the network connection between the local and peer BCManager servers. After the network connection is normal, wait for 5 minutes and check whether the alarm is cleared. If yes, no further action is required. If no, go to 5.

  5. Use PuTTY to log in to the local and remote nodes using the IP addresses corresponding to the local and remote fields.

    Default username: DRManager; default password: Huawei@CLOUD8

  6. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  7. Run the cd /opt/BCManager/Runtime/bin;sh showSystemStatus.sh command to check the service status on the local and peer BCManager servers.

    If the value of ResStatus in the command output is not Normal or Active_normal, some services are not running. Go to 8.

    If the value of ResStatus in the command output is Normal or Active_normal, all services are running. Contact technical support engineers.

  8. Wait for 10 minutes and check whether all services are running.

    • If yes, check whether the alarm is cleared. If yes, no further action is required.
    • If no, contact technical support engineers.

Related Information

None

0x3230031 HA Synchronization Failure

Description

Failed to synchronize files from the primary node to the secondary node.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230031

Major

Yes

Parameters

Name

Meaning

0

Primary node

1

Local link IP address

2

Secondary node

Impact on the System

Information about the primary and secondary nodes is inconsistent. After switchover, the configuration file may be abnormal, resulting in HA startup failures.

Possible Causes

  • The secondary node is abnormal (reset or power-off).
  • The file synchronization link is down.
  • The disk space is insufficient.

Procedure

  1. Use PuTTY to log in to the local node using the local link IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  2. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  3. Run the export LD_LIBRARY_PATH=/opt/BCManager/Runtime/ha/libs; cd /opt/BCManager/Runtime/ha/module/hacom/script;sh config_ha.sh -a command to obtain the IP address of the peer BCManager server. In the command output, the second value in the HaArbLK line is the IP address of the peer BCManager server.
  4. Run the ping IP address of the peer BCManager server command if the IP address of the peer BCManager server is an IPv4 address or ping6 IP address of the peer BCManager server if the IP address of the peer BCManager server is an IPv6 address to check whether the peer BCManager server is reachable.

    • If yes, go to 5.
    • If no, restore the network connection between the local and peer BCManager servers. After the network connection is normal, wait for 5 minutes and check whether the alarm is cleared. If yes, no further action is required. If no, go to 5.

  5. Use PuTTY to log in to the local and remote nodes using the IP addresses corresponding to the local and remote fields.

    Default username: DRManager; default password: Huawei@CLOUD8

  6. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  7. Run the cd /opt/BCManager/Runtime/bin;sh showSystemStatus.sh command to check the service status on the local and peer BCManager servers.

    If the value of ResStatus in the command output is not Normal or Active_normal, some services are not running. Go to 8.

    If the value of ResStatus in the command output is Normal or Active_normal, all services are running. Contact technical support engineers.

  8. Wait for 10 minutes and check whether all services are running.

    • If yes, go to 9.
    • If no, contact technical support engineers.

  9. Run the cd /opt/BCManager/Runtime/ha/module/hasync/plugin/conf command on the peer BCManager server to switch to the conf directory. Run the df -h command to check whether the storage space usage of any directory in the hasync_mod.xml file in the conf directory is higher than 95%.

    • If yes, increase the disk space for the directories on the peer BCManager server. After the disk space is increased, wait for 10 minutes and check whether the alarm is cleared. If the alarm persists, go to 10.
    • If no, go to 10.

  10. Contact technical support engineers.

Related Information

None

0x3230033 HA Link Interruption

Description

A link between the primary and secondary node is interrupted.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230033

Major

Yes

Parameters

Name

Meaning

0

Local node name

1

Local link IP address

2

Local link port

3

Peer node name

Impact on the System

The reliability of the synchronization links and arbitration links decreases.

Possible Causes

  • The current link connection is abnormal.
  • The network configurations have been modified.

Procedure

  1. Use PuTTY to log in to the local node using the local link IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  2. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  3. Run the export LD_LIBRARY_PATH=/opt/BCManager/Runtime/ha/libs; cd /opt/BCManager/Runtime/ha/module/hacom/script;sh config_ha.sh -a command to obtain the IP address of the peer BCManager server. In the command output, the second value in the HaArbLK line is the IP address of the peer BCManager server.
  4. Run the ping IP address of the peer BCManager server command if the IP address of the peer BCManager server is an IPv4 address or ping6 IP address of the peer BCManager server if the IP address of the peer BCManager server is an IPv6 address to check whether the peer BCManager server is reachable.

    • If yes, go to 5.
    • If no, restore the network connection between the local and peer BCManager servers. After the network connection is normal, wait for 5 minutes and check whether the alarm is cleared. If yes, no further action is required. If no, go to 5.

  5. Check whether packet loss occurs.

    • If yes,ask the administrator to improve network performance and quality and ensure stable communication between the local and peer BCManager servers, no further action is required.
    • If no, go to 9.

  6. Use PuTTY to log in to the local and remote nodes using the local and remote IP addresses.

    Default username: DRManager; default password: Huawei@CLOUD8

  7. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  8. Run the cd /opt/BCManager/Runtime/bin;sh showSystemStatus.sh command to check the service status on the local and peer BCManager servers.

    If the value of eReplicationServer in the command output is Not Normal, some services are not running. Go to 9.

    If the value of eReplicationServer in the command output is Normal, all services are running. Contact technical support engineers.

  9. Wait for 10 minutes and check whether all services are running.

    • If yes, check whether the alarm is cleared. If yes, no further action is required.
    • If no, contact technical support engineers.

Related Information

None

0x3230034 HA Gateway Inaccessible

Description

A gateway of the primary or secondary node cannot be pinged.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230034

Major

Yes

Parameters

Name

Meaning

0

Local node name

1

Local link IP address

2

Local role

3

Gateway

Impact on the System

The secondary node cannot be switched to be the primary node.

Possible Causes

  • The gateway server is abnormal (reset or power-off).
  • The link is interrupted due to abnormal network connection of the gateway.
  • The link is interrupted due to the gateway's network configuration changes.

Procedure

  1. Check whether gateway server is reset or powered off.

    • If yes, go to 2.
    • If no, go to 3.

  2. If the gateway server is reset, wait until the reset is complete. If the gateway server is powered off, power on it. After the gateway server is started for five minutes, view the real-time alarms to check whether the alarm is cleared.

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

  3. Use PuTTY to log in to operating system of the management server.

    Default username: DRManager; default password: Huawei@CLOUD8

  4. Run the ping command to check whether the network connection between the management server and the NE is normal.

    • If yes, go to 5.
    • If no, restore the network connection. Wait 5 minutes and check whether the alarm is cleared. If yes, no further action is required. If no, go to 5.

  5. Use PuTTY to log in to operating system of the management server.

    Default username: DRManager; default password: Huawei@CLOUD8

  6. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  7. Then run the cd /opt/BCManager/Runtime/bin; sh configSystem.sh -a command to check whether the network connection between the host and the gateway is normal.

    • If yes, go to 8.
    • If no, search in the OceanStor BCManager 6.5.0 eReplication User Guide for the configSystem.sh command and reconfigure networks as instructed. After the configuration is complete, check whether the alarm is cleared. If yes, no further action is required. If no, go to 8.

  8. Contact technical support engineers.

Related Information

None

0x3230036 Arbitration Service Abnormal

Description

The arbitration service is abnormal.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230036

Critical

Yes

Impact on the System

Services may fail to be restored during an exception.

Possible Causes

  • The eReplication arbitration service is improperly configured.
  • The certificate of the quorum server failed to be verified.
  • An internal error occurs to the arbitration service.

Procedure

  1. Search for Third_site_IP_of_Arbitration_Servic, Arbitration_DC1_01_API, Arbitration_DC1_02_API, Arbitration_DC2_01_API, and Arbitration_DC2_02_API in the xxx_export_all_EN.xlsm file exported from HUAWEI CLOUD Stack Deploy to obtain the IP addresses of quorum servers. Search for csha_region_map_info. The value following | is AZ configuration.
  2. Use PuTTY to log in to the local node using the local link IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  3. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  4. Run the cd /opt/BCManager/Runtime/bin && sh configArbitration.sh -a command. Check whether the values of localAZ, PeerAZ, and ArbIP in the command output are the same as those obtained in 1.

    • If yes, go to 5.
    • If no, search for the configArbitration.sh command in the OceanStor BCManager 6.5.0 eReplication User Guide and reconfigure the quorum servers as instructed. Wait for 10 seconds, query the arbitration service, and check whether the alarm is cleared. If the alarm persists, go to 5.

  5. Run the cd /opt/BCManager/Runtime/LegoRuntime/certs;../../jre6.0.18/bin/keytool -list -v -keystore arb.keystore command to check whether the certificate of the quorum server expires. To be specific, check whether the date following until in the Valid from row is earlier than the current date.

    • If yes, obtain the latest quorum server certificate to replace the one that expires. For details, see section Replacing the Quorum Server Certificate in the OceanStor BCManager 6.5.0 eReplication User Guide. Check whether the alarm is cleared. If yes, no further action is required. If no, go to 6.
    • If no, go to 6.

  6. Contact technical support engineers.

Related Information

None

0x3230037 Service Instance Switchover Failure

Description

Service instance (name: {1}) failed in switchover.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230037

Major

Yes

Parameters

Name

Meaning

0

Service instance ID

1

Service instance name

Impact on the System

Services may unable to be correctly recovered.

Possible Causes

None

Procedure

  1. Log in to the ManageOne OM plane using a browser, click eReplication under Quick Links to log in to eReplication.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin, default password: Huawei12#$.

  2. Click Recovery, select a restoration plan based on the service instance name, and rectify the fault based on the failure cause in the Execution Records area. If the alarm persists, go to 3.
  3. Contact technical support engineers.

Related Information

None

0x3230038 Service Instances Reprotection Failure

Description

Failed to reprotect service instance {1}.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230038

Major

Yes

Parameters

Name

Meaning

0

Service instance ID

1

Service instance name

Impact on the System

The service instance may unable to be protected.

Possible Causes

None

Procedure

  1. Log in to the ManageOne OM plane using a browser, click eReplication under Quick Links to log in to eReplication.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin, default password: Huawei12#$.

  2. Click Recovery, select a restoration plan based on the service instance name, and rectify the fault based on the failure cause in the Execution Records area. If the alarm persists, go to 3.
  3. Contact technical support engineers.

Related Information

None

0x323003A VM Does Not Meet Protection Requirements

Description

Service instance (name: {2}) on VM (name: {1}) does not meet protection requirements.

Attribute

ID

Alarm Level

Automatically Cleared

0x323003A

Major

Yes

Parameters

Name

Meaning

0

VM UUID

1

VM name

2

Service instance name

Impact on the System

The VM cannot be protected.

Possible Causes

Storage used by the VM or the VM type does not meet protection requirements.

Procedure

  1. Log in to ManageOne and check whether VMs that do not meet protection requirements exist in the service instance. For details, see Cloud Server High Availability (CSHA) > Viewing ECSs in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The procedure of Querying an ECS or Querying an ECS/BMS for the cloud server DR service is the same.

    • If yes, go to 2.
    • If no, go to 3.

  2. On ManageOne, cancel the VMs that do not meet the protection requirements. For details, see Cloud Server High Availability (CSHA) > Canceling ECS Protection in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I).The procedure of Canceling ECS Protection for the cloud server DR service is the same. Then check whether the alarm is cleared.

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

  3. On ManageOne, add an unprotected VM. For details, see Cloud Server High Availability (CSHA) > Adding an ECS in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I).The procedure of Adding an ECS for the cloud server DR service is the same. Then check whether the alarm is cleared.

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

  4. Contact technical support engineers.

Related Information

None

0x323003B DR Configurations of Unused Volume Resources Not Cleared

Description

The volumes that have been detached from the VM are not deleted from service instance (name: {1}).

Attribute

ID

Alarm Level

Automatically Cleared

0x323003B

Major

Yes

Parameters

Name

Meaning

0

VM UUID

1

Service instance name

2

VM Name

Impact on the System

The system storage resources are wasted.

Possible Causes

Volumes of VMs are detached.

Procedure

  1. Log in to ManageOne and check whether VMs whose EVSs have been detached exist in the service instance. For details, see Volume High Availability (VHA) > Viewing ECSs/BMSs in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The procedure of viewing ECSs/BMSs for the cloud server DR service and cloud server HA service is the same.

    • If yes, Delete the volume resources that are no longer used by the VM by referring to Volume High Availability (VHA) > Canceling EVS Protection of the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The procedure of canceling EVS protection for the cloud server DR service and cloud server HA service is the same.
    • If no, go to 3

  2. Check whether the alarm is cleared.

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

  3. Contact technical support engineers.

Related Information

None

0x323003C Replication Protection Is Not Created for Volumes Used by a VM

Description

Replication protection is not created for volumes used VM (name: {2}) in service instance (name: {1}), so the VM is not under consistency protection.

Attribute

ID

Alarm Level

Automatically Cleared

0x323003C

Critical

Yes

Parameters

Name

Meaning

0

VM UUID

1

Service instance name

2

VM name

Impact on the System

The VM cannot be protected by the consistency group.

Possible Causes

Replication protection is not created for volumes used by the VM.

Procedure

  1. Log in to ManageOne and add unprotected volumes. For details, see Volume High Availability (VHA) > Adding an EVS in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The procedure of adding an EVS for the cloud server DR service and cloud server HA service is the same.
  2. Check whether the alarm is cleared.

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

  3. Contact technical support engineers.

Related Information

None

0x323003D Removal of Protected VMs from Service Instance

Description

DR protection is not created for volumes used on VM (name: {2}) in service instance (name: {1}), so the VM is not under data consistency protection.

Attribute

ID

Alarm Level

Automatically Cleared

0x323003D

Critical

Yes

Parameters

Name

Meaning

0

VM UUID

1

Service instance name

2

VM Name

Impact on the System

The VM is deleted or migrated from the service instance or partially exists in the service instance.

Possible Causes

  • The VM is deleted.
  • The VM is not using the datastore corresponding to service instance.

Procedure

  1. Log in to the ManageOne operation plane and check whether the VM has been deleted. For details, see section Filter and Search in HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I).

    • If yes, manually clear the alarm. If the alarm persists, go to 2.
    • If no, go to 2.

  2. Contact technical support engineers.

Related Information

None

0x323003E Service Instance Not Meet Fault Recovery Requirements

Description

Service instance (name: {1}) does not meet the fault recovery requirements.

Attribute

ID

Alarm Level

Automatically Cleared

0x323003E

Critical

Yes

Parameters

Name

Meaning

0

Service instance UUID

1

Service instance name

Impact on the System

Fault recovery cannot be performed for the service instance.

Possible Causes

  • The VM is deleted.
  • The volume status of the VM in the service instance does not meet the requirements.

Procedure

  1. Check alarms relevant to the service instance, rectify the fault as instructed, and wait for the next fault recovery. If the alarm persists, go to 2.
  2. Contact technical support engineers.

Related Information

None

0x323003F IAM Certificate Update Failure

Description

Failed to update the IAM certificate.

Attribute

ID

Alarm Level

Automatically Cleared

0x323003F

Warning

Yes

Parameters

Name

Meaning

0

IAM IP address or domain name

Impact on the System

The user token may fail in the verification.

Possible Causes

  • The IAM server cannot be connected.
  • The user name or password for IAM interconnection is incorrect.

Procedure

  1. Log in to the ManageOne OM plane using a browser, click eReplication under Quick Links to log in to eReplication.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin, default password: Huawei12#$.

  2. Use PuTTY to log in to the active node based on the server IP address in the browser of 1.

    Default username: DRManager; default password: Huawei@CLOUD8

  3. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  4. Run the ping command to check whether the network between BCManager and the IAM server is normal.

    • If yes, go to 6.
    • If no, rectify the network connection and go to 5.

  5. After the network connection recovers, in the BCManager service management page choose Resource > localServer > FusionSphere. Select OpenStack and click refresh button.Check whether the alarm is cleared.

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

  6. Contact technical support engineers.

Related Information

None

0x3230041 Metering Information Report Failure

Description

Failed to report the metering information.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230041

Warning

Yes

Parameters

Name

Meaning

0

Project ID

1

Name of the instance that fails to be reported. If there are multiple instances, separate them with comma (,).

Impact on the System

The metering information report failure may result in inaccurate metering information about the DR services in the metering system.

Possible Causes

None

Procedure

  1. Log in to the ManageOne OM plane using a browser, click eReplication under Quick Links to log in to eReplication.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin, default password: Huawei12#$.

  2. Choose Resource > localServer > FusionSphere. Select OpenStack, and obtain the metering URL in the Metering column on the Region tab page.
  3. In the xxx_export_all_EN.xlsm file exported from the HUAWEI CLOUD Stack Deploy, search for cascading_region and cascading_domain to obtain the region and domain information, and replace the values in the URL https://metering.{cascading_region}.{cascading_domain}:443. Check whether the URL is the same as that obtained in 2. Alternatively, search for openstack_region and openstack_domain in the xxx_export_all_EN.xlsm file to obtain the region and domain information, and replace the values in the URL https://metering.{openstack_region}.{openstack_domain}:443/. Check whether the URL is the same as that obtained in 2.

    • If yes, go to 6.
    • If no, modify the metering URL using the modification button in the Metering column. If the alarm persists, go to 6.

  4. Use PuTTY to log in to the local node using the local link IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  5. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  6. Run the ping command to check whether the network between BCManager and the metering server (Obtained from the metering URL address in 2) is normal.

    • If yes, go to 7.
    • If no, rectify the network connection and go to 7.

  7. After the network connection recovers, wait for 5 minutes. After the system retries to report metering information, check whether the alarm is cleared.

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

  8. Contact technical support engineers.

Related Information

None

0x3230042 Connecting a Log Server Is Abnormal

Description

Connecting a log server is abnormal.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230042

Critical

Yes

Parameters

Name

Meaning

0

Server IP address

1

Log type

2

Log server IP address or Domain name

3

Port number

Impact on the System

This fault may cause log reporting failures.

Possible Causes

  • The network between BCManager and the log server is abnormal.
  • The log server runs abnormally.

Procedure

  1. Use PuTTY to log in to the local node using the server IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  2. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  3. Run the ping command to check whether the network between BCManager and the log server is normal.

    • If yes, go to 5.
    • If no, rectify the network connection and go to 4.

  4. After the network connection recovers, wait for 5 minutes. After the system retries to report logs, check whether the alarm is cleared.

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

  5. Contact technical support engineers.

Related Information

None

0x3230043 Replication Between The Active And Standby GaussDB Databases In The HA Cluster Is Down

Description

The replication between the active and standby GaussDB databases in the HA cluster is down. Data of the active GaussDB database is not synchronized to the standby one.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230043

Critical

Yes

Impact on the System

Data of the active GaussDB database cannot be synchronized to the standby one, resulting in data inconsistency. Data will be lost after active-standby switchover.

Possible Causes

  • The standby node breaks down.
  • The eReplication service on the standby end suspends.
  • The replication link between the active and standby GaussDB databases is down.

Procedure

  1. Use PuTTY to log in to the node using the server IP address in the alarm details.

    Default username: DRManager; default password: Huawei@CLOUD8

  2. Run the su - root command to switch to user root.

    The default account and password are root and Cloud12#$, respectively.

  3. Run the export LD_LIBRARY_PATH=/opt/BCManager/Runtime/ha/libs; cd /opt/BCManager/Runtime/ha/module/hacom/script;sh config_ha.sh -a command. In the command output, the second value in the HaArbLK line is the IP address of the peer BCManager server.
  4. Run the cd /opt/BCManager/Runtime/bin;sh showSystemStatus.sh command to check the service status on local and peer BCManager servers.

    • If the value of ResStatus in the command output is not Normal or Active_normal, some services are not running. Go to 5.
    • If the value of ResStatus in the command output is Normal or Active_normal, all services are running. Go to 7.

  5. Run the cd /opt/BCManager/Runtime/bin/;sh startSystem.sh command to start the peer BCManager eReplication service. If System started completely. is displayed in the command output, the peer eReplication service is successfully started. Check whether the alarm is cleared.

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

  6. In operating systems of local and peer BCManager servers, run the ping command to check whether the network connection between local and peer BCManager servers is normal.

    • If yes, go to 7.
    • If no, restore the network connection. When the network connection is restored, check whether the alarm is cleared. If the alarm persists, go to 7.

  7. Check whether packet loss occurs based on the result in 6.

    • If yes, ask the administrator to improve network performance and quality and ensure stable communication between the local and peer BCManager servers. No further action is required.
    • If no, go to 8.

  8. Contact technical support engineers.

Related Information

None

0x3230046 VMs Associated with Shared Volumes Are Not in the Same Service Instance

Description

VMs (name: {2}) associated with shared volumes is not in service instance (name: {1}).

Attribute

ID

Alarm Level

Automatically Cleared

0x3230046

Critical

Yes

Parameters

Name

Meaning

0

VM UUID

1

Service instance name

2

VM name

Impact on the System

The VM is not under consistency protection.

Possible Causes

Some VMs associated with shared volumes are not added to the service instance.

Procedure

  1. Log in to the ManageOne operation plane and add an ECS. For details, see Cloud Server DR Service (CSDR) > Adding an ECS in the HUAWEI CLOUD Stack 6.5.0 User Guide (Region Type I). The procedure for adding an ECS for the CSHA service is the same as that for the CSDR service. Check whether the alarm is cleared.

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

  2. Contact technical support engineers.

Related Information

None

0x3230047 Failed To Notify The Order Implementation Result

Description

Notifying the order implementation result fails.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230047

Warning

No

Parameters

Name

Meaning

0

Order ID

1

Notification failure cause

Impact on the System

If notifying the order implementation result fails, the order status in the order system is always in the implementation state, and the quota of a tenant cannot be modified.

Possible Causes

None

Procedure

  1. Rectify the fault based on the notification failure cause, wait for the next order task, and check whether the order implementation result is reported successfully.

    • If yes, manually clear the alarm.
    • If no, go to 2.

  2. Contact technical support engineers.

Related Information

None

0x3230048 Licensed Capacity Has Been Exhausted

Description

Number of protected VHA servers: {0}, CSHA servers: {1}, and CSDR servers: {2} exceed the licensed capacity (number of protected VHA servers{3}, CSHA servers: {4}, and CSDR servers: {5})

Attribute

ID

Alarm Level

Automatically Cleared

0x3230048

Critical

Yes

Parameters

Name

Meaning

0

Number of protected VHA servers

1

Number of protected CSHA servers

2

Number of protected CSDR servers

3

Number of authorized VHA servers

4

Number of authorized CSHA servers

5

Number of authorized CSDR servers

Impact on the System

Only DR protection is supported. Other features, such as DR recovery and DR topology are unavailable.

Possible Causes

None

Procedure

  1. Apply for a capacity expansion project license based on the types of DR services whose capacity exceeds the licensed capacity in Detailed Information. For details, see Applying for a Capacity Expansion Project License in the OceanStor BCManager V200R001C50 eReplication License Application Instructions. Ensure that the upper limit of licensed DR service types in the new license file is greater than the number of licensed DR service types in the original license file.
  2. Import the license file. For details, see Loading a License in the OceanStor BCManager V200R001C50 eReplication License Application Instructions. Then, check whether the alarm is cleared.

    If yes, no further action is required.

    If no, go to 3

  3. Contact technical support engineers.

Related Information

None

0x3230049 90-day Trial Period Expires

Description

90-day trial period expires.

Attribute

ID

Alarm Level

Automatically Cleared

0x3230049

Major

Yes

Impact on the System

  • You can only view, delete, and modify the basic information (name and description) of a DR service instance.
  • The automatic fault recovery and automatic reprotection functions of CSHA are unavailable.

Possible Causes

90-day trial period expires.

Procedure

  1. Apply for a license. For details, see Applying for a Formal Commercial License in the OceanStor BCManager V200R001C50 eReplication License Application Instructions.
  2. Import the license file. For details, see Loading a License in the OceanStor BCManager V200R001C50 eReplication License Application Instructions. Then check whether the alarm is cleared. If the alarm persists, go to 3.
  3. Contact technical support engineers.

Related Information

None

0x323005C Certificate is about to expire

Description

The {1} certificate will expire in {0} days.

Attribute

ID

Alarm Level

Automatically Cleared

0x323005C

Warning

Yes

Parameters

Name

Meaning

0

Days before expiration (31 or 7)

1

Component Name

Impact on the System

After the certificate expires, the certificate may be spoofed by attackers.

Possible Causes

The certificate is about to expire.

Procedure

  1. Replace the certificate. If the component name is eReplication-WebServer, see Replacing the eReplication Certificate (eReplication-WebServer) of DR&Backup Services in the HUAWEI CLOUD Stack 6.5.0 Security Management Guide. For details about other component names, see Replacing a Single or Multiple Certificates at a Time on ManageOne in the HUAWEI CLOUD Stack 6.5.0 Security Management Guide. If the alarm persists, go to 2.
  2. Contact technical support engineers.

Related Information

None

0x323005D Certificate has expired

Description

The {1} certificate has expired for {0} days.

Attribute

ID

Alarm Level

Automatically Cleared

0x323005D

Warning

Yes

Parameters

Name

Meaning

0

Days after expiration

1

Component Name

Impact on the System

The certificate may be spoofed by attackers.

Possible Causes

The certificate has expired.

Procedure

  1. Replace the certificate. If the component name is eReplication-WebServer, see Replacing the eReplication Certificate (eReplication-WebServer) of DR&Backup Services in the HUAWEI CLOUD Stack 6.5.0 Security Management Guide. For details about other component names, see Replacing a Single or Multiple Certificates at a Time on ManageOne in the HUAWEI CLOUD Stack 6.5.0 Security Management Guide. If the alarm persists, go to 2.
  1. Contact technical support engineers.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 46454

Downloads: 33

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