No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


eSight V300 License User Guide (For Huawei Engineer) 22

This document describes the application procedure for licenses of eSight products in various scenarios and the way to use these licenses.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Rectification Process

Rectification Process

The process of license rectification caused by R&D is divided into the following two phases:

  • Warning for software license rectification
  • Implementation of software license rectification onsite

Announcing the Rectification on Software License Issues (Owner: R&D)

If a project cannot be successfully delivered because of a license issue, the product R&D department will give a notice for license rectification based on the affected scope and measures. The process is as follows:

Implementation of Software License Rectification Onsite (Led by the Frontline)




Required Time

Frontline delivery personnel

Create a software license batch rectification application.

  • Create an application for batch replacement (W3 link:, fill in the information, estimate required labor, and attach the license information. The operations are as follows:
  • Set Regional division, Department*, Purpose*, and Product name* based on the site requirements.

    Note: The entered product name must be the product involved in the rectification notice, which may be different from the name of the product whose license is to be rectified onsite. For example, if the rectification of product A leads to the rectification of product B's license, the entered product name should be product A. However, in the license rectification demand template, the name of product B should be entered.

  • Set Precaution title* and Precaution ID* based on the warning rectification notice released on Support-E by the R&D team.

    Note: Precaution ID* is the document ID of the rectification notice on Support-E, for example, EUC-R-A-2013024. For detailed rules, see related announcements of the enterprise business.

  • Set Consignment or not* to NO and Relevant license or not* to YES.
  • If only a few new control items are delivered in the rectification, set Withdraw the Original License or not * to NO. If the entire license file is delivered, the original license needs to be withdrawn and invalidated in the ESDP system. In this situation, set Withdraw the Original License or not * to YES and attach the original license file to the batch rectification application.
  • Fill in Attachment 2 License Rectification Demand Template for XX Site of XX Network XX eSight Product_20XX-XX-XX.xlsm based on the actual condition. One template is required for each site:
  • Customer Name*: full name of the customer. For the channel sales mode of the enterprise business, enter the latest customer name in the contract. Only the full name can be used. If the customer name cannot be found in the ERP system, the name is incorrectly entered by the frontline, and the application cannot be submitted. (For the product resold by carriers, the customer name must be the same as that in the onsite license file.)
  • Quantity*: number of license items required by the product to be rectified. This parameter must be set by onsite engineers.
  • Packing Instructions(Site_Info) *: site to which the product to be rectified belongs. The parameter must be set by frontline engineers based on the site where an NE resides. The site name for each type of NE must be unique. Each license rectification demand template corresponds to only one site. If the rectification involves multiple sites, attach all the templates to the batch rectification e-Flow.
  • Upload the completed Attachment 2 License Rectification Demand Template for XX Site of XX Network XX eSight Product _20XX-XX-XX.xlsm and existing license files used on the live network (if there are formal commercial license files) to the license rectification e-Flow.


Service representative of the product engineering department/maintenance department

Serve as the technical center approver.

Check whether information in applications is accurate and reasonable.


PDT manager

Approve the applications.

Approve the software license demand list and frontline rectification fee.


Software license rectification specialist

Submit an order in the ERP system.

Submit an order in the ERP system according to the license demand list of each site, and provide the internal contract ID and order ID in the e-Flow. Within half a work day after this operation, the supply chain will generate license files based on the preceding contract and order information and deliver the license files to the ESDP system. Then frontline delivery personnel can search for and download required license files in the ESDP system based on the contract and order IDs provided in the batch rectification e-Flow.


Software delivery center engineer

Withdraw and invalidate the old license file.

If the entire original license needs to be replaced by a new license (not adding some license items), the original license file must be withdrawn on the license platform and invalidated after the new one is delivered.


Frontline delivery personnel

Confirm and close the application.

Confirm that the new license meets the service requirements and close the application.


Updated: 2020-01-22

Document ID: EDOC1000071873

Views: 56941

Downloads: 721

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next