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.
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:
support@huawei.com
Issue 01 (2013-04-08)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Operation Guide to the OMStar V500R008 for

Maintenance SOP
About This Document
About This Document

Author
Prepared By
Chen Ping (Employee ID: 00151537)
Date
2013-02-17
Reviewed By
Liu Junwei (Employee ID: 00148069);
Date
2013-04-07
Date
2013-04-08
Qi Peizhi (Employee ID: 00143926)

Approved By
Wang Yan (Employee ID: 45750)
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
Issue 01 (2013-04-08)

ii

Maintenance SOP
About This Document
NIC
Network Information Collection
OMStar
Operation&Maintenance Star
Issue 01 (2013-04-08)

iii
OMStar
Maintenance SOP
Contents
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
Issue 01 (2013-04-08)

iv
OMStar
Maintenance SOP
Contents
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
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
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
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
LTE-TDD
1 Overview
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.
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
1.5 Installation Requirements

1.5.1 Installation Environment Specifications
Hardware Requirement
Software Requirement
Model: common PC
OS: Windows 7 (32 bit)operating

system
CPU: P4 3.1 GHz or higher

Memory: 4 GB or higher
Hard Disk: 160 GB or higher
Browser: Internet Explorer 7.0 or later

Others: Office 2007 or Office 2010
Accessories: Network adapter/17-inch LCD

display
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
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
NIC
480 MB
Disk for NIC installation

directory: 170 MB/BSC
Collected data package: 5

GB
(300 base stations

1200 cells)
OMStar
1.36G
Disk for collected data

package: 180 MB/BSC
Disk for collected data

package: 5.5 GB
Disk for OMStar

installation directory: 2.5
GB
Disk for OMStar

GB (same as that in the
Required Space for
(Single BSC) column.)
Seven-day traffic
data and
granularity 60
minutes.
Disk for OMStar project

storage: 10 GB
LTE:
250 eNodeBs
Disk for OMStar

GB (same as that in the
Required Space for
(Single BSC) column.)
Seven-day traffic
data and
granularity 60
minutes.
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.
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
Ports
Source Device
Target Device
Description
30700
NIC server
NIC server
These ports are NIC internal ports.
31000
31007
31009
31015
31030
31032
31037
31038
6432
5432
OMStar Ports
Target Device
Description
Port
Source
Device
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.
30020
TCP/IP
OMStar and 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

communicating to update rules.
62956
TCP/IP
Authentication
The default port used when

communicating to authenticate.
9013
TCP/IP
Authentication
The standby port used when

communicating to authenticate.
5013
TCP/IP
ESAU CHR data
Used by default when obtaining
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
CHR data.
12345
TCP/IP
OSGI Frame
Used during OSGI monitor

service.
8091
TCP/IP
OMStar and eSAU

8081
TCP/IP
OMStar

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.
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
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/
BSC data
configuration file
MML command and FTP upload
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.
UMTS
Run the BKP CFGFILE command

to back up files. The parameter is the
customized file name.
Run the ULD CFGFILE command
to upload files.
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.
BSC alarm file

Run the COL LOG:
LOGTYPE=HISTORY_ALARM1; 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.
Issue 01 (2013-04-08)
BSC operation
logs
BSC active alarm

file
Run the LST ALMAF command to

save the returned information.
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.zi
p. Then, upload this log file through
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.
The BSC alarm file
is an optional item
and is used for alarm
analysis.
The BSC operation

logs is an optional
item and is used for
log analysis.
The BSC active

alarm file is an
optional item and is
used for alarm
analysis.
OMStar
Maintenance SOP
Mode
1 Overview
Data Source
Description
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
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,
automatic analysis
fails.
NodeB alarm file
M2000+FTP upload:

to upload files.
Obtain the alarm file name list such

as
20120116170448-alarm-log-auto-1.c
sv
The NodeB alarm

file is an optional
alarm analysis.
20120116170448-event-log-auto-1.c
sv
NodeB traffic
statistics file
Co-site
information table
Issue 01 (2013-04-08)

M2000 R11
/export/home/sysm/ftproot/pm/
M2000 R12
/export/home/sysm/ftproot/nbi/
A20110330.2000+0800-2030+0800
_EMS-NORMAL.mrf.gz. Then,
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.

