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).
Monitoring Active and Standby Servers

Monitoring Active and Standby Servers

This topic describes how to monitor the status of active and standby servers by using the VCS or the commands.

Checking the Data Replication Status

This topic describes how to check the data replication status of the active and standby servers.

Procedure
In the SUSE Linux OS:
  1. Log in to the active server as the root user.
  2. Run the following command to check the data replication status of the active and standby servers.

    # vradmin -g datadg repstatus datarvg

    The following information appears.
    Replicated Data Set: datarvg 
    Primary: 
      Host name:                  10.71.210.78 
      RVG name:                   datarvg 
      DG name:                    datadg 
      RVG state:                  enabled for I/O 
      Data volumes:               4 
      VSets:                      0 
      SRL name:                   lv_srl 
      SRL size:                   3.00 G 
      Total secondaries:          1 
     
    Secondary: 
      Host name:                  10.71.210.76 
      RVG name:                   datarvg 
      DG name:                    datadg 
      Data status:                consistent, up-to-date 
      Replication status:         replicating (connected) 
      Current mode:               asynchronous 
      Logging to:                 SRL 
      Timestamp Information:      behind by 0h 0m 0s
NOTE:
  • If Replication status is displayed as resync in progress (autosync), Data status is displayed as in consistent, and the value of DCM is becoming smaller, data is being duplicated between primary and secondary servers.
  • If Replication status is displayed as replicating (connected) and Data status is displayed as consistent, up-to-date, data duplication of the HA system is complete.
  • If Replication status is displayed as logging to DCM (needs dcm resynchronization), you must run the vradmin -g datadg resync datarvg command on the primary server as the root user to perform manual synchronization.
  • The duration of data replication depends on the stability of the network bandwidth and the volume of the data to be replicated.

Checking the Status of the Active and Standby Servers

This topic describes how to check the status of the all the resource groups on the active and standby servers and the heartbeat status.

Procedure
  1. Log in to the active server as the root user.
  2. Run the following command to check the resource group status on the active server:

    # hagrp -state

    When System is localclus and AppService, ClusterService, and VVRService are ONLINE in the command output, the resource group status on the active server is normal.

    #Group         Attribute             System                        Value
    AppService     State                 SecmasterCluster:Secmaster   |OFFLINE|
    AppService     State                 localclus:Primaster           |ONLINE|
    ClusterService State                 localclus:Primaster           |ONLINE|
    VVRService     State                 localclus:Primaster           |ONLINE|

  3. Run the following command to check the heartbeat status on both active and standby servers:

    # hahb -state

    When the heartbeat status is ALIVE in the command output, the heartbeat packet from the active server to the standby server is normal.

    #HB          Attribute     Scope            Value
    Icmp         State         SecmasterCluster ALIVE

  4. Log in to the standby server as the root user.
  5. Run the following command to check the resource group status on the standby server:

    # hagrp -state

    When System is localclus and AppService, ClusterService, and VVRService are ONLINE in the command output, the resource group status on the standby server is normal.

    #Group         Attribute             System                        Value
    AppService     State                 PrimasterCluster:Primaster   |ONLINE|
    AppService     State                 localclus:Secmaster           |OFFLINE|
    ClusterService State                 localclus:Secmaster           |ONLINE|
    VVRService     State                 localclus:Secmaster           |ONLINE|

  6. Run the following command to check the heartbeat status on both active and standby servers:

    # hahb -state

    When the heartbeat status is ALIVE in the command output, the heartbeat packet from the standby server to the active server is normal.

    #HB          Attribute     Scope            Value
    Icmp         State         PrimasterCluster ALIVE

Viewing the HA System Status Using the Maintenance Tool in Maintenance Scenarios

This topic describes how to view the HA system status using the maintenance tool in maintenance scenarios.

Procedure
  1. Log in to the maintenance tool.
  2. Choose HA Management > HA Deployment from the main menu.
  3. Check the value of Status:.

    NOTE:

    These states are available: Normal status,To-be-recovered dual-active status, Backup-protection-absent status, Single-node status, and Unknown. Unknown: An internal error occurs on the system and the current status of the HA system fails to be obtained. For the descriptions of other states, see HA System Status Overview.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24830

Downloads: 74

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