operation guide to the omstar v500r008 for maintenance sop

Operation Guide to the OMStar V500R008 for Maintenance SOP

Issue 01

Date 2013-04-08

HUAWEI TECHNOLOGIES CO., LTD.

Issue 01 (2013-04-08) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Operation Guide to the OMStar V500R008 for

Maintenance SOP About This Document



ii

About This Document

Author

Prepared By Chen Ping (Employee ID: 00151537) Date 2013-02-17

Reviewed By Liu Junwei (Employee ID: 00148069);

Qi Peizhi (Employee ID: 00143926)

Date 2013-04-07

Approved By Wang Yan (Employee ID: 45750) Date 2013-04-08

Change History

Date Version Description Author

2013-02-17 1.00 Updated and modified the document based on

the latest patch version.

Chen Ping

Keywords Maintenance SOP, OMStar, NIC

Abstract This document provides guidance for quick installation and operation 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 assistance

according to the help information.

List of acronyms and abbreviations:

Acronym or Abbreviation Full Name

SOP Standard Operation Procedure


Maintenance SOP About This Document



iii

NIC Network Information Collection

OMStar Operation&Maintenance Star

OMStar


Maintenance SOP Contents



iv

Contents

About This Document ............................................................................................................... ii

1 Overview ................................................................................................................................... 1

1.1 Intended Audience ..................................................................................................................................... 1

1.2 Application Scope ...................................................................................................................................... 1

1.3 Precautions ................................................................................................................................................ 2

1.3.1 Precautions for Installing and Operating NIC .................................................................................... 2

1.3.2 Other Precautions ............................................................................................................................. 2

1.4 Software Acquisition Means ...................................................................................................................... 2

1.5 Installation Requirements .......................................................................................................................... 3

1.5.1 Installation Environment Specifications ............................................................................................ 3

1.5.2 Hard Disk Specifications................................................................................................................... 4

1.5.3 Usage Ports ...................................................................................................................................... 4

1.5.4 Networking Modes ........................................................................................................................... 6

1.6 Data Sources Required for Analysis ........................................................................................................... 7

1.7 Experiences Sharing .................................................................................................................................. 9

2 Data Collection by using the NIC ........................................................................................ 11

2.1 Using NIC in Co-Deployment Mode ......................................................................................................... 11

2.1.1 Procedure for Logging In to the NIC in Co-Deployment Mode ......................................................... 11

2.1.2 Using NIC in Co-Deployment Mode to collection data .....................................................................14

2.2 Using NIC Stand-Alone Version................................................................................................................14

2.2.1 Installing the NIC Tool.....................................................................................................................14

2.2.2 Using NIC Stand-Alone Version .......................................................................................................15

2.2.3 Installing the Mediation Matching the NE Version ............................................................................15

2.2.4 Using the NIC to Collect Data ..........................................................................................................17

2.3 Collecting GSM Data ...............................................................................................................................21

2.4 Collecting UMTS Data .............................................................................................................................25

2.5 Collecting GSM and UMTS Data..............................................................................................................29

2.6 Collecting LTE Data .................................................................................................................................33

2.6.1 Editing NIC Scenario .......................................................................................................................33

2.6.2 Creating a collection task based on the Scenario ...............................................................................34

2.6.3 Collecting Data Based on the Scenarios of the NIC ..........................................................................38

2.7 Collecting data for RNC and NodeB PMI ..................................................................................................42

OMStar


Maintenance SOP Contents



v

2.7.1 Collecting RNC and NodeB Data in One Task ..................................................................................42

2.7.2 Collecting the RNC and NodeB Data Separately and Creating a Data Package ..................................44

2.8 Viewing the Collection Result ...................................................................................................................46

3 Data Analyze by using OMStar ........................................................................................... 49

3.1 Installing the OMStar Tool ........................................................................................................................49

3.2 Obtaining Authorization and Applying License .........................................................................................54

3.2.1 Background Information ..................................................................................................................54

3.2.2 Authentication Management .............................................................................................................54

Method1Domain Authentication ...........................................................................................................54

Method2Update the License .................................................................................................................55

Applying License Manually ......................................................................................................................56

Prerequisites .............................................................................................................................................56

Procedures for Applying for the License. ..................................................................................................56

Query License Infomation ........................................................................................................................58

3.3 Introduction to the OMStar V500R008 ......................................................................................................59

3.3.1 GSM Network Inspection.................................................................................................................59

3.3.2 UMTS Network Inspection ..............................................................................................................70

3.3.3 LTE Network Inspection ..................................................................................................................81

3.3.4 GUL Network Inspection .................................................................................................................92

3.4 Handling Problems Based on the Summary Report .................................................................................. 105

3.5 Updating a Project Package from Rule Store ........................................................................................... 109

4 Problem Handling ................................................................................................................ 111

4.1 Principles ............................................................................................................................................... 111

4.2 Creating an iCare Service Request .......................................................................................................... 111

4.3 iCare Help .............................................................................................................................................. 111

5 FAQ ........................................................................................................................................ 112

5.1 FAQs Related to the NIC ........................................................................................................................ 112

5.1.1 How Do I Handle the NIC Startup Failure? .................................................................................... 112

5.1.2 How Do I Handle the Failure to Add NEs to the NIC? .................................................................... 112

5.1.3 The System Displays the Message "Adaptation layer does not match the C version of the NE." When

the User Adds an NE .............................................................................................................................. 112

5.1.4 Data Collection Failure Scenarios (Configuration Data, Traffic Statistics Data, and MML Data) ..... 113

5.1.5 Why Does It Take Time for the NIC to Collect Inspection Data? ..................................................... 113

5.1.6 How to Add NEs More Efficiently by Using the Batch Import Function? ........................................ 113

5.1.7 What is the Maximum Number of NEs Whose Data Is Collected Concurrently on the NIC? ............ 116

5.1.8 How Do I Handle the Partial Data Collection Failure? .................................................................... 116

5.1.9 How Do I Handle the Failure to Create NEs with M2000 Agent Mode and Multiple IP Addresses? . 116

5.1.10 How Do I Obtain Co-site Information Manually on the M2000 When the NIC Cannot Collect the

Information Automatically? .................................................................................................................... 117

6 Help Information ................................................................................................................. 119

OMStar


