You can convert the standalone NSX deployment to cross- vCenter architecture.however below are the consideration for cross-vCenter deployment.
- Local objects cannot be converted to universal objects, (Ex- Local logical switch to universal logical switch, DLR to UDLR, DFW to UDFW etc)
- you have to redeploy the NSX controller cluster to universal controller cluster in the primary site and remove the local controller cluster in all of the sites
- During UCC deployment your control plan will not be functional, as a result in the logical networking elements are set to a read only mode and no new logical components can be modified or deployed from the NSX managers.no new routing information can be learned.
the NSX cross vCenter design guide will help you more details about this
Hi there sir,
In strict sense, secondary site will preserve everything since it is going to sync with universal controller cluster in master site, just take care of not overlapping ID for LS, what I'm about to check is about this dilemma : In order to promote secondary site to be ruled by universal controller cluster you are required to remove local controllers, if you do so you will get you overlay lost, but It is supposed that they are going to be sync but how is that if you are not yet promoted and yet controlled but UCC?
I have a setup in home Lab with cross vc nsx and I will destroy it to verify this gray area since I want to be sure before to make the deployment in one of my clients, so max this weekend will have the clarification to this.
Yes once you delete your secondary controllers ( at secondary site/vCenter/NSX Manager) it will use UCC to control secondary NSX environment. You will have to synchronize from universal environment to get it all consistent. You will end up having two local NSX deployments (as long as your VXLAN segment ID's dont overlap) therefor local Transport Zone at each location/vCenter and one Universal environment therefore Universal Transport zone.