HUAWEI CLOUD Stack 6.5.0 License Guide 04
HUAWEI CLOUD Stack 6.5.0 License Guide 04
HUAWEI CLOUD Stack 6.5.0 License Guide 04
6.5.0
License Guide
Issue 04
Date 2021-03-24
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Overview
This document describes how to apply for and load a HUAWEI CLOUD Stack license and
also provides troubleshooting methods for a license.
Intended Audience
This document is intended for:
Technical support engineers
Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Indicates an imminent hazardous situation which, if not avoided, will
result in death or serious injury.
Indicates a potentially hazardous situation which, if not avoided, could
result in serious injury or death.
Indicates a potentially hazardous situation which, if not avoided, may
result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not avoided, could
result in equipment damage, data loss, performance deterioration, or
unanticipated results.
NOTICE is used to address practices not related to personal injury.
Calls attention to important information, best practices and tips
NOTE is used to address information not related to personal injury,
equipment damage, and environment deterioration.
Change History
Issue Date Description
04 2021-03-24 This issue is the fourth official release.
Changed the license email to Huawei TAC
email.
03 2019-08-30 This issue is the third official release.
Optimized the document.
02 2019-06-14 This issue is the second official release.
Added description and modified the link to the
reference document in 2.5.2 FusionStorage
OBS.
01 2019-05-30 This is the first official release.
Contents
5 Appendix ...................................................................................................................................... 51
5.1 License Control Items and Scope ............................................................................................................................... 51
5.1.1 Resource Pool & Basic Cloud Services ................................................................................................................... 51
5.1.2 Cloud Management .................................................................................................................................................. 52
5.1.3 Device Monitoring ................................................................................................................................................... 53
5.1.4 Third-Party Management ......................................................................................................................................... 54
5.1.5 Storage Services ....................................................................................................................................................... 56
5.1.6 DR and Backup Services ......................................................................................................................................... 57
5.1.7 Security Services ..................................................................................................................................................... 59
5.1.8 Big Data Services .................................................................................................................................................... 60
1 Overview
1.1 Introduction
A license is an entitlement that defines the number, functions, and validity period of a product.
You can use the equipment serial number (ESN) of a product to activate its license and
generate the license file. After loading the license file to the product, you can obtain the
number of the products and the permission to use them.
1.3 Precautions
Table 1-2 lists the HUAWEI CLOUD Stack products requiring licenses and related
precautions.
Table 1-2 HUAWEI CLOUD Stack products requiring licenses and precautions for loading
licenses
1.4 Help
Please contact the overseas TAC at https://e.huawei.com/en/service-hotline-query.
Contact Huawei technical support.
2 Obtaining ESNs
----End
----End
----End
Obtaining the ESN for VM installation: Record the unique ESN of the VM that
is displayed.
Step 2 Record the server ESN on the ESN generation page that is displayed.
In the physical machine scenario, the ESNs of both the physical machine and VM are displayed. In the
VM scenario, only the ESN of the VM is displayed.
For the active and standby physical machines, you need to log in to eSight on the active and standby
servers to obtain the ESNs, and separate the ESNs with commas (,) when applying for a license for the
two-node cluster.
For the active and standby VMs, you can directly obtain the ESNs of the active and standby VMs on the
VM tab page.
----End
----End
OBS is automatically installed by using HUAWEI CLOUD Stack Deploy. Therefore, you need to
prepare the required license in advance. Enter the SN of any purchased storage node for ESN in the
OBS Service sheet of HUAWEI CLOUD Stack 6.5.0 LLD Template in HUAWEI CLOUD Stack 6.5.0
Integration Design Suite. The SN is used as the ESN of the storage cluster after installation, which is the
same as the serial number on the DeviceManager homepage. (Click in the upper right corner and
choose Cluster Details from the drop-down list. In the displayed dialog box, view SN of the
FusionStorage OBS product.)
You only need to obtain the ESNs of the backup server and backup proxy that functions as the standby
node. The backup manager and backup server of eBackup have independent GUIs. To obtain the ESNs,
log in to the backup server GUI.
In the displayed Obtain ESN dialog box, the MAC Address drop-down list shows the
MAC addresses of the NICs of backup servers. Choose the MAC address of one or
several NICs to generate an ESN.
If the backup server has multiple NICs, select any MAC address. If the NIC of the selected MAC
address is faulty, the license may become invalid.
You are advised to use an ESN corresponding to multiple MAC addresses of NICs to apply for a
license file, reducing the probability of license file invalidity due to NIC faults.
If a license becomes unavailable after the MAC address of a NIC is changed, rectify the fault by
referring to section 3.5.4 Changing an ESN.
Obtaining an ESN for a active and standby two-node system
− If the current system is a two-node one, the method for obtaining ESNs is as
follows:
In the displayed Obtain ESN dialog box, the MAC Address drop-down lists show
the MAC addresses of the NICs of active and standby backup servers. Choose the
MAC address of one or several NICs to generate an ESN.
If the backup server has multiple NICs, select any MAC address. If the NIC of the selected MAC
address is faulty, the license may become invalid.
You are advised to use an ESN corresponding to multiple MAC addresses of NICs to apply for a
license file, reducing the probability of license file invalidity due to NIC faults.
If a license becomes unavailable after the MAC address of a NIC is changed, rectify the fault by
referring to section 3.5.4 Changing an ESN.
− If the current system is a single-node one and will be configured into a two-node
one, you need to obtain ESNs of the active and standby nodes at the same time.
The method for obtaining ESNs of the active node is the same as Obtaining an ESN
for a single-node system. The method for obtaining ESNs of the standby node is as
follows:
i. Use PuTTY to log in to the backup proxy.
Default account: hcp. Default password: PXU9@ctuNov17!.
ii. Run the su root command and enter the password of user root to switch to
user root.
The default password of user root is Cloud12#$.
iii. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
After you run this command, the system continues to run when no operation is performed, resulting in a
risk. For security, run exit to exit the system.
iv. Run the cd /opt/huawei-data-protection/ebackup/sbin/ command to go to
the directory storing the eBackup script.
v. Run the sh generateESN.sh command to obtain the mapping between MAC
addresses and ESNs.
----End
Log in to the active and standby eReplication nodes and perform the following steps to obtain the
ESNs:When applying for a license, separate the ESNs of the two nodes with a comma (,), and then enter
the ESNs and apply for a license.
Step 1 Use a remote connection tool, such as PuTTY, to log in to the operating system where the
OceanStor BCManager eReplication software is deployed as user DRManager (the default
password is Huawei@CLOUD8).
Step 2 Run the su - ICUser command to switch to user ICUser (the default password is
Huawei@CLOUD8).
Step 3 Run the cd /opt/BCManager/Runtime/LegoRuntime/tools;sh esn.sh command to obtain
the ESN of the current node.
----End
----End
----End
Procedure
Step 1 Open a browser, enter https://Northbound floating IP address:31945 in the address bar and
press Enter to log in to the management plane of Agile Controller-DCN.
Step 2 Choose Maintenance > Collect Information > Collect ESN Information from the main
menu.
Step 3 On the Collect ESN Information page, select the product and click Collect.
Step 4 In the ESN list, click the .zip package of the collected ESN to download the file to the local
PC.
The ESNs are in the file in the .zip package, and the ESNs of different nodes are separated by
commas (,).
In the DR scenario, you need to log in to the primary and secondary management planes to obtain
the corresponding ESNs, and combine the two ESNs using a comma (,) to separate them. If the ESN
of only one cluster is used to apply for a license file, the cluster license may fail to be used.
----End
3.1 Overview
Table 3-1 lists the operations for applying for a license.
Table 3-2 Products whose license files need to be upgraded after an R version upgrade
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Activation > Entitlement Activation.
Step 3 Enter Huawei Contract No..
Step 4 Click Search & Refresh.
Step 5 Select the entitlement IDs to be activated and click Next.
Step 6 Activate entitlement IDs.
Activate one entitlement ID.
Set ESN for the product.
Activate entitlement IDs in batches and bind the entitlements to the same ESN.
a. Select Add Entitlement.
b. Enter Huawei Contract No..
c. Click Search & Refresh.
d. Click OK.
e. Set the same ESN for the entitlements selected.
Step 7 Click Next.
Step 8 Click Activate License.
Step 9 Click Download to obtain the license file.
----End
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Activation > Password Activation.
Step 3 Activate passwords.
Activate one password.
Enter Password.
Activate passwords in batches.
a. Click Add.
b. Set multiple activation passwords.
Step 4 Click Next.
Step 5 Set ESN for the product.
Step 6 Click Next.
Step 7 Click Are you sure you want to activate the license?
Step 8 Click OK.
Step 9 Click Download to obtain the license file.
----End
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Commissioning and Maintenance > Version
Change.
Step 3 Select I have read and agree to the above.
Step 4 Click Next.
Step 5 Set Input mode.
If you set it to License Document, upload the original license file.
If you set it to Equipment (Node), you can find and select the device (node) to be
upgraded by using the ESN.
If you set it to Batch Operate, you can activate license files in batches.
Step 6 Select Target Product Name and Target Product Version.
If Target Product Version is empty, check whether Subscription and Support (SnS) has expired.
If yes, renew the SnS.
If no, please contact the overseas TAC at https://e.huawei.com/en/service-hotline-query.
Table 3-4 Increment information about part numbers of an enterprise temporary license for each
product
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Commissioning and Maintenance > Commissioning
License Download.
Step 3 Set parameters as required.
Table 3-5 describes information about license templates.
Table 3-6 Operations performed when you are applying for a license
Application Scenario Operation Description
Resources defined in one contract are Split one entitlement into multiple ones. Bind
allocated to multiple licenses. each new entitlement to different devices to
generate multiple licenses.
For details, see 3.5.2 Splitting an Entitlement.
Resources defined in multiple contracts Merge multiple entitlements into one and bind
are combined to one license. it with one set of equipment to generate one
license.
For details, see 3.5.3 Entitlement Merging.
The license cannot be used because For details, see 3.5.4 Changing an ESN.
the ESN is incorrect.
The original license cannot be used
because the ESN has been changed.
The obtained license is incorrect. Roll back the license to the status before the
license is activated or upgraded. This operation
needs to be approved by regional offices.
For details, see 3.5.5 Rolling Back a License.
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose Order Management > Entitlement Management.
Step 3 Enter Huawei Contract No..
Step 4 Click Search.
Step 5 Select the target entitlement ID.
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Commissioning and Maintenance > ESN Change >
Product Hardware Change.
Step 3 Set ESN Change Type to Without Revocation Code, and set other parameters as required.
Step 4 Click Select Equipment (Node).
Step 5 Set the original ESN and specify New ESN.
Step 6 Click Submit.
----End
Procedure
Step 1 Log in to ESDP using the obtained account.
Step 2 In the navigation tree, choose License Commissioning and Maintenance > Commercial
License Rollback > Permanent License Rollback.
Step 3 Set Rollback Type to Rollback Without Revocation Code, and set other parameters as
required.
Step 4 Click Select Equipment (Node).
Step 5 Use the ESN to find and select the equipment (node) whose license is to be rolled back.
Step 6 Click Submit.
----End
4 Loading a License
3. Click Save.
4. Allocate resources.
a. In the row in which NE Type is OpenStack OM, click Allocate Resources in the
Operation column.
The Allocate Resources dialog box is displayed.
b. Input Quantity.
Quantity indicates license resources allocated to another NE. For example, if the target NE is
FusionCompute which has 10 servers, and each server has two CPUs, enter 20 in the box under IaaS
Cloud Suite Standard Edition.
IaaS Cloud Suite Standard Edition can be used for FusionSphere compute virtualization (KVM
virtualization or bare metal service).
OpenStack is used only for FusionSphere compute virtualization (KVM virtualization or bare metal
service).
c. Click OK.
----End
Step 4 In the Open dialog box, select a license file and click Open.
Step 5 Click Upload, as shown in Figure 4-1.
When you initially load a license file, the default value is Full and the setting cannot be changed.
----End
Step 3 Click on the eSight license import page, select a license file, and click Upload.
Table 4-2 Effective mode of the imported license in different eSight versions
Version Description
V300R008C00S If the imported license does not include functional module changes
PC100 and later but includes only resource item quantity changes, or the license
versions corresponding to the functional module is added or deleted but
eSight does not have the corresponding functional module installed,
eSight does not need to be restarted and the imported license takes
effect immediately.
If the imported license includes functional module changes (licenses
of the corresponding functional modules are added or deleted) and
eSight has the corresponding functional modules installed, perform
an operation in the dialog box that is displayed.
− If you click Yes, eSight automatically restarts within one minute.
After eSight restarts, the imported license takes effect and
functional modules without licenses are not started.
− If you click No, eSight does not restart and the license import is
terminated. The existing license is still used.
NOTE
If eSight has the application management component installed, you are advised
to restart eSight to improve the application management component performance
when the imported license includes the eSight application management license
(instance) and the quantity is greater than 500.
V300R007C00S If eSight has the application management component installed, you are
PC502 and advised to restart eSight to improve the application management
V300R007C00S component performance when the imported license includes the eSight
PC502 to application management license (instance) and the quantity is greater
Version Description
V300R008C00 than 500. Otherwise, you do not need to restart eSight.
versions
V300R006 and After the license is imported, eSight automatically restarts regardless of
V300R006 to whether the imported license function items include the report
V300R007C00S component.
PC502 versions
V300R006 and eSight automatically restarts if the imported license function items
earlier versions include the eSight Reporter, eSight Network Report Template Package,
or eSight Storage Report Template Package.
----End
The effective mode of the imported license varies depending on the eSight version. For details,
see Table 4-3.
Table 4-3 Effective mode of the imported license in different eSight versions
Version Description
V300R008C00S If the imported license does not include functional module changes
PC100 and later but includes only resource item quantity changes, or the license
versions corresponding to the functional module is added or deleted but
eSight does not have the corresponding functional module installed,
eSight does not need to be restarted and the imported license takes
Version Description
effect immediately.
If the imported license includes functional module changes (licenses
of the corresponding functional modules are added or deleted) and
eSight has the corresponding functional modules installed, perform
an operation in the dialog box that is displayed.
− If you click Yes, eSight automatically restarts within one minute.
After eSight restarts, the imported license takes effect and
functional modules without licenses are not started.
− If you click No, eSight does not restart and the license import is
terminated. The existing license is still used.
NOTE
If eSight has the application management component installed, you are advised
to restart eSight to improve the application management component performance
when the imported license includes the eSight application management license
(instance) and the quantity is greater than 500.
V300R007C00S If eSight has the application management component installed, you are
PC502 and advised to restart eSight to improve the application management
V300R007C00S component performance when the imported license includes the eSight
PC502 to application management license (instance) and the quantity is greater
V300R008C00 than 500. Otherwise, you do not need to restart eSight.
versions
V300R006 and After the license is imported, eSight automatically restarts regardless of
V300R006 to whether the imported license function items include the report
V300R007C00S component.
PC502 versions
V300R006 and eSight automatically restarts if the imported license function items
earlier versions include the eSight Reporter, eSight Network Report Template Package,
or eSight Storage Report Template Package.
----End
Step 5 After the license file is uploaded, click Update and select the license file to be activated from
the File Info drop-down list box.
Step 7 After the license is activated, view the license control details of each cloud service in the
Control Details area.
----End
Step 4 In the above dialog box, choose the license file and click Open.
----End
Step 3 In the dialog box that is displayed, select the license file, and then click Open.
----End
Step 7 Select the local license file of FusionGuard and click Upload.
Step 8 View the license information.
After the license file is loaded successfully, choose Security > License Management. View
license information in License Information.
----End
----End
2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the
FusionStage OM zone console.
Step 2 On the license interception page, click here.
Step 3 On the License Management page, click Import License.
When you initially load a license file, Update mode is Full by default and the setting cannot be
changed.
After the license file is loaded successfully, choose > License Management to view the
license information.
----End
Precautions
Error License Loading Policy
The file coding format is License loading is forbidden.
Procedure
Step 1 Open a browser, enter https://Northbound floating IP address:31943 in the address bar, and
press Enter to log in to the control plane of Agile Controller-DCN.
Step 2 After successful login, choose System > System Settings > License Management > License
File and click Upload License to open the Select License File dialog box.
Step 3 In the Select License File dialog box, click Select file, select a license file, and click
Confirm.
When the license file to be loaded is of the XML type, the sales item information can be displayed
on the page. For the DAT type, sales item information cannot be displayed.
In the DR scenario, load or update the license at the active site.
----End
5 Appendix
HiCloud VMwar Per CPU Calculates the No fee A HiCloud commercial license will
e number of exempt not expire.
Service licenses based ion However, a non-commercial license
and on the number (for example, a temporary license or a
Hyper- of managed commissioning license) has an
V physical CPUs. expiration date. After a license
Service expires, you need to apply for a
commercial license and load the
commercial license file.
After your license expires, new
physical machines and VMs cannot be
managed and the status of inventory
managed resources cannot be updated.
NSX Per CPU Calculates the No fee A HiCloud commercial license will
Service number of exempt not expire.
licenses based ion However, a non-commercial license
on the number (for example, a temporary license or a
of physical commissioning license) has an
CPU cores expiration date. After a license
occupied by expires, you need to apply for a
the VM where commercial license and load the
NSX Manager commercial license file.
resides.
After your license expires, new NSX
sites cannot be connected.
AWS Per VM Calculates the No fee A HiCloud commercial license will
Service number of exempt not expire.
licenses based ion However, a non-commercial license
on the number (for example, a temporary license or a
of VMs to be commissioning license) has an
managed and expiration date. After a license
provisioned. expires, you need to apply for a
commercial license and load the
commercial license file.
After your license expires, VMs
cannot be synchronized or
provisioned.
Security Functional Controlled as a No fee A HiCloud commercial license will
as a function. exempt not expire.
Service ion However, a non-commercial license
(SECaa (for example, a temporary license or a
S) commissioning license) has an
expiration date. After a license
expires, you need to apply for a
commercial license and load the
commercial license file.
FusionStage Per vCPU Based on the No fee License files are classified into the following
number of exemption based on different application scenarios:
5.2 Troubleshooting
5.2.1 An Error Occurs When an Entitlement Is Activated
5.2.1.1 Scenario 1: Error Message "Not meet the 'Check' expression
requirement" Is Displayed
Error Message
The error message "Not meet the 'Check' expression requirement: xxxxxx" is displayed.
Example: Not meet the 'Check' expression
requirement:(((88033KRC+88033KRH-88033KTG-88033KTN)*(88033KRL+88033KRP))=
=0)?1:0.
Possible Causes
One entitlement contains more than one commercial edition.For example, one
entitlement contains both standard and platinum license editions.
The license edition of the expanded capacity is different from that of the existing
entitlement. For example, the license of the existing entitlement is the platinum edition,
and the license of the new entitlement is the standard edition.
Procedure
1. Cause identification
On the page where the error is reported, click Activation ID to view the detailed
entitlement information.
If the entitlement contains more than one commercial edition, perform the required
operations based on Method 1. Otherwise, perform the required operations based on
Method 2.
2. Method 1
a. If the entire capacity of this entitlement is delivered at one site, change the project
contract to configure only one commercial edition.
b. If the capacity of this entitlement is delivered at multiple sites, split the entitlement
into multiple ones based on the site capacity planning and ensure that each contains
only one commercial edition, and then activate each entitlement.
3. Method 2
Change the project contract to configure the version of the new entitlement to be the
same as that of the existing entitlement.
Error Message
The error message "Cannot activate the suite entitlement. Add license bom to this entitlement
or contact IT support (The SA item cannot be activated independently as the core suite.)" is
displayed.
Possible Causes
An entitlement contains only the SnS service without its corresponding commercial license,
and no commercial license exists on the NE. For example, the entitlement contains only one
year SnS of the standard edition without the standard edition license.
Procedure
If you have purchased a license, locate the contract corresponding to the license, and
activate both the license and SnS entitlements. Alternatively, activate the license
entitlement first and then the SnS entitlement.
If no license is purchased, perform a contract change to configure a commercial license.
Error Message
The error message "The entitlement does not contain a license. You cannot activate only
Subscription and Support" is displayed.
Possible Causes
An entitlement contains only the SnS service without its corresponding commercial license,
and no commercial license exists on the NE. For example, the entitlement contains only one
year SnS of the standard edition without the standard edition license.
Procedure
If you have purchased a license, locate the contract corresponding to the license, and activate
both the license and SnS entitlements. Alternatively, activate the license entitlement first and
then the SnS entitlement.
If no license is purchased, perform a contract change to configure a commercial license.
Error Message
The error message "The component related to the activation ID xxxxxx is not a core
component. Please activate the entitlement of the core component xxxxxx first (activation ID:
xxxxxx)" is displayed.
Example: The component related to the activation ID TX4LAJ8V9Z2T-VFTA is not a core
component. Please activate the entitlement of the core component FusionSphere first
(activation ID: TX4LAJ8V9Z2T-6658).
Possible Causes
The product is sold as a whole. The component related to the activation ID is not a core
component and you need to activate the entitlement of the core component first.
Procedure
Activate the entitlement of the core component based on the prompted error message and then
activate the current entitlement.
5.2.1.5 Scenario 5: Error Message "The activation failed because the xxxxxx
do not exist in the target product xxxxx" Is Displayed
Error Message
The error message "The activation failed because the xxxxxx do not exist in the target product
xxxxx CarrierNetwork&Enterprises or the boms have been disabled" is displayed.
Example: The activation failed because the 88032QKF does not exist in the target product
FusionCompute V100R003 CarrierNetwork&Enterprises or the boms have been disabled.
Possible Causes
The versions of the two activated entitlements are different. For example, one is
V100R003 and the other is V100R005.
The NE version is different from that of the activated entitlement.For example, the NE
version is V100R003 and the version of the activated entitlement is V100R005.
Procedure
1. Cause identification
a. Obtain the version of the entitlement to be activated.
Select Order Management > Entitlement Management and use the contract
number to obtain the name and version of the entitlement to be activated.
b. Obtain the version of the NE.
On the Equipment (Node) Management page, use the ESN to identify the
equipment. Click Equipment (Node) Name in the query result to switch to the NE
page to view the NE name and version.
2. Method 1
a. If the entitlement of the earlier version contains the SnS service, is still valid, and a
license of a later version is required, perform the following operations:
i. Activate the entitlement of the earlier version and obtain the corresponding
license file. For details, see 3.2 Applying for a License in a New Deployment
or Capacity Expansion Project.
ii. Upgrade the activated license file from the earlier version to the later version.
For details, see 3.3 Applying for a License in an Upgrade Project.
iii. Add the to-be-activated entitlement of the later version for capacity expansion
and obtain the new license file. For details, see 3.2 Applying for a License in a
New Deployment or Capacity Expansion Project.
b. If the entitlement of the earlier version does not contain the SnS service, is valid, or
requires a license of the earlier version, change the project contract to configure the
required license of the earlier version.
3. Method 2
a. If the NE version is later than the version to be activated, the SnS service is valid,
and a license of a later version is required, perform the following operations:
i. Roll back the activated license file. For details, see 3.5.5 Rolling Back a
License.
ii. Activate the entitlement of the earlier version and obtain the license file. For
details, see 3.2 Applying for a License in a New Deployment or Capacity
Expansion Project.
iii. Upgrade the activated license file from the earlier version to the later version.
For details, see 3.3 Applying for a License in an Upgrade Project.
iv. Expand the entitlement of the rolled back version and obtain the license file of
the later version. For details, see 3.2 Applying for a License in a New
Deployment or Capacity Expansion Project.
b. If the version of the activated entitlement is earlier than that of the entitlement to be
activated, the SnS service is valid, and a license of a later version is required,
perform the following operations:
i. Upgrade the activated license file from the earlier version to the later version.
For details, see 3.3 Applying for a License in an Upgrade Project.
ii. Add the to-be-activated entitlement of the later version for capacity expansion
and obtain the new license file. For details, see 3.2 Applying for a License in a
New Deployment or Capacity Expansion Project.
iii. If the license of an earlier version is required, change the project contact to
configure the required license.
Error Message
The error message "xxxxxx value must equal xxxxxx" is displayed.
An example of the error message is as follows: 88032DPE must equal 10.
Possible Causes
The activated entitlement is a new entitlement of the commercial edition in an upgrade project,
but the capacity of the existing entitlement is different from that of the new entitlement. For
example, the standard license edition of the existing entitlement provides 100 CPUs, but the
new entitlement is to upgrade the standard edition to the platinum edition and provides 200
CPUs.
Procedure
1. Obtain information about the entitlement to be activated.
Select Order Management > Entitlement Management, and use the contract number
to obtain the entitlement to be activated.
In the query result, click Activation ID to switch to the entitlement page to view the
entitlement information.
2. Obtain existing NE license information.
On the Equipment (Node) Management page, use the ESN to identify the equipment.
Click Equipment (Node) Name in the query result to switch to the NE page. Click View
in the Part Details column in the Merged License list to view the capacity information.
3. Handle the issue.
a. If the capacity of the new entitlement is smaller than that of the existing entitlement,
change the project contract to ensure that the two entitlements have the same
capacity.
b. If the capacity of the new entitlement is larger than that of the existing entitlement,
split the new entitlement, ensure that one of the split entitlements provides the same
capacity as the existing entitlement, and then activate this split entitlement.
5.2.1.7 Scenario 7: Error Message "xxxxxx value must equal 0" Is Displayed
Error Message
The error message "xxxxxx value must equal 0" is displayed.
An example of the error message is as follows: 88031TRY value must equal 0.
Possible Causes
The activated entitlement is a new entitlement of the commercial edition in an upgrade project,
but the version of the new entitlement does not match that of the existing entitlement. For
example, the license of the new entitlement is to upgrade the standard edition to the platinum
edition, but the license of the existing entitlement is the platinum edition already.
Procedure
1. Obtain information about the entitlement to be activated.
Select Order Management > Entitlement Management, and use the contract number
to obtain the entitlement to be activated.
In the query result, click Activation ID to switch to the entitlement page to view the
entitlement information.
2. Obtain existing NE license information.
On the Equipment (Node) Management page, use the ESN to identify the equipment.
Click Equipment (Node) Name in the query result to switch to the NE page.
Click View in the Part Details column in the Merged License list to view the capacity
information.
3. Change the project contract to configure the version of the new entitlement to be the
same as that of the existing entitlement.
Error Message
The error message "The final configuration of node shouldn't contain replace sale part: xxx" is
displayed.
An example of the error message is as follows: "The final configuration of node shouldn't
contain replace sale part: 88033WRV"
Possible Causes
The activated entitlement authorizes the upgrade of a commercial version, but the source
version cannot be found either in the inventory or in any of the entitlements to be activated.
For example: There is no standard edition in the inventory or any of the entitlements to be
activated. However, an entitlement to be activated includes the permit to upgrade from this
standard edition to an platinum edition.
Procedure
1. Obtain information about the entitlement to be activated.
Select Order Management > Entitlement Management, and use the contract number
to obtain the entitlement to be activated.
In the query result, click Activation ID to switch to the entitlement page to view the
entitlement information.
2. Obtain existing NE license information.
On the Equipment (Node) Management page, use the ESN to identify the equipment.
Click Equipment (Node) Name in the query result to switch to the NE page.
Click View in the Part Details column in the Merged License list to view the capacity
information.
3. Change the project contract to configure the version of the new entitlement to be the
same as that of the existing entitlement.
Error Message
The error message "Upgrade is not allowed because Subscription Advantage (SA) expires" is
displayed.
Possible Causes
The software SnS for the equipment has expired.
Procedure
1. Obtain the SnS expiry date of an NE.
On the Equipment (Node) Management page, use the ESN to identify the equipment.
Click Equipment (Node) Name in the query result to switch to the NE page to view the
SnS expiry date of the NE.
2. Handling method: Purchase the SnS package, activate the SnS entitlement on the ESDP
platform, and then upgrade the license file.
5.2.2.2 Scenario 2: The activation failed because the xxxxxx do not exist in
the target product xxxxx
Error Message
The error message "The activation failed because the xxxxxx do not exist in the target product
xxxxx CarrierNetwork&Enterprises or the boms have been disabled" is displayed.
An example of the error message is as follows: The activation failed because the 88033JUA
does not exist in the target product FusionSphere V100R006 CarrierNetwork&Enterprises or
the boms have been disabled.
Possible Causes
License operations are not performed according to the license upgrade guide.
Procedure
Upgrade the license file according to 3.3 Applying for a License in an Upgrade Project and
follow the precautions.
SnS entitlement
Upgrade the license file.
Procedure
1. Log in to the ESDP platform, use the contract number (or activation password) to check
whether the V100R003/V100R005 version entitlement contains the SnS.
a. If yes, proceed to the remaining steps.
b. If no, purchase the SnS for V100R003/V100R005 and then activate the license file.
2. Install V100R006 and obtain its ESN.
3. Log in to the ESDP platform, use the ESN and contract number (or activation password)
to activate the entitlement of the V100R003/V100R005 version. For details, see 3.2
Applying for a License in a New Deployment or Capacity Expansion Project.
4. On the ESDP platform, use the ESN to upgrade the license file and obtain the license file
of the V100R006 version. For details, see 3.3 Applying for a License in an Upgrade
Project.