Bsc6910 Umts LMT User Guide (v100r015c00 - 09) (PDF) - en

BSC6910 UMTS
V100R015C00
LMT User Guide

Issue
09
Date
2014-12-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. 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 09 (2014-12-29)
Huawei Proprietary and Confidential

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

Overview
This document describes the functions and relevant components of the BSC6910 Local
Maintenance Terminal (LMT). It also provides instructions for performing basic operation and
maintenance (OM) tasks of theBSC6910.
Product Version
The following table lists the product version related to this document.
Product Name
Product Version
BSC6910
V100R015C00
Intended Audience
This document is intended for:
l
Network engineers
System engineers
Field engineers
Organization
1 Changes in the BSC6910 UMTS LMT User Guide
This chapter describes the changes made in the BSC6910 UMTS LMT User Guide.
2 Introduction to LMT
The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) for users for easy operation and maintenance of the BSC6910. Users can
perform operations such as alarm management, trace management, performance monitoring,
and device maintenance. Users can also run MML commands and read the corresponding
execution results on the LMT.
Issue 09 (2014-12-29)

ii
BSC6910 UMTS
LMT User Guide
About This Document
3 Management of Operation Rights

This chapter describes the management of operation rights, and provides instruction to manage
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 BSC6910.
5 Alarm/Event Management
This chapter describes how to manage BSC6910 alarms/Events through the LMT. Alarm/Event
management allows you to analyze alarms/events more efficiently and facilitates
troubleshooting.
6 Log Management
This chapter describes how to manage the BSC6910 logs through the LMT. Log files can be
saved in .txt and .csv formats. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can manage the logs.
7 Trace Management
This chapter describes how to manage message tracing on the BSC6910. A maximum of 64 trace
tasks can be performed simultaneously on the same LMT. When OMU boards perform an active/
standby switchover, monitoring can be restarted only 30 minutes after the switchover.
8 Performance Monitoring
This chapter describes how to monitor the BSC6910 performance. A maximum of 64 monitoring
9 Device Panel
This chapter describes how to manage the BSC6910 equipment by using the device and
emulation panels. You can use these panels to query for information about the boards, board
ports, board links, and board alarms.
10 BSC Maintenance
This chapter describes how to maintain the BSC equipment, Backing Up Data and Restoring
Data, and Fault Management Assistant.
11 FAQ
This chapter describes some frequently asked questions (FAQs) and the corresponding solutions.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 09 (2014-12-29)

iii
BSC6910 UMTS
LMT User Guide
About This Document
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 09 (2014-12-29)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.

iv
BSC6910 UMTS
LMT User Guide
About This Document
Convention
Description
[]
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 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Issue 09 (2014-12-29)
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
BSC6910 UMTS
LMT User Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the BSC6910 UMTS LMT User Guide.................................................................1
2 Introduction to LMT.....................................................................................................................6
2.1 Configuration Requirements of the LMT PC.................................................................................................................7
2.2 Logging In to and Logging Out of the LMT..................................................................................................................9
2.3 Components of the LMT Window................................................................................................................................13
2.4 LMT Software..............................................................................................................................................................17
2.4.1 Installing LMT Offline Tools....................................................................................................................................17
2.4.2 FTP Client..................................................................................................................................................................19
2.4.3 FTP Server.................................................................................................................................................................20
2.4.4 LMT Offline MML....................................................................................................................................................22
2.4.5 Convert Management System....................................................................................................................................26
2.4.6 Performance Browser Tool........................................................................................................................................27
2.4.7 TrafficRecording Review Tool..................................................................................................................................28
2.5 User-defined Command Group....................................................................................................................................29
2.6 File Manager.................................................................................................................................................................31
3 Management of Operation Rights............................................................................................36

3.1 Concepts Related to Operation Rights Management....................................................................................................37
3.1.1 Principles of Operation Rights Management.............................................................................................................37
3.1.2 User Password...........................................................................................................................................................37
3.1.3 Command Group.......................................................................................................................................................38
3.1.4 User Type..................................................................................................................................................................39
3.1.5 Operation Rights........................................................................................................................................................39
3.1.6 Operation Time Limit................................................................................................................................................40
3.2 Management of User Accounts....................................................................................................................................41
3.2.1 Creating an External User Account...........................................................................................................................41
3.2.2 Modifying an External User Account........................................................................................................................42
3.2.3 Deleting an External User Account...........................................................................................................................42
3.3 Management of User Passwords...................................................................................................................................42
3.3.1 Defining Login Password Policies............................................................................................................................43
3.3.2 Querying Login Password Policies............................................................................................................................43
Issue 09 (2014-12-29)

vii
BSC6910 UMTS
LMT User Guide
Contents
3.3.3 Changing the Password of the Active User Account................................................................................................43

3.3.4 Changing the Password of an External User Account...............................................................................................44
3.4 Management of Command Groups...............................................................................................................................44
3.4.1 Querying a Command Group....................................................................................................................................44
3.4.2 Setting the Command Group Name...........................................................................................................................44
3.4.3 Changing the Commands in a Command Group.......................................................................................................45
4 Running MML Commands........................................................................................................46

4.1 Concepts Related to MML Commands........................................................................................................................48
4.1.1 Introduction to MML Commands..............................................................................................................................48
4.1.2 Components of the MML Command Window..........................................................................................................49
4.1.3 Data Configuration Rights.........................................................................................................................................51
4.1.4 Data Configuration Rollback.....................................................................................................................................51
4.2 Running an MML Command.......................................................................................................................................52
4.3 Batch Processing MML Commands.............................................................................................................................53
4.3.1 Immediate Batch Processing of MML Commands...................................................................................................54
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 the Data Configuration Mode.......................................................................................................................57
4.6 Querying Data Configuration Rights............................................................................................................................58
4.7 Obtaining Data Configuration Rights...........................................................................................................................59
4.8 Undoing/Redoing a 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...........................................................................................................................................................63
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 Conditions of Alarm Logs................................................................................................................67
5.2.2 Querying Storage Conditions of Alarm Logs............................................................................................................67
5.3 Managing the Alarm Filter...........................................................................................................................................67
5.3.1 Creating an Alarm Filter............................................................................................................................................68
5.3.2 Deleting an Alarm Filter............................................................................................................................................68
5.3.3 Querying an Alarm Filter..........................................................................................................................................68
5.4 Managing the Filter of Derived Alarms.......................................................................................................................69
5.4.1 Setting the Filter of Derived Alarms.........................................................................................................................69
5.4.2 Querying the Filter of Derived Alarms......................................................................................................................69
5.5 Monitoring Alarms.......................................................................................................................................................70
Issue 09 (2014-12-29)

viii
BSC6910 UMTS
LMT User Guide
Contents
5.5.1 Browsing Alarm/Event..............................................................................................................................................70

5.5.2 Querying the Alarm/Event Log.................................................................................................................................70
5.5.3 Querying Alarm/Event Handling Suggestions..........................................................................................................71
5.5.4 Querying Alarm/Event Configuration.......................................................................................................................72
5.5.5 Filtering Fault Alarm/Event.......................................................................................................................................73
5.5.6 Setting Display Attributes for Alarms/Events...........................................................................................................73
5.5.7 Manually Clearing an Alarm/Event...........................................................................................................................76
5.5.8 Deleting Alarms/Events.............................................................................................................................................76
5.5.9 Refreshing the Alarm/Event Window.......................................................................................................................77
5.6 Managing the Alarm Box.............................................................................................................................................77
5.6.1 Querying Alarm Box Information.............................................................................................................................77
5.6.2 Querying Number of Alarms with Different Severities............................................................................................78
5.6.3 Operating the Alarm Box..........................................................................................................................................78
5.6.4 Querying the Alarm Box Filter Level........................................................................................................................79
6 Log Management.........................................................................................................................80
6.1 Log Types.....................................................................................................................................................................82
6.2 Querying Log Storage Conditions................................................................................................................................82
6.3 Setting Log Storage Conditions....................................................................................................................................82
6.4 Querying Operation Logs.............................................................................................................................................83
6.5 Exporting Operation Logs............................................................................................................................................83
6.6 Querying Security Logs................................................................................................................................................84
6.7 Exporting Security Logs...............................................................................................................................................84
6.8 Obtaining Running Logs..............................................................................................................................................85
6.9 Collecting Log Statistics...............................................................................................................................................87
7 Trace Management......................................................................................................................91
7.1 Concepts Related to Trace Management......................................................................................................................92
7.1.1 Trace Principles.........................................................................................................................................................92
7.1.2 Management of Tracing Operation Rights................................................................................................................93
7.1.3 BSC Interface Signaling Tracing Mode....................................................................................................................93
7.2 Device Commissioning.................................................................................................................................................94
7.2.1 Tracing OS Messages................................................................................................................................................94
7.2.2 Tracing Redirected Messages....................................................................................................................................95
7.2.3 Capturing Packets......................................................................................................................................................95
7.2.4 AC Tracing................................................................................................................................................................99
7.2.5 DHCP Tracing.........................................................................................................................................................101
7.3 UMTS Services...........................................................................................................................................................102
7.3.1 Tracing Messages on the Iu Interface......................................................................................................................103
7.3.2 Tracing Messages on the Iupc Interface..................................................................................................................116
7.3.3 Tracing Messages on the Iur Interface.....................................................................................................................124
7.3.4 Tracing Messages on the Iub Interface....................................................................................................................137
7.3.5 Tracing Messages on the Uu Interface....................................................................................................................145
Issue 09 (2014-12-29)

ix
BSC6910 UMTS
LMT User Guide
Contents
7.3.6 Tracing MNCDT Messages.....................................................................................................................................147

7.3.7 Message Setting.......................................................................................................................................................152
7.3.8 Tracing UE Messages..............................................................................................................................................152
7.3.9 Tracing Cell Messages.............................................................................................................................................159
7.3.10 Tracing IOS Messages...........................................................................................................................................162
7.3.11 Tracing Iurp Messages...........................................................................................................................................168
7.4 Basic Tracing Operations...........................................................................................................................................170
7.4.1 Browsing Traced Messages Online.........................................................................................................................171
7.4.2 Viewing the Interpretation of the Trace Message....................................................................................................172
7.4.3 Saving Traced Messages.........................................................................................................................................172
7.4.4 Browsing Traced Messages Offline........................................................................................................................173
7.4.5 Managing Tracing Tasks.........................................................................................................................................174
7.4.6 Managing the Trace File..........................................................................................................................................175
8 Performance Monitoring..........................................................................................................176
8.1 Concepts Related to Performance Monitoring...........................................................................................................177
8.1.1 Monitoring Principles..............................................................................................................................................177
8.1.2 Management of Monitoring Operation Rights........................................................................................................178
8.2 Common Monitoring..................................................................................................................................................179
8.2.1 Monitoring CPU Usage...........................................................................................................................................179
8.2.2 Monitoring CPU Usage on Subsystems..................................................................................................................180
8.2.3 Monitoring Transmission Resources.......................................................................................................................180
8.2.4 Monitoring BER Seconds........................................................................................................................................185
8.2.5 Monitoring BER......................................................................................................................................................186
8.2.6 Monitoring Link Performance.................................................................................................................................187
8.3 UMTS Monitoring......................................................................................................................................................203
8.3.1 Monitoring Connection Performance......................................................................................................................204
8.3.2 Monitoring Cell Performance..................................................................................................................................215
8.3.3 Monitoring System Resources.................................................................................................................................225
8.3.4 Iurp Monitoring.......................................................................................................................................................226
8.4 General Operations of Performance Monitoring........................................................................................................227
8.4.1 Browsing the Monitoring Results Online................................................................................................................227
8.4.2 Setting the Display Mode of the Chart....................................................................................................................228
8.4.3 Saving Monitoring Results......................................................................................................................................228
8.4.4 Browsing Monitoring Results Offline.....................................................................................................................228
8.5 Reference for Performance Monitoring......................................................................................................................229
9 Device Panel...............................................................................................................................232
9.1 Device Panel Operations............................................................................................................................................233
9.1.1 Introduction to the Device Panel.............................................................................................................................233
9.1.2 Starting the Device Panel........................................................................................................................................234
9.1.3 Querying the Status of an E1/T1 Port......................................................................................................................234
9.1.4 Querying the CPU Usage........................................................................................................................................234
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Contents
9.1.5 Querying BSC Board Clock Status.........................................................................................................................235

9.1.6 Querying the BSC Board Information.....................................................................................................................236
9.1.7 Resetting the BSC Board.........................................................................................................................................237
9.1.8 Switching Over the BSC Boards.............................................................................................................................239
9.1.9 Querying the BSC Board Alarm..............................................................................................................................240
9.2 Emulation Panel Operations.......................................................................................................................................240
9.2.1 Introduction to the Emulation Panel........................................................................................................................241
9.2.2 Starting the Emulation Panel...................................................................................................................................241
9.2.3 Querying the Status of an E1/T1 Port......................................................................................................................242
9.2.4 Querying the CPU Usage........................................................................................................................................243
9.2.5 Querying BSC Board Clock Status.........................................................................................................................243
9.2.6 Querying the BSC Board Information.....................................................................................................................244
9.2.7 Resetting the BSC Board.........................................................................................................................................245
9.2.8 Switching Over the BSC Boards.............................................................................................................................247
9.2.9 Querying the BSC Board Alarm..............................................................................................................................249
9.2.10 Querying the Status of an FE Port.........................................................................................................................249
9.2.11 Querying the Status of a GE Port..........................................................................................................................250
9.2.12 Querying the Status of an Optical Port..................................................................................................................250
9.2.13 Querying Alarm LED Information........................................................................................................................251
10 BSC Maintenance.................................................................................................................... 252

10.1 Backing Up Data......................................................................................................................................................253
10.2 Restoring Data..........................................................................................................................................................254
10.3 Diagnosing Fault.......................................................................................................................................................255
10.4 Batch Configuration.................................................................................................................................................262
10.5 OS Maintenance.......................................................................................................................................................263
11 FAQ............................................................................................................................................ 265
11.1 Slow Responses in the Firefox Browser...................................................................................................................270
11.2 LMT Colors Cannot Be Displayed...........................................................................................................................270
11.3 The Verification Code Cannot Be Displayed on the LMT Login Page...................................................................270
11.4 Installing OS Patches................................................................................................................................................271
11.5 No Response When Clicking the Menu Bar on the LMT........................................................................................272
11.6 Changing the Computer Time During the LMT Use Prohibited..............................................................................273
11.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding..................................................273
11.8 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously...........................................276
11.9 How to Set the Browser Under Citrix Farm Networking.........................................................................................276
11.10 Unable to Log In To LMT Because IE Default Security Level Is Too High.........................................................280
11.11 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...........................................................................................................................................287
11.12 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE.....................288
11.13 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes the Web Pages to Turn Blank
..........................................................................................................................................................................................289
Issue 09 (2014-12-29)

xi
BSC6910 UMTS
LMT User Guide
Contents
11.14 Configuring the HTTPS Login Mode.....................................................................................................................290

11.15 The Error "Certificate Invalid" Is Displayed During an HTTPS Login.................................................................291
11.16 The Error 'Mismatched Address' Is Displayed During an HTTPS Login..............................................................300
11.17 Tracing and Monitoring Functions Cannot Be Used..............................................................................................302
11.18 LMT Fails to Function Properly during the tracing/monitoring/batch processing.................................................307
11.19 Interfaces for Performing Tracing or Monitoring Tasks Blinking.........................................................................310
11.20 Unable to Save Tracking and Monitoring Data......................................................................................................310
11.21 The File Manager Functions Improperly................................................................................................................311
11.22 BTS Nodes Cannot Be Displayed Under Device Navigation Tree........................................................................313
11.23 The Alarm/Event Function Becomes Unavailable.................................................................................................314
11.24 The Message 'Class doesn't support Automation' Is Displayed in an IE Browser.................................................315
11.25 Java Installation Fails.............................................................................................................................................316
11.26 The LMT Login Web Page Cannot Be Opened with the PC OMU Installed........................................................316
11.27 Changing Settings for the Next-Generation Java Plug-in Fails..............................................................................317
11.28 Error Message"This user session already exists" Upon Login to LMT.................................................................321
11.29 The "Are You Sure You Want to Quit the Page" Dialog Box Is Displayed..........................................................322
11.30 Slow Response During an LMT Login...................................................................................................................322
11.31 Unclear Grids in the Tables in the MML Online Help...........................................................................................323
11.32 The "App Center" Web Page Is Automatically Displayed When Firefox Is Used to Browse the LMT................324
11.33 "Permission Denied" or "Access Denied" is Displayed When IE Is Used to Browse the LMT............................325
11.34 MML Command Failed to Be Executed or No Response to Tracing Tasks After the Browser Is Upgraded to IE8
..........................................................................................................................................................................................326
11.35 How to Handle Error Message Displayed on the LMT..........................................................................................327
11.36 Tracing File Not Being Uploaded to the Specified Directory................................................................................328
11.37 Settings on the LMT Failing to Take Effective......................................................................................................329
Issue 09 (2014-12-29)

xii
BSC6910 UMTS
LMT User Guide
Changes in the BSC6910 UMTS LMT User

Guide
This chapter describes the changes made in the BSC6910 UMTS LMT User Guide.
09 (2014-12-29)
This is the seventh commercial release of V100R015C00.
Compared with 08 (2014-06-09), this issue does not include any new topics.
Compared with 08 (2014-06-09), this issue incorporates the following changes:
Content
Description
Monitoring FE/GE Traffic
Added the description of GOUe board.
Compared with 08 (2014-06-09), this issue does not exclude any topics.
08 (2014-06-09)
This is the eighth commercial release of V100R015C00.
Compared with 07 (2014-03-28), this issue includes the following new topic:
l
Information Collection
Compared with 07 (2014-03-28), this issue does not incorporate any changes.
07 (2014-03-28)
This is the seventh commercial release of V100R015C00.
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Content
Description
2.1 Configuration
Requirements of the LMT PC
Deleted the description about the Windows XP operating

system as the recommended configuration from section
"Software Requirements" because Microsoft has stopped
maintaining the Windows XP operating system.
Added the following browser versions that are supported
by the LMT: Internet Explorer 10, FireFox 17.x, and
FireFox 24.x.
06 (2014-01-20)
This is the sixth commercial release of V100R015C00.
Compared with 05 (2013-11-15), this issue includes the following new topics:
l
11.37 Settings on the LMT Failing to Take Effective
Compared with 05 (2013-11-15), this issue does not incorporate any changes.
05 (2013-11-15)
This is the fifth commercial release of V100R015C00.
Content
Description
5.5.6 Setting Display Attributes

for Alarms/Events
Added the description of the display attributes for alarms

and events.
04 (2013-07-30)
This is the fourth commercial release of V100R015C00.
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Content
Description
Monitoring the Outer Loop

Power Control
Added the description: 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.
03 (2013-06-25)
This is the third commercial release of V100R015C00.
Content
Description
Monitoring the Outer Loop

Power Control
Updated the description of Outer Loop Power Control.
02 (2013-05-30)
This is the second commercial release of V100R015C00.
Content
Description
2.1 Configuration
Requirements of the LMT PC
Modified the requirements of Java Platform Standard

Edition Runtime Environment and Adobe Flash Player.
Added the description that the browser window is
displayed at 100% level.
Issue 09 (2014-12-29)
2.6 File Manager
Added the descriptions of Set Search Criteria and Delete

Search Criteria.
8.2.3 Monitoring Transmission

Resources
Added the description of RealTimeFluxBw and

RealTimeQueueFlux.
10.3 Diagnosing Fault
Added the description about the scenario options of fault

analysis.

BSC6910 UMTS
LMT User Guide
01 (2013-05-04)
This is the first commercial release of V100R015C00.
Compared with Draft B (2013-02-27), this issue includes the following new topics:
l
2.5 User-defined Command Group
Compared with Draft B (2013-02-27), this issue incorporates the following changes:
Content
Description
5.5.1 Browsing Alarm/Event
Added the description of dragging the rows in the Alarm/

Event tab page to rearrange the table.
5.5.2 Querying the Alarm/

Event Log
7.2.5 DHCP Tracing
Changed PID to DHCP Product ID.
7.3.8 Tracing UE Messages
Added the description that a maximum of six internal

message tracing tasks can be created.
Monitoring Cell Credit
Changed Cell CE to Cell Credit.
8.3.3 Monitoring System

Resources
Changed the units of the vertical coordinates in the chart

from KB to Erl and kbit/s.
Added the description about how the states of

performance measurement in short measurement periods
affect the KPI and counter change trend chart.
Added the procedures for selecting the logical NEs on
which fault diagnosis is to be performed.
11.15 The Error "Certificate

Invalid" Is Displayed During
an HTTPS Login
Changed the mode of downloading the certificate by the

filer manager to downloading the certificate by the FTP
client.
Compared with Draft B (2013-02-27), this issue does not exclude any topics.
Draft B (2013-02-27)
This is the Draft B release of V100R015C00.
Compared with Draft A (2013-01-30), this issue does not include any new topics.
Compared with Draft A (2013-01-30), this issue incorporates the following changes:
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Content
Description
2.4.3 FTP Server
Deleted the mode of starting the FTP server from the

Start menu.
Add the description of the password of FTP server and
Working directory.
Monitoring the Bit Rate

Provided by the HS-DSCH
Add the description of the bit rate on the HS-DSCH of the

cell is not reported when HSDPA_PBR_MEAS is set to
0.
Monitoring the Bit Rate

Provided by the E-DCH
Add the description of the bit rate on the E-DCH of the

cell is not reported when HSUPA_PBR_MEAS is set to
0.
Compared with Draft A (2013-01-30), this issue does not exclude any topics.
Draft A (2013-01-30)
This is the Draft A release of V100R015C00.
Issue 09 (2014-12-29)

BSC6910 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) for users for easy operation and maintenance of the BSC6910. Users can
perform operations such as alarm management, trace management, performance monitoring,
and device maintenance. Users can also run MML commands and read the corresponding
execution 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 the
following requirements related to 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 Window
You can log in to the LMT through a web browser to operate and maintain the BSC6910.
2.4 LMT Software
The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser, and TrafficRecording
Review Tool.
User-defined Command Group is used to add commands to a specified command group so that
an admin user can add operation authorities for authority-limited users.
2.6 File Manager
The file manager, which is a component of the LMT application, helps you upload files from
the LMT to the OMU and download files from the OMU to the LMT. Its functions are similar
to those of the FTP client. For example, you can obtain logs and upload data configuration files.
Issue 09 (2014-12-29)

BSC6910 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 the
following requirements related to 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
Issue 09 (2014-12-29)
Item
Recommended Configuration
Operating system
Windows Vista/7, Windows Server 2003/2008
Default language of the

operating system
Simplified Chinese or English

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

FireFox 10.X, 17.X and 24.X
NOTE
l You need to set the security level of the Web browser to medium
or low. Otherwise, the LMT menus cannot be viewed.
l If IE8 or later versions is used, you neeed to choose Tools >
Compatibility View Settings . In the displayed Compatibility
View Settings dialog box, select Display all websites in
Compatibility View.
Java plug-in called Java

Platform Standard Edition
Runtime Environment (JRE)
JRE 1.6.0_26 is recommended.
Flash plug-in called Adobe

Flash Player
Flash Player 11.1.102 is recommended.
NOTE
The plug-in can be obtained on LMT login window.
NOTE
The plug-in can be obtained on 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 can be used only in the 32-bit operating system and with the
32-bit Web explorer.
l Ensure that the browser window is zoomed at 100% level when you are using the LMT.
Otherwise, the layout of the LMT interface may be abnormal. If the layout of the LMT
interface is abnormal, check whether the browser window is zoomed at 100% level by
viewing the scaling icon at the lower right corner of the IE browser window.
Requirements of Connection Ports

Before you visit the LMT through the Web on a PC, ensure that ports 80, 20, 21, and 443 of the
firewall are open if there is a firewall between the PC and the LMT.
NOTE
l Port 80 is the default HTTP port that is used for Web page browsing.
l Ports 20 and 21 are the ports used for FTP file transfer.
l Port 443 is the default HTTPS port that is used for HTTPS login Mode.
Communication Capability Requirements

The LMT PC must support TCP/IP protocols and meet the requirements of effective bandwidth
in Table 2-3.
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
Table 2-3 Effective bandwidth requirements of the LMT PC

Item
Protocol
Recommended
Configuration
Minimum
Configuration
Requirements of
effective bandwidth
Hypertext Transfer
Protocol (HTTP)
Not lower than 2

Mbit/s
512 kbit/s
NOTE
l Bandwidth affects the speed of Web page visits. You can rapidly visit the LMT on an LMT PC with a
recommended configuration. Your visit to the LMT is, however, significantly delayed on an LMT PC
with the minimum configuration although all LMT functions can be used.
l Effective bandwidth in most cases indicates the bandwidth available for the LMT. If many programs
compete with the LMT for bandwidth resources, a serious delay occurs despite a link bandwidth of 2
Mbit/s under HTTP.
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.
A maximum of 32 local users and EMS users can log in to the LMT.
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.
Issue 09 (2014-12-29)

BSC6910 UMTS
LMT User Guide
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 the LMT is active in the IE6 browser and you choose Start > Run to start the FTP server,
the IE browser closes the LMT window and goes to the login window of the FTP server
directly. To avoid this problem, set the IE browser as follows: choose Tools > Internet
Options. In the Advanced tab page, deselect Reuse windows for launching shortcuts from
the Browsing options.
l If colors cannot be displayed in the LMT window, set the IE6 browser as follows: choose
Tools > Internet Options. In the General tab page, click Accessibility. Then, in the
Formatting area, deselect Ignore colors specified on Web pages.
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."
Procedure
Step 1 Enter the LMT login page by using one of the following modes:
Issue 09 (2014-12-29)

10
BSC6910 UMTS
LMT User Guide
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 BSC6910.
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 M2000_IP.
Mode 2:
connection
through the
M2000 that is
configured as
the proxy server
The LMT connects

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

to the OMU through
the M2000 with IP
addresses of both
M2000 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 M2000 and
cannot be changed.
Issue 09 (2014-12-29)
1. You can set the M2000 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 M2000 server in the Proxy
server area. The default port number is 80.
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 BSC6910.
Type "M2000_IP/OMU_IP/" (for example,
10.141.130.146/10.141.151.208/) or "http://
M2000_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 BSC6910. Note that "/" must be
included in "M2000_IP/OMU_IP/" behind
"OMU_IP." If another proxy server is already set,
you need to add M2000_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 M2000_IP indicates the IP address of the
M2000 server.

11
BSC6910 UMTS
LMT User Guide
NOTE
l When you are logging in to the LMT using the second or third method, settings on the M2000 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 querying and configuring the M2000 security connection mode, see section Configuring
M2000 Security Connection in M2000 Commissioning Guide.
M2000 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 Verify Code.

l Set User Type to Local or EMS.
l If the verify 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 BSC6910 as an EMS user, you need to set up a connection between the
BSC6910 and the M2000 server.
l If the login fails, click Reset. Specify User Name, Password, and Verify 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.
Issue 09 (2014-12-29)

12
BSC6910 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 11.14 Configuring the HTTPS Login Mode.
l In HTTPS mode, if you need to connect to the OMU with the M2000 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 11.15 The Error "Certificate Invalid" Is
Displayed During an HTTPS Login and 11.16 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 Window

You can log in to the LMT through a web browser to operate and maintain the BSC6910.
Interface
Figure 2-1 shows the LMT window.
Figure 2-1 LMT window
Table 2-4 describes components of an LMT window.
Issue 09 (2014-12-29)

13
BSC6910 UMTS
LMT User Guide
Table 2-4 Components of the LMT window

Component
Description
Alarm/Event tab
You can query active alarms, alarm logs, and alarm configuration
in this tab page. For details, see 5 Alarm/Event Management.
Batch tab
You can run MML commands in batches in this tab page. For
details, see 4.3 Batch Processing MML Commands.
Trace tab
You can manage message tracing tasks in this tab page. For details,
see 7 Trace Management.
Monitor tab
You can monitor performance data in this tab page. For details, see
8 Performance Monitoring.
Device Maintenance
tab
You can maintain the device panel. For details, see 9 Device
Panel.
FMA tab
It includes two functions: 10.3 Diagnosing Fault and Information

Collection.
MML tab
For details, see 4.1.2 Components of the MML Command

Window.
Progress tab
You can click the tab to display the progress of a task. 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. The Progress
Management dialog box is displayed, listing the detailed progress report.
Issue 09 (2014-12-29)
FTP Tool
You can click it to download the executable application file

SFTPServer.exe.For details, see 2.4.2 FTP Client and 2.4.3 FTP
Server.
Password
You can click it to change the password of the current user. After
changing the password, you need to use the new password when
logging in again.
User-defined
Command Group
User-defined Command Group is used to add commands to a

specified command group so that an admin user can add operation
authorities for authority-limited users.

14
BSC6910 UMTS
LMT User Guide
Component
Description
Obtain
Documentation List
Choose Obtain Documentation List on the LMT. The

documentation packages of the corresponding product version are
listed in the displayed dialog box. You can use either of the
following methods to download the documentation packages:
l Search for the documentation packages at the website http://
support.huawei.com and then download them.
l Click Export to export the corresponding .hdxi file. Then
double-click the .hdxi file to search for related product
documentation on http://support.huawei.com. The result will be
listed for downloading.
NOTE
Before using this function, ensure that:
l You can visit http://support.huawei.com and have obtained the
account.
l (For initial use only) You have downloaded the HedEx Lite from
the homepage of http://support.huawei.com to your PC and started
it.
System Setting
After clicking it, a dialog box containing three areas is displayed.

The three areas are named Language Setting, Auto Lock, and Result
file Save Path.
l Choosing a language in the Language Setting area allows text
in this language to be input and displayed on the LMT. Setting
the language does not change the display language of the LMT.
l In the Auto Lock area, the time for the LMT to wait before
locking the screen can be specified. If there is no mouse or
keyboard operation during the time, the LMT automatically
locks its operation screen and goes to the locked page. The
setting prevents unauthorized users from using others' accounts
and performing unauthorized configuration and maintenance.
l In the Result file Save Path area, the save path for all operation
result files can be specified. The system default save 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.6 File
Manager.
About
You can click it to display the version of the current LMT.
Lock
You can click it to lock the current operation interface for security.
NOTE
l After you click Lock on the toolbar, the LMT is locked.
l You can click the web page or press the Enter key, type the password,
and then click OK or press Enter to enter the LMT workspace again.
Issue 09 (2014-12-29)

15
BSC6910 UMTS
LMT User Guide
Component
Description
Logout
You can click it to log out the current user without exiting the
system. Logout of one account user facilitates login of another
account user.
Online Help
The LMT provides the following two types of online help:
l
Online help system
MML help
Table 2-5 describes the specific help and startup method of online help.
Table 2-5 Description of LMT online help
Name
Specific Help
Startup Method
Online
help
system
Provides the
following
information:
If the Microsoft Internet Explorer is used:
l LMT online
help
l Press F1 in a displayed dialog box on the LMT 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 LMT help information.
l Press F1 or click Help on the LMT main page to display

LMT help information.
l Event
reference
MML
help
Provides the
following
information
about an MML
command:
Type an MML command in the Command Input box. Press

