The process of registering a Local Manager (LM) with a Global Manager (GM) is initiated from the GM's user interface. To add a new location to the NSX Federation, the administrator must provide two key pieces of information to the GM: the connection endpoint for the LM cluster and the credentials to authenticate to it. The required endpoint is the highly available Virtual IP (VIP) or its corresponding Fully Qualified Domain Name (FQDN) of the LM cluster. The GM then uses these details to establish a secure connection and integrate the LM into the global management plane.

A. Licensing for NSX Federation is installed and managed on the Global Manager. The LM does not validate the GM's license during the registration process.

B. While using a VIP is correct, the detail about certificate updates is a benefit of proper certificate management, not a direct requirement of the registration workflow itself.

D. Using the IP or FQDN of an individual NSX Manager node is explicitly discouraged. The cluster VIP must be used to ensure high availability for communication.

1. VMware NSX-T Data Center 3.2 Federation Guide

"Add a Location to Global Manager"

Page 16.

The procedure states: "In the Location Manager text box

enter the FQDN or IP address of the NSX Manager cluster in the location you are adding. You must use the cluster VIP." This validates option C.

The procedure also states: "Enter the user name and password for the NSX Manager cluster." This validates option E.

2. VMware NSX-T Reference Design Guide

"NSX Federation Deployment"

Section 7.2.1

Page 141.

The guide details the onboarding process: "The onboarding of a location (NSX-T Local Manager) is initiated from the Global Manager UI. The user provides the FQDN/IP of the Local Manager cluster VIP and credentials." This confirms that both the LM Cluster VIP/FQDN (C) and credentials (E) are required inputs from the GM side.