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).