Known issues

Review the known issues related to the ThinkAgile VX Deployer.

Version 1.2.0

The ThinkAgile VX Deployer, Version 1.2.0, has the following known issues:
  • When configuring the VX Deployer, the XCC IP addresses and the ESXi Management IP addresses must be on different subnets. The deployment will not work if they are on the same subnet; intermittent failures can occur during ESXi deployment.

  • If you attempt to move from the Review page back to an earlier page in the VX Deployer using the left navigation pane, it is possible that the Next button will no longer be available (it will be greyed out). At that point, the workaround is to stop and restart the VX Deployer virtual machine.

Version 1.1.0

The ThinkAgile VX Deployer, Version 1.1.0, has the following known issues:
  • When adding nodes to an existing vSAN cluster, LXCI will not automatically discover and manage those nodes. You will need to manually discover the nodes through vCenter to add them to LXCI. For information about discovering nodes and adding them to LXCI, see the following topic:

    Configuring LXCI

    In addition, you will need to upgrade LXCI to version 7.4 if you vSAN cluster contains any of the following systems:
    • ThinkAgile VX2375 IS

    • ThinkAgile VX3375 IS

    • ThinkAgile VX7375-N IS

    For more information about upgrading LXCI, see the following topic:

    Upgrading LXCI

  • To utilize the full functionality of vLCM, you must enable the VMware Customer Experience Improvement Program (CEIP) in the vSphere client. For information about enabling CEIP, see the following topic:

    https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-F97CD334-CD4A-4592-B7B1-43A49CF74F39.html

  • If you have used the VX Deployer to deploy a vSAN cluster and you are using a shared VLAN for VSAN traffic, attempting to use the VX Deployer to deploy a second vSAN cluster will not succeed. To resolve this issue, choose one of these options:

    • Update the VLAN IP addresses in the existing VSAN cluster to use a different range.

    • Implement a separate VLAN for vSAN traffic on the new vSAN cluster being deployed.

  • When adding a new vSAN cluster to an existing vCenter instance, you are required to choose a name for the cluster that is unique within the datacenter. If you specify a cluster name that already exists, the Deployer will not generate an error message. However, the deployment will not be successful.

  • You must wait for a deployment to complete before attempting to deploy another vSAN cluster using the VX Deployer. If you attempt to start a new deployment while another deployment is running, the new deployment will stop immediately.

  • When configuring the VX Deployer, the XCC IP addresses and the EXCi Management IP addresses must be on different subnets. The deployment will not work if they are on the same subnet; intermittent failures can occur during ESXi deployment.

  • If ESXi host names are entered in mixed case or uppercase, the deployment will fail, even if the DNS entries are entered in mixed case or uppercase. Host names must be entered in lowercase to meet VMware requirements.

  • When adding nodes to an existing cluster, the General Networking page indicates that the vMotion and vSAN fields are optional, but that is not necessarily true. If you are using the ESXi management network for vMotion and vSAN traffic, you do not need to add a gateway address. However, if the vMotion and vSAN traffic travel over a separate VMK adapter, you must provide a gateway address.

  • On the Network Settings Per Physical Host page, IP addresses for discovered hosts might not display correctly, but a message is displayed indicating that the ESXi host names were validated successfully. In this case, you can continue with the deployment.

  • The boot script for configuring the networking within the VX Deployer will not work properly in the web console of the vSphere client. Use the VMware Remote Console or ESXi Console to configure networking for the Deployer VM at boot time.

  • Intermittent DNS resolution issues have been encountered which cause the 'Install ESXi on hosts' step to fail with one or more nodes not becoming available after installation. Networking connection failures are reported in the /var/log/weasel.log on the ESXi host. If you encounter this situation, restart the VX Deployer and attempt deployment again.

Version 1.0.0

The ThinkAgile VX Deployer, Version 1.0.0, has the following known issues:
  • Certain special characters cannot be used in XCC, vCenter, ESXi, or LXCI passwords. These special characters include:
    • Backslash

    • Single quotes

    • Double quotes

  • Occasionally, changing the XCC password might not work, even if the password is a valid password. The work around for this issue is to ensure that the password is valid and attempt to change it again.