Operation Guide To The FMA V1.51

Document Code Product Name FMA
Intended Audience Internal Product Version V3.42
Prepared by GU Delivery Department Document Version V1.51
Operation Guide to the FMA
Prepared by GU Delivery Department Date 2011-8-27

Reviewed by Date
Reviewed by Date
Approved by Date
Operation Guide to the FMA INTERNAL
Change History
Date Version Description Author
2010-12-01 V1.0 Completed the first draft. Xu Zhijie (Employee ID:

43183)
2011-12-30 V1.1 1. Add operation guide of Tang xiaocan KF32623
MML&License Scan Dang guangqiang KF31244
2. Add operation guide of filter He binbin KF33707
and extension of performance
3. Add operation guide of
dashboard function
2011-2-15 V1.2 1. Add operation guide of Xu Zhijie (Employee ID:
creating project 43183)
2. Add operation guide of Data
Collection function
2011-4-5 V1.3 1. Based on the new function of Xu Zhijie (Employee ID:
FMA V3.2, add the operation 43183)
guide of CHR analysis and
modify the guide of Data
Collection
2. Modify the guide of operation
log analysis
2011-5-1 V1.4 1. Enhanced MML Scan Xu Zhijie (Employee ID:
Function 43183)
2. CHR Filter based on condition
2011-5-16 V1.41 1. Introduce to License Xu Zhijie (Employee ID:
2. MML Scripts Check 43183)
2011-6-30 V1.5 1. Enhance the function of Xu Zhijie (Employee ID:

performance 43183)
2. Add CPU usage of SPU and
Trend Statistic for
CHR&PCHR
3. Add NodeB XML to MML
2011-8-27 V1.51 1. The performance optimization Xu Zhijie (Employee ID:
for CHR Analysis 43183)
2. Add comparative function of
TMF message and extract
content of L2_DATA_FWD
and drawing
2019-6-20 Huawei Confidential Page 2 of 144

Contents
1 Overview.........................................................................................................................................7
2 Functions of the FMA Version....................................................................................................8
3 Application Scope and Download...........................................................................................10
4 License...........................................................................................................................................11
4.1 Introduction......................................................................................................................................................11
4.2 Get ESN...........................................................................................................................................................11
4.3 Update License................................................................................................................................................12
5 Project............................................................................................................................................12
5.1 Introduction......................................................................................................................................................12
5.2 Operation Guide...............................................................................................................................................13
5.2.1 Create Project.........................................................................................................................................13
5.2.2 Open Project...........................................................................................................................................14
5.2.3 Modify/Delete Project............................................................................................................................15
5.2.4 Close Project...........................................................................................................................................16
6 Alarm Analysis............................................................................................................................17
6.1 Introduction......................................................................................................................................................17
6.2 Operation Guide...............................................................................................................................................17
6.2.1 Browsing Alarms....................................................................................................................................17
6.2.2 Associating Alarms with the MML Script..............................................................................................18
6.2.3 Filtering Alarms......................................................................................................................................19
6.2.4 Highlighting Alarms...............................................................................................................................20
6.2.5 Saving Alarms.........................................................................................................................................21
6.2.6 Sorting Alarms by Type..........................................................................................................................22
6.2.7 Analyzing the Trend of Alarms...............................................................................................................23
6.2.8 Analyzing the Frequency Trend of Alarms.............................................................................................27
7 Performance Measurement Browsing.....................................................................................30

7.1 Introduction......................................................................................................................................................30
7.2 Operation Guide...............................................................................................................................................30
7.2.1 Reading Performance Measurement.......................................................................................................30
7.2.2 Browsing Performance Quickly.............................................................................................................32

7.2.3 Query Performance Measurement..........................................................................................................34

7.2.4 Saving Performance Measurement.........................................................................................................36
7.2.5 Associating the Performance Measurement with the MML Script........................................................36
7.2.6 Setting User-Defined Counters...............................................................................................................37
7.2.7 Browsing Common KPIs........................................................................................................................38
7.2.8 Analyzing Top N Cells............................................................................................................................39
7.2.9 Analyzing Voice Mode...........................................................................................................................41
7.2.10 Analyzing with General(Cluster)..........................................................................................................42
7.2.11 Filter......................................................................................................................................................47
7.2.12 Search Counter.....................................................................................................................................49
7.2.13 Query the detailed information of counter...........................................................................................50
7.2.14 CPU Evaluation....................................................................................................................................50
7.2.15 Abnormal Counter Check.....................................................................................................................52
8 Dashboard.....................................................................................................................................53
8.1 Introduction......................................................................................................................................................53
8.2 Operation Guide...............................................................................................................................................53
9 Performance Measurement Comparison................................................................................57

9.1 Introduction......................................................................................................................................................57
9.2 Operation Guide...............................................................................................................................................57
9.2.1 Reading Performance Measurement.......................................................................................................57
9.2.2 Comparing Performance Measurement..................................................................................................59
9.2.3 Search Counter.......................................................................................................................................59
9.2.4 Query the detailed information of counter.............................................................................................60
10 Real-Time UKPI Monitoring...................................................................................................62

10.1 Introduction....................................................................................................................................................62
10.2 Operation Guide.............................................................................................................................................62
10.2.1 Browsing the UKPI Offline..................................................................................................................62
10.2.2 Displaying the Graphic Result..............................................................................................................64
10.2.3 Defining Cluster Cells..........................................................................................................................67
10.2.4 Setting User-Defined Counters.............................................................................................................69
10.2.5 Monitoring KPIs Online.......................................................................................................................70
11 Fault Diagnosis..........................................................................................................................73
11.1 Introduction....................................................................................................................................................73
11.2 Operation Guide.............................................................................................................................................73
11.2.1 Displaying the Panel.............................................................................................................................73
11.2.2 Extracting the Configuration Script......................................................................................................75
11.2.3 Obtaining the Associated Information on Cells, Links, and NodeBs...................................................77
11.2.4 Obtaining Statistics...............................................................................................................................79
11.2.5 Obtaining NetGroup Cells....................................................................................................................80
11.2.6 Obtaining Scripts of Blocked or Unblocked Cells...............................................................................80

11.2.7 Obtaining Information of Neighboring Cell.........................................................................................81

11.2.8 Obtaining Swap NodeB Commands for 1+1 RNC Backup..................................................................82
11.2.9 MML Check..........................................................................................................................................83
11.2.10 Diagnosing Faults...............................................................................................................................85
11.3 Fault Diagnosis Results..................................................................................................................................89
11.3.1 IU PERF List........................................................................................................................................89
11.3.2 Fault Cell Rate by INT Port(PERF)......................................................................................................89
11.3.3 INT PERF List......................................................................................................................................90
11.3.4 IUB INT Brd Alarm Check...................................................................................................................91
11.3.5 Config Info of IUB Brd Port.................................................................................................................91
11.3.6 Fault Path Alarm Check........................................................................................................................92
11.3.7 IUB SCTP/SAAL Alarm Check...........................................................................................................94
11.3.8 Fault Cell Alarm Check........................................................................................................................94
11.3.9 Port Alarm Check.................................................................................................................................95
11.3.10 SPU Brd Alarm Check........................................................................................................................95
11.3.11 Config Info of SPU Subsystem...........................................................................................................96
11.3.12 IUCS Current Alarm Check................................................................................................................97
11.3.13 IUCS all Alarm Check........................................................................................................................97
11.3.14 IUPS Current Alarm Check................................................................................................................98
11.3.15 IUPS all Alarm Check........................................................................................................................98
11.3.16 DSP UKPI List....................................................................................................................................99
11.3.17 IU UKPI List.....................................................................................................................................100
11.3.18 Fault Cell Rate by INT Port(UKPI)..................................................................................................100
11.3.19 INT UKPI Display............................................................................................................................101
11.3.20 Fault Cell Rate by SPU(PERF).........................................................................................................101
11.3.21 Fault Cell Rate by SPU(UKPI).........................................................................................................102
11.3.22 SPU UKPI Display...........................................................................................................................102
11.3.23 TOPN SR(UKPI)..............................................................................................................................103
11.3.24 TOPN SR(PERF)..............................................................................................................................103
12 Online Analysis.......................................................................................................................105
12.1 Introduction..................................................................................................................................................105
12.2 Operation Guide...........................................................................................................................................105
13 Operation Log Analysis.........................................................................................................109

13.1 Introduction..................................................................................................................................................109
13.2 Operation Guide...........................................................................................................................................109
14 Comparison Between MML Scripts.....................................................................................111

14.1 Introduction..................................................................................................................................................111
14.2 Operation Guide...........................................................................................................................................111
14.2.1 Comparing Parameters........................................................................................................................111
14.2.2 Comparing Commands.......................................................................................................................115

15 MML&License Scan................................................................................................................116
15.1 Introduction..................................................................................................................................................116
15.2 MML Scan Operation Guide........................................................................................................................116
15.2.1 Feature Definition...............................................................................................................................116
15.2.2 Operation Guide..................................................................................................................................117
15.3 License Scan Operation Guide.....................................................................................................................118
15.4 MML and License Feature Compare Operation Guide................................................................................119
16 CHR&PCHR Analysis............................................................................................................120
16.1 Introduction..................................................................................................................................................120
16.2 Operation Guide...........................................................................................................................................121
16.2.1 Adapter................................................................................................................................................121
16.2.2 CHR&PCHR Browse.........................................................................................................................121
16.2.3 Filter....................................................................................................................................................123
16.2.4 Classification of Fault.........................................................................................................................126
16.2.5 Statistic of Point Code........................................................................................................................128
16.2.6 Statistic of Parameter..........................................................................................................................131
16.2.7 SPU Error Code..................................................................................................................................133
16.2.8 Statistic of CPU Usage.......................................................................................................................135
16.2.9 Trend Statistic.....................................................................................................................................136
16.2.10 Filter,Statistic of Para and Trend in non-Project..............................................................................139
17 NodeB XML2MML..................................................................................................................142
18 Contact Information.................................................................................................................143

1 Overview
To improve the efficiency of UMTS fault location, the GU Delivery Department developed
the Fault Manager Assistant (FMA) for fast fault location and troubleshooting.
Currently, the FMA analyzes faults based on the following data sources:
 Configuration script of the RNC
Run the EXP CFGMML or EXP INNERCFGMML command to obtain the
configuration script.
 Original alarm file of the RNC
This is a text file or CSV file. On the BSC6900 V9R12, run the COL LOG:LOGTYPE
= HISTORY_ALARM -1; or EXP ALMLOG: FILETYPE=csv; command to obtain
the alarm log; or export the alarm information as CSV file in the alarm plane.
 UKPI file of the RNC
Run the EXP UKPI or EXP KPI command to export the UKPI file. The UKPI file
records the performance measurement on some devices in the last five minutes.
 Original performance measurement of the RNC
It indicates the normal compressed file used by the iManager M2000 or by the NASTAR.
 Operation log of the RNC
On the BSC6900 V9R12, run the COL LOG: LOGTYPE=OPT_LOG-1; command to
export the log, or download the bak operation log by FTP tool, or run the EXP LOG
command to get TXT or CSV file.

2 Functions of the FMA Version
Version: V3.1
No. Type Function
1 Performance The FMA can be used to parse and compare performance

measurement measurement, view key performance indicators (KPIs), and
analyze top N cells.
Provide the filter of performance to check the health of network.
Search the counter and display the detailed information of
counter.
Provide the voice mode.
Provide the KPI of cluster cell.
Provde the download the performance files online and then pop-
up the compare window
Support V210 and V211 version of RNC
2 Alarm The FMA can be used to parse alarms, associate alarms with the
MML script, and analyze the trend of some alarms.
Provide the MBSC V911 and V913 version
Provide the fault alarm to import and parse
Provide the CSV alarm file to import and parse
Analyze the trend of fault alarm
Analyze the trend of frequency of alarm
Support V210 and V211 version of RNC
3 UKPI The FMA supports real-time KPI monitoring to guarantee
satisfactory KPIs in hot spot cells or during holidays and
vacations.

FMA Operation Guide INTERNAL
4 Fault diagnosis The FMA can export the fast diagnosis result based on the
configuration script, alarms, UKPI file, and performance
measurement of the RNC.
Provide the V911 version for diagnosis
Set the threshold by hand and save the diagnosis report as htm
file
Add new four rules for diagnosis
Support the V913 version for diagnosis
Support the V211 version for diagnosis
5 Operation log Support the parsing the normal operation log and bak log and
display
6 Comparison of The FMA supports fast comparison between configuration
MML scripts scripts of different RNCs, discovering the differences between
the parameters in different scripts.
7 Feature Provide the feature extraction of MML scripts
extraction of Support to parse the RNC License file and compare the License
MML scripts file with MML scripts
8 Project Use the project to create and import the data for FMA tool
9 CHR&PCHR 1. Provide the parsing the CHR or PCHR files
Analysis 2. Support the fault classification of CHR or PCHR log
3. Support the statistic of error code of CHR log
4. Support the statistic of para of CHR or PCHR log
5.Support the filter function by condition or column or current
value
6.Support the result to get relate UE log for CHR and PCHR log

