Understanding License Expiration Date Discrepancies in VCF 9.0 Licensing 2.0

Products

• VCF Operations

Issue/Introduction

• This article explains the expected architectural behavior regarding license expiration date discrepancies observed between the VCF Business Services Console and the on-premises VCF inventory.
• License expiration date in VCF Business Services Console differs from the date shown in the local VCF inventory.

Environment

VCF Operations 9.x

Cause

This is an expected architectural behavior within the VCF 9.0 Licensing 2.0 framework. The Business Services Console displays the absolute expiration of the subscription, while the on-premises inventory reflects the Time-To-Live (TTL) validity period of the locally assigned entitlement file.

• Example: VCF Business Service Console shows expiration in 2031, while on-premises inventory shows a closer date (e.g., 2027).

Resolution

• No break-fix remediation is required for this discrepancy.
• In VCF 9.0, on-premises entitlements require periodic consumption data (usage) uploads to the Cloud License Manager to remain active.
• This refresh cadence is enforced by the TTL validity period. As usage reports are uploaded to the VCF Business Services Console, a newly signed entitlement file is generated and pushed to the on-premises License Manager, which automatically extends the local expiration date.
• If the environment is in "Connected (Automated)" mode, these uploads happen automatically.
• If the environment is in "Disconnected (Manual)" mode, ensure manual usage uploads are executed prior to the local TTL expiration to retrieve and import the refreshed entitlement file.

Additional Information

For more information on VCF licensing operations, please review the VCF Documentation. For defects and enhancements, subscribe to this article here to be updated on fix status.