Bsc6910 Umts Lmt User Guide(v100r021c10_02)(PDF)-En

BSC6910 UMTS
V100R021C10
LMT User Guide
Issue 02
Date 2019-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: https://www.huawei.com
Email: support@huawei.com
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. i

BSC6910 UMTS
LMT User Guide Preface
Preface
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 the BSC6910.
Product Versions
The following table lists the product version and the solution version related to
this document.
Product Name Product Version Solution Version
BSC6910 V100R021C10 RAN21.1
Intended Audience
This document is intended for:
● Network engineers
● System engineers
● Field engineers
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. ii

BSC6910 UMTS
LMT User Guide Contents
Contents
Preface........................................................................................................................................... ii
1 Change History.........................................................................................................................1
2 Introduction to LMT................................................................................................................5
2.1 Configuration Requirements of the LMT PC.................................................................................................................. 6
2.2 Logging In to and Logging Out of the LMT...................................................................................................................9
2.3 Components of the LMT Main Page.............................................................................................................................. 14
2.4 Obtaining a Documentation Package............................................................................................................................18
2.5 File Manager...........................................................................................................................................................................19
2.6 User-defined Command Group........................................................................................................................................ 23
2.7 LMT Software......................................................................................................................................................................... 25
2.7.1 Installing LMT Offline Tools...........................................................................................................................................25
2.7.2 LMT Offline MML.............................................................................................................................................................. 27
2.7.2.1 Introduction to the LMT Offline MML Server...................................................................................................... 27
2.7.2.2 Logging In to and Out of the LMT Offline MML Tool...................................................................................... 28
2.7.2.3 Introduction to the LMT Offline MML Window.................................................................................................. 29
2.7.2.4 Preparing Offline MML Scripts.................................................................................................................................. 31
2.7.3 Convert Management System.......................................................................................................................................31
2.7.4 Performance Browser Tool............................................................................................................................................. 33
2.7.5 TrafficRecording Review Tool........................................................................................................................................ 34
3 Operation Rights Management......................................................................................... 36

3.1 Concepts Related to Operation Rights Management.............................................................................................. 36
3.1.1 Principles of Operation Rights Management...........................................................................................................36
3.1.2 User Passwords...................................................................................................................................................................37
3.1.3 Command Groups............................................................................................................................................................. 37
3.1.4 Operation Rights................................................................................................................................................................ 39
3.1.5 Operation Time Limits..................................................................................................................................................... 40
3.1.6 Account Status....................................................................................................................................................................41
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
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. iii

BSC6910 UMTS
3.3.1 Defining Login Password Policies.................................................................................................................................43

3.3.2 Querying Login Password Policies............................................................................................................................... 43
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 Renaming Command Groups........................................................................................................................................ 44
3.4.3 Changing Commands in a Command Group...........................................................................................................45
3.5 Management of FTP Rights...............................................................................................................................................45
3.5.1 Managing Default FTP Rights....................................................................................................................................... 45
3.5.2 Managing FTP Access Control Rules........................................................................................................................... 46
4 Running MML Commands................................................................................................... 49

4.1 Concepts Related to MML Commands.......................................................................................................................... 50
4.1.1 Introduction to MML Commands................................................................................................................................ 50
4.1.2 Components of the MML Command Window........................................................................................................ 51
4.1.3 Data Configuration Rights..............................................................................................................................................53
4.1.4 Data Configuration Rollback......................................................................................................................................... 53
4.2 Running a Single MML Command.................................................................................................................................. 54
4.3 Batch Processing of MML Commands........................................................................................................................... 55
4.3.1 Immediate Batch Processing of MML Commands................................................................................................. 56
4.3.2 Scheduled Batch Processing of MML Commands.................................................................................................. 56
4.3.3 Syntax Check....................................................................................................................................................................... 57
4.4 Setting MML Parameters................................................................................................................................................... 59
4.5 Querying Data Configuration Modes.............................................................................................................................59
4.6 Querying Data Configuration Rights............................................................................................................................. 60
4.7 Obtaining Data Configuration Rights............................................................................................................................ 61
4.8 Undoing/Redoing a Single Data Configuration Action............................................................................................62
4.9 Undoing/Redoing Multiple Data Configuration Actions......................................................................................... 63
5 Alarm/Event Management..................................................................................................65
5.1 Concepts Related to Alarm Management.................................................................................................................... 65
5.1.1 Alarm Type........................................................................................................................................................................... 66
5.1.2 Alarm Severity.................................................................................................................................................................... 66
5.1.3 Alarm-Event Type.............................................................................................................................................................. 67
5.1.4 Alarm Flag........................................................................................................................................................................... 68
5.1.5 Alarm Box............................................................................................................................................................................. 69
5.2 Managing Alarm Logs......................................................................................................................................................... 70
5.2.1 Setting Storage Limitations of Alarm Logs.............................................................................................................. 70
5.2.2 Querying Storage Limitations of Alarm Logs.......................................................................................................... 71
5.3 Managing Alarm Masking Conditions........................................................................................................................... 71
5.3.1 Creating an Alarm Masking Condition...................................................................................................................... 71
5.3.2 Deleting an Alarm Masking Condition...................................................................................................................... 72
5.3.3 Querying an Alarm Masking Condition..................................................................................................................... 72
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. iv

BSC6910 UMTS
5.4 Managing the Alarm Masking Switch of Derived Alarms...................................................................................... 72

5.4.1 Enabling/Disabling the Alarm Masking Switch of Derived Alarms..................................................................72
5.4.2 Querying the Alarm Masking Switch of Derived Alarms.....................................................................................73
5.5 Monitoring Alarms............................................................................................................................................................... 73
5.5.1 Browsing Alarms/Events..................................................................................................................................................73
5.5.2 Querying Alarm/Event Logs........................................................................................................................................... 74
5.5.3 Querying Suggestions on Alarm/Event Handling.................................................................................................. 75
5.5.4 Querying Alarm/Event Configuration.........................................................................................................................75
5.5.5 Filtering Alarms/Events................................................................................................................................................... 76
5.5.6 Setting Display Attributes for Alarms/Events.......................................................................................................... 77
5.5.7 Manually Clearing an Alarm/Event............................................................................................................................. 79
5.5.8 Deleting Alarms/Events................................................................................................................................................... 80
5.5.9 Refreshing the Alarm/Event Window......................................................................................................................... 81
5.6 Managing the Alarm Box................................................................................................................................................... 81
5.6.1 Querying Alarm Box Information................................................................................................................................ 81
5.6.2 Querying the Number of Alarms of a Specific Severity....................................................................................... 81
5.6.3 Performing Operations on the Alarm Box................................................................................................................ 82
5.6.4 Querying the Alarm Suppression Level of the Alarm Box...................................................................................82
6 Log Management.................................................................................................................. 84
6.1 Logs........................................................................................................................................................................................... 84
6.2 Setting Log Storage Limitations...................................................................................................................................... 85
6.3 Querying Operation/Security Logs................................................................................................................................. 85
6.4 Obtaining Operation/Security Logs................................................................................................................................ 86
6.5 Obtaining Running Logs..................................................................................................................................................... 87
6.6 Collecting Logs....................................................................................................................................................................... 88
7 Trace Management............................................................................................................... 93
7.1 Concepts................................................................................................................................................................................... 93
7.1.1 Tracing Principles............................................................................................................................................................... 93
7.1.2 Management of Tracing Operation Rights............................................................................................................... 94
7.1.3 Tracing Mode...................................................................................................................................................................... 95
7.1.4 Tracing Specifications....................................................................................................................................................... 95
7.2 Basic Tracing Operations.................................................................................................................................................... 96
7.2.1 Browsing Traced Messages Online.............................................................................................................................. 96
7.2.2 Viewing the Interpretation of Traced Messages..................................................................................................... 97
7.2.3 Saving Traced Messages.................................................................................................................................................. 98
7.2.4 Browsing Traced Messages Offline..............................................................................................................................99
7.2.5 Managing Tracing Tasks............................................................................................................................................... 101
7.2.6 Managing the Trace File............................................................................................................................................... 101
7.3 Device Commissioning...................................................................................................................................................... 102
7.3.1 Tracing OS Messages..................................................................................................................................................... 102
7.3.2 Emergency Diagnosis..................................................................................................................................................... 103
7.3.3 Capturing Packets........................................................................................................................................................... 104
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. v

BSC6910 UMTS
7.3.4 AC Tracing.......................................................................................................................................................................... 111

7.3.5 DHCP Tracing.................................................................................................................................................................... 112
7.4 UMTS Services..................................................................................................................................................................... 114
7.4.1 Tracing Messages on the Iu Interface...................................................................................................................... 114
7.4.2 Tracing Messages on the Iupc Interface..................................................................................................................117
7.4.3 Tracing Messages on the Iur Interface.....................................................................................................................119
7.4.4 Tracing Messages on the Iub Interface....................................................................................................................121
7.4.5 Tracing Messages on the Uu Interface.................................................................................................................... 123
7.4.6 Tracing MNCDT Messages........................................................................................................................................... 125
7.4.7 Message Settings............................................................................................................................................................ 127
7.4.8 Tracing UE Messages..................................................................................................................................................... 128
7.4.9 Tracing Cell Messages....................................................................................................................................................138
7.4.10 Tracing IOS Messages................................................................................................................................................. 140
7.4.11 Tracing Iur-p Messages............................................................................................................................................... 150
7.4.12 Tracing Messages on the Sr Interface....................................................................................................................152
8 Performance Monitoring................................................................................................... 154

8.1 Concepts................................................................................................................................................................................ 154
8.1.1 Monitoring Principles..................................................................................................................................................... 154
8.1.2 Operation Rights Control............................................................................................................................................. 156
8.2 General Operations............................................................................................................................................................ 156
8.2.1 Browsing the Monitoring Results Online................................................................................................................ 156
8.2.2 Setting Chart Display Mode........................................................................................................................................ 157
8.2.3 Saving Monitoring Data............................................................................................................................................... 158
8.2.4 Offline Browsing Monitoring Data........................................................................................................................... 158
8.3 Common Monitoring......................................................................................................................................................... 158
8.3.1 Monitoring Board CPU Usage.....................................................................................................................................159
8.3.2 Monitoring CPU Usage on Subsystems................................................................................................................... 159
8.3.3 Monitoring Transmission Resources......................................................................................................................... 160
8.3.4 Monitoring BERS............................................................................................................................................................. 165
8.3.5 Monitoring BER................................................................................................................................................................ 165
8.3.6 Monitoring Link Performance..................................................................................................................................... 166
8.3.6.1 Reference for Performance Monitoring............................................................................................................... 166
8.3.6.2 Monitoring IMA Group Traffic................................................................................................................................ 168
8.3.6.3 Monitoring UNI Link Traffic..................................................................................................................................... 168
8.3.6.4 Monitoring Fractional ATM Link Traffic.............................................................................................................. 169
8.3.6.5 Monitoring SAAL Link Traffic.................................................................................................................................. 170
8.3.6.6 Monitoring IPOA PVC Link Traffic......................................................................................................................... 170
8.3.6.7 Monitoring AAL2 Path Traffic................................................................................................................................. 171
8.3.6.8 Monitoring FE/GE Port Traffic.................................................................................................................................171
8.3.6.9 Monitoring SCTP Link Traffic...................................................................................................................................172
8.3.6.10 Monitoring Logical Port Traffic............................................................................................................................ 173
8.3.6.11 Monitoring OAM Channel Traffic........................................................................................................................ 173
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. vi

BSC6910 UMTS
8.3.6.12 Monitoring Traffic on Non-Channelized ATM Optical Port....................................................................... 174

8.3.6.13 Monitoring IP Pool PM Link Traffic.................................................................................................................... 174
8.3.6.14 Monitoring Trunk Group Traffic........................................................................................................................... 175
8.3.6.15 Monitoring Local IP Traffic in IP Pool................................................................................................................ 175
8.3.6.16 Monitoring Iur-p Link Traffic................................................................................................................................. 176
8.3.6.17 Monitoring 10GE Port Traffic................................................................................................................................ 176
8.4 UMTS Monitoring............................................................................................................................................................... 177
8.4.1 Monitoring Connection Performance....................................................................................................................... 177
8.4.1.1 Monitoring P-CPICH Ec/No and RSCP.................................................................................................................. 177
8.4.1.2 Monitoring SIR Values of the Uplink RLSs.......................................................................................................... 179
8.4.1.3 Monitoring the Outer Loop Power Control........................................................................................................ 180
8.4.1.4 Monitoring the SIR Error Values of UL RLSs...................................................................................................... 181
8.4.1.5 Monitoring DL Code TX Power............................................................................................................................... 182
8.4.1.6 Monitoring UE TX Power.......................................................................................................................................... 183
8.4.1.7 Monitoring UL Traffic Volume................................................................................................................................ 184
8.4.1.8 Monitoring DL Traffic Volume................................................................................................................................ 184
8.4.1.9 Monitoring UL Throughput and Bandwidth.......................................................................................................185
8.4.1.10 Monitoring DL Throughput and Bandwidth.................................................................................................... 186
8.4.1.11 Monitoring Handover Delay.................................................................................................................................. 187
8.4.1.12 Monitoring DL Transport Channel BLER........................................................................................................... 188
8.4.1.13 Monitoring AMR Mode........................................................................................................................................... 188
8.4.1.14 Monitoring AMR EVQI............................................................................................................................................. 189
8.4.1.15 Monitoring AMR PSPELQ........................................................................................................................................190
8.4.2 Monitoring Cell Performance......................................................................................................................................191
8.4.2.1 Monitoring Cell P-CPICH TX Power....................................................................................................................... 191
8.4.2.2 Monitoring Cell UL RTWP......................................................................................................................................... 192
8.4.2.3 Monitoring DL Carrier TX Power in a Cell...........................................................................................................193
8.4.2.4 Monitoring Number of UEs in a Cell.................................................................................................................... 193
8.4.2.5 Monitoring Node Synchronization.........................................................................................................................194
8.4.2.6 Monitoring UL CAC..................................................................................................................................................... 194
8.4.2.7 Monitoring DL CAC..................................................................................................................................................... 195
8.4.2.8 Monitoring the Number of UL Equivalent UEs................................................................................................. 196
8.4.2.9 Monitoring the Number of DL Equivalent UEs................................................................................................. 197
8.4.2.10 Monitoring the Cell Code Tree..............................................................................................................................197
8.4.2.11 Monitoring the Minimum Power Required for the HS-DSCH................................................................... 198
8.4.2.12 Monitoring the HS-DSCH Bit Rate...................................................................................................................... 198
8.4.2.13 Monitoring the E-DCH Bit Rate............................................................................................................................199
8.4.2.14 Monitoring Cell UL Throughput........................................................................................................................... 200
8.4.2.15 Monitoring Cell DL Throughput........................................................................................................................... 200
8.4.2.16 Monitoring the Number of ACK Messages per Second in a Cell..............................................................201
8.4.2.17 Monitoring Cell Credit............................................................................................................................................. 201
8.4.2.18 Monitoring the FDPCH SYMBOL..........................................................................................................................203
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. vii

BSC6910 UMTS
8.4.3 Monitoring System Resources.................................................................................................................................... 204

8.4.4 Monitoring Iur-p Delay................................................................................................................................................. 204
9 Device Panel......................................................................................................................... 206

9.1 Device Panel Operations.................................................................................................................................................. 206
9.1.1 Introduction to the Device Panel............................................................................................................................... 206
9.1.2 Starting the Device Panel............................................................................................................................................. 207
9.1.3 Querying the Status of an E1/T1 Port..................................................................................................................... 207
9.1.4 Querying the CPU Usage..............................................................................................................................................208
9.1.5 Querying BSC Board Clock Status............................................................................................................................. 208
9.1.6 Querying the BSC Board Information...................................................................................................................... 209
9.1.7 Resetting a BSC Board................................................................................................................................................... 210
9.1.8 Switching Over BSC Boards......................................................................................................................................... 212
9.1.9 Querying the BSC Board Alarm..................................................................................................................................213
9.2 Emulation Panel Operations........................................................................................................................................... 214
9.2.1 Introduction to the Emulation Panel........................................................................................................................214
9.2.2 Starting the Emulation Panel......................................................................................................................................215
9.2.3 Querying the Status of an E1/T1 Port..................................................................................................................... 216
9.2.4 Querying the CPU Usage..............................................................................................................................................216
9.2.5 Querying BSC Board Clock Status............................................................................................................................. 217
9.2.6 Querying the BSC Board Information...................................................................................................................... 218
9.2.7 Resetting a BSC Board................................................................................................................................................... 219
9.2.8 Switching Over BSC Boards......................................................................................................................................... 220
9.2.9 Querying the BSC Board Alarm..................................................................................................................................222
9.2.10 Querying the FE/GE/10GE Port Status.................................................................................................................. 222
9.2.11 Querying the Optical Port Status............................................................................................................................223
9.2.12 Querying Alarm LED Information........................................................................................................................... 223
10 FMA...................................................................................................................................... 225
10.1 Fault Overview.................................................................................................................................................................. 228
10.2 Fast Fault Diagnosis........................................................................................................................................................ 231
10.3 Hierarchical Delimitation...............................................................................................................................................241
10.4 Recovery Confirmation................................................................................................................................................... 244
10.5 Information Collection................................................................................................................................................... 245
10.6 Business Validation.......................................................................................................................................................... 246
10.7 Business Query.................................................................................................................................................................. 252
10.8 Independent Rules Update........................................................................................................................................... 253
10.9 List of Alarms for UMTS Fault Diagnosis.................................................................................................................254
11 BSC Maintenance.............................................................................................................. 262

11.1 Backing Up Data.............................................................................................................................................................. 262
11.2 Restoring Data.................................................................................................................................................................. 263
11.3 Batch Configuration........................................................................................................................................................ 264
12 FAQ....................................................................................................................................... 266
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. viii

BSC6910 UMTS
12.1 Browser-related FAQs..................................................................................................................................................... 266

12.1.1 Slow Responses in the Firefox Browser................................................................................................................. 266
12.1.2 LMT Colors Cannot Be Displayed............................................................................................................................267
12.1.3 Verification Code Cannot Be Displayed on the LMT Login Page................................................................. 267
12.1.4 No Response When Clicking the Menu Bar on the LMT................................................................................ 268
12.1.5 How to Set the Browser Under Citrix Farm Networking................................................................................ 269
12.1.6 Unable to Log In To LMT Because IE Default Security Level Is Too High.................................................273
12.1.7 Unable to Download or Install the Java Plug-in and Two File Manager Windows Displayed
Windows IE8 or Any Later Version Is Used.......................................................................................................................280
12.1.8 The Error "Certificate Invalid" Is Displayed During an HTTPS Login..........................................................281
12.1.9 The Error 'Mismatched Address' Is Displayed During an HTTPS Login..................................................... 290
12.1.10 File Manager Functions are Improperly............................................................................................................. 292
12.1.11 Message 'Class doesn't support Automation' Displayed in an IE Browser.............................................294
12.1.12 Error Message"This user session already exists" Upon Login to LMT..................................................... 295
12.1.13 The "Are You Sure You Want to Quit the Page" Dialog Box Is Displayed..............................................296
12.1.14 Unclear Grids in the Tables in the MML Online Help................................................................................... 296
12.1.15 The "App Center" Web Page Is Automatically Displayed When Firefox Is Used to Browse the LMT
......................................................................................................................................................................................................... 297
12.1.16 "Permission Denied" or "Access Denied" is Displayed When IE Is Used to Browse the LMT.......... 298
12.1.17 MML Command Failed to Be Executed or No Response to Tracing Tasks After the Browser Is
Upgraded to IE8......................................................................................................................................................................... 299
12.1.18 Settings on the LMT Failing to Take Effective..................................................................................................300
12.1.19 The LMT login page of a host NE or built-in NE fails to be opened....................................................... 301
12.1.20 No progress message can be reported on the Web LMT............................................................................. 302
12.1.21 What Do I Do If A Message "Stop running this script?" Is Displayed?................................................... 303
12.2 Java-related FAQs............................................................................................................................................................ 303
12.2.1 Help for Installing and Using the Java Plug-in...................................................................................................303
12.2.2 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE......305
12.2.3 Tracing and Monitoring Functions Cannot Be Used.........................................................................................306
12.2.4 Chinese Characters Displayed in the Tracing and Monitoring Windows...................................................311
12.2.5 LMT Fails to Function Properly during the tracing/monitoring/batch processing................................. 313
12.2.6 Interfaces for Performing Tracing or Monitoring Tasks Blinking................................................................. 316
12.2.7 Java Installation Fails.................................................................................................................................................. 316
12.2.8 Changing Settings for the Next-Generation Java Plug-in Fails.................................................................... 316
12.2.9 How to Handle a Web Page Error or Java Error Displayed on the LMT................................................... 320
12.2.10 Displaying the Java Security Warning.................................................................................................................322
12.2.11 Failure in Verifying the Verification Code During the Login to the LMT................................................ 322
12.2.12 The Application Blocked by Security Settings Dialog Box Is Displayed When Batch Processing,
Tracing, Monitoring, or Device Maintenance Is Enabled............................................................................................. 324
12.2.13 What Do I Do If A Message that Your Java version is out of date Is Displayed?................................ 325
12.3 Other FAQs......................................................................................................................................................................... 325
12.3.1 Installing OS Patches................................................................................................................................................... 325
12.3.2 Changing the Computer Time During the LMT Use Prohibited................................................................... 327
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. ix

BSC6910 UMTS
12.3.3 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding..................................327
12.3.4 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously..........................330
12.3.5 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes the Web
Pages to Turn Blank.................................................................................................................................................................. 331
12.3.6 Configuring the HTTPS Login Mode...................................................................................................................... 331
12.3.7 Unable to Save Tracking and Monitoring Data................................................................................................. 332
12.3.8 BTS Nodes Cannot Be Displayed Under Device Navigation Tree.................................................................333
12.3.9 LMT Login Web Page Cannot Be Opened with the PC OMU Installed..................................................... 334
12.3.10 Slow Response During an LMT Login................................................................................................................. 335
12.3.11 Batch Execution of MML Commands Fails Because Some MML Commands Contain Invisible
Carriage Returns or Line Feeds............................................................................................................................................. 336
12.3.12 How to Handle Shortcut Key Invalidation.........................................................................................................337
12.3.13 Tracing File Not Being Uploaded to the Specified Directory...................................................................... 337
12.3.14 Error Dialog Box Displayed When Online Help Is Opened..........................................................................338
12.3.15 Garbled Characters Displayed in the Chinese Names of Files in the File Manager and These Files
Failing to Be Removed............................................................................................................................................................. 338
12.3.16 Failure to Obtain the Verification Code When Users Attempt to Log In to the Web LMT After a
Version Upgrade or Rollback................................................................................................................................................. 339
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. x

BSC6910 UMTS
LMT User Guide 1 Change History
1 Change History
This section provides information about the changes in different document

versions. There are two types of changes, including technical changes and editorial
changes. Technical changes refer to changes in functions of a specific product
version. Editorial changes refer to changes in wording or addition of information
that was not described in the earlier version.
02 (2019-09-30)
Compared with Issue 01 (2019-06-06) of V100R021C10, this issue includes the
following changes.
Change Change Description

Type
Technical Adde None

change d
Modif JRE 1.7.X is no longer supported. For details, see 2.1

ied Configuration Requirements of the LMT PC.
Delet None
ed
Editorial Added the description of the command that controls automatic start
change of the FMA function. For details, see 10.2 Fast Fault Diagnosis.
01 (2019-06-06)
Compared with Draft B (2019-04-15), this issue includes the following changes.
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 1

BSC6910 UMTS

Type
Technical Add ● Added the description that "The Java bit version must be
change ed the same as that of the operating system, for example,
32-bit Java for 32-bit operating system." For details, see
2.1 Configuration Requirements of the LMT PC.
Mod ● Changed the Save Result button to Start Save and the
ified Download Report button to Export in the MML
command window. For details, see 4.1.2 Components of
the MML Command Window.
● Changed "The Progress tab page is displayed" to "The
WebLMT dialog box is displayed". For details, see 2.3
Components of the LMT Main Page.
Dele None
ted
Editorial Revised descriptions about how to delete temporary Java files. For
change details, see 12.2.1 Help for Installing and Using the Java Plug-in.
Draft B (2019-04-15)
Compared with Draft A (2018-12-31), this issue includes the following changes.

Type
Technical Add ● Added the following description: "When you log in to the
change ed LMT or click other Java functions, the WebLMT dialog box
is not displayed. Instead, a message dialog box is
displayed." For details, see 2.2 Logging In to and Logging
Out of the LMT.
● Added descriptions about the Download Report
parameter in the "MML command window" table. For
details, see 4.1.2 Components of the MML Command
Window.
● Added the following description in Procedure: "In the
WebLMT dialog box that is displayed, click the Batch
tab." For details, see 4.3 Batch Processing of MML
Commands.
● Added the path for saving message tracing files. For
details, see 7.2.3 Saving Traced Messages.
● Added the path for saving monitoring result files. For
details, see 8.2.3 Saving Monitoring Data.

BSC6910 UMTS

Type
Mod ● Click FTP Tool. A help page is displayed, providing

ified descriptions about Deploying an FTP Server Using
Windows IIS. For details, see 2.3 Components of the
LMT Main Page.
● Updated the MML command window image. For details,
see 4.1.2 Components of the MML Command Window.
● Changed the tracing method to start a tracing task on the
WebLMT. For details, see 7 Trace Management.
● Changed the monitoring method to start a monitoring
task on the WebLMT. For details, see 8 Performance
Monitoring.
● Modified descriptions about how to start collecting fault
information and setting related parameters on the
WebLMT. For details, see 8 Performance Monitoring.
● Modified descriptions about viewing data or results on the
WebLMT for some BSC maintenance functions. For
details, see 11 BSC Maintenance
Dele ● Deleted section "Configuring the FTP Server."

ted
Editorial ● Added the permission and function processes required for

change business query. For details, see 10 FMA.
Draft A (2018-12-31)
Compared with Issue 01 (2018-03-31) of V100R020C10, this issue includes the
following changes.

Type
Technical Added ● Added descriptions about Base Station Selection. For

change details, see 10.2 Fast Fault Diagnosis.
● Added the Call Count Per Cell parameter. For
details, see 7.4.10 Tracing IOS Messages.
Modifi ● Changed the recommended JRE version to 1.8.0.191.

ed For details, see 2.1 Configuration Requirements of
the LMT PC.
● Optimized the fault diagnosis GUI. For details, see
10.2 Fast Fault Diagnosis.
● Replaced the word "anonymity" with
"pseudonymization" in some sections.
● Changed the name of the iManager U2000 to
U2020.

BSC6910 UMTS

Type
Delete ● Deleted the description that only 32-bit Java plug-ins

d are supported. For details, see 12.2.1 Help for
Installing and Using the Java Plug-in.
● Deleted the note that if over 100 alarms are cleared,
flow control will be automatically enabled. For
details, see 5.5.1 Browsing Alarms/Events.
● Deleted Internet Explorer 9 from the
Recommended Configuration column in the Web
browser row. For details, see 2.1 Configuration
Requirements of the LMT PC.
Editorial ● Added the following operation: On the Business tab page, set
change the time to query the alarm status. For details, see 10.7
Business Query.
● Added a caution about accessing LMT on a Firefox browse.
For details, see 2.2 Logging In to and Logging Out of the
LMT.

BSC6910 UMTS
LMT User Guide 2 Introduction to LMT
2 Introduction to LMT
The Local Maintenance Terminal (LMT) is a web-based application that provides a

graphical user interface (GUI) to simplify operation and maintenance of the
BSC6910. Using the LMT, you can manage alarms, view message tracing results,
monitor performance, and maintain devices. You can also run man-machine
language (MML) commands and view command results on the LMT.
2.1 Configuration Requirements of the LMT PC

The computer on which the LMT is running is called the LMT PC. The LMT PC
must meet certain requirements of hardware, software, connection ports, and
communication capability.
2.2 Logging In to and Logging Out of the LMT
This section describes how to log in to the LMT for operations and how to log out
of it after the operations are complete.
2.3 Components of the LMT Main Page
You can log in to the LMT using a web browser to perform operation and
maintenance (O&M) operations on the BSC6910. This section describes the main
page of the LMT.
2.4 Obtaining a Documentation Package
This section describes how to query and obtain a documentation package of the
corresponding product version.
2.5 File Manager
The File Manager, a component of the LMT application, enables you to upload
files from the LMT to the OMU and download files from the OMU to the LMT. For
example, you can use the File Manager to obtain logs and upload data
configuration files.
2.6 User-defined Command Group
The User-defined Command Group is used to add commands to a specified
command group so that an admin user can add operation rights for rights-limited
users.
2.7 LMT Software
The Local Maintenance Terminal (LMT) software consists of the LMT Offline Tools,
Convert Management System, Performance Browser Tool, and TrafficRecording
Review Tool.

BSC6910 UMTS
2.1 Configuration Requirements of the LMT PC

The computer on which the LMT is running is called the LMT PC. The LMT PC
must meet certain requirements of hardware, software, connection ports, and
communication capability.
Hardware Requirements
Table 2-1 describes the hardware requirements of the LMT PC.
Table 2-1 Hardware requirements of the LMT PC

Ite Quantity Recommended Minimum Configuration
m Configuration
CP 1 2.8 GHz or above 866 MHz

U
RA 1 1 GB 512 MB
M
Ha 1 80 GB 10 GB
rd
dis
k
Dis - 1024 x 768 or higher 1024 x 768

pla
y
res
olu
tio
n
CD 1 - -
dri
ve
Et 1 10/100 Mbit/s 10/100 Mbit/s

he
rn
et
ad
ap
ter
Ot 5x1 Keyboard, mouse, Keyboard and mouse

he modem, audio card, and
r speaker
de
vic
es

BSC6910 UMTS
Software Requirements
Table 2-2 describes the software requirements of the LMT PC.
Table 2-2 Software requirements of the LMT PC

Item Recommended Configuration
Operating system Windows Vista/7, Windows 10, Windows Server

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

operating system
Web browser Internet Explorer 10 or 11, Firefox 31.0, Firefox 38.0

or Firefox 45.0.
NOTE
● Set the security level of the Web browser to medium
or low. Otherwise, the LMT menus cannot be viewed.
● If the Firefox browser is used, set the attribute of
dom.disable_window_flip by performing the following
operations: Open the Firefox browser and enter
about:config in the address bar. Search
dom.disable_window_flip in Search and double-click
dom.disable_window_flip to set the value to false.
Then, restart the browser. The default value of
dom.disable_window_flip is true.
Java plug-in called Java JRE 1.8.0.191 is recommended.

Platform Standard Edition JRE 1.6.X is not supported.
Runtime Environment
(JRE) JRE 1.7.X is not supported.
NOTE
● The Java bit version must be the same as that of the
operating system, for example, 32-bit Java for 32-bit
operating system.
● To obtain desired JRE versions, visit the official website
of Java.
● After installing the JRE 1.8.0.65 version, modify default
settings of Java by following the steps provided in
section 12.2.1 Help for Installing and Using the Java
Plug-in.

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

If a firewall is deployed between a PC and the LMT, before you use the PC to visit
the LMT through the Web, enable ports 80, 20, 21, and 443 of the firewall.
● Port 80 is the default Hypertext Transfer Protocol (HTTP) port, which is used for web
page browsing.
● Ports 20 and 21 are File Transfer Protocol (FTP) ports.
● Port 443 is the default Hypertext Transfer Protocol Secure (HTTPS) port, which is used
for HTTPS login mode.
Communication Capability Requirements

The LMT PC must support Transmission Control Protocol/Internet Protocol
(TCP/IP) and meet the requirements of effective bandwidth. Table 2-3 describes
the effective bandwidth requirements of the LMT PC.
Table 2-3 Effective bandwidth requirements of the LMT PC
Item Protocol Recommended Minimum

Configuration Configuration
Requirements of HTTP 2 Mbit/s or higher 512 Kbit/s

effective
bandwidth
● The speed of web page browsing speed is highly dependent on bandwidth. An LMT PC
with the recommended configuration can speed up browsing, thereby improving your
browsing experience. If you use an LMT with the minimum configuration, you can use
all LMT functions. The browsing speed, however, will be relatively slow.
● Effective bandwidth indicates the bandwidth available for the LMT. If many programs
compete with the LMT for bandwidth resources, a serious delay occurs despite a
bandwidth of 2 Mbit/s.

BSC6910 UMTS
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
● You have installed the JAVA Platform Standard Edition Runtime Environment
(JRE) program before using the LMT. If no JRE plug-in is installed, a message
is displayed when you log in to the LMT, prompting you to install the plug-in.
Follow the instructions to install the plug-in. If the JRE plug-in on the LMT PC
is not the latest version, a message is displayed, prompting you to upgrade
the plug-in version. In this case, you are advised to uninstall the existing JRE
plug-in and then install a new version. If you cannot log in to the LMT after
you upgrade the JRE program, restart the web browser and retry.
● If the Java Update Needed popup is displayed when you log in to the LMT,
select Update (recommended) to install the latest version.
● A maximum of 32 local users and EMS users can log in to the LMT.
● You can log in to the BSC6910 LMT as a Local user or an EMS user.
– Local users:
Managed independently by the BSC6910 LMT. You can log in to the
BSC6910 when you are installing the BSC6910 system or when the OMU
is disconnected from the U2020. User admin is a default local user.
– EMS users:
Managed by the U2020. They are created, modified, authenticated, and
authorized by the U2020. Only authorized EMS users can log in to the
BSC6910 using the LMT. For BSC6910 operations, authorized EMS users
can also log in to the U2020 server through the U2020 client.
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.

BSC6910 UMTS
NOTICE
● 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.
● 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.
● 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.
● Before logging in to the LMT in the Internet Explorer (IE) browser, perform the
following operations:
● 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.
● 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.
● 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."
● The default policy to log in to the LMT can be specified by the WebLMT Login
Policy parameter in the SET WEBLOGINPOLICY command. The parameter can
be set to any of the following values. (1) COMPATIBLE(Compatible): Either
HTTP or HTTPS can be used to log in to the LMT. (2)
HTTPS_ONLY(Https_only): Only HTTPS can be used to log in to the LMT. (3)
LOGIN_HTTPS_ONLY(Login_https_only): When HTTP is used to log in to the
LMT, HTTP is changed to HTTPS before login, then HTTPS returns to HTTP after
login. Data over HTTP is transmitted in plaintext and prone to disclosure.
Therefore, the value HTTPS_ONLY(Https_only) is recommended.
● If LMT Login Policy is set to HTTPS_ONLY(Https_only) and the LMT login
policy set on the U2020 GUI is HTTP, the U2020 will fail to log in to the LMT
using the proxy server.
● By default, the LMT supports TLS1.0, TLS1.1, and TLS1.2. You can set the
supported SSL/TLS protocol type by running the SET WEBLOGINPOLICY
command. The SSL/TLS protocol with a higher security level is recommended,
and SSL3.0 or TLS1.0 is not recommended. The LMT always supports TLS1.2,
which cannot be disabled.
● The Java plug-in is incompatible with the IE browser. As a result, when you
open the Save window while creating a window to log in to the WebLMT
(using the windows.open algorithm), the new window is delayed. This problem
occurs only in IE 8 and IE 9, not in IE 10 and later versions. In addition, this
problem does not occur in a WebLMT later than RAN20.0.

BSC6910 UMTS
● To access LMT on a Firefox browser, do not repeatedly click go-back button on

the browser or press Backspace on keyboard. Otherwise, LMT will
automatically go back to the login page.
Procedure
Step 1 Enter the LMT login page by using one of the following modes:
Mode Mode Operation
Description
Mode 1: The LMT directly Type the external virtual IP address of the
direct connects to the OMU in the Address bar of the IE browser.
connection OMU without Press Enter on the keyboard, or click Go
using any proxy next to the Address bar to enter the login
server. 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 U2020_IP.
Mode 2: The LMT 1. You can set the U2020 proxy server in the
connection connects to the browser by using the following method:
through the OMU through Choose Tool > Internet Options on the tool
U2020 that is the U2020 that bar of the browser. In the Connection tab
configured as is configured as page, click LAN Settings. Then specify the
the proxy the proxy server IP address and port number of the U2020
server for the browser. server in the Proxy server area. The default
NOTE port number is 8080.
This mode is NOTE
recommended After the IP address and port No. of the U2020
when the U2020 proxy server are specified, you need to select the
proxy server Use the same proxy server for all protocols
needs to be used option.
to connect to the
OMU. 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.

BSC6910 UMTS
Mode Mode Operation

Description
Mode 3: The LMT Type "U2020_IP/OMU_IP/" (for example,

connection connects to the 10.141.130.146/10.141.151.208/) or
through the OMU through "http(s)://U2020_IP/OMU_IP/login.html" in
U2020 with the U2020 with the Address bar of the IE browser. Press
both IP IP addresses of Enter on the keyboard, or click Go next to
addresses both U2020 and the Address bar to enter the login window
entered OMU entered in of the BSC6910. Note that "/" must be
the browser. included in "U2020_IP/OMU_IP/" behind
NOTE "OMU_IP." If another proxy server is already
This mode is used set, you need to add U2020_IP to the IP
only when the addresses that do not use the proxy server
explorer is under Exceptions.
configured with a
proxy server, NOTE
which is not the OMU_IP indicates the external virtual IP address
U2020 and of the OMU and U2020_IP indicates the IP
cannot be address of the U2020 server.
changed.
● When you are logging in to the LMT using the second or third method, settings on the
U2020 and on the NE side must be consistent with the setting mapping listed in the
following table. Otherwise, the login fails.
● You can run the LST WEBLOGINPOLICY command to query the policy for login to LMT and
data transmission.
● For details about how to set the policy for logging in to the LMT on the U2020 GUI, see
section Setting Web LMT Options in U2020 Data Management User Guide.
U2020 Security Connection Mode Policy for Login to LMT and Data
Transmission
Common Mode Only COMPATIBLE(Both HTTP and

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

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

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

● Set User Type to Local or EMS.
● If User Type is set to EMS, the user name and password need to be
authorized by the U2020. The default password for users emscomm and
emscommneteco is ei*b+@b#6Nh(tS1j.

BSC6910 UMTS
● If port 8080 is used as the U2020 proxy port, enter the user name and
password of the proxy server when you open the LMT main page, Trace,
Monitor, Batch, Device Maintenance, or FMA tab page, and so on. The default
user name and password of the proxy server are proxyuser and
Changeme_123, respectively.
● You need to change the password upon the first login to LMT (including the
first login after the password is reset by the administrator) only when the
switch First Login Must Modify Password Switch is turned on. You can set
the switch parameter by running the SET PWDPOLICY command.
● It is recommended that you change the password at your first login and then
change the password every three months.
Step 3 Click Login.
● You can view the LMT main page after a successful login. In the lower right part of the
LMT main page, the fields related to the latest login are displayed, including Use
Default Password, Last Login IP, and Last Login Time.
● After a successful login to the LMT main page, when you click the batch processing,
tracing, monitoring, or device maintenance function, the Local Maintenance Terminal
window is opened for you to execute commands or view data and results. For details
about how to open the Local Maintenance Terminal, see How to Open the Local
Maintenance Terminal.
● Before logging in to the BSC6910 as an EMS user, you need to set up a connection
between the BSC6910 and the U2020 server.
● If the login fails, click Reset. Specify User Name, Password, and Verification Code
again to log in. If the login fails again, check whether the connection between the LMT
and the OMU is normal.
Step 4 Optional: To lock the LMT window, click Lock in the top right corner of the LMT
main page.
Step 5 To exit the LMT, click Logout in the top right corner of the LMT main page.
● After logout, the login interface for User type of Local is displayed. On this login interface, if
you want to re-log in to the LMT on the EMS, you must set User type to EMS.
● 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.
● Before logging in to the LMT through HTTPS, configure the HTTPS login mode and
certificate files by referring to 12.3.6 Configuring the HTTPS Login Mode.
● In HTTPS mode, if you need to connect to the OMU with the U2020 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.
● 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.
● Correct errors displayed during the login by referring to 12.1.8 The Error "Certificate
Invalid" Is Displayed During an HTTPS Login and 12.1.9 The Error 'Mismatched Address'
Is Displayed During an HTTPS Login.
● After entering the HTTPS login page, which is the same as the HTTP login page, perform the
same operations for a login.
----End

BSC6910 UMTS
2.3 Components of the LMT Main Page

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

BSC6910 UMTS
Table 2-4 Components of the LMT main page

Component Description
Workspace Provides the view of LMT function icons.

● If a BSC6910 is equipped with built-in network
elements (NEs), an icon bar is displayed on the upper
part of the Workspace, presenting the dependency
relationships between the host NE and the built-in
NEs.
– The host NE is displayed on the left of the dividing
line and the built-in NEs are displayed on the right
of the dividing line. When the LMT page for
performing operations on an NE is displayed, the
NE is highlighted and the name and type of the NE
are displayed on the label of the NE.
– You can double-click an NE that is not highlighted
to quickly enter the LMT page for performing
operations on the NE.
– If you have not logged in to this NE, a new LMT
login page is displayed, prompting you to enter
the user name and password.
– If you have logged in to this NE, the LMT page
for performing operations on the NE is displayed
immediately.
● If a BSC6910 is not equipped with built-in NEs, the
icon bar is not displayed.
● Below the icon bar, there are entries of other
functions. You can click an icon to start the
corresponding function.
Alarm/Event You can query active alarms, alarm logs, and alarm
configuration on this tab page. For details, see 5 Alarm/
Event Management.
Batch You can run man-machine language (MML) commands

in batches on this tab page. For details, see 4.3 Batch
Processing of MML Commands.
Trace You can manage message tracing tasks on this tab page.
For details, see 7 Trace Management.
Monitor You can monitor performance data on this tab page. For
details, see 8 Performance Monitoring.
Device You can maintain the device panel on this tab page. For
Maintenance details, see 9 Device Panel.
FMA You can use this function to handle network faults. It

includes the following functions: 10.2 Fast Fault
Diagnosis, 10.3 Hierarchical Delimitation, 10.5
Information Collection, 10.6 Business Validation, and
10.7 Business Query.

BSC6910 UMTS
MML You can run MML commands on this tab page. For
details, see 4.1.2 Components of the MML Command
Window.
Progress You can view the progress of a task on this tab page. The
eGBTS does not support this function.
NOTE
Click Progress. The WebLMT dialog box is displayed. Double-
click an entry to view the detailed information in the displayed
Progress Management dialog box.
FTP Tool Click FTP Tool on the toolbar. The FTP tool help page is
displayed.
Password You can click it to change the password of the current

user. After changing the password, use the new password
when logging in to the LMT again.
User-defined You can click it to add commands to a specified

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

Documentation the corresponding product versions. For details, see 2.4
List Obtaining a Documentation Package.
System Settings You can click it to modify the auto lock time and path for
saving result files.
● Auto Lock Time(s): You can specify a time period as
required. If there are no mouse or keyboard operations
during the specified time period, the LMT
automatically goes to the locked page. The setting
prevents unauthorized users from using others'
accounts to perform unauthorized configuration and
maintenance.
● Result File Save Path: You can specify a path for
saving operation result files. The default path is C:
\Web LMT\MBSC\output.
● Security Instructions: deselected by default. Once
selected, security instructions are prompted on the
login page.
File Manager You can click it to upload files from the LMT to the OMU
and download files from the OMU to the LMT. For
details, see 2.5 File Manager.
About You can click it to display the current version of the LMT.

BSC6910 UMTS
Lock You can click it to lock the current operation page for
security purposes.
NOTE
● After you click Lock on the toolbar, the LMT is locked.
● You can click in the blank area on the web page or press
Enter, type the password, and then click OK or press Enter to
log in to the LMT workspace again.
Logout You can click it to log out the current user without exiting
from the LMT. Logout of one user facilitates login of
another user.
Online Help
The LMT provides the following two types of online help:
● Online help system
● MML help
Table 2-5 describes the contents and startup method of the LMT online help.
Table 2-5 Description of LMT online help

Name Content Startup Method
Online Provides the If the Microsoft Internet Explorer is used:

help following ● On the LMT main page, press F1 or click Help to
system information: display online help information.
● LMT online ● In a displayed dialog box on the LMT, press F1 to
help display help information about the dialog box.
● Alarm If the Firefox Explorer is used, click Help on the LMT
reference main page to display online help information.
● Event
reference

BSC6910 UMTS
Name Content Startup Method
MML Provides the Type an MML command in the Command Input

help following field. Press Enter or click Assist, and then click the
information Help Information tab. Help information about the
about each command is displayed on the Help Information tab
MML page.
command:
● Command
function
● Note
● Parameters
● Example
● Output
description
(for query
commands
only)
2.4 Obtaining a Documentation Package

This section describes how to query and obtain a documentation package of the
corresponding product version.
Startup Method
On the toolbar of the LMT, click Obtain Documentation List.
GUI
● Library Name: Name of a documentation package of the current product
version.
● Product Version: Current product version number.
● Library Version: Version number of the documentation package of the
current product version.
● Available at support.huawei.com:
– Yes indicates that the documentation package has been released globally,
and you can obtain it from http://support.huawei.com.
– No indicates that the documentation package has not been released at
http://support.huawei.com and you can contact Huawei engineers to
obtain it.
Function
You can use either of the following methods to download a documentation
package:

BSC6910 UMTS
● Search for the required documentation package at http://support.huawei.com

and download the package.
● In the Obtain Documentation List dialog box, click Export. Then, use the
HedEx Lite to open the exported .hdxi file. The tool automatically searches on
http://support.huawei.com for the product documentation package included
in the file so that you can download the package.
Before using this function, ensure that:

● The documentation package in the documentation list can be downloaded from
http://support.huawei.com.
● You have obtained the account information for visiting http://support.huawei.com
and can visit the website successfully.
● (For initial use only) You have downloaded the HedEx Lite from the homepage of
http://support.huawei.com to your PC and the HedEx Lite is running properly.
NOTICE
To prevent a software package from being maliciously tampered with during

transmission or storage, download the corresponding digital signature file for
integrity verification when downloading the software package.
After the software package is downloaded, verify its PGP digital signature
according to the OpenPGP Signature Verification Guide. If the software
package fails the verification, do not use the software package, and contact
Huawei technical support engineers.
Before a software package is used in installation or upgrade, its digital
signature also needs to be verified according to the OpenPGP Signature
Verification Guide to ensure that the software package is not tampered with.
Visit either of the following websites to obtain the OpenPGP Signature
Verification Guide:
● Carrier customers: https://support.huawei.com/carrier/
digitalSignatureAction
● Enterprise customers: https://support.huawei.com/enterprise/en/tool/
pgp-verify-TL1000000054
2.5 File Manager

The File Manager, a component of the LMT application, enables you to upload
files from the LMT to the OMU and download files from the OMU to the LMT. For
example, you can use the File Manager to obtain logs and upload data
configuration files.
Startup Method
On the toolbar of the LMT, click File Manager in the WebLMT dialog box that is
displayed.

BSC6910 UMTS
Users' operation rights to the File Manager depend on their rights settings. For descriptions of
the operation rights, see 3.1.4 Operation Rights.
● ADMINISTRATOR-level and admin-level users have full operation rights to the File Manager.
● Users at other levels can only use the File Manager to download files. They are not
authorized to upload or delete files.
GUI
Figure 2-2 shows the window of the File Manager.
Figure 2-2 File Manager window
Table 2-6 describes the components of the File Manager window.
Table 2-6 Components of the File Manager window

Number Component Description
1 Path switch area Directly navigates to a file folder or file.
2 File navigation tree Displays files on the OMU in a navigation

tree.
3 File list Provides detailed information about files on

the OMU.
4 File processing area Provides buttons for processing files.
5 Task list Displays task processing information about

files.

BSC6910 UMTS
Path Switch Area

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

This area displays all directories that users can view and process on the server.
When you right-click on a selected folder, a shortcut menu containing the
following choices is displayed:
● Refresh Whole Folder Tree:
Choose Refresh Whole Folder Tree to refresh the navigation tree so that it
displays the latest directory organizations.
● Set Search Criteria:
When you choose Set Search Criteria, the Set Search Criteria dialog box is
displayed, as shown in Figure 2-3. Select required search criteria, enter details
about the selected search criteria, and click Confirm.
Figure 2-3 Set Search Criteria dialog box
– Modified time: You can specify a time from the year 2000 to 2038. If
both Start time and End time are set, End time must be later than Start
time.
– Files can be searched by File name. The file name has a maximum of 50
bytes containing only English letters, numbers, dots, and underscores.

BSC6910 UMTS
● For easy differentiation, the icon of the folder for which the search criteria has
been set is displayed as .

● After the search criteria are applied, only files meeting the search criteria under the
folder are displayed in the File Manager.
● The search criteria take effect only for the current folder, not for its sub-folders.
● If no search criteria are selected, after you click Confirm or Delete Search Criteria,
all files will be displayed.
● Delete Search Criteria: Choose Delete Search Criteria to delete the search
criteria set for a folder.
File List
This area displays files in a selected folder.
Only files meeting specific search criteria are displayed under a folder that is configured
with search criteria.
You can select a file, right-click it, and choose Refresh, Upload, Download, or
Delete from the shortcut menu.
File Processing Area

This area provides the following file processing buttons.
● Refresh:
Refreshes the list of files under the current folder.
● Upload:
Uploads a selected file from the LMT PC to the OMU.
● Download:
Downloads a selected file from the OMU to the LMT PC. If the directory is
specified before the download, the selected file is downloaded to the preset
directory.
● Delete:
Deletes a selected file.
● Directory:
Changes the target folder for saving a downloaded file. If the directory is
specified before the download, the selected file is downloaded to the preset
directory.
If a target directory has been specified and the File Manager has been running before the target
directory is specified, the target directory for saving downloaded files does not change.
When the bandwidth is 2 Mbit/s, you are advised to concurrently download a maximum of 1000
files and upload a maximum of 50 files.

BSC6910 UMTS
Task List
This area displays information about current tasks. You can perform the following
operations on the tasks:
● Clear Finished Task:
Right-click the blank area in the task list and choose Clear Finished Task
from the shortcut menu to clear all finished tasks from the task list.
● Clear Selected Task:
Select a task, right-click it, and choose Clear Selected Task from the shortcut
menu to remove the task from the task list.
● Pause Selected Task:
Select an ongoing upload/download task in the task list, right-click it, and
choose Pause Selected Task from the shortcut menu to suspend the current
upload/download task.
● Continue Selected Task:
Select a suspended upload/download task in the task list, right-click it, and
choose Continue Selected Task from the shortcut menu to resume the
upload/download task.
● Clear Failed Task: Right-click the blank area in the task list and choose Clear
Failed Task from the shortcut menu to clear all failed tasks from the task list.
● Download Selected Task: Select a task to be downloaded, right-click it, and
choose Download Selected Task from the shortcut menu to download the
task.
● Set Display Columns:
Right-click the blank area in the task list, choose Set Display Columns from
the shortcut menu, and select information to display in the submenu.
2.6 User-defined Command Group

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

BSC6910 UMTS
Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users are allowed to
perform this operation.
If an authority-limited user performs this operation, an error message will be displayed,
indicating an operation failure.
GUI
Figure 2-5 shows the User-defined Command Group dialog box.
Figure 2-5 User-defined Command Group dialog box
Table 2-7 describes the components of the User-defined Command Group dialog
box.
Table 2-7 Components of the User-defined Command Group dialog box

No. Component Description
1 Command group Used to select a command group ranging

selection area from G_15 to G_31.

BSC6910 UMTS
No. Component Description
2 Authorization item Displays all MML commands and

area encapsulated GUI commands.
NOTE
All items under *GUI Authorization Items are
marked with * to distinguish them from MML
commands.
3 Button for adding Used to add the selected commands in the

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

authorization items right pane.
5 Options for Display authorization items of MML

displaying or hiding commands.: Displays or hides authorization
authorization items items of MML commands.
Display authorization items of the GUI
function.: Displays or hides authorization
items of MML commands.
6 Authorization item Displays the commands to be added to the

addition area current command group.
7 Apply or Cancel Apply: Adds all the commands in the right

button pane to the current command group.
Cancel: Abandons previous operations on the
current dialog box and closes it.
2.7 LMT Software

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

This section describes how to install the LMT Offline Tools on the LMT PC.
Prerequisites
● A valid serial number for the LMT software has been obtained.
● The PC for installing the LMT Offline Tools complies with the specifications
described in 2.1 Configuration Requirements of the LMT PC.

BSC6910 UMTS
● When the LMT Offline Tools of the current version have been installed:
– If the LMT Offline Tools of a later version is required, install it directly.
– If the LMT Offline Tools of an earlier version is required, uninstall the
current version, install the earlier version, and reinstall the current
version.
These operations do not apply to patch versions of the same R version.
Procedure
● Using an installation CD-ROM
a. Log in to the LMT PC as an administrator.
b. Insert the installation CD-ROM into the CD-ROM drive.
▪ The setup program runs automatically.
▪ If the setup program fails to run automatically, double-click

setup.bat or setup.vbs in the installation directory of the CD-ROM.
c. Select an installation language, and click OK. The HUAWEI Local
Maintenance Terminal is displayed.
d. Click Next. A dialog box is displayed, prompting you to read the copyright
notice.
e. Read the software certificate declarations. If you accept the agreement
terms, select I accept these terms, and click Next. A dialog box is
displayed, prompting you to specify the installation path. If you do not
accept the agreement terms, click Cancel to quit the installation.
f. Use the default installation path or specify a custom installation path,
and click Next.
The default installation path is D:\HWLMT_Enhanced.

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

BSC6910 UMTS
● Using the installation package of the LMT Offline Tools
Contact Huawei engineers to obtain the installation package of the LMT

Offline Tools from http://support.huawei.com/carrier/#click=main3 and
enter BSC6910 in the search window. Then, download the required software
version.
NOTICE

according to the OpenPGP Signature Verification Guide. If the software
package fails the verification, do not use the software package, and contact
Huawei technical support engineers.
Before a software package is used in installation or upgrade, its digital
signature also needs to be verified according to the OpenPGP Signature
Verification Guide to ensure that the software package is not tampered with.
Visit either of the following websites to obtain the OpenPGP Signature
Verification Guide:
● Enterprise customers: https://support.huawei.com/enterprise/en/tool/
pgp-verify-TL1000000054
----End
2.7.2 LMT Offline MML

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

This section describes how to start the LMT offline MML server and the dialog box
of the LMT offline MML server.
Startup Method
To start the LMT offline MML server, choose Start > All Programs > HUAWEI
Local Maintenance Terminal > WebLMT OffLine MML on an LMT PC.
GUI
Figure 2-6 shows the dialog box of the LMT offline MML server.

BSC6910 UMTS
If the LMT offline MML server has been started and minimized, double-click the icon on
the system tray of the LMT PC to display the dialog box of the LMT offline MML server.
Figure 2-6 WebServer dialog box
Table 2-8 describes the components of the WebServer dialog box.
Table 2-8 Description of the LMT offline MML server
Routine tab page Displays the status of the LMT offline MML server.
NOTE
● Click Hide to minimize the LMT offline MML server to the
system tray of the LMT PC.
● Click Stop to stop the LMT offline MML server.
● Click Start to start the LMT offline MML server.
● Click Open Browser to display the login window of the LMT
offline MML tool.
Config tab page Configures the server port.
About tab page Displays information about the LMT offline MML tool.
2.7.2.2 Logging In to and Out of the LMT Offline MML Tool

This section describes how to log in to the LMT offline MML tool and how to exit
from it.

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

When you use a web browser to log in to the LMT offline MML, you can view
MMLs, make MML scripts, and obtain the LMT online help. This section describes
the LMT offline MML window.
GUI
Figure 2-7 shows the LMT offline MML window.

BSC6910 UMTS
Figure 2-7 LMT offline MML window
Table 2-9 describes the components of the LMT offline MML window.
Table 2-9 Components of the LMT offline MML window

Navigation Tree Displays all MML commands. When you double-click an

MML command, the MML command is displayed in the
Command Input field.
Search Uses keywords to search for MML commands.
Operation Record Displays commands that have been run.

tab page NOTE
The Send Time displayed in the operation record is the system
time of the LMT PC.
Help Information Displays help information about MML commands.

tab page
Manual editing area Displays manually input MML commands and their
parameters.
History Command Displays all commands executed during the current login
field and relevant parameters.
Command Input Displays all the MML commands available on the system
field in the drop-down list. You can select an MML command
from the drop-down list or enter an MML command.

BSC6910 UMTS
Parameter area Displays parameters of a selected or an input command.

Before running the command, set parameters for it.
Parameters in red are mandatory and those in black are
optional.
Help Click Help to obtain LMT online help of the required

version.
About Click About to obtain version information about the LMT

offline MML.
2.7.2.4 Preparing Offline MML Scripts

This section describes how to prepare offline MML scripts.
Procedure
Step 1 Log in to the LMT offline MML tool.
Step 2 In the LMT offline MML window, enter an MML command in the Command Input
text box and click Assist to set related parameters.
The LMT offline MML tool provides an association function. When you are typing a
command in the Command Input field, related commands are displayed for reference.
Step 3 Click Save to save the entered MML command.
● The command input and parameter settings saved to the local file by clicking Save do
not overwrite the existing information saved in the local file.
● You can select an MML command in the Operation Records area, right-click it, and
choose the related option to clear the selected or all records.
----End
2.7.3 Convert Management System

The Convert Management System is a component of the LMT Offline Tools. It
enables communication between the OMU and the alarm box and is used to
transfer the alarm information, alarm box control information, and alarm box
status information. To connect the LMT to the alarm box, the Convert
Management System must be started. The Convert Management System uses the
Ethernet port to communicate with the OMU and the serial port to communicate
with the alarm box.
Function
The Convert Management System provides the following functions:
● Forwards alarm operation instructions from the LMT.

BSC6910 UMTS
● Forwards alarm information to the alarm box.

● Detects the real-time status of the connection between the LMT and the
OMU and that between the LMT and the serial port of the alarm box, and
reports alarms if any.
Startup Method
If Microsoft Visual C++ 2005 SP1 Redistributable Package (X86) is not installed on the LMT
PC, the Convert Management System cannot start. Download this package from
www.microsoft.com.
On the LMT PC, choose Start > All Programs > HUAWEI Local Maintenance
Terminal > Convert Management System.
GUI
Figure 2-8 shows the window of the Convert Management System.
Figure 2-8 Convert Management System window
Table 2-10 describes the components of the Convert Management System

window.
Table 2-10 Components of the Convert Management System window
1 Menu bar Provides entries for system operations.

BSC6910 UMTS
2 Toolbar Provides the shortcut icons for system

operations.
3 Information output Displays the real-time output of the Convert

window Management System.
2.7.4 Performance Browser Tool

The Performance Browser Tool, a component of the LMT Offline Tools, is used to
parse descriptive performance files in the OMU.
Startup Method
On the LMT PC, choose Start > All Programs > HUAWEI Local Maintenance
Terminal > Performance Browser Tool.
GUI
Figure 2-9 shows the window of the Performance Browse Tool.
Figure 2-9 Performance Browse Tool window
The Table 2-11 describes the components of the Performance Browse Tool
window.

BSC6910 UMTS
Table 2-11 Components of the Performance Browse Tool window


You can click Help to obtain information
about how to use the tool.

operations.
3 Measurement Provides statistical measurement files in a

statistics window tree structure.
4 Detailed Displays the detailed information about a

information selected performance counter file.
window
2.7.5 TrafficRecording Review Tool

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

BSC6910 UMTS
Table 2-12 describes the components of the TrafficReview window.
Table 2-12 Components of the TrafficReview window


operations.
3 Service data Displays trace and monitor tasks.

retrieval window

BSC6910 UMTS
LMT User Guide 3 Operation Rights Management
3 Operation Rights Management
This chapter describes principles of managing operation rights, user accounts, and
command groups.
3.1 Concepts Related to Operation Rights Management

This section describes concepts related to operation rights management, including
principles of operation rights management, command groups, operation rights,
user passwords, operation time limits, and account status.
3.2 Management of User Accounts
This section describes how to create, modify, and delete external user accounts on
the BSC6910 LMT. Only user admin, ADMINISTRATOR-level users, and some
CUSTOM-level users are authorized to create, modify and delete external user
accounts.
3.3 Management of User Passwords
This section describes how to define and query login password policies, change the
password of an active user, or change the password of an external user account.
3.4 Management of Command Groups
This section describes how to query and rename command groups and how to
change commands in a command group. Only the admin, ADMINISTRATOR-level,
and authorized CUSTOM-level users can query, rename and change the
information about the command groups.
3.5 Management of FTP Rights
This section describes how to manage FTP rights. FTP rights of files in the
MBSCdirectory on the OMU are classified into the following two topics.
3.1 Concepts Related to Operation Rights Management

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

This section describes principles of managing the operation rights of the BSC6910
LMT in terms of user identities, operation rights, and operation time limits.

BSC6910 UMTS
The operation and maintenance (O&M) subsystem of the BSC6910 allows multiple
users to perform operations concurrently. For system security reasons, the
following aspect of operation rights must be managed and controlled:
● User identities:
A user must enter a correct user name and password to log in to the system.
● User rights:
Users of different levels are permitted to use different command groups for
GUI or MML command operations.
● Operation time limits:
An operation limit specifies the times when a user is permitted to perform
operations.
3.1.2 User Passwords

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

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

The password of user admin is set during the installation of the OMU software.
User admin, ADMINISTRATOR-level users, and authorized CUSTOM-level users
can create external user accounts and set passwords for these accounts.
Permissions to Change Passwords

All users can change their own passwords. To change the password of user admin,
run the MOD OP command on the U2020.
For details, see 3.3.3 Changing the Password of the Active User Account and
3.3.4 Changing the Password of an External User Account.
3.1.3 Command Groups

The BSC6910 provides 17 command groups, including G_0 to G_14, G_NIC, and
G_OTHER with different functions.
Table 3-1 describes these command groups.

BSC6910 UMTS
Table 3-1 Command groups
Command Group Function
G_0 Used to query system information, such as user groups,

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

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

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

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

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

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

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

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

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

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

panels.
G_12 Used to manage software, for example, to manage

patches.
G_13 Used to query base station information, such as

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

base station software or to reset base stations.
G_NIC Used to collect fault information.
G_OTHER Used to query other system information, for example,

to query the configuration parameters of the RNC.

BSC6910 UMTS
For operations related to these command groups, see 3.4 Management of

Command Groups.
3.1.4 Operation Rights

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

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

There are five types of external user accounts. Each type of external user accounts
is granted different operation rights, which are described in Table 3-2.
Table 3-2 External user accounts

Level Assigned Operation Rights Remarks
Command
Group
GUEST G_0, G_2, G_4, Data query The operation

G_6, G_8, and rights are
G_13, predefined by
G_OTHER the system and
cannot be
USER G_0, G_2, G_4, ● Operation rights of changed.
G_6, G_7, G_8, GUEST-level users
G_9, G_10, ● System operation and
G_11, G_12, maintenance (O&M)
G_13, and
G_14,
G_OTHER
OPERATOR G_0, G_2, G_3, ● Operation rights of

G_4, G_5, G_6, USER-level users
G_7, G_8, G_9, ● Data configuration
G_10, G_11,
G_12, G_13,
and G_14,
G_OTHER

BSC6910 UMTS
Level Assigned Operation Rights Remarks

Command
Group
ADMINISTRAT G_0, G_1, G_2, All operation rights

OR 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,
G_OTHER
CUSTOM Command Specified when the account The operation

groups are is being created rights can be
assigned changed.
when the Different
account is CUSTOM-level
being created. users may have
different
operation rights.
● An authorized CUSTOM-level user can perform operations on user accounts and

command groups only by running MML commands.
3.1.5 Operation Time Limits

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

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

An operation time limit is defined by date, day, and time.
Table 3-3 provides some examples of operation time limits.

BSC6910 UMTS
Table 3-3 Examples of operation time limits
SN Date Day Time Permitted Operation Time
1 2013-02-0 Monday to 8:00:00 to 8:00:00 to 18:00:00 on

1 to Friday 18:00:00 Monday through Friday from
2014-02-0 2013-02-01 to 2014-02-01
1
2 - Saturday - Any time on Saturdays and

and Sundays
Sunday
3 - - - No operation time limits are

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

User admin, ADMINISTRATOR-level users, and authorized CUSTOM-level users
can set or change operation time limits of all external user accounts.
3.1.6 Account Status

BSC6910 LMT account status is normal or prohibited.
● Normal: When the account status is normal, a user can log in to the system
using this account.
● Prohibited: When the account status is prohibited, a user can log in to the
system using this account.
3.2 Management of User Accounts

This section describes how to create, modify, and delete external user accounts on
the BSC6910 LMT. Only user admin, ADMINISTRATOR-level users, and some
CUSTOM-level users are authorized to create, modify and delete external user
accounts.
3.2.1 Creating an External User Account

This section describes how to create an external user account and set the account
password, user level, executable command groups (only for CUSTOM-level users),
operation time, and account status.
Prerequisites
You have logged in to the LMT with an authorized account.

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

This section describes how to modify attributes of an external user. The attributes
include the user name, user password, user level, operation rights, operation time,
and account status. The new password takes effect at the next login. Modifications
of other attributes take effect immediately.
Prerequisites
Procedure
Step 1 Run the MOD OP command to modify the attributes of an external user account.
----End
3.2.3 Deleting an External User Account

This section describes how to delete an external user account.
Context
NOTICE
User admin is the permanent built-in user account and cannot be deleted.
Procedure
Step 1 Run the RMV OP command to delete an external user account.
----End
3.3 Management of User Passwords

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

BSC6910 UMTS
3.3.1 Defining Login Password Policies

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

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

This section describes how to change the password of the active user account. The
new password takes effect at the next login.
Prerequisites
Procedure
Step 1 On the toolbar of the LMT main page, click Password. The Password dialog box is
displayed.
Step 2 In the displayed Password dialog box, enter the current password in the Old
Password field, enter the new password in the New Password and Confirm
Password fields, and click OK.
You are advised to change the password at your first login and then change the password every
three months.
----End

BSC6910 UMTS
3.3.4 Changing the Password of an External User Account

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

This section describes how to query and rename command groups and how to
change commands in a command group. Only the admin, ADMINISTRATOR-level,
and authorized CUSTOM-level users can query, rename and change the
information about the command groups.
3.4.1 Querying a Command Group

The system provides 17 command groups, including G_0 to G_14, G_NIC, and
G_OTHER.
Prerequisites
You have logged in to the LMT with an account authorized for this operation.
Procedure
Step 1 Run the LST CCG to query the command groups.
----End
3.4.2 Renaming Command Groups
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 the command group.
----End

BSC6910 UMTS
3.4.3 Changing Commands in a Command Group

Prerequisites
Procedure
● 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
3.5 Management of FTP Rights

This section describes how to manage FTP rights. FTP rights of files in the
MBSCdirectory on the OMU are classified into the following two topics.
● Default FTP rights of different levels of accounts.
● FTP rights of different levels of accounts based on the FTP access control rules
configured using MML commands.
When no FTP access control rule is configured, different levels of accounts in the
system use the default FTP rights. When FTP access control rules are configured,
these rules take effect based on the default FTP rights. Both of the preceding FTP
rights take effect on files upload or downloaded using FTP or LMT file manager.
3.5.1 Managing Default FTP Rights

The following table provides the commands for querying default FTP rights.
Table 3-4 Commands for querying default FTP rights
Function Command
Querying default FTP rights after the LST FTPDIRAUTH

current user logs in to FTP
Querying default FTP rights after a LST FTPDIRAUTH(DN=local,OP=XXX)

local user logs in to FTP
Querying default FTP rights after a LST FTPDIRAUTH(DN=EMS,OP=XXX)

domain user logs in to FTP
● A local administrator-level user can query default FTP rights of all local users and domain
users who have logged in to FTP.
● A local non-administrator-level user can query default FTP rights of itself after logging in
to FTP.
● A domain user can query default FTP rights of domain users who have logged in to FTP.

BSC6910 UMTS
Table 3-5 Commands for setting FTP rights on executable programs or

configuration files
Function Command
Prohibiting all FTP users from SET

accessing executable programs or OMUPARA(FtpDirPermEnhcSw=FORBI
configuration files in the MBSC root DDEN)
directory
Allowing all FTP users to access SET

executable programs or configuration OMUPARA(FtpDirPermEnhcSw=NOT_F
files in the MBSC root directory ORBIDDEN)
● Setting FTP Directory Permission Enhancement Switch affects the default FTP rights of
different levels of accounts.
● Modifying FTP Directory Permission Enhancement Switch affects only new FTP connection
or new Web LMT user login.
3.5.2 Managing FTP Access Control Rules

The following table provides the commands for adding FTP access control rules to
different levels of users. Command execution results are shown in command
outputs.
Table 3-6 Commands for adding FTP access control rules
Function Command
Adding FTP access control rules to ADD

administrator-level users on a specified FTPACCCTRL(UsrLvl=Administrators,
path Object="XXX",AccessPermission=View)
Adding FTP access control rules to ADD FTPACCCTRL(UsrLvl=Operators,

operator-level users on a specified Object="XXX",
path AccessPermission=None)
Adding FTP access control rules to ADD FTPACCCTRL(UsrLvl=Users,

user-level users on a specified path Object="XXX",
AccessPermission=Download)
Adding FTP access control rules to ADD FTPACCCTRL(UsrLvl=Guests,

guest-level users on a specified path Object="XXX",
AccessPermission=Upload)
Adding FTP access control rules to ADD FTPACCCTRL(UsrLvl=Customs,

custom-level users on a specified path Object="XXX", AccessPermission=View)
Adding FTP access control rules to ADD

domain users on a specified path FTPACCCTRL(UsrLvl=DomainUser,
Object="XXX", AccessPermission=View)

BSC6910 UMTS
Function Command
Adding FTP access control rules to FTP ADD FTPACCCTRL(UsrLvl=FtpUsr,

users on a specified path Object="XXX", AccessPermission=View)
Table 3-7 Commands for removing FTP access control rules

Function Command
Removing FTP access control rules RMV

from administrator-level users on a FTPACCCTRL(UsrLvl=Administrators,
specified path Object="XXX")
Removing FTP access control rules RMV FTPACCCTRL(UsrLvl=Operators,

from operator-level users on a Object="XXX")
specified path
Removing FTP access control rules RMV FTPACCCTRL(UsrLvl=Users,

from user-level users on a specified Object="XXX")
path
Removing FTP access control rules RMV FTPACCCTRL(UsrLvl=Guests,

from guest-level users on a specified Object="XXX")
path
Removing FTP access control rules RMV FTPACCCTRL(UsrLvl=Customs,

from custom-level users on a specified Object="XXX")
path
Removing FTP access control rules RMV

from domain users on a specified path FTPACCCTRL(UsrLvl=DomainUser,
Object="XXX")
Removing FTP access control rules RMV FTPACCCTRL(UsrLvl=FtpUsr,

from FTP users on a specified path Object="XXX")
Table 3-8 Commands for querying FTP access control rules

Function Command
Querying FTP access control rules of LST

administrator-level users FTPACCCTRL(UsrLvl=Administrators)
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=Operators)

operator-level users
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=Users)

user-level users
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=Guests)

guest-level users

BSC6910 UMTS
Function Command
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=Customs)

custom-level users
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=DomainUser)

domain users
Querying FTP access control rules of LST FTPACCCTRL(UsrLvl=FtpUsr)

FTP users
Modifying FTP access control rules affects only new FTP connection or new Web LMT user login.

BSC6910 UMTS
LMT User Guide 4 Running MML Commands
4 Running MML Commands
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 presents an introduction to MML commands, components of the MML
command window, data configuration rights, and configuration rollback.
4.2 Running a Single MML Command
This section describes how to run a single MML command for routine
configuration and maintenance.
4.3 Batch Processing of MML Commands
This section describes how to run multiple MML commands simultaneously. Batch
processing of MML commands allows you to use a function or perform an
operation by running a prepared group of MML commands all at the same time.
4.4 Setting MML Parameters
This section describes how to set the MML parameters as required.
4.5 Querying Data Configuration Modes
This section describes how to query the data configuration mode of a BSC6910
system. The data configuration mode can be effective or non-effective.
4.6 Querying Data Configuration Rights
This section describes how to query the status of data configuration rights.
4.7 Obtaining Data Configuration Rights
This section describes how to obtain exclusive data configuration rights when you
plan to perform data configuration, undo/redo operations on the BSC6910, or
perform batch data configuration without being affected by other users. Only the
U2020 users and users of the following types can obtain these data configuration
rights: admin, ADMINISTRATOR-level users, OPERATOR-level users, and
CUSTOM-level users entitled to use command group G_3 (used for data
configuration).
4.8 Undoing/Redoing a Single Data Configuration Action
This section describes how to undo and redo a single data configuration action.
4.9 Undoing/Redoing Multiple Data Configuration Actions
This section describes how to undo and redo multiple data configuration actions
at a time.

BSC6910 UMTS
4.1 Concepts Related to MML Commands

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

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

BSC6910 UMTS
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.

BSC6910 UMTS
Figure 4-1 MML command window
Table 4-2 describes the components of the MML command window.
Table 4-2 MML command window

1 Common Displays system responses, such as command

Maintenance results. You can save command results and
(Alt+C) tab page automatically scroll through the command
results by clicking Start Save, Export, or Auto
Scroll, respectively. You can also clear all
command results by clicking Clear All.
NOTE
● The time information displayed at the beginning of
command results is the system time of the OMU.
● When you click Start Save, the system starts to
save command results of MML commands.
● When Start Save is selected, the MML command
output results are not cleared.
● The previous MML command output results are
overwritten after the upper storage threshold is
exceeded.
2 Operation Displays commands that have been run.

Record (Alt+R) NOTE
tab page The Send Time in an operation record is the system
time of the LMT PC.
3 Help Displays the help information of MML

Information (Alt commands.
+N) tab page

BSC6910 UMTS
4 Manual editing Displays manually input MML commands and

area their parameters.
5 History Displays all commands executed during the

Command field current login and relevant parameters.
6 Command Input Displays all the MML commands available on

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

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

To avoid data conflict, the OMU manages data configuration rights to allow only
one user to perform BSC6910 data configuration through the LMT or the U2020 at
any time.
Manage the OMU data configuration rights by following the steps provided in 4.7
Obtaining Data Configuration Rights
4.1.4 Data Configuration Rollback

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

During data configuration, a rollback point is used to mark a data configuration
status. You can run the ADD ROLLBACKPOINT command to manually configure
rollback points.
When data configuration rollback is required, you can select a rollback point to
restore the system to a specific configuration status as required.
Operations of Data Configuration Rollback

The following data configuration rollback operations are available:
● Undo a single configuration action

BSC6910 UMTS
● Redo a single configuration action

● Undo multiple configuration actions
● Redo multiple configuration actions
NOTICE
A user cannot perform data configuration rollback in any of the following cases:
● The user does not obtain the data configuration rights because another user
who has occupied exclusive data configuration rights does not release the
data configuration rights by running the ULK CMCTRL command.
● The quick configuration mode has been enabled by running the SET
QUICKCFG command.
● Batch configuration is performed by running the RUN BATCHFILE command.
4.2 Running a Single MML Command

This section describes how to run a single MML command for routine
configuration and maintenance.
Context
To run an MML command, you can:
● Enter an MML command in the Command Input field.
● Select a previously executed command from the History Command drop-
down list.
● Select an MML command from the MML Command navigation tree.
● Enter or Copy an MML command script to the Manual Editing area.
Procedure
● Entering an MML command in the Command Input field
a. Enter an MML command in the Command Input field. When you are
entering a command, related commands are displayed in a drop-down
list. You can select the required command from the drop-down list.
b. Press Enter or click Assist to display parameters associated with the
command.
c. Specify parameter values.
d. Press F9 or click Exec to run the command. The command result is
displayed on the Common Maintenance tab page.
● Selecting a previously executed command from the History Command drop-
down list
a. 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 to select the next command.)
b. (Optional) Change parameter values in the command parameter area.

BSC6910 UMTS
c. Press F9 or click Exec to run the command. The command result is

● Selecting an MML command from the MML Command navigation tree
a. Double-click an MML command in the MML Command navigation tree.
b. Specify parameter values.
c. Press F9 or click Exec to run the command. The command result is
● Parameters in red are mandatory. Those in black are optional.

● To obtain general information about a parameter, place the cursor on the input
box for the parameter.
● If the execution of a command fails, the command result displayed on the
Common Maintenance tab page is in red.
● Copying an MML command script to the Manual Edit area
a. Copy an MML command script with required parameter values and paste
it to the Manual Edit area.
b. Press F9 or click Exec to run the command. The command result is
----End
4.3 Batch Processing of MML Commands

This section describes how to run multiple MML commands simultaneously. Batch
processing of MML commands allows you to use a function or perform an
operation by running a prepared group of MML commands all at the same time.
Context
A batch file (also called data script file) is a plain text file, which contains a group
of command scripts used for conducting a specific task. The command scripts in a
batch file are executed in sequence.
The following two batch processing modes are available:
● Immediate batch processing:
A batch file is run immediately.
● Scheduled batch processing:
A batch file is automatically run at a specific time set by users in advance.
When the LMT locks its operation screen, the following commands will fail:
● ADD OP, RMV OP, and MOD OP
● SET OPLOCK
● SET OPSW
● SET PWDPOLICY
● ULK USR
● SET WEBLOGINPOLICY

BSC6910 UMTS
4.3.1 Immediate Batch Processing of MML Commands

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

Step 4 Click Go to run the commands.
You can set Execution Type. By default, Prompt when an error occurs is selected. You are
advised to retain the default setting.
----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
● 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. On the LMT main page, click Batch to access the Batch tab page in the
WebLMT dialog box that 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

BSC6910 UMTS
uploaded to the /bam/version_a/ftp directory in the OMU active work area.

When the active workspace of the OMU is version_a, the following path changes
into version_a. When the active workspace of the OMU is version_b, the
following path changes into version_b accordingly. There are the following two
upload ways:
● Through File Manager on the LMT
a. Start File Manager by referring to File Manager.
b. Choose Root > bam > version_a > ftp in the left area of the displayed
window to navigate to the ftp directory. Then click Upload.
c. 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.
● Through command lines
a. On a local LMT PC, choose Start > Run, enter cmd, and click OK.
b. Type the d: command and press Enter to switch the local disk to disk D.
c. Enter the ftp IP address command to apply for connection to the OMU. IP
address is the IP address of the OMU.
d. Enter the FTP user name and password. If the authentication passes, an
FTP connection is established between the local PC and the OMU.
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.
e. Enter the cd /bam/version_a/ftp command to switch to the directory of
OMU active work area.
f. Enter the put BATCHFILE.txt command to upload the file.
g. 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.
● 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;
● BATCHFILE.txt is the name of a batch file that needs to be run at a scheduled time and
saved in the ftp directory of the OMU active work area; result_add.txt is the name of the
result file.
----End
4.3.3 Syntax Check

This section describes how to check the syntax of MML commands before running
a group of MML commands. This function helps locate incorrect MML commands,
thereby improving maintenance efficiency.

BSC6910 UMTS
Prerequisites
● A batch file is available.
Context
The syntax check can locate the following errors:
● Missing colon
● Missing semicolon
● Incorrect MML command
● No authority to execute a correct MML command
● Redundant parameters
● Incorrect parameters
Procedure
Step 1 Click New to create a batch file and input MML commands in the manual editing
area.
You can click Open... to open a prepared batch file.

If an encrypted .ecf file is selected, enter the password of the file to import the file for
batch processing.
Step 2 Click Analyze Syntax to check the syntax of the batch file.
● If no errors occur, the Information dialog box is displayed, indicating that no syntactical
errors occur. If an error occurs, the Result dialog box is displayed, indicating a line
number for locating the error and error reasons for correcting the error.
● To go to the command line with a syntactical error, double-click the information in the
Result dialog box.
● After Analyze Syntax is executed, a mark is displayed in front of a command line

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

BSC6910 UMTS
4.4 Setting MML Parameters

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

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

This section describes how to query the data configuration mode of a BSC6910
system. The data configuration mode can be effective or non-effective.
Context
When a BSC6910 system is in effective mode, data configured for the BSC6910
system takes effect immediately.

BSC6910 UMTS
When a BSC6910 system is in non-effective mode:

● Data configured for the system takes effect only for the OMU but not on the
subrack.
To make the data configuration take effect on the subrack, perform the
following operations: Run the SET CFGDATAEFFECTIVE command to set the
data configuration mode to effective mode, run the FMT DATA command to
generate the data configuration file for the subrack, and then run the RST
SUBRACK command to reset the subrack. In this way, the subrack can load
the data configuration from the OMU so that the data takes effect on the
subrack.
● You cannot query, compare, or perform CRC check on the host and OMU data.
● You cannot configure the host data of the subrack.
● License verification is not performed.
When the BSC6910 system attempts to switch the data configuration mode
from the non-effective mode to the effective mode, the OMU checks whether
the data configuration exceeds the limitations of the license. If the data
configuration exceeds the limitations of the license, the mode switching will
fail.
You can use menus or MML commands to query the data configuration mode.
Procedure
● Using menus
a. On the LMT main page, check the configuration mode of the BSC6910
system, as shown in Figure 4-3.
Figure 4-3 Data configuration mode
● Using MML commands

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

This section describes how to query the status of data configuration rights.
Context
You can use menus or MML commands to query the status of data configuration
rights.

BSC6910 UMTS
Procedure
● Using menus
a. Check the status of data configuration rights displayed at the top right
corner of the LMT main page.
a. Run the LST CMCTRL command to query the status of data configuration
rights.
----End
4.7 Obtaining Data Configuration Rights

This section describes how to obtain exclusive data configuration rights when you
plan to perform data configuration, undo/redo operations on the BSC6910, or
perform batch data configuration without being affected by other users. Only the
U2020 users and users of the following types can obtain these data configuration
rights: admin, ADMINISTRATOR-level users, OPERATOR-level users, and
CUSTOM-level users entitled to use command group G_3 (used for data
configuration).
Prerequisites
● You have logged in to the LMT.
Context
● By default, all users have data configuration rights. They can use the LMT or
U2020 to configure data for the BSC6910.
● Only one user can use the data configuration rights at any given time. You
can run the LCK CMCTRL command to obtain exclusive data configuration
rights.
● After the data configuration is complete, you can run the ULK CMCTRL
command to make the data configuration rights available to all users so that
another user can run the LCK CMCTRL command obtain exclusive data
configuration rights.
● If a user who had exclusive data configuration rights exits from the LMT, the
data configuration rights will be automatically made available to all users. In
this case, another user can also run the LCK CMCTRL command to obtain
exclusive data configuration rights.
Procedure
Step 1 Check whether the data configuration rights are available. For details, see 4.6
Querying Data Configuration Rights.
● If no user has exclusive data configuration rights, go to Step 2.
● If a user has exclusive data configuration rights, once that user releases those
configuration rights, go to Step 2.
Step 2 Run the LCK CMCTRL command to obtain the data configuration rights.

BSC6910 UMTS
If an LMT user has exclusive data configuration rights of the BSC6910, other LMT users
cannot obtain the data configuration rights. In this case, user admin or ADMINISTRATOR-
level users can run the FOC CMCTRL command to forcibly release the locked data
configuration rights.
----End
4.8 Undoing/Redoing a Single Data Configuration

Action
This section describes how to undo and redo a single data configuration action.
Prerequisites
● You have obtained data configuration rights by running the LCK CMCTRL
command.
● The quick configuration mode has been disabled by running the SET
QUICKCFG command.
● No batch commands have been executed.
Context
● You can undo or redo a data configuration action to fine-tune data
configuration. These operations, however, can decrease the efficiency of
running MML commands. Therefore, when the quick configuration mode is
enabled or when batch MML commands are running, do not undo or redo
data configuration actions.
● To prevent data conflicts, a user can undo or redo a data configuration action
only if the user has obtained exclusive data configuration rights.
● Certain MML commands cannot be undone or redone. If you run such an
MML command, the Undo and Redo buttons on the top of the LMT window
becomes unavailable and configuration actions performed before running the
MML command also cannot be undone or redone. For a list of MML
commands that can be undone or redone, see the description of the ADD
ROLLBACKPOINT command.
● The most recent 10 effective single configuration actions can be undone one
at a time. Likewise, the 10 most recent undone operations can be redone in
the same manner.
Procedure
● Undoing a single configuration action
a. Use either of the following methods to undo the latest configuration
action:
▪ On the toolbar of the LMT, click Undo.
▪ Run the BEG UNDO command.

BSC6910 UMTS
b. To undo multiple configuration actions, repeat Step 1.

● Redoing a single configuration action
a. Use either of the following methods to redo an undone action:
▪ On the toolbar of the LMT, click Redo.
▪ Run the BEG REDO command.

b. To redo multiple configuration actions, repeat Step 1.
----End
4.9 Undoing/Redoing Multiple Data Configuration

Actions
This section describes how to undo and redo multiple data configuration actions
at a time.
Prerequisites
● You have obtained data configuration rights by running the LCK CMCTRL
command.
● The quick configuration mode has been disabled by running the SET
QUICKCFG command.
● No batch commands have been performed.
Context
● You can undo or redo multiple data configuration actions simultaneously to
fine-tune data configuration. These operations, however, can decrease the
efficiency of running MML commands. Therefore, when the quick
configuration mode is enabled or when batch MML commands are running,
do not undo or redo multiple data configuration actions.
● To prevent data conflicts, a user can undo or redo multiple data configuration
actions simultaneously only if the user has exclusive data configuration rights.
● Certain MML commands do not support undoing or redoing multiple data
configuration actions at a time. If you run such MML commands, the rollback
point specified by running the ADD ROLLBACKPOINT command will become
invalid and undoing multiple data configuration actions at a time will fail.
Therefore, before running such MML commands, remove the configured
rollback point. For a list of MML commands that support undoing or redoing
multiple configuration actions, see the description of the ADD
ROLLBACKPOINT command.
● Multiple configuration actions can be undone simultaneously. After a multiple
undo operation is applied, the system is restored based on the configuration
status from a specified rollback point.
● Multiple configuration actions can be redone simultaneously. After the
multiple actions have been redone, the system is restored based on either the
configuration status at the specified rollback point or the final configuration
status from before undoing the configuration actions.

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

BSC6910 UMTS
LMT User Guide 5 Alarm/Event Management
5 Alarm/Event Management
This section describes how to use the LMT to manage BSC6910 alarms/events.
Alarm/event management helps you analyze alarms/events efficiently, thereby
facilitating troubleshooting.
5.1 Concepts Related to Alarm Management

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

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

BSC6910 UMTS
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 alarm types.
Table 5-1 Fault alarms and event alarms
Alarm Type Description
Fault alarm Fault alarms are caused by hardware faults or failures of major
functions, for example, board fault or link fault. Fault alarms
are of higher severity than event alarms and are classified into
active and cleared alarms according to the fault status.
Event alarm Event alarms record predefined events occurring during the
operation of the system. An event alarm reflects the system
condition (for example, congestion) at a specific time, which is
not necessarily a fault. Some event alarms are generated
repeatedly and regularly.
According to fault status, fault alarms are classified into:

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

Four alarm severities are available for fault alarms and event alarms of the
BSC6910: critical, major, minor, and warning.
Table 5-2 describes the four alarm severities.

BSC6910 UMTS
Table 5-2 Alarm severities
Alarm Definition Handling

Severity Requirement
Critical Alarms of this severity are triggered by Handle the faults

faults that affect services provided by the immediately to
system and must be handled immediately avoid service
even during non-working hours. For outage.
example, some devices break down or
some resources become unavailable.
Major Alarms of this severity are triggered by Handle the faults

faults that affect the Quality of Service in time. to avoid
(QoS) and must be handled. For example, failures of major
the performance of some devices or functions.
resources deteriorates.
Minor Alarms of this severity are triggered by Identify and

faults that are not serious enough to rectify potential
affect the QoS. These alarms can be faults in time.
handled as required or further observed to
prevent them from becoming critical. For
example, you need to clear obsolete
historical alarms regularly.
Warning Alarms of this severity are triggered by Learn the

faults that are potential threats to the operating status
system services. These alarms need to be of the system
handled according to specific situations. from warning
For example, the OMU startup alarm is a alarms and
warning. resolve problems
as required.
5.1.3 Alarm-Event Type

Alarms can be classified into 15 types based on event types.
● 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

BSC6910 UMTS
● 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
● 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 theBSC6910 alarm flags, including: to-alarm-box flag, shield flag,
modification flag, and alarm cleared flag.
To-Alarm-Box Flag
The to-alarm-box flag controls whether alarms are reported to the alarm box. This
flag can be set to either of the following values:
● Report
When alarms are generated, they are reported to the alarm box, which
provides audible and visual indications for the alarms.
● Not report
When alarms are generated or when the alarm status changes, the alarms
and the change of alarm status are not reported to the alarm box.
The to-alarm-box flag is applicable only to fault alarms. Event alarms are not reported to
the alarm box.
Whether an alarm is reported to the alarm box depends on the to-alarm-box flag
of the alarm and the alarm suppression level of the alarm box. Alarms are

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

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

BSC6910 uses Huawei universal alarm box, which provides audible and visual
indications for the BSC6910 alarms. The alarm box is optional and the BSC6910
can be equipped with only one alarm box. For details, see the documents
delivered with the alarm box.
Figure 5-1 shows the alarm box.

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

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

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

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

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

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

This section describes how to create an alarm masking condition. Only user
admin, OPERATOR-level users, ADMINISTRATOR-level users, and authorized
CUSTOM-level users can perform this operation.
Prerequisites
Procedure
Step 1 Run the ADD OBJALMSHLD command to create an alarm masking condition. The
alarm masking condition successfully created takes effect immediately.
● The name of a new alarm masking condition must be unique. Otherwise, the alarm
masking condition cannot be created.
● A maximum of 100 alarm masking conditions can be created for each BSC6910.
Step 2 Run the LST OBJALMSHLD command and enter required parameters to query
whether the alarm masking condition is successfully created.
----End

BSC6910 UMTS
5.3.2 Deleting an Alarm Masking Condition

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

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

Alarms
When a fault occurs, beside a fault alarm, some related alarms may be generated.
These alarms are termed derived alarms. The BSC6910 can mask derived alarms.
By default, derived alarms are not reported to the LMT. Unless otherwise specified,
derived alarms are not stored on the OMU and cannot be queried.
5.4.1 Enabling/Disabling the Alarm Masking Switch of Derived

Alarms
This section describes how to enable and disable the alarm masking switch of the
BSC6910 derived alarms. You can enable the alarm masking switch by setting it to

BSC6910 UMTS
ON and disable the alarm masking switch by setting it to OFF. Only user admin,
OPERATOR-level users, ADMINISTRATOR-level users, and authorized CUSTOM-
level users can perform this operation.
Prerequisites
● You have logged in to the LMT with an authorized account.
● You have obtained the data configuration rights (see 4.7 Obtaining Data
Configuration Rights).
Procedure
Step 1 Run the SET ALMML command to enable or disable the alarm masking switch of
derived alarms.
----End
5.4.2 Querying the Alarm Masking Switch of Derived Alarms

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

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

This section describes how to use the LMT to browse fault alarms and event
alarms. Fault alarms and event alarms are displayed on the Browse Alarm/Event
tab page of the Alarm/Event window. By browsing alarm information, you can
learn the operating status of the system in real time.
Prerequisites
You have logged in to the LMT.
Procedure
Step 1 On the LMT main page, click Alarm/Event. The Browse Alarm/Event tab page is
displayed. The Normal Alarm, Event, and Maintenance mode alarm tab pages
are displayed under the Browse Alarm/Event tab.

BSC6910 UMTS
Step 2 Browse alarms on the Browse Alarm/Event tab page.

Step 3 To view details of an alarm, double-click it. The Detail dialog box is displayed,
presenting detailed information about the alarm.
Step 4 To save an alarm record, select the alarm record, right-click it, and choose Save
Selected from the shortcut menu. To save all alarm records, right-click any place
in the area where alarms are displayed and choose Save All from the shortcut
menu; or click Save All.
----End
5.5.2 Querying Alarm/Event Logs

This section describes how to query alarm and event logs from the OMU
database. By viewing alarm and event logs, you can learn the past operating
status of the system.
Context
You can set the following query criteria:
● Alarm type
● Alarm severity
● Alarm time
● Filtering criteria
● Maintenance mode flag
● Number of logs to be queried
● Cleared time
● NodeB type
● Alarm-managed objects
● Alarm ID
● Alarm serial No.
Procedure
● Using menus
a. On the LMT main page, click Alarm/Event. The Browse Alarm/Event tab
page is displayed.
b. On the Query Alarm/Event Log tab page, click Query Settings. The
Query Settings dialog box is displayed.
c. Set query criteria as required. To reset the query criteria, click Reset. To
reset only the NodeB type, select Filter By NodeB.
After performing query by Filter By NodeB, you can click Filter to reset query
criteria.
d. Click Query. The query result is displayed in the Result area.
e. To view details of an alarm, double-click it. The Detail dialog box is
displayed, presenting detailed information about the alarm.

BSC6910 UMTS
f. To save an alarm record, select the alarm record, right-click it, and choose
Save Selected from the shortcut menu. To save all alarm records, right-
click any place in the area where alarms are displayed and choose Save
All from the shortcut menu; or click Save All.
You can drag rows on the Query Alarm/Event Log tab page to rearrange the
row order. Within a Cookie validity period, the row order on the Query Alarm/
Event Log tab page is the same as the row order when you closed the tab page
last time.
a. Run the LST ALMLOG command to query alarm logs.
----End
5.5.3 Querying Suggestions on Alarm/Event Handling

This section describes how to query suggestions on handling an alarm.
Context
The LMT provides the following help information about alarms:
● Alarm/event description
● Impact on the system
● System actions
● Handling suggestions
Procedure
Step 1 On the Alarm/Event tab page, double-click an alarm on the Browse Alarm/Event
or Query Alarm/Event Log tab page. The Detail dialog box is displayed.
Step 2 In the Detail dialog box, click Solution.... The online help window is displayed.
You can also select an alarm, right-click it, and choose Solution from the shortcut menu to
view the online help of this alarm.
Step 3 View the handling suggestions or other required information in the online help.
Step 4 To exit from the online help, close the online help window.
----End
5.5.4 Querying Alarm/Event Configuration

This section describes how to query alarm/event configuration.
Context
You can set the following query criteria:
● ID:
Specifies Start ID and End ID of alarms/events whose configuration
information is to be queried.

BSC6910 UMTS
● Severity:
Specifies the alarm severity of alarms/events whose configuration
information is to be queried.
● Modification Flag:
Specifies the modification flag of alarms/events whose configuration
information is to be queried. If All is selected, configuration information of
alarms/events whose Modification Flag is set to Unmodified or Modified is
displayed in the query result.
● Shield Flag:
Specifies the shield flag of alarms/events whose configuration information is
to be queried. If All is selected, configuration information of alarms/events
whose Shield Flag is set to Shielded or Unshielded is displayed in the query
result.
● To Alarm Box Flag:
Specifies the to-alarm-box flag of alarms/events whose configuration
information is to be queried. If All is selected, configuration information of
alarms/events whose To Alarm Box Flag is set to Report or Not Report is
displayed in the query result.
● Return Amount:
Specifies the number of alarms whose configuration information is to be
queried.
Procedure
Step 1 On the LMT main page, click Alarm/Event. The Alarm/Event tab page is
displayed.
Step 2 Click the Query Alarm/Event Configuration tab and click Query Settings. The
Query Settings dialog box is displayed.
Step 3 Set query criteria as required.
Step 4 Click Query. The query result is displayed in the Result area.
To modify the configuration of an alarm, select an alarm and click Modify Configuration,
or right-click the alarm in the Result area and choose Modify Configuration from the
shortcut menu.
----End
5.5.5 Filtering Alarms/Events

This section describes how to filter alarms according to specified filtering criteria,
such as sites and alarm types. Alarms filtered out are still reported to the LMT and
saved on the OMU, but not displayed on the Browse Alarm/Event tab page.
Prerequisites
You have logged in to the LMT.

BSC6910 UMTS
Procedure
displayed.
Step 2 On the Browse Alarm/Event tab page, click Filter Settings. The Filter Settings
dialog box is displayed.
Step 3 In the Filter Settings dialog box, specify filtering criteria, such as Alarm Source
and Alarm ID. Then, click OK. Alarms meeting the specified criteria are displayed.
● You can select BSC and NodeB for Alarm Source Type. When you select NodeB for Alarm
Source Type, alarms related to the NodeB are displayed in the filtering result. These alarms
are not generated by the NodeB but the RNC.
● When you specify Alarm Source Type, all alarm sources of the selected type are displayed in
the alarm source type area.
● You can select Alarm Source Type and then enter the alarm source under Alarm Source.
The input box under Alarm Source supports association display. For example, if you enter 3,
all alarm sources whose names start with 3 are displayed.
----End
5.5.6 Setting Display Attributes for Alarms/Events

This section describes how to set display attributes for alarms/events in the
Setting dialog box. After you set the display attributes, the settings take effect on
alarms/events on the following tab pages: Browse Alarm/Event, Query Alarm/
Event Log, and Query Alarm/Event Configuration.
Context
You can set the following display attributes for alarms/events:
● Colors
● Table columns
● Display tips
Procedure
displayed.
Step 2 Click Settings on the upper right of the Alarm/Event tab page. The Settings
Step 3 In the Settings dialog box, set Color, Table Columns, Auto-deletion, and Tips.
● Color:
You can set background colors for the following alarm/event types: Critical,
Major, Minor, Warning, and Cleared.
● Auto-deletion:
You can select Enable auto-deletion and specify the period for automatic
deletion of cleared alarms.

BSC6910 UMTS
● Tips:
Two options are available: Enable and Disable. If you select Enable, details
about an alarm/event are displayed when you put the cursor on the alarm/
event. If you select Disable, details about an alarm/event are displayed only
when you double-click the alarm/event.
● Table Columns:
You can specify the information to be displayed in the alarm/event table. The
following table describes all fields for an alarm.
Field Description
Name
Serial No. Specifies the alarm generating sequence. This field identifies
an alarm record in an alarm log.
ID Specifies the alarm ID. For a product, this field identifies an

alarm.
Name Specifies the alarm name. For a product, this field identifies an
alarm and has a one-to-one mapping relationship with the
alarm ID.
Severity Specifies the severity of the alarm on services.
Event Specifies the event type of the alarm.

Type
Alarm Specifies the network element that generates the alarm.

Source
Type Specifies that the alarm is an Alarm or Event.
Maintena Specifies whether the alarm is triggered by maintenance and

nce Mode engineering operations, such as capacity expansion or
Flag upgrades.
Raised Specifies the time when the alarm is generated.

Time
Changed Specifies the time when Severity of the alarm or Serial No. of
Time the root alarm is changed.
Cleared Specifies the time when the alarm is cleared.

Time
Common Specifies whether the alarm is generated by a common

component.
NOTE
A multi-mode product comprises common components, such as power
supply and temperature control devices. Alarms generated by these
common components are termed common alarms.
Special Specifies whether special information is reported.

Info

BSC6910 UMTS
Field Description
Name
Location Specifies information required for locating faults.

Info
Root CSN Specifies the serial number of the root alarm.
Cleared Specifies the way in which the alarm is cleared. Alarms can be
Type cleared in any of the following ways:
– Normal clear:
Alarms are normally cleared.
– Reset clear:
After the system is restarted, alarms are automatically
cleared.
– Manual clear:
Alarms are manually cleared.
– Configuration clear:
After the configuration of a board is deleted, alarms related
to the board are automatically cleared.
– Correlation clear:
After receiving the root alarm of an active alarm, the fault
management system reports the root alarm and
automatically clears the active alarm.
– Override clear:
Earliest alarms are removed to free disk space. If some
earliest alarms are still active, they are automatically
cleared.
– State switchover clear:
If a device switches from one state to another, the active
alarm reported by the device in the former state is
automatically cleared. The device in the latter state reports
the alarm again.
Sync Specifies the sequence for sending alarm report messages. The
Serial No. synchronization serial number ensures data synchronization
between the element management system (EMS) and network
elements (NEs). The alarm generating message and alarm
clearing message have different synchronization serial
numbers.
----End
5.5.7 Manually Clearing an Alarm/Event

When an alarm can be neglected or the fault triggering the alarm has been
rectified, you can manually clear the alarm. This section describes how to clear an
alarm/event. Only user admin, OPERATOR-level users, ADMINISTRATOR-level
users, and authorized CUSTOM-level users can perform this operation.

BSC6910 UMTS
Prerequisites
Context
You can clear an alarm/event using menus or MML commands.
Procedure
● Using menus
a. On the LMT main page, click Alarm/Event and select an active alarm to
be cleared on the Browse Alarm/Event or Query Alarm/Event Log tab
page. Click Clear Alarm. The Confirm dialog box is displayed.
b. Click OK in the Confirm dialog box. Manually cleared is displayed in the
Cleared Type column.
You can also right-click an alarm to be cleared and choose Clear Alarm from the shortcut
menu.
a. Run the RMV ALMFLT command to manually clear an alarm.
----End
5.5.8 Deleting Alarms/Events

This section describes how to delete cleared alarms/events.
Procedure
Step 1 On the Browse Alarm/Event or Query Alarm/Event Log tab page under the
Alarm/Event tab, click Delete Selected Cleared Alarms or Delete All Cleared
Alarms to delete the alarms/events as required. Table 5-3 describes the functions
of the buttons.
Table 5-3 Functions of the buttons
Button Description
Delete Selected Deletes cleared alarms that are selected in the active
Cleared Alarms window. This button is available on the Browse Alarm/
Event and Query Alarm/Event Log tab pages.
Delete All Cleared Deletes all cleared alarms that are displayed in the
Alarms active window. This button is available on the Browse
Alarm/Event and Query Alarm/Event Log tab pages.
----End

BSC6910 UMTS
5.5.9 Refreshing the Alarm/Event Window

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

The BSC6910 uses Huawei universal alarm box to provide audible and visual
indications when an alarm is reported. The alarm box notifies maintenance
engineers of alarms in time, thereby facilitating operation and maintenance.
5.6.1 Querying Alarm Box Information

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

This section describes how to query the number of alarms of a specific severity.

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

This section describes how to reset the alarm box, turn off the alarm LEDs, and
stop the alarm sound.
Prerequisites
Procedure
● 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.
----End
5.6.4 Querying the Alarm Suppression Level of the Alarm Box

This section describes how to query and set the alarm suppression level of the
alarm box. Only alarms of a severity equal to or higher than the alarm
suppression level are reported to the alarm box.
Prerequisites
Context
Only user admin, OPERATOR-level users, ADMINISTRATOR-level users, and
authorized CUSTOM-level users are authorized to set the alarm suppression level.

BSC6910 UMTS
Procedure
● Run the LST ALMSCRN command to query the alarm suppression of the
alarm box.
● Run the SET ALMSCRN command to set the alarm suppression of the alarm
box.
----End

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

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

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

This section describes how to query operation and security logs of the BSC6910
from the OMU database.
Procedure
Step 1 Run the LST OPTLOG command and set query criteria as required to query
operation logs.

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

This section describes how to export operation logs and security logs from the
OMU to the directory OMU active workspace installation directory\ftp
\operator_log\exp_log and use the File Manager or FTP Client tool to download
the logs to the LMT PC.
Prerequisites
● You have logged in to the LMT with an ADMINISTRATOR-level account
authorized to perform this operation.
● You are authorized to download files from the OMU to the LMT PC.
Procedure
● Using the File Manager
a. Run the EXP LOG command, set Log Type to OPTLOG(Operation Log)
or SECLOG(SECURITY LOG), and set other parameters as required.
The default path for saving the exported log is OMU active workspace installation
directory\ftp\operator_log\exp_log on the active workspace of the OMU.
b. On the LMT main page, click File Manager to start the File Manager.
c. In the File Navigation Area, type OMU active workspace installation
directory\ftp. In the File List Area, select the operation log exported in a.
Then, click Download to download the log to the LMT PC.
● Using the FTP Client
a. Run the EXP LOG command, set Log Type to OPTLOG(Operation Log)
or SECLOG(SECURITY LOG), and set other parameters as required.
The default path for saving the exported log is OMU active workspace installation
directory\FTP on the OMU active workspace.
b. Choose Start > All Programs > Huawei Local Maintenance Terminal >
FTP Client. The FTP Client is started.
c. 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.

BSC6910 UMTS
The FTP user name and password are set when the OMU is being installed. By
default, the FTP user name is FtpUsr.
d. Click Enter to connect to the OMU. The connection status is displayed in
the Connection tips pane.
e. When the connection is successful, double-click OMU active workspace
installation directory\ftp in the server file list. Files in the directory are
displayed in the server file list pane.
f. Double-click the file to download it to the LMT PC.
g. When the file is successfully downloaded, choose System > Exit on the
FTP Client or close the FTP Client window to exit from the FTP Client.
----End
6.5 Obtaining Running Logs

This section describes how to upload running logs to the directory bam\common
\fam\famlog and use the File Manager or FTP Client to download the running logs
to the LMT PC.
Context
● Running logs are named in the format BSCID_subrack number/Log/
yyyy/mm/dd/hh/mm/ss.zip. For example, if a running log of Extended
Processing Subrack (EPS) 3 is uploaded to the OMU of BSC 1 at 17:19:47 of
November 7, 2011, the log is named BSC0001_03Log20111107171947.zip.
BSC0001_03Log20111107171947.zip indicates that the log has been
successfully uploaded and compressed.
BSC0001_03Log20111107171947.tmp indicates that the log is being
uploaded.
● By default, running logs are uploaded to and saved in the directory bam
\common\fam\famlog on the OMU.
Procedure
● Using the File Manager
a. Run the ULD LOGTOOMU command and enter the number of the
subrack whose running log is to be uploaded to the OMU.
b. On the LMT main page, click File Manager to start the File Manager.
c. In the File Navigation Area, double-click bam\common\fam\famlog. In
the File List Area, select the running log uploaded in Step 1. Then, click
Download to download the log to the LMT PC.
● Using the FTP Client
a. Run the ULD LOGTOOMU command and enter the subrack number to
upload the corresponding running log to the OMU.
b. Choose Start > All Programs > Huawei Local Maintenance Terminal >
FTP Client. The FTP Client is started.
c. 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.

BSC6910 UMTS
The FTP user name and password are set when the OMU is being installed. By
default, the FTP user name is FtpUsr.
d. Click Enter to connect to the OMU. The connection status is displayed in
the Connection tips pane.
e. When the connection is set up successfully, double-click bam\common
\fam\famlog in the server file list. Files in the path are displayed in the
server file list pane.
f. Double-click the running log to download it to the LMT PC.
g. When the running log is successfully downloaded, choose System > Exit
or close the FTP Client window to exit from the FTP Client.
----End
6.6 Collecting Logs

This section describes how to collect logs for fault analysis. There are several types
of logs, such as host logs, OMU logs, database logs, system event logs, operation
logs, OMU installation logs, remote upgrade logs, security logs, and alarm logs.
Procedure
Step 1 Run the COL LOG command and set parameters as required to collect logs. For
more description about logs, see Table 6-1.
● The path for saving logs depends on the active workspace of the OMU. When the active
workspace of the OMU is version_a, the path for saving logs is version_a. When the active
workspace of the OMU is version_b, the path for saving logs is version_b.
● Log files that are not compressed into the BZ2 format in the OMU active workspace
installation directory\common\fam\famlog and the OMU active workspace installation
directory\common\fam\famlogfmt directories will not be collected.
Table 6-1 Description about logs
Type File Path Description
PFM_NOM_RESULT(Nor /bam/version_a/ftp/ Records normal-period

mal Performance Result COLLOGINFO/PFM-LOG/ traffic statistics that an
File) NE reports to the U2020.
Used for analyzing traffic
statistics.
PFM_RESULT(Performanc /bam/version_a/ftp/ Records traffic statistics

e Result File) COLLOGINFO/PFM-LOG/ that an NE reports to the
U2020.
statistics.

BSC6910 UMTS
HOST_PFM_RESULT(Perf /bam/version_a/ftp/ Records traffic statistics

ormance Result File from COLLOGINFO/PFM-LOG/ that boards report to the
Host) OMU.
statistics.
ACTIVE_DEF_MEAS_FILE( /bam/version_a/ftp/ Specifies the active

Active Default COLLOGINFO/PFM-LOG/ traffic statistic definition
Measurement Task File) file that the U2020
delivers to NEs.
statistics.
STANDBY_DEF_MEAS_FIL /bam/version_a/ftp/ Specifies the standby

E(Standby Default COLLOGINFO/PFM-LOG/ traffic statistic definition
Measurement Task File) file that the U2020
delivers to NEs.
statistics.
PFM_SWITCHS(Switch / Records reserved

Information for enumerated values.
Performance)
HISTORY_ALARM(History /bam/version_a/ftp/ Records alarms and

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

Fault File) COLLOGINFO/ALM-LOG/ by all NEs.
Used for analyzing
alarms and events.
ALM_SYSTEM_CFG(The /bam/version_a/ftp/ Records the

Configured Information COLLOGINFO/ALM-LOG/ configuration
of Alarm) information related to
alarm management.
Used for analyzing
alarms and events.
SECURITY_LOG(Security /bam/version_a/ftp/ Specifies security logs of

Logs) COLLOGINFO/SEC-LOG/ an NE.
Used for analyzing
security-related
OPT_LOG(Operation /bam/version_a/ftp/ Records operation logs

Logs) COLLOGINFO/OPT-LOG/ of an NE.
Used for analyzing user

BSC6910 UMTS
OMU_LOG(The Log ● Independent Records all running logs

Information of OMU) Mode: /bam/ and status information
version_a/ftp/ of the OMU board.
COLLOGINFO/ Used for analyzing OMU
SINGLE-BAM/ faults and status.
● 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 ● Independent Records the running logs

Simple Log of OMU) Mode: /bam/ and status information
version_a/ftp/ of the OMU board,
COLLOGINFO/ except information about
SINGLE-SIM-BAM/ scheduled tasks and the
● Active/Standby Mode standby workspace.
– Active OMU
/bam/
version_a/ftp/
COLLOGINFO/
Active-SIM-BAM/
– Standby OMU
/bam/
version_a/ftp/
COLLOGINFO/
STANDBY-SIM-
BAM/
BSC_CFG_MML(The Data /bam/version_a/ftp/ Records the BSC

Configure File of the COLLOGINFO/CFG-LOG/ configuration data.
BSC) ExportCfgmml/ Used for configuration
data restoration.
BSC_DYNAMIC_CFG_INF /bam/version_a/ftp/ Records the dynamic

O (Dynamic COLLOGINFO/CFG-LOG/ mapping relationships
Configuration BSCDynaCFGInfo/ between cell IDs and
Information of the BSC) internal cell IDs, between
cells, base stations, links,
process and the
corresponding
subsystems.

BSC6910 UMTS
BSC_SERIES_NO(The /bam/version_a/ftp/ Records the Equipment

Series No. of the BSC) COLLOGINFO/CFG-LOG/ Serial Number (ESN) of
a BSC.
Used for checking the
license validity.
DB_BAK(The Backup File /bam/version_a/ftp/ Records backed up OMU

of the Database) COLLOGINFO/CFG-LOG/ database information.
MysqlDbBak/ Used for data
restoration.
TRANSIPROUTE_LOG(Th /bam/common/fam/ Records transmission IP

e Transmission IP Route famlogfmt/transiproute route logs for base
Log) stations to help analyze
base station
disconnections.
DEBUG_LOG(The /bam/common/fam/ Records software

Common Debug Log) famlogfmt/ running errors.
Used for analyzing
software defects.
SDBG_LOG(The Channel /bam/common/fam/ Records channel faults.

Fault Log) famlogfmt/
UP_DEBUG_LOG(The /bam/common/fam/ Records UP debug logs.

Debug Log of UP) famlogfmt/ Used for locating UP
faults.
LAST_WORD(The Last /bam/common/fam Records the log

Word Log) information generated
before unexpected board
resetting.
Used for locating causes
of unexpected board
resetting.
HOST_LOG(The Running /bam/common/fam/ Records host operation

Log of the Host) famlog/ logs.
3G_CHR_LOG(The CHR /bam/common/fam/ Records call faults,

Log for UMTS) famlogfmt/ except call access failures
and call drops.
of soft handover, hard
handover, relocation, or
cell update failures.

BSC6910 UMTS
BSC_INFO(The Basic /bam/version_a/ftp/ Records the BSC

Information of the BSC) COLLOGINFO/BSC-LOG/ 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/ Records errors that occur

famlogfmt/ during the BIOS system
running.
Used for locating BIOS
faults.
CALLFAULT_LOG(CALLFA /bam/common/fam/ Records call access

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

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

T Log) famlogfmt/sysfault/ hardware faults such as
resource leakages and
device faults.
Used for checking
network health status.
----End

BSC6910 UMTS
LMT User Guide 7 Trace Management
7 Trace Management
This chapter describes how to manage message tracing on the BSC6910. A

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

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

BSC6910 UMTS
Principles of Message Tracing

Figure 7-1 shows the principles of message tracing.
Figure 7-1 Principles of message tracing
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.
Procedure for Closing a Tracing Task

1. When you close a tracing task on the LMT, the LMT sends a binary command
to the OMU to delete the task.
2. The OMU forwards the command to the specified board according to the task
ID.
3. The debugging module and service module delete the task from the filter
table.
Procedure for the Service Module to Report Traced Messages to the LMT
1. The service module compares the collected messages against the local filter
table and reports the qualified messages to the OMU.
2. The OMU forwards the traced messages to the LMT that creates the task
according to the task ID.
3. The LMT parses the messages and displays them on the tracing window.
7.1.2 Management of Tracing Operation Rights

You must have the required rights to perform message tracing operations.

BSC6910 UMTS
The users at the following levels can perform the tracing tasks online: admin,
USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command
group G_10.
That is, only the GUEST-level users and CUSTOM-level users who are not entitled
to use command group G_10 cannot perform tracing tasks online.
Group G_10 consists of binary commands for creating tracing and monitoring tasks.
Only G_1 command group users (ADMINISTRATOR and CUSTOM users with G_1 command
group permission) are allowed to perform a single-user CS tracing task.
Only G_1 command group users (ADMINISTRATOR and CUSTOM users with G_1 command
group permission) are allowed to perform a single-user PS tracing task.
7.1.3 Tracing Mode

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

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

This section describes the tracing specifications.
● A maximum of 64 trace tasks can be started simultaneously on the same LMT.

● Do not start excessive tracing tasks in heavy traffic scenarios, because starting
excessive tracing tasks slows the LMT responses. In this case, set Trace Mode
to Save To OMU before starting a tracing task.
● The following table lists the maximum number of tracing tasks that can be
simultaneously started for each type.

BSC6910 UMTS
Trace Type Specifications
Iu Interface Trace 6
Iupc Interface Trace 6
Iur Interface Trace 6
Iub Interface Trace 6
Uu Interface Trace 6
MNCDT Trace 3
Iur-p Trace 6
Cell Trace 6
IOS Trace 2
NOTE
A maximum of 100 calls can be traced in all tasks.
UE Trace 12
NOTE
A maximum of six tasks in the debug mode can be
performed simultaneously.
Sr Interface Trace 6
7.2 Basic Tracing Operations

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

This section describes how to browse traced messages online in a message
browser of the WebLMT after a tracing task is created.
Prerequisites
● A tracing task is successfully created.
● Traced messages are reported.
Context
● By default, each message browser is displayed in maximized mode. To
compare results displayed in multiple message browsers, set Layout to
Cascade, Tile Horizontal or Tile Vertical.
Each of the windows is configured with a default minimum width when
multiple windows are tiled vertically. This ensures clear comparison. With this
configuration, a maximum of six windows can be displayed in a monitor with
the resolution of 1280x1024. Other windows are hidden behind the displayed
windows.

BSC6910 UMTS
The cascaded or tiled window arrangements take effect only at every setting
of Layout to Cascade, Tile Horizontal, or Tile Vertical. After such a setting,
a new message browser will still be displayed in maximized mode.
● A maximum of 2000 messages can be displayed in a message browser. Newly
traced messages will replace old ones if 2000 messages are already displayed
in a message browser.
Procedure
Step 1 Browse or view traced messages in a message browser in real time. Right-click in
the message browser and choose an item from the shortcut menu to perform the
associated operation as described in Table 7-1.
Table 7-1 Operations available when browsing traced messages online
Shortcut Description
Stop Trace Task Suspend the tracing task.
Restart Trace Task Resume the suspended tracing task.
Save All Messages Save all traced messages displayed in the message
browser.
Save Selected Messages Save the selected messages.
Auto Scroll Enable messages in the message browser to

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

browser without affecting the saved messages.
Property Query properties of the tracing task.
Step 2 To view details of a message, double-click it. The Message Browser window is
displayed, showing details of the message.
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.2.2 Viewing the Interpretation of Traced Messages

This section describes how to view the interpretation of a traced message in the
message browser of the WebLMT.
Prerequisites

BSC6910 UMTS
Procedure
Step 1 In the message browser of the WebLMT, double-click the trace message.
Step 2 The Message Browser window is displayed, showing the details and meaning of
the message in protocol translation format, as shown in Figure 7-2.
Figure 7-2 Message Explanation
----End
7.2.3 Saving Traced Messages

This section describes how to save traced messages in a file to a local PC.
Prerequisites
● A tracing task is started.
Context
The name of the file containing saved messages cannot exceed 100 characters,
including the file name extension.
The traced results can be saved either automatically or manually.

BSC6910 UMTS
Procedure
● Automatic saving of traced messages
Select Save File when creating a tracing task. All traced messages to be
displayed in the message browser will be automatically saved in .tmf format.
The default save path is C:\Web LMT\MBSC\output\trace\tmfFile on the

local PC.
● 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.
● The file saving messages traced by a UE tracing task are named in a different
way from the file saving messages traced by other types of tracing task. The last
four digits of the traced number (IMSI, TMSI, IMEI, or MSISDN) are saved in the
file name. If there are fewer than four digits, use the digits in the file name
without adding more digits to reach four digits. For example, if the least
significant four digits of a UE IMSI are 1234, messages traced by a UE tracing
task of this UE are saved in a file named UE_YYYY-MM-DD-HH-MM-
SS-1234_Serial number.tmf.
● You can use the Traffic Recording Review Tool to browse messages saved in .tmf
format offline. For details, see 7.2.4 Browsing Traced Messages Offline.
● Manual saving of traced messages
When a tracing task is running, you can manually save all or some of the
messages in the message browser in .tmf, .txt, or .csv format.
a. To save all messages, right-click in the message browser and choose Save
All Messages from the shortcut menu. To save only the selected
messages displayed in the message browser, select the messages you
wish to save, right-click, and choose Save Selected Messages from the
shortcut menu. The Save dialog box is displayed.
b. Enter a file name, and specify the file type.
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.
On the toolbar of the LMT main window, click System Settings to change the
save path of the file.
c. Click Save to save the file in the specified path.
----End
7.2.4 Browsing Traced Messages Offline

This section describes how to use the Traffic Recording Review Tool to browse
offline the traced messages that are saved in .tmf format.

BSC6910 UMTS
Prerequisites
The traced messages are saved in .tmf format.
Context
You can find the .txt or .csv files in the saved directory. Double-click them to view
the traced messages.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal >
TrafficRecording Review Tool.
Step 2 The Open dialog box is displayed, prompting you to select the target file. Browse
to the folder where the trace files are saved, and select the target file.
Step 3 Click Open or double-click the file. The contents of the file are displayed in the
TrafficRecording Review Tool window.
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 All the messages are saved in the
the shortcut menu, window in .tmf or .txt format.
You choose Save Selected Messages The selected messages are saved
from the shortcut menu, in .tmf or .txt format.
You choose Filter By Byte from the Set the filter to selectively display the
shortcut menu, information.
You choose Filter By Column from the Filter the information by column to
shortcut menu, selectively display the information.
You choose Find from the shortcut Locate the message that you want.
menu,
During multi-user tracing or inter-RNC tracing, the order in which messages traced in real time
are displayed may be inaccurate because those messages are reported by multiple nodes in the
system at the same time. You can click the Time column to sort the messages by the time when
the RNC receives the messages.
----End

BSC6910 UMTS
7.2.5 Managing Tracing Tasks

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

This section describes how to query the trace files on the OMU and upload the
trace files onto the local PC as required.
Prerequisites
Procedure
● Through menu operations
a. Click Trace on the LMT main page. The Trace tab page is displayed.
b. On the Trace Navigation Tree pane, choose the Manage Trace File
node. The Manage Trace File dialog box is displayed.

BSC6910 UMTS
c. In the displayed Manage Trace File dialog box, set the parameters in the
Search Configure area, and then click Query to view the information
about the trace files saved on the OMU.
d. To upload a trace file to the local PC, select the target file listed in the
Result area, set the parameters in the Upload Settings area, and then
click Upload.
● Through MML commands
a. Run the LST TRCRST command to query the trace files.
----End
7.3 Device Commissioning

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

This section describes how to trace messages between the exchange module of
the OMU and internal modules of a board or between internal modules of
different boards.
Context
This task can be performed to trace the sent and received messages between two
modules or messages sent from and received by the same module.
NOTICE
Only ADMINISTRATOR-level users are authorized for performing Tracing OS

Messages because it involves private information of users.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab page is displayed.
Step 2 On the Trace Navigation Tree pane, choose Trace > Device Commissioning.
Double-click OS Trace.
Step 3 In the OS Trace dialog box, set the parameters as required, and click Submit. The
trace data pane displays the traced message flow on the Trace tab page on the
WebLMT.
Parameter Description
Trace Type Trace object.

BSC6910 UMTS
Sender When tracing the messages exchanged between the OMU and
Parameter other boards, you must set IP Type to OMU rather than
Receiver Specified IP.
Parameter IP Type cannot be set to OMU for the sender and the receiver
simultaneously, that is, the messages exchanged between the
internal modules of an OMU cannot be traced.
Trace ● Reason of starting this tracing task.

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

This section describes how to redirect the messages printed through the serial port
of a specified subsystem to the message browse window of the LMT.
Context
NOTICE
Only ADMINISTRATOR-level users are authorized for performing Emergency

Diagnosis.
Procedure
Step 2 On the Trace Navigation Tree pane, choose Trace > Device Commissioning.
Double-click Emergency Diagnosis.
Step 3 In the Emergency Diagnosis dialog box, set the parameters as required, and click
Submit. The trace data pane displays the traced message flow on the Trace tab
page on the WebLMT.
● Reason of starting this tracing task.
● Pressing the Enter key and the following are not supported: @ ; '. Letters,
digits, spaces and the following special characters are supported: ! # $ % ^ &
*()_+-=`~:",.|\<>?/{}[]
----End

BSC6910 UMTS
7.3.3 Capturing Packets

This section describes how to capture packets and locate transmission channel
disconnections and packet losses by analyzing packet headers.
Prerequisites
The communication between the LMT and the BSC is normal.
Context
● The following problems can be located by capturing packets:
– The base station controller does not receive the packet.
– After entering the interface board, the packet is discarded by the board
without being sent to other boards in the system.
– The packet is sent to non-interface boards, which then discard the packet.
● When packets are discarded between two boards or connection cannot be
established between two boards, you can check whether the correct packets
are sent to and received by interface boards and other boards in the system
by capturing backplane packets. Then you can quickly locate the problem,
which may be in an interface board or any other board in the system.
● The following types of packet capturing are supported:
– Panel Ethernet packet capturing
– Backplane Ethernet packet capturing
– Panel Ethernet + backplane Ethernet packet capturing
● Only one packet tracing task can be started for each interface board at a
time. Tracing of multiple interface boards can be started simultaneously.
● Only the header of the user plane packet (not including the payload of the
packet) can be captured.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab is displayed.
Step 2 In the Trace Navigation Tree pane, choose Trace > 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 in the WebLMT dialog box that is
displayed. For the specific capturing duration, see the value of Trace Time (OMU
time) in the Packet Capture interface.
● 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.
● To capture panel Ethernet packets, set PortType (Outer) to Ethernet Frame, and set the
parameters in the Outer tab.
● To capture panel Ethernet packets, set PortType (Inner) to Ethernet Frame, and set the
parameters in the Inner tab.

BSC6910 UMTS
● Basic Mode: Enter basic parameters (subrack number and physical slot
number) to start the packet capturing function. Therefore, this is defined as
the basic mode. Under the basic mode, only Panel Ethernet packet capturing
is supported, and backplane Ethernet packet capturing is not supported.
Figure 7-3 Basic Mode
Table 7-2 Basic Mode
Interface Description
Parameter
Trace Reason – Reason of starting this tracing task.

– Pressing the Enter key and the following are not
supported: @ ; '. Letters, digits, spaces and the
following special characters are supported: ! # $ % ^ &
*()_+-=`~:",.|\<>?/{}[]
Subrack No Indicates the number of the subrack which houses the

interface board.
Physical Slot Indicates the number of the physical slot which houses the
No interface board.

BSC6910 UMTS
Parameter
Port No Indicates the number of the port on the interface board

panel.
Scene Select Indicates the scene under which packets are captured are
differentiated by protocol type. For descriptions about
protocol types, see Table Protocol Types
Intercept Each Ethernet frame captured (especially for long packets)

Length 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.
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 in
minutes.
File Type The format of packet capturing files(default value: log).

− When this parameter is set to log, the packet capturing
file is Trace task No._Trace type_YYYYMMDD_HHMMSS
Time zone_File No._IP address.log.zip.
− When this parameter is set to pcap, the packet capturing
file is Trace task No._Trace type_YYYYMMDD_HHMMSS
Time zone_File No._IP address.pcap.zip.
Table 7-3 Protocol Types

Protocol Description
Types
All Packets All packets on the specified port.
DHCP Packet IP packets whose protocol type is UDP.

The destination port number of DHCP request packets
must be 67.
The destination port number of Dynamic Host
Configuration Protocol (DHCP) response packets (not
using relay) must be 68.
The destination port number of DHCP response (using
relay) packets must be 67.

BSC6910 UMTS
Types
IP Address- All IP packets whose local and peer IP addresses are

Specified specified.
Packet
802.3ah/LACP All slow protocol packets, including 802.3ah packets and

Packet LACP packets.
ARP Packet IP packets whose protocol type is Address Resolution

Protocol (ARP), including all request packets and response
packets.
ICMP Packet IP packets whose protocol type is Internet Control Message

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

The UDP destination port number must be 3784.
IPPM Packet IP packets whose protocol type is UDP.

The UDP destination port number must be 65020.
TCP Packet Packets whose protocol type is Transmission Control

Protocol (TCP), including O&M packets of the NodeB and
TWAMP packets.
GTPU Control IP packets whose protocol type is UDP.

Packet The UDP destination port number must be 2152.
GTPU Data IP packets whose protocol type is UDP.

Packet IP packets whose protocol type is UDP The UDP
destination port number must be 2152.
802.1ag Packets whose protocol type is 802.1ag CFM.

Packet
PTRAU Packet Packets whose protocol type is Packet Transcoder and Rate
Adapter Unit (PTRAU).
GSM RTP Packets whose protocol type is Real-Time Transport

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

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

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

Packet capture these packets, set Peer IP Address to an
appropriate value.

BSC6910 UMTS
Types
UMTS PDCP Packets whose protocol type is UMTS Packet Data

Packet Convergence Protocol. To capture these packets, set Peer
IP Address to an appropriate value.
UMTS IURCFP Packets whose protocol type is UMTS IUR Common Frame
Packet Protocol. To capture these packets, set Peer IP Address to
an appropriate value.
SCTP Packet IP packets whose protocol type is SCTP.
● 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.
Figure 7-4 Advanced Mode

BSC6910 UMTS
Table 7-4 Advanced Mode

Parameter
PortType Indicates capturing of packets at the port of the interface

(Outer) 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 Indicates the number of the port on the interface board panel.
Number
Outer Trace ● In: tracing packets entering the port of the interface board
Direction panel from the outside.
● Out: tracing packets sent from the port of the interface
board panel.
● Both: tracing packets in the two directions simultaneously.
Outer Peer Specifies the peer MAC address of the Ethernet frame to be
MAC Address 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 Specifies the local IP address of the IP packet to be captured.

Address 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 selected for the "outer trace
direction".
If left blank, it indicates capturing of all packets at the local IP
address.
Outer Peer IP Specifies the peer IP address of the IP packet to be captured.

Address 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 selected for the "outer trace
direction".
If left blank, it indicates capturing of all packets at the peer IP
address.

BSC6910 UMTS
Parameter
Local User Specifies the local User Datagram Protocol (UDP) port
Datagram number of the IP packet to be captured.
Protocol (UDP) This is the source User Datagram Protocol (UDP) port number
Port No 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 Specifies the peer User Datagram Protocol (UDP) port number
Datagram of the IP packet to be captured.
Protocol (UDP) This is the destination User Datagram Protocol (UDP) port
Port No 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 selected for the "outer
trace direction".
User Datagram Protocol (UDP) port.
PortType Indicates capturing of packets at the port of the interface

(Inner) 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 The number of the port on the interface board backplane.
Number
Inner Trace ● In: tracing the packets entering the interface board
Direction backplane from the SCU board.
● Out: tracing packets sent from the interface board
backplane to the SCU board.
● Both: tracing packets in the two directions simultaneously.
Inner Peer MAC Specifies the peer MAC address of the Ethernet frame to be
Address 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".
MAC address.
----End

BSC6910 UMTS
Follow-up Procedure
● You can manage packet capture in Manage Trace Task 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 or /bam/common/fam/trace/16778026_ packet
capturing _20120927_201909.pcap.zip) are created and saved on the OMU.
Packet capturing results are generated after the task is complete.
7.3.4 AC Tracing
This section describes how to trace signaling messages over the interface between
the base station controller and access controller (AC).
Procedure
Step 2 In the Trace Navigation Tree, choose Trace > Device Commissioning and
double-click AC Trace. The AC Trace dialog box is displayed, as shown in Figure
7-5.
Figure 7-5 AC tracing
Step 3 In the AC Trace dialog box, set parameters as required and click Submit to start
the tracing task in the WebLMT dialog box that is displayed.

BSC6910 UMTS
Table 7-5 Parameter Description

AC Index (0-49) AC index, which uniquely identifies an AC and can be

queried by running the LST ACADDR command.
Trace Reason ● Reason of starting this tracing task.

● Pressing the Enter key and the following are not
*()_+-=`~:",.|\<>?/{}[]
Trace Mode See 7.1.3 Tracing Mode.
----End
7.3.5 DHCP Tracing

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

BSC6910 UMTS
Figure 7-6 DHCP tracing
Step 3 In the DHCP Trace dialog box, set parameters as required and then click Submit
to start the tracing task in the WebLMT dialog box that is displayed.

Subrack No. Indicates the number of the subrack housing the board to
be traced.
Slot No. Indicates the number of the slot housing the board to be
traced. Specify the slot number in scenarios with
independent boards. In scenarios with active and standby
boards, the slot number should be an even number.
Board Type Indicates the type of the board to be traced. The board
type is automatically displayed after the slot number is
specified. It can also be queried by running the LST BRD
command.
Port Type Indicates the transmission type of the port.

BSC6910 UMTS
Port No./Link No./ Indicates the number of the port, link, or port group to
Group No. be traced. If this field is not specified, the entire board
will be traced. It is recommended that users should not
specify this field.
DHCP Product ID Indicates the type of base station to be traced. There are
four options: BTS, NodeB, SRAN, and Other.
● 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.
ESN Indicates the electronic serial number. At least one ESN is

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

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

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

This section describes how to trace the signaling messages over the Iu interface,
including the connection-oriented messages and the connectionless messages. You
can perform this task to identify the failure cause in the following procedures: RAB
assignment, RAB release, paging, Iu release, security mode control, initial UE
message, and relocation.

BSC6910 UMTS
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-7.
Figure 7-7 Message tracing on the Iu interface
Step 3 In the Iu Interface Trace dialog box, set parameters and click Submit to start the
tracing task in the WebLMT dialog box that is displayed.

Basic RNC ID indicates the RNC ID of the cell to be traced. To query it,
run the LST URNCBASIC command.
DPC can be set to All DPC or Specified DPC. If Specified DPC

Config is selected, DPC(HEX) needs to be specified.
uration

BSC6910 UMTS
Trace You can select IU, SCCP, MTP3, QAAL2, SAAL, SCTP or
Type M3UA.
SCCPFLG becomes available if SCCP is selected.
● If SCCPFLG is selected, SCCP messages compliant with
the current interface protocol are reported in tracing
results.
● If SCCPFLG is not selected, SCCP messages complaint
with all interface protocols are contained in tracing
results.

Reason ● Pressing the Enter key and the following are not
&*()_+-=`~:",.|\<>?/{}[]
Trace See 7.1.3 Tracing Mode.

Mode
Save See 7.2.3 Saving Traced Messages.

File
MTP3 MTP3 Set this parameter to Specified Link or Link Set. If this
Trace parameter is set to Link Set, a large number of messages
Type are traced.
Signali Index of an MTP3 signaling link set, which can be

ng Link queried by running the LST MTP3LKS command.
Set
Index
Signali Index of an MTP3 link in the specified link set, which can
ng Link be queried by running the LST MTP3LNK command.
Code
SAAL Signali indicates the number of an signaling link. To query it, run
ng Link the LST SAALLNK command.
ID
SCTP SCTP indicates the number of an SCTP link. To query it, run the
Link ID LST SCTPLNK command.
M3UA M3UA Set this parameter to Specified Link or Link Set. If this
Trace parameter is set to Link Set, a large number of messages
Type are traced.
Signali indicates the number of an M3UA link set. To query it,

ng Link run the LST M3LKS command.
Set
Index

BSC6910 UMTS
Signali indicates the number of an M3UA link. To query it, run

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

This section describes how to trace the signaling messages over the Iupc (Iu
Position Calculation) interface, including the connection-oriented messages. You
can perform this task to identify the cause of the failure in the following scenarios:
PCAP Position Initiations, PCAP Position Activation.
Procedure
Step 2 On the Trace Navigation Tree pane, choose Trace > UMTS Services > Iupc
Interface Trace. The Iupc Interface Trace dialog box is displayed, as shown in
Figure 7-8.
Figure 7-8 Message tracing on the Iupc interface
Step 3 In the Iupc Interface Trace dialog box, set parameters and click Submit to start

BSC6910 UMTS
Table 7-8 Iupc Interface Trace tab page

Basic RNC ID indicates the RNC ID of the cell to be traced.

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

Configuration Specified DPC is selected, DPC(HEX) needs
to be specified.
NOTE
If the DSP index cannot be queried using the LST
USAS command (when the SCCP address mode is
GT), obtain the new GT route index from the
command output and then run the LST
SCCPNGTRT command to query the DSP index
based on the new GT route index.
Trace Type You can select IUPC, SCCP, SCTP or M3UA.

SCCPFLG becomes available if SCCP is
selected.
● If SCCPFLG is selected, SCCP messages
compliant with the current interface
protocol are reported in tracing results.
● If SCCPFLG is not selected, SCCP
messages complaint with all interface
protocols are contained in tracing results.

● Pressing the Enter key and the following
are not supported: @ ; '. Letters, digits,
spaces and the following special
characters are supported: ! # $ % ^ & *
()_+-=`~:",.|\<>?/{}[]
SCTP SCTP Link ID indicates the number of an SCTP link. To

query it, run the LST SCTPLNK command.
M3UA M3UA Trace Set this parameter to Specified Link or Link

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

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

ID query it, run the LST M3LNK command.
----End

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

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

BSC6910 UMTS

Basic RNC ID indicates the RNC ID of the cell to be traced. To

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

Configurati Specified DPC is selected, DPC(HEX) needs to be
on specified.
Trace Type You can select IUR, SCCP, MTP3, QAAL2, SAAL,
SCTP or M3UA.
SCCPFLG becomes available if SCCP is selected.
● If SCCPFLG is selected, SCCP messages
compliant with the current interface protocol are
reported in tracing results.
● If SCCPFLG is not selected, SCCP messages
complaint with all interface protocols are
contained in tracing results.

following special characters are supported: ! # $
%^&*()_+-=`~:",.|\<>?/{}[]
IUR IUR_G In the IUR tab page, if you select IUR_G, the Iur-g
InMbsc 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.
MTP3 MTP3 Trace Set this parameter to Specified Link or Link Set. If
Type this parameter is set to Link Set, a large number of
messages are traced.
Signaling Index of an MTP3 signaling link set, which can be

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

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

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

ID it, run the LST SCTPLNK command.

BSC6910 UMTS
M3UA M3UA Set this parameter to Specified Link or Link Set. If

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

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

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

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

BSC6910 UMTS
Figure 7-10 Message tracing on the Iub interface
Step 3 In the Iub Interface Trace dialog box, set parameters and click Submit to start


NodeB Trace ● All NodeB: traces NodeB Application Part (NBAP)

Type 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.
Trace Type Trace Type

BSC6910 UMTS

%^&*()_+-=`~:",.|\<>?/{}[]
SAAL SAAL Link ID indicates the number of an SAAL link. To query it,
Signaling Link run the LST SAALLNK command.
ID
SCTP SCTP Link ID indicates the number of an SCTP link. To query it, run
the LST SCTPLNK command.
SCTPS SCTPSRV ID SCTP Signaling Server ID

RV
Peer IP Peer IP address
Address
Peer Port Peer Port No.
----End
7.4.5 Tracing Messages on the Uu Interface

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

BSC6910 UMTS
Figure 7-11 Message tracing on the Uu interface
Step 3 In the Uu Interface Trace dialog box, set the parameters as required. Then click
Submit to start the tracing task in the WebLMT dialog box that is displayed.
RNC ID indicates the RNC ID of the cell to be traced. To query it,

Cell Settings 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.
NOTE
A maximum of 32 cells can be traced simultaneously.

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

BSC6910 UMTS
----End
7.4.6 Tracing MNCDT Messages

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

BSC6910 UMTS
Step 3 Set parameters in the MNCDT Trace dialog box and then click Submit to start the


Detection includes Intra-frequency, Inter-frequency, and Inter-

Type RAT.

%^&*()_+-=`~:",.|\<>?/{}[]
Inter- Uplink indicates the uplink UTRA Absolute Radio

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

UARFCN traced for detecting missing neighboring
relationship.
Start of indicates the minimum scrambling code for an

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

Primary MNCDT task. End of Primary Scrambling Code
Scrambling must be not less than Start of Primary Scrambling
Code Code.
Inter-RAT Start of indicates the start of the Network Color Code

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

BSC6910 UMTS
Start of indicates the start of the Base Transceiver Station

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

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

BCCH Channel Number (ARFCN) for an MNCDT task.
ARFCN
End of indicates the maximum ARFCN for an MNCDT task.

BCCH
ARFCN
----End
7.4.7 Message Settings

Clicking this node in the navigation tree enables users to select messages that
need to be traced during UE tracing, cell tracing, and IOS tracing. Tracing these
messages in real time on the LMT facilitates debugging and problem analysis.
Message Name Description
UI_FAM_UT_CELL_I Selecting it enables the LMT to display values of received

NFO 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_ Selecting it enables the LMT to display mapping between

TBL UE IDs of the UE and internal units of the RNC.
UI_FAM_UT_GTPU_ Selecting it enables the LMT to display statistics on

DATA_FWD_MSG packets received and sent at the GPRS Tunneling Protocol
for User Plane (GTPU) layer.
UI_FAM_UT_INTRA Selecting it enables the LMT to display communication

_MSG messages between internal units of the RNC.

BSC6910 UMTS
Message Name Description
UI_FAM_UT_L2_TX Selecting it enables the LMT to display real-time

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

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

TIME_INFO information such as information about cell admission and
cell load control.
UI_FAM_UT_RPRT_ Selecting it enables the LMT to display the number of UEs

CELL_EVENT_INFO in a cell and the propagation delay from the NodeB to the
UEs.
UI_FAM_UT_STAN Selecting it enables the LMT to display UE messages

DARD_MSG traced on standard interfaces.
UI_FAM_UT_STATE Selecting it enables the LMT to trace state transitions of

_TRANS the UE.
7.4.8 Tracing UE Messages

This section describes how to trace UE messages. You can perform this task to
analyze the call procedure failure cause.
Context
NOTICE
There is no way to avoid that some user data such as IMSI, IMEI, TMSI, MSISDN,
and CELLID will be used during tracing. This function provides a pseudonymous
data processing method to encrypt such data as IMSI and IMEI using irreversible
HASH algorithm that provides a random key. 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 pseudonymous function and deleting the folder
that saves track records after you finish processing data. For details about personal
data description, see BSC6900&BSC6910 UMTS personal data description.

BSC6910 UMTS
● When entering IMSI, check whether IMSI data to be entered must be pseudonymous by
running the LST USERIDANONSWITCH command and querying User Identity
Pseudonymization Switch.
● If User Identity Pseudonymization Switch is ON, the pseudonymous policy is enabled,
and pseudonymous IMSI data must be entered in IMSI. The pseudonymous IMSI data is
the IMSI data encrypted by the HMACUtil using the cipher key.
● If User Identity Pseudonymization Switch is OFF, the pseudonymous policy is disabled,
and user IMSI data is directly entered in IMSI.
● Change the pseudonymous policy and cipher key on the U2020 by choosing Trace and
Maintenance > Signaling Trace > Pseudonymization Policy Management >
Pseudonymization Key Management (application style) or Trace and Maintenance >
Monitor > Signaling Trace > Pseudonymization Policy Management > Pseudonymization
Key Management (traditional style). For details, see U2020 Fault Management User Guide.
● If you change the pseudonymous policy or cipher key of a started tracing task, you need to
restart the tracing task. Otherwise, the tracing task becomes invalid.
● For details about how to obtain the HMACUtil, contact Huawei technical support.
● To view detailed description of TXT (Command Code) messages, right-click in the blank area
on the right part of the window and choose Update Text from the shortcut menu. The text
messages update once each time users choose Update Text. They do not automatically
update.
Procedure
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 a single-user CS tracing task.
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. The UE
Trace dialog box is displayed.
Step 3 In the displayed UE Trace dialog box, set the parameters as required. Then click
Table 7-13 UE Tab Parameter Description

RNC ID indicates the RNC ID of the cell to be traced. To query it, run the
LST URNCBASIC command.

BSC6910 UMTS
IMSI/ Identifying the UE to be traced. Choosing to trace the UE by the

MSISDN/ TMSI, you need to specify LAC, MCC, and MNC. Choosing to
IMEI/ trace the UE by the P-TMSI, you need to specify LAC, RAC, MCC,
TMSI/P- and MNC.
TMSI ● 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.
● Assume that you trace a UE by specifying the IMSI and the
IMSI is not carried in the RRC CONNECTION REQUEST
message but only carried in the RANAP COMMON ID
message. If CDT_MSG_FULL_TRACE is set to ON, the UE
tracing task traces the messages that are sent after the
RANAP COMMON ID message, and the messages sent before
the RANAP COMMON ID message are buffered and reported.
If CDT_MSG_FULL_TRACE is set to OFF, the messages sent
before the RANAP COMMON ID message are discarded
instead.
TRACE RRC Indicating whether to trace messages on the standard interface

PROCEDURE 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.

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

BSC6910 UMTS
Debug indicates a maintenance mode used for tracing communication

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

Reason ● Pressing the Enter key and the following are not supported:
characters are supported: ! # $ % ^ & * ( ) _ + - = ` ~ : " , . | \
<>?/{}[]
Table 7-14 Monitor Tab Parameter Description

Uplink SIR Selecting the counter starts monitoring of uplink Signal to

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

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

BLER (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 Selecting the counter starts monitoring of downlink code

Code Power 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 Selecting the counter starts monitoring of PCPICH Ec/No and

Ec/No RSCP Received Signal Code Power (RSCP) during tracing of a single UE.
The counter is reported periodically. The period of reporting the
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.

BSC6910 UMTS
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 Selecting the counter starts monitoring of downlink transmit

Transmit power transmitted for the cell serving the current UE. The
Power(0.4s) counter is reported every 0.4 second.
Table 7-15 Other Tab Parameter Description

Layer 2 Selecting it enables statistics on packets received and sent at

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

Data interface boards to be periodically reported to the LMT. Analysis
Periodic of these statistics helps users to determine whether a fault occurs
Report on the RNC side.
Report Indicates the period for reporting Layer 2 data transfer periodic
Period report.

BSC6910 UMTS
L2 Data Includes parameters that enable statistics on packets received

Report 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.
● TCP Proxy Data Report: After the TCP proxy function is
enabled, the TCP/IP headers of the following TCP packets are
reported to the LMT:
– In the downlink, user-plane TCP packets that are received
from the server and transmitted to the UE at the PDCP
layer.
– In the uplink, user-plane TCP packets that are received
from the UE and transmitted to the server at the PDCP
layer.
When RNC in Pool is used for user-plane load-sharing, Report
File is recommended if the user selects L2 TRB packet header
report (Iub interface) or L2 TRB packet header report (Iu
interface) on the Other tab page. After the user selects Report
File, the user needs to configure the FTP server and ensure that
the FTP server connects to the master RNC and overflow RNC.
The tracing results generated by the master RNC are saved on
the OMU of the master RNC and the tracing results generated by
the overflow RNC are saved on the OMU of the overflow RNC.
You can use the FTP server to upload the tracing results on the
OMU to the directory specified by Upload Path.
NOTE
You can run the MML command LST UPOOLLOADSHAREPARA to query
the value of UP Load Sharing Policy. If the value of this parameter is
UP_SHARE, RNC in Pool is used for user-plane load-sharing.
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.1 ms): indicates the interval at which ICMP
packets are sent.
● Packet Length (bytes): indicates the payload length of the
ICMP packets.

BSC6910 UMTS
Voice When this check box is selected, the LMT records the test results
Analysis 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 and 10. 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 Selecting it enables tracing of real-time QAAL2 standard protocol

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

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

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

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

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

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

FP PM Selecting it enables transmission statistics at the FP layer to be

Report reported to the LMT.

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

Downlink returned to the CN. This function is used for isolating other
Loop network elements during problem analysis, which facilitates
location of speech quality problems.
NOTE
When this operation is performed, the peer end can only hear the voice of
itself rather than that of the traced user.
PDCP Trace Selecting it enables information about Packet Data Convergence

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

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

Protocol reported to the LMT.
Trace Report
TCP Proxy When the TCP proxy function is enabled, protocol parameters
Protocol about user-plane TCP packets can be reported to the LMT.
Trace Report
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.
● 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.
● RearPanel trace: traces data flows sent or received on the
backplane of the interface board.
● FrontPanel trace: traces data flows sent or received on the
panel of the interface board.
NOTICE
Note that selecting Rear panel trace or Front panel trace may lead to
flow control, so exercise caution in this selection.

BSC6910 UMTS
TCP Proxy Selecting it configures the single-user TCP proxy function.

Function ● TCP Proxy Function Config Type: It can be set to DL TCP
Config Proxy Enable or TCP Proxy Disable.
– DL TCP Proxy Enable: Enables the single-user downlink
TCP proxy function.
– TCP Proxy Disable: Disables the single-user TCP proxy
function.
Bind: Binding the UE to a UP or path or transmission resource pool. This helps

users to determine whether a UP or path fault exists.
Table 7-17 Bind Tab Parameter Description

UUP 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.
● CID/UDP PORT(I1,I2,I3...): indicates the bound channel
identifier (CID) on the Iub path in ATM transmission mode or
the number of the bound User Datagram Protocol (UDP) port
in IP transmission mode.
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.
● CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iu-
CS path in ATM transmission mode or the number of the
bound UDP port in IP transmission mode.
Iur ● 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.
● CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iur
path in ATM transmission mode or the number of the bound
UDP port in IP transmission mode.
Iups ● Path ANI No.: indicates the ANI corresponding to the Iu-PS
path.
● Type: indicates the transport type of the Iu-PS Pool IP.
● IP Pool IP Address: indicates the number of the Iu-PS Pool IP.

BSC6910 UMTS
NODE ● Node ID/External Node ID: indicates the ID of the bound

physical node.
----End
7.4.9 Tracing Cell Messages

This section describes how to trace cell messages. The tracing results of the cell
messages provide reference for troubleshooting common channel faults when the
access success rate is low or zero in the cell. The UE statistics can be displayed in
the tracing result if required.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Cell Trace. The
Cell Trace dialog box is displayed, as shown in Figure 7-13.
Figure 7-13 Cell message tracing
Step 3 Set parameters in the Cell Trace dialog box and then click Submit to start the

BSC6910 UMTS
Table 7-18 Cell Trace Tab Parameter Description

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

Cell ID indicates the index of a cell.

NOTE
Only one cell can be traced simultaneously.
User Quantity/ indicates the event to be traced, either the

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

communication messages between units of the RNC.
Tracing tasks configured on Other and Bind tab pages
take effect only when Debug Mode is selected.

*()_+-=`~:",.|\<>?/{}[]
Table 7-19 FMR Tab Parameter Description

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

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

ms) Data Periodic Report or Transport Data Periodic Report
is selected in the FMR tab page.
Bind: Binding the UE to a UP. This helps users to determine whether a UP fault
exists.

BSC6910 UMTS

UUP UP No.: indicates the number of the UP.
Table 7-21 Table 4 Other Tab Parameter Description

SIG Trace Event includes internal transport events of the RNC to be traced.
CDR_SIG_QAAL2_P Selecting it enables tracing of real-time QAAL2 standard

DU_MSG protocol messages. Information elements carried in the
messages help determine whether QAAL2 message
interaction between NEs is successful.
CELL_SIG_AL_STRE Selecting it enables specified data flow of the cell on the

AMING_RPRT 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).
----End
7.4.10 Tracing IOS Messages

This section describes how to trace a number of calls that meet the sampling
criteria within a specified range of cells. When creating the task, you can specify
the number of calls to be traced and specify messages to be traced by selecting
the event type.
Context
NOTICE
The IOS tracing task involves a large amount of trace information, which affects
the system operation. Therefore, the maximum number of simultaneously traced
calls set in the Max calls simultaneously traced area in the IOS dialog box
should not be too high. In addition, you are advised not to trace all events at a
time. Furthermore, you should minimize the frequencies of performing this task
and the number of tasks performed simultaneously.
● 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 call tracing task, you can define the sampling criteria by
setting the RAB parameter constraints and the RRC Est Cause. Once the

BSC6910 UMTS
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.
● Assume that the specified number of continuous calls is N. If N calls are
already being traced, the system does not trace any newly accessed calls. If
the number becomes less than N because of the termination of a traced call,
the system automatically traces a new call.
● If multiple IOS tracing tasks with the same parameter settings are started,
one task can trace and display the tracing messages of only one user, because
each user is traced by a specific tracing task.
● To view detailed description of TXT (Command Code) messages, right-click in
the blank area on the right part of the window and choose Update Text from
the shortcut menu. The text messages update once each time users choose
Update Text. They do not automatically update.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > IOS Trace. The
IOS Trace dialog box is displayed, as shown in Figure 7-14.

BSC6910 UMTS
Figure 7-14 IOS message tracing
Step 3 In the displayed IOS Trace dialog box, set parameters and filter traced messages
in other tab pages. Then click Submit to start the tracing task in the WebLMT
Table 7-22 Basic Tab Parameter Description

RNC ID RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.
Call Count maximum number of calls that can be traced simultaneously

after a tracing task is started. The value ranges from 1 to 30.
Call Count Per Maximum number of calls that single cell can be traced
Cell simultaneously after a tracing task is started. The value ranges
from 1 to 30.
Cell ID You can type the ID of one cell or IDs of multiple cells.
NOTE
A maximum of 32 cells can be traced simultaneously.
VIP IMSI Run the ADD UVIPIMSI command to add the VIP IMSI.

BSC6910 UMTS
Trace only When this switch is turned on, only users with control plane
inter- load sharing are traced.
subsystem
users
IMEI IMEI TAC of the user to be traced. You can enter a maximum
TAC(TAC1,TAC2 of eight IMEI TACs. An IMEI TAC can be a decimal number of 1
,...TAC8) 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_QUE
RY_UE_IMEI_SWITCH-1,
PROCESSSWITCH4=SEND_MSG_NULL_SWITCH-1;
Event Type 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.

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

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

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

BSC6910 UMTS
Table 7-23 MM Tab Parameter Description

CELL CHANGE CELL CHANGE ORDER: Traced messages of the cell change
ORDER order procedure.
INTER RAT Traced messages of the incoming inter-RAT handover

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

HANDOVER procedure through relocation.
OUT
LOCATION Traced messages of the location area update procedure.

UPDATE
ROUT AREA Traced messages of the routing area update procedure.

UPDATE
PCH CELL Traced messages of the cell update procedure for UEs in the
UPDATE CELL_PCH and URA_PCH states.
SHO Traced messages of the soft handover procedure.
HHO Traced messages of the hard handover procedure.
CELL UPDATE Traced messages of the cell update procedure.
RB RECONFIG Traced messages of the route bit reconfig procedure.
RL REEST Traced messages of the radio link re-establish procedure.
RRC/RAB DRD Traced messages of the RRC/RAB directed retry decision

procedure.
CSFB Traced messages of the circuit-switched fallback procedure.
RAB tab page:

● 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.

BSC6910 UMTS
Table 7-24 RRC Tab Parameter Description

RRC(ms) Period of reporting measurement results of PCPICH Ec/No and

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

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

RRC(ms) 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 Period of reporting results of cell common measurement that

(ms) is selected in the Monitor tab page of IOS Trace.
NBAP Period of reporting measurement results of downlink code

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

Special(ms) transmit power in the DRNC cell when forward power control
tracing is selected or Downlink Tx Code Power in the Monitor
tab page is selected for IOS tracing.
RRC Located UE locating method used during IOS tracing.

Type
RRC Located Period for reporting UE locating results during IOS tracing.
Cycle (ms)
RTT Special Period of reporting results of Round Trip Time (RTT)

NBAP(ms) measurement in the SRNC cell when forward power control
tracing is selected or the Monitor tab page is configured for
IOS tracing.
RRC Est Cause Call establishment causes and filters UEs to be traced in the
cell based on the call establishment causes.
Monitor tab page: includes performance counters to be monitored during tracing

of a single UE

BSC6910 UMTS
Table 7-25 Monitor Tab Parameter Description

Uplink SIR Selecting the counter starts monitoring of uplink Signal to

Interference Ratio (SIR) during tracing of a single UE. The
counter is reported periodically. The period of reporting the
UE Tx Power Selecting the counter starts monitoring of uplink transmit

power during tracing of a single UE. The counter is reported
Downlink BLER Selecting the counter starts monitoring of Block Error Rate
(BLER) during tracing of a single UE. The counter is reported
Downlink Tx Selecting the counter starts monitoring of downlink code

Code Power 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 Selecting the counter starts monitoring of PCPICH Ec/No and
RSCP 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 Selecting the counter starts monitoring of downlink transmit

Power(0.4s) power transmitted for the cell serving the current UE. The
counter is reported every 0.4 second.
Table 7-26 Other Tab Parameter Description

Layer 2 Data To enable statistics on packets received and sent at layer 2 to

Transfer be periodically reported to the LMT, specify the parameter
Periodic Report value.

BSC6910 UMTS
L2 Data Report 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): 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.
● TCP Proxy Data Report: After the TCP proxy function is
enabled, the TCP/IP headers of the following TCP packets
are reported to the LMT:
– In the downlink, user-plane TCP packets that are
received from the server and transmitted to the UE at
the PDCP layer.
– In the uplink, user-plane TCP packets that are received
from the UE and transmitted to the server at the PDCP
layer.
When RNC in Pool is used for user-plane load-sharing, Report
File is recommended if the user selects L2 TRB packet header
report (Iub interface) or L2 TRB packet header report (Iu
interface) on the Other tab page. After the user selects
Report File, the user needs to configure the FTP server and
ensure that the FTP server connects to the master RNC and
overflow RNC. The tracing results generated by the master
RNC are saved on the OMU of the master RNC and the
tracing results generated by the overflow RNC are saved on
the OMU of the overflow RNC. You can use the FTP server to
upload the tracing results on the OMU to the directory
specified by Upload Path.
NOTE
You can run the MML command LST UPOOLLOADSHAREPARA to
query the value of UP Load Sharing Policy. If the value of this
parameter is UP_SHARE, RNC in Pool is used for user-plane load-
sharing.
QAAL2_protoco Selecting it enables tracing of real-time QAAL2 standard

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

BSC6910 UMTS
RT_BASIC_INF Selecting it enables the following information to be traced:

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

NTEXT_INFO the serving NodeB, communication context ID of the
controlling radio network controller (CRNC), URNTI, CRNTI,
and UE ID.
RT_INST_RESO Selecting it enables tracing of real-time index of resources

URCE_INFO that are allocated to the UE, for example, system memory.
RT_RAB_PARA_ Selecting it enables tracing of real-time radio access bearer

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

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

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

Loop returned to the CN. This function is used for isolating other
network elements during problem analysis, which facilitates
location of speech quality problems.
NOTE
When this operation is performed, the peer end can only hear the
voice of itself rather than that of the traced user.

BSC6910 UMTS
FP Trace Selecting it enables control frames on the IuUP or at the FP

layer to be reported to the LMT.

Iub Path ● Path ANI No.: Adjacent Node Identifier (ANI)

corresponding to the Iub path.
● Path Type: Transport type of the Iub path.
● Path ID: ID of an Iub path.
● CID/UDP PORT(I1,I2,I3...): Bound channel identifier (CID)
on the Iub path in ATM transmission mode .
Iucs Path ● Path ANI No.: ANI corresponding to the Iu-CS path.
● Path Type: Transport type of the Iu-CS path.
● Path ID: ID of an Iu-CS path.
● CID/UDP PORT(I1,I2,I3...): Bound CID on the Iu-CS path in
ATM transmission mode.
Iur Path ● Path ANI No.: ANI corresponding to the Iur path.
● Path Type: Transport type of the Iur path.
● Path ID: ID of an Iur path.
● CID/UDP PORT(I1,I2,I3...): Bound CID on the Iur path in
ATM transmission mode.
Iups GTPU ● Path ANI No.: ANI corresponding to the Iu-PS GTPU.
● IP Pool IP Address: IP pool IP address corresponding to the
Iu-PS GTPU.
----End
7.4.11 Tracing Iur-p Messages

This task traces messages over the Iur-p interface in a resource pool. The task can
be started to locate faults when the load sharing fails, the load is unbalanced, or
RNCs cannot communicate with each other in a resource pool.
Context
Physical RNCs of logical RNC communicate with each other through the Iurp
interface.

BSC6910 UMTS
Procedure
Step 1 ClickTraceon the LMT main page. The Trace tab page is displayed.
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iur-p Trace. The
Iur-p Trace dialog box is displayed, as shown in Figure 7-15.
Figure 7-15 Iur-p message trace
Step 3 In the displayed Iur-p Trace dialog box, set the parameters as required. Click
Table 7-29 Tab Parameter Description
Basic External You can select All External Node or Specified External
Node Node. When you select Specified External Node, you
Configur need to type Specified External Node.
ation
Trace You can select IURP or IURPLNK.

Type

&*()_+-=`~:",.|\<>?/{}[]

Mode

BSC6910 UMTS
IURP Frame You can select All, Control Frame, Data Frame or OM
Type Frame.
Direction You can select All, In or Out.
IURPLIN Link Set Uniquely identifies a signaling link set.

K Index
Link Uniquely identifies a signaling link.

Index
----End
7.4.12 Tracing Messages on the Sr Interface

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

BSC6910 UMTS
Step 3 On the Sr Interface Trace dialog box, set parameters and click Submit to start the

Basic RNC ID indicates the RNC ID of the cell to be traced. To query

it, run the LST URNCBASIC command.
Trace Type You can select SR or SCTP.

&*()_+-=`~:",.|\<>?/{}[]

Mode
SCTP SCTP Link indicates the number of an SCTP link. To query it, run
ID the LST SCTPLNK command.
----End

BSC6910 UMTS
LMT User Guide 8 Performance Monitoring
8 Performance Monitoring
This chapter describes how to monitorBSC6910 performance. A maximum of 64

monitoring tasks can be started simultaneously on the LMT. If OMU boards are
switched over, performance monitoring can be restarted 30 minutes after the
switchover.
8.1 Concepts
This section describes the concepts related toBSC6910 performance monitoring,
monitoring principles, and monitoring rights management.
8.2 General Operations
This section describes the general operations applicable to all performance
monitoring tasks performed on the BSC6910.
8.3 Common Monitoring
This section describes common performance monitoring.
8.4 UMTS Monitoring
This section describes performance monitoring of UMTS services.
8.1 Concepts
This section describes the concepts related toBSC6910 performance monitoring,
monitoring principles, and monitoring rights management.
8.1.1 Monitoring Principles

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

Figure 8-1 displays the principles of CPU usage monitoring.

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

Figure 8-2 shows the principles of other real-time performance monitoring, which
are similar to the principles of message tracing.
Figure 8-2 Real-time performance monitoring
The process when the LMT creates a real-time monitoring task, other than CPU
usage monitoring, is as follows:
1. The LMT sends a binary command to the OMU to create the task.
2. The OMU assigns a task ID to the task and sends the command to the
debugging module of a specified board.
3. Upon receiving the command, the debugging module records the filter
parameters in the filter table and notifies the service module of the
information.

BSC6910 UMTS
4. The service module updates the local filter table in accordance with the
messages from the debugging module.
The process when the LMT stops a real-time monitoring task is as follows:
1. When you stop a monitoring task on the LMT, the LMT sends a binary
command to the OMU to delete the task.
2. The OMU sends the command to the specified board based on the task ID.
3. The debugging module and service module delete the task from the filter
table.
The process when the LMT reports real-time monitoring data is as follows:
1. The service module compares the collected data with data in the local filter
table. If the data is the same, the service module reports the collected data to
the OMU.
2. Upon receiving the data, The OMU forwards it to the LMT that creates the
task based on the task ID.
3. The LMT displays the data in a chart or a list.
8.1.2 Operation Rights Control

Only authorized users can perform real-time monitoring on the BSC6910.
Only the admin, common—operator-level, operator-level, administrator-level, and
G_10-authorized custom-level users can perform this operation on BSC. Guest-
level users and G_10-unauthorized custom-level users can only perform CPU
usage monitoring.
Group G_10 consists of binary commands used for tracing and monitoring.
8.2 General Operations

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

This describes how to browse online and query the monitoring results that are
dynamically displayed in the real-time performance monitoring window of the
WebLMT.
Prerequisites
● A performance monitoring task has been started.
● Monitoring data has been reported.
Procedure
● Right-click on the Chart tab page in the real-time performance monitoring
window of the WebLMT. Then, you can perform the following operations by
selecting an appropriate option from the shortcut menu:

BSC6910 UMTS
– Auto Scroll
– Show Grid
– Switch Display Mode
When the number of real-time monitoring tasks is greater than 60, right-click on the
Chart tab page and choose Switch Display Mode from the shortcut menu:
● If the bar chart has been displayed, you can switch it to the sequence diagram.
● If the sequence diagram has been displayed, you cannot switch it to the bar
chart.
– Auto Adjust
● Right-click on the List tab page in the real-time performance monitoring
window. Then, you can perform the following operation by selecting an
appropriate option from the shortcut menu:
Setting auto scroll

● Right-click on the task information pane at the bottom of the real-time
performance monitoring window. Then, you can perform the following
operations by selecting an appropriate option from the shortcut menu:
– Add Task or Delete Task
– Stop Task or Restart Task
– List Detailed Task Info
----End
8.2.2 Setting Chart Display Mode

This section describes how to set the chart display mode in the real-time
performance monitoring window of the WebLMT after you create and start a
monitoring task. On the lower part of the Chart tab page in the window, you can
set the chart display properties, such as the line color, line type, and line width.
Prerequisites
Procedure
Step 1 In the task information pane of the real-time performance monitoring window,
click Line Color, Line Type, or Line Width.
Step 2 Select the required properties from the drop-down lists.
● The chart display attribute settings apply only to the current monitoring task.
● You can set the chart display mode. If data is displayed on the List tab page but no
chart is displayed on the Chart tab page during the real-time monitoring.
----End

BSC6910 UMTS
8.2.3 Saving Monitoring Data

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

This section describes how to offline browse CPU usage monitoring data files and
errored second monitoring data files using the traffic recording review tool.
Prerequisites
The monitoring data has been saved as files.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal >
TrafficRecording Review Tool.
Step 2 Open save path of monitoring data files. The default save path is C:/Web LMT/
MBSC/output/monitor. Select the file to be browsed.
Step 3 Click Open or double-click the file. The TrafficRecording Review Tool window is
displayed, showing the monitoring data in a chart or a table.
Step 4 Click the List or Chart tab to view the data in different modes.
Step 5 To view other files, choose File > Open. In the Open dialog box, select and open
the target files to browse them.
----End
8.3 Common Monitoring

This section describes common performance monitoring.

BSC6910 UMTS
8.3.1 Monitoring Board CPU Usage

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

This section describes how to monitor CPU usage on a board subsystem. This
function helps users know resource usage on a board subsystem.
Prerequisites
● You have logged in to the LMT with an account authorized for this operation.
● The subsystem under monitoring is running properly.
Context
NOTICE
This function increases the CPU usage. Therefore, if the CPU usage reaches 80% or
higher, set the monitoring period to 5s.

BSC6910 UMTS
Procedure
> Subsystem CPU Usage Monitor. The Subsystem CPU Usage Monitor dialog
box is displayed.
Step 3 In the Subsystem CPU Usage Monitor dialog box, set the parameters to
appropriate values, and click Submit to start the monitoring task in the WebLMT
----End
8.3.3 Monitoring Transmission Resources

This section describes how to monitor the transmission resources on the Iub
interface.
Prerequisites
The board under monitoring is functional.
Procedure
Step 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.
> Transport Resource Real-Time Monitoring. The Transport Resource Real-Time
Monitoring dialog box is displayed.
Step 3 In the Transport Resource Real-Time Monitoring dialog box, set the parameters
as required, and click Submit to start the monitoring task in the WebLMT dialog
box that is displayed.
● Statistic Period(s): Specifies the duration of the measurement period for
monitoring.
● 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.
– Logic Port No.: Indicates the
logical port number. To query the
logical port number, run the LST
IPLOGICPORT command.

BSC6910 UMTS
Transport Object Type Description
Physical Port Indicates the number of the physical

port. Physical Port Type must be
specified.
– FRA Link: Indicates the number
of the physical port carrying the
FRA link. To query FRA Link, run
the LST FRALNK command.
– 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.
– UNI Link: Indicates the number
of the physical port carrying the
UNI link. To query UNI Link, run
the LST UNILNK command.
● Subrack No.: Indicates the number of the subrack where the transport object
to be monitored is located.
● Slot No.: Indicates the number of the slot where the transport object to be
monitored is located.
● OP Index No.: Indicates the monitored operator of the transport object.
● 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.

BSC6910 UMTS
Table 8-2 Bandwidth(Original)

Statistic Description
Item(Original)
Admitted Admitted bandwidth for 3G services at the transport

Bandwidth(3G layer on the user plane. The admitted bandwidth consists
Total) 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 Overload control (OLC) end threshold. It equals

Threshold 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 available currently. It equals Total

Bandwidth 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.
Reserved Threshold Threshold for reserving bandwidth for handovers. It

for Handover equals configured bandwidth minus handover reserved
bandwidth.
To query the handover reserved bandwidth, run the ADD
TRMLOADTH command. Note that when Threshold
type is set to PERCENTAGE(Percentage), the handover
reserved bandwidth equals the configured bandwidth
multiplied by the handover reserved ratio.
RealTimeFluxBw Real-time traffic on a port, which is valid only during

downlink traffic monitoring.
RealTimeQueueFlu Real-time traffic in the service queues on a port, which is

x valid only during downlink traffic monitoring.

BSC6910 UMTS
Item(Original)
Congestion Clear Congestion end threshold. It equals configured

Threshold bandwidth minus congestion clear remain bandwidth.
To query the congestion clear remain bandwidth, run the
ADD TRMLOADTH command. Note that when
congestion clear remain bandwidth equals the
configured bandwidth multiplied by the congestion clear
remain ratio.
Congestion Congestion start threshold. It equals configured

Threshold bandwidth minus congestion remain bandwidth.
To query the congestion remain bandwidth, run the ADD
type is set 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)

Item(Statistic)
Admitted Admitted bandwidth for 3G services at the transport

Bandwidth(3G layer on the user plane. The admitted bandwidth consists
Total) 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.
Available Bandwidth available currently. It equals Total

Bandwidth 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.

BSC6910 UMTS
Item(Statistic)
Congestion Clear Congestion end threshold. It equals configured

Threshold bandwidth minus congestion clear remain bandwidth.
To query the congestion clear remain bandwidth, run the
ADD TRMLOADTH command. Note that when
congestion clear remain bandwidth equals the
configured bandwidth multiplied by the congestion clear
remain ratio.
Congestion Congestion start threshold. It equals configured

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

Threshold 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 TRMLOADTH command. Note that when
overload congestion remain bandwidth equals the
configured bandwidth multiplied by the congestion
remain ratio.
RealTimeFluxBw Real-time traffic on a port, which is valid only during

downlink traffic monitoring.
RealTimeQueueFlu Real-time traffic in the service queues on a port, which is

x valid only during downlink traffic monitoring.

BSC6910 UMTS
Item(Statistic)
Reserved Threshold Threshold for reserving bandwidth for handovers. It

for Handover equals configured bandwidth minus handover reserved
bandwidth.
To query the handover reserved bandwidth, run the ADD
type is set to PERCENTAGE(Percentage), the handover
reserved bandwidth equals the configured bandwidth
multiplied by the 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.3.4 Monitoring BERS

This section describes how to monitor errored second (ES)of an E1/T1 port to
monitor transmission quality of the link corresponding to a port. If any bit errors
occur on the E1/T1 port, this function helps users obtain data, such as ES, severely
errored second (SES), unavailable second (UAS), errored frames, CRC errors, bit
error rate (calculated by CRC errors). Based on the data and performance of the
peer device, you can evaluate the transport network status and identify the causes
for the errors. The AOUc board supports this function.
Procedure
> BERS Monitoring. The BERS Monitoring dialog box is displayed.
Step 3 In the BERS Monitoring dialog box, set parameters according to actual situations,
and click Submit to start the monitoring task in the WebLMT dialog box that is
displayed.
----End
8.3.5 Monitoring BER

This section describes how to monitor bit error rate (BER). The BER is used to
evaluate transport network quality. The AOUc board supports this function.

BSC6910 UMTS
Context
● Using this function interrupts IMA groups, UNI links, fractional ATM links,
carried on a board. As a result, services on the corresponding port are
interrupted.
● Before monitoring the BER, configure the local loopback or remote loopback,
or use a loopback connector to short-circuit the TX end and the RX end.
● BER monitoring test and loopback test cannot be performed simultaneously
because the result and principles of these tests are the same.
● Only one BER monitoring test can be started for a board at a time.
Procedure
> BER Monitoring. The BER Monitoring dialog box is displayed.
Step 3 In the BER Monitoring dialog box, set parameters according to actual situations,
and click Submit to start the monitoring task in the WebLMT dialog box that is
displayed.
----End
8.3.6 Monitoring Link Performance

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

This section describes the parameters used for performance monitoring.
Monitor Parameter Description

Item
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 FRAC Link No. Indicates the number of the fractional ATM
ATM Link link. To query the number of the fractional
ATM link, run the LST FRALNK command and
set Link type to FRAATM.
SAAL Link SAAL Link No. Indicates the number of the SAAL link. To
query the SAAL link, run the LST SAALLNK
command.

BSC6910 UMTS

Item
IPOA PVC IP Address Indicates the local and peer IP addresses of the
Ping Peer IP IPOA PCV. To query these IP addresses, run the
Address LST IPOAPVC command.
AAL2 Path Adjacent Node Indicates the ID of the adjacent node to an

ID AAL2 path and the AAL2 path symbol. To
AAL2 PATH query the adjacent node ID and the AAL2 path
Symbol symbol, run the LST AAL2PATH command.
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 IPLOGICPORT
command.
OAM NodeB ID Indicates the NodeB ID. To query the NodeB

ID, run the LST UNODEB command.
Non- Optical Port No. Indicates the number of the non-channelized

Channelized ATM optical port. To query the optical port,
ATM Optical run the LST OPT command.
Port
TRUNK TRUNK Group Indicates the number of the trunk group. To

Group No. query the trunk group, run the LST ETHTRK
command.
IPPOOL Local IP Address To query the local IP address, run the LST
LOCAL IP IPPOOLIP command.
IPPOOL PM Local IP Address Is the same as Currently bound SIP, the IP

Peer IP Address address currently bound to the adjacent node.
To query Currently bound SIP, run the DSP
Priority ADJNODE command.
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.

BSC6910 UMTS

Item
IURPLINK IURP Link No. To query the IURP Link, run the LST IURPLNK
command.
8.3.6.2 Monitoring IMA Group Traffic

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

This section describes how to monitor traffic on a specified UNI link in real time.
on the UNI links at both ends, you can check the IE loss, locate the fault, and
monitored traffic is consistent with the actual traffic processed by the UNI link and
whether the bandwidth is sufficient. The check result provides reference for
changing the link configuration mode. For example, change the link configuration
mode to the IMA mode to support more traffic.

BSC6910 UMTS
Context
NOTICE
The UNI link must be successfully set up and connected to the peer link before
this task is performed. This task is stopped if the monitored link is deleted.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to UNI Link
----End
8.3.6.4 Monitoring Fractional ATM Link Traffic

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

BSC6910 UMTS
8.3.6.5 Monitoring SAAL Link Traffic

This section describes how to monitor traffic on a specified SAAL link in real time.
The monitoring result is displayed in lists and charts. Based on the TX/RX statistics
on the SAAL links to a subsystem, you can check the packet loss, locate the SAAL
disconnection or intermittent disconnection. In addition, you can observe the link
traffic and check whether link congestion occurs based on the configured link
bandwidth.
Context
NOTICE
The SAAL must be successfully set up and connected to the peer link before this
task is performed. This task is stopped if the monitored link is deleted.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SAAL Link
----End
8.3.6.6 Monitoring IPOA PVC Link Traffic

This section describes how to monitor traffic on a specified IPOA PVC link in real
time. The monitoring result is displayed in lists and charts. If the IPOA PVC link
works as an OML for the ATM-based base station, this function helps you locate
base station startup and load problems and helps you observe the traffic and
bandwidth utilization. If the IPoA PVC link works as an IP path over the Iu-PS
interface, this function helps you observe the link traffic and locate connection
and congestion problems of upper-layer links.
Context
NOTICE
The IPOA PVC link must be successfully set up and connected to the peer link

BSC6910 UMTS
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPOA PVC
----End
8.3.6.7 Monitoring AAL2 Path Traffic

This section describes how to monitor traffic on a specified AAL2 path in real time.
The monitoring result is displayed in lists and charts. Based on the layer-2 TX/RX
statistics in the CDT data, you can check the packet loss and evaluate the traffic
condition. In addition, you can observe the link traffic and check whether link
congestion occurs based on the configured link bandwidth.
Context
NOTICE
The AAL2 path must be successfully set up and connected to the peer link before
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to AAL2 Path
----End
8.3.6.8 Monitoring FE/GE Port Traffic

This section describes how to monitor traffic on a specified FE/GE port in real
time. The monitoring result is displayed in lists and charts. Based on the traffic
statistics on the FE/GE port, you can check the packet loss, locate the fault, and
monitored traffic is consistent with the actual traffic on the port, check the port
utilization, and check whether the bandwidth is sufficient. The check result
provides reference for migrating services to prevent congestion.

BSC6910 UMTS
Context
NOTICE
The FE/GE port must be successfully configured and connected to the peer port
For FG2c, FG2e, GOUc, GOUe boards, if the physical port carries a logical port and
Monitor Type is set to QoS for this task, the queue statistics of the physical port
does not include the service data traffic on the logical port but includes only the
service data traffic on the physical port.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to FE/GE and
set other parameters according to actual situations. Then, click Submit to start the
monitoring task in the WebLMT dialog box that is displayed.
----End
8.3.6.9 Monitoring SCTP Link Traffic

This section describes how to monitor data packet traffic on a specified SCTP link
in real time. The monitoring result is displayed in lists and charts. Based on the
monitored traffic, you can check the packet loss, locate SCTP link intermittent
disconnection, and check whether link congestion occurs.
Context
NOTICE
The SCTP link must be successfully set up and connected to the peer link before
Procedure
displayed.

BSC6910 UMTS
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to SCTP Link
----End
8.3.6.10 Monitoring Logical Port Traffic

This section describes how to monitor traffic on a specified logical port. You can
set Monitor Type to Port or QoS for this function. If Monitor Type is set to Port,
the real-time traffic is shown in the monitoring result. If Monitor Type is set to
QoS, the QoS-specific TX traffic on the logical port is shown in the monitoring
result. Based on the traffic statistics on the logical port, you can check the packet
loss on the logical port and locate the fault. In addition, you can check whether
the monitored traffic is consistent with the actual traffic on the port, check the
port utilization, and check whether the bandwidth is sufficient. The check result
provides reference for increasing the bandwidth configured on the logical port.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Logical
Port and set other parameters according to actual situations. Then, click Submit
to start the monitoring task in the WebLMT dialog box that is displayed.
----End
8.3.6.11 Monitoring OAM Channel Traffic

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

BSC6910 UMTS
8.3.6.12 Monitoring Traffic on Non-Channelized ATM Optical Port

This section describes how to monitor traffic on a specified non-channelized ATM
optical port in real time. The monitoring result is displayed in lists and charts.
Based on the traffic statistics on the non-channelized ATM optical ports at both
ends, you can check the IE loss, locate the fault, and evaluate transport network
quality. In addition, you can check whether the monitored traffic is consistent with
the actual traffic on the port and whether the bandwidth is sufficient. The check
result provides reference for increasing the bandwidth.
Context
NOTICE
The specified non-channelized ATM optical port must be connected to the peer
port using links.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Non-
Channelized ATM Optical Port and set other parameters according to actual
situations. Then, click Submit to start the monitoring task in the WebLMT dialog
----End
8.3.6.13 Monitoring IP Pool PM Link Traffic

This section describes how to monitor PM link traffic in a specified IP pool in real
time. The monitoring result is displayed in lists and charts. Based on the PM link
traffic statistics on the IP pool at the TX and RX ends, you can check the packet
loss and locate transmission disconnection or intermittent disconnection in IP pool
networking mode. In addition, you can observe PM link traffic and check whether
link congestion occurs.
Context
NOTICE
The PM link to be monitored in the IP pool must be activated.

BSC6910 UMTS
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL
PM and set other parameters according to actual situations. Then, click Submit to
----End
8.3.6.14 Monitoring Trunk Group Traffic

This section describes how to monitor traffic on a specified trunk group in real
time. The monitoring result is displayed in lists and charts. Based on the traffic
statistics of the trunk groups at both ends, you can check the IE loss, locate the
fault, and evaluate transport network quality. In addition, you can check whether
the monitored traffic is consistent with the actual traffic processed by the trunk
group and check whether the bandwidth is sufficient. The check result provides
reference for adding links.
Context
NOTICE
The trunk group to be monitored must be configured successfully.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to TRUNK
Group and set other parameters according to actual situations. Then, click Submit
----End
8.3.6.15 Monitoring Local IP Traffic in IP Pool

This section describes how to monitor traffic on a specified local port in an IP pool
in real time. The monitoring result is displayed in lists and charts. Based on the
statistics on the local port, you can locate the fault and evaluate transport
network quality. In addition, you can check the local port utilization. The check
result provides reference for migrating services on the port to prevent congestion.

BSC6910 UMTS
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPOOL
LOCAL IP and set other parameters according to actual situations. Then, click
----End
8.3.6.16 Monitoring Iur-p Link Traffic

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

This section describes how to monitor traffic on a specified 10GE port in real time.
on the 10GE port, you can check the packet loss, locate the fault, and evaluate
transport network quality. In addition, you can check whether the monitored
traffic is consistent with the actual traffic on the port, check the port usage, and
check whether the bandwidth is sufficient. The check result provides reference for
migrating services on the port to prevent congestion.

BSC6910 UMTS
Prerequisites
Context
NOTICE
The 10GE port must be configured and connected to the peer port before this task
is performed. This task is stopped if the monitored link is deleted.
Procedure
displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to 10GE and
After the monitoring task is started, a real-time monitoring window is displayed. The task name
and related parameters are displayed in the title bar of the window and the monitoring result is
displayed in lists and charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the
RX and TX traffic in bit/s.
----End
8.4 UMTS Monitoring

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

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

This section describes how to monitor the P-CPICH Ec/No and RSCP of a cell in the
active set in real time. Based on the number of cells in the active set and signal
strength of each cell, you can learn about whether the current connection is at the
edge or the center of the cell.

BSC6910 UMTS
Context
NOTICE
Before running this monitoring task, perform either of the following operations:
● Run SET UCORRMALGOSWITCH to set Handover algorithm switch. Ensure
that SOFT_HANDOVER_SWITCH is selected for this parameter.
● Run MOD UCELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE.
● There is no way to avoid that some user data such as IMSI, IMEI, TMSI,
MSISDN, and CELLID will be used during tracing. This function provides a
pseudonymous data processing method to encrypt such data as IMSI and IMEI
using irreversible HASH algorithm that provides a random key. 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 pseudonymous
function and deleting the folder that saves track records after you finish
processing data. For details about personal data description, see
BSC6900&BSC6900 UMTS personal data description.
● This task is used only to monitor connections on dedicated channels. An ongoing task is
stopped if the monitored connection is released or relocated from the dedicated channel to a
common channel. The task is restarted if the monitored connection is relocated from the
common channel to a dedicated channel.
● This task is used only to monitor the real-time data of the cells in the active set. The data of
other cells is not reported. Therefore, the monitoring results reflect the changes in the
number of cells in the active set in real time.
● A maximum of three cells in the active set can be monitored in a task.
● When entering IMSI, check whether IMSI data to be entered must be pseudonymous by
running the LST USERIDANONSWITCH command and querying User Identity
Pseudonymization Switch.
● If User Identity Pseudonymization Switch is ON, the pseudonymous policy is enabled,
and pseudonymous IMSI data must be entered in IMSI. The pseudonymous IMSI data is
the IMSI data encrypted by the HMACUtil using the cipher key.
● If User Identity Pseudonymization Switch is OFF, the pseudonymous policy is disabled,
and user IMSI data is directly entered in IMSI.
● Change the pseudonymous policy and cipher key on the U2020 by choosing Trace and
Maintenance > Signaling Trace > Pseudonymization Policy Management >
Pseudonymization Key Management or Trace and Maintenance > Monitor > Signaling
Trace > Pseudonymization Policy Management > Pseudonymization Key Management.
For details, see U2020 Fault Management User Guide.
● If you change the pseudonymous policy or cipher key of a started tracing task, you need to
restart the tracing task. Otherwise, the tracing task becomes invalid.
● For details about how to obtain the HMACUtil, contact Huawei technical support.
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring >
Connection Performance Monitoring. The Connection Performance Monitoring

BSC6910 UMTS
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to
PCPICH Ec/No RSCP and set other parameters according to actual situations.
Then, click Submit to start the monitoring task in the WebLMT dialog box that is
displayed.
is displayed in the title bar of the window and the monitoring result is displayed in lists and
charts.
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents
the reported P-CPICH Ec/No (unit: dB) and RSCP (unit: dBm).
● RSCP refers to the received signal code power measured on a P-CPICH. The reference point
for RSCP measurement is at the antenna connector of a UE. If the P-CPICH uses transmit
diversity, you need to measure the RSCP of each antenna and sum up all of the RSCP values
to obtain the total RSCP of the P-CPICH.
● Ec/No refers to the ratio of received energy per chip to noise spectral density. Like RSCP/RSSI,
Ec/No is also measured on the P-CPICH. The reference point for Ec/No measurement is also
at the antenna connector of the UE. If the P-CPICH uses transmit diversity, you need to
measure the Ec/No of each antenna and sum up all of the Ec/No values to obtain the total
Ec/No of the P-CPICH.
----End
8.4.1.2 Monitoring SIR Values of the Uplink RLSs

This section describes how to monitor the signal-to-interference ratio (SIR) values
of the uplink radio link sets (RLSs) used by a UE in real time. By performing this
task, you can learn about the uplink radio link quality and quality variations.
Context
A task can be started for a UE. The monitoring result includes the number of cells in the
active set and the signal strength of each cell. Based on the monitoring result, you can
know whether the current connection is at the edge or the center of the cell.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL
SIR and set other parameters according to actual situations. Then, click Submit to

BSC6910 UMTS
charts. The monitoring result can reflect the changes in the number of the RLSs in real time.
In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents
the reported SIR of the UL RLSs (unit: dB).
The SIR is calculated using the formula (RSCP/ISCP) x SF, where:
● RSCP is short for Received Signal Code Power and reflects the received power on one code.
● ISCP is short for Interference Signal Code Power and reflects interference to the received
signal. Only the non-orthogonal interference is measured for ISCP.
● SF is short for the spreading factor of a DPCCH.
This task is performed on the DPCCH after radio links are combined on the NodeB. In
compressed mode, the SIR is not measured during the transmit intervals. The NodeB reports the
measured uplink SIR values to the BSC6910.
----End
8.4.1.3 Monitoring the Outer Loop Power Control

This section describes how to monitor parameter values during outer loop power
control. Based on the current service type, the parameters include Number of
Total Blocks, Number of Error Blocks, OLPC UL BLER, OLPC UL BER, OLPC BER
Filter, OLPC SIR Target, OLPC SIR Target High Precision, E-DCH Average
Transmission Number, Total Number of Transmission Times, Total Number of
Discarded PDUs, Total Number of PDUs, and E-DCH Residual BLER.
Procedure
OLPC and set other parameters according to actual situations. Then, click Submit

BSC6910 UMTS
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.
charts. In charts, the X-coordinate represents the hour: minute: second. Two charts are used to
describe five monitoring items.
● The first chart shows the output interface of the OLPC SIR target value, OLPC UL BLER,
and OLPC UL BER. The left Y coordinate represents OLPC SIR Target (range: -10 to 18;
unit: dB). The right Y coordinate represents OLPC UL BLER (range: 0 to 1; unit: none) and
OLPC UL BER (range: 0 to 1; unit: none).
● The second chart shows the output interface of E-DCH Average Transmission Number
and E-DCH Residual BLER. The left Y coordinate represents E-DCH Average Transmission
Number (default value range: 0 to 16; unit: none). The coordinate value range can be
dynamically adjusted based on the actual value. The right Y coordinate represents E-DCH
Residual BLER (range: 0 to 1; unit: none).
----End
8.4.1.4 Monitoring the SIR Error Values of UL RLSs

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

BSC6910 UMTS
charts.
reported SIR error values (SIRerror) of the UL RLSs.
● SIRerror (unit: dB) is reported from the NodeB to the BSC6910. The formula is as follows:
SIRerror = SIR - SIRtarget_ave.
● Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to the
time for calculating the SIR in the preceding formula for calculating SIRerror.
● In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave is not calculated during
transmission intervals. The average of SIRtarget is an arithmetical average. The unit of
SIRtarget_ave is dB.
----End
8.4.1.5 Monitoring DL Code TX Power

This section describes how to monitor the DL code TX power of each radio link of
the current connection in real time. By performing this task, you can analyze the
DL power consumption. If the DL code TX power increases and even approximates
to the maximum value configured in the signaling message, DL quality
deteriorates.
Context
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL
Tx Code Power and set other parameters according to actual situations. Then,
click Submit to start the monitoring task in the WebLMT dialog box that is
displayed.

BSC6910 UMTS
charts. The monitoring results reflect the changes in the number of the radio links involved in
the current connection in real time.
reported DL code TX power (unit: dBm).
Code TX power refers to the NodeB TX power on one channelization code that is on one given
scrambling code on one given carrier. The DL code TX power can be measured on the DPCCH of
any radio link outgoing from the UTRAN and indicates the pilot bit power of the DPCCH.
In compressed mode, the TX power measurement should cover all timeslots, including those
during the transmit intervals. The reference point for measurement is at the antenna connector.
If transmit diversity is used, the DL code TX power is the total of the code TX powers of all
antennas.
----End
8.4.1.6 Monitoring UE TX Power

This section describes how to monitor the TX power of a UE. By performing this
task, you can analyze the UL radio link quality. If the UE TX power increases and
even reaches the limit of the UE capability, the UL radio link quality deteriorates.
Context
UE TX power refers to the transmit power of a UE on a carrier. The reference point
for measurement of the UE TX power is at the antenna connector of the UE.

Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UE
Tx Power and set other parameters according to actual situations. Then, click
charts.
reported UE TX power (unit: dBm).
----End

BSC6910 UMTS
8.4.1.7 Monitoring UL Traffic Volume

This section describes how to monitor the UL traffic volume, that is, the buffered
data volume at the UE side, on the current connection in real time. By performing
this task, you can analyze transmission performance of UL traffic volume. The UL
traffic volume on transport channels is measured by the UE and reported to the
BSC6910.
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data
bytes to be transmitted or retransmitted from the RLC entity on a logical channel.
If RLC is in AM mode, the BO value includes the control Protocol Data Unit (PDU)
and the PDU outside the transmit window, excluding the PDUs for which no ACK is
received.
This task can be used to monitor the connections of PS interactive and

background services on common channels or dedicated channels. As specified in
protocols, UEs cannot report the UL traffic volume of HSUPA services to the RNC.
Therefore, the UL traffic volume is not displayed in the LMT monitoring window.
Procedure
Traffic Vol and set other parameters according to actual situations. Then. click
charts.
reported UL traffic volume on the UL physical channel (unit: byte).
----End
8.4.1.8 Monitoring DL Traffic Volume

This section describes how to monitor DL traffic volume, that is, the buffered data
volume on the MSC side, on the current connection in real time. By performing
this task, you can analyze transmission performance of DL traffic volume. The DL
traffic volume on transport channels is measured on the BSC6910.
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data
bytes to be transmitted or retransmitted from the RLC entity on a logical channel.
If RLC is in AM mode, the BO value includes the control Protocol Data Unit (PDU)

BSC6910 UMTS
and the PDU outside the transmit window, excluding the PDUs for which no ACK is
received.
background services on common channels or dedicated channels.
Procedure
Traffic Vol and set other parameters according to actual situations. Then, click
charts.
reported DL traffic volume (unit: byte).
----End
8.4.1.9 Monitoring UL Throughput and Bandwidth

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

BSC6910 UMTS
displayed.
charts.
reported UL throughput and UL bandwidth (unit: bit/s).
● Observe the variations of the UL throughput and bandwidth during verification of dynamic
channel configurations. If the UL bandwidth varies with the UL throughput, dynamic channel
configuration is normal.
● If dynamic channel configuration is not used, observe the variation of UL throughput to
verify service source rate variations.
----End
8.4.1.10 Monitoring DL Throughput and Bandwidth

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

BSC6910 UMTS
charts.
reported DL throughput and DL bandwidth (unit: bit/s).
● Observe the variations of the DL throughput and bandwidth during verification of dynamic
channel configurations. If the DL bandwidth varies with the DL throughput, dynamic channel
configuration is normal.
● If dynamic channel configuration is not used, observe the variation of DL throughput to
verify service source rate variations.
----End
8.4.1.11 Monitoring Handover Delay

This section describes how to monitor the handover delay.
Context
Handover delay refers to the time taken by each handover. During this period of
time, the BSC6910 makes a handover decision, initiates the handover (including
the soft handover and the hard handover), and completes the handover.
This task is used only to monitor the handover delay of a UE in the CELL_DCH
state. An ongoing task is stopped if the UE transits from the CELL_DCH state to
the CELL_FACH state or idle mode. The task is restarted if the UE transits from the
CELL_FACH state or idle mode back to the CELL_DCH state.
A maximum of five tasks can be simultaneously started on the LMT. This task can
monitor the delay of an intra-frequency or inter-frequency handover but not an
inter-RAT handover.
Procedure
Handover Delay and set other parameters according to actual situations. Then,
displayed.
Monitoring Description
Results
HO Delay(ms) Time taken by a handover
HO Interval(ms) Difference between the end time of the preceding

handover and the end time of the current handover

BSC6910 UMTS
charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate represents
handover delay and interval (unit: ms).
----End
8.4.1.12 Monitoring DL Transport Channel BLER

This section describes how to monitor block error rate (BLER) variations on all
transport channels. By performing this task, you can analyze the DL radio link
quality. If the BLER of the DL transport channel increases, the DL radio link quality
deteriorates. If the BLER decreases, the DL radio link quality improves.
Context
The BLER of the DL transport channel is measured on the UE and used for outer
loop power control.

Procedure
BLER and set other parameters according to actual situations. Then, click Submit
charts. The monitoring results reflect the changes in the number of traffic transport channels in
real time. The number of signaling transport channels is always 1.
reported BLER of the DL transport channel (unit: %).
When Monitor Item is DL BLER, Monitor Period (s) must be set to 2s or a greater value.
----End
8.4.1.13 Monitoring AMR Mode

This section describes how to monitor the variation in the configured AMR rate in
real time.

BSC6910 UMTS
Context
This task can be started only if the traced UE is processing AMR services.
The narrowband AMR has eight available rates, that is, eight AMR modes: 12.2
kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75
kbit/s.
The wideband AMR has nine available rates, that is, nine AMR modes: 23.85 kbit/s,
23.05 kbit/s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85
kbit/s, and 6.60 kbit/s.
Procedure
AMR Mode and set other parameters according to actual situations. Then, click
charts.
maximum AMR rate in the uplink and downlink (unit: kbit/s).
----End
8.4.1.14 Monitoring AMR EVQI

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

BSC6910 UMTS
Context
Perform the following operations before stating this monitoring task:

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

This section describes how to monitor the single-ended perceptual evaluation of
listening quality (PSPELQ) of the ongoing wideband or narrowband AMR services.
The monitoring results are used to analyze the voice quality of wideband,
narrowband, or always HD voice services. If the PSPELQ value of AMR services
increases, the voice quality improves. If the PSPELQ value of AMR services
decreases, the voice quality deteriorates. This monitoring task can be started only
if the traced UE is processing AMR services.

BSC6910 UMTS
Context
Perform the following operations before stating this monitoring task:

● Run the MML command SET UDEUCFGDATA with AlwaysHDVoicePSPELQMeaSw set to
ON.
● (Optional) Run the MML command SET UALWAYSHDVOICE with AlwaysHDVoiceEcN0Thld
set to 0 and AlwaysHDVoiceSw set to ON to evaluate the always HD voice quality.
Procedure
AMR PSPELQ and set other parameters as required. Then, click Submit to start
the monitoring task in the WebLMT dialog box that is displayed.
After the monitoring task is started, a real-time monitoring window is displayed. The task
name is displayed in the title bar of the window and the monitoring result is displayed in
lists and charts.
In charts, the X-coordinate represents the hour:minute:second. The Y-coordinate represents
the maximum UL and DL data rates of AMR services (unit: kbit/s).
As specified in protocols, the PSPELQ value ranges from 1 to 5. If the PSPELQ value is 0, the
evaluation resources have been occupied. In the performance monitoring window of the
LMT, the PSPELQ value is 100 times the actual value (ranging from 0 to 500).
----End
8.4.2 Monitoring Cell Performance

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

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

BSC6910 UMTS
Procedure
Cell Performance Monitoring. The Cell Performance Monitoring dialog box is
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to PCPICH
TxPower and set other parameters according to actual situations. Then, click
charts.
P-CPICH power (unit: dBm).
----End
8.4.2.2 Monitoring Cell UL RTWP

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

BSC6910 UMTS
8.4.2.3 Monitoring DL Carrier TX Power in a Cell

This section describes how to monitor the DL carrier transmit (TX) power of a
specified cell. By performing this task, you can observe the DL load in real time.
The DL TX power of a cell is measured and reported by the NodeB.
Context
The CAC procedure uses the ratio of the DL carrier TX power to the maximum TX
power of the cell to measure the cell DL load. When setting up a cell, you can run
ADD UCELLSETUP to set the maximum TX power. After the cell is set up, you can
run MOD UCELL to modify it.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell DL
Carrier TX Power and set other parameters according to actual situations. Then,
displayed.
charts.
ratio of the DL carrier TX power to the maximum TX power of the cell (unit: %).
----End
8.4.2.4 Monitoring Number of UEs in a Cell

This section describes how to monitor the number of UEs on common channels,
dedicated channels, HSDPA channels, and HSUPA channels in a specified cell. By
performing this task, you can learn about UE distribution in cells.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell User
Number and set other parameters according to actual situations. Then, click

BSC6910 UMTS
charts.
number of UEs in a cell.
HSDPA User Number and HSUPA User Number are measured during user access while DCH
User Number is measured after user access. Therefore, the value of HSDPA User Number or
HSUPA User Number may be greater than that of DCH User Number.
UL L2 Enhanced User Number measures only the number of users enabled with UL Layer 2
enhancement in the CELL_DCH state. Therefore, the value of UL L2 Enhanced User Number may
be less than that of E-RACH User Number.
DL L2 Enhanced User Number measures only the number of users enabled with DL Layer 2
enhancement in the CELL_DCH state. Therefore, the value of DL L2 Enhanced User Number may
be less than that of EFACH User Number.
----End
8.4.2.5 Monitoring Node Synchronization

This section describes how to monitor the time difference between RNC Frame
Number (RFN) and NodeB Frame Number (BFN) of a specified cell and the time
taken for node synchronization. By performing this task, you can observe the drift
between the RFN and BFN in real time. If the difference between RFN and BFN
varies too rapidly, transmission problems occur between the BSC6910 and the
NodeB.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Node Sync
charts.
time difference between RFN and BFN and the time taken by the NodeB to complete node
synchronization (unit: ms).
----End
8.4.2.6 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

BSC6910 UMTS
determine the prediction accuracy of the UL CAC algorithm. The monitoring

results are periodically reported and reported in real time when UEs access the
cell.
Context
The methods for measuring the cell load vary with CAC algorithms (CAC
algorithm 1 and CAC algorithm 2). You can run the MOD UCELLALGOSWITCH
command to set the UL CAC algorithm of a cell and run the LST
UCELLALGOSWITCH command to query the UL CAC algorithm of a cell.
● CAC algorithm 1 uses the UL load factor to measure the UL load. The UL load
factor is calculated using the following formula: UL load factor = 1 - Cell
background noise/UL RTWP. You can run the command ADD UCELLCAC or
MOD UCELLCAC to set the cell background noise.
● CAC algorithm 2 uses the ratio of the current number of UL equivalent UEs to
the maximum number of UL equivalent UEs to measure the cell load. By
default, algorithm 2 is used.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to UL CAC
Monitor and set other parameters according to actual situations. Then, click
charts.
predicted values and measured values of the load (unit: %).
----End
8.4.2.7 Monitoring DL CAC

This section describes how to monitor the DL call admission control (CAC)
procedure of a specified cell. By performing this task, you can observe the
variation in the predicted values and measured values of the DL load and
determine the prediction accuracy of the DL CAC algorithm. The monitoring
results are periodically reported and reported in real time when UEs access the
cell.
Context
The methods for measuring the cell load vary with CAC algorithms (CAC
algorithm 1 and CAC algorithm 2). You can run the MOD UCELLALGOSWITCH
command to set the DL CAC algorithm of a cell and run the LST
UCELLALGOSWITCH command to query the DL CAC algorithm of a cell.

BSC6910 UMTS
● CAC algorithm 1 uses the ratio of the DL carrier TX power to the maximum
TX power of the cell to measure the DL load of the cell. By default, algorithm
1 is used. The maximum TX power is a constant and set using the ADD
UCELLSETUP command.
● CAC algorithm 2 uses the ratio of the current number of DL equivalent UEs to
the maximum number of DL equivalent UEs.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to DL CAC
Monitor and set other parameters according to actual situations. Then, click
charts.
predicted values and measured values of the load (unit: %).
----End
8.4.2.8 Monitoring the Number of UL Equivalent UEs

This section describes how to monitor the number of UL equivalent UEs in a
specified cell. By performing this task, you can observe the variation in the number
of UL equivalent UEs. The monitoring results are periodically reported and
reported in real time when UEs access the cell.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to UL Total
Equivalent User Number and set other parameters according to actual situations.
displayed.

BSC6910 UMTS
charts.
predicted and measured number of UL equivalent UEs.
----End
8.4.2.9 Monitoring the Number of DL Equivalent UEs

This section describes how to monitor the number of DL equivalent UEs in a
specified cell. By performing this task, you can observe the variation in the number
of DL equivalent UEs. The monitoring results are periodically reported and
reported in real time when UEs access the cell.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to DL Total
Equivalent User Number and set other parameters according to actual situations.
displayed.
charts.
predicted and measured number of DL equivalent UEs.
----End
8.4.2.10 Monitoring the Cell Code Tree

This section describes how to monitor the DL channel OVSF code tree of a
specified cell. By performing this task, you can observe the code usage in real
time.
Procedure
Step 1 On the LMT main page, click Monitor on the LMT main page. The Monitor tab
page is displayed.
displayed.

BSC6910 UMTS
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell Code
Tree Monitor and set other parameters according to actual situations. Then, click
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
8.4.2.11 Monitoring the Minimum Power Required for the HS-DSCH

This section describes how to monitor the minimum power required for the HS-
DSCH in a specified cell. By performing this task, you can observe the ratio of the
minimum required power to the maximum TX power on the HS-DSCH in the cell.
Context
When this task is performed, if HSDPA_GBP_MEAS is set to 0 for the cell, the minimum
power required for the HS-DSCH is not reported. HSDPA_GBP_MEAS specifies whether to
perform an HSDPA GBR measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSDPA GBP Meas
Algorithm. If the value is OFF, run the MOD UCELLALGOSWITCH command to set it to 1.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Min Power Requirement and set other parameters according to actual situations.
displayed.
charts.
ratio of the required power to the maximum TX power of the cell (unit: ‰).
----End
8.4.2.12 Monitoring the HS-DSCH Bit Rate

This section describes how to monitor the HS-DSCH bit rate of a specified cell. By
performing this task, you can observe the variation in the HS-DSCH transmission
rate in real time.

BSC6910 UMTS
Context
When this task is performed, if HSDPA GBP Meas Algorithm is set to 0, the HS-DSCH bit
rate of the cell is not reported. HSDPA GBP Meas Algorithm specifies whether to perform
an HSDPA PBR measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSDPA GBP Meas
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Provided Bitrate and set other parameters according to actual situations. Then,
displayed.
charts.
bit rate (unit: bit/s).
----End
8.4.2.13 Monitoring the E-DCH Bit Rate

This section describes how to monitor the bit rate on an enhanced dedicated
channel (E-DCH) for HSUPA services. By performing this task, you can observe the
variation in the E-DCH transmission rate in real time.
Context
When this task is performed, if HSUPA GBP Meas Algorithm is set to 0, the E-DCH bit rate
of the cell is not reported. HSUPA GBP Meas Algorithm specifies whether to perform an
HSUPA PBR measurement.
Run the LST UCELLALGOSWITCH command to query the value of HSUPA GBP Meas
Procedure
displayed.

BSC6910 UMTS
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to E-DCH
Provided Bitrate and set other parameters according to actual situations. Then,
displayed.
charts.
bit rate (unit: bit/s).
----End
8.4.2.14 Monitoring Cell UL Throughput

This section describes how to monitor the UL throughput of a cell. Throughput
refers to the maximum rate that a device can reach without discarding frames.
Procedure
displayed.
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell
UL Throughput and set other parameters according to actual situations. Then,
displayed.
charts.
UL throughput of the cell.
----End
8.4.2.15 Monitoring Cell DL Throughput

This section describes how to monitor the DL throughput of a cell. Throughput
refers to the maximum rate that a device can reach without discarding frames.
Procedure
Step 1 On the LMT main page, click Monitor on the LMT main page. The Monitor tab
page is displayed.
displayed.

BSC6910 UMTS
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell
DL Throughput and set other parameters according to actual situations. Then,
displayed.
charts.
DL throughput of the cell.
----End
8.4.2.16 Monitoring the Number of ACK Messages per Second in a Cell

This section describes how to monitor the number of ACK messages that are sent
from the AICH to UEs on the RACH and E-RACH in a specified cell. By performing
this task, you can observe random access times in the cell in real time.
Context
The number of ACK messages is reported to the RNC through common
measurement messages over the Iub interface.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Number of
acknowledged random access and set other parameters according to actual
situations. and then click Submit to start the monitoring task in the WebLMT
● You can run the ADD UCELLALGOSWITCH and MOD UCELLALGOSWITCH commands
to set whether to report the number of ACK messages per second in a cell. This function
is disabled by default.
● You can run the SET ULDM command to set the report interval and filter window size.
● After the monitoring task is started, a real-time monitoring window is displayed. The
task name is displayed in the title bar of the window and the monitoring result is
displayed in lists and charts. In charts, the X-coordinate represents hour: minute: second.
The Y-coordinate represents the number of ACK messages per second in a cell.
----End
8.4.2.17 Monitoring Cell Credit

This section describes how to monitor the credit conditions of a local cell, a local
cell group, and a NodeB. By performing this task, the BSC6910 determines
whether a UE can access the network.

BSC6910 UMTS
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell Credit
----End
Result
The following table lists the items shown in the monitoring result.
When the CE Overbooking feature is enabled, the RNC performs admission control based on the
values of Adjusted UL Local Cell Group Credit usage (Permillage) and Adjusted UL NodeB
Credit used. The following items are not involved in admission control: UL local cell Credit
used, UL local cell group Credit used, and UL NodeB Credit used.
Monitoring Item Description
DL local cell total Credit Downlink credit capability of a local cell. The
NodeB reports the item value to the RNC using a
message.
UL local cell total Credit Uplink credit capability of a local cell. The NodeB
reports the item value to the RNC using a message.
DL local cell group total Downlink credit capability of a local cell group. The
Credit NodeB reports the item value to the RNC using a
message.
UL local cell group total Uplink credit capability of a local cell group. The
Credit NodeB reports the item value to the RNC using a
message.
DL NodeB total Credit Downlink credit capability of a NodeB. The NodeB

UL NodeB total Credit Uplink credit capability of a NodeB. The NodeB

DL local cell Credit used Downlink credit used by a local cell, that is, the
total downlink credit used by all UEs in the local
cell.
UL local cell Credit used Uplink credit used by a local cell, that is, the total
uplink credit used by all UEs in the local cell.
DL local cell group Credit Downlink credit used by a local cell group, that is,
used the total downlink credit used by all UEs in the
local cell group.

BSC6910 UMTS
Monitoring Item Description
UL local cell group Credit Uplink credit used by a local cell group, that is, the
used total uplink credit used by all UEs in the local cell
group.
DL NodeB Credit used Downlink credit used by a NodeB, that is, the total
downlink credit used by all UEs served by the
NodeB.
UL NodeB Credit used Uplink credit used by a NodeB, that is, the total
uplink credit used by all UEs served by the NodeB.
Adjusted UL Local Cell The NodeB reports the actually used uplink credit
Group Credit usage of a local cell group per second. The RNC divides
(Permillage) this value by the value of UL local cell group total
Credit and converts the specific value into a
permillage.
Adjusted UL NodeB Credit Uplink credit actually used by a NodeB. The NodeB
used reports the item value to the RNC per second.
After the monitoring task is started, a real-time monitoring window is displayed.

The task name is displayed in the title bar of the window and the monitoring
result is displayed in lists and charts.
In charts, the X-coordinate represents the hour: minute: second. The Y-coordinate
represents the values of Local Cell Credit and Local Cell Group/NodeB Total
Credit of the cell.
8.4.2.18 Monitoring the FDPCH SYMBOL

This section describes how to monitor the F-DPCH SYMBOL usage, including the
F-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied
SYMBOL.
Context
The F-DPCH carries the Transport Power Control (TPC) information of HSDPA
services and uses the spreading factor SF256.
Procedure
displayed.
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to FDPCH
SYMBOL monitoring and set other parameters according to actual situations.
displayed.

BSC6910 UMTS
charts.
● In the FDPCH SYMBOL monitoring window, you can view the usage of the SYMBOL
corresponding to the F-DPCH code. The numbers in the grids indicate the timeslot formats.
----End
8.4.3 Monitoring System Resources

This section describes how to monitor the licensed Erlang value and the PS user
plane throughput of the system in real time.
Procedure
System Resource Monitoring. The System Resource Monitoring dialog box is
displayed.
Step 3 In the System Resource Monitoring dialog box, set the parameters according to
actual situations, and click Submit to start the monitoring task in the WebLMT
usage of the license. (Unit: Erl and kbit/s)
----End
8.4.4 Monitoring Iur-p Delay

This section describes how to monitor and specify the delay of an Iur-p link
between two external nodes. By performing this task, you can observe and
determine whether the Iur—p link delay is normal in real time.
Context
● When RNC in Pool Load Sharing is enabled, the Iur-p one-way transmission
delay must be less than or equal to 10 ms.
● When RNC in Pool Node Redundancy is enabled, the Iur-p one-way
transmission delay must be less than or equal to 100 ms.
● If the delay exceeds either of the preceding values, the Iur-p delay is too large.
Procedure

BSC6910 UMTS
Iur-p Monitoring. The Iur-p Monitoring dialog box is displayed.
Step 3 In the Iur-p Monitoring dialog box, set the parameters according to actual
situations, and click Submit to start the monitoring task in the WebLMT dialog
Iur- delay. (Unit: 0.125 ms)
----End

BSC6910 UMTS
LMT User Guide 9 Device Panel
9 Device Panel
This chapter describes how to manage the BSC6910 using the device and
emulation panels. You can use these panels to query information about boards,
ports, links, and alarms.
9.1 Device Panel Operations

This section describes device panel operations of the BSC6910, including how to
start and use the device panel and how to query the board status.
9.2 Emulation Panel Operations
This section describes the operations of the BSC6910 emulation panel. By
performing this task, you can learn about how to start and use it, and how to
query the board status.
9.1 Device Panel Operations

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

In addition to MML commands, the LMT provides the graphical device panel to
help users maintain devices. The eGBTS does not support this function.
The device panel is automatically refreshed to show board status in real time. You
can learn about the board status based on the board indicator color and active
alarm indicators.
On the device panel, you can right-click a board in position and choose any option
from the shortcut menu to perform operations, such as querying the board status.

BSC6910 UMTS
Figure 9-1 Device Panel
Alarm indicators indicate the board alarm status, and board indicator colors
indicate the board running status. For details, see the descriptions shown in the
right side of the device pane.
● If the tab page under Device Maintenance is not in full view, click . The
drop-down list is displayed. Select the required item from the drop-down list
to view the corresponding tab page.
● You can right-click the peripheral frame of a rack, and choose Refresh Shelf
from the shortcut menu to refresh the rack.
● If you select Show logical function under the color descriptions of the board,
the logic functions of boards are displayed on the device panel.
● If a BSC6910 has built-in NEs, each of the EOMUa, EOMUb, EOMUc, EGPUa
whose logical function is GASP, EGPUb whose logical function is GASP, and
interface boards on the device panel is marked with b on the lower right
corner, indicating that the built-in NEs use the board at the moment.
● When you use the mouse pointer to point to a board marked with b, the Tip
window is displayed, showing information about the built-in NEs that use this
board.
9.1.2 Starting the Device Panel

This section describes how to start the device panel.
Procedure
Step 1 On the LMT main page, click Device Maintenance. The Device Maintenance tab
page is displayed. The device panel is displayed in the BSC Device Panel tab page.
----End
9.1.3 Querying the Status of an E1/T1 Port

This section describes how to query the status of an E1/T1 port.

BSC6910 UMTS
Prerequisites
● The boards are in position.
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the
emulation panel (see 9.2.2 Starting the Emulation Panel).
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to
be queried, and choose Query E1/T1 Port Status from the shortcut menu. The
Query E1/T1 Port Status dialog box is displayed, showing detailed information
about the E1/T1 port.
----End
9.1.4 Querying the CPU Usage

Prerequisites
Context
The OMU and SAU do not support this operation.
You can query the CPU usage using menus or MML commands.
Procedure
● Using menus
a. 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).
b. Right-click a board in position in the device panel or emulation panel,
and choose CPU Usage Query from the shortcut menu. The CPU Usage
window is displayed, showing the real-time CPU usage.
a. 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.
Context
You can query the clock status of a BSC board using menus or MML commands.
Procedure
● Using menus (1)

BSC6910 UMTS
a. Open the device panel (see 9.1.2 Starting the Device Panel) or open the
and choose Query BSC Board Clock Status from the shortcut menu. The
Query BSC Board Clock Status dialog box is displayed.
c. In the Query BSC Board Clock Status dialog box, set the parameters
according to actual situations, and click Query.
● Using menus (2)
a. On the LMT main page, click Device Maintenance. The Device
Maintenance tab page is displayed.
b. On the BSC Maintenance tab page, choose BSC Maintenance >
Maintain Device > Query BSC Board Clock Status. The Query BSC
Board Clock Status dialog box is displayed.
Figure 9-2 Query results of BSC Board Clock Status

a. Run the DSP CLK command to query the board clock status.
----End
9.1.6 Querying the BSC Board Information

This section describes how to query the status of a BSC board.
Prerequisites
Context
You can query the status of a board using menus or MML commands.

BSC6910 UMTS
Procedure
● Using menus (1)
a. Start the device panel (see 9.1.2 Starting the Device Panel) or start the
and choose Query BSC Board Information from the shortcut menu. The
Query BSC Board Information dialog box is displayed, showing the
detailed board information.
● Using menus (2)
Maintain Device > Query BSC Board Information. The Query BSC
Board Information dialog box is displayed.
c. In the Query BSC Board Information dialog box, set the parameters
Figure 9-3 Query results of board status

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

This section describes how to reset a board. The admin, administrator-level,
operator-level, user-level, and authorized custom-level users can perform this
operation.
Prerequisites

BSC6910 UMTS
Context
NOTICE
● If the standby board is not available or is faulty, resetting the board will
interrupt the ongoing services. Therefore, perform this operation with caution.
● Resetting the board may affect the ongoing services. Therefore, you are advised
to perform this operation during off-peak hours, for example, in the early
morning.
● Resetting the Board

Board reset is mandatory during software upgrade and software loading.
Board reset will reload the programs and data files. If the active board resets
and the standby board is running properly, services processed by the active
board will be switched over to the standby board, and then the standby board
(the original active board) resets after the switchover. If an SCUb board resets
while its standby board is not available or is faulty, the entire subrack resets.
Procedure
● Using menus (1)
and choose Reset BSC Board from the shortcut menu.
c. In the Reset BSC Board dialog box, set the parameters according to
actual situations, and click Reset.
● Using menus (2)
Maintain Device > Reset BSC Board. The Reset BSC Board dialog box is
displayed.
actual situations, and click Reset to reset the board. The operation result
is displayed, as shown in Figure 1.

BSC6910 UMTS
Figure 9-4 Resetting a board

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

This section describes how to switch over boards. When the active board is faulty,
you can switch all services from the active board to the standby board to ensure
the normal system operation. The admin, administrator-level, operator-level, user-
level, and authorized custom-level users can perform this operation.
Prerequisites
● Before you perform a board switchover, ensure that the standby board is
available and properly running without any critical or major alarms.
Context
NOTICE
● If the board switchover fails, the board configuration data is not lost but
services on the board will be interrupted. Therefore, perform this task with
caution.
● Board switchover may affect the ongoing services. Therefore, you are advised to
perform the switchover during off-peak hours, for example, in the early
morning.
● All boards configured in active/standby mode support switchover operations.
Only the active board can initiate the switchover, except the OMU board. The
OMUU board supports switchover initiated by the standby board.

BSC6910 UMTS
You can switch over a board using menus or MML commands.
Procedure
● Using menus (1)
and choose Switch BSC Board from the shortcut menu.
c. In the Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.
● Using menus (2)
Maintain Device > Switch BSC Board. The Switch BSC Board dialog box
is displayed.
c. In the Switch BSC Board dialog box, set the parameters according to
actual situations, and click Switch to switch over the boards. The
operation result is displayed, as shown in Figure 1.
Figure 9-5 Switching over boards

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

This section describes how to query the board alarm.

BSC6910 UMTS
Prerequisites
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the
Step 2 Right-click a board in position in the device panel or the emulation panel, and
choose Query Board Alarm from the shortcut menu. The alarm information is
displayed.
----End
9.2 Emulation Panel Operations

This section describes the operations of the BSC6910 emulation panel. By
performing this task, you can learn about how to start and use it, and how to
query the board status.
9.2.1 Introduction to the Emulation Panel

The LMT provides the emulation panel for each subrack. The emulation panel has
the same ports as those of the real subrack and helps you learn about the board
port status.
The emulation panel displays the operating status of the ports on each board and
provides right-click menus, as shown in Figure 9-6.

BSC6910 UMTS
Figure 9-6 Emulation panel
The emulation panel provides the following functions:

● Displays the operating status of the device.
● Provides right-click menus for users to query the board status and port status.
● Uses the mark b to show which board is used by the built-in NE.
● Uses the Tip window to show the information about built-in NE that occupies
resources of boards marked with b.
9.2.2 Starting the Emulation Panel

This section describes how to start the emulation panel.
Procedure
page is displayed.
Step 2 Click BSC6910 under Device Navigation Tree. The BSC Device Panel is displayed
on the right pane.
Step 3 Select the corresponding rack and double-click the peripheral of the subrack to
view the emulation panel of a subrack, as shown in Figure 9-7.

BSC6910 UMTS
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
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to
be queried, and choose Query E1/T1 Port Status from the shortcut menu. The
Query E1/T1 Port Status dialog box is displayed, showing detailed information
about the E1/T1 port.
----End
9.2.4 Querying the CPU Usage

Prerequisites

BSC6910 UMTS
Context
The OMU and SAU do not support this operation.
You can query the CPU usage using menus or MML commands.
Procedure
● Using menus
a. 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).
and choose CPU Usage Query from the shortcut menu. The CPU Usage
window is displayed, showing the real-time CPU usage.
a. 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.
Context
You can query the clock status of a BSC board using menus or MML commands.
Procedure
● Using menus (1)
a. Open the device panel (see 9.1.2 Starting the Device Panel) or open the
and choose Query BSC Board Clock Status from the shortcut menu. The
Query BSC Board Clock Status dialog box is displayed.
● Using menus (2)
Maintain Device > Query BSC Board Clock Status. The Query BSC
Board Clock Status dialog box is displayed.

BSC6910 UMTS
Figure 9-8 Query results of BSC Board Clock Status

a. Run the DSP CLK command to query the board clock status.
----End
9.2.6 Querying the BSC Board Information

This section describes how to query the status of a BSC board.
Prerequisites
Context
You can query the status of a board using menus or MML commands.
Procedure
● Using menus (1)
and choose Query BSC Board Information from the shortcut menu. The
Query BSC Board Information dialog box is displayed, showing the
detailed board information.
● Using menus (2)
Maintain Device > Query BSC Board Information. The Query BSC
Board Information dialog box is displayed.
c. In the Query BSC Board Information dialog box, set the parameters

BSC6910 UMTS
Figure 9-9 Query results of board status

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

This section describes how to reset a board. The admin, administrator-level,
operator-level, user-level, and authorized custom-level users can perform this
operation.
Prerequisites
Context
NOTICE
● If the standby board is not available or is faulty, resetting the board will
interrupt the ongoing services. Therefore, perform this operation with caution.
● Resetting the board may affect the ongoing services. Therefore, you are advised
to perform this operation during off-peak hours, for example, in the early
morning.
● Resetting the Board

Board reset is mandatory during software upgrade and software loading.
Board reset will reload the programs and data files. If the active board resets
and the standby board is running properly, services processed by the active
board will be switched over to the standby board, and then the standby board
(the original active board) resets after the switchover. If an SCUb board resets
while its standby board is not available or is faulty, the entire subrack resets.

BSC6910 UMTS
Procedure
● Using menus (1)
and choose Reset BSC Board from the shortcut menu.
actual situations, and click Reset.
● Using menus (2)
Maintain Device > Reset BSC Board. The Reset BSC Board dialog box is
displayed.
actual situations, and click Reset to reset the board. The operation result
is displayed, as shown in Figure 1.
Figure 9-10 Resetting a board

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

This section describes how to switch over boards. When the active board is faulty,
you can switch all services from the active board to the standby board to ensure
the normal system operation. The admin, administrator-level, operator-level, user-
level, and authorized custom-level users can perform this operation.

BSC6910 UMTS
Prerequisites
● Before you perform a board switchover, ensure that the standby board is
available and properly running without any critical or major alarms.
Context
NOTICE
● If the board switchover fails, the board configuration data is not lost but
services on the board will be interrupted. Therefore, perform this task with
caution.
● Board switchover may affect the ongoing services. Therefore, you are advised to
perform the switchover during off-peak hours, for example, in the early
morning.
● All boards configured in active/standby mode support switchover operations.
Only the active board can initiate the switchover, except the OMU board. The
OMUU board supports switchover initiated by the standby board.
You can switch over a board using menus or MML commands.
Procedure
● Using menus (1)
and choose Switch BSC Board from the shortcut menu.
c. In the Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.
● Using menus (2)
Maintain Device > Switch BSC Board. The Switch BSC Board dialog box
is displayed.
c. In the Switch BSC Board dialog box, set the parameters according to
actual situations, and click Switch to switch over the boards. The
operation result is displayed, as shown in Figure 1.

BSC6910 UMTS
Figure 9-11 Switching over boards

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

This section describes how to query the board alarm.
Prerequisites
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the
Step 2 Right-click a board in position in the device panel or the emulation panel, and
choose Query Board Alarm from the shortcut menu. The alarm information is
displayed.
----End
9.2.10 Querying the FE/GE/10GE Port Status

This section describes how to query the FE/GE/10GE port status.
Prerequisites
Context
You can query the FE/GE/10GE port status using menus or MML commands.

BSC6910 UMTS
Procedure
● Using menus
a. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
b. On the emulation panel of the subrack, right-click the FE/GE/10GE port
to be queried, and choose Display Ethernet Port Status from the
shortcut menu. The Display Ethernet Port Status window is displayed,
showing the FE/GE/10GE port status.
– Run the DSP ETHPORT to query the FE/GE/10GE port status of interface
boards.
– Run the DSP GEPORT command to query the GE/10GE port status of
SCU boards.
----End
9.2.11 Querying the Optical Port Status

This section describes how to query the optical port status. AOUc/UOIc boards
support this function.
Prerequisites
Context
You can query the optical port status using menus or using MML commands.
Procedure
● Using menus
a. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
b. On the emulation panel, right-click the optical port to be queried, and
choose Query Optical Port Status and Performance from the shortcut
menu. In the Query Optical Port Status and Performance window, set
parameters according to actual situations, and click Submit to query the
optical port status.
a. Run the DSP OPT to query the optical port status.
----End
9.2.12 Querying Alarm LED Information

This section describes how to query the detailed information about alarms
indicated by an alarm LED.
Prerequisites

BSC6910 UMTS
Procedure
Step 1 Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
Step 2 On the emulation panel, right-click the alarm LED to be queried, and choose
Query Alarm Indicator Info from the shortcut menu. The Query Alarm Indicator
Info window is displayed, showing the detailed information about alarms
indicated by the alarm LED.
----End

BSC6910 UMTS
LMT User Guide 10 FMA
10 FMA
This function helps users handle network faults. It includes the following
functions: fast fault diagnosis, hierarchical delimitation, information collection,
business validation, and business query. The fast fault diagnosis and hierarchical
delimitation functions analyze faults that are not rectified within eight hours from
the fault occurrence to the current time. The faults that have been rectified will
not be re-analyzed.
● The following rights are required to perform the fast fault diagnosis and
hierarchical delimitation functions.
– Administrators
– Operators
– Users
– Customers that have permissions to execute commands in command
groups G_2 and G_9
● The following rights are required to perform the information collection
function:
– Administrators
– Operators
– Users
groups G_2, G_8, G_9, and G_NIC
● The following rights are required to perform the business validation function:
– Administrators
– Operators
– Users
groups G_1 and G_9
● The following rights are required to perform the business query function:
– Administrators
– Operators
– Users

BSC6910 UMTS

groups G_1 and G_9
● The following figure shows the fault handling process using this assistant.
Figure 10-1 Fault handling process
The following details the fault handling process:

– Determine whether services are affected.
– Use the Fault Diagnosis function to identify some faults.
– Use the Hierarchical Delimitation function to analyze faults that cannot
be quickly identified.
– Use the Information Collection function to collect logs of faults that
cannot be identified using the preceding two functions, and use the
offline analysis tool to analyze these faults.
– Rectify the faults.
– Confirm that services are recovered.
● The following figure shows the business validation process using this
assistant.
Figure 10-2 Business validation process
The following details the business validation process:

– Reconstruct the network.
– Validate the service.
– Check whether the network status is normal.
● The following figure shows the business query process using this assistant.

BSC6910 UMTS
Figure 10-3 Business query process
The following details the business query process:

– Determine whether services are affected.
– Rectify the faults.
– Query the services.
● Information Collection can be simultaneously executed with Fault Diagnosis or

Hierarchical Delimitation. However, Fault Diagnosis and Hierarchical Delimitation cannot
be executed simultaneously.
● When Information Collection is executed, do not run the COL LOG command. When
Fault Diagnosis is executed, do not run the EXP CFGMML command.
● Only one WebLMT can perform an online FMA function at a time. The FMA is
automatically started to diagnose faults in the case of a KPI exception or an alarm. In
this case, an error message indicating function conflict is displayed if you execute the
online FMA function on the LMT. You can perform this function on the LMT upon
completion of the automatic FMA startup task. If the following KPIs are abnormal: CS
RAB Setup Success Rate, PS RAB Setup Success Rate, CS Call Drop Rate, and PS Call
Drop Rate, the online FMA automatically starts the Iu interface tracing to locate faults.
● Fault diagnosis and business validation can be performed only after data in the KPI
trend chart is loaded.
10.1 Fault Overview

Fault overview provides visualized illustration of operating status and fault
information of RNC network.
10.2 Fast Fault Diagnosis
This function is used to quickly diagnose common network faults, thereby helping
users identify the faulty NE or board. This function can be used when faults occur
and persist at a site and site maintenance personnel cannot directly use the
counters, alarms, and logs for fault analysis.
10.3 Hierarchical Delimitation
This function is used to analyze faults. When faults cannot be identified using
fault diagnosis, this function can be used.
10.4 Recovery Confirmation
After service recovery solutions are implemented, onsite O&M engineers can view
on the fault summary page the operating status of the GSM and UMTS networks
to check whether a fault has been rectified. For details, see Fault Overview.
10.5 Information Collection
This function can be used to quickly and accurately collect onsite information,
thereby shortening the event recovery period.
10.6 Business Validation
This task is used to quickly check the network status, helping users quickly
determine whether the network status is normal after network reconstruction.

BSC6910 UMTS
10.7 Business Query

This task helps to quickly check fault recovery results.
10.8 Independent Rules Update
This function enables quick publishing and deployment of FMA rules.
10.9 List of Alarms for UMTS Fault Diagnosis
The following table lists the alarms for UMTS fault diagnosis.
10.1 Fault Overview

Fault overview provides visualized illustration of operating status and fault
information of RNC network.
Context
This function allows field O&M engineers to quickly obtain fault information and
start fault troubleshooting when a network fault occurs.
Procedure
Step 1 On the LMT main page, click FMA. The FMA tab page is displayed.
Step 2 In the Fault Overview window, wait for viewing the KPI trend.
● During the KPI trend loading process, Scenario Options under the Fault
Diagnosis cannot be manually selected. The dialog box will pop up if Scenario
Options is selected. Automatic selection is not complete, and manual
selection is invalid.
● When the KPI trend loading completes, default selected fault scenarios will be
displayed in Scenario Options under Fault Diagnosis.
----End
Result
Successful operation
● The KPI trend chart is displayed in the Fault Overview window.

BSC6910 UMTS
Table 10-1 Information that O&M engineers can obtain using the fault overview
function
Category Details
UMTS KPI ● Trends in the RRC

● Trends in the CS RAB
● Trends in the PS RAB
● Trends in CS Erlang
● Trends in PS throughput
● Trends in the CS call drops
● Trends in the PS call drops
● Trends in paging

BSC6910 UMTS
Category Details
KPI trend chart ● KPI and counter change trend chart

that contains three curves
illustrating KPI and counter changes
in the latest eight hours, in the
same hours on the day before, and
in the same hours on the same day
last week, respectively. The X-
coordinate represents the
measurement time (expressed in
the format of HH:MM). The Y-
coordinate represents the counter
value in units of each counter or
the KPI value in percentages.
NOTE
Performance measurement has two
states in short measurement periods:
ENABLED and DISABLED. If no
counters are measured, performance
measurement is DISABLED.
● When fault diagnosis is used to
collect performance data,
performance data generated during
a sampling period is not available if
the current measurement state is
different from that used in the
sampling period.
For example, if the measurement
state was DISABLED last
Wednesday and changed to
ENABLED this Monday, only two
curves illustrating KPI and counter
changes in the latest eight hours of
this Wednesday and in the same
hours of this Tuesday are displayed
on the trend chart, with the one for
the KPI and counter changes in the
latest eight hours of last
Wednesday missing.
● When this occurs, FMA KPI result
files are generated once every FMA
period, which may take some time.
Therefore, the KPI update during
such process may cause the current
KPI value to be 0 or abnormal,
while KPI values at other time are
normal. Refresh the page later and
the current KPI value will be
restored to normal.

BSC6910 UMTS
Category Details
KPI trend value ● Automatically displays the KPI value

or counter value corresponding to a
point on the KPI and counter
change trend curves when you
move the mouse pointer to that
point.
● Provides KPI filtering on the right of
the fault summary interface to
allow viewing the change trend of
the selected KPI.
Unsuccessful operation
● A dialog box is displayed with the failure cause.
10.2 Fast Fault Diagnosis

This function is used to quickly diagnose common network faults, thereby helping
users identify the faulty NE or board. This function can be used when faults occur
and persist at a site and site maintenance personnel cannot directly use the
counters, alarms, and logs for fault analysis.
Context
According to the diagnosis rules, this function comprehensively analyzes the
counters, alarm, and logs related to the fault and provides analysis reports to
users. It helps users perform recovery operations, thereby shortening the fault
recovery period.
● This function is implemented on the OMU and can be used with tracing and
monitoring functions on the LMT.
● This function occupies resources of the OMU board. The DSP OMUSRV
command can be executed to query the disk space, memory usage, and CPU
usage of the OMU board. This function cannot be started or is stopped if any
of the following conditions is met:
– Free space on the OMU board is less than 500 MB.
– More than 95% of OMU memory is occupied and this function occupies
more than 500 MB OMU memory.
– When the OMU CPU usage reaches 100%, the operating system
schedules processes on the OMU by priority. The initial priority of the
fault analysis task using the fault diagnosis function is set to low.
According to the measured CPU usage statistics, when the OMU CPU
usage is lower than the minimum threshold (10%), increase its priority.
When the CPU usage is higher than the minimum threshold, decrease its
priority.

BSC6910 UMTS
When a fault occurs, it is recommended that you use this function to analyze the fault and then
run the COL LOG command to collect logs.
Procedure
Step 1 Optional: (Optional) Run the SET FMATH command to set the fault diagnosis
threshold.
When the default fault diagnosis threshold is not used, run the SET FMATH command to set
the threshold.
To query the specified fault diagnosis threshold, run the LST FMATH command.
Step 3 Select a logical NE for fault diagnosis from the drop-down list box in the upper
left corner.
Step 4 The system automatically selects the fault scenario, starts a detection, collects
information, and generates a diagnosis report. You can click Query Result to
obtain the diagnosis report. If a manual detection is required, refer to steps 5 and
6.
Step 5 (Optional) Select the fault scenarios requiring fault management on the Fault
Diagnosis tab page.
Step 6 Click Base Station Selection and enter the ID of the base station in the displayed
dialog box to detect the base station on the FMA and obtain the key interface
status of the base station.
A maximum of five IDs of base stations working only in IP transmission mode can be
entered.
Step 7 (Optional) Click Start and wait for the fault diagnosis report.

BSC6910 UMTS
For a manual detection, a folder named by the operation date and time is generated in the
bam/version_x/ftp/fma_data/FaultDiagnosis directory each time this function is implemented,
for example, /bam/version_x/ftp/fma_data/FaultDiagnosis /201501010101. For an automatic
detection, a folder named after the operation date and time is generated in the bam/
version_x/ftp/fma_data/FaultDiagnosis directory each time this function is implemented, and
auto is added in the folder name, for example, /bam/version_x/ftp/fma_data/FaultDiagnosis /
201501010101_auto. The sub-folders and files contained in the folder are described as follows:
● Alarm_data: Contains the active alarms and cleared alarms for the last 24 hours.
For details about the UMTS alarm list, see List of Alarms for UMTS Fault Diagnosis.
● Opt_data: Contains the operation data for the last 24 hours.
● Report: Contains the analysis report generated using the fault diagnosis function.
● FmaData_201501010101_auto.zip: Contains data related to the alarms, operations,
configurations, and more.
When KPI faults occur or alarms are reported, the FMA is automatically started for fault
diagnosis. You can set AutoStartFMASW in the SET OMUPARA command to control whether to
automatically start FMA for fault diagnosis. By default, this function is enabled for both new
networks and upgrade scenarios.
All historical folders are stored in the bam/version_x/ftp/fma_data/FaultDiagnosis directory.
The maximum size of these folders is 500 MB. If the size exceeds 500 MB, the system deletes
the earliest folder. Therefore, you must save required historical analysis results in a timely
manner.
Before using this function, save the FMA diagnosis report to ensure fast report backhaul. Then,
download original diagnosis data related to FMA.
Click Diagnosis_Collection to start fault diagnosis and quick information collection
simultaneously.
Table 10-2 UMTS fault analysis scenario options
Scenario Option Item
KPI RRC Success Rate The number of RRC

connection setup requests is 0.
The RRC connection setup

success rate is abnormal.
The number of RRC

connection setup requests
decreases significantly.
High risk operation check
CS RAB Setup Success The initial direct transmission

Rate flow control rate of CS services
is abnormal.
The Iu-CS SCCP setup success

rate is abnormal.
The CS security mode success

rate is abnormal.
The location update success

rate is abnormal.

BSC6910 UMTS
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 Service Drop Rate The CS service drop rate is

abnormal.
PS RAB Setup Success The initial direct transmission

Rate flow control rate of PS services
is abnormal.
The Iu-PS SCCP setup success

rate is abnormal.
The PS security mode success

rate is abnormal.
The RA update success rate is

abnormal.
The PS service redirection rate

in the 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 Service Drop Rate The PS service drop rate is

abnormal.

BSC6910 UMTS
Paging The paging success rate is

abnormal.
Traffic CS Erlang The CS service traffic

decreases significantly.
PS Throughput The PS throughput decreases

significantly.
Transmission Site Break Down A large number of cells are

unavailable.
Transmission Analyze the transmission

Connectivity Analysis connectivity.
Transmission Analysis of the transmission

Signaling Analysis signaling
Board faults Board Fault Diagnose The board is faulty or fails to

start.
Communication The communication between

Failure Between the the NE and NMS is abnormal.
NE and NMS
OMU Fault Diagnose The OMU is faulty.
Analysis on the Analysis on the Proportion of

Proportion of Faulty Faulty Board Links
Board Links
Hardware Sub-health Hardware sub-health status

Diagnosis
Health Check Equipment Health Health check on the interface

Check boards
Health check on the user-

plane boards and subsystems
Health check on the control-

plane boards and subsystems
Analysis on system
configuration errors
Control-plane Iu-CS and Iu-PS

interface status check
Iur-p interface status check

BSC6910 UMTS
Flow control of the board
Others License Fault A license is faulty.

Diagnose
RNC in Pool Load The number of RRC

Sharing connection setup requests of
the overflow RNC is 0.
The RRC connection setup

success rate of the overflow
RNC is abnormal.
The number of successful CS

RAB setups of the overflow
RNC is 0.
The CS RAB setup success rate

of the overflow RNC is
abnormal.
The CS service drop rate of the

overflow RNC is abnormal.
The number of successful PS

RAB setups of the overflow
RNC is 0.
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.
Table 10-3 lists the fault diagnosis scenarios for RNC in Pool. The system
automatically determines the application scenario based on the load sharing type,
redundancy type, and host status. You can query the load sharing type by running
the LST URNCBASIC command and query the host status by running the DSP
UHOSTRNC command.

BSC6910 UMTS
Table 10-3 RNC in Pool fault analysis scenario options

Scenari RNC in Pool Load RNC in Pool RNC in Pool Load Sharing
o Sharing Redundancy and Redundancy
Option
Load Load Host Host Load Load Load
Sharing Sharing Status= Status= Sharing Sharing Sharing
Type= Type=O MASTE BACKU Type= Type=O Type=O
MASTE VERFL R P MASTE VERFL VERFL
R OW R and OW OW
Host and and
Status= Host Host
MASTE Status= Status=
R BACKU MASTE
P R
RRC √ × √ × √ × √
connect
ion
setup
CS √ × √ × √ × √
service
setup
CS call √ × √ × √ × √
drop
PS √ × √ × √ × √
service
setup
PS call √ × √ × √ × √
drop
CS √ × √ × √ × √
Erlang
PS √ × √ × √ × √
through
put
Paging √ × √ × √ × √
A large √ × √ × √ × √
number
of
unavail
able
cells
Equipm √ √ √ √ √ √ √
ent
Health
Check

BSC6910 UMTS
Scenari RNC in Pool Load RNC in Pool RNC in Pool Load Sharing
o Sharing Redundancy and Redundancy
Option
Load Load Host Host Load Load Load
Sharing Sharing Status= Status= Sharing Sharing Sharing
Type= Type=O MASTE BACKU Type= Type=O Type=O
MASTE VERFL R P MASTE VERFL VERFL
R OW R and OW OW
Host and and
Status= Host Host
MASTE Status= Status=
R BACKU MASTE
P R
RNC in √ × × × √ × ×
Pool
Load
Sharing
----End
Result
● Successful operation
– A new browser window is displayed with the fault analysis report
displayed on a web page.
Table 10-4 Button functions

Button Name Description
Save Report 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.
Download Download the original data of the diagnosis report

Source Data that is generated by the NE.
A fault diagnosis report contains the information listed in the following

table.
Table 10-5 Content of a diagnosis report

Item Description
Rule Matching Containing the report of rule matching details

Summary Report

BSC6910 UMTS
Item Description
RNC Basic Containing RNC in Pool networking information

Information and RNC basic configuration information, such as
RNC ID, RNC name, transmission modes over the
Iub, Iur, Iu-CS, and Iu-PS interfaces, and the load-
sharing type of RNC in Pool
KPI Trend ● 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, RNC Alarm Quantity Trend, Active
alarms on the Iu-CS/Iu-PS/Iur-p interface, and
Alarms of last 24 hours are included.
● Containing three curves illustrating KPI and
counter changes that occurred during the eight
hours of today, yesterday, and last week,
respectively. The X-coordinate represents
hour:minute, the Y-coordinate represents the
counter value in the unit of the corresponding
counter or the KPI value in percentages.
● Containing the threshold used in the rules of the
fault diagnosis. 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
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.

BSC6910 UMTS
Item Description
FMA Dashboard ● The dashboard function supports association

analysis and graphical user interface (GUI)
display of KPI trend measured 8 hours before
the rapid fault diagnosis function starts and
alarms and key operation logs generated 24
hours before the rapid fault diagnosis function
starts. This function displays the KPI trend and
associates KPI trend, alarms, and operation logs
by time points so that the faults are located
quickly and services are restored in a short
period of time.
– KPI Trend: A line is displayed for each KPI or
counter indicating its 15-minute change
trend in the last 8 hours. In such type of
trend chart where the X axis represents the
time and two Y axes are used, the Y axis on
the right side displays proportion-type KPIs.
– Operation Log: The executed MML
commands are displayed from the earliest
one. Details such as the executed MML
commands, operating time, and execution
results are displayed.
– Alarm Log: Alarms are displayed from the
earliest one. Details such as alarm ID, alarm
report time, and location information are
displayed.
NOTE
When you enter the time to query alarms:
● If the entered time is the same as Alarm raised
time of a single alarm in alarm logs,
information about the alarm will be contained
in query results.
● If the entered time is the same as Alarm raised
time of multiple alarms, information about the
first alarm generated at the time will be
contained in query results.
● If the entered time is different from Alarm
raised time of all alarms in alarm logs,
information about alarms generated at the
time that is closest to the entered time will be
contained in query results.
● In the change trend chart, when you click a
certain time, alarms and operation logs
generated at this time point will be displayed.
When you click an alarm or an operation log,
the KPIs at this time point will be displayed.
Double-click an alarm log to open the Detail
info of alarm log dialog box. In the displayed
dialog box, click Solution to view the alarm

BSC6910 UMTS
Item Description
handling suggestions described in the alarm

reference.
● The dashboard function has two startup modes:
– In the Scenario Options dialog box, click
Dashboard without selecting the fault
scenario.
– In the Scenario Options dialog box, select a
fault scenario and click Start. Compared with
the first startup mode, the fault analysis
report is displayed in addition to the KPI
trend and FMA dashboard.
Fault analysis Includes the fault description, diagnose result, and

report handling suggestions in the fault diagnosis scenario
selected by a user. For details about fault diagnosis
scenarios, see Table 1.
Operation logs of Running the MML command EXP LOG to export

latest 24 hours the operation log.
– Query historical records of analysis reports.
▪ Click Query Result on the fault diagnosis page. In the Query Result
dialog box, select a query time to query the analysis report at this
time point. If Auto is displayed, the system generates reports
automatically.
▪ After the query is submitted, a window is displayed, indicating the

query results. If the bam/version_x/ftp/fma_data/FaultDiagnosis/
report directory does not contain the report.xml file, a window is
displayed to report an error.
● Unsuccessful operation
– A dialog box is displayed with the failure cause.
10.3 Hierarchical Delimitation

This function is used to analyze faults. When faults cannot be identified using
fault diagnosis, this function can be used.
Context
This function decomposes faults based on standard protocol layers from the KPIs
of the faulty network, until the smallest identifiable objects are obtained. The
counters, alarms, status, and operations of these objects are displayed and
identified to provide a fault analysis report for users.

BSC6910 UMTS
Procedure
Step 1 On the LMT main page, click FMA. The FMA window is displayed.
Step 2 On the FMA tab page, click Hierarchical Delimitation. The Hierarchical
Delimitation tab page is displayed.
Step 3 Set parameters on the Hierarchical Delimitation tab page.
Step 4 Click Analyze and wait for the fault analysis report.
Table 10-6 GUI parameter description

Select the KPI Set this parameter based on the abnormal KPIs by observing
items the KPI trend curve.
History Analyze In the drop-down list, select the time of saving historical
analysis reports, and click Query.
----End
Result
– A new browser window is displayed with the fault analysis report
presented on a web page.
Table 10-7 Button Functions

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 Download the original data of the diagnosis

Data report that is generated by the NE.
The following table lists information in a fault analysis report.

BSC6910 UMTS
Table 10-8 Information in a fault analysis report

Item Description
Fault cells Cells that are affected by faults.

● Cell ID: ID of the problem cell
● Failure rate: Proportion of the number of
failures in a problem cell to that in an RNC
related to a specific counter
● Fault counter: Proportion of the number of
failures in a problem cell to the number of
attempts in this cell related to a specific
counter
● Attempt number: Number of attempts in this
cell related to a specific counter
● NodeB name: Name of the NodeB to which the
problem cell belongs
● INT board: Interface board where the problem
cell is configured
● Subsystem: Subsystem where the problem cell
is configured

BSC6910 UMTS
Item Description
Scenario selection The smallest identifiable objects obtained after

faults are decomposed based on standard
protocol layers. The fault object can be selected
on the left, and the corresponding KPI and alarm
is displayed on the right. The fault object is
displayed below.
● The interface between BSC and BSS
– Control plane
– Wireless layer object, such as NBAP
protocol.
– Transmission layer object, such as
SCTPLINK and ETHPORT.
– Device layer object, such as INT board
and control plane subsystem.
– User plane
– Wireless layer object, such as Abis
protocol.
ETHPORT.
– Device layer object, such as INT board.
● The interface between BSC and CN
– Control plane
– Wireless layer object, such as RANAP
protocol.
MTP3LINK, SCTPLINK, and ETHPORT.
– Device layer object, such as INT board
and control plane subsystem.
– User plane
– Wireless layer object, such as IUUP and
GTPU.
ETHPORT.
– Device layer object, such as INT board.
10.4 Recovery Confirmation

After service recovery solutions are implemented, onsite O&M engineers can view
on the fault summary page the operating status of the GSM and UMTS networks
to check whether a fault has been rectified. For details, see Fault Overview.

BSC6910 UMTS
10.5 Information Collection

This function can be used to quickly and accurately collect onsite information,
thereby shortening the event recovery period.
Context
When faults occur, the information needs to be collected at the site. However,
there are various types of BSC logs, and the procedure for collecting these logs is
complex. In this situation, it is easy to make mistakes in collecting logs, which
leads to repeated collection of logs at the site and prolongs fault troubleshooting.
This function is introduced to simplify the procedure for collecting logs.
This function can be enabled only by the system administrator admin and an administrator-
level, operator-level, or user-level account.
Procedure
Step 1 Information Quick-Collection
1. On the LMT main page, click FMA. The FMA window is displayed.
2. On the FMA tab page, click Information Collection. Click the Information
Collection tab in the WebLMT dialog box that is displayed.
3. Set parameters on the Information Quick-Collection tab page. Specify
Current Time and File Path.
4. Click Collection to start collecting fault information.
After you click Collection, the progress bar may fail to show the progress, and this
status lasts for several minutes.
Table 10-9 GUI parameter description

GUI Parameter Description
Current Time You are advised not to modify the current time.
File Path Save path of log files to be collected. By default, files

are saved on the desktop.
Result Information about collected log files, such as the file

name, save path, and file size.
First Progress Log file collection progress.

Second Progress Second batch of log files start to be collected only
after the connection of the first batch completes.
Fault information can be collected in one-click mode. The collection consists

of two batches.

BSC6910 UMTS
– In the first batch, this function collects historical alarm files (48 hours),
operation logs (48 hours), BSC data configuration files, UKPI snapshot
(with the granularity of 5 minutes and 24 hours) generated when the
problem occurs, and last word log file (20 minutes), GCSR log (one file of
subrack 0).
– In the second batch, this function collects performance counter result files
(2 hours), UMTS CHR logs (one file for each subrack), common debug
log files (one file for each subrack), and call fault logs (one file for each
subrack).
The time in the brackets following the collected files indicates the time during which the
files are collected in the specific fault diagnosis scenario. For example, historical alarm
files (12 hours) indicates historical alarm files collected for 12 hours including the time
when the fault occurs.
----End
Result
● Quickly collecting information
After the collection is complete, the collected data can be obtained from the
directory specified by the user. Each batch of data is automatically saved in a
sub directory of the specified directory. For example, the directory specified by
the user is E:\DATA, the first and second batches of collected data will be
saved in E:\DATA\BATCH1_YYYYMMDDHHMMSS and E:\DATA
\BATCH2_YYYYMMDDHHMMSS, respectively. YYYYMMDDHHMMSS indicates
the time when data collection starts. The letters stand for Year, Month, Date,
Hour, Minute, and Second, respectively. In this manner, even if the whole data
collection is incomplete, the data collection progress can be viewed according
to the progress bar and the file collection progress in the Result box, and the
collected data can be obtained and retransmitted. This improves the data
collection efficiency.
● Collecting customized information
After the collection is complete, the collected data can be obtained from the
directory specified by the user. Data collected each time is automatically
saved in a sub directory of the specified directory. For example, the directory
specified by the user is E:\DATA, data collected each time will be saved in E:
\DATA\COLDAT_YYYYMMDDHHMMSS. YYYYMMDDHHMMSS indicates the
time when data collection starts. The letters stand for Year, Month, Date,
Hour, Minute, and Second, respectively.
10.6 Business Validation

This task is used to quickly check the network status, helping users quickly
determine whether the network status is normal after network reconstruction.
Context
This function provides users comprehensive network status comparison results
(including comparison results of traffic statistics and alarms) before and after

BSC6910 UMTS
network reconstruction, and guides users to the speedy determination of the

network status.
Procedure
Step 2 On the left options, select a logical RNC for business validation.
Step 3 Click Business Validation to open the Business Validation tab page.
Step 4 Select corresponding network reconstruction scenario (multiple choices are not
allowed). Enter the time segment (maximum value: 2 hours), the interval
(maximum value: 7 days, 1 indicating yesterday, 2 indicating the day before
yesterday, and so on.), cell, and BTS (only in BTS cutover scenarios).
Step 5 Click Start to validate the service and wait for the validation report.
A folder named by the operation date and time is generated in the bam/version_x/ftp/
fma_data/BusinessCheck directory each time business validation is performed, for
example, /bam/version_x/ftp/fma_data/BusinessCheck/20150804080339. This folder
contains four sub-folders which are described in the following.
● Alarm_data: Contains the active alarms and cleared alarms for the last 24 hours.
● Opt_data: Contains the operation data for the last 24 hours.
● Report: Contains the analysis report generated using the fault diagnosis function.
Table 10-10 Business validation scenario
Business Validation Scenario Options Items
Business Validation Common Counter RRC Access Success Rate

Verification
CS RAB Access Success
Rate
PS RAB Access Success

Rate
Whether the CS Service

Drop Rate Is Normal
Whether the PS Service

Drop Rate Is Normal
Whether the Traffic Is

Normal
ATM-to-IP Transmission Whether the

Reconstruction over the Transmission Link Is
Iub Interface Normal
Whether the Status of

Each Cell Is Normal
RRC Access Success Rate

BSC6910 UMTS

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal
Rehoming Whether the

Transmission Link Is
Normal
Whether the Status of

Each Cell Is Normal
RRC Access Success Rate

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal
IUR Reconstruction RRC Access Success Rate

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal

Normal
Whether the
Normal
Whether the Migration

Success Rate Is Normal

BSC6910 UMTS
IU Reconstruction RRC Access Success Rate

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal

Normal
Whether the
Normal
Whether NAS Counters

of the Iu Interface Are
Normal
RNC License Replace RRC Access Success Rate

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal

Normal
IUFLEX RRC Access Success Rate

Rate

Rate

Drop Rate Is Normal

Drop Rate Is Normal

BSC6910 UMTS

Normal
Whether the
Normal
Whether the
Configuration Is Intact
Whether NAS Counters

of the Iu Interface Are
Normal
Business validation can be performed only for items in the same User interface (UI).
Table 10-11 Configuration of check parameters

Parameter Description Value Range
Check Item Setting Time Specifies business 15 to 120 minutes

validation periods
on one day.
Interval (Day) Specifies the 1 to 7 days

number of days
when data is
required for
comparison for
business
validation.
Select a Cell By cell ID Specifies IDs of 1 to 500

Object cells requiring
business
validation.
By base station ID Specifies IDs of 1 to 50

base stations
requiring business
validation.

BSC6910 UMTS
In some business validation scenarios, not all parameters to be checked are required to be
entered. In these scenarios, these parameters are dimmed and become unavailable
automatically.
----End
Result
– A new browser window is displayed with the fault diagnosis report
presented on a web page.
Table 10-12 Button functions
Save Report 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.
Download Download the raw data of the diagnosis report that is

Source Data generated by the NE.
The business validation report contains business validation results

corresponding to scenarios selected on the GUI.
– The service verification result includes KPI verification result and alarm
verification result.
▪ KPI verification result: The FMA automatically selects KPIs based on

the selected scenario, time segment, and interval, and performs
comparison with KPIs before reconstruction at specified time
segment. If certain KPIs do not exist before reconstruction, the FMA
compares these KPIs with experience baseline values. In certain time
period, if the value of a KPI deteriorates over 5% compared with that
before reconstruction, the KPI is considered to deteriorate in this time
period. The time period proportion of KPI deterioration, the worst
value after reconstruction, and KPI priority are displayed in the KPI
verification result.
▪ Alarm verification result:

○ The FMA automatically filters active alarms generated within 12
hours.
○ The FMA automatically selects the alarm set based on the user-
selected scenario.
○ If an alarm belongs to alarms in both the previous two steps, the
alarm is generated due to reconstruction and will be displayed in
the alarm verification result for field engineers to troubleshoot.
– Query the history record of the analysis report.

BSC6910 UMTS
▪ On the Business Validation page, click the Query Result button.

The Query Result dialog box is displayed. In the dialog box, select a
time point to view the corresponding analysis report.
▪ An IE window is displayed after you click OK in the Query Result

dialog box. If the report.xml file in not stored under the bam/
version_x/ftp/fma_data/BusinessCheck/yyyymmddhhmmss/report
directory, a dialog box indicating that the file is not found is
displayed.
10.7 Business Query

This task helps to quickly check fault recovery results.
Context
Regular-period KPI check on service restoration requires a longer period of time.
Add this function to quickly check fault recovery results and reduce customers'
losses.
Procedure
Step 1 On the LMT main page, click FMA, and the FMA tab page is displayed.
Step 2 In the FMA tab page, click Business Query. The Business Query tab page is
displayed.
Step 3 On the Business tab, select the Time Settings checkbox, and set the start time to
query the alarm status. The start time for querying the alarm status cannot be
earlier than the current OMU time.
Step 4 View the restoration result.
● If the query results are abnormal, an error message is displayed, and the automatic
refreshing stops. In this case, close the Page Query tab page and open it again and the
refreshing function automatically starts.
----End
Result
● The operation succeeds.
– The interface lists the service restoration results. The results are refreshed
regularly.
– KPI information is listed in a table and updated periodically.
● The operation fails.
– The dialog box is displayed to indicate the failure cause and the
automatic refreshing stops.

BSC6910 UMTS
10.8 Independent Rules Update

This function enables quick publishing and deployment of FMA rules.
Prerequisites
Contact Huawei engineers to obtain the FMA rules update packet. Huawei
engineers can obtain the update packet based on the BSC/RNC version at:
Support > Software > Wireless Network > Wireless Network Common >
SingleRAN > SingleRAN_O&M tools > FMA Rules Update Packet.
NOTICE

according to the OpenPGP Signature Verification Guide. If the software package
fails the verification, do not use the software package, and contact Huawei
technical support engineers.
Before a software package is used in installation or upgrade, its digital signature
also needs to be verified according to the OpenPGP Signature Verification Guide
to ensure that the software package is not tampered with. Visit either of the
following websites to obtain the OpenPGP Signature Verification Guide:
● Enterprise customers: https://support.huawei.com/enterprise/en/tool/pgp-
verify-TL1000000054
Context
FMA rules can be updated independently using MML commands, eliminating the
need to update the BSC/RNC version and avoiding service interruptions.
Procedure
Step 1 On the LMT main page, click File Manager. The File Manager tab page is
displayed.
Step 2 Upload the FMA rules update packet to the directory /mbsc/upgrade.
Step 3 On the LMT main page, click MML. The MML tab page is displayed.
Step 4 Run the INS FMA command to install the FMA rules update packet.
Step 5 Run the LST FMAVER command to check whether the FMA version is correct.
----End

BSC6910 UMTS
10.9 List of Alarms for UMTS Fault Diagnosis

The following table lists the alarms for UMTS fault diagnosis.
Alarm ID Alarm Name
ALM-20201 1PPS State Abnormal
ALM-20202 Time Information Reception Abnormal
ALM-20204 Clock Signal Inputs Faulty
Faulty Phase-Locked Loop of the Board

ALM-20209
Clock
Current Clock Reference Source of

ALM-20210
Main Control Board Abnormal
GE Link on Signaling Processing Board

ALM-20226
Panel Faulty
GE Link Between GE Switching Board

ALM-20228
and Service Board Faulty
ALM-20232 GE Interface Unit Fault
ALM-20233 Board Voltage Abnormity Alarm
ALM-20239 Board Active-Standby Abnormal
ALM-20241 Board Unavailable
ALM-20242 Board Subsystem Unavailable
ALM-20243 Board Hardware Fault
ALM-20250 Sub-board Status Abnormal
ALM-20251 Board Temperature too High
ALM-20254 DSP Unavailable
ALM-20255 DSP Blocked
ALM-20256 CPU Overload
ALM-20257 Board Startup and Running Failure
Number of Resources Used Reaching

ALM-20258
Alarm Threshold Specified by License
Number of Resources Used Exceeding

ALM-20259
Alarm Threshold Specified by License
ALM-20260 Internal Communication Fault
ALM-20271 Statistical Alarm

BSC6910 UMTS
Alarm ID Alarm Name
Forwarding Overload of An Interface

ALM-20275
Board
License Inconsistency Between OMU

ALM-20734
and Host
ALM-20735 Trial Operation of License
ALM-20739 No License
Configuration Data Exceeding License

ALM-20741
Capacity
ALM-20743 Insufficient License Resources
ALM-20755 Feature Expired Alarm
ALM-20756 Feature Invalid Alarm
The Network License is to be Switched

ALM-20757
to Local State
ALM-20758 BTS License Will Be Revoked
POOL license information

ALM-20759
synchronization failure
ALM-21201 BCCH Mutual Aid in a Cell
Switchback after BCCH Mutual Aid in a

ALM-21202
Cell
ALM-21203 Baseband FH Mutual Aid in a Cell
Switchback after Baseband FH Mutual

ALM-21204
Aid in a Cell
ALM-21205 Cell Out of Service
ALM-21206 Cell BCCH Aiding to IUO_INN TRX
ALM-21207 E1/T1 Excessive Bit Error Rate
ALM-21208 E1/T1 Excessive Slip Frames
ALM-21209 E1/T1 Online Loopback Detection
ALM-21221 IMA Link Loss of Frame
ALM-21222 IMA Link Out of Delay Synchronization
ALM-21223 IMA Link Remote Failure Indication
ALM-21225 IMA Link TX Unusable at Far End
ALM-21226 IMA Link RX Unusable at Far End
ALM-21227 IMA/UNI Link Loss of Cell Delineation

BSC6910 UMTS
Alarm ID Alarm Name
ALM-21228 IMA Group Startup at Far End
ALM-21229 IMA Group Configuration Aborted
IMA Group Configuration Aborted at

ALM-21230
Far End
ALM-21231 IMA Group Activated Links Insufficient
IMA Group Activated Links Insufficient

ALM-21232
at Far End
ALM-21233 IMA Group Blocked at Far End
ALM-21234 Local IMA Group Blocked
ALM-21235 Local IMA Link Blocked
ALM-21236 IMA Group Local Startup
IMA Group Configuration at different

ALM-21237
port Failure
ALM-21241 Loss of Fractional IMA Frame
Fractional IMA Links out of

ALM-21242
Synchronization
Fractional IMA Link Remote Failure

ALM-21243
Indication
Fractional IMA Link TX Unusable at Far

ALM-21244
End
Fractional IMA Link Remote Reception

ALM-21245
Failure
Fractional IMA/ATM Link Loss of Cell

ALM-21246
Delineation
ALM-21248 Fractional Local Link Blocked
SDH/SONET Tributary Online

ALM-21251
Loopback Detection
ALM-21252 SDH/SONET Loss of Signal
SDH/SONET MS Remote Defect

ALM-21253
Indication
ALM-21254 SDH/SONET Loss of Frame
ALM-21255 SDH/SONET Loss of Frame Alignment
ALM-21256 SDH/SONET Loss of Cell Delineation
ALM-21257 SDH/SONET Signal Degraded

BSC6910 UMTS
Alarm ID Alarm Name
ALM-21258 SDH/SONET LP Signal Label Mismatch
SDH/SONET LP Trace Identifier

ALM-21259
Mismatch
SDH/SONET LP Remote Failure

ALM-21260
Indication
SDH/SONET LP Remote Defect

ALM-21261
Indication
ALM-21262 SDH/SONET LP Unequipped Defect
ALM-21263 SDH/SONET HP Signal Label Mismatch
ALM-21264 SDH/SONET HP Unequipped
SDH/SONET HP Trace Identifier

ALM-21265
Mismatch
ALM-21266 SDH/SONET Optical Port Loopback
SDH/SONET AU Alarm Indication

ALM-21267
Signal
SDH/SONET RS Trace Identifier

ALM-21268
Mismatch
SDH/SONET RS Trace Identifier

ALM-21269
Unstable
SDH/SONET MS Alarm Indication

ALM-21270
Signal
ALM-21271 SDH/SONET Signal Failure
ALM-21272 SDH/SONET AU Loss of Pointer
SDH/SONET HP Remote Defect

ALM-21273
Indication
SDH/SONET HP Trace Identifier

ALM-21274
Unstable
ALM-21275 SDH/SONET Tributary Loss of Frame
SDH/SONET TU Alarm Indication

ALM-21277
Signal
ALM-21278 SDH/SONET TU Loss of Pointer
ALM-21279 SDH/SONET LP Signal Label Unstable
SDH/SONET LP Trace Identifier

ALM-21280
Unstable

BSC6910 UMTS
Alarm ID Alarm Name
SDH/SONET Loss of Cell Delineation

ALM-21281
Alignment
ALM-21282 SDH/SONET HP Signal Failure
ALM-21283 SDH/SONET HP Signal Deteriorated
SDH/SONET Tributary Excessive Slip

ALM-21284
Frames
ALM-21285 Optical Module Fault
SDH/SONET Tributary Remote Alarm

ALM-21286
Indication Signal
SDH/SONET Tributary Alarm Indication

ALM-21287
Signal
SDH/SONET Tributary Loss of

ALM-21288
Multiframe
ALM-21289 SDH/SONET Tributary Loopback
ALM-21290 Optical Module Mismatch
SDH/SONET Tributary Excessive Bit

ALM-21291
Error Rate
ALM-21293 SDH/SONET HP Signal Label Unstable
ALM-21294 SDH/SONET TU Signal Loss
ALM-21295 SDH/SONET TU Multiframe Loss
ALM-21296 SDH/SONET TU Type Inconsistent
MSP Multiplex Section K1/K2

ALM-21311
Mismatch
ALM-21312 MSP Multiplex Section K2 Mismatch
ALM-21313 MSP Port Protection Mode Mismatch
ALM-21314 MSP Deactivated
ALM-21321 VCL CC Detection Failure
ALM-21322 VCL Alarm Indication Signal
ALM-21323 VCL Remote Alarm Indication
ALM-21326 VCL LB Detection Failure
ALM-21345 Ethernet Link Fault
ALM-21346 IP Connectivity Check Failure
ALM-21347 IP Address Conflict

BSC6910 UMTS
Alarm ID Alarm Name
ALM-21349 Ethernet Trunk Group Fault
ALM-21350 Ethernet Trunk Link Fault
ALM-21352 IP Path Excessive Packet Loss Rate
ALM-21371 ETHOAM 3AH Discovery Failure
ALM-21374 ETHOAM 3AH Remote Loopback
ALM-21375 ETHOAM 1AG CC Lost
ALM-21386 Backup Channel Faulty
Ethernet Port Broadcast Packets

ALM-21387
Exceeding Alarm
ALM-21388 Invalid Packets Exceeding Alarm
ALM-21389 MAC Excessive Frame Error Rate
ALM-21391 ARP Conflict
ALM-21392 Adjacent Node IP Address Ping Failure
ALM-21393 Adjacent Node IP Path Ping Failure
Transmission Resource Pool Ping

ALM-21394
Packet Loss
Adjacent Node IP Path Excessive

ALM-21395
Packet Loss Rate
ALM-21396 IP PM Capability Exceeded
Board Transmission Resource

ALM-21399
Insufficiency
ALM-21501 MTP3 Signaling Link Congestion
ALM-21502 MTP3 DSP Congestion
ALM-21503 MTP3 DSP Inaccessible
ALM-21504 MTP3 Signaling Route Inaccessible
ALM-21505 MTP3 Signaling Link Set Unavailable
ALM-21506 MTP3 Signaling Link Faulty
ALM-21521 SCCP Subsystem Prohibited
ALM-21522 Low SCCP Setup Success Rate
ALM-21531 SAAL Link Fault
ALM-21532 SAAL Link Congestion
ALM-21541 SCTP Link Fault

BSC6910 UMTS
Alarm ID Alarm Name
ALM-21542 SCTP Link Congestion
ALM-21543 SCTP Link IP Address Unreachable
ALM-21551 M3UA Link Fault
M3UA Destination Entity Route

ALM-21552
Unavailable
ALM-21553 M3UA Destination Entity Inaccessible
ALM-21561 AAL2 Path Blocked
ALM-21562 QAAL2 Adjacent Node Inaccessible
QAAL2 Protocol Version Mismatch on

ALM-21563
Adjacent Node
ALM-21564 Low QAAL2 Setup Success Rate
ALM-21580 IP Path Blocked
ALM-21581 Path Fault
ALM-21582 Path Congestion
IP Address In Transmission Resource

ALM-21602
Pool Blocked
ALM-21603 Adjacent Node Congestion
ALM-21604 Insufficient Transmission Resources
ALM-21605 Path Configuration Error
ALM-21606 IURP Link Fault
ALM-21607 External Node Unreachable
ALM-21608 IURP Link Congestion
ALM-21609 Link Packets Exceeding
ALM-22201 UMTS Cell Congested
ALM-22202 UMTS Cell Unavailable
ALM-22203 UMTS Cell Common Channel Faulty
ALM-22204 NCP Faulty
ALM-22205 CCP Faulty
ALM-22206 UMTS Cell Setup Failed
ALM-22207 UMTS Cell Reconfiguration Failed
UMTS Cell Common Channel Setup

ALM-22208
Failed

BSC6910 UMTS
Alarm ID Alarm Name
UMTS Cell Common Channel

ALM-22209
Reconfiguration Failed
UMTS Cell Information Exchange

ALM-22210
Failed
ALM-22212 UMTS Cell Blocked
CCP Information Inconsistency

ALM-22213
Between the RNC and the NodeB
ALM-22214 NodeB Unavailable
ALM-22215 UMTS Cell Max DL Power Mismatch
ALM-22216 NodeB Audit No Response
ALM-22217 UMTS Cell HSDPA Function Fault
ALM-22218 UMTS Cell HSUPA Function Fault
ALM-22219 UMTS Cell EFACH Function Fault
ALM-22220 UMTS Cell MIMO Function Fault
ALM-22224 NodeB Blocked
Configuration Between Related NE

ALM-22244
Dismatch
ALM-22245 NodeB Signaling Plane Creation Failure
ALM-22301 UMTS CN Overload
ALM-22302 KPI Exceed Threshold
ALM-22305 Resource overload on the user plane
ALM-22510 GTPU Faulty
Subsystem Measurement Result File

ALM-22806
Loss
ALM-22832 Board Switchover
ALM-22835 Flow Control
ALM-22839 Board Self-Recovery
ALM-22863 Active/Standby Trunk Port Switchover
ALM-22939 Path to SGSN Faulty

BSC6910 UMTS
LMT User Guide 11 BSC Maintenance
11 BSC Maintenance
This chapter describes how to maintain BSC equipment, back up and restore data,
and implement fast fault diagnosis.
11.1 Backing Up Data

This section describes how to back up system data on the OMU. The system data
includes configuration data, alarm configuration data, and counter configuration
data.
11.2 Restoring Data
This section describes how to restore configuration data on the OMU.
11.3 Batch Configuration
This section describes how to browse and deliver batch configuration script files.
Such files can be generated by the CME or manually generated by operators. Such
files can be in the .xml, .ecf, or .txt format, but only files in the .xml and .ecf
formats can be browsed.
11.1 Backing Up Data

This section describes how to back up system data on the OMU. The system data
includes configuration data, alarm configuration data, and counter configuration
data.
Context
● When the database system crashes or an upgrade fails, start the tool used for
backing up and restoring system data in the mbsc\bam\common\services
\omu_backup_linker directory. With the latest backup data, you can recover
the system.
● If you need to recover only OMU configuration data, run the RTR DB
command and select the corresponding data backup file for data recovery.
Procedure
● Using menus

BSC6910 UMTS
b. In the Device Navigation Tree, right-click BSC and choose Backup Data
from the short-cut menu. The dialog box is displayed with information
about backup files saved in the OMU active workspace installation
directory\data\backup directory.
c. In the dialog box, click Backup to back up system data on the OMU.
● A dialog box is displayed by clicking Backup Data, informing the user of whether
to encrypt the file before backing up it. If you select Yes, enter a password.
● The default save path of backup files is OMU active workspace installation
directory\data\backup. If this save path does not exist, it will be created
automatically.
● 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.
● The following special characters are forbidden in the file name: \\ / : * ? \" < > | ( )
& $ , %% +++ = ; blank character
● Backup files cannot be saved in a network path, for example, \\10.161.162.25.
● No space is allowed in the file name or the saving directory. For example, "BK2009
09 08.bak" is an illegal file name.
d. In the Backup Data dialog box, select a backup file and click Download
to download the backup file to a local path on the LMT PC.
Click Refresh to refresh backup files saved in the OMU active workspace
installation directory\data\backup directory in the Backup Data dialog box.
a. Run the LST BKPFILE command to query data backup files saved in the
OMU active workspace installation directory\data\backup directory.
b. Run the BKP DB command to back up system data on the OMU.
----End
11.2 Restoring Data

This section describes how to restore configuration data on the OMU.
Context
NOTICE
● Restore data with caution because data restore will overwrite OMU data.
● Versions of data backup files must be the same as the OMU version.
● Alarm information and operation logs are not restored. Their data remains
unchanged.
● After restoring OMU data, run the RST BSC command to reset the BSC.

BSC6910 UMTS
Procedure
● Using menus
b. Under Device Navigation Tree, right-click the BSC node and choose
Restore Data from the short-cut menu. The dialog box is displayed with
information about data backup files saved in the OMU active workspace
installation directory\data\backup directory.
c. Optional: In the displayed dialog box, click Upload to upload a backup
file on the LMT PC to the OMU.
Click Refresh to refresh backup files saved in the OMU active workspace
installation directory\data\backup directory in the Restore Data dialog box.
d. In the Restore Data dialog box, click Restore Data to restore
configuration data on the OMU.
If an .ecf encrypted file is selected after you click Restore Data, enter a password to
restore the backup file.
a. Run the LST BKPFILE command to query data backup files saved in the
OMU active workspace installation directory\data\backup directory.
b. Run the RTR DB command to restore configuration data on the OMU.
----End
11.3 Batch Configuration

This section describes how to browse and deliver batch configuration script files.
Such files can be generated by the CME or manually generated by operators. Such
files can be in the .xml, .ecf, or .txt format, but only files in the .xml and .ecf
formats can be browsed.
Prerequisites
● The LMT properly communicates with the BSC.
Context
● Batch configuration is based on the functions of the CME script executor and
aims at quickly validating and browsing patch configuration files.
● Batch configuration includes the Preactivate, Activate and Browse functions.
– Preactivate is used to check whether the data in the configuration scripts
is valid and whether the data conflicts with that on the live network
before data activation. This helps users rectify script problems in advance
and prevents activation failures.
– Activate includes the check functions of Preactivate. It is also used to
validate configuration scripts on the NE.

BSC6910 UMTS
– You can browse, modify, and save the batch configuration files in the
XML Browse area. The execution results of the batch configuration files
are also displayed in this area.
● 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
page is displayed.
Step 2 Under Device Navigation Tree, right-click a BSC node and select Batch
Configuration from the shortcut menu. The WebLMT dialog box is displayed.
Step 3 In the dialog box, select a batch configuration script file.
If an .ecf file is selected, enter a password to import files for batch configuration.
Step 4 Click Activate or Preactivate and wait until the configuration command takes
effect on the BSC.
----End
Result
● Successful operation:
– The progress of the activation and pre-activation related commands is
displayed in the progress bar.
– The execution results of the batch configuration files are displayed in the
message area.
● Failed operation: The failure cause is displayed in the message area.
The failure cause is displayed only for a batch configuration script file with the .xml file name
extension.

BSC6910 UMTS
LMT User Guide 12 FAQ
12 FAQ
This chapter describes some frequently asked questions (FAQs) and the
corresponding solutions.
12.1 Browser-related FAQs

This section describes browser setting-related common problems that hinder the
normal use of the LMT and corresponding handling procedures.
12.2 Java-related FAQs
This section describes Java-related common problems that hinder the normal use
of the LMT and corresponding handling procedures.
12.3 Other FAQs
This section describes common problems, except Java- or browser setting-related
problems, that hinder the normal use of the LMT and corresponding handling
procedures.
12.1 Browser-related FAQs

This section describes browser setting-related common problems that hinder the
normal use of the LMT and corresponding handling procedures.
12.1.1 Slow Responses in the Firefox Browser

Running in the Firefox browser, the LMT gives slow responses. For example, it
takes about 30 seconds to maximize the window of a trace task in the Trace tab
page. In this case, check whether the add-on extension Live Margins is installed.
Procedure
Step 1 Start the Firefox, choose Tool > Add-ons. The Add-ons window is displayed.
Step 2 In the Extensions tab page, select Live Margins, and click Disable. The message
"Restart Firefox to complete your changes" is prompted.
Step 3 Click Restart Firefox to validate the changes.
----End

BSC6910 UMTS
12.1.2 LMT Colors Cannot Be Displayed

When the LMT is started in the IE browser, the colors are not properly displayed.
For example, the colors indicating the status of the boards and alarms are not
displayed, or the background color of the LMT is not differentiated from that of
the IE browser. In this case, check the color settings of the browser.
Procedure
Step 1 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
Options dialog box is displayed.
Step 2 On the General tab page, click Accessibility. The Accessibility dialog box is
displayed.
Step 3 In the Formatting area, deselect Ignore colors specified on webpages, and then
click OK.
Step 4 In the Internet Options dialog box, click OK to exit the dialog box.
----End
12.1.3 Verification Code Cannot Be Displayed on the LMT

Login Page
The verification code cannot be displayed when you try to log in to the LMT using
an Internet Explorer (IE) browser in Windows Server 2008 or Windows Vista.
When this problem occurs, check the settings related to the protected mode of the
browser.
Context
If the protected mode is enabled for the IE browser in Windows Server 2008 or
Windows Vista, many security restrictions are imposed. For example, JavaScript
and Applet cannot be run. Therefore, you must disable the protected mode.
Otherwise, the LMT web page cannot be displayed.
Procedure
Step 1 Enter the external virtual IP address of the OMU in the address box of the IE
browser. Press Enter on the keyboard, or click Go next to the address bar to
display the login window of the BSC6910.
Step 2 Check whether "Internet | Protected Mode: Off" is displayed in the bottom right
corner of the window.
● If yes, the task is complete.
● If no, go to Step 3.
Step 3 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
Step 4 On the Security tab page, select Trusted sites in the Select a zone to view or
change security settings area.

BSC6910 UMTS
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.
If the U2020 proxy server is used for the login to the LMT, add the IP address of the U2020
to the Trusted sites list.
Step 7 In the Internet Options dialog box, click OK to exit the dialog box.
Restart the browser to validate the modifications.

If IE9\IE10\IE11 is used, in addition to the previous settings, choose Tools > Compatibility
View Settings. In the displayed Compatibility View Settings dialog box, select Display all
websites in Compatibility View.
----End
12.1.4 No Response When Clicking the Menu Bar on the LMT

When you browse the LMT web page, there is no response or a script error dialog
box is displayed. To be specific, when you click the menu bar or buttons or right-
click the web page, there is no response or a dialog box is displayed, indicating a
script error, for example, Permission Denied or Access Denied. In this case, check
the proxy settings in the browser.
Context
Do not modify the settings of the browser when you have logged in to the LMT.
Before you log in to the LMT, set the proxy server when necessary.
Procedure
● IE
a. Choose Tool > Internet Options on the tool bar of the IE browser. The
Internet Options dialog box is displayed.
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). 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.
d. 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
a. Choose Tools > Options on the tool bar of the Firefox browser. The
b. In the Options dialog box, click Advanced. On the Network tab page,
click Settings. The Connection Settings dialog box is displayed.

BSC6910 UMTS
c. 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.
d. In the No Proxy for area, type the OMU external virtual IP address and
click OK. Then close the Options dialog box.
----End
12.1.5 How to Set the Browser Under Citrix Farm Networking

Under Citrix farm networking, when you use the U2020 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:
● 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
● Script Setting
a. 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
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
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.

BSC6910 UMTS
b. 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.
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.
c. For details about how to create a domain user, refer to the Citrix Access
Solution User Guide.
d. Apply the script to the domain user.
Assume that there is a user named hong01 in the hongtest unit of the
citrixtest.com domain.
i. Start Active Directory Users and Computer and double-click
hongtest in the left-side pane. In the right-side pane, all users in the
hongtest unit are displayed, as shown in Figure 12-1.
Figure 12-1 Active Directory Users and Computers
ii. In the right-side pane, right-click hong01. Choose Properties from

the shortcut menu. The hong01 Properties dialog box shown in
Figure 12-2 is displayed.

BSC6910 UMTS
Figure 12-2 Displayed hong01 Properties dialog box
iii. In the hong01 Properties dialog box, click the Profile tab. Type IE-
unset.bat in Logon script, click Apply, and then click OK. Figure
12-3 shows the window.

BSC6910 UMTS
Figure 12-3 Applying the script in the hong01 Properties dialog box
● Manual Setting
a. Check the proxy server setting of the browser.
i. Choose Tools > Internet Options on the tool bar of the IE. The
ii. On the Connections tab page, click LAN Settings. The Local Area
Network (LAN) Settings dialog box is displayed.
iii. 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 U2020 and Port
to 80.
b. Check HTTP 1.1 settings of the browser.
i. Choose Tools > Internet Options on the tool bar of the IE. The
ii. On the Advanced tab page, select Use HTTP 1.1 through proxy
connections under HTTP 1.1 settings, click Apply, and then click
OK. Figure 12-4 shows the window.

BSC6910 UMTS
Figure 12-4 HTTP 1.1 settings
----End
12.1.6 Unable to Log In To LMT Because IE Default Security

Level Is Too High
In a Windows Server operating system (including Windows Server 2003 and
Windows Server 2008), the IE blocks Web programs of sites that are out of the
trusted site list to improve system security. As a result, you may fail to log in to
the LMT.
Context
● 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.

BSC6910 UMTS
● 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
● Setting a configuration startup script
a. Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.

@echo off
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
set uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\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
● The IE-unset.bat script file implements automatic setting of IE trusted sites for
Citrix domain users.
● 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.
● If the user needs to set multi-network elements and the network elements do not
exist in a same peer IP address, multi-scripts need to be prepared and loaded
separately.
● Trust in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Internet Settings\ZoneMap\EscRanges\Trust" can be named as you wish.
b. Load the startup script.

BSC6910 UMTS
▪ Script setting for a single Windows server

1) Log in to the Windows server with the account of administrator.
Choose Start > Run.
2) Type gpedit.msc in the displayed dialog box. Then click OK. The
Group Policy Object Editor dialog box is displayed.
3) In the Group Policy Object Editor dialog box shown in Figure
12-5, choose User Configuration > Windows Settings >
Scripts(Logon/Logoff).
Figure 12-5 Script
4) Double-click Logon. The Logon Properties dialog box is

displayed, as shown in Figure 12-6. Click Show Files and copy
the prepared script to the displayed directory. Then close the
dialog box displaying the directory.

BSC6910 UMTS
Figure 12-6 Logon Properties
5) Click Add in the dialog box. The Add a Script dialog box is
displayed, as shown in Figure 12-7.
Figure 12-7 Adding a script
6) In the Adding a script dialog box, click Browse to select the

prepared script and click OK. Then close the dialog box.
7) In the Logon Properties dialog box, click Apply and confirm to
load the prepared script.

BSC6910 UMTS
8) Restart the IE to validate the configuration.
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

1) 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.
● If the organization unit has been set, the users which belong to the
organization unit can all succeed in logging in to the LMT.
● You can rename the group policy object.
2) Select the created group policy object and click Edit. In the
displayed dialog box shown in Figure 12-8, choose User
Configuration > Windows Settings > Scripts(Logon/Logoff).
Figure 12-8 Script
3) Double-click Logon. The Logon Properties dialog box is

displayed, as shown in Figure 12-9. Click Show Files and copy
the prepared script to the displayed directory. Then close the
dialog box displaying the directory.

BSC6910 UMTS
Figure 12-9 Logon
4) In the Logon Properties dialog box, click Add. The Add a Script
dialog box is displayed, as shown in Figure 12-10.
Figure 12-10 Adding a script
5) Click Browse to select the prepared script and click OK. Then
close the dialog box.
6) In the Logon Properties dialog box, click Apply and confirm to
load the prepared script.

BSC6910 UMTS
● Removing Internet Explorer Enhanced Security Configuration

a. Log in to the Windows server with the account of administrator. Choose
Start > Control Panel > Add or Remove Programs. Select Internet
Explorer Enhanced Security Configuration in the displayed dialog box
shown in Figure 12-11.
Figure 12-11 Windows components wizard
b. In the Windows Components Wizard dialog box, click Details, and

deselect For administrator groups and For all other user groups, as

BSC6910 UMTS
Figure 12-12 Internet Explorer Enhanced Security Configuration
c. Click OK and then click Next to remove Internet Explorer Enhanced

Security Configuration. After the removal is complete, click Finish.
d. Restart the IE to validate the configuration.
----End
12.1.7 Unable to Download or Install the Java 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 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 plug-in during login to the LMT.
In addition, two file manager windows displays after clicking File Manager.
Procedure
Step 1 On the menu bar of the IE browser, choose Safety > SmartScreen Filter > Turn
Off SmartScreen Filter.

BSC6910 UMTS
Step 2 In the displayed Microsoft SmartScreen Filter dialog box, select Turn off
SmartScreen Filter and click OK to turn off the SmartScreen filter.
----End
12.1.8 The Error "Certificate Invalid" Is Displayed During an

HTTPS Login
The LMT certificate and the certificate used to access the LMT through the U2020
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
● Using an IE browser
a. After https://the external virtual IP address of the OMU, for example,
https://10.141.115.219, is entered in the Address bar of the browser, the
There is a problem with this website's security certificate dialog box
or Security Alert dialog box is displayed, as shown in Figure 12-13 and
Figure 12-14.
Figure 12-13 Dialog box showing "There is a problem with this website's
security certificate" (IE7 or later versions)

BSC6910 UMTS
Figure 12-14 Dialog box showing "Security Alert"(IE6)
b. Click Continue to this webpage(not recommended) in the There is a

problem with this website's security certificate dialog box or Yes in the
Security Alert dialog box to enter the LMT login page. In the Address bar
of the browser, the Certificate Error message is shown.
c. After clicking Certificate Error, the Certificate Invalid dialog box is
shown.
● Using a Firefox browser
a. After https://the external virtual IP address of the OMU, for example,
https://10.141.115.219, is entered in the Address bar of the browser, the
This Connection is Untrusted dialog box, as shown in Figure 12-15.
(The following figure uses Firefox3.0 as an example. The dialog box varies
with browser versions but has the same information.)

BSC6910 UMTS
Figure 12-15 Dialog box showing "This Connection is Untrusted"
● Connection Through the U2020

a. After connecting through the U2020 with both IP addresses, the
Certificate Invalid dialog box is shown.
Procedure
Step 1 Using an IE browser
In the Certificate Invalid dialog box, click View certificates to view the current
certificate. If the certificate displays Issued to: MBSC Certificate and Issued by:
Huawei Wireless Network Product CA, as shown in Figure 12-16, perform the
following steps:

BSC6910 UMTS
Figure 12-16 MBSC Certificate
1. On the login interface, click Download CA Certificate. In the displayed dialog

box, click Save. After the download is complete, the ca.zip file is saved.
2. Decompress the ca.zip file.
The ca.zip file is decompressed into two files: ne.cer and oss.cer. The ne.cer file is the
root certificate of Huawei certificate predefined for the LMT and the oss.cer file is the
root certificate predefined for the U2020 proxy server.

BSC6910 UMTS
3. Double-click ne.cer or oss.cer, then a Certificates dialog box is displayed.

Click Install Certificate, then a Certificate Import Wizard dialog box is
displayed.
4. Click Next, choose the Place all certificates in the following store option
button, and click Browse.
A Select Certificate Store dialog box is displayed.
5. Choose Trusted Root Certification Authorities and click OK.
6. Click Next, then click Finish and confirm that the ne.cer file has been
imported.
7. Repeat steps 3 to 6 to import the oss.cer file.
In the Certificate Invalid dialog box, click View certificates to view the current
certificate. If the certificate displays Issued to: server and Issued by: hwca, as
shown in Figure 12-17, perform the following steps:

BSC6910 UMTS
Figure 12-17 Server Certificate
1. Click Install Certificate and Next. A dialog box shown in Figure 12-18 is
displayed.

BSC6910 UMTS
Figure 12-18 Certificate Import Wizard dialog box
2. In the Certificate Import Wizard dialog box, select Place all certificates in
the following store and click Browse. In the displayed dialog box, select
Trusted Root Certification Authorities and click OK.
3. In the Certificate Import Wizard dialog box, click Next, Finish, and OK.
4. Restart the browser so that the reconfiguration can take effect.

In the Certificate Invalid dialog box, click View certificates. If the displayed
information about the current certificate is different from the information in the
preceding conditions, import the root certificate of the current certificate. Perform
the following steps:
1. Obtain the root certificate from the organization issuing the current
certificate.
2. In the menu of the IE browser, choose Tools > Internet Options > Content
tab and click Certificate on this tab page, the Certificate dialog box is
displayed.
3. In the Certificates > Personal tab, and click Import on this tab page, the
Certificate Import Wizard dialog box is displayed.
4. In the displayed Certificate Import Wizard dialog box, click Next to import
the certificate file. Then click Next, choose Place all certificates in the
following store, and then click Browse. Choose Trusted Root Certification
Authorities and click Next to import the certificate file.
5. Restart the browser to make the reconfiguration takes effect.
Step 4 Using a Firefox browser

BSC6910 UMTS
1. Click Add Exception shown in Figure 12-15. The Add Security Exception
dialog box is displayed, as shown in Figure 12-19.
Figure 12-19 Add Security Exception dialog box
2. Click Confirm Security Exception. After the website is added as a security

exception, no security error will be displayed during a login to the LMT using
Firefox.
Step 5 Connection Through the U2020
The certification path of the U2020 is shown as Figure 12-20.

BSC6910 UMTS
Figure 12-20 Certification Path of the U2020
1. Choose General > Install Certificate in the Certificate dialog box. And
Certificate Import Wizard dialog box is displayed.
2. Click Next in the Certificate Import Wizard dialog box and Certificate Store
dialog box is displayed. Then choose Place all Certificates in the following
store.
3. Click Browse, the Select Certificate Store dialog box is displayed. Then
choose Trusted Root Certification Authorities.
4. Click OK, the Completing the Certificate Import Wizard dialog box is
displayed.
5. Click Finish, the Security Warning dialog box is displayed.

BSC6910 UMTS
6. Choose Yes in the Security Warning dialog box. The import was successful
message is displayed. Then click OK.
----End
12.1.9 The Error 'Mismatched Address' Is Displayed During an

HTTPS Login
A user uses an IP address rather than a domain name to access the LMT.
Therefore, the Mismatched Address error is displayed on the browser during an
HTTPS login. This error does not impair the LMT functions. This section describes
how to correct the error "Mismatched Address" displayed during a login to the
LMT through HTTPS. To correct this error, deselect the Warn about certificate
address mismatch* option.
Context
1. Enter https://the external virtual IP address of the OMU, for example,
https://10.141.115.219, in the Address bar of the browser. The There is a
problem with this website's security certificate or Security Alert dialog
box is displayed, as shown in Figure 12-21 and Figure 12-22.
Figure 12-21 Dialog box showing "There is a problem with this website's
security certificate"(IE7 or later versions)

BSC6910 UMTS
Figure 12-22 Dialog box showing "Security Alert"(IE6)
2. Click Continue to this webpage(not recommended) in the There is a

problem with this website's security certificate dialog box or Yes in the
Security Alert dialog box to enter the LMT login page. In the Address bar of
the browser, an Certificate Error message is shown.
3. Click Certificate Error. The Mismatched Address error dialog box is
displayed.
Procedure
Step 1 Choose Tools > Internet Options on the Menu bar of the browser. Click the
Advanced tab in the displayed dialog box shown in Figure 12-23.

BSC6910 UMTS
Figure 12-23 Internet Options dialog box
Step 2 In the Internet Options dialog box, deselect Warn about certificate address
mismatch* and click OK.
The reconfiguration takes effect after the browser is restarted.
----End
12.1.10 File Manager Functions are Improperly

When the file manager functions improperly or cannot be used, perform the
Procedure
● 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:

BSC6910 UMTS
a. Open the Internet Options dialog box, click the Advanced tab, and clear
Do not save encrypted pages to disk. Figure 12-24 shows the dialog
box.
Figure 12-24 Internet Options dialog box
● Check that temporary Java files are saved on the computer. If they are not,
the file manager functions improperly. Perform the following operations:
a. Open Control Panel in the Windows operating system and double-click
Java. The Java Control Panel dialog box is displayed.
b. In the displayed Java Control Panel dialog box, click Setting. The
Temporary Files Settings dialog box is displayed. Select Keep temporary
files on my computer shown in Figure 12-25.

BSC6910 UMTS
Figure 12-25 Temporary Files Settings dialog box
● Check whether the browser agency has been set. If yes, eliminate the setting.
Using IE browser
a. Choose Tools > Internet Options. The Internet Options dialog box is
displayed.
b. In the displayed Internet Options dialog box, choose Connections > LAN
settings.
c. 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.
d. Click OK. The setting is complete.
Using FireFox browser
a. Choose Options > Advanced > Network > Settings. The Connection
Settings dialog box is displayed.
b. In the displayed Connection Settings dialog box, select No proxy.
c. Click OK. The setting is complete.
● If the file manager fails to be opened and the message Fail to parse
response is displayed, check whether the file names or folder names under
the /mbsc directory contain invalid characters. If there are invalid characters,
rename the files or folders.
----End
12.1.11 Message 'Class doesn't support Automation' Displayed

in an IE Browser
After clicking Login in an Internet Explorer (IE) browser, you find a blank window
displayed and login unable to continue. In the bottom left corner of the IE

BSC6910 UMTS
browser, a yellow error icon is displayed. The icon says "Class doesn't support
Automation". To solve the problem, perform the following steps:
Context
● This problem occurs because some registration components are missing from
the IE browser. To solve this problem, register the following components
again:
– msscript.ocx
– dispex.dll
– vbscript.dll
– scrrun.dll
– urlmon.dll
Procedure
Step 1 In Windows, choose StartRun and enter RegSvr32 msscript.ocx. To register the
other components again, replace the typed component in italics.
Step 2 After registering all the components again, clear the cache memory of the IE
browser.
Step 3 Log in to the LMT again.
----End
12.1.12 Error Message"This user session already exists" Upon

Login to LMT
The interface displays an error message "This user session already exists" upon
login to LMT. Solve the problem by using the method described in the procedure
part.
Context
To enhance system security, the client browser uses Cookie to store the session
information of users who have successfully logged in. Due to the session Cookie
mechanism, the user encounters the following problems when using LMT:
● 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 or IE10 or IE11 and
Firefox enabled by default. As a result, when the user attempts to repeatedly
log in to the LMTs of the same NE, the system determines a repeated login of
the same user session. For the IE6/7 browser in which each browser window
uses independent sessions, this problem does not arise.
● Problem 2: The LMT interface displays the error "this user session already
exists", while the user has not carried out the operation described in Problem
1. This is because the previous session information remains valid due to an
abnormal exit from LMT. As a result, the LMT determines a repeated login

BSC6910 UMTS
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
● For Problem 1, the following method is used:
a. 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.
This method applies only to the IE8 or IE9 or IE10 or IE11 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:
a. The IE6/7 browser user needs to close the browser window of the current
LMT login interface, and the IE8/9/10/11 and Firefox users need to close
all opened browser windows to invalidate the old sessions.
b. If the pop-up blocker is enabled for the browser, disable it.
c. Restart the browser and log in to LMT.
----End
12.1.13 The "Are You Sure You Want to Quit the Page" Dialog
Box Is Displayed
After successful login to the LMT in the IE8 or IE9 or IE10 or IE11 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
deselect Automatic Recovery from Page Layout Error.
Step 2 Restart the browser and log in to LMT again.
----End
12.1.14 Unclear Grids in the Tables in the MML Online Help

The grids in the tables are not clear in MML online help when users log in to the
LMT by some computers. To solve the problem, perform the following steps.
Context
The grids in the tables are not clear in MML online help, as shown in Figure
12-26.

BSC6910 UMTS
Figure 12-26 Unclear Grids in the Tables in the MML Online Help
Procedure
Step 1 In the menu of the IE browser, choose Tools > Compatibility View Settings. In
the displayed Compatibility View Settings dialog box, select Display all
websites in Compatibility View.
Step 2 Restart the browser and log in to the LMT to check the MML online help. The
problem is solved.
----End
12.1.15 The "App Center" Web Page Is Automatically

Displayed When Firefox Is Used to Browse the LMT
When you use Firefox to browse the LMT, if you press F1 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

BSC6910 UMTS
12.1.16 "Permission Denied" or "Access Denied" is Displayed

When IE Is Used to Browse the LMT
When you log in to the LMT through IE, a Permission Denied or Access Denied
message is displayed.
Prerequisites
The LMT cannot be visited due to errors in IE. An error message is displayed in the
status bar, as shown in Figure 1.
Figure 12-27 Error message in IE
Double-click the error message. A Permission Denied or Access Denied message

is displayed.
Context
The causes are as follows:
● The IE settings are modified when you log in to the LMT through IE, such as
the settings of the proxy. In this case, the access rights to the LMT page files
are changed, leading to access failures.
● Automatic configuration in the Local Area Network (LAN) Settings dialog
box is enabled, as shown in Figure 2. If Automatic configuration is enabled,
some uniform resource locators (URLs) will be allocated to other security
domains. Different security domains have different restrictions on access
rights. As a result, access failures occur.
Figure 12-28 Automatic configuration enabled

BSC6910 UMTS
Procedure
● Method 1: Do not modify IE settings when you log in to the LMT through IE.
● Method 2: Log out of the LMT when the Permission Denied or Access
Denied message is displayed. Restart IE and log in to the LMT again.
----End
12.1.17 MML Command Failed to Be Executed or No Response

to Tracing Tasks After the Browser Is Upgraded to IE8
After the browser is upgraded from IE6 to IE8, some cache files cannot be
removed. As a result, the system displays a Please check the MML macro
configure file! message when an MML command is executed, or there is no
response after tracing tasks are created. To solve this problem, you need to
manually remove cache files and cookies.
Context
● When MML commands are executed, the system displays a Please check the
MML macro configure file! message, as shown in Figure 12-29.
Figure 12-29 System message "Please check the MML macro configure file!"
● There is no response after tracing tasks are created.
Procedure
Step 1 On the menu bar of the IE browser, choose Tool > Internet Options. The Internet
Step 2 Click General > Browsing history and click Delete. The Delete Browsing History
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.

BSC6910 UMTS
Step 6 Click View files in the Temporary Internet Files and History Settings dialog box,
remove all displayed files, and close the Internet Options dialog box.
----End
12.1.18 Settings on the LMT Failing to Take Effective

After a successful login to the LMT, the previous settings, such as system settings,
do not take effect. To solve this problem, perform the following steps:
Procedure
Step 1 To clear the cache and cookies in the browser, perform the steps shown in the
following table.
Browser Type Handling Procedure
Firefox 1. Open the Firefox browser, and

choose Tools > Clear Private Data
from the menu bar.
2. In the displayed Clear Private Data
dialog box, select the Cache,
Cookies, and Offline Website
Datacheck boxes, and click Clear
Private Data Now.
Internet Explorer 7 1. Open the Internet Explorer, and

choose Tools > Internet Options
from the menu bar. The Internet
2. On the General tab page, click
Delete. The Delete Browsing
History dialog box is displayed.
3. To delete the files, click Delete
Files and then click OK in the
displayed dialog box. To delete the
cookies, click Delete Cookies and
then click OK in the displayed
dialog box.
4. In the Delete Browsing History
dialog box, click OK and close the
Internet Options dialog box.

BSC6910 UMTS
Internet Explorer 8 or 9 or IE10 or IE11 1. Open the Internet Explorer, and

3. Clear the Preserve Favorites
website data check box and select
the Cookies and Temporary
Internet files check boxes. Then,
click Delete and close the Internet
Options dialog box.
----End
12.1.19 The LMT login page of a host NE or built-in NE fails to

be opened
If a user visits the LMT through a browser, the LMT login page is being loaded for
a long period of time after the user clicks the icon of the host NE or built-in NE.
When the preceding problem occurs, perform the following operations.
Procedure
● To clear the cache and cookies in the browser, perform the steps shown in the
following table.

choose Tools > Clear Private
Data from the menu bar.
2. In the displayed Clear Private
Data dialog box, select the
Cache, Cookies, and Offline
Website Datacheck boxes, and
click Clear Private Data Now.
3. The operations take effect after
the browser restarts.

BSC6910 UMTS

displayed dialog box. To delete
the cookies, click Delete Cookies
and then click OK in the
displayed dialog box.
Internet Explorer 8 or 9 or 10 or 11 1. Open the Internet Explorer, and

website data check box and
select the Cookies and
Temporary Internet files check
boxes. Then, click Delete and
close the Internet Options dialog
box.
----End
12.1.20 No progress message can be reported on the Web

LMT.
When you execute a progress command on the MML or GUI module of the Web
LMT, no progress message can be reported. As a result, the command execution
result is unknown, or the GUI function fails.

BSC6910 UMTS
Context
When the Web LMT is running on the IE for a long period of time, there is a low
probability that the system timer function fails. If this occurs, the Web LMT
becomes abnormal.
Procedure
Step 1 Close the IE. Then, open the IE and log in to the Web LMT again.
----End
12.1.21 What Do I Do If A Message "Stop running this script?"

Is Displayed?
This section describes how to solve the problem that a message "Stop running this
script?" is displayed during script execution on the LMT.
Context
When it takes a long time to execute certain scripts, you are prompted with the
message "Stop running this script?", indicating whether to continue the script
execution.
To solve this problem, download the file at http://download.microsoft.com/
download/5/9/5/595D11B8-A0FD-4EA0-BF0D-F113258FC28A/
MicrosoftFixit50403.msi.
Procedure
Step 1 Install the downloaded file.
Step 2 Restart the computer, and then log in to the LMT to check whether this problem
has been solved.
----End
12.2 Java-related FAQs

This section describes Java-related common problems that hinder the normal use
of the LMT and corresponding handling procedures.
12.2.1 Help for Installing and Using the Java Plug-in

The Java plug-in used by LMT modules, including Batch, Trace, Monitor, and
Device Maintenance, is the Java runtime environment(JRE). You need to install the
Java plug-in(32-bit Java plug-in) before using these modules. You can try the
following methods to solve problems about installing or using Java plug-in.
Context
When a user logs in to the LMT, it checks the version of the installed java plug-in.
The following problems may occur when a user logs in to or use the LMT:

BSC6910 UMTS
1. A tooltip with the message "java plug-in is not found" is displayed on the
login interface.
2. A tooltip with the message "please download and install the recommended
Java plug-in" is displayed on the login interface.
3. LMT modules, including Batch, Trace, Monitor, and Device Maintenance,
cannot be used even after the java plug-in of a recommend version is
installed.
Procedure
● For the first problem, perform the following steps to check whether the java
plug-in is successfully installed:
a. On the windows system, click StartRun, enter CMD in the text box, and
press the Enter key. Enter java -version in the run window and press the
Enter key to view the current java plug-in version.
You can log in to the LMT even if the Java plug-in is not installed, but LMT modules,
including Batch, Trace, Monitor, and Device Maintenance cannot be used. You can
obtain the Java plug-in from the official website of Java.
b. If Java plug-ins of multiple versions are installed on the computer, the
current active Java plug-in version can be viewed on the Java control
panel. Select Control PanelJava, and click the Java icon to display the
Java control panel. Select the Java tab page, click View, and click the
User tab page in the displayed window to view and select the Java plug-
in version.
You may view the Java plug-in version on the Java control panel even when this plug-
in has been uninstalled. Therefore, ensure that the selected Java plug-in version is
available.
When Java plug-ins of more than one version are installed on the computer, they may
be incompatible. You are advised to uninstall the java plug-ins of versions that are not
required and use the recommend version. You can install or uninstall Java plug-ins on
the Windows control panel.
c. If the Java plug-in is successfully installed and you are using the IE
browser, you can ignore the tool tips and continue using the LMT. You
can also try to clear the tool tips using the following methods:
▪ If you are using IE browser, choose ToolsManage Add-ons. In the

displayed window, click Toolbars and Extensions, select All add-ons
in the Show combo box and ensure that the plug-ins Deployment
Toolkit and isInstalled Class are enabled.
▪ If you are using Firefox browser, open the Add-ons window, select
the Plugins tab page, and ensure that the installed Java plug-in is
enabled.
▪ Restart the browser, and log in to the LMT again.
If the Java plug-in is enabled in the IE browser and the tool tips still exist, choose
ToolsInternet Options, select the Advanced tab page, and click Reset.

BSC6910 UMTS
● The second problem indicates that you have installed a Java plug-in not
supported by the LMT. You can continue using the LMT, but some modules,
including Batch, Trace, Monitor, and Device Maintenance, may become
abnormal. You are advised to install the Java plug-in of a recommended
version.
When a Java plug-in of a later version has been installed, a java plug-in of an earlier
version installed afterward will not be activated. Tool tips with the message "please
download and install the recommended Java plug-in" will also be displayed on the login
interface even if the earlier version is supported by the LMT. If you need to activate the
Java plug-in version of the earlier version, first uninstall the one of the later versions.
● As for the third problem, the Java applet is forbidden by default because the
security is enhanced in JRE 1.8. Some tool tips will also be displayed before
the applet is executed. You can try the following methods to solve this
problem:
– Click the Java icon in the Windows control panel and select the Security
tab page in the Java control panel. Set Security Level to High and add
the current website to Exception Site List.
– If the Application Blocked by Security Settings dialog box is displayed,
or an error message is displayed on the LMT interface, you can
reconfigure Java security level or Exception Site List.
– When other exceptions occur, perform the following operations to delete
temporary Java files: Close the browser. In the Java Control Panel dialog
box that is displayed, select the General tab and click Settings. In the
dialog box that is displayed, click Delete Files.
----End
12.2.2 LMT Fails to Function Properly When Error Occurs in

Mixed Code Security Verification of JRE
This section describes how to solve the problem that the LMT does not respond or
responds incorrectly when users perform a function on the LMT.
Prerequisites
The LMT does not respond or responds incorrectly when users manage progress,
process MML commands in batches, trace messages, or perform monitoring.
Viewing the displayed message on the Java control panel, users find that the
following error is reported:
java.lang.SecurityException: class "com.swimap.lmt.util.mml.MMLHandler"'s signer information does not
match signer information of other classes in the same package at
java.lang.ClassLoader.checkCerts(ClassLoader.java:807) at
java.lang.ClassLoader.preDefineClass(ClassLoader.java:488) .......
Context
Java Runtime Environment (JRE for short) is a compulsory third-party component
for the LMT to run. Mixed code security verification is introduced in version
1.6.0_19 of JRE. With the function, codes are verified. If codes are found to be
untrustable, four operation options displayed in Figure 12-30 are provided.
Changing the default option as described below solves the previous problem.

BSC6910 UMTS
Figure 12-30 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
12.2.3 Tracing and Monitoring Functions Cannot Be Used

Tracing and monitoring functions cannot be used after a successful login to the
LMT. Solve this problem by using the following methods.

BSC6910 UMTS
Context
When a tracing or monitoring function is performed on the LMT, an error message
"Error. Click for details" is displayed and the Application Error dialog box is
displayed, as shown in Figure 12-31.
Figure 12-31 Application Error
After clicking Details, detailed error information is displayed. You need to correct
the error based on the error type as follows:
● If the "java.lang.ClassNotFoundException" error is displayed, perform steps 1
and 2.
● If the "java.lang.NullPointerException" error is displayed, perform steps 2.

● If the "netscape.javascript.JSException" error is displayed, perform step 3.
● If this problem occurs in Citrix Farm networking, you need to perform related
steps on the Citrix Farm server rather than on the local PC. If you have no
permission to log in to the Citrix Farm server, you cannot directly access
Windows Control Panel on the Citrix Farm server. To access it, right-click the
Java icon on Windows system tray on the local PC and choose Open Control
Panel from the short-cut menu. The following figure shows the window:

BSC6910 UMTS
● If this problem cannot be solved by performing the following steps, uninstall

and reinstall Java.
● This problem is caused by a Java defect. For details about this defect, visit
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6967414.
Procedure
Step 1 Enable the next-generation Java plug-in again.
1. Open Control Panel in the Windows operating system and double-click Java.
The Java Control Panel dialog box is displayed. In the Java Control Panel
dialog box, click the Advanced tab, clear Enable the next-generation Java
Plug-in (requires browser restart) under Java Plug-in and click OK.
2. Select Enable the next-generation Java Plug-in (requires browser restart)
by referring to step a and click OK. Figure 12-32 shows the window.

BSC6910 UMTS
Figure 12-32 Enabling the next-generation Java plug-in
3. Restart the browser to enable the new setting to take effect.

Step 2 Delete temporary Java files.
1. If this problem persists after performing step 1, delete temporary Java files.
The Java 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 12-33.

BSC6910 UMTS
Figure 12-33 Checking the amount of disk space set for storing temporary
files
4. Check the amount of disk space used for storing temporary Java files in the
directory where temporary Java files are saved. The part marked in red frame
in Figure 12-34 shows the directory. This amount is greater than the preset
one.

BSC6910 UMTS
Figure 12-34 Directory where temporary Java files are saved
5. Delete folders in this directory manually or by clicking Delete Files shown in

the figure above.
Before deleting folders in this directory, close all running LMT clients.
6. Log in to the LMT again to check whether this problem is solved.
Step 3 Install Windows operating system patch KB960714.
1. 12.3.1 Installing OS Patches
----End
12.2.4 Chinese Characters Displayed in the Tracing and

Monitoring Windows
When users successfully log in to the LMT after an upgrade, they can see Chinese
characters in the tracing and monitoring windows and in the saved files. To solve
this problem, perform the following steps:
Procedure
Step 1 Close all browsers that are opened at the moment.
Step 2 Clear temporary Java files.
1. If this problem persists after performing step 1, delete temporary Java files.
The Java Control Panel dialog box is displayed.

BSC6910 UMTS
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 12-35.
Figure 12-35 Checking the amount of disk space set for storing temporary
files
4. Check the amount of disk space used for storing temporary Java files in the
directory where temporary Java files are saved. The part marked in red frame
in Figure 12-36 shows the directory. This amount is greater than the preset
one.

BSC6910 UMTS
Figure 12-36 Directory where temporary Java files are saved
5. Delete folders in this directory manually or by clicking Delete Files shown in

the figure above.
Before deleting folders in this directory, close all running LMT clients.
6. Log in to the LMT again to check whether this problem is solved.
----End
12.2.5 LMT Fails to Function Properly during the tracing/

monitoring/batch processing
After you log in to the LMT and perform operations on it for a while, batch
processing operations may suddenly fail without any error messages. Alternatively,
after a tracing or monitoring task is created, the task page is not opened. There is
no response or any error message. The NE task list shows that this task has been
successfully created. After a tracing or monitoring task is created, a prompt
message "The tunnel does not exist. Some functions are unavailable" is displayed.
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 right-click
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

BSC6910 UMTS
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 12-37 shows the dialog box.
Figure 12-37 Java Control Panel dialog box
Step 3 Close all opened browsers and delete Java temporary files. To delete Java
temporary files, perform the following operations:
The Java Control Panel dialog box is displayed, as shown in Figure 12-38.

BSC6910 UMTS
Figure 12-38 Java Control Panel dialog box
2. In the Java Control Panel dialog box, click Settings. The Temporary Files
Settings dialog box is displayed, as shown in Figure 12-39.
Figure 12-39 Temporary Files Settings dialog box

BSC6910 UMTS
3. In the Temporary Files Settings dialog box, click Delete Files to delete Java
temporary files and click OK.
Step 4 Log in to the LMT again.
----End
12.2.6 Interfaces for Performing Tracing or Monitoring Tasks

Blinking
Interfaces for performing tracing or monitoring tasks blink.
Context
Java Applet in the IE browser is incompatible with HTML elements when they are
stacked together. As a result, interfaces (stacked in the Java Applet) for
performing tracing and monitoring tasks blink. This problem does not affect the
function but deteriorates user experience.
Procedure
● This problem occurs only on the IE browser. Use the Firefox browser to avoid
this problem.
----End
12.2.7 Java Installation Fails

During Java installation, the message "Error 25099, Unzipping core files failed." is
displayed. To solve the problem, perform the following steps:
Procedure
Step 1 Delete all files in the Java installation path. The default installation path is C:
\Program Files\Java\jre6\.
Step 2 If step 1 fails because files are locked or in use, restart the system and repeat step
1.
Step 3 Reinstall Java.
----End
12.2.8 Changing Settings for the Next-Generation Java Plug-in

Fails
When changing settings for Enable the next-generation Java Plug-in, you are
prompted with a message indicating that the changing fails because one or more
browsers are running. As a matter of fact, no browser is running. The following
figure shows the message: To solve the problem, perform the following steps.

BSC6910 UMTS
Context
Changing Settings for Next-Generation Java Plug-in Fails, the error message is
Figure 12-40 Unable to change Java Plug-in settings
This problem is caused by a Java defect. The setting changing fails not because
browsers are running but because the user has no permission to perform the
operation.
To change the settings, the user must belong to the Power Users group or have
more rights.
Perform the following steps to grant the user more rights.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account
authorized for the administrator's operations. Right-click My computer and
choose Manage from the shortcut menu.
Step 2 In the Computer Management window, choose System toolsLocal Users and
GroupsGroups and double-click Power Users in the right pane of the window, as
shown in the following figure:

BSC6910 UMTS
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:

BSC6910 UMTS
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:

BSC6910 UMTS
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.
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 Plug-in.
----End
12.2.9 How to Handle a Web Page Error or Java Error

Displayed on the LMT
Any of the following occurs during the login to the LMT: the controller version
displayed on the LMT is not the actual version after a controller upgrade or
rollback. A Java error message is displayed. A JavaScript error message is displayed
on the status bar in the browser. In other words, an exclamation mark is displayed
at the bottom left corner of the status bar.
Context
When the browser cache or Java Applet cache is insufficient, any of the following
cases will result in the inconsistency between the LMT displayed in the browser
and the actual LMT.
● After a controller version upgrade or rollback, the browser fails to obtain the
new Javascript, JAR files, and other files from the LMT server. As a result, the
browser uses the preceding files saved before the controller version upgrade
or rollback.
● The preceding files are damaged during the use of the LMT.
Procedure
following table.


BSC6910 UMTS


box.
● To clear the Java Applet, perform the following steps.
Before you clear the Java Applet, exit the LMT. Otherwise, some loaded data
will be lost and unexpected errors will occur.
a. Choose Start > Control Panel. The Control Panel is displayed.

b. Double-click Java in the displayed window. The JAVA Control Panel is
displayed.

BSC6910 UMTS
c. On the General tab page, click Settings. The Temporary Files Settings
d. Click Delete Files. In the displayed Delete Temporary Files dialog box,
select the Applications and Applets and Trace and Log Files check
boxes, and click OK.
e. In Java Control Panel, click OK.
f. The operations take effect after the browser restarts.
----End
12.2.10 Displaying the Java Security Warning

The Java security warning is displayed during the use of the progress
management, batch processing, tracing, or monitoring function on the LMT. Solve
this problem by using the following methods.
Procedure
Step 1 The error message Do you want to run this application? is displayed in the
Security Warning dialog box.
For Java 1.8, click I accept the risk and want to run this application. and click
Run. Then, click Continue.
----End
12.2.11 Failure in Verifying the Verification Code During the

Login to the LMT
The verification code needs to be entered when a user logs in to the LMT.
However, the message "Enter a correct verification code" is displayed even though
the user enters the correct verification code for many times. To solve this problem,
perform the following steps:
Procedure
following table.


BSC6910 UMTS


box.
● To clear the Java Applet, perform the following steps.
Before you clear the Java Applet, exit the LMT. Otherwise, some loaded data
will be lost and unexpected errors will occur.
a. Choose Start > Control Panel. The Control Panel is displayed.

b. Double-click Java in the displayed window. The JAVA Control Panel is
displayed.

BSC6910 UMTS
c. On the General tab page, click Settings. The Temporary Files Settings
d. Click Delete Files. In the displayed Delete Temporary Files dialog box,
select the Applications and Applets and Trace and Log Files check
boxes, and click OK.
e. In Java Control Panel, click OK.
f. The operations take effect after the browser restarts.
----End
12.2.12 The Application Blocked by Security Settings Dialog

Box Is Displayed When Batch Processing, Tracing, Monitoring,
or Device Maintenance Is Enabled
After the JRE is installed or upgraded, the Application Blocked by Security Settings
dialog box is displayed when the tab page related to batch processing, tracing,
monitoring, or device maintenance is open. Click OK, and the application cannot
be run dialog box is displayed, indicating that the batch processing, tracing,
monitoring, or device maintenance function is unavailable.
Context
A function is introduced to the JRE later than Java 1.7. 10 to control when and
how to run untrusted Java applications contained in a web page. The untrusted
Java application refers to an application with digital signature applied by an
unknown issuer or without a certificate issued by a trusted certificate authority.
The default security level is set to High, indicating that the untrusted Java
applications will be blocked.
Procedure
Step 1 Reconfigure the Java security level or add Exception Site List.
● On the Control Panel page, click Java. In the displayed Java Control Panel
dialog box, click Security. On the displayed Security tab page, select Enable
Java content in the browser, set Security Level to Medium, and then click
Apply.
● Alternatively, click Edit Site List on the Security tab page in the Java Control
Panel dialog box to add the sites accessing the LMT to the site list. If this
method is used, the Java security level does not need to be reconfigured. For
the sites added in the site list, mark whether the access to the LMT through
HTTPS or HTTP. For example, https://10.20.198.33 or http://10.30.192.60.
Step 2 Specify Enable the next-generation Java Plug-in(requires browser restart).

1. In the Java Control Panel dialog box, click Advanced. On the displayed
Advanced tab page, select Java Plug-in, clear Enable the next-generation
Java Plug-in(requires browser restart), and then click OK.
2. Select Enable the next-generation Java Plug-in(requires browser restart)
according to operations in step 2.a, and click OK.
3. Restart the browser to make the settings take effect.

BSC6910 UMTS
Step 3 Delete temporary Java files.

1. In the Java Control Panel dialog box, click General. On the displayed
General tab page, click Settings. The Temporary Files Settings dialog box is
displayed.
2. Close all running LMT windows and click Delete Files.
Step 4 Log in to the LMT again. When enabling any of the batch processing, tracing,
monitoring, and device maintenance functions, select I accept the risk and want
run this application on the displayed do you want run this application? dialog
box and click Run. If the Do you want to continue? dialog box is displayed, click
Continue.
----End
12.2.13 What Do I Do If A Message that Your Java version is

out of date Is Displayed?
If you are prompted with the message that Your Java version is out of date when
logging in to the WebLMT, follow instructions provided in this session.
Context
The JRE installed on the computer is not of the latest version and an upgrade to
the latest version is recommended by Java. To continue to use the WebLMT and
update the JRE later, it is good practice to perform the procedure described below.
Procedure
Step 1 In the Your Java version is out of date dialog box, select the Do not ask again
until the next update is available check box.
Step 2 Click Later.
----End
12.3 Other FAQs

This section describes common problems, except Java- or browser setting-related
problems, that hinder the normal use of the LMT and corresponding handling
procedures.
12.3.1 Installing OS Patches

In a Microsoft Windows operating system (OS), you need to install patch
KB944338, KB938397 or KB960714 if the OS and IE are in a certain version.
Context
● Patch KB960714 solves the problem of Java console output error. Therefore,
the Java application can be loaded successfully on the LMT.

BSC6910 UMTS
● Patch KB944338 improves the performance of the LMT by increasing the

speed of visiting a web page. Therefore, the LMT running rate can be
increased.
● If Windows 7 operating system is used, Windows patches do not need to be
installed.
Procedure
Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or
Remove Programs icon.
Step 2 In the displayed Add or Remove Programs window, select Show updates. Check
whether patches KB944338, KB938397 and KB960714 are present in the list of
Currently installed programs.
● If the patches are present, the task is complete.
● 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.
● 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
● Patch KB944338 needs to be installed when the OS version is Windows 2000

SP4 or Windows Server 2003 SP1/SP2.
● 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.
● When the Windows 2008 OS and Internet Explorer 7 or later are used, the OS
patch does not need to be installed.
● To download patch KB944338 or KB960714, go to http://www.microsoft.com/

downloads.
● To download patch KB938397, go to http://support.microsoft.com/?kbid=938397.
● Download a suitable patch according to the OS version and IE version.
----End

BSC6910 UMTS
12.3.2 Changing the Computer Time During the LMT Use

Prohibited
Changing the computer time during the LMT use is prohibited. Changing the
computer time causes some functions of the LMT to stop functioning normally.
For example, the OMU time fails to refresh normally; tracing data and monitoring
data fail to refresh normally; progress management fails to refresh normally.
12.3.3 Corrupted Characters Appearing When the csv File Is

Opened in UTF-8 Coding
If a csv file in UTF-8 coding is saved on the LMT with non-English characters in it
and the csv file is opened in the Excel format by using the regular method, all the
non-English characters are displayed as corrupted characters. In this case, open
the csv file by using the import method in Excel.
Procedure
● If the Excel version is earlier than Office 2007, perform the following
operations:
a. On the menu bar of Excel, choose Data > Import External Data >
Import Data. Then the Select Data Source dialog box is displayed.
Figure 12-41 shows the dialog box.
Figure 12-41 Operation interface for importing data in Excel
b. In the Select Data Source dialog box, select the csv file in UTF-8 coding.
Then the Text Import Wizard - Step 1 of 3 dialog box is displayed.
Figure 12-42 shows the dialog box. Select 65001:Unicode(UTF-8) in File
origin.

BSC6910 UMTS
Figure 12-42 Text import wizard-step 1
c. Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is
displayed. Figure 12-43 shows the dialog box. Select Comma under
Delimiters.
d. Click Finish. Then the Import Data dialog box is displayed. Figure 12-44
shows the dialog box.

BSC6910 UMTS
Figure 12-44 Interface after data importation is finished
e. Click OK. Then the file is displayed properly.

● If the Excel version is Office 2007 or later, perform the following operations:
a. On the menu bar of Excel, choose Data > From Text. Then the Import
Text File dialog box is displayed. Figure 12-41 shows the dialog box.
Figure 12-45 Operation interface for importing data in Excel
b. In the Import Text File dialog box, select the csv file in UTF-8 coding.
Then the Text Import Wizard - Step 1 of 3 dialog box is displayed.
Figure 12-42 shows the dialog box. Select 65001 : Unicode (UTF-8) in
File origin.
c. Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is
displayed. Figure 12-43 shows the dialog box. Select Comma under
Delimiters.

BSC6910 UMTS
d. Click Finish. Then the Import Data dialog box is displayed. Figure 12-44
shows the dialog box.
Figure 12-48 Interface after data importation is finished
e. Click OK. Then the file is displayed properly.

----End
12.3.4 Maximum Number of LMT Clients That Can Be Started

on One PC Simultaneously
You can have multiple LMT clients started on one PC. Starting too many LMT
clients simultaneously, however, affects maintenance performance. As being
limited by the PC memory and maximum number of dialog boxes that can be
opened on the IE browser, a PC does not support 32 LMT clients to be started
simultaneously.
In normal maintenance, the maximum number of LMT clients that can be
simultaneously started on one PC is as follows:

BSC6910 UMTS
● One PC with 2 GB memory or larger supports 16 LMT clients to be started

simultaneously.
● One PC with 1 GB memory supports 8 LMT clients to be started
simultaneously.
● One PC with 512 MB memory supports 4 LMT clients to be started
simultaneously.
12.3.5 Any Further Operation Performed When Some LMT

Web Pages Fail to Update Causes the Web Pages to Turn
Blank
Some LMT Web pages fail to update when batch processing, tracing, or
monitoring is in use. Any further operation causes the Web pages to turn blank. If
you restart the function, the Web page returns to normal. To prevent this problem,
perform the following operations to add an environment variable.
Procedure
Step 1 On the LMT PC, select My Computer and right-click Properties from the shortcut
menu. The System Properties dialog box is displayed.
Step 2 In the System Properties dialog box, click the Advanced tab and click
Environment Variables. The Environment Variables dialog box is displayed.
Step 3 In the Environment Variables dialog box, click New. The New User Variable
Step 4 In the New User Variable dialog box, set Variable name to
JPI_PLUGIN2_NO_HEARTBEAT and Variable value to 1. Then click OK.
Step 5 In the Environment Variables dialog box, click OK.
Step 6 In the System Properties dialog box, click OK to finish adding the environment
variable.
----End
12.3.6 Configuring the HTTPS Login Mode

This section describes how to configure the HTTPS login mode and a security
certificate. Users can log in to the LMT through either HTTP or HTTPS. The login
mode is configurable.
Prerequisites
● You have logged in to the LMT using a Built-In Administrator Account or
admin Account.
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://

BSC6910 UMTS
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
takes effect. In this step, set TG to ACTIVE and MNAME to weblmt.
NOTICE
1. Running this command disconnects all online users from the LMT.
2. Normally, the restart is complete within 5 seconds. After the restart is complete,
the change takes effect when users log in to the LMT again.
----End
12.3.7 Unable to Save Tracking and Monitoring Data

When a tracking or monitoring task (such as the UE tracking task) is running on
the LMT, it is possible that the vast amounts of tracking or monitoring data
cannot be saved even with sufficient hard disk space. Solve the problem by using
the method described in the procedure part.
Context
This problem arises when the operating system enables the system recovery
function that monitors changes of the files on the hard disk and consumes some
hard disk space. With insufficient hard disk space, the system displays "Insufficient
hard disk space", and if a tracking or monitoring task is running on the LMT, it is
likely that the tracking or monitoring data cannot be saved.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account
authorized for the administrator's operations. Right-click My computer and
choose Properties.
Step 2 In the "System Properties" window, click System Recovery, select Disable System
Recovery on All Drivers, and click Submit, as shown in Figure 12-49.

BSC6910 UMTS
Figure 12-49 System properties dialog box
----End
12.3.8 BTS Nodes Cannot Be Displayed Under Device

Navigation Tree
After a successful login to the LMT, you may find that BTS nodes cannot be
displayed under Device Navigation Tree. After upgrading the browser, you find
that the nodes can be displayed normally. This problem occurs because data under
Device Navigation Tree on the LMT is compressed whereas Internet Explorer 6 SP2
does not support compression of chunked data. Solve this problem by using either
of the following methods.
Context
BTS nodes cannot be displayed under Device Navigation Tree, as shown in Figure
12-50.

BSC6910 UMTS
Figure 12-50 BTS nodes cannot be displayed
Procedure
● Method 1: For the operating system Windows XP Service Pack 2 or 3, install
the KB982381 patch. To download this patch, visit http://www.microsoft.com/
downloads.
● Method 2: Upgrade the browser. You are advised to upgrade it to Internet
Explorer 8.
----End
12.3.9 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.

BSC6910 UMTS
This process is a system process and therefore cannot be closed directly. To close
it, perform the following steps.
Procedure
Step 1 In Windows, choose StartRun and enter regedit to open Registry Editor.
Step 2 Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\HTTP.
Step 3 Change the DWORD value of Start to 0.
Step 4 Restart the PC and log in to the LMT again.
----End
12.3.10 Slow Response During an LMT Login

The LMT responses slowly when the users are trying to log in to the LMT. To solve
the problem, perform the following steps:
Procedure
Step 1 In the Windows 2003 and Windows XP operating system (OS), choose Start >
Control Panel, and then click Add/Remove Programs, the Windows
Components Wizard dialog box is displayed.
Step 2 In the Windows Components Wizard dialog box, deselect Upload Root
Certificates, as shown in the following figure. Then click Next to complete the
modification.

BSC6910 UMTS
Figure 12-51 Deselect Upload Root Certificates
----End
12.3.11 Batch Execution of MML Commands Fails Because

Some MML Commands Contain Invisible Carriage Returns or
Line Feeds
After line feeds (LF) are deleted from MML command scripts copied to Batch,
command execution fails.
Context
Copy the MML commands failing to be executed to an UltraEdit file. It is found
that these MML commands are displayed in two lines. In UltraEdit, click to
view these MML commands in the binary format. A redundant carriage return
(CR) 0x0D stays at the LF location of the MML command each. See Figure 12-52.

BSC6910 UMTS
Figure 12-52 Viewing an MML command in the binary format using UltraEdit
In the Windows operating system (OS), the CR 0x0D and LF 0x0A must be used
pairwise. The unpaired CRs or LFs cannot be deleted. As a result, the MML
commands fail to be executed.
Procedure
Step 1 Copy the MML commands failing to the executed to an UltraEdit or notepad file
and delete all LFs and CRs. Then, copy these commands back to Batch and
execute them again.
----End
12.3.12 How to Handle Shortcut Key Invalidation

Shortcut keys are defined on the LMT. When logging in to the LMT through a web
page, you may fail to use the corresponding function by pressing a shortcut key. In
this case, the shortcut key becomes invalid. For example, you cannot stop pinging
by pressing Ctrl+Q in the MML Command window. This is because the same
shortcut key is preferentially used by another running program on the PC, which
leads to a shortcut key conflict.
Procedure
Step 1 Check all running programs on the PC. Find the program using the same shortcut
key settings as the LMT.
Step 2 Modify the program shortcut key settings which are the same as those on the LMT
or stop the program when you use the LMT.
----End
12.3.13 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.

BSC6910 UMTS
Context
A tracing task may generate multiple tracing files, which depends on the traced
messages.
If you close the trace dialog box, the last tracing file cannot be uploaded to the
specified directory. The last tracing file refers to the one being generated. The
generated tracing files can be uploaded.
Procedure
Step 1 In the Trace Navigation Tree, double-click Manage Trace Task. The Manage
Trace Task tab page is displayed.
Step 2 Query the UE tracing or IOS tracing task being performed, select a task, and click
Delete. The preceding settings enable the tracing result file being generated to be
uploaded to the specified directory.
----End
12.3.14 Error Dialog Box Displayed When Online Help Is

Opened
When Online Help is opened on the LMT, a dialog box is displayed with the
following information: An error on this web page disables the proper running of
the web page. As a result, Online Help cannot be used. To solve the problem,
perform the following steps:
Procedure
Step 1 1. Uninstall the Google chrome frame plug-in.
Step 2 2. Clear the IE browser cache.
Step 3 3. Log in to the LMT again
----End
12.3.15 Garbled Characters Displayed in the Chinese Names of

Files in the File Manager and These Files Failing to Be
Removed
When users view the files on the OMU using the LMT file manager, they can see
garbled characters in the Chinese names of the files, and the files cannot be
removed. To solve this problem, perform the following steps:
Procedure
Step 1 1. Use a third-party tool, such as the FileZilla, to upload a file to the OMU. Before
uploading this file, specify the file name using the gb2312 coding and save the
file. In this way, the file manager can manage this file.
Set the FileZilla as follows: Choose FileSite Manager. A Site Management dialog
box is displayed. Select the corresponding site from My Sites. On the Charset tab

BSC6910 UMTS
page, select Use custom charset, set Encoding to gb2312, and click Connect. The
encoding is modified. Then, upload the file.
Step 2 On the LMT, click System Settings. Select Chinese in Language, and click OK.
Open the file manager to view the file, and you can see a normally displayed file
name. The file can be removed now.
----End
12.3.16 Failure to Obtain the Verification Code When Users

Attempt to Log In to the Web LMT After a Version Upgrade or
Rollback
When users attempt to log in to the Web LMT after the product version software
is upgraded or rolled back, the verification code is not displayed and the user login
fails.
Context
When users attempt to log in to the Web LMT after the product version software
is upgraded or rolled back, they refresh the page for several times but still cannot
obtain the verification code. To ensure the normal operation of the LMT, perform
the following operations:
Procedure
● Internet Explorer
a. On the main menu of Internet Explorer, choose Tools > Internet Options.
The Internet Options dialog box is displayed.
b. Click Delete and perform the operation according to the Internet Explorer
version.
▪ If the Internet Explorer version is 8.0 or 9.0, click Temporary Internet

files and click Delete to delete temporary files.
▪ If the Internet Explorer version is 10.0 or 11.0, click Temporary

Internet Files and Website Files and click Delete to delete
temporary files and website files.
c. Click OK to close the Internet Options dialog box.
If any of the preceding steps cannot be performed because of browser version

reasons, set the browser to the active window and press [Ctrl] + [Shift] + [Del]. In the
displayed window, click Cache or Temporary Internet Files and Website Files, and
click Clear Now or Delete to delete temporary files.
● Firefox
a. On the main menu of FireFox, choose Tools > Options. The Options
b. Choose AdvancedNetwork, and perform the operation according to the
browser version.
▪ If the FireFox version is 10.0, click Clear Now in the Network dialog
box to delete files.

BSC6910 UMTS
▪ If the FireFox version is 17.0 or later, click Clear Now in the Cached
Web Content dialog box to delete files.
c. Click OK to close the Options dialog box.
If any of the preceding steps cannot be performed because of browser version

reasons, set the browser to the active window and press [Ctrl] + [Shift] + [Del]. In the
displayed window, select All for The necessary period for Time range to clear and
click Clear Now or Delete to delete files.
----End

Bsc6910 Umts Lmt User Guide(v100r021c10_02)(PDF)-En

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Bsc6910 Umts Lmt User Guide(v100r021c10_02)(PDF)-En

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bsc6910 Umts Lmt User Guide(v100r021c10_02)(PDF)-En

Uploaded by

Copyright:

Available Formats

BSC6910 UMTS

LMT User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. i

Product Name Product Version Solution Version

BSC6910 V100R021C10 RAN21.1

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. ii

3 Operation Rights Management......................................................................................... 36

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. iii

3.3.1 Defining Login Password Policies.................................................................................................................................43

4 Running MML Commands................................................................................................... 49

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. iv

5.4 Managing the Alarm Masking Switch of Derived Alarms...................................................................................... 72

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. v

7.3.4 AC Tracing.......................................................................................................................................................................... 111

8 Performance Monitoring................................................................................................... 154

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. vi

8.3.6.12 Monitoring Traffic on Non-Channelized ATM Optical Port....................................................................... 174

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. vii

8.4.3 Monitoring System Resources.................................................................................................................................... 204

9 Device Panel......................................................................................................................... 206

11 BSC Maintenance.............................................................................................................. 262

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. viii

12.1 Browser-related FAQs..................................................................................................................................................... 266

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. ix

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. x

This section provides information about the changes in different document

Change Change Description

Technical Adde None

Modif JRE 1.7.X is no longer supported. For details, see 2.1

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 1

Change Change Description

Change Change Description

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 2

Change Change Description

Mod ● Click FTP Tool. A help page is displayed, providing

Dele ● Deleted section "Configuring the FTP Server."

Editorial ● Added the permission and function processes required for

Change Change Description

Technical Added ● Added descriptions about Base Station Selection. For

Modifi ● Changed the recommended JRE version to 1.8.0.191.

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 3

Change Change Description

Delete ● Deleted the description that only 32-bit Java plug-ins

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 4

The Local Maintenance Terminal (LMT) is a web-based application that provides a

2.1 Configuration Requirements of the LMT PC

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 5

2.1 Configuration Requirements of the LMT PC

Table 2-1 Hardware requirements of the LMT PC

CP 1 2.8 GHz or above 866 MHz

Dis - 1024 x 768 or higher 1024 x 768

Et 1 10/100 Mbit/s 10/100 Mbit/s

Ot 5x1 Keyboard, mouse, Keyboard and mouse

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 6

Table 2-2 describes the software requirements of the LMT PC.