TheNodeB traffic
optional item and
can be used for
checking the device
and system loads
and analyzing
resource usage and
network
performance.
The co-site
information table is
an optional item and
is used for checking
the configuration of
an MBTS.
OMStar
Maintenance SOP
1 Overview
Mode
Data Source
Description
LTE
eNodeB data
configuration file
MML command and FTP upload:
The eNodeB data

a mandatory item
and provides basis
for network object
analysis on the
is not available,
automatic analysis
fails.
Run the BKP CFGFILE command

to back up files. The parameter is the
customized file name.
to upload files.
eNodeB traffic
statistics file
eNodeB alarm
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,
M2000+FTP upload:
Obtain the alarm file name list such
as
20120116170448-alarm-log-auto-1.c
sv
The eNodeB traffic

optional item and
can be used for
checking the device
and system loads
and analyzing
resource usage and
network
performance.
The eNodeB alarm
file is an optional
alarm analysis.
20120116170448-event-log-auto-1.c
sv
eNodeB MML
data file
MML command:
eNodeB CHR file
Run the following commands to

save the returned information: DSP
BRD; DSP LICENSE; DSP CELL;
LST VER; DSP ETHPORT and
DSP BRDVER.

20120302_145654+0800_0115.CH
R,
20120305_103500+0800_0000.SIG.
The eNodeB MML

data file is an
used for checking
device status and
analyzing
configuration.
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.
Issue 01 (2013-04-08)

OMStar
Maintenance SOP
1 Overview
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.
Issue 01 (2013-04-08)

10
OMStar
Maintenance SOP
2 Data Collection by using the NIC
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.
Issue 01 (2013-04-08)

11
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

12
OMStar
Maintenance SOP
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).
Issue 01 (2013-04-08)

13
OMStar
Maintenance SOP
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:
Issue 01 (2013-04-08)

14
OMStar
Maintenance SOP
----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.
Issue 01 (2013-04-08)

15
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

16
OMStar
Maintenance SOP
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:
Issue 01 (2013-04-08)

17
OMStar
Maintenance SOP
Step 2 Choose NE Management > NE Information Maintenance.
Step 3 Select the NE type.

For GSM NEs, select BSC6900 GSM, as shown below:
Issue 01 (2013-04-08)

18
OMStar
Maintenance SOP
For UMTS NEs, select BSC6900 UMTS, as shown below:
For GU dual-mode NEs, select BSC6900 GU, as shown below:
Issue 01 (2013-04-08)

19
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

20
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

21
OMStar
Maintenance SOP
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).
Issue 01 (2013-04-08)

22
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

23
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

24
OMStar
Maintenance SOP
----End
2.4 Collecting UMTS Data

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.
Issue 01 (2013-04-08)

25
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

26
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

27
OMStar
Maintenance SOP
downloaded packet.
Issue 01 (2013-04-08)

28
OMStar
Maintenance SOP
collection task.
----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.
Issue 01 (2013-04-08)

29
OMStar
Maintenance SOP
V500R008.
Issue 01 (2013-04-08)

30
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

31
OMStar
Maintenance SOP
downloaded packet.
collection task.
----End
Issue 01 (2013-04-08)

32
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

33
OMStar
Maintenance SOP
4.
Save the Customized Scenario.
2.6.2 Creating a collection task based on the Scenario

Issue 01 (2013-04-08)

34
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

35
OMStar
Maintenance SOP
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)
Issue 01 (2013-04-08)

36
OMStar
Maintenance SOP
Step 5 Next
collection task.
Issue 01 (2013-04-08)

37
OMStar
Maintenance SOP
----End
2.6.3 Collecting Data Based on the Scenarios of the NIC

Issue 01 (2013-04-08)

38
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

39
OMStar
Maintenance SOP
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)
Issue 01 (2013-04-08)

40
OMStar
Maintenance SOP
Step 5 Next
collection task.
Issue 01 (2013-04-08)

41
OMStar
Maintenance SOP
----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
Issue 01 (2013-04-08)

42
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

43
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

44
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

45
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

46
OMStar
Maintenance SOP
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:
Issue 01 (2013-04-08)

47
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

