omstar v500r010 data collection guide 03-en

Huawei Technologies Co., Ltd.

Product Name Security Level

OMStar INTERNAL

Product Version Pages

V500R010 Total 45 pages

OMStar V500R010 Data Collection Guide

For Internal Use Only

Prepared By Han Haowei (employee ID: 00151425) Date 2014-09-15

Reviewed By Liu Junwei (employee ID: 00148069) Date 2014-09-15

Approved By Wang Qiang (employee ID: 00108055) Date 2014-10-20

Huawei Technologies Co., Ltd.

All rights reserved

OMStar V500R010 Data Collection Guide INTERNAL

2014-10-20 Huawei Proprietary and Confidential Copyright Huawei

Technologies Co., Ltd. i

Change History

Date Version Description Author

2014-10-20 03 Added right query for LTE SIG Guo Hu(employee ID:

00131088)

2014-09-15 02 Added the chapter "Internal CHR Data Collection"

and "eNodeb MML Packet Collection".

Han Haowei (employee

ID: 00151425)

2014-08-15 01 First verison Han Haowei (employee

ID: 00151425)



Technologies Co., Ltd. ii

Contents

1 OMStar Data Source Overview .................................................................................................. 1

2 General Principles for Data Collection..................................................................................... 2

2.1 NIC Data Collection ..........................................................................................................................................................2

2.2 Manual Data Collection ....................................................................................................................................................2

2.2.1 BSC/RNC Configuration Data Collect ion ..........................................................................................................2

2.2.2 BSC/RNC Traffic Statistics Collection................................................................................................................5

2.2.3 BSC/RNC Alarm Log Collection .........................................................................................................................7

2.2.4 BSC/RNC MML Packet Collect ion .....................................................................................................................8

2.2.5 BSC/RNC CHR/MR Data Collect ion ..................................................................................................................8

2.2.6 BSC/RNC Operat ion Log Collection .................................................................................................................11

2.2.7 NodeB Configuration Data Collection...............................................................................................................12

2.2.8 NodeB Traffic Statistics Collection (.csv).........................................................................................................13

2.2.9 NodeB Traffic Statistics Collection (.mrf) ........................................................................................................15

2.2.10 NodeB Alarm Log Collect ion ...........................................................................................................................18

2.2.11 NodeB MML Command Collection .................................................................................................................22

2.2.12 NodeB License Collection .................................................................................................................................24

2.2.13 Co-Site Information Collection.........................................................................................................................25

2.2.14 eNodeB Configuration Data Collect ion ..........................................................................................................26

I. Collecting eNodeB Configurat ion Data Using the M2000 26 II. Collecting eNodeB Configuration Data Using the NIC (Co-Deployed with the M2000) 30

2.2.15 eNodeB Traffic Statistics Collection (.mrf) ....................................................................................................35

I. Collecting eNodeB Traffic Statistics Using the M2000 35 II. Collecting eNodeB Traffic Statistics Using the NIC (Co-Deployed with the M2000) 36

2.2.16 Internal CHR Data Collection ...........................................................................................................................39

2.2.17 eNodeB MML Packet Collect ion .....................................................................................................................39

2.2.18 LTE SIG Data Collection Based on the WebNIC ..........................................................................................42

2.2.19 Signaling Tracing ................................................................................................................................................42



Technologies Co., Ltd. 1

1 OMStar Data Source Overview

The OMStar V500R010 provides comprehensive analysis of NE configuration, traffic statistics, alarm

logs, and MML packets. The collected data must meet the interface specifications of the OMStar. The following data lists the data types supported by the OMStar.

NE Type Data Data Source

Controller (BSC/RNC) Configuration data Controller BAM

Traffic statistics Controller BAM

Alarm logs Controller BAM

MML packets WEB LMT

CHR Controller BAM

MR Controller BAM

NodeB Configuration data M2000

Traffic statistics M2000

Alarm logs M2000

MML packets M2000

License M2000

eNodeB Configuration data M2000

Traffic statistics M2000

Alarm logs M2000

CHR M2000

MML packets M2000




2 General Principles for Data Collection

Based on the onsite tool deployment situation, you can use the NIC tool to automatically or manually

collect data. You are advised to use the NIC tool for data collection. If the NIC tool is not available, you can manually collect the data.

2.1 NIC Data Collection

For details about how to use NIC for data collection, please refer to Data Collection by using the NIC.docx in OMStar V500R010 Data Collection Guide Attachments.

