InfoScale License Enforcement Feature and Unlimited SKU FAQ

book

Article ID: 1000766077

calendar_today

Updated On:

Description

General Information and Changes

  1. What is changing with the InfoScale License format?
    On May 11th, 2026, InfoScale (as part of the Cloud Software Group transition) will be discontinuing the use of permanent license keys for all versions of InfoScale 7.4.2 and newer.  As a replacement for this type of key, we will be issuing a universal, term-based license that will align to the subscription end-date for each customer's entitlement.
  2. What is required to adopt the new license model?
    For existing deployments, subscription customers will be required to download the new term-based license file from the InfoScale licensing portal. After obtaining the new license, you will need to install one of the following cumulative updates for Linux or Windows:  7.4.2 U9, 8.0 U6, 8.0.2 U8 or 9.0.7 (depending on your base installation). During the configuration step for the update, you will be prompted for the path to the new license file. Beginning with InfoScale 9.2, the updated license modules will be included with the GA binaries.
  3. When will the new InfoScale updates be available for download?
    The latest InfoScale patches will be made available in conjunction with the new term-based license on May 11th, 2026.
  4. Which Operating Systems and deployment methods will be supported initially?
    At the time of GA,  we plan to support the following OS combinations:
 Supported on May 11thSupported Post GA
LinuxRHEL 8, 9 & 10 + SLES 15RHEL 7, SLES 12, Rocky & OEL
Windows2019. 2022 & 20252016
DeploymentCPI (LNX) VPI (Win) Unattended (Win)YUM & Ansible

General Changes and Information (continued)

  1. Will license enforcement extend to UNIX versions?
    Yes,  UNIX will eventually be subject to the same term license policy, however the release of the UNIX patches is scheduled for mid-July 2026.  The universal license key will also be applicable to Solaris and AIX deployments.
  2. Can I use YUM or Ansible to deploy the updated patches and license key?
    Yes, however support for the license file and product updates will be released subsequent to the initial launch and therefore not part of the GA on May 11th (we anticipate by June 30th, 2026 to have this qualified) That said, If you wish to leverage our Ansible modules to update your hosts, please refer to the guide InfoScale™ Installation, Upgrade, and Configuration Using Ansible for more details on how to configure our InfoScale Playbooks.
  3. What happens if I have not yet converted my licenses to subscription?
    Access to all forthcoming patches for versions 7.4.2 or newer as well as major releases will be available to existing perpetual customers with active maintenance.  In order to get these updates you will be required to convert to the new license format. This license will expire at the end of your existing maintenance term.
  4. What will happen to my 7.4.1 or older deployments?
    There will be no changes to the license format for versions 7.4.1 or older. Nor will there be any further updates or patches released. These versions will continue to be supported in accordance with our standard product life cycle.  InfoScale Product Life Cycle
  5. How do I register with the new license and download portal?
    All active subscription and maintenance holders will automatically receive an email notification with the necessary instructions to register for the new portals. These notifications were sent at the end of April, 2026.
  6. What is the purpose of the InfoScale License Enforcement feature?
    The feature introduces controlled enforcement of licenses while ensuring customers have sufficient time to renew without service disruption. It is intended for customers and system administrators performing new deployments or upgrades.
  7. What is the benefit of the InfoScale License Simplification?
    InfoScale has merged the complexity of multiple license types, core counts, and platform-specific entitlements into a single license file for all product variants. Key benefits include:
      1. Ease of Management: A single file simplifies installation, renewal, and tracking.
      2. Reduced Complexity: Eliminates the need to manage different licenses for various platforms (Linux, Windows, Unix) or product tiers.
      3. Future-Proofing: The unified model can accommodate future product enhancements and packaging changes. 
  8. What can I expect when my subscription term approaches the expiration date?
    90 days prior to your license expiration, you will begin to see an increased number of log messages indicating that your subscription is close to its expiry date. Upon reaching the term end-date,  you will be required to renew your subscription or discontinue usage of the product. If after the expiry date (and subsequent 60 day grace period) you do not renew your license, an ordered shutdown of InfoScale services and daemons will commence.
  9. How does the new licensing behavior differ from the old one?
    Previously, licenses were non-enforcing, only generating notification messages upon expiry while product functionality continued indefinitely. The new behavior actively enforces the license lifecycle, impacting functionality and transitioning the product through Warning, Grace, and Enforced states.
  10. What can I expect when one of my systems enters Enforced Mode (after the grace period is exceeded)?
    I/O operations for existing workloads will be blocked.
      1. For resources managed by Veritas Cluster Server (VCS), all resources will undergo a graceful shutdown.
      2. For resources not managed by VCS, Veritas Volume Manager (VxVM) will stop the vxconfigd daemon and disable access to VxFS file systems.
  11. What if I am using Keyless licensing?
    Keyless licensing is also being deprecated with the new enforcing model.  
  12. What tools are being made available to help manage this transition?
    We strongly encourage users to deploy our License Management Service (LMS) as it will offer a centralized way to not only report on your utilization, but serve as the single point of activation for new license deployments.  Users will soon be able to use our Luminos Control Plane to manage patching, upgrade and license deployment operations. Both Luminos as well as LMS will be available on the InfoScale download portal.
  13. What is changing with the InfoScale variants/SKUs?
    Beginning on May 11th, 2026, InfoScale will be available as a subscription-only solution, exclusively using the Enterprise variant.  All other SKUs, including Foundation, Storage and Availability will no longer be transactable. 
  14. Will I still be able to deploy the different variants of InfoScale?  Absolutely,  we are not discontinuing the technology, but rather the individual transactable SKUs. This means all existing storage layouts, cluster topologies and DR configurations will not be affected.  Users however, will now be eligible to deploy on any platform with any variant in an unlimited capacity, regardless of the version you currently utilize.
  15. Does this also include the Kubernetes versions?
    Yes, InfoScale for Kubernetes and OpenShift VE will be included with the new unlimited Enterprise SKU.
  16. How can I access this new entitlement?
    At the time of renewal, you will be converted to the new InfoScale Enterprise SKU/entitlement and this will be visible in the InfoScale license portal. 
  17. How do I access my legacy licenses and binaries?
    If you have active maintenance, license keys for versions 7.4.1 and older will require a Customer Service case. A Technical Support case will be required to access binaries in the download portal that do not require the new keys.
  18. What is included with the new unlimited InfoScale SKU?
    All features, variants, supported versions and platform options will be included with the new unlimited Enterprise SKU in addition to world class technical support.  Entitlement will no longer be capped based on your core count, provided you have maintained an active subscription. 
  19. Will I still be required to track the Core Plus Co-efficient with this new model?
    No,  the Core Plus program will be discontinued as of May 11th, 2026.  Under the new InfoScale Enterprise program, entitlement will be unlimited (unless otherwise specified by InfoScale or Cloud Software Group management). Utilization however will still be tracked based on your compute footprint (regardless of the core type) for the purposes of reporting. This can be achieved via the InfoScale LMS (License Management Service). 
  20. Will I have to install a new license when I renew my subscription?
    Yes, the subscription end date is part of the license. Each time you renew, you will need to update your license. We recommend using License Management Service (LMS) to simplify this process.