48
OMStar
Maintenance SOP
3 Data Analyze by using OMStar
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.
Issue 01 (2013-04-08)

49
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

50
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

51
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

52
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

53
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

54
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

55
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

56
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

57
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

58
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

59
OMStar
Maintenance SOP
Figure 3-17 Network Inspection menu
Step 2 In the displayed Expand Subject Task Management tab page, click
Figure 3-18.
, as shown in
Figure 3-18 Network inspection task entrance
Issue 01 (2013-04-08)

60
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

61
OMStar
Maintenance SOP
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
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.
Issue 01 (2013-04-08)

62
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)

63
OMStar
Maintenance SOP
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:
Issue 01 (2013-04-08)
Idle: Indicates that the task is being initialized. You can edit, start, or delete the task.

64
OMStar
Maintenance SOP
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.
Issue 01 (2013-04-08)

65
OMStar
Maintenance SOP
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
Issue 01 (2013-04-08)
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.

66
OMStar
Maintenance SOP
Step 1 Choose Expand Subject > Summary Report from the OMStar main menu.
Step 3 In the displayed New Task dialog box, set TaskName and Data Source Path, choose
GSM_NetworkInspection for Scene, and then click Next.
Issue 01 (2013-04-08)

67
OMStar
Maintenance SOP
Scene: Choose GSM_NetworkInspection for GSM summary report.
Language: Indicates the language (Chinese or English) used by the report. This
Report Type: Indicates the file type (Excel or Word) of the report. This parameter is
mandatory.
Import: You can click this button to import reports to be summarized which generated
previously.
Delete: You can click this button to delete reports which has been loaded.
running.
Issue 01 (2013-04-08)

68
OMStar
Maintenance SOP
NOTE

NOTE
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.
Step 6 When the task is complete, click the hyperlink in the Report area.
Issue 01 (2013-04-08)

69
OMStar
Maintenance SOP
network evaluation result reports for all NEs in this task.
NOTE
Report Name: The report is named in the following format: Summary + Generation time stamp of the report.
---End
3.3.2 UMTS Network Inspection

I. UMTS One-Click Analysis
Figure 3-26.
Issue 01 (2013-04-08)

70
OMStar
Maintenance SOP
Figure 3-27.
, as shown in
Issue 01 (2013-04-08)

71
OMStar
Maintenance SOP
NE,and then click Next, as shown in Figure 3-28.
Inspection Type: Choose Single Network System Inspection for UMTS Network
NOTE
LTE ID: This parameter does not need in UMTS Network Inspection.
NodeB License: This parameter is optional in UMTS Network Inspection.
Co-site Info: This parameter does not need in UMTS Network Inspection.
Issue 01 (2013-04-08)

72
OMStar
Maintenance SOP
NOTE
Set Parameters: Indicates setting or adjusting the number of RNC in a task. A task can
be created for 5 RNCs of the same version in UMTS Network Inspection as default.
Issue 01 (2013-04-08)

73
OMStar
Maintenance SOP
check items.
exported and saved.
Issue 01 (2013-04-08)

74
OMStar
Maintenance SOP
take effect.
thresholds.
exported and saved.
NOTE

NOTE
Issue 01 (2013-04-08)

75
OMStar
Maintenance SOP
Issue 01 (2013-04-08)

76
OMStar
Maintenance SOP
NOTE
----End
II. UMTS Summary Report

NOTE
Issue 01 (2013-04-08)
historical data.
to 200 MB.

77
OMStar
Maintenance SOP
UMTS_NetworkInspection for Scene, and then click Next.
Issue 01 (2013-04-08)

78
OMStar
Maintenance SOP
Scene: Choose UMTS_NetworkInspection for UMTS summary report .
mandatory.
previously.
running.
Issue 01 (2013-04-08)

79
OMStar
Maintenance SOP
NOTE

NOTE
Issue 01 (2013-04-08)

80
OMStar
Maintenance SOP
NOTE
---End
3.3.3 LTE Network Inspection

I. LTE One-Click Analysis
Figure 3-35.
Issue 01 (2013-04-08)

81
OMStar
Maintenance SOP
Figure 3-36.
, as shown in
Issue 01 (2013-04-08)

