Operation Guide To The OMStar

Product Name Confidentiality
OMStar INTERNAL
Product Version
79 Pages
OMStar V500R001C00SPC200
OMStar V500R001C00SPC200 Maintenance

SOP Guide
(For internal use only)
Prepared by Wu Zhibiao Date 2010-08-30

Liang Kun, Mou Weiyan, Jia
Xiaorun, Wu Yuanjun, Tang
Reviewed by Zhihui, and Guo Hongliang Date 2010-9-1
Approved by Li Chengjun Date 2010-9-3
Huawei Technologies Co., Ltd.

All Rights Reserved
OMStar V500R001C00SPC200 Maintenance SOP Guide INTERNAL
Revision Record
Date Revision Description Author
Version
2010-8-30 V1.0 Draft completed. Wu Zhibiao and Wu

Yuanjun
2010-9-3 V1.01 Modified according to review comments Wu Zhibiao
2010-9-28 V1.02 Modified Using the OMStar part Wang Sen
3010-9-29 V1.03 Modified according to review comments Wang Sen
2017-6-21 Huawei Confidential Page 2 of 79

Contents
1 Introduction....................................................................................................................................6
1.1 Intended Audience.............................................................................................................................................6
1.2 Application Scope..............................................................................................................................................6
1.3 Important Hints..................................................................................................................................................6
1.4 Software Acquisition Modes..............................................................................................................................7
1.5 Installation Requirements..................................................................................................................................8
1.5.1 Installation Environment Specification....................................................................................................8
1.5.2 Hard Disk Specification............................................................................................................................8
1.5.3 Networking Modes...................................................................................................................................8
1.6 Quick Guide to the Software.............................................................................................................................9
2 Installing the SQL Server..........................................................................................................10

2.1 Installing the SQL Server 2000 Personal Edition............................................................................................10
2.2 Installing the SQL Server 2000 SP4................................................................................................................19
3 Installing the NIC........................................................................................................................25

3.1 Installing the NIC Tool....................................................................................................................................25
4 Installing the OMStar.................................................................................................................28

4.1 Installing the GENEX Shared Component......................................................................................................28
4.2 Installing the OMStar Tool..............................................................................................................................30
4.3 Applying for and Installing a License..............................................................................................................35
5 Using the NIC...............................................................................................................................43

5.1 Installing the Mediation Layer Matching the NE Version...............................................................................43
5.2 Setting the IP Address of the FTP Server.........................................................................................................45
5.3 Using the NIC to Collect Data.........................................................................................................................47
5.3.1 Creating an NE.......................................................................................................................................47
5.3.2 Customizing an SOP Collection Scenario..............................................................................................50
5.3.3 Creating a Collection Task......................................................................................................................50
5.3.4 Viewing the Collection Result................................................................................................................54
6 Using the OMStar........................................................................................................................56

6.1 Introduction to the Mini-OMStar.....................................................................................................................56
6.2 Starting the Mini-OMStar................................................................................................................................57

6.3 Creating a One-key Analysis Task...................................................................................................................59

6.4 Summarizing Reports......................................................................................................................................64
6.4.1 Main UI...................................................................................................................................................64
6.4.2 Function Buttons.....................................................................................................................................64
7 Help Information.........................................................................................................................67
8 FAQs...............................................................................................................................................68
8.1 FAQs Related to the SQL Server.....................................................................................................................68
8.1.1 How to Handle the SQL Server Installation Failure?.............................................................................68
8.1.2 Can the MSDE 2000 Be Used?..............................................................................................................69
8.1.3 Can the SQL Server 2005 Be Used?.......................................................................................................69
8.2 FAQs Related to the NIC.................................................................................................................................69
8.2.1 How to Handle the NIC Start Failure?...................................................................................................69
8.2.2 How to Handle the Failure of Adding NEs to the NIC?.........................................................................70
8.2.3 The System Prompts "Adaptation layer does not match the C version of the NE." When the User Adds
an NE...............................................................................................................................................................70
8.2.4 Data Collection Failure Scenarios (Configuration, Performance Measurement, MML, ).................70
8.2.5 Why Does It Take Time for the NIC to Collect Inspection Data?..........................................................70
8.2.6 How to Add NEs More Efficiently by Using the Batch Import Function?............................................71
8.2.7 The System Prompts "Please check whether the NIC application services and the database services run
normally." During Batch Management of NEs................................................................................................73
8.3 FAQs Related to the OMStar and the Transdata..............................................................................................73
8.3.1 The System Prompts the Incorrect Program Configuration at Startup of the Transdata........................73
8.3.2 The System Prompts Project Information Loading Failure and Invalid Parameters at Startup of the
Transdata..........................................................................................................................................................74
8.3.3 How to Handle the Automatic Import and Analysis Failure of the Transdata?......................................74
8.3.4 Is the OMStar Compatible with Office 2007?........................................................................................75
8.3.5 Does the OMStar Support Windows 7?..................................................................................................75

