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 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).
Veritas HA System FAQs

Veritas HA System FAQs

What Can I Do If the Active/Standby Switchover Fails Due to Misoperations

Question

During the switchover between the active and standby servers, if you perform incorrect operations (for example, bringing resources online) on the Veritas, the error message "Unable to switch group AppService. Group is in the middle of a remote operation" is displayed, and the switchover fails.

Answer
  1. Log in to the server as the root user.
  2. Run the following command to clear all previous operations:

    # hagrp -flush AppService -sys $(hostname)

  3. Run the following command to switch over the active and standby servers again:

    # hagrp -switch AppService -any -clus Host name of the standby server -localclus Host name of the active server

What Do I Do When eSight Does Not Receive Alarms from Managed Servers After Remote Two-Node Cluster Switchover

Question

What do I do when eSight does not receive alarms from managed servers after remote two-node cluster switchover?

Answer
  1. Log in to eSight.
  2. Choose Resource > Server > Server Device.
  3. Select a managed server and click in the Operations column.

What Do I Do When Software Sources Do Not Exist for Operating System Deployment Tasks After Two-Node Cluster Switchover

Question

What do I do when software sources do not exist for operating system deployment tasks after two-node cluster switchover?

Answer
  1. Log in to eSight.
  2. Choose Resource > Server > Configuration&Deployment.
  3. Click Software Source Management in the navigation tree on the left.
  4. Click Add and upload an operating system again.
  5. Use the loaded software source to deploy the operating system for the server again.

What Do I Do When the DHCP Server IP Address Range Is Restored to the Default Value After Remote Two-Node Cluster Switchover

Question

What do I do when the DHCP server IP address range is restored to the default value after remote two-node cluster switchover?

Answer
  1. Log in to eSight.
  2. Choose Resource > Server > Service Settings.
  3. Click DHCP Service in the navigation tree on the left.
  4. Set the DHCP server IP address range.
  5. Click Apply.

What Do I Do When the Stateless Computing Device Activation Progress Is Not Updated After Remote Two-Node Cluster Switchover

Question

What do I do when the stateless computing device activation progress is not updated after remote two-node cluster switchover?

Answer
  1. Log in to eSight.
  2. Choose Resource > Server > Stateless Computing.
  3. Choose Domain Management > Domain.
  4. Select a device that is being activated, and click Configuration in the Operation column.
  5. On the Configuration page, remove the device that is being activated, add the device, associate it to a profile, and activate it again.

How Do I Do If eSight Cannot Normally Provide the Location Function After an Active/Standby Switchover in a Remote Two-Node Cluster

Answer

After an active/standby switchover between eSight servers, you need to modify the eSight location template on the AC or AP to change the destination IP address in the template to the heartbeat IP address of the active eSight server. For detailed commands, see the related product documentation.

Failed to Log In to eSight When the NMSServer Resource Is Online

Symptom

Run the hares -state NMSServer -sys $(hostname) command as the root user. The result is online, but eSight cannot be accessed.

Possible Causes

If the eSight process stops unexpectedly, the system automatically restarts the eSight process. In this case, if you run the hares -state NMSServer -sys $(hostname) command as the root user, the result is online.

Procedure
  1. Wait until the system successfully restarts the eSight process.

    • If the restart succeeds, you can log in to eSight of the active server.
    • If the restart fails, a switchover is automatically triggered. Then you can log in to eSight of the standby server.
    NOTE:

    When the eSight process is faulty, the system automatically attempts to restart the process for a maximum of three times.

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.
    NOTE:

    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.
    NOTE:

    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:
    NOTE:

    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>

How Do I Do If Heartbeat IP Connection Between a Remote Server and the Local Two-Node Cluster Is Interrupted

Answer
NOTE:

The following uses bond1 as an example to describe how to check a heartbeat connection.

  1. Log in to the active and standby hosts as the root user and run the following command to check the network cable connection.

    # ethtool bond1

    If the following information is displayed, the cables are correctly connected. If the following information is not displayed, connect the network cables correctly.

    Settings for bond1:  Link detected: yes
  2. Run the following command on the active and standby servers as the root user to check whether the heartbeat network port is enabled:

    # ifconfig | grep bond1

    If no information is displayed, the heartbeat network port is disabled.

    Run the ifconfig bond1 up command. If the following information is displayed, the heartbeat network port is enabled.

     bond1     Link encap:Ethernet  HWaddr A4:DC:BE:1E:5D:F8
  3. Check whether the heartbeat IP addresses of the active and standby hosts are on the same network segment.

    Configure heartbeat IP addresses on the same network segment for the active and standby hosts.

What Can I Do If the VVRService Resource Group of the Veritas HA System Is Faulty and the Replication Enters the passthru State

Question

What can I do if the VVRService resource group of the Veritas HA system is faulty and the replication enters the passthru state?

Symptom
  1. The VVRService resource group is faulty.
  2. When the following command is executed on the active server as the root user to query the RVG resource status, the RVG resource is in the passthru state:

    # vradmin -g datadg repstatus datarvg | grep "RVG state"

    The query result is as follows:

    RVG state:                  enabled for I/O (passthru)

    Or

    RVG state:                  disabled for I/O (passthru)
Prerequisites

The heartbeat IP addresses of the active and standby servers can communicate with each other.

Answer
  1. Log in to the active server as the ossuser user.
  2. Run the following commands:

    > cd /opt/eSight/mttools/tools

    > ./force_primary.sh

  3. If the message "force primary finish." is displayed, the execution is successful and the replication status is restored.
Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25106

Downloads: 74

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