82
OMStar
Maintenance SOP
Step 3 In the displayed New Task dialog box, set TaskName and Data Source Path, choose NEs
sand then click Next, as shown in Figure 3-37.
Inspection Type: Choose Single Network System Inspection for LTE FDD/TDD
Network Inspection. This parameter is mandatory.
NOTE
LTE ID: Choose FDD or TDDfor LTE FDD/TDD Network Inspection. This
NodeB License: This parameter does not need in LTE FDD/TDD Network Inspection.
Co-site Info: This parameter does not need in LTE FDD/TDD Network Inspection.
Issue 01 (2013-04-08)

83
OMStar
Maintenance SOP
NOTE
Set Parameters: Indicates setting or adjusting the number of eNodeB in a task. A task
can be created for 250 eNodeBs of the same version in LTE FDD/TDD Network
Inspection as default.
Issue 01 (2013-04-08)

84
OMStar
Maintenance SOP
check items.
exported and saved.
Issue 01 (2013-04-08)

85
OMStar
Maintenance SOP
take effect.
thresholds.
exported and saved.
NOTE

NOTE
Issue 01 (2013-04-08)

86
OMStar
Maintenance SOP
Issue 01 (2013-04-08)

87
OMStar
Maintenance SOP
NOTE
----End
II. LTE Summary Report

NOTE
Issue 01 (2013-04-08)
historical data.
to 200 MB.

88
OMStar
Maintenance SOP
LTE_FDD_NetworkInspection or LTE_TDD_NetworkInspection for Scene, and then
click Next.
Issue 01 (2013-04-08)

89
OMStar
Maintenance SOP
Scene: choose LTE_FDD_NetworkInspection or LTE_TDD_NetworkInspection for

LTE FDD/TDD summary report.
mandatory.
previously.
running.
Issue 01 (2013-04-08)

90
OMStar
Maintenance SOP
NOTE

NOTE
Issue 01 (2013-04-08)

91
OMStar
Maintenance SOP
NOTE
---End
3.3.4 GUL Network Inspection

GUL integrated inspection is to respectively collect and analyze data on the GSM, UMTS, or
LTE network, summarize the reports, and generate a GUI integration inspection report. It
mainly applies to the network of GUI integration. Here, the BSC6900GU live network is used
as an example. Create the GSM/UMTS/LTE Integrated Inspection task twice (the data source
Issue 01 (2013-04-08)

92
OMStar
Maintenance SOP
of the tasks are GSM and UMTS NIC data package respectively), obtain inspection reports,
and summarize the reports to generate the inspection report on the overall network by
referring to the following steps:
I. GUL One-Click Analysis

Figure 3-44.
Figure 3-45.
Issue 01 (2013-04-08)

, as shown in
93
OMStar
Maintenance SOP
Step 3 In the displayed New Task dialog box, set TaskName and Data Source Path, and then click
Next, as shown in Figure 3-46.
Issue 01 (2013-04-08)

94
OMStar
Maintenance SOP
Inspection Type: Choose GSM/UMTS/LTE Integrated Inspection for GUL Network

NOTE
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.
NOTE
Issue 01 (2013-04-08)

95
OMStar
Maintenance SOP
Set Parameters: Indicates setting or adjusting the number of BSC/RNC/eNodeB for a

task. A task can be created for 5 BSCs or 5 RNCs or 250 eNodeBs of the same version as
default.
check items.
exported and saved.
Issue 01 (2013-04-08)

96
OMStar
Maintenance SOP
take effect.
thresholds.
exported and saved.
Issue 01 (2013-04-08)

97
OMStar
Maintenance SOP
Figure 3-50 sInterface for starting a network inspection task
NOTE

NOTE
Issue 01 (2013-04-08)

98
OMStar
Maintenance SOP
For GUL_ NetworkInspection during the process of Report Summary the SRAN GUL
Co-Analysis check items will run, the check items list as shown.
GL CO-Transmission DHCP Relay Check
GL CO-Transmission DHCP Server IP Check
GL CO-Transmission Eth Port Property Check
Issue 01 (2013-04-08)

