Which two requirements are part of the registration process for Local Manager (LM) to a Global Manager (GM) in NSX for centralized management of network and security services across different…

Question

Options

• AThe LM will validate the GM license to perform the GM registration.
• BThe external load balancer VIP is used for NSX Managers without requiring node API certificate
• CThe LM Cluster VIP / FQDN is provided for GM-LM communication.
• DThe IP / FQDN of any of the 3 LM must be used for registration.
• EThe GM-Active requests the LM IP / FQDN and admin credentials for registration.

• A
  4% (2)
• B
  15% (8)
• C
  72% (39)
• D
  9% (5)

Explanation

NSX Federation is the architectural framework used within VMware Cloud Foundation (VCF) to provide consistent networking and security across multiple sites. The core of this framework is the relationship between the Global Manager (GM) and one or more Local Managers (LMs). The registration process is the critical first step in establishing this "parent-child" relationship. According to the "NSX-T Data Center Administration Guide" and Federation-specific documentation, the registration is initiated from the Active Global Manager. Initiation and Credentials (Requirement E): The administrator logs into the Global Manager UI and navigates to the "System > Fabric > Locations" section. To add a new site, the GM-Active requires the IP address or FQDN of the target Local Manager and the Admin credentials. This allows the GM to authenticate with the LM, exchange security certificates, and establish a secure thumbprint-verified connection. Stable Communication Endpoint (Requirement C): For the ongoing management and synchronization of "Global Objects" (like Tier-0s or Security Groups), the GM must communicate with the LM cluster as a whole rather than a single individual node. Therefore, the LM Cluster Virtual IP (VIP) or a FQDN pointing to that VIP is provided. Using the VIP ensures that if the specific LM node that initially handled the registration fails, the GM can continue to communicate with the remaining nodes in the LM cluster without administrative intervention.

No community discussion yet for this question.