2.2 Manual Data Collection

This section mainly describes how to manually collect BSC/RNC data and NodeB data required by the

OMStar. For the LTE network mode, as the eNodeB data size is large, you are advised to use NIC for batch data collection.

2.2.1 BSC/RNC Configuration Data Collection

The BSC/RNC configuration data result files used by the OMStar are MML configuration scripts (*.txt), which are exported from the BSC/RNC using MML commands.

Step 1 Log in to the WEB LMT and click MML.




Step 2 Enter and execute the EXP CFGMML command. In the command output, the save directory for configuration data is displayed.




Step 3 Start the File Manager tool to download configuration files.

In the File Manager window, find the configuration data in the directory displayed in the EXP CFGMML command output and click Download to download the files to the local PC.

----End




2.2.2 BSC/RNC Traffic Statistics Collection

In the File Manager window, BSC and RNC traffic statistics are stored in the

\bam\common\MeasResult directory. The traffic statistics can be directly downloaded. You need to download only the files whose names contain EMS-NORMAL.

For Neighboring GSM Cell Analys is you need to start the Measurement of Neighboring GSM Cell Performance by M2000. The operate step as below.

(1) Login M2000 client, and select Performance > Measurement Management.




(2) Select the Measurement of Neighboring GSM Cell Performance and BSC that you want to collect, and select all counters in the module of Setting->60 minutes on the right of window. Click

button Apply to start the performance measurement. The performance files on the next period will contain the counters of Measurement of Neighboring GSM Cell Performance.




2.2.3 BSC/RNC Alarm Log Collection

Step 1 Use the WEB LMT to execute the COL LOG command. Select HISTORY_ALARM for Log File Type.

Step 2 Use the File Manager tool to download alarm logs. The file directory is \bam\version_b\ftp\COLLOGINFO\ALM-LOG. Click Download to download the files.

----End




2.2.4 BSC/RNC MML Packet Collection

Use the WEB LMT to execute the MML commands, such as DSP LICUSAGE. Store the command output information as a .txt file.

2.2.5 BSC/RNC CHR/MR Data Collection

Use the File Manager tool of the Web LMT to download CHR\MR files. The file directories are as follows: \bam\common\fam\famlogfmt\gchr\. Click Download to download the files to a local PC.

To use the GSM call drop in-depth analysis function of the OMStar, you are advised to enable the MR

and signaling messages to be contained in the CHR by running the SET GCSCHRCTRL command.




SET GCSCHRCTRL: CSRCDSW=ON,CSSIGINFO=ALLCSMRBFCLR=ON, CSCHRMR=ON

In this command, set CHR Signaling Output to ALL(Output All), Output MR Before Call Release

to ON(Output), and CHR MR Output to ON(Output).

After the CS CHR function is enabled in all the cells and for the specified subscribers under the BSC,

the CPU usage of the XPU board increases by about 5%, the detail information about SET

GCSCHRCTRL reference to MML Command Reference please.

UMTS PCHR data directory: \bam\common\fam\famlogfmt\pchr\

GSM/UMTS MR data directory: \bam\common\fam\mr




To use UMTS MR data for neighboring cell analysis, run the SET UMRCTRL and SET UMRSCOPE

commands to enable MR collection of neighboring cells. For details about the commands and the

impacts of the commands on NEs, see the related MML command reference.

In the SET UMRCTRL command, set MR Trace Traffic Type to TRAFFIC_AMR, MR Intra-freq

Measurement period to D12, and MR Report Configure S witch to a proper value according to the actual

situation.

SET UMRCTRL:

RTRAFFICTYPE=TRAFFIC_AMR-1&TRAFFIC_VP-1&TRAFFIC_BE-1&TRAFFIC_OTHER-

1, MRINTRAFREQPERIOD=D12,

MRRPRTCFGSWITCH=MR_PRD_INTRA_FREQ_MEAS_SWITCH_1-1&MR_EVT_INTRA_F

REQ_MEAS_SWITCH_2-1&MR_PRD_INTER_FREQ_MEAS_SWITCH_3-1&MR_EVT_INTE

R_FREQ_MEAS_SWITCH_4-1&MR_PRD_INTER_RAT_MEAS_SWITCH_5-1&MR_EVT_IN

TER_RAT_MEAS_SWITCH_6-1&MR_DL_BLER_MEAS_SWITCH_7-0&MR_UE_TX_POWER_

