Known issues
Review the known issues related to the ThinkAgile VX Deployer.
Version 2.1.0
When the deployment of a vSAN cluster is complete, the Download Log button might not work. Instead, click the help icon (i) and then click Download Debug Logs to download the deployment log.
When you initiate a deployment, you might briefly see the message No Data can be found as the deployment begins. This message has no impact on the deployment process.
When specifying a cluster location (6. Cluster location), the Organization Name and Region Name cannot be the same. In addition, the name used for the Organization Name cannot be a previously used Region Name, or vice-versa.
Version 2.0.1
A deployment consists of several steps, which are listed on the Deploy Cluster page. Multiple steps might be running simultaneously. When any of those steps complete, the Elapsed Time is reset to 00:00.
You can use a configuration file to add hosts to an existing cluster. If you choose to do so, the host names for the new hosts will be generated by the Deployer, but they might not be consistent with the other hosts in the cluster. After adding the hosts, make sure that you validate the host names on the Host Settings page. From that page, you can modify the host names if desired.
When attempting to deploy a new vSAN cluster, you can choose to follow the progress of the ESXi deployment by viewing the XCC console. If you chose vSphere 7 as the installation version, during the installation of ESXi on a host, you might see in the XCC console a message erroneously stating that VMware ESXi 7.0.3c is being installed; the VX Deployer will actually install VMware ESXi 7.0.3g.
When adding a node to an existing cluster, the Global ESXi Settings page states that you can specify the ESXi version. However, when you add a node to an existing cluster, the ESXi version to be installed on the node is based on the version of ESXi running on the nodes in the existing cluster. Therefore, you can specify the ESXi credentials, but you do not have the option to specify the ESXi version.
If the VX Deployer VM is shut down during the deployment process, the VM might be left in an indeterminate state. If the VM is inadvertently shut down, you will need to attempt the deployment again to reset the state of the VM. It will not succeed, but the VX Deployer will invoke a cleanup script. Then, you can attempt the deployment again.
On the LXCI Settings page, the XCC Network VLAN ID might be displayed as 1 by default. Make sure that you specify the correct VLAN ID.
On the General Networking page, you can specify a custom subnet mask for each of the networks (ESXi management, vSAN, vMotion, and XCC). The following subnet masks, if specified for a network, will cause issues with the deployment:
255.255.255.254 ( /31 ) – specifies a subnet mask for 0 hosts
255.255.255.252 ( /30 ) – specifies a subnet mask for 2 hosts
The VX Deployer requires that you specify a minimum of 3 hosts for a vSAN cluster.
Version 1.2.1
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.
The fully qualified domain name (FQDN) that you specify for the NTP host name cannot use more than three labels (two dots). If the NTP host name contains more than three labels, specify the IP address instead.
Specifying both primary and secondary DNS servers on the Network Services page will result in an error on the Network Settings per Physical Host page. The workaround is to specify only a primary DNS server (do not specify a secondary DNS server).
Version 1.2.0
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.
The fully qualified domain name (FQDN) that you specify for the NTP host name cannot use more than three labels (two dots). If the NTP host name contains more than three labels, specify the IP address instead.
Specifying both primary and secondary DNS servers on the Network Services page will result in an error on the Network Settings per Physical Host page. The workaround is to specify only a primary DNS server (do not specify a secondary DNS server).
Version 1.1.0
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:
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:
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:
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 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 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
- 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.