Solution providers looking to deliver virtualized networking to their customers have two options currently—VMware NSX-V and NSX-T. However, when you look at the differences between the two, it’s clear that NSX-T should be the platform of choice.
NSX offers organizations a variety of powerful L2-L7 networking and security virtualization benefits if appropriately utilized, as the technology essentially virtualizes the networking layer, allowing networks of all sizes and complexity to be deployed more rapidly. Network devices such as routers, switches, firewalls, and more can be included in the virtualized network, offering an endless number of combinations and capabilities. Entire virtual networks can be provisioned and managed independently of the hardware being used, saving your customers time and money.
NSX-V and NSX-T. What’s the difference?
NSX-V provides a powerful option for virtualizing layers 2 through 7 of a network. However, with the introduction of NSX-T, VMware greatly extended the capabilities. Here are just a few ways the two platforms differ:
|Supports VMware only.
||Supported on ESXi, KVM, bare-metal servers, Kubernetes, OpenShift, AWS and Azure.
|NSX Controllers are deployed separately from NSX Manager
||NSX Controllers are now integrated into NSX Manager as a single virtual appliance and controllers no longer need to be deployed independently.
|Requires you to register NSX Manager inside of vCenter.
|Directs to vCenter by registering Transport Nodes instead of registering NSX Manager inside of vCenter.
|Uses VXLAN (Virtual Extensible LAN) overlay technology for encapsulation, which has more flexibility than just traditional VLANs, but has its limitations when compared to GENEVE.
||Uses a more modern overlay technology called GENEVE for encapsulation. GENEVE is known to perform better and is more flexible for the future over older, more traditional VXLAN overlay technology.
|Reliant on the vSphere Distributed Switch (VDS), which means it can’t be deployed across different platforms.
||Uses a new distributed switch known as N-VDS. The N-VDS is not reliant on vCenter like the vSphere Distributed Switch used for NSX-V. This means the N-VDS can be used across multiple platforms because it no longer resides in vCenter.
Across the board, NSX-T provides more capabilities and possibilities, but the first difference might be the most significant selling point of NSX-T; it offers many new cloud options for those in need of building and supporting hybrid infrastructure. Eventually, VMware will sunset NSX-V, which is another reason to consider NSX-T. In the meantime, licenses for NSX-V are transferrable to NSX-T, eliminating yet another barrier.
Thanks to NSX-T, you and your customers have more options than ever to enable a virtual cloud network to connect and protect applications across the data center, multi-cloud, bare metal, and container infrastructure. If you would like more information on NSX-T, contact the appropriate VMware Market Development Executive for your territory:
• Justin Gawronski — VMware MDE East — firstname.lastname@example.org
• Dan Eyrick — VMware MDE Central — email@example.com
• Guru Padukone — VMware MDE West — firstname.lastname@example.org