nsx manager appliance failing to power on - deployed from GUI

[billdossett]

Question 1, in my lab, do I need to deploy a full nsx manager cluster to be able to fully bring up NSX and learn how it works?

if so, then

as the subject says, when I deploy an additional appliance from the GUI, it fails to power on, the installation says failed, my only option is to delete the deployment.  I have reduced memory and removed reservation so that it does power on and it runs in 12GB of memory wioth 2.5GB spare... but it hasn't joined the cluster and I can't figure anyway of adjusting this so that the deployment doesn't think it failed... so I'm kind of stumped on this one.
Thanks

[shank89 · Accepted solution]

In a lab environment you can continue with the initial single manager that you deploy.  You will have full read and write access to the manager and nsx-t environment.

In production, when you build out the 3 node cluster, the below applies

• 3 managers available - full access
• 2 managers available - full access
• 1 manager available read only

So it is in your best interest to recover whatever failed appliances you have ASAP.

[billdossett]

ok, thanks...  so I will just keep going with my single manager then for my lab.

[qcoelho]

From NSX-T 3.1 we now support deploying with a single NSX-T Manager.

See the release notes: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/rn/VMware-NSX-T-Data-Center-31-Release-Notes...

NSX now supports the deployment of a single NSX Manager in production deployments. This can be used in conjunction with vSphere HA to recover a failed NSX Manager. Please note that the recovery time for a single NSX Manager using backup/restore or vSphere HA may be much longer than the availability provided by a cluster of NSX Managers.

[shank89]

Ah yep good point forgot about that.  Suppose it would be use case dependant.