Configuring Global Managers and Local Managers in VMware NSX-T Federation

In this article I will cover setting up your first two Global Managers and adding the local managers from your sites.

Log into the newly deployed Global Manager

NSX-T Global Manager system page with controls to make the appliance active and add a standby manager.

System > Configuration > location Manager

Make Active

Make Active dialog requesting the name of the NSX-T Global Manager.

Provide the name of your Global Manager

Location Manager view showing Dallas-GM active with a stable cluster and its NSX-T version.

Confirm the GM is active

NSX-T command-line output from the get certificate api thumbprint command used to pair managers.

SSH into the Global Manager

Run the #get certificate api thumbprint

Store this output somewhere

Repeat this for your NSX-T Global Manager in location 1 and location 2

NSX-T Global Manager interface showing the Add Standby control.

Now it is time to deploy the standby Global Manager

Add standby

Add Standby Global Manager form with name, FQDN, credentials, SHA-256 thumbprint, and compatibility check.

Enter the name of the new GM

Provide the FQDN of the standby GM

Admin username

Copy the standby site NSX-T GM thumbprint here

NSX-T standby-manager form showing the compatibility section used to validate the remote manager.

Then check compatibility

Location Manager view listing Dallas-GM as active and FortWorth-GM as standby with stable clusters.

Confirm the managers

Global Manager Location Manager page showing successful synchronization and the control to add a new location.

Next we need to add the onprem location for the first site – my example Dallas

Add New Location form requesting the local-manager name, FQDN, credentials, thumbprint, and compatibility check.

Enter the name for the first site local manager

Provide the FQDN for the NSX-T manager for location 1

Copy the thumbprint for location 1 NSX-T manager

New-location form showing the compatibility check used before adding the first NSX-T Local Manager.

Click check compatibility

Location Manager warning that the default transport zone was not found while the Dallas Local Manager was still synchronizing.

Ignore this error as it will go away when the LM syncs with the GM – takes around 5-15 minutes

NSX-T Federation Add New Location panel with the Add On-Prem Location control.

Rinse and repeat to add in your second location – my example is FortWorth

Compatibility section used while adding the second NSX-T Local Manager location to Global Manager.

Next we need to import objects to the GM

Keep exploring

Choose your next step

Continue with the path that best matches the architecture or operating challenge in front of you.

Leave a Reply

Discover more from Digital Thought Disruption

Subscribe now to keep reading and get access to the full archive.

Continue reading