I. Authorization Change Description

1. To accelerate the HCI + SCP integration process, starting from SCP version 6.11.2, authorization is only supported through SCP for unified management. Standalone HCI authorization is no longer supported. Any scenarios involving authorization changes must follow the new authorization method (such as new cluster creation, capacity expansion, etc.). This change does not affect existing customers in upgrade or renewal scenarios.
2. Authorization is based on CPU core segments.
Authorization licenses issued for overseas markets are collectively referred to as Pro Specification Authorization.
3. SCP version 6.11.2 and later versions also support importing authorization serial number files from older versions. When older authorization serial numbers containing aSV, aNET, and aSEC with original CPU core count authorization are imported into SCP version 6.11.2 or later, they will be automatically recognized as Pro Specification Authorization.

II. Applicable Scenarios

1. New Cluster Creation
⦁SCP deployment is mandatory.
⦁The new authorization method only takes effect on SCP and cannot be used on HCI directly. The new license serial number cannot be imported on HCI.
⦁For a standard 3-node or above cluster (same applies for 2+1 scenario), the delivery process compared to previous versions requires an additional step: SCP must be deployed, and authorization must be issued from SCP to HCI.
⦁Clusters can be created and VS storage can be configured without authorization, and SCP VMs can be started normally to perform the authorization operation.
2. Upgrading Existing Clusters
1. Older version HCI (without SCP): The original authorization method remains unchanged.
2. Older version SCP upgrade: Existing authorizations will be automatically and free of charge converted to Pro version after the upgrade.
3. Expanding Existing Clusters
1. For older version cluster expansion: Existing node authorizations in the cluster will be free of charge converted to Pro version. New nodes to be added require authorization ordered under the new method, and the expansion must use the new SCP version (6.11.2) to issue the new authorization to HCI for expansion.
2. Legacy versions: Versions before 5.8.5, 590, 6.2.10, 6.7.30, and 6.8.80 do not support being managed by SCP. These versions must be upgraded to a version that supports SCP management before they can be expanded.
4. Replacing Hosts in Existing Clusters
No impact.
5. Cluster Expansion After Using New Authorization
When expanding a cluster, a new specification check will be added. If the cluster only has 1~32C authorization, expanding a single-CPU 64C host into the cluster will not be allowed. This means additional checks are required before expansion.
Cluster Host Replacement After Using New Authorization
When replacing hosts in a cluster, a new specification check will be added. If the cluster only has 1~32C authorization, replacing with a single-CPU 64C host will not be allowed. This means additional checks are required before replacement.
6. Patching
No change - existing mechanism remains unchanged.
7. Technical Support
No change - existing mechanism remains unchanged.
8. Renewal
No change - existing mechanism remains unchanged.