VMware Networking Community
jeffj2000
Enthusiast
Enthusiast

vCenter HA mode and NSX manager

We are doing a greenfield NSX deployment at a site. We are following the VVD so we have a 4-node management cluster with 2 vCenters, a Computer vCenter and a Management vCenter. We would like to put both of the vCenters in HA mode. Will the NSX manager or any other appliances that register with vCenter have any issues during failover? I have not seen that to be the case. We also using Ephemeral VDS ports for the vCenter nics just in case we have issues and need to do some things with the ESXi host.

However, in the VMware validated design, vCenter HA is not mentioned. So that got me thinking. Thank you very much.

0 Kudos
4 Replies
A13x
Hot Shot
Hot Shot

We have HA enabled on our vCenter with NSX and not had any issues (apart from those mentioned in the change logs in the past duplicate vteps etc). VMware also went through the design and we have had a health check inc NSX and nothing was flagged up for nsx

0 Kudos
jeffj2000
Enthusiast
Enthusiast

Thank you for the information. Is the duplicate vtep issue still present? I will look through the change log for it to show our VMware consul.

0 Kudos
Sateesh_vCloud

We have vCenter HA mode enabled recently and seeing some duplicate VTEP issues - Can you share more details about it?

I saw the KB, but curious to know more details.

VMware Knowledge Base

------------------------------------------------------------------------- Follow me @ www.vmwareguruz.com Please consider marking this answer "correct" or "helpful" if you found it useful T. Sateesh VCIX-NV, VCAP 5-DCA/DCD,VCP 6-NV,VCP 5 DCV/Cloud/DT, ZCP IBM India Pvt. Ltd
0 Kudos
A13x
Hot Shot
Hot Shot

We had this many times in the past, this has supposedly been fixed. Its basically vcenter getting rebooted while the nsx manager is up and then it recreating them. solution is to shut the nsx manager down before the vcenter but this is not possible in a ha situation. The issue has been resolved in the later versions of nsx if you dare upgrade

"This issue is resolved in VMware NSX for vSphere 6.2.4 with vSphere 6.0 Update 3"

0 Kudos