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-316010197 File Synchronization Failure in the OMMHA System

ALM-316010197 File Synchronization Failure in the OMMHA System

Description

This alarm is generated when eSight detects that files failed to be synchronized in the OMMHA system. eSight queries the OMMHA system status every 5 minutes. The alarm is triggered when the network is temporarily abnormal. After the network is recovered,no new alarms is generated.After the fault is rectified, the system can automatically clear the alarm.

Attribute

Alarm ID

Alarm Severity

Alarm Type

316010197

Major

Environmental alarm

Impact on the System

If files cannot be synchronized, data may get lost after an active/standby switchover.

Possible Causes

File synchronization fails in the OMMHA system.

Procedure

  1. When an alarm is detected, check whether the network is reachable between the active and standby nodes of the two-node cluster. If no, solve the network problem first.
    1. Log in to the active eSight server as ossuser.
    2. Ensure that the standby server is running properly and the network is reachable. You can use the ping command to connect the IP address of the standby server to the heartbeat IP address.
      ossuser@eSightServer:~> 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@eSightServer:~> 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
  2. Observe for 10 minutes and check whether the alarm is cleared.
    • If yes, the environment has been recovered and no manual rectification is required.
    • If no, the environment is abnormal. Perform the following steps to manually rectify the fault.
  3. Log in to the active eSight server as ossuser, 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 password 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 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 build credit finish is displayed, the password is changed successfully.

  6. Check whether new trust has taken effect.
    1. Access the standby server using the SSH on the active server.

      > ssh Heartbeat IP address of the standby server

    2. Enter the private key password of the key pair.
      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 logged in to the standby server successfully, and mutual trust has taken effect, else contact Huawei technical support.

      Last login: Fri Jun ; 2 17:01:47 2017 from 10.137.97.52   ossuser@eSightServer1:/ossuser>

Clearing

After the fault is rectified, the system can automatically clear the alarm.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24735

Downloads: 74

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