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


To have a better experience, please upgrade your IE browser.


CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

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).
Failure to Query the Address Book Because a Host Is Faulty for a Long Time

Failure to Query the Address Book Because a Host Is Faulty for a Long Time


The address book fails to be queried because a host (a maximum of two USMHTTP VMs are deployed) is faulty for a long time.

Possible Causes

The address book data uses N+1 backup. The address book data is stored on each USMHTTP VM, and each VM stores only part of the address book data. When two USMHTTP VMs are faulty, some address book data may be lost or the cluster status may be abnormal.

Troubleshooting Method

Run the GET LOG: LT=ALL; command to obtain the run logs of all USMHTTP VMs and check whether exception logs exist in RUNLOG\elasticsearch.


  1. Run the DSP MODULE: DEPLOYTYPE=HOST; command to check whether all modules after host replacement are running properly.
  2. After the query result shows that the host status is normal, run STR REDUNDANCE to resynchronize data to the ES.
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 19547

Downloads: 12

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