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-316010195 Active/Standby Switchover in the OMMHA System

ALM-316010195 Active/Standby Switchover in the OMMHA System

Description

This alarm is generated when eSight detects that an active/standby switchover has been performed in the OMMHA high availability (HA) system. eSight queries the OMMHA system status every 5 minutes. After the fault is rectified, the system will not automatically clears the alarm. The alarm must be manually cleared.

Attribute

Alarm ID

Alarm Severity

Alarm Type

316010195

Major

Environmental alarm

Impact on the System

The active server is faulty and cannot be used.

Possible Causes

This alarm is generated on the new active server after a switchover is performed due to the following reasons:

  • The link is down because the network configuration changes on the active or standby server or the virtual network of the FusionSphere platform is abnormal.
  • The active server is abnormal.
  • The overall resource status of the active server is worse than that of the standby server.

Procedure

  1. Check whether the communication of the IP address of the two-node cluster is normal.

    # ping -I 10.137.66.167 10.137.66.168

    # ping -I 192.168.66.167 192.168.66.168

    10.137.66.167: local system IP address

    10.137.66.168: remote system IP address

    192.168.66.167: local heartbeat IP address

    192.168.66.168: remote heartbeat IP address

    • If the following information is displayed, the communication is normal. Go to 4.
      64 bytes from 10.137.66.167: icmp_seq=1 ttl=64 time=0.034 ms
    • Otherwise, go to 2.

  2. Check whether the active and standby eSight servers are running properly.

    1. Use PuTTY to log in to any server as the root user. If the following information is displayed, the server is normal:
      eSightServer1:~#

      In the information, eSightServer1 is the host name of the server. Replace it with the actual host name.

    2. Use PuTTY to log in to the other server as the root user. If the following information is displayed, the server is normal:
      eSightServer2:~#

      In the information, eSightServer2 is the host name of the server. Replace it with the actual host name.

    If both servers are normal, go to 4. Otherwise, go to 3.

  3. Wait until the server is started or manually restart the server.

    1. Stop the standby eSight server.
      1. Log in to the standby eSight server as the ossuser user.
      2. 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. Stop the active eSight server.
      1. Log in to the active eSight server as the ossuser user.
      2. 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.
    3. Start the active eSight server.
      1. Log in to the active eSight server as the ossuser user.
      2. 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.
    4. Start the standby eSight server.
      1. Log in to the standby eSight server as the ossuser user.
      2. 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.

    If eSight is started successfully, go to 4. Otherwise, go to 5.

  4. View the status of the OMMHA two-node cluster.

    1. Log in to any eSight server as the ossuser user.
    2. Run the following command to switch to the directory where the status query script is stored:

      > cd /opt/ommha/ha/bin

    3. Query the status of the two servers.

      > sh status.sh

      If the value of HAActive is active, the corresponding node is the active server. If the value of HAActive is standby, the corresponding node is the standby server.
         
       NodeName    HostName        HAVersion    StartTime                   HAActive        HAAllResOK   HARunPhase  
       ha1        eSightServer174  V100R001C01  2017-07-05 14:14:50         active            normal       Actived  
       ha2        eSightServer165  V100R001C01  2017-07-07 10:43:20         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  
       ha1         RMSouthFloatIp  Normal             Normal                Single_active  
       ha2         Database        Standby normal     Normal                Active_standby  
       ha2         NMSServer       Stopped            Unknown               Single_active  
       ha2         RMFloatIp       Stopped            Normal                Single_active  
       ha2         RMSouthFloatIp  Stopped            Normal                Single_active  
      Table 9-257 Normal resource status of the eSight HA system

      Resource Item

      Description

      Node

      Normal Status

      Database

      Database resource status.

      active server

      Active_normal

      standby server

      Standby_normal

      NMSServer

      eSight service resource status.

      active server

      Normal

      standby server

      Stopped

      RMFloatIp

      System floating IP address status.

      active server

      Normal

      standby server

      Stopped

      RMSouthFloatIp

      Southbound floating IP address status.

      NOTE:

      This status is displayed only when the southbound and northbound services are isolated.

      active server

      Normal

      standby server

      Stopped

      If the status is normal, no further action is required. Otherwise, go to 5.

  5. Contact Huawei technical support.

Clearing

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

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24943

Downloads: 74

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