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


To have a better experience, please upgrade your IE browser.


eSight V300R010C00 Maintenance Guide 07

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-80004 Veritas in the Healing State

ALM-80004 Veritas in the Healing State


The eSight queries the Veritas cluster status every 5 minutes. This alarm is generated when the eSight detects that the Veritas cluster is in the healing state. This alarm is automatically cleared when the eSight detects that the Veritas cluster is not in the healing state.


Alarm ID

Alarm Severity

Alarm Type



Environmental alarm



Impact on the System

When the primary server is faulty, the secondary server does not automatically take over the services and the eSight services are unavailable.

Possible Causes

  • The data communication network (DCN) between the primary and secondary servers is unstable or the network is interrupted. As a result, the heartbeat and replication between the primary and secondary servers last for more than 10 minutes. The secondary server automatically takes over the services and the two servers work in the dual-active state. After the DCN recovers, the HA system works in the healing state.
  • The primary server does not respond after more than 10 minutes. As a result, the secondary server forcibly takes over the services of the primary server. This alarm is generated after the primary server recovers.


  1. Force either server as the active server.

    1. Stop the database service and the eSight processes.
    2. Log in to the maintenance tool.
    3. Choose HA Management > HA Deployment from the main menu.
    4. Choose Force primary, and click Apply.
      • The server with the latest service data functions as the primary server.
      • Forcibly setting the local server as the active server will overwrite data on the peer server with that on the local server. Excise caution when performing the operation.
    5. Click Yes in the confirmation dialog box that is displayed to forcibly make the server become the primary server.

      If a success message is displayed, the current server becomes the primary server.

    6. Click Close.

  2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.

    • If yes, the alarm handling process is complete.
    • If no, go to Step 3.

  3. Collect the information about alarm handling, and contact the technical support personnel.


When the fault is eliminated, the system will auto-clear the alarm. Manual clearing is not required.

Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25076

Downloads: 74

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