Maintenance SOP 1 Overview



1

1 Overview 1.1 Intended Audience

This document is intended to guide readers to deploy MAINEX operation and maintenance

(O&M) 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 OMStar V500R008 to support the maintenance SOP

as follows:

GSM BSC6900V900R012C01

BSC6900V900R013C00

BSC6900V900R013C01

BSC6900V900R014C00

UMTS BSC6900V900R012C01

BSC6900V900R013C00

BSC6900V900R013C01

BSC6900V900R014C00

LTE-FDD V100R003C00

V100R004C00

V100R005C00

V100R005C01

OMStar





2

LTE-TDD V100R004C00

V100R005C00

V100R005C01

GU BSC6900V900R012C01

BSC6900V900R013C00

BSC6900V900R013C01

BSC6900V900R014C00

NOTE For details about the mapping between the OMStar and the corresponding NEs, see the OMStar V500R008C00 Release Notes. This document takes RAN13 as an example to describe the installation and operation of the OMStar. In case of other versions, the installation and operation of the OMStar are similar.

1.3 Precautions

1.3.1 Precautions for Installing and Operating NIC

The NIC installation path must be an absolute path. It is a combination of English letters,

numbers, underlines, and hyphens. It does not support Chinese characters, garbled

characters, and spaces. The NIC cannot be installed by overlapping the installation path of the previously installed version.

The main program language edition and mediation language edition for the NIC installation must be consistent with the NE language edition.

Disable hard disk shutdown, standby mode, and sleep mode of the PC for NIC

collection.

1.3.2 Other Precautions

This document describes how to obtain, install, and use the NIC of English version.

Sufficient space should be available for installing the NIC and the OMStar. For details,

see section 1.5.2 "Hard Disk Specifications."

The special notes on the tool installation and usage are marked red.

1.4 Software Acquisition Means For details about how to obtain SOP documents and related tools, see the Overview of Supporting Documents&Tools for Wireless Maintenance SOP. You can obtain this document at

http://support.huawei.com/support/pages/news/NewsInfoAction.do?doc_id=IN0000036873&

colID=ROOTENWEB|CO0000002672&actionFlag=view.

OMStar





3

1.5 Installation Requirements

1.5.1 Installation Environment Specifications

Hardware Requirement Software Requirement

Model: common PC

CPU: P4 3.1 GHz or higher

Memory: 4 GB or higher

Hard Disk: 160 GB or higher

Accessories: Network adapter/17-inch LCD display

OS: Windows 7 (32 bit)operating

system

Browser: Internet Explorer 7.0 or later

Others: Office 2007 or Office 2010

OMStar





4

1.5.2 Hard Disk Specifications

Data Specification

Software Required Space

Required Space for Collection and Analysis (Single BSC)

Required Space for Collection and Analysis (30 BSCs)

GSM/UMTS:

Single BSC

(300 base stations 1200 cells)

Seven-day traffic

data and

granularity 60

minutes.

LTE:

250 eNodeBs

Seven-day traffic

data and

granularity 60

minutes.

NIC 480 MB Disk for NIC installation

directory: 170 MB/BSC

Collected data package: 5

GB

OMStar 1.36G Disk for collected data

package: 180 MB/BSC

Disk for OMStar

installation directory: 2.5 GB

Disk for OMStar project storage: 10 GB

Disk for collected data

package: 5.5 GB

Disk for OMStar

installation directory: 2.5

GB (same as that in the

Required Space for

Collection and Analysis (Single BSC) column.)

Disk for OMStar

installation directory: 2.5

GB (same as that in the

Required Space for

Collection and Analysis (Single BSC) column.)

PostgreSQL 2G Database installation

directory: 2GB

Database installation

directory: 2 GB (same as

that in the Required Space

for Collection and

Analysis (Single BSC) column.)

1.5.3 Usage Ports

NIC Ports

Ports Source Device Target Device Description

31035 NIC server M2000 server This port is provided by the M2000

server and used for the NIC to collect data.

6000 NIC server NE This port is provided by a specific NE

and used for the NIC to collect MML

data.

21 NIC server NE This port is provided by a GSM/UMTS

NE and used for the NIC to collect data in FTP transmission mode.

31038 Web browser NIC server This port is used to connect to the NIC

server through HTTP.

OMStar





5

Ports Source Device Target Device Description

30700

31000

31007

31009

31015

31030

31032

31037

31038

6432

5432

NIC server NIC server These ports are NIC internal ports.

OMStar Ports

Port Source Device

Target Device Description

5432 TCP/IP PG database Used by default during the PG

database installation.

30010 TCP/IP OMStar and eSAU Used by default in the

communication between the OMStar and the eSAU.



23457 TCP/IP eSAU and SAU Used by default during file transfer.

40005 TCP/IP SAU location module ssUsed by default in the SAU

location frame process.

62946 TCP/IP Rule update The default port used when

OMStar and RuleStore communicating to update rules.

9003 TCP/IP Rule update The standby port used when

OMStar and RuleStore communicating to update rules.

62956 TCP/IP Authentication The default port used when

OMStar and RuleStore communicating to authenticate.

9013 TCP/IP Authentication The standby port used when

OMStar and RuleStore communicating to authenticate.

5013 TCP/IP ESAU CHR data Used by default when obtaining

OMStar





6

CHR data.

12345 TCP/IP OSGI Frame Used during OSGI monitor

service.



8081 TCP/IP OMStar Used by default in the

WebService.

NOTE The preceding specifications are only for your reference. The actual specifications may vary with

networks and data. You must reserve sufficient disk space.

After the NIC is installed, the disk where the installation directory is located must have a minimum of 5% free space for saving collected data. Otherwise, the NIC displays error information.

1.5.4 Networking Modes

Offline Deployment

The OMStar V500R008 is used for offline analysis of wireless network data obtained using

the NIC collection tool. The collected data must be manually copied to the PC running the

OMStar V500R008 because the OMStar V500R008 does not communicate with the NIC

collection tool. Figure 1 shows the networking of the OMStar V500R008.

OMStar





7

1.6 Data Sources Required for Analysis The required data for maintenance SOP analysis and the collection methods are as follows.

The collection methods for different NEs may not be the same. The following description is

only for reference.

Mode Data Source NIC Collection Method Description