Enter or click Assist, and then click the Help Information
tab. Help information about the command is displayed in the
tab page.
l Command
function
l Note
l Parameter
l Example
l Output
description
(only for
query
commands)
Issue 09 (2014-12-29)

16
BSC6910 UMTS
LMT User Guide
2.4 LMT Software

The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser, and TrafficRecording
Review Tool.
2.4.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 is obtained.
The PC for installing the LMT offline tools complies with the specifications mentioned in
2.1 Configuration Requirements of the LMT PC.
Using setup disk
Procedure
1.
Use the administrator account to log in to the LMT PC.
2.
Insert the setup disk 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 directory of the setup disk.
3.
Choose the installation language, and click OK. The installation wizard prompts you
that you are installing HUAWEI Local Maintenance Terminal.
4.
Click Next. A dialog box is displayed, asking you to read the copyright notice.
5.
Read the software certificate declarations. If you accept the agreement terms, select
I accept these terms, and then click Next. A dialog box is displayed, asking 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 browse to a new path, and then click Next.
NOTE
The default installation path is D:\HW LMT.

l If the LMT of another version or NE has been installed, the installation path is that of the
original LMT software and cannot be altered.
l To alter the installation path, you must uninstall the existing LMT software.
If an LMT software is running, a Warning dialog box is displayed. Click Yes to enable the
system to automatically exit the LMT application. Click No to manually exit the LMT
application.
Issue 09 (2014-12-29)
7.
Select the software components and then click Next. It is recommended that you select
all components. A dialog box is displayed for entering the CD-KEY.
8.
Enter the CD-KEY correctly, and then click Next. A dialog box is displayed, asking
you to confirm the installation.
9.
Confirm the installation parameters and click Next. A dialog box is displayed,
indicating the progress of copying the files.
17
BSC6910 UMTS
LMT User Guide
When the task of copying files is complete, a dialog box is displayed for initializing
components. When all programs are installed, a dialog box is displayed, indicating
the completion of the installation.
10. Click Finish.
NOTE
The installation is complete. When the installation is complete, the LMT Service Manager starts
automatically.
Using 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 BSC6910 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.
Download the Hash compressed package (with the name "Product Version
Number Hash List.rar") from the same directory as the installation package of the
LMT offline tools. The Hash compressed package contains the file "Product Version
Number Hash List.mht". Decompress the Hash compressed package to obtain this
file. Then, open this file to obtain the Hash value for the installation package of the
LMT offline tools. The SHA-256 column in Figure 2-2 shows the calculated Hash
value.
Figure 2-2 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 SingleRAN_O&M tools 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. Choose file > Add Files. In the displayed dialog box, choose the
installation package of the LMT offline tools. The SHA-256 column in Figure 2-3
shows the calculated Hash value.
Figure 2-3 Hash value calculated by the Hash value calculation tool
4.
Issue 09 (2014-12-29)
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
18
BSC6910 UMTS
LMT User Guide
continue subsequent operations. If the Hash values are different, contact Huawei
engineers.
----End
2.4.2 FTP Client

The FTP client is a component of the LMT offline suite and enables the LMT to communicate
with the FTP server according to the FTP or FTPs protocol. You can obtain logs and upload data
configuration files through the FTP client.
Startup
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > FTP Client on
the LMT PC.
Interface
Figure 2-4 shows the FTP client interface.
Figure 2-4 FTP client interface
Table 2-6 describes the components of the FTP client interface.

Table 2-6 Components of FTP client interface
Issue 09 (2014-12-29)
Number
Component
Description
Menu bar
Provides the menus for the operation of the system.

19
BSC6910 UMTS
LMT User Guide
Number
Component
Description
Tool bar
Provides the shortcut icons for the operation of the

system.
Server input area
Includes the server name, user name, user password,

port number, and mode in this area.
NOTE
To query the port number, run the LST FTPSSRV
command to query 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.
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 the information such as the connection

status of the FTP server and the operation
descriptions.
2.4.3 FTP Server

The FTP server is a component of the LMT offline suite and provides FTP upload and download
service. It is used when users upload and download BTS software and license files.
Startup
To start up the FTP server, perform the following operation:
l
Click FTP Tool on the tool bar of the LMT window to download the executable application
file SFTPServer.exe. Then double-click the executable file to start the FTP server.
NOTE
Users cannot use the FTP server if they log in to the LMT through a proxy server.
Interface
Figure 2-5 shows the FTP server interface.
Issue 09 (2014-12-29)

20
BSC6910 UMTS
LMT User Guide
Figure 2-5 FTP server interface
Table 2-7 describes the components of the FTP server interface.

Table 2-7 Components of FTP server interface
Component
Description
User name
The user name of the FTP server is admin by default.
Password
The password of the FTP server is hwbs@com by default.

NOTE
To change the password, enter the old password to perform security check.
Working directory
Working directory after the FTP server is started.

NOTE
You are only allowed to visit files under the directory when using the FTP
client.
Port number
Indicates the number of the port used by the FTP server to intercept
the information on the network.
NOTE
To query the port number, run the LST FTPSSRV command to query 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 09 (2014-12-29)

21
BSC6910 UMTS
LMT User Guide
Component
Description
Thread number
Indicates the number of clients that can be connected to the FTP

server simultaneously.
2.4.4 LMT Offline MML

LMT offline MML is a component of the LMT offline tool. It enables users to use MML
functions, view MML, make MML scripts, and view LMT Online Help of the required version
offline by means of a browser.
Introduction to the LMT Offline MML Server

This section describes the startup method and interface of the LMT offline MML server.
Startup Method
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > WebLMT
OffLine MML on an LMT PC to start the LMT offline MML server.
Interface
Figure 2-6 shows the LMT offline MML server interface.
NOTE
You can double-click the

icon in the bottom right corner of the LMT PC to display the LMT offline
MML server interface after the LMT offline MML server is started and minimized.
Figure 2-6 LMT Offline MML Server Interface
Table 2-8 describes each area of the LMT offline MML server interface.
Issue 09 (2014-12-29)

22
BSC6910 UMTS
LMT User Guide
Table 2-8 Description of the LMT offline MML server

Field
Description
Routine tab
Displays the server state of LMT offline MML.

NOTE
l Click Hide to minimize the LMT offline MML server to the bottom
right corner 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 enter the login window of LMT offline MML.
Config tab
Click it to configure the server port.
About tab
Displays information about LMT offline MML.
Logging In to and Out of LMT Offline MML Tool

This section describes how to log in to LMT offline MML tool for relevant operations and how
to exit it after performing the operations.
Prerequisites
LMT offline MML server is started.
Procedure
Step 1 Select a method for logging in to LMT offline MML based on whether the LMT offline MML
tool is installed on the LMT PC.
If...
Then...
The LMT offline MML tool is installed and

started on the LMT PC.
Enter http://127.0.0.1:Port or http://

IPAddress:Port in the browser and the LMT
offline MML login window is displayed.
The LMT offline MML tool is not installed

on the LMT PC.
Enter http://IPAddress:Port in the browser

and the LMT offline MML login window is
displayed.
NOTE
l IPAddress stands for the IP address of an LMT PC installed with the LMT offline MML tool. Port
stands for the port number of the LMT offline MML server. The default port number is 810.
l You can change the default port number in the Config tab page of the server. The new port number
takes effect only after the LMT offline server is stopped and then restarted.
Step 2 Select OMType, Version, and Pattern in the LMT offline MML login window and click
Login to log in.
Issue 09 (2014-12-29)

23
BSC6910 UMTS
LMT User Guide
NOTE
l You can switch display language between English and Chinese by clicking the language-switching
button in the top right corner of the login window.
l You can restore the default setting used during installation by clicking Reset.
Step 3 To exit the LMT, click Logout in the top right corner of the LMT main page.
----End
Introduction to the LMT Offline MML Interface

This section describes the LMT offline MML interface. Logging in to LMT offline MML using
a browser, you can view MML, make relevant MML scripts, and obtain LMT Online Help.
Interface
Figure 2-7 shows the LMT offline MML interface.
Figure 2-7 LMT offline MML interface
Table 2-9 describes each area of the LMT offline MML interface.
Table 2-9 Description of the LMT offline MML interface
Issue 09 (2014-12-29)
Field
Description
Navigation Tree
Displays the entire set of MML commands. Double-click an MML

command to load it to the Command Input box.
Search
Enter a keyword to search for an MML command.

24
BSC6910 UMTS
LMT User Guide
Field
Description
Operation Record tab
Displays commands that have been run.

NOTE
The Send Time displayed in the operation record is the time of the LMT
PC.
Help Information tab
Displays help information for a command.
Manually editing area
Displays the area for manually editing an MML command script.
History Command box
Displays commands executed after a login and the relevant

parameters.
Command Input box
Displays in the drop-down list all the MML commands available

on the system. You can select an MML command from the dropdown list or type in an MML command for execution.
Parameter area
Displays parameters of a current command. You need to set

parameter values in the boxes before executing the command. The
parameters displayed in red are mandatory and those in black are
optional.
Help
Click Help to obtain LMT Online Help of the required version.
About
Click About to obtain information about the version of LMT

offline MML.
Making MML Scripts Offline

This section describes how to make MML scripts offline.
Procedure
Step 1 Log in to LMT offline MML. For detailed operations, see Logging In to and Out of LMT
Offline MML.
Step 2 Type an MML command in the LMT offline MML interface, click Assist, and set the parameters.
NOTE
LMT offline MML supports the association function. When a command is typed in the Command Input
box, relevant commands are provided for reference.
Step 3 Click Save to save the MML command and parameter settings to the local MML script file.
NOTE
l Saving the command input and parameter settings to the local file by clicking Save does not overwrite
what was saved.
l You can right-click in the Operation Record area and choose an option from the shortcut menu to
clear or save all MML commands.
l You can select an MML command in the Operation Record area and right-click it to clear or save the
MML command or all MML commands.
----End
Issue 09 (2014-12-29)

25
BSC6910 UMTS
LMT User Guide
2.4.5 Convert Management System

The Convert Management System is a component of the LMT offline tool. 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. The Convert
Management System must be started to connect the LMT to the alarm box. The Convert
Management System communicates with the OMU through the Ethernet port and to the alarm
box through the serial port.
Function
The Convert Management System performs the following functions:
l
Forwards the alarm operation instructions from the LMT.
Forwards the 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 ports of the alarm box, and reports the alarms if any.
Startup
NOTE
The Convert Management System cannot start if Microsoft Visual C++ 2005 SP1 Redistributable Package
(X86) is not installed on the LMT PC. Download this package from www.microsoft.com.
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Convert
Management System on the LMT PC.
Interface
Figure 2-8 shows the interface of the Convert Management System.
Figure 2-8 Interface of the Convert Management System
Issue 09 (2014-12-29)

26
BSC6910 UMTS
LMT User Guide
Table 2-10 describes the components of the Convert Management System interface.
Table 2-10 Components of the Convert Management System interface
Number
Component
Description
Menu bar
Tool bar

system.
Information output
window
Displays the real-time output information of the

Convert Management System.
2.4.6 Performance Browser Tool

The performance browser tool is a component of the LMT offline tool. It is used to parse the
performance descriptive files in the OMU.
Startup
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Performance
Browser Tool on the LMT PC.
Interface
Figure 2-9 shows the interface of the performance browser tool. The
Figure 2-9 Interface of performance browser tool
Issue 09 (2014-12-29)

27
BSC6910 UMTS
LMT User Guide
Table 2-11 describes the components of the performance browser tool interface.
Table 2-11 Components of the performance browser tool interface
Number
Component
Description
Menu bar

Click Help to obtain the use method of the tool.
Tool bar

system.
Measurement
statistics window
Provides the measurement statistic files in the tree

structure.
Detailed information
window
Provides the detailed information on a selected

performance file.
2.4.7 TrafficRecording Review Tool

The TrafficRecording Review Tool is a component of the LMT offline tool and is used to review
the trace and monitor data.
Startup
Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecording
Review Tool on the LMT PC.
Interface
Figure 2-10 displays the interface of the TrafficRecording Review Tool.
Issue 09 (2014-12-29)

28
BSC6910 UMTS
LMT User Guide
Figure 2-10 Interface of the TrafficRecording Review Tool
Table 2-12 describes the components of the TrafficRecording Review Tool interface.
Table 2-12 Components of the TrafficRecording Review Tool interface
Number
Component
Description
Menu bar
Tool bar

system.
Service data retrieval

window
Provides the data related to the trace and monitor

tasks.

User-defined Command Group is used to add commands to a specified command group so that
an admin user can add operation authorities for authority-limited users.
Startup Mode
Click User-defined Command Group on the toolbar of the LMT to start a user-defined
command group, as shown in Figure 2-11.
Issue 09 (2014-12-29)

29
BSC6910 UMTS
LMT User Guide
Figure 2-11 Start User-defined Command Group dialog box
NOTE
Only an admin user is allowed to perform this operation.

A message prompting an operation failure will be displayed if an authority-limited user performs this operation.
Interface
Figure 2-12 shows the User-defined Command Group dialog box.
Figure 2-12 User-defined Command Group dialog box
Table 2-13 describes each area in the User-defined Command Group dialog box.
Table 2-13 Introduction to the User-defined Command Group dialog box
Issue 09 (2014-12-29)
No.
Component
Description
Command group
selection area
Value range: G_15 to G_31

30
BSC6910 UMTS
LMT User Guide
No.
Component
Description
Authorization item
area
This area includes all MML commands and

encapsulated GUI commands.
NOTE
All items under *GUI Authorization Items are marked
with * to distinguish them from MML commands.
Authorization item
addition button
After selecting the target commands on the left area,

you can click this button to add the selected
commands from the left area to the right area.
NOTE
The directory level for commands on the right area is the
same that on the left area.
To improve operation efficiency, you are advised to add less
than 1024 commands at a time.
Authorization item
deletion button
After selecting the target commands on the right area,

you can click this button to delete the selected
commands from the right area.
Authorization item
displaying or hiding
area
Select Display authorization items of MML

commands. and Display authorization items of the
GUI function. to display the directory of the
corresponding authorization items. Deselect the two
items to hide the directory of the corresponding
authorization items.
Authorization item
addition area
This area displays the commands to be added to the

current command group.
Apply or Cancel
button
Click Apply to add the new commands to the current

command group, which contains all commands in the
directory on the right area.
Click Cancel to close the current dialog box.
2.6 File Manager

The file manager, which is a component of the LMT application, helps you upload files from
the LMT to the OMU and download files from the OMU to the LMT. Its functions are similar
to those of the FTP client. For example, you can obtain logs and upload data configuration files.
Startup Method
Click File Manager on the toolbar of the LMT to start the file manager.
Issue 09 (2014-12-29)

31
BSC6910 UMTS
LMT User Guide
NOTE
Operators with different operation rights have different rights to access the file manager. For description of
operation rights, see 3.1.5 Operation Rights.
l ADMINISTRATOR-level and admin-level users have full operation rights. They have all of the operation
rights to the file manager.
l Users at other levels have only download rights to the file manager. They are not authorized to upload or
delete files.
Interface
Figure 2-13 shows the interface of the file manager.
Figure 2-13 File manager interface
Table 2-14 describes each area of the file manager interface.

Table 2-14 Components of the file manager interface
Issue 09 (2014-12-29)
Number
Component
Description
Path switch area
Used to directly navigate to a file folder or file.
File navigation area
Displays files on the OMU in a file tree structure.
File list area
Provides detailed information about files on the

OMU.
File processing area
Contains file processing buttons.
Task list area
Displays task processing information about files.

32
BSC6910 UMTS
LMT User Guide
Path Switch Area

This area is used to directly go to a file folder or file. You can type the path of a required file or
file folder in the text box of the area, and press Enter or click Go to go to the required path.
NOTE
l You can only type a path, for example, /bam/common/log under the Root directory on the file manager
server side.
l Adding a slash (/) in front of the root directory is optional.
File Navigation Area

This area lists all file directories that can be viewed and operated by users on the server. After
right-click on a selected folder, a short-cut menu containing items Refresh Whole Folder
Tree, Set Search Criteria, and Delete Search Criteria is displayed.
l
You can refresh the folder tree by clicking Refresh Whole Folder Tree to obtain the latest
folder organizations.
If you choose Set Search Criteria, the Set Search Criteria dialog box is displayed, as
shown in Figure 2-14. Select the required search criteria, enter the correct search criteria,
and then click Confirm. The search criteria setting is complete.
Figure 2-14 Set Search Criteria dialog box
Modified time: The value range is from 2000 to 2038. If both Start time and End
time are set, the value of End time must be greater than the value of 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 _.
Issue 09 (2014-12-29)

33
BSC6910 UMTS
LMT User Guide
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 is applied, only files meeting the search criteria under the folder are
displayed in the file manager.
l The search criteria takes effect only for the current folder, not its sub-folders.
l If no search criteria is selected, all files will be displayed after Confirm is clicked, similar to the
result of clicking Delete Search Criteria.
You can delete the search criteria set for a folder by clicking Delete Search Criteria.
File List Area

This area lists files in a selected file folder.
NOTE
Only files compliant to the search criteria are displayed under a folder that is set with the search criteria.
You can select and then right-click a file in the area to choose Refresh, Upload, Download, or
Delete from the shortcut menu.
File Processing Area

This area contains the following file processing buttons.
l
Refresh: Click it to refresh the list of files under the current file folder.
Upload: Click it to upload a selected file from the LMT PC to the OMU.
Download: Click it to download a selected file from the OMU to the LMT PC. If the
directory is specified before the download, the selected file is automatically downloaded
to the preset directory.
Delete: Click it to delete a selected file.
Directory: Click it to change the target folder for saving a downloaded file. If the directory
is specified before the download, the selected file is automatically downloaded to the preset
directory.
NOTE
If no new directory is set and the file manager is not closed, the download directory is the one that was set last
time.
When the bandwidth is 2 Mbit/s, it is recommended that the number of files downloaded at the same time do
not exceed 100 and that of files uploaded do not exceed 10.
Task List Area

This area displays relevant information about current tasks. You can process tasks in the task
list area in the following ways:
l
Clear Finished Task: Right-click the task list area and choose Clear Finished Task to clear
all finished tasks from the task list area.
Clear Current Task: Select a task to be cleared in the area, right-click it, and choose Clear
Current Task from the shortcut menu to clear the task from the area.
Issue 09 (2014-12-29)

34
BSC6910 UMTS
LMT User Guide
Pause Current Task: Select an ongoing upload/download task in the area, right-click it, and
choose Pause Current Task from the shortcut menu to pause the current upload/download
task.
Continue Current Task: Select a paused upload/download task in the area, right-click it,
and choose Continue Current Task from the shortcut menu to continue with the current
upload/download task.
Set Display Columns: Right-click the area and choose Set Display Columns from the
shortcut menu to select information to display.
Issue 09 (2014-12-29)

35
BSC6910 UMTS
LMT User Guide
Management of Operation Rights
About This Chapter

This chapter describes the management of operation rights, and provides instruction to manage
user accounts and command groups.
3.1 Concepts Related to Operation Rights Management
This section describes the principles of managing the operation rights of the BSC6910 LMT in
terms of user identity, user rights, and operation time limit.
3.2 Management of User Accounts
This section describes how to manage user accounts of the BSC6910 LMT. Instructions are
provided for creating, modifying, and deleting the external user accounts.
3.3 Management of User Passwords
This section describes how to manage the user password of a BSC6910 LMT user account.
Instructions are provided for defining the login password policies, querying the login password
policies, changing the password of the current user, and changing the password of an external
user account by an authorized user.
3.4 Management of Command Groups
This section describes how to manage command groups. Instructions are provided for querying
the command groups, setting the command group name, and modifying the command group
contents.
Issue 09 (2014-12-29)

36
BSC6910 UMTS
LMT User Guide
3.1 Concepts Related to Operation Rights Management

3.1.1 Principles of Operation Rights Management

The BSC6910 OM subsystem supports operations by multiple users simultaneously. For the
sake of system security, the operation rights are managed and controlled on the basis of the
following aspects:
l
User identity: An operator must enter the correct user name and password to log in to the
system.
Operation rights: Users of different levels are permitted to use different command groups
for menu operations or MML operations.
Operation time limit: It defines the maximum period for a user to perform the operations.
3.1.2 User Password

This section describes the BSC6910 LMT user password in terms of password definition, initial
password setting, and password change.
Definition of User Password

To ensure the system security, each user account has a password. The operator must enter a valid
user name and password to log in to the LMT and then the OMU.
ADMINISTRATOR-level users can set password complexity. For more information refer to
Setting Password Policies.
Default Password
The password of admin is mbsc@com by default.
Initial Password Setting

The password of admin is set during the installation of the OMU application. The admin,
ADMINISTRATOR-level, and authorized CUSTOM-level users can create an external user
account and set the password for that account.
Permissions for Changing Passwords

All users can change their own password. The admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can change the passwords of all external user accounts. Only the admin
user can change the password of the admin account.
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.
Issue 09 (2014-12-29)

37
BSC6910 UMTS
LMT User Guide
3.1.3 Command Group

The BSC6910 provides 15 command groups (G_0 to G_14) with different functions.
Table 3-1 describes these command groups.
Table 3-1 Command groups
Command Group
Function
G_0
Used to query system information such as the user groups,

command groups, logs, NTP, 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 the data configuration information. These

commands usually start with LST.
G_3
Used to configure data, for example, to add a cell.
G_4
Used to query alarm information.
G_5
Used to manage alarms, for example, to manually clear alarms or

to set the 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 the performance, for example, to activate a

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

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

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

or the user plane, for example, to query the trace tasks or to create/
delete/start a trace task.
G_11
Used to modify the settings of the integrated equipment panels.
G_12
Used to manage the software, for example, patch management.
G_13
Used to query the base station information, for example, to query

the BTS attribute or to query the BTS boards.
G_14
Used to manage the base stations, for example, BTS software

management or BTS resetting.
For the operations related to command groups, see 3.4 Management of Command Groups.
Issue 09 (2014-12-29)

38
BSC6910 UMTS
LMT User Guide
3.1.4 User Type

You can log in to the BSC6910 LMT as the Local user and the EMS user.
l
Local user: This type of account (including the default local admin account) is managed
by the BSC6910 LMT independently. That is, you can log in to the BSC6910 when you
install the BSC6910 system or when the OMU is disconnected from the M2000.
EMS user: This type of account is managed by the M2000. They are created, modified,
authenticated, and authorized by the M2000. Only authorized EMS users can log in to the
BSC6910 using the LMT. The authorized EMS users can also log in to the M2000 server
through the M2000 client for BSC6910 operations.
3.1.5 Operation Rights

This section describes the operation rights of the built-in administrator account and other external
user accounts of the BSC6910 LMT.
Built-In Administrator Account

The system has a built-in administrator account, also referred to as super administrator. The user
name is admin and the password is set when the OMU is installed.
This account has all the operation rights and cannot be altered or deleted.
External User Accounts

There are five levels of external user accounts. Each level has distinctive operation rights, as
described in Table 3-2.
Table 3-2 External user accounts
Level
Assigned
Command
Group
Operation Right
Description
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
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
OPERATOR
Issue 09 (2014-12-29)
l System OM
l Data configuration

39
BSC6910 UMTS
LMT User Guide
Level
Assigned
Command
Group
Operation Right
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 the operation rights
CUSTOM
Command
groups are
assigned when
the account is
created.
Specified when the account is

created
Description
The operation
rights can be
changed. Different
CUSTOM-level
users may have
different operation
rights.
NOTE
The admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can add or delete an
external user account.
An authorized CUSTOM-level user can add users only by running MML commands.
3.1.6 Operation Time Limit

This section describes the definition, principle, and setting of the time limits for a user to operate
the BSC6910 LMT.
Definition of Operation Time Limit

The operation time limit defines the maximum time duration for a user to perform the operations.
l
There is no operation time limit for the admin account. The admin user can operate the
system anytime.
The operation time limit of an external user account is specified when the account is created.
If no time limit is set, the operator can operate the system anytime.
Principle of Operation Time Limit

The operation time limit is specified by a combination of date, day, and time.
Table 3-3 provides some examples of operation time limit settings.
Issue 09 (2014-12-29)

40
BSC6910 UMTS
LMT User Guide
Table 3-3 Examples of operation time limit settings

SN
Date
Day
Time
Permitted Operation Time
2008-08-01
to
2009-08-01
Monday to
Friday
8:00:00 to
18:00:00
8:00:00 to 18:00:00 on Monday

through Friday from 2008-08-01
to 2009-08-01
Saturday and
Sunday
Any time on Saturdays and

Sundays
No operation time limit. The

operator can operate the system at
any time.
Permissions to Set the Operation Time Limit

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

This section describes how to manage user accounts of the BSC6910 LMT. Instructions are
provided for creating, modifying, and deleting the external user accounts.
3.2.1 Creating an External User Account

This section describes how to create an external user account. You are required to set the
password, user level, command group (for CUSTOM-level user account only), and operation
time limit for the new user account. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can perform this operation.
Prerequisites
You have logged in to the LMT with an account authorized for this operation.
Procedure
Step 1 Run the ADD OP command to create an external user account.
NOTICE
The added external user account cannot be the same as any of the existing user accounts.
----End
Issue 09 (2014-12-29)

41
BSC6910 UMTS
LMT User Guide
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 upon the next login. Modifications of other attributes take effect
immediately. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users
can perform this operation.
Prerequisites
Procedure
Step 1 Run the MOD OP to modify the attributes of a user account.
----End
3.2.3 Deleting an External User Account

This section describes how to delete an external user account. Only the admin,
ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.
Prerequisites
Context
NOTICE
The admin account 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
3.3 Management of User Passwords

This section describes how to manage the user password of a BSC6910 LMT user account.
Instructions are provided for defining the login password policies, querying the login password
policies, changing the password of the current user, and changing the password of an external
user account by an authorized user.
Issue 09 (2014-12-29)

42
BSC6910 UMTS
LMT User Guide
3.3.1 Defining Login Password Policies

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

This section describes how to query the policies for setting the login passwords.
Prerequisites
You have logged in to the LMT.
Procedure
Step 1 Run the LST PWDPOLICY command to query the policies for setting the 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 from the next login.
Prerequisites
Procedure
Step 1 Click Password on the tool bar of the LMT main page. The Password dialog box is displayed.
Step 2 In the displayed Change Password window, enter the current password in the Old Password
field. Enter the new password in the New Password and Confirm Password fields. Then click
OK.
NOTE
It is recommended that you change the password at your first login and then change the password every three
months.
----End
Issue 09 (2014-12-29)

43
BSC6910 UMTS
LMT User Guide
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 the admin,
Prerequisites
Procedure
Step 1 Run the MOD OP to change the password of an external user account.
----End
3.4 Management of Command Groups

This section describes how to manage command groups. Instructions are provided for querying
the command groups, setting the command group name, and modifying the command group
contents.
3.4.1 Querying a Command Group

There are 15 command groups G_0 to G_14. Only the admin, ADMINISTRATOR-level, and
authorized CUSTOM-level users can query the information about the command groups.
Prerequisites
Procedure
Step 1 Run the LST CCG to query the command groups.
----End
3.4.2 Setting the Command Group Name

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can rename
the command groups.
Prerequisites
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 a command group.
----End
Issue 09 (2014-12-29)

44
BSC6910 UMTS
LMT User Guide
3.4.3 Changing the Commands in a Command Group

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can change
the contents of command groups.
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 09 (2014-12-29)

45
BSC6910 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 BSC6910.
4.1 Concepts Related to MML Commands
This section describes the following concepts related to MML commands: MML commands,
components of the MML command window, data configuration rights, and configuration
rollback.
4.2 Running an MML Command
This section describes how to use MML commands for routine configuration and maintenance.
4.3 Batch Processing MML Commands
This section describes how to run multiple MML commands at a time. By batch processing
MML commands, you can perform a function or operation by using a prepared series of MML
commands.
4.4 Setting MML Parameters
You can set the MML parameters as required.
4.5 Querying the Data Configuration Mode
This section describes how to determine if the data configuration mode of the BSC6910 system
is effective or non-effective.
4.6 Querying Data Configuration Rights
This section describes how to check the control status of the data configuration rights.
4.7 Obtaining Data Configuration Rights
You need to obtain the data configuration rights to perform data configuration, undo/redo
operations on the BSC6910 exclusively, or perform data configuration in batch without being
affected by other users. Only the M2000 users and users of the following levels can obtain the
data configuration rights: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to
use command group G_3 (for data configuration).
4.8 Undoing/Redoing a Data Configuration Action
This section describes how to undo and redo a single data configuration action.
Issue 09 (2014-12-29)

46
BSC6910 UMTS
LMT User Guide
4.9 Undoing/Redoing Multiple Data Configuration Actions

This section describes how to undo and redo multiple data configuration actions.
Issue 09 (2014-12-29)

47
BSC6910 UMTS
LMT User Guide
4.1 Concepts Related to MML Commands

This section describes the following concepts related to MML commands: MML commands,
components of the MML command window, data configuration rights, and configuration
rollback.
4.1.1 Introduction to MML Commands

This section describes the MML commands that can be used for operation and maintenance of
the BSC6910.
An MML command consists of two parts: action and object. For example, ADD OP, wherein
ADD is the action and OP is the object. Table 4-1 describes the actions that can be performed
through MML commands.
Table 4-1 Actions of the MML commands
Issue 09 (2014-12-29)
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
DSP
List
EST
Establish
EXP
Export
FMT
Format
FOC
Obtain
HO
Hand over
48
BSC6910 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 09 (2014-12-29)

49
BSC6910 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
Field
Description
Common
Maintenance(Alt
+C) tab
Displays system responses such as execution results. In

this area, you can save command execution results and
let the system automatically scroll the results by clicking
Save Results and Auto Scroll respectively. You can also
clear all the results by clicking Clear All.
NOTE
l The time displayed at the beginning of the returned result is
the OMU time.
l Click Save Results to save the execution result of the MML
command. Note that the previous operation result will not
be saved.
Operation Record
(Alt+R) tab
Displays commands that have been run.
Help Information
(Alt+N) tab
Displays the help information for a command.
Manual editing area
A text area for manually editing the MML command

script.
Issue 09 (2014-12-29)
NOTE
The Send Time displayed in the operation record is the time of
the LMT PC.

50
BSC6910 UMTS
LMT User Guide
Number
Field
Description
History Command
box
Displays the commands that you have run after logging

in to the system and the relevant parameters.
Command Input
box
Displays in the drop-down list all the MML commands

available on the system. You can select an MML
command from the drop-down list or type in an MML
command for execution.
Parameter area
Displays the parameters of the current command. You

need to set parameter values in the boxes before
executing the command. The parameters in red are
mandatory, and those in black are optional.
NOTE
For details of the MML commands and parameters, see the MML online help.
4.1.3 Data Configuration Rights

The management of the data configuration rights enables only one user to perform BSC6910
data configuration through the LMT or the M2000 at a time.
In case of conflicts during data configuration, the OMU manages the configuration rights as
follows:
l
All users have data configuration rights by default. Data configuration rights are not limited.
After a user obtains data configuration rights by running the LCK CMCTRL command,
data configuration rights are exclusive to this user.
After a user releases data configuration rights by running the ULK CMCTRL command,
data configuration rights are available to all users.
When a user occupies the data configuration rights for a long time, administrators can check
with the user. If the user is not performing data configuration, the administrators can run
the FOC CMCTRL command to release the data configuration rights manually.
If the user with the data configuration rights exits the LMT, the data configuration rights
are released automatically. In this case, all users have data configuration rights.
4.1.4 Data Configuration Rollback

Data configuration rollback is performed to restore the system to a previous configuration status.
If a data configuration action fails to achieve the expected result or even causes equipment or
network problems, you can perform rollback to restore the configurations so that normal
operation of the BSC6910 is restored as early as possible.
Definition of Configuration Rollback

During data configuration, a rollback point is used to mark a data configuration action.
You can select a rollback point corresponding to the expected data configuration status,
permitting a rollback to any point of the configuration. (You can run the ADD
ROLLBACKPOINT command to configure the rollback point.)
Issue 09 (2014-12-29)

51
BSC6910 UMTS
LMT User Guide
Operations of Configuration Rollback
NOTICE
Data configuration rollback cannot be performed if users have not obtained data configuration
rights (with ULK CMCTRL), or the quick configuration mode is enabled (with SET
QUICKCFG), or batch configuration is performed (with RUN BATCHFILE).
Data configuration rollback consists of the following types of operations:
l
Undo a single configuration action:This operation is performed to undo a previous

configuration action. It is applicable to the latest 10 effective configuration actions.
Redo a single configuration action:This operation is performed to redo a previously undone

configuration action. It is applicable to the latest 10 undone configuration actions.
Undo multiple configuration actions:This operation is performed to undo multiple

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

configuration actions that were undone previously. After the redo operation, the system
restores either the configuration status at the specified rollback point or the final
configuration status before undoing the configurations.
4.2 Running an MML Command

This section describes how to use MML commands for routine configuration and maintenance.
Prerequisites
Context
You can run an MML command in one of the following ways:
l
Entering an MML command in the Command Input box
Selecting a previously-executed command from the History Command box
Selecting an MML command from the MML Command navigation tree
Copying the MML command script to the Manual Editing area
Entering an MML command in the Command Input box
Procedure
Issue 09 (2014-12-29)
1.
Enter an MML command in the Command Input box. When you enter the command,
you can also select the required command from the drop-down list of suggested
commands.
2.
Press Enter or click Assist to display the parameters associated with the command.
3.
Specify the parameter values to run the command.

52
BSC6910 UMTS
LMT User Guide
4.
l
Press F9 or click Exec to run the command. The result is displayed in the Common
Maintenance tab page.
Selecting a previously-executed command from the History Command box

1.
Select a previously-executed command from the drop-down list of history commands.

(Press F7 or click
to select the previous command. Press F8 or click
select the next command.)
to
2.
(Optional) Change the parameter values in the command parameter area.
3.
Selecting an MML command from the MML Command navigation tree

1.
Select an MML command from the MML Command navigation tree, and doubleclick the command.
2.
Specify the parameter values to run the command.
3.
Press F9 or click Exec to run the command. The result is displayed on the Common
NOTE
l The parameters displayed in red are mandatory, and those in black are optional.
l Place the cursor on the parameter value input box to read the general information about the
parameter.
l If the execution of the command fails, the result is displayed in the Common Maintenance tab
page in red.
Copying the MML command script to the Manual Edit area

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

This section describes how to run multiple MML commands at a time. By batch processing
MML commands, you can perform a function or operation by using a prepared series of MML
commands.
Context
A batch file (also called data script file) is a plain text file. It contains a group of command scripts
for a special task. The system automatically runs the commands in sequence.
Batch running MML commands consists of immediate batch processing and scheduled batch
processing.
l
Immediate batch processing: The batch file is run immediately.
Scheduled batch processing: The batch file is automatically run at a moment of a day
specified by an operator in advance.
Issue 09 (2014-12-29)

53
BSC6910 UMTS
LMT User Guide
4.3.1 Immediate Batch Processing of MML Commands

This section describes how to enable the system to immediately run a batch of MML commands
at a time.
Prerequisites
l
You have obtained the data configuration rights. For details, see 4.7 Obtaining Data
Configuration Rights.
Procedure
Step 1 Click Batch on the LMT main page. The Batch tab page is displayed.
Step 2 Click New and enter the batch commands in the editing area, or click Open... to select the preedited batch file.
Step 3 Click Set... to set the parameters for running the MML commands.
Step 4 Click Go to enable the system to start running the commands.
NOTE
You can select Execution Type. You are advised to select Prompt when Error Occurs, which is selected by
default.
----End
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 /mbsc/
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:
Issue 09 (2014-12-29)

54
BSC6910 UMTS
LMT User Guide
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.
5.
Enter the cd /mbsc/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.
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 syntax of the MML commands before running a batch of
MML script commands. This function helps locate incorrect commands, improving maintenance
efficiency.
Prerequisites
l
A batch file is ready.
Context
The syntax check checks the following types of error:
Issue 09 (2014-12-29)

55
BSC6910 UMTS
LMT User Guide
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. Edit MML commands in the command editing area.
NOTE
You can click Open... to open an edited batch file.
Step 2 Click Analyze Syntax to check syntax of the batch file.

NOTE
l If no error exists, a Prompt dialog box is displayed showing no syntactical error. If error exists, a
Result Information dialog box is displayed showing the line number and error reason.
l You can go to the command line with syntactical error by double-clicking the information in the Result
Information dialog box.
l After Analyze Syntax is executed, a
mark is displayed in front of command lines with syntactical
error in the batch file. If you move the mouse to the

is displayed.
mark, information showing syntactical error
l You can check an MML command line in the batch file for error analysis by selecting it, right-clicking
it, and choosing Analyze Current Line from the shortcut menu.
Step 3 In the Result Information dialog box, click Save As... to save the result.
Step 4 Click Close to end the operation.
----End
Follow-up Procedure
You can clear all syntactical analysis marks in the batch file by right-clicking the batch file area
and choosing Clear Analyze Mark from the shortcut menu.
4.4 Setting MML Parameters

You can set the MML parameters as required.
Prerequisites
Procedure
Step 1 Click Settings on the Common Maintenance tab page in the MML window. The Settings
dialog box is displayed, as shown in Figure 4-2.
Issue 09 (2014-12-29)

56
BSC6910 UMTS
LMT User Guide
Figure 4-2 Setting MML Parameters
Step 2 Set the parameters as required.

Step 3 Click OK to save the settings.
----End
4.5 Querying the Data Configuration Mode

This section describes how to determine if the data configuration mode of the BSC6910 system
is effective or non-effective.
Prerequisites
Context
In effective mode, the data configured takes effect immediately on the BSC6910 system.
In non-effective mode, the data configured for the subrack takes effect only in the OMU and not
on the subrack. In this case, you can run the SET CFGDATAEFFECTIVE command to set
the 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.
When the BSC6910 system is in non-effective mode, you cannot query, compare, or perform
CRC check on the data between the host and the OMU. In addition, you cannot configure the
host data of the subrack.
Issue 09 (2014-12-29)

57
BSC6910 UMTS
LMT User Guide
When the BSC6910 system are in non-effective mode, license verification is not performed.
When the BSC6910 system is switched 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 is not allowed.
NOTE
You can query the data configuration through menu operations or through MML commands.
Procedure
l
Through menu operations

1.
On the main page of the LMT, check the configuration mode of the BSC6910 system,
as shown in Figure 4-3.
Figure 4-3 Subrack data configuration mode
Through MML commands

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

This section describes how to check the control status of the data configuration rights.
Prerequisites
Context
You can query the control status of the data configuration rights through menu operations or
through MML commands.
Procedure
l

1.
The status of data configuration rights is displayed in the top right corner of the LMT
main page.

1.
Run the LST CMCTRL command to check the status of the data configuration rights.
----End
Issue 09 (2014-12-29)

58
BSC6910 UMTS
LMT User Guide
4.7 Obtaining Data Configuration Rights

You need to obtain the data configuration rights to perform data configuration, undo/redo
operations on the BSC6910 exclusively, or perform data configuration in batch without being
affected by other users. Only the M2000 users and users of the following levels can obtain the
data configuration rights: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to
use command group G_3 (for data configuration).
Prerequisites
l
By default,all users can perform data configuration of the BSC6910 through the LMT or
M2000.
Only one user has the data configuration rights at a time. You can run the LCK
CMCTRL command to obtain the data configuration rights.
After the data configuration is complete, you can release the data configuration rights by
running the ULK CMCTRL command. In this way, another user can run the LCK
CMCTRL command to obtain the data configuration rights.
If the user with the data configuration rights exits the LMT, the data configuration rights
are released automatically. In this case, another user can also run the LCK CMCTRL
command to obtain the data configuration rights.
Context
Procedure
Step 1 Check whether the data configuration rights are assigned to another user. For details, see 4.6
Querying Data Configuration Rights.
l If no user is currently assigned with the data configuration rights, go to Step 2.
l If the data configuration rights are already assigned to another user, go to Step 2 after the
user releases the data configuration rights.
Step 2 Run the LCK CMCTRL command to obtain the data configuration rights.
NOTE
After the BSC6910 data configuration rights are already granted to one LMT user, other LMT users cannot
obtain it. If you are the admin or ADMINISTRATOR-level user, you can run the FOC CMCTRL
command to release the locked data configuration rights.
----End
4.8 Undoing/Redoing a Data Configuration Action

This section describes how to undo and redo a single data configuration action.
Prerequisites
l
Issue 09 (2014-12-29)

59
BSC6910 UMTS
LMT User Guide
You have obtained configuration rights (by running the LCK CMCTRL command).
The quick configuration mode is disabled by running the SET QUICKCFG command.
No batch commands were performed.
This task can be performed to fine-tune the configuration data. It cannot be used when the
quick configuration mode is enabled or when batch MML commands are run, because the
operation of undoing or redoing a configuration action will decrease the efficiency of
running the MML commands.
This function can be performed only with the exclusive operation rights to prevent
misoperations.
This function does not apply to all MML commands. If you run a command that does not
support this function, the Undo and Redo buttons on the top of the LMT window becomes
unavailable. In this case, the previous configuration operations that support this function
cannot be undone or redone. For the lists of commands that support undoing or redoing a
configuration action, see the descriptions of the ADD ROLLBACKPOINT command.
Undo a single configuration action: This operation is performed to undo a previous

configuration action. It is applicable to the latest 10 effective configuration actions.
Redo a single configuration action: This operation is performed to redo a previously undone
configuration action. It is applicable to the latest 10 undone configuration actions.
Undoing a single configuration action
Context
Procedure
1.
You can undo the latest configuration action in either of the following ways:
Click Undo on the LMT toolbar.
Run the BEG UNDO command.
2.
l
To undo multiple actions, repeat Step 1.
Redoing a single configuration action

1.
You can redo an undone action in either of the following ways:

Click Redo on the LMT toolbar.
Run the BEG REDO command.
2.
To redo multiple 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.
Prerequisites
l
You have obtained configuration rights (by running the LCK CMCTRL command).
The quick configuration mode is disabled by running the SET QUICKCFG command.
Issue 09 (2014-12-29)

60
BSC6910 UMTS
LMT User Guide
No batch commands are performed.
This task can be performed to fine-tune the configuration data. It cannot be used when the
quick configuration mode is enabled or when batch MML commands are run, because the
operation of undoing or redoing multiple configuration actions will decrease the efficiency
of running the MML commands.
This function can be performed only with the exclusive operation rights to prevent
misoperations.
This function does not apply to all MML commands. If you run a command that does not
support this function after you set the rollback point by running the ADD
ROLLBACKPOINT command, the rollback point is invalidated. That is, you cannot undo
multiple configuration actions with the configured rollback point. In this case, you need to
remove the configured rollback point and configure a new one. For the lists of commands
that support undoing or redoing multiple configuration actions, see the descriptions of the
ADD ROLLBACKPOINT command.
Undo multiple configuration actions: This operation is performed to undo multiple

configuration actions that took effect after a specified rollback point. After the undo
operation, the system rolls back to the configuration status at the specified rollback point.
Redo multiple configuration actions: This operation is performed to redo the multiple
configuration actions that were undone previously. Through this operation, you can roll
back the system to the configuration at a specified rollback point or to the configuration
before the multiple configuration actions were undone.
Context
NOTE
The initial rollback point is the first rollback point set by the user. The final rollback point is set
automatically when the latest configuration command is successfully run. A maximum of 10,000
configuration commands can be undone between the initial and final rollback points. If the system finds
more than 10,000 commands between the two rollback points, it does not undo the commands and reports
a failure message.
You can set a maximum of five rollback points. If you release the configuration rights, the OMU active
work area clears the information about the rollback stack and rollback points.
Procedure
Step 1 To undo/redo configuration actions in batches, you can use the ADD ROLLBACKPOINT
command to set the rollback points as required.
Step 2 Run the BEG ROLLBACK command to start the rollback.
Step 3 Run the BEG FORWARD command to resume the configurations that are rolled back.
----End
Issue 09 (2014-12-29)

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

This chapter describes how to manage BSC6910 alarms/Events through the LMT. Alarm/Event
management allows you to analyze alarms/events more efficiently and facilitates
troubleshooting.
5.1 Concepts Related to Alarm Management
This section describes the basic concepts related to the 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 details of alarms. They are collected by the OMU and stored in
the OMU database. You need to establish limitations on the number and storage time of alarm
logs to minimize storage requirements on the hard drive.
5.3 Managing the Alarm Filter
This section describes how to filter one or more alarms. The alarms that meet the filtering
conditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannot
be queried through the LMT or M2000. You can specify the conditions for filtering the alarms
on the LMT.
5.4 Managing the Filter of Derived Alarms
A derived alarm is caused by a root fault. BSC6910 supports filtering of the derived alarms. The
derived alarms are not reported to the LMT by default. Unless otherwise specified, the derived
alarms are not saved on the OMU and cannot be queried through the LMT.
5.5 Monitoring Alarms
In the Alarm Browse window of the LMT, you can monitor the alarm information sent to the
LMT in real time.
5.6 Managing the Alarm Box
The BSC6910 uses a universal alarm box of Huawei to provide audible and visual indications
when an alarm is reported.
Issue 09 (2014-12-29)

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

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

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

example, board failure or link failure. Fault alarms are of higher severity
than event alarms. The fault alarms are classified into active and cleared
alarms according to the fault status.
Event alarm
Alarms of predefined events during the operation of the devices. The alarm
reflects the system condition (for example, congestion) during a specific
period, which is not necessarily a fault. Some event alarms are generated
repeatedly and regularly. Event alarms cannot be classified into active and
cleared alarms.
The fault alarms are classified into active and cleared alarms according to the fault status.
l
Cleared alarm: If a fault is rectified, the corresponding alarm becomes a cleared alarm.
Active alarm: If the fault is not 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 cleared, the alarm remains active. After the congestion is
cleared, the alarm is cleared.
NOTE
l The record of a cleared alarm is stored in the OMU database and can be queried.
l In scenarios where equipment is being deployed, commissioned, upgraded, swapped, cut over, or the
capacity of a base station is expanded, operations cause a great number of alarms to be reported. There
is no special mechanism to handle such alarms. Large in number and short in existence period, these
alarms make real fault alarms inconspicuous and therefore disturb normal network monitoring. To
solve the problem discussed above, Huawei puts forward the concept of "engineering alarms". With
the concept, alarms in scenarios of engineering maintenance are identified and handled as special cases.
In this way, delicacy management of alarms is implemented and fault OM efficiency of the operator
is improved.
5.1.2 Alarm Severity

The BSC6910 alarm severity indicates the severity of a fault. The fault alarms and event alarms
can be classified into four severities: critical, major, minor, and warning.
Issue 09 (2014-12-29)

63
BSC6910 UMTS
LMT User Guide
Table 5-2 describes the four severities of alarms.

Table 5-2 Alarm severities
Alarm Severity
Definition
Handling
Requirement
Critical
Reporting faults that affect the services provided

by the system. These alarms need to be handled
immediately even during non-working hours. For
example, some equipment or resource breaks
down.
Handle the faults

immediately to
avoid service
outage.
Major
Reporting faults that affect the Quality of Service

(QoS). These alarms need to be handled during
working hours. For example, the performance of
some equipment or resource deteriorates.
Handle the faults in

time. Otherwise, the
system may fail to
perform some major
functions.
Minor
Reporting faults that 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 clear
the obsolete history alarms.
Find and rectify any

potential fault in
time.
Warning
Reporting faults that are potential threats to the

system services. These alarms need to be handled
according to specific situations. For example,
OMU startup alarm.
Investigate the
problem and
resolved as required.
5.1.3 Alarm-Event Type

The alarms can be classified into 15 types based on different event type.
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
Trunk: alarms related to the trunk system, including trunk circuits and trunk boards
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
BSC6910 host and the OMU
QoS: alarms related to QoS
Integrity: alarms generated when information is repeated, lost, distorted, disordered, or

unexpected
Issue 09 (2014-12-29)

64
BSC6910 UMTS
LMT User Guide
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 the BSS alarm flags that include: to-alarm-box flag, shield flag, modification
flag, and alarm cleared flag.
To-Alarm-Box Flag
The to-alarm-box flag controls whether the alarms are reported to the alarm box or not.
l
Report
In Report status, the LMT drives the alarm box to enable the audio and visual alarm
function.
Not report
In Not report status, the alarm box will not be activated when an alarm is generated or when
the alarm status changes.
NOTE
The to-alarm-box flag is used for fault alarms only. Event alarms are not reported to the alarm box.
Whether alarms are reported to the alarm box depends on the settings of to-alarm-box flag and
the shield severity of the alarm box. Alarms are reported to the alarm box only when the toalarm-box flag is set to Report and the alarm severity is greater than or equal to the shield
severity of the alarm box.
Shield Flag
The shield flag is set to shield the alarm information not required. The shield flag can be set to
Shielded or Unshielded.
l
Shielded
A board does not report the alarms whose shield flags are set to Shield to the network
manager or the alarm box. The server does not save the logs of such alarms.
Unshielded
A board reports the alarms whose shield flags are set to Shield to the network manager or
the alarm box. The server saves the logs of such alarms.
Modification Flag
The modification flag records the modification status of alarm configuration information. The
status of modification flag is Modified or Unmodified.
l
Issue 09 (2014-12-29)
Modified
65
BSC6910 UMTS
LMT User Guide
After the alarm configuration is modified through a modification command, the

modification flag is set to Modified.
l
Unmodified
When an alarm is in default setting or recovered to the default setting, the modification flag
is set to Unmodified.
Alarm Cleared Flag

The alarm cleared flag indicates whether a fault alarm is cleared or not. The status of the alarm
cleared flag is Not Cleared or Cleared.
l
Not Cleared
The fault alarm is not cleared.
Cleared
A recovery alarm is received and the fault alarm is cleared.
5.1.5 Alarm Box

BSC6910 uses the Huawei universal alarm box. The BSC6910 alarm box provides audible and
visual indications based on the alarm severity. It is optional and the BSC6910 can be configured
with only one alarm box. For details, see the documents delivered with the alarm box.
Figure 5-1 shows the alarm box.
Figure 5-1 Alarm box
When the BSC6910 reports a fault alarm to the LMT, the alarm box provides 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 manually stop the
sound on the LMT.
Issue 09 (2014-12-29)

66
BSC6910 UMTS
LMT User Guide
NOTE
The alarm box does not provide any indication for event alarms.
5.2 Managing Alarm Logs

Alarm logs are used to record details of alarms. They are collected by the OMU and stored in
the OMU database. You need to establish limitations on the number and storage time of alarm
logs to minimize storage requirements on the hard drive.
5.2.1 Setting Storage Conditions of Alarm Logs

This section describes how to set the maximum number of alarm logs and the time limitations
of the logs that can be stored in the OMU database. Only the admin, OPERATOR-level,
Prerequisites
Procedure
Step 1 Run the SET ALMCAPACITY command to set the maximum number of alarm logs and the
time limitation of storing the logs.
----End
5.2.2 Querying Storage Conditions of Alarm Logs

This section describes how to query the maximum number of alarm logs and the time limitations
of the logs that can be stored in the OMU database.
Prerequisites
Procedure
Step 1 Run the LST ALMCAPACITY command to set the maximum number of alarm logs and the
time limitations for storing the logs.
----End
5.3 Managing the Alarm Filter

This section describes how to filter one or more alarms. The alarms that meet the filtering
conditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannot
be queried through the LMT or M2000. You can specify the conditions for filtering the alarms
on the LMT.
Issue 09 (2014-12-29)

67
BSC6910 UMTS
LMT User Guide
5.3.1 Creating an Alarm Filter

This section describes how to create an alarm filter. Only the admin, OPERATOR-level,
Prerequisites
Procedure
Step 1 Run the ADD OBJALMSHLD command to create an alarm filter. The successfully added alarm
filter takes effect immediately.
NOTE
l The name of the new alarm filter cannot be a duplicate of an existing one. Otherwise, the filter cannot
be created.
l A maximum of 100 alarm filters can be created in each BSC6910.
Step 2 Run the LST OBJALMSHLD command and enter the parameters to query whether the alarm
filter is successfully created.
----End
5.3.2 Deleting an Alarm Filter

If you do not want to filter an alarm through the BSC6910, delete the filters related to this alarm.
Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level
users can perform this operation.
Prerequisites
Procedure
Step 1 Run the LST OBJALMSHLD command to check whether the alarm filter to be deleted exists.
If...
Then...
The filter is listed,
Go to Step 2.
The filter is not listed,
End this operation.
Step 2 Run the RMV OBJALMSHLD command. Select the Object Type and set other parameters as
required to delete an alarm filter.
----End
5.3.3 Querying an Alarm Filter

This section describes how to query the specific alarm filtering conditions.
Issue 09 (2014-12-29)

68
BSC6910 UMTS
LMT User Guide
Prerequisites
Procedure
Step 1 Run the LST OBJALMSHLD command, and specify the Query Mode to query the alarm
filtering conditions.
----End
5.4 Managing the Filter of Derived Alarms

A derived alarm is caused by a root fault. BSC6910 supports filtering of the derived alarms. The
derived alarms are not reported to the LMT by default. Unless otherwise specified, the derived
alarms are not saved on the OMU and cannot be queried through the LMT.
5.4.1 Setting the Filter of Derived Alarms

This section describes how to set the filter of the BSC6910 derived alarms. You can set the filter
of the derived alarms to ON or OFF. Only the admin, OPERATOR-level, ADMINISTRATORlevel, and authorized CUSTOM-level users can perform this 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 filter of the derived alarms.
----End
5.4.2 Querying the Filter of Derived Alarms

This section describes how to query the filter status of the BSC6910 derived alarms.
Prerequisites
Procedure
Step 1 Run the LST ALMML command to query the status of the alarm filter switch.
----End
Issue 09 (2014-12-29)

69
BSC6910 UMTS
LMT User Guide
5.5 Monitoring Alarms

In the Alarm Browse window of the LMT, you can monitor the alarm information sent to the
LMT in real time.
5.5.1 Browsing Alarm/Event

This section describes how to browse fault alarms and event alarms on the LMT. Fault alarms
and event alarms are displayed in the Browse Alarm/Event tab page of the Alarm/Event
window. The alarm information provides the running status of the system in real time.
Prerequisites
Procedure
Step 1 Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page is displayed.
The Normal Alarm, Event, and Engineering alarm tab pages are displayed under the Browse
Alarm/Event tab.
Step 2 Browse alarms in the Browse Alarm/Event tab page.
Step 3 To view the details of an alarm, double-click it. The Detail dialog box carrying the detailed
information about the alarm is displayed.
Step 4 To save an alarm record, select the alarm record first. Then right-click it and choose Save
Select from the shortcut menu. To save all alarm records, right-click anywhere in the alarm
display area and choose Save All from the shortcut menu; or directly click Save All.
NOTE
You can drag the rows in the Browse Alarm/Event tab page to rearrange the row order. The row order in
the Browse Alarm/Event tab page will be the same as the order before you closed the tab page within the
Cookie validity period.
----End
5.5.2 Querying the Alarm/Event Log

This section describes how to query alarm history from the OMU database. Using this function,
you can review the past performance and condition of the system.
Prerequisites
Context
You can set the following query conditions:
l
Issue 09 (2014-12-29)
Alarm Type
70
BSC6910 UMTS
LMT User Guide
Alarm Severity
Alarm Time
Maintenance Mode Alarm Flag
Return Amount
Cleared Time
NodeB Type
Alarm-Managed Objects
Alarm ID
Alarm Serial No.
You can query alarm logs through menu operations or through MML commands.
Procedure
l

1.
Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page is
displayed.
2.
In the Query Alarm/Event Log tab page, click Query Setting. The Log
Condition dialog box is displayed.
3.
To set the query conditions anew, click Reset. If you only need to set the NodeB type
anew, click Filter By NodeB and click Filter.
NOTE
Click Filter to reset the query conditions.
4.
Click Query. The query results are displayed in the Result area.
5.
To learn more about an alarm, double-click it. The displayed Detail dialog box shows
the details of the alarm.
6.
To save an alarm record, select the alarm record first. Then right-click it and choose
Save Select from the shortcut menu. To save all alarm records, right-click anywhere
in the alarm display area and choose Save All from the shortcut menu; or directly click
Save All.
NOTE
You can drag the rows in the Query Alarm/Event Log tab page to rearrange the row order.
The row order in the Query Alarm/Event Log tab page will be the same as the order before
you closed the tab page within the Cookie validity period.

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

This section describes how to query the handling suggestions of an alarm.
Prerequisites
Issue 09 (2014-12-29)

71
BSC6910 UMTS
LMT User Guide
Context
The LMT provides the following help information for all alarms:
l
Alarm meaning
Alarm impact
System action
Solution
Procedure
Step 1 In the Alarm/Event tab page, double-click an alarm in the Browse Alarm/Event or Query
Alarm/Event Log tab page. The Detail dialog box is displayed.
Step 2 In the Detail dialog box, click Solution.... The online help window is displayed.
NOTE
You can also click to select an alarm. Then right-click the alarm and choose Solution from the shortcut
menu to view the online help of this alarm.
Step 3 Find the handling suggestions or other required information in the online help.
Step 4 To exit the online help, click the Close button of the 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 search criteria:
l
Alarm ID: indicates the ID range of alarms to be queried. If the setting is successful, query
results show configuration of alarms/events only in the range.
Alarm Severity: indicates the Alarm Severity. If the setting is successful, query results
show configuration of alarms/events of only the specified severity. If none of the alarm
severities is selected, query results show configuration of alarms/events of all severity
options.
Modification Flag: indicates the Modification Flag. If the setting is successful, query
results show configuration of alarms/events matching the specified modification flag. If
All is selected, query results show configuration of alarms/events whose Modification
Flag is set to Unmodified or Modified.
Shield Flag: indicates the Shield Flag. If the setting is successful, query results show
configuration of alarms/events matching the specified shield flag. If All is selected, query
results show configuration of alarms/events whose Shield Flag is set to Shielded or
Unshielded.
To Alarm Box Flag: indicates the To Alarm Box Flag. If the setting is successful, query
results show configuration of alarms/events matching the specified flag. If All is selected,
Issue 09 (2014-12-29)

72
BSC6910 UMTS
LMT User Guide
query results show configuration of alarms/events whose To Alarm Box Flag is set to
Report or Not Report.
l
Return Amount: indicates the number of alarms to be returned in query results.
Procedure
Step 1 Click Alarm on the LMT main page. The Alarm tab page is displayed.
Step 2 Click the Query Alarm Configuration tab and click Query Setting. The Alarm Configuration
Condition dialog box is displayed for you to set the search criteria.
Step 3 Set the search criteria as required.
Step 4 Click Query. Query results are displayed in the Result area.
NOTE
If you need to modify alarm configuration, choose a configuration item and click Modify Alarm
Configuration, or right-click in the Result area and choose Modify Alarm Configuration from the
shortcut menu.
----End
5.5.5 Filtering Fault Alarm/Event

This section describes how to filter alarms by sites and specific filter options on the Browse
Alarm/Event tab page. All the alarms, however, are reported to the LMT and saved on the OMU.
Prerequisites
Procedure
Step 1 Click Alarm/Event on the LMT. The Alarm/Event tab page is displayed.
Step 2 On the Browse Alarm/Event tab page, click Filtrate Setting. The Set Alarm Filtering
Conditions dialog box is displayed.
Step 3 In the Set Alarm Filtering Conditions dialog box, specify Alarm Source or Alarm ID. Then
click OK. Alarms that meet the specified conditions are displayed.
NOTE
l You can select BSC and NodeB for Alarm Source Type. If you select NodeB for Alarm Source Type,
alarms related to the NodeB will be generated. These alarms are not generated by the NodeB but the BSC.
l Setting Alarm Source Type displays alarm sources of the selected type in the box below.
l You can manually type an alarm source in Selected Source.
l You can manually type an alarm source in Selected Source after selecting 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 the display attributes for alarms and events in the Setting dialog
box. After you set the display attributes, the settings take effect on alarms/events on the following
Issue 09 (2014-12-29)

73
BSC6910 UMTS
LMT User Guide
tab pages: Browse Alarm/Event, Query Alarm/Event Log, and Query Alarm/Event
Configuration.
Prerequisites
Context
You can set the following display attributes for alarms/events:
l
Set alarm colors
Set alarm table columns
Show/Hide tips
Procedure
Step 1 Click Alarm/Event on the LMT. The Alarm/Event tab page is displayed.
Step 2 Click Setting on the upper right of the Alarm/Event tab page. The Setting dialog box is
displayed.
Step 3 In the Setting dialog box, set Color, Set Table Columns, Auto-deletion, and Tips.
l Color: You can set the color of alarms/events with the following severities: Critical,
Major, Minor, Warning, and Cleared.
l Auto-deletion: You can select Enable auto-deletion and specify the interval in the box
below.
l Tips: Tips provides two options: Enable and Disable. If you have selected Enable, the
details about an alarm/event are displayed when you put the cursor at the alarm/event. If you
have selected Disable, the details about an alarm/event are displayed only when you doubleclick the alarm/event.
l Set Table Columns: You can specify the information to be displayed in the alarm table. The
following table describes definitions of all fields for an alarm.
Issue 09 (2014-12-29)
Field
Name
Description
Serial No.
Indicates the alarm generating sequence. This parameter uniquely

identifies an alarm in an alarm log.
ID
For a product, the alarm ID uniquely identifies an alarm.
Name
Indicates the alarm name. For a product, the alarm name is unique and has
a one-to-one mapping with the alarm ID.
Severity
Indicates the impact of an alarm on services.
Event Type
Alarms are classified based on alarm contents.
Alarm
Source
Indicates the type of the NE that reports the alarm.
Type
Provides two options: Alarm and Event.

74
BSC6910 UMTS
LMT User Guide
Field
Name
Description
Maintenanc
e Mode Flag
Indicates the activity during which the alarm is generated. For example,
capacity expansion or upgrade.
Raised Time
Indicates the time when an alarm is generated.
Changed
Time
Indicates the time when an alarm is changed. If an alarm is changed, the

values of Serial No. of the root alarm and Severity are changed.
Cleared
Time
Indicates the time when the alarm is cleared.
Common
A multi-mode product comprises common components, such as power

supply and temperature control devices. Alarms generated by these
common components are called common alarms.
Special Info
Indicates special information that is reported as required.
Location
Info
Indicates information for fault location.
Root CSN
Indicates the serial number of the root alarm.
Cleared
Type
Cleared types for alarms are specified as follows:

l Normal clear: Alarms are normally cleared.
l Reset clear: After the system is restarted, the active 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 for the non-cleared
correlated alarm, the fault management system automatically clears the
correlated alarm while normally reporting the root alarm. As a result,
the correlated alarm is not displayed on the alarm window.
l Override clear: Earliest alarms are removed to free space. If the earliest
alarm is an active alarm, the NE automatically clears the alarm.
l State switchover clear: If a device switches from one state to another
state, the active alarm reported by the device in the former state is
automatically cleared, and the device in the latter state reports the alarm
again.
Sync Serial
No.
Indicates the sequence for sending alarm report messages. The

synchronization serial number ensures synchronization between the EMS
and NEs. The alarm generating packet and alarm clearing packet have
different synchronization serial numbers.
----End
Issue 09 (2014-12-29)

75
BSC6910 UMTS
LMT User Guide
5.5.7 Manually Clearing an Alarm/Event

If a reported alarm can be neglected or the corresponding fault has been rectified, you can
manually set the alarm to a cleared alarm. Only the admin, the OPERATOR-level,
ADMINISTRATOR-level, or authorized CUSTOM-level operators can perform this operation.
Prerequisites
Procedure
l

1.
Click Alarm/Event and select an uncleared alarm that needs to be cleared in the
Browse Alarm/Event or the Query Alarm/Event Log tab. 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 perform the operation through the shortcut menu. Click Alarm/Event and right-click an
uncleared alarm that needs to be cleared in the Browse Alarm/Event or Query Alarm/Event Log tab.
Choose Clear Alarm from the shortcut menu.

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

This section describes how to delete alarms/Events when browsing alarms or querying alarm/
Event logs.
Prerequisites
Procedure
Step 1 In 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 as
required. Table 5-3 describes the functions of the buttons.
Table 5-3 Functions of the buttons
Issue 09 (2014-12-29)
Option
Description
Delete Selected Cleared

Alarms
Deletes the cleared alarms that are selected in the active window.
Available in the Browse Alarm/Event or Query Alarm/Event
Log tab page.

76
BSC6910 UMTS
LMT User Guide
Option
Description
Delete All Cleared

Alarms
Deletes all the cleared alarms in the active window. Available in

the Browse Alarm/Event or Query Alarm/Event Log tab page.
----End
5.5.9 Refreshing the Alarm/Event Window

This section describes how to manually refresh the alarm information when you browse or query
the alarms.
Prerequisites
Procedure
Step 1 In the Browse Alarm/Event tab page or Query Alarm/Event Log tab page under the Alarm/
Event tab, click Refresh or choose Refresh from the right-click menu to refresh the alarm
information.
NOTE
l On the Browse Alarm/Event tab page, the alarms are displayed in real time. Cleared alarms are
displayed in gray and new alarms are added as the window is automatically refreshed. When you refresh
the window manually, the cleared alarms are removed from the Browse Alarm/Event window.
l On the Query Alarm/Event Log tab page, the alarms are not displayed in real time. When you manually
refresh the window, the alarms on the window are updated according to the previous querying
conditions.
----End
5.6 Managing the Alarm Box

The BSC6910 uses a universal alarm box of Huawei to provide audible and visual indications
when an alarm is reported.
5.6.1 Querying Alarm Box Information

This section describes how to query the version information of the alarm box and the active
alarms that drive the alarm box.
Prerequisites
l
The BSC6910 is connected to the alarm box.
The Convert Management System is started, and it communicates with the OMU normally.
Issue 09 (2014-12-29)

77
BSC6910 UMTS
LMT User Guide
Procedure
l
Run the LST BOXVER command to query the version information of the alarm box.
Run the LST BOXALM command to query the active alarms that drive the alarm box.
----End
5.6.2 Querying Number of Alarms with Different Severities

This section describes how to query the number of alarms corresponding to a specific severity
indicated by an alarm LED.
Prerequisites
l
Context
When the LMT receives one or more fault alarms from the BSC6910, the corresponding LED
on the alarm box flashes. The flashing LED, however, does not indicate the number of alarms
of a specific severity.
Procedure
Step 1 Run the LST BOXLGT command to query the number of the alarms of a specific severity.
----End
5.6.3 Operating the Alarm Box

This section describes how to reset the alarm box, stop the alarm sound, and turn off the alarm
LED.
Prerequisites
l
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
Issue 09 (2014-12-29)

78
BSC6910 UMTS
LMT User Guide
5.6.4 Querying the Alarm Box Filter Level

This section describes how to query and set the filter level for reporting alarms to the alarm box.
All alarms with a severity higher than the filter level are reported to the alarm box. Otherwise,
the alarms are not reported.
Prerequisites
l
Context
Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level
operators can set alarm filter level.
Procedure
l
Run the LST ALMSCRN command to query the filter level on the alarm box.
Run the SET ALMSCRN command to set the filter level on the alarm box.
----End
Issue 09 (2014-12-29)

79
BSC6910 UMTS
LMT User Guide
6 Log Management
Log Management
About This Chapter

This chapter describes how to manage the BSC6910 logs through the LMT. Log files can be
saved in .txt and .csv formats. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can manage the logs.
6.1 Log Types
The logs are classified into operation logs, security logs, and running logs.
6.2 Querying Log Storage Conditions
This section describes how to query the conditions for storing the operation logs and security
logs, including the time limit and storage capacity of the logs.
6.3 Setting Log Storage Conditions
This section describes how to set the conditions for storing the operation and security logs,
including the time limit and the storage capacity. The OMU database automatically deletes an
entry that has crossed the specified time limit or the earliest entry when the number of saved
logs exceeds the specified capacity.
6.4 Querying Operation Logs
This section describes how to query an operation log from the OMU database. By performing
this task, you can obtain information about the BSC6910 operations.
6.5 Exporting Operation Logs
This section describes how to use the File Manager or FTP Client tool to download to the LMT
PC an exported operation log that is saved in the directory OMU active workspace installation
directory\ftp\operator_log\exp_log.
6.6 Querying Security Logs
This section describes how to query the security logs from the OMU database. By performing
this task, you can learn about the security events such as login, logout, and authorization in the
BSC6910.
6.7 Exporting Security Logs
This section describes how to use the FTP Client to download to the LMT PC an exported security
log that is saved in the directory OMU active workspace installation directory\ftp\operator_log
\exp_log.
Issue 09 (2014-12-29)

80
BSC6910 UMTS
LMT User Guide
6 Log Management
6.8 Obtaining Running Logs

This section describes how to use File Manager or FTP Client to download to the LMT PC a
running log uploaded to bam\common\fam\famlog.
6.9 Collecting Log Statistics
This section describes how to collect the log statistics for fault analysis. There are different types
of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installation
logs, remote upgrade logs, security logs, alarm logs and others.
Issue 09 (2014-12-29)

81
BSC6910 UMTS
LMT User Guide
6 Log Management
6.1 Log Types

The logs are classified into operation logs, security logs, and running logs.
Operation Log
The BSC6910 operation log refers to all the real-time operation information recorded in the
OMU database.
The operation log is mainly used to analyze the association between the device faults and
operations.
Security Log
The security log refers to the NE or EMS information related to security events such as login,
logout, and authorization.
The security log is used for auditing and tracing security events.
Running Log
The running log refers to the system running information the BSC6910host records in real time.
The running log is used for fault location, routine inspection, and device monitoring.
6.2 Querying Log Storage Conditions

This section describes how to query the conditions for storing the operation logs and security
logs, including the time limit and storage capacity of the logs.
Prerequisites
Procedure
Step 1 Run the LST LOGLIMIT command to query the conditions for storing the logs. For restrictions
on storing other logs, see OMU Folder Size List in OMU Administration Guide.
----End
6.3 Setting Log Storage Conditions

This section describes how to set the conditions for storing the operation and security logs,
including the time limit and the storage capacity. The OMU database automatically deletes an
entry that has crossed the specified time limit or the earliest entry when the number of saved
logs exceeds the specified capacity.
Issue 09 (2014-12-29)

82
BSC6910 UMTS
LMT User Guide
6 Log Management
Prerequisites
Procedure
Step 1 Run the SET LOGLIMIT command. Set the Time Limit and Counts Limit, and then choose
a Log Type.
----End
6.4 Querying Operation Logs

This section describes how to query an operation log from the OMU database. By performing
this task, you can obtain information about the BSC6910 operations.
Prerequisites
Procedure
Step 1 Run the LST OPTLOG command, and set the query parameters as required to query the
corresponding log information.
NOTE
If no query parameter is set, the LMT lists the latest 64 operation records.
----End
6.5 Exporting Operation Logs

This section describes how to use the File Manager or FTP Client tool to download to the LMT
PC an exported operation log that is saved in the directory OMU active workspace installation
directory\ftp\operator_log\exp_log.
Prerequisites
l
You have logged in to the LMT with an ADMINISTRATOR-level account authorized for
this operation.
You are authorized to download files from the OMU to the LMT PC.
Procedure
Step 1 Run the EXP LOG command to export the corresponding operation log. In this step, set Log
Type to OPTLOG(Operation Log) and other parameters to appropriate values.
NOTE
The default save path for the exported logs is OMU active workspace installation directory\FTP\operator_log
\exp_log on the OMU active workspace.
Issue 09 (2014-12-29)

83
BSC6910 UMTS
LMT User Guide
6 Log Management
Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The
FTP Client is started.
Step 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 is set when the OMU is installed. The FTP user name is FtpUsr by
default.
Step 4 Click Enter to connect the OMU. The connecting status is displayed in the Connection tips
pane.
Step 5 After the connection is successful, in the server file list pane, double-click OMU active
workspace installation directory\ftp. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the operation log file to download it to the LMT PC.
Step 7 When the download is complete, choose System > Exit or click the close button to exit the FTP
Client.
----End
6.6 Querying Security Logs

This section describes how to query the security logs from the OMU database. By performing
this task, you can learn about the security events such as login, logout, and authorization in the
BSC6910.
Prerequisites
Procedure
Step 1 Run the LST SECLOG command, and set the query parameters as required to query the security
logs.
NOTE
If no query parameter is set, the LMT lists the security logs of the current day.
----End
6.7 Exporting Security Logs

This section describes how to use the FTP Client to download to the LMT PC an exported security
log that is saved in the directory OMU active workspace installation directory\ftp\operator_log
\exp_log.
Prerequisites
You have logged in to the LMT with an ADMINISTRATOR-level account authorized for this
operation.
Issue 09 (2014-12-29)

84
BSC6910 UMTS
LMT User Guide
6 Log Management
Procedure
Step 1 Run the EXP LOG command to export the corresponding operation log. In this step, set Log
Type to SECLOG(SECURITY LOG) and other parameters to appropriate values.
NOTE
The default save path for the exported logs is OMU active workspace installation directory\FTP\operator_log
\exp_log on the OMU active workspace.
Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The
FTP Client is started.
Step 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 is set when the OMU is installed. The FTP user name is FtpUsr by
default.
Step 4 Click Enter to connect the OMU. The connecting status is displayed in the Connection tips
pane.
Step 5 After the connection is successful, in the server file list pane, double-click OMU active
workspace installation directory\ftp. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the operation log file to download it to the LMT PC.
Step 7 When the download is complete, choose System > Exit or click the close button to exit the FTP
Client.
----End
6.8 Obtaining Running Logs

This section describes how to use File Manager or FTP Client to download to the LMT PC a
running log uploaded to bam\common\fam\famlog.
Prerequisites
Procedure
l
Using File Manager

1.
Issue 09 (2014-12-29)
Run the ULD LOGTOOMU command and enter the subrack number to upload the
corresponding running log to the OMU.

85
BSC6910 UMTS
LMT User Guide
6 Log Management
NOTE
l The running log is 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 uploaded and compressed. BSC0001_03Log20111107171947.tmp
indicates that the log is being uploaded.
l By default, the uploaded running logs are saved in bam\common\fam\famlog on the
OMU.
2.
Click File Manager on the LMT main page to start the file manager.
3.
In the File Navigation Area, choose corresponding nodes to navigate to 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 FTP Client

1.
Run the ULD LOGTOOMU command and enter the subrack number to upload the
corresponding running log to the OMU.
NOTE
l The running log is named in the format BSCID_subrack number/Log/yyyy/mm/dd/hh/

mm/ss.zip. For example, if a running log of 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 uploaded and
compressed. BSC0001_03Log20111107171947.tmp indicates that the log is being
uploaded.
l By default, the uploaded running logs are saved in bam\common\fam\famlog on 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 installed. The FTP user name is
FtpUsr by default.
4.
Click Enter to connect to the OMU. The connecting status is displayed in the
Connection tips pane.
5.
After the connection is set up successfully, choose corresponding nodes to navigate

to bam\common\fam\famlog in the server file list pane. All files in the path are
displayed in the server file list pane.
6.
Based on the file name, double-click the running log to be downloaded to download
it to the LMT PC.
7.
When the download is complete, choose System > Exit or click the close button to
exit the FTP Client.
----End
Issue 09 (2014-12-29)

86
BSC6910 UMTS
LMT User Guide
6 Log Management
6.9 Collecting Log Statistics

This section describes how to collect the log statistics for fault analysis. There are different types
of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installation
logs, remote upgrade logs, security logs, alarm logs and others.
Prerequisites
Procedure
Step 1 Run the COL LOG command. Set the required parameters to collect the corresponding log
statistics. For more description about logs, see Table 6-1.
NOTE
l When the active workspace of the OMU is version_a, the storage path of the following logs changes into
version_a. When the active workspace of the OMU is version_b, the storage path of the following logs
changes into version_b accordingly.
l The log files that are not compressed in 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 saved.
Table 6-1 Description about logs
Issue 09 (2014-12-29)
Type
File Path
Description
PFM_RESULT
(Performance Result File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Recording traffic statistics

from NEs to the M2000.
Used for traffic analyzing.
HOST_PFM_RESULT
(Performance Result File
from Host)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Recording traffic statistics

from boards to the OMU.
Used for traffic analyzing.
ACTIVE_DEF_MEAS_FIL
E(Active Default
Measurement Task File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Active traffic statistic

definition file from the
M2000 to NEs. Used for
traffic analyzing.
STANDBY_DEF_MEAS_F
ILE(Standby Default
Measurement Task File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Standby traffic statistic

definition file from the
M2000 to NEs. Used for
traffic analyzing.
PFM_SWITCHS(Switch
Information for
Performance)
Reserved parameter value.
HISTORY_ALARM
(History Alarm File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Recording alarms and events

reported by NEs. Used for
alarm and event analysis.

87
BSC6910 UMTS
LMT User Guide
6 Log Management
Type
File Path
Description
HISTORY_FAULT(History
Fault File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Recoding the faults reported

by all NEs. Used for fault
analysis.
ALM_SYSTEM_CFG(The
Configured Information of
Alarm)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Recording the configuration

information related to alarm
management. Used for alarm
and event analysis.
SECURITY_LOG(Security
Logs)
/bam/version_a/ftp/
COLLOGINFO/SEC-LOG/
Security logs of a NE. Used

for analyzing security-related
operations on the NE.
OPT_LOG(Operation Logs)
/bam/version_a/ftp/
COLLOGINFO/OPT-LOG/
Operation logs of a NE. Used

for analyzing user operations
on the NE.
OMU_LOG(The Log
Information of OMU)
l Independent Mode: /bam/

version_a/ftp/
COLLOGINFO/
SINGLE-BAM/
Operation and status logs 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
Recording information same

as the OMU_LOG except
information about scheduled
tasks and the standby
workspace.
Active OMU
/bam/version_a/ftp/
COLLOGINFO/
Active-SIM-BAM/
Standby OMU
/bam/version_a/ftp/
COLLOGINFO/
STANDBY-SIMBAM/
Issue 09 (2014-12-29)

88
BSC6910 UMTS
LMT User Guide
Issue 09 (2014-12-29)
6 Log Management
Type
File Path
Description
BSC_CFG_MML(The Data
Configure File of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
ExportCfgmml/
Recording the BSC

configuration data. Used for
configuration data
restoration.
BSC_DYNAMIC_CFG_INFO (Dynamic Configuration

Information of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
BSCDynaCFGInfo/
Recording the dynamic

mapping between cell IDs
and internal cell IDs, between
cells, base stations, links,
process and the
corresponding subsystems.
BSC_SERIES_NO(The
Series No. of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
Recording the Equipment

Serial Number (ESN) of a
BSC. Used for license check.
DB_BAK(The Backup File

of the Database)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
MysqlDbBak/
Backed up OMU database

information. Used for data
restoration.
MEM_DB_BAK(The
Backup File of the Database
in Memory)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
MemDbBak/
Backed up OMU
memory database. Used for
locating the inconsistency
between the memory
database and the MYSQL
database.
DEBUG_LOG(The
Common Debug Log)
/bam/common/fam/
famlogfmt/
Recording software running

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

information that is generated
before a board is abnormally
reset. Used for locating the
abnormal board reset.
DSP_DEBUG_LOG(The
Debug Log of DSP)
/bam/common/fam/
famlogfmt/
DSP debug logs. Used for

locating DSP faults.
HOST_LOG(The Running
Log of the Host)
/bam/common/fam/famlog/
Host operation logs.

89
BSC6910 UMTS
LMT User Guide
6 Log Management
Type
File Path
Description
3G_CHR_LOG(The CHR
Log for UMTS)
/bam/common/fam/
famlogfmt/
Recording call faults except

faults during call access and
call drops. Used for
analyzing the causes of
failures in failed soft or hard
handovers, relocations, or
cell updates.
BSC_INFO(The Basic
Information of the BSC)
/bam/version_a/ftp/
COLLOGINFO/BSC-LOG/
Recording 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/
BIOS system abnormal

running logs. Used for
locating BIOS faults.
CALLFAULT_LOG
(CALLFAULT Log)
/bam/common/fam/
famlogfmt/
Recording faults during call

access and call drops. Used
for analyzing the causes of
call access failures and call
drops.
PCHR_LOG(PCHR Log)
/bam/common/fam/
famlogfmt/pchr
Recording detailed
information of each call,
including service access, call
release, handover, DCCC,
and signal quality. Used for
KPI analysis and as a
reference when handling user
complaints.
SYSFAULT_LOG
(SYSFAULT Log)
/bam/common/fam/
famlogfmt/sysfault/
Recording severe software/

hardware faults such as
resource leakages and device
faults. Used for network
health check.
----End
Issue 09 (2014-12-29)

90
BSC6910 UMTS
LMT User Guide
7 Trace Management
Trace Management
About This Chapter

This chapter describes how to manage message tracing on the BSC6910. A maximum of 64 trace
7.1 Concepts Related to Trace Management
Trace management is performed during routine maintenance of equipment, and traces messages
on interfaces and signaling links to verify data and locate faults. Do not start excessive tracing
tasks when traffic is high, as it slows the LMT responses. In this case, set Trace Mode to Save
To OMU before beginning a tracing task.
7.2 Device Commissioning
This section describes how to perform the device commission.
7.3 UMTS Services
This section describes how to perform tracing tasks related to UMTS services.
7.4 Basic Tracing Operations
The basic operations of message tracing apply to all the BSC6910 message tracing tasks.
Issue 09 (2014-12-29)

91
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.1 Concepts Related to Trace Management

Trace management is performed during routine maintenance of equipment, and traces messages
on interfaces and signaling links to verify data and locate faults. Do not start excessive tracing
tasks when traffic is high, as it slows the LMT responses. In this case, set Trace Mode to Save
To OMU before beginning a tracing task.
7.1.1 Trace Principles

This describes the principles of message tracing. It also describes how to create or close message
tracing tasks and the internal process for the service module to report traced messages to the
LMT.
Principles of the Message Tracing

Figure 7-1 shows the principles of the message tracing.
Figure 7-1 Principles of the 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.
Issue 09 (2014-12-29)

92
BSC6910 UMTS
LMT User Guide
7 Trace Management
3.
The debugging module and service module delete the task from the filter table.
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 translates the messages and displays them on the tracing window.
7.1.2 Management of Tracing Operation Rights

You must have the relevant 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, all users except the GUEST-level user and CUSTOM-level users that are not entitled to
use command group G_10 can perform the tracing tasks online.
NOTE
Group G_10 consists of binary commands for creating tracing and monitoring tasks.
7.1.3 BSC Interface Signaling Tracing Mode

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

This is an instant tracing mode. The tracing results are sent to the LMT PC from the OMU.
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 to the LMT PC from the OMU.
In this tracing mode, you can select Save File to save the tracing result file to the LMT PC
in .tmf format. The LMT analyzes 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 \mbsc\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.
You can query the saved tracing result file according to the operations in Browsing Traced
Messages Offline.
Issue 09 (2014-12-29)

93
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.2 Device Commissioning

This section describes how to perform the device commission.
7.2.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.
Prerequisites
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, expand 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.
l Trace Type: You can set this parameter to Trace Sender or Trace Receiver to trace the
messages sent or received by the sender or receiver, respectively.
l IP Type: You can set this parameter to All, OMU, or Specified IP. If this parameter is set
to All, you need to set Module Name. If this parameter is set to Specified IP, you need to
set Subrack No., Slot No., Subsystem No., and Module Name.
l Subrack No.: indicates the number of the subrack where the traced subsystem is located.
l Slot No.: indicates the number of the slot where the traced subsystem is located.
l Subsystem No.: indicates the number of the traced subsystem.
l Module Name: indicates the traced functional module.
----End
Issue 09 (2014-12-29)

94
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.2.2 Tracing Redirected Messages

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. eGBTS does not support this function.
Prerequisites
Context
NOTICE
For a subsystem, only one task of tracing redirected messages can be started. When many
messages are printed through the serial port, the task of tracing redirected messages may affect
the performance of the system.
Only ADMINISTRATOR-level users are authorized for performing Tracing Redirected
Messages.
Procedure
Step 2 On the Trace Navigation Tree pane, expand Trace > Device Commissioning. Double-click
Redirected Trace.
Step 3 In the Redirected Trace dialog box, set the parameters as required, and click Submit. The trace
data pane displays the traced message flow.
----End
7.2.3 Capturing Packets

This section describes how to capture packets and helps locate transmission channel
disconnection and packet loss by analyzing the packet header.
Prerequisites
l
The communication between the LMT and the BSC is normal.
The following problems can be located by capturing packets:
Context
the 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 other non-interface boards, which then discard the packet.
Issue 09 (2014-12-29)

95
BSC6910 UMTS
LMT User Guide
7 Trace Management
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 determine where the problem lies, 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 can be captured, not including the payload of the
packet.
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.
Interface
Parameter
Description
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.
Issue 09 (2014-12-29)
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.

96
BSC6910 UMTS
LMT User Guide
7 Trace Management
Interface
Parameter
Description
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.
Trace Time
Start Time: The start time and end time of the trace task.
Trace Time (minute) : duration of the tracing task. The unit is minutes.
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.
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 09 (2014-12-29)

97
BSC6910 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 09 (2014-12-29)

98
BSC6910 UMTS
LMT User Guide
7 Trace Management
Interface
Parameter
Description
Inner 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 "inner trace direction"; or the source IP address when the "In" is
selected for the "inner trace direction".
If left blank, it indicates capturing of all packets at the peer IP address.
----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 created after the task is complete.
7.2.4 AC Tracing
This section describes how to trace signaling messages over the interface between controller and
access point controller (AC).
Prerequisites
l
The Local Maintenance Terminal (LMT) has been started.
You have logged in to the LMT with an account with authorized operation rights.
Procedure
Step 2 In the Trace Navigation Tree, unfold Trace > Device Commissioning and double-click AC
Trace. The AC Trace dialog box is displayed, as shown in Figure 7-2.
Issue 09 (2014-12-29)

99
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-2 AC tracing
Step 3 In the AC Trace dialog box, set parameters as required.

l AC Index (0-9): AC index, which uniquely identifies an AP Controller and can be queried
by running the LST ACADDR command.
l Trace Mode: For descriptions about Trace Mode, see 7.1.3 BSC Interface Signaling
Tracing Mode.
Step 4 Click Submit.
----End
Result
l
The operation succeeds.

No traced message is displayed on the LMT if the Save to OMU trace mode is selected.
You can view the tracing result saved on the OMU by referring to Browsing Traced
Messages Offline.
A window is displayed if the Report trace mode is selected. The message browsing
window displays information about each traced message, including the number, time,
RFN, trace type, direction, message type, option, RNC, subrack number, slot number,
subsystem number, and content.
If the tracing fails, a dialog box is displayed with the failure cause.
Follow-up Procedure
l
You can double-click a result in the displayed result area to view the detailed information
about the traced message.
You can perform required operations by referring to 7 Trace Management.
Issue 09 (2014-12-29)

100
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.2.5 DHCP Tracing

This section describes how to trace DHCP packets.
Prerequisites
l
The Local Maintenance Terminal (LMT) has been started.
You have logged in to the LMT with an account with authorized operation rights.
Procedure
Step 2 In the Trace Navigation Tree, unfold Trace > Device Commissioning and double-click DHCP
Trace. The DHCP Trace dialog box is displayed, as shown in Figure 7-3.
Figure 7-3 DHCP tracing
Step 3 In the DHCP Trace dialog box, set parameters as required.

l Subrack No.: indicates the number of the subrack housing the board to be traced.
l 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.
Issue 09 (2014-12-29)

101
BSC6910 UMTS
LMT User Guide
7 Trace Management
l 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.
l Port Type: You can set this parameter to ETHPORT, ETHTRK, . It is recommended that
this parameter not be set or set to the actual port type.
l 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.
l DHCP Product ID: indicates the type of base station to be traced. There are four options:
BTS, NODEB, SRAN, and OTHER.
BTS: indicates the GSM base station.
NODEB: indicates the UMTS base station.
SRAN: indicates the SRAN base station.
NOTE
To trace SRAN base station, select NODEB and SRAN.
OTHER: indicates other base stations.

l 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 parsing interface. If this field is left blank, all DHCP
packets will be traced.
For descriptions about Trace Mode, see 7.1.3 BSC Interface Signaling Tracing Mode.
----End
Result
l
The operation succeeds.

Messages Offline.
window displays information about each traced message, including the number, time,
RFN, trace type, direction, message type, PID, subrack number, slot number, subsystem
number, and content.
Follow-up Procedure
l
You can perform required operations by referring to 7 Trace Management.
7.3 UMTS Services

This section describes how to perform tracing tasks related to UMTS services.
Issue 09 (2014-12-29)

102
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.3.1 Tracing Messages on the Iu Interface

This section describes how to trace messages on the Iu interface on the LMT.
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.
Prerequisites
Context
You can start the Iu interface tracing on the LMT to monitor interworking of the signaling
messages on the Iu interface.
When starting a tracing task, you can make the following choices:
l
Tracing the required types of message
Tracing all types of messages
Tracing signaling messages at the transport network layer
A maximum of six tracing tasks can be performed on the Iu interface simultaneously.
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-4.
Issue 09 (2014-12-29)

103
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-4 Message tracing on the Iu interface
Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and select
IU under Trace Type.
l RNC ID indicates the RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.
l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,
DPC(HEX) needs to be specified.
l For description of Trace Mode, see 7.1.3 BSC Interface Signaling Tracing Mode.
Step 4 In the IU tab page, select Message Type.
----End
Result
l
Successful operation
Messages Offline.
window displays information about each traced message, including the task number,
Issue 09 (2014-12-29)

104
BSC6910 UMTS
LMT User Guide
7 Trace Management
task time, RFN, trace type, direction, message type, message source, option, node,
subrack number, slot number, subsystem number, and message content.
l
Follow-up Procedure
l
You can perform required operations by referring to 7.4 Basic Tracing Operations.
Tracing MTP3 Messages

This section describes how to trace Message Transfer Part Level 3 (MTP3) messages, which
can be traced on the Iu interface. The traced messages include upper layer user messages such
as QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling link test
messages, and MTP3 signaling network management messages.
Prerequisites
Context
MTP3 message tracing can check whether Originating Signaling Point Code (OPC), Destination
Signaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link Test
Message (SLTM) messages match each other and the negotiated data. In this way,
troubleshooting the problem that MTP3 links are unavailable but the corresponding SAAL links
are available can be facilitated.
NOTE
A maximum of six MTP3 message tracing tasks can be performed simultaneously.
Procedure
Issue 09 (2014-12-29)

105
BSC6910 UMTS
LMT User Guide
7 Trace Management
MTP3 under Trace Type.
URNCBASIC command.
Step 4 In the MTP3 tab page, select Message Type and Parameters Settings.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

106
BSC6910 UMTS
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l
Tracing QAAL2 Messages

This section describes how to trace QAAL2 messages, which can be traced on the Iu interface.
QAAL2 message tracing helps to monitor interworking of QAAL2 messages and locate
establishment failure and abnormal release of channels on the AAL2 user plane on the Iu
interface.
Prerequisites
Context
QAAL2 message tracing determines whether the failure or abnormal release occurs at the local
or peer end by checking whether an ESTABLISH_REQUEST message is sent and checking the
returned messages.
l
If the RNC does not send an ESTABLISH_REQUEST message, the problem occurs
generally at the local end, namely RNC, because of insufficient bandwidth or incorrect
configuration of the ATM address.
If the RNC sends an ESTABLISH_REQUEST message and receives an

RELEASE_CONFIRM message from the peer end, you can infer that the problem occurs
at the peer end.
NOTE
A maximum of six QAAL2 message tracing tasks can be performed simultaneously.
Procedure
Issue 09 (2014-12-29)

107
BSC6910 UMTS
LMT User Guide
7 Trace Management
QAAL2 under Trace Type.
URNCBASIC command.
----End
Result
l
Messages Offline.
l
Issue 09 (2014-12-29)
108
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
Tracing SAAL Messages

This section describes how to trace Signaling ATM Adaptation Layer (SAAL) messages, which
can be traced on the Iu interface. SAAL message tracing helps to monitor interworking of SAAL
messages on the Iu interface and locate unavailable SAAL links.
Prerequisites
Context
NOTE
A maximum of six SAAL message tracing tasks can be performed simultaneously.
Procedure
Issue 09 (2014-12-29)

109
BSC6910 UMTS
LMT User Guide
7 Trace Management
SAAL under Trace Type.
URNCBASIC command.
Step 4 In the SAAL tab page, specify Signaling Link ID, Subrack No. of SAAL, Slot No. of
SAALand select Trace Object.
NOTE
To query the SAAL link ID, run the LST SAALLNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing SCTP Messages

This section describes how to trace Stream Control Transmission Protocol (SCTP) messages,
which can be traced on the Iu interface. SCTP message tracing helps to monitor interworking
of SCTP messages on the Iu interface and locate unavailable SCTP links.
Prerequisites
Issue 09 (2014-12-29)

110
BSC6910 UMTS
LMT User Guide
7 Trace Management
Context
As the NCP/CCP/M3UA function unit uses SCTP links as lower layer links in IP transport, you
can start SCTP message tracing to check whether the NCP/CCP/M3UA function unit works
improperly.
As data is frequently received by and sent to SCTP links, starting SCTP message tracing affects
system performance to a certain extent. It is not recommended that multiple SCTP message
tracing tasks be started simultaneously.
NOTE
A maximum of six SCTP message tracing tasks can be performed simultaneously.
Procedure
SCTP under Trace Type.
URNCBASIC command.
Issue 09 (2014-12-29)

111
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 4 In the SCTP tab page, specify SCTP Link ID and select SCTP Message.
NOTE
To query the SCTP Link ID, run the LST SCTPLNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing M3UA Messages

This section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, which
can be traced on the Iu interface. M3UA message tracing facilitates troubleshooting of the
problem that M3UA links are unavailable but the corresponding IP links are available.
Prerequisites
Context
M3UA message tracing can check whether Originating Signaling Point Code (OPC), Destination
troubleshooting of the problem that M3UA links are unavailable but the corresponding IP links
NOTE
A maximum of six M3UA message tracing tasks can be performed simultaneously.
Issue 09 (2014-12-29)

112
BSC6910 UMTS
LMT User Guide
7 Trace Management
Procedure
M3UA under Trace Type.
URNCBASIC command.
Step 4 In the M3UA tab page, select M3UA Message and set other parameters.
NOTE
l Before tracing M3UA messages, you need to configure its lower layer links, SCTP links and then configure
M3UA links.
l To query an M3UA link set number, an M3UA link number, and more information about M3UA links, run
the LST M3LNK command.
Issue 09 (2014-12-29)

113
BSC6910 UMTS
LMT User Guide
7 Trace Management

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing SCCP Messages

This section describes how to trace Signaling Connection Control Part (SCCP) messages, which
can be traced on the Iu interface. SCCP messages include the connection-oriented messages and
the connectionless messages. SCCP message tracing helps to monitor interworking of SCCP
messages and locate establishment failure and abnormal release of channels on the Iu interface.
Prerequisites
Context
NOTE
A maximum of six SCCP message tracing tasks can be performed simultaneously.
Procedure
Issue 09 (2014-12-29)

114
BSC6910 UMTS
LMT User Guide
7 Trace Management
SCCP under Trace Type.
URNCBASIC command.
----End
Result
l
Messages Offline.
l
Issue 09 (2014-12-29)
115
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.2 Tracing Messages on the Iupc Interface

This section describes how to trace messages on the Iupc interface on the LMT.
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.
Prerequisites
Context
You can start the Iupc interface tracing on the LMT to monitor the interworking of signaling
messages over the Iupc interface.
When starting a tracing task, you can select the following operations:
l
Tracing the required types of message
Tracing all types of messages
Tracing signaling messages at the transport network layer
A maximum of six Iupc interface tracing tasks can be performed simultaneously.
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-11.
Issue 09 (2014-12-29)

116
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-11 Message tracing on the Iupc interface
Step 3 In the Iupc Interface Trace dialog box, set parameters in the default Basic tab page and select
IUPC under Trace Type.
URNCBASIC command.
Step 4 In the IUPC tab page, select the message type.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

117
BSC6910 UMTS
LMT User Guide
7 Trace Management
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.

can be traced on the Iupc interfaces. M3UA message tracing facilitates troubleshooting of the
Prerequisites
Context
NOTE
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iupc Interface Trace. The
Iupc Interface Trace dialog box is displayed, as shown in Figure 7-12.
Issue 09 (2014-12-29)

118
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
NOTE
M3UA links.

----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

119
BSC6910 UMTS
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l

which can be traced on the Iupc interfaces. SCTP message tracing helps to monitor interworking
of SCTP messages on the Iupc interfaces and locate unavailable SCTP links.
Prerequisites
Context
improperly.
NOTE
Procedure
Issue 09 (2014-12-29)

120
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
NOTE

----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

121
BSC6910 UMTS
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l

can be traced on the Iupc interface. SCCP messages include the connection-oriented messages
and the connectionless messages. SCCP message tracing helps to monitor interworking of SCCP
messages and locate establishment failure and abnormal release of channels on the Iupc interface.
Prerequisites
Context
NOTE
Procedure
Issue 09 (2014-12-29)

122
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

123
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.3 Tracing Messages on the Iur Interface

This section describes how to trace messages on the Iur interface on the LMT.
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.
Prerequisites
Context
A maximum of six Iur interface tracing tasks can be performed simultaneously.
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-15.
Issue 09 (2014-12-29)

124
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-15 Message tracing on the Iur interface
Step 3 In the Iur Interface Trace dialog box, set parameters in the default Basic tab page and select
IUR under Trace Type.
URNCBASIC command.
Step 4 In the IUR tab page, select Message Type.
NOTE
In the IUR tab page, if you select IUR_G, the Iur-g interface messages between BSC6910s or in a
BSC6910 are traced. If you select InMbsc, the Iur-g interface messages between the GSM and UMTS in
a BSC6910 are traced.

----End
Result
l
Issue 09 (2014-12-29)

125
BSC6910 UMTS
LMT User Guide
7 Trace Management
Messages Offline.
l
Follow-up Procedure
l
Tracing MTP3 Messages

This section describes how to trace Message Transfer Part Level 3 (MTP3) messages, which
can be traced on the Iur interfaces. The traced messages include upper layer user messages such
as QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling link test
messages, and MTP3 signaling network management messages.
Prerequisites
Context
MTP3 message tracing can check whether Originating Signaling Point Code (OPC), Destination
troubleshooting the problem that MTP3 links are unavailable but the corresponding SAAL links
NOTE
A maximum of six MTP3 message tracing tasks can be performed simultaneously.
Procedure
Issue 09 (2014-12-29)

126
BSC6910 UMTS
LMT User Guide
7 Trace Management
MTP3 under Trace Type.
URNCBASIC command.
Step 4 In the MTP3 tab page, select Message Type and Parameter Settings.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

127
BSC6910 UMTS
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l

This section describes how to trace QAAL2 messages, which can be traced on the Iur interfaces.
establishment failure and abnormal release of channels on the AAL2 user plane on the Iur
interfaces.
Prerequisites
Context
returned messages.
l

at the peer end.
NOTE
Procedure
Issue 09 (2014-12-29)

128
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
----End
Result
l
Messages Offline.
l
Issue 09 (2014-12-29)
129
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l

can be traced on the Iur interfaces. SAAL message tracing helps to monitor interworking of
SAAL messages on the Iur interfaces and locate unavailable SAAL links.
Prerequisites
Context
NOTE
Procedure
Issue 09 (2014-12-29)

130
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
Step 4 In the SAAL tab page, specify Signaling Link ID, Subrack No. of SAAL, Slot No. of
SAAL and select Trace Object.
NOTE
To query the SAAL link ID, run the LST SAALLNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l

which can be traced on the Iur interfaces. SCTP message tracing helps to monitor interworking
of SCTP messages on the Iur interfaces and locate unavailable SCTP links.
Prerequisites
Issue 09 (2014-12-29)

131
BSC6910 UMTS
LMT User Guide
7 Trace Management
Context
improperly.
NOTE
Procedure
URNCBASIC command.
Issue 09 (2014-12-29)

132
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTE

----End
Result
l
Messages Offline.
Follow-up Procedure
l

can be traced on the Iur interfaces. M3UA message tracing facilitates troubleshooting of the
Prerequisites
Context
NOTE
Issue 09 (2014-12-29)

133
BSC6910 UMTS
LMT User Guide
7 Trace Management
Procedure
URNCBASIC command.
NOTE
M3UA links.
Issue 09 (2014-12-29)

134
BSC6910 UMTS
LMT User Guide
7 Trace Management

----End
Result
l
Messages Offline.
Follow-up Procedure
l

can be traced on the Iur interfaces. SCCP messages include the connection-oriented messages
and the connectionless messages. SCCP message tracing helps to monitor interworking of SCCP
messages and locate establishment failure and abnormal release of channels on the Iur interfaces.
Prerequisites
Context
NOTE
Procedure
Issue 09 (2014-12-29)

135
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
----End
Result
l
Messages Offline.
l
Issue 09 (2014-12-29)
136
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.4 Tracing Messages on the Iub Interface

This section describes how to trace messages on the Iub interface on the LMT.
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.
Prerequisites
Context
A maximum of six Iub interface tracing tasks can be performed simultaneously.
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-22.
Issue 09 (2014-12-29)

137
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-22 Message tracing on the Iub interface
Step 3 In the Iub Interface Trace dialog box, set parameters in the default Basic tab page and select
NBAP under Trace Type.
URNCBASIC command.
l NodeB Trace Type
All NodeB: traces NodeB Application Part (NBAP) messages of all NodeBs.
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.
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.
Step 4 In the NBAP tab page, select Message Type.
----End
Result
l
Issue 09 (2014-12-29)
138
BSC6910 UMTS
LMT User Guide
7 Trace Management
Messages Offline.
l
Follow-up Procedure
l

can be traced on the Iub interfaces. SAAL message tracing helps to monitor interaction of SAAL
messages on the Iub interface and locate faulty SAAL links.
Prerequisites
Context
NOTE
Procedure
Issue 09 (2014-12-29)

139
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 3 In the Iub Interface Trace dialog box, set parameters on the default Basic tab page and select
URNCBASIC command.
l NodeB Trace Type
Step 4 On the SAAL tab page, specify SAAL Link No., Subrack No. of SAAL, Slot No. of SAAL
and select Trace Object.
l SAAL Link No.: indicates the number of the SAAL link to be traced.
NOTE
To query the SAAL link number, run the LST SAALLNK command.

----End
Issue 09 (2014-12-29)

140
BSC6910 UMTS
LMT User Guide
7 Trace Management
Result
l
No traced message will be displayed on the LMT if the Save to OMU trace mode is
selected. You can view the tracing result saved on the OMU by referring to Browsing
Traced Messages Offline.
Follow-up Procedure
l
You can double-click a message in the displayed result area to view detailed information
You can perform further operations by referring to 7.4 Basic Tracing Operations.

which can be traced on the Iub interfaces. SCTP message tracing helps to monitor interworking
of SCTP messages on the Iub interfaces and locate unavailable SCTP links.
Prerequisites
Context
improperly.
NOTE
Procedure
Issue 09 (2014-12-29)

141
BSC6910 UMTS
LMT User Guide
7 Trace Management
URNCBASIC command.
l NodeB Trace Type
l SCTP Link ID: indicates the number of the SCTP link to be traced. To query the SCTP Link
ID, run the LST SCTPLNK command.
----End
Issue 09 (2014-12-29)

142
BSC6910 UMTS
LMT User Guide
7 Trace Management
Result
l
Messages Offline.
Follow-up Procedure
l

This section describes how to trace QAAL2 messages, which can be traced on the Iub interface.
establishment failure and abnormal release of channels on the AAL2 user plane on the Iub
interface.
Prerequisites
Context
returned messages.
l

at the peer end.
NOTE
Procedure
Issue 09 (2014-12-29)

143
BSC6910 UMTS
LMT User Guide
7 Trace Management
RNC ID indicates the RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

144
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.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.
Prerequisites
Context
You can start the Uu interface tracing on the LMT to monitor interworking of signaling messages
on the Uu interface.
When starting a tracing task, you can make the following choices:
l
Tracing messages of one or multiple BSC6910s and the cells
Tracing all types of messages on the Uu interface
Tracing the specified types of messages
A maximum of six Uu interface tracing tasks can be performed simultaneously. Each Uu

interface tracing task targets at a maximum of 32 cells.
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-26.
Issue 09 (2014-12-29)

145
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-26 Message tracing on the Uu interface
Step 3 In the Uu Interface Trace dialog box, specify RNCID:CellID under Cell Config and set other
parameters.
URNCBASIC command.
l CellID 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.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

146
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.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.
Tracing Intra-Frequency MNCDT Messages

This section describes how to trace messages indicating missing intra-frequency neighboring
cell relationship.
Prerequisites
l
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-27.
Figure 7-27 MNCDT message tracing
Issue 09 (2014-12-29)

147
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 3 In the MNCDT Trace dialog box, set Detection Type to Intra Freq.
URNCBASIC command.
----End
Result
l
Messages Offline.
task time, cell id, message type, URNTI, node, subrack number, slot number, subsystem
number, and message content.
Follow-up Procedure
l
Tracing Inter-Frequency MNCDT Messages

This section describes how to trace messages indicating missing inter-frequency neighboring
cell relationship.
Prerequisites
l
Procedure
Issue 09 (2014-12-29)

148
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 3 In the MNCDT Trace dialog box, set Detection Type to Inter Freq.
l Uplink UARFCN: indicates the uplink UTRA Absolute Radio Frequency Channel Number
(UARFCN) of the cell to be traced for detecting missing neighboring relationship
l Downlink UARFCN: indicates the downlink UARFCN of the cell to be traced for detecting
missing neighboring relationship
l Start of Primary Scrambling Code: indicates the minimum scrambling code for an
MNCDT task
l 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.
URNCBASIC command.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

149
BSC6910 UMTS
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l
Tracing Inter-RAT MNCDT Messages

This section describes how to trace messages indicating missing inter-RAT neighboring cell
relationship.
Prerequisites
l
Procedure
Issue 09 (2014-12-29)

150
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 3 In the MNCDT Trace dialog box, set Detection Type to Inter RAT.
l 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.
l 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.
l 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.
l 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.
l 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.
l Start of BCCH ARFCN: indicates the minimum Absolute Radio Frequency Channel
Number (ARFCN) for an MNCDT task
l End of BCCH ARFCN: indicates the maximum ARFCN for an MNCDT task
URNCBASIC command.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Issue 09 (2014-12-29)

151
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.3.7 Message Setting

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.
This function takes effect only when the debug mode is selected.
You can choose the following message types:
l
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_INTRA_MSG: Selecting it enables the LMT to display communication

messages between internal units of the RNC.
UI_FAM_UT_L2_TXT_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_PRINT_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.
UI_FAM_UT_RPRT_CELL_EVENT_INFO: 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_STANDARD_MSG: Selecting it enables the LMT to display UE messages

traced on standard interfaces.
UI_FAM_UT_STATE_TRANS: Selecting it enables the LMT to trace state transitions

of the UE.
7.3.8 Tracing UE Messages

This section describes how to trace UE messages. You can perform this task to analyze the call
procedure failure cause by monitoring interworking of the signaling on each standard interface,
interworking of the signaling on the user plane, and uplink and downlink data. In combination
with a drive test, this task helps to locate problems or deal with complaints from VIP subscribers.
Prerequisites
Issue 09 (2014-12-29)

152
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTICE
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.
Context
When initiating UE tracing, users need to select interfaces and types of message to be traced and
identify a UE by IMSI, MSISDN, IMEI, TMSI, or P-TMSI. Users can trace signaling messages
of the UE on Iu, Iur, Iub, and Uu interfaces or on a specified interface.
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.
NOTE
A maximum of 12 UE tracing tasks can be performed simultaneously and a maximum of six tasks for
tracing internal messages can be performed simultaneously.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. The UE Trace
Issue 09 (2014-12-29)

153
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-30 UE message tracing
Step 3 In the displayed UE Trace dialog box, set the parameters as required.
URNCBASIC command.
l 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 P-TMSI, you need to specify LAC, RAC, MCC, and MNC.
Issue 09 (2014-12-29)

154
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTE
l 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.
l 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.
l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI data
is directly entered in IMSI.
l Change the anonymous policy and cipher key on the M2000 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 M2000
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.
l TRACE RRC PROCEDURE: 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.
l Filter traced messages by setting parameters in the IUR, IUB, IU, and UU tab pages.
l Monitor tab page: includes performance counters to be monitored during tracing of a single
UE
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.
Issue 09 (2014-12-29)

155
BSC6910 UMTS
LMT User Guide
7 Trace Management
l 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.
Other tab page
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 area: includes parameters that enable statistics on packets received
and sent at layer 2 to be reported to the LMT.
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.
Report time(s): indicates the period for reporting L2 Data Report.
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.
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.
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.
Ping Interval (0.1ms): indicates the interval at which ICMP packets are sent.
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/.
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.
QAAL2_protocol_tracing: 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_INFO: Selecting it enables the following information to be traced: Realtime 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.
Issue 09 (2014-12-29)

156
BSC6910 UMTS
LMT User Guide
7 Trace Management
RT_COMM_CONTEXT_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.
RT_INST_RESOURCE_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.
Other1 tab page
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.
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.
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
L2 FL protocol Trace Report: Selecting it enables protocol parameters on the user
plane to be reported to the LMT.
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.
NOTICE
Note that selecting BackPanel Trace or FrontPanel Trace may lead to flow control,
so exercise caution in this selection.
Flow Trace Interface Type: indicates the interface to have its data flow traced.
Flow Trace Bearer Type: indicates the channel to have its data flow traced.
Flow Trace Service Type: indicates the service to have its data flow traced.
BackPanel Trace: traces data flow sent or received on the backplane of the
interface board.
Issue 09 (2014-12-29)

157
BSC6910 UMTS
LMT User Guide
7 Trace Management
FrontPanel Trace: traces data flow sent or received on the panel of the interface
board.
Bind tab page: is used for binding the UE to a UPor path or transmission resource pool.
This helps users to determine whether a UP or path fault exists.
UP
UP No.: indicates the number of the UP.
Iub
Path ANI No.: indicates the Adjacent Node Identifier (ANI) corresponding to the
Iub path.
Type: indicates the transport type of the Iub path.
Path ID: indicates the number of the Iub path.
Iucs
Path ANI No.: indicates the ANI corresponding to the Iu-CS path.
Type: indicates the transport type of the Iu-CS path.
Path ID: indicates the number of the Iu-CS path.
Iur
Path ANI No.: indicates the ANI corresponding to the Iur path.
Type: indicates the transport type of the Iur path.
Path ID: indicates the number of the Iur path.
Iups
Path ANI No.: indicates the ANI corresponding to the Iu-PS path.
Type: indicates the transport type of the Iu-PS path.
Path ID: indicates the number of the Iu-PS path.
NODE
Node ID/External Node ID: indicates the ID of the bound physical node.
NOTICE
Debug Mode: indicates a mode intended for Huawei technical support personnel for
maintenance. For use of it, contact Huawei technical support personnel.
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

158
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTE
The file that saves messages traced by a UE tracing task is named in a different way from the file that
saves 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 needing to add 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.
subrack number, slot number, subsystem number, message length, and message content.
NOTE
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.
l To view detailed description of TXT (Command Code) messages, right-click in the blank
area on the right and choose Update Text from the shortcut menu. The text messages update
once each time users choose Update Text. They do not automatically update.
Follow-up Procedure
l
7.3.9 Tracing Cell Messages

This section describes how to trace cell messages. The UE statistics can be displayed in the
tracing result if required. 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.
Prerequisites
Context
You can specify a cell by entering Cell ID and specify a message type to be traced by selecting
a trace event. The cell message tracing task can be performed to trace NBAP common messages
on the Iub interface of a specified cell and to report the UE statistics as required. The cell to be
traced must be activated.
Issue 09 (2014-12-29)

159
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTE
l A maximum of eight cell tracing tasks can be performed simultaneously.

l Each cell tracing task targets only one cell.
l Each cell tracing task targets a maximum of two SCCPCHs.
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-31.
Figure 7-31 Cell message tracing
Step 3 Set parameters in the Cell Trace dialog box.

URNCBASIC command.
l Cell ID: indicates the index of a cell.
l 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.
l FMR tab page: includes the following filter criteria:
Issue 09 (2014-12-29)

160
BSC6910 UMTS
LMT User Guide
7 Trace Management
Service Data Trace area: 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(100ms): is in the unit of 100 ms and needs to be specified if Layer 2 Data
transfer Periodic Report or Transport Data Periodic Report is selected in the FMR
tab page.
l IUB tab page: includes messages to be traced on the Iub interface.
l 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.
Bind tab page: is used for binding the UE to a UP. This helps users to determine whether
a UP fault exists.
UP No.: indicates the number of the UP.
Other tab page
SIG Trace Event area: 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.
CELL_SIG_AL_STREAMING_RDPT: Selecting it enables specified data flow of
the cell on the interface board to be reported to the LMT.
Transport Channel Type: indicates the type of transport channel to have its data
flow traced.
SCCPCH ID: indicates the ID of the Secondary Common Control Physical
Channel (S-CCPCH).
NOTICE
Debug Mode: indicates a mode intended for Huawei technical support personnel for
----End
Result
l
Messages Offline.
Issue 09 (2014-12-29)

161
BSC6910 UMTS
LMT User Guide
7 Trace Management
NOTE
To view detailed description of TXT (Command Code) messages, right-click in the blank area on the right and
choose Update Text from the shortcut menu. The text messages update once each time users choose Update
Text. They do not automatically update.
Follow-up Procedure
l
7.3.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.
Prerequisites
Context
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.
A maximum of six IOS tracing tasks can be performed simultaneously. Each task targets a
maximum of 30 calls and 32 cells.
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 BSC6910 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. You can also select one or more
cells to trace.
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.
Issue 09 (2014-12-29)

162
BSC6910 UMTS
LMT User Guide
7 Trace Management
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > IOS Trace. The IOS
Figure 7-32 IOS message tracing
Step 3 In the displayed IOS Trace dialog box, set parameters and filter traced messages in other tab
pages.
URNCBASIC command.
l Call Count: indicates the maximum number of calls that can be traced simultaneously after
a tracing task is started. The value ranges from 1 to 30.
l Cell ID: You can type the ID of one cell or IDs of multiple cells.
l VIP IMSI: Run the ADD UVIPIMSI command to add the VIP IMSI.
l Only InterSubSystem: When this switch is turned on, only users with control plane load
sharing are traced.
Issue 09 (2014-12-29)

163
BSC6910 UMTS
LMT User Guide
7 Trace Management
l IMEI TAC(TAC1,TAC2,...TAC8): specifies the 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_QUERY_UE_IMEI_S
WITCH-1, PROCESSSWITCH4=SEND_MSG_NULL_SWITCH-1;
l Event Type:indicates 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.
l MM tab page:
CELL CHANGE ORDER: indicates the traced messages of the cell change order
procedure.
INTER RAT HANDOVER IN: indicates the traced messages of the incoming interRAT handover procedure.
INTER RAT HANDOVER OUT: indicates the traced messages of the outgoing interRAT handover procedure through relocation.
LOCATION UPDATE: indicates the traced messages of the location area update
procedure.
ROUT AREA UPDATE: indicates the traced messages of the routing area update
procedure.
l RAB tab page:includes RAB parameters. If the BSC6910 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.
l RRC tab page:includes the RRC establishment cause. If the BSC6910 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):indicates the 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):indicates the 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):indicates the 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):indicates the period of reporting results of cell common
measurement that is selected in the Monitor tab page of IOS Trace
NBAP Special(ms):indicates the 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
Issue 09 (2014-12-29)

164
BSC6910 UMTS
LMT User Guide
7 Trace Management
RNSAP Special(ms):indicates the 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
RTT Special NBAP(ms):indicates the 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:indicates call establishment causes and filters UEs to be traced in the
cell based on the call establishment causes
l Monitor tab page:includes performance counters to be monitored during tracing of a single
UE
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.
l 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.
Other tab page
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.
L2 Data Report area:includes parameters that enable statistics on packets received
and sent at layer 2 to be reported to the LMT.
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.
Issue 09 (2014-12-29)

165
BSC6910 UMTS
LMT User Guide
7 Trace Management
Report time(s):indicates the period for reporting L2 Data Report.

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.
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.
QAAL2_protocol_tracing: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_INFO:Selecting it enables the following information to be traced:Realtime 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_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.
RT_INST_RESOURCE_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 tracing: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.
Other1 tab page
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
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.
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.
FP Trace:Selecting it enables control frames on the IuUP or at the FP layer to be
Bind tab page:is used for binding the call samples to a path. This helps users to determine
whether a path fault exists.
Iub Path
Path ANI No.:indicates the Adjacent Node Identifier (ANI) corresponding to the
Iub path.
Path Type:indicates the transport type of the Iub path.
Issue 09 (2014-12-29)

166
BSC6910 UMTS
LMT User Guide
7 Trace Management
Path ID:indicates the number of the Iub path.

CID/UDP PORT(I1,I2,I3...):indicates the bound channel identifier (CID) on the
Iub path in ATM transmission mode .
Iucs Path
Path ANI No.:indicates the ANI corresponding to the Iu-CS path.
Path Type:indicates the transport type of the Iu-CS path.
Path ID:indicates the number of the Iu-CS path.
CID/UDP PORT(I1,I2,I3...):indicates the bound CID on the Iu-CS path in ATM
transmission mode.
Iur Path
Path ANI No.:indicates the ANI corresponding to the Iur path.
Path Type:indicates the transport type of the Iur path.
Path ID:indicates the number of the Iur path.
CID/UDP PORT(I1,I2,I3...):indicates the bound CID on the Iur path in ATM
transmission mode.
Iups GTPU
Path ANI No.:indicates the ANI corresponding to the Iu-PS GTPU.
Path ID:indicates the path number of the Iu-PS GTPU.
NOTICE
Debug Mode:indicates a mode intended for Huawei technical support personnel for
----End
Result
l
Messages Offline.
NOTE
Issue 09 (2014-12-29)

167
BSC6910 UMTS
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.11 Tracing Iurp Messages

This section describes how to trace Iurp messages.
Prerequisites
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.
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iurp Trace. The Iurp
Figure 7-33 Iurp message trace
Step 3 In the displayed Iurp Trace > Basic dialog box, set the parameters as required.
l External Node Configuration: You can select All External Node or Specified External
Node. When you select Specified External Node, you need to type Specified External
Node.
l Trace Type: You can select IURP or IURPLNK.
Issue 09 (2014-12-29)

168
BSC6910 UMTS
LMT User Guide
7 Trace Management
l Trace Mode: For description of Trace Mode, see 7.1.3 BSC Interface Signaling Tracing
Mode.
Step 4 In the displayed Iurp Trace > IURP dialog box, set the parameters as required, as shown in
Figure 7-34.
Figure 7-34 IURP Trace Type
l Frame Type: You can select All, Control Frame, Data Frame or OM Frame.
l Direction: You can select All, In or Out.
l SendPid: You can select All or Specified PID. When you select Specified PID, you need
to type Send Specified PID.
l ReceiverPid: You can select All or Specified PID. When you select Specified PID, you
need to typeReceiver Specified PID.
Step 5 In the displayed Iurp Trace > IURPLNK dialog box, set the parameters as required, as shown
in Figure 7-35.
Issue 09 (2014-12-29)

169
BSC6910 UMTS
LMT User Guide
7 Trace Management
Figure 7-35 IURPLNK Trace Type
----End
Result
l
No traced message is displayed on the LMT if theSave to OMU trace mode is selected.
You can view the tracing result saved on the OMU by referring to 7.4.4 Browsing
Traced Messages Offline.
A window is displayed if theReport trace mode is selected. The message browsing
window displays information about each traced message, includingthe task number,
task time, RFN, trace type, direction, message type, message source, option, subrack
number, slot number, subsystem number, and message content.
NOTE
Follow-up Procedure
l
7.4 Basic Tracing Operations

The basic operations of message tracing apply to all the BSC6910 message tracing tasks.
Issue 09 (2014-12-29)

170
BSC6910 UMTS
LMT User Guide
7 Trace Management
7.4.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.
By default, each message browser is displayed in maximized mode. To compare results

displayed in multiple message browsers, set Windows to Cascade, Horizontal or
Vertical.
Context
Each of the windows is configured with a default minimum width, which ensures the
comparison effect when multiple windows are tiled vertically. 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
Windows to Cascade, Horizontal, or Vertical. After such a setting, a new message
browser will still be displayed in maximized mode.
l
A maximum of 2000 messages can be displayed in a message browser. Newly traced

messages will replace old ones if displayed messages in a message browser reach 2000.
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
Issue 09 (2014-12-29)
Shortcut
Description
Stop Trace Task
Suspend the tracing task.
Restart Trace Task
Resume the tracing task.
Save All Messages...
Saves 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 themselves upward.
Clear Messages
Clear all displayed messages from the message browser

without affecting the saved messages.
Property...
Query properties of the tracing task.

171
BSC6910 UMTS
LMT User Guide
7 Trace Management
Step 2 To view details of a message, double-click it. The Message Browser dialog box 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
7.4.2 Viewing the Interpretation of the Trace Message

This section describes how to view the interpretation of a trace message.
Prerequisites
l
Trace messages are reported.
Procedure
Step 1 In the message browse window, select and double-click the trace message.
Step 2 The Message Browser window is displayed. The dialog box displays the details and meaning
of the message in protocol translation format.
----End
7.4.3 Saving Traced Messages

This section describes how to save traced messages in a file to an LMT PC.
Prerequisites
l
A tracing task is started.
Traced messages are reported.
Context
The name of the file containing saved messages cannot exceed 100 characters, including the file
name extension.
There are two ways of saving the traced results: automatic and manual.
Procedure
l
Automatic saving of traced messages

Select Save File when creating a tracing task. All traced messages of this task 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 LMT PC.
Issue 09 (2014-12-29)

172
BSC6910 UMTS
LMT User Guide
7 Trace Management
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 needing to add 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-MMSS-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.4.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 some messages displayed in the message
browser, select them, 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
7.4.4 Browsing Traced Messages Offline

This section describes how to use the TrafficRecording 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. You can double-click them to read 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.
Issue 09 (2014-12-29)

173
BSC6910 UMTS
LMT User Guide
7 Trace Management
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.
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.
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
7.4.5 Managing Tracing Tasks

This section describes how to manage tracing tasks.
Prerequisites
l
Procedure
Issue 09 (2014-12-29)
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.
174
BSC6910 UMTS
LMT User Guide
7 Trace Management
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.
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. Time Settings does not need to be set 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.

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

This section describes how to query the trace files on the OMU and upload the trace files onto
the LMT PC as required.
Prerequisites
l
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 File node. The
Manage Trace File dialog box is displayed.
3.
In the displayed Manage Trace File tab page, set the parameters in the Search
Configure area, and then click Query to read the information about the trace files
saved on the OMU.
4.
To upload a trace file to the LMT PC, select the target file listed in the Result area,
set the parameters in the Upload configure area, and then click Upload.

1.
Run the LST TRCRST command to query the trace files.
----End
Issue 09 (2014-12-29)

175
BSC6910 UMTS
LMT User Guide
Performance Monitoring
About This Chapter

This chapter describes how to monitor the BSC6910 performance. A maximum of 64 monitoring
8.1 Concepts Related to Performance Monitoring
This section describes the concepts related to the BSC6910 performance monitoring: monitoring
principles and monitoring rights management.
8.2 Common Monitoring
This section describes the common performance monitoring.
8.3 UMTS Monitoring
This section describes the performance monitoring of the UMTS services.
8.4 General Operations of Performance Monitoring
This section describes the general operations applicable to all performance monitoring tasks
conducted on the BSC6910.
8.5 Reference for Performance Monitoring
This section describes the parameters used for performance monitoring.
Issue 09 (2014-12-29)

176
BSC6910 UMTS
LMT User Guide
8.1 Concepts Related to Performance Monitoring

This section describes the concepts related to the BSC6910 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
monitoring of the CPU usage and other real-time performances.
Principles of CPU Usage Monitoring

Figure 8-1 shows the principles of CPU usage monitoring.
Figure 8-1 CPU usage monitoring
The internal procedure of monitoring the CPU usage is as follows:

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

Figure 8-2 shows the principle of monitoring other real-time performances, which is similar to
the principle of message tracing.
Issue 09 (2014-12-29)

177
BSC6910 UMTS
LMT User Guide
Figure 8-2 Real-time performance monitoring
The internal procedure for creating a real-time monitoring task, other than the CPU usage
monitoring, is as follows:
1.
When you create a monitoring task on the LMT, the LMT sends a binary command to the
OMU to create the task.
2.
The OMU assigns a number to the task and sends the command to the debugging module
3.
After receiving the command, the debugging module records the filter parameters in the
filter table and notifies the service module.
4.
The service module updates the local filter table according to the messages from the
debugging module.
The internal procedure for closing a monitoring task is as follows:

1.
When you close the 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 according to the task number.
3.
The debugging module and service module delete the task from the filter table.
The internal procedure for reporting the real-time monitoring data is as follows:
1.
The service module compares the collected data against the local filter table and reports
the qualified messages to the OMU.
2.
The OMU forwards the data to the LMT that creates the task according to the task ID.
3.
The LMT displays the data in a chart or a list on the interface.
8.1.2 Management of Monitoring Operation Rights

You must have the required rights to perform real-time monitoring on the BSC6910.
Operators of the following levels can perform real-time performance monitoring of the BSC:
admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command
group G_10.
GUEST-level users can only perform CPU usage monitoring.
Issue 09 (2014-12-29)

178
BSC6910 UMTS
LMT User Guide
NOTE
Group G_10 consists of binary commands used for tracing and monitoring.
8.2 Common Monitoring

This section describes the common performance monitoring.
8.2.1 Monitoring CPU Usage

This section describes how to query the CPU usage of a board.
Prerequisites
l
The board under monitoring is functional.
Context
NOTICE
This operation affects the CPU usage. Therefore, if the CPU usage reaches 80% or higher, you
are advised to set the monitoring period to five seconds.
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 > Board
CPU Usage Monitoring. The Board CPU Usage Monitoring dialog box is displayed.
Step 3 In the displayed Board CPU Usage Monitoring dialog box, set the parameters as required, and
click Submit.
l Subrack No.: indicates the number of the subrack where the monitored board is located.
l Slot No.: indicates the number of the slot where the monitored board is located.
l Monitor Period(s): indicates the period in which the monitoring results are reported.
----End
Result
After the monitoring task is started, a monitoring window is displayed, showing the real-time
monitoring results by list and chart. The task name and related parameters are displayed on the
title bar of the window.
l
Issue 09 (2014-12-29)
The list shows the real-time monitoring results of the CPU usage of a monitored board.
179
BSC6910 UMTS
LMT User Guide
In the chart, the X coordinate represents hour: minute: second. The Y coordinate represents
the CPU usage in percentage.
8.2.2 Monitoring CPU Usage on Subsystems

This section describes how to monitor CPU usage on board subsystems.
Prerequisites
l
The subsystem under monitoring is functional.
Context
NOTICE
This operation affects the CPU usage. Therefore, if the CPU usage reaches 80% or higher, you
are advised to set the monitoring period to five seconds.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Subsystem
CPU Usage Monitor. The Subsystem CPU Usage Monitor dialog box is displayed.
Step 3 In the displayed Subsystem CPU Usage Monitor dialog box, set the parameters as required,
and click Submit.
l Subrack No.: indicates the number of the subrack where the monitored board is located.
l Slot No.: indicates the number of the slot where the monitored board is located.
l Monitor Period(s): indicates the period in which the monitoring results are reported.
----End
Result
monitoring results in the form of list and chart. The task name and related parameters are
displayed on the title bar of the window.
l
The list shows the real-time monitoring results of the CPU usage of the subsystem of a
monitored board.
the CPU usage in percentage.
8.2.3 Monitoring Transmission Resources

This section describes how to monitor the transmission resources on the Iub interface.
Issue 09 (2014-12-29)

180
BSC6910 UMTS
LMT User Guide
Prerequisites
l
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Transport
Resource RealTime monitoring. The Transport Resource RealTime monitoring dialog box
is displayed.
Step 3 In the Transport Resource RealTime 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.
Physical Port
Indicates the number of the physical port.

Physical Port Type must be specified.
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.
Issue 09 (2014-12-29)

181
BSC6910 UMTS
LMT User Guide
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.
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 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
Issue 09 (2014-12-29)
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.

182
BSC6910 UMTS
LMT User Guide
Statistic Item
(Original)
Description
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
Real-time traffic on a port.
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. 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 IPPOOLPM detection.
Table 8-3 Statistic Item(Statistic)
Issue 09 (2014-12-29)
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.

183
BSC6910 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.
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.
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
Issue 09 (2014-12-29)
Realtime Bandwidth
Bandwidth detected on a port.
RealTimeQueueFlux
Real-time traffic in the service queues on a port.

184
BSC6910 UMTS
LMT User Guide
Statistic Item
(Statistic)
Description
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. 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 IPPOOLPM detection.
----End
8.2.4 Monitoring BER Seconds

This section describes how to detect the BER seconds on an E1/T1 port to monitor the
transmission quality of the link corresponding to the port. If any bit error occurs on the E1/T1
port, you can start this task to obtain data such as Errored Second, Severely Errored Second,
Unavailable Second, Frame Errors, CRC Errors, Bit Error Rate (calculated by CRC Errors).
Based on the data, you can evaluate the operating condition of the transmission network and
find out the causes for the bit errors in combination with the performance of the peer end. The
AOUc board supports this function.
Prerequisites
l
Procedure
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 displayed BERS Monitoring dialog box, set the parameters as required, and click
Submit.
l Subrack No.: indicates the number of the subrack where the E1/T1 link is located.
l Slot No.: indicates the number of the slot where the E1/T1 link is located.
l E1/T1 Link No.: indicates the number of the E1/T1 link.
You can query the settings of the preceding parameters by running the LST E1T1 command.
----End
Issue 09 (2014-12-29)

185
BSC6910 UMTS
LMT User Guide
Result
l
The list shows the real-time monitoring results of Errored Second(s), Errored Second
Ratio(Percent), Severely Errored Second(s), Severely Errored Second Ratio
(Percent), Unavailable Second(s), Frame Errors, CRC Errors, and Error bit receiving
rate.
BER seconds (s) of the monitored link.
NOTE
Related parameters:
l Errored Second: Time interval of one second during which a given digital signal is received with one
or more errors.
l Severely Errored Second: A one-second period which has a bit error ratio >=110-3 or at least one
defect. Time interval of one second during which a given digital signal is received with an error ratio
greater than 1x10-3.
l Unavailable Second: A link is unavailable if 10 consecutive severe error seconds occur. A link is
available if 10 consecutive non-severe error seconds occur. The duration from 10 seconds before a link
becomes unavailable to 10 seconds before the link resumes available is the unavailable duration.
l Frame Errors: indicates the number of received frames that contain an error in the frame payload in
one direction of a single connection.
l CRC Errors: indicates the number of error bits detected in the CRC check.
l Errored Second: indicates the number of BER seconds.
l Severely Errored Second: indicates the number of severe BER seconds.
l Errored Second Ratio: indicates the ratio of erroneous second (ES) events to total seconds in the
available time during a fixed measurement interval.
l Severely Errored Second Ratio: indicates the ratio of severely erroneous second (SES) events to total
seconds in the available time during a fixed measurement interval.
8.2.5 Monitoring BER

This section describes how to monitor bit error rate (BER), thereby evaluating transport network
quality.
Prerequisites
Context
l
Using this function interrupts transmission of an IMA group, UNI link, fractional ATM
link, carried on a board. Services carried on the corresponding port are therefore affected.
Before starting BER monitoring, you need to configure local loopback at the local end or
configure remote loopback at the peer end. Or you can connect the transmitting end to the
receiving end using a loopback connector.
BER monitoring and a loopback test cannot be performed simultaneously. The result and
principle of these two tasks are the same.
Issue 09 (2014-12-29)

186
BSC6910 UMTS
LMT User Guide
Only one BER monitoring task can be started for one board at a time.
Procedure
Step 1 Click Monitor in the LMT home page. The Monitor tab page is displayed.
Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > BER
Monitoring. The BER Monitoring dialog box is displayed.
Step 3 In the displayed BER Monitoring dialog box, set the parameters as required, and click
Submit.
l Subrack No.: indicates the number of the subrack where the E1/T1 link is located.
l Slot No.: indicates the number of the slot where the E1/T1 link is located.
l Board Type: indicates the type of the board where the E1/T1 link is located.
l Test Time by Minute: indicates the duration of the monitoring task.
l Period(S): indicates the period in which the monitoring results are reported.
l Port No.: indicates the number of the port where the E1/T1 link is located.
l Timeslot No.: indicates the timeslot on the E1/T1 link. This parameter needs to be set for
only interface boards using electrical ports.
You can query the settings of Subrack No., Slot No., Board Type, and Port No. by running
the LST E1T1 command.
----End
Result
monitoring results by list or chart. The task name and related parameters are displayed on the
l
The list shows the real-time monitoring results of Unit BER(UNIT:1E-05) and Total BER
(UNIT:1E-05).
BER (1E-05) of the monitored link.
NOTE
Related parameters:
l Bit Error Ratio: Ratio of received bits that contain errors. BER is an important index used to measure
the communications quality of a network
l Unit BER: indicates the BER in a specified period
l Total BER: indicates the BER in a complete monitoring period
8.2.6 Monitoring Link Performance

This section describes how to monitor link performance. For the same monitoring item, you can
start a maximum of six monitoring tasks simultaneously. One monitoring task corresponds to
one link performance monitoring window. If six tasks are started, when you want to terminate
one of the six monitoring tasks, you must ensure that the link performance monitoring window
for this monitoring task is closed. Otherwise, this monitoring task will continue to occupy
resources. As a result, new monitoring tasks cannot be started.
Issue 09 (2014-12-29)

187
BSC6910 UMTS
LMT User Guide
Monitoring the IMA Group Traffic

This section describes how to monitor the traffic on a specified IMA group in real time. The
real-time traffic on the specified IMA group is displayed in the form of list and chart. Based on
the statistics from the two ends of the IMA group, you can confirm the IE loss, locate the fault,
and evaluate the network transmission quality. You can also compare the actual traffic volume
with the user volume and obtain the utilization of the port. In addition, you can evaluate the
bandwidth condition and decide whether to add a link to the IMA group for capacity expansion.
Prerequisites
Context
NOTICE
The IMA group must be successfully set up and connected to the peer end 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 displayed Link Performance Monitoring dialog box, set Monitor Item to IMA
Group. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the IMA group is located.
l Slot No.: indicates the number of the slot where the IMA group is located.
l IMA Group No.: indicates the number of the IMA group.
You can query the settings of the preceding parameters by running the LST IMAGRP command.
----End
Result
l
The list shows the real-time monitoring results of Rx Traffic(bps), Tx Traffic(bps), Cell
receiving speed(cps), and Cell sending speed(cps).
In the chart, the X coordinate represents the hour: minute: second. The Y coordinate
represents the RX and TX traffic in bit/s.
Issue 09 (2014-12-29)

188
BSC6910 UMTS
LMT User Guide
Monitoring the UNI Link Traffic

This section describes how to monitor the traffic on a specified UNI link in real time. The realtime traffic on the specified UNI link is displayed in the form of list and chart. Based on the
statistics from the two ends of the UNI link, you can confirm the IE loss, locate the fault, and
evaluate the network transmission quality. You can also compare the actual traffic volume with
the user volume and obtain the utilization of the port. In addition, you can evaluate the bandwidth
condition and decide whether to modify the UNI to IMA.
Prerequisites
Context
NOTICE
The UNI link must be successfully set up and connected to the peer end 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. Set other
parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the UNI link is located.
l Slot No.: indicates the number of the slot where the UNI link is located.
l UNI Link No.: indicates the number of the UNI link.
You can query the settings of the preceding parameters by running the LST UNILNK command.
----End
Result
l
Issue 09 (2014-12-29)

189
BSC6910 UMTS
LMT User Guide
Monitoring the Fractional ATM Link Traffic

This section describes how to monitor the traffic on a specified fractional ATM link in real time.
The real-time traffic on the specified fractional ATM link is displayed in the form of list and
chart. Based on statistics obtained from two ends of the fractional ATM link, you can confirm
the IE loss, locate the fault, and evaluate the network transmission quality. You can also compare
the actual traffic volume with the user volume carried by the current port and obtain the utilization
of the port. In addition, you can evaluate the bandwidth condition and add FRAC ATM links.
Prerequisites
Context
NOTICE
The FRAC ATM link must be successfully set up and connected to the peer end 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. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the FRA link is located.
l Slot No.: indicates the number of the slot where the FRA link is located.
l FRAC Link No.: indicates the number of the FRA link.
You can query the settings of the preceding parameters by running the LST FRALNK command.
----End
Result
l
Issue 09 (2014-12-29)

190
BSC6910 UMTS
LMT User Guide
Monitoring the SAAL Link Traffic

This section describes how to monitor the traffic on a specified SAAL path in real time. The
real-time traffic on the specified SAAL path is displayed in the form of list and chart. Based on
the transmit/receive statistics on the SAAL of the subsystem, you can confirm the packet loss,
locate the SAAL disconnection or intermittence problem. You can also predict the congestion
by comparing the traffic with the configured bandwidth.
Prerequisites
Context
NOTICE
The SAAL must be successfully set up and connected to the peer end before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SAAL Link. Set other
SAAL Link No.: indicates the number of the SAAL link. You can query the setting of the
preceding parameter by running the LST SAALLNK command.
----End
Result
l
Monitoring the IPoA PVC Traffic

This section describes how to monitor the traffic on a specified IPoA PVC in real time. The realtime traffic on the specified IPoA PVC is displayed in the form of list and chart. If the IPoA
PVC carries the OML for the ATM-based BTS, you can perform this task to observe the traffic
and bandwidth utilization when the NodeB is loading data and to locate the fault in the NodeB
Issue 09 (2014-12-29)

191
BSC6910 UMTS
LMT User Guide
startup and data loading processes. If the IPoA PVC carries the IP path over the Iu-PS interface,
you can perform this function to observe the traffic flow and locate the connection and congestion
status of the upper layer link.
Prerequisites
Context
NOTICE
The IPoA PVC must be successfully set up and connected to the peer end before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPOA PVC. Set other
l Subrack No.: indicates the number of the subrack where the IPoA PVC is located.
l IP Address: indicates the local IP address of the IPoA PVC.
l IP Address: indicates the peer IP address of the IPoA PVC.
You can query the settings of the preceding parameters by running the LST IPOAPVC
command.
----End
Result
l
Monitoring the AAL2 Path Traffic

This section describes how to monitor the traffic on a specified AAL2 path in real time. The
real-time traffic on the specified AAL2 path is displayed in the form of list and chart. Based on
the layer 2 transmit/receive statistics obtained from the CDT trace, you can confirm the packet
Issue 09 (2014-12-29)

192
BSC6910 UMTS
LMT User Guide
loss and evaluate the traffic condition. In addition, you can predict the congestion based on the
traffic conditions on the link.
Prerequisites
Context
NOTICE
The AAL2 path must be successfully set up and connected to the peer end before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to AAL2 Path. Set other
l Subrack No.: indicates the number of the subrack where the AAL2 path is located.
l Adjacent Node ID: indicates the ID of the adjacent node corresponding to the AAL2 path.
l AAL2 PATH Symbol: indicates the number of the AAL2 path.
You can query the settings of the preceding parameters by running the LST AAL2PATH
command.
----End
Result
l
Monitoring FE/GE Traffic

This section describes how to monitor the traffic on a specified FE/GE port in real time. The
real-time traffic on the specified FE/GE port is displayed in the form of list and chart. Based on
the traffic carried by the FE/GE port, you can confirm the packet loss, locate the fault, and
evaluate the network transmission quality. You can also compare the actual traffic volume with
Issue 09 (2014-12-29)

193
BSC6910 UMTS
LMT User Guide
the user volume carried by the current port and obtain the utilization of the port. In addition, you
can evaluate the bandwidth condition and decide whether to swap the services to avoid
congestion.
Prerequisites
Context
NOTICE
The FE/GE port must be successfully configured and connected to the peer end before this task
For the FG2c, GOUc, GOUe boards, if the physical port carries a logical port and Monitor
Type for the link performance monitoring task is set to QoS, the queue statistics of the physical
port does not include the service data traffic on the logical port but only the service data traffic
on the physical port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to FE/GE. Set other
l Subrack No.: indicates the number of the subrack where the FE/GE link is located.
l Slot No.: indicates the number of the slot where the FE/GE link is located.
l Monitor Type: You can set this parameter to Port or QoS.
l FE/GE Port No.: indicates the number of the port where the FE/GE link is located.
l Priority Group No.: If Monitor Type is set to QoS, you need to set this parameter to specify
the priority queue of a packet on the FE/GE port.
You can query the settings of the preceding parameters by running the LST ETHPORT
command.
----End
Result
l
Issue 09 (2014-12-29)
When Monitor Type is set to Port, the list shows the real-time monitoring results of Rx
Traffic(bps), Tx Traffic(bps), Packet receiving number, Error packet receiving rate
194
BSC6910 UMTS
LMT User Guide
(1/10000), Packet receiving speed(pps), and Packet sending speed(pps). When Monitor
Type is set to QoS, the list shows the real-time monitoring results of Tx Traffic(bps) and
Packet sending speed(pps).
l
Monitoring the SCTP Link Traffic

This section describes how to monitor the traffic on a specified SCTP path at the SCTP layer in
real time. The real-time traffic on the specified SCTP path is displayed in the form of list and
chart. Based on the transmit/receive statistics on the SCTP of the subsystem, you can confirm
the packet loss, locate the SCTP disconnection or intermittence problem. In addition, you can
predict the congestion based on the traffic conditions on the link.
Prerequisites
Context
NOTICE
The SCTP link must be successfully set up and connected to the peer end before this task is
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SCTP Link. Set other
SCTP Link ID: indicates the number of the SCTP link. You can query the setting of the
preceding parameter by running the LST SCTPLNK command.
----End
Result
l
The list shows the real-time monitoring results of Rx Traffic(bps), Tx Traffic(bps),

Packet receiving speed(pps), and Packet sending speed(pps).
represents the RX and TX traffic in kbit/s.
Issue 09 (2014-12-29)

195
BSC6910 UMTS
LMT User Guide
Monitoring Traffic on a Logical Port

This section describes how to monitor the traffic on a specified logical port. You can monitor
an entire port, where the monitoring results display the real-time traffic of the current logical
port. You can also monitor only the specified priority of the port, where the monitoring results
display the TX traffic of the specified priority of the current logical port. Based on the traffic
statistics at the logical port, you can confirm the packet loss at the logical port and locate the
fault. You can also compare the actual traffic volume with the user volume and obtain the
utilization of the port. In addition, you can evaluate the bandwidth condition and decide whether
to expand the configuration bandwidth of the logical port.
Prerequisites
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Logical Port. Set other
l Subrack No.: indicates the number of the subrack where the logical port is located.
l Slot No.: indicates the number of the slot where the logical port is located.
l Port No.: indicates the number of the logical port. You can query the logical ATM port
number by running the LST ATMLOGICPORT and query the logical IP port number by
running the LST IPLOGICPORT command.
the priority queue of a packet on the logical port.
----End
Result
l
The list shows the real-time monitoring results of Tx Traffic(bps) and Packet sending
speed(pps).
represents the real-time traffic of the current logical port in bit/s.
Monitoring OAM Traffic

This section describes how to monitor the RX and TX traffic on the operation and maintenance
(OAM) channel at the IP layer of an interface board in a specified NodeB. The OAM traffic on
the current NodeB is displayed in the form of list and chart. You can perform this task to observe
Issue 09 (2014-12-29)

196
BSC6910 UMTS
LMT User Guide
the traffic and bandwidth usage when the NodeB is loading data. Therefore, you can locate the
fault in the NodeB startup and data loading processes.
Prerequisites
l
The LMT is running normally.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to OAM. Set other
l Subrack No.: indicates the number of the subrack where the O&M IP address of the NodeB
is located.
l NodeB ID: indicates the number of the NodeB.
You can query the settings of the preceding parameters by running the LST UNODEB
command.
----End
Result
l

represents the RX and TX traffic of the NodeB OM channel in bit/s.
Monitoring Traffic on Non-Channelized Optical ATM Port

This section describes how to monitor the traffic on a specified non-channelized ATM optical
port in real time. The real-time traffic on this port is displayed in the form of list and chart. Based
on the statistics on the non-channelized ATM optical ports at both ends, you can check the IE
loss, locate the fault, and evaluate the network transmission quality. You can also compare the
actual traffic volume with the user volume and obtain the utilization of the port. In addition, you
can evaluate the bandwidth condition and decide whether capacity expansion is required.
Prerequisites
Issue 09 (2014-12-29)

197
BSC6910 UMTS
LMT User Guide
Context
NOTICE
The specified non-channelized ATM optical port is connected to the peer end.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Non-Channelized
ATM Optical Port. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the unchannelized ATM optical
port.
l Slot No.: indicates the number of the slot where the unchannelized ATM optical port.
l Optical Port No.: indicates the number of the unchannelized ATM optical port.
You can query the settings of the preceding parameters by running the LST OPT command.
----End
Result
l
In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms), and the Y
coordinate represents the RX and TX traffic in the unit of bit/s.
Monitoring IPPOOL PM Traffic

This section describes how to monitor traffic on the specified IPPOOL PM link in IP transmission
resource pool networking in real time, which is displayed by lists and charts. Together with
statistics on the IPPOOL PM link on the transmitting and receiving sides, the function can be
used to confirm packet loss and locate disconnection or intermittence in IP pool networking.
The function can also be used to predict congestion based on the traffic conditions on the link.
Prerequisites
Issue 09 (2014-12-29)

198
BSC6910 UMTS
LMT User Guide
Context
NOTICE
The IPPOOL PM link to be monitored is activated.
Procedure
Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > Link
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL PM. Set other
l Subrack No.: indicates the number of the subrack where the local IP address of the IP pool
is located.
l Adjacent Node ID: indicates the ID of the adjacent node that uses the IP pool. You can query
the setting of this parameter by running the LST IPPOOLPM command.
l Local IP Address: indicates the local IP address of the IP pool. You can query the setting
of this parameter by running the DSP ADJNODE command.
l Peer IP Address: indicates the peer IP address learnt by the IP pool. You can query the
setting of this parameter by running the DSP ADJNODEDIP command.
l Priority: indicates the priority of services with different DSCPs.
----End
Result
After the monitoring task has started, a monitoring window is displayed showing the real-time
monitoring results by lists and charts. The task name and related parameters are displayed on
the title bar of the window.
l
Based on the setting of Priority, the list shows the real-time monitoring results of Mean
bit sending speed(bps), Mean packet sending speed(bps), Peer mean bit sending speed
(bps), Peer mean packet sending speed(pps), Forward packet loss rate(1/100000),
Backward packet loss rate(1/100000), Forward mean jitter square(ms), and RTT
mean delay(ms).
the RX and TX traffic in the unit of bit/s.
Monitoring the Trunk Group

This section describes how to monitor the traffic on a specified trunk group in real time. The
real-time traffic on the specified trunk group is displayed in the form of list and chart. Together
with the statistics at both ends of the trunk group, the function can be used to confirm the IE
loss, help locate the fault, and evaluate the transmission network quality. The function can be
also used to compare the actual traffic volume with the user volume and obtain the utilization
Issue 09 (2014-12-29)

199
BSC6910 UMTS
LMT User Guide
of the port. In addition, the function can be used to evaluate the bandwidth condition and decide
whether to add a link to the trunk group for capacity expansion.
Prerequisites
Context
NOTICE
The trunk group to be monitored is configured successfully.
Procedure
Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to TRUNK
Group. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the TRUNK group is located.
l Slot No.: indicates the number of the slot where the TRUNK group is located.
l TRUNK Group No.: indicates the number of the TRUNK group.
You can query the settings of the preceding parameters by running the LST ETHTRK
command.
----End
Result
l

Packet receiving speed(pps), Packet sending speed(pps), Packet receiving number,
Packet sending number, Error packet receiving number, Loss packet sending
number, Error packet receiving rate(1/10000), Loss packet sending rate(1/10000).
In the chart, the X coordinate represents the time; the Y coordinate represents the
monitoring results in such a unit as bps or pps, depending on the report result.
Monitoring IPPOOL LOCAL IP Traffic

This section describes how to monitor traffic on the specified local port in IP transmission
resource pool networking in real time, which is displayed by lists and charts. The statistics
facilitate fault diagnosis and transmission quality evaluation. With usage of the local port
estimated, users can be reminded to take measures to prevent congestion.
Issue 09 (2014-12-29)

200
BSC6910 UMTS
LMT User Guide
Prerequisites
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL LOCAL
IP. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the local IP address of the IP pool
is located.
l Slot No.: indicates the number of the slot where the local IP address of the IP pool is located.
l Local IP Address: indicates the local IP address of the IP pool.
You can query the settings of the preceding parameters by running the LST IPPOOLIP
command.
----End
Result
After the monitoring task has started, a monitoring window is displayed showing the real-time
monitoring results by lists and charts. The task name and related parameters are displayed on
the title bar of the window.
l
the RX and TX traffic in the unit of bit/s.
Monitoring IURP Link Traffic

This section describes how to monitor the traffic on a specified IURP Link in real time and view
the real-time traffic on the IURP Link in tables and figures. This function enables you to: Check
whether data packets are lost, locate the problem, and evaluate the transmission network quality.
And query the real-time traffic so that users can accordingly adjust the IURP interface resources
to avoid congestion.
Prerequisites
Issue 09 (2014-12-29)

201
BSC6910 UMTS
LMT User Guide
Context
NOTICE
The IURP Link must be successfully configured and connected to the peer end before this task
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IURPLNK. Set other
l External Node: indicates the ID of the external node.
l Link Set Index: indicates the number of the link set.
l Link No.: indicates the number of the link.
You can query the settings of External Node, Link Set Index, and Link No. by running the
LST IURPLNK command.
----End
Result
l

Monitoring 10GE Traffic

This section describes how to monitor the traffic on a specified 10GE port in real time and view
the real-time traffic on the 10GE port in tables and figures. This function enables you to: Check
whether data packets are lost, locate the problem, and evaluate the transmission network quality.
Check whether the current traffic is equal to the traffic carried on the port and check the port
utilization. Check whether the bandwidth is sufficient and notify users of performing service
transfer, avoiding traffic congestion.
Prerequisites
Issue 09 (2014-12-29)

202
BSC6910 UMTS
LMT User Guide
Context
NOTICE
The 10GE port must be successfully configured and connected to the peer end before this task
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to 10GE. Set other
l Subrack No.: indicates the number of the subrack where the 10GE link is located.
l Slot No.: indicates the number of the slot where the 10GE link is located.
l 10GE Port No.: indicates the number of the port where the 10GE link is located.
the priority queue of a packet on the 10GE port.
You can query the settings of Subrack No., Slot No., and 10GE Port No. by running the LST
ETHPORT command.
----End
Result
l
When Monitor Type is set to Port, the list shows the real-time monitoring results of Rx
Traffic(bps), Tx Traffic(bps), Packet receiving number, Error packet receiving rate
(1/10000), Packet receiving speed(pps), and Packet sending speed(pps). When Monitor
Type is set to QoS, the list shows the real-time monitoring results of Tx Traffic(bps) and
Packet sending speed(pps).
8.3 UMTS Monitoring

This section describes the performance monitoring of the UMTS services.
Issue 09 (2014-12-29)

203
BSC6910 UMTS
LMT User Guide
8.3.1 Monitoring Connection Performance

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

This section describes how to monitor in real time the P-CPICH Ec/No and RSCP of a cell in
the active set. The monitoring result, including the number of cells in the active set and the signal
strength of each cell, is displayed in a chart. By performing this task, you can learn about whether
the current connection is at the edge or the center of the cell.
Prerequisites
Context
NOTICE
Before running this monitoring task, you need to perform one of the following operations:
l Run SET UCORRMALGOSWITCH to set Handover algorithm switch. Ensure that
SOFT_HANDOVER_SWITCH is selected.
l Run MOD UCELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE.
NOTE
l This task applies to only monitoring connections established on dedicated channels. An ongoing task
is stopped if the monitored connection is released or transited from the dedicated channel to the common
channel. The task is restarted if the monitored connection is transited from the common channel back
to the dedicated channel.
l This task is performed to monitor only 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 variation of 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 each 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 displayed Connection Performance Monitoring dialog box, set Monitor Item to
PCPICH Ec/No RSCP. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

204
BSC6910 UMTS
LMT User Guide
NOTE
A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. The
task name is indicated in the title bar of the window.
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 stands for Received Signal Code Power. It is the received power on one code measured on the PCPICH. The reference point for measurement of the RSCP is at the antenna connector of the UE. If the PCPICH uses transmit diversity, you need to measure the RSCP of each antenna and sum up all of the RSCP
values. Then you can obtain the total RSCP of the P-CPICH.
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 measurement is also at the antenna connector of the
UE. If the P-CPICH adopts transmit diversity, the total Ec value of all antennas must be measured to calculate
the Ec/No.
NOTE
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 track records after you finish processing data.
l 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.
l 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.
l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI data
is directly entered in IMSI.
l Change the anonymous policy and cipher key on the M2000 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 M2000
Fault Management User Guide.
l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the
monitoring task. Otherwise, the monitoring task becomes invalid.
l For details about how to obtain the HMACUtil, contact Huawei technical support.
----End
Monitoring SIR of the Uplink RLS

This section describes how to monitor in real time the SIR values of the uplink radio link sets
(RLSs) used by the UE. By performing this task, you can learn about the uplink radio link quality
and the quality variations.
Prerequisites
Context
NOTE
Each task can monitor only one UE. The monitoring result includes the number of cells in the active set
and the signal strength of each cell. From the monitoring result, you can know whether the current
connection is at the edge or the center of the cell.
Issue 09 (2014-12-29)

205
BSC6910 UMTS
LMT User Guide
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to UL
SIR. Set other parameters as required, and then click Submit.
NOTE
task name is indicated in the title bar of the window. The monitoring results reflect the variation of 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 calculation formula of SIR is (RSCP/ISCP) x SF, where:
l RSCP stands for Received Signal Code Power. It is the received power on one code.
l ISCP stands for Interference Signal Code Power. Only the non-orthogonal part of received interference
signals is measured.
l SF stands for the spreading factor of the DPCCH.
The measurement is performed on the DPCCH selected after radio links are combined on the NodeB. In
compressed mode, the SIR during the transmit intervals is not measured. The NodeB reports the measured SIR
values on the uplink to the BSC6910.
----End
Monitoring the Outer Loop Power Control

This section describes how to monitor the values of related parameters during outer loop power
control. Only the parameters related to the current service type are displayed. Related 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 E-DCH Residual BLER.
Prerequisites
Procedure
OLPC. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

206
BSC6910 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.
task name is indicated in the title bar of the window. In the chart, the X-coordinate represents the hour: minute:
second. Two small charts are respectively used to describe the five monitoring items.
l The first small 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 small 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 ( unit: none).
By default, the coordinate value ranges from 0 to 16. The coordinate value range can be dynamically adjusted
based on the actual value of E-DCH Average Transmission Number. 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 real-time SIR error values of radio link sets (RLSs)
of the current connection. 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 vary all the time but converge around 0 dB, you can infer that the UL
inner loop power control converges. Otherwise, the UL inner loop power control does not
converge.
Prerequisites
Context
This task applies to only monitoring connections established on dedicated channels. An ongoing
task is stopped if the monitored connection is released or transited from the dedicated channel
to the common channel. The task is restarted if the monitored connection is transited from the
common channel back to the dedicated channel.
Procedure
SIR Error. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

207
BSC6910 UMTS
LMT User Guide
NOTE
of the RLSs in real time.
SIR error values (SIRerror) of the UL RLSs.
l SIRerror (unit: dB) is reported to the BSC6910 by the NodeB. The calculation formula is 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 above formula of SIRerror.
l In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave in the transmission gap is not
calculated. 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 variation of 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, even approximately up to the maximum value
configured in the signaling message, it indicates that the link experiences a degraded quality.
Prerequisites
Context
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to DL
Tx Code Power. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

208
BSC6910 UMTS
LMT User Guide
NOTE
of the radio links involved in the current connection in real time.
In the chart, 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 adopted, the
DL code TX power is the total of the code TX powers of all antennas.
----End
Monitoring the UE TX Power

This section describes how to monitor in real time the variation of the UE TX power on the
current connection. By performing this task, you can analyze the UL quality of the radio link.
If the UE TX power increases, even reaching the limit of the UE capability, you can infer that
the radio link experiences a degraded UL quality.
Prerequisites
Context
UE TX power refers to the UE TX power in 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 displayed Connection Performance Monitoring dialog box, set Monitor Item to UE
Tx Power. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UE
TX power (unit: dBm).
----End
Issue 09 (2014-12-29)

209
BSC6910 UMTS
LMT User Guide
Monitoring UL Traffic
This section describes how to monitor in real time the variation in the UL traffic (that is, the
buffered data volume at the UE side) on the current connection. By performing this task, you
can analyze the transmission performance of UL traffic. The UL traffic is measured by the UE
and reported to the BSC6910 on the basis of the transport channel.
Prerequisites
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 each 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 monitor the connections of PS domain interactive and background services on both
common channels and dedicated channels.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL Traffic
Vol. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UL
traffic on the UL physical channel (unit: byte).
----End
Monitoring DL Traffic
This section describes how to monitor in real time the variation in the DL traffic (that is, the
buffered data volume on the MSC side) on the current connection. By performing this task, you
can analyze the transmission performance of DL traffic. The DL traffic is measured at the
BSC6910 on the basis of transport channel.
Prerequisites
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 each logical channel. If RLC is in
Issue 09 (2014-12-29)

210
BSC6910 UMTS
LMT User Guide
acknowledgment 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.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Traffic
Vol. Set other parameters as required, and then click Submit.
NOTE
traffic (unit: byte).
----End
Monitoring UL Throughput and Bandwidth

This section describes how to monitor in real time the rate variations on the UL transport access
stratum and non-access stratum of the current connection. By performing this task, you can
analyze the function of dynamic channel configuration and characteristics of the service source
rate variations.
Prerequisites
Context
Throughput refers to the amount of data transmitted on a transport channel in a unit of time.
Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculated
according to RLC payload. The bandwidth changes in RB reconfiguration. The throughput
measurement involves RLC headers, and therefore, the measured peak throughput is higher than
the bandwidth.
Procedure
Throughput Bandwidth. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

211
BSC6910 UMTS
LMT User Guide
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UL
throughput and UL bandwidth (unit: bit/s).
l If the UL bandwidth varies with the UL throughput, you can infer that the dynamic channel configuration
function is normal.
l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristics
of UL service source by observing the variation of UL throughput.
----End
Monitoring DL Throughput and Bandwidth

This section describes how to monitor in real time the rate variations on the DL transport access
stratum and non-access stratum of the current connection. By performing this task, you can
analyze the function of dynamic channel configuration and characteristics of the service source
rate variations.
Prerequisites
Context
Throughput refers to the amount of data transmitted on a transport channel in a unit of time.
Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculated
according to RLC payload. The bandwidth changes in RB reconfiguration. The throughput
measurement involves RLC headers, and therefore, the measured peak throughput is higher than
the bandwidth.
Procedure
Throughput Bandwidth. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

212
BSC6910 UMTS
LMT User Guide
NOTE
throughput and DL bandwidth (unit: bit/s).
l If the DL bandwidth increases/decreases with the increase/decrease of DL throughput, you can infer that
the dynamic channel configuration function is normal.
l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristics
of DL service source by observing the variation of DL throughput.
----End
Monitoring Handover Delay

This section describes how to monitor the handover delay.
Prerequisites
Context
Handover delay refers to the time taken by each handover. During this period of time, the
BSC6910 performs a handover decision, initiates the handover (including the soft handover and
the hard handover), and completes the handover.
This task can be performed to monitor the handover delay of only 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 handover delay monitoring tasks can be started simultaneously. This task
can monitor the delay of an intra-frequency or inter-frequency handover but not an inter-RAT
handover.
Procedure
Handover Delay. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)
Monitoring
Results
Description
HO Delay(ms)
Time taken by each handover
HO Interval(ms)
Time difference between the end of the last handover and the end of
the current handover

213
BSC6910 UMTS
LMT User Guide
NOTE
In the chart, the X coordinate represents the hour: minute: second. The Y-coordinate represents the interval of
each successful handover (unit: ms).
----End
Monitoring the BLER of the DL Transport Channel

This section describes how to monitor in real time the variation in the BLER values measured
on all transport channels of the current connection. By performing this task, you can analyze the
DL quality of the radio link. If the BLER of the DL transport channel increases, you can infer
that the DL quality declines. If the BLER decreases, you can infer that the DL quality is improved.
Prerequisites
Context
The BLER of the DL transport channel is measured at the UE. The BLER is used for outer loop
power control.
Procedure
BLER. Set other parameters as required, and then click Submit.
NOTE
of traffic transport channels in real time. The number of signaling transport channels is always 1.
BLER of the DL transport channel (unit: %).
----End
Monitoring the AMR Mode

This section describes how to monitor in real time the variation in the configured AMR rate.
Issue 09 (2014-12-29)

214
BSC6910 UMTS
LMT User Guide
Prerequisites
Context
The monitoring is valid only when the traced UE has an AMR service in process.
The narrowband AMR has eight available rates, that is, eight available 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 available 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 displayed Connection Performance Monitoring dialog box, set Monitor Item to AMR
Mode. Set other parameters as required, and then click Submit.
NOTE
In the chart, 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
8.3.2 Monitoring Cell Performance

This section describes how to monitor the cell performance, such as the common measurement
statistics and number of UEs on the common channel. For the same monitoring item, you can
start a maximum of six tasks simultaneously.
Monitoring Cell P-CPICH TX Power

The monitoring is performed on the PCPICH TX power of a specified cell. By performing this
task, you can observe and judge in real time whether the pilot power is normal.
Prerequisites
Context
The value range of the P-CPICH TX power can be obtained by running the LST UPCPICH
command. If the pilot power is outside the range, you can infer that the power is abnormal.
Issue 09 (2014-12-29)

215
BSC6910 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 displayed Cell Performance Monitoring dialog box, set Monitor Item to PCPICH
TxPower. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the P-CPICH
power (unit: dBm).
----End
Monitoring UL RX Total Wideband Power of a Cell

This section describes how to monitor the UL RX total wideband power (RTWP) in a specified
cell. By performing this task, you can observe the UL load level in real time. The UL RX total
wideband power is measured and reported by the related NodeB.
Prerequisites
Context
The CAC procedure measures the UL load by the UL load factor (UL load factor = 1 - cell
background noise/UL RX total wideband power). The background noise of the cell approximates
to a constant, which can be set through the command ADD UCELLCAC or MOD
UCELLCAC. Therefore, the UL RX total wideband power can also be used to measure the
relative level of the UL load of the cell.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to RTWP. Set
other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents hour: minute: second. The Y-coordinate represents the cell UL RX total
wideband power (unit: dBm).
----End
Issue 09 (2014-12-29)

216
BSC6910 UMTS
LMT User Guide
Monitoring DL TX Power in a Cell

This section describes how to monitor the DL transmit (TX) power of a specified cell. By
performing this task, you can observe the DL load level in real time. The DL TX power of a cell
is measured and reported by the related NodeB.
Prerequisites
Context
The CAC procedure 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. 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 displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell DL
Carrier TX Power. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ratio of the
DL TX carrier power to the maximum TX power of the cell (unit: %).
----End
Monitoring User Volume in Cell

This section describes how to monitor in real time the number of users on the common channel,
dedicated channel, HSDPA channel, and HSUPA channel in a specified cell. You can also learn
about the distribution of the users in the cell.
Prerequisites
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell User
Number. Set other parameters as required, and then click Submit.
Issue 09 (2014-12-29)

217
BSC6910 UMTS
LMT User Guide
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the number of
cell users.
----End
Monitoring Node Synchronization

This section describes how to monitor the time difference between RNC Frame Number (RFN)
and NodeB Frame Number (BFN) of the specified cell and the time taken for node
synchronization. By performing this task, you can observe the float between the RFN and BFN
in real time. If the difference between RFN and BFN varies too rapidly, you can infer that there
are some problems on the transmission between the BSC6910 and the NodeB.
Prerequisites
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Node Sync.
Set other parameters as required, and then click Submit.
NOTE
In the chart, 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 finish 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 judge the prediction accuracy of the UL CAC algorithm.
The monitoring results are periodically reported and are also reported when users access the cell.
Prerequisites
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC
algorithm 2). Run MOD UCELLALGOSWITCH to set the UL CAC algorithm of a cell. Run
LST UCELLALGOSWITCH to query the UL CAC algorithm of a cell.
Issue 09 (2014-12-29)

218
BSC6910 UMTS
LMT User Guide
CAC algorithm 1 measures the UL load by the UL load factor (UL load factor = 1 - cell
background noise/UL RX total wideband power). 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 to the maximum number of UL
equivalent users to measure the load of the cell. By default, algorithm 2 is used to measure
the UL load of the cell.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to UL CAC
Monitor. Set other parameters as required, and then click Submit.
NOTE
In the chart, 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 of the predicted values and
measured values of the DL load and judge the prediction accuracy of the DL CAC algorithm.
The monitoring results are periodically reported and are also reported when users access the cell.
Prerequisites
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC
algorithm 2). Run MOD UCELLALGOSWITCH to set the DL CAC algorithm of a cell. Run
LST UCELLALGOSWITCH 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 to measure the
DL load of the cell. The maximum TX power is a constant. You can run ADD
UCELLSETUP to set it.
CAC algorithm 2 uses the ratio of the current DL equivalent number of users to the
maximum DL equivalent number of users.
Procedure
Issue 09 (2014-12-29)

219
BSC6910 UMTS
LMT User Guide
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL CAC
Monitor. Set other parameters as required, and then click Submit.
NOTE
values and measured values of the load (unit: %).
----End
Monitoring the Number of UL Equivalent Users

This section describes how to monitor the number of UL equivalent users in a specified cell. By
performing this task, you can observe the variation in the number of UL equivalent users. The
monitoring results are periodically reported and are also reported when users access the cell.
Prerequisites
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to UL Total
Equivalent User Number. Set other parameters as required, and then click Submit.
NOTE
values and measured values of the number of UL equivalent users.
----End
Monitoring the Number of DL Equivalent Users

This section describes how to monitor the number of DL equivalent users in a specified cell. By
performing this task, you can observe the variation in the number of DL equivalent users. The
monitoring results are periodically reported and are also reported when users access the cell.
Prerequisites
Issue 09 (2014-12-29)

220
BSC6910 UMTS
LMT User Guide
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL Total
Equivalent User Number. Set other parameters as required, and then click Submit.
NOTE
values and measured values of the number of DL equivalent users.
----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.
Prerequisites
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell Code
Tree Monitor. Set other parameters as required, and 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 Required Power of the HS-DSCH

This section describes how to monitor in real time the minimum required power of the HS-DSCH
of 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.
Prerequisites
Issue 09 (2014-12-29)

221
BSC6910 UMTS
LMT User Guide
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Min Power Requirement. Set other parameters as required, and then click Submit.
NOTE
In the chart, 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 Bit Rate Provided by the HS-DSCH

This section describes how to monitor the bit rate on the HS-DSCH of a specified cell. By
performing this task, you can observe the variation in the transmission rate on the HS-DSCH in
real time.
Prerequisites
Context
NOTE
During the bit rate monitoring on the HS-DSCH, if HSDPA_PBR_MEAS is set to 0, the bit rate on the
HS-DSCH of the cell is not reported. HSDPA_PBR_MEAS indicates whether to perform HSDPA PBR
measurement.
Run the LST UCELLALGOSWITCH command on the MML client to query the state of
HSDPA_PBR_MEAS switch. If the queried result is HSDPA PBR MEAS ALGORITHM:OFF, run the
MOD UCELLALGOSWITCH command to set it to 1.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Provide Bitrate. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:
bit/s).
----End
Issue 09 (2014-12-29)