OMStar V500R001C00SPC200 Maintenance SOP Guide
Keywords
Maintenance SOP, OMStar, NIC
Abstract
This document provides guidance for quick installation and use of the OMStar and the NIC
for routine inspection and maintenance SOP. It does not involve the details of specific
technologies and services. In case of any exception or question related to the installation and
use, you can refer to the FAQs to handle it or contact relevant engineers for help according to
the help information.
List of Abbreviations
Abbreviation Full Name
SOP Standard Operation Procedure

NIC Network Information Collection
OMStar Operation & Maintenance Star
Transdata Transdata

1 Introduction
1.1 Intended Audience

This document is intended to guide readers to deploy MAINEX operation and maintenance
(OM) tools (including the NIC and the OMStar) to implement automatic network inspection
for routine OM tasks such as maintenance SOP.
It is intended for engineers responsible for routine inspection and delivery of maintenance
SOP.
1.2 Application Scope

This document describes how to use the NIC V100R006C00T and the OMStar
V500R001C00SPC200 to support the maintenance SOP of GSM8.1.
It is used only for automatic collection and analysis of NE information by using the preceding
tools. The scenarios of manual data collection and analysis are not involved.
1.3 Important Hints

1. The language version of the NIC must be consistent with that of the NE.
2. This document describes how to obtain, install, and use the NIC of English version.
3. The source files of the installation package of the SQL Server 2000 must be saved in a
directory that does not contain Chinese characters; otherwise, the installation may fail.
4. The OMStar V500R001 and the OMStar V500R006 can share the SQL Server. You do
not need to install the SQL Server repeatedly.
5. Sufficient space should be available for installing the NIC and the OMStar. For details,
see section 1.5.2"Hard Disk Specification."
6. The name of the NIC collection task for inspection or SOP can contain only letters (az
and AZ), numbers (09), and underline (_),the max number of the task name must less
then 27; otherwise, the subsequent automatic analysis may fail.
7. Disable hard disk shutdown, standby mode, and sleep mode of the PC for NIC
collection.

8. The special notes on the tool installation and usage are marked red.
1.4 Software Acquisition Modes

Product Tool Name Tool Description Tool Acquisition Mode
Version Version
GBSS8.1 NIC NIC_install Main program of the V100R006 http://support.huawei.com

NIC. C00T Log in to the Web site, and then
iManagerM2000_ Mediation layer of / choose Software center > Version
BSC6000_MATC the BSC6000, which Software > Wireless Product Line
H_ENG_BSC600 is installed after the > Wireless OSS > MAINEX > NIC
0V900R008C12 main program of the > NIC V100R006 > NIC
NIC. V100R006C00T.
OMSt OMStar Main program of the V500R001 http://support.huawei.com

ar V500R001C00_E OMStar, including C00 Log in to the Web site, and then
NG_SOFT the Transdata data SPC200 choose Software center > Version
import tool and the Software > Wireless Product Line
OMStar data analysis > Wireless OSS > MAINEX >
tool. OMSTAR > OMSTAR V500R001
GENEX Shared GENEX shared / > OMSTAR
20060729 component, which is V500R001C00SPC200.
installed prior to the
main program of the
OMStar.
Check Summary Summary table that /
for GBSS collects the reports of
Network multiple NEs
Inspection.xls generated by the
OMStar. It can be
used without being
installed.
SQL SQL Server 2000 SQL Server 2000, SQL Obtain the software from the IT
Server Personal Edition which can be shared Server administrator of the corresponding
by the OMStar 2000 representative office.
V500R001 and the Personal Obtain the software from the file
OMStar V500R006. Edition mirror server of the corresponding
You do not need to office/sub-regional division.
install the SQL Server
repeatedly. Download the setup program of the
SQL Server 2000 from \\lg-
sc_sql_server_20 Patch file of the SQL SP4 fs\Rnd\Software\2.ITapply\0.Datab
00_sp4 Server, which is ase\SQL Server\SQL Server 2000
installed after the personal_chn.
SQL Server 2000. Download the patch file of SQL
Server 2000 SP4 from \\lg-
fs\Rnd\Software\2.ITapply\0.Datab
ase\SQL Server\patch.

1.5 Installation Requirements

1.5.1 Installation Environment Specification
Hardware Requirement Software Requirement
Model: common PC OS: Windows XP SP3 or more advanced

CPU: P4 1.8 GHz or higher Windows Server
Memory: 1 GB or higher Database: SQL Server 2000 Personal Edition
SP4
Hard Disk: 80 GB or higher
Browser: Internet Explorer 6.0 or later
Accessories: Network adapter/17-inch LCD
display Others: Office 2003 or Office 2007
1.5.2 Hard Disk Specification

Software Required Required Space for Required Space for
Space Collection and Analysis Collection and Analysis
(Single BSC) (30 BSCs)
NIC 330 MB Collected data package: 150 Collected data package: 4 GB

MB/BSC
OMStar 600 MB Decompressed files of the Decompressed files of the
collected data package: 200 collected data package: 5 GB
MB/BSC
SQL Server 250 MB Required space for saving Required space for saving
temporary data in the database: temporary data in the
1.5 GB database: 1.5 GB
After the NIC is installed, the installation disk should still have at least 5% free space to store the
collected data; otherwise, the collection task cannot be created.
1.5.3 Networking Modes

