If Region A becomes unavailable, prepare the network layer in Region B for a failover of the management applications. Change the role of the NSX Manager to primary, deploy the universal controller cluster, and synchronize the universal controller cluster configuration.
Procedure
- Log in to vCenter Server by using the vSphere Web Client.
- Open a Web browser and go to https://lax01m01vc01.lax01.rainpole.local/vsphere-client.
- Log in using the following credentials.
Setting
Value
User name
administrator@vsphere.local
Password
vsphere_admin_password
- Promote the NSX Manager for the management cluster in Region B to the primary role.
You must first disconnect the NSX Manager for the management cluster in Region B from the Primary NSX Manager in Region A.
- From the Home menu, select Networking & Security.
- In the Navigator pane, click Installation and Upgrade.
- On the Management tab, click NSX Managers tab and select the 172.17.11.65 instance.
- Click the Actions menu and click Disconnect from Primary NSX Manager.
- In the Disconnect from Primary NSX Manager dialog box, click Yes.
The NSX Manager gets the Transit role.
- On the NSX Managers tab, select the 172.17.11.65 instance again.
- Click Actions and select Assign Primary Role.
- In the Assign Primary Role dialog box, click Yes.
- Configure an IP pool for the new universal controller cluster.
- In the Navigator pane, click Groups and Tags.
- Click the IP Pools tab and select the 172.17.11.65 instance.
- On the IP Pools tab, click + ADD.
- In the New IP Pool dialog box, enter the following settings, and click Add.
Setting
Value
Name
lax01-mgmt01-nsxc01
Gateway
172.17.11.253
Prefix Length
24
Primary DNS
172.17.11.5
Secondary DNS
172.17.11.4
DNS Suffix
lax01.rainpole.local
IP Pool Range
172.17.11.118-172.17.11.120
You enter the IP pool range by clicking + ADD below IP Pool Range.
- Deploy the universal controller cluster in Region B.
- In the Navigator pane, click Installation and Upgrade.
- On the Management tab, under NSX Controller nodes, click the Add icon to deploy three NSX Controller nodes with the same configuration.
- In the Add Controller dialog box, enter the following settings and click Next.
Setting
Value
NSX Manager
172.17.11.65
Password
mgmtnsx_controllers_password
Confirm Password
mgmtnsx_controllers_password
You configure a password only during the deployment of the first controller. The other controllers use the same password.
- In the Add Controller dialog box, under Deployment & Connectivity, enter the following settings and click Finish.
Setting
Value
Name
lax01m01nsxc01 for controller 1
lax01m01nsxc02 for controller 2
lax01m01nsxc03 for controller 3
Data center
lax01-m01dc
Cluster/Resource Pool
lax01-m01-mgmt01
Datastore
lax01-m01-vsan01
Folder
lax01-m01fd-nsx
Connected To
lax01-m01-vds01-management
Select IP Pool
lax01-mgmt01-nsxc01
- After the Status of the controller node changes to Connected, deploy the remaining two NSX Controller nodes lax01m01nsxc02 and lax01m01nsxc03.
Wait until the current deployment finishes before you start with the next controller.
- Configure DRS affinity rules for the deployed NSX Controller nodes.
- From the Home menu of the vSphere Web Client, select Hosts and Clusters.
- Expand the lax01m01vc01.lax01.rainpole.local>lax01-m01dc and click the lax01-m01-mgmt01 cluster.
- Click the Configure tab, under Configuration, click VM/Host Rules, and click Add.
- In the Create VM/Host Rule dialog box, enter the following settings and click OK.
Setting
Value
Name
anti-affinity-rule-nsxc
Enable rule
Selected
Type
Separate Virtual Machines
Members
lax01m01nsxc01
lax01m01nsxc02
lax01m01nsxc03
- Synchronize the state of the newly deployed controllers by using the Update Controller State mechanism on the NSX Manager.
Update Controller State pushes the current VXLAN and universal distributed logical router configuration from NSX Manager to the Controller cluster.
- From the Home menu of the vSphere Web Client, select Networking & Security.
- In the Navigator pane, click Installation and Upgrade.
- On the Management tab, under NSX Managers, select the 172.17.11.65 instance.
- From the Actions menu, select Update Controller State.
- In the Update Controller State dialog box, click Yes.