99
OMStar
Maintenance SOP
GU E1 CO-Transmission Logic Port Check
GU CO-Transmission DSCP Value Check
GU CO-Transmission DHCP Relay Check
GU CO-Transmission DHCP Server IP Check
GU CO-Transmission Eth Port Property Check
U3.8 M GSM Power Control Parameter Check
MBTS Version Consistent Check
NOTE
The report is named in the following format: NE name + Generation time stamp for GSM/UMTS,
Project name + Generation time stamp for LTE.
----End
II. GUL Summary Report

NOTE
Issue 01 (2013-04-08)
historical data.
to 200 MB.

100
OMStar
Maintenance SOP
Issue 01 (2013-04-08)

101
OMStar
Maintenance SOP
GUL_NetworkInspection for Scene, and then click Next.
Scene: Choose GUL_NetworkInspection for GUL summary report.
mandatory.
previously.
running.
Issue 01 (2013-04-08)

102
OMStar
Maintenance SOP
NOTE

NOTE
Issue 01 (2013-04-08)

103
OMStar
Maintenance SOP
NOTE
---End
Issue 01 (2013-04-08)

104
OMStar
Maintenance SOP
3.4 Handling Problems Based on the Summary Report

You need to handle the problems in the Summary Report after it is generated by the OMStar
V500R008. The following figure shows an example of the Summary Report.
Step 1 Filter key network problems.

If you need to focus on only exceptions, select Abnormal in column F to filter. If you need to
focus on only critical and major problems, select Critical and Major in column E to filter.
Step 2 Get familiar with the rules of the check items and the solutions.
Issue 01 (2013-04-08)

105
OMStar
Maintenance SOP
You can click Rules Description in column D of the Summary Report. Then the following
figure is displayed.
In the preceding figure, the cells under Rules Description of column F describe the cause
why each check item is marked Abnormal. For example, the rules of check item "GOU and
FG2a Brd Port" are as follows:
1.
If the interface boards (FG2a/GOUa) work in active/standby mode, and ports which do
not work in load sharing mode are occupied by IPPATH/SCTP (used for L3 networking),
the ports must be configured to work in active/standby mode.
2.
If two interface boards work in active/standby mode, the attributes of the ports with the
same number on the active and standby boards must be the same, namely, the AUTO
mode, MTU mode, and flow control mode must be the same.
3.
Check the active alarms, and whether the alarm id-21348 exists or not. If exists, list the
information of port.
4.
The value of MTU in the port attribute must be 1500, and AUTO mode should be
recommended as 'AUTO'.
Based on the preceding description, you can learn about when exceptions will occur on the
ports of the interface boards.
You can also learn about how to handle the problem based on the information under
Measures of column I.
Step 3 Locate and resolve the problem.
After learning the rules, you need to locate and resolve the problem accordingly.
Click a hyperlink in column C to return to the Check Item Summary sheet. Then, click an
item in column C or H to navigate to the sheet with specific check results. For example, the
following figure is displayed after you click "GOU and FG2a Brd Port" under column C. You
can learn that no standby port is configured for port 0 on the board that is housed in slot 26 of
subrack 2 of RNC 208 (RNC ID = 208). This information matches rule 1 for the check item
(see step 2); therefore, the result is displayed Abnormal. You can handle the problem by
Issue 01 (2013-04-08)

106
OMStar
Maintenance SOP
referring to the information under Measures of column I. For the example mentioned above,
you only need to configure a standby port for this port.
For some complex problems that you cannot handle by yourself, submit tickets in the iCare
system to track the progress and close the e-workflow.
Issue 01 (2013-04-08)