9. Online Deployment
The NIC, OMStar, and SQL Server are installed on the same PC. The PC keeps
connected to NEs through the network during data collection.

Required space (30 BSCs): at least 10 GB free space for one inspection.
10. Offline Deployment
The NIC is installed on a PC that keeps connected to NEs through the network. After
data is collected, you can manually copy the data to the PC where the OMStar and the
SQL Server are installed for automatic import and analysis.
Required space (30 BSCs):

PC where the NIC is installed: at least 5 GB free space for one inspection.
PC where the OMStar and the SQL Server are installed: at least 7 to 8 GB free space for
one inspection.

1.6 Quick Guide to the Software

2 Installing the SQL Server
2.1 Installing the SQL Server 2000 Personal Edition
The directory for saving the source files of the installation package and the installation directory of
the SQL Server 2000 cannot contain any Chinese character.
If the SQL Server 2000 fails to be installed, handle it by referring to section 8.1.1How to Handle
the SQL Server Installation Failure?"
To install the SQL Server 2000 Personal Edition, do as follows:

Step 2 Click SQL Server 2000 Components.

Step 3 Click Install Database Server.
Step 4 Click Next.

Step 5 Select Local Computer, and then click Next.
Step 6 Select Create a new instance of SQL Server, or install Client Tools, and then click Next.

Step 7 Enter the user name and the company name, and then click Next.
Step 8 Click Yes.

Step 9 Select Server and Client Tools, and then click Next.
Step 10 Select Default, and then click Next.

If Default is unavailable, it indicates that a database instance has been installed on the PC. In
this case, enter a new instance name, for example, OMSTARSOP, in Instance name.

Step 11 Select Custom, and then click Next.

You can set the destination folders of program files and data files as required or use the
default destination folders. (The path cannot contain Chinese characters.)
Step 12 Click Next.

Step 13 Select Use the same account for each service. Auto start SQL Server Service and Use the
Local System account, and then click Next.
Step 14 Select Mixed Mode (Windows Authentication and SQL Server Authentication), set the
password of the sa user, and then click Next.

Step 15 Select Chinese_PRC in Collation designator and Accent sensitive in Sort order, and then
click Next.

Step 16 Select Named Pipes and TCP/IP Sockets with the default values unchanged, and then click
Next, as shown in the following figure.
Step 17 Click Next. The setup program starts copying the program files.
Step 18 Click Finish to complete the installation of the SQL Server 2000 Personal Edition.

2.2 Installing the SQL Server 2000 SP4

To install the SQL Server 2000 SP4, do as follows:
Step 19 Click Next.

Step 20 Click Yes.
Step 21 Click Next.

Step 22 Select The SQL Server system administrator login information (SQL Server
authentication), enter the password of the sa user (this password has been set in Step 13 in
section 2.1"Installing the SQL Server 2000 Personal Edition"; the user name and password are
sa by default), and then click Next.
Step 23 Select Upgrade Microsoft Search and apply SQL Server 2000 SP4 (required), and then
click Continue.

Step 24 Click OK.

Step 25 Click Next.

Step 26 Back up the databases, and then click OK.
Step 27 Click Finish to complete the installation of the SQL Server 2000 SP4.

3 Installing the NIC
3.1 Installing the NIC Tool

Obtain the installation package of the NIC and start installing the NIC.
Step 28 Select the setup language of the NIC, and then click OK.
Step 29 Click Next.

Step 30 Select I accept these terms.
Step 31 Click Next.

You can set the target directory as required or use the default directory. The second method is
recommended.

Step 32 Click Next.
Step 33 Click Next.

Step 34 Click Finish to complete the NIC installation.

4 Installing the OMStar
4.1 Installing the GENEX Shared Component
If the GENEX Shared component has been installed, you do not need to install it again.
The installation package contains only one version, namely, GENEX Shared 20060729 (applicable
to both Chinese and English versions).
Step 35 Start installing the GENEX Shared component.

Step 36 Click Next.
Step 37 Click Yes.
Step 38 Click Finish to complete the installation.

4.2 Installing the OMStar Tool

To install the OMStar, do as follows:
Step 39 Select the setup language, and then click OK.
Step 40 Click Next.

Step 41 Click Accept.

Step 42 Enter User Name and Company Name, and then click Next.
Step 43 Click Next.

You can set the installation directory as required or use the default directory.

Step 44 Click Next.

Step 45 Click Install.
Step 46 Click Finish to complete the installation of the OMStar.

4.3 Applying for and Installing a License
The OMStar and the Transdata use the same license file with the same ESN. You need to activate the
license file for the OMStar and the Transdata respectively.
If the PC uses multiple network adapters, the ESNs may change when the system cannot read the
ESNs of the hard disks. In this case, the number of ESNs is equal to that of network adapters. You
are advised to record and reserve all the ESNs and apply the license in one templet.
Step 47 After the OMStar is installed, start it.
Step 48 In the displayed dialog box, record the ESN, and then click Close to exit the OMStar
temporarily.

Step 49 Log in to the W3 license management center.