222
BSC6910 UMTS
LMT User Guide
Monitoring the Bit Rate Provided by the E-DCH

This section describes how to monitor the bit rate on the enhanced dedicated channel (E-DCH)
for HSUPA services. By performing this task, you can observe the variation in the transmission
rate on the E-DCH in real time.
Prerequisites
Context
NOTE
During the bit rate monitoring on the E-DCH, if HSUPA_PBR_MEAS is set to 0, the bit rate on the EDCH of the cell is not reported. HSUPA_PBR_MEAS indicates whether to perform HSUPA PBR
measurement.
Run the LST UCELLALGOSWITCH command query the state of HSUPA_PBR_MEAS switch. If the
queried result is HSUPA PBR MEAS ALGORITHM:OFF, run the MOD UCELLALGOSWITCH
command to set it to ON.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to E-DCH
Provided Bitrate. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:
bit/s).
----End
Monitoring UL Throughput of a Cell

This section describes how to monitor the UL throughput of a cell. Throughput refers to the
maximum traffic rate that an entity can endure without discarding the frames.
Prerequisites
Procedure
Issue 09 (2014-12-29)

223
BSC6910 UMTS
LMT User Guide
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell UL
Throughput. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the UL
throughput of the cell.
----End
Monitoring DL Throughput of a Cell

