VCF 9 Architecture (Formerly: NSX Design Architecture)

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) Mandatory Licensing is TiB per Core and minimum license cap is 16 Core (even if you have 8 cores then it will be counted...

  Hi Readers! It was a long break and I myself got engaged in new dynamic skill upgrades that result in a long delay. It’s been a while since my last deep dive here — the IT landscape doesn’t wait, and neither should we! So, Let’s pick up with one of the most important shifts in VMware’s networking and security stack: NSX 4. Simplified Lifecycle Management NSX 4 integrates more tightly with vSphere Lifecycle Manager, making upgrades and patching smoother. Enhanced Security Features Distributed Firewall improvements, including L7 application ID enhancements and context‑aware microsegmentation . Deeper integration with VMware Threat Prevention and IDS/IPS. Networking Enhancements Better support for IPv6 , multi‑tier routing, and federation improvements for multi‑site deployments. Operational Visibility Expanded NSX Intelligence for real‑time flow visualization and policy recommendations. Container &...

  Hello everyone! Let’s continue our discussions about Site Resiliency model offered by NSX not through Multisite but through federation. What benefits we may have and what improvements we may have. This is all what we are going to discuss here in this topic. NSX Federation (a Quick Brief) Unlike Multisite NSX architecture, NSX Federation does not require to configure MTU over WAN or at provider side to be changed from typical (Default) value to 1700+. It’s a big change at infrastructure configuration or requirement level. NSX Managers can be on different geographical locations despite of 10ms RTT problem. Because, the global objects will penetrate into local NSX Managers through Async Replicator Service through Application Proxy Hub (APH) offered by Global NSX Managers. It only replicates Clusters with other site clusters not amongst the nodes of one cluster (or inside a cluster).  Whereas the distance in between Global managers (within same NSX Manager Cluster)  (Active...

  The NSX Multi-site Architecture  By – Adnan  Hussain (VCIX – NV)  Hi there, If you are looking for Multisite topologies based on applications availability across sites, may be in the form of stretch clusters or in the form of Active/Active Sites or Active/Stand-by sites architecture then you are at the right place.  I am writing this article in series / episodes to have a connection with you all and can discuss different aspects using this portal to address your understanding and to learn more In-order to have Applications available across multiple sites even from on-premise to public cloud tenancies, you keep your infrastructure ready and expandable or responsive to difference architectural challenges and changes.  VMware being pioneer in providing Infrastructure relevant software like  All above technologies run on top of software logics with no dependency on Hardware make and model (only needed x86 architecture). I will discuss all above listed te...