Professional Documents
Culture Documents
Appendix 2 - Operation Guide To OMStar Parameter Check V1.4
Appendix 2 - Operation Guide To OMStar Parameter Check V1.4
Appendix 2 - Operation Guide To OMStar Parameter Check V1.4
Confidential
Product Version Total 28 pages
Change History
Date version change Description Author
Table of Contents
1 Introduction....................................................................................................................................5
2 Version Requirement...................................................................................................................6
3 Environment Configuration........................................................................................................7
3.1 OMStar Environment Installation......................................................................................................................7
3.2 Soft Parameters..................................................................................................................................................7
3.3 Environment Configuration Method..................................................................................................................8
Abstract:
OMStar is a Huawei-developed tool used to perform operations in batches on eNodeBs,
including parameter check, coverage assessment, traffic analysis, and network check. This
document describes the method of parameter check in details.
List of abbreviations:
1 Introduction
2 Version Requirement
3 Environment Configuration
MO Indicates the unit for parameter configuration on the eNodeB and is the operation object of
the MML command.
Parameter ID Indicates the parameter ID and is an MO member, corresponding to an item in the MML
command.
Parameter Indicates the parameter name, proving description of a parameter.
Name
MML Indicates the MML command used to configure or modify the MO.
Command
Index Used to identify a parameter if the MO is the same. This field can be set yes or no. This field
cannot be modified when the template is customized.
Default Value Indicates the default value stated in the template, with which the actual eNodeB parameter
settings are compared.
Unit Indicates the unit of a parameter.
Attribute Indicates the MO type. All parameters can be classified into three types: Equipment,
Transport, and Radio.
Level Indicates the level of an MO, only applicable to radio parameters but not equipment and
transport parameters. Radio parameters can be classified into eNodeB-level parameters, cell-
level parameters (including cell and cell plus), and other-level parameters.
Category Indicates the parameter type. The user can select a type of parameters for check.
IsCheck Indicates whether to check. Yes indicates to check. No indicates not to check.
Select an NE and start the backup. After the backup is complete, click Download to OMC
Client to download the backup file to a local disk.
Decompress
After opening the folder after decompression, view the LMT.XML file, which is the required
file.
NOTE
The version of the XML2MML tool needs to support the eNodeB version; otherwise, the resolution will
fail. In case of a resolution failure, contact R&D personnel.
The XML2MML tool is obtained from the accessory packet of the generic manual.
1. Convert a single XML file to an MML file.
Step 1 Open the XML2MML tool and select a data file.
Step 2 Click Browse, select an XML file, and then click Export. The generated MML file is stored
in the same directory of the XML file.
----End
Step 2 Click Browse, select the directory where XML files are stored, and then click Export All.
The generated MML files are stored in the XML2MMLRESULT folder. Even if XML files
are stored in a multi-level directory, the tool can automatically identify the files.
----End
NOTE
You are advised to check a total of no more than 200 eNodeBs at a time; otherwise, the program is
vulnerable to faults.
Step 1 Choose OMStar V500R006C02 > Open the OMStar V500R006C02 Transdata. The
Login Server window is displayed.
Step 2 In the Login Server window, select the SQL server, enter the user name and password, and
then click Login.
NOTE
Select the local SQL database for login. If the SQL Server has not been installed, see chapter 2 in
Maintenance SOP of OMStar V500R006C02 to quickly install the SQL Server.
NOTE
Alternatively, in the Project View navigation tree, right-click LTE and choose New Project from the
shortcut menu. If the Project View navigation tree is unavailable, choose Settings > Work Space.
The selected version in the New Project dialog box must be compatible with the eNodeB
version.
NOTE
Select the eNodeB version in the Version List field, enter a user-defined project name in the Name
field, and then select a local folder in the Project Location field.
----End
Default Value Indicates the default value stated in the template, against which the actual eNodeB parameter
setting is checked.
IsCheck Indicates whether to check. Yes indicates to check. No indicates not to check.
The parameter check template is stored in the accessory package of the generic manual
(Appendix 1: Default Performance Parameter Check 3.0).
Save the modified template and import it into the created project before parameter check.
Ensure that the project corresponding to the eNodeB version has been created before
parameter check.
Step 1 Choose OMStar V500R006C02 > OMStar V500R006C02 to open the OMStar. The User
Login window is displayed.
Step 2 In the User Login window, select the SQL server, enter the user name and password, and then
click Login.
Select the local SQL database for login. If the SQL Server has not been installed, see chapter
2 in Maintenance SOP of OMStar V500R006C02 to quickly install the SQL Server.
Step 3 Select the project compatible with the eNodeB version in the Open Project dialog box.
Step 4 Choose Trouble Shooting > Configure Analysis > eNodeB Configure Check in the
navigation tree on the left.
Step 5 Click to import the customized template. For details, see section 4.2.2 "Customizing a
Parameter Check Template."
NOTE
For details about customizing a template, see section 4.2.2 "Customizing a Parameter Check Template."
Click Source Script to select the save path of the MML file.
Press Ctrl+A to select all MML files in the directory and click Open.
Click OK to start the parameter check. If Display all parameters in the Configuration
Parameter Check dialog box is selected, all parameters of the eNodeB are displayed,
including those consistent with default values in the template.
NOTE
Select an MML file from the drop-down menu in the Source Script field, that is, the MML file
converted from the XML file in section4.1.2 "MML Data Conversion." (You can simultaneously select
multiple files for check. The parent directory of the file is displayed if multiple files are to be selected
and the save path of the file is displayed if a single file is to be selected. In this example, two files are
selected.) Set Check Mode based on the requirement that only abnormal values are displayed or all
parameters are displayed. Then, click OK to start the check.
Step 8 Click to export the generated check report. The exported file is in XLS format.
----End
The check report in the preceding figure shows that the value (212) of the
REFERENCESIGNALPW parameter of eNodeB 110001 and 110003 is inconsistent with the
default value (182) in the template.
The OMStar differently colors the areas displaying data of different eNodeBs if parameter
check is performed in batches. For example, the area displaying parameters of eNodeB 11000
is in yellow and that of eNodeB 110003 in light blue.
Click a sheet to view the comparison results of parameters of one type or level.
----End
Step 2 Select a save path, enter a template name, and then click Save.
----End
Icons Description
Cancel
Cut
Copy
Paste
Sort A to Z
Sort Z to A
Icons Description
Filter
Refresh
Open as Excel
Inserting a row: Right-click a row and choose Insert Row from the shortcut menu to insert a
row before the clicked row.
Deleting a row: Right-click a row and choose Delete Row from the shortcut menu to delete
the clicked row.
NOTE
The default template is overwritten if Overwrite default template is selected. In this case, the modified
template can be directly loaded next time when the tool is open. The default template is not overwritten
if Save As is selected. In this case, select a save path. The default template is still loaded next time when
the tool is open.
----End