3 Application Scope and Download
The FMA is applicable to the following.

 RNC V210 (excluding fault diagnosis)
 RNC V211
 MBSC V911
 MBSC V912
 MBSC V913
The FMA tools can be downloaded from support network of HUAWEI and link is:

4 License
4.1 Introduction
For the current version of FMA, the License Code is needed to restrict user. If the License
Code is not applied, the FMA can be used for about 15 days. If the License Code is invalid,
the FMA tool can’t be used.
The user can get ESN Code, which is the serial number of hard-disk. The ESN Code can be
empty, and this is caused by the FMA tool can’t get ESN Code.
For the user in R&D area, the user can login the JIRA system to apply the License Code based
on the ESN Code. The WEB address of JIRA system is as follows:
 http://10.141.71.212:8080/secure/CreateIssue!default.jspa
If the ESN Code is empty, during applying, the user needs to input NO character in ESN. The
max valid day is 180.
For the user not in R&D, the user can send the ESN Code to the interface engineer(Liu
Zhijian 51085 or Xuzhijie 43183) of issue, and let the interface engineer to help.
4.2 Get ESN

Click License->How to get License:
And ESN Code is:
The ESN Code can be empty.

4.3 Update License

Click License->License Update:
And the following diag is:
Input the valid License Code, and click OK.
5 Project
5.1 Introduction
For the following functions, the data must be created and imported by project:

 Alarm Analysis
 Performance Measurement Browsing
 Fault Diagnosis
 Dashboard
 Operation log Analysis
 CHR&PCHR Analysis
The FMA can support only one project to open synchronously. During the opening the
project, the data can be imported to FMA, and if the project is closed, the FMA data will be
cleared automatically. In the next time, open the project and the data will be imported again.
If the project is modified, the data will not be updated immediately. Only when you close and
open the project, the data will be updated.
5.2 Operation Guide

5.2.1 Create Project
Step 1 Run the FMA, and then choose Project >Create Project from the shortcut menu.
Step 2 Input the Name and Version of project as below:
Step 3 Click the Next button, and input the path of relative log and other information based on
requirement. If import the MML scripts, input the path of MML scripts in the MML Node in
the left tree as below. The information of MML Scripts, Alarm, Performance, UKPI , Operator
log and CHR&PCHR log can be input in one project at same time.

Step 4 Click the Save button, and the project will be saved and opened automatically.
5.2.2 Open Project

Step 5 Run the FMA, and then choose Project >Open Project from the shortcut menu.
Step 6 Select the project needs.
Step 7 Click the OK button, and then the progress bar will be pop-up. If the project has the MML
script, or alarm, or performance file, the progress bar will occurred.

After finish the progress, and wait about 1~10 seconds to initiate the windows of project, the
following windows will be displayed.
5.2.3 Modify/Delete Project

Modification of project is only to modify the path of data, and during the opening the project,
the data will be imported by new path.
Step 8 Run the FMA, and then choose Project >Mod/Del Project from the shortcut menu.
Step 9 Click the project name and modify the information.

Step 10 If delete a project, right click the project name and select Delete.
5.2.4 Close Project

Double click the header of TAB, or click the ‘X’ button in the left, the project will be closed.

6 Alarm Analysis
6.1 Introduction
The FMA supports the following alarm analysis functions:
 Viewing alarms quickly
 Associating alarms with the MML script
 Quickly locating the SPU, interface board, and node where the specified alarm is
generated
The FMA can also provide trend charts of common fault alarms. Therefore, the relevant fault
rate of the specified alarm type on an SPU subsystem or port can be discovered quickly.
The current version supports parsing of user alarms (those exported by the COL LOG:
LOGTYPE=HISTORY_ALARM-1; command, or CSV file) and associate with MML
script, and supports parsing fault alarms (those exported by the COL LOG:
LOGTYPE=HISTORY_FAULT-1; command), but not associate with MML script.
The following alarm log will be supported:
 Run COL LOG to collect the user or fault alarm
 Run EXP ALMLOG to collect the CSV alarm file
 Export the CSV alarm file from the alarm plane
6.2 Operation Guide

6.2.1 Browsing Alarms
Step 11 Use the section 4.2.2 to create the alarm project and input the path of alarm file. If associate
with MML script, input the path of MML script in the alarm project.
Step 12 Choose Project >Open Project from the shortcut menu.

You can open a compressed ZIP file or a decompressed alm_useralm_historyalarm.txt. If opening a

project with compressed ZIP file fails due to the failure of memory decompression, decompress the file,
and then input the path of decompressed alm_useralm_historyalarm.txt in the project.
Step 13 Set the appropriate period, and then click Analysis Alarmlog.
The Alarm Data tab page lists the queried alarms, as shown in the following figure:
The alarm information includes the ID, name, type, severity, start time, restoration time, and
location of each alarm.
On the Alarm Data tab page, the values of the Dev Info, SPU Info, INT Info, and Node
Name parameters are displayed only when the alarms are associated with the scripts.
Set the appropriate query period based on the fault time. If the start time of a fault alarm is earlier than
the end time of query and the restoration time is later than the end time of query, the alarm is regarded as
a current alarm. You can obtain the current alarms based on actual requirements.

6.2.2 Associating Alarms with the MML Script

When create a alarm project, input the path of MML script to associate with alarm
information. The MML script file can be as ZIP or TXT file. Opening the project, the MML
script will be firstly to initiate, and then alarm file.
The following columns will be set by association.
 Dev Info indicates the device information (that is, board information) associated with the
alarm.
 SPU Info indicates the SPU subsystem information associated with the alarm, for
example, the control SPU subsystem of the SAAL link.
 INT Info indicates the interface board information associated with the alarm, for
example, the egress port on the interface board of the SAAL link.
 Node Name indicates the node name associated with the alarm, for example, the NodeB
name or the DPX name of the IUCS interface.
No associated information is available for an alarm in any of the following cases:
 No associated information (such as SPU subsystem and device information) is available
for the alarm.
 The alarm was generated a long time ago and the configuration of the associated object
has been deleted from the script.
 The alarm is an event alarm. The FMA does not support script association for most event
alarms, except for the traffic control events.
6.2.3 Filtering Alarms

Step 14 Right-click on the Alarm Data tab page, and then choose Show All from the shortcut menu.
Step 15 Choose Filter.
The data in the column is filtered by content, as shown in the following figure:
Step 16 In the dialog box shown in the following figure, choose desired alarms to be filtered.

The FMA also supports the following functions:

 Filtering out alarms
Right-click on the Alarm Data tab page, and then choose Reverse from the shortcut
menu. In the displayed dialog box, choose an alarm type, and then click OK. All alarms
of the specified type are filtered out quickly.
 Deleting an alarm
Right-click on the Alarm Data tab page, and then choose Delete from the shortcut menu
to delete the specified alarm.
 Displaying all alarms
Right-click on the Alarm Data tab page, and then choose Show All from the shortcut
menu to display all alarms.
6.2.4 Highlighting Alarms

Step 17 Right-click on the Alarm Data tab page, and then choose Color from the shortcut menu.
Step 18 Choose an appropriate color.
All alarms of the specified type are displayed in the chosen color. This function enables you to
locate an alarm quickly by color.

Step 19 Click OK.

The relevant result is displayed, as shown in the following figure:
6.2.5 Saving Alarms

Right-click on the Alarm Data tab page, and then choose Save from the shortcut menu to
save alarms as a CSV file.

6.2.6 Sorting Alarms by Type

The navigation tree on the left of the Alarm Data pane displays the different types of alarms.
The alarms are sorted by type.
Expand any alarm type.

All alarms of the type are listed by ID, as shown in the following figure:
The information in the parentheses indicates the number of alarms and the alarm name. You
can also sort the alarms by count, as shown in the following figure:

The alarms are sorted by count, as shown in the following figure:
6.2.7 Analyzing the Trend of Alarms

The FMA enables you to analyze the fault rate of the specified alarm type on an SPU
subsystem or on the ports of an interface board. For example, if an interface board is
configured with 100 SCTP links and 80 SCTP links fail in the measurement period, it
indicates that the SCTP link fault rate of the interface board is 80%.
The alarm chart varies with measurement periods. You can minimize the measurement period
to obtain an accurate alarm chart.
Step 20 Click the Alarm Chart button.
The New Alarm Statistic dialog box is displayed, as shown in the following figure:

Step 21 Choose an object to be measured (for example, Cell or SAAL Link).

If you choose Cell, the alarm chart depends on the Cell Unavailable and NodeB Unavailable
alarms.
Step 22 Set the time range, and then click Statistic, as shown in the following figure:
An alarm chart is displayed, as shown in the following figure:

To view the alarm chart of a specific object, choose the object from the drop box, as shown in
the following figure. To view different pages, press the PgDn or PgUp key on the keyboard.
If zoom the chart, click the following button:
And then drag the mouse with the left click in the chart as square as below:

Unclick the mouse; the following chart will be drawn with new calculation. The following is
more accurate.

6.2.8 Analyzing the Frequency Trend of Alarms

The frequency of alarm is to calculate the weight of starting alarms (the alarm is happened in
statistic period), restoring alarms (the alarm is restored in the statistic period), and fault alarms
(the alarm is happened or restored or fault all the time in the statistic period), and then draw
the weight of alarm as curve to reflect the trend of alarm. This function can be used to analyze
the happened time of accident quickly.
Step 23 Right Click the alarm table, and pop-up the menu, choose the Statis Chart as below:
Step 24 Set the appropriate the weight of alarm. If only know the frequency of Critical alarm, the
weight of the other type alarm can be set as zero.
Step 25 Click OK.

If zoom the chart, click the following button:
And then drag the mouse with the left click in the chart as square as below:
Unclick the mouse; the following chart will be drawn with new calculation.

The frequency of alarm will be drawn detailedly.

7 Performance Measurement Browsing
7.1 Introduction
The FMA enables you to parse and browse performance measurement of the RNC. The FMA
can be used to parse and browse up to 200 files. Particularly, the FMA parses one file every
one second. Therefore, it takes about two or three minutes to parse 200 files.
The FMA supports association between the performance measurement and the MML script.
That is, the FMA supports the cluster function, for example, the cluster of SPU boards or
subsystems, or the cluster of interface boards or ports.
The FMA supports common KPI analysis. The FMA also supports the analysis of Top N cells,
including detailed KPIs of Top N cells.
The FMA supports fast KPI query and query of user-defined counters. The query result can be
displayed as graphs (up to 2 x2).
The time for the performance measurement displayed on the FMA is set according to the local
daylight saving time (DST). That is, the time displayed on the FMA is the start time displayed
in the performance measurement file plus the DST offset.
The FMA support the KPI of cluster of cell, and user is easy to select one or more cells, or
one NodeB to calculate the KPI.
The FMA support the filter function to check the health of network. There have more than 280
rules and cover with all domains of counters.
The FMA support the voice mode of RNC or cell. Support CPU usage evaluation of SPU and
MPU.
7.2 Operation Guide

7.2.1 Reading Performance Measurement
Step 26 Use the section 5.2.2 to create the performance project and input the path of performance file.
If associate with MML script, input the path of MML script in the performance project.
Step 27 Choose Project >Open Project from the shortcut menu.

Step 28 Choose the performance project to open.
Step 29 Click OK.

The relevant result is displayed, as shown in the following figure. The following result is
displayed (the number of files) seconds later:

7.2.2 Browsing Performance Quickly

Step 30 Click the Object or Counter tab.
On the Object tab page, the performance measurement data is classified by object. On the
Counter tab page, the performance measurement data is classified by counter.
Step 31 Double-click a measurement unit.
The relevant performance measurement is displayed, as shown in the following figure:
You can choose to display multiple curves in the same graph or display different curves in
different graphs.
If you right-click a line in the data list, a tab page is displayed, showing the curves. You can
also right-click on the counter list and then choose Make Graph from the shortcut menu, as
shown in the following figure:

1. Double-click the required counters in the Chart Setting dialog box.

The chosen counters are displayed in the pane on the right, as shown in the following
figure:
2. Click OK.
A graph is displayed, as shown in the following figure:
To display different curves in different graphs, set the parameters in the Chart Setting
dialog box as follows:

1. Set Chart Name, Chart axis rows, and Chart axis columns (1 x 1, 1 x 2, 2 x 1, or 2 x
2).
2. Double-click the required counters in the left pane to add them to the right pane.
3. For 1 x 1 graphs, set Axis Index to 1. For a 2 x 2 graphs, set Axis Index to 1, 2, 3, or 4.
The curves with the same axis index are displayed in the same graph.
7.2.3 Query Performance Measurement

Click the Query button to get the result of counter. FMA support two methods to query
counter as below:

Method 1: the user can only select one class and counters which are belong to this class to
query, such as UCELL class, we can choose the counters and objects under UCELL class.
Method 2: the counters and objects under different class can be selected at same time, such as
CPU Usage under XPU and RRC SR under CPUS can be chosen simultaneity and display the
result in same report.
If choose the Method 1, and get the following dialog:
Click the Add Counter button to add counters belong to given class. The selected counters can
be saved as template. The Object can be chosen in the right and upper, or input by hand in the
right and bottom. Click OK and get result.
If choose the Method 2 as below:

Choose the Class, Object and Counters, double click the counter or click “>>”, and click
OK to get result.
7.2.4 Saving Performance Measurement

In the counter list, right-click and then choose Save from the shortcut menu to save the
performance measurement as a CSV file.
7.2.5 Associating the Performance Measurement with the MML

Script
When create a performance project, input the path of MML script to associate with
performance information. The MML script file can be as ZIP or TXT file. Opening the
project, the MML script will be firstly to initiate, and then performance files.
After the MML script is associated, under the UCELL node on the Object tab page, the red-
circled clusters shown in the following figure are added (the cluster computing for cells are
based on interface boards or ports and SPU subsystems). Under AAL2Path, IPPATH, SAAL,
or SCTP, clusters are added to services automatically.

On the KPI tab page, the red-circled KPIs shown in the following figure are added.
7.2.6 Setting User-Defined Counters

Step 32 Click the Counters button.
The Defined Counters Setting dialog box is displayed, as shown in the following figure:

The FMA provides all the user-defined counters in the Nastar. You must set Class Name and
Mu Name correctly when adding a user-defined counter. If you set Counter Name the same
as that of an existing counter, adding the counter fails. All the counters in the formula must
belong to the same class.
Set the correct names and formula, and then click Add to add a user-defined counter to the
program. The added user-defined counter remains the next time you run the program. The
user-defined counters are saved by version of the performance measurement.
The formula for dividing a counter by the measurement period is as follows:
A / {SP}
In the formula, A stands for the counter and SP stands for the measurement period.
7.2.7 Browsing Common KPIs

Click the KPI tab in the pane on the left, and then choose RNC Nastar KPI, CN Operator
KPI, Interface Board KPI, or SPU Subsystem KPI. The TRNC Nastar KPI report lists the
KPIs specified in the KPI report of the Nastar. The other three reports are defined by the
FMA.
The CN Operator KPI report lists the common KPIs by operator. The Interface Board KPI
and SPU Subsystem KPI reports list the throughput, SR success rate, and CDR call drop rate
by interface board and SPU subsystem respectively.
The Raw Record Unit indicates that the data is displayed by the minimum original
granularity. The All Time indicates that the data is displayed by all time.

To learn the detailed KPI definitions in the FMA, refer to the

V900R012C01UOKPIReport.xml in \Config\Mrf in the installation directory of the FMA.
It is recommended that you remain the content of the file to prevent errors in the subsequent
program.
7.2.8 Analyzing Top N Cells

Step 33 Click the TopCell tab.
The TopCell tab page is displayed, as shown in the following figure:
Step 34 Choose different Top N cells to analyze as required.

The FMA supports analysis of Top 10 cells only.
If you choose TOP RRC SR, the TOP RRC SR pane is displayed on the right, as shown in
the following figure:

The TOP RRC SR pane lists the RRC SR value of the RNC, the RRC SR value of the top 10
cells, and the ratio of the RRC setup failures of top 10 cells to the total RRC setup failures of
the RNC. The higher ratio indicates the greater contribution of top 10 cells to the KPI of the
RNC. The TOP RRC SR pane also lists the IDs and SR values of top 10 cells.
The TOP RRC SR pane also lists the cause for the specific counter in each period.
If the performance measurement is associated with the MML script, the TOP RRC SR pane
also lists the SPU subsystems and interface boards or ports where top N cells are located.
Therefore, you can check whether top N cells are located in the same SPU subsystem or the
same port on an interface board.
FMA supports the TOPN resource as below:

7.2.9 Analyzing Voice Mode

The FMA supports calculating the voice mode of RNC or Cell.
Step 35 Click the node as below red circle, and get the voice mode data in the right table. The Raw
Record Unit is calculating the voice mode with original periods, and the All Time is
calculating the voice mode by average.
If know the formula of voice mode, click the All Time:

If get the result of voice mode of cell, input the cell ID as below:
And the result is similar as the previous.
7.2.10 Analyzing with General(Cluster)

The FMA supports one or more cells, or all cells under one NodeB, compose a cluster, and
calculate the general KPI of the cluster. The cell can be listed in Element or Cluster. The
Element contains the all cell. The MML path is input in the project, the cell name will be
displayed in Element, or the cell id will be displayed. The Cluster contains the cluster of cell,
and one cluster can be formed by more than one cells. The user can define the cluster.

The FMA supports filter by cell Name or ID. If input the Name in Filter by, the cells which
name is satisfied with the condition will be listed as below:
The user can choose one or more cell as below, and then click the Investigate button to
calculate the general KPI.
The result will be gotten as below, and every counter is calculated by cluster, such as the
previous 4 cells can be formed as one cluster.

If user chooses cluster or NodeB, only one cluster or NodeB can be selected at same time. The
user can define a cluster by himself. The following chart is shown as adding a cluster.
Input the cluster name or cell id as below:

Click the OK and the cluster will be saved. The user can select one or more cells in Element
TAB page, and then right click, choose Add Cluster to add a cluster.
Input the cluster name as below:
Click OK.
For the cluster cell, the user can query the defined KPI. Select the cluster cells, and right click,
choose the Query counter as below:

Choose the required counter as below:
Click OK and get result.

7.2.11 Filter
The FMA supports user defined filter function to check the health of network quickly, and
about 280 rules can be selected by user which covers with all domains of counters.
There have two methods to filter. One is denoted as Filter Method1, and it can filter all objects
which are under same Class counter. The counters in one rule must be belong to same Class
counter. The other is denoted as Filter Method2, and it can filter one or more NodeBs, and all
objects which are relative with the NodeB, such as Path, SCTP link. If the condition of filter is
satisfied, the object will be listed.
Click the Filter button as below:
The following window will be pop-up.
Choose the rules which need to check and click the OK button:

If user wants to add the rule to filter, click Add Rule button as below:
The following window is shown:

All counters in one rule should be same in one Class, and this rule can filter all objects under
the Class. The name of filter can be set as, header1,header2,header3... and then the rules can
be classified by header. The rule can be used the formula, such as +, -, *, / and logical
calculation.
The FMA provides add, modify, delete and export operation. If use the export operation, all
rules will be exported as CSV file, and is easy to review by user.
7.2.12 Search Counter

Click the Object or Counter TAB page, and right click the page, and then choose the Search
counter as below, or press the Ctrl+F.
Input the counter name (upper capitalization, or lowercase) as below:
Click the find button, or press Enter, the counter will be found, and the counter or MU can be
highlight.
In the queried result of Object Tab, find function can be applied. Right click the page, and
then choose the Search counter as below, or press the Ctrl+F.
highlight.

7.2.13 Query the detailed information of counter

The FMA provides many user-defined counters, and if know the formula of counter, use this
function to query.
then choose the Display Counter Info as below
Or in the page of Counter Tab, right click the page, and then choose the Display Counter
Info as below
The detailed information is listed as below:
7.2.14 CPU Evaluation
FMA supports CPU usage of SPU and MPU based on the benchmark and KPI counters. The
function can be used when the RNC or MBSC MML scripts has been load in the project.

The user clicks the SPU CPU Load Evaluation and gets the benchmark value. If the value of
benchmark is changed, modify the value in the dialog.
If click the Reset, the value of benchmark will be set as default value given by FMA. The
result of evaluation is shown as below:

7.2.15 Abnormal Counter Check
If the value of counter is increase by degrees for all day, but not decrease, that means the
counter is abnormal. FMA can support this issue to check.

If Deltas(-) (the times when the value of counter is decreased) is less than and equal to 1, and
the percent of Deltas(+) is more than 50%, the counter is abnormal.
8 Dashboard
8.1 Introduction
The FMA support the associating analysis between the performance, alarm and operator log.
The user can query the performance and analyze the impact of KPI quickly. Click the point of
worse KPI in the chart, and the relative alarm and operator log will be given.
The project should be input the performance, alarm or operator log, and must be more than
two types log to display the history page.
8.2 Operation Guide

Step 36 Use the section 5.2.2 to create a project and input the path of performance file, or alarm file,
or operator log. If associate with MML script, input the path of MML script in the
performance project. Open the project, the History window is shown as below:

The RNC Nastar KPI will be drawn in the left window, and the operator log is listed in the
right table, and the alarm information is displayed in the bottom table.
If user clicks any area of chart, or any line of operator log, or any line of alarm log, the other
two types log will be located and highlight the line quickly based on the same time.
If right-click the operator or alarm log, the detailed information will be listed as below:

The filter function can be applied for alarm or operator table.
If check the frequency of alarm, refer to section 5.2.8 as below:

And result is shown as below:

9 Performance Measurement Comparison
9.1 Introduction
The FMA parses the performance measurement in the same period in two days, compares the
same counters or KPIs, and then displays the graphic result.
The number of performance measurement files must be the same for the two periods to be
compared.
9.2 Operation Guide

9.2.1 Reading Performance Measurement
Step 37 Choose Tool > Performance Compare from the menu.
Step 38 Choose the correct version.

Step 39 Choose the correct file path and measurement period.

Step 40 Click Load.

Wait for (the number of files) seconds. A dialog box is displayed, indicating that loading the
files succeeds.
9.2.2 Comparing Performance Measurement

Double-click the required leaf node on KPI tab page on the left.
The relevant performance measurement is displayed, as shown in the following figure. The
graph or data list shows the curves or data in the two periods. You can quickly recognize the
changes in KPIs.
9.2.3 Search Counter

Click the Object or Counter TAB page, and right click the page, and then choose the Search
counter as below, or press the Ctrl+F.

highlight.
then choose the Search counter as below, or press the Ctrl+F.
highlight.
9.2.4 Query the detailed information of counter

The FMA provides many user-defined counters, and if know the formula of counter, use this
function to query.
then choose the Display Counter Info as below

Or in the page of Counter Tab, right click the page, and then choose the Display Counter
Info as below
The detailed information is listed as below:

10 Real-Time UKPI Monitoring
10.1 Introduction
The real-time UKPI monitoring tool parses and displays the results of the EXP UKPI and
USERNUM commands to guarantee satisfactory services in holidays or in important
activities.
The UKPI file contains only some KPIs of the SPU, IU, DSP, and cells. The real-time UKPI
monitoring tool monitors the KPIs in real time, detecting whether congestion or failure occurs
in the SPU, IU, or cluster cells.
Note: The function of 5 minutes counter should be opened in M2000, and only one any
counter can be set as 5 minutes, not all counters.
10.2 Operation Guide

10.2.1 Browsing the UKPI Offline
Step 41 Choose Monitor > KPI Monitor from the menu, as shown in the following figure:
The KPI Monitor page is displayed, as shown in the following figure:

Step 42 Click Setting.

The KPI Monitor Setting dialog box is displayed, as shown in the following figure:
Step 43 Choose the correct version and set the correct local path of the UKPI file.
Step 44 Click Save.

Step 45 Click the required leaf node on the Object tab page to browse the relevant performance
measurement.
10.2.2 Displaying the Graphic Result

Step 46 On the KPI Monitor page, click New Chart.

The Chart Setting dialog box is displayed, as shown in the following figure:
Step 47 Set Chart Name, Chart axis rows, and Chart axis columns (1 x 1, 1 x 2, 2 x 1, or 2 x 2).
Step 48 Double-click the required counters in the left pane to add them to the right pane.
Step 49 For 1 x 1 graphs, set Axis Index to 1. For a 2 x 2 graphs, set Axis Index to 1, 2, 3, or 4. The
curves with the same axis index are displayed in the same graph.
You can also load and save a template.

1. Click Load.
The Choose a Chart-Setting file dialog box is displayed, as shown in the following
figure:
2. Choose a template (extension: .chartset).

After the template is loaded, the result is displayed as follows:

The graphs are displayed, as shown in the following figure:
10.2.3 Defining Cluster Cells