This section describes how to monitor the DL throughput of a cell. Throughput refers to the
maximum traffic rate that an entity can endure without discarding the frames.
Prerequisites
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell DL
Throughput. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the DL
throughput of the cell.
----End
Monitoring Cell Credit

This section describes how to monitor the credit conditions of the local cell, the local cell group,
and the corresponding NodeB. Based on the monitoring result, the BSC6910 determines whether
a UE can access the network.
Prerequisites
Procedure
Issue 09 (2014-12-29)

224
BSC6910 UMTS
LMT User Guide
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell Credit. Set other
NOTE
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the number of
Local Cell Credit and Local Cell Group/NodeB Total Credit of the cell.
----End
Monitoring the FDPCH SYMBOL

This section describes how to monitor the condition of the F-DPCH SYMBOL, including the
F-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.
Prerequisites
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 displayed Cell Performance Monitoring dialog box, set Monitor Item to FDPCH
SYMBOL monitoring. Set other parameters as required, and 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.
l In the view of the FDPCH SYMBOL monitoring, you can view the condition of the SYMBOL corresponding
to the F-DPCH code. The numbers in the grids indicate the timeslot formats.
----End
8.3.3 Monitoring System Resources

This section describes how to monitor the licensed Erlang value and the PS user plane throughput
of system in real time.
Prerequisites
Issue 09 (2014-12-29)

