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

HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide 02

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).
LVS Cluster Fault

LVS Cluster Fault

Symptom

The LVS cluster becomes faulty, and services on the data plane are unavailable.

Possible Causes

  • Keepalived processes of the LVS cluster are running improperly.
  • Configuration files are inconsistent between VMs in the LVS cluster.

Procedure

  1. Use PuTTY to log in to the netcluster_elb_lvs_vm_1_01 node.

    The default username is elb and the default password is cnp200@HW.

  2. Run the following command to check whether the Keepalived process is running properly:

    ps -ef|grep keepalived
    • If yes, the command output contains three Keepalived processes. Go to 4.
      -bash-4.1$ ps -ef|grep keepalived
      elb      19782 19741  0 07:46 pts/0    00:00:00 grep keepalived
      root     39607     1  0 Jul29 ?        00:00:00 /usr/local/sbin/keepalived
      root     39610 39607  0 Jul29 ?        00:00:05 /usr/local/sbin/keepalived
      root     39611 39607  0 Jul29 ?        00:00:00 /usr/local/sbin/keepalived
    • If no, the command output does not contain three processes, go to 3.

  3. Run the following command to start the Keepalived process:

    sudo /etc/init.d/keepalived start

  4. Run the following command to check whether the data service of a specified VIP is running properly:

    sudo ipvsadm -Ln -t IP address of the VIP data service:Port number

    • If yes, the command output contains the list of back-end VMs:
      [elb@lvs2 mult_works]#sudo  ipvsadm -Ln -t 117.78.38.81:5001
      Prot LocalAddress:Port Scheduler Flags
      -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
      TCP  117.78.38.81:5001 rr synproxy
      -> 100.64.12.49:5001            FullNat 6      0          0
      -> 100.64.12.50:5001            FullNat 6      0          0
      -> 100.64.12.51:5001            FullNat 6      0          0
    • If no, the command output does not contain the backend VM list.

  5. Log in to the netcluster_elb_lvs_vm_1_02 node and perform 2.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 2022

Downloads: 12

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