MEAS_SWITCH_8-0&MR_UL_SIR_MEAS_SWITCH_9-0&MR_LCS_MEAS_SWITCH_10-0&MR

_RACH_MEAS_SWITCH_11-0,

MRLCSMETHODSWITCH=LCS_AGPS_UEBASED_SWITCH_1-0&LCS_AGPS_STANDALONE_

SWITCH_2-0&LCS_CELLID_RTT_SWITCH_3-0, MRDLBLERPERIOD=D12, MRUETPPERIOD=D12, MRULSIRPERIOD=D12, MRLCSPERIOD=D12;

In the SET UMRSCOPE command, specify Scope Type to set the NE objects to be enabled.

For V9R12\V9R13\ V9R14

SET UMRSCOPE: SCOPETYPE=ByRack, SRN=0, SN=0, SSN=0, MRSCOPECTRL=ON;

For V9R15 and the later version




SET UMRSCOPE: SCOPETYPE=ByRnc, LOGICRNCID=1230, MRSCOPECTRL=ON;

The commands for turning on the switch for detecting missing inter-frequency and inter-RAT

neighboring cells are as follows:

R13: Run the SET UAUTONCELLDETECT command to set the GSM BSIC scope and BCCH ARFCN scope.

R13.1: Run the SET UAUTONCELLDETECT command to set the switch for detecting missing neighboring cells and parameters in the SON.

R14: Run the SET UAUTONCELLDETECT command to set the switch for detecting missing neighboring cells and parameters in the SON.

R15: Run the ADD UCELLAUTONCELLDETECT command to set the switch for detecting missing neighboring cells and related parameter groups, and run the ADD

UAUTOGSMNCELLGROUP command to set the BSIC scope and BCCH ARFCN scope.

R16: Run the ADD UCELLAUTONCELLDETECT command to set the switch for detecting missing neighboring cells and related parameter groups, and run the ADD

UAUTOGSMNCELLGROUP command to set the BSIC scope and BCCH ARFCN scope.

After the measurement report collecting function is enabled, load congestion is more likely to occur on

the Uu and Iub control plane and the number of signaling messages will increase by over 10%. The

detail information reference to MML Command Reference please.

2.2.6 BSC/RNC Operation Log Collection

Step 1 Use the WEB LMT to execute the COL LOG command. Select OPT_LOG for Log File Type.




Step 2 Use the File Manager tool to download alarm logs. The file directory is \bam\version_b\ftp\COLLOGINFO\OPT-LOG. Click Download to download the files to a local PC.

----End

2.2.7 NodeB Configuration Data Collection

Step 1 On the M2000 topology, choose Maintenance > Backup Management > NE Backup.




Step 2 In the NE tree in the left pane, select a NodeB and click Backup to back up the configuration data of the NodeB. The backup process is displayed in the Immediate Task list in the lower part of the window.

After the backup is complete, the FTP directory storing the NodeB configuration data is displayed in the

NE Backup List. You can obtain the configuration files from this directory using the FTP. The file name is NodeBCfg.xml.

----End

2.2.8 NodeB Traffic Statistics Collection (.csv)

Step 1 On the M2000 topology, choose Maintenance > Task Management.




Choose Task Management > File Interface > Performance Data Export.

Step 2 On the Task Management tab page, choose File Interface > Performance Data Export.

Step 3 Double-click Performance Data. In the displayed attribute dialog box, check the enabled NodeB traffic statistics measurement tasks on the M2000 and the FTP directories that store the NodeB traffic

statistics. Navigate to the corresponding FTP directory to obtain the traffic statistics files of the NodeB in .csv format.




For traffic statistics files in .csv format, the OMStar supports only the granularity period of 15 minutes, as shown in the following figure:

----End

2.2.9 NodeB Traffic Statistics Collection (.mrf)

The NodeB traffic statistics files in .mrf format are stored in a fixed directory on the M2000, /export/home/sysm/ftproot/nbi. You can directly access this directory on the M2000 using the FTP.

In this directory, the traffic statistics files are stored by NodeB. The traffic statistics of each NodeB is saved in one folder named after the NodeB FDN.




In the folder of each NodeB, the raw and compressed NodeB traffic statistics file in .mrf format is stored in the gz folder, which can be directly obtained.




On the M2000 main topology, right-click a selected NodeB and choose Properties from the shortcut menu to query the FDN of the NodeB.




