SCP deploys aSecurity aSec and reports an error: The number of CPUs of the Node of the aSecurity being edited exceeds the maximum number that can be edited
Problem Description
When deploying aSecurity on SCP, the linkage interface reports an error: The number of CPUs of the Node of aSecurity being edited exceeds the maximum number that can be edited

Effective troubleshooting steps
- Check whether the SCP service Licensing has been manually created with aSec Licensing, such as:
Root cause
aSec service Licensing is automatically created during the deployment aSecurity.
If you manually create authorization in Licensing, the deployment of aSecurity will fail.solution
When deploying aSecurity, ensure that no aSec service authorization has been manually created. If there is, Revoke it and then deploy the aSecurity.
Operation Impact Scope
Deploy aSecurity
Is this a temporary solution?
No
Original Link
https://support.sangfor.com.cn/cases/list?product_id=36&type=1&category_id=26720&isOpen=true