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-9803 Communication Between OpenStack OM and Internal Components Interrupted

ALM-9803 Communication Between OpenStack OM and Internal Components Interrupted

Description

Service OM checks the system connections to all its internal components. This alarm is generated when the connection to any component is interrupted.

Attribute

Alarm ID

Alarm Severity

Auto Clear

9803

Critical

Yes

Parameters

Name

Meaning

Fault Location Info

Communication Between OpenStack OM and Internal Components Interrupted

Additional Info

  • componentName: The value is fixed at OpenStack OM.
  • connectorType name: specifies the type of the component that fails to be connected, for example, alarm tangram or OpenStack connector fusionsphereplatform.
  • urn/IP: The key of fusionsphereplatform is urn. The other information is IP addresses of the connectors that fail to be connected.

Impact on the System

Most functions provided by Service OM are unavailable, for example, VM creation.

Possible Causes

  • The username or password for logging in to the component is incorrect, or the generated token is invalid.
  • Network connection is interrupted.
  • The management process of the components is terminated or the component database is unavailable for access.
  • An internal exception occurred on the third-party component.

Procedure

Check the component status.

  1. In the alarm list, check whether the alarm was generated 5 minutes ago.

    • If yes, go to 2.
    • If no, wait for 5 minutes and check again.

  2. In the alarm list, check whether the alarm persists.

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

  3. Locate the row that contains the alarm, click the alarm name, view the alarm details in the displayed dialog box, check the alarm component status in the Additional Info area, and perform the required operations:

    • If the alarm is generated for FusionCompute, fc-license, or fm-license, use PuTTY to log in to the Service OM server. (Ensure that username galaxmanager and the management floating IP address are used to establish the connection.)

      Default username: galaxmanager ; default password: IaaS@OS-CLOUD9!

      NOTE:

      Log in to the FusionSphere OpenStack web client. For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode). Choose Cloud Service > FusionSphere OpenStack OM and view VM List to obtain the management floating IP address.

      1. Run the following command and enter the password of user root to switch to user root:

        su - root

        The default password is IaaS@OS-CLOUD8!.

      2. Run the following command to check whether the IP address in the alarm information can be pinged:
        ping Alarm IP address
        • If yes, go to 4.
        • If no, check the network configuration and ensure that the network is normal. Wait for about 5 minutes and check whether the alarm is automatically cleared. If the alarm is automatically cleared, the task is complete. If the alarm persists, go to 4.
    • If the alarm is generated for OpenStack or fusionsphereplatform, use PuTTY to log in to the Service OM server. (Ensure that username galaxmanager and the floating IP address are used to establish the connection.)
      1. Run the following command and enter the password of user root to switch to user root:

        su - root

        The default password is IaaS@OS-CLOUD8!.

      2. Run the following command to check information about Keystone used by Service OM:

        fspops_secu_300029configHosts show | grep identity

        Check whether information about Keystone used by Service OM is the same as that used by FusionSphere OpenStack.
        • If yes, go to 3.b.ii.
        • If no, perform the following steps:
          1. Log in to the FusionSphere OpenStack web client, choose Cloud Service > FusionSphere OpenStack OM, and click Sync Domain. After the synchronization is complete, wait for about 10 minutes and check whether the alarm is automatically cleared.

            If yes, no further action is required.

            If the alarm persists, go to 3.b.ii.

          2. Check whether the password has been changed based on "Account List" in HUAWEI CLOUD Stack 6.5.0 Security Management Guide.

            If yes, go to 3.b.iii.

            If no, contact technical support for assistance.

          3. Check whether some steps are not performed when you change the password by following operations provided in "Resetting Internal Account Passwords (Except Database and rabbit Account Passwords)."

            If some steps are not performed, change the password again by following operations in this section. Wait for about 10 minutes and check whether the alarm is automatically cleared. If yes, no further action is required. If the alarm persists, contact technical support for assistance.

            If no, contact technical support for assistance.

    • If the alarm is generated for tangram, check whether the FusionSphere OpenStack alarm reporting function is configured properly. If the function is not configured properly, modify the configuration. For details, see "Configuring FusionSphere OpenStack Alarm Reporting" in HUAWEI CLOUD Stack 6.5.0 O&M Guide. Wait for about 5 minutes and check whether the alarm is automatically cleared.
      • If yes, no further action is required.
      • If no, perform the following operations:
        1. Check whether the database is faulty by performing operations provided in "Rectifying Database Faults" in HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide.

          If the database is running properly, go to 3.d.

          If exceptions occur on the database, restore the database by following operations in section "Rectifying Database Faults." About 15 minutes later after the database is restored, check whether the alarm is automatically cleared. If yes, no further action is required. If no, go to 3.d.

        2. Use PuTTY to log in to the Service OM server.

          Ensure that the floating IP address and username galaxmanager are used to establish the connection.

        3. Run the following command and enter the password of user root to switch to user root:

          su - root

          The default password is IaaS@OS-CLOUD8!.

        4. Run the following command to check whether an IP address conflict occurs: (In the alarm list, locate the row that contains the alarm, click the alarm name, view the alarm details in the displayed dialog box, and obtain the IP address in the Additional information area.)

          sudo arping -D Alarm IP address -c 5 -I eth1

          If only one response is received, go to 3.e.

          If multiple responses are received, an IP address conflict occurs. Check network configurations to ensure that the network is available. Then, go to 4.

        1. Log in to the FusionSphere OpenStack server and import environment variables. For details, see Importing Environment Variables. Then, run the following command to check the alarm service status:

          cps template-instance-list --service tangram omm-server | grep fault

          If command output contains information, the alarm service is faulty. Perform 3.f to restart the alarm service.

          If the command output does not contain information, the alarm service is normal. Go to 4.

        2. Run the following command to stop the alarm service:

          cps host-template-instance-operate --action stop --service tangram omm-server

          Wait for 30 seconds and start the alarm service.

          cps host-template-instance-operate --action start --service tangram omm-server

          Wait for one minute and check the alarm service status.

          If the alarm service status is normal, wait for five minutes and check whether the alarm is automatically cleared. If yes, no further action is required. If no, go to 4.

          If the alarm service status is abnormal, contact technical support for assistance.

  4. Contact the maintenance personnel to check whether the username and password of the internal components connected to Service OM are modified.

    • If the component login username and password settings on both the component and the FusionSphere OpenStack OM Web Client are different, change the settings on both sides to the same, log in to FusionSphere OpenStack OM again, and then go to 5.
    • If the component login username and password settings on both the component and the FusionSphere OpenStack OM Web Client are the same, go to 6.

  5. Wait for about 5 minutes and check whether the alarm is automatically cleared.

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

  6. Use PuTTY to log in to the Service OM server.

    Ensure that the floating IP address and username galaxmanager are used to establish the connection.

  7. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password is IaaS@OS-CLOUD8!.

  8. Run the following command to check whether the connector process is normal:

    galaxmanager status | grep connector

    • If yes, go to 10.
    • If no, go to 9.

  9. Run the following command to restart the connector process:

    connector restart

  10. Wait for about 5 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35977

Downloads: 31

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