Web site: http://w3.huawei.com/dominoapp/isc/license/libvcg.nsf/fmDatabase?ReadForm
Step 50 Click Platform License Application, and then select Non-Commercial License.

Step 51 Enter the relevant information on the application information page, and then click Get
License Application Template.
Step 52 Select the application template of the OMStar V500R001, namely, MAINEX OMStar
V500R001 license application (yyyy-mm-dd+full name+employee ID) .xls.

Step 53 Save the MAINEX OMStar V500R001 license application (yyyy-mm-dd+full name+employee
ID) .xls file. The information marked red should be filled by the applicant.

Step 54 Open the file, enter the required information such as Applicant, YYYY-MM-DD (end date),
ESN, OMStar Network Performance AnalysisAdd, and OMStar Enhanced
Development PlatformAdd, and then save the file.
Step 55 Click Upload on the application information page, and then select the application form that
you set in Step 54.

Step 56 Click Submit on the application information page. In the displayed confirmation dialog box,
click OK to submit the application information.
Step 57 After the license file is complete, the license center automatically sends a notification mail to
the applicant.
Step 58 Log in to the W3 license management center, choose My Applications > Non-Commercial
License, and then select the application license.
Web site: http://w3.huawei.com/dominoapp/isc/license/libvcg.nsf/fmDatabase?ReadForm

Step 59 On the license approval page, click View Detail Approval Log, and then download the
license file (.dat) in Attachment to the local PC.
Step 60 Restart the OMStar V500R001, and then select Update License. The Open dialog box is
displayed.

Step 61 Select the requested license file, and then click Open. A prompt box is displayed.
Step 62 Click OK. The License Update successful.
Start the Transdata and activate the same license file as the OMStar. The update method is similar.

5 Using the NIC
5.1 Installing the Mediation Layer Matching the NE

Version
Step 63 Choose NIC Tools Suite > Mediation layer manager.
Be sure to install the mediation layer of each NE version through the Mediation Layer
Manager. Install the mediation layer by double-clicking it is prohibited.
Step 64 Click Install From file.

Step 65 Select the mediation layer file to be installed.

The language version of the mediation layer (the name contains "CHS" or "ENG")
must match the language version of the main program of the NIC.
Step 66 After the mediation layer is installed successfully, click Exit.

5.2 Setting the IP Address of the FTP Server

Step 67 Choose NIC Tools Suite > FTP Server Configuration.
Step 68 Select the proper IP address from the IP address drop-down list box.
That is, select the IP address of the PC where the NIC is installed (Ensure that the IP
address can be connected to NEs through the network.)

Step 69 Click Ok to close the FTP Server Configuration dialog box.
If the NIC has been started, restart the NIC (instead of restarting the Internet Explorer) to make the
configuration take effect after the FTP server configuration is complete.

5.3 Using the NIC to Collect Data
1. NE Management: used to create or delete an NE. Section 5.3.1"Creating an NE"

describes how to create an NE.
2. Scenario Management: used to customize a collection scenario when the SOP collection
scenario is unavailable (optional).
3. Task Management: used to create a collection task (for selecting the collection scenario,
the NEs from which data is collected, and the time range of collection).
5.3.1 Creating an NE
This section describes only how to create a BSC manually on the NIC. For details on how to import NEs
in batches, see section 8.2.6"How to Add NEs More Efficiently by Using the Batch Import Function?"
Step 70 Choose NIC Tools Suite > Network Information Collection.
Step 71 Choose NE Management > NE Information Maintenance.

Step 72 Select an NE from the drop-down list box.
Step 73 Configure the NE connection information.

You are advised to log in as the admin user.

Step 74 Click Apply to create an NE.

5.3.2 Customizing an SOP Collection Scenario
This operation is optional.

For the GSM8.1, the installed mediation layer
(iManagerM2000_BSC6000_MATCH_CHS_BSC6000V900R008C12) matching the NIC
V100R006C00T provides the SOP collection scenario by default. You do not need to customize the
scenario.
5.3.3 Creating a Collection Task

Step 75 Click the Task Management tab. Select Unfinished Tasks in Navigation Tree, and then
select Based on Scenario from the Create Task drop-down list box in Task List.

Step 76 Set Task Name, and then select a product from the Product Type drop-down list box and a
scenario from the Scenario(Group) drop-down list box.
Task Name: The name of the collection task for inspection or SOP can contain only letters
(az and AZ), numbers (09), and underline (_),the max number of the task name must less
then 27; otherwise, the subsequent automatic import and analysis of the OMStar may fail.
Scenario(Group): Select the SOP collection scenario, namely, BSC6000_SOP.
Task Execution Type: You are advised to select Instant. (If you select Scheduled, you need
to set Task Execution Time.)
Data Collection Time Range: You are advised to collect the data of three to seven days (if
the time range is too large, the collection and analysis efficiency is affected).
Step 77 Select Display by NE type. Select a BSC under the BSC6000 node in Optional NEs, and
then click > to move the selected BSC to Selected NEs. Then, click Next.