107
OMStar
Maintenance SOP
NOTE
Rules Description Reading Note:
For the definition of counter in rules, please refer the Performance counter Reference document.
The column of "Problem or Risk?" show whether the abnormal item is definitely a problem or risk,
"To be confirmed" means it may be a problem or risk, manual detailed analysis is needed, which can
be referred the content of column "Measures".
The troubleshooting note of failed rule:
If the measures are related to product data configuration modification, please refer the document on
support.huawei.com: WCDMA iu&iur&iub Transmission Configuration Recommendation, UMTS
RAN Network Design Reference, related product UMTS Initial Configuration Guide. if the problem
cannot be resolved with above mentioned document, please contact GTAC by ITR ticket.
For transmission&link problem, please confirmed with the customer if it is caused by transmission
equipment, and clarify the risk of the problem per mail, to push the customer to resolve the problem.
For the high load problem of board and link, please clarify the risk to the customer for expansion
decision, any question for expansion procedure please contact GTAC by ITR ticket.
The abnormal KPI problem in Performance SOP, if there is no related product operation or major
alarm, please transfer the problem to NTS, the problem in RNC level or subsystem level is
recommended to resolve with high priority.
The critical severity problem must be resolved. If you have any question, please contact GTAC by
ITR ticket.
The risk of critical and major severity problem must be clarified to customer per mail. If the
customer considers the risk is under controlled, the problem can be ignored.
If the resource congestion problem must be resolved by expansion, please confirm the expansion
solution with marketing personnel or generate ITR ticket.
For Alarm problem, please refer to the Alarm Reference. If the Alarm Reference cannot guide you to
handle the problem, please contact GTAC with ITR ticket for document improvement.
The links of the documents mentioned in the "Measures" of this page are as follows:
UMTS Maintenance Guide:

http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailProductSimple
&web_doc_id=SE0000424185&doc_type=123-2
RAN12 Feature Deployment Guide:

&web_doc_id=SE0000521452&doc_type=123-2

&web_doc_id=SC0000642604&doc_type=123-2&doc_type=123-2&saveBrowserLoged=true

http://support.huawei.com/hedex/hdx.do?docid=SE0000611591&lang=en
URFSTG00323-Troubleshooting Guide to UMTS RRC Connection Setup and Voice Access

Problem:
http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailManuscript&w
eb_doc_id=SE0000505928&doc_type=4-00013050
URFSTG00322-Troubleshooting Guide to UMTS Voice Call Drops:

http://support.huawei.com/support/pages/kbcenter/view/product.do?actionFlag=detailManuscript&w
eb_doc_id=SE0000507463&doc_type=4-00013050
UMTS Signaling Storm Solution material package:

http://download.huawei.com/3msdownload/download.do?method=downLoad&f_id=UMTS2011032
30081&attachment_id=173874
UMTS RAN Product Specification:

http://3ms.huawei.com/mm/docMaintain/mmMaintain.do?method=showMMDetail&f_id=UMTS20
1009080081
----End
Issue 01 (2013-04-08)

108
OMStar
Maintenance SOP
3.5 Updating a Project Package from Rule Store

The RuleStore client provides a communication platform between the RuleStore server and
the OMStar.
The RuleStore client supports the following functions:
Updating project packages: With this function, user operations are reduced.
Reminding users of OMStar information: With this function, users can learn the
information about the OMStar in time. Therefore, the working efficiency of users can be
improved.
Starting the RuleStore Client

To manually start the RuleStore client, start the OMStar V500R008, and choose Help > Rule
Update, as shown in follow.
To update a project package, do as follows;

If you want to know some particular function about RuleStore, you should refer to the
RuleStore help.
Updating a Project Package

The RuleStore client supports the function of using the latest project package on the RuleStore
website to replace the project package on the OMStar.
After users specify the project package to be updated, the RuleStore client queries the latest
project package from the RuleStore website based on the network system supported by the
project package, tool type, and local OMStar information. If the latest project package is
available on the RuleStore website, the RuleStore client downloads the project package to the
local OMStar to replace the original project package. If the latest project package is
unavailable, the original project package remains unchanged.
Step 1 Select the project package to be updated.
Issue 01 (2013-04-08)

109
OMStar
Maintenance SOP
Step 2 Click
to update the selected project package.
If the project package is updated successfully, a window shown as following:
If the project package fails to be updated, a window shown as following:
----End
Issue 01 (2013-04-08)

110
OMStar
Maintenance SOP
4 Problem Handling
Problem Handling
4.1 Principles
If tool problems encountered during maintenance SOP cannot be resolved, submit service
requests to iCare for trace and solution. For example, the NIC fails to collect data properly,
the OMStar fails to analyze data or export reports properly, or customer equipment or network
problems are marked as critical in reports generated during maintenance SOP.
If certain tool problems are resolved onsite, field engineers are also advised to submit iCare
service requests for trace and feedback purposes.
The address of iCare is http://iCare.huawei.com/ for both intranet users and internet users.
4.2 Creating an iCare Service Request

