No route to host (Host unreachable) basically means there is a problem with DNS/Gateway . I believe the screenshot what you have captured before the controllers getting deleted ? So double check below points.
1. Ensure that you are connecting to right IP-Pool during deployment and entries are correct .
2. Do check DNS,Gateway connectivity from the Portgroup where Controllers are getting deployed also DNS/NTP between NSX Manager/vCenter/ESXi hosts
3. Any firewall between Controllers and NSX manager ?
Everything is configured properly, in fact if i deploy test VM with the same network setting we assign to a controller it can talk to NSX Manager.
I've tried to connect to the controller via VM console in "Deploying" state, however it doesn't accept my credentials - I've tried both root and admin account. It seems that startup script (inside the Controller VM), which should take ovf application properties doesn't assign them correctly.
Is there a way i can access Controller VM, while it is getting deployed?
I'm sure you are missing something very basic here .- wrong prefix/gateway/DNS etc are something very common what i have seen for these type of failures. Can you please provide NSX manager IP stack and controller IP pool information ,if that is not possible ,kindly retry the steps and post the NSX manager logs. Also do check if you have enough compute/storage resource on the underlying ESXI host.
I had the same issue, looks like that "root" password expiry issue. The attached PDF explains the procedure to fix the issue.
PS: Thanks for your screenshot.
Thank you this was a solution! Also I've upgraded Manager to to 6.3.4 and never had any issues with deploying Controllers - tested multiple times.
I'm getting the same error. (no ip address assigned and the same error/logs in the NSX Manager logs)
I don't have this file on the nsx controller:
so I'm not sure what to do about that (saw that in the PDF file)
Is this issue specific to 6.3.3?
I have an entry in my dns server for "nsx-controller.<domain>"
pings, dig, nslookup commands all look normal.
Anyone recommend me to upgrade to a later version of NSX?
yes update to 6.3.5 (or even 6.3.4) and your issue will be resolved.
Yes, that PDF document was great.
Just statically assigned the address and it came right up.
There is a typo in that document.
4. Type the following command:
that should be "systemd".