What Do I Do If a License Failed to Be Imported to ServiceCenter Because License Feature Verification Fails

6

【Product�?
ServiceCenter

【Version�?
3.0.5

【Fault Type�?
License fault

【Symptom�?
When a license file is imported to ServiceCenter, a message is displayed indicating that the license feature verification fails.

【Fault Locating�?
Contact frontline engineers to ask the process for applying for the license. When the license is applied for, both standard and advanced versions are selected. After the database is modified, the license is successfully imported.

【Root Cause�?
When a license is applied for, both standard and advanced versions are selected.

【Solution�?
Step 1 Use PuTTY to log in to the ServiceCenter node.
Ensure that user galaxmanager and the floating IP address of the ServiceCenter management node External API network are used to establish the connection.

Step 2 Run the following command to disable logout on timeout:
TMOUT=0

Step 3 Run the following command to enter the engineering mode:
gotoEngineerMode
Run the following command to disable logout on timeout:
TMOUT=0

Step 4 Run the following commands to switch to user dbadmin:
su �?dbadmin
Run the following command to disable logout on timeout:
TMOUT=0

Step 5 Run the following command to access the database:
gsql -U galaxmanager -d topfmdb -W GalaxManager7!

Step 6 Run the following command to update the database:
update swm.tbl_featureswitchs_info set ISSUPPORT = 0 where comptype ='SC' and version ='ALL' and virtualtype='ALL' and featurename='VERSION';

----End

Other related questions:
Solution if importing licenses fails
Solution if importing licenses fails: The failure of importing licenses may occur due to an incompatible tool version, incorrect license file, incorrect network, or incorrect gateway. To rectify the fault, perform the following operations: 1. Upgrade the tool version to the required one. 2. Ensure that the license file is correct and the SN used is consistent with that of the storage device. 3. If the PC is connected to several networks, disconnect or disable network ports that are not used for deployment. 4. Ensure that the gateway vendor is correct: Log in as user support to the file engine using the IP address of the file engine's management network port and execute cat/opt/HS/conf/product.ini to ensure that vendor is huawei and gateway is yes. If the gateway vendor remains incorrect, execute /opt/HS/factory/scripts/n8000_init.sh on each node and set the gateway vendor to HWG using the serial ports. Then restart all nodes and perform the previous operation again.

What Do I Do If a License Cannot Be Imported to ServiceCenter Because It Contains Invalid Characters
【Product�? ServiceCenter 【Version�? 3.0, 3.0.SPC2, 3.0.5, 3.0.5.SP1, 3.0.5.SP2, 3.0.5.SP3, 3.0.5.SP5, and 3.0.7 【Fault Type�? License fault 【Symptom�? When a license is imported to ServiceCenter, the error message "The request has Invalid parameter: <, >." or "The request has invalid parameter <, >" is displayed. 【Fault Locating�? The error message displayed on the page indicates that the license contains special characters such as angle brackets <>. Special characters will result in a verification failure. 【Root Cause�? The license file contains angle brackets <>. After the license is imported to ServiceCenter, the security framework verifies the license file. The verification will fail to prevent XSS attacks if special characters are found. Check the BOQ and find that the site information contains angle brackets <>. The license file generated on the ESDP platform contains the site information. As a result, the license contains special characters. 【Solution�? Temporary Solution After an ESN change (set ESN Change Type to Without revocation code) is performed on the ESDP platform, the changed ESN is still the original ESN. After the change, the new license file does not contain angle brackets <>. Final Solution This problem will be resolved in ServiceCenter 3.0.8. ----End

What should I do if I failed to import the license file into the MCU?
The possible causes are as follows: First, check the license file. For example, check whether the license file has been damaged or whether you have applied for the correct license file. Second, check the import operations. For example, check whether the license file path is correct or whether the import operations are correct. For a VP9000 series MCU, if the import still fails, upgrade the MCU to V500R002C00 or a later version. It is because versions earlier than V500R002C00 do not support universal transfer. To import a universal transfer license, you must upgrade the MCU to V500R002C00 or a later version.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top