You’ve probably seen it floating around on forums, Reddit threads, or whispered in the corridors of IT departments: “Broadcom now requires a minimum of 72 cores per host!” Panic ensues, eyebrows raise, procurement freezes… But before you start re-architecting your entire datacenter or cancelling your cluster expansion, let’s take a minute (or five) to cut through the FUD and clear things up.
Where the Confusion Starts
It all began with Broadcom introducing a 72-core minimum per order for its core-based licensing model. That’s right — not per host, not per CPU, not even per cluster — we’re talking per contract line item. And that’s a significant difference.
At the same time, there’s also the 16-core per CPU minimum, which remains in place for all core-based licenses, except VCF Edge which stays at 8 cores per CPU. Confused already? Let’s break it down clearly.
Core Concepts: Understanding the Rules
Here’s what actually applies, directly from Broadcom:
- All core-based licenses (vSphere, VCF, etc.) have a minimum of 16 cores per CPU.
- VCF Edge is an exception with only 8 cores per CPU.
-
The 72-core minimum applies only when:
- You place a new order for a core-based product.
- You renew an existing contract.
-
It does not apply when:
- You’re adding capacity to an existing contract.
- You’re correcting an error, topping up a few cores, or making adjustments.
To be clear: the 72-core rule is about per order, not per host. If you’re just buying a few more cores under an active contract, you’re not affected.
Real-World Scenarios: It’s All About the Contract
Let’s walk through a common case.
Customer A wants to order 48 cores for a new environment. The partner warns them that 72 is the minimum for a new order. However, upon reviewing the situation, they discover that the customer already has an existing contract with 16 CPUs. That changes everything. The 48 cores are now seen as additional capacity, which means no minimum applies. They can go ahead with their order.
Similarly, if you’re managing multiple contracts, you can consolidate intelligently:
- Contracts 1 and 2: 80 cores for VCF
- Contracts 3 and 4: 80 cores for vSphere
- Contracts 5 and 6: 128 cores combined
This kind of consolidation lets you align with the 72-core minimum while keeping products or business units separate if needed.
My 2 Cents
Broadcom’s move here isn’t entirely surprising. It’s more about aligning commercial processes and simplifying contract structures than targeting small customers.
Yes, it can feel like a push toward larger upfront commitments. But realistically, most enterprise environments already meet or exceed 72 cores per order without even trying. A three-host cluster with dual 12-core CPUs already gets you there.
The important thing is to not confuse licensing granularity with infrastructure design. You don’t need 72 cores per host. You don’t even need it per cluster. Just be strategic with your orders, consolidate when needed, and coordinate with your partner.
Final Thoughts
The “72-core minimum per host” myth? It’s just that, a myth. The reality is much more manageable and far less dramatic than the headlines suggest.
So next time someone drops the 72-core warning in a meeting, point them to the real rules, or better yet, your latest Broadcom contract. As always, read carefully, question assumptions, and don’t fall for marketing drama disguised as licensing changes.
Stay calm, stay licensed, and stay sharp.