Step 50 On the KPI Monitor page, click VIP Cells.
The VIP Cells Setting page is displayed, as shown in the following figure.
Step 51 Right-click on the page, and then choose Add from the shortcut menu.

Step 52 Set VIP Cells Name and set the cell IDs.
The format of the cell IDs is as follows:
RNCID: CellID1; CellID2; CellID3; …
Step 53 Click OK.

The cluster cells are added.
Step 54 Click Save.

Under the CLUSTER-CELL node on the left, the newly added cluster cells are displayed.

10.2.4 Setting User-Defined Counters

Step 55 On the KPI Monitor page, click Counters.
The User Defined Counters Setting dialog box is displayed, as shown in the following
figure. The dialog box lists the common user-defined counters. You can right-click any
counter to view the detailed information.

To add a user-defined counter, right-click on the counter list, and then choose Add from the
shortcut menu. The Add Defined Counters Dialog box is displayed, as shown in the
following figure:
Set the equation correctly. All counters in the equation must belong to the specified type (such
as an SPU).
To view the counters corresponding to each type, open the result file of the EXP UKPI
command.
10.2.5 Monitoring KPIs Online

Step 56 On the KPI Monitor page, click Setting.
 Set BAM IP, FTP IP (usually the same as the BMA IP), User Name, and Pwd.
 Set Path of KPI in BAM correctly (/bam/version_x/ftp/kpi_file). Choose version_a or
version_b based on the current area. To query the current area, log in to the BAM by
using the LMT and then run the LST OMUAREA command.
 Set Path of KPI in local to the default value.

Step 57 Click Save to save the settings.

Step 58 Set Interval Time (minutes) to 5 on the KPI Monitor page.
Step 59 Click Delete Log to delete the existing tracing data, and then click Start.
The progress bar on the left shows the monitoring progress and the monitored data is
displayed at the lower right corner.
Step 60 Click the required counter on the Object tab page, as shown in the following figure:

You can also display the graphic result as follows:
Step 61 To stop real-time KPI monitoring, click Stop on the KPI Monitor page.

11 Fault Diagnosis
11.1 Introduction
This function is applicable to the MML scripts, performance measurement, and UKPI files.
The configuration scripts must be exported by the EXP CFGMML or EXP
INNERCFGMML command. This function is applicable to RNC scripts in UO mode only.
The FMA supports the following functions:
 Displaying the panel
 Extracting the NodeB configuration script by NodeB name or ID
 Extracting configuration scripts of the IUCS, UUPS, and IUR interfaces
 Exporting cell information
 Exporting link information
 Exporting neighboring cell information
 Obtaining the scripts of the blocked or unblocked cells in the specified SPU subsystem
 Obtaining the scripts of the blocked or unblocked cells on the port of the specified
interface board
 Fast fault diagnosis
The FMA checks whether the SPU subsystems, interface boards, or IUCS or IUPS
interfaces are in normal state based on the various original rules, and then draws a
comprehensive conclusion.

11.2.1 Displaying the Panel
Step 62 Use the section 5.2.2 to create a project and input the path of MML script. If performance file,
or alarm file, or operator log is needed, this information should be input the project.
Step 63 Click Open.
A page is displayed, as shown in the following figure:

Enter the RNC data sources on the left. The configuration panel of the RNC is displayed on
the right.
On the panel, the interface information is displayed on the interface board, as shown in the
red-circled part in the preceding figure. C indicates the IUCS interface, P indicates the IUPS
interface, R indicates the IUR interface, and B indicates the IUB interface. If you double-click
the panel, the details about the panel are displayed, as shown in the following figure:

The detailed interface information is displayed near the port icons on the interface boards. For
example, C indicates the IUCS interface. You can learn the service types on the relevant ports
easily.
11.2.2 Extracting the Configuration Script

Step 64 Choose IAPT > MML Info > Extract NodeB MML by Cell ID (or other red-circled options
shown in the following figure) from the menu.
These menus enable you to extract the MML configuration scripts of the NodeB, IUCS, IUPS,
and IUR interfaces quickly.
The functions of the menus are as follows:

 Extract NodeB MML by NodeB Name or ID
This menu enables you to obtain the configuration script of a NodeB quickly based on
the NodeB name or NodeB ID.
 Extract NodeB MML by ADJNode ID

This menu enables you to obtain the configuration script of the NodeB quickly based on
the ID of the adjacent node of the NodeB.
 Extract NodeB MML by Cell ID
This menu enables you to obtain the configuration script of the NodeB quickly based on
the cell name of the NodeB.
 Extract IUCS MML
This menu enables you to obtain the configuration script of all the IUCS interfaces in the
configuration script of the RNC quickly.
 Extract IUPS MML
This menu enables you to obtain the configuration script of all the IUPS interfaces in the
 Extract IUR MML
This menu enables you to obtain the configuration script of all the IUR interfaces in the
The following figures show the obtained configuration script of a NodeB:
The following figure shows the obtained configuration script of the IUCS interfaces:

The following figure shows the obtained configuration script of the IUPS interfaces:
The following figure shows the obtained configuration script of the IUR interfaces:
11.2.3 Obtaining the Associated Information on Cells, Links, and

NodeBs
To obtain the associated information on cells, links, or NodeBs, choose IAPT > MML Info >
Export Cells Info as CSV File (or other red-circled options shown in the following figure)
from the menu.

The functions of the red-circled menus are as follows:

 Export Cell Info as CSV File
The FMA exports the following information on all cells as a CSV file:
− CellID: cell ID
− UARFCNDownlink: downlink frequency point of the cell
− NodeBName: name of the NodeB where the cell is located
− SPU Info: information on the SPU where the NodeB is located, including
SRN_SN_SSN
− Int Brd Info: information on egress ports on the interface board of the cell
The egress port information is calculated based on the AAL2Path or IPPATH mapped
by the common channel, including SRN_SN_PN_BoardName_bearer
type_ATM/IP/ ATMLOGICPORT.
If two egress ports are available for a cell, the NodeB works in the load balancing
mode.
 Export Links Info as CSV File
The FMA exports the following information on all links as a CSV file:
− Link Type: link type, including the SAAL, AAL2PATH, SCTP, and IPPATH
− Object: object information
Link Type: meaning of the object
SAAL: SRN_SN_SAALLNK of the SAAL link
SCTP: SRN_SN_SCTPLNK of the SCTP link, including the IP addresses of the
local and peer ends
AAL2PATH: ANI_PATHID of the AAL2PATH
IPPATH: ANI_PATHID of the IPPATH, including the IP addresses of the local and
peer ends
− NODENAME: node name
− Carry Type: bearer type, including the NCP, CCP, ALCAP, IUB UP, IUCS, IUPS, and
IUR
− SPU Info: control SPU of the link (that is, SRN_SN_SSN)
If the SCTP or SAAL link adopts the IU or IUR interface, only SRN_SN is
displayed.

− Int Brd Info: information on egress ports on the interface board of the link
The egress port information is calculated based on the AAL2Path or IPPATH mapped
by the common channel, including SRN_SN_PN_BoardName_bearer
type_ATM/IP/ ATMLOGICPORT.
 Export NodeBs Info as CSV File
The FMA exports the following information on all NodeBs as a CSV file:
− NODENAME: node name, that is, NodeB name
− NODEBID: NodeB ID
− TnlBearerType: bearer type of the NodeB, including the ATM, IP, and dual stack
− Int Brd Info: information on egress ports of the NodeB, that is, the egress ports on
the control plane and user plane of the NodeB
11.2.4 Obtaining Statistics

To obtain the statistics of the NodeBs, control plane, and user plane, choose IAPT > MML
Info > Export NodeB Stats Info by SPU as CSV File (or other red-circled options shown in
the following figure) from the menu.
The functions of the menus are as follows:

 Export NodeB Stats Info by SPU as CSV File
This menu enables you to obtain the number of configured NodeBs and the number of
configured cells on the specified SPU subsystem.
 Export NodeB Stats Info by INT Brd Port as CSV File
This menu enables you to obtain the number of configured NodeBs and the number of
configured cells on the specified egress port of the interface board.
 Export IUB SCTP/SAAL Stats Info by SPU as CSV File
This menu enables you to obtain the number of SCTP or SAAL links configured on the
specified SPU subsystem.
 Export IUB SCTP/SAAL Stats Info by INT Brd Port as CSV File
This menu enables you to obtain the number of SCTP or SAAL links configured on the
specified egress port of the interface board.
 Export IUB PATH Stats Info by INT Brd Port as CSV File

This menu enables you to obtain the number of PATH (IPPATH or AAL2Path) links
configured on the specified egress port of the interface board.
11.2.5 Obtaining NetGroup Cells

To obtain the NetGroup file to be used by the Omstar and Nastar, choose IAPT > MML Info
> Export Cells as NetGroup File from the menu.
The NetGroup file can be imported to the Omstar or Nastar for fast analysis of cluster cells.
The FMA classifies cell clusters based on SPU subsystems, SPU boards, egress ports or
boards of the cells.
11.2.6 Obtaining Scripts of Blocked or Unblocked Cells

To obtain the scripts of the blocked or unblocked cells, choose IAPT > MML Info > Export
Act/Dea Cell Commands as TXT File from the menu, as shown in the following figure:
The Export Dea/Act Cell Commands dialog box is displayed, as shown in the following
figure:

The FMA provides the following options for exporting cell commands:
 Export Cmd by Frequency
This option enables you to export the cell commands by frequency.
 Export Cmd by NodeB
This option enables you to export the cell commands by NodeB.
 Export Cmd by SPU
This option enables you to export the cell commands by SPU subsystem.
 Export Cmd by Int Brd Port
This option enables you to export the cell commands by egress port.
Choose the appropriate options, set the path for saving the file, and then click OK.
This function is used to block cells to ease the severe traffic control on the interface board,
SPU board, or IU interface.
11.2.7 Obtaining Information of Neighboring Cell

To obtain the information of neighboring cell, choose IAPT > NCELL Info from the menu.
 Export NRNC 3G Cells Info as CSV File: to obtain the 3G cell information of
neighboring RNC, including: NRNCID 、 N3CellID 、 N7DPC 、 NRNC CP SPU
Info 、 NRNC CP INT
Info、CNOPERATOR 、BandInd 、UARFCNDownlink 、PScrambCode。
 Export NBSC 2G Cells Info as CSV File: to obtain the 2G information of neighboring

BSC,
including:GSMCellIndex、GSMCellName、LdPrdRprtSwitch、CNOPERATOR、RatCell
Type、BandInd、UseOfHcs、NCC-BCC-CID、BcchArfcn。
 Export Intrafreq NCells Info as CSV File ： to obtain the intrafrequecy 3G cell
information , including: CellID SPG ID 、 RncId 、 NodeB Name 、 Intrafreq
NCellId、NSPG ID、PScrambCode、NRncId、Ncell NodeB Name。
 Export Interfreq NCells Info as CSV File ： to obtain the interfrequecy 3G cell
information , including:CellID RncId、NodeB Name、SPG ID、NRncId、Intrafreq
NCellId 、 PScrambCode 、 Ncell NodeB Name 、 NSPG
ID、BlindHoFlag、NPrioFlag、NPrio、InterNCellQualReqFlag、MBDRFlag、DrdOrLdrFl
ag。
 Export U2G NCells Info as CSV File ： to obtain the interrat 2G cell information ,
including:CellID、RncId、NodeB Name、GSMCellIndex、RatCellType、NCC-BCC-
CID、BcchArfcn、BlindHoFlag、NPrioFlag、NPrio、MBDRFlag。
 Export Intra NCells by CellID or CellID List as CSV File：to obtain the intrafrequency
cell information based on the 3G Cell ID or list or source RNC.
 Export Inter NCells by CellID or CellID List as CSV File：to obtain the interfrequency
cell information based on the 3G Cell ID or list or source RNC.
 Get the Intrafreq NCell Info by CellID and PScrambCode ：to obtain the intrafrequency
neighboring cell ID based on the Cell ID of source RNC and PScrambCode or
neighboring cell.
 Get the Interfreq NCell Info by CellID and PScrambCode ： to obtain the to obtain the
interfrequency neighboring cell ID based on the Cell ID of source RNC and
PScrambCode or neighboring cell.。
 Get the GSM NCell Info by CellID and BCCH:NCC:BCC ： to obtain the interrat
neighboring cell information based on the Cell ID of source RNC and BCCH:NCC:BCC
of interrat neighboring GSM cell.
11.2.8 Obtaining Swap NodeB Commands for 1+1 RNC Backup

RNC is backup with 1+1, and FMA supports to obtain the swap NodeB commands quickly by
SPU or interface board.
And following dialog window:

Set parameters and get scripts with SWAP NODEB.
11.2.9 MML Check

