There is a timeout at 1 200 000 ms = 20min seen in /opt/vmware/bringup/logs/vcf-bringup-debug.log that wait for all the services in the NSX cluster are UP and stable.

1. Each ESXi should be at least 46GB or later the installation of NSX bits will fail.
2.  What we experience in lab is that we use small form factor for NSX 4vCPUs and 16GB of RAM but official minimum is medium (6 and 24 respectively) from API standpoint.
   • We can get around that when we deploy as small to stop the NSX VM(s) and give it/them at minimum with 6vCPU = 20000Mhz and 20GB.
   • extend the timeout that wait  NSX to be UP, depending on your storage... i gave it 180min, just in case NSX installation bits fail
   • extend the timeout of overall ova deployment which default to 40min... i gave it 180

````sed -i 's/ovf.deployment.timeout.period.in.minutes=40/ovf.deployment.timeout.period.in.minutes=180/' /opt/vmware/bringup/webapps/bringup-app/conf/application.properties````
````sed -i -e's/nsxt.disable.certificate.validation=true/nsxt.disable.certificate.validation=true\nnsxt.manager.wait.minutes=180/' /opt/vmware/bringup/webapps/bringup-app/conf/application.properties````
systemctl restart vcf-bringup````

I know 180min is probably overkill since the cluster might need 25min, but that allow troubleshooting if things doesn't go as we expect.