When both active and standby VMware NSX Global Managers fail, the environment must be completely rebuilt from a valid backup. First, administrators must delete the corrupted active and standby Global Manager appliances across all clusters to prevent synchronization issues or IP conflicts. Second, deploy a brand-new Global Manager appliance using the exact same IP address and FQDN as the original active node. Third, access the newly deployed appliance to restore the active Global Manager configuration directly from the remote SFTP backup server. Finally, to re-establish high availability and Federation synchronization, deploy a new Global Manager at the secondary site and onboard it as a standby node to the newly restored active Global Manager.

VMware by Broadcom. VMware NSX-T Data Center Administration Guide. Chapter: "Backing Up and Restoring VMware NSX", Section: "Restore a Global Manager Cluster".

VMware by Broadcom. VMware NSX-T Data Center Administration Guide. Section: "Restore an Active Global Manager". (These sections explicitly detail the mandatory 4-step workflow for total Global Manager cluster failure recovery).

The scenario explicitly requires a "dedicated DHCP solution" for each virtual desktop segment (vdi-seg-02 and vdi-seg-03). In VMware NSX, this dictates the use of a Local/Segment DHCP Server rather than a shared Gateway DHCP server attached to the Tier-1 gateway. Because vdi-seg-01 uses static addresses, it requires no DHCP configuration. To configure Segment DHCP, you must first define the segment's DHCP type as Segment DHCP Server and bind a server profile. Second, you must assign the DHCP Server Address, which acts as the dedicated DHCP service IP on that specific segment. Finally, you configure the DHCP Range and DNS Servers to establish the pool of addresses for the VDI clients. This identical three-step sequence is applied to both desktop segments.

VMware NSX Administration Guide (v4.x / v3.2): Networking > IP Address Management (IPAM) > DHCP > Configure Segment DHCP. This section officially documents the requirement to create a DHCP profile, assign a DHCP server IP address, and define DHCP ranges when utilizing a Local DHCP Server at the segment level.

VMware Cloud Foundation (VCF) Operations Guide: Virtual Infrastructure Management > NSX Edge and Workload Networking. Details the architectural distinction between Gateway DHCP (shared across the gateway) and Local/Segment DHCP (isolated/dedicated per segment).

In NSX-T, segment realization follows a strict architectural path from user intent to data plane enforcement. User configurations enter the Policy engine, which translates and forwards the intent to the Manager role. The Manager computes the desired logical state and passes it to the Central Control Plane (CCP). For downstream communication, both the Manager and CCP utilize the Appliance Proxy Hub (APH) on the manager node to multiplex traffic to the transport nodes via NSX-RPC (TCP 1234 for management and TCP 1235 for control plane).

On the ESXi transport node, the Local Control Plane daemon (NSX-Proxy) receives the control state and programs the network configurations into the hypervisor's data plane kernel module, nsxt-vdl2, achieving the final realized state.

VMware, Inc. (2021). VMware NSX-T Reference Design Guide. Section: "NSX-T Architecture and Components" (Subsections covering Management Plane, Control Plane, and Data Plane communication via APH).

VMware, Inc. NSX-T Data Center Troubleshooting Guide. Section: "Understanding NSX-T Component Communication and State Realization" (Specifically detailing the APH multiplexing and the nsx-proxy to nsxt-vdl2 realization flow on ESXi hosts).

Ingress (North-to-South) traffic enters the VMware Cloud Foundation NSX environment via the external physical network hitting the Tier-0 Service Router (SR) Uplink on the Edge node. Inside the Edge, the packet routes from the Tier-0 SR to the Tier-0 Distributed Router (DR), crossing the transit link via the Tier-0 DR Inter-Tier interface to the Tier-1 DR. The Tier-1 DR on the Edge performs a lookup, identifies the VM's host, and uses the Edge Tunnel Endpoint (TEP) to encapsulate the traffic. The packet travels to the destination host's TEP. After decapsulation, the host's local Tier-1 DR forwards the packet through its segment downlink, passing through the NSX portgroup and dvfilter directly to the workload VM's vNIC.

VMware NSX-T Data Center Reference Design Guide (v3.2), Section 4.3: North-South Traffic Patterns and Section 4.3.2: Traffic Flow with Tier-0 and Tier-1 Architectures. This section provides explicit packet walks validating the ingress path from Edge SR uplinks, through the DR transit links, encapsulation at the Edge TEP, and decapsulation at the host TEP before hitting the segment downlink.

VMware Cloud Foundation Design Guide, Section: NSX Edge Node Design and Routing Architecture. Validates that when a Tier-1 is configured for Distributed Routing only, all stateful services are bypassed, and the North-South ingress handoff occurs exactly as sequenced across the inter-tier interfaces on the Edge before tunneling to the workload host.

In VMware Cloud Foundation (VCF), Centralized Connectivity Mode is a specialized network architecture designed for specific workload domains. Unlike a fully distributed routing model, it relies heavily on centralized edge resources, making it suitable for environments needing limited NSX networking services without full-scale distributed transit gateways. Because north-south traffic is funneled through specific Service Routers on the Edge nodes, this mode seamlessly supports stateful services configuration (e.g., NAT, load balancing, firewalling). To function, it inherently requires the deployment of an NSX Edge cluster to host the Tier-0 gateway, acting as the centralized egress point to the physical top-of-rack (ToR) switches. Finally, administrators can configure this mode natively during the deployment of the workload domain through standard SDDC Manager workflows.

VMware by Broadcom. VMware Cloud Foundation Networking Design Guide. Section: Workload Domain Networking Architectures and Topologies. (Details the automated deployment workflows and capabilities configured during workload domain creation).

VMware by Broadcom. VMware NSX Reference Design Guide. Section: Edge Node Design and Stateful Services. (Explains how centralized routing topologies mandate edge clusters to anchor stateful network services like NAT and stateful firewalls).

VMware by Broadcom. VMware Cloud Foundation Administration Guide. Section: Edge Cluster and Tier-0 Gateway Prerequisites. (Outlines the architectural streamlining and limits of localized edge connectivity compared to active/active distributed models).