License Management and Logging

  1. How can I list the details of the installed license?
    You can use the vxlicrep CLI command.
      1. Linux/Unix: # /opt/VRTS/bin/vxlicrep
      2. Windows: c:\> vxlicrep.exe
        The output primarily displays the license type, features enabled, Start & Expiry date, and Current enforcement state.
  2. What is the frequency of license-related log messages?
      1. Warning period logs: once per day
      2. Grace period logs: once per day
      3. Enforced mode logs: on every restricted operation
  3. What is the name and function of the license logging service?
    The service name is infoscaleLicense
    . It is a new logger service responsible for monitoring license compliance on the cluster nodes. On Linux/Unix, license messages are logged in /var/log/messages.
  4. How does the license service synchronize licenses across cluster nodes?
    The license service synchronizes the Blob key that has the later expiration date, ensuring all nodes in an InfoScale cluster managed by VCS have the same expiry date. It checks and syncs the license every 24 hours (currently available on Linux only).

Installation and Upgrade

  1. What is the recommended method for installing or updating licenses?
    The recommendation is to use the automated installer (CPI for Linux/Unix or VPI for Windows) to fully install the licenses on all cluster nodes. Manually installing licenses using utilities like vxlicinstupgrade requires repeating the operation on all nodes and manually restarting all InfoScale services.
  2. Will I require downtime to install the new license keys?
    No, the license files themselves will not require downtime to install, however depending on the type of update and the variant of InfoScale deployed, minimal downtime may be necessary.
  3. What are the different types of upgrade methods supported?
    InfoScale supports three main upgrade methods using the automated installer (CPI/VPI):
      1. Full Upgrade (Offline Upgrade): Requires full application downtime, with all nodes upgraded in one window.
      2. Rolling Upgrade (Cluster Rolling Upgrade): Minimal or no application downtime, where nodes are upgraded one at a time while applications run on the remaining nodes.
      3. Phased Upgrade: Components are upgraded in stages, offering a controlled and segmented approach.
  4. What should I do if the InfoScale upgrade fails to start services due to a missing license?
    You should download the latest version of our universal license or contact your Account team to obtain a valid Subscription-based license key. Once you have the license, use the CPI installer with the license option (
    \# /opt/VRTS/install/installer -license) to install the key, and then start the InfoScale services.

Troubleshooting and Best Practices

  1. What should I do if one or more cluster nodes are unreachable during license installation?
    Install the license on those nodes manually once they are up and running.
  2. What is a common cause for the vxconfigd daemon being down on Linux/Unix?
    License expiration is a common cause. The recovery step is to install the license using the menu-driven installer (installer –license).
  3. What are some best practices for managing InfoScale licenses?
      1. Renew licenses well before expiry.
      2. Monitor license status regularly.
      3. Automate license deployment during upgrades.
      4. Maintain time synchronization across clusters.
      5. Deploy the LMS (License Management Service) to centrally maintain your license footprint.
  4. Who should I contact for more details regarding the new SKU and license enforcement process?
    Please contact your ATS or Account team representative for further information regarding your new Enterprise entitlement and term-license program.

Issue/Introduction

This article covers the frequently asked questions (FAQ) regarding the InfoScale License Enforcement Feature and Unlimited SKU. A high level overview of the license enforcement feature is available here.