2.2.10 NodeB Alarm Log Collection

Step 1 Choose Topology > Main Topology from the M2000 main menu.




Step 2 In the NE tree in the left pane, right-click a selected NodeB and choose Query Alarm/Event > Alarm Logs from the shortcut menu.




Step 3 Right-click in the Query Alarm Logs result page and choose Save > Save All Records from the shortcut menu. In the displayed dialog box, select the .csv file format.

----End




2.2.11 NodeB MML Command Collection

Step 1 On the main topology of the M2000, right-click any NodeB and choose MML Command from the shortcut menu.




Step 2 In the MML Command window, select one or more NodeBs for MML command issuing, and the MML command execution result is displayed in the information display area.

Step 3 Select and right-click the result content and choose Save As from the shortcut menu to save the result as a default .txt file.

----End




2.2.12 NodeB License Collection

Step 1 On the M2000 main topology, choose License > NE license Management > NodeB.

Step 2 On the NodeB License Management tab page, select all records in the Shared/BASIC area. Right-click the selected records and choose Export from the shortcut menu.




In the displayed dialog box, click Export and the files are exported as .csv files by default.

----End

2.2.13 Co-Site Information Collection

Step 1 On the M2000 main topology, choose Configuration > Report > MBTS Relationship Report.




In the displayed dialog box, select MBTS(GL) NE Report, MBTS(GU) NE Report, MBTS(GUL) NE Report, and MBTS(UL) NE Report. Then, click OK.

Step 2 Click Save to save the displayed MBTS relationship reports in .xlsx format.

----End

2.2.14 eNodeB Configuration Data Collection

I. Collecting eNodeB Configuration Data Using the M2000

Step 1 Log in to the M2000 client and choose Maintenance > Backup Management > NE Backup.




Step 2 In the NE Backup window shown in the following figure, select eNodeB from the NE type drop-down list. After all NEs of the eNodeB type are displayed in the NE navigation tree in the left pane, select the check box of NE to select all NEs and click Backup.

Step 3 In the Confirm dialog box shown in the following figure, click Yes to back up data.




It takes an extended period if a large number of NEs are selected for backup. In addition, the backup is irreversible.

The backup progress is displayed in the Progress column, as shown in the following figure.

When the backup progress for all NEs becomes 100% and Succeeded is displayed in the Information

column, the backup is complete. The NEs whose data has been successfully backed up will be displayed

in the NE Backup List in the right pane. After the backup, all XML configuration files of the NEs are saved on the M2000 server and the save path is displayed in the Path column.




Step 4 In the NE Backup List, select all NEs and click Download to OMC Client at the right corner of the window to download the configuration files from the M2000 server to your local PC.

Step 5 In the Select Folder dialog box shown in the following figure, specify Directory and click Save.

The download progress is displayed in the Progress column. When Succeeded is displayed in the Status column, the configuration files are successfully downloaded to your local PC.




The downloaded configuration files are saved in the structure shown in the following figure.

The first-level node is the name of the folder for saving the configuration files. The second-level node is

the name of a base station displayed on the M2000. The third-level node is the backup date. The backup XML configuration files are all named M2000.XML.

----End

II. Collecting eNodeB Configuration Data Using the NIC (Co-Deployed with the M2000)

Step 1 Log in to the NIC.

1. Enter the IP address of the NIC server in the address bar of the Internet Explorer.

2. If the following page is displayed, click Continue to this website (not recommended).




3. Enter the login window.

4. Enter the user name and password of the M2000 and the verification code. Then, click Login.

Step 2 Create a data collection task.

1. On the Network Information Collection page, click the drop-down arrow of Create Task and choose Based on Customize Collection Item from the drop-down list to collect data by collection

item.




2. Enter a task name in Task Name and set Product Type to LTE. Then, click Next.




3. Select NEs whose data needs to be collected and click Next.




4. Select collection items.

To collect configuration data, choose DBS3900LTE > Configuration > eNodeB Configuration

in the navigation tree in the left pane to select collection items. In this scenario, data in

configuration files in both XML and DBS formats can be collected. Then, click Next.

5. Click Finish to collect data.

Step 3 Re-collect data.

If certain data is not collected after the collection task is complete, click Re-collect shown in the following f igure to manually re-collect data.

Step 4 Download the collected data.




Click the Result Information tab and click Download in the Task Result column to download the collected data to your local PC, as shown in the following figure.

----End

