Episode-02 for Transitioning NSX as crucial component of VCF/VVF

NSX and VVF/VCF 9 Introduction

Why am I jumping directly from NSX to VVF/VCF?

The core reason behind this topic discussion is the consolidation of VMware product line under 2 separate strategic groups

VVF (VMware vSphere Foundation) More focused on Core virtualizations (Compute, vSAN, NSX Options).

·       Moreover, vSphere (compute) is mandatory, and licensing based on cores and managed by vSphere. Other components like vSAN and NSX are optional if you want to use separate physical SAN other than VMware provided HCI model, yes you can use it and same is true for NSX if you go with simple networking instead of NSX.

Component	VVF Requirement	Notes
vSphere (Compute)	Mandatory	Core virtualization platform; baseline for VVF
vSAN (Storage)	Optional	Add‑on for hyperconverged storage; external storage still supported
NSX (Networking/Security)	Optional	Add‑on for advanced networking & security; not required for basic deployments

For your reference, please, visit this Link (VVF Structure) 

VCF (VMware Cloud Foundation): Full stack of VMware private cloud architecture that start with

1. ESXi Hosts
2. vCenter Server Appliance
3. vSAN
4. NSX Architecture
5. VMware Aria Suite

In simple words, for SDDC you require above 4 points by all means (Compulsory) and for a functional private cloud you require VMware Aria (Operations and Automation). So, on contrary, you require all the components for VCF to run a private cloud in any organizations.

Can we move from VVF to VCF at any point, so, the answer is “Yes”. 

Under VCF, there is a big concept of public cloud relevant architecture adapted by VMware private cloud for infrastructure management across the globe for any organization that manages its own Infrastructure till data administration.

So, if I try to conclude above explanation then, I only need to summarize VMware products by Broadcom into two major groups

1.      If any organization is only focusing on Server Virtualization and consolidation with manual data center services then move your workload to VVF

2.      IF any organization is moving from private cloud of older versions from VCF 5.x to new version of cloud then VCF and the version would be 9.x

Note: The perpetual keys for individual products are now changed into subscription whether its VVF or VCF 😊

VVF architecture is simple and managed through vCenter Server Appliance under subscription based licensing but If we talk about VCF, It has been changed even from VCF 5.x (you can say from its predecessor).

For more clarity about licensing, you can visit. You can also see the FAQs by VMware 

Will discuss this detailed architecture in my next upcoming series and also in my vLog through my channel 😊.

Stay Tuned!