During routine inspection and maintenance SOP, you need to select only BSCs. If Display by
Topo structure is selected, when you select a BSC, the BTSs under the selected BSC are also
selected. As a result, the total number of NEs may exceed the upper limit.
Step 78 Click each NEs in the left list, ensure that the parameters of each NE are correct, and then
click Next.

Step 79 Set the additional information such as Name and Email, and then click Next.
Step 80 After ensuring that the collected information is correct, click Finish to start the collection
task.

5.3.4 Viewing the Collection Result
Do not disable the FTP Server of the tool during data collection; otherwise, the collection may fail.
Check whether configuration collection fails. The data analysis of the NE where configuration
collection fails may also fail.
Step 81 During collection, you can view the progress of the whole collection task and the progress and
running status of each NE.

Step 82 The data collection results are saved in installation directory of the NIC\NIC\var\nic\task
ID.
Task IDs are generated randomly, for example, 10002, 10003, 10004, ...
Check whether the task ID folder saves the collection task created by the user based on the
collection task name in the folder.
Step 83 Record the directory for saving the data collection results for the subsequent analysis of the
OMStar in one-key mode.
1. If the online deployment mode is used (that is, the NIC and the OMStar are installed on
the same PC), record only the directory for saving the collected data.
2. If the offline deployment mode is used (that is, the NIC and the OMStar are installed on
different PCs), copy the data in the task ID folder to the PC where the OMStar is
installed, and then record the directory for saving the collected data.
After the collected data is copied to another PC, the directory structure should meet the
following requirements.

6 Using the OMStar
This chapter describes how to implement the automatic data import and analysis and generate
a summary report on the Mini-OMStar in one-key mode. The descriptions about the manual
data import and analysis and other functions of the OMStar are not included in this chapter.
6.1 Introduction to the Mini-OMStar

Mini-OMStar is a plugin of the OMStar, which integrates with the function of data collection
supported by the NIC and the function of data import and analysis supported by the OMStar.
The Mini-OMStar helps in network evaluation and inspection and reduces the time for manual
operation. This document describes only the overview information about the Mini-OMStar.
For details, click Help in the menu bar to see the Help document.
The Mini-OMStar creates a database on disk D to perform a one-key analysis task. If no disk D is
available, handle it by referring to section 8.3.1 "Why Does the Mini-OMStar Fail to Create an
Automatic Analysis Task?"
The language of the Mini-OMStar is English only.

6.2 Starting the Mini-OMStar

Step 84 Choose Microsoft SQL Server > Service Manager.
Step 85 Check that the default SQL Server instance is started properly.

Step 86 Start the Mini-OMStar.
Step 87 Enter the information for login.

SQL Server: indicates the database server used by the OMStar. You can type the information
by referring to the following description:
If the server name is typed in Server in Step 2, you just need to type period (.).
If Server name\instance name is typed in Server in Step 2, you just need to type
".\instance name."
Net type: Select UMTS for BSC6810 and MBSC_UO for BSC6900.

6.3 Creating a One-key Analysis Task

Step 88 Click to create a one-key analysis task.
Step 89 Set the NIC collection information, bind an NIC collection task, and then click Next.

Data Source Path: indicates the root directory for saving data collected by the NIC. After the
NIC is installed, this root directory can be identified automatically. If the NIC is not installed
on the PC, you need to manually specify it. For details, see Step 3 in section Error: Reference
source not found"Error: Reference source not found."
Task Type: indicates the task execution type. Currently, Task Type for the NIC can only be
set to Immediately.
Immediately: indicates that the task is executed immediately. This type of tasks
corresponds to immediate collection tasks or scheduled collection tasks on the NIC.
Period: indicates that the task is executed periodically. This type of tasks corresponds to
periodic tasks on the NIC.
Step 90 Set common parameters for analysis on the OMStar, and then click Next.

Step 91 Select the NE version, set check items and related thresholds, and then click Finish.
Step 92 Right-click a task on the main interface, and then choose Run from the shortcut menu to start
the task. Alternatively, click to start the task.

Step 93 View the task running status and execution process.

Task state: indicates the state of a task. A task can be in one of the following states:
Ready: indicates that the task is ready. You can run, edit, or delete the task.
Running: indicates that the task is running. You can stop this task but cannot edit or
delete it. Note that you can start multiple tasks at the same time but only one task can be
in the running state at a time.
Stopping: indicates that the task is being stopped. You cannot run, edit, or delete the
task.

If the online deployment is used (the NIC and the OMStar are installed on a PC): After the
task on the NIC is started, you can start a one-key analysis task even if the data collection is
not complete. The Mini-OMStar periodically detects the data integrity and implements the
automatic analysis after the data collection is complete.
If the offline deployment is used (the NIC and the OMStar are installed on different PCs):
After the collection task is executed completely, the data corresponding to the task ID can be
copied to the PC where the OMStar is installed. For details, see Step 3 in section Error:
Reference source not found"Error: Reference source not found."
The Mini-OMStar starts the Transdata automatically, but you need to close the Transdata before the
task is executed.
You can close the Transdata that is started by the Mini-OMStar only if the task is executed
completely.
Step 94 View NE reports generated by the one-key analysis task.

To view a report, do as follows: Select a task in the task list, and then choose Report > View
Report or click the hyperlink in the Report column.

