Bsc6900 Umts LMT User Guide (v900r017c10 - 02) (PDF) - en

BSC6900 UMTS
V900R017C10
LMT User Guide

Issue
02
Date
2015-05-08
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2015-05-08)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
BSC6900 UMTS
LMT User Guide
About This Document
About This Document

Overview
This document describes the functions and relevant components of the BSC6900 Local
Maintenance Terminal (LMT). It also provides instructions for performing basic operation and
maintenance (OM) tasks of theBSC6900.
Product Versions
The following table lists the product version and the solution version related to this document.
Product Name
Product Version
Solution Version
BSC6900
V900R017C10
RAN17.1
Intended Audience
This document is intended for:
l
Network engineers
System engineers
Field engineers
Organization
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
2 Introduction to LMT
The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) to simplify operation and maintenance of the BSC6900. Using the LMT,
Issue 02 (2015-05-08)

ii
BSC6900 UMTS
LMT User Guide
About This Document
you can manage alarms, view message tracing results, monitor performance, and maintain
devices. You can also run man-machine language (MML) commands and view command results
on the LMT.
3 Operation Rights Management
This chapter describes principles of managing operation rights, user accounts, and command
groups.
4 Running MML Commands
This chapter describes how to run MML commands on the LMT for operation and maintenance
of the BSC6900.
5 Alarm/Event Management
This section describes how to use the LMT to manage BSC6900 alarms/events. Alarm/event
management helps you analyze alarms/events efficiently, thereby facilitating troubleshooting.
6 Log Management
This section describes how to use the LMT to manage the BSC6900 logs, which can be saved
in .txt and .csv files. Only user admin, ADMINISTRATOR-level users, and authorized
CUSTOM-level users can manage the logs.
7 Trace Management
This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 trace
tasks can be started simultaneously on the same LMT, and a maximum of 6 trace tasks can be
started simultaneously for the same parameter of a trace item. When OMU boards perform an
active/standby switchover, monitoring cannot be restarted until 30 minutes after the switchover.
8 Performance Monitoring
This chapter describes how to monitorBSC6900 performance. A maximum of 64 monitoring
tasks can be started simultaneously on the LMT. If OMU boards are switched over, performance
monitoring can be restarted 30 minutes after the switchover.
9 Device Panel
This chapter describes how to manage the BSC6900 using the device and emulation panels. You
can use these panels to query information about boards, ports, links, and alarms.
10 FMA
This function helps users handle network faults. It includes the following functions: Fault
Diagnosis, Hierarchical Delimitation and Information Collection. The fault diagnosis and
hierarchical delimitation functions analyze faults only within eight hours from the fault
rectification to the current time.
11 BSC Maintenance
This chapter describes how to maintain BSC equipment, back up and restore data, and implement
fast fault diagnosis.
12 FAQ
This chapter describes some frequently asked questions (FAQs) and the corresponding solutions.
Issue 02 (2015-05-08)

iii
BSC6900 UMTS
LMT User Guide
About This Document
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 02 (2015-05-08)

iv
BSC6900 UMTS
LMT User Guide
About This Document
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
Issue 02 (2015-05-08)
About This Document
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

vi
BSC6900 UMTS
LMT User Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Change History..............................................................................................................................1
2 Introduction to LMT.....................................................................................................................4
2.1 Configuration Requirements of the LMT PC.................................................................................................................6
2.2 Logging In to and Logging Out of the LMT..................................................................................................................8
2.3 Components of the LMT Main Page............................................................................................................................12
2.4 Obtaining Documentation Packages.............................................................................................................................15
2.5 File Manager.................................................................................................................................................................16
2.6 FTP Server....................................................................................................................................................................19
2.7 User-defined Command Group....................................................................................................................................21
2.8 LMT Software..............................................................................................................................................................23
2.8.1 Installing LMT Offline Tools....................................................................................................................................23
2.8.2 LMT Offline MML....................................................................................................................................................25
2.8.3 FTP Client..................................................................................................................................................................29
2.8.4 Convert Management System....................................................................................................................................31
2.8.5 Performance Browser Tool........................................................................................................................................32
2.8.6 TrafficRecording Review Tool..................................................................................................................................33
3 Operation Rights Management................................................................................................35

3.1 Concepts Related to Operation Rights Management....................................................................................................36
3.1.1 Principles of Operation Rights Management.............................................................................................................36
3.1.2 User Passwords..........................................................................................................................................................36
3.1.3 Command Groups......................................................................................................................................................37
3.1.4 User Types.................................................................................................................................................................38
3.1.5 Operation Rights........................................................................................................................................................38
3.1.6 Operation Time Limits..............................................................................................................................................39
3.2 Management of User Accounts....................................................................................................................................40
3.2.1 Creating an External User Account...........................................................................................................................40
3.2.2 Modifying an External User Account........................................................................................................................41
3.2.3 Deleting an External User Account...........................................................................................................................41
3.3 Management of User Passwords...................................................................................................................................42
3.3.1 Defining Login Password Policies............................................................................................................................42
Issue 02 (2015-05-08)

vii
BSC6900 UMTS
LMT User Guide
Contents
3.3.2 Querying Login Password Policies............................................................................................................................42

3.3.3 Changing the Password of the Active User Account................................................................................................42
3.3.4 Changing the Password of an External User Account...............................................................................................43
3.4 Management of Command Groups...............................................................................................................................43
3.4.1 Querying a Command Group....................................................................................................................................43
3.4.2 Renaming Command Groups....................................................................................................................................43
3.4.3 Changing Commands in a Command Group.............................................................................................................44
4 Running MML Commands........................................................................................................45

4.1 Concepts Related to MML Commands........................................................................................................................47
4.1.1 Introduction to MML Commands..............................................................................................................................47
4.1.2 Components of the MML Command Window..........................................................................................................48
4.1.3 Data Configuration Rights.........................................................................................................................................50
4.1.4 Data Configuration Rollback.....................................................................................................................................50
4.2 Running a Single MML Command..............................................................................................................................51
4.3 Batch Processing of MML Commands........................................................................................................................52
4.3.1 Immediate Batch Processing of MML Commands...................................................................................................53
4.3.2 Scheduled Batch Processing of MML Commands....................................................................................................54
4.3.3 Syntax Check.............................................................................................................................................................55
4.4 Setting MML Parameters..............................................................................................................................................56
4.5 Querying Data Configuration Modes...........................................................................................................................57
4.6 Querying Data Configuration Rights............................................................................................................................58
4.7 Obtaining Data Configuration Rights...........................................................................................................................58
4.8 Undoing/Redoing a Single Data Configuration Action................................................................................................59
4.9 Undoing/Redoing Multiple Data Configuration Actions.............................................................................................60
5 Alarm/Event Management.........................................................................................................62
5.1 Concepts Related to Alarm Management.....................................................................................................................63
5.1.1 Alarm Type................................................................................................................................................................63
5.1.2 Alarm Severity...........................................................................................................................................................64
5.1.3 Alarm-Event Type.....................................................................................................................................................64
5.1.4 Alarm Flag.................................................................................................................................................................65
5.1.5 Alarm Box.................................................................................................................................................................66
5.2 Managing Alarm Logs..................................................................................................................................................67
5.2.1 Setting Storage Limitations of Alarm Logs...............................................................................................................67
5.2.2 Querying Storage Limitations of Alarm Logs...........................................................................................................68
5.3 Managing Alarm Masking Conditions.........................................................................................................................68
5.3.1 Creating an Alarm Masking Condition.....................................................................................................................68
5.3.2 Deleting an Alarm Masking Condition.....................................................................................................................69
5.3.3 Querying an Alarm Masking Condition....................................................................................................................69
5.4 Managing the Alarm Masking Switch of Derived Alarms...........................................................................................69
5.4.1 Enabling/Disabling the Alarm Masking Switch of Derived Alarms.........................................................................70
5.4.2 Querying the Alarm Masking Switch of Derived Alarms.........................................................................................70
Issue 02 (2015-05-08)

viii
BSC6900 UMTS
LMT User Guide
Contents
5.5 Monitoring Alarms.......................................................................................................................................................70

5.5.1 Browsing Alarms/Events...........................................................................................................................................70
5.5.2 Querying Alarm/Event Logs.....................................................................................................................................71
5.5.3 Querying Suggestions on Alarm/Event Handling.....................................................................................................72
5.5.4 Querying Alarm/Event Configuration.......................................................................................................................73
5.5.5 Filtering Alarms/Events.............................................................................................................................................74
5.5.6 Setting Display Attributes for Alarms/Events...........................................................................................................74
5.5.7 Manually Clearing an Alarm/Event...........................................................................................................................77
5.5.8 Deleting Alarms/Events.............................................................................................................................................77
5.5.9 Refreshing the Alarm/Event Window.......................................................................................................................78
5.6 Managing the Alarm Box.............................................................................................................................................78
5.6.1 Querying Alarm Box Information.............................................................................................................................79
5.6.2 Querying the Number of Alarms of a Specific Severity............................................................................................79
5.6.3 Performing Operations on the Alarm Box.................................................................................................................79
5.6.4 Querying the Alarm Suppression Level of the Alarm Box.......................................................................................80
6 Log Management.........................................................................................................................81
6.1 Logs..............................................................................................................................................................................82
6.2 Setting Log Storage Limitations...................................................................................................................................82
6.3 Querying Operation/Security Logs...............................................................................................................................82
6.4 Obtaining Operation/Security Logs..............................................................................................................................83
6.5 Obtaining Running Logs..............................................................................................................................................84
6.6 Collecting Logs.............................................................................................................................................................85
7 Trace Management......................................................................................................................90
7.1 Concepts.......................................................................................................................................................................91
7.1.1 Tracing Principles......................................................................................................................................................91
7.1.2 Management of Tracing Operation Rights................................................................................................................92
7.1.3 Tracing Mode............................................................................................................................................................92
7.1.4 Tracing Specifications...............................................................................................................................................92
7.2 Basic Tracing Operations.............................................................................................................................................93
7.2.1 Browsing Traced Messages Online...........................................................................................................................93
7.2.2 Viewing the Interpretation of Traced Messages........................................................................................................95
7.2.3 Saving Traced Messages...........................................................................................................................................95
7.2.4 Browsing Traced Messages Offline..........................................................................................................................97
7.2.5 Managing Tracing Tasks...........................................................................................................................................98
7.2.6 Managing the Trace File............................................................................................................................................98
7.3 Device Commissioning.................................................................................................................................................99
7.3.1 Tracing OS Messages................................................................................................................................................99
7.3.2 Emergency Diagnosis..............................................................................................................................................100
7.3.3 Capturing Packets....................................................................................................................................................101
7.3.4 AC Tracing..............................................................................................................................................................106
7.3.5 DHCP Tracing.........................................................................................................................................................107
Issue 02 (2015-05-08)

ix
BSC6900 UMTS
LMT User Guide
Contents
7.4 UMTS Services...........................................................................................................................................................109

7.4.1 Tracing Messages on the Iu Interface......................................................................................................................109
7.4.2 Tracing Messages on the Iupc Interface..................................................................................................................111
7.4.3 Tracing Messages on the Iur Interface.....................................................................................................................113
7.4.4 Tracing Messages on the Iub Interface....................................................................................................................115
7.4.5 Tracing Messages on the Uu Interface....................................................................................................................117
7.4.6 Tracing MNCDT Messages.....................................................................................................................................119
7.4.7 Message Settings.....................................................................................................................................................121
7.4.8 Tracing UE Messages..............................................................................................................................................122
7.4.9 Tracing Cell Messages.............................................................................................................................................131
7.4.10 Tracing IOS Messages...........................................................................................................................................134
7.4.11 Tracing Iur-p Messages.........................................................................................................................................143
7.4.12 Tracing Messages on the Sr Interface....................................................................................................................145
8 Performance Monitoring..........................................................................................................147
8.1 Concepts.....................................................................................................................................................................148
8.1.1 Monitoring Principles..............................................................................................................................................148
8.1.2 Operation Rights Control.........................................................................................................................................149
8.2 General Operations.....................................................................................................................................................150
8.2.1 Browsing the Monitoring Results Online................................................................................................................150
8.2.2 Setting Chart Display Mode....................................................................................................................................150
8.2.3 Saving Monitoring Data..........................................................................................................................................151
8.2.4 Offline Browsing Monitoring Data.........................................................................................................................151
8.3 Common Monitoring..................................................................................................................................................152
8.3.1 Monitoring Board CPU/DSP Usage........................................................................................................................152
8.3.2 Monitoring Transmission Resources.......................................................................................................................153
8.3.3 Monitoring BERS....................................................................................................................................................158
8.3.4 Monitoring BER......................................................................................................................................................159
8.3.5 Monitoring Link Performance.................................................................................................................................159
8.4 UMTS Monitoring......................................................................................................................................................173
8.4.1 Monitoring Connection Performance......................................................................................................................173
8.4.2 Monitoring Cell Performance..................................................................................................................................184
8.4.3 Monitoring System Resources.................................................................................................................................195
8.4.4 Monitoring Iur-p Delay...........................................................................................................................................195
9 Device Panel...............................................................................................................................197
9.1 Device Panel Operations............................................................................................................................................198
9.1.1 Introduction to the Device Panel.............................................................................................................................198
9.1.2 Starting the Device Panel........................................................................................................................................198
9.1.3 Querying the Status of an E1/T1 Port......................................................................................................................199
9.1.4 Querying the CPU/DSP Usage................................................................................................................................199
9.1.5 Querying BSC Board Clock Status.........................................................................................................................200
9.1.6 Querying the BSC Board Information.....................................................................................................................201
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
Contents
9.1.7 Resetting a BSC Board............................................................................................................................................202

9.1.8 Switching Over BSC Boards...................................................................................................................................203
9.1.9 Querying the BSC Board Alarm..............................................................................................................................205
9.2 Emulation Panel Operations.......................................................................................................................................205
9.2.1 Introduction to the Emulation Panel........................................................................................................................205
9.2.2 Starting the Emulation Panel...................................................................................................................................206
9.2.3 Querying the Status of an E1/T1 Port......................................................................................................................207
9.2.4 Querying the CPU/DSP Usage................................................................................................................................208
9.2.5 Querying BSC Board Clock Status.........................................................................................................................208
9.2.6 Querying the BSC Board Information.....................................................................................................................209
9.2.7 Resetting a BSC Board............................................................................................................................................210
9.2.8 Switching Over BSC Boards...................................................................................................................................212
9.2.9 Querying the BSC Board Alarm..............................................................................................................................213
9.2.10 Querying the FE/GE Port Status............................................................................................................................214
9.2.11 Querying the Optical Port Status...........................................................................................................................214
9.2.12 Querying the DPU DSP Status..............................................................................................................................215
9.2.13 Querying Alarm LED Information........................................................................................................................215
10 FMA............................................................................................................................................217
10.1 Fault Overview.........................................................................................................................................................219
10.2 Fault Diagnosis.........................................................................................................................................................221
10.3 Hierarchical Delimitation.........................................................................................................................................230
10.4 Recovery Confirmation............................................................................................................................................233
10.5 Information Collection.............................................................................................................................................233
11 BSC Maintenance....................................................................................................................236
11.1 Backing Up Data......................................................................................................................................................237
11.2 Restoring Data..........................................................................................................................................................238
11.3 Batch Configuration.................................................................................................................................................239
12 FAQ............................................................................................................................................241
12.1 Browser-related FAQs..............................................................................................................................................242
12.1.1 Slow Responses in the Firefox Browser................................................................................................................242
12.1.2 LMT Colors Cannot Be Displayed........................................................................................................................242
12.1.3 Verification Code Cannot Be Displayed on the LMT Login Page........................................................................242
12.1.4 No Response When Clicking the Menu Bar on the LMT.....................................................................................243
12.1.5 How to Set the Browser Under Citrix Farm Networking......................................................................................244
12.1.6 Unable to Log In To LMT Because IE Default Security Level Is Too High........................................................248
12.1.7 Unable to Download or Install the Java or Flash Plug-in and Two File Manager Windows Displayed Windows IE8
or Any Later Version Is Used...........................................................................................................................................255
12.1.8 The Error "Certificate Invalid" Is Displayed During an HTTPS Login................................................................256
12.1.9 The Error 'Mismatched Address' Is Displayed During an HTTPS Login.............................................................265
12.1.10 File Manager Functions are Improperly..............................................................................................................267
Issue 02 (2015-05-08)

xi
BSC6900 UMTS
LMT User Guide
Contents
12.1.11 Message 'Class doesn't support Automation' Displayed in an IE Browser.........................................................269

12.1.12 Error Message"This user session already exists" Upon Login to LMT..............................................................270
12.1.13 The "Are You Sure You Want to Quit the Page" Dialog Box Is Displayed.......................................................271
12.1.14 Unclear Grids in the Tables in the MML Online Help........................................................................................271
12.1.15 The "App Center" Web Page Is Automatically Displayed When Firefox Is Used to Browse the LMT.............272
12.1.16 "Permission Denied" or "Access Denied" is Displayed When IE Is Used to Browse the LMT.........................272
12.1.17 MML Command Failed to Be Executed or No Response to Tracing Tasks After the Browser Is Upgraded to IE8
..........................................................................................................................................................................................274
12.1.18 Settings on the LMT Failing to Take Effective...................................................................................................275
12.1.19 LMT Login Window Being Stopped by the Browser.........................................................................................276
12.1.20 The LMT login page of a host NE or built-in NE fails to be opened..................................................................276
12.2 Java-related FAQs....................................................................................................................................................278
12.2.1 Help for Installing and Using the Java Plug-in......................................................................................................278
12.2.2 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE....................279
12.2.3 Tracing and Monitoring Functions Cannot Be Used.............................................................................................281
12.2.4 Chinese Characters Displayed in the Tracing and Monitoring Windows.............................................................285
12.2.5 LMT Fails to Function Properly during the tracing/monitoring/batch processing................................................287
12.2.6 Interfaces for Performing Tracing or Monitoring Tasks Blinking........................................................................290
12.2.7 Java Installation Fails............................................................................................................................................290
12.2.8 Changing Settings for the Next-Generation Java Plug-in Fails.............................................................................290
12.2.9 How to Handle a Web Page Error or Java Error Displayed on the LMT..............................................................294
12.2.10 Displaying the Java Security Warning................................................................................................................296
12.2.11 Failure in Verifying the Verification Code During the Login to the LMT.........................................................296
12.2.12 The Application Blocked by Security Settings Dialog Box Is Displayed When Batch Processing, Tracing,
Monitoring, or Device Maintenance Is Enabled...............................................................................................................298
12.2.13 What Do I Do If A Message Your Java version is out of date Is Displayed?.....................................................299
12.3 Other FAQs...............................................................................................................................................................299
12.3.1 Installing OS Patches.............................................................................................................................................299
12.3.2 Changing the Computer Time During the LMT Use Prohibited...........................................................................301
12.3.3 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding...............................................301
12.3.4 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously........................................304
12.3.5 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes the Web Pages to Turn
Blank.................................................................................................................................................................................305
12.3.6 Configuring the HTTPS Login Mode....................................................................................................................305
12.3.7 Unable to Save Tracking and Monitoring Data.....................................................................................................306
12.3.8 BTS Nodes Cannot Be Displayed Under Device Navigation Tree.......................................................................307
12.3.9 Alarm/Event Function Becomes Unavailable.......................................................................................................308
12.3.10 LMT Login Web Page Cannot Be Opened with the PC OMU Installed............................................................309
12.3.11 Slow Response During an LMT Login................................................................................................................310
12.3.12 Batch Execution of MML Commands Fails Because Some MML Commands Contain Invisible Carriage Returns
or Line Feeds....................................................................................................................................................................311
12.3.13 How to Handle Shortcut Key Invalidation..........................................................................................................311
Issue 02 (2015-05-08)

xii
BSC6900 UMTS
LMT User Guide
Contents
12.3.14 Tracing File Not Being Uploaded to the Specified Directory.............................................................................312

12.3.15 Error Dialog Box Displayed When Online Help Is Opened................................................................................312
12.3.16 Garbled Characters Displayed in the Chinese Names of Files in the File Manager and These Files Failing to Be
Removed...........................................................................................................................................................................312
Issue 02 (2015-05-08)

xiii
BSC6900 UMTS
LMT User Guide
1 Change History
Change History
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
02 (2015-05-08)
This issue includes the following changes.
Change Type
Function
change
Change Description
Adde
d
None.
Modif
ied
Added descriptions of the Working directory setting on the FTP

server. For details, see FTP Server.
Added descriptions of user name, password, and port settings. For
details, see Logging In to and Logging Out of the LMT.
Modified the specifications of the number of real-time monitoring
tasks. For details, see Browsing the Monitoring Results
Online.
Delete
d
Editorial
change
None.
None.
01 (2015-03-25)
This issue includes the following changes.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
1 Change History
Change Type
Function
change
Change Description
Added
None.
Modifi
ed
Optimized descriptions about the FMA function to make the

descriptions clearer and more user-friendly. For details, see the
following chapters.
l FMA
l Fault Overview
l Fault Diagnosis
l Hierarchical Delimitation
l Information Collection
Delete
d
Editorial
change
None.
None.
Draft A (2015-01-15)
Compared with Issue 04 (2014-12-30) of V900R016C00, this issue includes the following
changes.
Change Type
Function
change
Issue 02 (2015-05-08)
Change Description
Added
None.

BSC6900 UMTS
LMT User Guide
1 Change History
Change Type
Change Description
Modifi
ed
l Modified the recommended Java JRE version. For details, see

Configuration Requirements of the LMT PC.
l Added the precautions for logging in to the LMT using the
U2000 proxy. For details, see Logging In to and Logging Out
of the LMT.
l Added descriptions of FTP permissions and protocol type
supported by the FTP server. For details, see FTP Server.
l Added descriptions of right control. For details, see
Management of Tracing Operation Rights.
l Added log descriptions. For details, see Collecting Logs.
l Added packet parameter descriptions. For details, see
Capturing Packets.
l Added descriptions of the fault information collection period.
For details, see Information Collection.
l Modified descriptions of supported board types. For details,
see Resetting a BSC Board.
l Added the solution to garbled characters displayed in
Office2007 and later versions. For details, see Corrupted
Characters Appearing When the csv File Is Opened in
UTF-8 Coding.
l Added the solution to the unavailable alarm function. For
details, see Alarm/Event Function Becomes Unavailable.
Delete
d
Editorial
change
Issue 02 (2015-05-08)
None.
None.

BSC6900 UMTS
LMT User Guide
Introduction to LMT
About This Chapter

The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) to simplify operation and maintenance of the BSC6900. Using the LMT,
you can manage alarms, view message tracing results, monitor performance, and maintain
devices. You can also run man-machine language (MML) commands and view command results
on the LMT.
2.1 Configuration Requirements of the LMT PC
The computer on which the LMT is running is called the LMT PC. The LMT PC must meet
certain requirements of hardware, software, connection ports, and communication capability.
2.2 Logging In to and Logging Out of the LMT
This section describes how to log in to the LMT for operations and how to log out of it after the
operations are complete.
2.3 Components of the LMT Main Page
You can log in to the LMT using a web browser to perform operation and maintenance (O&M)
operations on the BSC6900. This section describes the main page of the LMT.
2.4 Obtaining Documentation Packages
This section describes how to query and obtain documentation packages of the corresponding
product version.
2.5 File Manager
The File Manager, a component of the LMT application, enables you to upload files from the
LMT to the OMU and download files from the OMU to the LMT. For example, you can use the
File Manager to obtain logs and upload data configuration files.
2.6 FTP Server
The FTP server, a component of the LMT Offline Tools, is used for uploading and downloading
software and license files.
2.7 User-defined Command Group
The User-defined Command Group is used to add commands to a specified command group so
that an admin user can add operation rights for rights-limited users.
2.8 LMT Software
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser Tool, and TrafficRecording
Review Tool.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
2.1 Configuration Requirements of the LMT PC

The computer on which the LMT is running is called the LMT PC. The LMT PC must meet
certain requirements of hardware, software, connection ports, and communication capability.
Hardware Requirements
Table 2-1 describes the hardware requirements of the LMT PC.
Table 2-1 Hardware requirements of the LMT PC
Item
Quantity
Recommended
Configuration
Minimum
Configuration
CPU
2.8 GHz or above
866 MHz
RAM
1 GB
512 MB
Hard disk
80 GB
10 GB
Display resolution
1024 x 768 or
above
1024 x 768
CD drive
Ethernet adapter
10/100 Mbit/s
10/100 Mbit/s
Other devices
5x1
Keyboard, mouse,
modem, audio
card, and speaker
Keyboard and
mouse
Software Requirements
Table 2-2 describes the software requirements of the LMT PC.
Table 2-2 Software requirements of the LMT PC
Item
Recommended Configuration
Operating system
Windows Vista/7, Windows Server 2003/2008

NOTE
If the LMT PC runs an operating system other than these ones,
compatibility issues occur. As a result, some functions of the LMT,
such as the File Manager function, may fail.
Default language of the

operating system
Issue 02 (2015-05-08)
Simplified Chinese or English

BSC6900 UMTS
LMT User Guide
Item
Recommended Configuration
Web browser
Internet Explorer (IE) 8, 9 or 10 (IE 8 recommended);

FireFox 10.X, 17.X and 24.X.
NOTE
l Set the security level of the Web browser to medium or low.
Otherwise, the LMT menus cannot be viewed.
l If IE8 or a later version is used, choose Tools > Compatibility
View Settings. In the displayed Compatibility View Settings
dialog box, select Display all websites in Compatibility
View.
l If the Firefox browser is used, set the attribute of
dom.disable_window_flip by performing the following
operations: Open the Firefox browser and enter about:config in
the address bar. Search dom.disable_window_flip in Search and
double-click dom.disable_window_flip to set the value to false.
Then, restart the brwoser. The default value of
dom.disable_window_flip is true.
Java plug-in called Java

Platform Standard Edition
Runtime Environment (JRE)
JRE 1.7.0.65 is recommended. Versions between JRE 1.7.0.0

and JRE 1.7.0.45 are not supported. Note that JRE 1.7.0.0 is
not supported but JRE 1.7.0.45 is supported.
NOTE
You can download the recommended JRE 1.7.0.65 version in the
LMT login window. To obtain other JRE versions, visit the official
website of Java.
After installing the JRE 1.7.0.65 version, modify default settings of
Java by following the steps provided in section 12.2.1 Help for
Installing and Using the Java Plug-in.
Flash plug-in called Adobe

Flash Player
Flash Player 11.1.102 is recommended.

NOTE
You can download the plug-in in the LMT login window.
NOTICE
l You are advised to run the LMT on a PC with the recommended configurations to ensure
stable operation.
l The LMT in the current version is compatible only with 32-bit operating systems and 32-bit
web browsers.
l When using the LMT, ensure that the IE window is zoomed at 100% level. Otherwise, the
layout of the LMT graphical user interface (GUI) may be abnormal. To check whether the
IE window is zoomed at 100% level, view the scaling icon at the lower right corner of the
IE window.
Requirements of Connection Ports

If a firewall is deployed between a PC and the LMT, before you use the PC to visit the LMT
through the Web, enable ports 80, 20, 21, and 443 of the firewall.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
NOTE
l Port 80 is the default Hypertext Transfer Protocol (HTTP) port, which is used for Web page browsing.
l Ports 20 and 21 are File Transfer Protocol (FTP) ports.
l Port 443 is the default Hypertext Transfer Protocol Secure (HTTPS) port, which is used for HTTPS
login mode.
Communication Capability Requirements

The LMT PC must support Transmission Control Protocol/Internet Protocol (TCP/IP) and meet
the requirements of effective bandwidth. Table 2-3 describes the effective bandwidth
requirements of the LMT PC.
Table 2-3 Effective bandwidth requirements of the LMT PC
Item
Protocol
Recommended
Configuration
Minimum
Configuration
Requirements of
effective bandwidth
HTTP
2 Mbit/s or higher
512 Kbit/s
NOTE
l The speed of web page browsing speed is highly dependent on bandwidth. An LMT PC with the
recommended configuration can speed up browsing, thereby improving your browsing experience. If
you use an LMT with the minimum configuration, you can use all LMT functions. The browsing speed,
however, will be relatively slow.
l Effective bandwidth indicates the bandwidth available for the LMT. If many programs compete with
the LMT for bandwidth resources, a serious delay occurs despite a bandwidth of 2 Mbit/s.
2.2 Logging In to and Logging Out of the LMT

This section describes how to log in to the LMT for operations and how to log out of it after the
operations are complete.
Context
l
You have installed the JAVA Platform Standard Edition Runtime Environment (JRE)
program before using the LMT. If no JRE plug-in is installed, a message is displayed when
you log in to the LMT, prompting you to install the plug-in. Follow the instructions to install
the plug-in. If the JRE plug-in on the LMT PC is not the latest version, a message is
displayed, prompting you to upgrade the plug-in version. In this case, you are advised to
uninstall the existing JRE plug-in and then install a new version. If you cannot log in to the
LMT after you upgrade the JRE program, restart the web browser and retry.
If the Java Update Needed popup is displayed when you log in to the LMT, select Update
(recommended) to install the latest version.
A maximum of 32 local users and EMS users can log in to the LMT.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
CAUTION
When the LMT is running, do not modify the system time and time zone. Otherwise, severe
errors may occur in the system. Close the LMT window before you modify the system time and
time zone.
NOTICE
l Do not use refresh the browser on the LMT. Refreshing the main page, you will be logged
out of the LMT. Refreshing the tracing or monitoring page, a message indicating a script
error will be displayed.
l If you log in to the LMT through the IE browser, do not modify any file folder properties.
Otherwise, the IE browser is automatically refreshed, and error occurs on the LMT.
l Before logging in to the LMT through the IE browser, enable the IE browser to support HTTP
1.1 as follows: In the IE browser, choose Tools > Internet Options > Advanced > HTTP
1.1 Setting and select Use HTTP 1.1. If the IE browser is configured with login to the LMT
through a proxy server, select Use HTTP 1.1 through proxy connection.
l Before logging in to the LMT in the Internet Explorer (IE) browser, perform the following
operations:
l Choose Tools > Internet Options in the IE browser and click the Privacy tab in the
Internet Options dialog box. On the Privacy tab page, move the slider in the Settings
field to the middle until Medium is displayed on the right of the slider. Then, click
Sites. The Per Site Privacy Actions dialog box is displayed. In the Address of Web
site text box, enter the IP address of each website that is allowed to use cookies, and click
Allow.
l You are also advised to perform the following operations: Choose Tools > Internet
Options in the IE browser and click the General tab in the Internet Options dialog box.
Clear the Delete browsing history on exit check box on the General tab page.
l If AVG Internet Security is installed on an LMT PC, the web shield function must be disabled.
Otherwise, a dialog box will be displayed, showing "Disconnected. Please log in again."
l The default policy to log in to the LMT can be specified by the WebLMT Login Policy
parameter in the SET WEBLOGINPOLICY command. The parameter can be set to any of
the following values. (1) COMPATIBLE(Compatible): Either HTTP or HTTPS can be
used to log in to the LMT. (2) HTTPS_ONLY(Https_only): Only HTTPS can be used to
log in to the LMT. (3) LOGIN_HTTPS_ONLY(Login_https_only): When HTTP is used
to log in to the LMT, HTTP is changed to HTTPS before login, then HTTPS returns to HTTP
after login. Data over HTTP is transmitted in plaintext and prone to disclosure. Therefore,
the value HTTPS_ONLY(Https_only) is recommended.
l If WebLMT Login Policy is set to HTTPS_ONLY(Https_only) and the LMT login policy
set on the U2000 GUI is HTTP, the U2000 will fail to log in to the LMT using the proxy
server.
Issue 02 (2015-05-08)

BSC6900 UMTS
LMT User Guide
Procedure
Step 1 Enter the LMT login page by using one of the following modes:
Mode
Mode
Description
Operation
Mode 1: direct
connection
The LMT directly

connects to the
OMU without using
any proxy server.
Type the external virtual IP address of the OMU in

the Address bar of the IE browser. Press Enter on
the keyboard, or click Go next to the Address bar to
enter the login window of the BSC6900.
NOTE
If another proxy server is already set, you need to add
OMU_IP to the IP addresses that do not use the proxy
server under Exceptions. Set the IP addresses under
Exceptions by using the following method: Choose
Tool > Internet Options on the tool bar of the IE browser.
In the Connection tab page, click LAN Settings. In the
displayed window, click Advanced. In the displayed
Proxy Settings window, specify an IP address that does
not use the proxy server under Exceptions. For example,
OMU_IP or U2000_IP.
Mode 2:
connection
through the
U2000 that is
configured as
the proxy server
The LMT connects

to the OMU through
the U2000 that is
configured as the
proxy server for the
browser.
NOTE
This mode is
recommended when
the U2000 proxy
server needs to be
used to connect to
the OMU.
Mode 3:
connection
through the
U2000 with
both IP
addresses
entered
The LMT connects

to the OMU through
the U2000 with IP
addresses of both
U2000 and OMU
entered in the
browser.
NOTE
This mode is used
only when the
explorer is
configured with a
proxy server, which
is not the U2000 and
cannot be changed.
Issue 02 (2015-05-08)
1. You can set the U2000 proxy server in the

browser by using the following method: Choose
Tool > Internet Options on the tool bar of the
browser. In the Connection tab page, click LAN
Settings. Then specify the IP address and port
number of the U2000 server in the Proxy server
area. The default port number is 8080.
NOTE
After the IP address and port No. of the U2000 proxy
server are specified, you need to select the Use the same
proxy server for all protocols option.
2. Type the external virtual IP address of the OMU

in the Address bar of the browser. Press Enter on
the keyboard, or click Go next to the Address bar to
enter the login window of the BSC6900.
Type "U2000_IP/OMU_IP/" (for example,
10.141.130.146/10.141.151.208/) or "http://
U2000_IP/OMU_IP/login.html" in the Address bar
of the IE browser. Press Enter on the keyboard, or
click Go next to the Address bar to enter the login
window of the BSC6900. Note that "/" must be
included in "U2000_IP/OMU_IP/" behind
"OMU_IP." If another proxy server is already set,
you need to add U2000_IP to the IP addresses that
do not use the proxy server under Exceptions.
NOTE
OMU_IP indicates the external virtual IP address of the
OMU and U2000_IP indicates the IP address of the U2000
server.

10
BSC6900 UMTS
LMT User Guide
NOTE
l When you are logging in to the LMT using the second or third method, settings on the U2000 and on the
NE side must be consistent with the setting mapping listed in the following table. Otherwise, the login fails.
l You can run the LST WEBLOGINPOLICY command to query the policy for login to LMT and data
transmission.
l For details about how to set the policy for logging in to the LMT on the U2000 GUI, see section Setting
Web LMT Options in U2000 Data Management User Guide.
U2000 Security Connection Mode
Policy for Login to LMT and Data

Transmission
Common Mode
Only COMPATIBLE(Both HTTP and

HTTPS) can be selected.
SSL Mode
Either COMPATIBLE(Both HTTP and

HTTPS) or HTTPS(HTTPS Only) can be
selected.
Common Mode and SSL Mode
COMPATIBLE(Both HTTP and

HTTPS), HTTPS(HTTPS Only), or
LOGINHTTPS(HTTPS for Login Only)
can be selected.
Step 2 Specify User Name, Password, and Verification Code.

l Set User Type to Local or EMS.
l If User Type is set to EMS, the user name and password need to be authorized by the U2000.
The default password for users emscomm and emscommneteco is ei*b+@b#6Nh(tS1j.
l If port 8080 is used as the U2000 proxy port, enter the user name and password of the proxy
server when you open the LMT mainpage, Trace, Monitor, Batch, or Device Maintenance
tab page. The default user name and password of the proxy server are proxyuser and
Changeme_123, respectively.
l If the Verification Code is illegible, click Refresh for a new code.
l It is recommended that you change the password at your first login and then change the
password every three months.
Step 3 Click Login.
NOTE
l Before logging in to the BSC6900 as an EMS user, you need to set up a connection between the
BSC6900 and the U2000 server.
l If the login fails, click Reset. Specify User Name, Password, and Verification Code again to log in.
If the login fails again, check whether the connection between the LMT and the OMU is normal.
Step 4 Optional: To lock the LMT window, click Lock in the top right corner of the LMT main page.
Step 5 To exit the LMT, click Logout in the top right corner of the LMT main page.
NOTE
After logout, the login interface for User type of Local is displayed. On this login interface, if you want
to re-log in to the LMT on the EMS, you must set User type to EMS.
Issue 02 (2015-05-08)

11
BSC6900 UMTS
LMT User Guide
NOTE
l HTTPS is the default mode. You can log in to the LMT through the HTTP Secure (HTTPS) mode. Based
on HTTP, HTTPS introduces SSL or TLS to ensure security.
l Before logging in to the LMT through HTTPS, configure the HTTPS login mode and certificate files by
referring to 12.3.6 Configuring the HTTPS Login Mode.
l In HTTPS mode, if you need to connect to the OMU with the U2000 as the proxy server, you are advised
to adopt mode 2. Visiting the OMU by adopting mode 3 takes four times the time taken by adopting mode
2.
l To log in to the LMT through HTTPS, enter https://the external virtual IP address of the OMU, for
example, https://10.141.115.219, in the Address bar of the browser.
l Correct errors displayed during the login by referring to 12.1.8 The Error "Certificate Invalid" Is
Displayed During an HTTPS Login and 12.1.9 The Error 'Mismatched Address' Is Displayed During
an HTTPS Login.
l After entering the HTTPS login page, which is the same as the HTTP login page, perform the same operations
for a login.
----End
2.3 Components of the LMT Main Page

You can log in to the LMT using a web browser to perform operation and maintenance (O&M)
operations on the BSC6900. This section describes the main page of the LMT.
GUI
Figure 2-1 shows the LMT main page.
Figure 2-1 LMT main page
Table 2-4 describes the components of the LMT main page.

Table 2-4 Components of the LMT main page
Issue 02 (2015-05-08)
Component
Description
Workspace
Provides the view of LMT function icons.

12
BSC6900 UMTS
LMT User Guide
Component
Description
Alarm/Event
You can query active alarms, alarm logs, and alarm configuration
on this tab page. For details, see 5 Alarm/Event Management.
Batch
You can run man-machine language (MML) commands in batches

on this tab page. For details, see 4.3 Batch Processing of MML
Commands.
Trace
You can manage message tracing tasks on this tab page. For details,
see 7 Trace Management.
Monitor
You can monitor performance data on this tab page. For details, see
8 Performance Monitoring.
Device Maintenance
You can maintain the device panel on this tab page. For details, see
9 Device Panel.
FMA
You can use this function to handle network faults. It includes the
following functions: 10.2 Fault Diagnosis, 10.3 Hierarchical
Delimitation and 10.5 Information Collection.
MML
You can run MML commands on this tab page. For details, see
4.1.2 Components of the MML Command Window.
Progress
You can view the progress of a task on this tab page. eGBTS does
not support this function.
NOTE
To display the Progress tab page, click Progress on the toolbar. Then,
double-click an entry to view the detailed information in the displayed
Progress Management dialog box.
Issue 02 (2015-05-08)
FTP Tool
You can click it to download the executable application file

SFTPServer.exe. For details, see 2.8.3 FTP Client and 2.6 FTP
Server.
Password
You can click it to change the password of the current user. After
changing the password, use the new password when logging in to
the LMT again.
User-defined
Command Group
You can click it to add commands to a specified command group

so that an admin user can add operation rights for rights-limited
users. For details, see 2.7 User-defined Command Group.
Obtain
Documentation List
You can click it to obtain the documentation packages of the

corresponding product versions. For details, see 2.4 Obtaining
Documentation Packages.

13
BSC6900 UMTS
LMT User Guide
Component
Description
System Settings
You can click it to modify the language, auto lock time, and path
for saving result files.
l Language Setting: You can select a language as required. After
setting a language successfully, you can enter texts in the
selected language on the LMT. The system language of the
LMT, however, does not change.
l Auto Lock Time(s): You can specify a time period as required.
If there are no mouse or keyboard operations during the
specified time period, the LMT automatically goes to the locked
page. The setting prevents unauthorized users from using others'
accounts to perform unauthorized configuration and
maintenance.
l Result File Save Path: You can specify a path for saving
operation result files. The default path is C:\Web LMT\MBSC
\output.
File Manager
You can click it to upload files from the LMT to the OMU and
download files from the OMU to the LMT. For details, see 2.5 File
Manager.
About
You can click it to display the current version of the LMT.
Lock
You can click it to lock the current operation page for security
purposes.
NOTE
l After you click Lock on the toolbar, the LMT is locked.
l You can click in the blank area on the web page or press Enter, type
the password, and then click OK or press Enter to log in to the LMT
workspace again.
Logout
You can click it to log out the current user without exiting from the
LMT. Logout of one user facilitates login of another user.
Online Help
The LMT provides the following two types of online help:
l
Online help system
MML help
Table 2-5 describes the contents and startup method of the LMT online help.
Issue 02 (2015-05-08)

14
BSC6900 UMTS
LMT User Guide
Table 2-5 Description of LMT online help

Name
Content
Startup Method
Online
help
system
Provides the
following
information:
If the Microsoft Internet Explorer is used:
l LMT online
help
l In a displayed dialog box on the LMT, press F1 to display

help information about the dialog box.
l Alarm
reference
If the FireFox Explorer is used, press Help on the LMT main

page to display online help information.
l On the LMT main page, press F1 or click Help to display

online help information.
l Event
reference
MML
help
Provides the
following
information
about each MML
command:
Type an MML command in the Command Input field. Press

Enter or click Assist, and then click the Help Information
tab. Help information about the command is displayed on the
Help Information tab page.
l Command
function
l Note
l Parameter
l Example
l Output
description
(for query
commands
only)
2.4 Obtaining Documentation Packages

This section describes how to query and obtain documentation packages of the corresponding
product version.
Startup Method
On the toolbar of the LMT, click Obtain Documentation List.
GUI
l
Library Name: Name of a documentation package of the current product version.
Product Version: Current product version number.
Library Version: Version number of the documentation package of the current product
version.
Available at support.huawei.com:
Issue 02 (2015-05-08)

15
BSC6900 UMTS
LMT User Guide
Yes indicates that the documentation package has been released globally, and you can
obtain it from http://support.huawei.com.
No indicates that the documentation package has not been released at http://
support.huawei.com and you can contact Huawei engineers to obtain it.
Function
You can use either of the following methods to download documentation packages:
l
Search for required documentation packages at http://support.huawei.com and download

them.
In the Obtain Documentation List dialog box, click Export. Then, double-click the
exported .hdxi file, search for required documentation packages at http://
support.huawei.com, and download them.
NOTE
Before using this function, ensure that:

l You have obtained the account information for visiting http://support.huawei.com and can visit
the website successfully.
l (For initial use only) You have downloaded the HedEx Lite from the homepage of http://
support.huawei.com to your PC and the HedEx Lite is running properly.
2.5 File Manager

The File Manager, a component of the LMT application, enables you to upload files from the
LMT to the OMU and download files from the OMU to the LMT. For example, you can use the
File Manager to obtain logs and upload data configuration files.
Startup Method
On the toolbar of the LMT, click File Manager.
NOTE
Users' operation rights to the File Manager depend on their rights settings. For descriptions of the operation
rights, see 3.1.5 Operation Rights.
l ADMINISTRATOR-level and admin-level users have full operation rights to the File Manager.
l Users at other levels can only use the File Manager to download files. They are not authorized to upload or
delete files.
GUI
Figure 2-2 shows the window of the File Manager.
Issue 02 (2015-05-08)

16
BSC6900 UMTS
LMT User Guide
Figure 2-2 File Manager window
Table 2-6 describes the components of the File Manager window.

Table 2-6 Components of the File Manager window
Number
Component
Description
Path switch area
Directly navigates to a file folder or file.
File navigation tree
Displays files on the OMU in a navigation tree.
File list
Provides detailed information about files on the

OMU.
File processing area
Provides buttons for processing files.
Task list
Displays task processing information about files.
Path Switch Area

This area is used to directly navigate to a file folder or file. You can type the path of a required
file or file folder in the Rapid Positioning field, and press Enter or click Go to navigate to the
required path.
NOTE
l You can only type a path under the root directory on the File Manager server (for example, /bam/common/
log).
l A slash (/) in front of the root directory is optional.
File Navigation Tree

This area displays all directories that users can view and process on the server. When you rightclick on a selected folder, a shortcut menu containing the following choices is displayed:
l
Issue 02 (2015-05-08)
Refresh Whole Folder Tree:

17
BSC6900 UMTS
LMT User Guide
Choose Refresh Whole Folder Tree to refresh the navigation tree so that it displays the
latest directory organizations.
l
Set Search Criteria:

When you choose Set Search Criteria, the Set Search Criteria dialog box is displayed,
as shown in Figure 2-3. Select required search criteria, enter details about the selected
search criteria, and click Confirm.
Figure 2-3 Set Search Criteria dialog box
Modified time: You can specify a time from the year 2000 to 2038. If both Start
time and End time are set, End time must be later than Start time.
Files can be searched by File name. The file name has a maximum of 50 bytes containing
only English letters, numbers, dots, and underscores.
NOTE
l For easy differentiation, the icon of the folder for which the search criteria has been set is
displayed as
l After the search criteria are applied, only files meeting the search criteria under the folder are
displayed in the File Manager.
l The search criteria take effect only for the current folder, not for its sub-folders.
l If no search criteria are selected, after you click Confirm or Delete Search Criteria, all files
will be displayed.
Delete Search Criteria: Choose Delete Search Criteria to delete the search criteria set
for a folder.
File List
This area displays files in a selected folder.
NOTE
Only files meeting specific search criteria are displayed under a folder that is configured with search criteria.
You can select a file, right-click it, and choose Refresh, Upload, Download, or Delete from
the shortcut menu.
File Processing Area

This area provides the following file processing buttons.
Issue 02 (2015-05-08)

18
BSC6900 UMTS
LMT User Guide
Refresh:
Refreshes the list of files under the current folder.
Upload:
Uploads a selected file from the LMT PC to the OMU.
Download:
Downloads a selected file from the OMU to the LMT PC. If the directory is specified before
the download, the selected file is downloaded to the preset directory.
Delete:
Deletes a selected file.
Directory:
Changes the target folder for saving a downloaded file. If the directory is specified before
the download, the selected file is downloaded to the preset directory.
NOTE
If a target directory has been specified and the File Manager has been running before the target directory is
specified, the target directory for saving downloaded files does not change.
When the bandwidth is 2 Mbit/s, you are advised to concurrently download a maximum of 100 files and upload
a maximum of 10 files.
Task List
This area displays information about current tasks. You can perform the following operations
on the tasks:
l
Clear Finished Task:

Right-click the blank area in the task list and choose Clear Finished Task from the shortcut
menu to clear all finished tasks from the task list.
Clear Current Task:

Select a task, right-click it, and choose Clear Current Task from the shortcut menu to
remove the task from the task list.
Pause Current Task:

Select an ongoing upload/download task in the task list, right-click it, and choose Pause
Current Task from the shortcut menu to suspend the current upload/download task.
Continue Current Task:

Select a suspended upload/download task in the task list, right-click it, and choose
Continue Current Task from the shortcut menu to resume the upload/download task.
Set Display Columns:

Right-click the blank area in the task list, choose Set Display Columns from the shortcut
menu, and select information to display in the submenu.
2.6 FTP Server

The FTP server, a component of the LMT Offline Tools, is used for uploading and downloading
software and license files.
Issue 02 (2015-05-08)

19
BSC6900 UMTS
LMT User Guide
Startup Method
To start the FTP server, perform the following operations:
l
Click FTP Tool on the Toolbar of the LMT to download the executable application file
SFTPServer.exe. Then, double-click the executable file to start the FTP server.
NOTE
l If the FTP server is started for the first time, an FTP password config dialog box is displayed, prompting
you to modify the password of the FTP server. In the dialog box, enter the initial password hwbs@com,
and enter and confirm a new password.
l Users who log in to the LMT through a proxy server cannot use the FTP server.
l When FTP server uses encrypted transmission, it supports TLSV1.0, TLSV1.1, and TLSV1.2 protocol types.
If these protocol types are not specified as the SSL protocol type, the FTP client cannot be properly connected
to the FTP server.
GUI
Figure 2-4 shows the FTP server configuration dialog box.
Figure 2-4 FTP server configuration
Table 2-7 describes the components of the FTP server configuration dialog box.
Table 2-7 Components of the FTP server configuration dialog box
Issue 02 (2015-05-08)
Component
Description
User name
Specifies the user name for logging in to the FTP server. By default,
the user name is admin.An operator account added by running the
ADD OP command has FTP permissions.
Password
Specifies the user name for logging in to the FTP server. By default,
the password is hwbs@com.
20
BSC6900 UMTS
LMT User Guide
Component
Description
Working directory
Specifies the working directory of the FTP server.

NOTE
When using the FTP client, you are only allowed to access files under the
directory.
When setting Working directory, ensure that no sensitive information is
saved in the specified directory or the parent path of the FTP server installation
directory is not specified as Working directory.
Port number
Specifies the number of the port used by the FTP server to lawfully
intercept the information on the network.
NOTE
To query the port number, run the LST FTPSSRV command and obtain the
setting for the Command Port of FTPS Server. If an incorrect port number
is used, the LMT cannot be connected to the FTP server.
Thread number
Specifies the number of clients that can be connected to the FTP

server concurrently.
FTP Permissions
Local operators have FTP permissions.
l
Administrator-level operators: read and write permissions of log file directories and data
file directories and read permission of software files;
Operator-level operators: read permissions of log file directories, data file directories, and
software file directories;
Common-operator-level operators: read permissions of log file directories and data file
directories;
Guest-level operators: read permission of data file directories;
Custom-level operators: FTP permissions of guest-level operators and permissions of

MML command directories.
2.7 User-defined Command Group

The User-defined Command Group is used to add commands to a specified command group so
that an admin user can add operation rights for rights-limited users.
Startup Method
On the toolbar of the LMT, click User-defined Command Group, as shown in Figure 2-5.
Figure 2-5 Starting the User-defined Command Group
Issue 02 (2015-05-08)

21
BSC6900 UMTS
LMT User Guide
NOTE
Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users are allowed to perform this
operation.
If an authority-limited user performs this operation, an error message will be displayed, indicating an operation
failure.
GUI
Figure 2-6 shows the User-defined Command Group dialog box.
Figure 2-6 User-defined Command Group dialog box
Table 2-8 describes the components of the User-defined Command Group dialog box.
Table 2-8 Components of the User-defined Command Group dialog box
No.
Component
Description
Command group
selection area
Used to select a command group ranging from G_15

to G_31.
Authorization item
area
Displays all MML commands and encapsulated GUI

commands.
NOTE
All items under *GUI Authorization Items are marked
with * to distinguish them from MML commands.
Issue 02 (2015-05-08)

22
BSC6900 UMTS
LMT User Guide
No.
Component
Description
Button for adding

authorization items
Used to add the selected commands in the left pane

to the right pane.
NOTE
The command hierarchy in the right pane is the same as that
in the left pane.
To improve operation efficiency, you are advised to add less
than 1024 commands at a time.
Button for deleting

authorization items
Deletes the selected commands from the right pane.
Options for displaying

or hiding authorization
items
Display authorization items of MML commands.:

Displays or hides authorization items of MML
commands.
Display authorization items of the GUI function.:
Displays or hides authorization items of MML
commands.
Authorization item
addition area
Displays the commands to be added to the current

command group.
Apply or Cancel
button
Apply: Adds all the commands in the right pane to

the current command group.
Cancel: Abandons previous operations on the current
dialog box and closes it.
2.8 LMT Software

The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser Tool, and TrafficRecording
Review Tool.
2.8.1 Installing LMT Offline Tools

This section describes how to install the LMT Offline Tools on the LMT PC.
Prerequisites
l
A valid serial number for the LMT software has been obtained.
The PC for installing the LMT Offline Tools complies with the specifications described in
2.1 Configuration Requirements of the LMT PC.
When the LMT Offline Tools of the current version have been installed:
If the LMT Offline Tools of a later version is required, install it directly.
If the LMT Offline Tools of an earlier version is required, uninstall the current version,
install the earlier version, and reinstall the current version.
These operations do not apply to patch versions of the same R version.
Issue 02 (2015-05-08)

23
BSC6900 UMTS
LMT User Guide
Procedure
l
Using an installation CD-ROM

1.
Log in to the LMT PC as an administrator.
2.
Insert the installation CD-ROM into the CD-ROM drive.

The setup program runs automatically.
If the setup program fails to run automatically, double-click setup.bat or
setup.vbs in the installation directory of the CD-ROM.
3.
Select an installation language, and click OK. The HUAWEI Local Maintenance
Terminal is displayed.
4.
Click Next. A dialog box is displayed, prompting you to read the copyright notice.
5.
Read the software certificate declarations. If you accept the agreement terms, select
I accept these terms, and click Next. A dialog box is displayed, prompting you to
specify the installation path. If you do not accept the agreement terms, click Cancel
to quit the installation.
6.
Use the default installation path or specify a custom installation path, and click
Next.
NOTE
The default installation path is D:\HW LMT.

l If the LMT of another version or network element (NE) has been installed, the installation
path is that of the original LMT software and cannot be changed.
l To change the installation path, you must uninstall the existing LMT software.
If the LMT software is running, a Warning dialog box is displayed. Click Yes to enable the
system to automatically exit the LMT. If you click No, stop the LMT manually.
7.
Select the components to be installed and click Next. You are advised to select all
components. A dialog box is displayed for entering the CD-KEY.
8.
Enter the CD-KEY and click Next. A dialog box is displayed, prompting you to
confirm the installation.
9.
Confirm the installation information and click Next. A dialog box is displayed,
displaying the file copy progress.
When all required files are copied, a dialog box is displayed, displaying the progress
of component initialization. When all the programs are installed, a dialog box is
displayed, indicating that the installation is complete.
10. Click Finish.

NOTE
When the installation is complete, the LMT Service Manager starts automatically.
Using the installation package of the LMT Offline Tools

Contact Huawei engineers to obtain the installation package of the LMT Offline Tools from
http://support.huawei.com/carrier/#click=main3 and enter BSC6900 in the search
window. Then, download the required software version.
After downloading the LMT Offline Tools, use Hash values to check the integrity of the
LMT Offline Tools by performing the following steps:
1.
Issue 02 (2015-05-08)
Download the Hash compressed package ("Product Version Number Hash List.rar")
from the path for obtaining the installation package of the LMT Offline Tools.
Decompress the Hash compressed package to obtain the Product Version Number
24
BSC6900 UMTS
LMT User Guide
Hash List.mht file. Then, open this file to obtain the Hash value for the installation
package of the LMT Offline Tools. Obtain the Hash value from the SHA-256 column,
as shown in Figure 2-7.
Figure 2-7 Hash value for the installation package of the LMT Offline Tools
2.
Contact Huawei engineers to obtain the Hash value calculation tool from http://
support.huawei.com/carrier/#click=main3 and enter hashmyfiles in the search
window. Then, download the Hash value calculation tool hashmyfiles-1.8.5.rar. If
the language of the displayed window is not in the target language, select the target
language in the upper plane.
3.
Decompress hashmyfiles-1.8.5.rar to obtain HashMyFiles.exe, run

HashMyFiles.exe, and choose file > Add Files. In the displayed dialog box, select
the installation package of the LMT Offline Tools. The calculated Hash value is
displayed in the SHA-256 column, as shown in Figure 2-8.
Figure 2-8 Hash value calculated by the Hash value calculation tool
4.
Compare the Hash values obtained in Step 1 and Step 3. If the Hash values are the
same, the installation package of the LMT Offline Tools is complete and you can
continue subsequent operations. If the Hash values are different, contact Huawei
engineers.
----End
2.8.2 LMT Offline MML

The LMT offline MML tool, a component of the LMT Offline Tools, enables users to use a web
browser to perform the following offline operations: use MML functions, view MML
commands, prepare MML scripts, and view LMT Online Help of the required version.
Introduction to the LMT Offline MML Server

This section describes how to start the LMT offline MML server and the dialog box of the LMT
offline MML server.
Startup Method
To start the LMT offline MML server, choose Start > All Programs > HUAWEI Local
Maintenance Terminal > WebLMT OffLine MML on an LMT PC.
Issue 02 (2015-05-08)

25
BSC6900 UMTS
LMT User Guide
GUI
Figure 2-9 shows the dialog box of the LMT offline MML server.
NOTE
If the LMT offline MML server has been started and minimized, double-click the
tray of the LMT PC to display the dialog box of the LMT offline MML server.
icon on the system
Figure 2-9 WebServer dialog box
Table 2-9 describes the components of the WebServer dialog box.

Table 2-9 Description of the LMT offline MML server
Component
Description
Routine tab page
Displays the status of the LMT offline MML server.

NOTE
l Click Hide to minimize the LMT offline MML server to the system tray
of the LMT PC.
l Click Stop to stop the LMT offline MML server.
l Click Start to start the LMT offline MML server.
l Click Open Browser to display the login window of the LMT offline
MML tool.
Config tab page
Configures the server port.
About tab page
Displays information about the LMT offline MML tool.
Logging In to and Out of the LMT Offline MML Tool

This section describes how to log in to the LMT offline MML tool and how to exit from it.
Issue 02 (2015-05-08)

26
BSC6900 UMTS
LMT User Guide
Prerequisites
The LMT offline MML server has been started.
Procedure
Step 1 Install and start the LMT offline MML tool on the LMT PC.
Step 2 Enter http://127.0.0.1:Port into the address bar of the web browser. The login window of the
LMT offline MML tool is displayed.
NOTE
l Port specifies the port number of the LMT offline MML server. The default port number is 810.
l You can change the default port number on the Config tab page of the server. The new port number
takes effect only after the LMT offline server is restarted.
Step 3 Specify OMType, Version, and Pattern in the login window and click Login.
NOTE
l To switch display language between English and Chinese, click the language-switching button at the
top right corner of the login window.
l To restore the default setting used during installation, click Reset.
Step 4 To exit from the LMT offline MML tool, click Logout at the top right corner of the LMT main
page.
----End
Introduction to the LMT Offline MML Window

When you use a web browser to log in to the LMT offline MML, you can view MMLs, make
MML scripts, and obtain the LMT online help. This section describes the LMT offline MML
window.
GUI
Figure 2-10 shows the LMT offline MML window.
Issue 02 (2015-05-08)

27
BSC6900 UMTS
LMT User Guide
Figure 2-10 LMT offline MML window
Table 2-10 describes the components of the LMT offline MML window.
Table 2-10 Components of the LMT offline MML window
Issue 02 (2015-05-08)
Component
Description
Navigation Tree
Displays all MML commands. When you double-click an MML

command, the MML command is displayed in the Command
Input field.
Search
Uses keywords to search for MML commands.
Operation Record tab

page
Displays commands that have been run.
Help Information tab

page
Displays help information about MML commands.
Manual editing area
Displays manually input MML commands and their parameters.
History Command
field
Displays all commands executed during the current login and

relevant parameters.
Command Input field
Displays all the MML commands available on the system in the

drop-down list. You can select an MML command from the dropdown list or enter an MML command.
Parameter area
Displays parameters of a selected or an input command. Before

running the command, set parameters for it. Parameters in red are
mandatory and those in black are optional.
NOTE
The Send Time displayed in the operation record is the system time of the
LMT PC.

28
BSC6900 UMTS
LMT User Guide
Component
Description
Help
Click Help to obtain LMT online help of the required version.
About
Click About to obtain version information about the LMT offline

MML.
Making MML Scripts Offline

This section describes how to make MML scripts offline.
Procedure
Step 1 Log in to the LMT offline MML tool. For details, see Logging In to and Out of LMT Offline
MML.
Step 2 Enter an MML command in the LMT offline MML window, click Assist, and set the parameters.
NOTE
The LMT offline MML tool provides an association function. When you are typing a command in the
Command Input field, relevant commands are displayed for reference.
Step 3 Click Save to save the MML command and parameter settings to the local MML script file.
NOTE
l The command input and parameter settings saved to the local file by clicking Save do not overwrite
the existing information saved in the local file.
l You can select an MML command in the Operation Record area, right-click it, and choose a menu
item to clear or save the MML command. You can use the same method to clear or save all MML
commands.
----End
2.8.3 FTP Client

The FTP client, a component of the LMT Offline Tools, enables the LMT to communicate with
the FTP server through FTP or FTPs. You can use the FTP client to obtain logs and upload data
configuration files.
Startup Method
On the LMT PC, choose Start > All Programs > HUAWEI Local Maintenance Terminal >
FTP Client.
GUI
Figure 2-11 shows the window of the FTP client.
Issue 02 (2015-05-08)

29
BSC6900 UMTS
LMT User Guide
Figure 2-11 FTP Client window
Table 2-11 describes the components of the FTP Client window.

Table 2-11 Components of the FTP Client window
Number
Component
Description
Menu bar
Provides entries for system operations.
Toolbar
Provides the shortcut icons for system operations.
Server input area
Includes the server name, user name, password, port

number, and mode.
NOTE
To query the port number, run the LST FTPSSRV
command and obtain the setting for the Command Port of
FTPS Server. If an incorrect port number is used, the LMT
cannot be connected to the FTP server.
Issue 02 (2015-05-08)
Local directory list

window
Displays the directory structure of the current

computer.
Server file list window
Lists the files and file folders stored in the connected

FTP server.
Local file list window
Lists the files and file folders stored in the current

computer.
Prompt information
window
Displays information, such as the connection status

of the FTP server and the operation descriptions.

30
BSC6900 UMTS
LMT User Guide
2.8.4 Convert Management System

The Convert Management System is a component of the LMT Offline Tools. It enables
communication between the OMU and the alarm box and is used to transfer the alarm
information, alarm box control information, and alarm box status information. To connect the
LMT to the alarm box, the Convert Management System must be started. The Convert
Management System uses the Ethernet port to communicate with the OMU and the serial port
to communicate with the alarm box.
Function
The Convert Management System provides the following functions:
l
Forwards alarm operation instructions from the LMT.
Forwards alarm information to the alarm box.
Detects the real-time status of the connection between the LMT and the OMU and that
between the LMT and the serial port of the alarm box, and reports alarms if any.
Startup Method
NOTE
If Microsoft Visual C++ 2005 SP1 Redistributable Package (X86) is not installed on the LMT PC, the
Convert Management System cannot start. Download this package from www.microsoft.com.
Convert Management System.
GUI
Figure 2-12 shows the window of the Convert Management System.
Figure 2-12 Convert Management System window
Issue 02 (2015-05-08)

31
BSC6900 UMTS
LMT User Guide
Table 2-12 describes the components of the Convert Management System window.
Table 2-12 Components of the Convert Management System window
Number
Component
Description
Menu bar
Toolbar
Information output
window
Displays the real-time output of the Convert

Management System.
2.8.5 Performance Browser Tool

The Performance Browser Tool, a component of the LMT Offline Tools, is used to parse
descriptive performance files in the OMU.
Startup Method
Performance Browser Tool.
GUI
Figure 2-13 shows the window of the Performance Browse Tool.
Figure 2-13 Performance Browse Tool window
Issue 02 (2015-05-08)

32
BSC6900 UMTS
LMT User Guide
The Table 2-13 describes the components of the Performance Browse Tool window.
Table 2-13 Components of the Performance Browse Tool window
Number
Component
Description
Menu bar

You can click Help to obtain information about how
to use the tool.
Toolbar
Measurement
statistics window
Provides statistical measurement files in a tree

structure.
Detailed information
window
Displays the detailed information about a selected

performance counter file.
2.8.6 TrafficRecording Review Tool

The TrafficRecording Review Tool, a component of the LMT Offline Tools, is used to review
trace and monitor data.
Startup Method
On the LMT PC, choose Start > All Programs > Huawei Local Maintenance Terminal >
TrafficRecording Review Tool.
GUI
Figure 2-14 shows the window of the TrafficRecording Review Tool.
Issue 02 (2015-05-08)

33
BSC6900 UMTS
LMT User Guide
Figure 2-14 TrafficReview window
Table 2-14 describes the components of the TrafficReview window.

Table 2-14 Components of the TrafficReview window
Issue 02 (2015-05-08)
Number
Component
Description
Menu bar
Toolbar
Service data retrieval

window
Displays trace and monitor tasks.

34
BSC6900 UMTS
LMT User Guide
Operation Rights Management
About This Chapter

This chapter describes principles of managing operation rights, user accounts, and command
groups.
3.1 Concepts Related to Operation Rights Management
This section describes concepts related to operation rights management, including principles of
operation rights management, command groups, user types, operation rights, user passwords,
and operation time limits.
3.2 Management of User Accounts
This section describes how to create, modify, and delete external user accounts on the
BSC6900 LMT.
3.3 Management of User Passwords
This section describes how to define and query login password policies, change the password
of an active user, or change the password of an external user account.
3.4 Management of Command Groups
This section describes how to query and rename command groups and how to change commands
in a command group.
Issue 02 (2015-05-08)

35
BSC6900 UMTS
LMT User Guide
3.1 Concepts Related to Operation Rights Management

This section describes concepts related to operation rights management, including principles of
operation rights management, command groups, user types, operation rights, user passwords,
and operation time limits.
3.1.1 Principles of Operation Rights Management

This section describes principles of managing the operation rights of the BSC6900 LMT in terms
of user identities, operation rights, and operation time limits.
The operation and maintenance (O&M) subsystem of the BSC6900 allows multiple users to
perform operations concurrently. For system security reasons, the following aspect of operation
rights must be managed and controlled:
l
User identities:
A user must enter a correct user name and password to log in to the system.
User rights:
Users of different levels are permitted to use different command groups for GUI or MML
command operations.
Operation time limits:

An operation limit specifies the times when a user is permitted to perform operations.
3.1.2 User Passwords

This section describes user passwords of the BSC6900 LMT. It includes definitions, the default
password, initial password settings, and permissions required to change passwords.
Definition of User Passwords

To ensure system security, each user account is password protected. A user must enter a valid
user name and correct password to log in to the LMT and then the OMU.
ADMINISTRATOR-level users can set password complexity. For details, see Setting Password
Policies.
Default Password
The default password for user admin is mbsc@com.
Initial Password Setting

The password of user admin is set during the installation of the OMU software. User admin,
ADMINISTRATOR-level users, and authorized CUSTOM-level users can create external user
accounts and set passwords for these accounts.
Issue 02 (2015-05-08)

36
BSC6900 UMTS
LMT User Guide
Permissions to Change Passwords

All users can change their own passwords. User admin, ADMINISTRATOR-level users, and
authorized CUSTOM-level users can change the passwords of all external user accounts. To
change the password of user admin, run the MOD OP command on the U2000.
For details, see 3.3.3 Changing the Password of the Active User Account and 3.3.4 Changing
the Password of an External User Account.
3.1.3 Command Groups

The BSC6900 provides 15 command groups (G_0 to G_14) with different functions.
Table 3-1 describes these command groups.
Table 3-1 Command groups
Issue 02 (2015-05-08)
Command Group
Function
G_0
Used to query system information, such as user groups, command

groups, logs, Network Time Protocol (NTP), element
management system (EMS), and time zone.
G_1
Used to manage system information, such as user groups, time

zone, Daylight Saving Time (DST), and batch configuration.
G_2
Used to query configuration information. These commands

usually start with LST.
G_3
Used to configure data, for example, to configure data for a newly

added board.
G_4
Used to query alarm information.
G_5
Used to manage alarms, for example, to manually clear alarms or

to set alarm severity.
G_6
Used to query performance statistics, for example, to query a

performance statistical file or task file.
G_7
Used to manage performance, for example, to activate a

performance task file or to upload a performance statistical file.
G_8
Used to query equipment information, such as equipment status.

These commands usually start with DSP.
G_9
Used to manage equipment, for example, to reset, block,

unblock, or switch over boards.
G_10
Used to trace or monitor the signaling flows on the control plane

and the user plane, for example, to query the trace tasks or to
create/delete/start a trace task.
G_11
Used to modify settings of integrated equipment panels.
G_12
Used to manage software, for example, to manage patches.

37
BSC6900 UMTS
LMT User Guide
Command Group
Function
G_13
Used to query base station information, such as attributes and

boards.
G_14
Used to manage base stations, for example, to manage base

station software or to reset base stations.
For operations related to these command groups, see 3.4 Management of Command
Groups.
3.1.4 User Types

You can log in to the BSC6900 LMT as a Local user or an EMS user.
l
Local users:
Managed independently by the BSC6900 LMT. You can log in to the BSC6900 when you
are installing the BSC6900 system or when the OMU is disconnected from the U2000. User
admin is a default local user.
EMS users:
Managed by the U2000. They are created, modified, authenticated, and authorized by the
U2000. Only authorized EMS users can log in to the BSC6900 using the LMT. For
BSC6900 operations, authorized EMS users can also log in to the U2000 server through
the U2000 client.
3.1.5 Operation Rights

This section describes operation rights of the admin account and external user accounts of the
BSC6900 LMT.
Built-In Administrator Account

User admin is a built-in administrator account, also termed super administrator. The password
of this user is set during the installation of the OMU.
The admin account is an administrator-level account and cannot be modified or deleted.
External User Accounts

There are five types of external user accounts. Each type of external user accounts is granted
different operation rights, which are described in Table 3-2.
Issue 02 (2015-05-08)

38
BSC6900 UMTS
LMT User Guide
Table 3-2 External user accounts

Level
Assigned
Command
Group
Operation Rights
Remarks
GUEST
G_0, G_2, G_4,

G_6, G_8, and
G_13
Data query
USER
G_0, G_2, G_4,

G_6, G_7, G_8,
G_9, G_10,
G_11, G_12,
G_13, and G_14
l Operation rights of GUESTlevel users
The operation
rights are
predefined by the
system and cannot
be changed.
G_0, G_2, G_3,

G_4, G_5, G_6,
G_7, G_8, G_9,
G_10, G_11,
G_12, G_13,
and G_14
l Operation rights of USERlevel users
ADMINISTRA
TOR
G_0, G_1, G_2,

G_3, G_4, G_5,
G_6, G_7, G_8,
G_9, G_10,
G_11, G_12,
G_13, and G_14
All operation rights
CUSTOM
Command
groups are
assigned when
the account is
being created.
Specified when the account is

being created
OPERATOR
l System operation and

maintenance (O&M)
l Data configuration
The operation
rights can be
changed. Different
CUSTOM-level
users may have
different operation
rights.
NOTE
User admin, ADMINISTRATOR-level users, and authorized CUSTOM-level users can add or delete
external user accounts.
An authorized CUSTOM-level user can perform operations on user accounts and command groups
only by running MML commands.
3.1.6 Operation Time Limits

This section defines operation time limits for a user to perform operations on the BSC6900 LMT
and explains their principles and required permissions.
Definition of Operation Time Limits

An operation time limit specifies the times when a user can perform operations on the LMT.
Issue 02 (2015-05-08)

39
BSC6900 UMTS
LMT User Guide
No operation limits are imposed on user admin. User admin can perform operations on
the LMT at any time.
An operation time limit can be set for an external user account when the account is being
created. If no time limits are set for the account, the account can perform operations on the
LMT at any time.
Principle of Operation Time Limits

An operation time limit is defined by date, day, and time.
Table 3-3 provides some examples of operation time limits.
Table 3-3 Examples of operation time limits
SN
Date
Day
Time
Permitted Operation Time
2013-02-01
to
2014-02-01
Monday to
Friday
8:00:00 to
18:00:00
8:00:00 to 18:00:00 on Monday

through Friday from 2013-02-01
to 2014-02-01
Saturday and
Sunday
Any time on Saturdays and

Sundays
No operation time limits are

imposed on the user. A user with
this setting can perform operations
on the LMT at any time.
Permissions to Set Operation Time Limits

User admin, ADMINISTRATOR-level users, and authorized CUSTOM-level users can set or
change operation time limits of all external user accounts.
3.2 Management of User Accounts

This section describes how to create, modify, and delete external user accounts on the
BSC6900 LMT.
3.2.1 Creating an External User Account

This section describes how to create an external user account. You are required to set a password,
a user type, an operation time limit, and command groups (for CUSTOM-level users only) for
the new user account. Only user admin, ADMINISTRATOR-level users, and some CUSTOMlevel users are authorized to create external user accounts.
Prerequisites
You have logged in to the LMT with an authorized account.
Issue 02 (2015-05-08)

40
BSC6900 UMTS
LMT User Guide
Procedure
Step 1 Run the ADD OP command to create an external user account.
NOTICE
The new external user account must be different from any of the existing user accounts.
----End
3.2.2 Modifying an External User Account

This section describes how to modify the attributes of an external user account, including the
user name, user password, user level, operation rights, and operation time limit. The new
password takes effect at the next login. Modifications of other attributes take effect immediately.
Only user admin, ADMINISTRATOR-level users, and some CUSTOM-level users are
authorized to modify external user accounts.
Prerequisites
Procedure
Step 1 Run the MOD OP command to modify the attributes of an external user account.
----End
3.2.3 Deleting an External User Account

This section describes how to delete an external user account. Only user admin,
ADMINISTRATOR-level users, and some CUSTOM-level users are authorized to delete
external user accounts.
Context
NOTICE
User admin is the permanent built-in user account and cannot be deleted.
Procedure
Step 1 Run the RMV OP command to delete an external user account.
----End
Issue 02 (2015-05-08)

41
BSC6900 UMTS
LMT User Guide
3.3 Management of User Passwords

This section describes how to define and query login password policies, change the password
of an active user, or change the password of an external user account.
3.3.1 Defining Login Password Policies

This section describes how to define policies for setting login passwords. Login password
policies set restrictions on the minimum length and complexity of a password. Only
ADMINISTRATOR-level users can define policies for setting login passwords.
Prerequisites
Procedure
Step 1 Run the SET PWDPOLICY command to define policies for setting login passwords.
----End
3.3.2 Querying Login Password Policies

This section describes how to query policies for setting login passwords.
Prerequisites
You have logged in to the LMT.
Procedure
Step 1 Run the LST PWDPOLICY command to query policies for setting login passwords.
----End
3.3.3 Changing the Password of the Active User Account

This section describes how to change the password of the active user account. The new password
takes effect at the next login.
Prerequisites
Procedure
Step 1 On the toolbar of the LMT main page, click Password. The Password dialog box is displayed.
Step 2 In the displayed Password dialog box, enter the current password in the Old Password field,
enter the new password in the New Password and Confirm Password fields, and click OK.
Issue 02 (2015-05-08)

42
BSC6900 UMTS
LMT User Guide

NOTE
You are advised to change the password at your first login and then change the password every three months.
----End
3.3.4 Changing the Password of an External User Account

This section describes how to change the password of an external user account. Only user
admin, ADMINISTRATOR-level users, and authorized CUSTOM-level users can change the
password of an external user account.
Prerequisites
Procedure
Step 1 Run the MOD OP command to change the password of an external user account.
----End
3.4 Management of Command Groups

This section describes how to query and rename command groups and how to change commands
in a command group.
3.4.1 Querying a Command Group

There are 16 command groups G_0 to G_14 and G_NICThere are 13 command groups G_0 to
G_12. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can
query the information about the command groups.
Prerequisites
You have logged in to the LMT with an account authorized for this operation.
Procedure
Step 1 Run the LST CCG to query the command groups.
----End
3.4.2 Renaming Command Groups

This section describes how to rename command groups. Only user admin, ADMINISTRATORlevel users, and authorized CUSTOM-level users can rename command groups.
Prerequisites
Issue 02 (2015-05-08)

43
BSC6900 UMTS
LMT User Guide
Procedure
Step 1 Run the LST CCGN command to query the name of a command group.
Step 2 Run the SET CCGN command to rename the command group.
----End
3.4.3 Changing Commands in a Command Group

This section describes how to change commands in a command group. Only user admin,
ADMINISTRATOR-level users, and authorized CUSTOM-level users can change commands
in a command group.
Prerequisites
Procedure
l
Run the ADD CCG command to add commands to a command group.
Run the RMV CCG command to remove commands from a command group.
----End
Issue 02 (2015-05-08)

44
BSC6900 UMTS
LMT User Guide
Running MML Commands
About This Chapter

This chapter describes how to run MML commands on the LMT for operation and maintenance
of the BSC6900.
4.1 Concepts Related to MML Commands
This section presents an introduction to MML commands, components of the MML command
window, data configuration rights, and configuration rollback.
4.2 Running a Single MML Command
This section describes how to run a single MML command for routine configuration and
maintenance.
4.3 Batch Processing of MML Commands
This section describes how to run multiple MML commands simultaneously. Batch processing
of MML commands allows you to use a function or perform an operation by running a prepared
group of MML commands all at the same time.
4.4 Setting MML Parameters
This section describes how to set the MML parameters as required.
4.5 Querying Data Configuration Modes
This section describes how to query the data configuration mode of a subrack. The data
configuration mode can be effective or non-effective.
4.6 Querying Data Configuration Rights
This section describes how to query the status of data configuration rights.
4.7 Obtaining Data Configuration Rights
This section describes how to obtain exclusive data configuration rights when you plan to
perform data configuration, undo/redo operations on the BSC6900, or perform batch data
configuration without being affected by other users. Only the U2000 users and users of the
following types can obtain these data configuration rights: admin, ADMINISTRATOR-level
users, OPERATOR-level users, and CUSTOM-level users entitled to use command group G_3
(used for data configuration).
4.8 Undoing/Redoing a Single Data Configuration Action
This section describes how to undo and redo a single data configuration action.
Issue 02 (2015-05-08)

45
BSC6900 UMTS
LMT User Guide
4.9 Undoing/Redoing Multiple Data Configuration Actions

This section describes how to undo and redo multiple data configuration actions at a time.
Issue 02 (2015-05-08)

46
BSC6900 UMTS
LMT User Guide
4.1 Concepts Related to MML Commands

This section presents an introduction to MML commands, components of the MML command
window, data configuration rights, and configuration rollback.
4.1.1 Introduction to MML Commands

This section describes MML commands used for operation and maintenance of the BSC6900.
An MML command consists of two parts, an action and an object. For example, ADD OP,
wherein ADD is the action part and OP is the object part. Table 4-1 describes actions that can
be performed by MML commands.
Table 4-1 Actions of the MML commands
Issue 02 (2015-05-08)
Action
Description
ACT
Activate
ADD
Add
ADT
Audit
BEG
Begin
BKP
Back up
BLK
Block
CHK
Check
CLR
Clear
CMP
Compare
COL
Collect
CON
Confirm
DEA
Deactivate
DLD
Download
DSP
List
EST
Establish
EXP
Export
FMT
Format
FOC
Obtain
HO
Hand over

47
BSC6900 UMTS
LMT User Guide
Action
Description
INH
Inhibit
INS
Install
LCK
Lock
LOD
Load
LOP
Loopback test
LST
List
MOD
Modify
PING
Ping
REL
Release
REQ
Request
RUN
Run
RMV
Remove
RST
Reset
SET
Set
STR
Start/Open
STP
Stop/Close
STA
Collect statistics
SWP
Swap
SYN
Synchronize
TRC
Trace
UBL
Unblock
UIN
Uninhibit
ULD
Upload
ULK
Unlock
4.1.2 Components of the MML Command Window

This section describes the components of the MML command window.
Figure 4-1 shows the MML command window.
Issue 02 (2015-05-08)

48
BSC6900 UMTS
LMT User Guide
Figure 4-1 MML command window
Table 4-2 describes the components of the MML command window.

Table 4-2 MML command window
Number
Component
Description
Common
Maintenance (Alt
+C) tab page
Displays system responses, such as command results.

You can save command results and automatically scroll
through the command results by clicking Save Results
and Auto Scroll, respectively. You can also clear all
command results by clicking Clear All.
NOTE
l The time information displayed at the beginning of
command results is the system time of the OMU.
l When you click Save Results, command results of only
selected MML commands are saved.
Issue 02 (2015-05-08)
Operation Record
(Alt+R) tab page
Displays commands that have been run.
Help Information
(Alt+N) tab page
Displays the help information of MML commands.
Manual editing area
Displays manually input MML commands and their

parameters.
NOTE
The Send Time in an operation record is the system time of the
LMT PC.

49
BSC6900 UMTS
LMT User Guide
Number
Component
Description
History Command
field
Displays all commands executed during the current login

and relevant parameters.
Command Input
field
Displays all the MML commands available on the system

in the drop-down list. You can select an MML command
from the drop-down list or enter an MML command.
Parameter area
Displays parameters of a selected or an input command.

Before running the command, set parameters for it.
Parameters in red are mandatory. Those in black are
optional.
NOTE
For details of MML commands and parameters, see the MML help.
4.1.3 Data Configuration Rights

To avoid data conflict, the OMU manages data configuration rights to allow only one user to
perform BSC6900 data configuration through the LMT or the U2000 at any time.
The OMU manages data configuration rights as follows:
l
By default, all users have data configuration rights.
When a user runs the LCK CMCTRL command, data configuration rights are exclusive
to this user.
When the user runs the ULK CMCTRL command, data configuration rights become
available to all users.
If a user occupies exclusive data configuration rights for a long time but does not configure
data, administrators can run the FOC CMCTRL command to forcibly release the data
configuration rights to all users.
If a user who had exclusive data configuration rights exits from the LMT, the data
configuration rights will be automatically made available to all users.
4.1.4 Data Configuration Rollback

If a data configuration operation fails to achieve the expected result or even causes equipment
or network problems, you can roll back the configuration to restore the system to a previous
configuration status. The data configuration rollback function ensures that the operating of the
BSC6900 is restored to normal as soon as possible.
Definition of Data Configuration Rollback

During data configuration, a rollback point is used to mark a data configuration status. You can
run the ADD ROLLBACKPOINT command to manually configure rollback points.
When data configuration rollback is required, you can select a rollback point to restore the system
to a specific configuration status as required.
Issue 02 (2015-05-08)

50
BSC6900 UMTS
LMT User Guide
Operations of Data Configuration Rollback
NOTICE
A user cannot perform data configuration rollback in any of the following cases:
l
The user does not obtain the data configuration rights because another user who has
occupied exclusive data configuration rights does not release the data configuration rights
by running the ULK CMCTRL command.
The quick configuration mode has been enabled by running the SET QUICKCFG
command.
Batch configuration is performed by running the RUN BATCHFILE command.
The following data configuration rollback operations are available:

l
Undo a single configuration action:

This operation is performed to undo a previous configuration action. Up to 10 of the most
recent effective configuration actions can be undone.
Redo a single configuration action:

This operation is performed to redo a previously undone configuration action. Up to 10 of
the most recent effective configuration actions can be redone.
Undo multiple configuration actions:

This operation is performed to simultaneously undo multiple configuration actions that
have taken effect. After the undo operation, the system is restored to the configuration status
at a specified rollback point.
Redo multiple configuration actions:

This operation is performed to simultaneously redo multiple configuration actions that have
been undone. After the redo operation, the system is restored based on either the
configuration status at the specified rollback point or the final configuration status from
before undoing the configurations.
4.2 Running a Single MML Command

This section describes how to run a single MML command for routine configuration and
maintenance.
Prerequisites
Context
To run an MML command, you can:
l
Enter an MML command in the Command Input field.
Select a previously executed command from the History Command drop-down list.
Select an MML command from the MML Command navigation tree.
Issue 02 (2015-05-08)

51
BSC6900 UMTS
LMT User Guide
Copy an MML command script to the Manual Editing area.
Entering an MML command in the Command Input field
Procedure
1.
Enter an MML command in the Command Input field. When you are entering a
command, related commands are displayed in a drop-down list. You can select the
required command from the drop-down list.
2.
Press Enter or click Assist to display parameters associated with the command.
3.
Specify parameter values.
4.
Press F9 or click Exec to run the command. The command result is displayed on the
Common Maintenance tab page.
Selecting a previously executed command from the History Command drop-down list
1.
Select a previously executed command from the drop-down list of history commands.
to select the previous command. Press F8 or click
(Press F7 or click
select the next command.)
to
2.
(Optional) Change parameter values in the command parameter area.
3.
Selecting an MML command from the MML Command navigation tree

1.
Double-click an MML command in the MML Command navigation tree.
2.
Specify parameter values.
3.
NOTE
l Parameters in red are mandatory. Those in black are optional.

l To obtain general information about a parameter, place the cursor on the input box for the
parameter.
l If the execution of a command fails, the command result displayed on the Common
Maintenance tab page is in red.
Copying an MML command script to the Manual Edit area

1.
Copy an MML command script with required parameter values and paste it to the
Manual Edit area.
2.
----End
4.3 Batch Processing of MML Commands

This section describes how to run multiple MML commands simultaneously. Batch processing
of MML commands allows you to use a function or perform an operation by running a prepared
group of MML commands all at the same time.
Issue 02 (2015-05-08)

52
BSC6900 UMTS
LMT User Guide
Context
A batch file (also called data script file) is a plain text file, which contains a group of command
scripts used for conducting a specific task. The command scripts in a batch file are executed in
sequence.
The following two batch processing modes are available:
l
Immediate batch processing:

A batch file is run immediately.
Scheduled batch processing:

A batch file is automatically run at a specific time set by users in advance.
NOTE
When the LMT locks its operation screen, the following commands will fail:
l ADD OP, RMV OP, and MOD OP
l SET OPLOCK
l SET OPSW
l SET PWDPOLICY
l ULK USR
l SET WEBLOGINPOLICY
4.3.1 Immediate Batch Processing of MML Commands

This section describes how to enable the system to immediately run a group of MML commands
in a batch file simultaneously.
Prerequisites
l
You have obtained the required data configuration rights. For details, see 4.7 Obtaining
Data Configuration Rights.
Procedure
Step 1 On the LMT main page, click Batch. The Batch tab page is displayed.
Step 2 In the editing area, click New and enter the MML commands to be executed at a time, or click
Open... to select the prepared batch file.
NOTE
If an encrypted .ecf file is selected, enter the password of the file to import the file for batch processing.
Step 3 Click Settings to set parameters.

Step 4 Click Go to run the commands.
NOTE
You can set Execution Type. By default, Prompt when an error occurs is selected. You are advised to retain
the default setting.
----End
Issue 02 (2015-05-08)

53
BSC6900 UMTS
LMT User Guide
4.3.2 Scheduled Batch Processing of MML Commands

This section describes how to enable the system to automatically run a batch of MML commands
in a batch file at a moment of a day specified by an operator in advance.
Prerequisites
l
You have obtained FTP user name and password.
You have obtained the data configuration rights. For details, see 4.7 Obtaining Data
Configuration Rights.
Procedure
Step 1 Edit a batch file.
1.
Click Batch on the LMT main page. The Batch tab page is displayed.
2.
Click New and type a batch of MML commands in the input box.
3.
Click Save to save the edited batch file.
Step 2 Upload the MML command script file to the /ftp directory in the OMU active work area. Assume
that the MML command script file BATCHFILE.txt saved in disk D is uploaded to the /bam/
version_a/ftp directory in the OMU active work area. When the active workspace of the OMU
is version_a, the following path changes into version_a. When the active workspace of the
OMU is version_b, the following path changes into version_b accordingly. There are the
following two upload ways:
l Through File Manager on the LMT
1.
Start File Manager by referring to File Manager.
2.
Choose Root > bam > version_a > ftp in the left area of the displayed window to
navigate to the ftp directory. Then click Upload.
3.
In the displayed Select Upload File dialog box, select the BATCHFILE.txt file saved
in local disk D and click Open to upload the file.
l Through command lines

1.
On a local LMT PC, choose Start > Run, enter cmd, and click OK.
2.
Type the d: command and press Enter to switch the local disk to disk D.
3.
Enter the ftp IP address command to apply for connection to the OMU. IP address is
the IP address of the OMU.
4.
Enter the FTP user name and password. If the authentication passes, an FTP connection
is established between the local PC and the OMU.
NOTE
The FTP user name must be the fixed value FtpUsr. The FTP password was set during installation of
product software. You can run the MOD FTPPWD command to change the password.
Issue 02 (2015-05-08)
5.
Enter the cd /bam/version_a/ftp command to switch to the directory of OMU active

work area.
6.
Enter the put BATCHFILE.txt command to upload the file.
7.
Enter the quit command to disconnect FTP connection when the file upload is complete.
54
BSC6900 UMTS
LMT User Guide
Step 3 Add scheduled batch processing tasks by running the ADD SCHTSK and ADD SUBTSK
commands.
NOTE
l Add scheduled batch processing tasks

ADD SCHTSK: ID=1, TSKN="batch"; ADD SUBTSK: ID=1, TSKN="batch", SUBID=2,
SCMD="RUN BATCHFILE: SRCF=\"BATCHFILE.txt\", TYPE=ALL_END_RETURN, RSTF=
\"result_add.txt\"", FREQ=ONTIME, SD=2010&08&30, TM=09&56;
l BATCHFILE.txt is the name of a batch file that needs to be run at a scheduled time and saved in the ftp
directory of the OMU active work area; result_add.txt is the name of the result file.
----End
4.3.3 Syntax Check

This section describes how to check the syntax of MML commands before running a group of
MML commands. This function helps locate incorrect MML commands, thereby improving
maintenance efficiency.
Prerequisites
l
A batch file is available.
Context
The syntax check can locate the following errors:
l
Missing colon
Missing semicolon
Incorrect MML command
No authority to execute a correct MML command
Redundant parameters
Incorrect parameters
Procedure
Step 1 Click New to create a batch file and input MML commands in the manual editing area.
NOTE
You can click Open... to open a prepared batch file.

If an encrypted .ecf file is selected, enter the password of the file to import the file for batch processing.
Step 2 Click Analyze Syntax to check the syntax of the batch file.
Issue 02 (2015-05-08)

55
BSC6900 UMTS
LMT User Guide

NOTE
l If no errors occur, the Information dialog box is displayed, indicating that no syntactical errors occur.
If an error occurs, the Result dialog box is displayed, indicating a line number for locating the error
and error reasons for correcting the error.
l To go to the command line with a syntactical error, double-click the information in the Result dialog
box.
l After Analyze Syntax is executed, a
mark is displayed in front of a command line with syntactical
errors in the batch file. If you move the mouse to the

information is displayed.
mark in front of a command line, error
l To check a single MML command line for syntactical errors in a batch file, select a single MML
command line, right-click it, and choose Analyze Current Line from the shortcut menu.
Step 3 In the Result dialog box, click Save As... to save the result.
Step 4 Click Close.
----End
Follow-up Procedure
To clear all syntactical analysis marks in a batch file, right-click in the batch file and choose
Clear Analyze Mark from the shortcut menu.
4.4 Setting MML Parameters

This section describes how to set the MML parameters as required.
Procedure
Step 1 On the Common Maintenance tab page in the MML window, click Settings. The Settings
dialog box is displayed, as shown in Figure 4-2.
Figure 4-2 Setting MML Parameters
Issue 02 (2015-05-08)

56
BSC6900 UMTS
LMT User Guide
Step 2 Set parameters as required.

Step 3 Click OK to save the settings.
NOTE
The parameter settings in System and MML Command are stored on the server and client, respectively.
Therefore, after the BSC resets or restarts, the parameter setting in System is restored to the default value but
the parameter settings in MML Command remain unchanged.
----End
4.5 Querying Data Configuration Modes

This section describes how to query the data configuration mode of a subrack. The data
configuration mode can be effective or non-effective.
Prerequisites
Context
When a subrack is in effective mode, data configured for the subrack takes effect immediately.
When a subrack is in non-effective mode:
l
Data configured for the subrack takes effect only for the OMU, not on the subrack.
To make the data configuration take effect on the subrack, perform the following
operations: Run the SET CFGDATAEFFECTIVE command to set the data configuration
mode to effective mode, run the FMT DATA command to generate the data configuration
file for the subrack, and then run the RST SUBRACK command to reset the subrack. In
this way, the subrack can load the data configuration from the OMU so that the data takes
effect on the subrack.
You cannot query, compare, or perform CRC check on the host and OMU data. In addition,
You cannot configure the host data of the subrack.
When all subracks are in non-effective mode, license verification is not performed. When a
subrack attempts to switch the data configuration mode from the non-effective mode to the
effective mode, the OMU checks whether the data configuration exceeds the limitations of the
license. If the data configuration exceeds the limitations of the license, the mode switching will
fail.
When the OMU is newly installed, subrack 0 is in non-effective mode by default. When a subrack
is newly added, it is in non-effective mode by default.
NOTE
You can use menus or MML commands to query the data configuration mode.
Procedure
l
Issue 02 (2015-05-08)
Using menus
57
BSC6900 UMTS
LMT User Guide
1.
On the LMT main page, check the configuration mode of a subrack from the dropdown list on the tool bar, as shown in Figure 4-3.
Figure 4-3 Data configuration mode
Using MML commands

1.
Run the LST CFGMODE command to query the current data configuration mode.
----End
4.6 Querying Data Configuration Rights

This section describes how to query the status of data configuration rights.
Prerequisites
Context
You can use menus or MML commands to query the status of data configuration rights.
Procedure
l
Using menus
1.
Check the status of data configuration rights displayed at the top right corner of the
LMT main page.
Using MML commands

1.
Run the LST CMCTRL command to query the status of data configuration rights.
----End
4.7 Obtaining Data Configuration Rights

This section describes how to obtain exclusive data configuration rights when you plan to
perform data configuration, undo/redo operations on the BSC6900, or perform batch data
configuration without being affected by other users. Only the U2000 users and users of the
following types can obtain these data configuration rights: admin, ADMINISTRATOR-level
users, OPERATOR-level users, and CUSTOM-level users entitled to use command group G_3
(used for data configuration).
Issue 02 (2015-05-08)

58
BSC6900 UMTS
LMT User Guide
Prerequisites
l
By default, all users have data configuration rights. They can use the LMT or U2000 to
configure data for the BSC6900.
Only one user can use the data configuration rights at any given time. You can run the
LCK CMCTRL command to obtain exclusive data configuration rights.
After the data configuration is complete, you can run the ULK CMCTRL command to
made the data configuration rights available to all users so that another user can run the
LCK CMCTRL command obtain exclusive data configuration rights.
If a user who had exclusive data configuration rights exits from the LMT, the data
configuration rights will be automatically made available to all users. In this case, another
user can also run the LCK CMCTRL command to obtain exclusive data configuration
rights.
Context
Procedure
Step 1 Check whether the data configuration rights are available. For details, see 4.6 Querying Data
Configuration Rights.
l If no user has exclusive data configuration rights, go to Step 2.
l If a user has exclusive data configuration rights, once that user releases those configuration
rights, go to Step 2.
Step 2 Run the LCK CMCTRL command to obtain the data configuration rights.
NOTE
If an LMT user has exclusive data configuration rights of the BSC6900, other LMT users cannot obtain
the data configuration rights. In this case, user admin or ADMINISTRATOR-level users can run the
FOC CMCTRL command to forcibly release the locked data configuration rights.
----End
4.8 Undoing/Redoing a Single Data Configuration Action

This section describes how to undo and redo a single data configuration action.
Prerequisites
l
You have obtained data configuration rights by running the LCK CMCTRL command.
The quick configuration mode has been disabled by running the SET QUICKCFG
command.
No batch commands have been executed.
You can undo or redo a data configuration action to fine-tune data configuration. These
operations, however, can decrease the efficiency of running MML commands. Therefore,
Context
Issue 02 (2015-05-08)

59
BSC6900 UMTS
LMT User Guide
when the quick configuration mode is enabled or when batch MML commands are running,
do not undo or redo data configuration actions.
l
To prevent data conflicts, a user can undo or redo a data configuration action only if the
user has obtained exclusive data configuration rights.
Certain MML commands cannot be undone or redone. If you run such an MML command,
the Undo and Redo buttons on the top of the LMT window becomes unavailable and
configuration actions performed before running the MML command also cannot be undone
or redone. For a list of MML commands that can be undone or redone, see the description
of the ADD ROLLBACKPOINT command.
The most recent 10 effective single configuration actions can be undone one at a time.
Likewise, the 10 most recent undone operations can be redone in the same manner.
Undoing a single configuration action
Procedure
1.
Use either of the following methods to undo the latest configuration action:
On the toolbar of the LMT, click Undo.
Run the BEG UNDO command.
2.
l
To undo multiple configuration actions, repeat Step 1.
Redoing a single configuration action

1.
Use either of the following methods to redo an undone action:

On the toolbar of the LMT, click Redo.
Run the BEG REDO command.
2.
To redo multiple configuration actions, repeat Step 1.
----End
4.9 Undoing/Redoing Multiple Data Configuration Actions

This section describes how to undo and redo multiple data configuration actions at a time.
Prerequisites
l
You have obtained data configuration rights by running the LCK CMCTRL command.
The quick configuration mode has been disabled by running the SET QUICKCFG
command.
No batch commands have been performed.
You can undo or redo multiple data configuration actions simultaneously to fine-tune data
configuration. These operations, however, can decrease the efficiency of running MML
commands. Therefore, when the quick configuration mode is enabled or when batch MML
commands are running, do not undo or redo multiple data configuration actions.
Context
Issue 02 (2015-05-08)

60
BSC6900 UMTS
LMT User Guide
To prevent data conflicts, a user can undo or redo multiple data configuration action
simultaneously only if the user has exclusive data configuration rights.
Certain MML commands do not support undoing or redoing multiple data configuration
actions at a time. If you run such MML commands, the rollback point specified by running
the ADD ROLLBACKPOINT command will become invalid and undoing multiple data
configuration actions at a time will fail. Therefore, before running such MML commands,
remove the configured rollback point. For a list of MML commands that support undoing
or redoing multiple configuration actions, see the description of the ADD
ROLLBACKPOINT command.
Multiple configuration actions can be undone simultaneously. After a multiple undo

operation is applied, the system is restored based on the configuration status from a
specified rollback point.
Multiple configuration actions can be redone simultaneously. After the multiple actions
have been redone, the system is restored based on either the configuration status at the
specified rollback point or the final configuration status from before undoing the
configuration actions.
NOTE
An initial rollback point is the first rollback point set by a user. The final rollback point is automatically
set to the latest configuration command successfully executed. The LMT allows you to undo a maximum
of 10,000 configuration commands from the initial rollback point to the final rollback point at a time. If
there are more than 10,000 commands from the initial rollback point to the final rollback point, the undoing
operation will fail and the LMT will display a failure message.
A user who has obtained the data configuration rights can set a maximum of five rollback points. If the
user releases the data configuration rights, the active workspace of the OMU will clear the information
about the rollback stack and rollback points.
Procedure
Step 1 To undo/redo multiple data configuration actions simultaneously, before running configuration
commands, run the ADD ROLLBACKPOINT command to set rollback points as required.
Step 2 Run the BEG ROLLBACK command to restore the system to the configuration status at a
specified rollback point.
Step 3 Run the BEG FORWARD command to restore the system to the final configuration status
before undoing the configurations.
----End
Issue 02 (2015-05-08)

61
BSC6900 UMTS
LMT User Guide
Alarm/Event Management
About This Chapter

This section describes how to use the LMT to manage BSC6900 alarms/events. Alarm/event
management helps you analyze alarms/events efficiently, thereby facilitating troubleshooting.
5.1 Concepts Related to Alarm Management
This section describes basic concepts related to alarm management, including the alarm type,
alarm severity, alarm-managed objects, and alarm box.
5.2 Managing Alarm Logs
Alarm logs are used to record alarm details. They are collected by the OMU and stored in the
OMU database. To minimize storage requirements on the hard drive of the OMU, limitations
must be imposed on the number and the storage duration of alarm logs.
5.3 Managing Alarm Masking Conditions
Alarms that meet alarm masking conditions are not reported to the LMT or U2000. These alarms
cannot be queried on the LMT or U2000 but are still saved on the OMU. This section describes
how to manage alarm masking conditions.
5.4 Managing the Alarm Masking Switch of Derived Alarms
When a fault occurs, beside a fault alarm, some related alarms may be generated. These alarms
are termed derived alarms. The BSC6900 can mask derived alarms. By default, derived alarms
are not reported to the LMT. Unless otherwise specified, derived alarms are not stored on the
OMU and cannot be queried.
5.5 Monitoring Alarms
This section describes how to use the LMT to monitor alarm information in real time. The alarm
information is displayed in the Alarm Browse window on the LMT.
5.6 Managing the Alarm Box
The BSC6900 uses Huawei universal alarm box to provide audible and visual indications when
an alarm is reported. The alarm box notifies maintenance engineers of alarms in time, thereby
facilitating operation and maintenance.
Issue 02 (2015-05-08)

62
BSC6900 UMTS
LMT User Guide
5.1 Concepts Related to Alarm Management

This section describes basic concepts related to alarm management, including the alarm type,
alarm severity, alarm-managed objects, and alarm box.
5.1.1 Alarm Type

The alarms in the BSC6900 system can be classified into fault alarms and event alarms.
Table 5-1 describes the two alarm types.
Table 5-1 Fault alarms and event alarms
Alarm Type
Description
Fault alarm
Fault alarms are caused by hardware faults or failures of major functions,

for example, board fault or link fault. Fault alarms are of higher severity
than event alarms and are classified into active and cleared alarms
according to the fault status.
Event alarm
Event alarms record predefined events occurring during the operation of

the system. An event alarm reflects the system condition (for example,
congestion) at a specific time, which is not necessarily a fault. Some event
alarms are generated repeatedly and regularly.
According to fault status, fault alarms are classified into:

l
Cleared alarms:
If a fault has been rectified, the corresponding alarm becomes a cleared alarm.
Active alarms:
If a fault has not been rectified, the corresponding alarm is an active alarm.
For example, when congestion occurs in a cell, the system reports a fault alarm of cell
congestion. Before the congestion is relieved, the alarm remains active. After the congestion is
relieved, the alarm becomes a cleared alarm.
NOTE
l Cleared alarms are stored in the OMU database and can be queried.
l In engineering and maintenance scenarios, such as site deployment, equipment commissioning,
upgrades, capacity expansion, swapping, and cutover, a large number of alarms are reported in a short
period of time. Due to the absence of the mechanism for handling such alarms, the alarm burst makes
it hard for users to identify real fault alarms, thereby disturbing network monitoring. To solve this
problem, Huawei puts forward the concept of "maintenance mode alarms". Alarms triggered by
engineering and maintenance operations are considered as maintenance mode alarms and handled in
a special way. This mechanism streamlines alarm management and facilitates operation and
maintenance.
Issue 02 (2015-05-08)

63
BSC6900 UMTS
LMT User Guide
5.1.2 Alarm Severity

Four alarm severities are available for fault alarms and event alarms of the BSC6900: critical,
major, minor, and warning.
Table 5-2 describes the four alarm severities.
Table 5-2 Alarm severities
Alarm Severity
Definition
Handling
Requirement
Critical
Alarms of this severity are triggered by faults that

affect services provided by the system and must
be handled immediately even during nonworking hours. For example, some devices break
down or some resources become unavailable.
Handle the faults

immediately to
avoid service
outage.
Major

affect the Quality of Service (QoS) and must be
handled. For example, the performance of some
devices or resources deteriorates.
Handle the faults in

time. to avoid
failures of major
functions.
Minor

are not serious enough to affect the QoS. These
alarms can be handled as required or further
observed to prevent them from becoming critical.
For example, you need to clear obsolete historical
alarms regularly.
Identify and rectify

potential faults in
time.
Warning

are potential threats to the system services. These
alarms need to be handled according to specific
situations. For example, the OMU startup alarm
is a warning.
Learn the operating

status of the system
from warning alarms
and resolve
problems as
required.
5.1.3 Alarm-Event Type

Alarms can be classified into 15 types based on event types.
l
Power:
Alarms related to the power system
Environment:
Alarms related to equipment room environment, such as temperature, humidity, and door
sensor
Signaling:
Alarms related to the signaling system
l
Issue 02 (2015-05-08)
Trunk:
64
BSC6900 UMTS
LMT User Guide
Alarms related to the trunk system, including trunk circuits and trunk boards
l
Hardware:
Alarms related to board hardware, such as clock and CPU
Software:
Alarms related to software
Running:
Alarms generated during the operation of the BSC
Communication:
Alarms related to the communication system, such as alarms between the BSC6900 host
and the OMU
QoS:
Alarms related to QoS
Integrity:
Alarms generated when information is repeated, lost, distorted, disordered, or unexpected
Operational:
Alarms related to refusal of operations that are generated when a service is refused or
unavailable, or when an operation procedure is improper
Physical:
Alarms related to cable interference or detection of invasion
Security:
Alarms related to violation of security such as failed authentication, breach of
confidentiality, failed non-repudiation, and unauthorized visit
Time domain:
Alarms related to timeout such as information delay and password expiration
Processing error:
Alarms caused by other abnormal conditions
5.1.4 Alarm Flag

This describes theBSC6900 alarm flags, including: to-alarm-box flag, shield flag, modification
flag, and alarm cleared flag.
To-Alarm-Box Flag
The to-alarm-box flag controls whether alarms are reported to the alarm box. This flag can be
set to either of the following values:
l
Report
When alarms are generated, they are reported to the alarm box, which provides audible and
visual indications for the alarms.
Not report
When alarms are generated or when the alarm status changes, the alarms and the change
of alarm status are not reported to the alarm box.
Issue 02 (2015-05-08)

65
BSC6900 UMTS
LMT User Guide
NOTE
The to-alarm-box flag is applicable only to fault alarms. Event alarms are not reported to the alarm box.
Whether an alarm is reported to the alarm box depends on the to-alarm-box flag of the alarm
and the alarm suppression level of the alarm box. Alarms are reported to the alarm box only
when the to-alarm-box flag is set to Report and the alarm severity is higher than or equal to the
alarm suppression level of the alarm box.
Shield Flag
The shield flag controls whether alarms are suppressed as required. This flag can be set to either
of the following values:
l
Shielded
A board does not report alarms whose shield flags are set to Shield to the element
management system (EMS) or the alarm box. The OMU does not save the logs of such
alarms.
Unshielded
A board reports alarms whose shield flags are set to Unshield to the EMS or the alarm box.
The OMU saves the logs of such alarms.
Modification Flag
The modification flag records the modification status of alarm configurations. This flag can be
set to either of the following values:
l
Modified
When the configuration of an alarm is modified using a modification command, the
modification flag is set to Modified.
Unmodified
When an alarm uses its default configuration or is restored to its default configuration, the
modification flag is set to Unmodified.
Alarm Cleared Flag

The alarm cleared flag specifies whether a fault alarm is cleared. This flag can be set to either
of the following values:
l
Not Cleared
The fault alarm has not been cleared.
Cleared
The fault alarm has been cleared and a clear alarm has been received.
5.1.5 Alarm Box

BSC6900 uses Huawei universal alarm box, which provides audible and visual indications for
the BSC6900 alarms. The alarm box is optional and the BSC6900 can be equipped with only
one alarm box. For details, see the documents delivered with the alarm box.
Figure 5-1 shows the alarm box.
Issue 02 (2015-05-08)

66
BSC6900 UMTS
LMT User Guide
Figure 5-1 Alarm box
When the BSC6900 reports a fault alarm to the LMT, the alarm box is activated to provide
audible and visual indications based on the alarm severity. When the LMT receives the fault
alarm, the alarm box generates a sound. The sound stops when the alarm is cleared. You can
also use the LMT to manually stop the sound.
NOTE
The alarm box does not provide any indication for event alarms.
5.2 Managing Alarm Logs

Alarm logs are used to record alarm details. They are collected by the OMU and stored in the
OMU database. To minimize storage requirements on the hard drive of the OMU, limitations
must be imposed on the number and the storage duration of alarm logs.
5.2.1 Setting Storage Limitations of Alarm Logs

This section describes how to set the maximum number of alarm logs that can be stored in the
OMU database and the maximum storage duration. Only user admin, OPERATOR-level users,
ADMINISTRATOR-level users, and authorized CUSTOM-level users can perform this
operation.
Prerequisites
Issue 02 (2015-05-08)

67
BSC6900 UMTS
LMT User Guide
Procedure
Step 1 Run the SET ALMCAPACITY command to set the maximum number of alarm logs that can
be stored in the OMU database and the maximum storage duration.
----End
5.2.2 Querying Storage Limitations of Alarm Logs

This section describes how to query the maximum number of alarm logs that can be stored in
the OMU database and the maximum storage duration.
Prerequisites
Procedure
Step 1 Run the LST ALMCAPACITY command to query the maximum number of alarm logs that
can be stored in the OMU database and the maximum storage duration.
----End
5.3 Managing Alarm Masking Conditions

Alarms that meet alarm masking conditions are not reported to the LMT or U2000. These alarms
cannot be queried on the LMT or U2000 but are still saved on the OMU. This section describes
how to manage alarm masking conditions.
5.3.1 Creating an Alarm Masking Condition

This section describes how to create an alarm masking condition. Only user admin,
OPERATOR-level users, ADMINISTRATOR-level users, and authorized CUSTOM-level
users can perform this operation.
Prerequisites
Procedure
Step 1 Run the ADD OBJALMSHLD command to create an alarm masking condition. The alarm
masking condition successfully created takes effect immediately.
NOTE
l The name of a new alarm masking condition must be unique. Otherwise, the alarm masking condition
cannot be created.
l A maximum of 100 alarm masking conditions can be created for each BSC6900.
Issue 02 (2015-05-08)

68
BSC6900 UMTS
LMT User Guide
Step 2 Run the LST OBJALMSHLD command and enter required parameters to query whether the
alarm masking condition is successfully created.
----End
5.3.2 Deleting an Alarm Masking Condition

If you do not want to mask an alarm generated by the BSC6900, delete all alarm masking
conditions related to this alarm. Only user admin, OPERATOR-level users,
operation.
Prerequisites
Procedure
Step 1 Run the LST OBJALMSHLD command to check whether the alarm masking condition to be
deleted exists.
If...
Then...
The alarm masking condition exists,
Go to Step 2.
The alarm masking condition does not exist,
No further action is required.
Step 2 Run the RMV OBJALMSHLD command, specify Object Type, and set other parameters as
required to delete an alarm masking condition.
----End
5.3.3 Querying an Alarm Masking Condition

This section describes how to query a specific alarm masking condition.
Prerequisites
Procedure
Step 1 Run the LST OBJALMSHLD command and specify Query Mode to query an alarm masking
condition.
----End
5.4 Managing the Alarm Masking Switch of Derived Alarms

When a fault occurs, beside a fault alarm, some related alarms may be generated. These alarms
are termed derived alarms. The BSC6900 can mask derived alarms. By default, derived alarms
Issue 02 (2015-05-08)

69
BSC6900 UMTS
LMT User Guide
are not reported to the LMT. Unless otherwise specified, derived alarms are not stored on the
OMU and cannot be queried.
5.4.1 Enabling/Disabling the Alarm Masking Switch of Derived

Alarms
This section describes how to enable and disable the alarm masking switch of the BSC6900
derived alarms. You can enable the alarm masking switch by setting it to ON and disable the
alarm masking switch by setting it to OFF. Only user admin, OPERATOR-level users,
operation.
Prerequisites
l
You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration
Rights).
Procedure
Step 1 Run the SET ALMML command to enable or disable the alarm masking switch of derived
alarms.
----End
5.4.2 Querying the Alarm Masking Switch of Derived Alarms

This section describes how to query the alarm masking switch of the BSC6900 derived alarms.
Prerequisites
Procedure
Step 1 Run the LST ALMML command to query the alarm masking switch of derived alarms.
----End
5.5 Monitoring Alarms

This section describes how to use the LMT to monitor alarm information in real time. The alarm
information is displayed in the Alarm Browse window on the LMT.
5.5.1 Browsing Alarms/Events

This section describes how to use the LMT to browse fault alarms and event alarms. Fault alarms
and event alarms are displayed on the Browse Alarm/Event tab page of the Alarm/Event
window. By browsing alarm information, you can learn the operating status of the system in real
time.
Issue 02 (2015-05-08)

70
BSC6900 UMTS
LMT User Guide
Prerequisites
Procedure
Step 1 On the LMT main page, click Alarm/Event. The Browse Alarm/Event tab page is displayed.
The Normal Alarm, Event, and Maintenance mode alarm tab pages are displayed under the
Browse Alarm/Event tab.
Step 2 Browse alarms on the Browse Alarm/Event tab page.
Step 3 To view details of an alarm, double-click it. The Detail dialog box is displayed, presenting
detailed information about the alarm.
Step 4 To save an alarm record, select the alarm record, right-click it, and choose Save Selected from
the shortcut menu. To save all alarm records, right-click any place in the area where alarms are
displayed and choose Save All from the shortcut menu; or click Save All.
NOTE
You can drag rows on the Browse Alarm/Event tab page to rearrange the row order. Within a Cookie
validity period, the row order on the Browse Alarm/Event tab page is the same as the row order when you
closed the tab page last time.
----End
5.5.2 Querying Alarm/Event Logs

This section describes how to query alarm and event logs from the OMU database. By viewing
alarm and event logs, you can learn the past operating status of the system.
Prerequisites
Context
You can set the following query criteria:
l
Alarm type
Alarm severity
Alarm time
Filtering criteria
Maintenance mode flag
Number of logs to be queried
Cleared time
NodeB type
Alarm-managed objects
Alarm ID
Alarm serial No.
Issue 02 (2015-05-08)

71
BSC6900 UMTS
LMT User Guide
Procedure
l
Using menus
1.
On the LMT main page, click Alarm/Event. The Browse Alarm/Event tab page is
displayed.
2.
On the Query Alarm/Event Log tab page, click Query Settings. The Query
Settings dialog box is displayed.
3.
Set query criteria as required. To reset the query criteria, click Reset. To reset only
the NodeB type, select Filter By NodeB.
NOTE
After performing query by Filter By NodeB, you can click Filter to reset query criteria.
4.
Click Query. The query result is displayed in the Result area.
5.
To view details of an alarm, double-click it. The Detail dialog box is displayed,
presenting detailed information about the alarm.
6.
To save an alarm record, select the alarm record, right-click it, and choose Save
Selected from the shortcut menu. To save all alarm records, right-click any place in
the area where alarms are displayed and choose Save All from the shortcut menu; or
click Save All.
NOTE
You can drag rows on the Query Alarm/Event Log tab page to rearrange the row order. Within
a Cookie validity period, the row order on the Query Alarm/Event Log tab page is the same
as the row order when you closed the tab page last time.
Using MML commands

1.
Run the LST ALMLOG command to query alarm logs.
----End
5.5.3 Querying Suggestions on Alarm/Event Handling

This section describes how to query suggestions on handling an alarm.
Prerequisites
Context
The LMT provides the following help information about alarms:
l
Alarm/event description
Impact on the system
System actions
Handling suggestions
Procedure
Step 1 On the Alarm/Event tab page, double-click an alarm on the Browse Alarm/Event or Query
Alarm/Event Log tab page. The Detail dialog box is displayed.
Issue 02 (2015-05-08)

72
BSC6900 UMTS
LMT User Guide
Step 2 In the Detail dialog box, click Solution.... The online help window is displayed.
NOTE
You can also select an alarm, right-click it, and choose Solution from the shortcut menu to view the online
help of this alarm.
Step 3 View the handling suggestions or other required information in the online help.
Step 4 To exit from the online help, close the online help window.
----End
5.5.4 Querying Alarm/Event Configuration

This section describes how to query alarm/event configuration.
Prerequisites
Context
You can set the following query criteria:
l
ID:
Specifies Start ID and End ID of alarms/events whose configuration information is to be
queried.
Severity:
Specifies the alarm severity of alarms/events whose configuration information is to be
queried.
Modification Flag:
Specifies the modification flag of alarms/events whose configuration information is to be
queried. If All is selected, configuration information of alarms/events whose Modification
Flag is set to Unmodified or Modified is displayed in the query result.
Shield Flag:
Specifies the shield flag of alarms/events whose configuration information is to be queried.
If All is selected, configuration information of alarms/events whose Shield Flag is set to
Shielded or Unshielded is displayed in the query result.
To Alarm Box Flag:

Specifies the to-alarm-box flag of alarms/events whose configuration information is to be
queried. If All is selected, configuration information of alarms/events whose To Alarm
Box Flag is set to Report or Not Report is displayed in the query result.
Return Amount:
Specifies the number of alarms whose configuration information is to be queried.
Procedure
Step 1 On the LMT main page, click Alarm/Event. The Alarm/Event tab page is displayed.
Issue 02 (2015-05-08)

73
BSC6900 UMTS
LMT User Guide
Step 2 Click the Query Alarm/Event Configuration tab and click Query Settings. The Query
Step 3 Set query criteria as required.
Step 4 Click Query. The query result is displayed in the Result area.
NOTE
To modify the configuration of an alarm, select an alarm and click Modify Configuration, or right-click
the alarm in the Result area and choose Modify Configuration from the shortcut menu.
----End
5.5.5 Filtering Alarms/Events

This section describes how to filter alarms according to specified filtering criteria, such as sites
and alarm types. Alarms filtered out are still reported to the LMT and saved on the OMU, but
not displayed on the Browse Alarm/Event tab page.
Prerequisites
Procedure
Step 2 On the Browse Alarm/Event tab page, click Filter Settings. The Filter Settings dialog box is
displayed.
Step 3 In the Filter Settings dialog box, specify filtering criteria, such as Alarm Source and Alarm
ID. Then, click OK. Alarms meeting the specified criteria are displayed.
NOTE
l You can select BSC and NodeB for Alarm Source Type. When you select NodeB for Alarm Source
Type, alarms related to the NodeB are displayed in the filtering result. These alarms are not generated by
the NodeB but the RNC.
l When you specify Alarm Source Type, all alarm sources of the selected type are displayed in the alarm
source type area.
l You can manually type an alarm source in Selected Source.
l You can manually type an alarm source in Selected Source after specifying Alarm Source Type.
Association display is supported in the input box under Selected Source. For example, if you type 3, all
alarm sources of the source type starting with 3 are displayed in the box under Selected Source.
----End
5.5.6 Setting Display Attributes for Alarms/Events

This section describes how to set display attributes for alarms/events in the Setting dialog box.
After you set the display attributes, the settings take effect on alarms/events on the following
tab pages: Browse Alarm/Event, Query Alarm/Event Log, and Query Alarm/Event
Configuration.
Issue 02 (2015-05-08)

74
BSC6900 UMTS
LMT User Guide
Prerequisites
Context
You can set the following display attributes for alarms/events:
l
Colors
Table columns
Display tips
Procedure
Step 2 Click Settings on the upper right of the Alarm/Event tab page. The Settings dialog box is
displayed.
Step 3 In the Settings dialog box, set Color, Table Columns, Auto-deletion, and Tips.
l Color:
You can set background colors for the following alarm/event types: Critical, Major,
Minor, Warning, and Cleared.
l Auto-deletion:
You can select Enable auto-deletion and specify the period for automatic deletion of cleared
alarms.
l Tips:
Two options are available: Enable and Disable. If you select Enable, details about an alarm/
event are displayed when you put the cursor on the alarm/event. If you select Disable, details
about an alarm/event are displayed only when you double-click the alarm/event.
l Table Columns:
You can specify the information to be displayed in the alarm/event table. The following table
describes all fields for an alarm.
Issue 02 (2015-05-08)
Field
Name
Description
Serial No.
Specifies the alarm generating sequence. This field identifies an alarm

record in an alarm log.
ID
Specifies the alarm ID. For a product, this field identifies an alarm.
Name
Specifies the alarm name. For a product, this field identifies an alarm and
has a one-to-one mapping relationship with the alarm ID.
Severity
Specifies the severity of the alarm on services.
Event Type
Specifies the event type of the alarm.
Alarm
Source
Specifies the network element that generates the alarm.

75
BSC6900 UMTS
LMT User Guide
Field
Name
Description
Type
Specifies that the alarm is an Alarm or Event.
Maintenanc
e Mode Flag
Specifies whether the alarm is triggered by maintenance and engineering

operations, such as capacity expansion or upgrades.
Raised Time
Specifies the time when the alarm is generated.
Changed
Time
Specifies the time when Severity of the alarm or Serial No. of the root
alarm is changed.
Cleared
Time
Specifies the time when the alarm is cleared.
Common
Specifies whether the alarm is generated by a common component.

NOTE
A multi-mode product comprises common components, such as power supply and
temperature control devices. Alarms generated by these common components are
termed common alarms.
Special Info
Specifies whether special information is reported.
Location
Info
Specifies information required for locating faults.
Root CSN
Specifies the serial number of the root alarm.
Cleared
Type
Specifies the way in which the alarm is cleared. Alarms can be cleared in
any of the following ways:
l Normal clear:
Alarms are normally cleared.
l Reset clear:
After the system is restarted, alarms are automatically cleared.
l Manual clear:
Alarms are manually cleared.
l Configuration clear:
After the configuration of a board is deleted, alarms related to the board
are automatically cleared.
l Correlation clear:
After receiving the root alarm of an active alarm, the fault management
system reports the root alarm and automatically clears the active alarm.
l Override clear:
Earliest alarms are removed to free disk space. If some earliest alarms
are still active, they are automatically cleared.
l State switchover clear:
If a device switches from one state to another, the active alarm reported
by the device in the former state is automatically cleared. The device in
the latter state reports the alarm again.
Issue 02 (2015-05-08)

76
BSC6900 UMTS
LMT User Guide
Field
Name
Description
Sync Serial
No.
Specifies the sequence for sending alarm report messages. The

synchronization serial number ensures data synchronization between the
element management system (EMS) and network elements (NEs). The
alarm generating message and alarm clearing message have different
synchronization serial numbers.
----End
5.5.7 Manually Clearing an Alarm/Event

When an alarm can be neglected or the fault triggering the alarm has been rectified, you can
manually clear the alarm. This section describes how to clear an alarm/event. Only user
admin, OPERATOR-level users, ADMINISTRATOR-level users, and authorized CUSTOMlevel users can perform this operation.
Prerequisites
Context
You can clear an alarm/event using menus or MML commands.
Procedure
l
Using menus
1.
On the LMT main page, click Alarm/Event and select an active alarm to be cleared
on the Browse Alarm/Event or Query Alarm/Event Log tab page. Click Clear
Alarm. The Confirm dialog box is displayed.
2.
Click OK in the Confirm dialog box. Manually cleared is displayed in the Cleared
Type column.
NOTE
You can also right-click an alarm to be cleared and choose Clear Alarm from the shortcut menu.
Using MML commands

1.
Run the RMV ALMFLT command to manually clear an alarm.
----End
5.5.8 Deleting Alarms/Events

This section describes how to delete cleared alarms/events.
Prerequisites
Issue 02 (2015-05-08)

77
BSC6900 UMTS
LMT User Guide
Procedure
Step 1 On the Browse Alarm/Event or Query Alarm/Event Log tab page under the Alarm/Event
tab, click Delete Selected Cleared Alarms or Delete All Cleared Alarms to delete the alarms/
events as required. Table 5-3 describes the functions of the buttons.
Table 5-3 Functions of the buttons
Button
Description
Delete Selected Cleared

Alarms
Deletes cleared alarms that are selected in the active window. This
button is available on the Browse Alarm/Event and Query
Alarm/Event Log tab pages.
Delete All Cleared

Alarms
Deletes all cleared alarms that are displayed in the active window.
This button is available on the Browse Alarm/Event and Query
Alarm/Event Log tab pages.
----End
5.5.9 Refreshing the Alarm/Event Window

This section describes how to manually refresh the alarm/event window to obtain the latest alarm
information.
Prerequisites
Procedure
Step 1 On the Browse Alarm/Event or Query Alarm/Event Log tab page under the Alarm/Event
tab, click Refresh or choose Refresh from the shortcut menu.
NOTE
l On the Browse Alarm/Event tab page, alarm information is updated in real time. Cleared alarms are
displayed in gray and newly generated alarms are added to the top of the alarm list. When you manually
refresh the tab page, cleared alarms are removed from the Browse Alarm/Event tab page.
l On the Query Alarm/Event Log tab page, alarm information is not updated in real time. When you
manually refresh the tab page, the query result on the tab page is updated according to the previously
set query criteria.
----End
5.6 Managing the Alarm Box

The BSC6900 uses Huawei universal alarm box to provide audible and visual indications when
an alarm is reported. The alarm box notifies maintenance engineers of alarms in time, thereby
facilitating operation and maintenance.
Issue 02 (2015-05-08)

78
BSC6900 UMTS
LMT User Guide
5.6.1 Querying Alarm Box Information

This section describes how to query the version information of the alarm box and active alarms
that drive the alarm box.
Prerequisites
l
The BSC6900 has been connected to the alarm box.
The Convert Management System has been started and can communicate with the OMU
properly.
Run the LST BOXVER command to query the version information of the alarm box.
Run the LST BOXALM command to query active alarms that drive the alarm box.
Procedure
----End
5.6.2 Querying the Number of Alarms of a Specific Severity

This section describes how to query the number of alarms of a specific severity.
Prerequisites
l
properly.
Context
When the BSC6900 reports one or more fault alarms of the same severity to the LMT, the LED
corresponding to the severity flashes on the alarm box. Users, however, cannot identify the
number of alarms of the severity from the flashing LED.
Procedure
Step 1 Run the LST BOXLGT command to query the number of the alarms of a specific severity.
----End
5.6.3 Performing Operations on the Alarm Box

This section describes how to reset the alarm box, turn off the alarm LEDs, and stop the alarm
sound.
Prerequisites
l
Issue 02 (2015-05-08)

79
BSC6900 UMTS
LMT User Guide
properly.
Run the RST ALMBOX command to reset the alarm box.
Run the CLR BOXLGT to manually turn off the alarm LEDs.
Run the STP BOXSND command to stop the alarm sound.
Procedure
----End
5.6.4 Querying the Alarm Suppression Level of the Alarm Box

This section describes how to query and set the alarm suppression level of the alarm box. Only
alarms of a severity equal to or higher than the alarm suppression level are reported to the alarm
box.
Prerequisites
l
Context
Only user admin, OPERATOR-level users, ADMINISTRATOR-level users, and authorized
CUSTOM-level users are authorized to set the alarm suppression level.
Procedure
l
Run the LST ALMSCRN command to query the alarm suppression of the alarm box.
Run the SET ALMSCRN command to set the alarm suppression of the alarm box.
----End
Issue 02 (2015-05-08)

80
BSC6900 UMTS
LMT User Guide
6 Log Management
Log Management
About This Chapter

This section describes how to use the LMT to manage the BSC6900 logs, which can be saved
in .txt and .csv files. Only user admin, ADMINISTRATOR-level users, and authorized
CUSTOM-level users can manage the logs.
6.1 Logs
Logs are classified into operation logs, security logs, and running logs.
6.2 Setting Log Storage Limitations
This section describes how to set storage limitations on operation logs and security logs, such
as the maximum storage duration and the maximum number of records. If some operation logs
and security logs are stored for a period longer than the maximum storage duration, the OMU
database automatically deletes these logs. If the number of records stored exceeds the allowed
maximum value, the OMU database automatically deletes the earliest records.
6.3 Querying Operation/Security Logs
This section describes how to query operation and security logs of the BSC6900 from the OMU
database.
6.4 Obtaining Operation/Security Logs
This section describes how to export operation logs and security logs from the OMU to the
directory OMU active workspace installation directory\ftp\operator_log\exp_log and use the
File Manager or FTP Client tool to download the logs to the LMT PC.
6.5 Obtaining Running Logs
This section describes how to upload running logs to the directory bam\common\fam\famlog
and use the File Manager or FTP Client to download the running logs to the LMT PC.
6.6 Collecting Logs
This section describes how to collect logs for fault analysis. There are several types of logs, such
as host logs, OMU logs, database logs, system event logs, operation logs, OMU installation logs,
remote upgrade logs, security logs, and alarm logs.
Issue 02 (2015-05-08)

81
BSC6900 UMTS
LMT User Guide
6 Log Management
6.1 Logs
Logs are classified into operation logs, security logs, and running logs.
Operation Logs
Operation logs record the information about operations on the BSC6900 in real time and are
saved on the OMU database.
The operation logs are used to analyze the association between device faults and operations.
Security Logs
Security logs record information about security events occurring on network elements (NEs) or
the element management system (EMS).
The security logs are used to audit and trace security events, such as login, logout, and
authorization.
Running Logs
Running logs record the operating information of the BSC6900 host in real time.
The running logs are used for fault location, routine inspection, and device monitoring.
6.2 Setting Log Storage Limitations

This section describes how to set storage limitations on operation logs and security logs, such
as the maximum storage duration and the maximum number of records. If some operation logs
and security logs are stored for a period longer than the maximum storage duration, the OMU
database automatically deletes these logs. If the number of records stored exceeds the allowed
maximum value, the OMU database automatically deletes the earliest records.
Procedure
Step 1 Run the SET LOGLIMIT command and specify Time Limit, Counts Limit, and Log Type.
Run the LST LOGLIMIT command to query the storage limitations. For storage limitations
on other logs, see "OMU Folder Size List" in OMU Administration Guide.
----End
6.3 Querying Operation/Security Logs

This section describes how to query operation and security logs of the BSC6900 from the OMU
database.
Procedure
Step 1 Run the LST OPTLOG command and set query criteria as required to query operation logs.
Issue 02 (2015-05-08)

82
BSC6900 UMTS
LMT User Guide
6 Log Management
NOTE
If no query criteria are set, the LMT displays the latest 64 operation records.
Step 2 Run the LST SECLOG command and set query criteria as required to query security logs.
NOTE
If no query criteria are set, the LMT displays the security logs generated on the current day.
----End
6.4 Obtaining Operation/Security Logs

This section describes how to export operation logs and security logs from the OMU to the
directory OMU active workspace installation directory\ftp\operator_log\exp_log and use the
File Manager or FTP Client tool to download the logs to the LMT PC.
Prerequisites
l
You have logged in to the LMT with an ADMINISTRATOR-level account authorized to

perform this operation.
You are authorized to download files from the OMU to the LMT PC.
Using the File Manager
Procedure
1.
Run the EXP LOG command, set Log Type to OPTLOG(Operation Log) or
SECLOG(SECURITY LOG), and set other parameters as required.
NOTE
The default path for saving the exported log is OMU active workspace installation directory\ftp
\operator_log\exp_log on the active workspace of the OMU.
2.
On the LMT main page, click File Manager to start the File Manager.
3.
In the File Navigation Area, type OMU active workspace installation directory
\ftp. In the File List Area, select the operation log exported in Step 1. Then, click
Download to download the log to the LMT PC.
Using the FTP Client

1.
Run the EXP LOG command, set Log Type to OPTLOG(Operation Log) or
SECLOG(SECURITY LOG), and set other parameters as required.
NOTE
The default path for saving the exported log is OMU active workspace installation directory\FTP
on the OMU active workspace.
2.
Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP
Client. The FTP Client is started.
3.
In the server entry bar on the FTP Client, enter the external virtual IP address of the
OMU, the FTP user name, and the password.
NOTE
The FTP user name and password are set when the OMU is being installed. By default, the
FTP user name is FtpUsr.
Issue 02 (2015-05-08)

83
BSC6900 UMTS
LMT User Guide
6 Log Management
4.
Click Enter to connect to the OMU. The connection status is displayed in the
Connection tips pane.
5.
When the connection is successful, double-click OMU active workspace installation

directory\ftp in the server file list. Files in the directory are displayed in the server
file list pane.
6.
Double-click the file to download it to the LMT PC.
7.
When the file is successfully downloaded, choose System > Exit on the FTP Client
or close the FTP Client window to exit from the FTP Client.
----End
6.5 Obtaining Running Logs

This section describes how to upload running logs to the directory bam\common\fam\famlog
and use the File Manager or FTP Client to download the running logs to the LMT PC.
Context
l
Running logs are named in the format BSCID_subrack number/Log/yyyy/mm/dd/hh/

mm/ss.zip. For example, if a running log of Extended Processing Subrack (EPS) 3 is
uploaded to the OMU of BSC 1 at 17:19:47 of November 7, 2011, the log is named
BSC0001_03Log20111107171947.zip. BSC0001_03Log20111107171947.zip indicates
that the log has been successfully uploaded and compressed.
BSC0001_03Log20111107171947.tmp indicates that the log is being uploaded.
By default, running logs are uploaded to and saved in the directory bam\common\fam
\famlog on the OMU.
Using the File Manager
Procedure
1.
Run the ULD LOGTOOMU command and enter the number of the subrack whose
running log is to be uploaded to the OMU.
2.
On the LMT main page, click File Manager to start the File Manager.
3.
In the File Navigation Area, double-click bam\common\fam\famlog. In the File

List Area, select the running log uploaded in Step 1. Then, click Download to
download the log to the LMT PC.
Using the FTP Client

1.
Run the ULD LOGTOOMU command and enter the subrack number to upload the
corresponding running log to the OMU.
2.
Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP
Client. The FTP Client is started.
3.
In the server entry bar on the FTP Client, enter the external virtual IP address of the
OMU, the FTP user name, and the password.
NOTE
The FTP user name and password are set when the OMU is being installed. By default, the
FTP user name is FtpUsr.
Issue 02 (2015-05-08)

84
BSC6900 UMTS
LMT User Guide
6 Log Management
4.
Click Enter to connect to the OMU. The connection status is displayed in the
Connection tips pane.
5.
When the connection is set up successfully, double-click bam\common\fam

\famlog in the server file list. Files in the path are displayed in the server file list pane.
6.
Double-click the running log to download it to the LMT PC.
7.
When the running log is successfully downloaded, choose System > Exit or close the
FTP Client window to exit from the FTP Client.
----End
6.6 Collecting Logs

This section describes how to collect logs for fault analysis. There are several types of logs, such
as host logs, OMU logs, database logs, system event logs, operation logs, OMU installation logs,
remote upgrade logs, security logs, and alarm logs.
Procedure
Step 1 Run the COL LOG command and set parameters as required to collect logs. For more
description about logs, see Table 6-1.
NOTE
l The path for saving logs depends on the active workspace of the OMU. When the active workspace of the
OMU is version_a, the path for saving logs is version_a. When the active workspace of the OMU is
version_b, the path for saving logs is version_b.
l Log files that are not compressed into the BZ2 format in the OMU active workspace installation directory
\common\fam\famlog and the OMU active workspace installation directory\common\fam\famlogfmt
directories will not be collected.
Table 6-1 Description about logs
Issue 02 (2015-05-08)
Type
File Path
Description
PFM_NOM_RESULT
(Normal Performance Result
File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Records normal-period
traffic statistics that an NE
reports to the U2000.
Used for analyzing traffic
statistics.
PFM_RESULT
(Performance Result File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Records traffic statistics that

an NE reports to the U2000.
statistics.
HOST_PFM_RESULT
(Performance Result File
from Host)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Records traffic statistics that

boards report to the OMU.
statistics.

85
BSC6900 UMTS
LMT User Guide
Issue 02 (2015-05-08)
6 Log Management
Type
File Path
Description
ACTIVE_DEF_MEAS_FIL
E(Active Default
Measurement Task File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Specifies the active traffic

statistic definition file that
the U2000 delivers to NEs.
statistics.
STANDBY_DEF_MEAS_F
ILE(Standby Default
Measurement Task File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Specifies the standby traffic

statistic definition file that
the U2000 delivers to NEs.
statistics.
PFM_SWITCHS(Switch
Information for
Performance)
Records reserved
enumerated values.
HISTORY_ALARM
(History Alarm File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Records alarms and events

reported by all NEs.
Used for analyzing alarms
and events.
HISTORY_FAULT(History
Fault File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Records faults reported by all

NEs.
and events.
ALM_SYSTEM_CFG(The
Configured Information of
Alarm)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Records the configuration

information related to alarm
management.
and events.
SECURITY_LOG(Security
Logs)
/bam/version_a/ftp/
COLLOGINFO/SEC-LOG/
Specifies security logs of an

NE.
Used for analyzing securityrelated operations on the NE.
OPT_LOG(Operation Logs)
/bam/version_a/ftp/
COLLOGINFO/OPT-LOG/
Records operation logs of an

NE.
Used for analyzing user
operations on the NE.

86
BSC6900 UMTS
LMT User Guide
6 Log Management
Type
File Path
Description
OMU_LOG(The Log
Information of OMU)
l Independent Mode: /bam/

version_a/ftp/
COLLOGINFO/
SINGLE-BAM/
Records all running logs and

status information of the
OMU board.
Used for analyzing OMU
faults and status.
l Active/Standby Mode
Active OMU
/bam/version_a/ftp/
COLLOGINFO/
Active-BAM/
Standby OMU
/bam/version_a/ftp/
COLLOGINFO/
STANDBY-BAM/
OMU_SIM_LOG(The
Simple Log of OMU)
l Independent Mode: /bam/

version_a/ftp/
COLLOGINFO/
SINGLE-SIM-BAM/
l Active/Standby Mode
Active OMU
Records the running logs and

status information of the
OMU board, except
information about scheduled
tasks and the standby
workspace.
/bam/version_a/ftp/
COLLOGINFO/
Active-SIM-BAM/
Standby OMU
/bam/version_a/ftp/
COLLOGINFO/
STANDBY-SIMBAM/
Issue 02 (2015-05-08)
BSC_CFG_MML(The Data
Configure File of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
ExportCfgmml/
Records the BSC

configuration data.
Used for configuration data
restoration.
CELL_BASIC_INFO(The
Basic Information of Cells)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
CellBasicInfo/
Records the basic

information of cells under a
BSC.
Used for checking the
mapping relationships
between cell IDs and internal
cell IDs.
BSC_SERIES_NO(The
Series No. of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
Records the Equipment

Serial Number (ESN) of a
BSC.
Used for checking the license
validity.

87
BSC6900 UMTS
LMT User Guide
Issue 02 (2015-05-08)
6 Log Management
Type
File Path
Description
DB_BAK(The Backup File

of the Database)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
MysqlDbBak/
Records backed up OMU

database information.
Used for data restoration.
DEBUG_LOG(The
Common Debug Log)
/bam/common/fam/
famlogfmt/
Records software running

errors.
Used for analyzing software
defects.
SDBG_LOG(The Channel
Fault Log)
/bam/common/fam/
famlogfmt/
Records channel faults.
LAST_WORD(The Last
Word Log)
/bam/common/fam
Records the log information

generated before unexpected
board resetting.
Used for locating causes of
unexpected board resetting.
DSP_DEBUG_LOG(The
Debug Log of DSP)
/bam/common/fam/
famlogfmt/
Records DSP debug logs.

Used for locating DSP faults.
HOST_LOG(The Running
Log of the Host)
/bam/common/fam/famlog/
Records host operation logs.
3G_CHR_LOG(The CHR
Log for UMTS)
/bam/common/fam/
famlogfmt/
Records call faults, except

call access failures and call
drops.
soft handover, hard
handover, relocation, or cell
update failures.
BSC_INFO(The Basic
Information of the BSC)
/bam/version_a/ftp/
COLLOGINFO/BSC-LOG/
Records the BSC software

patch information, and the
bar code, software
information, hardware
information, loading
information, and license of
each board.
Used for checking whether
the software versions, data,
and licenses of boards are
correct.
BIOS_LOG(BIOS Log)
/bam/common/fam/
famlogfmt/
Records errors that occur

during the BIOS system
running.
Used for locating BIOS
faults.

88
BSC6900 UMTS
LMT User Guide
6 Log Management
Type
File Path
Description
CALLFAULT_LOG
(CALLFAULT Log)
/bam/common/fam/
famlogfmt/
Records call access failures

and call drops.
call access failures and call
drops.
PCHR_LOG(PCHR Log)
/bam/common/fam/
famlogfmt/pchr
Records detailed information

of each call, including service
access, call release,
handover, DCCC, and signal
quality.
Used for analyzing
performance and used as a
reference for handling
subscriber complaints.
SYSFAULT_LOG
(SYSFAULT Log)
/bam/common/fam/
famlogfmt/sysfault/
Records severe software/

hardware faults such as
resource leakages and device
faults.
Used for checking network
health status.
----End
Issue 02 (2015-05-08)

89
BSC6900 UMTS
LMT User Guide
7 Trace Management
Trace Management
About This Chapter

This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 trace
tasks can be started simultaneously on the same LMT, and a maximum of 6 trace tasks can be
started simultaneously for the same parameter of a trace item. When OMU boards perform an
active/standby switchover, monitoring cannot be restarted until 30 minutes after the switchover.
7.1 Concepts
This chapter describes tracing principles, tracing modes, and required operation rights. Do not
start excessive tracing tasks in heavy traffic scenarios, because starting excessive tracing tasks
slows the LMT responses. In this case, set Trace Mode to Save To OMU before starting a
tracing task.
7.2 Basic Tracing Operations
The basic operations of message tracing apply to all BSC6900 message tracing tasks.
7.3 Device Commissioning
This section describes how to perform routine device commissioning.
7.4 UMTS Services
This section describes how to perform tracing tasks related to UMTS services.
Issue 02 (2015-05-08)

90
BSC6900 UMTS
LMT User Guide
7 Trace Management
7.1 Concepts
This chapter describes tracing principles, tracing modes, and required operation rights. Do not
start excessive tracing tasks in heavy traffic scenarios, because starting excessive tracing tasks
slows the LMT responses. In this case, set Trace Mode to Save To OMU before starting a
tracing task.
7.1.1 Tracing Principles

This describes the principles of message tracing. It also describes how to create and close a
message tracing task and how the service module of a board reports traced messages to the LMT.
Principles of Message Tracing

Figure 7-1 shows the principles of message tracing.
Figure 7-1 Principles of message tracing
Internal Procedure for Creating a Tracing Task

1.
When you create a tracing task on the LMT, the LMT sends a binary command to the OMU
to create the task.
2.
The OMU assigns an ID to the task and forwards the command to the debugging module
of the specified board.
3.
After receiving the command, the debugging module records the filter parameters of the
trace data in the filter table and notifies the service module.
4.
The service module updates the local filter table according to the message from the
debugging module.
Internal Procedure for Closing a Tracing Task

1.
When you close a tracing task on the LMT, the LMT sends a binary command to the OMU
to delete the task.
2.
The OMU forwards the command to the specified board according to the task ID.
3.
The debugging module and service module delete the task from the filter table.
Issue 02 (2015-05-08)

91
BSC6900 UMTS
LMT User Guide
7 Trace Management
Internal Procedure for the Service Module to Report Traced Messages to the LMT
1.
The service module compares the collected messages against the local filter table and
reports the qualified messages to the OMU.
2.
The OMU forwards the traced messages to the LMT that creates the task according to the
task ID.
3.
The LMT parses the messages and displays them on the tracing window.
7.1.2 Management of Tracing Operation Rights

You must have the required rights to perform message tracing operations.
The users at the following levels can perform the tracing tasks online: admin, USER,
OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command group G_10.
That is, only the GUEST-level users and CUSTOM-level users that are not entitled to use
command group G_10 cannot perform tracing tasks online.
NOTE
Group G_10 consists of binary commands for creating tracing and monitoring tasks.
7.1.3 Tracing Mode

The tracing mode decides where the signaling tracing results are stored.
Interface signaling tracing modes are as follows:
l
Report And Not Show

This is an instant tracing mode. The tracing results are sent from the OMU to the LMT PC.
In this tracing mode, you can select Save File to save the tracing result file to the LMT PC
in .tmf format.
Report And Show

This is an instant tracing mode. The tracing results are sent from the OMU to the LMT PC.
In this tracing mode, you can select Save File to save the tracing result file to the LMT PC
in .tmf format. The LMT parses the tracing result file and displays the analysis results in
the window.
Save to OMU
You can set Trace Period (OMU Time) for a tracing task in this mode. The tracing start
time and tracing end time refer to the time on the OMU. The tracing end time must be later
than the tracing start time. The tracing result file is saved on the OMU in .zip format and
is not sent to the LMT PC. The default save path is \bam\common\fam\trace.
Report File
The tracing result file is temporarily saved on the OMU in .zip format. Then, it is transferred
to the specified directory on the LMT PC through the FTP server.
7.1.4 Tracing Specifications

This section describes the tracing specifications.
l
Issue 02 (2015-05-08)
A maximum of 64 trace tasks can be started simultaneously on the same LMT.

92
BSC6900 UMTS
LMT User Guide
7 Trace Management
Do not start excessive tracing tasks in heavy traffic scenarios, because starting excessive
tracing tasks slows the LMT responses. In this case, set Trace Mode to Save To OMU
before starting a tracing task.
The following table lists the maximum number of tracing tasks that can be simultaneously
started for each type.
Trace Type
Specifications
Iu Interface Trace
Iupc Interface Trace
Iur Interface Trace
Iub Interface Trace
Uu Interface Trace
MNCDT Trace
Iur-p Trace
Cell Trace
IOS Trace
2
NOTE
All tasks targets a maximum of 100 calls.
UE Trace
12
NOTE
A maximum of six tasks in the debug mode can be performed
simultaneously.
Sr Interface Trace
7.2 Basic Tracing Operations

The basic operations of message tracing apply to all BSC6900 message tracing tasks.
7.2.1 Browsing Traced Messages Online

This section describes how to browse traced messages online in a message browser after a tracing
task is created.
Prerequisites
l
A tracing task is successfully created.
Traced messages are reported.
Issue 02 (2015-05-08)

93
BSC6900 UMTS
LMT User Guide
7 Trace Management
Context
l
By default, each message browser is displayed in maximized mode. To compare results

displayed in multiple message browsers, set Layout to Cascade, Tile Horizontal or Tile
Vertical.
Each of the windows is configured with a default minimum width when multiple windows
are tiled vertically. This ensures clear comparison. With this configuration, a maximum of
six windows can be displayed in a monitor with the resolution of 1280x1024. Other
windows are hidden behind the displayed windows.
The cascaded or tiled window arrangements take effect only at every setting of Layout to
Cascade, Tile Horizontal, or Tile Vertical. After such a setting, a new message browser
will still be displayed in maximized mode.
A maximum of 2000 messages can be displayed in a message browser. Newly traced

messages will replace old ones if 2000 messages are already displayed in a message
browser.
Procedure
Step 1 Browse or view traced messages in a message browser in real time. Right-click in the message
browser and choose an item from the shortcut menu to perform the associated operation as
described in Table 7-1.
Table 7-1 Operations available when browsing traced messages online
Shortcut
Description
Stop Trace Task
Suspend the tracing task.
Restart Trace Task
Resume the suspended tracing task.
Save All Messages...
Save all traced messages displayed in the message browser.
Save Selected Messages...
Save the selected messages.
Auto Scroll
Enable messages in the message browser to automatically

refresh themselves in real time and scroll upward.
Clear Messages
Clear all displayed messages from the message browser

without affecting the saved messages.
Property...
Query properties of the tracing task.
Step 2 To view details of a message, double-click it. The Message Browser window is displayed,
showing details of the message.
NOTE
During multi-user tracing or inter-RNC tracing, the display order of messages traced in real time may be
inaccurate because those messages are reported by multiple nodes in the system at the same time. You can click
the Time column to sort the messages by the time when the RNC receives the messages.
----End
Issue 02 (2015-05-08)

94
BSC6900 UMTS
LMT User Guide
7 Trace Management
7.2.2 Viewing the Interpretation of Traced Messages

This section describes how to view the interpretation of a traced message.
Prerequisites
l
Context
To view detailed description of TXT (Command Code) messages, right-click in the blank area
on the right part of the window and choose Update Text from the shortcut menu. The text
messages update once each time users choose Update Text. They do not automatically update.
Procedure
Step 1 In the message browse window, double-click the trace message.
Step 2 The Message Browser window is displayed, showing the details and meaning of the message
in protocol translation format, as shown in Figure 7-2.
Figure 7-2 Message Explanation
----End
7.2.3 Saving Traced Messages

This section describes how to save traced messages in a file to a local PC.
Issue 02 (2015-05-08)

95
BSC6900 UMTS
LMT User Guide
7 Trace Management
Prerequisites
l
A tracing task is started.
Context
The name of the file containing saved messages cannot exceed 100 characters, including the file
name extension.
The traced results can be saved either automatically or manually.
Procedure
l
Automatic saving of traced messages

Select Save File when creating a tracing task. All traced messages to be displayed in the
message browser will be automatically saved in .tmf format.
The default save path is C:\Web LMT\MBSC\output\trace\tmfFile on the local PC.
NOTE
l The LMT saves every 5,000 messages in a file. Messages starting from 5,001 are saved in another
file with a serial number and the serial number is increased by one for every subsequent 5,000
messages. For example, the 5001st to 10000th messages traced on the interface are saved in file's
name_1.tmf format by default. YYYY, MM, DD, HH, MM, and SS represent the year, month,
day, hour, minute, and second, respectively.
l The file saving messages traced by a UE tracing task is named in a different way from the file
saving messages traced by other types of tracing task. The least significant four digits of the
traced number (IMSI, TMSI, IMEI, or MSISDN) are saved in the file name. If there are fewer
than four digits, use the digits in the file name without adding more digits to reach four digits.
For example, if the least significant four digits of a UE IMSI are 1234, messages traced by a UE
tracing task of this UE are saved in a file named UE_YYYY-MM-DD-HH-MM-SS-1234_Serial
number.tmf.
l You can use the Traffic Recording Review Tool to browse messages saved in .tmf format offline.
For details, see 7.2.4 Browsing Traced Messages Offline.
Manual saving of traced messages

When a tracing task is running, you can manually save all or some of the messages in the
message browser in .tmf, .txt, or .csv format.
1.
To save all messages, right-click in the message browser and choose Save All
Messages from the shortcut menu. To save only the selected messages displayed in
the message browser, select the messages you wish to save, right-click, and choose
Save Selected Messages from the shortcut menu. The Save dialog box is displayed.
2.
Enter a file name, and specify the file type and save path.
The default save path is C:\Web LMT\MBSC\output\trace\tmfFile. The default file
name is in IP address_Tracing type_YYYY-MM-DD-HH-MM-SS.tmf format.
3.
Click Save to save the file in the specified path.
----End
Issue 02 (2015-05-08)

96
BSC6900 UMTS
LMT User Guide
7 Trace Management
7.2.4 Browsing Traced Messages Offline

This section describes how to use the Traffic Recording Review Tool to browse offline the traced
messages that are saved in .tmf format.
Prerequisites
The traced messages are saved in .tmf format.
Context
You can find the .txt or .csv files in the saved directory. Double-click them to view the traced
messages.
Procedure
Step 1 Choose Start > > All Programs > > Huawei Local Maintenance Terminal > >
TrafficRecording Review Tool.
Step 2 The Open dialog box is displayed, prompting you to select the target file. Browse to the folder
where the trace files are saved, and select the target file.
Step 3 Click Open or double-click the file. The contents of the file are displayed in the
TrafficRecording Review Tool window.
NOTE
The time format is YYYY-MM-DD HH:MM:SS(Tick). The unit of Tick is 10 ms.
Step 4 Browse the messages or double-click a specific one to read the details.
Step 5 To view the contents of more files, choose File > > Open. In the Open dialog box, select and
open files to view the traced messages that are saved in the files.
Step 6 You can further perform the following operations by right-clicking in the TrafficRecording
Review Tool window.
Issue 02 (2015-05-08)
If...
Then...
You choose Save All Messages from the

shortcut menu,
All the messages are saved in the window

in .tmf or .txt format.
You choose Save Selected Messages from

the shortcut menu,
The selected messages are saved in .tmf or .txt

format.
You choose Filter By Byte from the shortcut

menu,
Set the filter to selectively display the

information.
You choose Filter By Column from the

shortcut menu,
Filter the information by column to

selectively display the information.
You choose Find from the shortcut menu,
Locate the message that you want.

97
BSC6900 UMTS
LMT User Guide
7 Trace Management
NOTE
During multi-user tracing or inter-RNC tracing, the order in which messages traced in real time are displayed
may be inaccurate because those messages are reported by multiple nodes in the system at the same time. You
can click the Time column to sort the messages by the time when the RNC receives the messages.
----End
7.2.5 Managing Tracing Tasks

This section describes how to manage tracing tasks.
Prerequisites
l
Trace messages are reported.
Through menu operations
Procedure
1.
Click Trace on the LMT main page. The Trace tab page is displayed.
2.
On the Trace Navigation Tree pane, choose the Manage Trace Task. The Manage
Trace Task dialog box is displayed.
3.
In the displayed Manage Trace Task tab page, set the parameters as required, and
click Query to query the information about the trace tasks.
4.
To stop, restart, or delete a trace task, select the target task listed in the Result area,
and then click Stop, Restart, or Delete, respectively.
NOTE
l The tasks whose Trace Mode is Report Messages listed in the query result can only be
deleted on the LMT where it was started.
l If Trace Mode is set to Save to OMU, you can specify the tracing start time and tracing
end time. After the duration is specified, the tracing tasks in this duration will be displayed
in the area below. You do not need to set Time Settings in other trace modes.
l The tasks whose Create Type is Net Create listed in the query result are created by the
OMU according to the command from the BSC. Such tasks can only be deleted by the
admin or ADMINISTRATOR-level users.
Through MML commands

1.
Run the LST TRCTASK command to query the trace tasks.
----End
7.2.6 Managing the Trace File

This section describes how to query the trace files on the OMU and upload the trace files onto
the local PC as required.
Prerequisites
l
Issue 02 (2015-05-08)

98
BSC6900 UMTS
LMT User Guide
7 Trace Management
Procedure
l
Through menu operations

1.
Click Trace on the LMT main page. The Trace tab page is displayed.
2.
On the Trace Navigation Tree pane, choose the Manage Trace File node. The
Manage Trace File dialog box is displayed.
3.
In the displayed Manage Trace File dialog box, set the parameters in the Search
Configure area, and then click Query to view the information about the trace files
saved on the OMU.
4.
To upload a trace file to the local PC, select the target file listed in the Result area,
set the parameters in the Upload configure area, and then click Upload.
Through MML commands

1.
Run the LST TRCRST command to query the trace files.
----End
7.3 Device Commissioning

This section describes how to perform routine device commissioning.
7.3.1 Tracing OS Messages

This section describes how to trace messages between the exchange module of the OMU and
internal modules of a board or between internal modules of different boards.
Context
This task can be performed to trace the sent and received messages between two modules or
messages sent from and received by the same module.
NOTICE
Only ADMINISTRATOR-level users are authorized for performing Tracing OS Messages
because it involves private information of users.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab page is displayed.
Step 2 On the Trace Navigation Tree pane, choose Trace > > Device Commissioning. Double-click
OS Trace.
Step 3 In the OS Trace dialog box, set the parameters as required, and click Submit. The trace data
pane displays the traced message flow.
Issue 02 (2015-05-08)

99
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Type
Trace object.
Sender
Parameter
When tracing the messages exchanged between the OMU and other boards,
you must set IP Type to OMU rather than Specified IP.
Receiver
Parameter
IP Type cannot be set to OMU for the sender and the receiver
simultaneously, that is, the messages exchanged between the internal
modules of an OMU cannot be traced.
Trace Reason
l Reason of starting this tracing task.

l Pressing the Enter key is not supported. Letters, digits, spaces and the
following special characters are supported: ! @ # $ % ^ & * ( ) _ + - =
`~:",.|\<>?/{}[]
Trace Mode
See 7.1.3 Tracing Mode.
Save File
See 7.2.3 Saving Traced Messages.
----End
7.3.2 Emergency Diagnosis

This section describes how to redirect the messages printed through the serial port of a specified
subsystem to the message browse window of the LMT.
Context
NOTICE
Only ADMINISTRATOR-level users are authorized for performing Emergency Diagnosis.
Procedure
Step 2 On the Trace Navigation Tree pane, choose Trace > > Device Commissioning. Double-click
Emergency Diagnosis.
Step 3 In the Emergency Diagnosis dialog box, set the parameters as required, and click Submit. The
trace data pane displays the traced message flow.
l Pressing the Enter key is not supported. Letters, digits, spaces and the following special
characters are supported: ! @ # $ % ^ & * ( ) _ + - = ` ~ : " , . | \ < > ? / { } [ ]
----End
Issue 02 (2015-05-08)

100
BSC6900 UMTS
LMT User Guide
7 Trace Management
7.3.3 Capturing Packets

This section describes how to capture packets and locate transmission channel disconnections
and packet losses by analyzing packet headers.
Prerequisites
The communication between the LMT and the BSC is normal.
Context
l
The following problems can be located by capturing packets:

The base station controller does not receive the packet.
After entering the interface board, the packet is discarded by the board without being
sent to other boards in the system.
The packet is sent to non-interface boards, which then discard the packet.
When packets are discarded between two boards or connection cannot be established
between two boards, you can check whether the correct packets are sent to and received by
interface boards and other boards in the system by capturing backplane packets. Then you
can quickly locate the problem, which may be in an interface board or any other board in
the system.
The following types of packet capturing are supported:

Panel Ethernet packet capturing
Backplane Ethernet packet capturing
Panel Ethernet + backplane Ethernet packet capturing
Only one packet tracing task can be started for each interface board at a time. Tracing of
multiple interface boards can be started simultaneously.
Only the header of the user plane packet (not including the payload of the packet) can be
captured.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab is displayed.
Step 2 In the Trace Navigation Tree pane, choose Trace Management > Device Commissioning >
Packet Capture. The Packet Capture dialog box is displayed.
Step 3 In the Packet Capture dialog box, set parameters as required.
Step 4 Click Submit, to start capturing packets. For the specific capturing duration, see the value of
Trace Time (OMU time) in the Packet Capture interface.
NOTE
l Panel Ethernet packet capture and backplane Ethernet packet capture can be supported simultaneously. If
you only need to capture the panel Ethernet packet, set PortType(Inner) to Inner Invalid or set PortType
(Outer) to Outer Invalid.
l To capture panel Ethernet packets, set PortType (Outer) to Ethernet Frame, and set the parameters in the
Outer tab.
l To capture panel Ethernet packets, set PortType (Inner) to Ethernet Frame, and set the parameters in the
Inner tab.
Issue 02 (2015-05-08)

101
BSC6900 UMTS
LMT User Guide
7 Trace Management
l Basic Mode: just enter the basic parameters (subrack number and physical slot number) to
start the packet capturing function. Therefore, this is defined as the basic mode. Under the
basic mode, only Panel Ethernet packet capturing is supported, and backplane Ethernet
packet capturing is not supported.
Table 7-2 Basic Mode
Interface
Parameter
Description
Trace Reason

l Pressing the Enter key is not supported. Letters, digits, spaces and
the following special characters are supported: ! @ # $ % ^ & *
()_+-=`~:",.|\<>?/{}[]
Subrack No
Indicates the number of the subrack which houses the interface board.
Physical Slot No
Indicates the number of the physical slot which houses the interface
board.
Port No
Indicates the number of the port on the interface board panel.
Scene Select
Indicates the scene under which packets are captured are differentiated
by protocol type. For descriptions about protocol types, see Table
7-3.
Intercept Length
Each Ethernet frame captured (especially for long packets) is reduced

to the "Intercept length" of the packet, the rest of which is not
submitted. If the captured packet is shorter than the "Intercept length",
the actual length captured prevails.
VLAN Tag
Indicates whether the data packet carries a VLAN ID.

Tagged: The data packet carries a VLAN ID.
Untagged: The data packet does not carry a VLAN ID.
Tagged&Untagged: The data packet carries or does not carry a
VLAN ID.
For the FG2a and GOUa, VLAN Tag can be set only to Tagged or
Untagged. That is, you cannot capture packets with VLAN IDs and
those with no VLAN IDs at the same time.
Trace Time
Start Time: The start time and end time of the trace task.
Trace Time (minute): Duration of the tracing task in minutes.
Table 7-3 Protocol Types
Issue 02 (2015-05-08)
Protocol Types
Description
All Packets
All packets on the specified port

102
BSC6900 UMTS
LMT User Guide
7 Trace Management
Protocol Types
Description
DHCP Packet
IP packets whose protocol type is UDP.

The destination port number of DHCP request packets must be 67.
The destination port number of Dynamic Host Configuration Protocol
(DHCP) response packets (not using relay) must be 68.
The destination port number of DHCP response (using relay) packets
must be 67.
IP AddressSpecified Packet
All IP packets whose local and peer IP addresses are specified
802.3ah/LACP
Packet
All slow protocol packets, including 802.3ah packets and LACP

packets
ARP Packet
IP packets whose protocol type is Address Resolution Protocol (ARP),

including all request packets and response packets
ICMP Packet
IP packets whose protocol type is Internet Control Message Protocol

(ICMP)
BFD Packet
IP packets whose protocol type is UDP

The UDP destination port number must be 3784.
IPPM Packet

Issue 02 (2015-05-08)
TCP Packet
Packets whose protocol type is Transmission Control Protocol (TCP),

including O&M packets of the NodeB and TWAMP packets
GTPU Control
Packet
GTPU Data
Packet
802.1ag Packet
Packets whose protocol type is 802.1ag CFM
PTRAU Packet
Packets whose protocol type is Packet Transcoder and Rate Adapter

Unit (PTRAU)
RTP Packet
Packets whose protocol type is Real-Time Transport Protocol (RTP)
UMTS RTP
Packet
Packets whose protocol type is UMTS Real-Time Transport Protocol

(RTP). To capture these packets, set Peer IP Address to an appropriate
value.
UMTS IUUP
Packet
Packets whose protocol type is UMTS Iu User Plane. To capture these

packets, set Peer IP Address to an appropriate value.
UMTS FP
Packet
Packets whose protocol type is UMTS Frame Protocol. To capture

these packets, set Peer IP Address to an appropriate value.
IP packets whose protocol type is UDP The UDP destination port

number must be 2152.

103
BSC6900 UMTS
LMT User Guide
7 Trace Management
Protocol Types
Description
UMTS PDCP
Packet
Packets whose protocol type is UMTS Packet Data Convergence

Protocol. To capture these packets, set Peer IP Address to an
appropriate value.
UMTS IURCFP
Packet
Packets whose protocol type is UMTS IUR Common Frame Protocol.

To capture these packets, set Peer IP Address to an appropriate value.
l Advanced Mode: In addition to the basic parameters (subrack number and physical slot
number), several other parameters are required to start the packet capturing function, which
is defined as the advanced mode. The advanced mode supports panel Ethernet packet
capturing, backplane Ethernet packet capturing and panel Ethernet + backplane Ethernet
packet capturing.
Table 7-4 Advanced Mode
Interface
Parameter
Description
PortType (Outer)
Indicates capturing of packets at the port of the interface board panel.

Outer Intercept length: Each Ethernet frame captured (especially for
long packets) is reduced to the "Intercept Length" of the packet, the rest
of which is not submitted. If the captured packet is shorter than the
"Intercept Length", the actual length captured prevails.
Outer Port
Number
Indicates the number of the port on the interface board panel.
Outer Trace
Direction
l In: tracing packets entering the port of the interface board panel from
the outside.
l Out: tracing packets sent from the port of the interface board panel.
l Both: tracing packets in the two directions simultaneously.
Outer Peer MAC

Address
Specifies the peer MAC address of the Ethernet frame to be captured.

This is the destination MAC address of the packet when "Out" is selected
for the "outer trace direction"; or the source MAC address when "In" is
selected for the "outer trace direction".
If left blank, it indicates capturing of all packets at the peer MAC address.
Outer Local IP
Address
Specifies the local IP address of the IP packet to be captured.

This is the source IP address of the packet when the "Out" is selected for
the "outer trace direction"; or the destination IP address when the "In" is
If left blank, it indicates capturing of all packets at the local IP address.
Issue 02 (2015-05-08)

104
BSC6900 UMTS
LMT User Guide
7 Trace Management
Interface
Parameter
Description
Outer Peer IP
Address
Specifies the peer IP address of the IP packet to be captured.

This is the destination IP address of the packet when the "Out" is selected
for the "outer trace direction"; or the source IP address when the "In" is
If left blank, it indicates capturing of all packets at the peer IP address.
Local User
Datagram
Protocol (UDP)
Port No
Specifies the local User Datagram Protocol (UDP) port number of the IP
packet to be captured.
This is the source User Datagram Protocol (UDP) port number of the
packet when the "Out" is selected for the "outer trace direction"; or the
destination User Datagram Protocol (UDP) port number when the "In"
is selected for the "outer trace direction".
If left blank, it indicates capturing of all packets at the local User
Datagram Protocol (UDP) port.
Peer User
Datagram
Protocol (UDP)
Port No
Specifies the peer User Datagram Protocol (UDP) port number of the IP
packet to be captured.
This is the destination User Datagram Protocol (UDP) port number of
the packet when the "Out" is selected for the "outer trace direction"; or
the source User Datagram Protocol (UDP) port number when the "In" is
If left blank, it indicates capturing of all packets at the peer User
Datagram Protocol (UDP) port.
PortType (Inner)
Indicates capturing of packets at the port of the interface board

backplane.
Inner Intercept length: Each Ethernet frame captured (especially for
long packets) is reduced to the "Intercept length" of the packet, the rest
of which is not submitted. If the captured packet is shorter than the
"Intercept length", the actual length captured prevails.
Inner Port
Number
The number of the port on the interface board backplane.
Inner Trace
Direction
l In: tracing the packets entering the interface board backplane from
the SCU board.
l Out: tracing packets sent from the interface board backplane to the
SCU board.
l Both: tracing packets in the two directions simultaneously.
Inner Peer MAC

Address
Specifies the peer MAC address of the Ethernet frame to be captured.

This is the destination MAC address of the packet when the "Out" is
selected for the "inner trace direction"; or the source MAC address when
the "In" is selected for the "inner trace direction".
If left blank, it indicates capturing of all packets at the peer MAC address.
Issue 02 (2015-05-08)

105
BSC6900 UMTS
LMT User Guide
7 Trace Management
----End
Follow-up Procedure
l
You can manage packet capture in Manage Trace File on the Trace tab. You can query,
stop, delete or restart a packet capture task.
After packet capturing is complete, packet capturing log files (for example, /bam/common/
fam/trace/16778026_ packet capturing _20120927_201909.log.zip) are created and saved
on the OMU.
NOTE
Packet capturing results are generated after the task is complete.
7.3.4 AC Tracing
This section describes how to trace signaling messages over the interface between the base
station controller and access controller (AC).
Procedure
Step 2 In the Trace Navigation Tree, choose Trace > > Device Commissioning and double-click
AC Trace. The AC Trace dialog box is displayed, as shown in Figure 7-3.
Figure 7-3 AC tracing
Issue 02 (2015-05-08)

106
BSC6900 UMTS
LMT User Guide
7 Trace Management
Step 3 In the AC Trace dialog box, set parameters as required and click Submit.
Table 7-5 Parameter Description
Parameter
Description
AC Index (0-9)
AC index, which uniquely identifies an AC and can be queried by

running the LST ACADDR command.
Trace Reason

the following special characters are supported: ! @ # $ % ^ &
*()_+-=`~:",.|\<>?/{}[]
Trace Mode
Save File
----End
7.3.5 DHCP Tracing

This section describes how to trace DHCP packets.
Procedure
Step 2 In the Trace Navigation Tree, choose Trace > > Device Commissioning and double-click
DHCP Trace. The DHCP Trace dialog box is displayed, as shown in Figure 7-4.
Issue 02 (2015-05-08)

107
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-4 DHCP tracing
Step 3 In the DHCP Trace dialog box, set parameters as required and then click Submit.
Issue 02 (2015-05-08)
Parameter
Description
Subrack No.
Indicates the number of the subrack housing the board to be traced.
Slot No.
Indicates the number of the slot housing the board to be traced.

Specify the slot number in scenarios with independent boards. In
scenarios with active and standby boards, the slot number should
be an even number.
Board Type
Indicates the type of the board to be traced. The board type is

automatically displayed after the slot number is specified. It can
also be queried by running the LST BRD command.
Port Type
Indicates the transmission type of the port.

108
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Port No./Link No./

Group No.
Indicates the number of the port, link, or port group to be traced. If

this field is not specified, the entire board will be traced. It is
recommended that users should not specify this field.
DHCP Product ID
Indicates the type of base station to be traced. There are four

options: BTS, NodeB, SRAN, and Other.
l BTS: indicates the GSM base station.
l NodeB: indicates the UMTS base station.
l SRAN: indicates the SRAN base station.
NOTE
To trace SRAN base station, select NodeB and SRAN.
l Other: indicates other base stations.

ESN
Indicates the electronic serial number. At least one ESN is carried

in DHCP packets. If two ESNs are carried, one is a main ESN and
the other is an optional ESN. If an optional ESN is typed in this
field, DHCP packets carrying this ESN will be traced. However,
the main ESN is always displayed on the dll parsing interface. If
this field is left blank, all DHCP packets will be traced.
Trace Reason

l Pressing the Enter key is not supported. Letters, digits, spaces
and the following special characters are supported: ! @ # $ %
^&*()_+-=`~:",.|\<>?/{}[]
Trace Mode
Save File
----End
7.4 UMTS Services

This section describes how to perform tracing tasks related to UMTS services.
7.4.1 Tracing Messages on the Iu Interface

This section describes how to trace the signaling messages over the Iu interface, including the
connection-oriented messages and the connectionless messages. You can perform this task to
identify the failure cause in the following procedures: RAB assignment, RAB release, paging,
Iu release, security mode control, initial UE message, and relocation.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iu Interface Trace. The
Iu Interface Trace dialog box is displayed, as shown in Figure 7-5.
Issue 02 (2015-05-08)

109
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-5 Message tracing on the Iu interface
Step 3 In the Iu Interface Trace dialog box, set parameters and click Submit.
Parameter
Basic
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query

it, run the LST URNCBASIC command.
DPC
Configuration
can be set to All DPC or Specified DPC. If Specified

DPC is selected, DPC(HEX) needs to be specified.
Trace Type
Trace Type.
Trace Reason

l Pressing the Enter key is not supported. Letters,
digits, spaces and the following special characters are
supported: ! @ # $ % ^ & * ( ) _ + - = ` ~ : " , . | \
<>?/{}[]
Issue 02 (2015-05-08)
Trace Mode
Save File

110
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
MTP3
Description
MTP3 Trace Type
Set this parameter to Specified Link or Link Set. If this

parameter is set to Link Set, a large number of messages
are traced.
Signaling Link Set

Index
Index of an MTP3 signaling link set, which can be

queried by running the LST MTP3LKS command.
Signaling Link
Code
Index of an MTP3 link in the specified link set, which

can be queried by running the LST MTP3LNK
command.
SAAL
SAAL Link ID
indicates the number of an SAAL link. To query it, run

the LST SAALLNK command.
SCTP
SCTP Link ID
indicates the number of an SCTP link. To query it, run

the LST SCTPLNK command.
M3UA
M3UA Trace
Type

parameter is set to Link Set, a large number of messages
are traced.
Signaling Link Set

Index
indicates the number of an M3UA link set. To query it,

run the LST M3LKS command.
Signaling Link ID
indicates the number of an M3UA link. To query it, run

the LST M3LNK command.
----End
7.4.2 Tracing Messages on the Iupc Interface

This section describes how to trace the signaling messages over the Iupc (Iu Position Calculation)
interface, including the connection-oriented messages. You can perform this task to identify the
cause of the failure in the following scenarios: PCAP Position Initiations, PCAP Position
Activation.
Procedure
Step 2 On the Trace Navigation Tree pane, choose Trace > UMTS Services > Iupc Interface
Trace. The Iupc Interface Trace dialog box is displayed, as shown in Figure 7-6.
Issue 02 (2015-05-08)

111
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-6 Message tracing on the Iupc interface
Step 3 In the Iupc Interface Trace dialog box, set parameters and click Submit.
Table 7-8 Iupc Interface Trace Tab
Parameter
Basic
Description
RNC ID
indicates the RNC ID of the cell to be traced. To

query it, run the LST URNCBASIC command.
DPC
Configuration
can be set to All DPC or Specified DPC. If

Specified DPC is selected, DPC(HEX) needs to be
specified.
Trace Type
Trace Type
Trace Reason

l Pressing the Enter key is not supported. Letters,
digits, spaces and the following special
characters are supported: ! @ # $ % ^ & * ( ) _
+-=`~:",.|\<>?/{}[]
Issue 02 (2015-05-08)
Trace Mode
Save File

112
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
SCTP
SCTP Link ID
indicates the number of an SCTP link. To query it,

run the LST SCTPLNK command.
M3UA
M3UA Trace
Type
Set this parameter to Specified Link or Link Set. If

this parameter is set to Link Set, a large number of
messages are traced.
Signaling Link
Set Index
indicates the number of an M3UA link set. To query

it, run the LST M3LKS command.
Signaling Link ID
indicates the number of an M3UA link. To query it,

run the LST M3LNK command.
----End
Result
NOTE
In the message browse window of Iupc Interface Tracing, the number in the Information Source column
represents the DPC of the neighboring RNC. You can query more information about the DPC by running
the command LST N7DPC.
7.4.3 Tracing Messages on the Iur Interface

This section describes how to trace the signaling messages over the Iur interface, including the
connection-oriented messages and the connectionless messages. You can perform this task to
identify the failure cause in the following procedures on the Iur interface: radio link setup, radio
link addition, radio link deletion, resource release on common transport channel, DL power
control, and paging.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iur Interface Trace. The
Iur Interface Trace dialog box is displayed, as shown in Figure 7-7.
Issue 02 (2015-05-08)

113
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-7 Message tracing on the Iur interface
Step 3 In the Iur Interface Trace dialog box, set parameters and Click Sumit.
Parameter
Basic
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it,

run the LST URNCBASIC command.
DPC
Configuratio
n
can be set to All DPC or Specified DPC. If Specified

DPC is selected, DPC(HEX) needs to be specified.
Trace Type
Trace Type.
Trace Reason

l Pressing the Enter key is not supported. Letters, digits,
spaces and the following special characters are
supported: ! @ # $ % ^ & * ( ) _ + - = ` ~ : " , . | \ < >
?/{}[]
Trace Mode
Issue 02 (2015-05-08)

114
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
IUR
Description
Save File
IUR_G
In the IUR tab page, if you select IUR_G, the Iur-g interface
messages between BSC6900s or in a BSC6900 are traced.
If you select InMbsc, the Iur-g interface messages between
the GSM and UMTS in a BSC6900 are traced.
InMbsc
MTP3
MTP3 Trace
Type

parameter is set to Link Set, a large number of messages are
traced.
Signaling
Link Set
Index
Index of an MTP3 signaling link set, which can be queried

by running the LST MTP3LKS command.
Signaling
Link Code
Index of an MTP3 link in the specified link set, which can

be queried by running the LST MTP3LNK command.
SAAL
SAAL Link
ID
indicates the number of an SAAL link. To query it, run the

LST SAALLNK command.
SCTP
SCTP Link
ID
indicates the number of an SCTP link. To query it, run the

LST SCTPLNK command.
M3UA
M3UA Trace
Type

parameter is set to Link Set, a large number of messages are
traced.
Signaling
Link Set
Index
indicates the number of an M3UA link set. To query it, run

the LST M3LKS command.
Signaling
Link ID
indicates the number of an M3UA link. To query it, run the

LST M3LNK command.
----End
7.4.4 Tracing Messages on the Iub Interface

This section describes how to trace the signaling messages over the Iub interface, that is, the
NodeB Application Part (NBAP) messages. You can perform this task to identify the failure
cause in the following procedures on the Iub interface: radio link setup, radio link
reconfiguration, resource audit, cell setup, cell reconfiguration, common transport channel setup,
and system information update.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iub Interface Trace. The
Iub Interface Trace dialog box is displayed, as shown in Figure 7-8.
Issue 02 (2015-05-08)

115
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-8 Message tracing on the Iub interface
Step 3 In the Iub Interface Trace dialog box, set parameters and Click Submit.
Parameter
Description
Basic
RNC ID
indicates the RNC ID of the cell to be traced. To query it, run

the LST URNCBASIC command.
NodeB Trace
Type
l All NodeB: traces NodeB Application Part (NBAP)

messages of all NodeBs.
l All Ports of a NodeB: traces NBAP messages of a
specified NodeB on all ports. Both NodeB Control Ports
(NCPs) and Communication Control Ports (CCPs) are to
be traced.
l Specified Port of a NodeB: traces NBAP messages of a
specified NodeB on a specified type of port. Either NCPs
or CCPs are to be traced.
Trace Type
Issue 02 (2015-05-08)
Trace Type

116
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Reason

supported: ! @ # $ % ^ & * ( ) _ + - = ` ~ : " , . | \ < > ?
/{}[]
Trace Mode
Save File
SAAL
SAAL Link ID
indicates the number of an SAAL link. To query it, run the

LST SAALLNK command.
SCTP
SCTP Link ID
indicates the number of an SCTP link. To query it, run the

LST SCTPLNK command.
SCTPS
RV
SCTPSRV ID
SCTP Signaling Server ID
Peer IP Address
Peer IP address
Peer Port
Peer Port No.
----End
7.4.5 Tracing Messages on the Uu Interface

This section describes how to trace all or specified types of signaling messages in a specified
cell over the Uu interface. You can perform this task to identify the failure cause in the following
procedures: RRC connection setup, radio bearer setup, physical channel reconfiguration, and
cell update.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Uu Interface Trace. The
Uu Interface Trace dialog box is displayed, as shown in Figure 7-9.
Issue 02 (2015-05-08)

117
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-9 Message tracing on the Uu interface
Step 3 In the Uu Interface Trace dialog box, set the parameters as required. Then Click Submit.
Parameter
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.
Cell Config
needs to be set to the ID of the cell sending and receiving messages.

The parameter can be queried by running the LST UCELL command.
Trace Reason

the following special characters are supported: ! @ # $ % ^ & *
()_+-=`~:",.|\<>?/{}[]
Issue 02 (2015-05-08)
Trace Mode
Save File

118
BSC6900 UMTS
LMT User Guide
7 Trace Management
----End
7.4.6 Tracing MNCDT Messages

This section describes how to detect missing neighboring cell relationship of a cell. Using the
Missing Neighbor Cell Detect Trace (MNCDT) function, you can detect missing neighboring
cell relationship. MNCDT consists of intra-frequency, inter-frequency, and inter-RAT MNCDT,
which are independent of each other.
Prerequisites
The parameter switch for detecting missing neighboring cell relationship is set to ON. The setting
can be queried by running the LST UNCELLDETECTSWITCH command.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > MNCDT Trace. The
MNCDT Trace dialog box is displayed, as shown in Figure 7-10.
Figure 7-10 MNCDT message tracing
Step 3 Set parameters in the MNCDT Trace dialog box and then click Submit.
Issue 02 (2015-05-08)

119
BSC6900 UMTS
LMT User Guide
7 Trace Management

Parameter
Basic
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it,

run the LST URNCBASIC command.
Detection
Type
includes Intra-frequency, Inter-frequency, and Inter-RAT.
Trace Reason

supported: ! @ # $ % ^ & * ( ) _ + - = ` ~ : " , . | \ < >
?/{}[]
Interfrequency
Inter-RAT
Issue 02 (2015-05-08)
Trace Mode
Save File
Uplink
UARFCN
indicates the uplink UTRA Absolute Radio Frequency

Channel Number (UARFCN) of the cell to be traced for
detecting missing neighboring relationship.
Downlink
UARFCN
indicates the downlink UARFCN of the cell to be traced for

detecting missing neighboring relationship.
Start of
Primary
Scrambling
Code
indicates the minimum scrambling code for an MNCDT

task.
End of
Primary
Scrambling
Code
indicates the maximum scrambling code for an MNCDT

task. End of Primary Scrambling Code must be not less
than Start of Primary Scrambling Code.
Start of NCC
indicates the start of the Network Color Code (NCC) for the
cell to be traced for detecting missing neighboring cell
relationship. The parameter value ranges from 0 to 7.
End of NCC
indicates the end of the NCC for the cell to be traced for
detecting missing neighboring cell relationship. The
parameter value ranges from 0 to 7. End of NCC must be
greater than or equal to Start of NCC.
Start of BCC
indicates the start of the Base Transceiver Station Color

Code (BCC) for the cell to be traced for detecting missing
neighboring cell relationship. The parameter value ranges
from 0 to 7.
End of BCC
indicates the end of the BCC for the cell to be traced for
detecting missing neighboring cell relationship. The
parameter value ranges from 0 to 7. End of BCC must be
greater than or equal to Start of BCC.

120
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Band
Indicator
Indicates the band to which the overlapping UARFCNs

between bands DCS1800 and PCS1900 are attributed. It can
be set either DCS1800 or PCS1900 if the neighbor cell is not
DCS1800 or PCS1900 cell.
Start of
BCCH
ARFCN
indicates the minimum Absolute Radio Frequency Channel

Number (ARFCN) for an MNCDT task.
End of BCCH
ARFCN
indicates the maximum ARFCN for an MNCDT task.
----End
7.4.7 Message Settings

Clicking this node in the navigation tree enables users to select messages that need to be traced
during UE tracing, cell tracing, and IOS tracing. Tracing these messages in real time on the LMT
facilitates debugging and problem analysis.
Issue 02 (2015-05-08)
Message Name
Description
UI_FAM_UT_CELL
_INFO
Selecting it enables the LMT to display values of received total

wideband power (RTWP) and transmitted carrier power (TCP) in a
cell. Analysis of these values helps users to determine whether an
admission request is denied because of heavy load and insufficient
resources on the Uu interface.
UI_FAM_UT_CTRL
_TBL
Selecting it enables the LMT to display mapping between UE IDs of

the UE and internal units of the RNC.
UI_FAM_UT_GTPU
_DATA_FWD_MSG
Selecting it enables the LMT to display statistics on packets received

and sent at the GPRS Tunneling Protocol for User Plane (GTPU)
layer.
UI_FAM_UT_INTR
A_MSG
Selecting it enables the LMT to display communication messages

between internal units of the RNC.
UI_FAM_UT_L2_T
XT_FWD_MSG
Selecting it enables the LMT to display real-time information such

as the RLC state, FP synchronization information, and information
about HS-DSCH capacity allocation.
UI_FAM_UT_PRIN
T_INFO
Selecting it enables the LMT to display real-time log information,

including text messages. The text messages can be of the TXT or
TXT (Command Code) type.
UI_FAM_UT_REAL
_TIME_INFO
Selecting it enables the LMT to display real-time information such

as information about cell admission and cell load control.

121
BSC6900 UMTS
LMT User Guide
7 Trace Management
Message Name
Description
UI_FAM_UT_RPRT
_CELL_EVENT_IN
FO
Selecting it enables the LMT to display the number of UEs in a cell

and the propagation delay from the NodeB to the UEs.
UI_FAM_UT_STAN
DARD_MSG
Selecting it enables the LMT to display UE messages traced on

standard interfaces.
UI_FAM_UT_STAT
E_TRANS
Selecting it enables the LMT to trace state transitions of the UE.
7.4.8 Tracing UE Messages

This section describes how to trace UE messages. You can perform this task to analyze the call
procedure failure cause.
Context
l
As private information of users is revealed during the tracing, only G1 command group
users (ADMINISTRATOR and CUSTOM users with G1 command group permission) are
allowed to perform UE tracing task.
There is no way to avoid that some user data such as International Mobile Subscriber
Identity (IMSI) will be used during problem location and resolution. This function provides
an anonymous data processing method. You are recommended to comply with local laws
when executing the task and take ample measures to fully protect user data, such as enabling
the anonymous function and deleting the folder that saves trace records after you finish
processing data.
When entering IMSI, check whether IMSI data to be entered must be anonymous by running
the LST USERIDANONSWITCH command and querying User Identity Anonymity
Switch.
If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and
anonymous IMSI data must be entered in IMSI. The anonymous IMSI data is the IMSI
data encrypted by the HMACUtil using the cipher key.
If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user
IMSI data is directly entered in IMSI.
NOTE
l Change the anonymous policy and cipher key on the U2000 by choosing Trace and Maintenance >
Signaling Trace > Anonymous Policy Management > Anonymous Cypher Key Management
(application style) or Trace and Maintenance > Monitor > Signaling Trace > Anonymous Policy
Management > Anonymous Cypher Key Management (traditional style). For details, see U2000
Fault Management User Guide.
l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the
tracing task. Otherwise, the tracing task becomes invalid.
l For details about how to obtain the HMACUtil, contact Huawei technical support.
Issue 02 (2015-05-08)

122
BSC6900 UMTS
LMT User Guide
7 Trace Management
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. The UE Trace
Figure 7-11 UE message tracing
Step 3 In the displayed UE Trace dialog box, set the parameters as required. Then Click Submit.
Table 7-13 UE Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.

123
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
IMSI/
MSISDN/
IMEI/TMSI/
P-TMSI
Identifying the UE to be traced. Choosing to trace the UE by the TMSI, you

need to specify LAC, MCC, and MNC. Choosing to trace the UE by the PTMSI, you need to specify LAC, RAC, MCC, and MNC.
l If you trace a UE by specifying the IMSI and the IMSI is carried in the
RRC CONNECTION REQUEST message sent by the UE for network
access, the UE tracing task traces all the messages that are sent after the
RRC CONNECTION REQUEST message.
l Assume that you trace a UE by specifying the IMSI and the IMSI is not
carried in the RRC CONNECTION REQUEST message but only carried
in the RANAP COMMON ID message. If CDT_MSG_FULL_TRACE
is set to ON, the UE tracing task traces the messages that are sent after
the RANAP COMMON ID message, and the messages sent before the
RANAP COMMON ID message are buffered and reported. If
CDT_MSG_FULL_TRACE is set to OFF, the messages sent before the
RANAP COMMON ID message are discarded instead.
TRACE RRC
PROCEDUR
E
Issue 02 (2015-05-08)
Indicating whether to trace messages on the standard interface during an

RRC connection setup process when the international mobile subscriber
identity (IMSI) is specified. When this switch is turned on, users with
specified IMSIs cannot trace messages on the standard interface until a
second RRC connection setup process.

124
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Config
Template
Commonly used tracing items are combined to form various templates, so

that users can start a tracing task conveniently. Following describe the
meanings of various parameters in different templates:
l User-defined Mode: Users can set parameters on each tab page in the
UE Trace dialog box.
l Standard UE CDT Trace Method: When this template is selected, all
standard signaling messages on the IUR, IUB, IU, IUPC, and UU tab
pages are traced. Debug Mode is unavailable.
l UE CDT Trace Method (Debug + Internal Event): When this template
is selected, the following messages are traced: all standard signaling
messages on the IUR, IUB, IU, IUPC, and UU tab pages and Internal
Event on the Other1 tab page.
l UE CDT Trace Method (Debug + Internal Event + L2 Statistics):
When this template is selected, the following messages are traced: all
standard signaling messages on the IUR, IUB, IU, IUPC, and UU tab
pages, Internal Event on the Other1 tab page, and Layer 2 data
transfer periodic report on the Other tab page.
l UE CDT Trace Method (Debug + Internal Event + L2 Statistics +
SRB): When this template is selected, the following messages are traced:
all standard signaling messages on the IUR, IUB, IU, IUPC, and UU tab
pages, Internal Event on the Other1 tab page, Layer 2 data transfer
periodic report on the Other tab page, and L2 SRB Data Report.
SRB + TRB): When this template is selected, the following messages
are traced: all standard signaling messages on the IUR, IUB, IU,
IUPC, and UU tab pages, Internal Event on the Other1 tab page, Layer
2 data transfer periodic report on the Other tab page, L2 SRB Data
Report, L2 TRB packet header report (Iub interface), and L2 TRB
packet header report (Iu interface).
SRB + TRB + MOS): When this template is selected, the following
messages are traced: all standard signaling messages on the IUR, IUB,
IU, IUPC, and UU tab pages, Internal Event on the Other1 tab page,
Layer 2 data transfer periodic report on the Other tab page, L2 SRB
Data Report, L2 TRB packet header report (Iub interface), L2 TRB
packet header report (Iu interface), and Voice Analysis.
Debug Mode
indicates a maintenance mode used for tracing communication messages

between units of the RNC. Tracing tasks configured on Other, Other1, and
Bind tab pages take effect only when Debug Mode is selected.
For use of it, contact Huawei technical support personnel.
Trace Reason

following special characters are supported: ! @ # $ % ^ & * ( ) _ + - =
`~:",.|\<>?/{}[]
Issue 02 (2015-05-08)

125
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Mode
Save File
Table 7-14 Monitor Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
Uplink SIR
Selecting the counter starts monitoring of uplink Signal to Interference Ratio

(SIR) during tracing of a single UE. The counter is reported periodically.
The period of reporting the monitoring reports ranges from 0.1s to 60s.
UE Tx Power
Selecting the counter starts monitoring of uplink transmit power during

tracing of a single UE. The counter is reported periodically. The period of
reporting the monitoring reports ranges from 0.25s to 64s.
Downlink
BLER
Selecting the counter starts monitoring of Block Error Rate (BLER) during
tracing of a single UE. The counter is reported periodically. The period of
reporting the monitoring reports ranges from 0.25s to 64s.
Downlink Tx
Code Power
Selecting the counter starts monitoring of downlink code transmit power

during tracing of a single UE. The counter is reported periodically. The
period of reporting the monitoring reports ranges from 0.1s to 60s.
PCPICH Ec/
No RSCP
Selecting the counter starts monitoring of PCPICH Ec/No and Received

Signal Code Power (RSCP) during tracing of a single UE. The counter is
reported periodically. The period of reporting the monitoring reports ranges
from 0.25s to 64s.
AMR Mode
Selecting the counter starts monitoring of AMR mode during tracing of a

single UE. The counter is reported periodically. If AMR mode changes, the
current mode is reported.
RTWP(0.4s)
Selecting the counter starts monitoring of received total wideband power

(RTWP) received for the cell serving the current UE. The counter is reported
every 0.4 second.
TRX Transmit
Power(0.4s)
Selecting the counter starts monitoring of downlink transmit power

transmitted for the cell serving the current UE. The counter is reported every
0.4 second.

126
BSC6900 UMTS
LMT User Guide
7 Trace Management
Table 7-15 Other Tab Parameter Description

Parameter
Description
Layer 2 Data
Transfer
Periodic
Report
Selecting it enables statistics on packets received and sent at layer 2 to be

periodically reported to the LMT.
Transport
Data Periodic
Report
Selecting it enables statistics on packets received and sent by interface

boards to be periodically reported to the LMT. Analysis of these statistics
helps users to determine whether a fault occurs on the RNC side.
Report Period
Indicates the period for reporting Layer 2 data transfer periodic report.
L2 Data
Report
Includes parameters that enable statistics on packets received and sent at

layer 2 to be reported to the LMT.
l L2 SRB Data Report: enables packets received in the UL and sent in
the DL on the control plane at the Frame Protocol (FP) layer to be reported
to the LMT in messages.
l Report Time(s): indicates the period for reporting L2 Data Report.
l L2 TRB Packet Header Report (Iub Interface): Selecting it enables
frame headers received in the UL or sent in the DL on the user plane at
the FP layer to be reported to the LMT.
l L2 TRB Packet Header Report (Iu Interface): Selecting it enables
packet TCP/IP headers sent in the UL or received in the DL on the user
plane at the RLC layer to be reported to the LMT.
l TCP Proxy Data Report: After the TCP proxy function is enabled, the
TCP/IP headers of the following TCP packets are reported to the LMT:
In the downlink, user-plane TCP packets that are received from the
server and transmitted to the UE at the PDCP layer.
In the uplink, user-plane TCP packets that are received from the UE
and transmitted to the server at the PDCP layer.
When RNC in Pool is used for user-plane load-sharing, Report File is
recommended if the user selects L2 TRB packet header report (Iub
interface) or L2 TRB packet header report (Iu interface) on the Other
tab page. After the user selects Report File, the user needs to configure the
FTP server and ensure that the FTP server connects to the master RNC and
overflow RNC. The tracing results generated by the master RNC are saved
on the OMU of the master RNC and the tracing results generated by the
overflow RNC are saved on the OMU of the overflow RNC. You can use
the FTP server to upload the tracing results on the OMU to the directory
specified by Upload Path.
NOTE
You can run the MML command LST UPOOLLOADSHAREPARA to query the
value of UP Load Sharing Policy. If the value of this parameter is UP_SHARE, RNC
in Pool is used for user-plane load-sharing.
Issue 02 (2015-05-08)

127
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Auto Ping
Selecting it enables the RAN to send the UE Internet Control Message

Protocol (ICMP) packets. This function helps users to determine whether
data disconnection exists between a server and the RNC or a low rate on the
server side causes the low UE rate.
l Ping Interval (0.1 ms): indicates the interval at which ICMP packets are
sent.
l Packet Length (bytes): indicates the payload length of the ICMP
packets.
Voice
Analysis
When this check box is selected, the LMT records the test results of voice
frames over the Iu interface, for example, the frame type, mean opinion score
(MOS), and speech noise detection result. Based on the recorded test results,
the maintenance personnel can judge the voice quality. The MOS is saved
in the following path by default:/bam/common/fam/speechmos/.
l Sampling No.: This parameter indicates the voice quality sample to be
used. Currently, the valid value range of this parameter is 0 to 8. The
value of this parameter depends on the selected test tool. It is set to 0 only
when no voice quality sample is used. In this case, no test tool is required.
Issue 02 (2015-05-08)
QAAL2
protocol
message
Selecting it enables tracing of real-time QAAL2 standard protocol messages.

Information elements carried in the messages help determine whether
QAAL2 message interaction between NEs is successful.
RT_BASIC_I
NFO
Selecting it enables the following information to be traced: Real-time RRC

service state of the UE such as CELL_DCH and CELL_FACH, connection
mode over the Iu interface (idle or connected mode), the homing RNC
(SRNC or DRNC), and cells in the active set of the UE.
RT_COMM_
CONTEXT_I
NFO
Selecting it enables tracing of real-time information such as the serving

NodeB, communication context ID of the controlling radio network
controller (CRNC), URNTI, CRNTI, and UE ID.
RT_INST_RE
SOURCE_IN
FO
Selecting it enables tracing of real-time index of resources that are allocated

to the UE, for example, system memory.
RT_RAB_PA
RA_INFO
Selecting it enables tracing of real-time radio access bearer (RAB)

information such as traffic class, maximum rate, and guaranteed bit rate
(GBR).
SCCP
protocol
message
Selecting it enables tracing of real-time SCCP standard protocol messages.

SCCP is short for Signaling Connection Control Part. Information elements
carried in the messages help determine whether SCCP message interaction
between NEs is successful.

128
BSC6900 UMTS
LMT User Guide
7 Trace Management
Table 7-16 Other1 Tab Parameter Description

Parameter
Description
FP PM Report
Selecting it enables transmission statistics at the FP layer to be reported to

the LMT.
IUUP Uplink
Loop
Selecting it enables Iu user plane (IuUP) data that would be transmitted to

the CN to be transmitted in the downlink direction. This function is used for
isolating other network elements during problem analysis, which facilitates
location of speech quality problems.
NOTE
When this operation is performed, the traced user can only hear the voice of itself rather
than that of the peer end.
IUUP
Downlink
Loop
Selecting it enables IuUP data received from the CN to be returned to the

CN. This function is used for isolating other network elements during
problem analysis, which facilitates location of speech quality problems.
NOTE
When this operation is performed, the peer end can only hear the voice of itself rather
than that of the traced user.
Issue 02 (2015-05-08)
PDCP Trace
Selecting it enables information about Packet Data Convergence Protocol

(PDCP) header compression to be reported to the LMT.
FP Trace
Selecting it enables control frames on the IuUP or at the FP layer to be

reported to the LMT.
L2 FL
Protocol
Trace Report
Selecting it enables protocol parameters on the user plane to be reported to

the LMT.
TCP Proxy
Protocol
Trace Report
When the TCP proxy function is enabled, protocol parameters about userplane TCP packets can be reported to the LMT.

129
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Flow Trace
Selecting it enables specified data flow of the UE on the interface board to

be reported in packets to the LMT. If RNC data flow is blocked, the problem
may lie in the RNC, the interface board, or the peer end. You can use this
function to exclude some problems.
l Flow Trace Interface Type: indicates the interface to have its data flow
traced.
l Flow Trace Bearer Type: indicates the channel to have its data flow
traced.
l Flow Trace Service Type: indicates the service to have its data flow
traced.
l RearPanel trace: traces data flow sent or received on the backplane of
the interface board.
l FrontPanel trace: traces data flow sent or received on the panel of the
interface board.
NOTICE
Note that selecting Rear panel trace or Front panel trace may lead to flow control,
so exercise caution in this selection.
TCP Proxy
Function
Config
Selecting it configures the single-user TCP proxy function.

l TCP Proxy Function Config Type: It can be set to DL TCP Proxy
Enable or TCP Proxy Disable.
DL TCP Proxy Enable: Enables the single-user downlink TCP
proxy function.
TCP Proxy Disable: Disables the single-user TCP proxy function.
Bind: Binding the UE to a DSP or path or transmission resource pool. This helps users to
determine whether a DSP or path fault exists.
Table 7-17 Bind Tab Parameter Description
Parameter
Description
DSP
l Subrack No.: indicates the number of the subrack corresponding to the

DSP.
l Slot No.: indicates the number of the slot corresponding to the DSP.
l DSP No.: indicates the number of the DSP.
Iub
l Path ANI No.: indicates the Adjacent Node Identifier (ANI)

corresponding to the Iub path.
l Type: indicates the transport type of the Iub path.
l Path ID: indicates the number of the Iub path.
l CID/UDP PORT(I1,I2,I3...): indicates the bound channel identifier
(CID) on the Iub path in ATM transmission mode or the number of the
bound User Datagram Protocol (UDP) port in IP transmission mode.
Issue 02 (2015-05-08)

130
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Iucs
l Path ANI No.: indicates the ANI corresponding to the Iu-CS path.
l Type: indicates the transport type of the Iu-CS path.
l Path ID: indicates the number of the Iu-CS path.
l CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iu-CS path
in ATM transmission mode or the number of the bound UDP port in IP
transmission mode.
Iur
l Path ANI No.: indicates the ANI corresponding to the Iur path.
l Type: indicates the transport type of the Iur path.
l Path ID: indicates the number of the Iur path.
l CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iur path
in ATM transmission mode or the number of the bound UDP port in IP
transmission mode.
Iups
l Path ANI No.: indicates the ANI corresponding to the Iu-PS path.
l Type: indicates the transport type of the Iu-PS path.
l Path ID: indicates the number of the Iu-PS path.
NODE
l Node ID/External Node ID: indicates the ID of the bound physical node.
----End
7.4.9 Tracing Cell Messages

This section describes how to trace cell messages. The tracing results of the cell messages provide
reference for troubleshooting common channel faults when the access success rate is low or zero
in the cell. The UE statistics can be displayed in the tracing result if required.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Cell Trace. The Cell
Trace dialog box is displayed, as shown in Figure 7-12.
Issue 02 (2015-05-08)

131
BSC6900 UMTS
LMT User Guide
7 Trace Management
Figure 7-12 Cell message tracing
Step 3 Set parameters in the Cell Trace dialog box and then click Submit.
Table 7-18 Cell Trace Tab Parameter Description
Parameter
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it, run the
LST URNCBASIC command.
Cell ID
indicates the index of a cell.
User Volume/
Propagation Delay
indicates the event to be traced, either the USER_VOLUME event

or the PROPAGATION_DELAY event. If you select the User
volume event, some custom messages reflecting statistics about UEs
in a cell will be reported. The value ranges from 1000 to 10000 given
in 10 ms. If you select the Propagation delay event, propagation
delay in messages will be reported. The value ranges from 1 to 80.
Debug Mode
indicates a maintenance mode used for tracing communication

messages between units of the RNC. Tracing tasks configured on
Other and Bind tab pages take effect only when Debug Mode is
selected.
Issue 02 (2015-05-08)

132
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Reason

the following special characters are supported: ! @ # $ % ^ &
*()_+-=`~:",.|\<>?/{}[]
Trace Mode
Save File
Table 7-19 FMR Tab Parameter Description

Parameter
Description
Service Data Trace
includes different types of service data to be traced.
SCCPCH ID
indicates the IDs of the SCCPCHs to be traced. You can choose to

trace two SCCPCHs at the same time by specifying two SCCPCH
IDs.
Report period(100
ms)
in the unit of 100 ms and needs to be specified if Layer 2 Data

Periodic Report or Transport Data Periodic Report is selected in
the FMR tab page.
Bind: Binding the UE to a DSP. This helps users to determine whether a DSP fault exists.
Parameter
Description
Bind DSP
l Subrack No.: indicates the number of the subrack corresponding

to the DSP.
l Slot No.: indicates the number of the slot corresponding to the
DSP.
l DSP No.: indicates the number of the DSP.
Table 7-21 Table 4 Other Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
SIG Trace Event
includes internal transport events of the RNC to be traced.
CDR_SIG_QAAL2_
PDU_MSG
Selecting it enables tracing of real-time QAAL2 standard protocol

messages. Information elements carried in the messages help
determine whether QAAL2 message interaction between NEs is
successful.

133
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
CELL_SIG_AL_STR
EAMING_RDPT
Selecting it enables specified data flow of the cell on the interface

board to be reported to the LMT.
l Transport Channel Type: indicates the type of transport
channel to have its data flow traced.
l SCCPCH ID: indicates the ID of the Secondary Common
Control Physical Channel (S-CCPCH).
----End
7.4.10 Tracing IOS Messages

This section describes how to trace a number of calls that meet the sampling criteria within a
specified range of cells. When creating the task, you can specify the number of calls to be traced
and specify messages to be traced by selecting the event type.
Context
NOTICE
The IOS tracing task involves a large amount of trace information, which affects the system
operation. Therefore, the maximum number of simultaneously traced calls set in the Max calls
simultaneously traced area in the IOS dialog box should not be too high. In addition, you are
advised not to trace all events at a time. Furthermore, you should minimize the frequencies of
performing this task and the number of tasks performed simultaneously.
l
You need to specify the number of successive calls to be traced, tracing cell range, sampling
criteria, and tracing time. The calls that meet the sampling criteria are traced within the
specified tracing time.
When creating a new call tracing task, you can define the sampling criteria by setting
the RAB parameter constraints and the RRC Est Cause. Once the call meets the criteria,
the tracing of the call is not stopped even if the RAB parameters of the RRC
establishment cause are changed during the call. If the initial settings of the RAB
parameters or the RRC establishment cause value of a call does not meet the criteria,
the BSC6900 does not trace the call even if these parameters are modified to meet the
criteria during the call.
You can specify the message types to be traced by selecting the event types.
Assume that the specified number of continuous calls is N. If N calls are already being traced,
the system does not trace any newly accessed calls. If the number becomes less than N because
of the termination of a traced call, the system automatically traces a new call.
If multiple IOS tracing tasks with the same parameter settings are started, one task can trace and
display the tracing messages of only one user, because each user is traced by a specific tracing
task.
Issue 02 (2015-05-08)

134
BSC6900 UMTS
LMT User Guide
7 Trace Management
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > IOS Trace. The IOS
Figure 7-13 IOS message tracing
Step 3 In the displayed IOS Trace dialog box, set parameters and filter traced messages in other tab
pages. Then click Submit.
Table 7-22 Basic Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
RNC ID
RNC ID of the cell to be traced. To query it, run the LST

URNCBASIC command.
Call Count
maximum number of calls that can be traced simultaneously after a

tracing task is started. The value ranges from 1 to 30.
135
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Cell ID
You can type the ID of one cell or IDs of multiple cells.
VIP IMSI
Run the ADD UVIPIMSI command to add the VIP IMSI.
Trace only intersubsystem users
When this switch is turned on, only users with control plane load sharing
are traced.
IMEI TAC
(TAC1,TAC2,...
TAC8)
IMEI TAC of the user to be traced. You can enter a maximum of eight
IMEI TACs. An IMEI TAC can be a decimal number of 1 to 8 digits.
IMEI is short for international mobile equipment identity and TAC is
short for type allocation code.
NOTE
This parameter is valid only when the IMEI query function is enabled on the CN
or RNC side.
To enable the IMEI query function on the RNC side, run the following command
SET URRCTRLSWITCH:
SET URRCTRLSWITCH:
PROCESSSWITCH2=RNC_CS_QUERY_UE_IMEI_SWITCH-1&RNC_PS_QU
ERY_UE_IMEI_SWITCH-1,
PROCESSSWITCH4=SEND_MSG_NULL_SWITCH-1;
Event Type
Issue 02 (2015-05-08)
Types of event to be traced. The event types classify all messages related
to calls. You can select or clear all event types by clicking Select All or
Clear All. You can restore the setting to the original one by clicking
Reset.

136
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
Trace Config
Template
Commonly used tracing items are combined to form various templates,

so that users can start a tracing task conveniently. Following describe the
meanings of various parameters in different templates:
l User-defined Mode: Users can set parameters on each tab page in
the IOS Trace dialog box.
l Standard IOS Trace Method: When this template is selected, all
standard signaling messages generated by RRC Est Cause on the
RRC tab page are traced. Debug Mode is unavailable.
l IOS Trace Method (Debug + Internal Event): When this template
is selected, the following messages are traced: all standard signaling
messages generated by RRC Est Cause on the RRC tab page and
Internal Event on the Other1 tab page.
l IOS Trace Method (Debug + Internal Event + L2 Statistics):
When this template is selected, the following messages are traced: all
standard signaling messages generated by RRC Est Cause on the
RRC tab page, Internal Event on the Other1 tab page, and Layer 2
data transfer periodic report on the Other tab page.
l IOS Trace Method (Debug + Internal Event + L2 Statistics +
SRB): When this template is selected, the following messages are
traced: all standard signaling messages generated by RRC Est
Cause on the RRC tab page, Internal Event on the Other1 tab page,
Layer 2 data transfer periodic report on the Other tab page, and
L2 SRB Data Report.
l IOS Trace Method (Debug + Internal Event + L2 Statistics + SRB
+ TRB): When this template is selected, the following messages are
traced: all standard signaling messages generated by RRC Est
Cause on the RRC tab page, Internal Event on the Other1 tab page,
Layer 2 data transfer periodic report on the Other tab page, L2
SRB Data Report, L2 TRB packet header report (Iub interface),
and L2 TRB packet header report (Iu interface).
Debug Mode
maintenance mode used for tracing communication messages between

units of the RNC. Tracing tasks configured on Other, Other1, and
Bind tab pages take effect only when Debug Mode is selected.
Trace Reason

following special characters are supported: ! @ # $ % ^ & * ( ) _ +
-=`~:",.|\<>?/{}[]
Issue 02 (2015-05-08)
Trace Mode
Save File

137
BSC6900 UMTS
LMT User Guide
7 Trace Management
Table 7-23 MM Tab Parameter Description

Parameter
Description
CELL CHANGE
ORDER
CELL CHANGE ORDER: Traced messages of the cell change order

procedure.
INTER RAT
HANDOVER IN
Traced messages of the incoming inter-RAT handover procedure.
INTER RAT
HANDOVER
OUT
Traced messages of the outgoing inter-RAT handover procedure through

relocation.
LOCATION
UPDATE
Traced messages of the location area update procedure.
ROUT AREA
UPDATE
Traced messages of the routing area update procedure.
PCH CELL
UPDATE
Traced messages of the cell update procedure for UEs in the CELL_PCH
and URA_PCH states.
RAB tab page:

l If the BSC6900 receives an RAB ASSIGNMENT REQUEST message of a call that matches
the specified RAB parameters in the specified cell, the call is traced. If a call sets up multiple
RAB links, the call is traced if one of the RAB links meets the specified RAB parameters.
Table 7-24 RRC Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
RRC
includes the RRC establishment cause. If the BSC6900 receives an

RRC_CONN_REQ message of a call that matches the specified RRC
establishment cause in the specified cell, the call is traced.
RRC(ms)
Period of reporting measurement results of PCPICH Ec/No and Received

Signal Code Power (RSCP) when forward power control tracing is
selected or PCPICH Ec/No RSCP in the Monitor tab page is selected for
IOS tracing
UE Internal RRC
(ms)
Period of reporting measurement results of UE transmit power when

forward power control tracing is selected or UE Tx Power in the Monitor
tab page is selected for IOS tracing.
UE Quality RRC
(ms)
Period of reporting measurement results of downlink Block Error Rate

(BLER) when forward power control tracing is selected or Downlink
BLER in the Monitor tab page is selected for IOS tracing.
NBAP Common
(ms)
Period of reporting results of cell common measurement that is selected

in the Monitor tab page of IOS Trace.

138
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
NBAP Special
(ms)
Period of reporting measurement results of downlink code transmit

power in the SRNC cell when forward power control tracing is selected
or Downlink Tx Code Power in the Monitor tab page is selected for IOS
tracing.
RNSAP Special
(ms)
Period of reporting measurement results of downlink code transmit

power in the DRNC cell when forward power control tracing is selected
or Downlink Tx Code Power in the Monitor tab page is selected for IOS
tracing.
RRC Located
Type
UE locating method used during IOS tracing.
RRC Located
Cycle (ms)
Period for reporting UE locating results during IOS tracing.
RTT Special
NBAP(ms)
Period of reporting results of Round Trip Time (RTT) measurement in

the SRNC cell when forward power control tracing is selected or the
Monitor tab page is configured for IOS tracing.
RRC Est Cause
Call establishment causes and filters UEs to be traced in the cell based
on the call establishment causes.
Monitor tab page: includes performance counters to be monitored during tracing of a single UE
Table 7-25 Monitor Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
Uplink SIR
Selecting the counter starts monitoring of uplink Signal to Interference

Ratio (SIR) during tracing of a single UE. The counter is reported
periodically. The period of reporting the monitoring reports ranges from
0.1s to 60s.
Uplink Tx Power
Selecting the counter starts monitoring of uplink transmit power during

tracing of a single UE. The counter is reported periodically. The period
of reporting the monitoring reports ranges from 0.25s to 64s.
Downlink BLER
Selecting the counter starts monitoring of Block Error Rate (BLER)

Downlink Tx
Code Power
Selecting the counter starts monitoring of downlink code transmit power

PCPICH Ec/No
RSCP
Selecting the counter starts monitoring of PCPICH Ec/No and Received

Signal Code Power (RSCP) during tracing of a single UE. The counter
is reported periodically. The period of reporting the monitoring reports
ranges from 0.25s to 64s.

139
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
AMR Mode
Selecting the counter starts monitoring of AMR mode during tracing of

a single UE. The counter is reported periodically. If AMR mode changes,
the current mode is reported.
RTWP(0.4s)
Selecting the counter starts monitoring of received total wideband power

(RTWP) received for the cell serving the current UE. The counter is
reported every 0.4 second.
TRX Transmit
Power(0.4s)
Selecting the counter starts monitoring of downlink transmit power

transmitted for the cell serving the current UE. The counter is reported
every 0.4 second.
Table 7-26 Other Tab Parameter Description
Issue 02 (2015-05-08)
Parameter
Description
Layer 2 Data
Transfer Periodic
Report
To enable statistics on packets received and sent at layer 2 to be

periodically reported to the LMT, specify the parameter value.

140
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
L2 Data Report
includes parameters that enable statistics on packets received and sent at

layer 2 to be reported to the LMT.
l L2 SRB Data Report: enables packets received in the UL and sent
in the DL on the control plane at the Frame Protocol (FP) layer to be
reported to the LMT in messages.
l Report Time(s): period for reporting L2 Data Report.
l L2 TRB Packet Header Report (Iub Interface): Selecting it enables
frame headers received in the UL or sent in the DL on the user plane
at the FP layer to be reported to the LMT.
l L2 TRB Packet Header Report (Iu Interface): Selecting it enables
packet TCP/IP headers sent in the UL or received in the DL on the
user plane at the RLC layer to be reported to the LMT.
l TCP Proxy Data Report: After the TCP proxy function is enabled,
the TCP/IP headers of the following TCP packets are reported to the
LMT:
In the downlink, user-plane TCP packets that are received from
the server and transmitted to the UE at the PDCP layer.
In the uplink, user-plane TCP packets that are received from the
UE and transmitted to the server at the PDCP layer.
When RNC in Pool is used for user-plane load-sharing, Report File is
recommended if the user selects L2 TRB packet header report (Iub
interface) or L2 TRB packet header report (Iu interface) on the
Other tab page. After the user selects Report File, the user needs to
configure the FTP server and ensure that the FTP server connects to the
master RNC and overflow RNC. The tracing results generated by the
master RNC are saved on the OMU of the master RNC and the tracing
results generated by the overflow RNC are saved on the OMU of the
overflow RNC. You can use the FTP server to upload the tracing results
on the OMU to the directory specified by Upload Path.
NOTE
You can run the MML command LST UPOOLLOADSHAREPARA to query
the value of UP Load Sharing Policy. If the value of this parameter is
UP_SHARE, RNC in Pool is used for user-plane load-sharing.
Issue 02 (2015-05-08)
QAAL2_protoco
l_message
Selecting it enables tracing of real-time QAAL2 standard protocol

messages. Information elements carried in the messages help determine
whether QAAL2 message interaction between NEs is successful.
RT_BASIC_INF
O
Selecting it enables the following information to be traced: Real-time

RRC service state of the UE such as CELL_DCH and CELL_FACH,
connection mode over the Iu interface (idle or connected mode), the
homing RNC (SRNC or DRNC), and cells in the active set of the UE.
RT_COMM_CO
NTEXT_INFO
Selecting it enables tracing of real-time information such as the serving

NodeB, communication context ID of the controlling radio network
controller (CRNC), URNTI, CRNTI, and UE ID.

141
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
Description
RT_INST_RESO
URCE_INFO
Selecting it enables tracing of real-time index of resources that are

allocated to the UE, for example, system memory.
RT_RAB_PARA
_INFO
Selecting it enables tracing of real-time radio access bearer (RAB)

information such as traffic class, maximum rate, and guaranteed bit rate
(GBR).
SCCP protocol
message
Selecting it enables tracing of real-time SCCP standard protocol

messages. SCCP is short for Signaling Connection Control Part.
Information elements carried in the messages help determine whether
SCCP message interaction between NEs is successful.
Table 7-27 Other1 Tab Parameter Description

Parameter
Description
Internal Event
Selecting it enables tracing of internal events, communication messages

between RNC units.
FP PM Report
Selecting it enables transmission statistics at the FP layer to be reported

to the LMT.
IUUP Uplink
Loop
Selecting it enables Iu user plane (IuUP) data that would be transmitted

to the CN to be transmitted in the downlink direction. This function is
used for isolating other network elements during problem analysis, which
facilitates location of speech quality problems.
NOTE
When this operation is performed, the traced user can only hear the voice of itself
rather than that of the peer end.
IUUP Downlink
Loop
Selecting it enables IuUP data received from the CN to be returned to the

CN. This function is used for isolating other network elements during
problem analysis, which facilitates location of speech quality problems.
NOTE
When this operation is performed, the peer end can only hear the voice of itself
rather than that of the traced user.
FP Trace
Issue 02 (2015-05-08)
Selecting it enables control frames on the IuUP or at the FP layer to be

reported to the LMT.

142
BSC6900 UMTS
LMT User Guide
7 Trace Management

Parameter
Description
Iub Path
l Path ANI No.: Adjacent Node Identifier (ANI) corresponding to the

Iub path.
l Path Type: Transport type of the Iub path.
l Path ID: ID of an Iub path.
l CID/UDP PORT(I1,I2,I3...): Bound channel identifier (CID) on the
Iub path in ATM transmission mode or the number of the bound User
Datagram Protocol (UDP) port in IP transmission mode.
Iucs Path
l Path ANI No.: ANI corresponding to the Iu-CS path.

l Path Type: Transport type of the Iu-CS path.
l Path ID: ID of an Iu-CS path.
l CID/UDP PORT(I1,I2,I3...): Bound CID on the Iu-CS path in ATM
transmission mode or the number of the bound UDP port in IP
transmission mode.
Iur Path
l Path ANI No.: ANI corresponding to the Iur path.

l Path Type: Transport type of the Iur path.
l Path ID: ID of an Iur path.
l CID/UDP PORT(I1,I2,I3...): Bound CID on the Iur path in ATM
transmission mode or the number of the bound UDP port in IP
transmission mode.
Iups GTPU
l Path ANI No.: ANI corresponding to the Iu-PS GTPU.

l IP Pool IP Address: IP pool IP address corresponding to the Iu-PS
GTPU.
l Path ID: Path ID of the Iu-PS GTPU.
l Path Type: Path type of the Iu-PS GTPU.
----End
7.4.11 Tracing Iur-p Messages

This task traces messages over the Iur-p interface in a resource pool. The task can be started to
locate faults when the load sharing fails, the load is unbalanced, or RNCs cannot communicate
with each other in a resource pool.
Context
Physical RNCs of logical RNC communicate with each other through the Iurp interface.
Procedure
Step 1 ClickTraceon the LMT main page. The Trace tab page is displayed.
Issue 02 (2015-05-08)

143
BSC6900 UMTS
LMT User Guide
7 Trace Management
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iur-p Trace. The Iur-p
Figure 7-14 Iur-p message trace
Step 3 In the displayed Iur-p Trace dialog box, set the parameters as required. Click Submit.
Table 7-29 Tab Parameter Description
Parameter
Basic
IURP
Issue 02 (2015-05-08)
Description
External
Node
Configura
tion
You can select All External Node or Specified External Node.

When you select Specified External Node, you need to type
Specified External Node.
Trace
Type
You can select IURP or IURPLNK.
Trace
Reason
Trace
Mode
Save File
Frame
Type
You can select All, Control Frame, Data Frame or OM Frame.

and the following special characters are supported: ! @ # $ %
^&*()_+-=`~:",.|\<>?/{}[]

144
BSC6900 UMTS
LMT User Guide
7 Trace Management
Parameter
IURPLI
NK
Description
Direction
You can select All, In or Out.
Link Set
Index
Uniquely identifies a signaling link set.
Link
Index
Uniquely identifies a signaling link.
----End
7.4.12 Tracing Messages on the Sr Interface

This task is used to trace messages on the Sr interface, which are used to analyze the signaling
interaction between the eCoordinator module and RNC. The messages include the following:
messages from the eCoordinator for subscribing/unsubscribing the load of cells under the RNC,
messages in which the RNC reports the load of the subscribed cells, and radio information
messages (RIMs) carried on the eCoordinator for the RNC.
Procedure
Step 1 Click Trace on the LMT home page. The Trace tab page is displayed.
Step 2 In the Trace Navigation Tree, choose Trace > UMTS Services > Sr Interface Trace. The Sr
Interface Trace dialog box is displayed, as shown in Figure 7-15.
Figure 7-15 Settings in the Sr Interface Tracing dialog box
Step 3 On the Sr Interface Trace dialog box, set parameters and click Submit.
Issue 02 (2015-05-08)

145
BSC6900 UMTS
LMT User Guide
7 Trace Management

Parameter
Basic
SCTP
Description
RNC ID
indicates the RNC ID of the cell to be traced. To query it, run the
LST URNCBASIC command.
Trace Type
You can select SR or SCTP.
Trace
Reason
Trace Mode
Save File
SCTP Link
ID
indicates the number of an SCTP link. To query it, run the LST
SCTPLNK command.

and the following special characters are supported: ! @ # $
%^&*()_+-=`~:",.|\<>?/{}[]
----End
Issue 02 (2015-05-08)

146
BSC6900 UMTS
LMT User Guide
Performance Monitoring
About This Chapter

This chapter describes how to monitorBSC6900 performance. A maximum of 64 monitoring
tasks can be started simultaneously on the LMT. If OMU boards are switched over, performance
monitoring can be restarted 30 minutes after the switchover.
8.1 Concepts
This section describes the concepts related toBSC6900 performance monitoring, monitoring
principles, and monitoring rights management.
8.2 General Operations
This section describes the general operations applicable to all performance monitoring tasks
performed on the BSC6900.
8.3 Common Monitoring
This section describes common performance monitoring.
8.4 UMTS Monitoring
This section describes performance monitoring of UMTS services.
Issue 02 (2015-05-08)

147
BSC6900 UMTS
LMT User Guide
8.1 Concepts
This section describes the concepts related toBSC6900 performance monitoring, monitoring
principles, and monitoring rights management.
8.1.1 Monitoring Principles

This section describes the principles of real-time performance monitoring, including the
principles of CPU usage monitoring and real-time performance monitoring.
Principles of CPU Usage Monitoring

Figure 8-1 displays the principles of CPU usage monitoring.
Figure 8-1 CPU usage monitoring
The process for monitoring CPU usage is as follows:

1.
When you use the LMT to create a task for monitoring CPU usage, the LMT periodically
sends a binary command to the OMU maintenance module to query CPU usage.
2.
The OMU sends the corresponding command to the configuration and maintenance module
of a specified board.
3.
The board collects data according to the commands and reports it to the OMU.
4.
The OMU forwards the data to the LMT.
5.
The BSC supports CPU usage monitoring by subrack No. or by slot No.
Principles of Real-time Performance Monitoring

Figure 8-2 shows the principles of other real-time performance monitoring, which are similar
to the principles of message tracing.
Issue 02 (2015-05-08)

148
BSC6900 UMTS
LMT User Guide
Figure 8-2 Real-time performance monitoring
The process when the LMT creates a real-time monitoring task, other than CPU usage
monitoring, is as follows:
1.
The LMT sends a binary command to the OMU to create the task.
2.
The OMU assigns a task ID to the task and sends the command to the debugging module
of a specified board.
3.
Upon receiving the command, the debugging module records the filter parameters in the
filter table and notifies the service module of the information.
4.
The service module updates the local filter table in accordance with the messages from the
debugging module.
The process when the LMT stops a real-time monitoring task is as follows:
1.
When you stop a monitoring task on the LMT, the LMT sends a binary command to the
OMU to delete the task.
2.
The OMU sends the command to the specified board based on the task ID.
3.
The debugging module and service module delete the task from the filter table.
The process when the LMT reports real-time monitoring data is as follows:
1.
The service module compares the collected data with data in the local filter table. If the
data is the same, the service module reports the collected data to the OMU.
2.
Upon receiving the data, The OMU forwards it to the LMT that creates the task based on
the task ID.
3.
The LMT displays the data in a chart or a list.
8.1.2 Operation Rights Control

Only authorized users can perform real-time monitoring on the BSC6900.
Only the admin, commonoperator-level, operator-level, administrator-level, and G_10authorized custom-level users can perform this operation on BSC. Guest-level users and G_10unauthorized custom-level users can only perform CPU usage monitoring.
NOTE
Group G_10 consists of binary commands used for tracing and monitoring.
Issue 02 (2015-05-08)

149
BSC6900 UMTS
LMT User Guide
8.2 General Operations

This section describes the general operations applicable to all performance monitoring tasks
performed on the BSC6900.
8.2.1 Browsing the Monitoring Results Online

This describes how to browse online and query the monitoring results that are dynamically
displayed in the real-time performance monitoring window.
Prerequisites
l
A performance monitoring task has been started.
Monitoring data has been reported.
Right-click on the Chart tab page in the real-time performance monitoring window. Then,
you can perform the following operations by selecting an appropriate option from the
shortcut menu:
Procedure
Auto Scroll
Show Grid
Switch Display Mode
NOTE
When the number of real-time monitoring tasks is greater than 60, right-click on the Chart tab page
and choose Switch Display Mode from the shortcut menu:
l If the bar chart has been displayed, you can switch it to the sequence diagram.
l If the sequence diagram has been displayed, you cannot switch it to the bar chart.
Auto Adjust
l
Right-click on the List tab page in the real-time performance monitoring window. Then,
you can perform the following operation by selecting an appropriate option from the
shortcut menu:
Setting auto scroll
Right-click on the task information pane at the bottom of the real-time performance
monitoring window. Then, you can perform the following operations by selecting an
appropriate option from the shortcut menu:
Add Task or Delete Task
Stop Task or Restart Task
List Detailed Task Info
----End
8.2.2 Setting Chart Display Mode

This section describes how to set the chart display mode in the real-time performance monitoring
window after you create and start a monitoring task. On the lower part of the Chart tab page in
Issue 02 (2015-05-08)

150
BSC6900 UMTS
LMT User Guide
the window, you can set the chart display properties, such as the line color, line type, and line
width.
Prerequisites
l
Procedure
Step 1 In the task information pane of the real-time performance monitoring window, click Line
Color, Line Type, or Line Width.
Step 2 Select the required properties from the drop-down lists.
NOTE
l The chart display attribute settings apply only to the current monitoring task.
l You can set the chart display mode If data is displayed on the List tab page but no chart is displayed
on the Chart tab page during the real-time monitoring.
----End
8.2.3 Saving Monitoring Data

This section describes how to save the monitoring data as local files.
Prerequisites
l
Procedure
Step 1 When you create a monitoring task, select the Save File check box and specify the save path.
By default, the Save File check box is selected and the save path is C:/Web LMT/MBSC/
output/monitor.
----End
8.2.4 Offline Browsing Monitoring Data

This section describes how to offline browse CPU usage monitoring data files and errored
second monitoring data files using the traffic recording review tool.
Prerequisites
The monitoring data has been saved as files.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecording
Review Tool.
Issue 02 (2015-05-08)

151
BSC6900 UMTS
LMT User Guide
Step 2 Open save path of monitoring data files. The default save path is C:/Web LMT/MBSC/output/
monitor. Select the file to be browsed.
Step 3 Click Open or double-click the file. The TrafficRecording Review Tool window is displayed,
showing the monitoring data in a chart or a table.
Step 4 Click the List or Chart tab to view the data in different modes.
Step 5 To view other files, choose File > Open. In the Open dialog box, select and open the target files
to browse them.
----End
8.3 Common Monitoring

This section describes common performance monitoring.
8.3.1 Monitoring Board CPU/DSP Usage

This section describes how to query the CPU/DSP usage of a board.
Prerequisites
The board to be monitored is running properly.
Context
The OMU and SAU boards do not support this function.
NOTICE
This function increases the CPU usage. Therefore, if the CPU usage reaches 80% or higher, set
the monitoring period to 5s.
Procedure
Step 1 On the LMT main page, click Monitor. The Monitor tab page is displayed.
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > CPU/DSP
Usage Monitoring. The CPU/DSP Usage Monitoring dialog box is displayed.
Step 3 In the CPU/DSP Usage Monitoring dialog box, set parameters according to actual situations,
and click Submit.
l NE Time displayed in the status bar may be different from the actual NE time, but the
difference does not affect services.
----End
Issue 02 (2015-05-08)

152
BSC6900 UMTS
LMT User Guide
8.3.2 Monitoring Transmission Resources

This section describes how to monitor the transmission resources on the Iub interface.
Prerequisites
The board under monitoring is functional.
Procedure
Step 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Transport
Resource Real-Time Monitoring. The Transport Resource Real-Time Monitoring dialog
box is displayed.
Step 3 In the Transport Resource Real-Time Monitoring dialog box, set the parameters as required,
and click Submit.
l Statistic Period(s): Specifies the duration of the measurement period for monitoring.
l Transport Object Type: Specifies the type of the transport object to be monitored. It can
be set to IP Logic Port, Physical Port. For detailed settings, see Table 8-1.
Table 8-1 Detailed settings of Transport Object Type
Transport Object Type
Description
IP Logic Port
Indicates the number of the IP logical port.

Logic Port No. must be specified.
l Logic Port No.: Indicates the logical
port number. To query the logical port
number, run the LST
IPLOGICPORT command.
Issue 02 (2015-05-08)

153
BSC6900 UMTS
LMT User Guide
Transport Object Type
Description
Physical Port
Indicates the number of the physical port.

Physical Port Type must be specified.
l MP Group: Indicates the number of the
physical port carrying an MP link in the
MP group. To query MP Group, run the
LST MPGRP command.
l PPP Link: Indicates the number of the
physical port carrying the PPP link. To
query PPP Link, run the LST
PPPLNK command.
l FRA Link: Indicates the number of the
physical port carrying the FRA link. To
query FRA Link, run the LST
FRALNK command.
l IMA Group: Indicates the number of
the physical port number carrying an
IMA link in the IMP group. To query
IMA Group, run the LST IMAGRP
command.
l UNI Link: Indicates the number of the
physical port carrying the UNI link. To
query UNI Link, run the LST
UNILNK command.
l Subrack No.: Indicates the number of the subrack where the transport object to be monitored
is located.
l Slot No.: Indicates the number of the slot where the transport object to be monitored is
located.
l OP Index No.: Indicates the monitored operator of the transport object.
l Statistic Type: Indicates the statistic type displayed in the monitoring report. It can be set
to Bandwidth(Original) or Bandwidth(Statistic). Then, you can select Uplink or
Downlink to view the uplink or downlink statistics. If you have selected Bandwidth
(Original), the bandwidths allocated to different services are displayed. If you have selected
Bandwidth(Statistic), the total bandwidth used by all services is displayed.
Bandwidth(Original): Displays the actual bandwidths allocated to different services
when the UE is performing a voice service or data service. Table 8-2 shows the related
statistic items.
Bandwidth(Statistic): Displays the total bandwidths of those allocated to different
services. Table 8-3 shows the related statistic items.
Uplink/Downlink: Displays the statistics of the bandwidths in the uplink or downlink.
Issue 02 (2015-05-08)

154
BSC6900 UMTS
LMT User Guide
Table 8-2 Bandwidth(Original)

Statistic Item
(Original)
Description
Admitted Bandwidth
(3G Total)
Admitted bandwidth for 3G services at the transport layer on the

user plane. The admitted bandwidth consists of bandwidth used for
setting up the common channel and bandwidth for guaranteed bit
rate (GBR). When calculating the bandwidth for GBR, bandwidth
at the radio layer needs to be converted to that at the transport layer.
OLC Clear Threshold
Overload control (OLC) end threshold. It equals configured

bandwidth minus overload congestion clear remain bandwidth.
To query the configured bandwidth, run the DSP
To query the overload congestion clear remain bandwidth, run the
ADD TRMLOADTH command. Note that when Threshold
type is set to PERCENTAGE(Percentage), the overload
congestion clear remain bandwidth equals the configured
bandwidth multiplied by the overload congestion clear remain
ratio.
OLC Threshold
OLC start threshold. It equals configured bandwidth minus

overload congestion remain bandwidth.
To query the overload congestion remain bandwidth, run the ADD
TRMLOADTH command. Note that when Threshold type is set
to PERCENTAGE(Percentage), the overload congestion remain
bandwidth equals the configured bandwidth multiplied by the
congestion remain ratio.
Available Bandwidth
Bandwidth available currently. It equals Total Bandwidth minus

Admitted Bandwidth(3G Total) minus Admitted Bandwidth
(2G Total) minus signaling bandwidth. Admitted Bandwidth(2G
Total) is valid when 2G and 3G services share the same port.
To query the signaling bandwidth, run the DSP
IPLOGICPORT command. The signaling bandwidth cannot be
queried when Transport Object Type is set to Physical Port.
Reserved Threshold
for Handover
Threshold for reserving bandwidth for handovers. It equals

configured bandwidth minus handover reserved bandwidth.
To query the handover reserved bandwidth, run the ADD
to PERCENTAGE(Percentage), the handover reserved
handover reserved ratio.
RealTimeFluxBw
Issue 02 (2015-05-08)
Real-time traffic on a port.

155
BSC6900 UMTS
LMT User Guide
Statistic Item
(Original)
Description
Realtime Bandwidth
Bandwidth detected on a port.
RealTimeQueueFlux
Real-time traffic in the service queues on a port.
Congestion Clear
Threshold
Congestion end threshold. It equals configured bandwidth minus

congestion clear remain bandwidth.
To query the congestion clear remain bandwidth, run the ADD
to PERCENTAGE(Percentage), the congestion clear remain
congestion clear remain ratio.
Congestion Threshold
Congestion start threshold. It equals configured bandwidth minus

congestion remain bandwidth.
To query the congestion remain bandwidth, run the ADD
to PERCENTAGE(Percentage), congestion remain bandwidth
equals the configured bandwidth multiplied by congestion remain
ratio.
Total Bandwidth
When Auto adjust bandwidth switch is set to OFF(OFF) in the

ADD IPLOGICPORT command, Total Bandwidth equals
configured bandwidth. To query configured bandwidth, run the
DSP IPLOGICPORT command. When Auto adjust bandwidth
switch is set to ON(ON), Total Bandwidth fluctuates between
Max bandwidth [64kbps] and Min bandwidth [64kbps] based
on transmission quality indicated by IPPM detection.
Table 8-3 Statistic Item(Statistic)
Issue 02 (2015-05-08)
Statistic Item
(Statistic)
Description
Admitted Bandwidth
(3G Total)
Admitted bandwidth for 3G services at the transport layer on the

user plane. The admitted bandwidth consists of bandwidth used for
setting up the common channel and bandwidth for guaranteed bit
rate (GBR). When calculating the bandwidth for GBR, bandwidth
at the radio layer needs to be converted to that at the transport layer.

156
BSC6900 UMTS
LMT User Guide
Statistic Item
(Statistic)
Description
Available Bandwidth
Bandwidth available currently. It equals Total Bandwidth minus

Admitted Bandwidth(3G Total) minus Admitted Bandwidth
(2G Total) minus signaling bandwidth. Admitted Bandwidth(2G
Total) is valid when 2G and 3G services share the same port.
To query the signaling bandwidth, run the DSP
IPLOGICPORT command. The signaling bandwidth cannot be
queried when Transport Object Type is set to Physical Port.
Congestion Clear
Threshold
Congestion end threshold. It equals configured bandwidth minus

congestion clear remain bandwidth.
To query the congestion clear remain bandwidth, run the ADD
to PERCENTAGE(Percentage), the congestion clear remain
congestion clear remain ratio.
Congestion Threshold
Congestion start threshold. It equals configured bandwidth minus

congestion remain bandwidth.
To query the congestion remain bandwidth, run the ADD
to PERCENTAGE(Percentage), the congestion remain
OLC Clear Threshold
OLC end threshold. It equals configured bandwidth minus

overload congestion clear remain bandwidth.
To query the overload congestion clear remain bandwidth, run the
ADD TRMLOADTH command. Note that when Threshold
type is set to PERCENTAGE(Percentage), the overload
congestion clear remain bandwidth equals the configured
bandwidth multiplied by the overload congestion clear remain
ratio.
Issue 02 (2015-05-08)

157
BSC6900 UMTS
LMT User Guide
Statistic Item
(Statistic)
Description
OLC Threshold
Overload control (OLC) start threshold. It equals configured

bandwidth minus overload congestion remain bandwidth.
To query the overload congestion remain bandwidth, run the ADD
to PERCENTAGE(Percentage), the overload congestion remain
Realtime Bandwidth
Bandwidth detected on a port.
RealTimeQueueFlux
Real-time traffic in the service queues on a port.
Reserved Threshold
for Handover
Threshold for reserving bandwidth for handovers. It equals

configured bandwidth minus handover reserved bandwidth.
To query the handover reserved bandwidth, run the ADD
to PERCENTAGE(Percentage), the handover reserved
handover reserved ratio.
Total Bandwidth
When Auto adjust bandwidth switch is set to OFF(OFF) in the

ADD IPLOGICPORT command, Total Bandwidth equals
configured bandwidth. To query configured bandwidth, run the
DSP IPLOGICPORT command. When Auto adjust bandwidth
switch is set to ON(ON), Total Bandwidth fluctuates between
Max bandwidth [64kbps] and Min bandwidth [64kbps] based
on transmission quality indicated by IPPM detection.
----End
8.3.3 Monitoring BERS

This section describes how to monitor errored second (ES)of an E1/T1 port to monitor
transmission quality of the link corresponding to a port. If any bit errors occur on the E1/T1 port,
this function helps users obtain data, such as ES, severely errored second (SES), unavailable
second (UAS), errored frames, CRC errors, bit error rate (calculated by CRC errors). Based on
the data and performance of the peer device, you can evaluate the transport network status and
identify the causes for the errors. The AEUa, AOUc, PEUa, PEUc, POUc board supports this
function.
Procedure
Issue 02 (2015-05-08)

158
BSC6900 UMTS
LMT User Guide
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > BERS
Monitoring. The BERS Monitoring dialog box is displayed.
Step 3 In the BERS Monitoring dialog box, set parameters according to actual situations, and click
Submit.
----End
8.3.4 Monitoring BER

This section describes how to monitor bit error rate (BER). The BER is used to evaluate transport
network quality. The AEUa, AOUc, PEUa, PEUc, POUc, POUa, AOUa board supports this
function.
Context
l
Using this function interrupts IMA groups, UNI links, fractional ATM links, fractional
IMA links, MP groups, or PPP links carried on a board. As a result, services on the
corresponding port are interrupted.
Before monitoring the BER, configure the local loopback or remote loopback, or use a
loopback connector to short-circuit the TX end and the RX end.
BER monitoring test and loopback test cannot be performed simultaneously because the
result and principles of these tests are the same.
Only one BER monitoring test can be started for a board at a time.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > BER
Monitoring. The BER Monitoring dialog box is displayed.
Step 3 In the BER Monitoring dialog box, set parameters according to actual situations, and click
Submit.
----End
8.3.5 Monitoring Link Performance

This section describes how to monitor link performance. A maximum of six monitoring tasks
can be started simultaneously on the LMT. One monitoring task corresponds to one task window.
When six tasks have started, you must close one task window before starting a new task.
Reference for Performance Monitoring

This section describes the parameters used for performance monitoring.
Issue 02 (2015-05-08)
Monitor
Item
Parameter
Description
IMA Group
IMA Group No.
Indicates the number of the IMA group. To query the

IMA group, run the LST IMAGRP command.

159
BSC6900 UMTS
LMT User Guide
Monitor
Item
Parameter
Description
UNI link
UNI Link No.
Indicates the number of the UNI link. To query the UNI

link, run the LST UNILNK command.
Fractional
ATM Link
FRAC Link No.
Indicates the number of the fractional ATM link. To

query the number of the fractional ATM link, run the
LST FRALNK command and set Link type to
FRAATM.
SAAL Link
SAAL Link No.
Indicates the number of the SAAL link. To query the

SAAL link, run the LST SAALLNK command.
IPOA PVC
IP Address
Indicates the local and peer IP addresses of the IPOA

PCV. To query these IP addresses, run the LST
IPOAPVC command.
Ping Peer IP
Address
AAL2 Path
Adjacent Node ID
AAL2 PATH
Symbol
FE/GE
FE/GE Port No.
Indicates the number of the FE/GE port. To query the

number of the FE/GE port, run the LST ETHPORT
command.
PPP Link
PPP Link No.
Indicates the number of the PPP link. To query the PPP

link, run the LST PPPLNK command.
MLPPP
Group
MLPPP Group
No.
Indicates the number of the MLPPP group. To query

the number of the MLPPP group, run the LST
MPGRP command.
SCTP Link
SCTP Link No.
Indicates the number of the SCTP link. To query the

SCTP link, run the LST SCTPLNK command.
IP Path
Adjacent Node ID
Indicates the number of the adjacent node of the IP

path. To query the adjacent node of the IP path, run the
LST IPPATH command.
IP PATH Symbol
Issue 02 (2015-05-08)
Indicates the ID of the adjacent node to an AAL2 path

and the AAL2 path symbol. To query the adjacent node
ID and the AAL2 path symbol, run the LST
AAL2PATH command.
Logical Port
Port No.
Indicates the number of a logical port. To query the

ATM logical port, run the LST ATMLOGICPORT
command.To query the IP logical port, run the LST
OAM
NodeB ID
Indicates the NodeB ID. To query the NodeB ID, run

the LST UNODEB command.

160
BSC6900 UMTS
LMT User Guide
Monitor
Item
Parameter
Description
FE/GE
Priority Group No.
Indicates the priority queue number. (value range: 0-7).
NonChannelized
ATM Optical
Port
Optical Port No.
Indicates the number of the non-channelized ATM

optical port. To query the optical port, run the LST
OPT command.
IPPM
Adjacent Node ID
IP Path ID
Indicates the ID of the node adjacent to an IPPM and

the IP path ID. To query the two, run the LST IPPM
command.
TRUNK
Group
TRUNK Group
No.
Indicates the number of the trunk group. To query the

trunk group, run the LST ETHTRK command.
IPPOOL
LOCAL IP
Local IP Address
To query the local IP address, run the LST

IPPOOLIP command.
IPPOOL PM
Local IP Address
Is the same as Currently bound SIP, the IP address

currently bound to the adjacent node. To query
Currently bound SIP, run the DSP ADJNODE
command.
PPP Link
MLPPP
Group
Logical Port
Bandwidth
Peer IP Address
Priority
To query the peer IP address, run the DSP

ADJNODEDIP command.
To query the priority, run the LST IPPOOLPM
command and view the setting for Per-Hop
Behavior.
IURPLINK
IURP Link No.
To query the IURP Link, run the LST IURPLNK

command.
Monitoring IMA Group Traffic

This section describes how to monitor traffic on a specified IMA group in real time. The
monitoring result is displayed in lists and charts. Based on the traffic statistics on the IMA groups
at both ends, you can check the IE loss, locate the fault, and evaluate transport network quality.
In addition, you can check whether the monitored traffic is consistent with the actual traffic
processed by the IMA group and whether the bandwidth is sufficient. The check result provides
reference for adding links.
Issue 02 (2015-05-08)

161
BSC6900 UMTS
LMT User Guide
Context
NOTICE
The IMA group must be successfully set up and connected to the peer link before this task is
performed. This task is stopped if the monitored IMA group is deleted.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Link
Performance Monitoring. The Link Performance Monitoring dialog box is displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IMA Group and set
other parameters according to actual situations. Then, click Submit.
----End
Monitoring UNI Link Traffic

This section describes how to monitor traffic on a specified UNI link in real time. The monitoring
result is displayed in lists and charts. Based on the traffic statistics on the UNI links at both ends,
you can check the IE loss, locate the fault, and evaluate transport network quality. In addition,
you can check whether the monitored traffic is consistent with the actual traffic processed by
the UNI link and whether the bandwidth is sufficient. The check result provides reference for
changing the link configuration mode. For example, change the link configuration mode to the
IMA mode to support more traffic.
Context
NOTICE
The UNI link must be successfully set up and connected to the peer link before this task is
performed. This task is stopped if the monitored link is deleted.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to UNI Link and set other
parameters according to actual situations. Then, click Submit.
----End
Issue 02 (2015-05-08)

162
BSC6900 UMTS
LMT User Guide
Monitoring Fractional ATM Link Traffic

This section describes how to monitor traffic on a specified fractional ATM link in real time.
The monitoring result is displayed in lists and charts. Based on the traffic statistics on the
fractional ATM links at both ends, you can check the IE loss, locate the fault, and evaluate
transport network quality. In addition, you can check whether the monitored traffic is consistent
with the actual traffic processed by the link and whether the bandwidth is sufficient. The check
result provides reference for changing the link configuration mode. For example, change the
link configuration mode to the IMA mode.
Context
NOTICE
The fractional ATM link must be successfully set up and connected to the peer link before this
task is performed. This task is stopped if the monitored link is deleted.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Fractional ATM
Link and set other parameters according to actual situations. Then, click Submit.
----End
Monitoring SAAL Link Traffic

This section describes how to monitor traffic on a specified SAAL link in real time. The
monitoring result is displayed in lists and charts. Based on the TX/RX statistics on the SAAL
links to a subsystem, you can check the packet loss, locate the SAAL disconnection or
intermittent disconnection. In addition, you can observe the link traffic and check whether link
congestion occurs based on the configured link bandwidth.
Context
NOTICE
The SAAL must be successfully set up and connected to the peer link before this task is
Issue 02 (2015-05-08)

163
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SAAL Link and set
----End
Monitoring IPOA PVC Link Traffic

This section describes how to monitor traffic on a specified IPOA PVC link in real time. The
monitoring result is displayed in lists and charts. If the IPOA PVC link works as an OML for
the ATM-based base station, this function helps you locate base station startup and load problems
and helps you observe the traffic and bandwidth utilization. If the IPoA PVC link works as an
IP path over the Iu-PS interface, this function helps you observe the link traffic and locate
connection and congestion problems of upper-layer links.
Context
NOTICE
The IPOA PVC link must be successfully set up and connected to the peer link before this task
is performed. This task is stopped if the monitored link is deleted.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPOA PVC and set
----End
Monitoring AAL2 Path Traffic

This section describes how to monitor traffic on a specified AAL2 path in real time. The
monitoring result is displayed in lists and charts. Based on the layer-2 TX/RX statistics in the
CDT data, you can check the packet loss and evaluate the traffic condition. In addition, you can
observe the link traffic and check whether link congestion occurs based on the configured link
bandwidth.
Issue 02 (2015-05-08)

164
BSC6900 UMTS
LMT User Guide
Context
NOTICE
The AAL2 path must be successfully set up and connected to the peer link before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to AAL2 Path and set
----End
Monitoring FE/GE Port Traffic

This section describes how to monitor traffic on a specified FE/GE port in real time. The
monitoring result is displayed in lists and charts. Based on the traffic statistics on the FE/GE
port, you can check the packet loss, locate the fault, and evaluate transport network quality. In
addition, you can check whether the monitored traffic is consistent with the actual traffic on the
port, check the port utilization, and check whether the bandwidth is sufficient. The check result
provides reference for migrating services to prevent congestion.
Context
NOTICE
The FE/GE port must be successfully configured and connected to the peer port before this task
is performed. This task is stopped if the monitored link is deleted.
For FG2c, GOUc, GOUe boards, if the physical port carries a logical port and Monitor Type
is set to QoS for this task, the queue statistics of the physical port does not include the service
data traffic on the logical port but includes only the service data traffic on the physical port.
Procedure
Issue 02 (2015-05-08)

165
BSC6900 UMTS
LMT User Guide
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to FE/GE and set other
----End
Monitoring PPP Link Traffic

This section describes how to monitor traffic on a specified PPP link in real time. The monitoring
result is displayed in lists and charts. Based on the traffic statistics on the PPP links at both ends,
you can check the packet loss, locate the fault, and evaluate transport network quality. In addition,
you can check whether the monitored traffic is consistent with the actual traffic processed by
the link and whether the link bandwidth is sufficient. The check result provides reference for
adding PPP links or changing the link configuration mode to MLPPP.
Context
NOTICE
The PPP link must be successfully set up and connected to the peer link before this task is
For POUc boards, if the physical port carries a logical port and Monitor Type is set to QoS for
this task, the queue statistics of the physical port does not include the service data traffic on the
logical port but includes only the service data traffic on the physical port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to PPP Link and set other
----End
Monitoring MLPPP Group Traffic

This section describes how to monitor traffic on a specified MLPPP group in real time. The
monitoring result is displayed in lists and charts. Based on the statistics on MLPPP groups at
both ends, you can check the packet loss, locate the fault, and evaluate transport network quality.
processed by the MLPPP group and whether the bandwidth is sufficient. The check result
provides reference for adding links.
Issue 02 (2015-05-08)

166
BSC6900 UMTS
LMT User Guide
Context
NOTICE
The MLPPP group must be successfully configured and connected to the peer link before this
task is performed. This task is stopped if the monitored MLPPP link group is deleted.
For POUc boards, if the physical port carries a logical port and Monitor Type is set to QoS for
this task, the queue statistics of the physical port does not include the service data traffic on the
logical port but includes only the service data traffic on the physical port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to MLPPP Group and
set other parameters according to actual situations. Then, click Submit.
----End
Monitoring SCTP Link Traffic

This section describes how to monitor data packet traffic on a specified SCTP link in real time.
The monitoring result is displayed in lists and charts. Based on the monitored traffic, you can
check the packet loss, locate SCTP link intermittent disconnection, and check whether link
congestion occurs.
Context
NOTICE
The SCTP link must be successfully set up and connected to the peer link before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SCTP Link and set
----End
Issue 02 (2015-05-08)

167
BSC6900 UMTS
LMT User Guide
Monitoring IP Path Traffic

This section describes how to monitor IP traffic on a specified IP path over an interface board
in real time. The monitoring result is displayed in lists and charts. Based on the layer-2 statistics
in the CDT data, you can check the packet loss and user data traffic. In addition, you can observe
link traffic and check whether link congestion occurs.
Context
NOTICE
The IP path must be successfully set up and connected to the peer link before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IP Path and set other
----End
Monitoring Logical Port Traffic

This section describes how to monitor traffic on a specified logical port. You can set Monitor
Type to Port or QoS for this function. If Monitor Type is set to Port, the real-time traffic is
shown in the monitoring result. If Monitor Type is set to QoS, the QoS-specific TX traffic on
the logical port is shown in the monitoring result. Based on the traffic statistics on the logical
port, you can check the packet loss on the logical port and locate the fault. In addition, you can
check whether the monitored traffic is consistent with the actual traffic on the port, check the
port utilization, and check whether the bandwidth is sufficient. The check result provides
reference for increasing the bandwidth configured on the logical port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Logical Port and set
----End
Issue 02 (2015-05-08)

168
BSC6900 UMTS
LMT User Guide
Monitoring OAM Channel Traffic

This section describes how to monitor RX and TX IP traffic on a specified operation,
administration, and maintenance (OAM) channel over an interface board in a NodeB. The
monitoring result is displayed in lists and charts. You can perform this function to observe the
traffic and bandwidth usage when the NodeB is loading data. Therefore, this function helps
locate the fault in the NodeB startup and data loading processes.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to OAM and set other
----End
Monitoring Logical Port Bandwidth

This section describes how to monitor the bandwidth changes in a logical port after the dynamic
bandwidth adjustment. The monitoring result is displayed in lists and charts. This task supports
IP pool performance monitoring (PM) function so that you can observe the bandwidth changes
after dynamic adjustment. In this way, you can check whether the bandwidth is adjusted properly.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Logic Port
Bandwidth and set other parameters according to actual situations. Then, click Submit.
----End
Monitoring Traffic on Non-Channelized ATM Optical Port

This section describes how to monitor traffic on a specified non-channelized ATM optical port
in real time. The monitoring result is displayed in lists and charts. Based on the traffic statistics
on the non-channelized ATM optical ports at both ends, you can check the IE loss, locate the
fault, and evaluate transport network quality. In addition, you can check whether the monitored
traffic is consistent with the actual traffic on the port and whether the bandwidth is sufficient.
The check result provides reference for increasing the bandwidth.
Issue 02 (2015-05-08)

169
BSC6900 UMTS
LMT User Guide
Context
NOTICE
The specified non-channelized ATM optical port must be connected to the peer port using links.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Non-Channelized
ATM Optical Port and set other parameters according to actual situations. Then, click
Submit.
----End
Monitoring IP Pool PM Link Traffic

This section describes how to monitor PM link traffic in a specified IP pool in real time. The
monitoring result is displayed in lists and charts. Based on the PM link traffic statistics on the
IP pool at the TX and RX ends, you can check the packet loss and locate transmission
disconnection or intermittent disconnection in IP pool networking mode. In addition, you can
observe PM link traffic and check whether link congestion occurs.
Context
NOTICE
The PM link to be monitored in the IP pool must be activated.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL PM and set
----End
Monitoring Trunk Group Traffic

This section describes how to monitor traffic on a specified trunk group in real time. The
monitoring result is displayed in lists and charts. Based on the traffic statistics of the trunk groups
Issue 02 (2015-05-08)

170
BSC6900 UMTS
LMT User Guide
at both ends, you can check the IE loss, locate the fault, and evaluate transport network quality.
processed by the trunk group and check whether the bandwidth is sufficient. The check result
provides reference for adding links.
Context
NOTICE
The trunk group to be monitored must be configured successfully.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to TRUNK Group and
----End
Monitoring Local IP Traffic in IP Pool

This section describes how to monitor traffic on a specified local port in an IP pool in real time.
The monitoring result is displayed in lists and charts. Based on the statistics on the local port,
you can locate the fault and evaluate transport network quality. In addition, you can check the
local port utilization. The check result provides reference for migrating services on the port to
prevent congestion.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL LOCAL
IP and set other parameters according to actual situations. Then, click Submit.
----End
Monitoring IPPM Link Traffic

This section describes how to monitor traffic on a specified IPPM link in real time. The
monitoring result is displayed in lists and charts. Based on the traffic statistics on IPPM links at
both ends, you can check the packet loss, and locate the IPPM link disconnection or intermittent
disconnection. In addition, you can observe link traffic and check whether link congestion
occurs.
Issue 02 (2015-05-08)

171
BSC6900 UMTS
LMT User Guide
Context
NOTICE
The IPPM link to be monitored has been activated.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPM and set other
----End
Monitoring Iur-p Link Traffic

This section describes how to monitor traffic on a specified Iur-p link in real time. The monitoring
result is displayed in lists and charts. Based on the traffic statistics on the Iur-p link, you can
check the packet loss, locate the fault, and evaluate transport network quality. In addition, you
can check the link traffic. The check result provides reference for adding links to the Iur-p
interface to prevent congestion.
Context
NOTICE
The Iur-p link must be configured and connected to the peer port before this task is performed.
This task is stopped if the monitored link is deleted.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IURPLNK and set
----End
Issue 02 (2015-05-08)

172
BSC6900 UMTS
LMT User Guide
8.4 UMTS Monitoring

This section describes performance monitoring of UMTS services.
8.4.1 Monitoring Connection Performance

This section describes how to monitor performance of physical connections of UEs during a
call. A maximum of six monitoring tasks can be started simultaneously for a monitoring item.
Monitoring P-CPICH Ec/No and RSCP

This section describes how to monitor the P-CPICH Ec/No and RSCP of a cell in the active set
in real time. Based on the number of cells in the active set and signal strength of each cell, you
can learn about whether the current connection is at the edge or the center of the cell.
Context
l
There is no way to avoid that some user data such as International Mobile Subscriber
Identity (IMSI) will be used during problem location and resolution. This function provides
an anonymous data processing method. You are recommended to comply with local laws
when executing the task and take ample measures to fully protect user data, such as enabling
the anonymous function and deleting the folder that saves trace records after you finish
processing data.
When entering IMSI, check whether IMSI data to be entered must be anonymous by running
the LST USERIDANONSWITCH command and querying User Identity Anonymity
Switch.
If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and
anonymous IMSI data must be entered in IMSI. The anonymous IMSI data is the IMSI
data encrypted by the HMACUtil using the cipher key.
If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user
IMSI data is directly entered in IMSI.
NOTE
l Change the anonymous policy and cipher key on the U2000 by choosing Trace and Maintenance >
Signaling Trace > Anonymous Policy Management > Anonymous Cypher Key Management
(application style) or Trace and Maintenance > Monitor > Signaling Trace > Anonymous Policy
Management > Anonymous Cypher Key Management (traditional style). For details, see U2000
Fault Management User Guide.
l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the
tracing task. Otherwise, the tracing task becomes invalid.
l For details about how to obtain the HMACUtil, contact Huawei technical support.
Issue 02 (2015-05-08)

173
BSC6900 UMTS
LMT User Guide
NOTICE
Before running this monitoring task, perform either of the following operations:
l Run SET UCORRMALGOSWITCH to set Handover algorithm switch. Ensure that
SOFT_HANDOVER_SWITCH is selected for this parameter.
l Run MOD UCELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE.
NOTE
l This task is used only to monitor connections on dedicated channels. An ongoing task is stopped if the
monitored connection is released or relocated from the dedicated channel to a common channel. The
task is restarted if the monitored connection is relocated from the common channel to a dedicated
channel.
l This task is used only to monitor the real-time data of the cells in the active set. The data of other cells
is not reported. Therefore, the monitoring results reflect the changes in the number of cells in the active
set in real time.
l A maximum of three cells in the active set can be monitored in a task.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Connection
Performance Monitoring. The Connection Performance Monitoring dialog box is displayed.
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to PCPICH Ec/
No RSCP and set other parameters according to actual situations. Then, click Submit.
NOTE
After the monitoring task is started, a real-time monitoring window is displayed. The task name is displayed in
the title bar of the window and the monitoring result is displayed in lists and charts.
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported PCPICH Ec/No (unit: dB) and RSCP (unit: dBm).
l RSCP refers to the received signal code power measured on a P-CPICH. The reference point for RSCP
measurement is at the antenna connector of a UE. If the P-CPICH uses transmit diversity, you need to
measure the RSCP of each antenna and sum up all of the RSCP values to obtain the total RSCP of the PCPICH.
l Ec/No refers to the ratio of received energy per chip to noise spectral density. Like RSCP/RSSI, Ec/No is
also measured on the P-CPICH. The reference point for Ec/No measurement is also at the antenna connector
of the UE. If the P-CPICH uses transmit diversity, you need to measure the Ec/No of each antenna and sum
up all of the Ec/No values to obtain the total Ec/No of the P-CPICH.
----End
Monitoring SIR Values of the Uplink RLSs

This section describes how to monitor the signal-to-interference ratio (SIR) values of the uplink
radio link sets (RLSs) used by a UE in real time. By performing this task, you can learn about
the uplink radio link quality and quality variations.
Issue 02 (2015-05-08)

174
BSC6900 UMTS
LMT User Guide
Context
NOTE
A task can be started for a UE. The monitoring result includes the number of cells in the active set and the
signal strength of each cell. Based on the monitoring result, you can know whether the current connection
is at the edge or the center of the cell.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL SIR and set
NOTE
the title bar of the window and the monitoring result is displayed in lists and charts. The monitoring result can
reflect the changes in the number of the RLSs in real time.
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported
SIR of the UL RLSs (unit: dB).
The SIR is calculated using the formula (RSCP/ISCP) x SF, where:
l RSCP is short for Received Signal Code Power and reflects the received power on one code.
l ISCP is short for Interference Signal Code Power and reflects interference to the received signal. Only the
non-orthogonal interference is measured for ISCP.
l SF is short for the spreading factor of a DPCCH.
This task is performed on the DPCCH after radio links are combined on the NodeB. In compressed mode, the
SIR is not measured during the transmit intervals. The NodeB reports the measured uplink SIR values to the
BSC6900.
----End
Monitoring the Outer Loop Power Control

This section describes how to monitor parameter values during outer loop power control. Based
on the current service type, the parameters include Number of Total Blocks, Number of Error
Blocks, OLPC UL BLER, OLPC UL BER, OLPC BER Filter, OLPC SIR Target, OLPC
SIR Target High Precision, E-DCH Average Transmission Number, Total Number of
Transmission Times, Total Number of Discarded PDUs, Total Number of PDUs, and EDCH Residual BLER.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to OLPC and set
Issue 02 (2015-05-08)

175
BSC6900 UMTS
LMT User Guide
NOTE
If Monitor Period(s) is set to OLPC, the monitor period is set to the value specified by the OLPC adjustment
period parameter in the ADD UTYPRABOLPC or MOD UTYPRABOLPC command.
the title bar of the window and the monitoring result is displayed in lists and charts. In charts, the X-coordinate
represents the hour: minute: second. Two charts are used to describe five monitoring items.
l The first chart shows the output interface of the OLPC SIR target value, OLPC UL BLER, and OLPC UL
BER. The left Y coordinate represents OLPC SIR Target (range: -10 to 18; unit: dB). The right Y coordinate
represents OLPC UL BLER (range: 0 to 1; unit: none) and OLPC UL BER (range: 0 to 1; unit: none).
l The second chart shows the output interface of E-DCH Average Transmission Number and E-DCH
Residual BLER. The left Y coordinate represents E-DCH Average Transmission Number (default value
range: 0 to 16; unit: none). The coordinate value range can be dynamically adjusted based on the actual
value. The right Y coordinate represents E-DCH Residual BLER (range: 0 to 1; unit: none).
----End
Monitoring the SIR Error Values of UL RLSs

This section describes how to monitor the SIR error values of radio link sets (RLSs) of the current
connection in real time. By performing this task, you can observe whether the SIR can keep up
with the variation of the target values and estimate the UL inner loop power control function. If
the SIR error values change all the time but are approximate to 0 dB, the UL inner loop power
control converges. Otherwise, the UL inner loop power control does not converge.
Context
This task is used only to monitor connections on dedicated channels. An ongoing task is stopped
if the monitored connection is released or relocated from the dedicated channel to a common
channel. The task is restarted if the monitored connection is relocated from the common channel
to a dedicated channel.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL SIR
Error and set other parameters according to actual situations. Then, click Submit.
Issue 02 (2015-05-08)

176
BSC6900 UMTS
LMT User Guide
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported SIR
error values (SIRerror) of the UL RLSs.
l SIRerror (unit: dB) is reported from the NodeB to the BSC6900. The formula is as follows: SIRerror = SIR SIRtarget_ave.
l Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to the time for calculating
the SIR in the preceding formula for calculating SIRerror.
l In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave is not calculated during transmission
intervals. The average of SIRtarget is an arithmetical average. The unit of SIRtarget_ave is dB.
----End
Monitoring DL Code TX Power

This section describes how to monitor the DL code TX power of each radio link of the current
connection in real time. By performing this task, you can analyze the DL power consumption.
If the DL code TX power increases and even approximates to the maximum value configured
in the signaling message, DL quality deteriorates.
Context
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Tx Code
Power and set other parameters according to actual situations. Then, click Submit.
NOTE
the title bar of the window and the monitoring result is displayed in lists and charts. The monitoring results
reflect the changes in the number of the radio links involved in the current connection in real time.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported DL
code TX power (unit: dBm).
Code TX power refers to the NodeB TX power on one channelization code that is on one given scrambling code
on one given carrier. The DL code TX power can be measured on the DPCCH of any radio link outgoing from
the UTRAN and indicates the pilot bit power of the DPCCH.
In compressed mode, the TX power measurement should cover all timeslots, including those during the transmit
intervals. The reference point for measurement is at the antenna connector. If transmit diversity is used, the DL
code TX power is the total of the code TX powers of all antennas.
----End
Issue 02 (2015-05-08)

177
BSC6900 UMTS
LMT User Guide
Monitoring UE TX Power
This section describes how to monitor the TX power of a UE. By performing this task, you can
analyze the UL radio link quality. If the UE TX power increases and even reaches the limit of
the UE capability, the UL radio link quality deteriorates.
Context
UE TX power refers to the transmit power of a UE on a carrier. The reference point for
measurement of the UE TX power is at the antenna connector of the UE.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UE Tx Power
and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UE
TX power (unit: dBm).
----End
Monitoring UL Traffic Volume

This section describes how to monitor the UL traffic volume, that is, the buffered data volume
at the UE side, on the current connection in real time. By performing this task, you can analyze
transmission performance of UL traffic volume. The UL traffic volume on transport channels
is measured by the UE and reported to the BSC6900.
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be
transmitted or retransmitted from the RLC entity on a logical channel. If RLC is in AM mode,
the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmit
window, excluding the PDUs for which no ACK is received.
This task can be used to monitor the connections of PS interactive and background services on
common channels or dedicated channels. As specified in protocols, UEs cannot report the UL
traffic volume of HSUPA services to the RNC. Therefore, the UL traffic volume is not displayed
in the LMT monitoring window.
Issue 02 (2015-05-08)

178
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL Traffic
Vol and set other parameters according to actual situations. Then. click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UL
traffic volume on the UL physical channel (unit: byte).
----End
Monitoring DL Traffic Volume

This section describes how to monitor DL traffic volume, that is, the buffered data volume on
the MSC side, on the current connection in real time. By performing this task, you can analyze
transmission performance of DL traffic volume. The DL traffic volume on transport channels
is measured on the BSC6900.
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be
transmitted or retransmitted from the RLC entity on a logical channel. If RLC is in AM mode,
the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmit
window, excluding the PDUs for which no ACK is received.
common channels or dedicated channels.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Traffic
Vol and set other parameters according to actual situations. Then, click Submit.
NOTE
traffic volume (unit: byte).
----End
Issue 02 (2015-05-08)

179
BSC6900 UMTS
LMT User Guide
Monitoring UL Throughput and Bandwidth

This section describes how to monitor rate variations on the UL transport access stratum and
non-access stratum of the current connection in real time. By performing this task, you can
analyze dynamic channel configuration and service source rate variations.
Context
Throughput refers to the amount of data transmitted on a transport channel in units of time and
is measured on the MAC-d. Bandwidth refers to the maximum rate calculated based on the RLC
payload. The bandwidth changes during RB reconfiguration. The throughput measurement
involves RLC headers, and therefore the measured peak throughput is greater than the
bandwidth.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL Throughput
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UL
throughput and UL bandwidth (unit: bit/s).
l Observe the variations of the UL throughput and bandwidth during verification of dynamic channel
configurations. If the UL bandwidth varies with the UL throughput, dynamic channel configuration is
normal.
l If dynamic channel configuration is not used, observe the variation of UL throughput to verify service source
rate variations.
----End
Monitoring DL Throughput and Bandwidth

This section describes how to monitor rate variations on the DL transport access stratum and
non-access stratum of the current connection in real time. By performing this task, you can
analyze dynamic channel configuration and service source rate variations.
Context
Throughput refers to the amount of data transmitted on a transport channel in units of time and
is measured on the MAC-d. Bandwidth refers to the maximum rate calculated based on the RLC
payload. The bandwidth changes during RB reconfiguration. The throughput measurement
involves RLC headers, and therefore the measured peak throughput is greater than the
bandwidth.
Issue 02 (2015-05-08)

180
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Throughput
NOTE
throughput and DL bandwidth (unit: bit/s).
l Observe the variations of the DL throughput and bandwidth during verification of dynamic channel
configurations. If the DL bandwidth varies with the DL throughput, dynamic channel configuration is
normal.
l If dynamic channel configuration is not used, observe the variation of DL throughput to verify service source
rate variations.
----End
Monitoring Handover Delay

This section describes how to monitor the handover delay.
Context
Handover delay refers to the time taken by each handover. During this period of time, the
BSC6900 makes a handover decision, initiates the handover (including the soft handover and
the hard handover), and completes the handover.
This task is used only to monitor the handover delay of a UE in the CELL_DCH state. An ongoing
task is stopped if the UE transits from the CELL_DCH state to the CELL_FACH state or idle
mode. The task is restarted if the UE transits from the CELL_FACH state or idle mode back to
the CELL_DCH state.
A maximum of five tasks can be simultaneously started on the LMT. This task can monitor the
delay of an intra-frequency or inter-frequency handover but not an inter-RAT handover.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Handover
Delay and set other parameters according to actual situations. Then, click Submit.
Issue 02 (2015-05-08)

181
BSC6900 UMTS
LMT User Guide
Monitoring
Results
Description
HO Delay(ms)
Time taken by a handover
HO Interval(ms)
Difference between the end time of the preceding handover and the
end time of the current handover
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents handover delay
and interval (unit: ms).
----End
Monitoring DL Transport Channel BLER

This section describes how to monitor block error rate (BLER) variations on all transport
channels. By performing this task, you can analyze the DL radio link quality. If the BLER of
the DL transport channel increases, the DL radio link quality deteriorates. If the BLER decreases,
the DL radio link quality improves.
Context
The BLER of the DL transport channel is measured on the UE and used for outer loop power
control.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL BLER and
NOTE
the title bar of the window and the monitoring result is displayed in lists and charts. The monitoring results
reflect the changes in the number of traffic transport channels in real time. The number of signaling transport
channels is always 1.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported BLER
of the DL transport channel (unit: %).
----End
Issue 02 (2015-05-08)

182
BSC6900 UMTS
LMT User Guide
Monitoring AMR Mode

This section describes how to monitor the variation in the configured AMR rate in real time.
Context
This task can be started only if the traced UE is processing AMR services.
The narrowband AMR has eight available rates, that is, eight AMR modes: 12.2 kbit/s, 10.2 kbit/
s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.
The wideband AMR has nine available rates, that is, nine AMR modes: 23.85 kbit/s, 23.05 kbit/
s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.60 kbit/s.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to AMR Mode and
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the maximum
AMR rate in the uplink and downlink (unit: kbit/s).
----End
Monitoring AMR EVQI

This section describes how to monitor the UL and DL enhanced-VQI (EVQI) of the ongoing
wideband or narrowband AMR services. The monitoring results are used to analyze the UL and
DL voice quality of these services. If the UL or DL EVQI value of AMR services increases, the
UL or DL voice quality improves. If the UL or DL EVQI value of AMR services decreases, the
UL or DL voice quality deteriorates. This monitoring task can be started only if the traced UE
is processing AMR services.
Issue 02 (2015-05-08)

183
BSC6900 UMTS
LMT User Guide
Context
NOTE
Perform the following operations before stating this monitoring task.

l Run the SET URRCTRLSWITCH command with PROCESSSWITCH5 set to
UL_EVQI_SWITCH-1 or DL_EVQI_SWITCH-1.
l Run the SET UEVQIPARA command with EVQIUplinkPeriod set to an appropriate value. Run the
command SET UMRCTRL command with MrDlBlerPeriod set to an appropriate value. If
UL_EVQI_SWITCH and DL_EVQI_SWITCH are set to 1 simultaneously, the EVQIs are reported at the
interval specified by EVQIUplinkPeriod.
l Run the SET UMRCTRL command with MrRprtCfgSwitch and MrDlBlerPeriod set to
MR_DL_BLER_MEAS_SWITCH_7-1 and D4, respectively. The DL EVQI evaluation depends on the
BLER measurement on the UE side. Therefore, enable the BLER measurement when monitoring the
downlink EVQI. However, the BLER measurement will be temporarily stopped when some tracing or
monitoring tasks, such as UE transmit power tracing or Ec/No tracing under UE tracing and UE transmit
power monitoring under connection performance monitoring, are started. In this case, you can enable the
DL transport channel BLER monitoring under connection performance monitoring to measure the BLER.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to AMR EVQI and set
NOTE
After the monitoring task is started, a real-time monitoring window is displayed. The task name is displayed
in the title bar of the window and the monitoring result is displayed in lists and charts.
In charts, the X-coordinate represents the hour:minute:second. The Y-coordinate represents the maximum
UL and DL data rates of AMR services (unit: kbit/s).
As specified in protocols, The EVQI value ranges from 0 to 5. In the performance monitoring window of
the LMT, the EVQI value is 100 times the actual value (ranging from 0 to 500).
----End
8.4.2 Monitoring Cell Performance

This section describes how to monitor cell performance, such as common measurement values
and number of UEs on common channels. A maximum of six tasks can be simultaneously started
for a monitoring item.
Monitoring Cell P-CPICH TX Power

This section describes how to monitor the PCPICH TX power of a specified cell. By performing
this task, you can observe and determine whether the power is normal.
Context
You can run the LST UPCPICH command to query the automatic adjustment range of the PCPICH TX power. The power is abnormal if it is beyond the range.
Issue 02 (2015-05-08)

184
BSC6900 UMTS
LMT User Guide
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Cell
Performance Monitoring. The Cell Performance Monitoring dialog box is displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to PCPICH TxPower and
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the P-CPICH power
(unit: dBm).
----End
Monitoring Cell UL RTWP

This section describes how to monitor the UL received total wideband power (RTWP) in a
specified cell. By performing this task, you can observe the UL load in real time. The UL RTWP
is measured and reported by the NodeB.
Context
The CAC procedure measures the UL load based on the UL load factor. The UL load factor is
calculated using the following formula: UL load factor = 1 - Cell background noise/UL RTWP).
The cell background noise is a constant and set using the ADD UCELLCAC or MOD
UCELLCAC command. Therefore, the UL RTWP can also be used to measure the relative UL
load of the cell.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to RTWP and set other
NOTE
In charts, the X-coordinate represents hour: minute: second. The Y-coordinate represents the cell UL RTWP
(unit: dBm).
----End
Monitoring DL Carrier TX Power in a Cell

This section describes how to monitor the DL carrier transmit (TX) power of a specified cell.
By performing this task, you can observe the DL load in real time. The DL TX power of a cell
is measured and reported by the NodeB.
Issue 02 (2015-05-08)

185
BSC6900 UMTS
LMT User Guide
Context
The CAC procedure uses the ratio of the DL carrier TX power to the maximum TX power of
the cell to measure the cell DL load. When setting up a cell, you can run ADD
UCELLSETUP to set the maximum TX power. After the cell is set up, you can run MOD
UCELL to modify it.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell DL Carrier TX
Power and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ratio of the DL
carrier TX power to the maximum TX power of the cell (unit: %).
----End
Monitoring Number of UEs in a Cell

This section describes how to monitor the number of UEs on common channels, dedicated
channels, HSDPA channels, and HSUPA channels in a specified cell. By performing this task,
you can learn about UE distribution in cells.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell User Number and
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the number of UEs
in a cell.
----End
Monitoring Node Synchronization

This section describes how to monitor the time difference between RNC Frame Number (RFN)
and NodeB Frame Number (BFN) of a specified cell and the time taken for node synchronization.
Issue 02 (2015-05-08)

186
BSC6900 UMTS
LMT User Guide
By performing this task, you can observe the drift between the RFN and BFN in real time. If the
difference between RFN and BFN varies too rapidly, transmission problems occur between the
BSC6900 and the NodeB.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Node Sync and set other
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the time difference
between RFN and BFN and the time taken by the NodeB to complete node synchronization (unit: ms).
----End
Monitoring UL CAC
This section describes how to monitor the UL call admission control (CAC) procedure of a
specified cell. By performing this task, you can observe the variation in the predicted values and
measured values of the UL load and determine the prediction accuracy of the UL CAC algorithm.
The monitoring results are periodically reported and reported in real time when UEs access the
cell.
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 and CAC
algorithm 2). You can run the MOD UCELLALGOSWITCH command to set the UL CAC
algorithm of a cell and run the LST UCELLALGOSWITCH command to query the UL CAC
algorithm of a cell.
l
CAC algorithm 1 uses the UL load factor to measure the UL load. The UL load factor is
calculated using the following formula: UL load factor = 1 - Cell background noise/UL
RTWP). You can run the command ADD UCELLCAC or MOD UCELLCAC to set the
cell background noise.
CAC algorithm 2 uses the ratio of the current number of UL equivalent UEs to the maximum
number of UL equivalent UEs to measure the cell load. By default, algorithm 2 is used.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to UL CAC Monitor and
Issue 02 (2015-05-08)

187
BSC6900 UMTS
LMT User Guide
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predicted values
and measured values of the load (unit: %).
----End
Monitoring DL CAC
This section describes how to monitor the DL call admission control (CAC) procedure of a
specified cell. By performing this task, you can observe the variation in the predicted values and
measured values of the DL load and determine the prediction accuracy of the DL CAC algorithm.
The monitoring results are periodically reported and reported in real time when UEs access the
cell.
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 and CAC
algorithm 2). You can run the MOD UCELLALGOSWITCH command to set the DL CAC
algorithm of a cell and run the LST UCELLALGOSWITCH command to query the DL CAC
algorithm of a cell.
l
CAC algorithm 1 uses the ratio of the DL carrier TX power to the maximum TX power of
the cell to measure the DL load of the cell. By default, algorithm 1 is used. The maximum
TX power is a constant and set using the ADD UCELLSETUP command.
CAC algorithm 2 uses the ratio of the current number of DL equivalent UEs to the maximum
number of DL equivalent UEs.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to DL CAC Monitor and
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predicted values
and measured values of the load (unit: %).
----End
Monitoring the Number of UL Equivalent UEs

This section describes how to monitor the number of UL equivalent UEs in a specified cell. By
performing this task, you can observe the variation in the number of UL equivalent UEs. The
monitoring results are periodically reported and reported in real time when UEs access the cell.
Issue 02 (2015-05-08)

188
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to UL Total Equivalent
User Number and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predicted and
measured number of UL equivalent UEs.
----End
Monitoring the Number of DL Equivalent UEs

This section describes how to monitor the number of DL equivalent UEs in a specified cell. By
performing this task, you can observe the variation in the number of DL equivalent UEs. The
monitoring results are periodically reported and reported in real time when UEs access the cell.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to DL Total Equivalent
User Number and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predicted and
measured number of DL equivalent UEs.
----End
Monitoring the Cell Code Tree

This section describes how to monitor the DL channel OVSF code tree of a specified cell. By
performing this task, you can observe the code usage in real time.
Procedure
Step 1 On the LMT main page, click Monitor on the LMT main page. The Monitor tab page is
displayed.
Issue 02 (2015-05-08)

189
BSC6900 UMTS
LMT User Guide
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell Code Tree
Monitor and set other parameters according to actual situations. Then, click Submit.
NOTE
A monitoring window is displayed, showing the real-time monitoring results in chart. The task name is indicated
in the title bar of the window.
----End
Monitoring the Minimum Power Required for the HS-DSCH

This section describes how to monitor the minimum power required for the HS-DSCH in a
specified cell. By performing this task, you can observe the ratio of the minimum required power
to the maximum TX power on the HS-DSCH in the cell.
Context
NOTE
When this task is performed, if HSDPA_GBP_MEAS is set to 0 for the cell, the minimum power required
for the HS-DSCH is not reported. HSDPA_GBP_MEAS specifies whether to perform an HSDPA GBR
measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSDPA GBP Meas
Algorithm. If the value is OFF, run the MOD UCELLALGOSWITCH command to set it to 1.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH Min Power
Requirement and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ratio of the
required power to the maximum TX power of the cell (unit: ).
----End
Monitoring the HS-DSCH Bit Rate

This section describes how to monitor the HS-DSCH bit rate of a specified cell. By performing
this task, you can observe the variation in the HS-DSCH transmission rate in real time.
Context
NOTE
When this task is performed, if HSDPA GBP Meas Algorithm is set to 0, the HS-DSCH bit rate of the
cell is not reported. HSDPA GBP Meas Algorithm specifies whether to perform an HSDPA PBR
measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSDPA GBP Meas
Issue 02 (2015-05-08)

190
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH Provided
Bitrate and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:
bit/s).
----End
Monitoring the E-DCH Bit Rate

This section describes how to monitor the bit rate on an enhanced dedicated channel (E-DCH)
for HSUPA services. By performing this task, you can observe the variation in the E-DCH
transmission rate in real time.
Context
NOTE
When this task is performed, if HSUPA GBP Meas Algorithm is set to 0, the E-DCH bit rate of the cell
is not reported. HSUPA GBP Meas Algorithm specifies whether to perform an HSUPA PBR
measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSUPA GBP Meas
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to E-DCH Provided
Bitrate and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:
bit/s).
----End
Monitoring Cell UL Throughput

This section describes how to monitor the UL throughput of a cell. Throughput refers to the
maximum rate that a device can reach without discarding frames.
Issue 02 (2015-05-08)

191
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell UL
Throughput and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the UL throughput
of the cell.
----End
Monitoring Cell DL Throughput

This section describes how to monitor the DL throughput of a cell. Throughput refers to the
maximum rate that a device can reach without discarding frames.
Procedure
Step 1 On the LMT main page, click Monitor on the LMT main page. The Monitor tab page is
displayed.
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell DL
Throughput and set other parameters according to actual situations. Then, click Submit.
NOTE
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the DL throughput
of the cell.
----End
Monitoring the Number of ACK Messages per Second in a Cell

This section describes how to monitor the number of ACK messages that are sent from the AICH
to UEs on the RACH and E-RACH in a specified cell. By performing this task, you can observe
random access times in the cell in real time.
Context
The number of ACK messages is reported to the RNC through common measurement messages
over the Iub interface.
Issue 02 (2015-05-08)

192
BSC6900 UMTS
LMT User Guide
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Number of
acknowledged random access and set other parameters according to actual situations. and then
click Submit.
NOTE
l You can run the ADD UCELLALGOSWITCH and MOD UCELLALGOSWITCH commands to
set whether to report the number of ACK messages per second in a cell. This function is disabled by
default.
l You can run the SET ULDM command to set the report interval and filter window size.
l After the monitoring task is started, a real-time monitoring window is displayed. The task name is
displayed in the title bar of the window and the monitoring result is displayed in lists and charts. In
charts, the X-coordinate represents hour: minute: second. The Y-coordinate represents the number of
ACK messages per second in a cell.
----End
Monitoring Cell Credit

This section describes how to monitor the credit conditions of a local cell, a local cell group,
and a NodeB. By performing this task, the BSC6900 determines whether a UE can access the
network.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell Credit and set other
----End
Result
The following table lists the items shown in the monitoring result.
NOTE
When the CE Overbooking feature is enabled, the RNC performs admission control based on the values of
Adjusted UL Local Cell Group Credit usage (Permillage) and Adjusted UL NodeB Credit used. The
following items are not involved in admission control: UL local cell Credit used, UL local cell group Credit
used, and UL NodeB Credit used.
Issue 02 (2015-05-08)
Monitoring Item
Description
DL local cell total Credit
Downlink credit capability of a local cell. The NodeB

reports the item value to the RNC using a message.

193
BSC6900 UMTS
LMT User Guide
Monitoring Item
Description
UL local cell total Credit
Uplink credit capability of a local cell. The NodeB reports

the item value to the RNC using a message.
DL local cell group total Credit
Downlink credit capability of a local cell group. The NodeB

UL local cell group total Credit
Uplink credit capability of a local cell group. The NodeB

DL NodeB total Credit
Downlink credit capability of a NodeB. The NodeB reports

the item value to the RNC using a message.
UL NodeB total Credit
Uplink credit capability of a NodeB. The NodeB reports the

item value to the RNC using a message.
DL local cell Credit used
Downlink credit used by a local cell, that is, the total

downlink credit used by all UEs in the local cell.
UL local cell Credit used
Uplink credit used by a local cell, that is, the total uplink
credit used by all UEs in the local cell.
DL local cell group Credit used
Downlink credit used by a local cell group, that is, the total
downlink credit used by all UEs in the local cell group.
UL local cell group Credit used
Uplink credit used by a local cell group, that is, the total
uplink credit used by all UEs in the local cell group.
DL NodeB Credit used
Downlink credit used by a NodeB, that is, the total downlink

credit used by all UEs served by the NodeB.
UL NodeB Credit used
Uplink credit used by a NodeB, that is, the total uplink credit
used by all UEs served by the NodeB.
Adjusted UL Local Cell Group

Credit usage (Permillage)
The NodeB reports the actually used uplink credit of a local

cell group per second. The RNC divides this value by the
value of UL local cell group total Credit and converts the
specific value into a permillage.
Adjusted UL NodeB Credit

used
Uplink credit actually used by a NodeB. The NodeB reports

the item value to the RNC per second.
After the monitoring task is started, a real-time monitoring window is displayed. The task name
is displayed in the title bar of the window and the monitoring result is displayed in lists and
charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents
the values of Local Cell Credit and Local Cell Group/NodeB Total Credit of the cell.
Monitoring the FDPCH SYMBOL

This section describes how to monitor the F-DPCH SYMBOL usage, including the F-DPCH
code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.
Issue 02 (2015-05-08)

194
BSC6900 UMTS
LMT User Guide
Context
The F-DPCH carries the Transport Power Control (TPC) information of HSDPA services and
uses the spreading factor SF256.
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to FDPCH SYMBOL
monitoring and set other parameters according to actual situations. Then, click Submit.
NOTE
l In the FDPCH SYMBOL monitoring window, you can view the usage of the SYMBOL corresponding to
the F-DPCH code. The numbers in the grids indicate the timeslot formats.
----End
8.4.3 Monitoring System Resources

This section describes how to monitor the licensed Erlang value and the PS user plane throughput
of the system in real time.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > System
Resource Monitoring. The System Resource Monitoring dialog box is displayed.
Step 3 In the System Resource Monitoring dialog box, set the parameters according to actual
situations, and click Submit.
NOTE
After the monitoring task is started, a real-time monitoring window is displayed. The task name and related
parameters are displayed in the title bar of the window and the monitoring result is displayed in lists and charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the usage of the
license. (Unit: Erl and kbit/s)
----End
8.4.4 Monitoring Iur-p Delay

This section describes how to monitor and specify the delay of an Iur-p link between two external
nodes. By performing this task, you can observe and determine whether the Iurp link delay is
normal in real time.
Issue 02 (2015-05-08)

195
BSC6900 UMTS
LMT User Guide
Context
l
When RNC in Pool Load Sharing is enabled, the Iur-p one-way transmission delay must
be less than or equal to 10 ms.
When RNC in Pool Node Redundancy is enabled, the Iur-p one-way transmission delay
must be less than or equal to 100 ms.
If the delay exceeds either of the preceding values, the Iur-p delay is too large.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Iur-p
Monitoring. The Iur-p Monitoring dialog box is displayed.
Step 3 In the Iur-p Monitoring dialog box, set the parameters according to actual situations, and click
Submit.
NOTE
After the monitoring task is started, a real-time monitoring window is displayed. The task name and related
parameters are displayed in the title bar of the window and the monitoring result is displayed in lists and charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the Iur- delay.
(Unit: 0.125 ms)
----End
Issue 02 (2015-05-08)

196
BSC6900 UMTS
LMT User Guide
9 Device Panel
Device Panel
About This Chapter

This chapter describes how to manage the BSC6900 using the device and emulation panels. You
can use these panels to query information about boards, ports, links, and alarms.
9.1 Device Panel Operations
This section describes device panel operations of the BSC6900, including how to start and use
the device panel and how to query the board status.
9.2 Emulation Panel Operations
This section describes the operations of the BSC6900 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the board status.
Issue 02 (2015-05-08)

197
BSC6900 UMTS
LMT User Guide
9 Device Panel
9.1 Device Panel Operations

This section describes device panel operations of the BSC6900, including how to start and use
the device panel and how to query the board status.
9.1.1 Introduction to the Device Panel

In addition to MML commands, the LMT provides the graphical device panel to help users
maintain devices. The eGBTS does not support this function.
The device panel is automatically refreshed to show board status in real time. You can learn
about the board status based on the board indicator color and active alarm indicators.
On the device panel, you can right-click a board in position and choose any option from the
shortcut menu to perform operations, such as querying the board status.
Figure 9-1 Device Panel
Alarm indicators indicate the board alarm status, and board indicator colors indicate the board
running status. For details, see the descriptions shown in the right side of the device pane.
l
. The drop-down
If the tab page under Device Maintenance is not in full view, click
list is displayed. Select the required item from the drop-down list to view the corresponding
tab page.
You can right-click the peripheral frame of a rack, and choose Refresh Shelf from the
shortcut menu to refresh the rack.
If you select Show logical function under the color descriptions of the board, the logic
functions of boards are displayed on the device panel.
9.1.2 Starting the Device Panel

This section describes how to start the device panel.
Issue 02 (2015-05-08)

198
BSC6900 UMTS
LMT User Guide
9 Device Panel
Procedure
Step 1 On the LMT main page, click Device Maintenance. The Device Maintenance tab page is
displayed. The device panel is displayed in the BSC Device Panel tab page.
----End
9.1.3 Querying the Status of an E1/T1 Port

This section describes how to query the status of an E1/T1 port.
Prerequisites
l
The boards are in position.
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel
(see 9.2.2 Starting the Emulation Panel).
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, and
choose Query E1/T1 Port Status from the shortcut menu. The Query E1/T1 Port Status dialog
box is displayed, showing detailed information about the E1/T1 port.
----End
9.1.4 Querying the CPU/DSP Usage

Prerequisites
l
Context
The OMU and SAU do not support this operation.
You can query the CPU/DSP usage using menus or MML commands.
Procedure
l
Using menus
1.
Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation
panel (see 9.2.2 Starting the Emulation Panel).
2.
Right-click a board in position in the device panel or emulation panel, and choose
CPU/DSP Usage Query from the shortcut menu. The CPU/DSP Usage window is
displayed, showing the real-time CPU/DSP usage.
Using MML commands

1.
Run the DSP CPUUSAGE command to query the CPU/DSP usage.
----End
Issue 02 (2015-05-08)

199
BSC6900 UMTS
LMT User Guide
9 Device Panel
9.1.5 Querying BSC Board Clock Status

This section describes how to query the clock status of a BSC board.
Context
You can query the clock status of a BSC board using menus or MML commands.
Procedure
l
Using menus (1)

1.
Open the device panel (see 9.1.2 Starting the Device Panel) or open the emulation
2.
Query BSC Board Clock Status from the shortcut menu. The Query BSC Board
Clock Status dialog box is displayed.
3.
In the Query BSC Board Clock Status dialog box, set the parameters according to
actual situations, and click Query.
Using menus (2)

1.
On the LMT main page, click Device Maintenance. The Device Maintenance tab
page is displayed.
2.
On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device
> Query BSC Board Clock Status. The Query BSC Board Clock Status dialog
box is displayed.
3.
actual situations, and click Query. The query result is displayed, as shown in Figure
1.
Figure 9-2 Query results of BSC Board Clock Status
Issue 02 (2015-05-08)

200
BSC6900 UMTS
LMT User Guide
9 Device Panel
Using MML commands

1.
Run the DSP CLK command to query the board clock status.
----End
9.1.6 Querying the BSC Board Information

This section describes how to query the status of a BSC board.
Prerequisites
l
Context
You can query the status of a board using menus or MML commands.
Procedure
l
Using menus (1)

1.
Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation
2.
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing the detailed board information.
Using menus (2)

1.
page is displayed.
2.
> Query BSC Board Information. The Query BSC Board Information dialog box
is displayed.
3.
In the Query BSC Board Information dialog box, set the parameters according to
1.
Figure 9-3 Query results of board status
Issue 02 (2015-05-08)

201
BSC6900 UMTS
LMT User Guide
9 Device Panel
Using MML commands

1.
Run the DSP BRD command to query the board information.
----End
9.1.7 Resetting a BSC Board

This section describes how to reset a boardthe CPU on an SPUa/SPUb/SPUc board, and the DSP
on a DPU board. The admin, administrator-level, operator-level, user-level, and authorized
custom-level users can perform this operation.
Prerequisites
l
Context
NOTICE
l If the standby board is not available or is faulty, resetting the board will interrupt the ongoing
services. Therefore, perform this operation with caution.
l Resetting the board may affect the ongoing services. Therefore, you are advised to perform
this operation during off-peak hours, for example, in the early morning.
l
Resetting the Board

Board reset is mandatory during software upgrade and software loading. Board reset will
reload the programs and data files. If the active board resets and the standby board is running
properly, services processed by the active board will be switched over to the standby board,
and then the standby board (the original active board) resets after the switchover. If an
SCUa/SCUb board resets while its standby board is not available or is faulty, the entire
subrack resets.
Resetting the CPU

An SPUa board has four CPUs numbered from 0 to 3. An SPUb/SPUc board has four CPUs
numbered from 0 to 3. Other types of boards have one CPU each. SPUb/SPUc boards
support resetting only CPU O. If you reset any CPU on the SPUa or SPUb/SPUc board,
the board will reset.
Resetting the DSP

DSPs can be reset separately:
A DPUb board has 22 DSPs numbered from 0 to 21.
A DPUe board has 28 DSPs numbered from 0 to 27.
A DEUa board has 48 DSPs numbered from 0 to 47.
Procedure
l
Issue 02 (2015-05-08)
Using menus (1)

202
BSC6900 UMTS
LMT User Guide
9 Device Panel
1.
2.
Reset BSC Board from the shortcut menu.
3.
In the Reset BSC Board dialog box, set the parameters according to actual situations,
and click Reset.
Using menus (2)

1.
page is displayed.
2.
> Reset BSC Board. The Reset BSC Board dialog box is displayed.
3.
and click Reset to reset the board. The operation result is displayed, as shown in
Figure 1.
Figure 9-4 Resetting a board
Using MML commands

1.
Run the RST BRD command to reset a board.
----End
9.1.8 Switching Over BSC Boards

This section describes how to switch over boards. When the active board is faulty, you can switch
all services from the active board to the standby board to ensure the normal system operation.
The admin, administrator-level, operator-level, user-level, and authorized custom-level users
can perform this operation.
Issue 02 (2015-05-08)

203
BSC6900 UMTS
LMT User Guide
9 Device Panel
Prerequisites
l
Before you perform a board switchover, ensure that the standby board is available and
properly running without any critical or major alarms.
Context
NOTICE
l If the board switchover fails, the board configuration data is not lost but services on the board
will be interrupted. Therefore, perform this task with caution.
l Board switchover may affect the ongoing services. Therefore, you are advised to perform
the switchover during off-peak hours, for example, in the early morning.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMU board. The OMUU board supports
switchover initiated by the standby board.
You can switch over a board using menus or MML commands.
Procedure
l
Issue 02 (2015-05-08)
Using menus (1)

1.
2.
Switch BSC Board from the shortcut menu.
3.
In the Switch BSC Board dialog box, set the parameters as required, and then click
Switch to switch over the boards.
Using menus (2)

1.
page is displayed.
2.
> Switch BSC Board. The Switch BSC Board dialog box is displayed.
3.
In the Switch BSC Board dialog box, set the parameters according to actual situations,
and click Switch to switch over the boards. The operation result is displayed, as shown
in Figure 1.

204
BSC6900 UMTS
LMT User Guide
9 Device Panel
Figure 9-5 Switching over boards
Using MML commands

1.
Run the SWP BRD command to switch over boards.
----End
9.1.9 Querying the BSC Board Alarm

This section describes how to query the board alarm.
Prerequisites
l
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see
9.2.2 Starting the Emulation Panel).
Step 2 Right-click a board in position in the device panel or the emulation panel, and choose Query
Board Alarm from the shortcut menu. The alarm information is displayed.
----End
9.2 Emulation Panel Operations

This section describes the operations of the BSC6900 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the board status.
9.2.1 Introduction to the Emulation Panel

The LMT provides the emulation panel for each subrack. The emulation panel has the same
ports as those of the real subrack and helps you learn about the board port status.
Issue 02 (2015-05-08)

205
BSC6900 UMTS
LMT User Guide
9 Device Panel
The emulation panel displays the operating status of the ports on each board and provides rightclick menus, as shown in Figure 9-6.
Figure 9-6 Emulation panel
The emulation panel provides the following functions:

l
Displays the operating status of the device.
Provides right-click menus for users to query the board status and port status.
Uses the mark b to show which board is used by the built-in NE.
Uses the Tip window to show the information about built-in NE that occupies resources
of boards marked with b.
9.2.2 Starting the Emulation Panel

This section describes how to start the emulation panel.
Procedure
displayed.
Issue 02 (2015-05-08)

206
BSC6900 UMTS
LMT User Guide
9 Device Panel
Step 2 Click BSC6900 under Device Navigation Tree. The BSC Device Panel is displayed on the
right pane.
Step 3 Select the corresponding rack and double-click the peripheral of the subrack to view the
emulation panel of a subrack, as shown in Figure 9-7.
Figure 9-7 Subrack peripheral
----End
9.2.3 Querying the Status of an E1/T1 Port

This section describes how to query the status of an E1/T1 port.
Prerequisites
l
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel
(see 9.2.2 Starting the Emulation Panel).
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, and
choose Query E1/T1 Port Status from the shortcut menu. The Query E1/T1 Port Status dialog
box is displayed, showing detailed information about the E1/T1 port.
----End
Issue 02 (2015-05-08)

207
BSC6900 UMTS
LMT User Guide
9 Device Panel
9.2.4 Querying the CPU/DSP Usage

Prerequisites
l
Context
The OMU and SAU do not support this operation.
You can query the CPU/DSP usage using menus or MML commands.
Procedure
l
Using menus
1.
Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation
2.
CPU/DSP Usage Query from the shortcut menu. The CPU/DSP Usage window is
displayed, showing the real-time CPU/DSP usage.
Using MML commands

1.
Run the DSP CPUUSAGE command to query the CPU/DSP usage.
----End
9.2.5 Querying BSC Board Clock Status

This section describes how to query the clock status of a BSC board.
Context
You can query the clock status of a BSC board using menus or MML commands.
Procedure
l
Using menus (1)

1.
Open the device panel (see 9.1.2 Starting the Device Panel) or open the emulation
2.
Query BSC Board Clock Status from the shortcut menu. The Query BSC Board
Clock Status dialog box is displayed.
3.
actual situations, and click Query.
Using menus (2)

1.
Issue 02 (2015-05-08)
page is displayed.
208
BSC6900 UMTS
LMT User Guide
9 Device Panel
2.
> Query BSC Board Clock Status. The Query BSC Board Clock Status dialog
box is displayed.
3.
1.
Figure 9-8 Query results of BSC Board Clock Status
Using MML commands

1.
Run the DSP CLK command to query the board clock status.
----End
9.2.6 Querying the BSC Board Information

This section describes how to query the status of a BSC board.
Prerequisites
l
Context
You can query the status of a board using menus or MML commands.
Procedure
l
Using menus (1)

1.
Issue 02 (2015-05-08)
209
BSC6900 UMTS
LMT User Guide
9 Device Panel
2.
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing the detailed board information.
Using menus (2)

1.
page is displayed.
2.
> Query BSC Board Information. The Query BSC Board Information dialog box
is displayed.
3.
In the Query BSC Board Information dialog box, set the parameters according to
1.
Figure 9-9 Query results of board status
Using MML commands

1.
Run the DSP BRD command to query the board information.
----End
9.2.7 Resetting a BSC Board

This section describes how to reset a boardthe CPU on an SPUa/SPUb/SPUc board, and the DSP
on a DPU board. The admin, administrator-level, operator-level, user-level, and authorized
custom-level users can perform this operation.
Prerequisites
l
Issue 02 (2015-05-08)

210
BSC6900 UMTS
LMT User Guide
9 Device Panel
Context
NOTICE
l If the standby board is not available or is faulty, resetting the board will interrupt the ongoing
services. Therefore, perform this operation with caution.
l Resetting the board may affect the ongoing services. Therefore, you are advised to perform
this operation during off-peak hours, for example, in the early morning.
l
Resetting the Board

Board reset is mandatory during software upgrade and software loading. Board reset will
reload the programs and data files. If the active board resets and the standby board is running
properly, services processed by the active board will be switched over to the standby board,
and then the standby board (the original active board) resets after the switchover. If an
SCUa/SCUb board resets while its standby board is not available or is faulty, the entire
subrack resets.
Resetting the CPU

An SPUa board has four CPUs numbered from 0 to 3. An SPUb/SPUc board has four CPUs
numbered from 0 to 3. Other types of boards have one CPU each. SPUb/SPUc boards
support resetting only CPU O. If you reset any CPU on the SPUa or SPUb/SPUc board,
the board will reset.
Resetting the DSP

DSPs can be reset separately:
A DPUb board has 22 DSPs numbered from 0 to 21.
A DPUe board has 28 DSPs numbered from 0 to 27.
A DEUa board has 48 DSPs numbered from 0 to 47.
Procedure
l
Issue 02 (2015-05-08)
Using menus (1)

1.
2.
Reset BSC Board from the shortcut menu.
3.
and click Reset.
Using menus (2)

1.
page is displayed.
2.
> Reset BSC Board. The Reset BSC Board dialog box is displayed.
3.
and click Reset to reset the board. The operation result is displayed, as shown in
Figure 1.
211
BSC6900 UMTS
LMT User Guide
9 Device Panel
Figure 9-10 Resetting a board
Using MML commands

1.
Run the RST BRD command to reset a board.
----End
9.2.8 Switching Over BSC Boards

This section describes how to switch over boards. When the active board is faulty, you can switch
all services from the active board to the standby board to ensure the normal system operation.
The admin, administrator-level, operator-level, user-level, and authorized custom-level users
can perform this operation.
Prerequisites
l
Before you perform a board switchover, ensure that the standby board is available and
properly running without any critical or major alarms.
Context
NOTICE
l If the board switchover fails, the board configuration data is not lost but services on the board
will be interrupted. Therefore, perform this task with caution.
l Board switchover may affect the ongoing services. Therefore, you are advised to perform
the switchover during off-peak hours, for example, in the early morning.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMU board. The OMUU board supports
switchover initiated by the standby board.
Issue 02 (2015-05-08)

212
BSC6900 UMTS
LMT User Guide
9 Device Panel
You can switch over a board using menus or MML commands.
Procedure
l
Using menus (1)

1.
2.
Switch BSC Board from the shortcut menu.
3.
In the Switch BSC Board dialog box, set the parameters as required, and then click
Switch to switch over the boards.
Using menus (2)

1.
page is displayed.
2.
> Switch BSC Board. The Switch BSC Board dialog box is displayed.
3.
In the Switch BSC Board dialog box, set the parameters according to actual situations,
and click Switch to switch over the boards. The operation result is displayed, as shown
in Figure 1.
Figure 9-11 Switching over boards
Using MML commands

1.
Run the SWP BRD command to switch over boards.
----End
9.2.9 Querying the BSC Board Alarm

This section describes how to query the board alarm.
Issue 02 (2015-05-08)

213
BSC6900 UMTS
LMT User Guide
9 Device Panel
Prerequisites
l
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see
9.2.2 Starting the Emulation Panel).
Step 2 Right-click a board in position in the device panel or the emulation panel, and choose Query
Board Alarm from the shortcut menu. The alarm information is displayed.
----End
9.2.10 Querying the FE/GE Port Status

This section describes how to query the FE/GE port status.
Prerequisites
l
Context
You can query the FE/GE port status using menus or MML commands.
Procedure
l
Using menus
1.
Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
2.
On the emulation panel of the subrack, right-click the FE/GE port to be queried, and
choose Display Ethernet Port Status from the shortcut menu. The Display Ethernet
Port Status window is displayed, showing the FE/GE port status.
Using MML commands

Run the DSP ETHPORT to query the FE/GE port status of interface boards.
Run the DSP GEPORT command to query the GE port status of SCU boards.
----End
9.2.11 Querying the Optical Port Status

This section describes how to query the optical port status. AOUa/AOUc/POUa/POUc/UOIa/
UOIc boards support this function.
Prerequisites
l
Issue 02 (2015-05-08)

214
BSC6900 UMTS
LMT User Guide
9 Device Panel
Context
You can query the optical port status using menus or using MML commands.
Procedure
l
Using menus
1.
2.
On the emulation panel, right-click the optical port to be queried, and choose Query
Optical Port Status and Performance from the shortcut menu. In the Query Optical
Port Status and Performance window, set parameters according to actual situations,
and click Submit to query the optical port status.
Using MML commands

1.
Run the DSP OPT to query the optical port status.
----End
9.2.12 Querying the DPU DSP Status

This section describes how to query the DPU DSP status.
Prerequisites
l
The board has been installed in a specified slot.
Context
You can query the DPU DSP status using menus or MML commands.
Procedure
l
Using menus
1.
2.
On the emulation panel, right-click the required DSP, and choose Query DSP
Status from the shortcut menu. The displayed Query DSP Status window shows the
DSP status.
Using MML commands

1.
Run the DSP DSP command to query the DPU DSP status.
----End
9.2.13 Querying Alarm LED Information

This section describes how to query the detailed information about alarms indicated by an alarm
LED.
Prerequisites
l
Issue 02 (2015-05-08)

215
BSC6900 UMTS
LMT User Guide
9 Device Panel
Procedure
Step 1 Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
Step 2 On the emulation panel, right-click the alarm LED to be queried, and choose Query Alarm
Indicator Info from the shortcut menu. The Query Alarm Indicator Info window is displayed,
showing the detailed information about alarms indicated by the alarm LED.
----End
Issue 02 (2015-05-08)

216
BSC6900 UMTS
LMT User Guide
10 FMA
10
FMA
About This Chapter

This function helps users handle network faults. It includes the following functions: Fault
Diagnosis, Hierarchical Delimitation and Information Collection. The fault diagnosis and
hierarchical delimitation functions analyze faults only within eight hours from the fault
rectification to the current time.
l
The following rights are required to perform the fast fault diagnosis and hierarchical
delimitation.
Administrators
Operators
Users
Customers that have rights to execute the commands in command groups G2 and G9.
The following rights are required to perform the fault information collection.
Administrators
Customers that have rights to execute the commands in command groups G2, G8, and
G9.
The following figure shows the fault handling process using this assistant:
Figure 10-1 Fault handling process
Issue 02 (2015-05-08)

217
BSC6900 UMTS
LMT User Guide
10 FMA
Determine whether services are affected.

Use the fault diagnosis function to identify partial of the faults.
Use the hierarchical delimitation function to analyze faults that cannot be fast identified.
Use the information collection function to collect logs of faults that cannot be identified
by the preceding two methods, and use the offline analysis tool to analyze these faults.
Rectify the faults.
Check that services are recovered.
NOTE
l Information Collection can be simultaneously executed with Fault Diagnosis or Hierarchical

Delimitation. However, Fault Diagnosis and Hierarchical Delimitation cannot be executed
simultaneously. When Information Collection is executed, do not run the COL LOG command.
l Only one Web LMT can perform an online FMA function at a time.
l This function does not support the analysis of an eGBTS.
10.1 Fault Overview

Fault overview provides visualized illustration of operating status and fault information of
RNC network.
10.2 Fault Diagnosis
This function is used to quickly diagnose common network faults, thereby helping users identify
the faulty NE or board. This function can be used when faults occur and persist at a site and site
maintenance personnel cannot directly use the counters, alarms, and logs for fault analysis.
10.3 Hierarchical Delimitation
This function is used to analyze faults. When faults cannot be identified using fault diagnosis,
this function can be used.
10.4 Recovery Confirmation
After service recovery solutions are implemented, onsite O&M engineers can view on the fault
summary page the operating status of the GSM and UMTS networks to check whether a fault
has been rectified. For details, see Fault Overview.
10.5 Information Collection
This function can be used to quickly and accurately collect onsite information, thereby
shortening the event recovery period.
Issue 02 (2015-05-08)

218
BSC6900 UMTS
LMT User Guide
10 FMA
10.1 Fault Overview

Fault overview provides visualized illustration of operating status and fault information of
RNC network.
Context
This function allows field O&M engineers to quickly obtain fault information and start fault
troubleshooting when a network fault occurs.
Procedure
Step 1 On the LMT main page, click FMA. The FMA tab page is displayed.
Step 2 In the Fault Overview window, wait for viewing the KPI trend.
----End
Result
Successful operation
l
The KPI trend chart is displayed in the Fault Overview window.
Table 10-1 Information that O&M engineers can obtain using the fault overview function
Category
Details
UMTS KPI
l Trends in the RRC

l Trends in the CS RAB
l Trends in the PS RAB
l Trends in CS Erlang
l Trends in PS throughput
l Trends in the CS call drops
l Trends in the PS call drops
l Trends in paging
Issue 02 (2015-05-08)

219
BSC6900 UMTS
LMT User Guide
10 FMA
Category
Details
KPI trend chart
l KPI and counter change trend chart that

contains three curves illustrating KPI and
counter changes in the latest eight hours,
in the same hours on the day before, and
in the same hours on the same day last
week, respectively. The X-coordinate
represents the measurement time
(expressed in the form of HH:MM). The
Y-coordinate represents the counter value
in units of each counter or the KPI value
in percentages.
NOTE
Performance measurement has two states in
short measurement periods: ENABLED and
DISABLED. If no counters are measured,
performance measurement is DISABLED.
l When fault diagnosis is used to collect

performance data, performance data
generated during a sampling period is not
available if the current measurement state
is different from that used in the sampling
period.
For example, if the measurement state was
DISABLED last Wednesday and
changed to ENABLED this Monday, only
two curves illustrating KPI and counter
changes in the latest eight hours of this
Wednesday and in the same hours of this
Tuesday are displayed on the trend chart,
with the one for the KPI and counter
changes in the latest eight hours of last
Wednesday missing.
KPI trend value
l Automatically displays the KPI value or

counter value corresponding to a point on
the KPI and counter change trend curves
when you move the mouse pointer to that
point.
l Provides KPI filtering on the right of the
fault summary interface to allow viewing
the change trend of the selected KPI.
Unsuccessful operation
l
Issue 02 (2015-05-08)
A dialog box is displayed with the failure cause.

220
BSC6900 UMTS
LMT User Guide
10 FMA
10.2 Fault Diagnosis

This function is used to quickly diagnose common network faults, thereby helping users identify
the faulty NE or board. This function can be used when faults occur and persist at a site and site
maintenance personnel cannot directly use the counters, alarms, and logs for fault analysis.
Context
According to the diagnosis rules, this function comprehensively analyzes the counters, alarm,
and logs related to the fault and provides analysis reports to users. It helps users perform recovery
operations, thereby shortening the fault recovery period.
l
This function is implemented on the OMU and can be used with tracing and monitoring
functions on the LMT.
This function is stopped when more than 95% of OMU memory is occupied and this
function occupies more than 200 MB OMU memory.
When the OMU CPU usage reaches 100%, the operating systems schedules processes on
the OMU by priority. The initial priority of the fault analysis task using the fault diagnosing
function is set to low. When the CPU usage of this task is lower than the minimum threshold
(10%), increase its priority. When the CPU usage of this task is higher than the minimum
threshold (10%), decrease its priority.
NOTE
When a fault occurs, it is recommended that you use this function to analyze the fault and then run the COL
LOG command to collect logs.
Procedure
Step 1 Optional: Run the SET FMATH command to set the fault diagnosis threshold.
NOTE
When the default fault diagnosis threshold is not used, run the SET FMATH command to set the threshold.
To query the specified fault diagnosis threshold, run the LST FMATH command.
Step 2 On the LMT main page, click FMA. The FMA tab page is displayed.
Step 3 Select the fault scenarios requiring fault management on the Fault Diagnosis tab page.
Step 4 Click Start and wait for the diagnosis report.
NOTE
A folder named by the operation date and time is generated in the bam/version_x/ftp/fma_data/
FaultDiagnosis directory each time this function is implemented, for example, /bam/version_x/ftp/fma_data/
FaultDiagnosis /201501010101. This folder contains four sub-folders which are described in the following
table.
Issue 02 (2015-05-08)
Sub-Folder
Description
alarm_data
Contains the active alarms and cleared alarms for the

last 24 hours.
opt_data
Contains the operation data for the last 24 hours.

221
BSC6900 UMTS
LMT User Guide
10 FMA
Sub-Folder
Description
report
Contains the analysis report generated using the fault

diagnosis function.
stat_data
Contains the performance data for the last 8 hours,

the corresponding 8 hours in the yesterday, and the
corresponding 8 hours 7 days ago.
All historical folders are stored in the bam/version_x/ftp/fma_data/FaultDiagnosis directory. The maximum
size of these folders is 500 MB. If the size exceeds 500 MB, the system deletes the earliest folder. Therefore,
you must save required historical analysis results in a timely manner.
Table 10-2 UMTS fault analysis scenario options

Scenario Options
KPI
Items
RRC Success Rate
The number of RRC

connection setup requests is
0.
The RRC connection setup
success rate is abnormal.
The number of RRC
connection setup requests
decreases significantly.
CS RAB Setup Success Rate
The initial direct

transmission flow control
rate of CS services is
abnormal.
The Iu-CS SCCP setup
The CS security mode
The location update success
rate is abnormal.
The CS service rejection rate
is abnormal.
The CS service redirection
rate in a multi-operator core
network (MOCN) is
abnormal.
The number of successful CS
RAB setups is 0.
Issue 02 (2015-05-08)

222
BSC6900 UMTS
LMT User Guide
10 FMA
Scenario Options
Items
The CS RAB setup success
rate is abnormal.
The number of CS RAB
setup requests decreases
significantly.
CS Service Drop Rate
The CS service drop rate is

abnormal.
PS RAB Setup Success Rate
The initial direct

transmission flow control
rate of PS services is
abnormal.
The Iu-PS SCCP setup
The PS security mode
The RA update success rate is
abnormal.
The PS service rejection rate
is abnormal.
The attach success rate is
abnormal.
The PDP context activation
The PS service redirection
rate in a multi-operator core
network (MOCN) is
abnormal.
The number of successful PS
RAB setups is 0.
The PS RAB setup success
rate is abnormal.
The number of PS RAB setup
requests decreases
significantly.
Issue 02 (2015-05-08)
PS Service Drop Rate
The PS service drop rate is

abnormal.
Paging
The paging success rate is

abnormal.

223
BSC6900 UMTS
LMT User Guide
10 FMA
Scenario Options
Traffic
Items
PS throughput
The PS throughput decreases

significantly.
CS Erlang
The CS Erlang decreases

significantly.
Transmission
Site Break Down
A large number of cells are

unavailable.
Others
Equipment health check
Health check on the interface

boards
Health check on the userplane boards and subsystems
Health check on the controlplane boards and subsystems
Analysis on system
configuration errors
Control-plan Iu-CS and IuPS interface status check
Iur-p interface status check
Flow control of the board
RNC in Pool Load Sharing
The number of RRC

connection setup requests of
the overflow RNC is 0.
The RRC connection setup
success rate of the overflow
RNC is abnormal.
The number of successful CS
RAB setups of the overflow
RNC is 0.
The CS RAB setup success
rate of the overflow RNC is
abnormal.
The CS service drop rate of
the overflow RNC is
abnormal.
The number of successful PS
RAB setups of the overflow
RNC is 0.
Issue 02 (2015-05-08)

224
BSC6900 UMTS
LMT User Guide
10 FMA
Scenario Options
Items
The PS RAB setup success
rate of the overflow RNC is
abnormal.
The PS service drop rate of
the overflow RNC is
abnormal.
The CS Erlang of overflow
RNC decreases significantly.
The PS throughput of
overflow RNC decreases
significantly.
RNC in Pool can be used in different scenarios. The system automatically determines the
application scenario based on the load sharing type, redundancy type, and host status, as shown
in Table 10-3. You can query the load sharing type by running the LST URNCBASIC command
and query the host status by running the DSP UHOSTRNC command.
Table 10-3 RNC in Pool fault analysis scenario options
Issue 02 (2015-05-08)
Scenari
o
Option
s
RNC in Pool Load

Sharing
RNC in Pool
Redundancy

and Redundancy
Load
Sharing
Type=
MASTE
R
Load
Sharing
Type=
OVERF
LOW
Host
Status=
MASTE
R
Host
Status=
BACK
UP
Load
Sharing
Type=
MASTE
R and
Host
Status=
MASTE
R
Load
Sharing
Type=
OVERF
LOW
and
Host
Status=
BACK
UP
Load
Sharing
Type=
OVERF
LOW
and
Host
Status=
MASTE
R
RRC
connecti
on setup
CS
service
setup
CS call
drop

225
BSC6900 UMTS
LMT User Guide
10 FMA
Scenari
o
Option
s
RNC in Pool Load

Sharing
RNC in Pool
Redundancy

and Redundancy
Load
Sharing
Type=
MASTE
R
Load
Sharing
Type=
OVERF
LOW
Host
Status=
MASTE
R
Host
Status=
BACK
UP
Load
Sharing
Type=
MASTE
R and
Host
Status=
MASTE
R
Load
Sharing
Type=
OVERF
LOW
and
Host
Status=
BACK
UP
Load
Sharing
Type=
OVERF
LOW
and
Host
Status=
MASTE
R
PS
service
setup
PS call
drop
CS
Erlang
PS
throughp
ut
Paging
A large
number
of
unavaila
ble cells
Equipme
nt health
check
RNC in
Pool
Load
Sharing
----End
Result
l
A new browser window is displayed with the fault analysis report presented on a web
page.
Issue 02 (2015-05-08)

226
BSC6900 UMTS
LMT User Guide
10 FMA
Table 10-4 Button Functions

Button Name
Description
Save Report
When using the IE browser, click this button to save the

diagnosis report as an html page. On the saved html page,
the log GUI does not provide the query or filtering function.
When using the FireFox browser, there will be no Save
Report button and you can use the save function of the
browser itself to save the diagnosis report.
Download Source
Data
Download the original data of the diagnosis report that is

generated by the NE.
A fault diagnosis report covers the following:

Table 10-5 Contents of the diagnosis report
Issue 02 (2015-05-08)
Item
Description
RNC Basic Information
Containing RNC in Pool networking information and

RNC basic configuration information, such as RNC
ID, RNC name, transmission modes over the Iub, Iur,
Iu-CS, and Iu-PS interfaces, and the load-sharing type
of RNC in Pool

227
BSC6900 UMTS
LMT User Guide
10 FMA
Item
Description
KPI Trend
l Containing KPI and alarm trend figures. RRC

Trend, CS RAB Trend, PS RAB Trend, CS Erlang
Trend, PS Throughput Trend, CS Call Drop Trend,
PS Call Drop Trend, Iu-CS SCCP Trend, Iu-PS
SCCP Trend, Active alarms on the Iu-CS/Iu-PS/
Iur-p interface, RNC Alarm Quantity Trend and
Alarms of last 24 hours are included.
l Containing three curves illustrating KPI and
counter changes that occurred during the eight
hours of today, yesterday, and last week,
respectively. The X-coordinate represents
hour:minute, the Y-coordinate represents the
counter value in the unit of the corresponding
counter or the KPI value in percentages.
l Containing the threshold used in the rules of the
fault management assistant analysis. You can set
the threshold value by running the MML command
SET FMATH.
NOTE
Performance measurement has two states in short
measurement periods: ENABLED and DISABLED. If no
counters are measured, performance measurement is in
DISABLED state.
When the Fault Management Assistant function for rapid
fault diagnosis is enabled to analyze performance statistics,
performance statistics during a sampling period of eight
hours cannot be obtained if the measurement states are
different in a short measurement period during the sampling
period and in the current short period. For example, if the
measurement state was DISABLED during a sampling
period last Wednesday and the measurement state changed
to ENABLED on this Monday, only two curves illustrating
KPI and counter changes that occurred during the same eight
hours of this Tuesday and Wednesday are displayed in the
KPI and counter change trend chart of this Wednesday.
Issue 02 (2015-05-08)

228
BSC6900 UMTS
LMT User Guide
10 FMA
Item
Description
FMA DashBoard
l The dashboard function supports association

analysis and graphical user interface (GUI) display
of KPI trend measured 8 hours before the rapid
fault diagnosis function starts and alarms and key
operation logs generated 24 hours before the rapid
fault diagnosis function starts. This function
displays the KPI trend and associates KPI trend,
alarms, and operation logs by time points so that
the faults are located quickly and services are
restored in a short period of time.
KPI and counter change trend chart: A line is
displayed for each KPI or counter indicating its
change trend in the last 8 hours. The X axis, left
Y axis, and right Y axis indicate the time,
number, and ratio, respectively.
Operation log: The executed MML commands
are displayed from the earliest one. Information
such as the executed MML commands,
operating time, and execution results are
displayed.
Alarm log: Alarms are displayed from the
earliest one. Information such as alarm ID,
alarm report time, and location information are
displayed.
NOTE
When you enter the time to query alarms:
l If the entered time is the same as Alarm raised
time of a single alarm in alarm logs, information
about the alarm will be contained in query
results.
l If the entered time is the same as Alarm raised
time of multiple alarms, information about the
first alarm generated at the time will be
contained in query results.
l If the entered time is different from Alarm
raised time of all alarms in alarm logs,
information about alarms generated at the most
approximate time to the entered time will be
contained in query results.
l In the change trend chart, click a certain time, and

alarms and operation logs generated at this time
will be displayed. Click an alarm or an operation
log, and the KPIs for the corresponding time will
be displayed. Double-click an alarm log to open
the Detail info of alarm log dialog box. In the
displayed dialog box, click Solution to view the
alarm handling suggestion described in the alarm
reference.
Issue 02 (2015-05-08)

229
BSC6900 UMTS
LMT User Guide
10 FMA
Item
Description
l The dashboard function has two startup modes.
In the Scenario Options dialog box, click
Dashboard without selecting the fault
scenario.
In the Scenario Options dialog box, select the
fault scenario and click Start. Compared with
the first startup mode, the fault analysis report
is displayed in addition to the KPI trend and
FMA dashboard.
Fault analysis report
Includes the fault description, diagnose result, and

recommend option in the fault diagnosis scenario
selected by a user. For details about fault diagnosis
scenarios, see Table 1.
Operation logs of last 24

hours
Running the MML command EXP LOG to export the

operation log.
Query historical records of analysis reports.

Click the Query Result button to list the latest 200 alarm logs around the specified
query time on the current page. The latest one alarm log is highlighted.
If the report.xml file in not stored under the bam/version_x/ftp/fma_data/
FaultDiagnosis/report directory, a dialog box indicating that the file is not found is
displayed.
l
10.3 Hierarchical Delimitation

This function is used to analyze faults. When faults cannot be identified using fault diagnosis,
this function can be used.
Context
This function decomposes faults based on standard protocol layers from the KPIs of the faulty
network, until the smallest identifiable objects are obtained. The counters, alarms, status, and
operations of these objects are displayed and identified to provide a fault analysis report for
users.
Procedure
Step 1 On the LMT main page, click FMA. The FMA window is displayed.
Step 2 On the FMA tab page, click Hierarchical Delimitation. The Hierarchical Delimitation tab
page is displayed.
Step 3 Set parameters on the Hierarchical Delimitation tab page.
Issue 02 (2015-05-08)

230
BSC6900 UMTS
LMT User Guide
10 FMA
Step 4 Click Analyze and wait for the fault analysis report.
Table 10-6 GUI parameter description
Parameter
Description
Select the KPI

items
Set this parameter based on the abnormal KPIs by observing the KPI
trend curve.
History Analyze
In the drop-down list, select the time of saving historical analysis reports,
and click Query.
----End
Result
l
A new browser window is displayed with the fault analysis report presented on a web
page.
Table 10-7 Button Functions
Button Name
Description
Save Report
When using the IE browser, click this button to save the

diagnosis report as an html page. On the saved html page,
the log GUI does not provide the query or filtering function.
When using the FireFox browser, there will be no Save
Report button and you can use the save function of the
browser itself to save the diagnosis report.
Download Source
Data
Download the original data of the diagnosis report that is

generated by the NE.
The following table lists information in a fault analysis report.
Issue 02 (2015-05-08)

231
BSC6900 UMTS
LMT User Guide
10 FMA
Table 10-8 Information in a fault analysis report

Item
Description
Fault cells
Cells that are affected by faults.

l Cell ID: ID of the problematic cell
l Failure rate: Proportion of the number of failures in a
problematic cell to that in an RNC related to a specific
counter
l Fault counter: Proportion of the number of failures in a
problematic cell to the number of attempts in this cell
related to a specific counter
l Attempt number: Number of attempts in this cell related
to a specific counter
l NodeB name: Name of the NodeB to which the
problematic cell belongs
l INT board: Interface board where the problematic cell is
configured
l Subsystem: Subsystem where the problematic cell is
configured
Issue 02 (2015-05-08)

232
BSC6900 UMTS
LMT User Guide
10 FMA
Item
Description
Scenario selection
The smallest identifiable objects obtained after faults are

decomposed based on standard protocol layers. The fault
object can be selected on the left, and the corresponding KPI
and alarm is displayed on the right. The fault object is
displayed below.
l The interface between BSC and BSS
Control plane
Wireless layer object, such as NBAP protocol.
Transmission layer object, such as SCTPLINK
and ETHPORT.
Device layer object, such as INT board and
control plane subsystem.
User plane
Wireless layer object, such as Abis protocol.
Transmission layer object, such as ETHPORT.
Device layer object, such as INT board.
l The interface between BSC and CN
Control plane
Wireless layer object, such as RANAP protocol.
Transmission layer object, such as
MTP3LINK,SCTPLINK and ETHPORT.
Device layer object, such as INT board and
control plane subsystem.
User plane
Wireless layer object, such as IUUP and GTPU.
Transmission layer object, such as ETHPORT.
Device layer object, such as INT board.
10.4 Recovery Confirmation

After service recovery solutions are implemented, onsite O&M engineers can view on the fault
summary page the operating status of the GSM and UMTS networks to check whether a fault
has been rectified. For details, see Fault Overview.
10.5 Information Collection

This function can be used to quickly and accurately collect onsite information, thereby
shortening the event recovery period.
Issue 02 (2015-05-08)

233
BSC6900 UMTS
LMT User Guide
10 FMA
Context
When faults occur, the information needs to be collected at the site. However, there are various
types of BSC logs, and the procedure for collecting these logs is complex. In this situation, it is
easy to make mistakes in collecting logs, which leads to repeated collection of logs at the site
and prolongs fault troubleshooting. This function is introduced to simplify the procedure for
collecting logs.
NOTE
This function can be enabled only by the system administrator admin and an administrator-level, operator-level,
or user-level account.
Procedure
Step 1 Information Quick-Collection
1.
On the LMT main page, click FMA. The FMA window is displayed.
2.
On the FMA tab page, click Information Collection. The Information Collection tab
page is displayed.
3.
Set parameters on the Information Quick-Collection tab page. Specify Failure Time and
File Path.
4.
Click Collection to start collecting fault information.

NOTE
After you click Collection, the progress bar may fail to show the progress, and this status lasts for
several minutes.
Table 10-9 GUI parameter description

GUI Parameter
Description
Failure Time
Time when a fault occurs. You can obtain the failure time point
within the counter measurement period (15 minutes) after the
inflection point of the abnormal KPI in the FMA main
interface.
File Path
Save path of log files to be collected
Result
Information about collected log files, such as the file name,

save path, and file size.
Subrack
Number of the subrack.
First Progress
Log file collection progress.
Second Progress
Second batch of log files start to be collected only after the

connection of the first batch completes. Log files are collected
in two batches so that the first logs can be viewed while the
second batch is being collected for fast troubleshooting.
Fault information can be collected in one-click mode. The collection consists of two
batches.
Issue 02 (2015-05-08)

234
BSC6900 UMTS
LMT User Guide
10 FMA
l In the first batch, this function collects operation logs, historical alarm files (12 hours),
BSC data configuration files, and UKPI snapshot generated when the problem occurs.
l In the second batch, this function collects performance counter result file (6 hours),
historical alarm files (7 days), 3G CHR log file, common debug log file (15 min), call
fault log files generated when the problem occurs.
NOTE
The time in the brackets following the collected files indicates the time during which the files are collected
in the specific fault diagnosis scenario. For example, historical alarm files (12 hours) indicates historical
alarm files collected for 12 hours including the time when the fault occurs.
----End
Result
l
Quickly collecting information

After the collection is complete, the collected data can be obtained from the directory
specified by the user. Each batch of data is automatically saved in a sub directory of the
specified directory. For example, the directory specified by the user is E:\DATA, the first
and second batches of collected data will be saved in E:\DATA
\BATCH1_YYYYMMDDHHMMSS and E:\DATA
\BATCH2_YYYYMMDDHHMMSS, respectively. YYYYMMDDHHMMSS indicates
the time when data collection starts. The letters stand for Year, Month, Date, Hour, Minute,
and Second, respectively. In this manner, even if the whole data collection is incomplete,
the data collection progress can be viewed according to the progress bar and the file
collection progress in the Result box, and the collected data can be obtained and
retransmitted. This improves the data collection efficiency.
Collecting customized information

After the collection is complete, the collected data can be obtained from the directory
specified by the user. Data collected each time is automatically saved in a sub directory of
the specified directory. For example, the directory specified by the user is E:\DATA, data
collected each time will be saved in E:\DATA\COLDAT_YYYYMMDDHHMMSS.
YYYYMMDDHHMMSS indicates the time when data collection starts. The letters stand
for Year, Month, Date, Hour, Minute, and Second, respectively.
Issue 02 (2015-05-08)

235
BSC6900 UMTS
LMT User Guide
11 BSC Maintenance
11
BSC Maintenance
About This Chapter

This chapter describes how to maintain BSC equipment, back up and restore data, and implement
fast fault diagnosis.
11.1 Backing Up Data
This section describes how to back up system data on the OMU. The system data includes
configuration data, alarm configuration data, and counter configuration data.
11.2 Restoring Data
This section describes how to restore configuration data on the OMU.
11.3 Batch Configuration
This section describes how to browse and deliver batch configuration script files. Such files can
be generated by the CME or manually generated by operators. Such files can be in the .xml, .ecf,
or .txt format, but only files in the .xml and .ecf formats can be browsed.
Issue 02 (2015-05-08)

236
BSC6900 UMTS
LMT User Guide
11 BSC Maintenance
11.1 Backing Up Data

This section describes how to back up system data on the OMU. The system data includes
configuration data, alarm configuration data, and counter configuration data.
Context
l
When the database system crashes or an upgrade fails, start the tool used for backing up
and restoring system data in the mbsc\bam\common\services\omu_backup_linker
directory. With the latest backup data, you can recover the system.
If you need to recover only OMU configuration data, run the RTR DB command and select
the corresponding data backup file for data recovery.
Using menus
Procedure
1.
page is displayed.
2.
In the Device Navigation Tree, right-click BSC and choose Backup Data from the
short-cut menu. The Backup Data dialog box is displayed with information about
backup files saved in the OMU active workspace installation directory\data
\backup directory.
3.
In the Backup Data dialog box, click Backup to back up system data on the OMU.
NOTE
l A dialog box is displayed by clicking Backup Data, informing the user of whether to encrypt
the file before backing up it. If you select Yes, enter a password.
l The default save path of backup files is OMU active workspace installation directory\data
\backup. If this save path does not exist, it will be created automatically.
l If the name of a backup file is not typed, the file is named BKPDB_#_*.bak automatically.
Here, "#" stands for the detailed version information of the working OMU and "*" stands for
the current system time when the backup is performed. When the number of backup files in the
backup directory exceeds 30, the earliest backup file is automatically deleted.
l The following special characters are forbidden in the file name: \\ / : * ? \" < > | ( ) & $ , %%
+++ = ; blank character
l Backup files cannot be saved in a network path, for example, \\10.161.162.25.
l No space is allowed in the file name or the saving directory. For example, "BK2009 09 08.bak"
is an illegal file name.
4.
In the Backup Data dialog box, select a backup file and click Download to download
the backup file to a local path on the LMT PC.
NOTE
Click Refresh to refresh backup files saved in the OMU active workspace installation directory
\data\backup directory in the Backup Data dialog box.
Using MML commands

1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the BKP DB command to back up system data on the OMU.
----End
Issue 02 (2015-05-08)

237
BSC6900 UMTS
LMT User Guide
11 BSC Maintenance
11.2 Restoring Data

This section describes how to restore configuration data on the OMU.
Context
NOTICE
l Restore data with caution because data restore will overwrite OMU data.
l Versions of data backup files must be the same as the OMU version.
l Alarm information and operation logs are not restored. Their data remains unchanged.
l After restoring OMU data, run the RST BSC command to reset the BSC.
Procedure
l
Using menus
1.
page is displayed.
2.
Under Device Navigation Tree, right-click the BSC node and choose Restore
Data from the short-cut menu. The Restore Data dialog box is displayed with
information about data backup files saved in the OMU active workspace installation
directory\data\backup directory.
3.
Optional: In the displayed Restore Data dialog box, click Upload to upload a backup
file on the LMT PC to the OMU.
NOTE
Click Refresh to refresh backup files saved in the OMU active workspace installation directory
\data\backup directory in the Restore Data dialog box.
4.
In the Restore Data dialog box, click Restore Data to restore configuration data on
the OMU.
NOTE
If an .ecf encrypted file is selected after you click Restore Data, enter a password to restore the
backup file.
Using MML commands

1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the RTR DB command to restore configuration data on the OMU.
----End
Issue 02 (2015-05-08)

238
BSC6900 UMTS
LMT User Guide
11 BSC Maintenance
11.3 Batch Configuration

This section describes how to browse and deliver batch configuration script files. Such files can
be generated by the CME or manually generated by operators. Such files can be in the .xml, .ecf,
or .txt format, but only files in the .xml and .ecf formats can be browsed.
Prerequisites
l
The LMT properly communicates with the BSC.
Batch configuration is based on the functions of the CME script executor and aims at
quickly validating and browsing patch configuration files.
Batch configuration includes the Preactivate, Activate and Browse functions.
Context
Preactivate is used to check whether the data in the configuration scripts is valid and
whether the data conflicts with that on the live network before data activation. This
helps users rectify script problems in advance and prevents activation failures.
Activate includes the check functions of Preactivate. It is also used to validate
configuration scripts on the NE.
You can browse, modify, and save the batch configuration files in the XML Browse
area. The execution results of the batch configuration files are also displayed in this
area.
l
Compared with batch processing, batch configuration can validate configuration scripts in
a shorter time. The validating speed of batch configuration is the same as that of the RUN
BATCHFILE command.
During batch configuration, the BSC is managed independently and the MML commands
from other LMT cannot be executed.
Procedure
displayed.
Step 2 In the Device Navigation Tree, right-click BSC and choose Batch Configuration from the
short-cut menu. The Batch Configuration dialog box is displayed.
Step 3 In the Batch Configuration dialog box, select a batch configuration script file.
NOTE
If an .ecf file is selected, enter a password to import files for batch configuration.
Step 4 Click Activate or Preactivate and wait until the configuration command takes effect on the
BSC.
----End
Issue 02 (2015-05-08)

239
BSC6900 UMTS
LMT User Guide
11 BSC Maintenance
Result
l
Successful operation:
The progress of the activation and pre-activation related commands are displayed in the
progress bar.
The execution results of the batch configuration files are displayed in the message area.
Issue 02 (2015-05-08)
Failed operation: The failure cause is displayed in the message area.

240
BSC6900 UMTS
LMT User Guide
12 FAQ
12
FAQ
About This Chapter

This chapter describes some frequently asked questions (FAQs) and the corresponding solutions.
12.1 Browser-related FAQs
This section describes browser setting-related common problems that hinder the normal use of
the LMT and corresponding handling procedures.
12.2 Java-related FAQs
This section describes Java-related common problems that hinder the normal use of the LMT
and corresponding handling procedures.
12.3 Other FAQs
This section describes common problems, except Java- or browser setting-related problems, that
hinder the normal use of the LMT and corresponding handling procedures.
Issue 02 (2015-05-08)

241
BSC6900 UMTS
LMT User Guide
12 FAQ
12.1 Browser-related FAQs

This section describes browser setting-related common problems that hinder the normal use of
the LMT and corresponding handling procedures.
12.1.1 Slow Responses in the Firefox Browser

Running in the Firefox browser, the LMT gives slow responses. For example, it takes about 30
seconds to maximize the window of a trace task in the Trace tab page. In this case, check whether
the add-on extension Live Margins is installed.
Procedure
Step 1 Start the Firefox, choose Tool > Add-ons. The Add-ons window is displayed.
Step 2 In the Extensions tab page, select Live Margins, and click Disable. The message "Restart
Firefox to complete your changes" is prompted.
Step 3 Click Restart Firefox to validate the changes.
----End
12.1.2 LMT Colors Cannot Be Displayed

When the LMT is started in the IE browser, the colors are not properly displayed. For example,
the colors indicating the status of the boards and alarms are not displayed, or the background
color of the LMT is not differentiated from that of the IE browser. In this case, check the color
settings of the browser.
Procedure
Step 1 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialog
box is displayed.
Step 2 On the General tab page, click Accessibility. The Accessibility dialog box is displayed.
Step 3 In the Formatting area, deselect Ignore colors specified on Web pages, and then click OK.
Step 4 In the Internet Options dialog box, click OK to exit the dialog box.
----End
12.1.3 Verification Code Cannot Be Displayed on the LMT Login

Page
The verification code cannot be displayed when you try to log in to the LMT using an Internet
Explorer (IE) browser in Windows Server 2008 or Windows Vista. When this problem occurs,
check the settings related to the protected mode of the browser.
Context
If the protected mode is enabled for the IE browser in Windows Server 2008 or Windows Vista,
many security restrictions are imposed. For example, JavaScript and Applet cannot be run.
Issue 02 (2015-05-08)

242
BSC6900 UMTS
LMT User Guide
12 FAQ
Therefore, you must disable the protected mode. Otherwise, the LMT web page cannot be
displayed.
Procedure
Step 1 Enter the external virtual IP address of the OMU in the address box of the IE browser. Press
Enter on the keyboard, or click Go next to the address bar to display the login window of the
BSC6900.
Step 2 Check whether "Internet | Protected Mode: Off" is displayed in the bottom right corner of the
window.
l If yes, the task is complete.
l If no, go to Step 3.
Step 3 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialog
box is displayed.
Step 4 On the Security tab page, select Trusted sites in the Select a Web content zone to specify its
security settings area.
Step 5 Clear Enable Protected Mode in the Security level for this zone area. Click Sites. The Trusted
sites dialog box is displayed.
Step 6 Type the external virtual IP address of the OMU in the Add this website to the zone text box,
and then click Add. The external virtual IP address of the OMU is added to the Trusted sites
list.
NOTE
If the U2000 proxy server is used for the login to the LMT, add the IP address of the U2000 to the Trusted
sites list.
Step 7 In the Internet Options dialog box, click OK to exit the dialog box.
NOTE
Restart the browser to validate the modifications.

If IE9 is used, in addition to the previous settings, choose Tools > Compatibility View Settings. In the
displayed Compatibility View Settings dialog box, select Display all websites in Compatibility View.
----End
12.1.4 No Response When Clicking the Menu Bar on the LMT

When you browse the LMT web page, there is no response or a script error dialog box is
displayed. To be specific, when you click the menu bar or buttons or right-click the web page,
there is no response or a dialog box is displayed, indicating a script error, for example,
Permission Denied or Access Denied. In this case, check the proxy settings in the browser.
Context
Do not modify the settings of the browser when you have logged in to the LMT. Before you log
in to the LMT, set the proxy server when necessary.
Issue 02 (2015-05-08)

243
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
l
IE
1.
Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
Options dialog box is displayed.
2.
On the Connections tab page, click LAN Settings. The Local Area Network (LAN)
3.
In the Proxy server area, select Use a proxy server for your LAN (These settings
will not apply to dial-up or VPN connections). Type the IP address and port number
of the proxy server in the corresponding text boxes, and then click Advanced. The
Proxy settings dialog box is displayed.
4.
In the Exceptions area, type the external virtual IP address of the OMU in the text
box, and then click OK. Close the Internet Options dialog box.
Firefox
1.
Choose Tools > Options on the tool bar of the Firefox browser. The Options dialog
box is displayed.
2.
In the Options dialog box, click Advanced. On the Network tab page, click
Settings. The Connection Settings dialog box is displayed.
3.
In the Connection Settings dialog box, select Manual proxy configuration. Type
server address and port number in the HTTP proxy area. Then select Use this proxy
server for all protocols.
4.
In the No Proxy for area, type the OMU external virtual IP address and click OK.
Then close the Options dialog box.
----End
12.1.5 How to Set the Browser Under Citrix Farm Networking

Under Citrix farm networking, when you use the U2000 proxy server to log in to the LMT on a
Citrix client, the LMT may be suspended, the verification code may be unavailable, or
initialization of the MML navigation tree may fail. When these problems occur, check the
browser settings, including the setting of the browser proxy server and the HTTP 1.1 setting. If
either setting is wrong, reset it.
Context
You can set the browser under Citrix farm networking in the following ways:
l
Script setting: An automatic setting script is placed on the domain control server. After a
Citrix user logs in to the server, the script automatically sets the browser.
Manual setting: The browser is set manually.
The Citrix server works in the farm mode. In farm mode, the primary Citrix server and secondary
Citrix servers work in cooperation to achieve load balancing. When a Citrix user logs in to the
Citrix server on a Citrix client, the server in use may vary. The proxy server of the browser
therefore may need to be set again and again. We therefore recommend setting the browser using
the script. With the script, each time the user visits the server, automatic setting of the browser
is performed.
The following procedure uses Internet Explorer (IE) as an example.
Issue 02 (2015-05-08)

244
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
l
Script Setting
1.
Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
setlocal ENABLEDELAYEDEXPANSION
set uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul
\Internet Settings"
reg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nul
reg add %uu% /v ProxyOverride /t REG_SZ /d "<local>" /f >nul
reg add %uu% /v ProxyEnable /t REG_DWORD /d "1" /f >nul
NOTE
The IE-unset.bat script file implements automatic setting of the browser for the domain user.
The domain user can change 10.121.49.213:80 in reg add %uu% /v ProxyServer /t
REG_SZ /d "10.121.49.213:80" /f >nul in the script to the actual IP address of the proxy
server and the actual port number.
2.
Log in to the primary or a secondary domain control server with the user name of
administrator and place the IE-unset.bat file in the C:\WINDOWS\SYSVOL\sysvol
\citrixtest.com\scripts path on the server.
NOTE
The default installation path on the domain control server is C:\WINDOWS\SYSVOL\sysvol

\citrixtest.com\scripts. The path changes if you install the file elsewhere. Here,
citrixtest.com is an example of the domain name. The actual domain name may be different.
3.
For details about how to create a domain user, refer to the Citrix Access Solution User
Guide.
4.
Apply the script to the domain user.

Assume that there is a user named hong01 in the hongtest unit of the citrixtest.com
domain.
a.
Start Active Directory Users and Computer and double-click hongtest in the
left-side pane. In the right-side pane, all users in the hongtest unit are
displayed, as shown in Figure 12-1.
Figure 12-1 Active Directory Users and Computers
Issue 02 (2015-05-08)

245
BSC6900 UMTS
LMT User Guide
12 FAQ
b.
In the right-side pane, right-click hong01. Choose Properties from the shortcut
menu. The hong01 Properties dialog box shown in Figure 12-2 is displayed.
Figure 12-2 Displayed hong01 Properties dialog box
c.
Issue 02 (2015-05-08)
In the hong01 Properties dialog box, click the Profile tab. Type IE-unset.bat
in Logon script, click Apply, and then click OK. Figure 12-3 shows the
window.

246
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-3 Applying the script in the hong01 Properties dialog box
Manual Setting
1.
2.
Issue 02 (2015-05-08)
Check the proxy server setting of the browser.

a.
Choose Tools > Internet Options on the tool bar of the IE. The Internet
b.
On the Connections tab page, click LAN Settings. The Local Area Network
(LAN) Settings dialog box is displayed.
c.
In the Proxy server area, select Use a proxy server for your LAN (These
settings will not apply to dial-up or VPN connections). Set Address of the
proxy server to the IP address of the U2000 and Port to 80.
Check HTTP 1.1 settings of the browser.

a.
Choose Tools > Internet Options on the tool bar of the IE. The Internet
b.
On the Advanced tab page, select Use HTTP 1.1 through proxy connections
under HTTP 1.1 settings, click Apply, and then click OK. Figure 12-4 shows
the window.
247
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-4 HTTP 1.1 settings
----End
12.1.6 Unable to Log In To LMT Because IE Default Security Level

Is Too High
In a Windows Server operating system (including Windows Server 2003 and Windows Server
2008), the IE blocks Web programs of sites that are out of the trusted site list to improve system
security. As a result, you may fail to log in to the LMT.
Context
l
Issue 02 (2015-05-08)
When you try to log in to the LMT by entering the IP address in the IE address bar, the
following web page will be displayed for your wanted page is out of the trusted site list.
Therefore, you may fail to log in to the LMT.
248
BSC6900 UMTS
LMT User Guide
12 FAQ
According to the acceptable IE security level, there are the following two solutions:
When lowering the IE security level on the Windows server is unacceptable, you can
add the LMT site to the trusted sites of the IE by using a configuration startup script.
The system automatically loads the script and configures the IE after a Citrix user logs
in.
When lowering the IE security level on the Windows server is acceptable, you can
remove the Windows component, Internet Explorer Enhanced Security Configuration.
Procedure
l
Setting a configuration startup script

1.
Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul
\Internet Settings\ZoneMap\EscRanges\Trust"
reg add %uu% /v :Range /t REG_SZ /d "10.141.149.193" /f >nul
reg add %uu% /v http /t REG_DWORD /d "2" /f >nul
NOTE
l The IE-unset.bat script file implements automatic setting of IE trusted sites for Citrix domain
users.
l The domain user can change 10.141.149.193 in reg add %uu% /v :Range REG_SZ /d
"10.141.149.193" /f >nul in the script to the IP address of the network element or the peer IP
address of the network elements that need to be visited.
l If the user needs to set multi-network elements and the network elements don't exist in a same
peer IP address, multi-scripts need to be prepared and loaded separately.
l Trust in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ZoneMap\EscRanges\Trust" can be named as you wish.
2.
Load the startup script.

Script setting for a single Windows server
Issue 02 (2015-05-08)

249
BSC6900 UMTS
LMT User Guide
12 FAQ
a.
Log in to the Windows server with the account of administrator. Choose

Start > Run.
b.
Type gpedit.msc in the displayed dialog box. Then click OK. The Group
Policy Object Editor dialog box is displayed.
c.
In the Group Policy Object Editor dialog box shown in Figure 12-5, choose
User Configuration > Windows Settings > Scripts(Logon/Logoff).
Figure 12-5 Script
d.
Issue 02 (2015-05-08)
Double-click Logon. The Logon Properties dialog box is displayed, as

shown in Figure 12-6. Click Show Files and copy the prepared script to the
displayed directory. Then close the dialog box displaying the directory.

250
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-6 Logon Properties
e.
Click Add in the dialog box. The Add a Script dialog box is displayed, as
shown in Figure 12-7.
Figure 12-7 Adding a script
f.
Issue 02 (2015-05-08)
In the Adding a script dialog box, click Browse to select the prepared script
and click OK. Then close the dialog box.

251
BSC6900 UMTS
LMT User Guide
12 FAQ
g.
In the Logon Properties dialog box, click Apply and confirm to load the
prepared script.
h.
Restart the IE to validate the configuration.

NOTE
The users need to log in to the Citrix client to validate the configuration in the single Citrix
network.
Script setting in a Citrix Farm network

a.
Log in to the primary or secondary Citrix domain control server with the
account of administrator. Choose Start > Programs > Administrative
Tools > Active Directory Users and Computer. Select an organization unit
and then right-click Properties. Click the Group Policy tab page in the
displayed dialog box and click New to create a group policy object.
NOTE
l If the organization unit has been set, the users which belong to the organization unit
can all succeed in logging in to the LMT.
l You can rename the group policy object.
b.
Select the created group policy object and click Edit. In the displayed dialog
box shown in Figure 12-8, choose User Configuration > Windows
Settings > Scripts(Logon/Logoff).
Figure 12-8 Script
c.
Issue 02 (2015-05-08)
Double-click Logon. The Logon Properties dialog box is displayed, as

shown in Figure 12-9. Click Show Files and copy the prepared script to the
displayed directory. Then close the dialog box displaying the directory.

252
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-9 Logon
d.
In the Logon Properties dialog box, click Add. The Add a Script dialog
box is displayed, as shown in Figure 12-10.
Figure 12-10 Adding a script
e.
Issue 02 (2015-05-08)
Click Browse to select the prepared script and click OK. Then close the dialog
box.

253
BSC6900 UMTS
LMT User Guide
12 FAQ
f.
l
In the Logon Properties dialog box, click Apply and confirm to load the
prepared script.
Removing Internet Explorer Enhanced Security Configuration

1.
Log in to the Windows server with the account of administrator. Choose Start >
Control Panel > Add or Remove Programs. Select Internet Explorer Enhanced
Security Configuration in the displayed dialog box shown in Figure 12-11.
Figure 12-11 Windows components wizard
2.
Issue 02 (2015-05-08)
In the Windows Components Wizard dialog box, click Details, and deselect For
administrator groups and For all other user groups, as shown in Figure 12-12.

254
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-12 Internet Explorer Enhanced Security Configuration
3.
Click OK and then click Next to remove Internet Explorer Enhanced Security
Configuration. After the removal is complete, click Finish.
4.
Restart the IE to validate the configuration.
----End
12.1.7 Unable to Download or Install the Java or Flash Plug-in and

Two File Manager Windows Displayed Windows IE8 or Any Later
Version Is Used
If users log in to the LMT in IE8 or later versions, an error message displays when they are
downloading or installing a Java or Flash plug-in, or two file manager windows are displayed.
To solve the problem, disable SmartScreen Filter of IE8.
Context
SmartScreen Filter is a new function of IE8 and later versions. It prevents users from visiting
phishing websites and prevents plug-ins from being installed automatically.
SmartScreen Filter causes an error message to be displayed when users are downloading the
Java or Flash plug-in during login to the LMT.
In addition, two file manager windows displays after clicking File Manager.
Issue 02 (2015-05-08)

255
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
Step 1 On the menu bar of the IE browser, choose Safety > SmartScreen Filter > Turn Off
SmartScreen Filter.
Step 2 In the displayed Microsoft SmartScreen Filter dialog box, select Turn off SmartScreen
Filter and click OK to turn off the SmartScreen filter.
----End
12.1.8 The Error "Certificate Invalid" Is Displayed During an

HTTPS Login
The LMT certificate and the certificate used to access the LMT through the U2000 proxy with
dual IP addresses are not granted by any commercial organization. Therefore, they are not trusted
by a browser such as IE by default. In such a scenario, the SSL certificate negotiation is
performed when you visit the LMT in HTTPS mode. If the organization for issuing the current
certificate is not in the default trust list of Microsoft, the Certificate Invalid error is displayed
on the browser. This error does not impair the LMT functions. This section describes how to
correct the error Certificate Invalid displayed during a login to the LMT through HTTPS. To
correct this error, add the root certificate of the certificate in use to the Trusted Root
Certification Authorities list.
Context
l
Using an IE browser
1.
After https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, is entered in the Address bar of the browser, the There is a problem
with this website's security certificate dialog box or Security Alert dialog box is
displayed, as shown in Figure 12-13 and Figure 12-14.
Figure 12-13 Dialog box showing "There is a problem with this website's security
certificate" (IE7 or later versions)
Issue 02 (2015-05-08)

256
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-14 Dialog box showing "Security Alert"(IE6)
2.
Click Continue to this webpage(not recommended) in the There is a problem with

this website's security certificate dialog box or Yes in the Security Alert dialog box
to enter the LMT login page. In the Address bar of the browser, the Certificate
Error message is shown.
3.
After clicking Certificate Error, the Certificate Invalid dialog box is shown.
Using a Firefox browser

1.
Issue 02 (2015-05-08)
After https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, is entered in the Address bar of the browser, the This Connection is
Untrusted dialog box, as shown in Figure 12-15. (The following figure uses
Firefox3.0 as an example. The dialog box varies with browser versions but has the
same information.)

257
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-15 Dialog box showing "This Connection is Untrusted"
Connection Through the U2000

1.
After connecting through the U2000 with both IP addresses, the Certificate Invalid
dialog box is shown.
Procedure
Step 1 Using an IE browser
In the Certificate Invalid dialog box, click View certificates to view the current certificate. If
the certificate displays Issued to: MBSC Certificate and Issued by: Huawei Wireless
Network Product CA, as shown in Figure 12-16, perform the following steps:
Issue 02 (2015-05-08)

258
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-16 MBSC Certificate
1.
On the login interface, click Download CA Certificate. In the displayed dialog box, click
Save. After the download is complete, the ca.zip file is saved.
2.
Decompress the ca.zip file.

NOTE
The ca.zip file is decompressed into two files: ne.cer and oss.cer. The ne.cer file is the root certificate
of Huawei certificate predefined for the LMT and the oss.cer file is the root certificate predefined
for the U2000 proxy server.
Issue 02 (2015-05-08)

259
BSC6900 UMTS
LMT User Guide
12 FAQ
3.
Double-click ne.cer or oss.cer, then a Certificates dialog box is displayed. Click Install
Certificate, then a Certificate Import Wizard dialog box is displayed.
4.
Click Next, choose the Place all certificates in the following store option button, and
click Browse.
A Select Certificate Store dialog box is displayed.
5.
Choose Trusted Root Certification Authorities and click OK.
6.
Click Next, then click Finish and confirm that the ne.cer file has been imported.
7.
Repeat steps 3 to 6 to import the oss.cer file.

In the Certificate Invalid dialog box, click View certificates to view the current certificate. If
the certificate displays Issued to: server and Issued by: hwca, as shown in Figure 12-17,
perform the following steps:
Issue 02 (2015-05-08)

260
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-17 Server Certificate
1.
Issue 02 (2015-05-08)
Click Install Certificate and Next. A dialog box shown in Figure 12-18 is displayed.

261
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-18 Certificate Import Wizard dialog box
2.
In the Certificate Import Wizard dialog box, select Place all certificates in the following
store and click Browse. In the displayed dialog box, select Trusted Root Certification
Authorities and click OK.
3.
In the Certificate Import Wizard dialog box, click Next, Finish, and OK.
4.
Restart the browser so that the reconfiguration can take effect.

In the Certificate Invalid dialog box, click View certificates. If the displayed information about
the current certificate is different from the information in the preceding conditions, import the
root certificate of the current certificate. Perform the following steps:
1.
Obtain the root certificate from the organization issuing the current certificate.
2.
In the menu of the IE browser, choose Tools > Internet Options > Content tab and click
Certificate on this tab page, the Certificate dialog box is displayed.
3.
In the Certificates > Personal tab, and click Import on this tab page, the Certificate
Import Wizard dialog box is displayed.
4.
In the displayed Certificate Import Wizard dialog box, click Next to import the certificate
file. Then click Next, choose Place all certificates in the following store, and then click
Browse. Choose Trusted Root Certification Authorities and click Next to import the
certificate file.
5.
Restart the browser to make the reconfiguration takes effect.
Step 4 Using a Firefox browser

1.
Issue 02 (2015-05-08)
Click Add Exception shown in Figure 12-15. The Add Security Exception dialog box is
displayed, as shown in Figure 12-19.
262
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-19 Add Security Exception dialog box
2.
Click Confirm Security Exception. After the website is added as a security exception, no
security error will be displayed during a login to the LMT using Firefox.
3.
Step 5 Connection Through the U2000

The certification path of the U2000 is shown as Figure 12-20.
Issue 02 (2015-05-08)

263
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-20 Certification Path of the U2000
1.
Choose General > Install Certificate in the Certificate dialog box. And Certificate
Import Wizard dialog box is displayed.
2.
Click Next in the Certificate Import Wizard dialog box and Certificate Store dialog box
is displayed. Then choose Place all Certificates in the following store.
3.
Click Browse, the Select Certificate Store dialog box is displayed. Then choose Trusted
Root Certification Authorities.
4.
Click OK, the Completing the Certificate Import Wizard dialog box is displayed.
5.
Click Finish, the Security Warning dialog box is displayed.
Issue 02 (2015-05-08)

264
BSC6900 UMTS
LMT User Guide
12 FAQ
6.
Choose Yes in the Security Warning dialog box. The import was successful message is
displayed. Then click OK.
7.
----End
12.1.9 The Error 'Mismatched Address' Is Displayed During an

HTTPS Login
A user uses an IP address rather than a domain name to access the LMT. Therefore, the
Mismatched Address error is displayed on the browser during an HTTPS login. This error does
not impair the LMT functions. This section describes how to correct the error "Mismatched
Address" displayed during a login to the LMT through HTTPS. To correct this error, deselect
the Warn about certificate address mismatch* option.
Context
1.
Enter https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, in the Address bar of the browser. The There is a problem with this
website's security certificate or Security Alert dialog box is displayed, as shown in
Figure 12-21 and Figure 12-22.
Figure 12-21 Dialog box showing "There is a problem with this website's security
certificate"(IE7 or later versions)
Issue 02 (2015-05-08)

265
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-22 Dialog box showing "Security Alert"(IE6)
2.
Click Continue to this webpage(not recommended) in the There is a problem with this
website's security certificate dialog box or Yes in the Security Alert dialog box to enter
the LMT login page. In the Address bar of the browser, an Certificate Error
message is shown.
3.
Click Certificate Error. The Mismatched Address error dialog box is displayed.
Procedure
Step 1 Choose Tools > Internet Options on the Menu bar of the browser. Click the Advanced tab in
the displayed dialog box shown in Figure 12-23.
Issue 02 (2015-05-08)

266
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-23 Internet Options dialog box
Step 2 In the Internet Options dialog box, deselect Warn about certificate address mismatch* and
click OK.
NOTE
The reconfiguration takes effect after the browser is restarted.
----End
12.1.10 File Manager Functions are Improperly

When the file manager functions improperly or cannot be used, perform the following
operations:
Procedure
l
Issue 02 (2015-05-08)
If you use HTTPS to log in to the LMT, check that Do not save encrypted pages to
disk is cleared. Selecting this security option causes the file manager to be unavailable.
Therefore, clear this option as follows:
267
BSC6900 UMTS
LMT User Guide
12 FAQ
1.
Open the Internet Options dialog box, click the Advanced tab, and clear Do not save
encrypted pages to disk. Figure 12-24 shows the dialog box.
Figure 12-24 Internet Options dialog box
Issue 02 (2015-05-08)
Check that temporary Java files are saved on the computer. If they are not, the file manager
functions improperly. Perform the following operations:
1.
Open Control Panel in the Windows operating system and double-click Java. The
Java Control Panel dialog box is displayed.
2.
In the displayed Java Control Panel dialog box, click Setting. The Temporary Files
Settings dialog box is displayed. Select Keep temporary files on my computer
shown in Figure 12-25.

268
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-25 Temporary Files Settings dialog box
Check whether the browser agency has been set. If yes, eliminate the setting.
Using IE browser
1.
Choose Tools > Internet Options. The Internet Options dialog box is displayed.
2.
In the displayed Internet Options dialog box, choose Connections > LAN
settings.
3.
In the displayed Local Area Network(LAN) Settings dialog box, deselect Use a
proxy server for your LAN(These settings will not apply to dial-up or VPN
connections) and Bypass proxy server for local addresses.
4.
Click OK. The setting is complete.
Using FireFox browser
1.
Choose Options > Advanced > Network > Settings. The Connection Settings dialog
box is displayed.
2.
In the displayed Connection Settings dialog box, select No proxy.
3.
Click OK. The setting is complete.
If the file manager fails to be opened and the message Fail to parse response is displayed,
check whether the file names or folder names under the /mbsc directory contain invalid
characters. If there are invalid characters, rename the files or folders.
----End
12.1.11 Message 'Class doesn't support Automation' Displayed in

an IE Browser
After clicking Login in an Internet Explorer (IE) browser, you find a blank window displayed
and login unable to continue. In the bottom left corner of the IE browser, a yellow error icon is
Issue 02 (2015-05-08)

269
BSC6900 UMTS
LMT User Guide
12 FAQ
displayed. The icon says "Class doesn't support Automation". To solve the problem, perform
the following steps:
Context
l
This problem occurs because some registration components are missing from the IE
browser. To solve this problem, register the following components again:
msscript.ocx
dispex.dll
vbscript.dll
scrrun.dll
urlmon.dll
Procedure
Step 1 In Windows, choose StartRun and enter RegSvr32 msscript.ocx. To register the other
components again, replace the typed component in italics.
Step 2 After registering all the components again, clear the cache memory of the IE browser.
Step 3 Log in to the LMT again.
----End
12.1.12 Error Message"This user session already exists" Upon Login

to LMT
The interface displays an error message "This user session already exists" upon login to LMT.
Solve the problem by using the method described in the procedure part.
Context
To enhance system security, the client browser uses Cookie to store the session information of
users who have successfully logged in. Due to the session Cookie mechanism, the user
encounters the following problems when using LMT:
l
Problem 1: For the same NE, the user desires to log in to multiple LMTs. After successfully
logging in to the first LMT, the user logs in to the second LMT of the NE, and the interface
displays "this user session already exists". This is because all browser windows opened by
the same user share the same session under the session sharing mechanism of IE8 or IE9
and Firefox enabled by default. As a result, when the user attempts to repeatedly log in to
the LMTs of the same NE, the system determines a repeated login of the same user session.
For the IE6/7 browser in which each browser window uses independent sessions, this
problem does not arise.
Problem 2: The LMT interface displays the error "this user session already exists", while
the user has not carried out the operation described in Problem 1. This is because the
previous session information remains valid due to an abnormal exit from LMT. As a result,
the LMT determines a repeated login attempt when the same user tries to login to the LMT.
This problem arises when the browser automatically recovers from breaking down during
Issue 02 (2015-05-08)

270
BSC6900 UMTS
LMT User Guide
12 FAQ
use of the LMT, or when the pop-up LMT window is blocked by the browser pop-up blocker
enabled.
Procedure
l
For Problem 1, the following method is used:

1.
In the menu bar of the IE browser, click File > New Session, to start a new IE browser
window and log in to the LMT.
NOTE
This method applies only to the IE8 or IE9 browser, not Firefox. Users of the Firefox browser can
log in to only one LMT of a single NE.
For Problem 2, the following method is used:

1.
The IE6/7 browser user needs to close the browser window of the current LMT login
interface, and the IE8/9 and Firefox users need to close all opened browser windows
to invalidate the old sessions.
2.
If the pop-up blocker is enabled for the browser, disable it.
3.
Restart the browser and log in to LMT.
----End
12.1.13 The "Are You Sure You Want to Quit the Page" Dialog Box
Is Displayed
After successful login to the LMT in the IE8 or IE9 browser, the "are you sure you want to quit
the page?" dialog box is displayed when the alarm feature is enabled. Solve the problem by using
the method described in the procedure part.
Procedure
Step 1 Open the Internet Explorer, and then choose Tools > Internet Options from the menu bar. The
Internet Options dialog box is displayed. Click Advanced, and uncheck Automatic Recovery
from Page Layout Error.
Step 2 Restart the browser and log in to LMT again.
----End
12.1.14 Unclear Grids in the Tables in the MML Online Help

The grids in the tables are not clear in MML online help when users log in to the LMT by some
computers. To solve the problem, perform the following steps.
Context
The grids in the tables are not clear in MML online help, as shown in Figure 12-26.
Issue 02 (2015-05-08)

271
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-26 Unclear Grids in the Tables in the MML Online Help
Procedure
Step 1 In the menu of the IE browser, choose Tools > Compatibility View Settings. In the displayed
Compatibility View Settings dialog box, select Display all websites in Compatibility View.
Step 2 Restart the browser and log in to the LMT to check the MML online help. The problem is solved.
----End
12.1.15 The "App Center" Web Page Is Automatically Displayed

When Firefox Is Used to Browse the LMT
When you use Firefox to browse the LMT, if you press F1 or click FTP Tool on the LMT web
page, the App Center web page is automatically displayed. In this case, disable the App
Center on the Add-ons Manager page.
Procedure
Step 1 On the Firefox browser, choose Tools > Add-ons. The Add-ons Manager page is displayed.
Step 2 On the Extensions tab page, locate App Center and click Disable. The App Center will
be disabled if you restart Firebox message is displayed.
Step 3 Click Restart now. The settings will take effect after the restart.
----End
12.1.16 "Permission Denied" or "Access Denied" is Displayed When

IE Is Used to Browse the LMT
When you log in to the LMT through IE, a Permission Denied or Access Denied message is
displayed.
Issue 02 (2015-05-08)

272
BSC6900 UMTS
LMT User Guide
12 FAQ
Prerequisites
The LMT cannot be visited due to errors in IE. An error message is displayed in the status bar,
as shown in Figure 1.
Figure 12-27 Error message in IE
Double-click the error message. A Permission Denied or Access Denied message is displayed.
Context
The causes are as follows:
l
The IE settings are modified when you log in to the LMT through IE, such as the settings
of the proxy. In this case, the access rights to the LMT page files are changed, leading to
access failures.
Automatic configuration in the Local Area Network (LAN) Settings dialog box is
enabled, as shown in Figure 2. If Automatic configuration is enabled, some uniform
resource locators (URLs) will be allocated to other security domains. Different security
domains have different restrictions on access rights. As a result, access failures occur.
Figure 12-28 Automatic configuration enabled
Issue 02 (2015-05-08)

273
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
l
Method 1: Don't modify IE settings when you log in to the LMT through IE.
Method 2: Log out of the LMT when the Permission Denied or Access Denied message
is displayed. Restart IE and log in to the LMT again.
----End
12.1.17 MML Command Failed to Be Executed or No Response to

Tracing Tasks After the Browser Is Upgraded to IE8
After the browser is upgraded from IE6 to IE8, some cache files cannot be removed. As a result,
the system displays a Please check the MML macro configure file! message when an MML
command is executed, or there is no response after tracing tasks are created. To solve this
problem, you need to manually remove cache files and cookies.
Context
l
When MML commands are executed, the system displays a Please check the MML macro
configure file! message, as shown in Figure 12-29.
Figure 12-29 System message "Please check the MML macro configure file!"
There is no response after tracing tasks are created.
Procedure
Step 1 On the menu bar of the IE browser, choose Tool > Internet Options. The Internet Options
dialog box is displayed.
Step 2 Click General > Browsing history and click Delete. The Delete Browsing History dialog box
is displayed.
Step 3 In the Delete Browsing History dialog box, deselect the Preserve Favorites website data.
Step 4 Select Cookies and Temporary Internet files, and then click Delete and close the Delete
Browsing History dialog box.
Step 5 Click the General tab and click Setting in Browsing history. The Temporary Internet Files
and History Settings dialog box is displayed.
Issue 02 (2015-05-08)

274
BSC6900 UMTS
LMT User Guide
12 FAQ
Step 6 Click View files in the Temporary Internet Files and History Settings dialog box, remove all
displayed files, and close the Internet Options dialog box.
----End
12.1.18 Settings on the LMT Failing to Take Effective

After a successful login to the LMT, the previous settings, such as system settings, do not take
effect. To solve this problem, perform the following steps:
Procedure
Step 1 To clear the cache and cookies in the browser, perform the steps shown in the following table.
Browser Type
Handling Procedure
Firefox
1. Open the Firefox browser, and choose

Tools > Clear Private Data from the
menu bar.
2. In the displayed Clear Private Data
dialog box, select the Cache, Cookies,
and Offline Website Datacheck boxes,
and click Clear Private Data Now.
Internet Explorer 7
1. Open the Internet Explorer, and choose

Tools > Internet Options from the menu
bar. The Internet Options dialog box is
displayed.
2. On the General tab page, click Delete.
The Delete Browsing History dialog box
is displayed.
3. To delete the files, click Delete Files and
then click OK in the displayed dialog box.
To delete the cookies, click Delete
Cookies and then click OK in the
displayed dialog box.
4. In the Delete Browsing History dialog
box, click OK and close the Internet
Options dialog box.
Issue 02 (2015-05-08)

275
BSC6900 UMTS
LMT User Guide
12 FAQ
Browser Type
Handling Procedure
Internet Explorer 8 or 9

Tools > Internet Options from the menu
bar. The Internet Options dialog box is
displayed.
The Delete Browsing History dialog box
is displayed.
3. Clear the Preserve Favorites website
data check box and select the Cookies
and Temporary Internet files check
boxes. Then, click Delete and close the
Internet Options dialog box.
----End
12.1.19 LMT Login Window Being Stopped by the Browser

The LMT login window is stopped by the browse, and the login stills fails even though the user
selects Allow popups. To solve the problem, perform the following steps:
Procedure
l
IE browser
1.
Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
2.
On the Privacy tab page, clear Turn on Pop-up Blocker in the Pop-up Blocker pane.
Or, select Turn on Pop-up Blocker, and click Settings to add allowed websites.
3.
Click OK. Close the browser and log in to the LMT again.
FireFox browser
1.
Choose Tool > Options on the tool bar of the FireFox browser. The Options dialog
box is displayed.
2.
On the Content tab page, clear Block popup windows. Or, select Turn on Pop-up
Blocker, and click Exceptions to add allowed websites.
3.
Click OK. Close the browser and log in to the LMT again.
----End
12.1.20 The LMT login page of a host NE or built-in NE fails to be

opened
If a user visits the LMT through a browser, the LMT login page is being loaded for a long period
of time after the user clicks the icon of the host NE or built-in NE. When the preceding problem
occurs, perform the following operations.
Issue 02 (2015-05-08)

276
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
l
To clear the cache and cookies in the browser, perform the steps shown in the following
table.
Browser Type
Handling Procedure
Firefox

menu bar.
3. The operations take effect after the
browser restarts.
Internet Explorer 7

Tools > Internet Options from the
menu bar. The Internet Options dialog
box is displayed.
The Delete Browsing History dialog
box is displayed.
3. To delete the files, click Delete Files
and then click OK in the displayed
dialog box. To delete the cookies, click
Delete Cookies and then click OK in
the displayed dialog box.
Options dialog box.
browser restarts.

box is displayed.
box is displayed.
data check box and select the
Cookies and Temporary Internet
files check boxes. Then, click Delete
and close the Internet Options dialog
box.
browser restarts.
Issue 02 (2015-05-08)

277
BSC6900 UMTS
LMT User Guide
12 FAQ
----End
12.2 Java-related FAQs

This section describes Java-related common problems that hinder the normal use of the LMT
and corresponding handling procedures.
12.2.1 Help for Installing and Using the Java Plug-in

The Java plug-in used by LMT modules, including Batch, Trace, Monitor, and Device
Maintenance, is the Java runtime environment(JRE). You need to install the Java plug-in before
using these modules. You can try the following methods to solve problems about installing or
using Java plug-in.
Context
When a user logs in to the LMT, it checks the version of the installed java plug-in. The following
problems may occur when a user logs in to or use the LMT:
1.
A tooltip with the message "java plug-in is not found" is displayed on the login interface.
2.
A tooltip with the message "please download and install the recommended Java plug-in"
is displayed on the login interface.
3.
LMT modules, including Batch, Trace, Monitor, and Device Maintenance, cannot be used
even after the java plug-in of a recommend version is installed.
For the first problem, perform the following steps to check whether the java plug-in is
successfully installed:
Procedure
1.
On the windows system, click StartRun, enter CMD in the text box, and press the
Enter key. Enter java -version in the run window and press the Enter key to view the
current java plug-in version.
NOTE
You can log in to the LMT even if the Java plug-in is not installed, but LMT modules, including
Batch, Trace, Monitor, and Device Maintenance cannot be used. You can obtain the Java plug-in
from the official website of Java.
2.
If Java plug-ins of multiple versions are installed on the computer, the current active
Java plug-in version can be viewed on the Java control panel. Select Control
PanelJava, and click the Java icon to display the Java control panel. Select the
Java tab page, click View, and click the User tab page in the displayed window to
view and select the Java plug-in version.
NOTE
You may view the Java plug-in version on the Java control panel even when this plug-in has been
uninstalled. Therefore, ensure that the selected Java plug-in version is available.
When Java plug-ins of more than one version are installed on the computer, they may be
incompatible. You are advised to uninstall the java plug-ins of versions that are not required and use
the recommend version. You can install or uninstall Java plug-ins on the Windows control panel.
Issue 02 (2015-05-08)

278
BSC6900 UMTS
LMT User Guide
12 FAQ
3.
If the Java plug-in is successfully installed and you are using the IE browser, you can
ignore the tooltips and continue using the LMT. You can also try to clear the tooltips
using the following methods:
If you are using IE browser, choose ToolsManage Add-ons. In the displayed
window, click Toolbars and Extensions, select All add-ons in the Show combo
box and ensure that the plug-ins Deployment Toolkit and isInstalled Class are
enabled.
If you are using Firefox browser, open the Add-ons window, select the Plugins
tab page, and ensure that the installed Java plug-in is enabled.
Restart the browser, and log in to the LMT again.
NOTE
If the Java plug-in is enabled in the IE browser and the tooltips still exist, choose ToolsInternet
Options , select the Advanced tab page, and click Reset.
The second problem indicates that you have installed a Java plug-in not supported by the
LMT. You can continue using the LMT, but some modules, including Batch, Trace,
Monitor, and Device Maintenance, may become abnormal. You are advised to install the
Java plug-in of a recommended version.
NOTE
The Java plug-in of version 1.7.0.65 is recommended for the SRAN10.0 LMT. The SRAN10.0 LMT also
supports JRE 1.6. If the SRAN7.0, SRAN8.0, SRAN9.0, and SRAN10.0 LMTs are used simultaneously,
JRE 1.6.0.27 is recommended.
When a Java plug-in of a later version has been installed, a java plug-in of an earlier version installed
afterward will not be activated. Tooltips with the message "please download and install the recommended
Java plug-in" will also be displayed on the login interface even if the earlier version is supported by the
LMT. If you need to activate the Java plug-in version of the earlier version, first uninstall the one of the
later version.
As for the third problem, the Java applet is forbidden by default because the security is
enhanced in JRE 1.7. Some tooltips will also be displayed before the applet is executed.
You can try the following methods to solve this problem:
Click the Java icon in the Windows control panel and select the Security tab page in
the Java control panel. Set Security Level to Medium or add the current website to
Exception Site List.
If JRE 1.6 and JRE 1.7 are installed simultaneously on the computer. A dialog box may
be displayed for selecting the appropriate Java plug-in version to execute the applet.
If the Application Blocked by Security Settings dialog box is displayed, or an error
message is displayed on the LMT interface, you can reconfigure Java security level or
Exception Site List.
When other exceptions occur, you can try to delete temporary java files. Open the Java
Control Panel dialog box, select the General tab page, and click Settings. The
Temporary Files Settings dialog box is displayed. Close all running LMT windows
and click Delete Files.
----End
12.2.2 LMT Fails to Function Properly When Error Occurs in Mixed

Code Security Verification of JRE
This section describes how to solve the problem that the LMT does not respond or responds
incorrectly when users perform a function on the LMT.
Issue 02 (2015-05-08)

279
BSC6900 UMTS
LMT User Guide
12 FAQ
Prerequisites
The LMT does not respond or responds incorrectly when users manage progress, process MML
commands in batches, trace messages, or perform monitoring. Viewing the displayed message
on the Java control panel, users find that the following error is reported:
java.lang.SecurityException: class "com.swimap.lmt.util.mml.MMLHandler"'s signer
information does not match signer information of other classes in the same package
at
java.lang.ClassLoader.checkCerts(ClassLoader.java:807) at
java.lang.ClassLoader.preDefineClass(ClassLoader.java:488) .......
Context
Java Runtime Environment (JRE for short) is a compulsory third-party component for the LMT
to run. Mixed code security verification is introduced in version 1.6.0_19 of JRE. With the
function, codes are verified. If codes are found to be untrustable, four operation options displayed
in Figure 12-30 are provided. Changing the default option as described below solves the previous
problem.
Figure 12-30 Java control panel
Issue 02 (2015-05-08)

280
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
Step 1 Open Control Panel in the operating system and double-click JAVA. The Java Control
Panel dialog box is displayed.
Step 2 In the Advanced tab page, choose Security > Mixed code (sandboxed vs. trusted) security
verification and click Disable verification (not recommended).
Step 3 Click OK to save the new setting.
----End
12.2.3 Tracing and Monitoring Functions Cannot Be Used

Tracing and monitoring functions cannot be used after a successful login to the LMT. Solve this
problem by using the following methods.
Context
When a tracing or monitoring function is performed on the LMT, an error message "Error. Click
for details" is displayed and the Application Error dialog box is displayed, as shown in Figure
12-31.
Figure 12-31 Application Error
After clicking Details, detailed error information is displayed. You need to correct the error
based on the error type as follows:
l
Issue 02 (2015-05-08)
If the "java.lang.ClassNotFoundException" error is displayed, perform steps 1 and 2.

281
BSC6900 UMTS
LMT User Guide
12 FAQ
If the "java.lang.NullPointerException" error is displayed, perform steps 2.
If the "netscape.javascript.JSException" error is displayed, perform step 3.
If this problem occurs in Citrix Farm networking, you need to perform related steps on the
Citrix Farm server rather than on the local PC. If you have no permission to log in to the
Citrix Farm server, you cannot directly access Windows Control Panel on the Citrix Farm
server. To access it, right-click the Java icon on Windows system tray on the local PC and
choose Open Control Panel from the short-cut menu. The following figure shows the
window:
If this problem cannot be solved by performing the following steps, uninstall and reinstall
Java.
This problem is caused by a Java defect. For details about this defect, visit http://
bugs.sun.com/bugdatabase/view_bug.do?bug_id=6967414.
Procedure
Step 1 Enable the next-generation Java plug-in again.
1.
Open Control Panel in the Windows operating system and double-click Java. The Java
Control Panel dialog box is displayed. In the Java Control Panel dialog box, click the
Advanced tab, clear Enable the next-generation Java Plug-in (requires browser
restart) under Java Plug-in and click OK.
2.
Select Enable the next-generation Java Plug-in (requires browser restart) by referring
to step a and click OK. Figure 12-32 shows the window.
Issue 02 (2015-05-08)

282
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-32 Enabling the next-generation Java plug-in
3.
Restart the browser to enable the new setting to take effect.
Step 2 Delete temporary Java files.

1.
If this problem persists after performing step 1, delete temporary Java files.
2.
Control Panel dialog box is displayed.
3.
Settings dialog box is displayed. Check the amount of disk space set for storing temporary
files, as shown in Figure 12-33.
Issue 02 (2015-05-08)

283
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-33 Checking the amount of disk space set for storing temporary files
4.
Check the amount of disk space used for storing temporary Java files in the directory where
temporary Java files are saved. The part marked in red frame in Figure 12-34 shows the
directory. This amount is greater than the preset one.
Figure 12-34 Directory where temporary Java files are saved
Issue 02 (2015-05-08)

284
BSC6900 UMTS
LMT User Guide
12 FAQ
5.
Delete folders in this directory manually or by clicking Delete Files shown in the figure
above.
NOTE
Before deleting folders in this directory, close all running LMT clients.
6.
Log in to the LMT again to check whether this problem is solved.
Step 3 Install Windows operating system patch KB960714.

1.
12.3.1 Installing OS Patches
----End
12.2.4 Chinese Characters Displayed in the Tracing and Monitoring

Windows
When users successfully log in to the LMT after an upgrade, they can see Chinese characters in
the tracing and monitoring windows and in the saved files. To solve this problem, perform the
following steps:
Procedure
Step 1 Close all browsers that are opened at the moment.
Step 2 Clear temporary Java files.
1.
If this problem persists after performing step 1, delete temporary Java files.
2.
3.
Settings dialog box is displayed. Check the amount of disk space set for storing temporary
files, as shown in Figure 12-35.
Issue 02 (2015-05-08)

285
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-35 Checking the amount of disk space set for storing temporary files
4.
Check the amount of disk space used for storing temporary Java files in the directory where
temporary Java files are saved. The part marked in red frame in Figure 12-36 shows the
directory. This amount is greater than the preset one.
Figure 12-36 Directory where temporary Java files are saved
Issue 02 (2015-05-08)

286
BSC6900 UMTS
LMT User Guide
12 FAQ
5.
Delete folders in this directory manually or by clicking Delete Files shown in the figure
above.
NOTE
Before deleting folders in this directory, close all running LMT clients.
6.
Log in to the LMT again to check whether this problem is solved.
----End
12.2.5 LMT Fails to Function Properly during the tracing/

monitoring/batch processing
After you log in to the LMT and perform operations on it for a while, batch processing operations
may suddenly fail without any error messages. Alternatively, after a tracing or monitoring task
is created, the task page is not opened. There is no response or any error message. The NE task
list shows that this task has been successfully created. There is no response when you click
saving files in the tracing or monitoring interface. There is no detailed parsing information when
you double-click a tracing or monitoring message. There is no response when you right-click
the window for displaying tracing or monitoring results. There is no response when you rightclick the window for displaying tracing or monitoring results and choose Save All Messages
and Save Selected Messages from the shortcut menu. If you open a new browser and log in to
the LMT again, the task nevertheless can be successfully created. If either of the previous
problems occurs, perform the following operations:
Procedure
Step 1 Open Control Panel in the Windows operating system and double-click Java. The Java
Step 2 In the displayed Java Control Panel dialog box, click the Advanced tab, choose SecurityMixed
code (sandboxed vs. trusted) security verification, and select Disable verification (not
recommended). Figure 12-37 shows the dialog box.
Issue 02 (2015-05-08)

287
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-37 Java Control Panel dialog box
Step 3 Close all opened browsers and delete Java temporary files. To delete Java temporary files,
perform the following operations:
1.
Issue 02 (2015-05-08)
Control Panel dialog box is displayed, as shown in Figure 12-38.

288
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-38 Java Control Panel dialog box
2.
In the Java Control Panel dialog box, click Settings. The Temporary Files Settings
Figure 12-39 Temporary Files Settings dialog box
Issue 02 (2015-05-08)

289
BSC6900 UMTS
LMT User Guide
12 FAQ
3.
In the Temporary Files Settings dialog box, click Delete Files to delete Java temporary
files and click OK.
Step 4 Log in to the LMT again.

----End
12.2.6 Interfaces for Performing Tracing or Monitoring Tasks

Blinking
Interfaces for performing tracing or monitoring tasks blink.
Context
Java Applet in the IE browser is incompatible with HTML elements when they are stacked
together. As a result, interfaces (stacked in the Java Applet) for performing tracing and
monitoring tasks blink. This problem does not affect the function but deteriorates user
experience.
Procedure
l
To avoid this problem, use the following methods:

1.
This problem occurs only on the IE browser. Use the Firefox browser to avoid this
problem.
2.
This problem occurs only on Java later than the version of 1.6.21. Visit
www.oracle.com and download Java SE Runtime Environment 6u21 or an earlier
version to avoid this problem.
----End
12.2.7 Java Installation Fails

During Java installation, the message "Error 25099, Unzipping core files failed." is displayed.
To solve the problem, perform the following steps:
Procedure
Step 1 Delete all files in the Java installation path. The default installation path is C:\Program Files
\Java\jre6\.
Step 2 If step 1 fails because files are locked or in use, restart the system and repeat step 1.
Step 3 Reinstall Java.
----End
12.2.8 Changing Settings for the Next-Generation Java Plug-in Fails

When changing settings for Enable the next-generation Java Plug-in, you are prompted with
a message indicating that the changing fails because one or more browsers are running. As a
matter of fact, no browser is running. The following figure shows the message: To solve the
problem, perform the following steps.
Issue 02 (2015-05-08)

290
BSC6900 UMTS
LMT User Guide
12 FAQ
Context
Changing Settings for Next-Generation Java Plug-in Fails, the error message is shown in
Figure 12-40.
Figure 12-40 Unable to change Java Plug-in settings
This problem is caused by a Java defect. The setting changing fails not because browsers are
running but because the user has no permission to perform the operation.
To change the settings, the user must belong to the Power Users group or have more rights.
Perform the following steps to grant the user more rights.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account authorized for the
administrator's operations. Right-click My computer and choose Manage from the shortcut
menu.
Step 2 In the Computer Management window, choose System toolsLocal Users and
GroupsGroups and double-click Power Users in the right pane of the window, as shown in the
following figure:
Issue 02 (2015-05-08)

291
BSC6900 UMTS
LMT User Guide
12 FAQ
Step 3 In the displayed window, click Add, add the user account to the Power Users group, and click
OK, as shown in the following figures:
Issue 02 (2015-05-08)

292
BSC6900 UMTS
LMT User Guide
12 FAQ
Step 4 Use an administrator-level account to delete the Windows folder in C:\Documents and Settings
\User account\Local Settings\Application Data\Microsoft\Windows shown in the following
figure:
Issue 02 (2015-05-08)

293
BSC6900 UMTS
LMT User Guide
12 FAQ
Step 5 Use the user account to log in the OS again after the previous steps are complete. The user
account now has permission to change settings for Enable the next-generation Java Plug-in.
NOTE
After changing the settings, you can restore the user rights. To restore the user rights, log in to OS using an
administrator-level account again and remove the user account from the Power Users group by referring to steps
1 through 3. The change of the user rights does not affect settings for Enable the next-generation Java Plugin.
----End
12.2.9 How to Handle a Web Page Error or Java Error Displayed on

the LMT
Any of the following occurs during the login to the LMT: the controller version displayed on
the LMT is not the actual version after a controller upgrade or rollback. The error message
Problems with this Web page might prevent it from being displayed properly or
functioning properly . A Java error message is displayed. A JavaScript error message is
displayed on the status bar in the browser. In other words, an exclamation mark is displayed at
the bottom left corner of the status bar.
Context
When the browser cache or Java Applet cache is insufficient, any of the following cases will
result in the inconsistency between the LMT displayed in the browser and the actual LMT.
l
After a controller version upgrade or rollback, the browser fails to obtain the new Javascript,
JAR files, and other files from the LMT server. As a result, the browser uses the preceding
files saved before the controller version upgrade or rollback.
The preceding files are damaged during the use of the LMT.
table.
Procedure
Browser Type
Handling Procedure
Firefox

menu bar.
browser restarts.
Issue 02 (2015-05-08)

294
BSC6900 UMTS
LMT User Guide
12 FAQ
Browser Type
Handling Procedure
Internet Explorer 7

box is displayed.
box is displayed.
Options dialog box.
browser restarts.

box is displayed.
box is displayed.
box.
browser restarts.
To clear the Java Applet, perform the following steps.
CAUTION
Before you clear the Java Applet, exit the LMT. Otherwise, some loaded data will be lost
and unexpected errors will occur.
Issue 02 (2015-05-08)
1.
Choose Start > Control Panel. The Control Panel is displayed.
2.
Double-click Java in the displayed window. The JAVA Control Panel is displayed.

295
BSC6900 UMTS
LMT User Guide
12 FAQ
3.
On the General tab page, click Settings. The Temporary Files Settings dialog box
is displayed.
4.
Click Delete Files. In the displayed Delete Temporary Files dialog box, select the
Applications and Applets and Trace and Log Files check boxes, and click OK.
5.
In Java Control Panel, click OK.
6.
The operations take effect after the browser restarts.
----End
12.2.10 Displaying the Java Security Warning

The Java security warning is displayed during the use of the progress management, batch
processing, tracing, or monitoring function on the LMT. Solve this problem by using the
following methods.
Procedure
Step 1 The error message Are you sure you want to continue this operation? The connection to the
website is unreliable. is displayed in the Security Warning dialog box.
The certificate for system check is a general certificate. It is the same on all Huawei MBSCs
and the certificate issuer is MBSC Certificate. However, the device IP address is allocated by
the network. Therefore, the certificate issuer is inconsistent with the equipment ID. As a result,
the error message is displayed.
This problem is riskless and can be ignored. You can click Continue to proceed with the
subsequent operations. If this problem needs to be resolved, enable the PKI system to allocate
unique certificates to all MBSCs by IP addresses.
Step 2 The error message Do you want to run this application? is displayed in the Security
Warning dialog box.
The Web LMT is a terminal software and does not contain any key information. In addition, the
Jar package execution requires OM identity authentication on the NE. Therefore, this problem
is riskless and can be ignored.
l For Java 1.6, click Always trust content from this publisher. and click Run.
l For Java 1.7, click I accept the risk and want to run this application. and click Show
Options. Then, click Always trust content from this publisher. and click Run.
----End
12.2.11 Failure in Verifying the Verification Code During the Login

to the LMT
The verification code needs to be entered when a user logs in to the LMT. However, the message
"Enter a correct verification code" is displayed even though the user enters the correct
verification code for many times. To solve this problem, perform the following steps:
Procedure
l
Issue 02 (2015-05-08)
table.
296
BSC6900 UMTS
LMT User Guide
12 FAQ
Browser Type
Handling Procedure
Firefox

menu bar.
browser restarts.
Internet Explorer 7

box is displayed.
box is displayed.
Options dialog box.
browser restarts.

box is displayed.
box is displayed.
box.
browser restarts.
Issue 02 (2015-05-08)
To clear the Java Applet, perform the following steps.

297
BSC6900 UMTS
LMT User Guide
12 FAQ
CAUTION
Before you clear the Java Applet, exit the LMT. Otherwise, some loaded data will be lost
and unexpected errors will occur.
1.
Choose Start > Control Panel. The Control Panel is displayed.
2.
Double-click Java in the displayed window. The JAVA Control Panel is displayed.
3.
On the General tab page, click Settings. The Temporary Files Settings dialog box
is displayed.
4.
Click Delete Files. In the displayed Delete Temporary Files dialog box, select the
Applications and Applets and Trace and Log Files check boxes, and click OK.
5.
In Java Control Panel, click OK.
6.
The operations take effect after the browser restarts.
----End
12.2.12 The Application Blocked by Security Settings Dialog Box Is

Displayed When Batch Processing, Tracing, Monitoring, or Device
Maintenance Is Enabled
After the JRE is installed or upgraded, the Application Blocked by Security Settings dialog
box is displayed when the tab page related to batch processing, tracing, monitoring, or device
maintenance is open. Click OK, and the The application cannot be run dialog box is displayed,
indicating that the batch processing, tracing, monitoring, or device maintenance function is
unavailable.
Context
A function is introduced to the JRE later than Java 1.7. 10 to control when and how to run
untrusted Java applications contained in a web page. The untrusted Java application refers to an
application with digital signature applied by an unknown issuer or without a certificate issued
by a trusted certificate authority. The default security level is set to High, indicating that the
untrusted Java applications will be blocked.
Procedure
Step 1 Reconfigure the Java security level or add Exception Site List.
l On the Control Panel page, click Java. In the displayed Java Control Panel dialog box,
click Security. On the displayed Security tab page, select Enable Java content in the
browser, set Security Level to Medium, and then click Apply.
l Alternatively, click Edit Site List on the Security tab page in the Java Control Panel dialog
box to add the sites accessing the LMT to the site list. If this method is used, the Java security
level does not need to be reconfigured. For the sites added in the site list, mark whether the
access to the LMT through HTTPS or HTTP. For example, https://10.20.198.33 or http://
10.30.192.60.
Step 2 Specify Enable the next-generation Java Plug-in(requires browser restart).
Issue 02 (2015-05-08)

298
BSC6900 UMTS
LMT User Guide
12 FAQ
1.
In the Java Control Panel dialog box, click Advanced. On the displayed Advanced tab
page, select Java Plug-in, clear Enable the next-generation Java Plug-in(requires
browser restart), and then click OK.
2.
Select Enable the next-generation Java Plug-in(requires browser restart) according to

operations in step 2.a, and click OK.
3.
Restart the browser to make the settings take effect.
Step 3 Delete temporary Java files.

1.
In the Java Control Panel dialog box, click General. On the displayed General tab page,
click Settings. The Temporary Files Settings dialog box is displayed.
2.
Close all running LMT windows and click Delete Files.
Step 4 Log in to the LMT again. When enabling any of the batch processing, tracing, monitoring, and
device maintenance functions, select I accept the risk and want run this application on the
displayed do you want run this application? dialog box and click Run. If the Do you want to
continue? dialog box is displayed, click Continue.
----End
12.2.13 What Do I Do If A Message Your Java version is out of date

Is Displayed?
If you are prompted with the message that Your Java version is out of date when logging in to
the WebLMT, follow instructions provided in this session.
Context
The JRE installed on the computer is not of the latest version and an upgrade to the latest version
is recommended by Java. To continue to use the WebLMT and update the JRE later, it is good
practice to perform the procedure described below.
Procedure
Step 1 In the Your Java version is out of date dialog box, select the Do not ask again until the next
update is available check box.
Step 2 Click Later.
----End
12.3 Other FAQs

This section describes common problems, except Java- or browser setting-related problems, that
hinder the normal use of the LMT and corresponding handling procedures.
12.3.1 Installing OS Patches

In a Microsoft Windows operating system (OS), you need to install patch KB944338, KB938397
or KB960714 if the OS and IE are in a certain version.
Issue 02 (2015-05-08)

299
BSC6900 UMTS
LMT User Guide
12 FAQ
Context
l
Patch KB960714 solves the problem of Java console output error. Therefore, the Java
application can be loaded successfully on the LMT.
Patch KB944338 improves the performance of the LMT by increasing the speed of visiting
a web page. Therefore, the LMT running rate can be increased.
If Windows 7 operating system is used, Windows patches do not need to be installed.
Procedure
Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or Remove
Programs icon.
Step 2 In the displayed Add or Remove Programs window, select Show updates. Check whether
patches KB944338, KB938397 and KB960714 are present in the list of Currently installed
programs.
l If the patches are present, the task is complete.
l If the patches are not present, go to Step 3.
Step 3 Determine whether a Windows patch needs to be installed according to the OS version and IE
version.
l Patch KB960714 needs to be installed when the OS version and IE version are combined in
the following ways:
OS Version
IE Version
Windows 2000 SP4
IE5/IE6 SP1
Windows XP SP3
IE6/IE7
Windows Server 2003 SP1/SP2
IE6/IE7
Windows Vista
IE7
l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4 or
Windows Server 2003 SP1/SP2.
l When the Windows 2003 operating system is used, the service pack KB938397 needs to be
installed. This service pack ensures that the Windows 2003 operating system supports the
SHA256 algorithm. After the service pack is installed, the LMT can work properly.
l When the Windows 2008 OS and Internet Explorer 7 or later are used, the OS patch does
not need to be installed.
NOTE
l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.

l To download patch KB938397, go to http://support.microsoft.com/?kbid=938397.
l Download a suitable patch according to the OS version and IE version.
----End
Issue 02 (2015-05-08)

300
BSC6900 UMTS
LMT User Guide
12 FAQ
12.3.2 Changing the Computer Time During the LMT Use

Prohibited
Changing the computer time during the LMT use is prohibited. Changing the computer time
causes some functions of the LMT to stop functioning normally. For example, the OMU time
fails to refresh normally; tracing data and monitoring data fail to refresh normally; progress
management fails to refresh normally.
12.3.3 Corrupted Characters Appearing When the csv File Is

Opened in UTF-8 Coding
If a csv file in UTF-8 coding is saved on the LMT with non-English characters in it and the csv
file is opened in the Excel format by using the regular method, all the non-English characters
are displayed as corrupted characters. In this case, open the csv file by using the import method
in Excel.
Procedure
l
If the Excel version is earlier than Office 2007, perform the following operations:
1.
On the menu bar of Excel, choose Data > Import External Data > Import Data.
Then the Select Data Source dialog box is displayed. Figure 12-41 shows the dialog
box.
Figure 12-41 Operation interface for importing data in Excel
2.
Issue 02 (2015-05-08)
In the Select Data Source dialog box, select the csv file in UTF-8 coding. Then the
Text Import Wizard - Step 1 of 3 dialog box is displayed. Figure 12-42 shows the
dialog box. Select 65001:Unicode(UTF-8) in File origin.

301
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-42 Text import wizard-step 1
3.
Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed.
Figure 12-43 shows the dialog box. Select Comma under Delimiters.
4.
Issue 02 (2015-05-08)
Click Finish. Then the Import Data dialog box is displayed. Figure 12-44 shows the
dialog box.
302
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-44 Interface after data importation is finished
5.
l
Click OK. Then the file is displayed properly.
If the Excel version is Office 2007 or later, perform the following operations:
1.
On the menu bar of Excel, choose Data > From Text. Then the Import Text File
dialog box is displayed. Figure 12-41 shows the dialog box.
Figure 12-45 Operation interface for importing data in Excel
2.
In the Import Text File dialog box, select the csv file in UTF-8 coding. Then the
Text Import Wizard - Step 1 of 3 dialog box is displayed. Figure 12-42 shows the
dialog box. Select 936:Chinese Simplified(GB2312) in File origin.
3.
Issue 02 (2015-05-08)
Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed.
Figure 12-43 shows the dialog box. Select Comma under Delimiters.
303
BSC6900 UMTS
LMT User Guide
12 FAQ
4.
Click Finish. Then the Import Data dialog box is displayed. Figure 12-44 shows the
dialog box.
Figure 12-48 Interface after data importation is finished
5.
Click OK. Then the file is displayed properly.
----End
12.3.4 Maximum Number of LMT Clients That Can Be Started on

One PC Simultaneously
You can have multiple LMT clients started on one PC. Starting too many LMT clients
simultaneously, however, affects maintenance performance. As being limited by the PC memory
and maximum number of dialog boxes that can be opened on the IE browser, a PC does not
support 32 LMT clients to be started simultaneously.
In normal maintenance, the maximum number of LMT clients that can be simultaneously started
on one PC is as follows:
Issue 02 (2015-05-08)

304
BSC6900 UMTS
LMT User Guide
12 FAQ
One PC with 2 GB memory or larger supports 16 LMT clients to be started simultaneously.
One PC with 1 GB memory supports 8 LMT clients to be started simultaneously.
One PC with 512 MB memory supports 4 LMT clients to be started simultaneously.
12.3.5 Any Further Operation Performed When Some LMT Web

Pages Fail to Update Causes the Web Pages to Turn Blank
Some LMT Web pages fail to update when batch processing, tracing, or monitoring is in use.
Any further operation causes the Web pages to turn blank. If you restart the function, the Web
page returns to normal. To prevent this problem, perform the following operations to add an
environment variable.
Procedure
Step 1 On the LMT PC, select My Computer and right-click Properties from the shortcut menu. The
System Properties dialog box is displayed.
Step 2 In the System Properties dialog box, click the Advanced tab and click Environment
Variables. The Environment Variables dialog box is displayed.
Step 3 In the Environment Variables dialog box, click New. The New User Variable dialog box is
displayed.
Step 4 In the New User Variable dialog box, set Variable name to
JPI_PLUGIN2_NO_HEARTBEAT and Variable value to 1. Then click OK.
Step 5 In the Environment Variables dialog box, click OK.
Step 6 In the System Properties dialog box, click OK to finish adding the environment variable.
----End
12.3.6 Configuring the HTTPS Login Mode

This section describes how to configure the HTTPS login mode and a security certificate. Users
can log in to the LMT through either HTTP or HTTPS. The login mode is configurable.
Prerequisites
l
You have logged in to the LMT using a Built-In Administrator Account or External
User Accounts.
Context
HTTPS is Hypertext Transfer Protocol Secure. Based on HTTP, HTTPS introduces SSL (or
TLS) to ensure transmission security. To put it simply, HTTPS is a combination of HTTP and
SSL. To enter the HTTPS login mode, enter https://Website to be visited + Port No in the Address
bar of the browser. The default port No. is 443. Use the default port No. to enter the LMT login
page.
Issue 02 (2015-05-08)

305
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
Step 1 Change the login mode
1.
Log in to the LMT through HTTPS.
2.
Run the MML command SET WEBLOGINPOLICY. In this step, set POLICY to
HTTPS.
Step 2 Run the MML command RST OMUMODULE to restart the LMT so that the change take effect.
In this step, set TG to ACTIVE and MNAME to weblmt.
NOTICE
1. Running this command disconnects all online users from the LMT.
2. Normally, the restart is complete within 5 seconds. After the restart is complete, the change
take effect when users log in to the LMT again.
----End
12.3.7 Unable to Save Tracking and Monitoring Data

When a tracking or monitoring task (such as the UE tracking task) is running on the LMT, it is
possible that the vast amounts of tracking or monitoring data cannot be saved even with sufficient
hard disk space. Solve the problem by using the method described in the procedure part.
Context
This problem arises when the operating system enables the system recovery function that
monitors changes of the files on the hard disk and consumes some hard disk space. With
insufficient hard disk space, the system displays "Insufficient hard disk space", and if a tracking
or monitoring task is running on the LMT, it is likely that the tracking or monitoring data cannot
be saved.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account authorized for the
administrator's operations. Right-click My computer and choose Properties.
Step 2 In the "System Properties" window, click System Recovery, select Disable System Recovery
on All Drivers, and click Submit, as shown in Figure 12-49.
Issue 02 (2015-05-08)

306
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-49 System properties dialog box
----End
12.3.8 BTS Nodes Cannot Be Displayed Under Device Navigation

Tree
After a successful login to the LMT, you may find that BTS nodes cannot be displayed under
Device Navigation Tree. After upgrading the browser, you find that the nodes can be displayed
normally. This problem occurs because data under Device Navigation Tree on the LMT is
compressed whereas Internet Explorer 6 SP2 does not support compression of chunked data.
Solve this problem by using either of the following methods.
Context
BTS nodes cannot be displayed under Device Navigation Tree, as shown in Figure 12-50.
Issue 02 (2015-05-08)

307
BSC6900 UMTS
LMT User Guide
12 FAQ
Figure 12-50 BTS nodes cannot be displayed
Procedure
l
Method 1: For the operating system Windows XP Service Pack 2 or 3, install the KB982381
patch. To download this patch, visit http://www.microsoft.com/downloads.
Method 2: Upgrade the browser. You are advised to upgrade it to Internet Explorer 8.
----End
12.3.9 Alarm/Event Function Becomes Unavailable

When starting or using the Alarm/Event function after a successful login to the LMT, the page
may become white with an exclamation mark displayed in the center. The exclamation mark is
circled in gray, as shown in the following figure: Solve this problem by using the following
methods.
Context
The page of alarm/event function become white, as shown in Figure 12-51.
Figure 12-51 Alarm/Event Function
Issue 02 (2015-05-08)

308
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
l
Method 1:Disable the alarm or event module. If the problem persists after you reopens the
page, use method 2 to resolve the problem.
Method 2: Check that the flash player is of a version supported by the LMT, Flash Player
11.1.102 or later. Flash Player 11.1.102 is available on the LMT login web page. For later
versions, visit http://adobe.com. If installing the flash player fails and a message saying
that the version is not the latest one is displayed, perform the following steps:
1.
Download and install the flash player of the latest version.
2.
Choose StartRun and enter regedit to open Registry Editor. Navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer
\SafeVersions, delete the item with the DWORD value of 10.0, and reinstall the flash
player.
Method 3: Check that the browser type is supported by the LMT, Internet Explorer or
Firefox. For details about the supported browser versions, see 2.1 Configuration
Requirements of the LMT PC.
----End
12.3.10 LMT Login Web Page Cannot Be Opened with the PC OMU
Installed
With the PC OMU installed in Windows 7, the LMT login web page cannot be opened. In
addition, the LMT process cannot be found in the task manager.
Context
Port 80 is the default port for LMT login. This problem occurs because port 80 is occupied by
a default HTTP service in Windows 7.
To confirm the cause, run the netstat naop tcp command at the Windows 7 command prompt
to check whether port 80 is occupied. If it is occupied by a process with the PID of 4, as shown
in the following figure, the problem occurs due to the cause.
This process is a system process and therefore cannot be closed directly. To close it, perform
the following steps:
Issue 02 (2015-05-08)

309
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
Step 1 In Windows, choose StartRun and enter regedit to open Registry Editor.
Step 2 Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP.
Step 3 Change the DWORD value of Start to 0.
Step 4 Restart the PC and log in to the LMT again.
----End
12.3.11 Slow Response During an LMT Login

The LMT responses slowly when the users are trying to log in to the LMT. To solve the problem,
perform the following steps:
Procedure
Step 1 In the Windows 2003 and Windows XP operating system (OS), choose Start > Control
Panel, and then click Add/Remove Programs, the Windows Components Wizard dialog box
is displayed.
Step 2 In the Windows Components Wizard dialog box, deselect Upload Root Certificates, as shown
in the following figure. Then click Next to complete the modification.
----End
Issue 02 (2015-05-08)

310
BSC6900 UMTS
LMT User Guide
12 FAQ
12.3.12 Batch Execution of MML Commands Fails Because Some

MML Commands Contain Invisible Carriage Returns or Line Feeds
After line feeds (LF) are deleted from MML command scripts copied to Batch, command
execution fails.
Context
Copy the MML commands failing to be executed to an UltraEdit file. It is found that these MML
commands are displayed in two lines. In UltraEdit, click
to view these MML commands
in the binary format. A redundant carriage return (CR) 0x0D stays at the LF location of the MML
command each. See Figure 12-52.
Figure 12-52 Viewing an MML command in the binary format using UltraEdit
In the Windows operating system (OS), the CR 0x0D and LF 0x0A must be used pairwise. The
unpaired CRs or LFs cannot be deleted. As a result, the MML commands fail to be executed.
Procedure
Step 1 Copy the MML commands failing to the executed to an UltraEdit or notepad file and delete all
LFs and CRs. Then, copy these commands back to Batch and execute them again.
----End
12.3.13 How to Handle Shortcut Key Invalidation

Shortcut keys are defined on the LMT. When logging in to the LMT through a web page, you
may fail to use the corresponding function by pressing a shortcut key. In this case, the shortcut
key becomes invalid. For example, you cannot stop pinging by pressing Ctrl+Q in the MML
Command window. This is because the same shortcut key is preferentially used by another
running program on the PC, which leads to a shortcut key conflict.
Procedure
Step 1 Check all running programs on the PC. Find the program using the same shortcut key settings
as the LMT.
Issue 02 (2015-05-08)

311
BSC6900 UMTS
LMT User Guide
12 FAQ
Step 2 Modify the program shortcut key settings which are the same as those on the LMT or stop the
program when you use the LMT.
----End
12.3.14 Tracing File Not Being Uploaded to the Specified Directory

If you close the UE Trace or IOS Trace dialog box during the UE tracing or IOS tracing, the
tracing result file being generated cannot be uploaded to the specified directory. This problem
occurs in the following scenario: In the UE Trace or IOS Trace dialog box, Debug is selected
and Trace Mode is set to Report File. To solve the problem, perform the steps in Procedure.
Context
A tracing task may generate multiple tracing files, which depends on the traced messages.
If you close the trace dialog box, the last tracing file cannot be uploaded to the specified directory.
The last tracing file refers to the one being generated. The generated tracing files can be uploaded.
Procedure
Step 1 In the Trace Navigation Tree, double-click Manage Trace Task. The Manage Trace Task
tab page is displayed.
Step 2 Query the UE tracing or IOS tracing task being performed, select a task, and click Delete. The
preceding settings enable the tracing result file being generated to be uploaded to the specified
directory.
----End
12.3.15 Error Dialog Box Displayed When Online Help Is Opened

When Online Help is opened on the LMT, a dialog box is displayed with the following
information: An error on this web page disables the proper running of the web page. As a result,
Online Help cannot be used. To solve the problem, perform the following steps:
Procedure
Step 1 1. Uninstall the Google chrome frame plug-in.
Step 2 2. Clear the IE browser cache.
Step 3 3. Log in to the LMT again
----End
12.3.16 Garbled Characters Displayed in the Chinese Names of Files

in the File Manager and These Files Failing to Be Removed
When users view the files on the OMU using the LMT file manager, they can see garbled
characters in the Chinese names of the files, and the files cannot be removed. To solve this
problem, perform the following steps:
Issue 02 (2015-05-08)

312
BSC6900 UMTS
LMT User Guide
12 FAQ
Procedure
Step 1 1. Use a third-party tool, such as the FileZilla, to upload a file to the OMU. Before uploading
this file, specify the file name using the gb2312 coding and save the file. In this way, the file
manager can manage this file.
Set the FileZilla as follows: Choose FileSite Manager. A Site Management dialog box is
displayed. Select the corresponding site from My Sites. On the Charset tab page, select Use
custom charset, set Encoding to gb2312, and click Connect. The encoding is modified. Then,
upload the file.
Step 2 On the LMT, click System Settings. Select Chinese in Language, and click OK. Open the file
manager to view the file, and you can see a normally displayed file name. The file can be removed
now.
----End
Issue 02 (2015-05-08)

313

Bsc6900 Umts LMT User Guide (v900r017c10 - 02) (PDF) - en

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Bsc6900 Umts LMT User Guide (v900r017c10 - 02) (PDF) - en

Hochgeladen von

Copyright:

Verfügbare Formate

BSC6900 UMTS

LMT User Guide

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

Huawei Proprietary and Confidential

About This Document

The keywords of a command line are in boldface.

Command arguments are in italics.

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Huawei Proprietary and Confidential

About This Document

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

3 Operation Rights Management................................................................................................35

Huawei Proprietary and Confidential

3.3.2 Querying Login Password Policies............................................................................................................................42

4 Running MML Commands........................................................................................................45

Huawei Proprietary and Confidential

5.5 Monitoring Alarms.......................................................................................................................................................70

Huawei Proprietary and Confidential

7.4 UMTS Services...........................................................................................................................................................109

Huawei Proprietary and Confidential

9.1.7 Resetting a BSC Board............................................................................................................................................202

Huawei Proprietary and Confidential

12.1.11 Message 'Class doesn't support Automation' Displayed in an IE Browser.........................................................269

Huawei Proprietary and Confidential

12.3.14 Tracing File Not Being Uploaded to the Specified Directory.............................................................................312

Huawei Proprietary and Confidential

Added descriptions of the Working directory setting on the FTP

Huawei Proprietary and Confidential

Optimized descriptions about the FMA function to make the

Huawei Proprietary and Confidential

l Modified the recommended Java JRE version. For details, see

Huawei Proprietary and Confidential

About This Chapter

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

2.1 Configuration Requirements of the LMT PC

2.8 GHz or above