License Status and Exceptions

After the USB Key is removed, the USB Key status is displayed as removed. The platform checks whether the current License has expired.

• If the License has expired, the status remains expired after the USB Key is removed.
• If the License has not expired, a buffer License is generated. The buffer duration varies based on the removal scenario:
  • For the first removal, the buffer License duration is 30 days.
  • For a later removal, if the interval since the last removal is less than 60 days, the expiration time of the previous buffer License is inherited. If the interval is 60 days or longer, the buffer License is updated to 60 days.
  • After the USB Key is removed and a new USB Key is inserted, the License information of the new USB Key is displayed, and the buffer License of the old USB Key becomes invalid.

In a dual-management-node environment, if one management node has multiple USB Keys inserted while the other management node has no USB Key or multiple USB Keys inserted, a USB Key fault occurs.

In a single-management-node environment, if multiple USB Keys are inserted into the management node, a USB Key fault occurs.

Note: When the USB Key status is Fault and the buffer License has expired, authorization cannot be used.

When the platform license has expired, the platform automatically redirects to the License Management page after login to remind you that the license has expired.

Note: If existing services on the platform are still running, do not reconnect hosts, image storage, or data storage to avoid affecting service operation.

• Dedicated License: When you update a license and the actual resource usage exceeds the licensed quota, most platform features are restricted. The restrictions are as follows:
  • You can log in to the platform and obtain, refresh, and view resource status.
  • Operations that reduce quotas are supported, such as deleting hosts, deleting clusters, modifying host status, and deleting virtual machines.
  • License management operations are supported, such as downloading the Request Key, uploading licenses, and deleting licenses.
  • All other operations are restricted.
  Note:

  • License authorization includes CPU sockets, CPU cores, and hosts. If actual resource usage exceeds the licensed quota for any authorization method, platform usage is restricted.
  • After the management node is shut down, it cannot be restarted. You can only log in to the management node console and update the license in command-line mode.
• Shared License: When the available quota in the license pool is insufficient, you cannot create resources, but existing resources continue to run. Contact the ZCenter administrator to add quota to the license pool or adjust the sites that use Shared Licenses.

If a site using a Shared License loses its connection to the license server, the platform temporarily uses cached license information. Check network connectivity or contact the ZCenter administrator to restore the connection.