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-12002 HA Resource Abnormal

ALM-12002 HA Resource Abnormal

Description

This alarm is generated when the high availability (HA) software detects that the WebService floating IP addresses or databases of Manager are abnormal. The HA periodically checks the floating IP addresses and databases.

This alarm is cleared when the HA detects that the floating IP addresses or databases are normal.

Attribute

Alarm ID

Alarm Severity

Auto Clear

12002

Major

Yes

Parameters

Name

Meaning

ServiceName

Identifies the service for which the alarm is generated.

RoleName

Identifies the role for which the alarm is generated.

HostName

Identifies the host for which the alarm is generated.

ResourceName

Identifies the resource name for which the alarm is generated.

Impact on the System

If the WebService floating IP addresses of the Manager are abnormal, users cannot log in to and use FusionInsight Manager. If databases are abnormal, all core services and related service processes, such as alarms and monitoring functions, are affected.

Possible Causes

  • The floating IP address is abnormal.
  • An exception occurs in the database.

Procedure

Check the floating IP address status of the active management node.

  1. Log in to the FusionInsight Manager.

    1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
    2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
    3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
    4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

  2. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and view the alarm host address and resource name in the alarm details.
  3. Log in to the active management node as user root using PuTTY. The password is specified by users before the installation. Obtain it from the system administrator.

    NOTE:

    You can view the IP addresses of the active and standby management nodes on the Host tab page of FusionInsight Manager.

  4. Go to the ${BIGDATA_HOME}/om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP address of the active Manager is normal. View the row where the active Manager ResName is floatip in the command output to check whether the following information is displayed:

    For example:

    10-10-10-160 floatip  Normal  Normal Single_active      
    • If yes, go to 8.
    • If no, go to 5.

  5. Run the ifconfig command to check whether the floating IP NIC exists.

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

  6. Run the ifconfig NIC name floating IP address netmask subnet mask command to reconfigure the floating IP NIC (for example, ifconfig eth0 10.10.10.102 netmask 255.255.255.0).
  7. Wait for 5 minutes. In the alarm list, check whether the alarm is cleared.

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

Check the database status of the active and standby management nodes.

  1. Log in to the active and standby management nodes respectively, run the su - ommdba command to switch to user ommdba, and run the gs_ctl query command to check whether the following information is displayed in the command output.

    Command output on the active management node:

     Ha state: 
            LOCAL_ROLE                    : Primary 
            STATIC_CONNECTIONS            : 1 
            DB_STATE                      : Normal 
            DETAIL_INFORMATION            : user/password invalid 
     Senders info: 
            No information 
     Receiver info: 
            No information     

    Command output on the standby management node:

     Ha state: 
            LOCAL_ROLE                    : Standby 
          STATIC_CONNECTIONS            : 1 
            DB_STATE                      : Normal 
            DETAIL_INFORMATION            : user/password invalid 
     Senders info: 
            No information 
     Receiver info: 
            No information
    • If yes, go to 10.
    • If no, go to 9.

  2. Contact the network administrator to check whether the network is faulty, and rectify the network fault.

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

  3. Wait for 5 minutes. In the alarm list, check whether the alarm is cleared.

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

  4. Log in to the active and standby management nodes, run the su - omm command to switch to user omm, go to the ${BIGDATA_HOME} /om-server/om/sbin/ directory, and run the status-oms.sh script to check whether the floating IP addresses and GaussDB resources of the active and standby Managers are as follows:

    • If yes, find the alarm in the list and manually clear the alarm.
    • If no, go to 12.

Collect fault information.

  1. On the FusionInsight Manager, choose System > Log Download.
  2. Select OmmServer from the Services drop-down list, and click OK.
  3. Set Start time for log collection to 10 minutes ahead of the alarm generation time and End time to 10 minutes behind the alarm generation time, and click Download.
  4. Contact Technical Support and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47700

Downloads: 33

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