SSP 5.1.2 and the License Hub: What the Licensing Shift Actually Means
SSP 5.1.2 ships License Hub — a centralized licensing layer for vDefend and Avi that replaces 25-character keys with subscription files. Here’s what’s changing and what it requires if you’re planning an SSP 5.1.2 upgrade.
SSP 5.1.2 went GA on May 12, 2026. On the surface it’s a focused release — the installer build increments, and License Hub for VMware vDefend and Avi Load Balancer is the headline addition. But the licensing change it introduces is a meaningful architectural shift, not a routine maintenance item, and it’s worth understanding what it does before your next SSP 5.1.2 upgrade lands it in scope.
What License Hub is
License Hub is a new management layer that sits between Broadcom’s licensing infrastructure and your NSX Manager instances. Instead of entering a 25-character key into each NSX Manager individually, you register NSX Manager instances with a central License Hub and assign licenses from there. A single License Hub instance handles up to 120 vDefend and Avi endpoints.
The model supports two operating modes. In connected mode, License Hub communicates with VMware Avi Cloud Console for usage reporting. In disconnected mode, you submit usage data manually — required every 180 days. If your environment is air-gapped or your security policy limits outbound SaaS connectivity, disconnected mode is the path.
The key format change
The shift from 25-character keys to digitally signed subscription files is the part with the most operational weight. The old keys don’t go away immediately — existing licenses can be migrated through the Broadcom Support Portal — but starting with SSP 5.1.2, subscription-based license files are the required format. 25-character keys are not accepted.
That’s a hard dependency: SSP 5.1.2 with VCF 9.1 requires License Hub 5.1.2 installed and registered before the upgrade completes. If you’re planning a VCF 9.1 rollout, SSP 5.1.2 is a prerequisite, not an optional follow-on.
What to do now
If you’re not planning an SSP 5.1.2 upgrade yet, License Hub is still worth deploying — particularly if you want to consolidate license visibility across multiple NSX Manager instances. The unified usage view across vDefend and Avi endpoints is genuinely useful if you’re running a multi-site or multi-tenant environment.
If you are planning an SSP 5.1.2 or VCF 9.1 upgrade, confirm SSP 5.1.2 is in your pre-upgrade checklist and start the key migration through the Broadcom Support Portal before your maintenance window. Migrating keys under a deadline is avoidable friction.
The 180-day usage submission window in disconnected mode is long enough that it won’t feel urgent the day you deploy, but short enough to miss if the task doesn’t have an owner. Set a reminder now for 150 days out and assign it.
Further reading
- SSP 5.1.2 Release Notes — Broadcom TechDocs
- KB 414369 — NSX/SSP Interoperability Issues — Broadcom Knowledge Base