FMA supports the MML health check, and the following rules is shown:
NO Rule Name Description of Rule
1 Check the backup of If the board (FG2 or GOU) is configed as backup mode, and
port of GOU and FG2 the relative port is used for IPPAT or SCTP, and the port is
board not used for load sharing mode, the port should be configed
as backup mode.
2 Check the MSP If the board(UOI/AOU/POU) is configed as backup mode,

configuration for and the port is used, the port should be set as MSP and make
UOI/AOU/POU board sure is is actived
3 Check the IPCHK 1). If the ETH port is used for L3 network, and if the port is
configuration for ETH configed as backup mode, the ARP or BFD check should be
Port opened for the active port.
2). If the port is used for load sharing mode, the ARP or BFD
check should be opened for the active and standby port.
4 Check the ATMTRF For the IUCS and IUPS interface, if SAAL link is used and
CFG of SAAL for IU carried for MTP3B link, the traffic service type of SAAL
interface should be as CBR or RTVBR.
5 Check the Band Width For the IUCS and IUPS interface, if SAAL link is used and
of SAAL for IU carried for MTP3B link, the bandwidth of SAAL should be
interface greater than 256kbps.
6 Check the ATMTRF For the IUCS and IUPS interface, the traffic service type of
CFG of AAL2Path for AAL2Path should be as CBR or RTVBR.
IU interface
7 Check the band width For the IUCS and IUPS interface, the band width of
CFG of AAL2Path for AAL2Path should be greater than 4096kbps.
IU interface
8 Check the PING If the tran type of IU interface is IP, and the port which is
Check of IPPATH for carried for IPPATH is not configed as load sharing
IU interface mode(board is bacup, and port is not backup), the ping check
flag of ippath should be set as enabled.
9 Check the service type 1). If IPPATH is configed for IUPS interface, the PATHT
for IUPS interface should be set as QoS.
2). If IPOAPVC is configed for IUPS interface, the service

type of IPOAPVC should be set as UBR or UBR+.

10 Check the AAL2RT AAL2RT must be configed for IUCS interface(ATM). The
Cfg for IUCS following IUCS ANI has no AAL2RT, please check.
interface(ATM)
11 Check the PATH for 1). The IUCS Adjnode(ATM) must be configed the
IU interface AAL2Path.
2). The IUCS Adjnode(IP) must be configed the IPPATH.
3). The IUPS Adjnode(ATM) must be configed the
IPOAPVC and IPPATH.
4). The IUPS Adjnode(IP) must be configed the IPPATH.
12 Check the 1). The redundancy IPRT should be check in same subrack.
Redundancy IPRT 2). The IPRT should not contain another IPRT, that means:
IP1$MASK1 == IP2&MASK2 and MASK1 != MASK2
3). If IP1$MASK1 == IP2&MASK2, and MASK1==
MASK2, check the port information. If the port information
(ATM and IP) is not same, the IPRT information will be
listed.
4). IF IP1$MASK1 == IP2&MASK2, and MASK1==
MASK2, check the priority of IPRT. If the priority is not
same, and the slot NO. of IPRT is not same, the IPRT
information will be listed.
13 Check the IPRT for 1). If the L3 is used for SCTP or IPPATH, the IPRT must be
SCTP/IPPATH configed.
2). IF the L3 is used for SCTP or IPPATH, and the port is set
load sharing mode(the board is backup, and port is not
backup), the IPRT links musted be configed in the active and
standby port at least.
14 Check the IPRT for If dual-home is used for SCTP, or CROSSIPFLAG of SCTP
SCTP(Dual-Home) is opened, the IPRT should be configed for each home.
15 Check the ATMTRF 1). If CDVT is configed for ATMTRF, and is not 1024, the
CFG ATMTRF info is listed.
2). If MBS is configed for ATMTRF, and is not 1000, the
ATMTRF info is listed.
16 Check the VLANID 1). If the L3 is used for SCTP/IPPATH, and the VLANFlAG
CFG of SCTP/IPPATH is set ENABLE, the VALID must be
configed for the nexthop of SCTP/IPPATH (ADD
VLANID), and VLANID of then must be same.
2). If the L3 is used for SCTP/IPPATH, and the VLANID is
configed for the peerip of SCTP/IPPATH(ADD VLANID),
the VLANID must be configed for the nexthop of
SCTP/IPPATH too. The VLANID of then needs to be same.
3). If the L3 is used for SCTP/IPPATH, and the port of
SCTP/IPPATH is set as loadsharing mode(the board is
backup, and port is not backup). If one port(active or standby
port) is set VLANID, the other port must be set VLANID,
and should be same .
4). If the L2 is used for SCTP/IPPATH, and the VLANFlAG
of SCTP/IPPATH is set ENABLE, the VLANID must be
configed for the peerip of SCTP/IPPATH(ADD VLANID),
and must be same.
17 Check the TRMMAP Check the TRMMAP of IUCS and type of
CFG for IUCS AAL2Path/IPPATH, whether the type of PATH is consistent.
18 Check the CNNODE Check the CNNODE is configed or not.
CFG
19 Check the SPG CFG The PriorityServiceForR99RT of all cell is configed as zero,

please check.
Click IAPT->MML Check as below:
And the result is shown as below:
11.2.10 Diagnosing Faults

Step 65 The user should input the path of alarm, performance or UKPI and operation log in project,
and click IATT->Diagnose as below:

And the following dialog windows is pop-up as below:
Step 66 Enter the start time and end time of the fault. Usually, you only need to enter a period when
the fault occurs. Click Analysis and the program diagnoses the fault automatically. The Status
bar shows the diagnosis progress, as shown in the following figure:

After entering the alarm path, wait for 10 to 30 seconds till the Status bar displays a message
"Finish to read the alarm file!"
The Status bar displays a message "End to analyze!" indicating that the fault diagnosis
succeeds. The Rule Analysis tab page is displayed, indicating the diagnosis result, as shown
in the following figure:
Step 67 Click Diagnose Results on the navigation tree on the left.

The Diagnose Results page is displayed, as shown in the following figure:

The Diagnose Results page lists the symptom, diagnosis result, and suggested recovery
operations.
To filter the NOK items on the navigation tree on the left, right-click on the tree and then
choose Filter NOK Items from the shortcut menu, as shown in the following figure:
To display the faults in the list on the right, right-click on the list and then choose Show Fault
from the shortcut menu, as shown in the following figure:
All abnormal KPIs are highlighted in red, as shown in the preceding figure.

11.3 Fault Diagnosis Results

11.3.1 IU PERF List
This list analyzes the SCCP setup success rate of IU interfaces. The following figure shows
the details of the list:
You can view the statistics in different periods.

If SCCP Setup SuccRate: VS.IU.SCCP.Tx.Con.Succ/VS.IU.SCCP.Tx.Con.Req is lower
than 90%, the value is highlighted in red. The numerals in the parentheses indicate
VS.IU.SCCP.Tx.Con.Succ and VS.IU.SCCP.Tx.Con.Req respectively. For other counters,
see the help of the performance measurement.
11.3.2 Fault Cell Rate by INT Port(PERF)

To display Fault Cell Rate by INT Port(PERF), click the Fault Cell Rate by INT
Port(PERF) node on the navigation tree on the left, as shown in the following figure:
This rule measures the KPIs of interface boards based on the performance measurement. The
relevant parameters in the list are as follows:
 INT
This parameter indicates the board name, subrack ID, slot ID or port ID, and the number
of cells that bear the board or port. This parameter also indicates whether the board is
backed up.
 Cell Ratio with lower RRC SR
This parameter calculates the RRC SR of cells. It indicates the ratio of the number of the
cells whose SR is lower than 80% on the port to the total number of cells whose RRC
attempt is not zero. If the ratio exceeds 80%, this parameter is highlighted in red.

 Cell Ratio with Zero RRC

This parameter calculates the RRC attempts of cells. It indicates the ratio of the number
of cells whose RRC attempt is zero to the total number of cells configured on the port. If
the ratio exceeds 80%, this parameter is highlighted in red.
 Cell Ratio with lower AMR RAB SR
This parameter calculates the CS RAB SR of cells. It indicates the ratio of the number of
the cells whose SR is lower than 80% on the port to the total number of cells whose CS
RAB attempt is not zero. If the ratio exceeds 80%, this parameter is highlighted in red.
 Cell Ratio with Zero AMR RAB
This parameter calculates the CS RAB attempts of cells. It indicates the ratio of the
number of cells whose CS RAB attempt is zero to the total number of cells configured on
the port. If the ratio exceeds 80%, this parameter is highlighted in red.
 Cell Ratio with lower PS RAB SR
This parameter calculates the PS RAB SR of cells. It indicates the ratio of the number of
the cells whose SR is lower than 80% on the port to the total number of cells whose PS
RAB attempt is not zero. If the ratio exceeds 80%, this parameter is highlighted in red.
 Cell Ratio with Zero PS RAB
This parameter calculates the PS RAB attempts of cells. It indicates the ratio of the
number of cells whose PS RAB attempt is zero to the total number of cells configured on
the port. If the ratio exceeds 80%, this parameter is highlighted in red.
11.3.3 INT PERF List

To display INT PERF List, click the INT PERF Display node on the navigation tree on the
left, as shown in the following figure:
This rule measures the KPIs of interface boards based on the performance measurement. The
relevant parameters in the list are as follows:
 INT Brd Port
This parameter indicates the board name, subrack ID, slot ID or port ID, and the number
of cells that bear the board or port. This parameter also indicates whether the board is
backed up.
 RRC Setup SuccRate(%)
This parameter indicates the RRC setup success rate. The equation is as follows: RRC
Setup SuccRate = RRC.SuccConnEstab.sum / VS.RRC.AttConnEstab.Sum. The
value lower than 80% is highlighted in red.
 AMR Setup SuccRate(%)

This parameter indicates the AMR setup success rate. The equation is as follows: AMR
Setup SuccRate = VS.RAB.SuccEstabCS.AMR / VS.RAB.AttEstab.AMR. The value
lower than 90% is highlighted in red.
 VP Setup SuccRate(%)
This parameter indicates the VP service setup success rate. The equation is as follows:
VP Setup SuccRate = VS.RAB.SuccEstCS.Conv.64 / VS.RAB.AttEstCS.Conv.64.
The value lower than 85% is highlighted in red.
 PS Setup SuccRate(%)
This parameter indicates the PS service setup success rate. The equation is as follows:
PS Setup SuccRate = VS.RAB.SuccEstabPS.Conv + VS.RAB.SuccEstabPS.Str +
VS.RAB.SuccEstabPS.Int + VS.RAB.SuccEstabPS.Bkg) /
(VS.RAB.AttEstabPS.Conv + VS.RAB.AttEstabPS.Str + S.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg). The value lower than 85% is highlighted in red.
11.3.4 IUB INT Brd Alarm Check

To display the diagnosis result of IUB INT Brd Alarm Check, click the IUB INT Brd
Alarm Check node on the navigation tree on the left, as shown in the following figure:
This rule lists the alarms related to the board within the fault period. On the BSC6900 V9R12,
the involved alarm IDs are as follows:
'20256', '22835', '20241',' 20242', '20243', '20272', '20250', '20251', '20233', '20257'
11.3.5 Config Info of IUB Brd Port

To display the diagnosis result of IUB INT Brd Alarm Check, click the Config Info of IUB
Brd Port node on the navigation tree on the left, as shown in the following figure:

This list displays the configuration information on the specified port. The parameters in the
list are as follows:
 NodeB Num(based on CCH)
This parameter indicates the number of NodeBs on the egress port based on the common
channel of the cell.
 Config Cell Num(based on CCH)
This parameter indicates the number of cells configured on the egress port based on the
common channel of the cell.
 Active Cell Num(based on CCH)
This parameter indicates the number of activated cells on the port.
 Config IUB SAAL Num
This parameter indicates the number of IUB SAAL links on the port.
 Config IUB SCTP Num
This parameter indicates the number of IUB SCTP links on the port.
 Config IUB AAL2PATH Num
This parameter indicates the number of IUB AAL2PATH links on the port.
 Config IUB IPPATH Num
This parameter indicates the number of IUB IPPATH links on the port.
The configuration data is displayed in the list on the right and in the red-circled part on the
left.
11.3.6 Fault Path Alarm Check

To display the diagnosis result of Fault Path Alarm Check, click the Fault Path Alarm
Check node on the navigation tree on the left, as shown in the following figure:

This rule measures the ratio of number of faulty paths to the total number of paths configured
on the port and displays a detailed path fault list. The upper part of the table on the right lists
the statistics of path faults, whereas the lower part lists the specific alarms of path faults. On
the BSC6900 V9R12, the involved alarm ID is 21581.
The statistics includes the following parameters:
 Object
