NSX-T Architecture

The diagram depicted above is a high level NSX-T architecture that I will explain today.

NSX manager and its cluster communication with transport nodes through APH server (Application Proxy Hub)

All transport node connect with NSX-T component using NSX-Proxy service.

Transport node connect with NSX-Manager on port 1234 and CCP(Central control plane) on port 1235

In NSX-T  have its own NSX-RPC for used as messaging queuing between manager and transport node.

Before NSX-T 2.5 or NSX-V it was rabbitmq messaging queuing protocol use for communication between manager and ESXI nodes

NSX services details
**********************

NSX Vibs details
****************

nsx-cfgagent:
1) Report VIF connect to CCP

2) Push CCP properties to KCP, L2 FIB to VDL2, L3 info to VDR, FW Rule to DFW, and so on.

nsx-cfgagent maintains a state cache for config and L2 data which is received from nsx-nestdb.nsx-cfgagent provides several NSXCLI commands to dump its cache data.
Nsx-cfgagent detects the connection to both nsx-proxy and nsx-nestdb. Daemon health state can impact “com.vmware.common.opaqueDvs.status.component.lcp.ccpSession” property. If the connection between nsx-proxy or nsx-nestdb is down, then the property value is down. The down property will impact the vMotion compatible check.

nsx-mpa:
Provides communication between NSX Manager and hypervisor hosts.

nsx-opsagent:
Communicates operations agent executions
such as transport node realization, Link Layer Discovery Protocol – LLDP,traceflow, packet capture, etc with the management plane.

nsx-proxy:
nsx-proxy gets information about 3 CCP nodes from the controller-info.xml file. The file contents of controller-info.xml will be same on all the hosts. nsx-proxy creates a random ordering of the 3 CCP nodes and saves the list in memory. nsx-proxy will select the first one from that list and try to connect to it.

nestdb:
nestdb is local data store

nsx-exporter:
Provides host agents that report runtime state to the aggregation service running in the management plane.

nsx-sfhc:
Service fabric host component (SFHC).
Provides a host agent for managing the lifecycle of the hypervisor as a fabric host in the management plane’s inventory.
This provides a channel for operations such as NSX-T Data Center upgrade and uninstall and monitoring of NSX-T Data Center modules on hypervisors.

nsx-platform-client:
Provides a common CLI execution agent, for centralized CLI and audit log collecting.

nsxcli:
Provides the NSX-T Data Center CLI on hypervisor hosts.