Task name: indicates the name of the executed task that corresponds to reports in the report
list.
Report path: indicates the path for saving reports in the report list.
Open: enables you to navigate to the path for saving reports.
Open report file: enables you to open a report file.
Open report path: enables you to navigate to the path for saving reports.
The report is named in the following format: NE name + Generation time stamp of the report.

6.4 Summarizing Reports

The GSM summarization tool is used to summarize the single-BSC reports generated by the
OMStar.
6.4.1 Main UI
The following figure shows the main UI of the summarization tool.
6.4.2 Function Buttons

Clear
Click the Clear button to clear all summary data.
Summary Analysis
Click the Summary Analysis button and select the reports of all the BSCs. Then, the tool
summarizes the data of the BSCs.

You can import the reports of more BSCs. That is, after a batch of BSC reports are imported and
summarized, click Summary Analysis again to import the reports of other BSCs.
1. Summarization procedure
2. Summarization results (Click the link of the number of problems of each check item
under each NE to view the summary analysis data.)
3. Contents of summarization table
Help
Click the Help button to view the help information about the tool.


7 Help Information
Contact person: Wu Zhibiao

Notes ID: 107306
Email: wuzhibiao @huawei.com
Your valuable advice is most welcome.
In case of any problem related to the tool usage, please collect relevant log information and
send it to R&D engineers for handling.
Directories for saving logs of the NIC:
Main logs for troubleshooting:
Installation directory of the NIC\etc\NICServer\omstarnicscript\omstar_Log
Auxiliary logs for troubleshooting:
Installation directory of the NIC\var\logs
Installation directory of the NIC\data\pg_log
Installation directory of the NIC\bin\pgbouncer.log
Installation directory of the NIC\bin\pgbouncer.pid
Installation directory of the NIC\bin\postgres_install.log
Log directories of the OMStar V500R001:
Installation directory\OMStar V500R001\OMStar V500R001\UNP\Log
Installation directory\OMStar V500R001\Transdata V500R001\Runtime
Tips: Compress the log data if the data amount is large.

8 FAQs
8.1 FAQs Related to the SQL Server

8.1.1 How to Handle the SQL Server Installation Failure?
The cause of most installation failures is that the previously installed SQL Server is
uninstalled incompletely. The following describes some common installation errors. The
handling methods can also be used to uninstall the SQL Server 2000 completely.
1. Files are pending.
This error usually occurs when the SQL Server is uninstalled and then reinstalled.
Solution:
Delete the key value "PendingFileRenameOperation" in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager of
the registry.
2. The installation program fails to configure the server.
Solution:
Cause 1: The previously installed SQL Server 2000 is uninstalled incompletely.
Delete the Microsoft SQL Server folder in C:\Program Files.
Find "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server"
in the registry and delete it.
Cause 2: The name of the computer running Windows contains lower-case letters.
The SQL Server 2000 fails to be installed when the name of the computer running
Windows contains some or only lower-case letters, with the prompt of general network
error in the sqlstp.log file.
To solve this problem, change the lower-case letters to upper-case letters. For example,
to change the computer name from jys0800964 to JYS0800964, do as follows:
Open the registry (by running the regedit command in the Run window), find
"HKEY_LOCAL_MACHINE\System\CurrenControlSet\Control\ComputerName\Comp
uterName", and then change the primary key value of 'ComputerName' from jys0800964
to JYS0800964. Then, log out the user or restart the system to make the modification
take effect.
3. The system prompts "command line option syntax error".

The cause of this error is that the name of the directory for saving the source files of the
SQL Server installation package contains Chinese characters. In this case, the SQL
Server can be installed successfully after you click OK, but the OMStar fails to connect
to the database.
Solution:
Ensure that the name of the directory for saving source files of the SQL Server does not
contain any Chinese character.
4. The UI is suspended during installation.
Solution:
The SQL Server 2000 Personal Edition should be installed for Windows XP. Check
whether the SQL Server Standard Edition or Enterprise Edition is installed on Windows
XP (the two editions can be installed only on Windows Server 2000 or Windows Server
2003).
5. The SQL Server fails to be started after the domain password is changed.
Go to Control Panel > Management Tools > Services. In the displayed window, right-
click MSSQLSERVER and select Properties from the shortcut menu. Then, click the
Login tab and change the password to the password of the current domain user.
8.1.2 Can the MSDE 2000 Be Used?

6. The MSDE 2000 is equivalent to a lite edition of SQL Server 2000 with the limited
specification (the performance decreases abruptly when the size of a single table exceeds
2 GB). The MSDE 2000 is not recommended especially when the performance
measurement data collected from a single BSC exceeds 150 MB.
7. If the conditions for installing the SQL Sever 2000 are not met but users can take the low
efficiency risks caused by the MSDE, install the MSDE encapsulated by Genex. The
MSDE can be downloaded from the Web site http://support.huawei.com.
http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do?
actionFlag=getDetail&node=000001423430&colID=ROOTENWEB|CO0000000174
8. The MSDEs of other products may be inapplicable to normal analysis of the OMStar.
8.1.3 Can the SQL Server 2005 Be Used?