This parameter indicates the measured object, that is, the specific port.
 Alarm Ratio per Object(%)
This parameter indicates the ratio of the number of faulty paths measured in the fault
period to the total number of paths configured on the port. An alarm is counted in any of
the following cases:
− The restoration time or start time of the alarm is within the fault period.
− The start time of the alarm is later than the start time of the fault, and the end time of
the alarm is earlier than the end time of the fault.
− The start time of the alarm is earlier than the start time of the fault, and the end time
of the alarm is later than the end time of the fault.
The ratio is also displayed on the Fault Path Alarm Check node on the left, as shown in
the red-circled part in the preceding figure.
 Active Alarm Ratio per Object(%)
This parameter indicates the ratio of the number of active alarms within the fault period
to the total number of paths configured on the port.
An alarm is counted as an active alarm if the start time of the alarm is earlier than the
end time of the fault and the end time of the alarm is later than the end time of the fault.
The ratio is also displayed on the Fault Path Alarm Check node on the left, as shown in
the red-circled part in the preceding figure.
 Time Period
This parameter indicates the fault period, that is, the start time and end time of the fault.
 Configured Links Number per Object
This parameter indicates the number of links configured on the port.
 Configured Links Type
This parameter indicates the type of the links configured on the port.

The information displayed in the alarm list is the same as that in the alarm page of the alarm
analysis tool.
11.3.7 IUB SCTP/SAAL Alarm Check

To display the diagnosis result of IUB SCTP/SAAL Alarm Check, click the IUB
SCTP/SAAL Alarm Check node on the navigation tree on the left, as shown in the following
figure:
This rule measures the fault rate of the IUB SCTP or SAAL links on the specified interface
board or SPU subsystem and lists the specific alarms.
On the BSC6900 V9R12, the involved alarm IDs are as follows:
'21542', '21541', '21531', '21532'
The measurement method is the same as that described in section 11.3.6"Fault Path Alarm
Check."
11.3.8 Fault Cell Alarm Check

To display the diagnosis result of Fault Cell Alarm Check, click the Fault Cell Alarm
Check node on the navigation tree on the left, as shown in the following figure:

This rule measures the fault rate of all cells on the specified port or SPU subsystem.
'22206', '22203', '22202', '22214'
If a fault alarm is generated on a NodeB, all the cells on the NodeB are regarded as faulty.
The measurement method is the same as that described in section 11.3.6"Fault Path Alarm
Check."
11.3.9 Port Alarm Check

To display the diagnosis result of Port Alarm Check, click the Port Alarm Check node on
the navigation tree on the left, as shown in the following figure:
This rule measures whether any fault alarm is generated on the specified port within the fault
period.
'21387', '21345', '21346', '21252', '21253', '21254', '21255', '21255', '21266', '21263', '21264',
'21267', '21270', '21272', '21273', '21274', '21282', '21283', '21285', '21311', '21312', '21313'
The list on the right displays the fault alarms, if any. The measurement method is the same as
that described in section 11.3.6"Fault Path Alarm Check."
11.3.10 SPU Brd Alarm Check

To display the diagnosis result of SPU Brd Alarm Check, click the SPU Brd Alarm Check
node on the navigation tree on the left, as shown in the following figure:

This rule measures whether any fault alarm is generated on the specified port within the fault
period.
'20256', '22835', '20241', '20242', '20243', '20272', '20250', '20251', '20233', '20257'
11.3.11 Config Info of SPU Subsystem

To display the diagnosis result of Config Info of SPU Subsystem, click the Config Info of
SPU Subsystem node on the navigation tree on the left, as shown in the following figure:
This list displays the configuration information on the specified SPU subsystem. The
parameters in the list are as follows:
 NodeB Num
This parameter indicates the number of NodeBs configured on the SPU subsystem.
 Config Cell Num
This parameter indicates the number of cells configured on the SPU subsystem.
 Active Cell Num(based on CCH)
This parameter indicates the number of activated cells on the SPU subsystem.
 Config IUB SAAL Num
This parameter indicates the number of IUB SAAL links configured on the SPU
subsystem.
 Config IUB SCTP Num

This parameter indicates the number of IUB SCTP links configured on the SPU
subsystem.
The configuration data is displayed in the list on the right and in the red-circled part on the
left.
11.3.12 IUCS Current Alarm Check

To display the diagnosis result of IUCS Current Alarm Check, click the IUCS Current
This rule measures whether any active alarm exists on the IUCS interface within the fault
period.
'20256', '22835', '20241', '20242', '20243', '20272', '20250', '20251', '20233', '20257', '21387',
'21345', '21346', '21252', '21253', '21254', '21255', '21255', '21266', '21263', '21264', '21267',
'21270', '21272', '21273', '21274', '21282', '21283', '21285', '21311', '21312', '21313', '21542',
'21541', '21531', '21532', '21505', '21501', '21506', '21502', '21503', '21504', '21521', '21551',
'21552', '21553', '21562', '21563', '21581', '21582'
11.3.13 IUCS all Alarm Check

To display the diagnosis result of IUCS all Alarm Check, click the IUCS all Alarm Check

This rule measures whether any associated alarm exists on the IUCS interface within the fault
period, and lists the alarm statistics and specific alarms.
'20256', '22835', '20241', '20242', '20243', '20272', '20250', '20251', '20233', '20257', '21387',
'21345', '21346', '21252', '21253', '21254', '21255', '21255', '21266', '21263', '21264', '21267',
'21270', '21272', '21273', '21274', '21282', '21283', '21285', '21311', '21312', '21313', '21542',
'21541', '21531', '21532', '21505', '21501', '21506', '21502', '21503', '21504', '21521', '21551',
'21552', '21553', '21562','21563', '21581', '21582'
11.3.14 IUPS Current Alarm Check

To display the diagnosis result of IUPS Current Alarm Check, click the IUPS Current
This rule measures whether any active alarm exists on the IUPS interface within the fault
period.
'20256', '22835', '20241', '20242', '20243', '20272', '20250', '20251', '20233', '20257', '21387',
'21345', '21346', '21252', '21253', '21254', '21255', '21255', '21266', '21263', '21264', '21267',
'21270', '21272', '21273', '21274', '21282', '21283', '21285', '21311', '21312', '21313', '21542',
'21541', '21531', '21532', '21505', '21501', '21506', '21502', '21503', '21504', '21521', '21551',
'21552', '21553', '21562','21563', '21581', '21582'
11.3.15 IUPS all Alarm Check

To display the diagnosis result of IUPS all Alarm Check, click the IUPS all Alarm Check

This rule measures whether any associated alarm exists on the IUPS interface within the fault
period, and lists the alarm statistics and specific alarms.
'20256', '22835', '20241', '20242', '20243', '20272', '20250', '20251', '20233', '20257', '21387',
'21345', '21346', '21252', '21253', '21254', '21255', '21255', '21266', '21263', '21264', '21267',
'21270', '21272', '21273', '21274', '21282', '21283', '21285', '21311', '21312', '21313', '21542',
'21541', '21531', '21532', '21505', '21501', '21506', '21502', '21503', '21504', '21521', '21551',
'21552', '21553', '21562','21563', '21581', '21582'
11.3.16 DSP UKPI List

To display DSP UKPI List, click the DSP UKPI List node on the navigation tree on the left,
as shown in the following figure:
This rule measures the KPIs of DSPs based on the UKPI file. The relevant parameters in the
list are as follows:
 DSPID
This parameter indicates the subrack ID, slot ID, and DSP ID.
 RRC Setup SuccRate(%)
This parameter indicates the RRC setup success rate, that is, the ratio of the number of
RRC setup successes on the DSP to the number of RRC setup attempts. The equation is

as follows: RRC Setup SuccRate = VS.RRC.SuccConnEstab.DSP /

VS.RRC.AttConnEstab.DSP. The value lower than 90% is highlighted in red.
 CS RAB Setup SuccRate(%)
This parameter indicates the CS RAB setup success rate, that is, the ratio of the number
of CS RAB setup successes on the DSP to the number of CS RAB setup attempts. The
equation is as follows: CS RAB Setup SuccRate = VS.CS.RAB.SuccEstab.DSP /
VS.CS.RAB.AttEstab.DSP. The value lower than 85% is highlighted in red.
 PS RAB Setup SuccRate(%)
This parameter indicates the PS RAB setup success rate, that is, the ratio of the number
of PS RAB setup successes on the DSP to the number of PS RAB setup attempts. The
equation is as follows: PS RAB Setup SuccRate = VS.PS.RAB.SuccEstab.DSP /
VS.PS.RAB.AttEstab.DSP. The value lower than 85% is highlighted in red.
The list on the right displays the KPI values in different periods.
11.3.17 IU UKPI List

To display IU UKPI List, click the IU UKPI List node on the navigation tree on the left, as
shown in the following figure:
If SCCP Setup SuccRate: VS.IU.SCCP.Tx.Con.Succ/VS.IU.SCCP.Tx.Con.Req is lower

than 90%, the value is highlighted in red. The numerals in the parentheses indicate
VS.IU.SCCP.Tx.Con.Succ and VS.IU.SCCP.Tx.Con.Req respectively. For other counters,
see the help of the performance measurement.
On the BSC6900 V9R12, the CNID parameter in the list indicates the internal ID that differs from the
ID in the configuration script. No mapping between internal IDs and IDs in the script is available
currently. Therefore, the diagnosis results in the IU UKPI List are incorrect for all V912 releases earlier
than V912SPC506.
The diagnosis result of this rule is for your reference only.
11.3.18 Fault Cell Rate by INT Port(UKPI)

To display the Fault Cell Rate by INT Port (UKPI) list, click the Fault Cell Rate by INT
Port(UKPI) node on the navigation tree on the left.

This rule is similar to Fault Cell Rate by INT Port(PERF), except that this rule measures the
fault cell rate based on the UKPI file. For details, see section 11.3.2"Fault Cell Rate by INT
Port(PERF)."
11.3.19 INT UKPI Display

To display the diagnosis result of INT UKPI Display, click the INT UKPI Display node on
This rule is similar to INT PERF List, except that this rule measures the statistics based on the
UKPI file. For details, see section 11.3.3"INT PERF List."
11.3.20 Fault Cell Rate by SPU(PERF)

To display the Fault Cell Rate by SPU(PERF) list, click the Fault Cell Rate by
SPU(PERF) node on the navigation tree on the left, as shown in the following figure:

fault rate by SPU subsystem based on the performance measurement. For details, see section
11.3.2"Fault Cell Rate by INT Port(PERF)."
11.3.21 Fault Cell Rate by SPU(UKPI)

To display the Fault Cell Rate by SPU(UKPI) list, click the Fault Cell Rate by SPU(UKPI)
statistics by SPU subsystem based on the UKPI file. For details, see section 11.3.2"Fault Cell
Rate by INT Port(PERF)."
11.3.22 SPU UKPI Display

To display the diagnosis result of SPU UKPI Display, click the SPU UKPI Display node on

This rule is similar to INT PERF List, except that this rule measures the statistics by SPU
subsystem based on the UKPI file. For details, see section 11.3.3"INT PERF List."
11.3.23 TOPN SR(UKPI)

To display the TOPN SR(UKPI) list, click the TOPN SR(UKPI) node on the navigation tree
on the left, as shown in the following figure:
This rule measures the SR rate, contribution rate, and KPIs of top 10 cells based on the CELL
KPI parameter in the UKPI file. You can view the diagnosis result of this rule and check
whether the KPIs are degraded by top 10 cells.
11.3.24 TOPN SR(PERF)

To display the TOPN SR(PERF) list, click the TOPN SR(PERF) node on the navigation
tree on the left, as shown in the following figure:

This rule measures the SR rate, contribution rate, and KPIs of top 10 cells based on the CELL
KPI parameter in the performance measurement. You can view the diagnosis result of this
rule and check whether the KPIs are degraded by top 10 cells.

12 Online Analysis
12.1 Introduction
Use the FMA to download the required data online, and then use the fault diagnosis tool and
performance measurement comparison tool to analyze the data.

Step 68 Choose Tools > Online Analysis Tool from the menu.
The Performance Compare Setting dialog box is displayed, as shown in the following
figure:

Step 69 Set BAM IP, User Name, Pwd, and Time correctly.
 The +/- Hours parameter indicates that the data N hours later or earlier than the entered
time is to be loaded.
 The Compare with the day offset parameter indicates the period in which the data is to