225
BSC6910 UMTS
LMT User Guide
Context
NOTE
l This task can be performed only through menu operations and applies to the system running properly.
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 as required, and click
Submit.
NOTE
After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring result
in the form of list and chart. The task name and related parameters are displayed on the title bar of the window.
In the chart, the X coordinate represents the hour: minute: second. The Y-coordinate represents the usage of the
license. (Unit: Erl and kbit/s)
----End
8.3.4 Iurp Monitoring

This section describes how to monitor and specify the delay of Iurp links between two external
controllers to observe and determine in real time whether the delay of Iurp links is normal.
Prerequisites
Context
l
When RNC in Pool Load Sharing is enabled, the requirements for the Iur-p interface are
as follows: The one-way transmission delay must not exceed 10 ms. Any value greater than
10 ms is considered abnormal.
When RNC in Pool Node Redundancy is enabled, the requirements for the Iur-p interface
are as follows: The one-way transmission delay must not exceed 100 ms. Any value greater
than 100 ms is considered abnormal.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > Iurp
Monitoring. The Iurp Monitoring dialog box is displayed.
Step 3 In the Iurp Monitoring dialog box, set the parameters as required, and click Submit.
Issue 09 (2014-12-29)

226
BSC6910 UMTS
LMT User Guide
NOTE
After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring result
in the form of list and chart. The task name and related parameters are displayed on the title bar of the window.
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the delay of Iurp
links. (Unit: 0.125 ms)
----End
8.4 General Operations of Performance Monitoring