GSM/

UMTS

BSC data

configuration file

MML command and FTP upload

Run the BKP CFGFILE command

to back up files. The parameter is the customized file name.

Run the ULD CFGFILE command to upload files.

The BSC data

configuration file is

a mandatory item

and provides basis

for network object

analysis on the

OMStar. If this file

is not available,

automatic analysis fails.

BSC traffic

statistics file

BIN command and FTP upload

Obtain the file name list such as

mbsc/bam/common/MeasResult/

A20110330.2000+0800-2030+0800_EMS-NORMAL.mrf.bz2. Then,

upload the list by using FTP.

The BSC traffic

statistics file is an

optional item and

can be used for

checking the device

and system loads

and analyzing

resource usage and

network

performance.

BSC alarm file MML command and FTP upload

Run the COL LOG:

LOGTYPE=HISTORY_ALARM-1; command to create an alarm log

file such as

mbsc/bam/version_a/ftp/COLLO

GINFO/ALM-LOG/ALARM_INF

O.zip. Then, upload this log file

through by using FTP.

The BSC alarm file

is an optional item

and is used for alarm analysis.

BSC operation

logs

MML command and FTP upload

Run the COL LOG: LOGTYPE=

OPT_LOG-1; command to create

an operate log file such as

mbsc/bam/version_a/ftp/COLLO

GINFO/OPT-LOG/OperateLog.zip. Then, upload this log file through by using FTP.

The BSC operation

logs is an optional

item and is used for log analysis.

BSC active alarm

file

Run the LST ALMAF command to

save the returned information.

The BSC active

alarm file is an

optional item and is

used for alarm analysis.

OMStar





8


BSC MML data

file

Run the following commands to

save the returned information: DSP

ACIC, DSP LICUSAGE, LST BC,

LST VER, LST LICENSE, LST

SOFTWARE, and DSP BTSBRD.

The BSC MML data

file is an optional

item and is used for

checking device

status and analyzing configuration.

NodeB data

configuration file

FTP upload:


The NodeB data


a mandatory item

and provides basis

for network object

analysis on the


is not available,


NodeB alarm file M2000+FTP upload:

Obtain the alarm file name list such

as

20120116170448-alarm-log-auto-1.csv

20120116170448-event-log-auto-1.csv

The NodeB alarm

file is an optional

item and is used for alarm analysis.

NodeB traffic

statistics file



M2000 R11/export/home/sysm/ftproot/pm/

M2000 R12/export/home/sysm/ftproot/nbi/ A20110330.2000+0800-2030+0800

_EMS-NORMAL.mrf.gz. Then,

upload the list by using FTP.

TheNodeB traffic


optional item and

can be used for

checking the device

and system loads

and analyzing

resource usage and

network performance.

Co-site

information table

FTP upload:

The M2000 automatically generates

the co-site information table and

saves it in EAMInfo.xml. The NIC

obtains it from the M2000 server upon data collection.

The co-site

information table is

an optional item and

is used for checking

the configuration of an MBTS.

OMStar





9


LTE eNodeB data

configuration file

MML command and FTP upload:

Run the BKP CFGFILE command

to back up files. The parameter is the customized file name.


The eNodeB data


a mandatory item

and provides basis

for network object

analysis on the


is not available,


eNodeB traffic

statistics file



M2000 R11/export/home/sysm/ftproot/pm/

M2000 R12/export/home/sysm/ftproot/nbi/ A20110330.2000+0800-2030+0800

_EMS-NORMAL.mrf.gz. Then, upload the list by using FTP.

The eNodeB traffic


optional item and

can be used for

checking the device

and system loads

and analyzing

resource usage and

network

performance.

eNodeB alarm

file

M2000+FTP upload:

Obtain the alarm file name list such

as

20120116170448-alarm-log-auto-1.csv

20120116170448-event-log-auto-1.c

sv

The eNodeB alarm

file is an optional

item and is used for alarm analysis.

eNodeB MML

data file

MML command:

Run the following commands to

save the returned information: DSP

BRD; DSP LICENSE; DSP CELL;

LST VER; DSP ETHPORT and

DSP BRDVER.

The eNodeB MML

data file is an


used for checking

device status and

analyzing configuration.

eNodeB CHR file BIN command and FTP upload


20120302_145654+0800_0115.CH

R, 20120305_103500+0800_0000.SIG.

The eNodeB CHR

data file is an


used for CHR analysis.

1.7 Experiences Sharing Suggestion 1: Set NIC task, one task for collecting five controllers' data for GSM and UMTS,

set two tasks for one batch, collect a maximum of1000 NEs' data for LTE in one task.

OMStar





10

Suggestion 2: Set NIC task, collect data of seven days, and collect data by busy hours.

Suggestion 3: Use OMStar to analyze data at night.

OMStar


Maintenance SOP 2 Data Collection by using the NIC



11

2 Data Collection by using the NIC There are two kinds of NIC tool, Stand-alone Mode and Co-Deployment Mode.

We still recommend using NIC in Co-Deployment Mode.

1. For the NIC stand-alone version, please refer to section2.1 "Using NIC in Co-Deployment Mode."

2. For the NIC in Co-Deployment Mode, please refer to section 2.2 "Using NIC Stand-Alone Version."

NOTE All data collected from customers' offices for analysis by the OMStar can be taken out of the

customers' offices only after consent is given by the customers.

Obtain the CHR and PCHR data for analysis with written consent of the customer.

Do not transmit raw network data outside EEA area and to China.

Delete data after using it. Do not keep any permanent file that contains plaintext private data, such as raw files, reports, and database.

The plaintext private data, such as IMSI, ESN, and IMEI, should be masked in the report provided for the customer. This type of data should be expressed in such methods as anonymization, division, and code.

2.1 Using NIC in Co-Deployment Mode The following steps show how to use the NIC in co-deployment mode. For details, see related

sections.

1. Start the NIC in co-deployment mode.

2. Collect data.

2.1.1 Procedure for Logging In to the NIC in Co-Deployment Mode

Step 1 Start the Microsoft Internet Explorer (IE). Type http://Server IP address/nic and press Enter. In SSL mode, you need to type https://server IP address: 31040/nic in the address bar

of the IE.

The server IP address refers to the IP address of the M2000.

