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

FAQs of the HA System

This topic describes the common problems related to the HA system.

How to Troubleshoot the Failure to Switch Between the Primary and Secondary Sites Due to Misoperations

Question

The switchover between the primary and secondary server fails due to misoperations (such as making resources go online) on the Veritas. How do I troubleshoot the failure?

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

    # hagrp -flush <service_group_name> -sys <hostname>

  3. Switch over the active and standby servers again.

What Should I Do if datarvg Become Faulty and Cannot Be Brought Online During Force Active?

Symptom

When force active was performed for an HA system in dual-active state, the datarvg resource on the active server became faulty, and the AppService resource group automatically went offline. After the fault was cleared, the datarvg resource failed to go online.

Possible Causes

During force active, the datarvg resource is automatically created for the active and standby servers. The creation will fail when an exception occurs.

Procedure
  1. Log in to the fault node as the root user.
  2. Run the following command to adjust the monitoring parameters of the datarvg resource:

    haconf -makerw

    hatype -modify RVG MonitorInterval 60

    hatype -modify RVG ToleranceLimit 10

    haconf -dump -makero

  3. Run the following command to clear the datarvg fault:

    hares -clear datarvg

  4. Run the following command to check the datarvg status:

    vxprint -g datadg -Vl datarvg

    Information similar to the following is displayed:
    Rvg:      datarvg 
    info:     rid=0.1140 version=0 rvg_version=45 last_tag=2 
    state:    state=ACTIVE kernel=ENABLED 
    assoc:    datavols=lvdbdata,lvfiledata 
              srl=srl 
              rlinks=(none) 
              exports=(none) 
              vsets=(none) 
    att:      rlinks=(none) 
    flags:    closed primary enabled attached logging 
    device:   minor=9003 bdev=199/9003 cdev=199/9003 path=/dev/vx/dsk/datadg/datarvg 
    perms:    user=root group=root mode=0600

    According to the information, the datavols and srl configurations of datarvg are normal. You can bring the datarvg resource and AppService resource group online and continue force active.

    If datarvg is not found or datavols=(none) or srl=(none) is displayed, perform the following steps to restore the datarvg resource:

  5. Create the datarvg resource again.

    1. Run the following commands in sequence to clear the datarvg resource:

      vxrlink -g datadg -f det datarlk

      vxrlink -g datadg -f dis datarlk

      vxvol -g datadg -f dis lvdbdata

      vxvol -g datadg -f dis lvfiledata

      vxvol -g datadg -f dis srl

      vxedit -g datadg -rf rm datarlk

      vxedit -g datadg -rf rm datarvg

    2. Run the following commands in sequence to create the datarvg resource:

      vxmake -g datadg rvg datarvg primary=<true|false>

      vxvol -g datadg aslog datarvg srl

      vxrvg -g datadg start datarvg

      vxvol -g datadg assoc datarvg lvdbdata

      vxvol -g datadg assoc datarvg lvfiledata

      NOTE:

      To restore datarvg on the active server, use primary=true; to restore datarvg on the standby server, use primary=false.

    If an error occurs during the creation of the datarvg resource, contact Huawei technical support.

  6. Check the datarvg status. For details, see What Should I Do if datarvg Become Faulty and Cannot Be Brought Online During Force Active?.
  7. Bring the datarvg resource and AppService resource group online. For details, see Bringing a Resource Online.
  8. Perform force active. For details, see Forcibly Setting the Local Server as the Active Server.
  9. After forcibly making a server become the primary server, run the following command to restore the monitoring parameters of the datarvg resource:

    haconf -makerw

    hatype -modify RVG MonitorInterval 60

    hatype -modify RVG ToleranceLimit 0

    haconf -dump -makero

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24825

Downloads: 74

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