2.2.15 eNodeB Traffic Statistics Collection (.mrf)

I. Collecting eNodeB Traffic Statistics Using the M2000

Log in to /export/home/sysm/ftproot/nbi/ of the M2000 server using FTP and check whether traffic

statistics exist in the NE folder. If the traffic statistics exist, copy the folder of the corresponding NE to your local PC.

For example, NE270 in /export/home/sysm/ftproot/nbi/NE270/gz is the full distinguished name (FDN) of the NE.

Example of a standard name of a traffic statistics file :

A20120228.0900+0800-1000+0800_EMS-NORMAL.mrf.gz




II. Collecting eNodeB Traffic Statistics Using the NIC (Co-Deployed with the M2000)

Step 1 Customize collection items on the NIC.

Step 2 Create a data collection task.




Step 3 Set the time range for data collection.

Step 4 Select NEs whose data needs to be collected.

Step 5 Select collection items.

To collect traffic statistics and configuration data, select Obtain Traffic Statistics of the M2000 and eNodeB Configuration XML Only.




Step 6 After the collection task is complete, save and download the data to your local PC.




----End

2.2.16 Internal CHR Data Collection

Step 1 Log in to the M2000, enter the MML interface, and choose the sites whose internal CHR data needs to be collected.

Step 2 Run the following command to collect internal CHR data:

ULD

FILE:FUNCTYPE=ENODEB,SRCF=CHRLOG,DSTF="XXXX",MODE=IPV4,IP="172.16.0.194",USR="root",PWD="***",CF=COMPRESSED,FLOWCTRL=N;

Step 3 Log in to the corresponding directory using FTP to copy required data.

----End

2.2.17 eNodeB MML Packet Collection

The eNodeB MML packets can be collected using NIC or manually collected. A default OMStar_Check

scenario is provided if you use NIC to collect MML packets. For details, see section 2.1 "NIC Data

Collection."

To manually collect MML packets, choose Maintenance > MML Command on the U2000 and click

the eNodeB whose MML packets need to be collected. Then, deliver the corresponding MML command

and right-click the packet result on the U2000 to save it as a .txt file.




If NIC data package is directly imported, the OMStar determines the homing eNodeB based on the NE

folder of the packets when importing MML packets.

If MML packets are manually imported, the information in yellow following three plus signs (+) is the

information used by the OMStar to identify the packet homing eNodeB. By default, the information

indicates the name of the eNodeB. Otherwise, the OMStar cannot identify the MML packets and

therefore fails to import them.

+++ eNodeB11_JJFA 2014-07-21 14:44:18

O&M #9533

%%DSP LOCALETHPORT: CLEAR=NO;%%

RETCODE = 0 Operation succeeded.

Display Local Ethernet Port Status

----------------------------------

Config Status = Enable

Port Status = Up

Number of RX Packets(packet) = 1634600

Number of RX Discarded Packets(packet) = 0

Number of TX Packets(packet) = 5269

Number of TX Discarded Packets(packet) = 0

(Number of results = 1)

--- END

The eNodeB information contained in MML packets needs to be independently set. If the MML packets

fail to be imported because they do not contain eNodeB information, do as follows to set the eNodeB

information before MML packet collection:

For eRAN3.0 and earlier versions:

Run the SET OFFICENAME command with System Name set to the eNodeB name.

The following figure shows detailed information about this command.




For eRAN6.0 and later versions:

Run the SET NE command with Network Element Name set to the eNodeB name. Before running this

command, run the LST NE command to check whether Network Element Name is set to the eNodeB

name. If yes, skip this step.

The following figure shows detailed information about this command.

After the preceding settings, the eNodeB name is displayed after three plus signs (+) in collected MML

packets by default. In this case, the OMStar can import MML packets in batches.




2.2.18 LTE SIG Data Collection Based on the WebNIC

For details about the LTE SIG Data Collection Based on the WebNIC, please refer to LTE SIG Data Collection Based on the WebNIC.docx in OMStar V500R010 Data Collection Guide Attachments.

2.2.19 Signaling Tracing

For details about the Signaling Tracing, please refer to LTE Signaling Tracing.docx in OMStar V500R010 Data Collection Guide Attachments.

omstar v500r010 data collection guide 03-en

Documents

nic data collection

manual data collection

bscrnc configuration

bscrnc alarm log collection

bscrnc chrmr data

enodeb mml packet collection

omstar data source overview

huawei proprietary