OMStar





12

In the Security Alert dialog box, click Yes. In the Security Information dialog box, click

Yes.

NOTE

If M2000 established SSL to register safely,then need to set certificate in the IE. The method is as follows:

a. open the IE tool >Internet option > content -> certificate -> import the right certificate

b. You can get the certificate files from the M2000 install path:

\client\client\style\defaultstyle\conf\ssl\keyStore\PFX\client.p12

\client\client\style\defaultstyle\conf\ssl\trust\PEM\trust.cer

P.S Consultation the manager of M2000 to get the password of client.p12,please.

Step 2 In the NIC login window, type the user name, password, and verification code.

OMStar





13

NOTE If the verification code is illegible, you can click Reset to refresh the verification code. After that, you need to type the password again.

Step 3 Click Login. If the login fails, check whether the NIC service has been started by referring to How Do I Handle the NIC Startup Failure?

----End

I. Overview of NIC in Co-Deployment Mode

1. 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).

2. Scenario Management: Used to customize a collection scenario that the SOP collection is unavailable (optional).

OMStar





14

3. NE Management: In Co-Deployment Mode cannot create or delete an NE.

4. NE Mediation Version Information: Check the NE Mediation Version information on M2000

2.1.2 Using NIC in Co-Deployment Mode to collection data

After preparations, use the NIC in co-deployment mode to collect data in the specific

collection scenarios by referring to sections 2.3 "Collecting GSM Data" to 2.7 "Collecting

data for RNC and NodeB PMI."

After data collection, view data collection results by referring to section 2.8 "Viewing the

Collection Result."

2.2 Using NIC Stand-Alone Version

NOTE The NIC installation path must be an absolute path. It is a combination of English letters, numbers,

underlines, and hyphens. It does not support Chinese characters, garbled characters, and spaces.

The NIC cannot be installed by overlapping the installation path of the previously installed version.

The main program language edition for the NIC installation must be consistent with the NE language edition.

The following section describes the procedure for installing NIC V100R006C00SPC500 and later versions.

The last version of stand-alone is NIC V100R006C00SPC800. The WebNIC is from the version of iManager M2000 V200R11C01SPC230 start. It does not need to install independently.

2.2.1 Installing the NIC Tool

Obtain the NIC package NICV100R006C00SPC***.exe, and start the NIC console. Then, do

as follows:

Step 1 Double-click NICV100R006C00SPC***.exe. In the displayed dialog box, select a temporary path for decompressing the package, and click OK.

Step 2 In the directory saving the decompressed files, click NIC.exe. The NIC Console dialog box is displayed, as shown in step 3.

Step 3 When the NIC Console dialog box is displayed, perform related operations on the NIC console:

OMStar





15

----End

2.2.2 Using NIC Stand-Alone Version

The following steps show how to use the NIC stand-alone version. For details, see related

sections.

1. Obtain and install the mediation matching the NE version.

2. Start the NIC and create an NE.

3. Collect data.

2.2.3 Installing the Mediation Matching the NE Version

I. Precautions for Installing the Mediation

The mediation for each NE involved should be installed for SingleRAN check, including the

mediations of GSM NEs (GBSC and GBTS), UMTS NEs (RNC and NodeB), and eNodeB.

NOTE

The main program language edition and mediation language edition for the NIC installation must be consistent with the NE language edition.

You must install the mediation matching a specific NE version by choosing NIC Tools Suite >

Mediation layer manager. Double-clicking the setup program to install the mediation is not allowed.

The following section describes the procedure for installing the mediation of NIC V100R006C00SPC500 and later versions.

You need to configure "Server Proxy Configuration" to collect NodeB data.

II. Procedure for Installing the Mediation for NIC V100R006C00SPC500 and Later Versions

Step 1 Choose NIC Console > Mediation Packages Manager.

OMStar





16

Use the Mediation Packages Manager to install the mediation of each NE version. If you

install a mediation by double-clicking the mediation package, the mediation may be installed

in an incorrect directory.

Step 2 Click Install From file.

Step 3 Select a mediation file to install. Mediation files have three formats: .exe, .tar, and .zip. In the Files of Type field, select a required format.

The language of the mediation package whose name contains CHS or ENG must be consistent

with the language of the NIC main program.

OMStar





17

Step 4 After the installation of the mediation package is complete, click Exit.

----End

2.2.4 Using the NIC to Collect Data

I. Overview of NIC GUI

1. 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).

2. Scenario Management: Used to customize a collection scenario that the SOP collection is unavailable (optional).

3. NE Management: Used to create or delete an NE. For details about how to create an NE.