The SQL Server 2005 can be installed on Windows Server with standard configuration. It is
not recommended to install the SQL Server 2005 on Windows XP with common
configuration.
8.2 FAQs Related to the NIC

8.2.1 How to Handle the NIC Start Failure?
9. Ensure that the FTP Server is disabled and the default FTP port is not used before
starting the NIC.
The FTP Server ports conflict between the LMT and the NIC. Therefore, disable the FTP
Server before starting the NIC.
10. At present, the ports conflict between the M2000 client and the NIC. Therefore, disable
the M2000 client before starting the NIC.
11. For other causes, send the log information to development engineers for troubleshooting.

8.2.2 How to Handle the Failure of Adding NEs to the NIC?

12. Check whether the user name and password are correct (that is, check whether the login
by using the LMT succeeds).
13. Check whether the IP address in FTP Server Configuration is consistent with the IP
address of the PC.
If the IP addresses are inconsistent, modify them and restart the NIC to make the
modification take effect. (Caution: Restart the NIC program instead of the Internet
Explorer.)
14. Check Mediation layer manager to ensure that mediation layer matching the NEs to
collect data from has been installed.
15. For other causes, send the log information to development engineers for troubleshooting.
8.2.3 The System Prompts "Adaptation layer does not match the C
version of the NE." When the User Adds an NE
16. This error is a kind of NE adding failures. Check whether the mediation layer matching
the NE version is installed.
17. If the mediation layer matching the NE version is installed, the possible cause is that the
NIC of Chinese version has been manually installed with the mediation layer of English
version.
8.2.4 Data Collection Failure Scenarios (Configuration,

Performance Measurement, MML, )
18. If the NIC fails to connect to NEs, check whether the FTP Server of the NIC is disabled.
Do not disable the FTP Server during startup or running of the NIC.
19. Check whether the IP address in FTP Server Configuration is consistent with the IP
address of the PC.
If the IP addresses are inconsistent, modify them and restart the NIC to make the
modification take effect. (Caution: Restart the NIC program instead of the Internet
Explorer.)
20. Check whether the user has the operation right.
It is recommended to collect data as the admin user; otherwise, the collection may fail
due to lack of rights to certain collection items.
Check whether the user has the right to operate MML commands. If not, collecting
configuration files and MML commands may fail.
Check whether the user has the right to back up configuration files. If not, collecting
configuration files may fail.
Check whether the user has the right to run the BIN command. If not, collecting
performance measurement data may fail.
8.2.5 Why Does It Take Time for the NIC to Collect Inspection
Data?
21. Check whether the BSC6000 mediation layer of the NIC V100R006C00T downloaded
from http://support.huawei.com.

22. Check whether the default SOP scenario of the NIC is used for collection (it is
unnecessary to collect the massive data such as logs for inspection or SOP).
23. At present, the NIC reports the progress according to collection items. The execution
sequence of the collection items may change each time when a task is created. If the
amount of the data collected by the first collection item is large, the required time is
longer and displayed as X%.
24. The execution sequence of collection items may change each time when a task is created.
When the items with a small amount of data are collected in priority, it seems that the
collection becomes faster.
25. If the collection progress does not change for a long time, send the log information to
R&D engineers to check whether the NIC is still collecting data.
8.2.6 How to Add NEs More Efficiently by Using the Batch Import
Function?
26. Choose NE Management > NE Information Maintenance, and then click Batch
Manage.
27. On the Batch Manage page, click Download Template to save the template to the local
PC.

28. Open the batch import template (*.xls) downloaded to the local PC and generate an XML
file according to the description.
The generated XML file is saved in the NEList folder in the same-level directory as the XLS template.
29. On the Batch Manage page, click Browse, select the XML file, and then click Import.
30. After the XML file is imported, click OK.

8.2.7 The System Prompts "Please check whether the NIC

application services and the database services run normally."
During Batch Management of NEs
It is a bug of the NIC V100R005C00SPC200. This error occurs when the imported XML file
contains Chinese characters because the default XML code is UTF-8. You can use one of the
following methods to solve this problem:
31. Modify the NE name to contain only English characters.
32. Modify the XML code to GB2312.
If you have any question, contact development engineers.
8.3 FAQs Related to the OMStar and the Transdata

8.3.1 The System Prompts the Incorrect Program Configuration at
Startup of the Transdata
The possible cause is that the OS of an earlier version is installed on the PC.
Solution:
Install the vcredist_x86.exe patch.
vcredist_x86.exe

8.3.2 The System Prompts Project Information Loading Failure

and Invalid Parameters at Startup of the Transdata
This error occurs when the Nastar CS Transdata or the CDMA Transdata was deployed on the
PC but the project library was directly deleted from the PC.
This prompt does not affect other project operations. You can directly click OK and then
proceed according to the normal procedure.
8.3.3 How to Handle the Automatic Import and Analysis Failure

