While trying to install the NSX Manager I have strange problem. Maybe anyone else have this issue, too?
When I am installing the NSX Manager with the ova-File there will be a task "Install Solution" of com.vmware.nsx.manager created, but it seems to be never started and times out after 1 hour.
So, what can I do to install the NSX Manager plugin into vCenter? Is there maybe a workaround?
Thank you for your replies.
Today I had more luck on another vCenter host (with more CPU power). There, the vCenter plugin was installed without any issues after a bit time waiting. Hmm...maybe I should have to buy another more powerful machine for the lab environment...
All in all, the installation of the NSX-T vCenter plugin seems to success really randomly. 😞
Can you share a screenshot of error you are facing?
Can you please confirm the following?
vCenter Version?
ESXi Version?
NSX-T OVA version?
Are you using Integrated NSX-T Deployment workflow to deploy NSX-T? Also, is it possible to share event logs on ESXi and vCenter around same time when error occurred for any potential cause?
I've seen this issue in a 'dirty' vCenter install. You will need to ensure there are no remnants of the plugin in the vCenter mob and you are using the correct OVA.
If this is a nested environment, storage latency could also be an issue.
Hi, Can you please check NTP sync? This could happen when NTP is not in sync.
Thank you for your replies.
Today I had more luck on another vCenter host (with more CPU power). There, the vCenter plugin was installed without any issues after a bit time waiting. Hmm...maybe I should have to buy another more powerful machine for the lab environment...
All in all, the installation of the NSX-T vCenter plugin seems to success really randomly. 😞
The result you faced may be less random than you think.
Typically in lab environments there are resource constraints (generally storage, but in your case may have been CPU), as a result the deployment workflow is preconfigured to achieve certain results / tasks within a set period of time. Now if your resource constraints cause that configuration task to not complete within that time, the workflow will time out and not deploy (as you saw).
The better hardware / environment that you deployed it to was likely that fraction (or more) quicker, and was able to complete the tasks within the workflows time out period.
Hopefully this makes sense, glad you got it deployed!