Description

FusionSphere OpenStack fails to connect to the VMware vCenter server.

Attribute

Parameters

Impact on the System

The service functions of the VM network may be affected when the system connects to the VMware vSphere hypervisor.

Possible Causes

• The external switches face the problems of high packet loss rate or long delay for data forwarding.
• The bandwidth of the host NIC or switch is insufficient.
• The NIC is faulty.
• VMware vCenter fails to run properly.
• The password for logging in to VMware vCenter is incorrect.

Procedure

1. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

   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.

   NOTE:

   To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:

   • Region Type I scenario:

     Cascading system: Cascading-ExternalOM-Reverse-Proxy

     Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

   • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

2. 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!.

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

   TMOUT=0

4. Import environment variables. For details, see Importing Environment Variables.
5. Run the following command to check whether the Neutron service is used to connect vCenter:

   openstack service list | grep neutron

   Check whether a command output is returned.

   • If yes, go to 6.
   • If no, go to 10.

6. Check whether the network connection between FusionSphere OpenStack and vCenter is normal.
   • If yes, go to 7.
   • If no, check whether the physical network is connected and correctly configured. If the physical network is correctly configured, go to 12.
   NOTE:

   vCenter and FusionSphere OpenStack hosts are connected through the External OM plane. Ensure that the switch VLAN has been correctly configured, and the host can be connected to the vCenter through the external_om network.

7. On the FusionSphere OpenStack web client, choose Configuration > Manage Resource Pool.
8. In the Resource Pool area, click in the VMware resource pool and check whether the connection parameters of vCenter are correct.

   The following figure shows parameters.

   Figure 3-13 Parameters configuration
   

9. After ensuring that the parameters are correct, click Submit.

   After performing this operation, go to 12.

10. Check whether the physical network is connected and correctly configured. After confirming that the configuration is correct, run the cd /home/install_vmware command to switch to the directory.
11. Run the sh install_FSP.sh set_vcenter_alarm command to modify the information required for connecting vCenter to FusionSphere OpenStack.

    Enter the correct IP address, username, and password as prompted in the command.

12. Wait for a few minutes and check whether the alarm is cleared on the Service OM alarm page.
    • If yes, no further action is required.
    • If no, go to 13.

13. Contact technical support for assistance.

Related Information

None