In this blog post I will cover section 6 objective 6.1 of the VCAP6-NV Deploy exam.
Objective 6.1 – Configure Cross vCenter VMware NSX infrastructure components
Skills and Abilities
- Configure NSX manager roles (Primary, Secondary, Standalone, Transit) according to a deployment
- Assign Primary role to specified NSX Manager
- Assign Secondary role to specified NSX Managers
- Deploy/configure Universal Controller Cluster
- Configure Universal segment ID pools
- Create/manage Universal transport zones
Configure NSX manager roles (Primary, Secondary, Standalone, Transit) according to a deployment
plan: Assign Primary role to specified NSX Manager
In a Cross-vCenter NSX deployment, the NSX Manager can have one of four different roles:
The primary role can only be given to one NSX Manager. The primary manager has the controllers installed and all universal objects are created on the primary NSX Manager. The secondary NSX Manager becomes secondary when it added to the primary manager. All universal objects are read only on the secondary NSX Manager. The secondary NSX Manager cannot have it’s own controllers. Each NSX Manager can have its own local objects that are only seen by that NSX environment. The Standalone role is the default role of a newly installed NSX Manager. It is not a part of a cross-vCenter setup. The Transit role comes into play when a once primary or secondary is made standalone again but there are still universal objects that exist. In the transit role, universal objects can only be deleted, not created. Once all universal objects are deleted, the NSX Manager can become a standalone or secondary NSX Manager.
To assign the primary role to a NSX Manager, navigate to Networking & Security > Installation and Upgrade > Management. Select the the NSX Manager and click the Actions wheel and select Assign Primary Role.
Read Full Article