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).
Verifying the Specification Adjustment

Verifying the Specification Adjustment

After specification adjustment, you need to verify the adjustment effect and ensure that the eSight service is running properly after the VM adjustment.

Verifying the Two-Node Cluster Status

After the VM is started, wait for 5 to 10 minutes (for the operating system and OMMHA to start) and check the two-node cluster status.

Procedure
  1. Log in to the active server as the ossuser user.
  2. Go to the directory where the status query script is stored and query the two-node cluster status.

    > cd /opt/ommha/ha/bin

    > sh status.sh

    HAMode 
    double 
    
    NodeName  HostName        HAVersion    StartTime        HAActive  HAAllResOK   HARunPhase 
    ha1       eSightServer54  V100R001C01  2017-07-18       active    normal       Actived    
    ha2       eSightServer55  V100R001C01  2017-07-18       standby   normal       Deactived  
    
    NodeName ResName    ResStatus       ResHAStatus  ResType          
    ha1      Database   Active_normal   Normal     Active_standby 
    ha1      NMSServer  Normal          Normal     Single_active  
    ha1      RMFloatIp  Normal          Normal     Single_active  
    ha2      Database   Standby_normal  Normal     Active_standby 
    ha2      NMSServer  Stopped         Unknown    Single_active  
    ha2      RMFloatIp  Stopped         Normal     Single_active 
    As shown in the figure, the value of HAActive is active for eSightServer54 and is standby for eSightServer55, indicating that eSightServer54 is the active server and eSightServer55 is the standby server.
    • Expected results
      • On the active server, the values of ResStatus for Database, NMSServer, and RMFloatIp are Active_normal, Normal, and Normal, respectively.
      • On the standby server, the values of ResStatus for Database, NMSServer, and RMFloatIp are Standby_normal, Stopped, and Stopped, respectively.
    • Troubleshooting
      • The monitoring resource items on the standby server cannot be obtained.

        Log in to the FusionSphere OM and choose Resources > Computing Instance to check whether the VM for which the specification is adjusted is started properly.

        • If the VM is not started, the problem may be related to the specification adjustment. Contact Huawei engineers for troubleshooting.
        • If the VM is started properly, the problem is irrelevant to the specification adjustment. Contact Huawei engineers to troubleshoot exceptions of the OMMHA two-node cluster.
      • The resource items on the standby node are abnormal.

        This problem is irrelevant to the VM specification adjustment. Contact Huawei engineers to troubleshoot exceptions of the OMMHA two-node cluster.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24674

Downloads: 74

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