12.5 License Operations: State, Assignment, Reclamation, and Expiry
Key Takeaways
- Objective 2.4 breaks licensing into five operational tasks: identify current state, assign, reclaim and unassign, inspect available licenses, and verify expiration.
- Seamless licensing applies license actions automatically for internet-connected clusters, while manual license management uses a downloaded and uploaded license file for dark sites.
- Reclaiming a license returns it to the available pool so it can be assigned elsewhere, which is the required step before decommissioning or destroying a cluster.
- Destroying a cluster without first reclaiming its licenses strands that entitlement and requires Nutanix support to recover it.
- Some Nutanix products and features do not require a license at all, so a license is not the explanation for every unavailable capability.
12.5 License Operations: State, Assignment, Reclamation, and Expiry
Objective 2.4 is unusually specific. It does not ask you to explain licensing philosophy — it lists five tasks: identify current license state, assign/reclaim/unassign licenses, inspect available licenses, verify licensing expiration, and identify the correct license by use case. Section 3.3 covered the tiers and what they contain; this section covers the operations.
Where Licensing Is Managed
Licensing is administered through the License Manager, reached from the Nutanix Support Portal and from Nutanix Central, and license state is visible from Prism. The mental model:
- Your account holds an entitlement pool — the licenses you have purchased.
- Licenses are assigned from that pool to clusters.
- Reclaiming returns a license to the pool so it can be assigned somewhere else.
Because the pool is the account-level construct, "do we have a spare license?" is answered in the License Manager, not on any individual cluster.
Identifying Current License State
The licensing page in Prism reports what the cluster is running under:
| What you read | Why it matters |
|---|---|
| Tier in use — Starter, Pro, or Ultimate | Determines which features are permitted |
| Add-ons applied — Flow, NUS, NCM and others | Add-ons are licensed separately from the NCI tier |
| Compliance status | Whether the cluster is correctly licensed for what it is doing |
| Expiration date | The renewal deadline |
A cluster can drift out of compliance without anyone doing anything wrong — most commonly by being expanded. Licensing is metered by capacity, so adding nodes to a cluster can push it beyond what its assigned license covers. Checking license state after an expansion is the habit to build.
Two Ways to Apply License Actions
This is the same split you saw for LCM updates in section 8.3, and for the same reason.
Seamless licensing — for connected clusters
Where the cluster can reach Nutanix over the internet, license actions are applied directly. You perform the action and the cluster and portal reconcile between themselves. Assigning, reclaiming, and unlicensing a cluster are all handled this way, with no files to move.
Manual license management — for dark sites
Where there is no outbound connectivity — the dark site case introduced in section 8.3 — licensing becomes a three-step file exchange:
- Download a cluster summary file from Prism.
- Upload it to the Support Portal, which generates a license file for that cluster.
- Download the license file and apply it in Prism.
[!TIP] The recognition point: connectivity determines the workflow. A question describing an air-gapped or dark-site cluster is describing manual license management; a question about a normally connected cluster is describing seamless licensing.
Assign, Reclaim, and Unassign
Assigning allocates a license from the pool to a cluster, which is what happens when a cluster is first licensed or when it is expanded and needs more capacity covered.
Reclaiming returns a license to the pool. The situations that require it:
- Decommissioning a cluster. The entitlement should go back so it can be used elsewhere.
- Moving a license between clusters. Reclaim from one, assign to the other.
- Downgrading a tier, where a cluster no longer needs Ultimate.
- Rebuilding a cluster, where the licence must be released before the cluster is destroyed.
[!WARNING] Reclaim licenses before destroying a cluster. This is the single most examinable point in the objective, and the most costly one to get wrong in real life. A destroyed cluster cannot return its licenses, so the entitlement is stranded and recovering it becomes a support request. The blueprint names "Reclaiming Licenses when Destroying a Cluster" as its own reference for exactly this reason.
Unlicensing a cluster removes its license assignment entirely, returning the cluster to its unlicensed state and the license to the pool.
Inspecting Available Licenses and Verifying Expiration
Available licenses are inspected in the License Manager, which shows what has been purchased, what is currently assigned and to which clusters, and what remains free to assign. This is what you consult before planning an expansion — discovering mid-project that no entitlement is available is an avoidable delay.
Expiration is visible both per cluster in Prism and across the estate in the License Manager. Checking it matters because licenses expire on their own schedule, independent of anything happening on the cluster, and an expiry that passes unnoticed is a compliance problem discovered at the worst time.
License tags
Tags let an organization label licenses with its own metadata — a business unit, a project, a cost centre — so that entitlement can be tracked and attributed across a large estate. They are an administrative convenience rather than a technical control, but the blueprint names them, so recognize what they are for.
Not Everything Needs a License
The blueprint closes Objective 2.4 with a reference titled "Products that do not require a license," and it is there to correct a common assumption. Some Nutanix products and capabilities carry no separate license — several of the Objective 1.3 tools, for instance, are free downloads from the Support Portal.
The exam-relevant consequence: do not reflexively answer "a license is required" when a capability is unavailable. The cause may equally be the hypervisor in use, the cluster size, an unmet configuration prerequisite, or an unsupported version combination.
Task Summary
| Task | Where | Note |
|---|---|---|
| Identify current license state | Prism licensing page | Tier, add-ons, compliance, expiry |
| Inspect available licenses | License Manager | The account-level entitlement pool |
| Assign a license | Seamless, or manual for dark sites | Needed after expansion |
| Reclaim / unassign | Seamless, or manual | Always before destroying a cluster |
| Verify expiration | Prism and License Manager | Independent of cluster activity |
| Choose the right license | By use case | NCI tier plus add-ons such as Flow, NUS, NCM |
A cluster is being decommissioned and its hardware repurposed. What must be done with its licenses, and when?
An air-gapped cluster with no outbound internet connectivity needs a license applied. Which workflow is used?
After adding three nodes to a cluster, an administrator finds it reported as out of licensing compliance even though nothing else changed. What is the most likely reason?