This section describes the general operations applicable to all performance monitoring tasks
conducted on the BSC6910.
8.4.1 Browsing the Monitoring Results Online

This describes how to browse online and query the monitoring results that are dynamically
displayed in the monitoring window in real time.
Prerequisites
l
A performance monitoring task is started.
Monitoring results are reported.
Right-click on the Chart tab page in the real-time performance monitoring window. Then,
you can perform the following operations by selecting the corresponding item from the
shortcut menu:
Procedure
Setting auto scroll

Showing or hiding the grid
Switching the display mode
Auto Adjust
l
Right-click on the List tab page in the real-time performance monitoring window. Then,
you can perform the following operations by selecting the corresponding item 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 the
corresponding item from the shortcut menu:
Adding or deleting tasks
Stopping or restarting tasks
Querying details of tasks
----End
Issue 09 (2014-12-29)

227
BSC6910 UMTS
LMT User Guide
8.4.2 Setting the Display Mode of the Chart

This section describes how to set the display mode of the chart in the real-time monitoring
window after a monitoring task is started. Below the Chart tab page in the window, you can set
the display properties such as the line color, line type, and line width.
Prerequisites
l
Procedure
Step 1 In the task information pane at the bottom of the window, click the property boxes of the Line
Color, Line Type, or Line Width column.
Step 2 Select the required properties from the drop-down lists.
NOTE
l The setting of the display properties applies only to the current monitoring task.
l If data is displayed on the List tab page but no chart is displayed on the Chart tab page during the realtime monitoring, set the display properties of the chart.
----End
8.4.3 Saving Monitoring Results

