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 V300R010C00SPC200, 300, and 500 Local HA System Software Installation Guide (SUSE Linux + Oracle + Veritas) 10

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).
Why Is the Veritas HA System Not Automatically Switched Over After the Management Port Is Forcibly Powered Off

Why Is the Veritas HA System Not Automatically Switched Over After the Management Port Is Forcibly Powered Off

Question

Why is the Veritas HA system not automatically switched over after the management port is forcibly powered off?

Answer

The implementation mode of the management port software varies depending on the server. Whether active/standby switchover is triggered for a server when the server is forcibly powered off depends on whether the server operating system sends the normal shutdown signal. If the server operating system does not send a normal shutdown signal, active/standby switchover is triggered. If the server operating system sends a normal shutdown signal, active/standby switchover is not triggered.

  • To verify the automatic switchover capability in the case of abnormal power-off of the active server, use the following methods to solve the problem:
    Method 1: Manually remove the power supply cable of the active server.

    Software and hardware may be damaged when the power supply cable is forcibly removed. Therefore, method 1 is not recommended.

    Method 2: Disable the heartbeat network adapter on the active server.

    In a local HA environment where this scenario is simulated, the standby server automatically switches over. However, the floating IP address of the active server still exists. As a result, the standby server cannot be started.

    The active and standby servers communicate with each other through the heartbeat network. If the heartbeat network adapter on the active server is disabled, the standby server cannot detect the status of the active server. In this case, you can simulate the abnormal power failure of the active server.

    1. Log in to the active server as the root user, and run the following command:

      # ifdown bond1

    2. (Optional) Run the following command to enable the heartbeat network adapter after the verification:

      # ifup bond1

  • To start the standby server, run the following command as the root user:

    After the standby server is started, the HA system works in active-active mode.

    # hagrp -online -force AppService -sys <Host name of the standby server>

Translation
Download
Updated: 2019-10-30

Document ID: EDOC1100044372

Views: 30206

Downloads: 26

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