Check the following link for creating iCare SR and workflow:
http://icare.huawei.com/OA_HTML/operationGuide/index-EN.html
For detailed operation guide, please find the attached Detail operation guide on the
left-bottom website.
4.3 iCare Help

Contact methods of coordinators responsible for handling different iCare problems are as
follows:
Service problems: Contact iCare system administrators.
Send emails to iCareadmin@huawei.com.
For other problems, contact IT hotline engineers by using one of the following methods:
Visit the IT service platform at http://w3.huawei.com/it/. This method is

recommended.
Submit problems at http://w3.huawei.com/sm/ess.do.
Send emails to the IT hotline email address, i12345@notesmail.huawei.com or

ithotline@huawei.com.
Dial the hotline number, +86-0755-28560160 (Extension number: 0755-60160).
Issue 01 (2013-04-08)

111
OMStar
Maintenance SOP
5 FAQ
FAQ
5.1 FAQs Related to the NIC

5.1.1 How Do I Handle the NIC Startup Failure?
If the Server Proxy Setting of NIC is set to common mode, ensure that the FTP Server is
shut down on the PC before starting the NIC and that the default FTP port is not
occupied.
For other causes, send the log information to R&D engineers for troubleshooting.
5.1.2 How Do I Handle the Failure to Add NEs to the NIC?

1.
Check whether the user name and password are correct, that is, check whether the login
by using the LMT succeeds.
2.
If the PC is configured with multiple network adapters and the NIC earlier than
V100R006C00SPC300 is used, 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 without restarting the
Internet Explorer.)
3.
Check Mediation layer manager to ensure that mediation matching the version of the
NE whose data needs to be collected has been installed.
4.
For other causes, send the log information to R&D engineers for troubleshooting.
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
1.
This error is a type of NE adding failures. Check whether the mediation matching the NE
version is installed.
2.
If the mediation matching the NE version is installed, the possible cause is that the
mediation of English version has been installed on the NIC of Chinese version.
Issue 01 (2013-04-08)

112
OMStar
Maintenance SOP
5 FAQ
5.1.4 Data Collection Failure Scenarios (Configuration Data,

Traffic Statistics Data, and MML Data)
3.
If the NIC fails to be connected 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.
4.
If the PC is configured with multiple network adapters and the NIC earlier than
V100R006C00SPC300 is used, 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 without restarting the
Internet Explorer.)
5.
Check whether the user has the operation right.

Collect data as user admin; otherwise, the collection may fail due to lack of rights for
certain collection items.
Check whether the user is authorized to operate MML commands. If the user is not
authorized to operate MML commands, collecting configuration data and MML data
may fail.
Check whether the user is authorized to back up configuration files. If the user is not
authorized to back up configuration files, collecting configuration files may fail.
Check whether the user is authorized to run the BIN command. If the user is not
authorized to run the BIN command, collecting traffic statistics data may fail
5.1.5 Why Does It Take Time for the NIC to Collect Inspection
Data?
6.
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).
7.
At present, the NIC reports the progress according to collection items. The execution
sequence of the collection items may change each time 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%.
8.
The execution sequence of the collection items may change each time a task is created.
When the items with a small amount of data are collected in priority, it seems that the
collection becomes faster.
9.
If the collection progress does not change for a long time, send the log information to
R&D engineers to check whether the NIC still collects data
5.1.6 How to Add NEs More Efficiently by Using the Batch Import
Function?
10. Choose NE Management > NE Information Maintenance, and click Batch Manage.
Issue 01 (2013-04-08)

113
OMStar
Maintenance SOP
5 FAQ
11. In the Batch Manage window, click Download Template to save the template to the
local PC.
12. Open the batch import template (.xls file) 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.
Issue 01 (2013-04-08)

114
OMStar
Maintenance SOP
5 FAQ
13. In the Batch Manage window, click Browse, select the .xml file, and click Import.
14. After the .xml file is imported, click OK.
Issue 01 (2013-04-08)

115
OMStar
Maintenance SOP
5 FAQ
The batch NE import and export functions are deleted from NIC V100R006C00SPC700 and
later versions. You can use the Syn From M2000 function to import the NE information from
the M2000. For details, see NIC V100R006C00 User Guide.
5.1.7 What is the Maximum Number of NEs Whose Data Is

