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

eSight V300R010C00 Maintenance Guide 08

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).
Causes of Failover on an HA System

Causes of Failover on an HA System

This topic describes the causes of failover on an HA system. If the primary server does not function properly, services are automatically switched to the secondary server and the secondary server takes over the monitoring and management of networks. This ensures service protection.

Generally, the causes of a failover on an HA system are as follows:
NOTE:

An automatic switching is triggered if the HA system is in the Normal state and one of the following conditions is met. If the HA system is not in the Normal state, an automatic switching is not triggered even if the following conditions are met.

  • Cause 1: A resource in the AppService resource group does not function properly. After the failover is complete, the HA system enters the Fault switching state.
    NOTE:
    • If you manually stop the following resources, the HA system switchover is not triggered.
    • BackupServer is used to monitor the backup database server process. If the backup database server is faulty, the HA system switchover is not triggered.
    Table 3-6 Resources in the AppService resource group

    Resource Name

    Description

    NMSServer

    Used to monitor key eSight processes. If a key eSight process does not function properly, the eSight automatically restart the process for three times. If three attempts fail, a failover occurs on the HA system.

    Netlsnr

    Used to monitor the Oracle database listening process. When the listening process is faulty, a failover occurs on the HA system.

    Oracle

    Used to monitor the Oracle database process. When the Oracle database process is faulty, a failover occurs on the HA system.

    mountDBRes

    Used to monitor disk volume lvdbdata. When disk volume lvdbdata is faulty, a failover occurs on the HA system.

    mountFileRes

    Used to monitor disk volume lvfiledata. When disk volume lvfiledata is faulty, a failover occurs on the HA system.

    RVGPrimary

    Used to monitor the RVG on the local server. If the RVG on the local server does not function properly, a failover occurs on the HA system.

    APPBOND

    Used to monitor the network adapter corresponding to the eSight application IP address. When the network adapter is faulty, a failover occurs on the HA system.

  • Cause 2: The eSight on the primary server abnormally powers off, has a hardware fault, or is broken down. A hardware fault may occur because of disasters such as earthquake, tsunami, or flood. The eSight may be broken down because the operating system is damaged. After the failover is complete, the HA system enters the Fault switching state.
  • Cause 3: The interval for interruption of heartbeat connections between the primary and secondary servers exceeds 600 seconds, the HA system enters the Primary-primary state.
Translation
Download
Updated: 2019-08-03

Document ID: EDOC1100044373

Views: 26603

Downloads: 84

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