NSX After Broadcom: The Landscape in 2026
VMware NSX existed in two major generations before the Broadcom acquisition: NSX for vSphere (NSX-V), which reached end of life in January 2022, and NSX-T Data Center (now VMware NSX), which became the primary SDN platform from VMware 3.x onward. Both generations have been affected by Broadcom's post-acquisition restructuring, but in different ways.
For NSX-V customers, the challenge is binary: VMware NSX-V has had no vendor support since January 2022, and Broadcom has shown no interest in extending it. Organisations still running NSX-V for vSphere must either migrate to NSX-T (now rebranded simply as VMware NSX) or find an independent support path. NSX-V third-party support has emerged as the bridge for organisations whose NSX-V migration timelines extend beyond Broadcom's end-of-support window.
For NSX-T and VMware NSX customers, the issue is commercial rather than lifecycle-based. Broadcom's restructuring of VMware licensing folded NSX into VCF bundles, eliminating the standalone NSX licensing model that customers had previously relied on for cost control. Organisations renewing NSX maintenance now face VCF pricing that includes vSAN, vSphere, and Aria Suite alongside NSX — whether they want those components or not.
NSX-V End of Life — January 2022: VMware NSX for vSphere (NSX-V) reached General End of Availability in October 2019 and End of Technical Guidance in January 2022. There is no Broadcom support path for NSX-V. Third-party support is the only supported maintenance option for organisations still operating NSX-V environments.
VMware NSX Version Support Matrix
| NSX Version | Type | Broadcom Status | TPS Coverage | Typical Saving |
|---|---|---|---|---|
| NSX for vSphere (NSX-V) 6.2–6.4 | NSX-V | EOL Jan 2022 | Full TPS Coverage | 80–90% |
| VMware NSX-T 2.x | NSX-T | End of Support | Full TPS Coverage | 70–80% |
| VMware NSX-T 3.0 / 3.1 | NSX-T | End of Support | Full TPS Coverage | 65–75% |
| VMware NSX-T 3.2 / 3.3 | NSX-T | Approaching EOS | Full TPS Coverage | 60–70% |
| VMware NSX 4.0 / 4.1 | NSX (Renamed) | Active — VCF only | Full TPS Coverage | 55–65% |
| VMware NSX 4.2+ | NSX (Renamed) | Active — VCF only | Full TPS Coverage | 50–60% |
What Third-Party NSX Support Covers
Security and CVE Management
NSX has a significant CVE history, with vulnerabilities affecting the NSX Manager API, data plane components, and certificate handling. Critical vulnerabilities in network virtualisation platforms are particularly dangerous because they can affect the security of every workload in the overlay network. Third-party NSX support provides security patch engineering for your specific NSX version, with P1 security vulnerabilities addressed within 24 hours regardless of Broadcom's version lifecycle decisions.
NSX-V to NSX-T Migration Support
For organisations that need to migrate from NSX-V to NSX-T (or VMware NSX 4.x), the migration is technically complex: NSX-V and NSX-T use different data plane architectures, different logical switch constructs, and different integration methods with vCenter. Third-party support provides migration planning and execution assistance, including logical topology mapping, firewall rule migration analysis, and phased migration support that allows workloads to be moved without network downtime.
Micro-Segmentation and Distributed Firewall Support
NSX Distributed Firewall (DFW) is one of NSX's most widely adopted features — providing east-west micro-segmentation at the hypervisor kernel level. DFW rule management, troubleshooting, and performance optimisation in complex environments requires deep NSX expertise. Third-party support covers DFW configuration issues, rule set optimisation, and integration with identity sources including Active Directory for user-identity-based policies.
Overlay Networking and VXLAN/Geneve Support
NSX overlay networking — whether VXLAN-based (NSX-V) or Geneve-based (NSX-T and NSX 4.x) — introduces additional troubleshooting complexity compared to traditional VLANs. Packet encapsulation, MTU configuration, VTEP issues, and host preparation failures are common operational challenges. Third-party NSX support provides overlay networking diagnostic support with 15-minute P1 response for production network issues.
Running NSX-V Without Support? That Changes Today.
NSX-V environments with no vendor support represent significant security and operational risk. Get a third-party coverage assessment within 48 hours.
Get NSX-V Coverage NowThe NSX-V Migration Reality Check
The NSX-V to NSX-T migration is routinely underestimated. Organisations that budgeted for a three-month migration project have frequently found themselves 12–18 months in, with complex distributed firewall rule sets proving particularly resistant to automated migration tools. NSX-T's Policy API-based management model differs fundamentally from NSX-V's manager-centric configuration approach, requiring rethinking of both administrative workflows and automation tooling.
Third-party support for NSX-V is not a permanent alternative to migration — it is a commercially rational bridge that allows organisations to execute the migration on a schedule driven by technical complexity and business risk, rather than by Broadcom's end-of-support clock. For organisations with 500+ distributed firewall rules and complex security group configurations, this bridge can represent 18–36 months of supported operation while the migration is properly planned and executed.
NSX-V migration scope reality: A mid-size enterprise running NSX-V with 800 distributed firewall rules across 12 security zones typically requires 8–14 months to fully migrate to NSX-T, factoring in firewall rule analysis, security group rationalisation, host preparation, and phased workload migration. Third-party support removes the arbitrary deadline from this timeline.
NSX TPS vs VCF Subscription: The Cost Comparison
Broadcom's NSX bundling into VCF makes precise cost comparison difficult — VCF pricing includes vSphere, vSAN, NSX, and Aria, and Broadcom does not publish standalone NSX pricing. However, the practical comparison for organisations evaluating TPS is their prior NSX maintenance cost versus TPS cost, or their VCF bundle cost versus TPS covering only their NSX investment:
| Scenario | Environment | Prior Annual Cost | Broadcom VCF Now | TPS Annual | TPS Saving vs VCF |
|---|---|---|---|---|---|
| NSX-V (no vendor support) | 200 hosts, NSX-V 6.4 | £0 (EOS) | £960,000 (VCF) | £220,000 | £740,000 / yr |
| NSX-T 3.2 renewal | 150 hosts, NSX-T 3.2 | £380,000 | £720,000 (VCF) | £195,000 | £525,000 / yr |
| VMware NSX 4.x renewal | 300 hosts, NSX 4.1 | £750,000 | £1,440,000 (VCF) | £415,000 | £1,025,000 / yr |
VMware/Broadcom Survival Guide — Free White Paper
The 2026 guide to navigating Broadcom's post-acquisition pricing — perpetual licence rights, NSX strategy, VCF alternatives, and negotiation tactics for IT leaders.
Download Free →NSX TPS Transition Process
The NSX third-party support transition follows the same commercial pattern as vSphere TPS — no technical changes are made to your NSX environment. The process is primarily documentation and commercial in nature:
- NSX environment inventory — NSX Manager version, deployment type (NSX-V or NSX-T/NSX), host count, transport zone configurations, logical router topology, and distributed firewall rule count. This is the TPS coverage definition document.
- Licence entitlement review — For NSX-T and NSX 4.x, confirm perpetual licence entitlements versus subscription licences. Perpetual licences can be maintained under TPS independently; subscription licences require a different approach.
- Security posture baseline — TPS onboarding includes a review of your NSX security patch currency to establish the starting baseline for ongoing security patch management.
- Coverage agreement execution — TPS agreement covering NSX Manager instances, host count, and SLA terms. Standard execution timeline is 5–10 business days.
- Broadcom maintenance non-renewal — Standard notification per Broadcom's contract terms. For NSX-V, there is no active Broadcom maintenance to cancel.
Evaluate NSX TPS Before Your Next Broadcom Renewal
Three months before your renewal is the optimal time to assess TPS — when you still have leverage with Broadcom. Our NSX specialists provide a firm quote within 48 hours.
Start NSX TPS AssessmentNSX TPS: The Right Profile
Third-party NSX support is the right decision for organisations running NSX-V (where TPS is the only supported option), organisations on NSX-T facing VCF pricing that represents a 2× or greater cost increase, and organisations with complex NSX-V environments that require 12+ months to safely migrate to NSX-T. It is also appropriate for financial services organisations where network micro-segmentation is a PCI DSS or regulatory compliance requirement and the cost of moving to unsupported infrastructure is unacceptable.
Our VMware TPS service covers both NSX-V and NSX-T/NSX 4.x across all deployment configurations. Whether you need bridge support for a planned migration or long-term TPS for a stable NSX deployment, our network virtualisation specialists provide the same 15-minute P1 response and security patch engineering that Broadcom's former customers relied on before the acquisition.