Collected Concurrently on the NIC?
NIC V100R006C00T and earlier versions:
15. The maximum number of multiple collection tasks running concurrently on the NIC is
10.
16. The maximum number of NEs whose data is collected concurrently in a single collection
task is 5.
17. The maximum number of NEs (including BSCs/RNCs and BTSs/NodeBs) created in a
single collection task is 100.
Versions later than the NIC V100R006C00T:
1.
The maximum number of multiple collection tasks concurrently running on the NIC is 5.
2.
The maximum number of NEs whose data is collected concurrently in a single collection
task is 10.
3.
The maximum number of NEs (including BSCs/RNCs and BTSs/NodeBs) created in a

single collection task is 1000s.
To sum up, the maximum number of NEs whose data is collected concurrently on the NIC is
50.
NOTE
Currently, the data for maintenance SOP is collected only from BSCs or RNCs.
5.1.8 How Do I Handle the Partial Data Collection Failure?

If a collection task has been completed, but data of some NEs or some data is not successfully
collected, you can use the supplementary collection function.
In the Task Manager GUI, select the task and choose to make supplementary collection.
The result collected by supplementary collection should save in another folders, and create an
new analysis task by OMStar.
NOTE
This feature is available NIC V1R6C00SPC100T and later versions. NIC V1R6C00T and earlier
versions do not support this feature.
5.1.9 How Do I Handle the Failure to Create NEs with M2000

Agent Mode and Multiple IP Addresses?
1.
Please update the version to iManagerM2000V200R010C00CP24002 when the current

version is M2000 iManagerM2000V200R010C00SPC240.
2.
See the following attachment when the current version is M2000

iManagerM2000V200R010C00SPC260.
Issue 01 (2013-04-08)

116
OMStar
Maintenance SOP
5 FAQ
Workaround Guide
to the Problem That the NIC Tool Fails to Connect to NodeB Using the M2000 Agent.doc
5.1.10 How Do I Obtain Co-site Information Manually on the

M2000 When the NIC Cannot Collect the Information
Automatically?
For an M2000 version earlier than V200R012, NIC is unable to automatically collect the
co-site information. In this case, you have to manually obtain the information on the M2000.
The procedure is as follows:
1.
Log in to the M2000, and choose Report > RAN Report Wizard from the menu bar.
2.
In the displayed window, check MBTS, and click Next.
3.
In the Select RAN report types page, check MBTS(GU)NE Report, MBTS(GL)NE
Report, MBTS(UL)NE Report, and MBTS(GUL)NE Report, and click Finish.
Issue 01 (2013-04-08)

117
OMStar
Maintenance SOP
4.
Issue 01 (2013-04-08)
5 FAQ
Click Save as follows:

118
OMStar
Maintenance SOP
6 Help Information
Help Information
Contact person: Chen Ping

Staff ID: 00151537
Email: helen.chenping@huawei.com
Your valuable advice is always 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.
How to obtain NIC stand-alone version logs?
Click Logs Collecting in the NIC Console dialog box, as shown in the following figure.
How to obtain NIC in Co-Deployment Mode logs?

Login in M2000 by the FTP tool to obtain the following files:
/opt/oss/server/var/logs/omstar_nic.log
Issue 01 (2013-04-08)

119
OMStar
Maintenance SOP
6 Help Information
/opt/oss/server/var/logs/iMAP.nicservice_agent.trace
/opt/oss/server/var/logs/ds/dsXXXX
How to obtain OMStar V500R008 logs?

1.
Huawei\GENEX\OMStarV500R008\client\tracefile
2.
Huawei\GENEX\OMStarV500R008\client\plugins\com.huawei.galaxy.framework.isdk.impl
\startprocess\Script\iSDKFramwork\UNP\log
3.
Huawei\GENEX\OMStarV500R008\client\plugins\com.huawei.galaxy.framework.isdk.impl
\startprocess\tracefile
Issue 01 (2013-04-08)

120

Operation Guide To The OMStar V500R008 For Maintenance SOP

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Operation Guide To The OMStar V500R008 For Maintenance SOP

Cargado por

Copyright:

Formatos disponibles

Operation Guide to the OMStar

V500R008 for Maintenance SOP

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential