How to Activate a Router License - Huawei Router License Operation Guide
- License, License Classification, and License Mechanism
- Checking Whether a License Has Been Activated Before Delivery
- Applying for and Activating a License File for a Newly Delivered Device
- Activating Hardware RTUs and Service Licenses
- Activating a Trial License
- Replacing a License with a Commercial License
- Revoking a License and Activating Another After the ESN Is Changed (Due to Part Replacement for Example)
- Managing a License During Version Upgrade or Downgrade
- Checking the Remaining Validity Period of a License
- Manually Enabling the Emergency Mode (When a Natural Disaster Occurs or the Grace Period of the License Is About to Expire)
- Using the License Query Tool to View License Items
- A Description of Parameters in the License File
- B Common License Commands
- C Applying for the ESDP Website Permission
- D Adjusting License Resources Among Multiple Devices (Splitting a License)
- E Troubleshooting Common License Activation Problems
- The File Does Not Exist (Error: The specified file does not exist)
- The License File Format Is Invalid (Error: The format of the license file is invalid)
- ESNs or Software Versions Do Not Match (Error: The ESN or version of the license file does not match with the device)
- Product Types Do Not Match (Error: The product type of the license file does not match with the device)
- Some License Control Items Are Missing (Warning: No product feature is present in the license file)
- The License File Expires (Info: The license file has expired)
- Verification Fails Consecutively (Error: Verify license failed)
- How Do I Retrieve a License After It Is Revoked by Mistake?
- Hardware RTU Activation Fails
- Service License Activation Fails
License, License Classification, and License Mechanism
A license is an agreement in which the supplier authorizes the customer to use certain functions of the purchased products within a validity period. The physical form of a license is a license file, also called Global Trotter License (GTL). Some router features can be used only after a license is obtained and activated.
License File
A license file is an authorization file that controls the capacity and functions of a product. This file is generated on the Electronic Software Delivery Platform (ESDP) website (https://app.huawei.com/sdp/) based on the project contract and device information. In most cases, a license file is preinstalled on a device before device shipment. Alternatively, Huawei technical support engineers can download the license file from the ESDP website based on the project contract and the device's electronic serial number (ESN).
A router license file can be in .xml or .dat format. Figure 1-1 shows an example of a typical license file in .xml format. For details on versions that support license files in .xml or .dat format, as well as parameters in license files, see A Description of Parameters in the License File.
License Classification
Figure 1-2 shows license types.
Licenses are classified as either commercial or non-commercial licenses. Commercial licenses can be used in scenarios, such as commercial projects, beta tests, and testing and certification.
Licenses can also be classified as fixed-term or permanent licenses by the validity period. Currently, the licenses used for commercial projects and purchased licenses are permanent licenses (referred to as permanent commercial licenses in this document).
Licenses can also be classified by the object to be activated. Table 1-1 describes different types of licenses.
License Type |
Description |
Activation Time |
Activation Method |
---|---|---|---|
License file |
The license file is preinstalled on a device before device shipment or can be downloaded from the ESDP website based on the project contract and device ESN. Commercial licenses and non-commercial licenses (excluding trial licenses) are physically presented as license files. |
The license file has been pre-activated before device shipment, or can be applied for and activated by Huawei technical support engineers. |
Applying for and Activating a License File for a Newly Delivered Device |
Hardware Right to Use (RTU) |
Hardware RTUs control the valid ports of boards or box-shaped devices that are sold in consumption model (CM). If hardware RTUs are not activated for such ports as GE/10GE/25GE/40GE/50GE/100GE/400GE/POS/E1 on the boards or box-shaped devices sold in CM, the use of these ports is restricted. The restriction includes, but is not limited to, the following: The bandwidth of the GE/10GE/25GE/40GE/50GE/100GE/400GE port is limited to 100 Mbit/s by default, or the port cannot go up; by default, the bandwidth of a POS interface is limited to 5 Mbit/s; serial ports cannot be created on E1 ports. Hardware RTUs' license item descriptions contain Port Enable RTU. Hardware RTUs control resource allocation. That is, purchased resources (such as 10 x 100G) are allocated to specified ports based on the hardware RTUs. To obtain the slots of the CM boards housing the ports (hereinafter referred to as CM ports) for which hardware RTUs are to be activated, run the active port-basic slot ? command in the license view. NOTE:
Boards with a silkscreen or description containing CM are CM boards. However, a small number of boards whose silkscreen or description does not contain CM may also be CM boards. |
During project delivery or service usage, Huawei technical support engineers or service configuration engineers activate hardware RTUs for specified ports based on the number of purchased hardware RTUs. |
|
Service license |
A software license control item that controls one or more services. The display license command output shows that service licenses are classified into the following types:
For details about how to check the description of each service license, see Using the License Query Tool to View License Items. |
During project delivery or service usage, Huawei technical support engineers or service configuration engineers enable services for a specified board or port based on the number of purchased resource control service licenses. |
|
Trial license |
License control item that supports trial use. A trial license can be enabled twice for each R version, and can be used for a maximum of 90 days each time it is enabled. When the trial period ends, the controlled features become invalid immediately or after the device is restarted. These controlled features can still be used only if a commercial license is purchased. To view all trial license control items and supported resources, run the display license trial command. |
A trial license can be activated only when no other activated license file (including commercial and non-commercial licenses) exists on the device. |
In the following example, LCR8S8KVBSLCP is a hardware RTU, and LCR8S8KXMSCCP is a resource control service license.
<HUAWEI> display license ... Item name Item type Value Description ------------------------------------------------------------- CR8S8KXMSCCP -- 32 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KXMSCCP Resource 32 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KVBSLCP -- 64 NetEngine 8000 50G Port Enable RTU(per 50G/40G) LCR8S8KVBSLCP Resource 64 NetEngine 8000 50G Port Enable RTU(per 50G/40G) ... Item name (View)Resource License Command-line ------------------------------------------------------------- LCR8S8KXMSCCP (License)active port-macsec slot <slot-id> card <card-id> port <port-list> LCR8S8KVBSLCP (License)active port-basic slot <slot-id> card <card-id> port <port-list> ...
License Mechanism
Based on the license loading and running status, the license module has several states, as listed in Table 1-2.
State |
Description |
Handling Suggestion |
---|---|---|
Default |
This state applies when no license file is activated after device shipment, or when the license file is not reactivated after the grace period expires. |
Apply for and activate a license. |
Normal |
This state applies when a permanent commercial license is running normally after being activated. |
None. |
Emergency |
This state applies when the device operates with the maximum specifications of existing dynamic resource items (resource items that are not included in the license are not controlled in some earlier versions). This state can be considered as a temporary state when license control items are not under restriction. The emergency mode can be enabled a maximum of three times for each version, and for a maximum of seven days each time. |
None. |
Demo |
This state applies when a fixed-term license is running normally after being activated. |
Apply for and activate a permanent commercial license before the period ends. |
Trial |
This state applies when the license module is allowed to run based on the authorization policy in the Normal or Demo state. After the state changes from Normal or Demo to Trial, the Trial state lasts a grace period of 60 days. If the license module enters the Trial state from Demo state and the license revoke command is run before the grace period expires, the license automatically enters another 60-day grace period. |
Apply for and activate a new license. |
Figure 1-3 shows license state transitions.
Table 1-3 describes all the events that trigger license state transitions.
No. |
Trigger Event |
---|---|
0 |
A license file fails to be activated, and the license module is not allowed to enter the grace period due to the cause of the activation failure. |
1 |
A permanent commercial license file is successfully activated. |
2 |
A fixed-term license file is successfully activated. |
3 |
A trial license is activated, or license file activation fails and the license module is allowed to enter the grace period (for example, ESNs or versions do not match for the first time). |
4 |
A permanent commercial license becomes invalid. For example, the license is manually revoked for license replacement. |
5 |
The grace period expires. |
6 |
A fixed-term license becomes invalid. For example, it expires automatically or is manually revoked. |
7 |
The emergency mode is manually enabled. |
8 |
The emergency mode expires after running for seven days. |
Checking Whether a License Has Been Activated Before Delivery
For most routers, a license is obtained, loaded, and activated according to the contract order during the production phase. This topic lists the products that support license pre-activation, and any products not included in the list do not support license pre-activation. If hardware is delivered in separate parts, for example, a device set is purchased through multiple orders or Bills of Quotation (BOQs), license pre-activation may fail. In this case, check the device status.
Procedure
- Log in to the device.
- In the user view, check the state of the license module.
display license state Info: No license is activated.
If No license is activated is displayed, the license module is in the Default state, and the license is not pre-activated. In this case, go to Applying for and Activating a License File for a Newly Delivered Device. If Current license state is Normal is displayed, the license has been pre-activated. In this case, go to the next step.
- Check license items.
display license
Check the license items based on the project contract and service requirements. If any exceptions are found, contact project sales personnel. If the license needs to be replaced, go to Replacing a License with a Commercial License.
Products That Support License Pre-activation
Table 1-4 lists the products that support license pre-activation.
Product |
Entire System or Series |
Support License Pre-activation |
---|---|---|
NetEngine 8000 |
X4/X8 |
No |
M8/M14 |
Yes |
|
M1/M6 |
Yes |
|
F1A |
Yes |
|
NE40E |
X16/X16A |
No |
X3/X3A/X8/X8A |
Yes |
|
M2H/M2K/M2K-B |
Yes |
|
F1A |
Yes |
|
ME60 |
X16/X16A |
No |
X3/X8/X8A |
Yes |
|
NE9000 |
NE9000-20 |
No |
NE9000-8 |
No |
|
NE5000E |
NE5000E |
No |
NE20E |
S4/S8/S16/S8A/S16A |
Yes |
S2E/S2F |
Yes |
|
NE05E&NE08E |
NE05E-SQ/SR/S2, NE08E-S6E/S9 |
Yes |
Applying for and Activating a License File for a Newly Delivered Device
For a device with no pre-activated license, Huawei technical support engineers must download a license from the ESDP website based on the contract order, upload the license to the device, and then activate the license.
Prerequisites
- The project contract order has been recorded in the enterprise resource planning (ERP) system.
- The license certificate delivered with the device has been obtained.
- The task outlined in C Applying for the ESDP Website Permission has been completed.
Context
Huawei sales engineers sell both software and licenses when selling devices. After the contract administrator of the supply chain records the contract order in the ERP system, the ESDP platform automatically generates a license file. Huawei technical support engineers can then search for and download the license file from the ESDP website based on the contract number.
Downloading a license file also requires the device's ESN, which is a character string that uniquely identifies a device. The ESN is used to ensure that the license is authorized for a specified device.
Procedure
- In the user view, check and record the device's ESN.
display license esn MainBoard: ESN: 2102352168P0B2333333
Record the last 20 or 16 characters of the ESN. If multiple devices are involved, record all the involved ESNs.
For an NE5000E CCC-0 cluster, record the ESNs of the two CLCs. For an NE5000E CCC-2 cluster, record the ESNs of the two CCCs.
If the device has been connected to NCE-IP or U2000, you can choose on U2000 to export NE information (such as ESNs) in batches. In addition, you can load and activate license files on the NMS page. For details about the operations on the NMS, see the NMS online help.
on NCE-IP or choose - Download the license file.
- Upload the license file.
- Verify the license file.
license verify LICXXXX_VXXXRXXX_XXXX.xml Info: Verify license succeeded.
If Verify license succeeded is displayed, verification is successful. Otherwise, verification has failed due to an invalid license file, or an ESN, version, or product type mismatch. For details on how to solve these issues, see E Troubleshooting Common License Activation Problems.
If an ESN or version mismatch occurs on the first occasion, you can still perform the next step to activate the license file. If activation fails, the license module automatically enters the Trial state. In this case, obtain and activate a valid license file within the 60-day validity period.
- Activate the license file.
license active LICXXXX_VXXXRXXX_XXXX.xml Now activing the license....done. Info: Succeeded in activating the license file.
- Check the hardware RTU and service license items.
display license Active License : LICXXXX_VXXXRXXX_XXXX.xml License state : Normal Revoke ticket : No ticket RD of Huawei Technologies Co., Ltd. Product name : XXXX Product version : VXXXRXXX License Serial No : LIC202004162VXXXX Creator : Huawei Technologies Co., Ltd. Created Time : 2020-04-16 19:30:41 ------------------------------------------------------------- ... Item name Item type Value Description ------------------------------------------------------------- CR8S8KXMSCCP -- 32 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KXMSCCP Resource 32 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KVBSLCP -- 64 NetEngine 8000 50G Port Enable RTU(per 50G/40G) LCR8S8KVBSLCP Resource 64 NetEngine 8000 50G Port Enable RTU(per 50G/40G) ... Item name (View)Resource License Command-line ------------------------------------------------------------- LCR8S8KXMSCCP (License)active port-macsec slot <slot-id> card <card-id> port <port-list> LCR8S8KVBSLCP (License)active port-basic slot <slot-id> card <card-id> port <port-list> ...
Ensure that the license items displayed in the preceding command output meet the project requirements, including the hardware RTU types, the number of resources of each hardware RTU type, the function control service license types, the resource control service license types, and the number of resources of each service license type. If any exceptions are found, contact project sales personnel. If the license needs to be replaced, go to Replacing a License with a Commercial License.
Activating Hardware RTUs and Service Licenses
After a license file is activated, hardware RTUs and service licenses must also be activated to allocate license resources to specific boards and ports.
Activating Hardware RTUs
Hardware RTUs control the valid ports of boards or boxes that are sold based on the CM. Some or all restrictions on such ports as GE/10GE/25GE/40GE/50GE/100GE/400GE/POS/E1 on boards or box-shaped devices sold by CM can be removed only after hardware RTUs are activated for these ports. If no hardware RTUs have been purchased, skip this task.
Context
If hardware RTUs are not activated for such ports as GE/10GE/25GE/40GE/50GE/100GE/400GE/POS/E1 on the boards or box-shaped devices sold in CM, the use of these ports is restricted. These restrictions include, but are not limited to, the following: The bandwidth of the GE/10GE/25GE/40GE/50GE/100GE/400GE port is limited to 100 Mbit/s by default, or the port cannot go up; by default, the bandwidth of a POS interface is limited to 5 Mbit/s; serial ports cannot be created on E1 ports. To obtain the slots of the CM boards housing CM ports, run the active port-basic slot ? command in the license view.
Boards with a silkscreen or description containing CM are CM boards. However, a small number of boards whose silkscreen or description does not contain CM may also be CM boards. As such, running the active port-basic slot ? command to obtain the slots of the CM boards housing CM ports is recommended.
The license item descriptions of hardware RTUs contain Port Enable RTU. Hardware RTUs control resource allocation, whereby purchased resources (such as 10 x 100G) are allocated to specified ports based on the hardware RTUs.
Hardware RTUs are classified into enabling hardware RTUs and upgrade hardware RTUs.
- Enabling hardware RTUs: enable the specified bandwidth for ports. For example, 10G Port Enable RTU enables the 10 Gbit/s bandwidth for ports.
- Upgrade hardware RTUs: increase the port bandwidth from a specified value to a larger value (under the condition that the physical port rate is the target bandwidth). For example, 10G upgrade to 25G increases the port bandwidth from 10 Gbit/s to 25 Gbit/s.
Generally, a GE/10GE/25GE/40GE/50GE/100GE/400GE/POS/E1 CM port requires a corresponding GE/10GE/25GE/40GE/50GE/100GE/400GE/POS/E1 Port Enable RTU for bandwidth restriction removal.
A high-bandwidth physical port can be manually configured to operate in a low-rate mode using the port split command. For example, a 100GE interface can be configured as one 50GE interface, one 40GE interface, four 25GE interfaces, four 10GE interfaces, or ten 10GE interfaces. According to the port support mode and sales strategy, a small number of hardware RTUs with specific codes for routers can be allocated to physical ports in combination mode. For example:
- A 100GE port is used as a 50GE port after one 50G Port Enable RTU is allocated to the port (under the condition that the port rate has been manually set to 50 Gbit/s), and the bandwidth restriction can be canceled (meaning that the port is used as a 100GE port) if two 50G Port Enable RTUs are allocated to the port.
- A 25GE port is used as a 10GE port after one 10G Port Enable RTU is allocated to the port (under the condition that the port rate has been manually set to 10 Gbit/s), and the bandwidth restriction can be canceled if another 10G upgrade to 25G is allocated to the port.
You can use the license query tool to check whether an RTU can be allocated in combination mode based on the RTU code (Item name displayed in the display license command output). For details, see Using the License Query Tool to View License Items.
To activate hardware RTUs, you only need to specify the ports for which the hardware RTUs are activated. The allocation result is automatically determined by the device based on the port rate, RTU type, and number of RTUs. For example, if five 10G Port Enable RTUs and three 10G upgrade to 25Gs have been purchased for a 32x25GE CM subcard, ports 0 to 2 use the default mode, and ports 3 and 4 have been set to the 10G rate mode, after the RTUs are activated for ports 0 to 4, bandwidth restrictions on ports 0 to 2 are removed, and ports 3 and 4 are used as 10GE ports, as shown in Figure 1-6.
Procedure
- Check the slots where CM boards reside and record all the ports for which bandwidth restrictions are to be removed.
system-view license active port-basic slot ? <1,2> The available slot return display interface brief PHY: Physical *down: administratively down ^down: standby (l): loopback (s): spoofing (E): E-Trunk down (b): BFD down (B): Bit-error-detection down (e): ETHOAM down (d): Dampening Suppressed (p): port alarm down (ld): loop-detect trigger down (mf): mac-flapping blocked (c): CFM down (sd): STP instance discarding InUti/OutUti: input utility/output utility Interface PHY Protocol InUti OutUti inErrors outErrors 100GE1/0/0(100M) down down 0% 0% 0 0 100GE1/0/1(100M) down down 0% 0% 0 0 ... 25GE2/0/0(10G) down down 0% 0% 0 0 25GE2/0/1(100M) down down 0% 0% 0 0 ... 100GE3/0/0 down down 0% 0% 0 0 100GE3/0/1 down down 0% 0% 0 0 ...
For all products except the NE5000E, and for NE5000E V800R011C10 and earlier versions, all ports with (100M) displayed in the display interface brief command output are CM ports with the default bandwidth restriction, for example, 100GE1/0/0(100M). If the bandwidth restriction in the brackets is not 100M, but is less than the rate of the physical port, for example, 25GE2/0/0(10G), at least one enabling hardware RTU has been activated. You need to record both types of ports.
For NE5000E V800R012C00 and later versions, all CM ports cannot go up by default (the undo shutdown command cannot be run for the CM ports). That is, all the ports in the down state in the slots where the CM boards reside have not been activated with any RTU.
- Check the available (purchased) hardware RTUs.
display license resource usage port-basic all FeatureName Descriptions: ==================================================================================== FeatureName Description -------------------------------------------------------------------------------- LCR8S8KXBSLCQ NetEngine 8000 10G Port Enable RTU for Line Process Unit L(per 10G) LCR8S8KVBSLCP NetEngine 8000 50G Port Enable RTU(per 50G/40G) LCR8S8KXBSLCP NetEngine 8000 10G Port Enable RTU(per 10G) LCR8S8KYBSLCP NetEngine 8000 10G upgrade to 25G Port Enable RTU(per 25G) LCR8S8KVBSLCQ NetEngine 8000 50G Port Enable RTU for Line Process Unit L(per 50G/40G) LCR8S8KYBSLCQ NetEngine 8000 10G upgrade to 25G Port Enable RTU for Line Process Unit L(per 25G) Global license information: ==================================================================================== FeatureName Offline Allocated Activated Available Total -------------------------------------------------------------------------------- LCR8S8KXBSLCQ 0 0 0 76 76 LCR8S8KYBSLCQ 0 0 0 76 76 LCR8S8KYBSLCP 0 0 0 176 176 LCR8S8KXBSLCP 0 0 0 76 76 LCR8S8KVBSLCQ 0 0 0 40 40 LCR8S8KVBSLCP 0 0 0 140 140 ...
The value in the Available column indicates the number of each license item's remaining resources. You are advised to refer to Table 1-5 when collecting statistics on the number of available RTUs.
Table 1-5 Statistics on the number of available hardware RTUsCategory
Description
Number of Ports for Which the RTU Can Be Activated
Remarks (When Applicable Boards Are Limited)
Enabling hardware RTUs
10G Port Enable RTU
____
____________________
25G Port Enable RTU
____
____________________
50G Port Enable RTU
____
____________________
100G Port Enable RTU
____
____________________
400G Port Enable RTU
____
____________________
_____ Port Enable RTU
____
____________________
Upgrade hardware RTUs
____ upgrade to ____ Port Enable RTU
____
____________________
____ upgrade to ____ Port Enable RTU
____
____________________
____ upgrade to ____ Port Enable RTU
____
____________________
- Plan the range of ports for which RTUs are to be activated based on the list of ports for which bandwidth restrictions are to be removed, the number of available RTUs, and service requirements.
Plan the range of ports as required. If the number of ports for which RTUs are to be activated exceeds the number of purchased license resources, RTU activation will fail for some ports. The device reports an alarm in such cases.
- Activate RTUs for the ports as planned.
system-view license active port-basic slot slot-id card card-id port port-list commit
To check the detailed activation command of each license item on the current device, run the display license command. For some product models (including the NE8000-M1, and NE8000-M6), the activation command is active port-basic slot slot-id port port-list (card card-id is not included).
If a port requires multiple RTUs in combination mode during the activation, you need to run the activation command only once for the port.
- Check hardware RTU resource usage statistics.
display license resource usage port-basic all FeatureName Descriptions: ==================================================================================== FeatureName Description -------------------------------------------------------------------------------- LCR8S8KXBSLCQ NetEngine 8000 10G Port Enable RTU for Line Process Unit L(per 10G) LCR8S8KVBSLCP NetEngine 8000 50G Port Enable RTU(per 50G/40G) LCR8S8KXBSLCP NetEngine 8000 10G Port Enable RTU(per 10G) LCR8S8KYBSLCP NetEngine 8000 10G upgrade to 25G Port Enable RTU(per 25G) LCR8S8KVBSLCQ NetEngine 8000 50G Port Enable RTU for Line Process Unit L(per 50G/40G) LCR8S8KYBSLCQ NetEngine 8000 10G upgrade to 25G Port Enable RTU for Line Process Unit L(per 25G) Global license information: ==================================================================================== FeatureName Offline Allocated Activated Available Total -------------------------------------------------------------------------------- LCR8S8KXBSLCQ 0 0 76 0 76 LCR8S8KYBSLCQ 0 0 70 6 76 LCR8S8KYBSLCP 0 0 170 6 176 LCR8S8KXBSLCP 0 0 72 4 76 LCR8S8KVBSLCQ 0 0 40 0 40 LCR8S8KVBSLCP 0 0 140 0 140 License detailed information: ==================================================================================== Physical Position FeatureName Needed Count Used Count Active Status -------------------------------------------------------------------------------- 3/0/0 LCR8S8KVBSLCP 2 2 Activated 3/0/1 LCR8S8KVBSLCP 2 2 Activated 3/0/2 LCR8S8KVBSLCP 2 2 Activated ...
Fields in Global license information in the preceding command output are described as follows:
- Offline: indicates the number of resources used by offline ports (for example, the boards where the ports reside are powered off or removed).
- Allocated: indicates the number of ports that fail RTU activation due to insufficient available RTUs, despite the active port-basic command being run. In this case, the device reports an alarm, and you need to replan the range of ports for which RTUs are to be activated based on the number of available RTUs or have the license capacity expanded.
- Activated: indicates the number of ports for which RTUs are successfully activated.
- Available: indicates the number of remaining license item resources.
Check whether RTUs are activated for ports as planned. If any port in the planned port range fails to have an RTU activated, return to the previous step for adjustment.
Activating Service Licenses
A service license controls one or more software features. Resource control service licenses need to be activated so that related resources are allocated to specified ports. If no resource control service licenses have been purchased, skip this task.
Prerequisites
The license file has been activated. Before allocating service license resources to CM ports, ensure that hardware RTUs have been activated.
Context
Function control service licenses are valid for the entire system (including CM boards unless otherwise specified in the license item description) and are automatically activated with the license file. As such, additional activation is not required.
Resource control service licenses need to be activated so that related resources are allocated to specified ports. Some service licenses are used only on CM boards or a specific board and cannot be allocated to ports on other boards. For details about license items, contact sales engineers or see Using the License Query Tool to View License Items.
If the service item corresponding to a sales code contains an initial service configuration (generally referred to as Initial Bundle) and the initial configuration contains a default resource authorization (for example, enabling L3VPN&EVPN for 10x10GE and all GE ports), one or more resource control service license items is displayed for the service item. In this case, the resource control service license items contain the resource authorization for 10GE and higher-speed ports. For ports with speeds lower than 10 Gbit/s, the resource control service license items are automatically activated with the license file and no additional activation is required.
Procedure
- Check currently available (purchased) resource control service licenses.
Run the display license command in the user view and record all resource control service licenses (Item type is Resource, and Description does not contain Port Enable RTU) and the corresponding activation commands. You are advised to refer to Table 1-6 when collecting statistics on the number of available resources.
display license ... Item name Item type Value Description ------------------------------------------------------------- CR8P00TSYFC0 -- 1 NetEngine 8000 Timing Synchronization Function Package License LCR8P00TSYFC0 Function YES NetEngine 8000 Timing Synchronization Function Package License CR8P00OAMFC0 -- 1 NetEngine 8000 OAM Function Package License LCR8P002544C0 Function YES NetEngine 8000 OAM Function Package License CR8S8KXMSCCP -- 152 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KXMSCCP Resource 152 NetEngine 8000 10G MACsec Port Function License(per 10G) CR8S0VCAGGC0 -- 40 NetEngine 8000 50G Core&Aggregation Scenario License(per 50G/40G) LCR8S0VCAGGC0 Resource 40 NetEngine 8000 50G Core&Aggregation Scenario License(per 50G/40G) CR8S0XCAGGC0 -- 152 NetEngine 8000 10G Core&Aggregation Scenario License(per 10G) LCR8S0XCAGGC0 Resource 152 NetEngine 8000 10G Core&Aggregation Scenario License(per 10G) ... Item name (View)Resource License Command-line ------------------------------------------------------------- LCR8S0VCAGGC0 (License)active port-core-aggregation slot <slot-id> card <card-id> port <port-list> LCR8S0XCAGGC0 (License)active port-core-aggregation slot <slot-id> card <card-id> port <port-list> LCR8S8KXMSCCP (License)active port-macsec slot <slot-id> card <card-id> port <port-list> ...
Table 1-6 Service license resource statisticsService Name
Number of Resources
Activation Command
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
active ____________________ slot slot-id card card-id port port-list
_________________
________
_______________________________________________________________________________
_________________
________
_______________________________________________________________________________
For some product models (including the NE8000-M1, and NE8000-M6), the activation command is active XXXX slot slot-id port port-list (card card-id is not included). Similar details will be omitted in the rest of the document.
If the slot ID of a board that does not support the current service license is entered, an error message will be displayed. To check the slots of the boards that need a service license, run the active XXXX slot ? command.
For example, to check the slots of the boards that need the MACsec service license, run the active port-macsec slot ? command in the license view.
- Plan the ranges of boards and ports for which each service license needs to be activated based on the available service license resources and service requirements.
Plan the ranges of boards and ports as required. If the number of boards or ports for which service licenses are to be activated exceeds the number of purchased license resources, service license activation will fail for some boards or ports. The device reports an alarm in such cases.
- Allocate license resources based on the planned ranges.
system-view license active XXXX slot slot-id card card-id port port-list commit
Some service license resources need to be activated by board, and the corresponding activation command may vary from other activation commands. As such, run the corresponding activation command according to Table 1-6.
- Check service license resource statistics.
Activating a Trial License
After a trial license is activated, you can use some functions provided by the device free of charge for a short period. To continue using these functions, you are recommended to purchase and activate a permanent commercial license before the trial license expires.
Context
A trial license can be enabled twice for each R version, and can be used for a maximum of 90 days each time it is enabled. When the trial period ends, the controlled features become invalid immediately or after the device is restarted.
Procedure
- Run the license trial enable command in the user view to activate the trial license.
license trial enable Warning: This operation will enable the license-controlled feature and can be used only after authorization. Please apply for a license before the feature expires. Continue? [Y/N]:y Info: Operating, please wait for a moment...........done. Info: Succeeded to perform this operation.
- Check activated trial license items.
display license trial License trial status : Enable Remain times : 1 Remain days : 89 Feature-name Value Description ------------------------------------------------------------ LCR8SX0SRV6C1 1 NetEngine 8000 SRv6 Function License LCR8SX0L3VPC1 1 NetEngine 8000 L3VPN Function License ...
Replacing a License with a Commercial License
Scenarios where a license may need to be replaced with a commercial license include but are not limited to adding hardware RTUs and service licenses or having their capacities expanded, replacing a non-commercial license with a commercial license before the non-commercial license enters the grace period, and replacing a non-commercial license with a commercial license after the non-commercial license enters the grace period.
Prerequisites
The project contract order corresponding to the target commercial license has been recorded in the ERP system.
If you only need to adjust license resources among multiple devices with no new contract involved, see D Adjusting License Resources Among Multiple Devices (Splitting a License).
Procedure
- Obtain the target license file.
- Upload the license file.
- Verify the license file.
license verify LICXXXX_VXXXRXXX_XXXX.xml Info: Verify license succeeded.
If Verify license succeeded is displayed, verification is successful. Otherwise, verification has failed due to an invalid license file, or an ESN, version, or product type mismatch. For details on how to solve this issue, see E Troubleshooting Common License Activation Problems.
- Activate the license file.
The license file that has been activated does not need to be revoked before you run the following command to activate the target license file:
license active LICXXXX_VXXXRXXX_XXXX.xml Now activing the license....done. Info: Succeeded in activating the license file.
- (Optional) Delete the original license file.
For example, to delete the XXXX.xml file from a device with two main control boards, run the following commands in the user view:
delete cfcard:/XXXX.xml delete salve#cfcard:/XXXX.xml
Revoking a License and Activating Another After the ESN Is Changed (Due to Part Replacement for Example)
The license file is bound to the device ESN. If the ESN is changed, the license module automatically enters the grace period. In such cases, you need to obtain and activate a new license file as soon as possible.
Context
Each ESN uniquely identifies a device and is key to authorizing a license for the device.
The ESN is associated with the backplane of the device. Generally, the ESN is not changed unless the subrack is replaced. In abnormal scenarios, if a device fails to read backplane information, it automatically uses the barcode in main control board information as its ESN; if the main control board is replaced, the ESN changes accordingly. To check whether the ESN of the current device is associated with the backplane or the main control board, run the display elabel backplane command to view the barcode of the backplane. If the barcode is the same as the ESN, the ESN is associated with the backplane. Otherwise, the ESN is associated with the main control board.
Procedure
- In the user view, check and record the device's new ESN.
display license esn MainBoard: ESN: 2102352168P0B2333333
- Revoke the current license and record the revocation code.
If the revocation code cannot be obtained due to such circumstances as a device startup failure, go to the next step.
license revoke Warning: The license will enter the Trial state and will not be activated again. Continue? [Y/N]:y Now revoking the license...................done. Info: Succeeded in revoking the license. The revoke ticket is LIC20201120YBXXXX:0E47B21121D40C4BBBBB8E8255A437E6D532XXXX.
Record the revocation code in the preceding command output. You can also run the following command to view the revocation code:
display License revoke-ticket Info: The revoke ticket is LIC20201120YBXXXX:0E47B21121D40C4BBBBB8E8255A437E6D532XXXX.
- Download a new license file.
- Upload the license file.
- Verify the license file.
license verify LICXXXX_VXXXRXXX_XXXX.xml Info: Verify license succeeded.
If Verify license succeeded is displayed, verification is successful. Otherwise, verification has failed due to an invalid license file, or an ESN, version, or product type mismatch. For details on how to solve this issue, see E Troubleshooting Common License Activation Problems.
- Activate the license file.
license active LICXXXX_VXXXRXXX_XXXX.xml Now activing the license....done. Info: Succeeded in activating the license file.
Managing a License During Version Upgrade or Downgrade
During a version upgrade or downgrade, the license must be processed according to requirements to prevent service failures or new service provisioning failures.
Prerequisites
The license file has been activated. If the license capacity needs to be expanded, the expansion order must have been recorded in the ERP system.
Context
After a version upgrade, the license can be automatically inherited, and you do not need to apply for or activate the license again in such cases. However, to use license-controlled new services in the target version, you must apply for a new license file for license capacity expansion.
After a version downgrade, if the license version is the target version or earlier, the license does not need to be processed. Otherwise, you need to apply for a new license file on the ESDP website and activate it. If the order version is later than the software version, the license also needs to be downgraded.
The sales strategies before and after the upgrade may be different. Example scenarios include those where a service control is removed (a service is no longer under license control) or where a service is tailored (no longer supported) in the target version. In the case of the former, the number of license items decreases in the target version without compromising the service. In the case of the latter, the service immediately becomes invalid (without a grace period) after the upgrade. In the pre-upgrade evaluation phase, check whether services are tailored. If such services exist and have been enabled, carefully follow the upgrade process for approval.
The versions described in this document are all VRP V8 versions. If a VRP V5 version is involved, contact Huawei engineers for assistance.
Procedure
- Save the license information before the upgrade.
display license ... Item name Item type Value Description ------------------------------------------------------------- CR8P00TSYFC0 -- 1 NetEngine 8000 Timing Synchronization Function Package License LCR8P00TSYFC0 Function YES NetEngine 8000 Timing Synchronization Function Package License CR8P00OAMFC0 -- 1 NetEngine 8000 OAM Function Package License LCR8P002544C0 Function YES NetEngine 8000 OAM Function Package License CR8S8KXMSCCP -- 152 NetEngine 8000 10G MACsec Port Function License(per 10G) LCR8S8KXMSCCP Resource 152 NetEngine 8000 10G MACsec Port Function License(per 10G) CR8S0VCAGGC0 -- 40 NetEngine 8000 50G Core&Aggregation Scenario License(per 50G/40G) LCR8S0VCAGGC0 Resource 40 NetEngine 8000 50G Core&Aggregation Scenario License(per 50G/40G) CR8S0XCAGGC0 -- 152 NetEngine 8000 10G Core&Aggregation Scenario License(per 10G) LCR8S0XCAGGC0 Resource 152 NetEngine 8000 10G Core&Aggregation Scenario License(per 10G) ...
- (Optional, and applicable only in license capacity expansion scenarios) Obtain and activate a new license file.
- (Optional, and applicable only in license version downgrade scenarios) Obtain and activate the new license file.
- Check the license information after the upgrade.
display license
Compare the license items before and after the upgrade. If the result is not as expected, contact Huawei technical support personnel.
Checking the Remaining Validity Period of a License
Non-permanent-commercial licenses have a fixed validity period, and must be replaced with permanent commercial licenses before the validity period expires. Otherwise, features under license control will become invalid.
Procedure
- If a non-permanent-commercial license file has been activated, run the following command:
display license state Info: Current license state is Demo. The license for the current configuration will expire in 7 day(s).
- If a trial license has been activated, run the following command:
display license trial License trial status : Enable Remain times : 1 Remain days : 7 ...
- If a non-permanent-commercial license is in the grace period, run the following command:
display license state trial Info: Current license state is Trial. The trial days remains 59 days.The license for the current configuration will expire at 02:00 on the next day of the last trial day.
Manually Enabling the Emergency Mode (When a Natural Disaster Occurs or the Grace Period of the License Is About to Expire)
After the emergency mode is enabled, the device operates with the maximum specifications of existing dynamic resource items (resource items that are not included in the license are not controlled in some earlier versions). This state can be considered as a temporary state when license control items are not under restriction. The emergency mode can be enabled a maximum of three times for each version, and for a maximum of seven days each time.
Prerequisites
The license module is in the Normal, Demo, or Trial state, and the emergency mode has been enabled no more than twice.
Procedure
- Run the following command in the user view:
license emergency Warning: This operation will cause LCS into the EMERGENCY state. Continue? [Y/N]:y Info: The emergency has been started. You can stop it only by activating a new license file.
- Check license items in the emergency mode.
display license emergency License emergency status : Enable Remain times : 2 Remain days : 6 Feature-name Value Description ------------------------------------------------------------ LCR8SX0SRV6C1 1 NetEngine 8000 SRv6 Function License LCR8SX0L3VPC1 1 NetEngine 8000 L3VPN Function License ...
Using the License Query Tool to View License Items
The license query tool helps you query the description of a specified license item by code and can be used only by Huawei engineers.
Prerequisites
You have obtained the code of the license item to be queried (Item name displayed in the display license command output).
Procedure
- Click the following link to access the tool page.
- Set the search criteria and click Search, as shown in Figure 1-13.
A Description of Parameters in the License File
Router license files have two file name extensions: .xml and .dat. The XML license files are used in V800R011 (released in 2019) or later versions. Figure 1-14 shows an example of an XML license file.
Table 1-7 describes the parameters in an XML license file.
Module |
Parameter |
Mandatory |
Description |
---|---|---|---|
LicFile |
formatVersion |
Yes |
Version of the license file format. The format version of each XML license file is 3.00 or later. |
GeneralInfo |
CopyRight |
Yes |
Copyright information. |
LSN |
Yes |
The license serial number is also known as the Fulfillment ID, and is the unique identifier of a license file. You can search for a license file on license management pages of the ESDP website. To check the LSN, run the display license command. |
|
LicType |
Yes |
COMM indicates a permanent commercial license that has been purchased. DEMO indicates a non-permanent-commercial license. |
|
GraceDay |
Yes |
Number of days in the grace period after the license file expires. The value is fixed at 60. |
|
Creator |
Yes |
Publisher information. This parameter has a fixed value of Huawei Technologies Co., Ltd.. |
|
Issuer |
Yes |
Name of the user who generated the license file in the license distribution system. For a commercial license file, the value is fixed at License Distribution Center. For a non-commercial license file, the value is the applicant information. |
|
CreateTime |
Yes |
Time when the license file was created, and is the local system time of the license distribution system, rather than the system time of the NE that uses the license. |
|
CustomerInfo |
Customer |
No |
Customer name. |
Country |
No |
Country name. |
|
Office |
No |
City name. |
|
NodeInfo |
Node |
Yes |
Device ID. |
Des |
No |
Device description. |
|
LockModel |
No |
Lock mode. NODELOCK indicates single node lock mode, and DUALLOCK indicates dual node lock mode. By default, the single node lock mode is used. |
|
ESN |
Yes |
Electronic serial number of a device, also called device fingerprint. It is a string of characters that uniquely identifies a device and ensures that a license is authorized to the device. |
|
SaleInfo |
OfferingProduct |
Yes |
Product name and version. |
SaleItem |
Yes |
Sales item code. |
|
Value |
Yes |
Sales volume. |
|
DesChs |
No |
Description of the sales item, in Chinese. |
|
DesEng |
No |
Description of the sales item, in English. |
|
CapacityKey |
No |
Resource control service license item. Value indicates the number of authorized resources. validDate indicates the authorization expiration date. If the date is PERMANENT or left blank, the authorization is permanent. |
|
FeatureKey |
No |
Function control service license item. The Value is fixed at 1. validDate indicates the authorization expiration date. If the date is PERMANENT or left blank, the authorization is permanent. |
|
KeyInfo |
productName |
Yes |
Product name and version. |
CapacityKey |
No |
Resource control service license item. name indicates the sales item name; group indicates the sales item type; Value indicates the number of authorized resources; validDate indicates the authorization expiration date. If the date is PERMANENT or left blank, the authorization is permanent. |
|
FeatureKey |
No |
Function control service license item. name indicates the sales item name. group indicates the sales item type. The Value is fixed at 1. validDate indicates the authorization expiration date. If the date is PERMANENT or left blank, the authorization is permanent. |
|
Footer |
CommonSign |
Yes |
Signature. method indicates the encryption algorithm. Currently, the 1-RSA1024, 2-RSA2048, 3-ECC163, and 4-ECC233 encryption algorithms are supported. |
ProductSign |
Yes |
The DAT license files are used in versions earlier than V800R011 (released in 2018 or earlier). Figure 1-15 shows an example of a DAT license file.
Table 1-8 describes the parameters in a DAT license file.
Parameter |
Mandatory |
Description |
---|---|---|
LicenseSerialNo |
Yes |
The license serial number is also known as the Fulfillment ID, and is the unique identifier of a license file. You can search for a license file on license management pages of the ESDP website. To check the LSN, run the display license command. |
Creator |
Yes |
Publisher information. This parameter has a fixed value of Huawei Technologies Co., Ltd.. |
CreatedTime |
Yes |
Time when the license file was created. The time is the local system time of the license distribution system, rather than the system time of the NE that uses the license. |
Country |
Yes |
Country name. |
Custom |
Yes |
Customer name. |
Office |
Yes |
Region name or user ID in a contract. |
Sign |
Yes |
Signature. |
Product |
Yes |
Product name. |
Feature |
Yes |
License item type. |
Esn |
Yes |
Electronic serial number of a device, also called device fingerprint. The ESN is a string of characters that uniquely identifies a device and ensures that a license is authorized to the device. If there are multiple ESNs, the license file can be allocated to multiple devices. |
Attrib |
Yes |
Six fields separated by commas from left to right:
|
Version |
Yes |
Product version. |
Libver |
No |
Version of the license file format. |
Resource |
No |
Resource control service license item. The value following the equal sign (=) in each license item indicates the number of authorized resources. |
Function |
No |
Function control service license item. The value following the equal sign (=) in each license item is fixed at 1. |
Comment |
No |
Comment information, such as the project name, order, and contract. |
B Common License Commands
Function |
Command |
|
---|---|---|
Displaying detailed license information |
display license display license verbose |
|
Displaying the ESN of the current device |
display license esn |
|
Checking whether a license file is valid |
license verify |
|
Activating a license file |
license active file-name |
|
Activating/Displaying Hardware RTUs |
active port-basic slot slotid card cardid port port-list display license resource usage port-basic { all | slot slotid } [ active | deactive ] |
|
Activating/Displaying service licenses |
SRv6 |
active port-srv6 slot slotid card cardid port port-list display license resource usage port-srv6 { all | slot slotid } [ active | deactive ] |
L3VPN |
active port-l3vpn slot slot-id card card-id port port-list display license resource usage port-l3vpn { all | slot slotid } [ active | deactive ] |
|
EVPN |
active port-evpn slot slotid card cardid port portlist display license resource usage port-evpn { all | slot slotid } [ active | deactive ] |
|
VXLAN |
active port-vxlan slot slotid card cardid port portlist display license resource usage port-vxlan { all | slot slotid } [ active | deactive ] |
|
MACsec |
active port-macsec slot slotid card cardid port port-list display license resource usage port-macsec { all | slotslotid } [ active | deactive ] |
|
FlexE |
active port-flexe slot slotid card cardid port port-list display license resource usage port-flexe { all | slot slotid } [ active | deactive ] |
|
HQoS |
active port-hqos slot slotid card cardid port port-list display license resource usage port-hqos { all | slot slotid } [ active | deactive ] [ slave ] |
|
Channelized sub-interfaces |
active port-mode-channel slot slotid card cardid port port-list display license resource usage port-mode-channel { all | slot slotid } [ active | deactive ] |
|
BRAS access |
active port-bras slot slotid card cardid port port-list display license resource usage port-bras { all | slot slotid } [ active | deactive ] [ slave ] |
|
Port slicing |
active port-slicing slot slot-id card card-id port port-list display license resource usage port-slicing |
|
Service enhancement scenarios (Segment Routing, VXLAN, EVPN, HQoS, and L3VPN) |
active port-service-enhance slot slot-id card cardid port port-list display license resource usage port-service-enhance { all | slot slotid } [ active | deactive ] |
|
Aggregation scenarios (Segment Routing, Telemetry, NG MVPN, and IPv6) |
active port-aggregation slot slot-id card cardid port port-list display license resource usage port-aggregation { all | slot slotid } [ active | deactive ] |
|
Core&aggregation scenarios (Segment Routing, RSVP-TE, MPLS TE, VXLAN, and HQoS) |
active port-core-aggregation slot slot-id card cardid port port-list display license resource usage port-core-aggregation { all | slot slotid } [ active | deactive ] |
|
Peering gateway-specific license scenarios (NE8000-X: BGP RPD, BGP Flowspec, BMP, and RPKI; M2: Segment Routing, Telemetry, and IPv6) |
active port-peering slot slot-id card card-id port port-list display license resource usage port-peering { all | slot slotid } [ active | deactive ] |
|
Trial license |
Enabling/Disabling a trial license |
license trial enable license trial disable |
Displaying detailed trial license information |
display license trial |
|
Enabling/Displaying the emergency mode of a license |
license emergency display license emergency |
|
Displaying the license state |
display license state |
|
Displaying the usage of active license resource items |
display license resource usage |
|
Displaying the remaining days of the grace period |
display license state trial |
|
Configuring/Displaying the license resource alarm threshold |
set license license-item threshold threshold-value display license threshold |
|
Revoking the current license |
license revoke |
|
Displaying the revocation code of the current invalid license |
display license revoke-ticket |
|
Saving a license file |
license export file-name |
|
Deleting a license file |
delete cfcard:/XXXX.xml delete salve#cfcard:/XXXX.xml |
For some product models (including the NE8000-M1, and NE8000-M6), the activation command is active XXXX slot slot-id port port-list (card card-id is not included).
Some service license activation commands may activate a license for a specified service on a specific board. When running the commands, ensure that they are the same as those in the display license command output.
The list of the preceding commands may vary according to products and versions. When running the commands, refer to the display license command output or Command Reference of the involved product and version.
C Applying for the ESDP Website Permission
Procedure
- Log in to https://w3.huawei.com/iauth/#/searchRolePage?keepData=1&isDraft=.
- Enter Carrier GTS or Enterprise GTS in the text box on the right and click Search.
- Select the check box in the search result and click Next, as shown in Figure 1-16.
- Enter basic personal information and click Submit.
After the application is approved, you obtain the ESDP website permission.
- Log in to the ESDP website (https://app.huawei.com/sdp/).
Check whether Current Role in the upper right corner is either Carrier GTS or Enterprise GTS. If so, the application is successful. Otherwise, trace the approval process.
D Adjusting License Resources Among Multiple Devices (Splitting a License)
If hardware RTU or service license resources are insufficient and license capacity cannot be expanded, you can adjust license resources among multiple devices. For example, if device A has 20 SRv6 Function Licenses (per 100GE), all of which are in use, and device B also has 20 SRv6 Function Licenses (per 100GE), but with only 10 in use, you can allocate the 10 available resources on device B to device A.
Prerequisites
- You have obtained the ESDP website permission.
- You have obtained the ESNs of the devices involved.
- (Optional) You have obtained the revocation code. If no revocation code is obtained, approval is required.
Context
The ESDP website allows you to adjust only resources of licenses with the same customer, product, and version. The total number of license resources before and after the adjustment must be the same.
Procedure
- Log in to the ESDP website (https://app.huawei.com/sdp/).
- In the navigation tree on the left, choose , as shown in D Adjusting License Resources Among Multiple Devices (Splitting a License).Figure 1-17 Adjusting a license
- Select Application Stage and Source Equipment based on the actual project information.
If Application Stage is set to After PAC (Preliminary Acceptance Certificate) or Source Equipment is set to Without revocation code (approval required), enter the application reason and other information as prompted.
- Click Add. In the dialog box that is displayed, enter search criteria, select multiple target devices, and click Confirm.
- Select the devices whose license resources are to be adjusted, and enter the number of resources to be adjusted in Changed Value, as shown in Figure 1-18.
- Click Submit and confirm the operation.
- Click Download to save the adjusted license file of each device locally.
- Upload and activate the adjusted license files.
E Troubleshooting Common License Activation Problems
The File Does Not Exist (Error: The specified file does not exist)
Possible Causes
- The license file name in the activation command is incorrect.
- The license file fails to be uploaded.
- The license file is not copied to the slave main control board.
Procedure
- Check the license file.
dir Directory of cfcard:/ Idx Attr Size(Byte) Date Time FileName ... 8 -rw- 13,012 Apr 07 2020 23:10:47 LICXXXX_VXXXRXXX_XXXX.xml ...
For a device with two main control boards, check whether the involved license file also exists on the slave main control board.
dir slave#cfcard:
If the license file name in the activation command is different from the actual file name, run the activation command again based on the actual file name.
If the license file to be activated is not found, go to the next step.
If the license file fails to be activated on the slave main control board, run the following command and then run the activation command again:
copy cfcard:/LICXXXX_VXXXRXXX_XXXX.xml slave#cfcard:/LICXXXX_VXXXRXXX_XXXX.xml
- Upload and activate the license file.
The License File Format Is Invalid (Error: The format of the license file is invalid)
Possible Causes
- The license file name in the activation command is incorrect.
- The file name extension of the uploaded license file is not .xml or .dat.
Procedure
- Check that the file name in the activation command is correct.
If the file name is incorrect, run the command again with the correct file name.
- Check that an XML or DAT license file is uploaded to the device.
If a correct license file is available locally, go to the next step. Otherwise, apply for and download a new license file.
- Upload and activate the license file.
ESNs or Software Versions Do Not Match (Error: The ESN or version of the license file does not match with the device)
Symptom
During license activation, Error: The ESN or version of the license file does not match with the device is displayed.
Possible Causes
- The ESN bound to the license does not match the ESN of the device.
- The software version in the license does not match that of the device.
Procedure
- Check and record the new ESN of the device.
display license esn
Use the text editor to open the copy of the license file and compare the recorded ESN with that in the license file. If they are different, the ESN bound to the license is incorrect. If you attempt to activate multiple license files for different devices, ensure that the license files are correctly uploaded.
- Check the software version.
display version
Compare the displayed software version with the software version in the license file. If they are inconsistent, the software version in the license is incorrect.
- Apply for and download a new license file.
- Upload and activate the license file.
Product Types Do Not Match (Error: The product type of the license file does not match with the device)
Symptom
During license activation, Error: The product type of the license file does not match with the device is displayed.
Procedure
- Check the type of the device.
display version
Use the text editor to open the copy of the license file and compare the displayed device type with the product type in the license file. If they are different, the type of the product bound to the license is incorrect.
- Apply for and download a new license file.
- Upload and activate the license file.
Verification Fails Consecutively (Error: Verify license failed)
Possible Causes
License activation is performed multiple times when ESNs or versions do not match.
If activation is performed on a license file with an incorrect ESN or software version for the first time, Error: The ESN or version of the license file does not match with the device is displayed. In this case, the license module automatically enters the grace period.
If activation is performed on a license file with an incorrect ESN or software version for multiple times, the license module cannot enter the grace period.
Procedure
- Check and record the new ESN of the device.
display license esn
Use the text editor to open the copy of the license file and compare the recorded ESN with that in the license file. If they are different, the ESN bound to the license is incorrect. If you attempt to activate multiple license files for different devices, ensure that the license files are correctly uploaded.
- Check the software version.
display version
Compare the displayed software version with the software version in the license file. If they are inconsistent, the software version in the license is incorrect.
- Apply for and download a new license file.
- Upload and activate the license file.
How Do I Retrieve a License After It Is Revoked by Mistake?
Symptom
The license module enters the grace period. The output of the display license revoke-ticket command shows a revocation code.
Procedure
- Check and record the revocation code.
Record the displayed revocation code. You can also run the following command to view the revocation code:
display License revoke-ticket Info: The revoke ticket is LIC20201120YBXXXX:0E47B21121D40C4BBBBB8E8255A437E6D532XXXX.
- Download a new license file.
- Upload the license file.
- Verify the license file.
license verify LICXXXX_VXXXRXXX_XXXX.xml Info: Verify license succeeded.
If Verify license succeeded is displayed, verification is successful. Otherwise, verification has failed due to an invalid license file, or an ESN, version, or product type mismatch. For details on how to solve these issues, see E Troubleshooting Common License Activation Problems.
- Activate the license file.
license active LICXXXX_VXXXRXXX_XXXX.xml Now activing the license....done. Info: Succeeded in activating the license file.
Hardware RTU Activation Fails
Possible Causes
The ports for which hardware RTUs fail to be activated are not controlled by the hardware RTUs. The possible causes are as follows:
- The ports for which hardware RTUs fail to be activated are not CM ports.
- The ports for which hardware RTUs fail to be activated are CM ports, but bandwidth restrictions are not imposed on them due to software implementation and hardware production batch issues. This issue occurs only in rare cases, and does not consume license resources or compromise services.
Procedure
- Check the slots of CM boards.
system-view license active port-basic slot ? <3,5> The available slot return
If the slots of the boards housing the ports for which hardware RTUs fail to be activated are not in the list of the slots obtained in the previous step, the boards are not CM boards. In this case, no action is required. Otherwise, go to the next step.
- Check that bandwidth restrictions are imposed on the ports.
display interface brief ... InUti/OutUti: input utility/output utility Interface PHY Protocol InUti OutUti inErrors outErrors 100GE1/0/0(100M) down down 0% 0% 0 0 100GE1/0/1(100M) down down 0% 0% 0 0 ... 25GE2/0/0(10G) down down 0% 0% 0 0 25GE2/0/1(100M) down down 0% 0% 0 0 ... 100GE3/0/0 down down 0% 0% 0 0 100GE3/0/1 down down 0% 0% 0 0 ...
All ports with (100M) displayed in the display interface brief command output are CM ports with the default bandwidth restriction, for example, 100GE1/0/0(100M). If the bandwidth restriction in the brackets is not 100M, but is less than the rate of the physical port, for example, 25GE2/0/0(10G), at least one enabling hardware RTU has been activated.
If the ports for which hardware RTUs fail to be activated do not have the (100M) bandwidth restriction flag, no bandwidth restrictions are imposed on the ports. In this case, no action is required. Otherwise, go to the next step.
- Collect fault information, and contact Huawei technical support engineers.
Service License Activation Fails
Symptom
During service license activation, Error: Wrong parameter found at '^' position is displayed.
Possible Causes
- The service license is a function control service license that is automatically activated with the license file. Therefore, no action is required.
- The service license is used only for a specified board and cannot be allocated to ports on other boards.
Procedure
- Check whether a function control service license of the involved service exists.
SRv6 service licenses are used as an example. If an SRv6 Function License exists, SRv6 has been enabled globally on the device. Otherwise, go to the next step.
display license ... CR8SX0SRV6C1 -- 1 NetEngine 8000 SRv6 Function License LCR8SX0SRV6C1 Function YES NetEngine 8000 SRv6 Function License ...
- Check the slots of the boards for which service licenses of the involved service can be allocated.
SRv6 service licenses are used as an example.
system-view license active port-srv6 slot ? <3,5> The available slot return
If the slots of the boards for which the service licenses of the involved service fail to be activated are not in the list of the slots obtained in the previous step, the service licenses cannot be allocated to the ports on these boards.
- Configure the involved service on the ports for which the service licenses of the involved service fail to be activated.
If the configuration succeeds, no other actions are required. Otherwise, go to the next step.
- Collect fault information, and contact Huawei technical support engineers.
- License, License Classification, and License Mechanism
- Checking Whether a License Has Been Activated Before Delivery
- Applying for and Activating a License File for a Newly Delivered Device
- Activating Hardware RTUs and Service Licenses
- Activating a Trial License
- Replacing a License with a Commercial License
- Revoking a License and Activating Another After the ESN Is Changed (Due to Part Replacement for Example)
- Managing a License During Version Upgrade or Downgrade
- Checking the Remaining Validity Period of a License
- Manually Enabling the Emergency Mode (When a Natural Disaster Occurs or the Grace Period of the License Is About to Expire)
- Using the License Query Tool to View License Items
- A Description of Parameters in the License File
- B Common License Commands
- C Applying for the ESDP Website Permission
- D Adjusting License Resources Among Multiple Devices (Splitting a License)
- E Troubleshooting Common License Activation Problems
- The File Does Not Exist (Error: The specified file does not exist)
- The License File Format Is Invalid (Error: The format of the license file is invalid)
- ESNs or Software Versions Do Not Match (Error: The ESN or version of the license file does not match with the device)
- Product Types Do Not Match (Error: The product type of the license file does not match with the device)
- Some License Control Items Are Missing (Warning: No product feature is present in the license file)
- The License File Expires (Info: The license file has expired)
- Verification Fails Consecutively (Error: Verify license failed)
- How Do I Retrieve a License After It Is Revoked by Mistake?
- Hardware RTU Activation Fails
- Service License Activation Fails