We do have a VxRail cluster (vCenter 6.7) where I want to deploy my own nested vSphere lab.
My nested ESXi VMs running version 7.0 U3 (60 days evaluation) downloaded from: https://williamlam.com/nested-virtualization/nested-esxi-virtual-appliance
vCenter downloaded from my.vmware.com, version 7.0 U3.
Deployed the ESXi VMs following this article: https://mattadam.com/2021/07/21/configuring-nested-esxi7-on-supermicro/
I did connect all 3 nested ESXis to Network port group in the vDS and assign them IPs and FQDN with no issues.
Tried deploying vCenter from the jump station on my nested ESXi-01-VM following instruction from Matt in here: https://mattadam.com/2021/07/26/deploy-vcenter-7-and-vsan-on-nested-esxi/
At the end of the Stage 1, I always get this error: The installer is unable to connect to the vCenter Server Management Interface.
I checked and vCenter VM is up and running, I can access it's DCUI, but I can not reach it over the IP or FQDN, I can not even ping them.
Even though, I created a Win2016 VM in my Cluster and tried deploying from it I got the same error.
Error snapshot:
Example of errors I got in the installer.log:
2022-02-25T17:16:22.246Z - error: Could not get response for get request from url https://192.168.1.70:5480/: Error: connect ETIMEDOUT 192.168.1.70:5480
2022-02-25T17:16:22.265Z - error: VAMI is NOT accessilbe[25]: https://192.168.1.70:5480/, err: Could not get response for get request from url https://192.168.1.70:5480/: Error: connect ETIMEDOUT 192.168.1.70:5480
Environment illustration:
I hope some one could help 🙂
Thank you.
Finally the issue has been solved, I do have access to the nested deployed VCSA now from the Windows VM and also from my Jump station.
I'm not sure to be honest what was the issue, maybe I just need needed to wait for a while or something. But I remember I did change the values to "Accept" in Security tab of the current cluster vDS port group for traffic as indicated in the topology i shared earlier.
