An administrator is tasked to configure NSX Federation between separate VMware Cloud Foundation (VCF) Fleets. Which requirement must all sites meet before being added to a Global Manager (GM) for…

Question

Options

• AAll Sites must use the same VTEP VLAN and IP pools.
• BAll sites must use identical Tier-0 gateway BGP autonomous system numbers.
• CAll sites must be managed by the same VCF instance.
• DAll sites must have the same NSX version and build.

• A
  4% (1)
• B
  11% (3)
• C
  4% (1)
• D
  81% (22)

Explanation

NSX Federation, a core component of large-scale VCF deployments across multiple sites or "fleets," introduces a hierarchical management model where a Global Manager (GM) orchestrates security policies and networking objects across multiple Local Managers (LMs). To ensure stability and compatibility in the communication between the Global Manager and the Local Managers, VMware documentation specifies strict version parity requirements. When onboarding a site into a Federation, the Local Manager at that site must be running the same NSX version and build as the other sites in the Federation and must be compatible with the Global Manager's version. Discrepancies in versions can lead to synchronization failures, as the API schemas and internal database structures for Global Objects (like Global Segments or Groups) may differ between builds. While Federation allows for geographic and administrative separation, the underlying software- defined networking stack must be synchronized. Option A is incorrect; in fact, VTEP/TEP VLANs and IP pools should be unique to each site to avoid IP conflicts in the transport network, though they must have Layer 3 reachability to one another. Option B is incorrect; unique BGP AS numbers are often preferred for multi-site routing to prevent loops. Option C is also incorrect, as Federation is specifically designed to link different VCF instances (sites) together into a single manageable entity. In a VCF 5.x or 9.0 context, the SDDC Manager helps maintain this requirement by ensuring that the "Bill of Materials" (BOM) is consistent across sites intended for Federation. Before the GM can successfully register and "push" configuration to an LM, the handshake process validates the build version to prevent the corruption of the global intended state.

No community discussion yet for this question.