Understanding NSX cross vCenter Server
Earlier versions of NSX had a 1:1 relationship with vCenter Server and that means NSX features and functionalities were limited to that specific vCenter Server. So whenever we are scaling vCenter Servers, it demands separate installation and configuration of NSX Manager and each of these environments has to be managed separately. When VMware released NSX 6.2 in August 2015, security and cross vCenter Server networking were exciting features that were announced. With cross vCenter networking and security features, we can extend logical switches across vCenter boundaries and, adding to that, we can extend distributed routing and distributed firewalling seamlessly across VCs to provide a true network hybridity between both the sites. There are numerous use cases customers can benefit from with this cross VC NSX integration. The following are a few of them:
By leveraging cross vCenter Server, we can have a primary and secondary vSphere environment and can...
