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.


HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

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-6030 IP Addresses Conflict

ALM-6030 IP Addresses Conflict


FusionSphere OpenStack periodically (default interval: 60s) detects IP addresses of all hosts. This alarm is generated when an IP address of a host conflicts with that of another host.


Alarm ID

Alarm Severity

Auto Clear







Fault Location Info

Specifies the ID of the host for which the alarm is generated.

Additional Info

  • error_info:
    • ip: specifies the conflicting IP address.
    • port: specifies the conflicting port.
    • mac: specifies the conflicting MAC address.
  • host_id: specifies the ID of the host for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.

Impact on the System

Services using these conflicting IP addresses cannot work properly.

Possible Causes

Multiple sets of controller nodes are deployed in the hypervisor.


  1. Obtain the IDs of the hosts for which the alarm is generated as well as the conflicting IP addresses based on Alarm Object and Additional Info.

    • Make a note of the host IDs and conflicting IP addresses and then go to 2.
    • If this alarm is generated for only one host, go to 12.

  2. Log in to the FusionSphere OpenStack web client.

    For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode).

  3. On the Summary page, obtain the management IP address of the host in the OM IP Address column based on the host ID or host name in the alarm additional information.
  4. Use PuTTY to log in to the host for which the alarm is generated using the management IP address of the host.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

  5. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

  6. Run the following command to disable user logout upon system timeout:


  7. Run the following command to import environment variables:

    source set_env

    Information similar to the following is displayed:

      please choose environment variable which you want to import: 
      (1) openstack environment variable (keystone v3) 
      (2) cps environment variable 
      (3) openstack environment variable legacy (keystone v2) 
      (4) openstack environment variable of cloud_admin (keystone v3) 
      please choose:[1|2|3|4] 

  8. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

    Default account format: DCname_admin; default password: FusionSphere123.

  9. Repeat 2 to 8 to log in to hosts that report the alarm in SSH mode one by one and run the corresponding command based on the IP address type to view all conflicting IP addresses in the current environment. $ipaddress indicates the conflicting IP addresses.

    • For IPv4 address, run the ip addr show | grep 'inet '| grep '$ipaddress/' command.
    • For an IPv6 address, run the ip addr show |grep '$ipaddress' -C 5 command.

    An example command is as follows:

    ip addr show | grep 'inet '| grep ''

    Information similar to the following is displayed:

    inet scope global 
    secondary brcps:novcprox 

  10. Check whether the names of ports that the queried IP addresses correspond to are brcps, brcps:cps-s, brcps:zk-server, or brcps:cbs-s.

    • If yes, go to 11.
    • If no, go to 12.

  11. Check whether all these hosts on which the IP address conflict occurs are located in the AZ. (If you are uncertain about the AZ, contact technical support for assistance.)

    • If yes, go to 12.
    • If no, power off the target host. If the host needs to be added, install it in PXE mode.

  12. Contact technical support for assistance.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37974

Downloads: 31

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