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-9801 OpenStack OM Resource Status Abnormal

ALM-9801 OpenStack OM Resource Status Abnormal

Description

The system checks the resource status of Service OM every 20 seconds. This alarm is generated when the system detects that the resource status is abnormal for three consecutive times.

Attribute

Alarm ID

Alarm Severity

Auto Clear

9801

Major

Yes

Parameters

Name

Meaning

Fault Location Info

Name: The value is fixed at OpenStack OM.

IP Address: specifies the fixed IP address of the VM where the abnormal resource is located.

Additional Info

Component type: The value is fixed at OpenStack OM.

Resource name: specifies the name of the abnormal resource.

Node name: specifies the name of the VM where the abnormal resource is located.

Impact on the System

The impact of abnormal resources varies with resources. The additional information contains the names of abnormal resources. Table 3-9 lists the impact of each abnormal resource.

Table 3-9 Impact of abnormal resources

Resource Name

Impact

irm

The system cannot manage resources.

uportal

User cannot log in to Service OM. All the operation interfaces become abnormal.

Northbound interfaces become unavailable.

primarydb

All the operations performed on Service OM may not take effect immediately.

csm

The modules using Remote Procedure Call Protocol (RPC) will be affected, such as irm and connector.

The following functions are unavailable, such as software commissioning, license management, and time management. The automatic backup in the background fails.

uhm

The resource management operations relevant to hardware become unavailable.

exfloatip

All the operations on the Service OM node become unavailable.

omfloatip

The Simple Network Management Protocol (SNMP) alarms cannot be provided.

standbydb

All the operations on the web client of Service OM cannot be synchronized to the standby node. When the active Service OM node is powered off, data in it may lose.

arcontrol

The resource management functions of Service OM are not available.

ardata

The report and monitoring modules become unavailable.

nginx

The entire system will become faulty.

connector

The resource pool management functions of Service OM are unavailable.

orchestrator

Some resources of are unavailable.

fault

The alarm function is unavailable.

HA

The database and file system on the active and standby Service OM nodes cannot be synchronized.

When the active Service OM node is faulty, the system cannot switch to the standby node.

Possible Causes

This alarm is generated when a resource fails to be restarted for three consecutive times after it is detected as an abnormal resource.

Procedure

Check the resource status in the system.

  1. In the alarm list, click the row that the alarm locates. In the Additional information displayed in the Alarm Details area, view the following information:

    • The name of the resource for which the alarm is generated, for example, connector.
    • The name of the node for which the alarm is generated, for example, allinonefm0.

  2. Use PuTTY to log in to the active Service OM node using the management floating IP address as user galaxmanager.

    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.

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  4. Run the following command to obtain the names and IP addresses of the active and standby nodes:

    QueryHaState om

    In this example command output, the current node is the standby node, whose name is allinonefm0 and management IP address is 192.168.61.138 and the peer node is the active node, whose name is allinonefm1 and management IP address is 192.168.61.165.

    LOCAL_HOST=allinonefm0
    LOCAL_STATE=standby
    LOCAL_IP=192.168.61.138
    
    REMOTE_HOST=allinonefm1
    REMOTE_STATE=active
    REMOTE_IP=192.168.61.165

  5. Check whether the resource name is standbydb.

    • If yes, go to 6.
    • If no, go to 11.

  6. Check whether the name of the node for which the alarm is generated is the name of the standby node.

    • If yes, go to 7.
    • If no, go to 16.

  7. Use PuTTY to log in to the standby Service OM node.

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

  8. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  9. Run the following command to enable the HA function:

    haStartAll -r

  10. After 15 minutes, check whether the alarm is cleared.

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

  11. Check whether the name of the node for which the alarm is generated is the name of the active node.

    • If yes, go to 12.
    • If no, go to 16.

  12. Use PuTTY to log in to the active Service OM node.

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

  13. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  14. Run the following command to enable the HA function:

    haStartAll -r

  15. After 15 minutes, check whether the alarm is cleared.

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

  16. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45667

Downloads: 33

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