be compared.
− The value –1 indicates that the data is compared with the data in the same period in
yesterday.
− The value –2 indicates that the data is compared with the data in the same period in
the day before yesterday.
Step 70 Click Save.
The Progress dialog example dialog box is displayed, as shown in the following figure. Wait
for up to five minutes. The script, UKPI data, alarms, and performance measurement are
downloaded during this period. The EXP UKPI command is executed 20 seconds before any
time that can be exactly divided by five minutes to obtain the UKPI data. The UKPI data then
is downloaded through the FTP.
The following two pages are displayed after the data is downloaded:

Step 71 Set the time period correctly, and then click Analysis.
The diagnosis result is displayed.
For the performance measurement comparison tool, do as follows:

Click Load.
After the data is loaded, click the relevant counters on the navigation tree on the left to view
comparison results of the counters.

13 Operation Log Analysis
13.1 Introduction
FMA can parse and analyze all operation log for all MBSC versions, and including normal
operation log, CSV log, and BAK log as below:
 Run COL LOG: LOGTYPE=OPT_LOG-1 to collect the normal operation log
 Download the BAK log from OMU by FTP tool
 Run EXP LOG to collect the TXT or CSV log file
The FMA parses the operation log, saves the useful information as a CSV file, and defines
high risk commands. You can view and filter the commands by using Microsoft Office Excel.

Step 72 Refer to the Section 5.2 to create the project, and then import the operation log files as below:

There have three mode to parse:

Normal log: use the normal operation log to parse
Bak log: use the bak operation log to parse. This mode can be selected with ‘Normal mode’ at
same time. If the operation log is repeatedly in two mode log files, one operation log in BAK
mode file will be discarded.
Exp log: Run the EXP LOG to collect the CSV or TXT log and parse. If you select this mode
to parse, the ‘Normal log’ or ‘Bak log’ cannot be selected at same time.
Step 73 Click the Save button and get the following window:

FMA supports the following functions:

 Show All：displa all log
 Reverse：reverse the log, and then this type of log will be hided
 Hide LST/DSP OPlog: filter the LST and DSP commands, and these commands will
be hided
 Filter：filter by column
 Save：the log can be saved as csv file
In the bar status of FMA, the detailed number information of log will be displayed.

14 Comparison Between MML Scripts
14.1 Introduction
This function is applicable to the configuration scripts of all RNC versions (including V1, V2,
and V9). The FMA can be used to compare the configuration scripts of different RNC
versions. The configuration scripts, however, must be exported by the EXP CFGMML or
EXP INNERCFGMML command.
The FMA supports the following two comparison methods:
 Compare parameters. If a parameter and its values (multiple values included) are the
same in both scripts, it indicates that the parameter is consistent in both scripts.
 Compare command lines. Compare the commands (similar commands included) in both
scripts by using the Beyond Compare or similar function.
The following parameters will be ignored by FMA:
'SRN','SN','SSN','PN','PHB','DSCP','DPX','DSPN','BRDTYPE','IPADDR','MASK','NOD
EBNAME','NODEBID','REMARK','RTDESTMASK','NEXTHOP','RTDEST','DSTIP','D
STMASK','PEERPN','LOCIP1','PEERIP1','LOCIP2','PEERIP2','SCTPLNKN','SAALLN
KN','CARRYSR','CARRYSN','CARRYPN','CARRYVPI','CARRYVCI','TXTRFX',
'RXTRFX','DPX','DPC','NAME','SIGLKSX','SIGSLC','MTP3BLNKNAME','DPCT','M
TP3BRTNAME','ANI','ANT','PATHID','LSN','BT','CMCFCELLTYPE','CMMETHOD','
CMMEASTYPE','RABINDEX','SRBINDEX','TRAFFICCLASS','SUBFLOWINDEX','S
RBINDEX','CELLID','PSCRAMBCODE','SAC','NBIPOAMIP','AID','TYPE','TMI','IP','I
PINDEX','CELLNAME','LOCHINDEX','LOCELL','PEERIPADDR','BRDCLASS','NSA
P','LNKN','NCELLID','ANTENNALATITUDEDEGREE','MAXANTENNARANGE','A
NTENNAORIENTATION','PT','RNCID','NCELLRNCID'
In the scenario of upgrading or RNC, or the little variety of commands for two MML scripts,
recommend to use the Beyond Compare Tool to compare the MML scripts.

14.2.1 Comparing Parameters
Step 74 Choose MML > MML Compare from the menu, as shown in the following figure:

The MML Compare dialog box is displayed, as shown in the following figure:
Step 75 Choose two scripts to be compared.
The blue-circled part lists the versions and IDs of the relevant RNCs.
Step 76 Click the Parameter Mode tab.
The Parameter Mode tab page lists the following options:
 All Paras
All parameters are compared, including the global parameters, typical service
parameters, transmission parameters, and radio parameters.
 Global Paras
Global parameters are compared, for example, the parameters in all SET commands.
Typical service parameters are not compared.
 TYP Paras
Typical service parameters are compared, for example, the parameters in the ADD
TYPRAB SRB command.
 Switch Paras
Algorithm parameters are compared.
 Cell Paras
Cell parameters are compared.
 Node Paras
Node parameters are compared, for example, transmission parameters of NodeBs.

The comparison time depends on the size of scripts. For example, it takes about three minutes to
compare two 40 Mb scripts if you choose the All Paras option. Wait with patience.
Step 77 Click Run.

The comparison is displayed, as shown in the following figure:
 The black items indicate identical parameters.

 The blue items indicate the parameters that exist in one script only.
 The red items indicate the parameters with different values.
To extract the parameters of a command quickly, do as follows:
Right-click on the comparison result.
A shortcut menu is displayed, as shown in the following figure:
Choose Extract.
The Command Extract dialog box is displayed, as shown in the following figure:

Choose a command, and then click OK.

To display the inconsistent parameters quickly, do as follows:

Right-click on the comparison result.
 A shortcut menu is displayed, as shown in the following figure.
 Choose Display Red.

14.2.2 Comparing Commands

On the MML Compare page, click the Command Mode tab.
The Command Mode tab page lists the following three comparison options:
 Global Commands
Global commands are compared. Typical service parameters are not compared.
 TYP Commands
Typical service commands are compared.
 Cell Commands
Cell commands are compared. If the RNCID is the same in both scripts, choose all cells
or the same cells (multiple cells) in Cell1 and Cell2. If the RNCID differs in two scripts,
choose a reference cell in Cell1.
The comparison result is displayed, as shown in the following figure:
The MML comparison tool provided by the FMA enables you to quickly identify parameter
differences between the scripts of different RNCs. Therefore, the abnormal KPIs can be
located quickly.

15 MML&License Scan
15.1 Introduction
The FMA supports scanning the feature of RNC MML script, License (dat file), and compare
the feature between MML and License. The results of scan of MML and compare are saved in
EXCEL file.
Which feature can be included in MML scripts if you want to know, define the feature in
excel file. For example, the feature of PDCP Header Compression can be defined as: ‘ET
UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH-1;’ in excel
configuration file. FMA will scan the MML scripts to check the switch is opened or not, if
not, the feature will be set OFF.
FMA supports to display the features of License, and status.
FMA supports to compare the feature of MML scripts and License file. If the status of feature
between MML and License is not consistent, the feature will be denoted as RED color.
15.2 MML Scan Operation Guide

15.2.1 Feature Definition
All rules are in a file which type is xls, system read rules from here. If define the features of
MML scripts, open the V900R012Rules.xls or V900R013Rules.xls file. Orther versions are
same.
Rules can be format as below:
1, Boolean logic operate (support “and”, “or”, “not”, “bracket”)
 Single expression
 Function: It is familiar rule. It can calculate the value of the expression.
 Such as: ADD UNODEB: TnlBearerType=IP_TRANS;
 Describe: IP Transportation in Iub Interface.
 Complex expression
 Function: It make up of any Single expression and join up with operator and
parse by PRI. Software support nesting with any level. The PRI can be changed
by bracket. At last calculate the result of Complex expression.
 Such as: (SET UFRCCHLTYPEPARA: ImsChlType=HSDPA;) or (SET
UFRCCHLTYPEPARA: ImsChlType=HSPA;)
 Describe: IMS Signaling over HSPA
2, Extract the value of parameter

 Function: Scan the MML script and calculate the value of parameter
 Such as: SET SS7PATCHSWITCH:SWITCHPARAMETER8，
 Describe: calculate the value of SWITCHPARAMETER8 about SET
SS7PATCHSWITCH.
3, Mathematical operate (support +，-，*，/，&，|)
 Mathematical operate on the extract the value of parameter.
 Such as: (SET SS7PATCHSWITCH:SWITCHPARAMETER8;) & 0x0000100000
 Describe: At first extract the value of SET
SS7PATCHSWITCH:SWITCHPARAMETER8 and then “&” with
0x0000100000.
4, Function operate (support MAX()，MIN()，SUM())
 Function: Statistic the maximal、minimal of the expression, it can also statistic the
number occurrence in the MML script.
 SUM(STR IPCHK: CHKTYPE=MBFD;) Describe: statistic the number of
STR IPCHK: CHKTYPE=MBFD; occurrence in the MML script.
 MAX(ADD SCTPLNK: MTU;) Describe: the maximal of ADD
SCTPLNK: MTU;
 MIN(ADD SCTPLNK: MTU;) Describe: the minimal of ADD SCTPLNK:
MTU;
5, Complex Mathematical operate
 Mathematical operate on the extract the value of parameter.
 Such as: ((SET SS7PATCHSWITCH:SWITCHPARAMETER8;) &
0x0000100000) and (ADD IPPATH: PATHCHK=ENABLED;)
 Describe: At first calcuate ”SET SS7PATCHSWITCH:SWITCHPARAMETER8;”
and then ‘&’ with 0x0000100000, at last ‘and’ with the value of “ADD
IPPATH: PATHCHK=ENABLED;”
15.2.2 Operation Guide

Choose Tools > MML Scan from the menu.
After this function is opened, the FMA will read the rule file which saved in FMA\Config\
MMLAndLicenseScan. Choose the version as below:
And choose the rule which needs to scan:

Choose the path if RNC scripts:
Click Run:
The result is shown as below:
15.3 License Scan Operation Guide

Choose Tools > MML&License Scan from the menu.
Choose the License Scan TAB as below:

Input the License file (the license file can be downloaded from OMU by FTP tool, and ext is
dat) and result is shown as below:
15.4 MML and License Feature Compare Operation Guide

Choose Tools > MML&License Scan from the menu.

Choose the License Compare TAB page, and input the file directory of MML script and
License file. Click the Run button and get result to save as Excel file.
16 CHR&PCHR Analysis
16.1 Introduction
The CHR&PCHR and binary log can be parsed and analyzed by FMA tool, and version is
MBSC V911, V912 and V913. FMA supports the browsing of CHR&PCHR, classification of
fault of CHR and PCHR, statistic of error code and parameter.

FMA takes less than 1s to parse one CHR or CallFault log file, and about 2~3s for PCHR log
file. Efficiency of parsing is far quicker than other tool.
The maximum of log is 1,000,000 to parse for FMA. One CHR log file has about 10,000 logs,
and FMA can import and parse about 60 CHR log files at same time. But for DEBUG log, one
file has about 200,000 logs, and then FMA can only open about 4~5 DEBUG files
simultaneously.

16.2.1 Adapter
If parse the CHR&PCHR log, the adapter files should be provided for different patch version
of MBSC V911, V912 and V913. The adapter file can be gotten from product and list is
shown as below:
The five types of adapter file should be provided by product:

 WCDMA RNC CHR.xml：parameter definition for CHR&PCHR，about 300~400K
 logdb.xml：parameter value definition for CHR&PCHR, about 200~300K
 WCDMA RNC CHR.dat：point code definition for CHR, about 25~30M
 spu.err：SPU Error Code definition, about 300~400K。
 pfmid.dat：counter ID definition, about 600~700K
 asndll folder: provides the ASN DLL file to parse the RAB and other info in CHR log.
The size of folder is about 2~3M.
The name of adapter file must be same as list, if not, issue will be occurred. When get the
adapter files, the size and content of file should be checked whether it is right or not.
Under the directory (Config->CHR->RNC), new version should be created, such as
V900R011C00SPC720,, and then the adapter files must be save in this new path. When these
adapter files are used to parse firstly, the Log_x.txt files will be automatically created, and x
means the type of log.
16.2.2 CHR&PCHR Browse

Refer to the Section 5.2 to create a project to input one or more CHR&PCHR log files, and
choose right adapter version as below:

If load too many CHR log to parse, the Max Memory Size can be set, and max value is about
500M. If the memory size of PC is about 2G, and idle memory size is about 1G, and Max
Memory Size of CHR project is set as 500M, for CHR log of V211 version, the max number
of CHR log can be reached as more than 200.
Open the project and pop-up the following window:
Double-click any log in List window, and detailed information about this log will be
displayed in the right tree, and the detailed point information will be listed in the bottom
window as below:

16.2.3 Filter
FMA supports the filter function by condition. Select a page and right-click mouse, and
pop-up menu as below:
Select Filter and get the following dialog window.

The user can click Add button to add new condtion to filter, and click Mod button to
modify a condtion. Click Add button and pop-up the following:
The conditons are satisfied as below:

 Support +,-,*,/,>,<,>=,<=,enum，range，exist、notexist
 Support &&,||
 UeId[1:1].u[1:1,2,3,4].UEID == ["302610002140301", "302610002314609"]
 ulCpuId==["0x50a81081", "0x50a81002"]
 UeId[1:1].u[1:1,2,3,4].UEID==[NOTEXIST]
 UeId[1:1].u[1:1,2,3,4].UEID==[EXIST]
 CommonInfo.CommHeaderInfo.FastDormancyInfo[1:1].bitFastDormancyUserFlag
==[EXIST]
 (ulCpuId==0x50a81001)&&(CommonInfo.CommHeaderInfo.FastDormancyInfo[1:
1].bitFastDormancyUserFlag==[EXIST])
 ucFailRabNum==[0~1]
Choose a filter rule and click OK button to get result.
FMA support filter function by column. For the following window, the FMA support the filter
by column or by current value.
If choose the filter by column, the following dialog will be pop-up, and select one or more
value to filter. The result of filter will be displayed in new window.

16.2.4 Classification of Fault

Click the Fault TAB page in the left window, and classification of fault will be listed in the
fault tree.
For the classification of fault of CHR, the method is:
 If the Fault Type value is non-zero or non-empty, the log of CHR will be joined to
classify. The first content is RAB Traffic, the second is RAB Bear, the third is Fault
Type, the fourth is Fault Reason, the fifth is Interface Fault Reason, and the sixth is
CAC Fault Reason.
 If the Fault Type value is non-zero or non-empty, but the RAB Traffic or RAB Bear is
empty, the log will be classified as RRC fault.
For the classification of fault of PCHR, the method is:
 Calculate the parameter (<PARA name="bit2RabLossInd" length="2" type="4"
dll="GetTextByKeyName: abLossInd" />), if RabLossInd is not existed, and then
calculate:
<PARA name="ConnSetupAbnormInfo" type="16" tag="83" notuse="2">
<PARACHOICE>
<PARA name="ConnSetupAbnormInfo" length="1" type="0" notuse="2" />
<PARA name="Len" length="2" type="0" notuse="2" />
<PARA name="ConnSetupFailCauseChoice" length="1" type="0"

dll="GetTextByKeyName:FailCauseChoice" />
<PARA name="ConnSetupItfFailDesc" length="2" type="0"

dll="GetTextByKeyName:ItfFailDesc" />
<PARA name="ConnSetupErrorCause" length="4" type="0"

dll="GetTextByKeyRange:ErrorCause" />
</PARACHOICE>
</PARA>
If FailCauseChoice is existed, the value of FailCauseChoice will be set to Fault

Reason, and value of ItfFailDesc is set to Interface Fault Reason, and Fault Type
is set as 1, RAB Traffic and RAB Bear is set as empty. This log of PCHR is
classified as RRC fault. The value definition of Fault Type is same as that of CHR,
but the value definition of Fault Reason and Interface Fault Reason is not same
that of CHR. The value definition of Fault Reason is refer to < FailCauseChoice >
node in logdb.xml, and the value definition of Interface Fault Reason is refer to <
ItfFailDesc > node in logdb.xml.
 If the value of RabLossInd is 1 or 3, and then calculate:

<PARA name="RABAbnormInfo" type="16" tag="102" notuse="2">
<PARACHOICE>
<PARA name="RABAbnormInfo" length="1" type="0" notuse="2" />
<PARA name="Len" length="2" type="0" notuse="2" />
<PARA name="RabFailTime" length="4" type="0" />

<PARA name="RabFailCauseChoice" length="1" type="0"

dll="GetTextByKeyName:FailCauseChoice" />
<PARA name="RabItfFailDesc" length="2" type="0"

dll="GetTextByKeyName:ItfFailDesc" />
<PARA name="RabErrorCause" length="4" type="0"

dll="GetTextByKeyRange:ErrorCause" />
<PARA name="RABAbnormInfo_RNCId" length="2" type="0" />
<PARA name="RABAbnormInfo_CellId" length="2" type="0" />
</PARACHOICE>
The value of RabFailCauseChoice is set to Fault Reason, and value of

RabItfFailDesc is set to Interface Fault Reason. If value of RabLossInd is 1, the
Fault Type is set 7, and if value of RabLossInd is 3, the Fault Type is set 2.
The following window is shown as classification of fault.
If click the Cell or User TAB page, the TOP10 cell or user of fault will be listed in the tree
based on the number of all type of fault. If want to get the classification of fault of any cell or
user, right-click and choose the “ADD CELLID” or “ADD UEID” menu under the fault tree
as below:

16.2.5 Statistic of Point Code

1. Statistic of point code for all log, including CHR or other log
Click the Fault RAB page in left window as below:
FMA supports the two methods:

 Statistic of point code with CPUID: the point code will be classified by CPUID
firstly, and then distribution of point code of CPUID will be statistic.
 Statistic of point code with no CPUID
The following statistic types are supported by FMA:

The Code Statistic is for all log, and the other is based on the value of Fault Type. If choose
the Code Statistic by Fault RRC, the value of Fault Type is 1, and only when the value of
Fault Type of CHR log is 1, the log will be joined into classification.
The result of statistic with CPUID is shown as below, and numerator of the percent is the
number of log for the point code, and the denominator of the percent is total number of log
for the point code under the CPUID.
The result can be saved as CSV file and filter be column function is supported by FMA.

The value of column can be sorted by clicking on the list header.
2.Statistic of point code for result of filter or statistic

Right-click on the result window of classification, filter, or statistic, the following menu is
pop-up, and choose Code Statistic or Code Statistic with CPUID.
The following window is shown as result of statistic, and also right-click:

16.2.6 Statistic of Parameter

FMA provides the statistic of parameter for the current window, and get distribution of value
of parameter quickly.
Choose the log type and input the parameter(full name):

The name parameter must be full name, and this is provided by tool. Click the select button to
get the full name.
The result of statistic of parameter is shown as below:

16.2.7 SPU Error Code
The FMA supports the SPU error code to query. The user can right-click the following text
and select Query SPU Error Code, and explain dialog is pop-up.
The result is:

The user can double-click the ulCause in the CHR log tree as below:
The result is:

16.2.8 Statistic of CPU Usage

The CPU Usage of SPU and other board can be statistic and drawn as curve. The DEBUG log
should be load by project and right-click in the table as below and select the CPU Usage
Statistic menu.
The period step must be set, and default value is 1 second.
The max and average value of CPU usage during the period will be provided as below:

16.2.9 Trend Statistic

The function is statistic for the number of given logs by condition during the period. If the log
is satisfied with the given condition, and then the log will be added to statistic.
Right-Click as below and select Trend Statistic menu:
And the following dialog is pop-up.

The time should be set, and user can select the current time or access time for log. The
Current time comes from that in log table, that is time of print log. The Access time is the
access time for call log. The Start Time and End Time can be set by user, and the following
condition should be satisfied: The statistic poing must be less than 3600, that means, (the
period time from start to end)/period step must be less than 3600. If not, the error dialog will
be pop-up as below:

Click Add, Delete or Mod button to add, delete or modify the condition.
Input the following para:

 Stat Name；name of statistic
 Log Type：the log type, such as Performance User Log
 Sort by: the statistic will be classfied by this value, such as ulCpuId. If the value is
empty, the statistic will not be classfied.
 Condition：logical condtion, and same as Fiter. If the value is empty, the Condition will
be set as TRUE.
The following is statistic for RRC attempt time by SPU:
And the result is:

16.2.10 Filter,Statistic of Para and Trend in non-Project

In the project, the max CHR&PCHR number is limited. If analyze the more CHR log, such as
more than 1000, it is diffcult to analyze the CHR log under the project. The FMA supports the
Filter, Para and Trend statistic under non-project as below:
 Filter: The FMA can filter all CHR&PCHR log files in given path, and result is
saved in new folder. FMA can load the result (such as more than 1000 files) in one
project.
 Statistic of Para: The FMA can make statistic of para for all CHR&PCHR log files
in given path and result can be displayed quickly.
 Statistic of Trend: The FMA can make trend of CHR&PCHR same as Section
16.2.9, and result is saved in CSV file.
1) Filter
Click Tools->CHR&PCHR->Filter menu as below：
Set the path of filter and save, and condition is same as Section 16.2.3.

2) Statistic of Para
Click Tools->CHR&PCHR->Para Statistic Menu as following：
Set the path of statistic and condition is same as 16.2.6.

3) Trend
Click Tools->CHR&PCHR->Para Statistic menu as below:
Set the path of statistic and condition is same as 16.2.9.

17 NodeB XML2MML
The FMA can transfer the NodeB XML configuration to MML scripts, and then the user is
easy to browse the value of parameter. Before use this function, the LMT of NodeB must be
installed. The FMA use the file of LMT to parse the scripts.
Click the NodeB XML to MML menu as below:
And the dialog is:
Input the file path of NodeB scripts and version, and click Run button and then MML scripts
will be provided.
After input the file path, the version of scripts will be displayed in the left and upper.
There have two types of MML scripts. One provides the detailed descript of Para and Value,
and the other does not provide.

18 Contact Information
If you have any question, send an email to the project manager Zhang Xu (Notes ID:
00103773) or PO Ye Fei (Notes ID: 44671) of the FMA.
Your suggestions and requirements are highly appreciated.

Operation Guide To The FMA V1.51

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operation Guide To The FMA V1.51

Uploaded by

Copyright:

Available Formats

Document Code Product Name FMA

Intended Audience Internal Product Version V3.42

Prepared by GU Delivery Department Document Version V1.51

Operation Guide to the FMA

Prepared by GU Delivery Department Date 2011-8-27

2010-12-01 V1.0 Completed the first draft. Xu Zhijie (Employee ID:

2011-6-30 V1.5 1. Enhance the function of Xu Zhijie (Employee ID:

2019-6-20 Huawei Confidential Page 2 of 144

7 Performance Measurement Browsing.....................................................................................30

2019-6-20 Huawei Confidential Page 3 of 144

7.2.3 Query Performance Measurement..........................................................................................................34

9 Performance Measurement Comparison................................................................................57

10 Real-Time UKPI Monitoring...................................................................................................62

2019-6-20 Huawei Confidential Page 4 of 144

11.2.7 Obtaining Information of Neighboring Cell.........................................................................................81

13 Operation Log Analysis.........................................................................................................109

14 Comparison Between MML Scripts.....................................................................................111

2019-6-20 Huawei Confidential Page 5 of 144

2019-6-20 Huawei Confidential Page 6 of 144

2019-6-20 Huawei Confidential Page 7 of 144

2 Functions of the FMA Version

No. Type Function

1 Performance The FMA can be used to parse and compare performance

2019-6-20 Huawei Confidential Page 8 of 144

2019-6-20 Huawei Confidential Page 9 of 144

3 Application Scope and Download

The FMA is applicable to the following.

2019-6-20 Huawei Confidential Page 10 of 144

4.2 Get ESN

And ESN Code is:

The ESN Code can be empty.

2019-6-20 Huawei Confidential Page 11 of 144

4.3 Update License

And the following diag is:

Input the valid License Code, and click OK.

2019-6-20 Huawei Confidential Page 12 of 144

5.2 Operation Guide

Step 2 Input the Name and Version of project as below:

2019-6-20 Huawei Confidential Page 13 of 144

5.2.2 Open Project

Step 6 Select the project needs.

2019-6-20 Huawei Confidential Page 14 of 144

5.2.3 Modify/Delete Project

Step 9 Click the project name and modify the information.

2019-6-20 Huawei Confidential Page 15 of 144

5.2.4 Close Project

2019-6-20 Huawei Confidential Page 16 of 144

6.2 Operation Guide

2019-6-20 Huawei Confidential Page 17 of 144

You can open a compressed ZIP file or a decompressed alm_useralm_historyalarm.txt. If opening a

2019-6-20 Huawei Confidential Page 18 of 144

6.2.2 Associating Alarms with the MML Script

6.2.3 Filtering Alarms

2019-6-20 Huawei Confidential Page 19 of 144

The FMA also supports the following functions:

6.2.4 Highlighting Alarms

2019-6-20 Huawei Confidential Page 20 of 144

Step 19 Click OK.

6.2.5 Saving Alarms

2019-6-20 Huawei Confidential Page 21 of 144

6.2.6 Sorting Alarms by Type

Expand any alarm type.