4. Upload Management: Used to create an upload task (uploading data to the FTP server automatically (this function can be ignored for SOP)

The upload management module is deleted in NIC V100R006C00SPC700 and later

versions.

II. Creating an NE

NOTE

This section describes how to create a BSC manually on the NIC. For details about how to import NEs in batches, see the FAQ.

Step 1 Start the NIC service.

Click Start NIC in the NIC Console, as shown in the following figure:

OMStar





18

Step 2 Choose NE Management > NE Information Maintenance.

Step 3 Select the NE type.

For GSM NEs, select BSC6900 GSM, as shown below:

OMStar





19

For UMTS NEs, select BSC6900 UMTS, as shown below:

For GU dual-mode NEs, select BSC6900 GU, as shown below:

OMStar





20

For LTE NEs, select eNodeB, as shown below:

Step 4 Configure the NE connection information (use UMTS as the example).

BSC6900 UMTS:

Network element name and Network element IP: Indicates the name and IP address of the

NE to be created. Network element name and Network element IP are both unique and

identify a unique NE.

User type: Indicates the type of the user for logging in to the RNC. The user can be either a

domain user or a local user. If you select a domain user to create an NE, the NE must be

managed by the M2000.

OMStar





21

LMT User name and LMT Password: Is equivalent to the LMT login "user name" and

"password", the user's operating authority need to be "Administrator" management level.

Connect and Authenticate Mode: Sets the RNC connection mode to Plain or SSL. When

SSL is selected, the authentication mode can be None or Peer.

NodeB user name and NodeB password: Indicates the user name and password of all

NodeBs under the current RNC. By default, NodeB user name is admin and NodeB

password is NodeB.

FTP port, FTP user name, and FTP password: Indicates the port number, user name,

password of the FTP server on the current RNC. By default, FTP port is 21 and User name is

FtpUsr.

Connect NodeB: Indicates whether to connect a NodeB when creating an RNC. If data is

only collected on the RNC, you are advised to select no. You need to install the mediation for

the NodeB before selecting yes.

Step 5 Click Apply to create an NE.

SOP data collection will collect configuration data, performance data, alarm data, and MML

data from the BSC, NodeB data, and eNodeB data. If data collection of the NodeB and

eNodeB fails, check whether Proxy Mode is selected in the Server Proxy Configuration

window and whether the NodeB and eNodeB are running properly.

NOTE If NE creation fails, please see the FAQ.

----End

III. Creating a Collection Task

After preparations, use the NIC stand-alone version to collect data in the specific collection

scenarios by referring to sections 2.3 "Collecting GSM Data" to 2.7 "Collecting data for RNC

and NodeB PMI."

After data collection, view data collection results by referring to section 2.8 "Viewing the

Collection Result."

2.3 Collecting GSM Data

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

OMStar





22

Step 2 Set Task Name, and select GSM from the Product Type drop-down list box, and select BSC6900GSM_SOP from the Scenario(Group) drop-down list box.

Task Name: The name of the collection task for inspection or SOP can contain letters (a to z

and A to Z), numbers (0 to 9), spaces, Chinese characters, underline (_), and dashes (-). The

name cannot contain more than 64 characters, and spaces before and after task name will be

ignored. The task name here must be consistent with the name of the analysis task in OMStar

V500R008.

Task Execution Type: You are recommended to select Instant. If you select Scheduled, you

also need to set the execution time.

Step 3 Click Next to set Data collection time range.

Data collection time range: You are advised to collect data of three to seven days (if the time

range is too large, the collection and analysis efficiency is affected).

OMStar





23

Step 4 Select Display by NE type. Select a BSC under the BSC6900 GSM node in Optional NEs, and move the selected BSC to Selected NEs. Then, click Next.

During routine inspection and maintenance SOP, you need to select only BSC/RNC. If

Display by Topo structure is selected, when you select a BSC/RNC, the BTSs/NodeBs under

the selected BSC/RNC are also selected. As a result, the total number of NEs may exceed the

upper limit.

Step 5 For R12 version and earlier, click each NE in the left pane, ensure that the parameter settings of each NE are correct, and click Next.

OMStar





24

Step 6 Set additional information such as Name and Email, and click Next.

Do not select Download collection results by NEs. Otherwise, the OMStar cannot identify the

downloaded packet.

Step 7 After ensuring that the collected information is correct, click Finish to start executing the collection task.

OMStar





25

----End

2.4 Collecting UMTS Data Step 1 Click the Task Management tab. Select Unfinished Tasks in Navigation Tree, and select

Based on Scenario from the Create Task drop-down list box in Task List.

Step 2 Set Task Name, and select UMTS from the Product Type drop-down list box, and select BSC6900_SOP from the Scenario(Group) drop-down list box.

OMStar





26





V500R008.

Product type:Choice UMTS

Scenario group: Choice SOP scenario(RNC and NodeB scenario group name change for SOP after the version of V9R14C00SPC200). Choice UMTS_SOP scenario. Why the NIC both have UMTS_SOP and SOP scenario in the NE version of R15. Has anything to

distinguish? Which data have been collected? Answer: The scene (group) has been unified

SOP where is in the following picture.There are contain UMTS SOP scenario and NodeB SOP scenario when you choice SOP scenario, to ensure you can collect the SOP data of RNC and NodeB at the same time.






OMStar





27

Step 4 Select Display by NE type. Select an RNC under the BSC6900 UMTS node in Optional NEs, and move the selected RNC to Selected NEs. Then, click Next.




upper limit.

OMStar





28




downloaded packet.

OMStar





29


----End

2.5 Collecting GSM and UMTS Data


Step 2 Set Task Name, and select SingleRAN from the Product Type drop-down list box, and select BSC6900GU_SOP from the Scenario(Group) drop-down list box.

OMStar





30





V500R008.






OMStar





31

Step 4 Select Display by NE type. Select an RNC under the BSC6900 UMTS node in Optional NEs, and move the selected RNC to Selected NEs. Then, click Next.




upper limit.


OMStar





32



downloaded packet.


----End

OMStar





33

2.6 Collecting LTE Data If the versions of the eNodeBs to be inspected are all LTE V100R005C00SPC360 or later, see

the instructions in section 2.6.3 "Collecting Data Based on the Scenarios of the NIC" for data

collection. Otherwise, see the instructions in sections 2.6.1 "Editing NIC Scenario" and

2.6.2 "Creating a Collection Task Based on the Scenario."

2.6.1 Editing NIC Scenario

1. Scenario Management

2. Default ScenariosLTECommonOMSTAR_Check.

3. Add 4 collection items in all eNodeB types. (such as the blue part)

License Information

Querying patch on NE

eNodeB Information Query

Software Version Query

OMStar





34

4. Save the Customized Scenario.

2.6.2 Creating a collection task based on the Scenario


OMStar





35

Step 2 Set Task Name, and select LTE from the Product Type drop-down list box, and select Common from the Scenario(Group) drop-down list box, then choose OMSTAR Check.

Step 3 Set collection data for the beginning and ending time: 00:00-00:00

OMStar





36

Beginning and ending time for data collection related to the inspection scene,

specific requirements are as follows:

According to the days of inspection, collecting data of the last day;

According to the weeks of inspection, collection of data in the last 7 days;

According to the months of inspection, collection of data in the last 7 days;

According to the Quarters of inspection, collection of data in the last 7 days;(Priority)

Step 4 Select the selection of the Network Element object: (select about 200-250 eNodeBs every time)

OMStar





37

Step 5 Next



OMStar





38

----End

2.6.3 Collecting Data Based on the Scenarios of the NIC


OMStar





39

Step 2 In the displayed Scenario Task Creation Wizard window, enter the task name, select LTE for Product Type, and select Common for Scenario(Group).

In LTE V100R005C00SPC360 or later versions, four collection scenarios are available for

LTE FDD.

LTE FDD Key Alarms Scene(Daily) Collects configuration files, alarm lists, and

some MML query results.

LTE FDD Routine Inspection Scene(Weekly) Collects configuration files, alarm lists, some

MML query results, and traffic statistics.

LTE FDD Basic Inspection Scene(Monthly) Collects configuration files, alarm lists, some


LTE FDD Deep Inspection Scene(Quarterly) Collects configuration files, alarm lists, all


NOTE

If only alarm data is to be analyzed, select LTE FDD Key Alarms Scene (Daily). Otherwise, select LTE FDD Deep Inspection Scene (Quarterly).

Step 3 Set collection data for the beginning and ending time: 00:00-00:00

OMStar





40

Beginning and ending time for data collection related to the inspection scene,

specific requirements are as follows:

According to the days of inspection, collecting data of the last day;

According to the weeks of inspection, collection of data in the last 7 days;

According to the months of inspection, collection of data in the last 7 days;

According to the Quarters of inspection, collection of data in the last 7 days;(Priority)

Step 4 Select the selection of the Network Element object: (select about 200-250 eNodeBs every time)

OMStar





41

Step 5 Next



OMStar





42

----End

2.7 Collecting data for RNC and NodeB PMI

NOTE The UMTS_SOP V5.2 script package (matched with OMStar V500R008C00SPC200) supports the

NodeB preventive maintenance inspection (DBS3900WCDMAV200R013C00/BTS3900WCDMAV200R013C00). The OMStar whose version is earlier than V500R008C00SPC200 does not need to collect the NodeB data.

The NIC in co-deployment mode provides the access of all NodeBs in the following versions. The NIC in co-deployment mode in the OMStar of earlier versions does not support the NodeB data collection.

iManager M2000 V200R011C01SPC240 and later versions

iManager M2000 V200R012C00SPC220 and later versions

The following section uses the UMTS NE as an example. The data collection method for the SingleRAN is the same.

The method described here also applies to the NICs in stand-alone and co-deployment modes.

You are advised to collect data of one RNC and its corresponding NodeBs for the RNC and

NodeB preventive maintenance inspection. It is recommended that you create multiple collection tasks for multiple NEs.

Before collect the NodeB performance data, you should firstly make sure the M2000 let the NodeB performance to be saved.

2.7.1 Collecting RNC and NodeB Data in One Task

In BSC6900 V900R014C00SPC200 and later versions, the Scenario(Group) names of RNC

and NodeB are both SOP.For RNC and NobeB co-collection task, see step 3.

In BSC6900V900R014C00SPC200 earlier versions, As the UMTS_SOP and the NodeB_SOP

collection scenarios belong to different groups, they cannot be selected concurrently when

you create a collection task. You can modify the groups that the UMTS_SOP and

NodeB_SOP collection scenarios belong to ensure that the two collection scenarios belong to

the same group by performing the following operations. Then, the RNC and NodeB data can

be collected concurrently in one task.

One task collects the data of 1 RNC and 249 NodeBs at most.( In M2000

V200R012C01SPC230 and later versions, when the NIC is co-deployed with the M2000, a

OMStar





43

collection task can support the data collection of one RNC and 999 NodeBs, and the NIC

automatically divides the task to four subtasks.)

Step 1 Modify the group that the UMTS_SOP scenario belongs to.

Choose Scenario Management > UMTO_SOP to view the scenario configuration of the

BSC6900UMTS_SOP. Change the default group UMTS_SOP to SOP and click Save As. In

the displayed dialog box, change the scenario name to BSC6900UMTS_SOP_NEW.

If the number of existing scenarios in the NIC exceeds 200, the modification cannot be saved.

Collect data by referring to section 2.7.2 "Collecting the RNC and NodeB Data Separately

and Creating a Data Package."

Step 2 Modify the group that the NodeB_SOP scenario belongs to.

Choose Scenario Management > NodeB_SOP to view the scenario configuration of the

NodeB_SOP. Change the default group NodeB_SOP to SOP and click Save As. In the

displayed dialog box, change the scenario name to NodeB_SOP_NEW.

OMStar





44

Step 3 Return to the Task Management window to create a collection task, choose the SOP scenario group, and select the UMTS and NodeB collection scenarios.

----End

2.7.2 Collecting the RNC and NodeB Data Separately and Creating a Data Package

If you cannot concurrently collect RNC and NodeB data in one task in the methods described

in section 2.7.1 "Collecting RNC and NodeB Data in One Task," collect the RNC and NodeB

data separately and manually create a data package to perform the PMI.

Step 1 Create a UMTS_SOP collection task and obtain an RNC data package.

OMStar





45

Step 2 Create a NodeB_SOP collection task and obtain a NodeB data package.

You can select a maximum of 1000 NodeBs in one task. The NIC automatically collects data

of 1000 NodeBs per subtask.

OMStar





46

Step 3 Compress the UMTS_SOP and NodeB_SOP collection results into a data package by performing the following operations.

The UMTS_SOP and NodeB_SOP collection tasks obtain the following two collection

results:

Drag the data folders in the UMTS compression package to the directory of the NodeB

compression package. Then, you obtain a combo data package.

----End

2.8 Viewing the Collection Result

NOTE

Do not terminate the FTP service of the tool during data collection; otherwise, the collection will fail.

Check whether configuration data collection fails. The data analysis of the NE where configuration data collection fails will also fail.

Step 1 During collection, view the progress of the whole collection task and the progress and running status of each NE.

OMStar





47

Step 2 The data collection results are saved.

The NIC stand-alone version collects and saves data.

The save path of NIC V100R006C00SPC500 and later versions is Installation directory of

the NIC\NIC\var\nic\task ID.

NOTE

Task IDs are generated randomly, for example, 10002, 10003, and 10004.

Check whether the task ID folder saves the collection task created by the user based on the collection task name in the folder.

After data collection by using the NIC in co-deployment mode, collection results are

downloaded and saved through a web page, as shown in the following figure:

OMStar





48

Collection results are downloaded in .zip format. The naming convention of the data package

is collection task name_timestamp, as shown in the following figure:

NOTE The data packet downloaded by the NIC in co-deployment mode from the GUI must be copied to

the directory that is used as the database directory when you create a task in the OMStar

V500R008. The version earlier than OMStar V500R008C00SPC200 does not support the download of data packet by the NIC in co-deployment mode.

Step 3 Record the directory for saving the data collection results for the further analysis of the OMStar in one-click 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 record the directory for saving the collected data.

----End

OMStar


Maintenance SOP 3 Data Analyze by using OMStar



49

3 Data Analyze by using OMStar This chapter describes how to implement the automatic data import and analysis and generate

a summary report on the OMStar V500R008 in one-click mode. The descriptions about the

manual data import and analysis and other functions of the OMStar are not included in this

chapter.

3.1 Installing the OMStar Tool

Perform the following steps to install OMStar V500R008:

Step 1 Run GENEX_OMStar_V500R008.exe. In the displayed Installer Language Selection dialog box, choose English from the drop-down list box and then click OK, as shown in Figure 3-1.

Figure 3-1 Installer Language Selection dialog box

Step 2 The GENEX OMStar V500R008 Setup Wizard dialog box is displayed and then click Next, as shown in Figure 3-2.

OMStar





50

Figure 3-2 GENEX OMStar V500R008 Setup Wizard dialog box

Step 3 The License Agreement dialog box is displayed and then click I Agree, as shown in Figure 3-3.

Figure 3-3 License Agreement dialog box

OMStar





51

Step 4 The Select Installation Path dialog box is displayed. Select the installation path, and then click Next, as shown in Figure 3-4.

Figure 3-4 Select Installation Path dialog box

NOTE

If PostgreSQL had been installed, the dialog box is displayed as shown in Figure 3-5. Select an

installation path and then click Next to Step 6.

OMStar





52

Figure 3-5 Select Installation Path dialog box

Step 5 The Set Password dialog box is displayed. Set the database password by request and then chick Install, as shown in Figure 3-6.

Figure 3-6 Set Password dialog box

OMStar





53

Step 6 The Installation Status dialog box is displayed, as shown is Figure 3-7.

Figure 3-7 Installation Status dialog box

Step 7 After the installation is complete, the Setup Complete dialog box is displayed and click Finish, as shown in Figure 3-8.

Figure 3-8 Setup Complete dialog box

OMStar





54

Step 8 Return to the desktop. The shortcut icons of the installed components are displayed on the desktop.

----End

3.2 Obtaining Authorization and Applying License

3.2.1 Background Information

Usage authority control applies in limiting the usage scope of the OMStar series software and

the user roles. It is related to all the functions of the OMStar series software. When a user

starts the software, the system first checks whether the current software is authorized. If the

software is not authorized, it is unavailable. When a user installs or upgrades the OMStar

series software, the user must first obtain the usage authority.

3.2.2 Authentication Management

When the software is started, the system first checks whether the current software has been

authorized. If the software is not authorized, the OMStar Authentication dialog box is

displayed, as shown in Figure 3-9.

Figure 3-9 Authentication window

Method1Domain Authentication

Click Login China Domain. OMStar will connect your computer to the China domain network, if

the connection is successful; the login interface is displayed, as shown in Figure 3-10.

OMStar





55

Figure 3-10 China domain authentication

Type the information for authentication and click OK. If the authentication is successful, a

dialog box is displayed.

Figure 3-11 Authentication result dialog box

Method2Update the License

If your computer cannot access the China domain network, click Update License to obtain

usage authority. Procedures are as follows:

1. Before updating the license, send the ESN(as shown in Figure 3-9) of your computer to a

Huawei engineer who can access China domain network. The engineer uses the OMStar

License Application function to apply for an offline license file. For details, see section

Appllying License Manually."

2. After obtaining the offline license file, click Update License. The Select License file dialog

box is displayed, as shown in Figure 3-12. In the dialog box, select the License Code.lic file

that has been applied for and click OK.

OMStar





56

Figure 3-12 Select License file dialog box

If the license update succeeded shows the OMStar dialog box.

Figure 3-13 Update Success dialog box

Applying License Manually

The OMStar series software allows you to apply for offline license files. This section provides a

method of obtaining the authorization for the OMStar users who cannot choose Login China

Domain.

Prerequisites

The current computer has been connected to the China domain network and has obtained OMStar

Authentication.

Procedures for Applying for the License.

1. Choose Help > Apply Off-line License from the menu bar, as shown in Figure 3-14.

OMStar





57

Figure 3-14 Off-lice License Application dialog box

Click Browse to set the save path for the license file. Enter the ESN of the computer to be

authorized. If you, on behalf of others, apply for the license, enter the ESN of their computers.

Click Submit. If the application is successful, the system displays a message, as shown

inFigure 3-15. The file License Code.lic is saved to the preset path.

Figure 3-15 OMStar License Application dialog box

NoteEnsure that you have obtained the usage authority for the OMStart software through domain authentication before you apply for the license manually. To obtain the usage

authority by updating the license, you must pass the domain authentication before applying

for the license. If your computer cannot access the China domain, the authentication cannot be

done.

OMStar





58

Query License Infomation

After you start the tool software, choose Help >Authority Management from the

system menu. The License Information dialog box is displayed, as shown in Figure 3-16.

Figure 3-16 License Information dialog box

The OMStar series software can be used only within the license validity period. When the license expires, the software is unavailable. You can use the software again after being authorized.

----End

WARNING

Ensure that you have obtained the usage authority for the OMStar software through domain

authentication before you apply for the license manually. To obtain the usage authority by

updating the license, you must pass the domain authentication before applying for the license.

If your computer cannot access the China domain, the authentication cannot be done.

OMStar





59

3.3 Introduction to the OMStar V500R008

The automatic task setting function can be used for network inspection. Automatic task setting

and inspection analysis can be implemented in GSM Network Inspection, UMTS Network

Inspection, LTE FDD Network Inspection, LTE TDD Network Inspection, and GUL Network

Inspection, which facilitates the implementation of the standard operating procedure (SOP)

for daily maintenance.

NOTE All data collected from customers' offices for analysis by the OMStar can be taken out of the

customers' offices only after consent is given by the customers.

Obtain the CHR and PCHR data for analysis with written consent of the customer.

Do not transmit raw network data outside EEA area and to China.

Delete data after using it. Do not keep any permanent file that contains plaintext private data, such as raw files, reports, and database.

The plaintext private data, such as IMSI, ESN, and IMEI, should be masked in the report provided for the customer. This type of data should be expressed in such methods as anonymization, division, and code.

Click Start, click OMStar V500R008, start OMStar V500R008.

3.3.1 GSM Network Inspection

I. GSM One-Click Analysis

Step 1 Choose Expand Subject > Network Inspection from the OMStar main menu, as shown in Figure 3-17.

OMStar





60

Figure 3-17 Network Inspection menu

Step 2 In the displayed Expand Subject Task Management tab page, click , as shown in Figure 3-18.

Figure 3-18 Network inspection task entrance

OMStar





61

Step 3 In the displayed New Task dialog box, set TaskName and Data Source Path, choose NE, and then click Next, as shown in Figure 3-19.

Figure 3-19 New Task dialog box

Task Name: Indicates the name of a task. This parameter is mandatory.

Description: Indicates the information about a task. This parameter is optional.

Inspection Type: Choose Single Network System Inspection for GSM Network Inspection. This parameter is mandatory.

Data Source Path: Indicates the directory where raw data collected by the NIC is stored. This parameter is mandatory.

NOTE

The OMStar can automatically derive NE information from the raw data collected by the NIC. You can

choose an NE for analysis according to actual requirements.

The OMStar distributes NEs of the same version into the same task.

LTE ID: This parameter does not need in GSM Network Inspection.

NodeB License: This parameter does not need in GSM Network Inspection.

Co-site Info: This parameter does not need in GSM Network Inspection.

Step 4 In the displayed New Task dialog box, specify Report Path, Report Language, and Time Setting, and then click Next, as shown in Figure 3-20.

OMStar





62

Figure 3-20 New Task dialog box

NOTE

If multiple versions of an NE are selected in step 1, the Next button in Figure 3-20 is

displayed as Finish. In this situation, click Finish. Check items and thresholds can be adjusted by editing task information.

Report Path: Indicates the path for saving the report. This parameter is mandatory.

Report Language: Indicates the language (Chinese or English) used by the report. This parameter is mandatory.

Reserve Project: Indicates whether to delete the project when a task is complete. This parameter is optional.

Set Parameters: Indicates setting or adjusting the number of BSC in a task. A task can

be created for 5 BSCs of the same version in GSM Network Inspection as default.

Time Setting: Indicates the duration for task analysis. Its default value is All Day. This parameter is mandatory.

Step 5 On the Check Item Setting tab page, specify Sub Scenario and select check items, as shown in Figure 3-21. On the Threshold Setting tab page, select check items and set thresholds for

these check items, as shown in Figure 3-22.

OMStar





63

Figure 3-21 Check Item Setting tab page

Import: You can click this button to import an exported template, without selecting check items.

Export: After selecting check items, click this button. The selected check items can be exported and saved.

Figure 3-22 Threshold Setting tab page

OMStar





64

Reset all threshold of current version: If you click this button, all thresholds of the

current version are restored to their default values.

Reset current threshold: If you click this button, the selected thresholds are restored to their default values.

Save: Each time thresholds are adjusted, click this button so that the adjustments can take effect.

Import: You can click this button to import an exported template, without setting

thresholds.

Export: After setting thresholds, click this button. The configured thresholds can be exported and saved.

Step 6 Click Finish. Right-click the task that has been configured in the main interface of Expand Subject Task Management, and then choose Run from the shortcut menu to start the task.

Alternatively, click to start the task. The OMStar supports multiple tasks simultaneously

running. Figure 3-23 shows the interface for starting a network inspection task.

Figure 3-23 Interface for starting a network inspection task

NOTE

For tasks created in batch, adjust parameters for each task.

Step 7 View the task running status and execution process.

NOTE

The Status area indicates the running status of a task. A task can be in one of the following states:

Idle: Indicates that the task is being initialized. You can edit, start, or delete the task.

OMStar





65

Waiting: Indicates that the task is waiting. You can stop 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 running state at a time and the other tasks are in waiting state.

Finish: Indicates that the task is complete. You can edit, restart, or delete the task.

Failed: Indicates that the task fails. You can edit, restart, or delete the task.

Step 8 When the task is complete, click the hyperlink in the Report area, as shown in Figure 3-24.

Figure 3-24 Interface for viewing result reports

Step 9 In the displayed Browse Report dialog box, click the hyperlink to the report to view the network evaluation result reports for all NEs in this task, as shown in Figure 3-25.

OMStar





66

Figure 3-25 Browse Report dialog box

NOTE

Report Name: The report is named in the following format: NE name + Generation time stamp of the report.

----End

II. GSM Summary Report

Report summarization is used to summarize single-NE reports generated by one-click analysis

tasks which support the type of Excel and Word. You can generate summary reports by

enabling the Summary Report function supported by the OMStar V500R008.

NOTE

Do not start the Excel program during the summarization; otherwise, the summarization will fail.

Data only in one file can be selected for analysis if an NE generates multiple files containing historical data.

The current version supports only the sum of Excel reports that have the same language types, NE versions, and sub-scenarios.

To ensure that reports can be summed correctly, keep the size of each Excel report less than or equal to 200 MB.

When generating a Word summarization report, an Excel report is also generated incidentally. The Excel report is different from the Excel summarization report and is used only for reference. In

addition, some tables and figures in the Word summarization report display only Top N records. You can view the entire records in the incidentally generated Excel report.

OMStar





67

Step 1 Choose Expand Subject > Summary Report from the OMStar main menu.

Step 2 In the displayed Expand Subject Task Management tab page, click .

Step 3 In the displayed New Task dialog box, set TaskName and Data Source Path, choose GSM_NetworkInspection for Scene, and then click Next.

OMStar





68

Task Name: Indicates the name of a task. This parameter is mandatory.

Description: Indicates the information about a task. This parameter is optional.

Scene: Choose GSM_NetworkInspection for GSM summary report.

Language: Indicates the language (Chinese or English) used by the report. This parameter is mandatory.

Report Type: Indicates the file type (Excel or Word) of the report. This parameter is mandatory.

Report Path: Indicates the path for saving the report. This parameter is mandatory.

Import: You can click this butto

operation guide to the omstar v500r008 for maintenance sop

Documents

huawei proprietary

huawei trademarks

document issue

document author

omstar v500r008

maintenance sop issue

maintenance sop contents

huawei industrial base