- The following error message is seen when starting a migration job.
Mobility group with id: null does not exist
- As the migration is not even initiated, no job related messages are seen in HCX Manager app.log under /common/logs/admin/app.log
- In web.log under /common/logs/admin/web.log
, migration group ID and migration ID show as null.
2025-01-06 17:54:49.292 UTC [https-jsse-nio-127.0.0.1-8443-exec-3, Ent: HybridityAdmin, , TxId: TxId: ############] INFO c.v.v.h.a.m.c.MobilityGroupUtils- doesAllMigrationsHaveSameSourceAndDestination-intent: class MobilityGroupIntent {
migrationId: null
migrationGroupId: null
operationType: ADD
state: null
migrationType: vSphereReplication
tags: null
entity: class Entity {
entityId: vm-######
entityType: VirtualMachine
entityName: ######
summary: class EntitySummary {
- Curl tests from the HCX manager to connect.hcx.vmware.com are successful
curl -vk https://connect.hcx.vmware.com
- Even though the connection to the activation server is successful, there is a message shown in the HCX UI: 'The HCX service is disconnected. Restore your connection to the HCX service to proceed.'
Prior to HCX 4.11
A proxy server is configured in HCX and it is acting as a Certificate Authority and presenting an invalid certificate to HCX to validate.
Curl output shows certificate information related to the proxy server
Example:
admin@HCXmanager [ ~ ]$ curl -v -k https://connect.hcx.vmware.com
.
* Connected to connect.hcx.vmware.com (142.182.19.19) port 443 (#0)
.
.
* Server certificate:
* subject: C=--; ST=State; L=City; O=Organization; OU=OrganizationalUnit; CN=Domain; emailAddress=Email
* start date: date
* expire date: date
* issuer: C=--; ST=State; L=City; O=Organization; OU=OrganizationalUnit; CN=Domain; emailAddress=Email
* SSL certificate verify result: self-signed certificate (18), continuing anyway.
* using HTTP/1.x
> GET / HTTP/1.1
> Host: connect.hcx.vmware.com
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/1.1 200 OK
.
.
<html>
<Your Proxy Server Response>
</html>
.
.
Note: After upgrading to HCX 4.11, hyperscaler systems become automatically disconnected from VMware activation server "connect.hcx.vmware.com" and system will start operating in the local activation mode.
Edit the HCX proxy settings to add an exclusion for connect.hcx.vmware.com
https://<hcx-manager-ip>:9443
Navigate to Administration --> Proxy --> Proxy Exclusions --> Edit