of the Transdata?
33. Check whether the current PC has disk D.
By default, databases are automatically created on disk D for automatic import and
analysis of the OMStar in one-key mode. If the PC does not have disk D, automatic data
import may fail.
Solution:
Open the config.ini file in the following path:
Installation directoryOMStar V500R001\Mini_OMStar\config.ini
Find the DBPATH field, and then rplace the D as an available drive letter (with the
free space of at least 2 GB) of the local PC next to the = symbol.

34. Check whether the name of the NIC collection task complies with specifications.
During the automatic import and analysis of the OMStar in one-key mode, the name of
the project database has character restrictions, which must be noted when users create
collection tasks on the NIC. For details, see Step 76 in section 5.3.3"Creating a
Collection Task."
Task Name: The name of the collection task for inspection or SOP can contain only
letters (az and AZ), numbers (09), and underline (_).
Solution:
Use the suggested characters to name the collection tasks created by using the NIC.
If the collection with the invalid NIC task name is complete, use the following
method to avoid re-collection:

Find the directory for saving the collected data package (see section 5.3.4"Viewing the
Collection Result"), and then modify the task name correctly.
35. Check whether the installation of the SQL Server meets requirements.
If the MSDE 2000 needs to be installed, be sure to use the MSDE is encapsulated by
Genex. See section 8.1.2"Can the MSDE 2000 Be Used?"
If the SQL Server 2000 is installed, ensure that the collation rules meet the
requirements of the OMStar (see Step 15 in section 2.1"Installing the SQL Server
2000 Personal Edition").
If the SQL Server 2000 has been installed, verify the installation as follows:
Choose Microsoft SQL Server > Enterprise Manager.
Check the properties of the local services and ensure that the collation rule is
SQL_Latin1_Gerenal_CP1_CI_AS.

8.3.4 Is the OMStar Compatible with Office 2007?

The OMStar V005R001C00SPC120 and earlier versions do not support Office 2007. The
OMStar V005R001C00SPC200 and later versions can support Office 2007.
8.3.5 Does the OMStar Support Windows 7?

The compatibility test is in progress. The OMStar V005R001C00SPC200 does not support
Windows 7 temporarily.

Operation Guide To The OMStar

Uploaded by

Copyright:

Available Formats

Operation Guide To The OMStar

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operation Guide To The OMStar

Uploaded by

Copyright:

Available Formats

Product Name Confidentiality

OMStar V500R001C00SPC200 Maintenance

Prepared by Wu Zhibiao Date 2010-08-30

Huawei Technologies Co., Ltd.

2010-8-30 V1.0 Draft completed. Wu Zhibiao and Wu

2017-6-21 Huawei Confidential Page 2 of 79

2 Installing the SQL Server..........................................................................................................10

3 Installing the NIC........................................................................................................................25

4 Installing the OMStar.................................................................................................................28

5 Using the NIC...............................................................................................................................43

6 Using the OMStar........................................................................................................................56

2017-6-21 Huawei Confidential Page 3 of 79

6.3 Creating a One-key Analysis Task...................................................................................................................59

2017-6-21 Huawei Confidential Page 4 of 79

OMStar V500R001C00SPC200 Maintenance SOP Guide

SOP Standard Operation Procedure

2017-6-21 Huawei Confidential Page 5 of 79

1.1 Intended Audience

1.2 Application Scope

1.3 Important Hints

2017-6-21 Huawei Confidential Page 6 of 79

1.4 Software Acquisition Modes

GBSS8.1 NIC NIC_install Main program of the V100R006 http://support.huawei.com

OMSt OMStar Main program of the V500R001 http://support.huawei.com

2017-6-21 Huawei Confidential Page 7 of 79

1.5 Installation Requirements

Model: common PC OS: Windows XP SP3 or more advanced

1.5.2 Hard Disk Specification

NIC 330 MB Collected data package: 150 Collected data package: 4 GB

1.5.3 Networking Modes

2017-6-21 Huawei Confidential Page 8 of 79

Required space (30 BSCs):

2017-6-21 Huawei Confidential Page 9 of 79

1.6 Quick Guide to the Software

2017-6-21 Huawei Confidential Page 10 of 79

2 Installing the SQL Server

2.1 Installing the SQL Server 2000 Personal Edition

To install the SQL Server 2000 Personal Edition, do as follows:

2017-6-21 Huawei Confidential Page 11 of 79

Step 3 Click Install Database Server.

Step 4 Click Next.

2017-6-21 Huawei Confidential Page 12 of 79

Step 5 Select Local Computer, and then click Next.

2017-6-21 Huawei Confidential Page 13 of 79

Step 8 Click Yes.

2017-6-21 Huawei Confidential Page 14 of 79

Step 10 Select Default, and then click Next.

2017-6-21 Huawei Confidential Page 15 of 79

Step 11 Select Custom, and then click Next.

Step 12 Click Next.

2017-6-21 Huawei Confidential Page 16 of 79

2017-6-21 Huawei Confidential Page 17 of 79

2017-6-21 Huawei Confidential Page 18 of 79

2017-6-21 Huawei Confidential Page 19 of 79

2.2 Installing the SQL Server 2000 SP4

2017-6-21 Huawei Confidential Page 20 of 79

Step 20 Click Yes.

Step 21 Click Next.

2017-6-21 Huawei Confidential Page 21 of 79