This section describes how to save the monitoring results to local files.
Prerequisites
l
Procedure
Step 1 To automatically save the monitoring results, ensure that the Save File check box is selected
when you create the task. The default save path is C:/Web LMT/MBSC/output/monitor.
----End
8.4.4 Browsing Monitoring Results Offline

This section describes how to browse the monitoring results of the CPU usage and BER
seconds in offline mode.
Prerequisites
The monitoring results are saved to files.
Issue 09 (2014-12-29)

228
BSC6910 UMTS
LMT User Guide
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecording
Review Tool.
Step 2 Open the directory where the monitoring results are saved. The default save path is C:/Web
LMT/MBSC/output/monitor. Select the result file corresponding to the monitoring task.
Step 3 Click Open or double-click the file. The TrafficRecording Review Tool window is displayed,
providing the monitoring results in chart and list.
Step 4 Click the List tab or the Chart tab to view the data in different modes.
Step 5 To view other saved results, choose File > Open. In the Open dialog box, select the target files
to read the details.
----End
8.5 Reference for Performance Monitoring

This section describes the parameters used for performance monitoring.
Monitor Item
Parameter
Description
Transport Resource
RealTime Monitoring
IP Logic Port
Indicates the number of the IP logical port. To

query the number of the IP logical port, run
the LST IPLOGICPORT command.
Physical Port
Physical port query

l To query the number of the FRA Link
physical port , run the LST FRALNK
command.
l To query the number of the IMA Group
physical port , run the LST IMAGRP
command.
l To query the number of the UNI Link
physical port , run the LST UNILNK
command.
Link
Performanc
e
Monitoring
Issue 09 (2014-12-29)
IMA Group
IMA Group
No.
Indicates the number of the IMA group. To

query the IMA group, run the LST
IMAGRP command.
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.

229
BSC6910 UMTS
LMT User Guide
Monitor Item
Parameter
Description
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.
10GE
10GE Port No.
Indicates the number of the 10GE port. To

query the number of the 10GE port, run the
LST ETHPORT command.
SCTP Link
SCTP Link No.
Indicates the number of the SCTP link. To

query the SCTP link, run the LST
SCTPLNK 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.
Logical
Port
Bandwidth
Logical 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
FE/GE
Priority Group
No.
Indicates the priority queue number. (value

range: 0-7).
Optical Port
No.
Indicates the number of the non-channelized

ATM optical port. To query the optical port,
run the LST OPT command.
Logical
Port
NonChannelize
d ATM
Optical
Port
Issue 09 (2014-12-29)
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.

230
BSC6910 UMTS
LMT User Guide
Monitor Item
Parameter
Description
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.
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.
IURP Link
Issue 09 (2014-12-29)
IURP Link No.
To query the IURP link, run the LST

IURPLNK command.

231
BSC6910 UMTS
LMT User Guide
9 Device Panel
Device Panel
About This Chapter

This chapter describes how to manage the BSC6910 equipment by using the device and
emulation panels. You can use these panels to query for information about the boards, board
ports, board links, and board alarms.
9.1 Device Panel Operations
This section describes the operations of the BSC6910 device panel, including how to start and
use it and how to query the status of the boards.
9.2 Emulation Panel Operations
This section describes the operations of the BSC6910 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the status of the boards.
Issue 09 (2014-12-29)

232
BSC6910 UMTS
LMT User Guide
9 Device Panel
9.1 Device Panel Operations

This section describes the operations of the BSC6910 device panel, including how to start and
use it and how to query the status of the boards.
9.1.1 Introduction to the Device Panel

In addition to MML commands, the LMT also provides the graphical device panel to facilitate
device maintenance. eGBTS does not support this function.
The device panel is automatically refreshed, showing board status in real time with the help of
board colors and alarm indicators on the board.
On the device panel, you can right-click a board in position and choose operations from the
shortcut menu. For example, you can query the board status. Figure 9-1 shows the device panel.
Figure 9-1 Device Panel
Alarm indicators represent the alarm status of a board, and board colors indicate the running
status of a board. See the color descriptions shown on the right side of the device panel for
specific meanings of alarm indicators and board colors.
l
. The drop-down
If the tab page under Device Maintenance is not in full view, click
list is displayed. Choose the required menu to display 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 Display Logic Function under the color descriptions of the board, the logic
functions of boards are displayed on the device panel.
Issue 09 (2014-12-29)

233
BSC6910 UMTS
LMT User Guide
9 Device Panel
9.1.2 Starting the Device Panel

This section describes how to start the device panel.
Prerequisites
Procedure
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is
displayed.
Step 2 The BSC 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 displayed Query E1/T1 Port
Status shows the details about the E1/T1 port.
----End
9.1.4 Querying the CPU Usage

Prerequisites
l
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
l
Issue 09 (2014-12-29)

234
BSC6910 UMTS
LMT User Guide
9 Device Panel
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 then choose
CPU Usage Query from the shortcut menu. The CPU Usage window is displayed,
showing the real-time CPU usage.

1.
Run the DSP CPUUSAGE command to query the CPU usage.
----End
9.1.5 Querying BSC Board Clock Status

This section describes how to query the clock status of a BSC board.
Prerequisites
Context
You can query the clock status of a BSC board through menu operations or through MML
commands.
Procedure
l
Issue 09 (2014-12-29)
Through menu operations 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 as required,
and click Query.

1.
Click Device Maintenance on the LMT main page. The Device Maintenance tab
page is displayed.
2.
In 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.
and click Query.

235
BSC6910 UMTS
LMT User Guide
9 Device Panel
Figure 9-2 Querying results of BSC Board Clock Status

1.
Run the DSP CLK command to query the clock status of a BSC board.
----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 through menu operations or through MML commands.
Procedure
l
Issue 09 (2014-12-29)

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 details of the board.

1.
page is displayed.
2.
Query BSC Board Information. The Query BSC Board Information dialog box
is displayed.
236
BSC6910 UMTS
LMT User Guide
9 Device Panel
3.
In the Query BSC Board Information dialog box, set the parameters as required,
and click Query.
Figure 9-3 Querying results of board status

1.
Run the DSP BRD command to query the information about the BSC board.
----End
9.1.7 Resetting the BSC Board

This section describes how to reset the BSC 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 disrupt the ongoing
services. Therefore, perform this operation with caution.
l Resetting the board may affect the ongoing services. Therefore, you are advised to perform
the switchover when the traffic load is light, for example, in the middle of the night.
l
Issue 09 (2014-12-29)
Resetting the Board

237
BSC6910 UMTS
LMT User Guide
9 Device Panel
The board resetting is mandatory during software upgrade and software loading. Resetting
the board will reload the programs and data files. If the active board is reset and the standby
board is working normally, the services processed by the active board will be switched over
to the standby board first, and then the standby board (the original active board) is reset
after the switchover. If an SCUb board is reset while its standby board is not available or
is faulty, the entire subrack is reset.
Procedure
l

1.
2.
Reset BSC Board.
3.
In the displayed Reset BSC Board dialog box, set the parameters as required, and
then click Reset.

1.
page is displayed.
2.
Reset BSC Board. The Reset BSC Board dialog box is displayed.
3.
In the Reset BSC Board dialog box, set the parameters as required, and then click
Reset to reset the board. The operation result is displayed, as shown in Figure 1.
Figure 9-4 Resetting the BSC Board

1.
Run the RST BRD command to reset a BSC board.
----End
Issue 09 (2014-12-29)

238
BSC6910 UMTS
LMT User Guide
9 Device Panel
9.1.8 Switching Over the BSC Boards

This section describes how to switch over the active BSC board and the standby BSC board.
When the active board is faulty, you can switch all the services over to the standby board to
ensure the normal operation of the system. The admin, ADMINISTRATOR-level, OPERATORlevel, USER-level, and authorized CUSTOM-level users can perform this operation.
Prerequisites
l
Before you perform the switchover, ensure that the standby board is present and running
normally without any critical or major alarms.
Context
NOTICE
l If the board switchover fails, the configuration data is not affected but the services will be
disrupted. Therefore, perform this task with caution.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMU board. The OMU board also supports
switchover initiated by the standby board.
You can switch over a board through menu operations or through MML commands.
Procedure
l
Issue 09 (2014-12-29)

1.
2.
Switch BSC Board.
3.
In the displayed Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.

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 as required, and then click
Switch to switch over the boards. The operation result is displayed, as shown in Figure
1.
239
BSC6910 UMTS
LMT User Guide
9 Device Panel
Figure 9-5 Switching over a BSC board

1.
Run the SWP BRD command to switch over the BSC boards.
----End
9.1.9 Querying the BSC Board Alarm

This section describes how to query the BSC 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 then 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 BSC6910 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the status of the boards.
Issue 09 (2014-12-29)

240
BSC6910 UMTS
LMT User Guide
9 Device Panel
9.2.1 Introduction to the Emulation Panel

The LMT provides the emulation panel for each subrack. The emulation subrack has the same
ports as those of the real subrack and helps to ascertain the status of each board.
The emulation panel displays the running status of the ports of each board and provides rightclick menus as shown in Figure 9-6.
Figure 9-6 Emulation panel
The emulation panel has the following features:

l
It displays the running status of the device directly.
You can query the board status and port status through the right-click menus.
9.2.2 Starting the Emulation Panel

This section describes how to start the emulation panel.
Prerequisites
Issue 09 (2014-12-29)

241
BSC6910 UMTS
LMT User Guide
9 Device Panel
Procedure
displayed.
Step 2 Click BSC6910 under Device Navigation Tree. The BSC Device Panel is displayed on the
right pane.
Step 3 To display the emulation panel of a subrack, select the corresponding rack and double-click the
peripheral of the 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).
Issue 09 (2014-12-29)

242
BSC6910 UMTS
LMT User Guide
9 Device 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 displayed Query E1/T1 Port
Status shows the details about the E1/T1 port.
----End
9.2.4 Querying the CPU Usage

Prerequisites
l
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
l

1.
Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation
2.
CPU Usage Query from the shortcut menu. The CPU Usage window is displayed,
showing the real-time CPU usage.

1.
Run the DSP CPUUSAGE command to query the CPU usage.
----End
9.2.5 Querying BSC Board Clock Status

This section describes how to query the clock status of a BSC board.
Prerequisites
Context
You can query the clock status of a BSC board through menu operations or through MML
commands.
Procedure
l

1.
Issue 09 (2014-12-29)
Open the device panel (see 9.1.2 Starting the Device Panel) or open the emulation
243
BSC6910 UMTS
LMT User Guide
9 Device Panel
2.
Query BSC Board Clock Status from the shortcut menu. The Query BSC Board
Clock Status dialog box is displayed.
3.
and click Query.

1.
page is displayed.
2.
Query BSC Board Clock Status. The Query BSC Board Clock Status dialog box
is displayed.
3.
and click Query.
Figure 9-8 Querying results of BSC Board Clock Status

1.
Run the DSP CLK command to query the clock status of a BSC board.
----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 through menu operations or through MML commands.
Issue 09 (2014-12-29)

244
BSC6910 UMTS
LMT User Guide
9 Device Panel
Procedure
l

1.
2.
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing details of the board.

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 as required,
and click Query.
Figure 9-9 Querying results of board status

1.
Run the DSP BRD command to query the information about the BSC board.
----End
9.2.7 Resetting the BSC Board

This section describes how to reset the BSC board. The admin, ADMINISTRATOR-level,
OPERATOR-level, USER-level, and authorized CUSTOM-level users can perform this
operation.
Prerequisites
l
Issue 09 (2014-12-29)

245
BSC6910 UMTS
LMT User Guide
9 Device Panel
Context
NOTICE
l If the standby board is not available or is faulty, resetting the board will disrupt the ongoing
services. Therefore, perform this operation with caution.
l
Resetting the Board

The board resetting is mandatory during software upgrade and software loading. Resetting
the board will reload the programs and data files. If the active board is reset and the standby
board is working normally, the services processed by the active board will be switched over
to the standby board first, and then the standby board (the original active board) is reset
after the switchover. If an SCUb board is reset while its standby board is not available or
is faulty, the entire subrack is reset.
Procedure
l
Issue 09 (2014-12-29)

1.
2.
Reset BSC Board.
3.
In the displayed Reset BSC Board dialog box, set the parameters as required, and
then click Reset.

