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

FAQs

This section describes common FAQs related to maintenance of the OMMHA HA system and provides reference information.

How Do I Distinguish the Active Server from the Standby One

Question

How do I determine which server is the active one and which server is the standby one?

Answer
  1. Log in to either of the two servers as ossuser.
  2. Run the following commands to check the two-node cluster status:

    > cd /opt/ommha/ha/bin

    > ./status.sh

    HAMode                                                                            
    double                                   
                                             
    NodeName  HostName        HAVersion       StartTime    HAActive        HAAllResOK  HARunPhase          
    ha1       eSightServer40  V100R001C01     2017-09-16   active          normal      Actived             
    ha2       eSightServer46  V100R001C01     2017-09-16   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 

    The status of eSightServer40 is active, indicating that eSightServer40 is the active server, while eSightServer46 is the standby server.

How Do I View the Two-Node Cluster Status

Question

How do I view the running status of the two-node cluster?

Answer
  1. Log in to the server of which the status you want to query as ossuser.
  2. Run the following commands to check the two-node cluster status:

    > cd /opt/ommha/ha/bin

    > ./status.sh

    The normal status is as follows:

    HAMode                                                                            
    double                                   
                                             
    NodeName  HostName        HAVersion       StartTime    HAActive        HAAllResOK  HARunPhase          
    ha1       eSightServer40  V100R001C01     2017-09-16   active          normal      Actived             
    ha2       eSightServer46  V100R001C01     2017-09-16   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  

What Can I Do If a Message Indicating an Invalid License Is Displayed After the Active/Standby Switchover of the OMMHA Two-Node Cluster

Question

A license has been imported to the OMMHA two-node cluster. However, after the active/standby switchover, the license becomes invalid. How can I deal with this problem?

Answer

Re-import the license.

How Do I Solve the Problem that config.sh Fails to Connect the Active and Standby Servers

Question

If the network connection is normal, run the config.sh script to connect the active and standby servers. The active and standby servers fail to be connected. The error information is as follows:

NOTE:

Both IPv4 and IPv6 addresses are supported. The IPv4 address is used as an example in this document.

Can not connect to xx.xx.xx.xx. Quit ...
Answer
  1. Log in to the active and standby servers as the root user.
  2. Modify the /etc/ssh/sshd_conf file to set UseDNS and GSSAPIAuthentication to no.

    UseDNS no
    GSSAPIAuthentication no

  3. Restart the sshd service.

    # service sshd restart

How Do I Do If the ESNs of the Active and Standby VMs Are the Same on the License Page

Symptom

When applying for a license, I find that the ESNs of the active and standby VMs are the same.

Possible Causes

The trust relationship between the two nodes of the two-node cluster is lost.

Procedure
  1. Log in to the active eSight server as the ossuser user.
  2. Ensure that the standby server is running properly and the network is reachable. You can run the ping command to connect to the system IP address and heartbeat IP address of the standby server.
    ossuser@eSightServer1:/ossuser> ping -c 4 10.137.63.225
    PING 10.137.63.225 (10.137.63.225) 56(84) bytes of data.
    64 bytes from 10.137.63.225: icmp_seq=1 ttl=64 time=0.477 ms
    64 bytes from 10.137.63.225: icmp_seq=2 ttl=64 time=0.439 ms
    64 bytes from 10.137.63.225: icmp_seq=3 ttl=64 time=0.437 ms
    64 bytes from 10.137.63.225: icmp_seq=4 ttl=64 time=0.384 ms
    
    --- 10.137.63.225 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.384/0.434/0.477/0.036 ms
    ossuser@eSightServer1:/ossuser> ping -c 4 192.168.122.1
    PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data.
    64 bytes from 192.168.122.1: icmp_seq=1 ttl=64 time=0.018 ms
    64 bytes from 192.168.122.1: icmp_seq=2 ttl=64 time=0.016 ms
    64 bytes from 192.168.122.1: icmp_seq=3 ttl=64 time=0.015 ms
    64 bytes from 192.168.122.1: icmp_seq=4 ttl=64 time=0.014 ms
    
    --- 192.168.122.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2998ms
    rtt min/avg/max/mdev = 0.014/0.015/0.018/0.005 ms
    ossuser@eSightServer1:/ossuser>
  3. Run the following commands to change the private key password of the mutual trust key pair:

    > cd /opt/eSight/mttools/ha/filecopy

    > sh credit.sh

  4. Enter the heartbeat IP address and ossuser user password of the standby server as prompted.
    Please input the IP address for the standby node:
    Please input the standby node password for ossuser:
  5. Enter the private key password of the new key pair as prompted. The new password must contain uppercase letters, lowercase letters, digits, and special characters.
    Please input the password for certificate private key:
    Please input the password again:
    build credit...
    build credit finish.

    If the message "build credit finish" is displayed, the password is changed successfully.

  6. Check whether the new trust relationship takes effect.
    1. Log in to the active server and access the standby server through SSH.

      > ssh Heartbeat IP address of the standby server

    2. Enter the private key password of the key pair as prompted.
      You are trying to access a restricted zone. Only Authorized Users allowed.
      Enter passphrase for key '/ossuser/.ssh/id_rsa': 

      If the following information is displayed, you have successfully logged in to the standby server and the trust relationship takes effect:

      Last login: Fri Jun  2 17:01:47 2017 from 10.137.97.52
      ossuser@eSightServer1:/ossuser>
  7. Stop eSight.

    To stop eSight, you must run the stop command on both the active and standby servers. eSight is successfully stopped only when both the active and standby servers are stopped. The stopping process takes about 5 minutes.

    1. Log in to the standby eSight server as the ossuser user through the system IP address and run the following commands to stop eSight:

      > cd /opt/ommha/ha/bin

      > ./stop.sh

      If the following information is displayed, the standby eSight server is successfully stopped:

      stop HA successfully.
    2. Log in to the active eSight server as the ossuser user through the system IP address and run the following commands to stop eSight:

      > cd /opt/ommha/ha/bin

      > ./stop.sh

      If the following information is displayed, the active eSight server is successfully stopped:

      stop HA successfully.
  8. Start eSight.

    To start eSight, you must run the startup command on both the active and standby servers. eSight is successfully started when both the active and standby servers are started successfully and the eSight two-node cluster resource status is normal. The startup takes about 10 minutes.

    1. Log in to the active eSight server as the ossuser user through the system IP address and run the following commands to start eSight:

      > cd /opt/ommha/ha/bin

      > ./start.sh

      If the following information is displayed, the operation is successful:

      start HA successfully.
    2. Log in to the standby eSight server as the ossuser user through the system IP address and run the following commands to start eSight:

      > cd /opt/ommha/ha/bin

      > ./start.sh

      If the following information is displayed, the operation is successful:

      start HA successfully.
  9. Query the two-node cluster resource status.

    Log in to the active eSight server as the ossuser user through the system IP address and run the following commands to check the two-node cluster resource status:

    > cd /opt/ommha/ha/bin

    > ./status.sh

    If the following information is displayed, the resource status is normal:

    HAMode  
    double  
    
    NodeName   HostName   HAVersion    StartTime            HAActive    HAAllResOK    HARunPhase 
    ha1        Primaster  V100R001C01 2017-02-22 16:44:01    active       normal       Actived 
    ha2        Secmaster  V100R001C01 2017-02-22 16:46:45    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   
Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25099

Downloads: 74

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