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).
ALM-80006 Veritas Replication Interruption

ALM-80006 Veritas Replication Interruption

Description

The eSight queries the data replication status between the primary and secondary servers every 5 minutes. This alarm is generated when the eSight detects that the data replication between the primary and secondary servers interrupts. This alarm is automatically cleared when the eSight detects that the data replication status between the primary and secondary servers is normal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

80006

Critical

Environmental alarm

Parameters

None.

Impact on the System

When the primary server is faulty, the data is inconsistent between the primary and secondary servers. As a result, the secondary server does not automatically take over the services and the eSight services are unavailable.

Possible Causes

  • The replication network adapters of the primary and secondary servers are faulty.
  • The replication data communication network (DCN) of the primary and secondary servers is interrupted.
  • The replication IP addresses of the primary and secondary servers are unreachable.
  • The application I/O data volume on the primary server increases dramatically. As a result, the replication buffer data overflows.

Procedure

  1. Run the following command on the primary and secondary servers to check whether their replication IP addresses exist:

    # ifconfig -a

    If the displayed information contains an IP address, the replication IP exists. Otherwise, reconfigure the replication IP address. For details, see chapter Installing Veritas and Database Software in the eSight Local High Availability System Software Installation Guide or eSight Remote High Availability System Software Installation Guide.

  2. Check whether the status of the network adapters assigned the replication IP addresses of the primary and secondary servers contains UP and RUNNING, but not DUPLICATED.

  3. Set the status of the network adapter assigned the replication IP address.

    • If the displayed information does not contain UP, run the ifconfig network adapter name up command to make the network adapter in the UP state.
    • If the displayed information does not contain RUNNING, ensure that the network adapter is properly connected.
    • If DUPLICATED is displayed, the IP address may have been used. Reconfigure an IP address.

  4. Run the following command on the primary and secondary servers to check the replication IP addresses:

    # ifconfig -a

  5. Run the following command on the primary and secondary servers to check whether their replication IP addresses are reachable:

    # ping peer replication IP address

    If the ping is successful, the replication IP addresses between the primary and secondary servers are reachable.

  6. On the primary server, run the following command to check whether the replication buffer data overflows:

    # vradmin -g datadg repstatus datarvg | grep "Logging to"

    If the displayed information contains DCM, the replication buffer data overflows.

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

  7. Run the following command to restore the replication:

    # vradmin -g datadg resync datarvg

  8. 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 9.

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

Clearing

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

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24682

Downloads: 74

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