1.
page is displayed.
2.
Reset BSC Board. The Reset BSC Board dialog box is displayed.
3.
In the Reset BSC Board dialog box, set the parameters as required, and then click
Reset to reset the board. The operation result is displayed, as shown in Figure 1.

246
BSC6910 UMTS
LMT User Guide
9 Device Panel
Figure 9-10 Resetting the BSC Board

1.
Run the RST BRD command to reset a BSC board.
----End
9.2.8 Switching Over the BSC Boards

This section describes how to switch over the active BSC board and the standby BSC board.
When the active board is faulty, you can switch all the services over to the standby board to
ensure the normal operation of the system. The admin, ADMINISTRATOR-level, OPERATORlevel, USER-level, and authorized CUSTOM-level users can perform this operation.
Prerequisites
l
Before you perform the switchover, ensure that the standby board is present and running
normally without any critical or major alarms.
Issue 09 (2014-12-29)

247
BSC6910 UMTS
LMT User Guide
9 Device Panel
Context
NOTICE
l If the board switchover fails, the configuration data is not affected but the services will be
disrupted. Therefore, perform this task with caution.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMU board. The OMU board also supports
switchover initiated by the standby board.
You can switch over a board through menu operations or through MML commands.
Procedure
l
Issue 09 (2014-12-29)

1.
2.
Switch BSC Board.
3.
In the displayed Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.

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 as required, and then click
Switch to switch over the boards. The operation result is displayed, as shown in Figure
1.

248
BSC6910 UMTS
LMT User Guide
9 Device Panel
Figure 9-11 Switching over a BSC board

1.
Run the SWP BRD command to switch over the BSC boards.
----End
9.2.9 Querying the BSC Board Alarm

This section describes how to query the BSC 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 then choose Query
Board Alarm from the shortcut menu. The alarm information is displayed.
----End
9.2.10 Querying the Status of an FE Port

This section describes how to query the status of an FE port.
Prerequisites
l
Issue 09 (2014-12-29)

249
BSC6910 UMTS
LMT User Guide
9 Device Panel
Context
You can query the status of an FE port through menu operations or through MML commands.
Procedure
l

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 port to be queried, and choose
Display Ethernet Port Status from the shortcut menu. The Display Ethernet Port
Status window is displayed, showing the details of the FE port status.

1.
Run the DSP ETHPORT to query the status of the FE port.
----End
9.2.11 Querying the Status of a GE Port

This section describes how to query the status of a GE port.
Prerequisites
l
Context
You can query the status of a GE port through menu operations or through MML commands.
Procedure
l

1.
2.
On the emulation panel of the subrack, right-click the 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 details of the GE port status.

1.
Run the DSP GEPORT command to query the status of the GE port.
----End
9.2.12 Querying the Status of an Optical Port

This section describes how to query the status of an optical port. AOUc/UOIc board supports
this function.
Prerequisites
l
Issue 09 (2014-12-29)

250
BSC6910 UMTS
LMT User Guide
9 Device Panel
Context
You can query the status of an optical port through menu operations or through MML commands.
Procedure
l

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 displayed
Query Optical Port Status and Performance window, specify the parameters as
required, and click Submit to query the detailed information about the optical port.

1.
Run the DSP OPT to query the status of the optical port.
----End
9.2.13 Querying Alarm LED Information

This section describes how to query the details of alarms indicated by an alarm LED.
Prerequisites
l
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 then choose Query Alarm
Indicator Info from the shortcut menu. The Query Alarm Indicator Info window is displayed,
showing the details of alarms indicated by the alarm LED.
----End
Issue 09 (2014-12-29)

251
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
10
BSC Maintenance
About This Chapter

This chapter describes how to maintain the BSC equipment, Backing Up Data and Restoring
Data, and Fault Management Assistant.
10.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 performance configuration data.
10.2 Restoring Data
This section describes how to restore configuration data on the OMU.
This function is used when faults occur and persist at a site and site maintenance personnel
cannot directly use the counters, alarms, and logs for fault analysis. This section describes how
to use the Fault Management Assistant function for rapid fault diagnosis. With this function, the
LMT analyzes counters, alarms, and logs of a site where a fault occurs by following the diagnosis
rules, and then sends an analysis report to guide users in rapid troubleshooting.
10.4 Batch Configuration
This task is performed to deliver batch configuration script files. Such files can be generated by
the CME or manually generated by operators.
10.5 OS Maintenance
The OS debugging function provides commands for querying the operating system (OS)
information and commands for system debugging. The OS information refers to timer, memory,
task, message, reset record, IPC info, MOT info and start record.
Issue 09 (2014-12-29)

252
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
10.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 performance configuration data.
Prerequisites
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
a corresponding data backup file for data recovery.
Context
Procedure
1.
page is displayed.
2.
Under Device Navigation Tree, right-click the BSC node 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 displayed Backup Data dialog box, click Backup to back up system data on
the OMU.
NOTE
l The default directory for saving backup files is OMU active workspace installation directory
\data\backup. If such a directory 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 displayed 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.
l
Issue 09 (2014-12-29)
Through an MML command

253
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
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
10.2 Restoring Data

This section describes how to restore configuration data on the OMU.
Prerequisites
l
Context
NOTICE
l Restoring data overwrites OMU data, so restore data with caution.
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

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.
l
In the displayed Restore Data dialog box, click Restore Data to restore configuration
data on the OMU.
Through an MML command

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 09 (2014-12-29)

254
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance

This function is used when faults occur and persist at a site and site maintenance personnel
cannot directly use the counters, alarms, and logs for fault analysis. This section describes how
to use the Fault Management Assistant function for rapid fault diagnosis. With this function, the
LMT analyzes counters, alarms, and logs of a site where a fault occurs by following the diagnosis
rules, and then sends an analysis report to guide users in rapid troubleshooting.
Context
NOTE
Do not run the COL LOG, EXP LOG, and EXP ALMLOG commands at the same time during the process
of the rapid fault diagnosis because this way may cause the failure of rapid fault diagnosis.
This function occupies resources of the OMU board. Therefore this function cannot be
started or is stopped when a certain condition is met:
This function cannot be started when free space available on the OMU board is less than
500 MB.
This function is stopped when more than 95% of OMU memory is occupied and this
function occupies more than 500 MB OMU memory.
Procedure
Step 1 Click FMA on the LMT main page. The FMA tab page is displayed.
Step 2 Under FMA, double-click Fault Diagnosis. The Fault Diagnosis dialog box is displayed. Select
the logical NEs requiring fault management under BSC Options.
NOTE
Under BSC Options in the Fault Management Assistant dialog box, selection between RNCs is mutually
exclusive. That is, only one logical NE can be selected during a fault management process.
Step 3 Click Next in the lower right corner. The Scenario Options dialog box is displayed. Select the
fault scenarios requiring fault management.
Step 4 Click Start and wait for the diagnosis report.
Table 10-1 UMTS fault analysis scenario options
Scenario Options
KPI
Items
RRC connection setup
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.
Issue 09 (2014-12-29)

255
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Scenario Options
Items
CS service setup
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.
The CS RAB setup success
rate is abnormal.
The number of CS RAB
setup requests decreases
significantly.
CS call drop
The CS service drop rate is

abnormal.
PS service setup
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.
Issue 09 (2014-12-29)

256
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Scenario Options
Items
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.
PS call drop
The PS service drop rate is

abnormal.
Paging
The paging success rate is

abnormal.
PS throughput
The PS throughput decreases

significantly.
CS Erlang
The CS Erlang decreases

significantly.
Transmission
A large number of
unavailable cells
A large number of cells are

unavailable.
Others
Equipment health check
Health check on the interface

boards
Traffic
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
RNC in Pool Load Sharing
Issue 09 (2014-12-29)

The number of RRC

connection setup requests of
the overflow RNC is 0.
257
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Scenario Options
Items
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.
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-2. You can query the load sharing type by running the LST URNCBASIC command
and query the host status by running the DSP UHOSTRNC command.
Issue 09 (2014-12-29)

258
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Table 10-2 RNC in Pool fault analysis scenario options
Issue 09 (2014-12-29)
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
PS
service
setup
PS call
drop
CS
Erlang
PS
throughp
ut
Paging
A large
number
of
unavaila
ble cells
Equipme
nt health
check

259
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
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
RNC in
Pool
Load
Sharing
----End
Result
l
A new browser window is displayed with the fault analysis report presented on a web
page.
Table 10-3 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:
Issue 09 (2014-12-29)

260
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Table 10-4 Contents of the diagnosis report

Item
Description
RNC Basic Information
RNC ID, RNC name, transmission modes over the

Iub, Iur, Iu-CS, and Iu-PS interfaces, and the loadsharing type of RNC in Pool
KPI and counter change

trend chart
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 left Y-coordinate represents the
counter value in the unit of the corresponding
counter, and the right Y-coordinate represents 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.
Fault analysis report
Including KPI statistics, Fault causes and Fault

rectification advice.
Operation logs of last 24

hours
Running the MML command EXP LOG to export the

operation log.
Unsuccessful operation
A dialog box is displayed with the failure cause.
Issue 09 (2014-12-29)

261
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
10.4 Batch Configuration

This task is performed to deliver batch configuration script files. Such files can be generated by
the CME or manually generated by operators.
Prerequisites
l
The LMT communicates properly with the BSC.
Batch configuration must be performed in accordance with the function of the CME script
executor to quickly validate patch configuration script files on the BSC.
Batch configuration includes the Preactivate and Activate functions.
Context
Preactivate is performed 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 faults in advance and prevents activation failures.
Activate includes the check functions of Preactivate. It is also performed to validate
configuration scripts on the NE.
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
Step 1 On the LMT, click Device Maintenance. The Device Maintenance tab page is displayed.
Step 2 Under Device Navigation Tree, right-click the BSC node and choose Batch Configuration
from the short-cut menu. The Batch Configuration dialog box is displayed, as shown in Figure
10-1.
Issue 09 (2014-12-29)

262
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Figure 10-1 Batch Configuration dialog box
Step 3 In the displayed Batch Configuration dialog box, configure the FTP Server related parameters
and select a batch configuration script file.
Step 4 Click Activate or Preactivate and wait until the configuration command takes effect on the
BSC.
----End
Result
l
Successful operation:
The progress of the activation and preactivation related commands are displayed in the
progress bar.
Upload the file. The execution results of activation and preactivation related commands
are displayed in the message area.
Failed operation: The failure cause is displayed in the message area.
10.5 OS Maintenance
The OS debugging function provides commands for querying the operating system (OS)
information and commands for system debugging. The OS information refers to timer, memory,
task, message, reset record, IPC info, MOT info and start record.
Prerequisites
Issue 09 (2014-12-29)

263
BSC6910 UMTS
LMT User Guide
10 BSC Maintenance
Context
NOTICE
Only ADMINISTRATOR-level users are authorized for performing OS Maintenancing because
it involves private information of users.
Procedure
displayed.
Step 2 Under Device Navigation Tree, right-click the BSC node and choose OS Maintenance from
the short-cut menu. The OS Maintenance dialog box is displayed.
Step 3 In the OS Maintenance dialog box, set the parameters as required, and click Submit. The LMT
returns the detailed information.
NOTE
The returned information can be text and binary messages. You can view the text messages directly. For
a binary message, double-click it to read the detailed explanation.
----End
Issue 09 (2014-12-29)

264
BSC6910 UMTS
LMT User Guide
11 FAQ
11
FAQ
About This Chapter

This chapter describes some frequently asked questions (FAQs) and the corresponding solutions.
11.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.
11.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.
11.3 The 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.
11.4 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.
11.5 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.
11.6 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.
11.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding
Issue 09 (2014-12-29)

265
BSC6910 UMTS
LMT User Guide
11 FAQ
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.
11.8 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.
11.9 How to Set the Browser Under Citrix Farm Networking
Under Citrix farm networking, when you use the M2000 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.
11.10 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.
11.11 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.
11.12 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.
11.13 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.
11.14 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.
11.15 The Error "Certificate Invalid" Is Displayed During an HTTPS Login
The LMT certificate and the certificate used to access the LMT through the M2000 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.
11.16 The Error 'Mismatched Address' Is Displayed During an HTTPS Login
Issue 09 (2014-12-29)

266
BSC6910 UMTS
LMT User Guide
11 FAQ
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.
11.17 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.
11.18 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:
11.19 Interfaces for Performing Tracing or Monitoring Tasks Blinking
Interfaces for performing tracing or monitoring tasks blink.
11.20 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.
11.21 The File Manager Functions Improperly
When the file manager functions improperly or cannot be used, perform the following
operations:
11.22 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.
11.23 The 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.
11.24 The Message 'Class doesn't support Automation' Is 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
displayed. The icon says "Class doesn't support Automation". To solve the problem, perform
the following steps:
11.25 Java Installation Fails
Issue 09 (2014-12-29)

267
BSC6910 UMTS
LMT User Guide
11 FAQ
During Java installation, the message "Error 25099, Unzipping core files failed." is displayed.
To solve the problem, perform the following steps:
11.26 The 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.
11.27 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.
11.28 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.
11.29 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.
11.30 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:
11.31 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.
11.32 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.
11.33 "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.
11.34 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.
11.35 How to Handle Error Message Displayed on the LMT
The error message Problems with this Web page might prevent it from being displayed
properly or functioning properly. is displayed in the Internet Explorer during the logging in
of the LMT.
11.36 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
Issue 09 (2014-12-29)

268
BSC6910 UMTS
LMT User Guide
11 FAQ
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.
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:
Issue 09 (2014-12-29)

269
BSC6910 UMTS
LMT User Guide
11 FAQ
11.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
11.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
11.3 The 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.
Therefore, you must disable the protected mode. Otherwise, the LMT web page cannot be
displayed.
Issue 09 (2014-12-29)

270
BSC6910 UMTS
LMT User Guide
11 FAQ
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
BSC6910.
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 M2000 proxy server is used for the login to the LMT, add the IP address of the M2000 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

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.
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.
Issue 09 (2014-12-29)

271
BSC6910 UMTS
LMT User Guide
11 FAQ
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.
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
11.5 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 09 (2014-12-29)

272
BSC6910 UMTS
LMT User Guide
11 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)
Settings dialog box is displayed.
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
11.6 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.
11.7 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
Step 1 On the menu bar of Excel, choose Data > Import External Data > Import Data. Then the
Select Data Source dialog box is displayed. Figure 11-1 shows the dialog box.
Issue 09 (2014-12-29)

273
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-1 Operation interface for importing data in Excel
Step 2 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 11-2 shows the dialog box. Select UTF-8
in File origin.
Figure 11-2 Text import wizard-step 1
Issue 09 (2014-12-29)

274
BSC6910 UMTS
LMT User Guide
11 FAQ
Step 3 Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed. Figure 11-3
shows the dialog box. Select Comma under Delimiters.
Figure 11-3 Text import wizard-step 2
Step 4 Click Finish. Then the Import Data dialog box is displayed. Figure 11-4 shows the dialog box.
Figure 11-4 Interface after data importation is finished
Step 5 Click OK. Then the file is displayed properly.

----End
Issue 09 (2014-12-29)

275
BSC6910 UMTS
LMT User Guide
11 FAQ
11.8 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.
In normal maintenance, the maximum number of LMT clients that can be started on one PC
simultaneously is as follows:
l
One PC with 2 GB memory can start 16 LMT clients simultaneously.
One PC with 1 GB memory can start 8 LMT clients simultaneously.
One PC with 512 MB memory can start 4 LMT clients simultaneously.
11.9 How to Set the Browser Under Citrix Farm Networking

Under Citrix farm networking, when you use the M2000 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.
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"
Issue 09 (2014-12-29)

276
BSC6910 UMTS
LMT User Guide
11 FAQ
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 11-5.
Figure 11-5 Active Directory Users and Computers
b.
Issue 09 (2014-12-29)
In the right-side pane, right-click hong01. Choose Properties from the shortcut
menu. The hong01 Properties dialog box shown in Figure 11-6 is displayed.

277
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-6 Displayed hong01 Properties dialog box
c.
Issue 09 (2014-12-29)
In the hong01 Properties dialog box, click the Profile tab. Type IE-unset.bat
in Logon script, click Apply, and then click OK. Figure 11-7 shows the
window.

278
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-7 Applying the script in the hong01 Properties dialog box
Manual Setting
1.
2.
Issue 09 (2014-12-29)
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 M2000 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 11-8 shows
the window.

279
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-8 HTTP 1.1 settings
----End
11.10 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 09 (2014-12-29)
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.

280
BSC6910 UMTS
LMT User Guide
11 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.
Issue 09 (2014-12-29)

281
BSC6910 UMTS
LMT User Guide
11 FAQ
2.
Load the startup script.

Script setting for a single Windows server
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 11-9, choose
User Configuration > Windows Settings > Scripts(Logon/Logoff).
Figure 11-9 Script
d.
Issue 09 (2014-12-29)
Double-click Logon. A dialog box shown in Figure 11-10 is displayed. Click

Show Files and copy the prepared script to the displayed directory. Then close
the dialog box displaying the directory.

282
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-10 Logon
e.
Click Add in the dialog box shown in Figure 11-11. A dialog box shown in
Figure 11-11 is displayed.
Figure 11-11 Adding a script
f.
Issue 09 (2014-12-29)
In the dialog box shown in Figure 11-11, click Browse to select the prepared
script and click OK. Then close the dialog box.

283
BSC6910 UMTS
LMT User Guide
11 FAQ
g.
In the dialog box shown in Figure 11-10, 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 be 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 11-12, choose User Configuration > Windows
Settings > Scripts(Logon/Logoff).
Figure 11-12 Script
c.
Issue 09 (2014-12-29)
Double-click Logon. A dialog box shown in Figure 11-13 is displayed. Click

Show Files and copy the prepared script to the displayed directory. Then close
the dialog box displaying the directory.

284
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-13 Logon
d.
Click Add in the dialog box shown in Figure 11-13. A dialog box shown in
Figure 11-14 is displayed.
Figure 11-14 Adding a script
e.
Issue 09 (2014-12-29)
In the dialog box shown in Figure 11-14, click Browse to select the prepared
script and click OK. Then close the dialog box.

285
BSC6910 UMTS
LMT User Guide
11 FAQ
f.
l
In the dialog box shown in Figure 11-13, 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 11-15.
Figure 11-15 Windows components wizard
2.
Issue 09 (2014-12-29)
Click Details... in the dialog box shown in Figure 11-15. In the displayed dialog box
shown in Figure 11-16, deselect For administrator groups and For all other user
groups.

286
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-16 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
11.11 Unable to Download or Install the Java or Flash Plugin 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 09 (2014-12-29)

287
BSC6910 UMTS
LMT User Guide
11 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
11.12 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.
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 11-17 are provided. Changing the default option as described below solves the previous
problem.
Issue 09 (2014-12-29)

288
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-17 Java control panel
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
11.13 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
Issue 09 (2014-12-29)

289
BSC6910 UMTS
LMT User Guide
11 FAQ
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
11.14 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.
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.
Issue 09 (2014-12-29)

290
BSC6910 UMTS
LMT User Guide
11 FAQ
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
11.15 The Error "Certificate Invalid" Is Displayed During an

HTTPS Login
The LMT certificate and the certificate used to access the LMT through the M2000 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, a dialog box shown in
Figure 11-18 or Figure 11-19 is displayed.
Figure 11-18 Dialog box showing "There is a problem with this website's security
certificate" (IE7 or later versions)
Issue 09 (2014-12-29)

291
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-19 Dialog box showing "Security Alert"(IE6)
2.
Click Continue to this webpage(not recommended) in Figure 11-18 or Yes in

Figure 11-19 to enter the LMT login page. In the Address bar of the browser, an
Certificate Error message is shown.
3.
After clicking Certificate Error, An Certificate Invalid dialog box is shown.
Using a Firefox browser

1.
Issue 09 (2014-12-29)
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, a dialog box shown in
Figure 11-20 is displayed. (The following figure uses Firefox3.0 as an example. The
dialog box varies with browser versions but has the same information.)

292
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-20 Dialog box showing "This Connection is Untrusted"
Connection Through the M2000

1.
After connecting through the M2000 with both IP addresses, an 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 11-21, perform the following steps:
Issue 09 (2014-12-29)

293
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-21 MBSC Certificate
1.
Download the certificate file rootca.pem by the 2.4.2 FTP Client and save this file to a
local path. (The certificate file is saved in the following directory: /bam/version_a/ftp/
cert/default_cert. In this path, version_a is the active workspace of the OMU. If the active
workspace of the OMU is version_b, change the directory to /bam/version_b/ftp/cert/
default_cert.)
2.
Double-click rootca.pem and the content of this file is displayed, as shown in Figure
11-22. Create a .txt file, cut the content following -----END CERTIFICATE----- in the
rootca.pem file, and then paste it into this new .txt file. Save this new .txt file and rename
it as rootca2.pem. The rootca2.pem is the new certificate file.
Issue 09 (2014-12-29)

294
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-22 Content in the rootca.pem file
3.
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.
4.
In the Certificates > Personal tab, and click Import on this tab page, the Certificate
Import Wizard dialog box is displayed.
5.
In the displayed Certificate Import Wizard dialog box, click Next, to import the certificate
file rootca.pem. Then click Next, choose Place all certificates in the following store, and
then click Browse. In the displayed dialog box, choose Trusted Root Certification
Authorities and click Next to start the certificate file import.
6.
Import the certificate file rootca2.pem.
7.
Restart the browser so that the reconfiguration can take effect. If the error Mismatched
Address is displayed when you log in to the LMT after the browser is restarted, refer to
Issue 09 (2014-12-29)

295
BSC6910 UMTS
LMT User Guide
11 FAQ
"FAQ" in 11.16 The Error 'Mismatched Address' Is Displayed During an HTTPS

Login for troubleshooting.
8.
Restart the browser so that the reconfiguration can take effect.

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 11-23,
Figure 11-23 Server Certificate
1.
Issue 09 (2014-12-29)
Click Install Certificate and Next. A dialog box shown in Figure 11-24 is displayed.

296
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-24 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
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 09 (2014-12-29)
Click Add Exception shown in Figure 11-20. The Add Security Exception dialog box is
displayed, as shown in Figure 11-25.
297
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-25 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 M2000

The certification path of the M2000 is shown as Figure 11-26.
Issue 09 (2014-12-29)

298
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-26 Certification Path of the M2000
1.
Choose General > Install Certificate in the Certificate dialog box. And Certificate
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.
6.
Choose Yes in the Security Warning dialog box. The import was successful message is
displayed. Then Click OK.
Issue 09 (2014-12-29)

299
BSC6910 UMTS
LMT User Guide
11 FAQ
7.
----End
11.16 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. A dialog box shown in the Figure
11-27 or Figure 11-28is displayed.
Figure 11-27 Dialog box showing "There is a problem with this website's security
certificate"(IE7 or later versions)
Issue 09 (2014-12-29)

300
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-28 Dialog box showing "Security Alert"(IE6)
2.
Click Continue to this webpage(not recommended) in Figure 11-27 or Yes in Figure

11-28 to enter the LMT login page. In the Address bar of the browser, an Certificate
Error message is shown.
3.
Click Certificate Error. An Mismatched Address error dialog box is shown.
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 11-29.
Issue 09 (2014-12-29)

301
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-29 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
11.17 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
An error message is displayed, as shown in Figure 11-30.
Issue 09 (2014-12-29)

302
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-30 Application Error
After clicking Details, detailed error information is displayed. You need to correct the error
based on the error type as follows:
l
If the "java.lang.ClassNotFoundException" error is displayed, perform steps 1 and 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:
Issue 09 (2014-12-29)

303
BSC6910 UMTS
LMT User Guide
11 FAQ
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 11-31 shows the window.
Issue 09 (2014-12-29)

304
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-31 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.
In the displayed Java Control Panel dialog box, click Setting. The Temporary Files
Settings dialog box is displayed. Check the amount of disk space set for storing temporary
files, as shown in Figure 11-32.
Issue 09 (2014-12-29)

305
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-32 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 11-33 shows the
directory. This amount is greater than the preset one.
Figure 11-33 Directory where temporary Java files are saved
Issue 09 (2014-12-29)

306
BSC6910 UMTS
LMT User Guide
11 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.
----End
11.18 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
Control Panel dialog box is displayed.
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 11-34 shows the dialog box.
Issue 09 (2014-12-29)

307
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-34 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 09 (2014-12-29)
Control Panel dialog box is displayed, as shown in Figure 11-35.

308
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-35 Java Control Panel dialog box
2.
In the Java Control Panel dialog box, click Settings. The Temporary Files Settings
Figure 11-36 Temporary Files Settings dialog box
Issue 09 (2014-12-29)

309
BSC6910 UMTS
LMT User Guide
11 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
11.19 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
11.20 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.
Issue 09 (2014-12-29)

310
BSC6910 UMTS
LMT User Guide
11 FAQ
Step 2 In the "System Properties" window, click System Recovery, select Disable System Recovery
on All Drivers, and click Submit, as shown in Figure 11-37.
Figure 11-37 System properties dialog box
----End
11.21 The File Manager Functions Improperly

When the file manager functions improperly or cannot be used, perform the following
operations:
Procedure
l
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:
1.
Issue 09 (2014-12-29)
Open the Internet Options dialog box, click the Advanced tab, and clear Do not save
encrypted pages to disk. Figure 11-38 shows the dialog box.

311
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-38 Internet Options dialog box
Issue 09 (2014-12-29)
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 11-39.

312
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-39 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.
----End
11.22 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
Issue 09 (2014-12-29)

313
BSC6910 UMTS
LMT User Guide
11 FAQ
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 11-40.
Figure 11-40 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
11.23 The 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 11-41.
Issue 09 (2014-12-29)

314
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-41 Alarm/Event Function
Procedure
l
Method 1: Check that the flash player is of a version supported by the LMT, Flash Player
10.1.82 or later. Flash Player 10.1.82 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 2: 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
11.24 The Message 'Class doesn't support Automation' Is

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
displayed. The icon says "Class doesn't support Automation". To solve the problem, perform
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
Issue 09 (2014-12-29)

315
BSC6910 UMTS
LMT User Guide
11 FAQ
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
11.25 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
11.26 The 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.
Issue 09 (2014-12-29)

316
BSC6910 UMTS
LMT User Guide
11 FAQ
This process is a system process and therefore cannot be closed directly. To close it, perform
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
11.27 Changing Settings for the Next-Generation Java Plugin 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.
Context
Changing Settings for Next-Generation Java Plug-in Fails, the error message is shown in
Figure 11-42.
Issue 09 (2014-12-29)

317
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-42 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 09 (2014-12-29)

318
BSC6910 UMTS
LMT User Guide
11 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 09 (2014-12-29)

319
BSC6910 UMTS
LMT User Guide
11 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 09 (2014-12-29)

320
BSC6910 UMTS
LMT User Guide
11 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
11.28 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,
Issue 09 (2014-12-29)

321
BSC6910 UMTS
LMT User Guide
11 FAQ
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
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
11.29 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
11.30 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,
Issue 09 (2014-12-29)

322
BSC6910 UMTS
LMT User Guide
11 FAQ
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
11.31 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 11-43.
Issue 09 (2014-12-29)

323
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-43 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
11.32 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
Issue 09 (2014-12-29)

324
BSC6910 UMTS
LMT User Guide
11 FAQ
11.33 "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.
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 11-44 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.
Issue 09 (2014-12-29)

325
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-45 Automatic configuration enabled
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
11.34 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
Issue 09 (2014-12-29)
When MML commands are executed, the system displays a Please check the MML macro
configure file! message, as shown in Figure 11-46.

326
BSC6910 UMTS
LMT User Guide
11 FAQ
Figure 11-46 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.
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
11.35 How to Handle Error Message Displayed on the LMT

The error message Problems with this Web page might prevent it from being displayed
properly or functioning properly. is displayed in the Internet Explorer during the logging in
of the LMT.
Context
If the Internet Explorer has insufficient buffer or is upgraded, the Internet Explorer cannot obtain
new files from a base station after the base station is upgraded. The Internet Explorer obtains
files about the base station in the original version from the buffer, which is inconsistent with the
information about the base station in the current version.
Procedure
l
Issue 09 (2014-12-29)
Internet Explorer Browser

327
BSC6910 UMTS
LMT User Guide
11 FAQ
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 in the Browsing history area. The Delete
Browsing History dialog box is displayed.
3.
Clear the Preserve Favorites website data check box, select the Cookie and
Temporary Internet files check boxes, and click Delete.
4.
Close the Delete Browsing History dialog box.
5.
On the General tab page, click Settings in the Browsing history area. The
Temporary Internet Files and History Settings dialog box is displayed.
6.
Click View objects and delete all displayed files.
7.
Close the displayed window and the Internet Options dialog box.
Firefox Browser
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 Data check boxes, and click Clear Private Data Now.
----End
11.36 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
Issue 09 (2014-12-29)

328
BSC6910 UMTS
LMT User Guide
11 FAQ

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
l
Internet Explorer Browser

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 in the Browsing history area. The Delete
Browsing History dialog box is displayed.
3.
Clear the Preserve Favorites website data check box, select the Cookie and
Temporary Internet files check boxes, and click Delete.
4.
Close the Delete Browsing History dialog box.
5.
On the General tab page, click Settings in the Browsing history area. The
Temporary Internet Files and History Settings dialog box is displayed.
6.
Click View objects and delete all displayed files.
7.
Close the displayed window and the Internet Options dialog box.
Firefox Browser
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 Data check boxes, and click Clear Private Data Now.
----End
Issue 09 (2014-12-29)

329

Bsc6910 Umts LMT User Guide (v100r015c00 - 09) (PDF) - en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bsc6910 Umts LMT User Guide (v100r015c00 - 09) (PDF) - en

Загружено:

Авторское право:

Доступные форматы

BSC6910 UMTS

LMT User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. 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

3 Management of Operation Rights

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

The keywords of a command line are in boldface.

Command arguments are in italics.

About This Document

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 Management of Operation Rights............................................................................................36

Huawei Proprietary and Confidential

3.3.3 Changing the Password of the Active User Account................................................................................................43

4 Running MML Commands........................................................................................................46

Huawei Proprietary and Confidential

5.5.1 Browsing Alarm/Event..............................................................................................................................................70

Huawei Proprietary and Confidential

7.3.6 Tracing MNCDT Messages.....................................................................................................................................147

Huawei Proprietary and Confidential

9.1.5 Querying BSC Board Clock Status.........................................................................................................................235

10 BSC Maintenance.................................................................................................................... 252

Huawei Proprietary and Confidential

11.14 Configuring the HTTPS Login Mode.....................................................................................................................290

Huawei Proprietary and Confidential

1 Changes in the BSC6910 UMTS LMT User Guide

Changes in the BSC6910 UMTS LMT User

Monitoring FE/GE Traffic

Added the description of GOUe board.

Huawei Proprietary and Confidential

1 Changes in the BSC6910 UMTS LMT User Guide

Deleted the description about the Windows XP operating

11.37 Settings on the LMT Failing to Take Effective

5.5.6 Setting Display Attributes

Added the description of the display attributes for alarms

Huawei Proprietary and Confidential

1 Changes in the BSC6910 UMTS LMT User Guide