occur error while service mesh deployment: repareFleetPools Failed. Reason: Interconnect Service Workflow PrepareFleetNetwork failed. Error: ["Unable to fetch NSX-T Transport Zone from Configured Compute in Compute Profile."]
HCX Cloud site components version information:
vc6.7 16046713
esxi6.7 15160138
nsxt3.0 15946738
hcx cloud R140:3.5.3.16246360
HCX Enterprise site components version information:
vc6.7 15129973
esxi6.7 15160138
nsxv 6.4.6.14819921
hcx connector R140:3.5.3.16246370
Have you defined a transport zone in NSX-T? Have you prepared the clusters for NSX-T?
I have not used HCX with NSX-T yet, but I did see a similar error with NSX-V. Creating the transport zone, and installing NSX on the clusters, and preparing the clusters - solved the issue for me.
Hello,
Have you figured our the issue? I have the same issue with NSX-T in the source and remote site.
Regards,
Just found out:
- Source can't be NSX 3.0
- vSphere 7.0 not supported
This is from the release notes:
VMware Product Interoperability Enhancements
Regards,
it helps to see the full error message from the HCX Cloud manager, but this usually comes up when there is no NSX-T Overlay Transport Zone available at the destination. Specifically the selected HCX Deployment Cluster in the CP has to be part of the overlay tz. Also this error can happen if DVS were selected instead of the NSX-T Overlay TZ in the CP screen where you select objects for Network Extension (the screen says select DVS, so it's misleading, but it will be fixed in upcoming release).
Thanks! It was the fact I hadn't deployed an overlay TZ.
I faced this error and it was due to miss configuration of the compute profile. basically you select a transport zone that does not exisit on the cluster I choose to deploy the HCX appliances on.
To Fix this you need to properly configure the compute profile and make sure that the cluster that HCX appliances are going to be deployed on have the transport zone that you are referencing in the compute profile. The network profiles protgroups should be configured properly as well (make sure to select PGs that have the right IPs configured and the Vlans trunked to the hosts).