As we discussed in first post of this series that NSX-T was born to meet the demands of the containerized workload, multi-hypervisor and multi-cloud.
The best use case that you can think of NSX-T is that it provides seamless connectivity and security services for all types of endpoints including virtual machines, containers and bare metal. It doesn’t really matter where these endpoints are. It could be in your on-prem datacenter, a remote office or in the cloud.
In this post we will look how NSX-T architecture looks like.
Like NSX-V, NSX-T too contains a management plane, data plane and a control plane. Lets discuss about each plane individually here.
Data Plane
- NSX-T uses in-kernel modules for ESXi and KVM hypervisors for constructing data plane.
- Since NSX-T is decoupled from vSphere, it don’t rely on vSphere vSwitch for network connectivity. NSX-T data plane introduces a host switch called N-VDS (NSX Managed Virtual Distributed Switch).