HCX troubleshooting

Review the following information for common HCX™ issues and fixes.

HCX Client user interface issues

HCX user interface token timeout

Typically, if the VMware Cloud Foundation for Classic - Automated user interface has been opened for some time you might encounter a timeout in the HCX™ user interface, because the login token to the HCX Manager server timed out. Log out of the vSphere web user interface and back in to refresh the token.

HCX Client user interface displaying “NaN” for all metrics on the dashboard screen

This issue is related to the permissions of the currently logged in vCenter account. Ensure that the Enterprise Administrator group is set in the HCX cloud-side appliance manager user interface.

Migration issues

Migration issues in the current versions of HCX are usually in three categories: licensing, cloud gateway networking connectivity, and destination hardware compatibility.

Licensing

If a migration fails because of a licensing issue, current versions of HCX clearly display this issue in the error message with the client web user interface within the vCenter user interface.

Network (WAN) connectivity

If you have any WAN connectivity issues, always check the Interconnect -> HCX Components screen within the HCX user interface for tunnel status. The fleet components typically do not need to be reset or restarted. If WAN connectivity is restored, they reconnect automatically.

If any fixes and updates were applied to the HCX managers (Client and Cloud) and those updates also patch issues with the fleet components, you must redeploy the Cloud Gateway and any L2Cs deployed. You can debug tunnel status further by connecting to HCX Manager through an SSH client such as ccli.

Connect through SSH to HCX Manager by using the admin account and the supplied password.
Run the su – command and enter the root password (same as the admin password) to change to root.
Change the directory to /opt/vmware/bin and run the ./ccli command. If this attempt is not successful because the environment is not set up for root, run the ./ccliSetup.pl command.
Run the list command within the ccli shell to list the fleet components registered with HCX Manager.
Specify the fleet ID for ccli by typing the ID listed for the fleet component. For example, go 8.
Run the debug remoteaccess enable command to connect by using SSH to the wanted fleet component.
Exit ccli and connect by using SSH to the IP address of the SSH-enabled fleet component.
Continue to troubleshoot.
Return to ccli and disable the ssh service for the component.
If necessary, use the hc ccli command to run a health check on the components.

Destination hardware compatibility issues

vMotion migration can be an issue when the client source side is of a newer hardware version and vSphere release than the cloud. Since replication-based migration copies data to a newly built virtual machine (VM) on the destination side, changing the migration type to “Bulk Migration” allows the migration to succeed in most cases.

Stretched L2 Concentrator issues

If the L2C loses connectivity it reconnects automatically after the network connectivity is restored. Use the ccli shell to check health and operation. After SSH is enabled and the L2C is connected, run the ip tunnel and ip link |grep t_ commands to view the status of the tunnels.