GJJ

BSC6900 UMTS
V900R011C00
LMT User Guide
Issue 08
Date 2011-03-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 08 (2011-03-28) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
BSC6900 UMTS
LMT User Guide About This Document
About This Document
Overview
This document describes the functions and relevant components of the BSC6900 Local
Maintenance Terminal (LMT). It also provides instructions for performing basic operation and
maintenance (OM) tasks of theBSC6900.
Product Version
The following table lists the product version related to this document.
Product Name Product Version
BSC6900 V900R011C00
Intended Audience
This document is intended for:
l Network engineers
l System engineers
l Field engineers
Organization
1 Changes in the BSC6900 UMTS LMT User Guide
This chapter describes the changes made in theBSC6900 UMTS LMT User Guide.
2 Introduction to LMT
The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) for users for easy operation and maintenance of the BSC6900. Users can
perform operations such as alarm management, trace management, performance monitoring,
and device maintenance. Users can also run MML commands and read the corresponding
execution results on the LMT.
Issue 08 (2011-03-28) Huawei Proprietary and Confidential iii

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

This chapter describes the management of operation rights, and provides instruction to manage
user accounts and command groups.
4 Running MML Commands
This chapter describes how to run MML commands on the LMT to operate and maintain the
BSC6900.
5 Alarm Management
This describes how to manage BSC6900 alarms through the LMT. Alarm management allows
you to analyze alarms more efficiently and facilitates troubleshooting.
6 Log Management
This chapter describes how to manage the BSC6900 logs through the LMT. Log files can be
saved in .txt and .log formats. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can manage the logs.
7 Trace Management
This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 trace
tasks can be performed simultaneously on the same LMT.
8 Performance Monitoring
This chapter describes how to monitor the BSC6900 performance. A maximum of 64 monitoring
9 Device Panel
This chapter describes how to manage the BSC6900 equipment by using the device and
emulation panels. You can use these panels to query for information about the boards, board
ports, board links, and board alarms.
10 FAQ
This chapter describes the frequently asked questions (FAQs) and the corresponding solutions.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
iv Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
LMT User Guide About This Document
Symbol Description
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

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

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

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

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Issue 08 (2011-03-28) Huawei Proprietary and Confidential v

BSC6900 UMTS
About This Document LMT User Guide
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

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

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
vi Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
LMT User Guide Contents
Contents
About This Document...................................................................................................................iii

1 Changes in the BSC6900 UMTS LMT User Guide..............................................................1-1
2 Introduction to LMT..................................................................................................................2-1
2.1 Configuration Requirements of the LMT PC..................................................................................................2-2
2.2 LMT Login and Exit.......................................................................................................................................2-4
2.3 Components of the LMT Window..................................................................................................................2-6
2.4 LMT Software.................................................................................................................................................2-9
2.4.1 Installing LMT Offline Tools...............................................................................................................2-10
2.4.2 FTP Client............................................................................................................................................2-11
2.4.3 FTP Server............................................................................................................................................2-13
2.4.4 Convert Management System..............................................................................................................2-14
2.4.5 Performance Browser Tool..................................................................................................................2-15
2.4.6 Traffic Recording Review Tool...........................................................................................................2-16
2.5 File Manager.................................................................................................................................................2-17
3 Management of Operation Rights..........................................................................................3-1

3.1 Concepts Related to Operation Rights Management......................................................................................3-2
3.1.1 Principles of Operation Rights Management.........................................................................................3-2
3.1.2 User Password........................................................................................................................................3-2
3.1.3 Command Group....................................................................................................................................3-3
3.1.4 User Type...............................................................................................................................................3-4
3.1.5 Operation Rights....................................................................................................................................3-4
3.1.6 Operation Time Limit.............................................................................................................................3-5
3.2 Management of User Accounts.......................................................................................................................3-6
3.2.1 Creating an External User Account........................................................................................................3-6
3.2.2 Modifying an External User Account....................................................................................................3-7
3.2.3 Deleting an External User Account........................................................................................................3-7
3.3 Management of User Passwords.....................................................................................................................3-8
3.3.1 Defining Login Password Policies.........................................................................................................3-8
3.3.2 Querying Login Password Policies........................................................................................................3-8
3.3.3 Changing the Password of the Active User Account.............................................................................3-9
3.3.4 Changing the Password of an External User Account...........................................................................3-9
3.4 Management of Command Groups...............................................................................................................3-10
Issue 08 (2011-03-28) Huawei Proprietary and Confidential vii

BSC6900 UMTS
Contents LMT User Guide
3.4.1 Querying a Command Group...............................................................................................................3-10

3.4.2 Setting the Command Group Name.....................................................................................................3-10
3.4.3 Changing the Commands in a Command Group.................................................................................3-10
4 Running MML Commands......................................................................................................4-1

4.1 Concepts Related to MML Commands...........................................................................................................4-3
4.1.1 Introduction to MML Commands..........................................................................................................4-3
4.1.2 Components of the MML Command Window......................................................................................4-5
4.1.3 Data Configuration Rights.....................................................................................................................4-6
4.1.4 Data Configuration Rollback.................................................................................................................4-6
4.2 Running an MML Command..........................................................................................................................4-7
4.3 Batch Processing MML Commands...............................................................................................................4-8
4.4 Setting MML Parameters................................................................................................................................4-9
4.5 Querying the Data Configuration Mode..........................................................................................................4-9
4.6 Querying Data Configuration Rights............................................................................................................4-10
4.7 Obtaining Data Configuration Rights...........................................................................................................4-11
4.8 Undoing/Redoing a Data Configuration Action............................................................................................4-12
4.9 Undoing/Redoing Multiple Data Configuration Actions..............................................................................4-13
5 Alarm Management...................................................................................................................5-1
5.1 Concepts Related to Alarm Management........................................................................................................5-2
5.1.1 Alarm Type............................................................................................................................................5-2
5.1.2 Alarm Severity.......................................................................................................................................5-3
5.1.3 Alarm-Managed Objects........................................................................................................................5-3
5.1.4 Alarm Box..............................................................................................................................................5-4
5.2 Managing Alarm Logs....................................................................................................................................5-5
5.2.1 Setting Storage Conditions of Alarm Logs............................................................................................5-5
5.2.2 Querying Storage Conditions of Alarm Logs........................................................................................5-5
5.3 Managing the Alarm Filter..............................................................................................................................5-5
5.3.1 Creating an Alarm Filter........................................................................................................................5-6
5.3.2 Deleting an Alarm Filter........................................................................................................................5-6
5.3.3 Querying an Alarm Filter.......................................................................................................................5-7
5.4 Managing the Filter of Derived Alarms..........................................................................................................5-7
5.4.1 Setting the Filter of Derived Alarms......................................................................................................5-7
5.4.2 Querying the Filter of Derived Alarms..................................................................................................5-8
5.5 Monitoring Alarms..........................................................................................................................................5-8
5.5.1 Browsing Alarms....................................................................................................................................5-9
5.5.2 Querying the Alarm Log........................................................................................................................5-9
5.5.3 Querying Alarm Handling Suggestions...............................................................................................5-10
5.5.4 Querying Alarm Configuration............................................................................................................5-10
5.5.5 Filtering Fault Alarms..........................................................................................................................5-11
5.5.6 Setting Alarm Attributes......................................................................................................................5-12
5.5.7 Manually Clearing an Alarm................................................................................................................5-12
5.5.8 Removing Alarms................................................................................................................................5-12
viii Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
5.5.9 Refreshing the Alarm Window............................................................................................................5-13

5.6 Managing the Alarm Box..............................................................................................................................5-13
5.6.1 Querying Alarm Box Information........................................................................................................5-14
5.6.2 Querying Number of Alarms with Different Severities.......................................................................5-14
5.6.3 Operating the Alarm Box.....................................................................................................................5-14
5.6.4 Querying the Alarm Box Filter Level..................................................................................................5-15
6 Log Management........................................................................................................................6-1
6.1 Log Types........................................................................................................................................................6-3
6.2 Querying Log Storage Conditions...................................................................................................................6-3
6.3 Setting Log Storage Conditions...................................................................................................................... 6-3
6.4 Querying Operation Logs................................................................................................................................6-4
6.5 Exporting Operation Logs...............................................................................................................................6-4
6.6 Querying Security Logs.................................................................................................................................. 6-5
6.7 Exporting Security Logs..................................................................................................................................6-5
6.8 Exporting Running Logs.................................................................................................................................6-6
6.9 Collecting Log Statistics................................................................................................................................. 6-7
7 Trace Management.....................................................................................................................7-1
7.1 Concepts Related to Trace Management.........................................................................................................7-2
7.1.1 Trace Principles......................................................................................................................................7-2
7.1.2 Management of Tracing Operation Rights.............................................................................................7-3
7.1.3 Trace Mode............................................................................................................................................ 7-3
7.2 UMTS Services...............................................................................................................................................7-4
7.2.1 Tracing Messages on the Iu Interface.....................................................................................................7-5
7.2.2 Tracing Messages on the Iur Interface...................................................................................................7-7
7.2.3 Tracing Messages on the Iub Interface...................................................................................................7-9
7.2.4 Tracing Messages on the Uu Interface.................................................................................................7-11
7.2.5 Tracing IP Messages............................................................................................................................7-13
7.2.6 Tracing MNCDT Messages.................................................................................................................7-14
7.2.7 Tracing UE Messages...........................................................................................................................7-14
7.2.8 Tracing Cell Messages.........................................................................................................................7-17
7.2.9 Tracing IOS Messages.........................................................................................................................7-19
7.2.10 Location Report Control.....................................................................................................................7-23
7.3 Basic Tracing Operations..............................................................................................................................7-26
7.3.1 Browsing Traced Messages Online......................................................................................................7-26
7.3.2 Viewing the Interpretation of the Trace Message................................................................................7-27
7.3.3 Saving Traced Messages......................................................................................................................7-27
7.3.4 Browsing Traced Messages Offline.....................................................................................................7-28
7.3.5 Managing Tracing Tasks......................................................................................................................7-29
7.3.6 Managing the Trace File......................................................................................................................7-30
7.3.7 Reference for Tracing Parameters........................................................................................................7-30
8 Performance Monitoring...........................................................................................................8-1
Issue 08 (2011-03-28) Huawei Proprietary and Confidential ix

BSC6900 UMTS
Contents LMT User Guide
8.1 Concepts Related to Performance Monitoring................................................................................................8-2

8.1.1 Monitoring Principles.............................................................................................................................8-2
8.1.2 Management of Monitoring Operation Rights.......................................................................................8-3
8.2 Common Monitoring.......................................................................................................................................8-4
8.2.1 Monitoring CPU/DSP Usage.................................................................................................................8-4
8.2.2 Monitoring Transmission Resources......................................................................................................8-5
8.2.3 Monitoring BER Seconds.......................................................................................................................8-5
8.2.4 Monitoring Link Performance................................................................................................................8-6
8.3 UMTS Monitoring.........................................................................................................................................8-16
8.3.1 Monitoring Connection Performance...................................................................................................8-16
8.3.2 Monitoring Cell Performance...............................................................................................................8-27
8.3.3 Monitoring Board Resources...............................................................................................................8-37
8.4 General Operations of Performance Monitoring...........................................................................................8-38
8.4.1 Browsing the Monitoring Results Online.............................................................................................8-38
8.4.2 Setting the Display Mode of the Chart.................................................................................................8-39
8.4.3 Saving Monitoring Results...................................................................................................................8-40
8.4.4 Browsing Monitoring Results Offline..................................................................................................8-40
8.5 Reference for Performance Monitoring........................................................................................................8-40
9 Device Panel................................................................................................................................9-1
9.1 Device Panel Operations.................................................................................................................................9-2
9.1.1 Introduction to the Device Panel............................................................................................................9-2
9.1.2 Starting the Device Panel.......................................................................................................................9-3
9.1.3 Querying the Status of an E1/T1 Port....................................................................................................9-3
9.1.4 Querying the CPU Usage.......................................................................................................................9-3
9.1.5 Querying the BSC Board Information...................................................................................................9-4
9.1.6 Resetting the BSC Board........................................................................................................................9-4
9.1.7 Switching Over the BSC Boards............................................................................................................9-5
9.2 Emulation Panel Operations............................................................................................................................9-6
9.2.1 Introduction to the Emulation Panel.......................................................................................................9-7
9.2.2 Starting the Emulation Panel..................................................................................................................9-8
9.2.3 Querying the Status of an E1/T1 Port....................................................................................................9-9
9.2.4 Querying the CPU Usage.......................................................................................................................9-9
9.2.5 Querying the BSC Board Information.................................................................................................9-10
9.2.6 Resetting the BSC Board......................................................................................................................9-10
9.2.7 Switching Over the BSC Boards..........................................................................................................9-11
9.2.8 Querying the Status of an FE Port........................................................................................................9-12
9.2.9 Querying the Status of a GE Port.........................................................................................................9-13
9.2.10 Querying the Status of an Optical Port...............................................................................................9-13
9.2.11 Querying the DSP Status of a DPU....................................................................................................9-14
9.2.12 Querying Alarm LED Information.....................................................................................................9-14
10 FAQ...........................................................................................................................................10-1
10.1 Browser Cache expires................................................................................................................................10-3
x Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
10.2 The LMT gives slow responses to user operations in the Firefox browser.................................................10-4
10.3 The color of the LMT is not correctly displayed.........................................................................................10-4
10.4 The verify code cannot be displayed on the LMT login page.....................................................................10-5
10.5 Installing OS Patches..................................................................................................................................10-5
10.6 Clicking the menu bar on the LMT has no response...................................................................................10-6
10.7 Changing the Computer Time During the LMT Use Prohibited................................................................10-7
10.8 Corrupt Characters Occurring When Opening the csv File in UTF-8 Coding............................................10-7
10.9 Methods for Setting the Explorer Under Citrix Farm Networking...........................................................10-10
10.10 Unable to Log In To LMT Because IE Default Security Level Is Too High..........................................10-15
10.11 Unable to Log In To LMT and Class can't Stand Automation Operation is Displayed..........................10-21
10.12 LMT Failing to Load the Progress Interface After a Successful Login..................................................10-22
Issue 08 (2011-03-28) Huawei Proprietary and Confidential xi

BSC6900 UMTS
LMT User Guide Figures
Figures
Figure 2-1 LMT window......................................................................................................................................2-7

Figure 2-2 FTP client interface..........................................................................................................................2-12
Figure 2-3 FTP server interface..........................................................................................................................2-13
Figure 2-4 Interface of the Convert Management System.................................................................................2-14
Figure 2-5 Interface of performance browser tool.............................................................................................2-15
Figure 2-6 Interface of the Traffic Recording Review Tool .............................................................................2-17
Figure 2-7 File manager interface......................................................................................................................2-18
Figure 4-1 MML command window....................................................................................................................4-5
Figure 4-2 Setting MML Parameters....................................................................................................................4-9
Figure 4-3 Subrack data configuration mode.....................................................................................................4-10
Figure 4-4 All users enabled with the data configuration rights........................................................................4-11
Figure 4-5 Data configuration rights granted to the admin user........................................................................4-12
Figure 5-1 Alarm box...........................................................................................................................................5-4
Figure 7-1 Principles of the message tracing.......................................................................................................7-2
Figure 7-2 Message tracing on the Iu interface....................................................................................................7-6
Figure 7-3 Results of tracing messages on the Iu interface..................................................................................7-7
Figure 7-4 Message tracing on the Iur interface...................................................................................................7-8
Figure 7-5 Message tracing on the Iub interface................................................................................................7-10
Figure 7-6 Results of Tracing Messages on the Iub Interface............................................................................7-11
Figure 7-7 Message tracing on the Uu interface................................................................................................7-12
Figure 7-8 Results of message tracing on the Uu interface................................................................................7-13
Figure 7-9 UE message tracing..........................................................................................................................7-15
Figure 7-10 Results of UE message tracing.......................................................................................................7-16
Figure 7-11 Cell message tracing.......................................................................................................................7-18
Figure 7-12 Results of cell message tracing.......................................................................................................7-19
Figure 7-13 IOS message tracing.......................................................................................................................7-21
Figure 7-14 Results of IOS message tracing......................................................................................................7-23
Figure 7-15 Location Report Control..............................................................................................................7-24
Figure 7-16 Results of Location Report Control................................................................................................7-25
Figure 8-1 CPU usage monitoring........................................................................................................................8-2
Figure 8-2 Real-time performance monitoring.....................................................................................................8-3
Figure 9-1 Device Panel.......................................................................................................................................9-2
Figure 9-2 Emulation panel..................................................................................................................................9-8
Issue 08 (2011-03-28) Huawei Proprietary and Confidential xiii

BSC6900 UMTS
Figures LMT User Guide
Figure 9-3 Subrack peripheral..............................................................................................................................9-9

Figure 10-1 Operation interface for importing data in Excel.............................................................................10-8
Figure 10-2 Text import wizard—step 1............................................................................................................10-8
Figure 10-3 Text import wizard—step 2............................................................................................................10-9
Figure 10-4 Interface after data importation is finished.....................................................................................10-9
Figure 10-5 Active Directory Users and Computers........................................................................................10-11
Figure 10-6 hong01 Properties 1......................................................................................................................10-12
Figure 10-7 hong01 Properties 2......................................................................................................................10-13
Figure 10-8 HTTP 1.1 settings.........................................................................................................................10-14
Figure 10-9 Script.............................................................................................................................................10-16
Figure 10-10 Logon..........................................................................................................................................10-17
Figure 10-11 Adding a script............................................................................................................................10-17
Figure 10-12 Script...........................................................................................................................................10-18
Figure 10-13 Logon..........................................................................................................................................10-19
Figure 10-14 Adding a script............................................................................................................................10-19
Figure 10-15 Windows components wizard.....................................................................................................10-20
Figure 10-16 Internet Explorer Enhanced Security Configuration..................................................................10-21
xiv Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
LMT User Guide Tables
Tables
Table 2-1 Hardware requirements of the LMT PC...............................................................................................2-2

Table 2-2 Software requirements of the LMT PC................................................................................................2-2
Table 2-3 Effective bandwidth requirements of the LMT PC..............................................................................2-3
Table 2-4 Components of the LMT window........................................................................................................2-7
Table 2-5 Description of LMT online help..........................................................................................................2-9
Table 2-6 Components of FTP client interface..................................................................................................2-12
Table 2-7 Components of FTP server interface..................................................................................................2-13
Table 2-8 Components of the Convert Management System interface..............................................................2-15
Table 2-9 Components of the performance browser tool interface....................................................................2-16
Table 2-10 Components of the Traffic Recording Review Tool interface.........................................................2-17
Table 2-11 Components on the file manager interface.......................................................................................2-18
Table 3-1 Command groups.................................................................................................................................3-3
Table 3-2 External user accounts..........................................................................................................................3-4
Table 3-3 Examples of operation time limit settings............................................................................................3-6
Table 4-1 Actions of the MML commands..........................................................................................................4-3
Table 4-2 MML command window......................................................................................................................4-5
Table 5-1 Fault alarms and event alarms..............................................................................................................5-2
Table 5-2 Alarm severity levels............................................................................................................................5-3
Table 5-3 Functions of the buttons.....................................................................................................................5-13
Table 6-1 Description of Logs..............................................................................................................................6-8
Table 7-1 Operations available when browsing traced messages online...........................................................7-27
Issue 08 (2011-03-28) Huawei Proprietary and Confidential xv

BSC6900 UMTS
LMT User Guide 1 Changes in the BSC6900 UMTS LMT User Guide
1 Changes in the BSC6900 UMTS LMT User

Guide
This chapter describes the changes made in theBSC6900 UMTS LMT User Guide.
08 (2011-03-28)
This is the eighth commercial release.
Compared with issue 07 (2011-01-30) of V900R011C00, this issue dose not add any new topics.
Compared with issue 07 (2011-01-30) of V900R011C00, this issue incorporates the following
changes:
Topic Change Description
6.9 Collecting Log Statistics The description about log is added.
Compared with issue 07 (2011-01-30) of V900R011C00, this issue does not exclude any topics.
07 (2011-01-30)
This is the seventh commercial release.
Compared with issue 06 (2010-09-15) of V900R011C00, this issue includes the following new
topics:
l LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification
of JRE
changes:
2.3 Components of the LMT Window Modify the figure according to the GUI.
Issue 08 (2011-03-28) Huawei Proprietary and Confidential 1-1

BSC6900 UMTS
1 Changes in the BSC6900 UMTS LMT User Guide LMT User Guide
06 (2010-09-15)
This is the sixth commercial release.
topics:
l 10.10 Unable to Log In To LMT Because IE Default Security Level Is Too High
l 10.11 Unable to Log In To LMT and Class can't Stand Automation Operation is
Displayed
l 10.12 LMT Failing to Load the Progress Interface After a Successful Login
changes:
2.1 Configuration Requirements of the The description about requirements of Web

LMT PC browser for the LMT PC is modified.
4.3 Batch Processing MML Commands The description about scheduled batch
running is added.
05 (2010-05-31)
This is the fifth commercial release.
topics:
l 10.9 Methods for Setting the Explorer Under Citrix Farm Networking
changes:
2.1 Configuration Requirements of the The description about requirements of

LMT PC connection ports for the LMT PC is added.
04 (2010-03-25)
This is the fourth commercial release.
topics:
l 10.7 Changing the Computer Time During the LMT Use Prohibited
l 10.8 Corrupt Characters Occurring When Opening the csv File in UTF-8 Coding
1-2 Huawei Proprietary and Confidential Issue 08 (2011-03-28)

BSC6900 UMTS
LMT User Guide 1 Changes in the BSC6900 UMTS LMT User Guide
changes:
2.3 Components of the LMT Window The description about the Language Setting
is added.
03 (2009-12-05)
This is the third commercial release.
topics:
l 2.5 File Manager
Compared with issue 02 (2009-10-30) of V900R011C00, this issue does not incorporate any
changes.
02 (2009-10-30)
This is the second commercial release.
topics:
l 10 FAQ
Compared with issue 01 (2009-07-30) of V900R011C00, this issue does not incorporate any
changes.
Compared with issue 01 (2009-07-30) of V900R011C00, this issue excludes the following
topics:
l Device Commissioning
l Debugging Test
01 (2009-07-30)
This is the first commercial release.

BSC6900 UMTS
LMT User Guide 2 Introduction to LMT
2 Introduction to LMT
About This Chapter
The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) for users for easy operation and maintenance of the BSC6900. Users can
perform operations such as alarm management, trace management, performance monitoring,
and device maintenance. Users can also run MML commands and read the corresponding
execution results on the LMT.
2.1 Configuration Requirements of the LMT PC

The computer on which the LMT is running is called the LMT PC. The LMT PC must meet the
requirements related to hardware, software, connection ports, and communication capability.
2.2 LMT Login and Exit
This describes how to log in to the LMT for NE operations and how to exit it after performing
the operations.
2.3 Components of the LMT Window
You can log in to the LMT through the web browser to operate and maintain the BSC6900.
2.4 LMT Software
The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser, and Traffic Recording
Review Tool.
2.5 File Manager
The file manager is a component of the LMT software suite. It enables file uploading and
downloading between the LMT and the OMU. The functions of the file manager are similar to
those of the FTP client. For example, you can obtain logs and upload data configuration files.

BSC6900 UMTS
2 Introduction to LMT LMT User Guide
2.1 Configuration Requirements of the LMT PC

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

Item Quantit Recommended Minimum
y Configuration Configuration
CPU 1 2.8 GHz or above 866 MHz
RAM 1 1 GB 512 MB
Hard disk 1 80 GB 10 GB
Display resolution - 1024 x 768 or above 1024 x 768
CD drive 1 - -
Ethernet adapter 1 10/100 Mbit/s 10/100 Mbit/s
Other devices 5×1 Keyboard, mouse, Keyboard and mouse

modem, audio card,
and speaker
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 XP Professional SP2, Windows Server 2003,

Windows Server 2008, Windows Vista, or Windows 7.
Default language of the Simplified Chinese or English

operating system

BSC6900 UMTS
Item Recommended Configuration
Web browser Internet Explorer 6.0.2900.2180.xpsp_sp2_gdr or later

releases, Internet Explorer 7.0.5730.13 or later releases,
Internet Explorer 8.0.6001.18702 or later releases, or
FireFox 3.0 or later releases.
NOTE
l You need to set the security level of the Web browser to medium
or low. Otherwise, the LMT menus cannot be viewed.
l when you use the FireFox 3.6 or later releases, you need to install
a JRE plug-in of a version that later than 1.6.0_18 .
Java plug-in called Java jre-6u11-windows-i586-p-s.exe or later official versions

Platform Standard Edition NOTE
Runtime Environment (JRE) The plug-in can be obtained on the official Java website http://
java.com or on Huawei support website http://
support.huawei.com.
CAUTION
l You are advised to run the LMT on a PC with the recommended configurations to ensure
stable operation.
l The LMT in the current version can be used only in the 32-bit operating system and with the
32-bit Web explorer.
Requirements of Connection Ports

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

The LMT PC must support TCP/IP protocols and meet the requirements of effective bandwidth
in Table 2-3.
Table 2-3 Effective bandwidth requirements of the LMT PC
Item Protocol Recommended Minimum

Configuration Configuration
Requirements of HyperText Transfer Not lower than 2 512 Kbit/s

effective bandwidth Protocol (HTTP) Mbit/s

BSC6900 UMTS
NOTE
l Bandwidth affects the speed of webpage visits. You can rapidly visit the LMT on an LMT PC with a
recommended configuration. Your visit to the LMT is, however, significantly delayed on an LMT PC
with the minimum configuration although all LMT functions can be used.
l Effective bandwidth in most cases indicates the bandwidth available for the LMT. If many programs
compete with the LMT for bandwidth resources, a serious delay occurs despite a link bandwidth of 2
Mbit/s under HTTP.
2.2 LMT Login and Exit

This describes how to log in to the LMT for NE operations and how to exit it after performing
the operations.
Context
You must install the JAVA Platform Standard Edition Runtime Environment (JRE) program
before launching the LMT. If no JRE program is installed, a message is displayed when you log
in to the LMT, prompting you to install the program. Follow the instructions to install the
program. If the JRE program on the LMT PC is not the latest version, a message is displayed,
prompting you to upgrade the program version. In this case, you are advised to uninstall the
existing JRE program and then install the new version. If you cannot log in to the LMT after
you upgrade the JRE program, restart the web browser and retry.
WARNING
When the LMT is running, do not modify the system time or time zone as errors may occur on
the system. Close the LMT window before modifying these values.

BSC6900 UMTS
CAUTION
l The LMT does not support the refreshing function of the browser. If you refresh the window,
you are logged out of the LMT. If you refresh the trace and monitor page, a message indicating
the script error is displayed.
l When the LMT window is open, do not modify any file folder properties. Otherwise, the IE
browser is automatically refreshed, and error occurs on the LMT.
l If users open the LMT window through the IE browser, the IE browser must support the
HTTP 1.1 protocol. You can refer to the following setting: choose Tools > Internet
Options > Advanced > HTTP 1.1 Settings, select Use HTTP 1.1. If users need to connect
LMT through the proxy server, Use HTTP 1.1 through proxy connection must be selected.
l If the LMT is active in the IE browser and you choose Start > Run to start the FTP server,
the IE browser closes the LMT window and goes to the login window of the FTP server
directly. To avoid this problem, set the IE browser as follows: choose Tools > Internet
Options. In the Advanced tab page, deselect Reuse windows for launching shortcuts in
the Browsing options.
l If the colors on the LMT window cannot be displayed, set the IE browser as follows: choose
Tools > Internet Options. In the General tab, click Accessibility. Then, in the
Formatting area, deselect Ignore colors specified on Web pages.
l You need to clear the cache and cookies in the browser (see 10.1 Browser Cache expires.)
before you roll back or upgrade the LMT version.
l If AVG Internet Security is installed on the LMT PC, the web shield function must be
disabled. If this function is enabled, a dialog box will be displayed, prompting "Disconnected.
Please log in again."
Procedure
Step 1 Type the external virtual IP address of the OMU in the address bar of the IE. Press Enter on the
keyboard, or click Go next to the address bar to enter the login window of the BSC6900.

BSC6900 UMTS
NOTE
l 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. In the Connection tab page, click LAN Settings. In the
displayed window, click Advanced. In the displayed Proxy Settings window, specify an IP address that
does not use the proxy server under Exceptions. For example, OMU_IP or M2000_IP.
l If users need to connect the LMT to the OMU through the M2000 proxy server and then enter the
BSC6900 login window, they can adopt the following two methods:
l Type "M2000_IP/OMU_IP/" or "http://M2000_IP/OMU_IP/login.html" in the address bar of the IE.
Then press Enter on the keyboard, or click Go next to the address bar to enter the login window of the
BSC6900. Note that "/" must be included in "M2000_IP/OMU_IP/" behind OMU_IP. If another proxy
server is already set, you need to add M2000_IP to the IP addresses that do not use the proxy server
under Exceptions.
l Set the M2000 proxy server in the IE and type the external virtual IP address of the OMU in the address
bar of the IE. Press Enter on the keyboard, or click Go next to the address bar to enter the login window
of the BSC6900. You can set the M2000 proxy server in the IE by using the following method: Choose
Tool > Internet Options on the tool bar of the IE. In the Connection tab page, click LAN Settings.
Then specify the IP address and port number of the M2000 server in the Proxy server area. The default
port number is 80.
l OMU_IP indicates the external virtual IP address of the OMU and M2000_IP indicates the IP address of
the M2000 server.
Step 2 Specify User Name, Password, and Verify Code.

l Set User Type to Local or EMS.
l If the verify code is illegible, click Change the verify code for a new code.
Step 3 Click Login.
NOTE
l Before logging in to the BSC6900 as an EMS user, you need to set up a connection between the
BSC6900 and the M2000 server.
l If the login fails, click Reset. Specify User Name, Password, and Verify Code again to log in. If the
login fails again, verify there is a normal connection between the LMT and the OMU.
Step 4 Optional: To lock the LMT window, click Lock on the top bar.
Step 5 To exit the LMT, click Logout in the top right corner of the LMT main page.
----End
2.3 Components of the LMT Window

You can log in to the LMT through the web browser to operate and maintain the BSC6900.
Interface
Figure 2-1 shows the LMT window.

BSC6900 UMTS
Figure 2-1 LMT window
Table 2-4 describes components of the LMT window.
Table 2-4 Components of the LMT window

Component Description
Alarm tab You can query active alarms, alarm logs, and alarm configuration
on this tab page. For details, see 5 Alarm Management.
Batch tab You can run MML commands in batches on this tab page.
Trace tab You can manage message tracing tasks on this tab page. For details,
see 7 Trace Management.
Monitor tab You can monitor performance data on this tab page. For details, see
8 Performance Monitoring.
Device Maintenance You can maintain the device panel. For details, see 9 Device
tab Panel.
MML tab For details, see 4.1.2 Components of the MML Command
Window.
Progress tab This tab displays the progress of tasks.

NOTE
If this tab is hidden, click Progress on the toolbar to show the Progress tab
page. Then, double-click an entry to view the detailed information. The
Progress Management dialog box is displayed, listing the detailed progress
report.

BSC6900 UMTS
FTP Tool Click FTP Tool on the tool bar of the LMT window to download
the executable application file SFTPServer.exe. Then double-click
the executable file to start the FTP server. For details, see 2.4.2 FTP
Client and 2.4.3 FTP Server.
Password You can select this tab to change the password of the current user
account. After changing the password, you need to use the new
password when logging in again.
File Manager You can select this tab to upload and download files between the
LMT and the OMU. For details, see 2.5 File Manager.
Language Setting After you choose a language, input and display in the language are
supported.
NOTE
Setting the language does not change the display language of the LMT.
About Displays the version of the current LMT.
Lock You can click it to lock the current operation interface for security.
NOTE
l After you click Lock on the toolbar, the LMT is locked.
l You can click the web page or press the enter key; then enter the
password, or type the password and press OK to enter the LMT
workspace.
Logout You can click it to log out the current user without exiting the
system. Logout of one account user facilitates login of another
account user.
Online Help
The LMT provides the following two types of online help:
l Online help system
l MML help
Table 2-5 lists the specific help and startup method of online help.

BSC6900 UMTS
Table 2-5 Description of LMT online help

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

help following l Press F1 or click Help on the LMT main page to display
system information: LMT help information.
l LMT online l Press F1 in a displayed dialog box to display help
help information about the specific dialog box.
l Alarm If the FireFox Explorer is used, press Help on the LMT main
reference page to display LMT help information.
l Event
reference
MML Provides the Type an MML command in the Command Input box. Press
help following Enter or click Assist, and then click the Help Information
information tab. Accordingly, help information about the command is
about an MML displayed on the tab page.
command:
l Command
function
l Note
l Parameter
l Example
l Output
description
(only for
query
commands)
2.4 LMT Software

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

This describes how to install the LMT offline tools on the LMT PC.
2.4.2 FTP Client
The FTP client is a component of the LMT offline tool and enables the communication between
the LMT and the FTP server according to the FTP protocol. You can obtain logs and upload
data configuration files through the FTP client.
2.4.3 FTP Server
The FTP server is a component of the LMT offline tool and provides upload and download
services according to the FTP protocol. It is used when uploading and downloading BTS software
and license file.
2.4.4 Convert Management System

BSC6900 UMTS
The Convert Management System is a component of the LMT offline tool. It enables
communication between the OMU and the alarm box and is used to transfer the alarm
information, alarm box control information, and alarm box status information. The Convert
Management System must be started to connect the LMT to the alarm box. The Convert
Management System communicates with the OMU through the Ethernet port and to the alarm
box through the serial port.
2.4.5 Performance Browser Tool
The performance browser tool is a component of the LMT offline tool. It is used to parse the
performance descriptive files in the OMU.
2.4.6 Traffic Recording Review Tool
The Traffic Recording Review Tool is a component of the LMT offline tool and is used to review
the trace and monitor data.
2.4.1 Installing LMT Offline Tools

This describes how to install the LMT offline tools on the LMT PC.
Prerequisite
l A legal serial number for the LMT software is obtained.
l The PC for installing the LMT offline tools complies with the specifications in 2.1
Configuration Requirements of the LMT PC.
Context
CAUTION
If the setup languages of the LMT and OMU software are different, some functions such as the
management of user accounts will not be available. Therefore, you are advised to install them
in the same language.
Procedure
Step 1 Use the administrator account to log in to the LMT PC.
Step 2 Insert the setup disk into the CD-ROM drive.
l The setup program runs automatically.
l If the setup program fails to run automatically, double-click setup.bat or setup.vbs in the
directory of the setup disk.
NOTE
You can also download the installation package of the LMT offline tool from http://
support.huawei.com. Log in to the website, and then choose Support > Software Center > Version
Software > Wireless Product Line > Single RAN > MBSC > BSC6900. Then, select the required software
version to download.
Step 3 Choose the installation language, and click OK. The installation wizard prompts you that you
are installing HUAWEI Local Maintenance Terminal.
Step 4 Click Next. A dialog box is displayed, asking you to read the copyright notice.

BSC6900 UMTS
Step 5 Read the software certificate declarations. If you accept the agreement terms, select I accept
these terms, and then click Next. A dialog box is displayed, asking you to specify the installation
path. If you do not accept the agreement terms, click Cancel to quit the installation.
Step 6 Use the default installation path or browse to a new path, and then click Next.
NOTE
The default installation path is D:\HW LMT.

l If the LMT of another version or NE has been installed, the installation path is that of the original LMT
software and cannot be altered.
l To alter the installation path, you must uninstall the existing LMT software.
If an LMT software is running, the Warning dialog box is displayed. Click Yes to automatically exit the
LMT application. Click No to manually exit the LMT application.
Step 7 Select the software components and then click Next. It is recommended that you select all
components. A dialog box is displayed for entering the CD-KEY.
Step 8 Enter the CD-KEY correctly, and then click Next. A dialog box is displayed, asking you to
confirm the installation.
Step 9 Confirm the installation parameters and click Next. A dialog box is displayed, indicating the
progress of copying the files.
When the task of copying files is complete, a dialog box is displayed for initializing components.
When all programs are installed, a dialog box is displayed, indicating the completion of the
installation.
Step 10 Click Finish.
NOTE
The installation is complete. When the installation is complete, the LMT Service Manager automatically
starts.
----End
2.4.2 FTP Client

The FTP client is a component of the LMT offline tool and enables the communication between
the LMT and the FTP server according to the FTP protocol. You can obtain logs and upload
data configuration files through the FTP client.
Startup
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > FTP Client on
the LMT PC.
Interface
Figure 2-2 shows the FTP client interface.

BSC6900 UMTS
Figure 2-2 FTP client interface
Table 2-6 describes the components of the FTP client interface.
Table 2-6 Components of FTP client interface

Number Component Description
1 Menu bar Provides the menus for the operation of the system.
2 Tool bar Provides the shortcut icons for the operation of the
system.
3 Server input area You can specify the server name, user name, user
password, port number, and mode in this area.
4 Local directory list Displays the directory structure of the current

window computer.
5 Server file list window Lists the files and file folders stored in the connected
FTP server.
6 Local file list window Lists the files and file folders stored in the current
computer.
7 Prompt information Displays the information such as the connection

window status of the FTP server and the operation
descriptions.

BSC6900 UMTS
2.4.3 FTP Server

The FTP server is a component of the LMT offline tool and provides upload and download
services according to the FTP protocol. It is used when uploading and downloading BTS software
and license file.
Startup
There are two ways to start up the FTP server:
l Choose Start > All Programs > HUAWEI Local Maintenance Terminal > FTP
Server on the LMT PC.
l Click FTP Tool on the tool bar of the LMT window to download the executable application
file SFTPServer.exe.
Interface
Figure 2-3 shows the FTP server interface.
Figure 2-3 FTP server interface
Table 2-7 describes the components of the FTP server interface.
Table 2-7 Components of FTP server interface
Port number Indicates the number of the port used by the FTP server to
intercept the information on the network. According to the FTP
protocol, the port 21 is used as the default port.

BSC6900 UMTS
Thread number Indicates the number of clients that can be connected to the FTP
server simultaneously.
2.4.4 Convert Management System

The Convert Management System is a component of the LMT offline tool. It enables
communication between the OMU and the alarm box and is used to transfer the alarm
information, alarm box control information, and alarm box status information. The Convert
Management System must be started to connect the LMT to the alarm box. The Convert
Management System communicates with the OMU through the Ethernet port and to the alarm
box through the serial port.
Function
The Convert Management System performs the following functions:
l Forwards the alarm operation instructions from the LMT.
l Forwards the alarm information to the alarm box.
l Detects the real-time status of the connection between the LMT and the OMU and that
between the LMT and the serial ports of the alarm box, and reports the alarms if any.
Startup
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Convert
Management System on the LMT PC.
Interface
Figure 2-4 shows the interface of the Convert Management System.
Figure 2-4 Interface of the Convert Management System

BSC6900 UMTS
Table 2-8 describes the components of the Convert Management System interface.
Table 2-8 Components of the Convert Management System interface

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

window Convert Management System.
2.4.5 Performance Browser Tool

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

BSC6900 UMTS
Table 2-9 describes the components of the performance browser tool interface.
Table 2-9 Components of the performance browser tool interface

system.
3 Measurement Provides the measurement statistic files in the tree

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

window performance file.
2.4.6 Traffic Recording Review Tool

The Traffic Recording Review Tool is a component of the LMT offline tool and is used to review
the trace and monitor data.
Startup
Choose Start > All Programs > Huawei Local Maintenance Terminal > Traffic Recording
Review Tool on the LMT PC.
Interface
Figure 2-6 displays the interface of the Traffic Recording Review Tool.

BSC6900 UMTS
Figure 2-6 Interface of the Traffic Recording Review Tool
Table 2-10 describes the components of the Traffic Recording Review Tool interface.
Table 2-10 Components of the Traffic Recording Review Tool interface

system.
3 Service data retrieval Provides the data related to the trace and monitor
window tasks.
2.5 File Manager

The file manager is a component of the LMT software suite. It enables file uploading and
downloading between the LMT and the OMU. The functions of the file manager are similar to
those of the FTP client. For example, you can obtain logs and upload data configuration files.
Startup
Click File Manager in the tool bar on the LMT main interface.

BSC6900 UMTS
Interface
Figure 2-7 shows the interface of the file manager.
Figure 2-7 File manager interface
Table 2-11 describes the components on the file manager interface.
Table 2-11 Components on the file manager interface
1 Navigation tree Displays the files on the OMU.
2 File manager panel Displays details about the files on the OMU.
3 Processing status area Displays the progress of a task.
NOTE
l To upload files from the LMT PC to the OMU, you can click Upload on the file manger panel.
Alternatively, you can right-click files in the file manager panel, and then choose Upload from the
shortcut menu.
l To download files from the OMU to the LMT PC, you can click Download on the file manger panel.
Alternatively, you can right-click files in the file manager panel, and then choose Download from the
shortcut menu.
l To store a file on the LMT PC, you can click Directory to specify a save path.

BSC6900 UMTS
LMT User Guide 3 Management of Operation Rights
3 Management of Operation Rights
About This Chapter
This chapter describes the management of operation rights, and provides instruction to manage
user accounts and command groups.
3.1 Concepts Related to Operation Rights Management

This section describes the principles of managing the operation rights of the BSC6900 LMT in
terms of user identity, user rights, and operation time limit.
3.2 Management of User Accounts
This section describes how to manage user accounts of the BSC6900 LMT. Instructions are
provided for creating, modifying, and deleting the external user accounts.
3.3 Management of User Passwords
This section describes how to manage the user password of a BSC6900 LMT user account.
Instructions are provided for defining the login password policies, querying the login password
policies, changing the password of the current user, and changing the password of an external
user account by an authorized user.
3.4 Management of Command Groups
This section describes how to manage command groups. Instructions are provided for querying
the command groups, setting the command group name, and modifying the command group
contents.

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

3.1.1 Principles of Operation Rights Management

3.1.2 User Password
This section describes the BSC6900 LMT user password in terms of password definition, initial
password setting, and password change.
3.1.3 Command Group
The BSC6900 provides 15 command groups (G_0 to G_14) with different functions.
3.1.4 User Type
You can log in to the BSC6900 LMT as the Local user and the EMS user.
3.1.5 Operation Rights
This section describes the operation rights of the built-in administrator account and other external
user accounts of the BSC6900 LMT.
3.1.6 Operation Time Limit
This section describes the definition, principle, and setting of the time limits for a user to operate
the BSC6900 LMT.
3.1.1 Principles of Operation Rights Management

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

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

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

BSC6900 UMTS
Initial Password Setting

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

All users can change their own password. The admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can change the passwords of all external user accounts. Only the admin
user can change the password of the admin account.
For details, see 3.3.3 Changing the Password of the Active User Account and 3.3.4 Changing
the Password of an External User Account.
3.1.3 Command Group

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

command groups, logs, NTP, EMS, and time zone.
G_1 Used to manage system information such as user groups, time

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

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

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

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

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

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

unblock, or switch over the boards.
G_10 Used to trace or monitor the signaling flows on the control plane
or the user plane, for example, to query the trace tasks or to create/
delete/start a trace task.

BSC6900 UMTS
Command Group Function
G_11 Used to modify the settings of the integrated equipment panels.
G_12 Used to manage the software, for example, patch management.
G_13 Used to query the base station information, for example, to query
the BTS attribute or to query the BTS boards.
G_14 Used to manage the base stations, for example, BTS software
management or BTS resetting.
For the operations related to command groups, see 3.4 Management of Command Groups.
3.1.4 User Type

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

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

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

There are five levels of external user accounts. Each level has distinctive operation rights, as
described in Table 3-2.
Table 3-2 External user accounts
Level Assigned Operation Right Description

Command
Group
GUEST G_0, G_2, G_4, Data query The operation

G_6, G_8, and rights are
G_13 predefined by the

BSC6900 UMTS
Level Assigned Operation Right Description

Command
Group
USER G_0, G_2, G_4, l Operation rights of GUEST- system and cannot
G_6, G_7, G_8, level be changed.
G_9, G_10, l System OM
G_11, G_12,
G_13, and G_14
OPERATOR G_0, G_2, G_3, l Operation rights of USER-

G_4, G_5, G_6, level
G_7, G_8, G_9, l Data configuration
G_10, G_11,
G_12, G_13,
and G_14
ADMINISTRA G_0, G_1, G_2, All the operation rights

TOR 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
CUSTOM Command Specified when the account is The operation

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

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

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

BSC6900 UMTS
Principle of Operation Time Limit

The operation time limit is specified by a combination of date, day, and time.
Table 3-3 provides some examples of operation time limit settings.
Table 3-3 Examples of operation time limit settings
SN Date Day Time Permitted Operation Time
1 2008-08-01 Monday to 8:00:00 to 8:00:00 to 18:00:00 on Monday

to Friday 18:00:00 through Friday from 2008-08-01
2009-08-01 to 2009-08-01
2 - Saturday and - Any time on Saturdays and

Sunday Sundays
3 - - - No operation time limit. The

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

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

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

This section describes how to create an external user account. You are required to set the
password, user level, command group (for CUSTOM-level user account only), and operation
time limit for the new user account. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can perform this operation.
3.2.2 Modifying an External User Account
This section describes how to modify the attributes of an external user account, including the
user name, user password, user level, operation rights, and operation time limit. The new
password takes effect upon the next login. Modifications of other attributes take effect
immediately. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users
can perform this operation.
3.2.3 Deleting an External User Account
This section describes how to delete an external user account. Only the admin,
ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.
3.2.1 Creating an External User Account

This section describes how to create an external user account. You are required to set the
password, user level, command group (for CUSTOM-level user account only), and operation

BSC6900 UMTS
time limit for the new user account. Only the admin, ADMINISTRATOR-level, and authorized
Prerequisite
You have logged in to the LMT with an account authorized for this operation.
Procedure
Step 1 Run the ADD OP command to create an external user account.
CAUTION
The new user account cannot be the same as any of the existing ones.
----End
3.2.2 Modifying an External User Account

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

This section describes how to delete an external user account. Only the admin,
Prerequisite
Context
CAUTION
The admin account is the permanent built-in user account and cannot be deleted.

BSC6900 UMTS
Procedure
Step 1 Run the RMV OP command to delete an external user account.
----End
3.3 Management of User Passwords

This section describes how to manage the user password of a BSC6900 LMT user account.
Instructions are provided for defining the login password policies, querying the login password
policies, changing the password of the current user, and changing the password of an external
user account by an authorized user.
3.3.1 Defining Login Password Policies

This section describes how to define policies for setting the login passwords. The login password
policies set restrictions on the minimum length and complexity of the password. Only the
ADMINISTRATOR-level users can define the policies for setting the login passwords.
3.3.2 Querying Login Password Policies
This section describes how to query the policies for setting the login passwords.
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 upon the next login.
3.3.4 Changing the Password of an External User Account
This section describes how to change the password of an external user account. Only the admin,
3.3.1 Defining Login Password Policies

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

This section describes how to query the policies for setting the login passwords.
Prerequisite
You have logged in to the LMT.

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

This section describes how to change the password of the active user account. The new password
takes effect upon the next login.
Prerequisite
Context
CAUTION
Exercise caution when changing the password of the admin account. If you forget the password,
you cannot log in to the system with the admin account. Contact Huawei for technical support
if needed.
Procedure
Step 1 Click Password on the tool bar of the LMT main page. The Password dialog box is displayed.
Step 2 In the displayed Change Password window, enter the current password in the Old Password
field. Enter the new password in the New Password and Confirm Password fields. Then click
OK.
----End
3.3.4 Changing the Password of an External User Account

This section describes how to change the password of an external user account. Only the admin,
Prerequisite
Procedure
Step 1 Run the MOD OP to change the password of an external user account.
----End

BSC6900 UMTS
3.4 Management of Command Groups

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

There are 15 command groups G_0 to G_14. Only the admin, ADMINISTRATOR-level, and
authorized CUSTOM-level users can query the information about the command groups.
3.4.2 Setting the Command Group Name
Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can rename
the command groups.
3.4.3 Changing the Commands in a Command Group
Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can change
the contents of command groups.
3.4.1 Querying a Command Group

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

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can rename
the command groups.
Prerequisite
Procedure
Step 1 Run the LST CCGN command to query the name of a command group.
Step 2 Run the SET CCGN command to rename a command group.
----End
3.4.3 Changing the Commands in a Command Group

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can change
the contents of command groups.

BSC6900 UMTS
Prerequisite
Procedure
l Run the ADD CCG command to add commands to a command group.
l Run the RMV CCG command to remove commands from a command group.
----End

BSC6900 UMTS
LMT User Guide 4 Running MML Commands
4 Running MML Commands
About This Chapter
This chapter describes how to run MML commands on the LMT to operate and maintain the
BSC6900.
4.1 Concepts Related to MML Commands

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

BSC6900 UMTS
4 Running MML Commands LMT User Guide
This section describes how to undo and redo multiple data configuration actions.

BSC6900 UMTS
4.1 Concepts Related to MML Commands

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

This describes the MML commands that can be used to operate and maintain the BSC6900.
4.1.2 Components of the MML Command Window
This section describes the components of the MML command window.
4.1.3 Data Configuration Rights
The management of the data configuration rights enables only one user to perform BSC6900
data configuration through the LMT or the M2000 at a time.
4.1.4 Data Configuration Rollback
Data configuration rollback is performed to restore the system to a previous configuration status.
If a data configuration action fails to achieve the expected result or even causes equipment or
network problems, you can perform rollback to restore the configurations so that normal
operation of the BSC6900 is restored as early as possible.
4.1.1 Introduction to MML Commands

This describes the MML commands that can be used to operate and maintain the BSC6900.
An MML command consists of two parts: action and object. For example, ADD OP, wherein
ADD is the action and OP is the object. Table 4-1 describes the actions that can be performed
through MML commands.
Table 4-1 Actions of the MML commands
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

BSC6900 UMTS
Action Description
DEA Deactivate
DSP List
EST Establish
EXP Export
FMT Format
FOC Obtain
HO Hand over
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

BSC6900 UMTS
Action Description
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.
Figure 4-1 MML command window
Table 4-2 describes the components of the MML command window.
Table 4-2 MML command window
Field Description
Common Displays system responses such as execution results. In this area,

Maintenance tab you can save command execution results and let the system
automatically scroll the results by clicking Save Results and Auto
Scroll respectively. You can also clear all the results by clicking
Clear All.
NOTE
The time displayed at the beginning of the returned result is the OMU time.
Operation Record tab Displays commands that have been run.

NOTE
The Send Time displayed in the operation record is the time of the LMT
PC.
Help Information tab Displays the help information for a command.

BSC6900 UMTS
Field Description
Manual editing area Displays the area for manually editing the MML command script.
History Command box Displays the commands that you have run after logging in to the
system and the relevant parameters.
Command Input box Displays in the drop-down list all the MML commands available
on the system. You can select an MML command from the drop-
down list or type in an MML command for execution.
Parameter area Displays the parameters of the current command. You need to set
parameter values in the boxes before executing the command. The
parameters in red are mandatory, and those in black are optional.
NOTE
For details of the MML commands and parameters, see the MML online help.
4.1.3 Data Configuration Rights

The management of the data configuration rights enables only one user to perform BSC6900
data configuration through the LMT or the M2000 at a time.
In case of conflicts during data configuration, the OMU manages the configuration rights as
follows:
l When the control switch of the data configuration rights is ON, only one user has the data
configuration rights at a time. When the switch is OFF, no control is applied on the data
configuration rights. (You can run the SET CMCTRLSW command to set the switch to
ON or OFF.)
l When a user occupies the data configuration rights for a long time, the administrators can
check with the user. If the user is not performing data configuration, the administrators can
run the FOC CMCTRL command to obtain the data configuration rights manually.
l If the user with the data configuration rights exits the LMT, the data configuration rights
are released automatically. In this case, another user can also run the REQ CMCTRL
command to obtain the data configuration rights.
4.1.4 Data Configuration Rollback

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

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

BSC6900 UMTS
Operations of Configuration Rollback
CAUTION
Data configuration rollback cannot be performed if the data configuration control switch is
disabled (with SET CMCTRLSW), quick configuration mode is enabled (with SET
QUICKCFG), or batch configuration is performed (with RUN BATCHFILE).
Data configuration rollback consists of the following types of operations:

l Undo a single configuration action: This operation is performed to undo a previous
configuration action. It is applicable to the latest 10 effective configuration actions.
l Redo a single configuration action: This operation is performed to redo a previously undone
configuration action. It is applicable to the latest 10 undone configuration actions.
l Undo multiple configuration actions: This operation is performed to undo multiple
configuration actions that have taken effect after a specified rollback point. After the undo
operation, the system rolls back to the configuration status at the specified rollback point.
l Redo multiple configuration actions: This operation is performed to redo the multiple
configuration actions that were undone previously. After the redo operation, the system
restores either the configuration status at the specified rollback point or the final
configuration status before undoing the configurations.
4.2 Running an MML Command

This section describes how to use MML commands for routine configuration and maintenance.
Prerequisite
Context
You can run an MML command in one of the following ways:
l Entering an MML command in the Command Input box
l Selecting a previously-executed command from the History Command box
l Selecting an MML command from the MML Command navigation tree
l Copying the MML command script to the Manual Edit area
NOTE
You can set the control switch of the data configuration rights to ON by running SET CMCTRLSW. If
you do not have data configuration rights, you can only run query commands. To obtain the data
configuration rights, see 4.7 Obtaining Data Configuration Rights.
Procedure
l Entering an MML command in the Command Input box
1. Enter an MML command in the Command Input box. When you enter the command,
you can also select the required command from the drop-down list of suggested
commands.

BSC6900 UMTS
2. Press Enter or click Assist to display the parameters associated with the command.
3. Specify the parameter values to run the command.
4. Press F9 or click Exec to run the command. The result is displayed on the Common
Maintenance tab page.
l Selecting a previously-executed command from the History Command box
1. Select a previously-executed command from the drop-down list of history commands.
(Press F7 or click to select the previous command. Press F8 or click to
select the next command.)
2. (Optional) Change the parameter values in the command parameter area.
l Selecting an MML command from the MML Command navigation tree
1. Select an MML command from the MML Command navigation tree, and double-
click the command.
2. Specify the parameter values to run the command.
NOTE
l The parameters displayed in red are mandatory, and those in black are optional.
l Place the cursor on the parameter value input box to read the general information about the
parameter.
l If the execution of the command fails, the result is displayed in red on the Common
l Copying the MML command script to the Manual Edit area
1. Copy the script of a MML command with the required parameter values, and paste it
in the Manual Edit area.
----End
4.3 Batch Processing MML Commands

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

BSC6900 UMTS
l Scheduled batch processing: the batch file is automatically run at a moment of a day
specified by an operator in advance
4.4 Setting MML Parameters

You can set the MML parameters as required.
Prerequisite
Procedure
Step 1 Click Setting on the Common Maintenance tab page in the MML window. The MML
Setting dialog box is displayed, as shown in Figure 4-2.
Figure 4-2 Setting MML Parameters
Step 2 Set the parameters as required.
Step 3 Click OK to save the settings.
----End
4.5 Querying the Data Configuration Mode

This section describes how to determine if the data configuration mode of the subrack is effective
or non-effective.
Prerequisite

BSC6900 UMTS
Context
In effective mode, the data configured takes effect immediately on the subrack.
In non-effective mode, the data configured for the subrack takes effect only in the OMU and
does not takes effect on the subrack. In this case, you can run the SET
CFGDATAEFFECTIVE command to set the mode to effective mode, run the FMT DATA
command to generate the data configuration file for the subrack, and then run the RST
SUBRACK command to reset the subrack. In this way, the subrack can load the data
configuration from the OMU to put the data changes into effect on the subrack.
When a subrack is in non-effective mode, you cannot query, compare, or perform CRC check
on the data between the host and the OMU. In addition, you cannot configure the host data of
the subrack.
When all the subracks are in non-effective mode, license verification is not performed. When a
subrack is switched from the non-effective mode to the effective mode, the OMU checks whether
the data configuration exceeds the limitations of the license. If the data configuration exceeds
the limitations of the license, the mode switching is not allowed.
If the OMU is newly installed, subrack 0 is in non-effective mode by default. If a subrack is
newly added, it is in non-effective mode by default.
Context
You can query the data configuration through menu operations or through MML commands.
Procedure
l Through menu operations
1. On the main page of the LMT, check the configuration mode of a subrack from the
drop-down list on the tool bar, as shown in Figure 4-3.
Figure 4-3 Subrack data configuration mode
l Through MML commands

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

This section describes how to check the control status of the data configuration rights.
Prerequisite

BSC6900 UMTS
Context
You can query the control status of the data configuration rights through menu operations or
through MML commands.
If the result indicates that the control status of the data configuration rights is NULL, you can
infer that no one has the data configuration rights currently.
Procedure
1. In the main page of the LMT, check the configuration mode of a subrack from the
drop-down list on the toolbar.
For example, Figure 4-4 indicates that all users have the data configuration rights.
Figure 4-4 All users enabled with the data configuration rights

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

You need to obtain the data configuration rights to perform data configuration, undo/redo
operations on the BSC6900 exclusively, or perform data configuration in batch without being
affected by other users. Only the M2000 users and users of the following levels can obtain the
data configuration rights: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled to
use command group G_3 (for data configuration).
Prerequisite
l You have logged in to the LMT.
l You have set the control switch of the data configuration rights to ON by running the SET
CMCTRLSW command.
Context
l By default, the control switch of the data configuration rights is set to OFF. In this case, all
users can perform data configuration of the BSC6900 through the LMT or M2000.
l When the control switch of the data configuration rights is ON, only one user has the data
configuration rights at a time.
l After the data configuration is complete, you can release the data configuration rights by
running the REL CMCTRL command. In this way, another user can run the REQ
CMCTRL command to obtain the data configuration rights.

BSC6900 UMTS
l If the user with the data configuration rights exits the LMT, the data configuration rights
are released automatically. In this case, another user can also run the REQ CMCTRL
command to obtain the data configuration rights.
Procedure
Step 1 Check whether the data configuration rights are assigned to another user. For details, see 4.6
Querying Data Configuration Rights.
l If no user is currently assigned with the data configuration rights, go to Step 2.
l If the data configuration rights are already assigned to another user, go to Step 2 after the
user releases the data configuration rights.
Step 2 Run the REQ CMCTRL command to obtain the data configuration rights.
Step 3 Check the CM control state from the drop-down list of the CM control state on the toolbar.
Figure 4-5 shows that the data configuration rights are granted to the admin user.
Figure 4-5 Data configuration rights granted to the admin user
NOTE
l After the BSC6900 data configuration rights are already granted to one LMT user, other LMT users
cannot obtain it. If you are the admin or ADMINISTRATOR-level user, you can run the FOC
CMCTRL command to retrieve the data configuration rights.
l If an LMT user does not access the assigned BSC6900 data configuration rights exclusively, the rights
will be obtained automatically by the M2000 user during the BSC6900 maintenance through the
M2000.
----End
4.8 Undoing/Redoing a Data Configuration Action

This section describes how to undo and redo a single data configuration action.
Prerequisite
l You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration
Rights), and have run multiple configuration commands successfully.
l The quick configuration mode is disabled by running the SET QUICKCFG command.
l No batch commands were performed.
Context
l This task can be performed to fine-tune the configuration data. It cannot be used when the
quick configuration mode is enabled or when batch MML commands are run, because the

BSC6900 UMTS
operation of undoing or redoing a configuration action will decrease the efficiency of

running the MML commands.
l This function can be performed only with the exclusive operation rights to prevent
misoperations.
l This function does not apply to all MML commands. If you run a command that does not
support this function, the Undo and Redo buttons on the top of the LMT window becomes
unavailable. In this case, the previous configuration operations that support this function
cannot be undone or redone. For the lists of commands that support undoing or redoing a
configuration action, see the descriptions of the ADD ROLLBACKPOINT command.
l Undo a single configuration action: This operation is performed to undo a previous
configuration action. It is applicable to the latest 10 effective configuration actions.
l Redo a single configuration action: This operation is performed to redo a previously undone
configuration action. It is applicable to the latest 10 undone configuration actions.
Procedure
l Undoing a single configuration action
1. You can undo the latest configuration action in either of the following ways:
– Click Undo on the LMT toolbar.
– Run the BEG UNDO command.
2. To undo multiple actions, repeat Step 1.
l Redoing a single configuration action
1. You can redo an undone action in either of the following ways:
– Click Redo on the LMT toolbar.
– Run the BEG REDO command.
2. To redo multiple actions, repeat Step 1.
----End
4.9 Undoing/Redoing Multiple Data Configuration Actions

This section describes how to undo and redo multiple data configuration actions.
Prerequisite
Rights), and have run multiple configuration commands successfully.
l The quick configuration mode is disabled by running the SET QUICKCFG command.
l No batch commands were performed.
Context
l This task can be performed to fine-tune the configuration data. It cannot be used when the
quick configuration mode is enabled or when batch MML commands are run, because the
operation of undoing or redoing multiple configuration actions will decrease the efficiency
of running the MML commands.

BSC6900 UMTS
l This function can be performed only with the exclusive operation rights to prevent
misoperations.
l This function does not apply to all MML commands. If you run a command that does not
support this function after you set the rollback point by running the ADD
ROLLBACKPOINT command, the rollback point is invalidated. That is, you cannot undo
multiple configuration actions with the configured rollback point. In this case, you need to
remove the configured rollback point and configure a new one. For the lists of commands
that support undoing or redoing multiple configuration actions, see the descriptions of the
ADD ROLLBACKPOINT command.
l Undo multiple configuration actions: This operation is performed to undo multiple
configuration actions that took effect after a specified rollback point. After the undo
operation, the system rolls back to the configuration status at the specified rollback point.
l Redo multiple configuration actions: This operation is performed to redo the multiple
configuration actions that were undone previously. Through this operation, you can roll
back the system to the configuration at a specified rollback point or to the configuration
before the multiple configuration actions were undone.
NOTE
The initial rollback point is the first rollback point set by the user. The final rollback point is set
automatically when the latest configuration command is successfully run. A maximum of 10,000
configuration commands can be undone between the initial and final rollback points. If the system finds
more than 10,000 commands between the two rollback points, it does not undo the commands and reports
a failure message.
You can set a maximum of five rollback points. If you release the configuration rights, the OMU active
work area clears the information about the rollback stack and rollback points.
Procedure
Step 1 To undo/redo configuration actions in batches, you can use the ADD ROLLBACKPOINT
command to set the rollback points as required.
Step 2 Run the BEG ROLLBACK command to start the rollback.
Step 3 Run the BEG FORWARD command to resume the configurations that are rolled back.
----End

BSC6900 UMTS
LMT User Guide 5 Alarm Management
5 Alarm Management
About This Chapter
This describes how to manage BSC6900 alarms through the LMT. Alarm management allows
you to analyze alarms more efficiently and facilitates troubleshooting.
5.1 Concepts Related to Alarm Management

This section describes the basic concepts related to the alarm management, including the alarm
type, alarm severity, alarm-managed objects, and alarm box.
5.2 Managing Alarm Logs
Alarm logs are used to record details of alarms. They are collected by the OMU and stored in
the OMU database. You need to establish limitations on the number and storage time of alarm
logs to minimize storage requirements on the hard drive.
5.3 Managing the Alarm Filter
This section describes how to filter one or more alarms. The alarms that meet the filtering
conditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannot
be queried through the LMT or M2000. You can specify the conditions for filtering the alarms
on the LMT.
5.4 Managing the Filter of Derived Alarms
A derived alarm is caused by a root fault. BSC6900 supports filtering of the derived alarms. The
derived alarms are not reported to the LMT by default. Unless otherwise specified, the derived
alarms are not saved on the OMU and cannot be queried through the LMT.
5.5 Monitoring Alarms
In the Alarm Browse window of the LMT, you can monitor the alarm information sent to the
LMT in real time.
5.6 Managing the Alarm Box
The BSC6900 uses a universal alarm box of Huawei to provide audible and visual indications
when an alarm is reported.

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

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

The alarms in the BSC6900 system can be classified into fault alarms and event alarms.
5.1.2 Alarm Severity
The BSC6900 alarm severity indicates the severity of a fault. The fault alarms and event alarms
can be classified into four severity levels: critical, major, minor, and warning.
5.1.3 Alarm-Managed Objects
The alarms can be classified into 10 types based on different managed objects.
5.1.4 Alarm Box
BSC6900 uses the Huawei universal alarm box. The BSC6900 alarm box provides audible and
visual indications based on the alarm severity. It is optional and the BSC6900 can be configured
with only one alarm box. For details, see the documents delivered with the alarm box.
5.1.1 Alarm Type

The alarms in the BSC6900 system can be classified into fault alarms and event alarms.
Table 5-1 describes the two types of alarms.
Table 5-1 Fault alarms and event alarms
Alarm Type Description
Fault alarm Alarms caused by hardware faults or the exceptions of major functions, for
example, board failure or link failure. Fault alarms are of higher severity
than event alarms. The fault alarms are classified into active and cleared
alarms according to the fault status.
Event alarm Alarms of predefined events during the operation of the devices. The alarm
reflects the system condition (for example, congestion) during a specific
period, which is not necessarily a fault. Some event alarms are generated
repeatedly and regularly. Event alarms cannot be classified into active and
cleared alarms.
The fault alarms are classified into active and cleared alarms according to the fault status.
l Cleared alarm: If a fault is rectified, the corresponding alarm becomes a cleared alarm.
l Active alarm: If the fault is not rectified, the corresponding alarm is an active alarm.
For example, when congestion occurs in a cell, the system reports a fault alarm of cell
congestion. Before the congestion is cleared, the alarm remains active. After the congestion is
cleared, the alarm is cleared.

BSC6900 UMTS
NOTE
l The record of a cleared alarm is stored in the OMU database and can be queried.
l In scenarios where equipment is being deployed, commissioned, upgraded, swapped, cut over, or the
capacity of a base station is expanded, operations cause a great number of alarms to be reported. There
is no special mechanism to handle such alarms. Large in number and short in existence period, these
alarms make real fault alarms inconspicuous and thus disturb normal network monitoring. To solve
the problem discussed above, Huawei puts forward the concept of "engineering alarms". With the
concept, alarms in scenarios of engineering maintenance are identified and handled as special cases.
In this way, delicacy management of alarms is implemented and fault OM efficiency of the operator
is improved.
5.1.2 Alarm Severity

The BSC6900 alarm severity indicates the severity of a fault. The fault alarms and event alarms
can be classified into four severity levels: critical, major, minor, and warning.
Table 5-2 describes the four severity levels of alarms.
Table 5-2 Alarm severity levels
Alarm Severity Definition Handling

Requirement
Critical alarm Reporting faults that affect the services provided Handle the faults
by the system. These alarms need to be handled immediately to
immediately even during non-working hours. For avoid service
example, some equipment or resource breaks outage.
down.
Major alarm Reporting faults that affect the Quality of Service Handle the faults in
(QoS). These alarms need to be handled during time. Otherwise, the
working hours. For example, the performance of system may fail to
some equipment or resource deteriorates. perform some major
functions.
Minor alarm Reporting faults that are not serious enough to Find and rectify any
affect the QoS. These alarms can be handled as potential fault in
required or further observed to prevent them from time.
becoming critical. For example, you need clear
the obsolete history alarms.
Warning alarm Reporting faults that are potential threats to the Investigate the
system services. These alarms need to be handled problem and
according to specific situations. For example, resolved as required.
OMU startup alarm.
5.1.3 Alarm-Managed Objects

The alarms can be classified into 10 types based on different managed objects.
l Power system: alarms related to the power system
l Environment system: alarms related to the equipment room environment, such as
temperature, humidity, and door sensor

BSC6900 UMTS
l Signaling system: alarms related to the signaling system

l Trunk system: alarms related to the trunk system, including trunk circuits and trunk boards
l Hardware system: alarms related to a board, such as clock and CPU
l Software system: alarms related to the software
l Operating system: alarms generated during the operation of the system
l Communication system: alarms related to the communication system, such as alarms
between the BSC6900 host and the OMU
l QoS: alarms related to QoS
l Processing error: alarms caused by other exceptions not listed above
5.1.4 Alarm Box

BSC6900 uses the Huawei universal alarm box. The BSC6900 alarm box provides audible and
visual indications based on the alarm severity. It is optional and the BSC6900 can be configured
with only one alarm box. For details, see the documents delivered with the alarm box.
Figure 5-1 shows the alarm box.
Figure 5-1 Alarm box
When the BSC6900 reports a fault alarm to the LMT, the alarm box provides audible and visual
indications based on the alarm severity. When the LMT receives the fault alarm, the alarm box
generates a sound. The sound stops when the alarm is cleared. You can also manually stop the
sound on the LMT.
NOTE
The alarm box does not provide any indication for event alarms.

BSC6900 UMTS
5.2 Managing Alarm Logs

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

This section describes how to set the maximum number of alarm logs and the time limitations
of the logs that can be stored in the OMU database. Only the admin, OPERATOR-level,
5.2.2 Querying Storage Conditions of Alarm Logs
This section describes how to query the maximum number of alarm logs and the time limitations
of the logs that can be stored in the OMU database.
5.2.1 Setting Storage Conditions of Alarm Logs

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

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

This section describes how to filter one or more alarms. The alarms that meet the filtering
conditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannot

BSC6900 UMTS
be queried through the LMT or M2000. You can specify the conditions for filtering the alarms
on the LMT.
5.3.1 Creating an Alarm Filter

This section describes how to create an alarm filter. Only the admin, OPERATOR-level,
5.3.2 Deleting an Alarm Filter
If you do not want to filter an alarm through the BSC6900, delete the filters related to this alarm.
Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-level
users can perform this operation.
5.3.3 Querying an Alarm Filter
This section describes how to query the specific alarm filtering conditions.
5.3.1 Creating an Alarm Filter

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

If you do not want to filter an alarm through the BSC6900, delete the filters related to this alarm.
users can perform this operation.
Prerequisite
Procedure
Step 1 Run the LST OBJALMSHLD command to check whether the alarm filter to be deleted exists.

BSC6900 UMTS
If... Then...
The filter is listed, Go to Step 2.
The filter is not listed, End this operation.
Step 2 Run the RMV OBJALMSHLD command. Select the Object Type and set other parameters as
required to delete an alarm filter.
----End
5.3.3 Querying an Alarm Filter

This section describes how to query the specific alarm filtering conditions.
Prerequisite
Procedure
Step 1 Run the LST OBJALMSHLD command, and specify the Query Mode to query the alarm
filtering conditions.
----End
5.4 Managing the Filter of Derived Alarms

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

This section describes how to set the filter of the BSC6900 derived alarms. You can set the filter
of the derived alarms to ON or OFF. Only the admin, OPERATOR-level, ADMINISTRATOR-
level, and authorized CUSTOM-level users can perform this operation.
5.4.2 Querying the Filter of Derived Alarms
This section describes how to query the filter status of the BSC6900 derived alarms.
5.4.1 Setting the Filter of Derived Alarms

This section describes how to set the filter of the BSC6900 derived alarms. You can set the filter
of the derived alarms to ON or OFF. Only the admin, OPERATOR-level, ADMINISTRATOR-
level, and authorized CUSTOM-level users can perform this operation.
Prerequisite
l You have logged in to the LMT with an account authorized for this operation.
Rights).

BSC6900 UMTS
Procedure
Step 1 Run the SET ALMML command to enable or disable the filter of the derived alarms.
----End
5.4.2 Querying the Filter of Derived Alarms

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

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

This describes how to browse the fault alarms and event alarms on the LMT. The alarm
information provides the running status of the system in real time.
5.5.2 Querying the Alarm Log
This section describes how to query alarm history from the OMU database. Using this function,
you can review the past performance and condition of the system.
5.5.3 Querying Alarm Handling Suggestions
This section describes how to query the handling suggestions of an alarm.
5.5.4 Querying Alarm Configuration
This section describes how to query the alarm configuration.
5.5.5 Filtering Fault Alarms
This section describes how to filter alarms by sites and specific filter options in the Browse
Alarm tab page. Only the alarms that meet the specified requirements are displayed. All the
alarms, however, are reported to the LMT and saved on the OMU.
5.5.6 Setting Alarm Attributes
This section describes how to set the display attributes of the alarms in the Alarm window.
5.5.7 Manually Clearing an Alarm
This section describes how to manually clear an alarm. If a reported alarm can be neglected or
the corresponding fault has been rectified, you can manually set the corresponding alarm as a
clear alarm. Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized
5.5.8 Removing Alarms
This section describes how to remove the alarms on the Browse Alarm or Query Alarm Log
window.

BSC6900 UMTS
5.5.9 Refreshing the Alarm Window

This section describes how to manually refresh the alarm information when you browse or query
the alarms.
5.5.1 Browsing Alarms

This describes how to browse the fault alarms and event alarms on the LMT. The alarm
information provides the running status of the system in real time.
Prerequisite
Procedure
Step 1 Click Alarm on the LMT main page to display the Browse Alarm tab page. The Fault,
Event, and Engineering alarm tab pages are displayed under the Browse Alarm tab.
Step 2 Browse alarms in the Browse Alarm tab page.
Step 3 To view the details of an alarm, double-click it. The Detail dialog box carrying the detailed
information about the alarm is displayed.
Step 4 To save an alarm, select corresponding entry, and click Save. Alternatively, right-click the
corresponding entry, and then choose Save Selected Records from the shortcut menu.
----End
5.5.2 Querying the Alarm Log

This section describes how to query alarm history from the OMU database. Using this function,
you can review the past performance and condition of the system.
Prerequisite
Context
You can set the following query conditions:
l Alarm Type
l Alarm Severity
l Alarm Time
l Special Alarm Flag
l Return Amount
l Alarm-Managed Objects
l Alarm ID
l Alarm Serial No.
You can query the alarm logs through menu operations or through MML commands.

BSC6900 UMTS
Procedure
1. You can set the query conditions on the Query Alarm Log tab page under the
Alarm tab.
2. Set the query parameters as required. To reset the query parameters, click Reset.
3. Click Query. The query results are displayed in the Result area on the lower part of
the window.
4. To learn more about an alarm, double-click it. The displayed Alarm Detailed
Information dialog box shows the details of the alarm.
5. To save an alarm, select the corresponding entry, right-click it, and then choose Save
Selected Records from the shortcut menu.
6. To save the queried records, click Save.
1. Run the LST ALMLOG command to query the alarm logs.
----End
5.5.3 Querying Alarm Handling Suggestions

This section describes how to query the handling suggestions of an alarm.
Prerequisite
Context
The LMT provides the following help information for all alarms:
l Alarm meaning
l Alarm impact
l System action
l Solution
Procedure
Step 1 In the Alarm tab page, double-click an alarm in the Browse Alarm or Query Alarm Log tab
page. The Alarm Detailed Information dialog box is displayed.
Step 2 In the Alarm Detailed Information dialog box, click Solution.... The online help window is
displayed.
NOTE
You can also right-click an alarm and choose Solution to view the online help of this alarm.
Step 3 Find the handling suggestions or other required information in the online help.
----End
5.5.4 Querying Alarm Configuration

This section describes how to query the alarm configuration.

BSC6900 UMTS
Prerequisite
Context
You can set the following query conditions:
l Alarm ID
l Alarm Severity
l Modification Flag
l Shield Flag
l Return Amount
Procedure
Step 1 Set the query conditions in the Query Alarm Configuration page under the Alarm tab.
Step 2 Set the query conditions as required.
Step 3 Click Query. The query results are displayed in the Result area.
NOTE
If you need to modify the alarm settings, click Modify Alarm Configuration, or right-click the Result
area and choose Modify Alarm Configuration from the shortcut menu.
----End
5.5.5 Filtering Fault Alarms

This section describes how to filter alarms by sites and specific filter options in the Browse
Alarm tab page. Only the alarms that meet the specified requirements are displayed. All the
alarms, however, are reported to the LMT and saved on the OMU.
Prerequisite
Procedure
Step 1 Click Alarm on the LMT main page. The Browse Alarm tab page is displayed.
Step 2 Click Filter Fault Alarm. The Set Alarm Filtering Conditions dialog box is displayed.
NOTE
The Set Alarm Filtering Conditions dialog box is displayed automatically, the first time you enter the
Filter Fault Alarm tab page.
Step 3 In the Set Alarm Filtering Conditions dialog box, set the Alarm ID or Alarm Source. Then,
click OK. The alarms that meet the specified requirements are displayed.
----End

BSC6900 UMTS
5.5.6 Setting Alarm Attributes

This section describes how to set the display attributes of the alarms in the Alarm window.
Prerequisite
Context
You can set the following alarm attributes:
l Set alarm colors
l Set alarm table columns
l Show/Hide tips
Procedure
Step 1 Click Setting on the upper right of the Alarm tab page to set the display attributes of the alarms.
----End
5.5.7 Manually Clearing an Alarm

This section describes how to manually clear an alarm. If a reported alarm can be neglected or
the corresponding fault has been rectified, you can manually set the corresponding alarm as a
clear alarm. Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized
Prerequisite
Procedure
Step 1 Run the RMV ALMFLT command to manually clear an alarm.
----End
5.5.8 Removing Alarms

This section describes how to remove the alarms on the Browse Alarm or Query Alarm Log
window.
Prerequisite
Procedure
Step 1 In the Browse Alarm or Query Alarm Log tab page under the Alarm tab, click Delete All
Clear Alarms or Delete All Alarms to delete the alarms as required. Table 5-3 describes the
functions of the buttons.

BSC6900 UMTS
Table 5-3 Functions of the buttons

Option Description
Delete All Clear Alarms Deletes all the clear alarms in the active window. Available on the
Query Alarm Log tab page.
Delete All Alarms Deletes all alarms in the active window. Available on the Browse
Alarm or Query Alarm Log tab pages.
----End
5.5.9 Refreshing the Alarm Window

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

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

This section describes how to query the version information of the alarm box and the active
alarms that drive the alarm box.
5.6.2 Querying Number of Alarms with Different Severities
This section describes how to query the number of alarms corresponding to a specific severity
indicated by an alarm LED.
5.6.3 Operating the Alarm Box
This section describes how to reset the alarm box, stop the alarm sound, and turn off the alarm
LED.
5.6.4 Querying the Alarm Box Filter Level

BSC6900 UMTS
This section describes how to query and set the filter level for reporting alarms to the alarm box.
All alarms with a severity higher than the filter level are reported to the alarm box. Otherwise,
the alarms are not reported.
5.6.1 Querying Alarm Box Information

This section describes how to query the version information of the alarm box and the active
alarms that drive the alarm box.
Prerequisite
l The BSC6900 is connected to the alarm box.
l The Convert Management System is started, and it communicates with the OMU normally.
Procedure
l Run the LST BOXVER command to query the version information of the alarm box.
l Run the LST BOXALM command to query the active alarms that drive the alarm box.
----End
5.6.2 Querying Number of Alarms with Different Severities

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

This section describes how to reset the alarm box, stop the alarm sound, and turn off the alarm
LED.
Prerequisite

BSC6900 UMTS

Procedure
l Run the RST ALMBOX command to reset the alarm box.
l Run the CLR BOXLGT to manually turn off the alarm LEDs.
l Run the STP BOXSND command to stop the alarm sound.
----End
5.6.4 Querying the Alarm Box Filter Level

This section describes how to query and set the filter level for reporting alarms to the alarm box.
All alarms with a severity higher than the filter level are reported to the alarm box. Otherwise,
the alarms are not reported.
Prerequisite
Context
operators can set alarm filter level.
Procedure
l Run the LST ALMSCRN command to query the filter level on the alarm box.
l Run the SET ALMSCRN command to set the filter level on the alarm box.
----End

BSC6900 UMTS
LMT User Guide 6 Log Management
6 Log Management
About This Chapter
This chapter describes how to manage the BSC6900 logs through the LMT. Log files can be
saved in .txt and .log formats. Only the admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can manage the logs.
6.1 Log Types

The logs are classified into operation logs, security logs, and running logs.
6.2 Querying Log Storage Conditions
This section describes how to query the conditions for storing the operation logs and security
logs, including the time limit and storage capacity of the logs.
6.3 Setting Log Storage Conditions
This section describes how to set the conditions for storing the operation and security logs,
including the time limit and the storage capacity. The OMU database automatically deletes an
entry that has crossed the specified time limit or the earliest entry when the number of saved
logs exceeds the specified capacity.
6.4 Querying Operation Logs
This section describes how to query an operation log from the OMU database. By performing
this task, you can obtain information about the BSC6900 operations.
6.5 Exporting Operation Logs
This describes how to use the FTP Client to download to the LMT PC an exported operation log
that is saved in the directory OMU active workspace installation directory\ftp.
6.6 Querying Security Logs
This section describes how to query the security logs from the OMU database. By performing
this task, you can learn about the security events such as login, logout, and authorization in the
BSC6900.
6.7 Exporting Security Logs
This section describes how to use the FTP Client to download to the LMT PC an exported security
log that is saved in the directory OMU active workspace installation directory\ftp.
6.8 Exporting Running Logs
This section describes how to use the FTP Client to download to the LMT PC an exported running
log that is saved in the bam\common\fam\famlog directory.

BSC6900 UMTS
6 Log Management LMT User Guide
6.9 Collecting Log Statistics

This section describes how to collect the log statistics for fault analysis. There are different types
of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installation
logs, remote upgrade logs, and alarm logs.

BSC6900 UMTS
6.1 Log Types

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

This section describes how to query the conditions for storing the operation logs and security
logs, including the time limit and storage capacity of the logs.
Prerequisite
Procedure
Step 1 Run the LST LOGLIMIT command to query the conditions for storing the logs.
----End
6.3 Setting Log Storage Conditions

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

BSC6900 UMTS
Procedure
Step 1 Run the SET LOGLIMIT command. Set the Time Limit and Counts Limit, and then choose
a Log Type.
NOTE
l Time Limit ranges from 7 to 365 days and the default setting is 30 days.
l Counts Limit ranges from 10,000 to 50,000 entries, and the default setting is 50,000 entries.
----End
6.4 Querying Operation Logs

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

This describes how to use the FTP Client to download to the LMT PC an exported operation log
that is saved in the directory OMU active workspace installation directory\ftp.
Prerequisite
Procedure
Step 1 Run the EXP LOG command. Set Log Type to OPTLOG(Operating Log) and other
parameters as required to export the corresponding log information. When exporting operation
logs, you can name the file or use the default name provided by the system. The default name
of the exported file is MBSC-start time-end time-OLOG.txt.
l If Time Mode is set to RELATIVE_T(Relative Time), the operation log within the latest
N hours is exported. N stands for the relative time length. For example, if Relative Time is
72, then the log within the latest 72 hours is exported.
l If Time Mode is set to ONTIME(Fixed Time), the operation log within the absolute time
is exported. For example, Start Time for exporting the operation log is 2007-06-11 17:32:46

BSC6900 UMTS
and End Time is 2007-06-12 17:32:46. The default file name is MBSC-
Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-OLOG.txt.
The default save path for the exported logs is OMU active workspace installation directory
\FTP on the OMU active workspace.
Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The
FTP Client is started.
Step 3 In the server entry bar on the FTP Client, enter the external virtual IP address of the OMU, the
FTP user name, and the password.
NOTE
The FTP user name and password is set when the OMU is installed. The FTP user name is FtpUsr by
default.
Step 4 Click Enter to connect the OMU. The connecting status is displayed in the Connection tips
pane.
Step 5 After the connection is successful, in the server file list pane, double-click OMU active
workspace installation directory\ftp. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the operation log file to download it to the LMT PC.
Step 7 When the download is complete, choose System > Exit or click the close button to exit the FTP
Client.
----End
6.6 Querying Security Logs

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

This section describes how to use the FTP Client to download to the LMT PC an exported security
log that is saved in the directory OMU active workspace installation directory\ftp.

BSC6900 UMTS
Prerequisite
Procedure
Step 1 Run the EXP LOG command. Set Log Type to SECLOG(SECURITY LOG) and other
requirements as required to export the corresponding log information. When exporting the
security logs, you can name the file or use the default name provided by the system. The default
name of the exported file is MBSC-start time-end time-SLOG.txt.
l If Time Mode is set to RELATIVE_T(Relative Time), the security log within the last N
hour(s) before the command is executed is exported. N stands for the relative time length.
For example, if Relative Time is 72, then the log within the latest 72 hours is exported.
l If Time Mode is set to ONTIME(Fixed Time), the security log within the absolute time is
exported. For example, Start Time for exporting the security log is 2007-06-11 17:32:46
and End Time is 2007-06-12 17:32:46. The default file name is MBSC-
Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-SLOG.txt.
The default save path for the exported logs is OMU active workspace installation directory
\FTP on the OMU active workspace.
FTP user name, and the password.
NOTE
default.
pane.
Step 5 After the connection is successful, in the server file list pane, double-click OMU active
workspace installation directory\ftp. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the security log file to download it to the LMT PC.
Client.
----End
6.8 Exporting Running Logs

This section describes how to use the FTP Client to download to the LMT PC an exported running
log that is saved in the bam\common\fam\famlog directory.
Prerequisite

BSC6900 UMTS
Procedure
Step 1 Run the ULD LOGTOOMU command. Enter the subrack number, and export the
corresponding log information.
NOTE
l The format of the file name is subrack number/Log/yyyy/mm/dd/hh/mm/ss.log. For example, for
the running log of the No. 3 EPS that is uploaded to the OMU at 2008-11-07 17:19:47, the file name
is 03Log20081107171947.log.
l By default, the uploaded running logs are saved in the bam\common\fam\famlog directory.
user name, and the password.
NOTE
default.
pane.
Step 5 After the connection is successful, in the server file list pane, double-click bam\common\fam
\famlog. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the running log file to download it to the LMT PC.
Client.
----End
6.9 Collecting Log Statistics

This section describes how to collect the log statistics for fault analysis. There are different types
of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installation
logs, remote upgrade logs, and alarm logs.
Prerequisite
Procedure
Step 1 Run the COL LOG command. Set the required parameters to collect the corresponding log
statistics. For more description of log ,see Table 6-1.

BSC6900 UMTS
Table 6-1 Description of Logs

Type File Path Description
PFM_RESULT /bam/version_a/ftp/ Recording traffic statistics

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

(Performance Result File COLLOGINFO/PFM-LOG/ from boards to the OMU.
from Host) Used for traffic analyzing.
ACTIVE_DEF_MEAS_FIL /bam/version_a/ftp/ Active traffic statistic

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

ILE(Standby Default COLLOGINFO/PFM-LOG/ definition file from the
Measurement Task File) M2000 to NEs. Used for
traffic analyzing.
PFM_SWITCHS(The / Reserved parameter value.

Switchs Information for
Performance)
HISTORY_ALARM /bam/version_a/ftp/ Recording alarms and events

(History Alarm File) COLLOGINFO/ALM-LOG/ reported by NEs. Used for
alarm and event analysis.
HISTORY_FAULT(History /bam/version_a/ftp/ Recoding the faults reported

Fault File) COLLOGINFO/ALM-LOG/ by all NEs. Used for fault
analysis.
ALM_SYSTEM_CFG(The /bam/version_a/ftp/ Recording the configuration

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

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

COLLOGINFO/OPT-LOG/ for analyzing user operations
on the NE.
OMU_LOG(The Log /bam/version_a/ftp/ Operation and status logs of

Information of OMU) COLLOGINFO/SINGLE- the OMU board. Used for
BAM/ analyzing OMU faults and
status.
BSC_CFG_MML(The Data /bam/version_a/ftp/ Recording the BSC

Configure File of the BSC) COLLOGINFO/CFG-LOG/ configuration data. Used for
ExportCfgmml/ configuration data
restoration.

BSC6900 UMTS
CELL_BASIC_INFO(The /bam/version_a/ftp/ Recoding the basic

Basic Information of Cells) COLLOGINFO/CFG-LOG/ information of cells under a
CellBasicInfo/ BSC. Used for checking the
mapping between cell IDs
and internal cell IDs.
BSC_SERIES_NO(The /bam/version_a/ftp/ Recording the Equipment

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

of the Database) COLLOGINFO/CFG-LOG/ information. Used for data
MysqlDbBak/ restoration.
MEM_DB_BAK(The /bam/version_a/ftp/ Backed up OMU

Backup File of the Database COLLOGINFO/CFG-LOG/ memory database. Used for
in Memory) MemDbBak/ locating the inconsistency
between the memory
database and the MYSQL
database.
DEBUG_LOG(The /bam/common/fam/ Recording software running

Common Debug Log) famlogfmt/ errors. Used for locating soft-
ware defects.
LAST_WORD(The Last /bam/common/fam Recording the log

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

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

Log of the Host)
3G_CHR_LOG(The CHR /bam/common/fam/ Recording call faults except

Log for UMTS) famlogfmt/ faults during call access and
call drops. Used for
analyzing the causes of
failures in failed soft or hard
handovers, relocations, or
cell updates.

BSC6900 UMTS
BSC_INFO(The Basic /bam/version_a/ftp/ Recording the BSC software

Information of the BSC) COLLOGINFO/BSC-LOG/ 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/ BIOS system abnormal

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

(CALLFAULT Log) famlogfmt/ access and call drops. Used
for analyzing the causes of
call access failures and call
drops.
PCHR_LOG(PCHR Log) /bam/common/fam/ Recording detailed

famlogfmt/pchr information of each call,
including service access, call
release, handover, DCCC,
and signal quality. Used for
KPI analysis and as a
reference when handling user
complaints.
SYSFAULT_LOG /bam/common/fam/ Recording severe software/

(SYSFAULT Log) famlogfmt/sysfault/ hardware faults such as
resource leakages and device
faults. Used for network
health check.
NOTE
l version_a is the active workspace of OMU.
----End

BSC6900 UMTS
LMT User Guide 7 Trace Management
7 Trace Management
About This Chapter
This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 trace
7.1 Concepts Related to Trace Management

Trace management is performed during routine maintenance of equipment, and traces messages
on interfaces and signaling links to verify data and locate faults. Do not start excessive tracing
tasks when traffic is high, as it slows the LMT responses. In this case, set Trace Mode to Save
To OMU before beginning a tracing task.
7.2 UMTS Services
This section describes how to perform tracing tasks related to UMTS services.
7.3 Basic Tracing Operations
The basic operations of message tracing apply to all the BSC6900 message tracing tasks.

BSC6900 UMTS
7 Trace Management LMT User Guide
7.1 Concepts Related to Trace Management

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

This describes the principles of message tracing. It also describes how to create or close message
tracing tasks and the internal process for the service module to report traced messages to the
LMT.
7.1.2 Management of Tracing Operation Rights
You must have the relevant rights to perform message tracing operations.
7.1.3 Trace Mode
This section describes trace modes of signaling tracing on an interface on a BSC LMT. Trace
modes determine where to save results of signaling tracing and knowledge of trace modes
facilitates finding of tracing results.
7.1.1 Trace Principles

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

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

1. When you create a tracing task on the LMT, the LMT sends a binary command to the OMU
to create the task.
2. The OMU assigns an ID to the task and forwards the command to the debugging module
of the specified board.

BSC6900 UMTS
3. After receiving the command, the debugging module records the filter parameters of the
trace data in the filter table and notifies the service module.
4. The service module updates the local filter table according to the message from the
debugging module.
Internal Procedure for Closing a Tracing Task

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

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

This section describes trace modes of signaling tracing on an interface on a BSC LMT. Trace
modes determine where to save results of signaling tracing and knowledge of trace modes
facilitates finding of tracing results.
The trace modes of signaling tracing on an interface are divided into the following two types:
l Report
In this mode, the trace results are reported in real time. The OMU sends the traced messages
to an LMT PC directly, and the output file is automatically saved to the LMT PC in the
*.tmf format.
l Save to OMU
In this mode, you can set the trace interval. The traced messages are saved on the OMU
and are not reported to the LMT PC. The output file is saved to the OMU in the *.tmf
format. The default path is \mbsc\bam\common\fam\trace directory of the OMU.
You can view tracing results saved on the OMU by referring to Browsing Traced Messages
Offline.

BSC6900 UMTS
7.2 UMTS Services

This section describes how to perform tracing tasks related to UMTS services.
7.2.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.
7.2.2 Tracing Messages on the Iur Interface
This section describes how to trace the signaling messages over the Iur interface, including the
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.
7.2.3 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.
7.2.4 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.
7.2.5 Tracing IP Messages
This function is used to trace IP messages exchanged between the RNC and the NodeB, between
the MSC and the RNC, or between interface boards within the RNC when IP transmission mode
is used. Based on the tracing result, engineers can analyze and identify the problem of packet
loss during IP transmission.
7.2.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.
7.2.7 Tracing UE Messages
This section describes how to trace UE messages. You can perform this task to analyze the call
procedure failure cause by monitoring interworking of the signaling on each standard interface,
interworking of the signaling on the user plane, and uplink and downlink data. In combination
with a drive test, this task helps to locate problems or deal with complaints from VIP subscribers.
7.2.8 Tracing Cell Messages
This section describes how to trace cell messages. The UE statistics can be reported in the tracing
result if required. The tracing results of the cell messages provide reference for troubleshooting
common channel faults when the access success rate is low or zero in the cell.
7.2.9 Tracing IOS Messages

BSC6900 UMTS
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.
7.2.10 Location Report Control
This section describes how to trace the results of a location tracing initiated by the CN. You can
also perform this task to simulate CN-initiated location tracing and to trace the results of the
location tracing.
7.2.1 Tracing Messages on the Iu Interface

This section describes how to trace the signaling messages over the Iu interface, including the
identify the failure cause in the following procedures: RAB assignment, RAB release, paging,
Iu release, security mode control, initial UE message, and relocation.
Prerequisite
Context
You can start the Iu interface tracing on the LMT to monitor interworking of the signaling
messages on the Iu interface.
When starting a tracing task, you can make the following choices:
l Tracing the messages processed by a specified CPUS subsystem
l Tracing the required types of message
l Tracing all types of messages
l Tracing signaling messages at the transport network layer
For each subsystem, a maximum of six tracing tasks can be performed on the Iu interface
simultaneously. Therefore, the maximum number of tracing tasks that can be performed on the
Iu interface is the number of subsystems multiplied by six.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab page is displayed.
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iu Interface Trace.
Accordingly, the Iu Interface Trace dialog box is displayed, as shown in Figure 7-2.

BSC6900 UMTS
Figure 7-2 Message tracing on the Iu interface
Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and select
IU under Trace Type.
l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,
DPC(HEX) needs to be specified.
l For description of Trace Mode, see 7.1.3 Trace Mode.
Step 4 In the IU tab page, select Message Type.
Step 5 Click Submit.
----End
Result
l Successful operation
– No traced message is displayed on the LMT if the Save to OMU trace mode is selected.
You can view the tracing result saved on the OMU by referring to Browsing Traced
Messages Offline.
– A window shown in Figure 7-3 is displayed if the Report trace mode is selected. The
message browsing window displays information about each traced message, including
the task number, task time, RFN, subrack number, slot number, subsystem number,
message direction, message type, message source, user ID, and message content.

BSC6900 UMTS
Figure 7-3 Results of tracing messages on the Iu interface
l If the tracing fails, a dialog box is displayed with the failure cause.
Follow-up Procedure
l You can double-click a result in the displayed result area to view the detailed information
about the traced message.
l You can perform required operations by referring to 7.3 Basic Tracing Operations.
7.2.2 Tracing Messages on the Iur Interface

This section describes how to trace the signaling messages over the Iur interface, including the
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.
Prerequisite
Context
For each subsystem, a maximum of six Iur interface tracing tasks can be performed
Iur interface is the number of subsystems multiplied by six.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iur Interface Trace.
Accordingly, the Iur Interface Trace dialog box is displayed, as shown in Figure 7-4.

BSC6900 UMTS
Figure 7-4 Message tracing on the Iur interface
Step 3 In the Iur Interface Trace dialog box, set parameters in the default Basic tab page and select
IUR under Trace Type.
l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,
DPC(HEX) needs to be specified.
Step 4 In the IUR tab page, select Message Type.

NOTE
In the IUR tab page, if you select IUR_G, the Iur-g interface messages between BSC6900s or in a
BSC6900 are traced. If you select InMbsc, the Iur-g interface messages between the GSM and UMTS in
a BSC6900 are traced.
----End
Result

BSC6900 UMTS
Messages Offline.
– A window is displayed if the Report trace mode is selected. The message browsing
window displays information about each traced message, including the task number,
task time, RFN, subrack number, slot number, subsystem number, message direction,
message type, message source, user ID, and message content.
Follow-up Procedure
7.2.3 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.
Prerequisite
Context
For each subsystem, a maximum of six Iub interface tracing tasks can be performed
Iub interface is the number of subsystems multiplied by six.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iub Interface Trace.
Accordingly, the Iub Interface Trace dialog box is displayed, as shown in Figure 7-5.

BSC6900 UMTS
Figure 7-5 Message tracing on the Iub interface
Step 3 In the Iub Interface Trace dialog box, set parameters in the default Basic tab page and select
IUB under Trace Type.
Step 4 In the IUB tab page, select Message Type and set other parameters.
----End
Result
Messages Offline.

BSC6900 UMTS
Figure 7-6 Results of Tracing Messages on the Iub Interface
Follow-up Procedure
7.2.4 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.
Prerequisite
Context
You can start the Uu interface tracing on the LMT to monitor interworking of signaling messages
on the Uu interface.
When starting a tracing task, you can make the following choices:
l Tracing messages of one or multiple BSC6900s and the cells
l Tracing all types of messages on the Uu interface
l Tracing the specified types of messages
A maximum of six Uu interface tracing tasks can be performed simultaneously. Each Uu
interface tracing task targets at a maximum of 32 cells.
Procedure

BSC6900 UMTS
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Uu Interface Trace.
Accordingly, the Uu Interface Trace dialog box is displayed, as shown in Figure 7-7.
Figure 7-7 Message tracing on the Uu interface
Step 3 In the Uu Interface Trace dialog box, specify RNCID:CellID under Cell Config and set other
parameters.
l RNC ID indicates the RNC ID of the cell to be traced. To query it, run the LST
URNCBASIC command.
l CellID needs to be set to the ID of the cell sending and receiving messages. The parameter
can be queried by running the LST UCELL command.
----End
Result
Messages Offline.

BSC6900 UMTS
Figure 7-8 Results of message tracing on the Uu interface
Follow-up Procedure
7.2.5 Tracing IP Messages

This function is used to trace IP messages exchanged between the RNC and the NodeB, between
the MSC and the RNC, or between interface boards within the RNC when IP transmission mode
is used. Based on the tracing result, engineers can analyze and identify the problem of packet
loss during IP transmission.
Prerequisite
Context
When a trace is started, you can specify Flow Trace Type to trace IP messages in different
transmission directions. When Flow Trace Type is set to RNC Input Flow, IP messages from
the NodeB to the RNC are traced. When Flow Trace Type is set to RNC Output Flow, IP
messages from the RNC to the NodeB are traced. When Flow Trace Type is set to GTPU
Uplink, IP messages from the RNC to the MSC are traced. When Flow Trace Type is set to
GTPU Downlink, IP messages from the MSC to the RNC are traced.

BSC6900 UMTS
Procedure
Step 2 In the Trace Navigation Tree pane, choose Trace > UMTS Services > IP Trace. The IP
Trace dialog box is displayed.
Step 3 In the IP Trace dialog box, set the parameters as required, and click Submit.
----End
7.2.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.
7.2.7 Tracing UE Messages

This section describes how to trace UE messages. You can perform this task to analyze the call
procedure failure cause by monitoring interworking of the signaling on each standard interface,
interworking of the signaling on the user plane, and uplink and downlink data. In combination
with a drive test, this task helps to locate problems or deal with complaints from VIP subscribers.
Prerequisite
Context
The UE tracing task is to trace signaling messages of a UE on the Iu, Iur, Iub, and Uu interfaces.
The UE can be specified by IMSI, TMSI, P-TMSI, or IMEI.
NOTE
A maximum of 12 UE tracing tasks can be performed simultaneously.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. Accordingly,
the UE Trace dialog box is displayed, as shown in Figure 7-9.

BSC6900 UMTS
Figure 7-9 UE message tracing
Step 3 In the displayed UE Trace dialog box, set the parameters as required.
l IMSI/IMEI/TMSI/P-TMSI: identifies the UE. You can choose to trace the UE by its IMSI,
IMEI, TMSI, or P-TMSI. Choosing to trace the UE by the TMSI, you need to specify LAC,
MCC, and MNC. Choosing to trace the UE by the P-TMSI, you need to specify LAC, RAC,
MCC, and MNC.
l Filter traced messages by setting parameters in the IUR, IUB, IU, and UU tab pages.
l Monitor tab page: indicates performance counters to be monitored during tracing of a single
UE
– Uplink SIR: Selecting the counter starts monitoring of uplink Signal to Interference Ratio
(SIR) during tracing of a single UE. The counter is reported periodically. The period of
reporting the monitoring reports ranges from 0.1s to 60s.
– Uplink Tx Power: Selecting the counter starts monitoring of uplink transmit power
during tracing of a single UE. The counter is reported periodically. The period of reporting
the monitoring reports ranges from 0.25s to 64s.
– Downlink BLER: Selecting the counter starts monitoring of Block Error Rate (BLER)

BSC6900 UMTS
– Downlink Tx Code Power: Selecting the counter starts monitoring of downlink code
transmit power during tracing of a single UE. The counter is reported periodically. The
period of reporting the monitoring reports ranges from 0.1s to 60s.
– PCPICH Ec/No RSCP: Selecting the counter starts monitoring of PCPICH Ec/No and
Received Signal Code Power (RSCP) during tracing of a single UE. The counter is
reported periodically. The period of reporting the monitoring reports ranges from 0.1s to
60s.
– AMR Mode: Selecting the counter starts monitoring of AMR mode during tracing of a
single UE. The counter is reported periodically. If AMR mode changes, the current mode
is reported.
– RTWP(0.4s): Selecting the counter starts monitoring of received total wideband power
(RTWP) received for the cell serving the current UE. The counter is reported every 0.4
second.
– TRX Transmit Power(0.4s): Selecting the counter starts monitoring of downlink
transmit power transmitted for the cell serving the current UE. The counter is reported
every 0.4 second.
----End
Result
Messages Offline.
Figure 7-10 Results of UE message tracing

BSC6900 UMTS
NOTE
l If you trace a UE by specifying the IMSI and the IMSI is carried in the RRC CONNECTION
REQUEST message sent by the UE for network access, the UE tracing task traces all the
messages that are sent after the RRC CONNECTION REQUEST message.
l Assume that you trace a UE by specifying the IMSI and the IMSI is not carried in the RRC
CONNECTION REQUEST message but only carried in the RANAP COMMON ID
message. If CDT_MSG_FULL_TRACE is set to ON, the UE tracing task traces the messages
that are sent after the RANAP COMMON ID message, and the messages sent before the
RANAP COMMON ID message are buffered and reported. If CDT_MSG_FULL_TRACE
is set to OFF, the messages sent before the RANAP COMMON ID message are discarded
instead.
Follow-up Procedure
7.2.8 Tracing Cell Messages

This section describes how to trace cell messages. The UE statistics can be reported in the tracing
result if required. The tracing results of the cell messages provide reference for troubleshooting
common channel faults when the access success rate is low or zero in the cell.
Prerequisite
Context
You can specify a cell by entering Cell ID and specify a message type to be traced by selecting
a trace event. The cell message tracing task can be used to trace NBAP common messages on
the Iub interface of a specified cell and to report the UE statistics as required. The cell to be
traced must be activated.
NOTE
l A maximum of six cell tracing tasks can be performed simultaneously.

l Each cell tracing task targets only one cell.
l Each cell tracing task targets a maximum of two S-CCPCHs.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Cell Trace. Accordingly,
the Cell Trace dialog box is displayed, as shown in Figure 7-11.

BSC6900 UMTS
Figure 7-11 Cell message tracing
Step 3 Set parameters in the Cell Trace dialog box.

l Cell ID: indicates the index of a cell.
l USER_VOLUME/PROPAGATION_DELAY: indicates the event to be traced, including
the USER_VOLUME event or PROPAGATION_DELAY event. If you select the
USER_VOLUME event, some custom messages reflecting statistics about UEs in a cell will
be reported. The value ranges from 1000 to 10000 with the unit of 10 ms. If you select the
PROPAGATION_DELAY event, propagation delay in messages will be reported. The
value ranges from 1 to 80 with the unit of times.
l FMR tab page: The following filtering conditions are specified in the FMR tab page.
– Service Data Trace: specifies different types of data report in the area
– SCCPCH ID: specifies 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: If FP Data Periodic Report or Transport Data Periodic Report is
selected in the FMR tab page, Report Period(100ms) needs to be specified.
l You can select messages to be traced on the Iub interface in the IUB tab page.
----End

BSC6900 UMTS
Result
Messages Offline.
Figure 7-12 Results of cell message tracing
Follow-up Procedure
7.2.9 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.
Prerequisite

BSC6900 UMTS
Context
Assume that the specified number of continuous calls is N. If N calls are already being traced,
the system does not trace any newly accessed calls. If the number becomes less than N because
of the termination of a traced call, the system automatically traces a new call.
A maximum of six IOS tracing tasks can be performed simultaneously. Each task targets a
maximum of 30 calls and 32 cells.
You need to specify the number of successive calls to be traced, tracing cell range, sampling
criteria, and tracing time. The calls that meet the sampling criteria are traced within the specified
tracing time. When creating a new call tracing task, you can define the sampling criteria by
setting the RAB parameter constraints and the RRC Est Cause. Once the call meets the criteria,
the tracing of the call is not stopped even if the RAB parameters of the RRC establishment cause
are changed during the call. If the initial settings of the RAB parameters or the RRC
establishment cause value of a call does not meet the criteria, the BSC6900 does not trace the
call even if these parameters are modified to meet the criteria during the call. You can specify
the message types to be traced by selecting the event types. You can also select one or more
cells to trace.
CAUTION
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.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > IOS Trace. Accordingly,
the IOS Trace dialog box is displayed, as shown in Figure 7-13.

BSC6900 UMTS
Figure 7-13 IOS message tracing
Step 3 In the displayed IOS Trace dialog box, set parameters and filter traced messages in other tab
pages.
l Call Count: indicates the maximum number of calls that can be traced simultaneously after
a tracing task is started. The value ranges from 1 to 30.
l Cell ID: You can type the ID of one cell or IDs of multiple cells.
l Event Type: indicates types of event to be traced. The event types classify all messages
related to calls. You can select or clear all event types by clicking Select All or Clear All.
You can restore the setting to the original one by clicking Reset.
l RAB tab page: RAB parameters are specified in the tab page. If the BSC6900 receives an
RAB ASSIGNMENT REQUEST message of a call that matches the specified RAB
parameters in the specified cell, the call is traced. If a call sets up multiple RAB links, the
call is traced if one of the RAB links meets the specified RAB parameters.
l RRC tab page: The RRC establishment cause is specified in the tab page. If the BSC6900
receives an RRC_CONN_REQ message of a call that matches the specified RRC
establishment cause in the specified cell, the call is traced.
– RRC(ms): indicates the period of reporting measurement results of PCPICH Ec/No and
Received Signal Code Power (RSCP) when forward power control tracing is selected or
PCPICH Ec/No RSCP in the Monitor tab page is selected for IOS tracing
– UE Internal RRC(ms): indicates the period of reporting measurement results of UE
transmit power when forward power control tracing is selected or UE Tx Power in the
Monitor tab page is selected for IOS tracing

BSC6900 UMTS
– UE Quality RRC(ms): indicates the period of reporting measurement results of downlink

Block Error Rate (BLER) when forward power control tracing is selected or Downlink
BLER in the Monitor tab page is selected for IOS tracing
– NBAP Common (ms): indicates the period of reporting results of cell common
measurement that is selected in the Monitor tab page of IOS Trace
– NBAP Special RRC(ms): indicates the period of reporting measurement results of
downlink code transmit power in the SRNC cell when forward power control tracing is
selected or Downlink Tx Code Power in the Monitor tab page is selected for IOS tracing
– RNSAP Special RRC(ms): indicates the period of reporting measurement results of
downlink code transmit power in the DRNC cell when forward power control tracing is
selected or Downlink Tx Code Power in the Monitor tab page is selected for IOS tracing
– RRC Located Type: indicates the type of location measurement during IOS tracing
– RRC Located Cycle(ms): indicates the period of reporting results of location
measurement during IOS tracing
– RTT Special NBAP(ms): indicates the period of reporting results of Round Trip Time
(RTT) measurement in the SRNC cell when forward power control tracing is selected or
the Monitor tab page is configured for IOS tracing
– RRC Est Cause: indicates call establishment causes and filters UEs to be traced in the
cell based on the call establishment causes
l Monitor tab page: indicates performance counters to be monitored in tracing of a single UE
– Uplink SIR: Selecting the counter starts monitoring of uplink Signal to Interference Ratio
(SIR) during tracing of a single UE. The counter is reported periodically. The period of
reporting the monitoring reports ranges from 0.1s to 60s.
– Uplink Tx Power: Selecting the counter starts monitoring of uplink transmit power
– Downlink BLER: Selecting the counter starts monitoring of Block Error Rate (BLER)
– Downlink Tx Code Power: Selecting the counter starts monitoring of downlink code
transmit power during tracing of a single UE. The counter is reported periodically. The
period of reporting the monitoring reports ranges from 0.1s to 60s.
– PCPICH Ec/No RSCP: Selecting the counter starts monitoring of PCPICH Ec/No and
Received Signal Code Power (RSCP) during tracing of a single UE. The counter is
reported periodically. The period of reporting the monitoring reports ranges from 0.1s to
60s.
– AMR Mode: Selecting the counter starts monitoring of AMR mode during tracing of a
single UE. The counter is reported periodically. If AMR mode changes, the current mode
is reported.
– RTWP(0.4s): Selecting the counter starts monitoring of received total wideband power
(RTWP) received for the cell serving the current UE. The counter is reported every 0.4
second.
– TRX Transmit Power(0.4s): Selecting the counter starts monitoring of downlink
transmit power transmitted for the cell serving the current UE. The counter is reported
every 0.4 second.

BSC6900 UMTS
----End
Result
Messages Offline.
Figure 7-14 Results of IOS message tracing
Follow-up Procedure
7.2.10 Location Report Control

This section describes how to trace the results of a location tracing initiated by the CN. You can
also perform this task to simulate CN-initiated location tracing and to trace the results of the
location tracing.

BSC6900 UMTS
Prerequisite
Context
Based on different settings, this task can simulate location tracing in different scenarios.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Location Report
Control. Accordingly, the Location Report Control dialog box is displayed, as shown in
Figure 7-15.
Figure 7-15 Location Report Control
Step 3 Set parameters in the Location Report Control dialog box.

BSC6900 UMTS
l IMSI: indicates the IMSI of the UE to be located.

l Location Report Control: After it is selected, you can simulate CN-initiated location tracing
by setting the parameters: Event, Report Area, Horizontal Accuracy Code, Interval, Vertical
Accuracy Code, Response Time Type, Locating Priority, and Client Type.
l Event: indicates the type of event to be traced.
l Report Area: indicates the type of area to be located.
l Horizontal Accuracy Code: indicates the horizontal accuracy requirement for the reported
result. The value ranges from 0 to 1800000.
l Interval: indicates the interval between two location requests. The value ranges from 0 to
1440 with the unit of 10s.
l Vertical Accuracy Code: indicates the vertical accuracy requirement for the reported result.
The value ranges from 0 to 990.
l Response Time Type: indicates the response time type of the location protection timer.
l Locating Priority: indicates the priority of the UE to be located.
l Client Type: indicates the type of service that requests location or purpose of requesting
location.
----End
Result
Messages Offline.
Figure 7-16 Results of Location Report Control
NOTE
l Right-click on the Location Monitor Info tab page, and then choose Save as Excel to save
the location results as an Excel file.
l The Location Time Delay Info tab page reflects the variation of the location delay in list
and in chart.
l Right-click in the chart on the Location Time Delay Info tab page, and then choose Set Y
axis display range to adjust the display range of the Y coordinate axis.

BSC6900 UMTS
Follow-up Procedure
7.3 Basic Tracing Operations

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

This describes how to browse the traced messages online, in the message browse window, after
the tracing task is created.
7.3.2 Viewing the Interpretation of the Trace Message
This section describes how to view the interpretation of a trace message.
7.3.3 Saving Traced Messages
This describes how to save the trace message file to the local computer.
7.3.4 Browsing Traced Messages Offline
This describes how to use the Traffic Recording Review Tool to browse offline, the traced
messages that are saved in .tmf format.
7.3.5 Managing Tracing Tasks
This section describes how to manage tracing tasks.
7.3.6 Managing the Trace File
This section describes how to query the trace files on the OMU and upload the trace files onto
the LMT PC as required.
7.3.7 Reference for Tracing Parameters
This section describes the tracing parameters for reference.
7.3.1 Browsing Traced Messages Online

This describes how to browse the traced messages online, in the message browse window, after
the tracing task is created.
Prerequisite
l A tracing task is successfully created.
l Traced messages are reported.
Procedure
Step 1 Browse or query the traced messages in the message browse window in real time. You can right-
click in the message browse window and then choose an item from the shortcut menu to perform
the associated operation as described in Table 7-1.

BSC6900 UMTS
Table 7-1 Operations available when browsing traced messages online

Shortcut Description
Stop Trace Task Suspend the task.
Restart Trace Task Resume the task.
Save All Messages... Save all trace messages.
Save Selected Messages... Save the selected trace messages.
Auto Scroll The messages in the window are automatically refreshed in

real time and are scrolled upward.
Clear Messages All the displayed messages are cleared from the browse
window without affecting the saving of the messages.
Property.... Query the task properties.
Step 2 To view the details of a message, double-click it. The Message Browser dialog box is displayed,
showing the details of the message.
----End
7.3.2 Viewing the Interpretation of the Trace Message

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

This describes how to save the trace message file to the local computer.
Prerequisite
l A tracing task is started.
Context
The length of the file name (including the extension) used for storing the tracing results cannot
exceed 100 characters.

BSC6900 UMTS
There are two ways of saving the trace results: auto saving and manual saving.
Procedure
l Automatically saving the trace messages
If Save File is selected when a tracing task is created, all messages displayed in the message
browse window are saved in .tmf format.
The default save path is C:\Web LMT\output\MBSC\trace\tmfFile on the LMT PC.
NOTE
l The LMT saves every 5,000 messages in a file, that is, it saves messages starting from 1 to 5,000
in one file, and so on. Note that the messages starting from 5,001 are saved in another file with
a serial number, wherein the serial number is increased by one for every 5,000 messages. For
example, the default save name of the traced 5001st to 10000th OS messages is OS_YYYY-
MM-DD-HH-MM-SS.tmf.
l You can use the Traffic Recording Review Tool to browse the messages saved in .tmf format
offline. For details, see 7.3.4 Browsing Traced Messages Offline.
l Manually saving the trace messages
When the tracing task is running, you can manually save all or part of the messages in the
message browse window in .tmf, .txt, or .csv format.
1. Right-click in the message browse window, and choose Save All Messages from the
shortcut menu. You can also select the messages to be saved in the message browse
window. Then, right-click the messages and choose Save Selected Messages from
the shortcut menu. The Save dialog box is displayed.
2. Enter a file name, and specify the file type and save path.
The default save path is C:\Web LMT\output\MBSC\trace\tmfFile. The default file

name is IP address_Trace type_YYYY-MM-DD-HH-MM-SS.tmf.
3. Click Save to save the file in the specified path.
----End
7.3.4 Browsing Traced Messages Offline

This describes how to use the Traffic Recording Review Tool to browse offline, the traced
messages that are saved in .tmf format.
Prerequisite
The traced messages are saved in .tmf format.
Context
You can find the .txt or .csv files in the save directory. You can double-click them to read the
traced messages.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Traffic Recording
Review Tool.

BSC6900 UMTS
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 Traffic
Recording Review Tool window.
NOTE
The time format is YYYY-MM-DD HH:MM:SS(Tick). The unit of Tick is 10 ms.
Step 4 Browser 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 Traffic Recording
Review Tool window.
If... Then...
You choose Save All Messages from the All the messages are saved in the window
shortcut menu, in .tmf or .txt format.
You choose Save Selected Messages from The selected messages are saved in .tmf or .txt
the shortcut menu, format.
You choose Filter from the shortcut menu, Set the filter to selectively display the
information.
You choose Filter By Column from the Filter the information by column to selectively
shortcut menu, display the information.
You choose Find from the shortcut menu, Locate the message that you want.
You choose Properties from the shortcut View the properties of the task that the tracing
menu, result corresponds to.
----End
7.3.5 Managing Tracing Tasks

This section describes how to manage tracing tasks.
Prerequisite
Procedure
1. Click Trace on the LMT main page. The Trace tab page is displayed.

BSC6900 UMTS
2. On the Trace Navigation Tree pane, expand the Trace node. Double-click Manage
Trace Task.
3. In the displayed Manage Trace Task tab page, set the parameters as required, and
click Query to query the information about the trace tasks.
4. To stop, restart, or delete a trace task, select the target task listed in the Result area,
and then click Stop, Restart, or Delete.
NOTE
l The tasks whose Trace Mode is Report listed in the query result can only be deleted on
the LMT where it was started.
l The tasks whose Create Type is Net Create listed in the query result are created by the
OMU according to the command from the BSC. Such tasks can only be deleted by the
admin or ADMINISTRATOR-level users.
1. Run the LST TRCRST command to query the trace tasks.
----End
7.3.6 Managing the Trace File

This section describes how to query the trace files on the OMU and upload the trace files onto
the LMT PC as required.
Prerequisite
Procedure
Step 2 On the Trace Navigation Tree pane, expand the Trace node. Double-click Manage Trace
File.
Step 3 In the displayed Manage Trace File tab page, set the parameters in the Search Configure area,
and then click Query to read the information about the trace files saved on the OMU.
Step 4 To upload a trace file to the LMT PC, select the target file listed in the Result area, set the
parameters in the Upload configure area, and then click Upload.
----End
7.3.7 Reference for Tracing Parameters

This section describes the tracing parameters for reference.

BSC6900 UMTS
Item Parameter Description
UMTS Trace Mode l Report

Services In this mode, the trace results are reported in real
time. The server sends the traced messages to the
LMT PC directly, and the output file is
automatically saved to the LMT PC in *.tmf format.
l Save to OMU
In this mode, you can set the trace interval. The
output file is automatically saved to the OMU in
*.tmf format.
MNCDT Band Indicator Indicates the band in which the ARFCN is used (DCS
Trace 1800 or PCS 1900).
UE Trace IMSI/IMEI/ These are used to identify the UE. You can choose to
TMSI/P-TMSI trace the UE by the IMSI, IMEI, TMSI, or P-TMSI.
l If you trace a UE by the TMSI, the Location Area
Code (LAC), Mobile Country Code (MCC), and
Mobile Network Code (MNC) are required.
l If you trace a UE by the P-TMSI, the LAC, Routing
Area Code (RAC), MCC, and MNC are required.
Cell Trace USER_VOLUME You can choose the events to be traced, including the
/ USER_VOLUME event or PROPAGATION_DE-
PROPAGATION LAY event. To trace the customized messages of UE
_DELAY statistical information, select USER_VOLUME. To
trace the propagation delay, select
PROPAGATION_DELAY.
SCCPCH ID This is used to specify the IDs of the SCCPCHs to be

traced. You can choose to trace two SCCPCHs at the
same time by specifying two SCCPCH IDs.

BSC6900 UMTS
LMT User Guide 8 Performance Monitoring
8 Performance Monitoring
About This Chapter
This chapter describes how to monitor the BSC6900 performance. A maximum of 64 monitoring
8.1 Concepts Related to Performance Monitoring

This section describes the concepts related to the BSC6900 performance monitoring: monitoring
principles and monitoring rights management.
8.2 Common Monitoring
This section describes the common performance monitoring.
8.3 UMTS Monitoring
This section describes the performance monitoring of the UMTS services.
8.4 General Operations of Performance Monitoring
This section describes the general operations applicable to all performance monitoring tasks
conducted on the BSC6900.
8.5 Reference for Performance Monitoring
This describes the parameters used for performance monitoring.

BSC6900 UMTS
8 Performance Monitoring LMT User Guide
8.1 Concepts Related to Performance Monitoring

This section describes the concepts related to the BSC6900 performance monitoring: monitoring
principles and monitoring rights management.
8.1.1 Monitoring Principles

This describes the principles of real-time performance monitoring, including the monitoring of
the CPU usage and other real-time performances.
8.1.2 Management of Monitoring Operation Rights
You must have the required rights to perform real-time monitoring operations on the
BSC6900.
8.1.1 Monitoring Principles

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

Figure 8-1 shows the principles of CPU usage monitoring.
Figure 8-1 CPU usage monitoring
The internal procedure of monitoring the CPU usage is as follows:
1. When you create a task for monitoring the CPU usage on the LMT, the LMT sends a binary
command querying the CPU usage to the maintenance module of the OMU periodically.
2. The OMU sends the corresponding command to the maintenance and configuration module
3. The board collects data according to the commands, and reports it to the OMU.
4. The OMU sends the data to the LMT.
Principle of Real-time Performance Monitoring

Figure 8-2 shows the principle of monitoring other real-time performances, which is similar to
the principle of message tracing.

BSC6900 UMTS
Figure 8-2 Real-time performance monitoring
The internal procedure for creating a real-time monitoring task, other than the CPU usage
monitoring, is as follows:
1. When you create a monitoring task on the LMT, the LMT sends a binary command to the
OMU to create the task.
2. The OMU assigns a number to the task and sends the command to the debugging module
3. After receiving the command, the debugging module records the filter parameters in the
filter table and notifies the service module.
4. The service module updates the local filter table according to the messages from the
debugging module.
The internal procedure for closing a monitoring task is as follows:
1. When you close the monitoring task on the LMT, the LMT sends a binary command to the
OMU to delete the task.
2. The OMU sends the command to the specified board according to the task number.
3. The debugging module and service module delete the task from the filter table.
The internal procedure for reporting the real-time monitoring data is as follows:
1. The service module compares the collected data against the local filter table and reports
the qualified messages to the OMU.
2. The OMU forwards the data to the LMT that creates the task according to the task ID.
3. The LMT displays the data in a chart or a list on the interface.
8.1.2 Management of Monitoring Operation Rights

You must have the required rights to perform real-time monitoring operations on the
BSC6900.
Operators of the following levels can perform the real-time performance monitoring tasks:
admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command
group G_10.
That is, except GUEST-level users and CUSTOM users that are not entitled to command group
G_10, all the other levels of users can perform the real-time monitoring.

BSC6900 UMTS
NOTE
Group G_10 consists of binary commands for creating tracing and monitoring tasks.
8.2 Common Monitoring

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

This section describes how to query the CPU/DSP usage of a board.
8.2.2 Monitoring Transmission Resources
This describes how to monitor the transmission resources on the Iub interface.
8.2.3 Monitoring BER Seconds
This describes how to detect the BER seconds on an E1/T1 port to monitor the transmission
quality of the link corresponding to the port. If any bit error occurs on the E1/T1 port, you can
start this task to obtain data such as BERS, critical BERS, unavailable seconds, frame errors,
CRC errors. Based on these data, you can evaluate the operating condition of the transmission
network and find out the causes for the bit errors in combination with the performance of the
peer end. The AEUa/PEUa/AOUc/POUc board supports this function.
8.2.4 Monitoring Link Performance
This section describes how to monitor the link performance. For the same monitoring item, you
can start a maximum of six tasks simultaneously.
8.2.1 Monitoring CPU/DSP Usage

This section describes how to query the CPU/DSP usage of a board.
Prerequisite
l The board under monitoring is functional.
Context
CAUTION
This operation affects the CPU usage. Therefore, if the CPU usage reaches 80% or higher, you
are advised to set the monitoring period to five seconds.
Procedure
Step 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > CPU/DSP
Usage Monitoring. The CPU/DSP Usage Monitoring dialog box is displayed.
Step 3 In the displayed CPU/DSP Usage Monitoring dialog box, set the parameters as required, and
click Submit.

BSC6900 UMTS
NOTE
After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring result
by list and chart. The task name and related parameters are displayed on the title bar of the window.
----End
8.2.2 Monitoring Transmission Resources

This describes how to monitor the transmission resources on the Iub interface.
Prerequisite
Procedure
Step 2 On the Monitor Navigation Tree pane, expand Monitor > Common Monitoring. Double-
click Transport Resource RealTime monitoring.
Step 3 In the 8.5 Reference for Performance Monitoring dialog box, set the parameters as required,
and click Submit.
NOTE
After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring
result by list and chart. The task name and related parameters are displayed on the title bar of the window.
----End
8.2.3 Monitoring BER Seconds

This describes how to detect the BER seconds on an E1/T1 port to monitor the transmission
quality of the link corresponding to the port. If any bit error occurs on the E1/T1 port, you can
start this task to obtain data such as BERS, critical BERS, unavailable seconds, frame errors,
CRC errors. Based on these data, you can evaluate the operating condition of the transmission
network and find out the causes for the bit errors in combination with the performance of the
peer end. The AEUa/PEUa/AOUc/POUc board supports this function.
Prerequisite
Procedure
click BERS Monitoring.
Step 3 In the displayed BERS Monitoring dialog box, set the parameters as required, and click
Submit.

BSC6900 UMTS
NOTE
result by list and chart. The task name and related parameters are displayed on the title bar of the window.
----End
8.2.4 Monitoring Link Performance

This section describes how to monitor the link performance. For the same monitoring item, you
can start a maximum of six tasks simultaneously.
Monitoring the IMA Group Traffic

This section describes how to monitor the traffic on a specified IMA group in real time. The
real-time traffic on the specified IMA group is displayed in the form of list and chart. Based on
the statistics from the two ends of the IMA group, you can confirm the IE loss, locate the fault,
and evaluate the network transmission quality. You can also compare the actual traffic volume
with the user volume and obtain the utilization of the port. In addition, you can evaluate the
bandwidth condition and decide whether to add a link to the IMA group for capacity expansion.
Prerequisite
Context
CAUTION
The IMA group must be successfully set up and connected to the peer end before this task is
performed. This task is stopped if the monitored IMA group is deleted.
Procedure
click Link Performance Monitoring.
Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to 8.5 Reference
for Performance Monitoring. Set other parameters as required, and then click Submit.
NOTE
result in the form of list and chart. The task name and related parameters are displayed on the title bar of
the window.
In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate represents
the RX and TX traffic in bit/s.
----End

BSC6900 UMTS
Monitoring the UNI Link Traffic

This section describes how to monitor the traffic on a specified UNI link in real time. The real-
time traffic on the specified UNI link is displayed in the form of list and chart. Based on the
statistics from the two ends of the UNI link, you can confirm the IE loss, locate the fault, and
evaluate the network transmission quality. You can also compare the actual traffic volume with
the user volume and obtain the utilization of the port. In addition, you can evaluate the bandwidth
condition and decide whether to modify the UNI to IMA.
Prerequisite
Context
CAUTION
The UNI link must be successfully set up and connected to the peer end before this task is
performed. This task is stopped if the monitored link is deleted.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to 8.5 Reference for
Performance Monitoring. Set other parameters as required, and then click Submit.
NOTE
the window.
----End
Monitoring the Fractional ATM Link Traffic

This section describes how to monitor the traffic on a specified fractional ATM link in real time.
The real-time traffic on the specified fractional ATM link is displayed in the form of list and
chart. Based on statistics obtained from two ends of the fractional ATM link, you can confirm
the IE loss, locate the fault, and evaluate the network transmission quality. You can also compare
the actual traffic volume with the user volume carried by the current port and obtain the utilization
of the port. In addition, you can evaluate the bandwidth condition and decide whether to modify
the FRAC ATM to IMA to expand the bandwidth.
Prerequisite

BSC6900 UMTS
Context
CAUTION
The FRAC ATM link must be successfully set up and connected to the peer end before this task
is performed. This task is stopped if the monitored link is deleted.
Procedure
NOTE
After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results
in list and chart. The task name and related parameters are indicated in the title bar of the window.
----End
Monitoring the SAAL Link Traffic

This describes how to monitor the traffic on a specified SAAL path at the IP layer of the interface
board in real time. The real-time traffic on the specified SAAL path is displayed in the form of
list and chart. Based on the transmit/receive statistics on the SAAL of the CPUS subsystem, you
can confirm the packet loss, locate the SAAL disconnection or intermittence problem. You can
also predict the congestion by comparing the traffic with the configured bandwidth.
Prerequisite
Context
CAUTION
The SAAL must be successfully set up and connected to the peer end before this task is
Procedure

BSC6900 UMTS
NOTE
----End
Monitoring the IPoA PVC Traffic

This section describes how to monitor the traffic on a specified IPOA PVC at the IP layer of an
interface board in real time. The real-time traffic on the specified IPOA PVC is displayed in the
form of list and chart. If the IPOA PVC carries the OML for the ATM-based BTS, you can
perform this task to observe the traffic and bandwidth utilization when the NodeB is loading
data and to locate the fault in the NodeB startup and data loading processes. If the IPOA PVC
carries the IP path over the Iu-PS interface, you can perform this function to observe the traffic
flow and locate the connection and congestion status of the upper layer link.
Prerequisite
Context
CAUTION
The IPoA PVC must be successfully set up and connected to the peer end before this task is
Procedure
NOTE
----End

BSC6900 UMTS
Monitoring the AAL2 Path Traffic

This section describes how to monitor the traffic on a specified AAL2 path at the IP layer of the
interface board in real time. The real-time traffic on the specified AAL2 path is displayed in the
form of list and chart. Based on the layer 2 transmit/receive statistics obtained from the CDT
trace, you can confirm the packet loss and evaluate the traffic condition. In addition, you can
predict the congestion based on the traffic conditions on the link.
Prerequisite
Context
CAUTION
The AAL2 path must be successfully set up and connected to the peer end before this task is
Procedure
NOTE
----End
Monitoring FE/GE Traffic

This section describes how to monitor the traffic on a specified FE/GE port in real time. The
real-time traffic on the specified FE/GE port is displayed in the form of list and chart. Based on
the traffic carried by the FE/GE port, you can confirm the packet loss, locate the fault, and
evaluate the network transmission quality. You can also compare the actual traffic volume with
the user volume carried by the current port and obtain the utilization of the port. In addition, you
can evaluate the bandwidth condition and decide whether to swap the services to avoid
congestion.
Prerequisite

BSC6900 UMTS
Context
CAUTION
The FE/GE port must be successfully configured and connected to the peer end before this task
is performed. This task is stopped if the monitored link is deleted.
Procedure
NOTE
the window.
----End
Monitoring the PPP Link Traffic

This section describes how to monitor the traffic on a specified PPP link in real time. The real-
time traffic on the specified PPP link is displayed in the form of list and chart. This task can be
performed to achieve the following functions by comparing the statistics from the two ends of
the PPP link: to confirm the packet loss, locate the fault, and evaluate the network transmission
quality; to compare the total traffic with the traffic carried by the current port and obtain the
utilization of the port; and to check the bandwidth condition based on which the user can decide
whether to expand the bandwidth or modify the PPP to MLPPP.
Prerequisite
Context
CAUTION
The PPP link must be successfully set up and connected to the peer end before this task is

BSC6900 UMTS
Procedure
NOTE
the window.
----End
Monitoring Traffic on the MLPPP Link Group

This describes how to monitor the traffic on a specified MLPPP link group in real time. The
real-time traffic on the specified MLPPP link group is displayed in the form of list and chart.
Based on the statistics from the two ends of the MLPPP link, you can confirm the packet loss,
locate the fault, and evaluate the transmission network quality. You can also compare the actual
traffic volume with the user volume carried by the current port and obtain the utilization of the
port. In addition, you can evaluate the bandwidth condition and decide whether to add a link to
expand the bandwidth.
Prerequisite
Context
CAUTION
The MLPPP group must be successfully configured and connected to the peer end before this
task is performed. This task is stopped if the monitored MLPPP link group is deleted.
Procedure

BSC6900 UMTS
NOTE
the window.
----End
Monitoring the SCTP Link Traffic

This describes how to monitor the traffic on a specified SCTP path at the IP layer of the interface
board in real time. The real-time traffic on the specified SCTP path is displayed in the form of
list and chart. Based on the transmit/receive statistics on the SCTP of the CPUS subsystem, you
can confirm the packet loss, locate the SCTP disconnection or intermittence problem. In addition,
you can predict the congestion based on the traffic conditions on the link.
Prerequisite
Context
CAUTION
The SCTP link must be successfully set up and connected to the peer end before this task is
Procedure
NOTE
the window.
the RX and TX traffic in kbit/s.
----End
Monitoring the IP Path Traffic

This describes how to monitor the traffic on a specified IP path at the IP layer of the interface
board in real time. The real-time traffic on the specified IP path is displayed in the form of list
and chart. Based on the layer 2 statistics obtained from the CDT trace, you can confirm the

BSC6900 UMTS
packet loss and evaluate the user data flow conditions. In addition, you can predict the congestion
based on the traffic conditions on the link.
Prerequisite
Context
CAUTION
The IP path must be successfully set up and connected to the peer end before this task is
Procedure
NOTE
----End
Monitoring Traffic on a Logical Port

This section describes how to monitor the traffic on a specified logical port. You can monitor
an entire port, where the monitoring result displays the real-time traffic of the current logical
port. You can also monitor only the specified priority of the port, where the monitoring result
displays the TX traffic of the specified priority of the current logical port. Based on the traffic
statistics at the logical port, you can confirm the packet loss at the logical port and locate the
fault. You can also compare the actual traffic volume with the user volume and obtain the
utilization of the port. In addition, you can evaluate the bandwidth condition and decide whether
to expand the configuration bandwidth of the logical port.
Prerequisite
Procedure

BSC6900 UMTS
NOTE
the window.
the real-time traffic of the current logical port in bit/s.
----End
Monitoring OAM Traffic

This section describes how to monitor the RX and TX traffic on the operation and maintenance
(OAM) channel at the IP layer of an interface board in a specified NodeB. The OAM traffic on
the current NodeB is displayed in the form of list and chart. You can perform this task to observe
the traffic and bandwidth usage when the NodeB is loading data. Thus, you can locate the fault
in the NodeB startup and data loading processes.
Prerequisite
l The LMT is running normally.
Procedure
NOTE
the window.
the RX and TX traffic of the NodeB OM channel in bit/s.
----End
Monitoring the Bandwidth of a Logical Port

This section describes how to monitor the bandwidth changes on a logical port after the dynamic
bandwidth adjustment. The bandwidth on the specified logical port is displayed in the form of
list and chart. The IP PM function is supported so that you can observe the dynamic bandwidth
changes. In this way, you can judge the bandwidth adjustment performance based on the traffic
volume.

BSC6900 UMTS
Prerequisite
Procedure
Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to 8.5 Reference
for Performance Monitoring. Set other parameters as required, and then click Submit.
NOTE
the window.
the bandwidth in bit/s.
----End
8.3 UMTS Monitoring

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

This section describes how to monitor the performance of the physical connections of the UE
during a conversation. A maximum of six monitoring tasks can be performed simultaneously
for each monitoring item.
8.3.2 Monitoring Cell Performance
This section describes how to monitor the cell performance, such as the common measurement
statistics and number of UEs on the common channel. For the same monitoring item, you can
start a maximum of six tasks simultaneously.
8.3.3 Monitoring Board Resources
This section describes how to monitor the licensed Erlang value and the PS user plane throughput
of a specified board in real time.
8.3.1 Monitoring Connection Performance

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

This section describes how to monitor in real time the P-CPICH Ec/No and RSCP of a cell in
the active set. The monitoring result, including the number of cells in the active set and the signal
strength of each cell, is displayed in a chart. By performing this task, you can learn about whether
the current connection is at the edge or the center of the cell.

BSC6900 UMTS
Prerequisite
Context
CAUTION
Before running this monitoring task, you need to perform one of the following operations:
l Run SET UCORRMALGOSWITCH to set Handover algorithm switch. Ensure that
SOFT_HANDOVER_SWITCH is selected.
l Run MOD UCELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE.
NOTE
l This task applies to only monitoring connections established on dedicated channels. An ongoing task
is stopped if the monitored connection is released or transited from the dedicated channel to the common
channel. The task is restarted if the monitored connection is transited from the common channel back
to the dedicated channel.
l This task is performed to monitor only the real-time data of the cells in the active set. The data of other
cells is not reported. Therefore, the monitoring results reflect the variation of the number of cells in
the active set in real time.
l A maximum number of three cells in the active set can be monitored in each task.
Procedure
Step 2 On the Monitor Navigation Tree pane, expand Monitor > UMTS Monitoring. Double-click
Connection Performance Monitoring.
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to P-
CPICH Ec/No and RSCP. Set other parameters as required, and then click Submit.
NOTE
A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart.
The task name is indicated in the title bar of the window.
In the chart, the X-coordinate represents the time. If the reporting period is less than 10s, the time unit is
RFN (1 RFN = 10 ms). If the reporting period is not less than 10s, the time unit is TICK (1 TICK = 10 ms).
The Y-coordinate represents the reported P-CPICH Ec/No (unit: dB) and RSCP (unit: dBm).
l RSCP stands for Received Signal Code Power. It is the received power on one code measured on the
P-CPICH. The reference point for measurement of the RSCP is at the antenna connector of the 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. Then you can obtain the total RSCP of the P-CPICH.
l Ec/No refers to the ratio of received energy per chip to noise spectral density. Like RSCP/RSSI, Ec/
No is also measured on the P-CPICH. The reference point for measurement is also at the antenna
connector of the UE. If the P-CPICH adopts transmit diversity, the total Ec value of all antennas must
be measured to calculate the Ec/No.
----End

BSC6900 UMTS
Monitoring SIR of the Uplink RLS

This section describes how to monitor in real time the SIR values of the uplink radio link sets
(RLSs) used by the UE. By performing this task, you can learn about the uplink radio link quality
and the quality variations.
Prerequisite
Context
NOTE
Each task can monitor only one UE. The monitoring result includes the number of cells in the active set
and the signal strength of each cell. From the monitoring result, you can know whether the current
connection is at the edge or the center of the cell.
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to UL
SIR. Set other parameters as required, and then click Submit.
NOTE
The task name is indicated in the title bar of the window. The monitoring results reflect the variation of
the number of the RLSs in real time.
The Y-coordinate represents the reported SIR of the UL RLSs (unit: dB).
The calculation formula of SIR is (RSCP/ISCP) x SF, where:
l RSCP stands for Received Signal Code Power. It is the received power on one code.
l ISCP stands for Interference Signal Code Power. Only the non-orthogonal part of received interference
signals is measured.
l SF stands for the spreading factor of the DPCCH.
The measurement is performed on the DPCCH selected after radio links are combined on the NodeB. In
compressed mode, the SIR during the transmit intervals is not measured. The NodeB reports the measured
SIR values on the uplink to the BSC6900.
----End
Monitoring the Enhanced Outer Loop Power Control

This section describes how to monitor the enhanced outer loop power control. The following
items are monitored: the target UL RLS SIR, BER of the UL physical channel, BER filter values
of the UL transport channel, BLER of the UL transport channel, E-DCH average times of
retransmission, and E-DCH retransmission probability.
Prerequisite

BSC6900 UMTS
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to
OLPC. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the time. The time unit is RFN (1 RFN = 10 ms). Two small charts
are respectively used to describe the five monitoring items.
l The first small chart shows the output interface of the SIR target values of the UL RLSs, BLER of the
UL transport channel, and BER of the UL physical channel. The left Y-coordinate represents the SIR
target values of the UL RLSs (range: -10 to 18, unit: dB). The right Y-coordinate represents the BLER
of the UL transport channel (range: 0 to 1, unit: BLER) and BER of the UL physical channel (range:
0 to 1, unit: BER).
l The second small chart shows the output interface of the E-DCH average times of retransmission and
E-DCH retransmission probability. The left Y-coordinate represents the E-DCH average times of
retransmission (range: 0 to 16, unit: none). The right Y-coordinate represents the E-DCH retransmission
probability (range: 0 to 1, unit: none).
----End
Monitoring the SIR Error Values of UL RLSs

This task is performed to monitor the real-time SIR error values of radio link sets (RLSs) of the
current connection. By performing this task, you can observe whether the SIR can keep up with
the variation of the target values and estimate the UL inner loop power control function. If the
SIR error values vary all the time but converge around 0 dB, you can infer that the UL inner
loop power control converges. Otherwise, the UL inner loop power control does not converge.
Prerequisite
Context
This task applies to only monitoring connections established on dedicated channels. An ongoing
task is stopped if the monitored connection is released or transited from the dedicated channel
to the common channel. The task is restarted if the monitored connection is transited from the
common channel back to the dedicated channel.
Procedure
SIR Error. Set other parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
the number of the RLSs in real time.
The Y-coordinate represents the reported SIR error values (SIRerror) of the UL RLSs.
l SIRerror (unit: dB) is reported to the BSC6900 by the NodeB. The calculation formula is SIRerror = SIR
- SIRtarget_ave.
l Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to the time for
calculating the SIR in the above formula of SIRerror.
l In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave in the transmission gap is not
calculated. The average of SIRtarget is an arithmetical average. The unit of SIRtarget_ave is dB.
----End
Monitoring DL Code TX Power

This section describes how to monitor the variation of the DL code TX power of each radio link
of the current connection in real time. By performing this task, you can analyze the DL power
consumption. If the DL code TX power increases, even approximately up to the maximum value
configured in the signaling message, it indicates that the link experiences a degraded quality.
Prerequisite
Context
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to DL
Tx Code Power. Set other parameters as required, and then click Submit.

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

This section describes how to monitor in real time the variation of the UE TX power on the
current connection. By performing this task, you can analyze the UL quality of the radio link.
If the UE TX power increases, even reaching the limit of the UE capability, you can infer that
the radio link experiences a degraded UL quality.
Prerequisite
Context
UE TX power refers to the UE TX power in a carrier. The reference point for measurement of
the UE TX power is at the antenna connector of the UE.
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to UE
Tx Power. Set other parameters as required, and then click Submit.
NOTE
The Y-coordinate represents the reported UE TX power (unit: dBm).
----End

BSC6900 UMTS
Monitoring UL Traffic
This task is performed to monitor in real time the variation in the UL traffic (that is, the buffered
data volume at the UE side) on the current connection. By performing this task, you can analyze
the transmission performance of UL traffic. The UL traffic is measured by the UE and reported
to the BSC6900 on the basis of the transport channel.
Prerequisite
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be
transmitted or retransmitted from the RLC entity on each logical channel. If RLC is in AM mode,
the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmit
window, excluding the PDUs for which no ACK is received.
This task can monitor the connections of PS domain interactive and background services on both
common channels and dedicated channels.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL Traffic. Set
other parameters as required, and then click Submit.
NOTE
The Y-coordinate represents the reported UL traffic on the UL physical channel (unit: byte).
----End
Monitoring DL Traffic
This task is performed to monitor in real time the variation in the DL traffic (that is, the buffered
data volume on the MSC side) on the current connection. By performing this task, you can
analyze the transmission performance of DL traffic. The DL traffic is measured at the
BSC6900 on the basis of transport channel.
Prerequisite
Context
Traffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to be
transmitted or retransmitted from the RLC entity on each logical channel. If RLC is in

BSC6900 UMTS
acknowledgment mode, the BO value includes the control Protocol Data Unit (PDU) and the
PDU outside the transmit window, excluding the PDUs for which no ACK is received.
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Traffic. Set
NOTE
The Y-coordinate represents the reported DL traffic (unit: byte).
----End
Monitoring UL Throughput and Bandwidth

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

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

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

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

This section describes how to monitor the handover delay performance. By performing this task,
you can observe and obtain the time taken by each handover (including the intra-frequency
handover and inter-frequency handover) of the current connection.
Prerequisite
Context
Handover delay refers to the period during which the BSC6900 receives a measurement report,
the handover decision is made, the handover is initiated, and the handover is completed.
At most five handover delay monitoring tasks can be started simultaneously. This task can
monitor only intra-frequency handover and inter-frequency handover but cannot monitor inter-
RAT handover.
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to
Handover Delay. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y-coordinate represents
the interval of each successful handover (unit: ms).
----End

BSC6900 UMTS
Monitoring the BLER of the DL Transport Channel

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

This section describes how to monitor in real time the variation in the configured AMR rate.
Prerequisite
Context
The monitoring is valid only when the traced UE has an AMR service in process.
The narrowband AMR has eight available rates, that is, eight available modes: 12.2 kbit/s, 10.2
kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.

BSC6900 UMTS
The wideband AMR has nine available rates, that is, nine available modes: 23.85 kbit/s, 23.05
kbit/s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.60
kbit/s.
Procedure
Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to AMR
Mode. Set other parameters as required, and then click Submit.
NOTE
In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y-coordinate represents
the maximum AMR rate in the uplink and downlink (unit: kbit/s).
----End
8.3.2 Monitoring Cell Performance

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

The monitoring is performed on the PCPICH TX power of a specified cell. By performing this
task, you can observe and judge in real time whether the pilot power is normal.
Prerequisite
Context
The value range of the P-CPICH TX power can be obtained by running the LST UPCPICH
command. If the pilot power is outside the range, you can infer that the power is abnormal.
Procedure
Cell Performance Monitoring.
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to PCPICH
TxPower. Set other parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
In the chart, the X-coordinate represents the time. If the reporting period is not greater than 10s, the time
unit is RFN (1 RFN = 10 ms). If the reporting period is greater than 10s, the time unit is TICK (1 TICK =
10 ms). The Y-coordinate represents the P-CPICH power (unit: dBm).
----End
Monitoring UL RX Total Wideband Power of a Cell

This section describes how to monitor the UL RX total wideband power (RTWP) in a specified
cell. By performing this task, you can observe the UL load level in real time. The UL RX total
wideband power is measured and reported by the related NodeB.
Prerequisite
Context
The CAC procedure measures the UL load by the UL load factor (UL load factor = 1 - cell
background noise/UL RX total wideband power). The background noise of the cell approximates
to a constant, which can be set through the command ADD UCELLCAC or MOD
UCELLCAC. Therefore, the UL RX total wideband power can also be used to measure the
relative level of the UL load of the cell.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to RTWP. Set
NOTE
unit is RFN (1 RFN = 10 ms). Otherwise, the time unit is TICK (1 TICK = 10 ms). The Y-coordinate
represents the cell UL RX total wideband power (unit: dBm).
----End
Monitoring DL TX Power in a Cell

This section describes how to monitor the DL transmit (TX) power of a specified cell. By
performing this task, you can observe the DL load level in real time. The DL TX power of a cell
is measured and reported by the related NodeB.
Prerequisite

BSC6900 UMTS
Context
The CAC procedure uses the ratio of the DL carrier TX power to the maximum TX power of
the cell to measure the DL load of the cell. When setting up a cell, you can run ADD
UCELLSETUP to set the maximum TX power. After the cell is set up, you can run MOD
UCELL to modify it.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell DL
Carrier TX Power. Set other parameters as required, and then click Submit.
NOTE
represents the ratio of the DL TX carrier power to the maximum TX power of the cell (unit: %).
----End
Monitoring User Volume in Cell

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

BSC6900 UMTS
Monitoring Node Synchronization

This section describes how to monitor the time difference between RNC Frame Number (RFN)
and NodeB Frame Number (BFN) of the specified cell and the time taken for node
synchronization. By performing this task, you can observe the float between the RFN and BFN
in real time. If the difference between RFN and BFN varies too rapidly, you can infer that there
are some problems on the transmission between the BSC6900 and the NodeB.
Prerequisite
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Node Sync.
Set other parameters as required, and then click Submit.
NOTE
In the chart, the X-coordinate represents the time. The time unit is TICK (1 TICK = 10 ms). The Y-
coordinate represents the time difference between RFN and BFN and the time taken by the NodeB to finish
node synchronization (unit: ms).
----End
Monitoring UL CAC
This section describes how to monitor the UL Call Admission Control (CAC) procedure of a
specified cell. By performing this task, you can observe the variation in the predicted values and
measured values of the UL load and judge the prediction accuracy of the UL CAC algorithm.
Prerequisite
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC
algorithm 2). Run MOD UCELLALGOSWITCH to set the UL CAC algorithm of a cell. Run
LST UCELLALGOSWITCH to query the UL CAC algorithm of a cell.
l CAC algorithm 1 measures the UL load by the UL load factor (UL load factor = 1 - cell
background noise/UL RX total wideband power). You can run the command ADD
UCELLCAC or MOD UCELLCAC to set the cell background noise.
l CAC algorithm 2 uses the ratio of the current number to the maximum number of UL
equivalent users to measure the load of the cell. By default, algorithm 2 is used to measure
the UL load of the cell.

BSC6900 UMTS
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to UL CAC. Set
NOTE
unit is RFN (1 RFN = 10 ms). If the reporting period is greater than 10s, the time unit is TICK (1 TICK =
10 ms). The Y-coordinate represents the predicted values and measured values of the load (unit: %).
----End
Monitoring DL CAC
This section describes how to monitor the DL Call Admission Control (CAC) procedure of a
specified cell. By performing this task, you can observe the variation of the predicted values and
measured values of the DL load and judge the prediction accuracy of the DL CAC algorithm.
Prerequisite
Context
The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CAC
algorithm 2). Run MOD UCELLALGOSWITCH to set the UL CAC algorithm of a cell. Run
LST UCELLALGOSWITCH to query the UL CAC algorithm of a cell.
l CAC algorithm 1 uses the ratio of the DL carrier TX power to the maximum TX power of
the cell to measure the DL load of the cell. By default, algorithm 1 is used to measure the
DL load of the cell. The maximum TX power is a constant. You can run ADD
UCELLSETUP to set it.
l CAC algorithm 2 uses the ratio of the current DL equivalent number of users to the
maximum DL equivalent number of users.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL CAC. Set

BSC6900 UMTS
NOTE
represents the predicted values and measured values of the load (unit: %).
----End
Monitoring the Number of UL Equivalent Users

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

This section describes how to monitor the number of DL equivalent users in a specified cell. By
performing this task, you can observe the variation in the number of DL equivalent users.
Prerequisite
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL Total
Equivalent User Number. Set other parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
represents the predicted values and measured values of the number of DL equivalent users.
----End
Monitoring the Cell Code Tree

This section describes how to monitor the DL channel OVSF code tree of a specified cell. By
performing this task, you can observe the code usage in real time.
Prerequisite
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell Code
Tree. Set other parameters as required, and then click Submit.
NOTE
A monitoring window is displayed, showing the real-time monitoring results in chart. The task name is
indicated in the title bar of the window.
represents the codes.
----End
Monitoring the Minimum Required Power of the HS-DSCH

This section describes how to monitor in real time the minimum required power of the HS-DSCH
of a specified cell. By performing this task, you can observe the ratio of the minimum required
power to the maximum TX power on the HS-DSCH in the cell.
Prerequisite
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Min Power Requirement. Set other parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
represents the ratio of the required power to the maximum TX power of the cell (unit: ‰).
----End
Monitoring the Bit Rate Provided by the HS-DSCH

This section describes how to monitor the bit rate on the HS-DSCH of a specified cell. By
performing this task, you can observe the variation in the transmission rate on the HS-DSCH in
real time.
Prerequisite
Context
NOTE
Before performing the bit rate monitoring on the HS-DSCH, ensure that the HSDPA_PBR_MEAS of the
cell is selected (that is, set to 1). Otherwise, "Measurement not available" is displayed when you create the
measurement task.
Run the LST UCELLALGOSWITCH command on the MML client to query the state of
HSDPA_PBR_MEAS switch. If the queried result is HSDPA PBR MEAS ALGORITHM:OFF, run the
MOD UCELLALGOSWITCH command to set it to 1.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCH
Provide Bitrate. Set other parameters as required, and then click Submit.
NOTE
represents the bit rate (unit: bit/s).
----End
Monitoring the Bit Rate Provided by the E-DCH

This section describes how to monitor the bit rate on the enhanced dedicated channel (E-DCH)
for HSUPA services. By performing this task, you can observe the variation in the transmission
rate on the E-DCH in real time.

BSC6900 UMTS
Prerequisite
Context
NOTE
Before performing the bit rate monitoring on the E-DCH, ensure that the HSDPA_PBR_MEAS of the cell
is switched on (that is, set to 1). Otherwise, "Measurement not available" is displayed when you create the
measurement task.
Run the LST UCELLALGOSWITCH command query the state of HSUPA_PBR_MEAS switch. If the
queried result is HSUPA PBR MEAS ALGORITHM:OFF, run the MOD UCELLALGOSWITCH
command to set it to 1.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to E-DCH
Provide Bitrate. Set other parameters as required, and then click Submit.
NOTE
represents the bit rate (unit: bit/s).
----End
Monitoring UL Throughput of a Cell

This section describes how to monitor the UL throughput of a cell. Throughput refers to the
maximum traffic rate that an entity can endure without discarding the frames.
Prerequisite
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell UL
Throughput. Set other parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
represents the UL throughput of the cell.
----End
Monitoring DL Throughput of a Cell

This section describes how to monitor the DL throughput of a cell. Throughput refers to the
maximum traffic rate that an entity can endure without discarding the frames.
Prerequisite
Procedure
Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell DL
Throughput. Set other parameters as required, and then click Submit.
NOTE
represents the DL throughput of the cell.
----End
Monitoring Cell CE
This section describes how to monitor the channel element (CE) conditions of the local cell, the
local cell group, and the corresponding NodeB. Based on the monitoring result, the BSC6900
determines whether a UE can access the network.
Prerequisite
Procedure
Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell CE. Set other
parameters as required, and then click Submit.

BSC6900 UMTS
NOTE
represents the number of CEs of the cell.
----End
Monitoring the FDPCH SYMBOL

This section describes how to monitor the condition of the F-DPCH SYMBOL, including the
F-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.
Prerequisite
Context
The F-DPCH carries the Transport Power Control (TPC) information of HSDPA services and
uses the spreading factor SF256.
Procedure
Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to FDPCH
SYMBOL. Set other parameters as required, and then click Submit.
NOTE
A monitoring window is displayed, showing the real-time monitoring results in chart. The task name is
indicated in the title bar of the window.
l In the static view of the FDPCH SYMBOL monitoring, you can view the condition of the SYMBOL
corresponding to the F-DPCH code. The numbers in the grids indicate the timeslot formats.
l In the dynamic view of the FDPCH SYMBOL monitoring, the X-coordinate represents the time, and
the Y-coordinate represents the F-DPCH code, position of the F-DPCH SYMBOL, and timeslot format.
----End
8.3.3 Monitoring Board Resources

This section describes how to monitor the licensed Erlang value and the PS user plane throughput
of a specified board in real time.
Prerequisite

BSC6900 UMTS
Context
NOTE
l This task can be performed only through menu operations and applies to only the boards that are in
position and running properly.
l This function supports the monitoring of the SPUa board only.
Procedure
Board Resource Monitoring.
Step 3 In the Board Resource Monitoring dialog box, set the parameters as required, and click
Submit.
NOTE
the window.
the RX and TX traffic in kbit/s.
----End
8.4 General Operations of Performance Monitoring

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

This describes how to browse online and query the monitoring results that are dynamically
displayed in the monitoring window in real time.
8.4.2 Setting the Display Mode of the Chart
This section describes how to set the display mode of the chart in the real-time monitoring
window after a monitoring task is started. Below the Chart tab page in the window, you can set
the display properties such as the line color, line type, and line width.
8.4.3 Saving Monitoring Results
This section describes how to save the monitoring results to local files.
8.4.4 Browsing Monitoring Results Offline
This section describes how to browse the monitoring results of the CPU usage and BER
seconds in offline mode.
8.4.1 Browsing the Monitoring Results Online

This describes how to browse online and query the monitoring results that are dynamically
displayed in the monitoring window in real time.

BSC6900 UMTS
Prerequisite
l A performance monitoring task is started.
l Monitoring results are reported.
Procedure
l Right-click on the Chart tab page in the real-time performance monitoring window. Then,
you can perform the following operations by selecting the corresponding item from the
shortcut menu:
– Setting auto scroll
– Showing or hiding the grid
– Switching the display mode
– Setting the display range of the Y axis
l Right-click on the List tab page in the real-time performance monitoring window. Then,
you can perform the following operations by selecting the corresponding item from the
shortcut menu:
Setting auto scroll
l Right-click on the task information pane at the bottom of the real-time performance
monitoring window. Then, you can perform the following operations by selecting the
corresponding item from the shortcut menu:
– Adding or deleting tasks
– Stopping or restarting tasks
– Querying details of tasks
----End
8.4.2 Setting the Display Mode of the Chart

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

BSC6900 UMTS
8.4.3 Saving Monitoring Results

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

This section describes how to browse the monitoring results of the CPU usage and BER
seconds in offline mode.
Prerequisite
The monitoring results are saved to files.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Traffic Recording
Review Tool.
Step 2 Open the directory where the monitoring results are saved. The default save path is C:\Web LMT
\output\MBSC\monitor. Select the result file corresponding to the monitoring task.
Step 3 Click Open or double-click the file. The Traffic Recording Review Tool window is displayed,
providing the monitoring results in chart and list.
Step 4 Click the List tab or the Chart tab to view the data in different modes.
Step 5 To view other saved results, choose File > Open. In the Open dialog box, select the target files
to read the details.
----End
8.5 Reference for Performance Monitoring

This describes the parameters used for performance monitoring.
Monitor Item Parameter Description
Transport Resource IP Logic Port Indicates the number of the IP logical port. To
RealTime Monitoring query the number of the IP logical port, run
the LST IPLOGICPORT command.

BSC6900 UMTS
Link IMA Group IMA Group Indicates the number of the IMA group. To
Performanc No. query the IMA group, run the LST
e IMAGRP command.
Monitoring
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 Indicates the number of the fractional ATM

ATM Link No. 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 Indicates the number of the SAAL link. To
No. query the SAAL link, run the LST
SAALLNK command.
IPoA PVC IP Address Indicates the local and peer IP addresses of the
Ping Peer IP IPoA PCV. To query these IP addresses, run
Address the 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 Indicates the number of the FE/GE port. To

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

Group No. query the number of the MLPPP group, run
the LST MPGRP command.
SCTP Link SCTP Link No. Indicates the number of the SCTP link. To
query the SCTP link, run the LST
SCTPLNK command.
IP Path Adjacent Node Indicates the number of the adjacent node of

ID the IP path. To query the adjacent node of the
IP PATH IP path, run the LST IPPATH command.
Symbol
Logical Port No. Indicates the number of a logical port. To

Port query the ATM logical port, run the LST
ATMLOGICPORT command.To query the
IP logical port, run the LST
IPLOGICPORT command.

BSC6900 UMTS
OAM NodeB ID Indicates the NodeB ID. To query the NodeB

ID, run the LST UNODEB command.
Logical Logical Port Indicates the number of a logical port. To

Port No. query the ATM logical port, run the LST
Bandwidth ATMLOGICPORT command.To query the
IP logical port, run the LST
IPLOGICPORT command.
FE/GE Priority Group Indicates the priority queue number. (value

PPP Link No. range: 0-5).
MLPPP
Group
Logical
Port

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

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

BSC6900 UMTS
9 Device Panel LMT User Guide
9.1 Device Panel Operations

This section describes the operations of the BSC6900 device panel, including how to start and
use it and how to query the status of the boards.
9.1.1 Introduction to the Device Panel
In addition to MML commands, the LMT also provides the graphical device panel to facilitate
device maintenance.
9.1.2 Starting the Device Panel
This section describes how to start the device panel.
9.1.3 Querying the Status of an E1/T1 Port
This describes how to query the status of an E1/T1 port.
9.1.4 Querying the CPU Usage
This describes how to query the CPU usage of a board.
9.1.5 Querying the BSC Board Information
This describes how to query the status of a BSC board.
9.1.6 Resetting the BSC Board
This describes how to reset the BSC board, the CPU on the XPUa board, and the DSP on the
DPU board. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users
9.1.7 Switching Over the BSC Boards
This describes how to switch over the active BSC board and the standby BSC board. When the
active board is faulty, you can switch all the services over to the standby board to ensure the
normal operation of the system. Only the admin, ADMINISTRATOR-level, and authorized
9.1.1 Introduction to the Device Panel

In addition to MML commands, the LMT also provides the graphical device panel to facilitate
device maintenance.
The device panel is automatically refreshed, showing board status in real time through the board
colors and alarm indicators on the board.
On the device panel, you can right-click a board in position and choose operations from the
shortcut menu. For example, you can query the board status. Figure 9-1 shows the device panel.
Figure 9-1 Device Panel

BSC6900 UMTS
The alarm indicators represent the alarm status of a board, and the board colors indicate the
running status of the board. See the color descriptions shown on the right of the device panel for
the specific meanings of the alarm indicators and board colors.
l If the tab page under Device Maintenance is not in full view, click . The drop-down list
is displayed. Choose the required menu to display the corresponding tab page.
l Right-click the peripheral of the rack, and choose Refresh Shelf to refresh the rack.
l Below the color descriptions of the board, choose Display Logic Function. Then, the logic
functions of the boards are displayed.
9.1.2 Starting the Device Panel

This section describes how to start the device panel.
Prerequisite
Procedure
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is
displayed.
Step 2 The BSC Device Panel tab is displayed.
Step 3 Click BSC under Device Navigation Tree. Click the required BTS, and the corresponding BTS
Device Panel tab is displayed on the right.
----End

Prerequisite
l The boards are in position.
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see
9.2.2 Starting the Emulation Panel).
Step 2 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 Optical Interface Board
Port Information is displayed, showing the details about the E1/T1 port.
----End


BSC6900 UMTS
Prerequisite
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
1. Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation
panel (see 9.2.2 Starting the Emulation Panel).
2. Right-click a board in position in the device panel or emulation panel, and then choose
Display CPU Usage from the shortcut menu. The CPU Usage window is displayed,
showing the real-time CPU usage.
1. Run the DSP CPUUSAGE command to query the CPU usage.
----End

Prerequisite
Context
You can query the status of a board through menu operations or through MML commands.
Procedure
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing details of the board.
1. Run the DSP BRD command to query the information about the BSC board.
----End


BSC6900 UMTS
Prerequisite
Context
CAUTION
l If the standby board is not available or the standby board is faulty, resetting the board will
disrupt the ongoing services. Thus, perform this operation with caution.
l Resetting the board may affect the ongoing services. Therefore, you are advised to perform
the switchover when the traffic load is light, for example, in the middle of the night.
l Resetting the Board

The board resetting is mandatory during software upgrade and software loading. Resetting
the board will reload the programs and data files. If the active board is reset and the standby
board is working normally, the services processed by the active board will be switched over
to the standby board first, and then the standby board (the original active board) is reset
after the switchover. If an SCUa board is reset while its standby board is not available or
is faulty, the entire subrack is reset.
l Reset the CPU
Each XPUa board has four CPUs numbered from 0 to 3. Other types of boards have one
CPU each. If CPU 0 of the XPUa board is reset, the entire board is reset.
l Resetting the DSP
Each DPU board has 22 DSPs numbered from 0 to 21. Each DSP can be reset separately.
Procedure
Reset BSC Board.
3. In the displayed Reset BSC Board dialog box, set the parameters as required, and
then click Reset.
1. Run the RST BRD command to reset a BSC board.
----End


BSC6900 UMTS
Prerequisite
l Before you perform the switchover, ensure that the standby board is present and running
normally without any critical or major alarms.
Context
CAUTION
l If the board switchover fails, the configuration data is not affected but the services will be
disrupted. Thus, perform this task with caution.
l Resetting the board may affect the ongoing services. Thus, you are advised to perform the
switchover when the traffic load is light, for example, in the middle of the night.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMUa board. The OMUa board also supports
switchover initiated by the standby board.
Procedure
Switch BSC Board.
3. In the displayed Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.
1. Run the SWP BRD command to switch over the BSC boards.
----End
9.2 Emulation Panel Operations

This section describes the operations of the BSC6900 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the status of the boards.
9.2.1 Introduction to the Emulation Panel

The LMT provides the emulation panel for each subrack. The emulation subrack has the same
ports as the real subrack and helps to ascertain the status of each board.
9.2.2 Starting the Emulation Panel
This section describes how to start the emulation panel.

BSC6900 UMTS

9.2.8 Querying the Status of an FE Port
This section describes how to query the status of an FE port.
9.2.9 Querying the Status of a GE Port
This section describes how to query the status of a GE port on the SCUa board.
9.2.10 Querying the Status of an Optical Port
This section describes how to query the status of an optical port.
9.2.11 Querying the DSP Status of a DPU
This section describes how to query the DSP status of a DPU board.
9.2.12 Querying Alarm LED Information
This section describes how to query the details of alarms indicated by an alarm LED.
9.2.1 Introduction to the Emulation Panel

The LMT provides the emulation panel for each subrack. The emulation subrack has the same
ports as the real subrack and helps to ascertain the status of each board.
The emulation panel displays the running status of the ports of each board and provides right-
click menus as shown in Figure 9-2.

BSC6900 UMTS
Figure 9-2 Emulation panel
The emulation panel has the following features:

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

This section describes how to start the emulation panel.
Prerequisite
Procedure
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is
displayed.
Step 2 Click BSC6900 under Device Navigation Tree. The BSC Device Panel is displayed on the
right pane.
Step 3 To display the emulation panel of a subrack, select the corresponding rack and double-click the
peripheral of the subrack, as shown in Figure 9-3.

BSC6900 UMTS
Figure 9-3 Subrack peripheral
----End

Prerequisite
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see
9.2.2 Starting the Emulation Panel).
Step 2 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 Optical Interface Board
Port Information is displayed, showing the details about the E1/T1 port.
----End

Prerequisite

BSC6900 UMTS
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
Display CPU Usage from the shortcut menu. The CPU Usage window is displayed,
showing the real-time CPU usage.
1. Run the DSP CPUUSAGE command to query the CPU usage.
----End

Prerequisite
Context
Procedure
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing details of the board.
1. Run the DSP BRD command to query the information about the BSC board.
----End

Prerequisite

BSC6900 UMTS
Context
CAUTION
l If the standby board is not available or the standby board is faulty, resetting the board will
disrupt the ongoing services. Thus, perform this operation with caution.
l Resetting the board may affect the ongoing services. Therefore, you are advised to perform
the switchover when the traffic load is light, for example, in the middle of the night.
l Resetting the Board

The board resetting is mandatory during software upgrade and software loading. Resetting
the board will reload the programs and data files. If the active board is reset and the standby
board is working normally, the services processed by the active board will be switched over
to the standby board first, and then the standby board (the original active board) is reset
after the switchover. If an SCUa board is reset while its standby board is not available or
is faulty, the entire subrack is reset.
l Reset the CPU
Each XPUa board has four CPUs numbered from 0 to 3. Other types of boards have one
CPU each. If CPU 0 of the XPUa board is reset, the entire board is reset.
l Resetting the DSP
Each DPU board has 22 DSPs numbered from 0 to 21. Each DSP can be reset separately.
Procedure
Reset BSC Board.
3. In the displayed Reset BSC Board dialog box, set the parameters as required, and
then click Reset.
1. Run the RST BRD command to reset a BSC board.
----End

Prerequisite

BSC6900 UMTS
l Before you perform the switchover, ensure that the standby board is present and running
normally without any critical or major alarms.
Context
CAUTION
l If the board switchover fails, the configuration data is not affected but the services will be
disrupted. Thus, perform this task with caution.
l Resetting the board may affect the ongoing services. Thus, you are advised to perform the
switchover when the traffic load is light, for example, in the middle of the night.
l All boards configured in active/standby mode support switchover operations. Only the active
board can initiate the switchover, except the OMUa board. The OMUa board also supports
switchover initiated by the standby board.
Procedure
Switch BSC Board.
3. In the displayed Switch BSC Board dialog box, set the parameters as required, and
then click Switch to switch over the boards.
1. Run the SWP BRD command to switch over the BSC boards.
----End
9.2.8 Querying the Status of an FE Port

This section describes how to query the status of an FE port.
Prerequisite
Context
You can query the status of an FE port through menu operations or through MML commands.
Procedure
1. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).

BSC6900 UMTS
2. On the emulation panel of the subrack, right-click the FE port to be queried, and choose
Display Ethernet Port Status from the shortcut menu. The Display Ethernet Port
Status window is displayed, showing the details of the FE port status.
1. Run the DSP ETHPORT to query the status of the FE port.
----End
9.2.9 Querying the Status of a GE Port

This section describes how to query the status of a GE port on the SCUa board.
Prerequisite
Context
You can query the status of a GE port through menu operations or through MML commands.
Procedure
2. On the emulation panel of the subrack, right-click the GE port to be queried, and
choose Display Ethernet Port Status from the shortcut menu. The Display Ethernet
Port Status window is displayed, showing the details of the GE port status.
1. Run the DSP GEPORT command to query the status of the GE port.
----End
9.2.10 Querying the Status of an Optical Port

This section describes how to query the status of an optical port.
Prerequisite
Context
You can query the status of an optical port through menu operations or through MML commands.
Procedure
2. On the emulation panel, right-click the optical port to be queried, and choose Query
Optical Port Status and Performance from the shortcut menu. In the displayed

BSC6900 UMTS
Query Optical Port Status and Performance window, specify the parameters as
required, and click Submit to query the detailed information about the optical port.
1. Run the DSP OPT to query the status of the optical port.
----End
9.2.11 Querying the DSP Status of a DPU

This section describes how to query the DSP status of a DPU board.
Prerequisite
l The board is in the specified slot.
Context
You can query the DSP status of a DPU board through menu operations or through MML
commands.
Procedure
2. On the emulation panel, right-click the required port on the DPU board, and choose
Query DSP Status from the shortcut menu. The displayed Query DSP Status shows
the details about the DSP status.
1. Run the DSP DSP command to query the DSP status of the DPU board.
----End
9.2.12 Querying Alarm LED Information

This section describes how to query the details of alarms indicated by an alarm LED.
Prerequisite
Procedure
Step 1 Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
Step 2 On the emulation panel, right-click the alarm LED to be queried, and then choose Query Alarm
Indicator Info from the shortcut menu. The Query Alarm Indicator Info window is displayed,
showing the details of alarms indicated by the alarm LED.
----End

BSC6900 UMTS
LMT User Guide 10 FAQ
10 FAQ
About This Chapter
This chapter describes the frequently asked questions (FAQs) and the corresponding solutions.
10.1 Browser Cache expires.

After the LMT software is upgraded or rolled back, a warning message is displayed as follows:
"Warning: the temporary files have expired, you must clear the browser's temporary files and
cookies, then refresh to re-open the browser." In this case, you need to clear the cache, cookies,
and Java Applet.
10.2 The LMT gives slow responses to user operations in the Firefox browser.
When the LMT runs in the Firefox browser, it 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.
10.3 The color of the LMT is not correctly displayed.
When the LMT is started in the IE browser, the colors are not correctly 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.
10.4 The verify code cannot be displayed on the LMT login page.
The verify code cannot be displayed when you try to log in to the LMT through the IE browser
in the Windows Server 2008 or Windows Vista system. In this case, check the settings related
to the protection mode of the browser.
10.5 Installing OS Patches
In a Microsoft Windows operating system (OS), you need to install patch KB944338 or
KB960714 if the OS and IE are in a certain version.
10.6 Clicking the menu bar on the LMT has no response.
When the LMT webpage is browsed through IE, there is no response or a webpage script error
occurs when you click the menu bar. To be specific, when you click the menu bar or buttons or
right-click the webpage, there is no response or a dialog box is displayed, indicating a script
error, for example, you are rejected or have no right to access the webpage. In this case, check
the proxy settings in IE.
10.7 Changing the Computer Time During the LMT Use Prohibited

BSC6900 UMTS
10 FAQ LMT User Guide
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.
10.8 Corrupt Characters Occurring When Opening the csv File 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 corrupt characters. In this case, open the csv file by using the import method in
Excel.
10.9 Methods for Setting the Explorer Under Citrix Farm Networking
Under Citrix farm networking, you log in to the LMT on a Citrix client. When you use the M2000
as the proxy server for the login, the LMT may be suspended or the verification code may be
unavailable. When these problems occur, you can check the explorer setting, including the
setting of the explorer proxy server and HTTP 1.1 setting. If the setting is wrong, you can set it
anew.
10.10 Unable to Log In To LMT Because IE Default Security Level Is Too High
In a Windows Server operating system (including Windows Server 2003 and Windows Server
2008), the IE blocks Web programs of sites that are out of the trusted site list to improve system
security. As a result, you may fail to log in to the LMT.
10.11 Unable to Log In To LMT and Class can't Stand Automation Operation is Displayed
When the LMT is started in the IE browser, Class can't Stand Automation Operation is
displayed.
10.12 LMT Failing to Load the Progress Interface After a Successful Login
After logging in to the LMT successfully, you may find that the LMT fail to load the progress
interface. This section describes the solution to the problem.

BSC6900 UMTS
10.1 Browser Cache expires.

After the LMT software is upgraded or rolled back, a warning message is displayed as follows:
"Warning: the temporary files have expired, you must clear the browser's temporary files and
cookies, then refresh to re-open the browser." In this case, you need to clear the cache, cookies,
and Java Applet.
Procedure
l To clear the cache and cookies in the Firefox browser, do as follows:
1. Choose Tools > Clear Private Data in the Firefox browser.
2. In the displayed Clear Private Data dialog box, select Cache, Cookies, and Offline
Website Data, and then click Clear Private Data Now.
NOTE
In this section, FireFox V3.0 is taken as an example. The previous steps are only for reference, and
may be changed based on the actual version of FireFox.
l To clear the cache and cookies in the IE 6.0 browser, do as follows:
1. Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
Options dialog box is displayed.
2. In the General tab page, click Delete Cookies. A dialog box is displayed, prompting
you to confirm the operation. Click OK.
3. In the General tab page, click Delete Files. A dialog box is displayed, prompting you
to confirm the operation. Select Delete all offline content and click OK.
4. In the Internet Options dialog box, click OK to exit the dialog box.
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 confirmation dialog
box. To delete the cookies, click Delete Cookies, and then click OK in the
confirmation dialog box.
4. In the Delete Browsing History dialog box, click OK and exit the Internet
Options dialog box.
2. On the General tab page, click Delete. The Delete Browsing History dialog box is
displayed.
3. In the Delete Browsing History dialog box, choose Temporary Internet Files and
Cookies. Click Delete.
4. In the Internet Options dialog box, click OK to exit the dialog box.
l To clear Java Applet, do as follows:
1. Choose Start > Control Panel.

BSC6900 UMTS
2. Double-click the Java icon. The Java Control Panel dialog box is displayed.
3. In the General tab page, click Settings. The Temporary Files Settings dialog box is
displayed.
4. Click Delete Files. In the displayed Delete Temporary Files dialog box, select
Applications and Applets and Trace and Log Files. Click OK.
5. In the Java Control Panel dialog box, click OK to exit the panel.
NOTE
Restart the browser to validate the modifications.
----End
10.2 The LMT gives slow responses to user operations in the

Firefox browser.
When the LMT runs in the Firefox browser, it 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
10.3 The color of the LMT is not correctly displayed.

When the LMT is started in the IE browser, the colors are not correctly displayed. For example,
the colors indicating the status of the boards and alarms are not displayed, or the background
color of the LMT is not differentiated from that of the IE browser. In this case, check the color
settings of the browser.
Procedure
Step 1 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialog
box is displayed.
Step 2 On the General tab page, click Accessibility. The Accessibility dialog box is displayed.
Step 3 In the Formatting area, deselect Ignore colors specified on Web pages, and then click OK.
Step 4 In the Internet Options dialog box, click OK to exit the dialog box.
----End

BSC6900 UMTS
10.4 The verify code cannot be displayed on the LMT login

page.
The verify code cannot be displayed when you try to log in to the LMT through the IE browser
in the Windows Server 2008 or Windows Vista system. In this case, check the settings related
to the protection mode of the browser.
Context
If the protected mode is enabled for the IE browser in the Windows Server 2008 or Windows
Vista system, there are many security restrictions. For example, JavaScript and Applet cannot
be run. Therefore, you need to turn off 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 bar on the IE. Press Enter on
the keyboard, or click Go next to the address bar to display the login window of the BSC6900.
Step 2 Check whether "Internet | Protected Mode: Off" is displayed on the bottom right of the window.
l If yes, the task is complete.
l If no, go to Step 3.
Step 3 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialog
box is displayed.
Step 4 On the Security tab page, select Trusted sites in the Select a Web content zone to specify its
security settings area.
Step 5 Deselect Enable Protected Mode. Click Sites. The Trusted sites dialog box is displayed.
Step 6 Type the external virtual IP address of the OMU in the Add this Web site to the zone text box,
and then click Add. Thus, the external virtual IP address of the OMU is added to the Trusted
sites list.
Step 7 In the Internet Options dialog box, click OK to exit the dialog box.
NOTE
----End
10.5 Installing OS Patches

In a Microsoft Windows operating system (OS), you need to install patch KB944338 or
KB960714 if the OS and IE are in a certain version.
Context
l Patch KB960714 solves the problem of Java console output error. Thus, the Java application
can be loaded successfully on the LMT.

BSC6900 UMTS
l Patch KB944338 improves the performance of the LMT by increasing the speed of visiting
a web page. Thus, the LMT running rate can be increased.
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 and KB960714 are present in the list of Currently installed programs.
l If the patches are present, the task is complete.
l If the patches are not present, go to Step 3.
Step 3 Determine whether a Windows patch needs to be installed according to the OS version and IE
version.
l Patch KB960714 needs to be installed when the OS version and IE version are combined in
the following ways:
OS Version IE Version
Windows 2000 SP4 IE5/IE6 SP1
Windows XP SP2/SP3 IE6/IE7
Windows Server 2003 SP1/SP2 IE6/IE7
Windows Vista IE7
l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4, Windows
XP SP1/SP2, or Windows Server 2003 SP1/SP2.
NOTE
l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.

l Download a suitable patch according to the OS version and IE version.
----End
10.6 Clicking the menu bar on the LMT has no response.

When the LMT webpage is browsed through IE, there is no response or a webpage script error
occurs when you click the menu bar. To be specific, when you click the menu bar or buttons or
right-click the webpage, there is no response or a dialog box is displayed, indicating a script
error, for example, you are rejected or have no right to access the webpage. In this case, check
the proxy settings in IE.
Context
Do not modify the settings of the IE when you have logged in to the LMT. Set the proxy server
when necessary before you log in to the LMT.

BSC6900 UMTS
Procedure
Step 1 Choose Tools > Internet Options on the tool bar of IE. The Internet Options dialog box is
displayed.
Step 2 On the Connections tab page, click LAN Settings. The LAN Settings dialog box is displayed.
Step 3 In the Proxy server area, select Use a proxy server for your LAN (These settings will not
apply to dial-up or VPN connections). Type the IP address and port number of the proxy server
in the corresponding text boxes, and then click Advanced. The Proxy settings dialog box is
displayed.
Step 4 In the Exceptions area, type the external virtual IP address of the OMU in the text box, and then
click OK. Close the Internet Options dialog box.
----End
10.7 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.
10.8 Corrupt Characters Occurring When Opening the csv

File 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 corrupt characters. In this case, open the csv file by using the import method in
Excel.
Procedure
Step 1 On the menu bar of Excel, choose Data > Import External Data > Import Data. Then the
Select Data Source dialog box is displayed. Figure 10-1 shows the dialog box.

BSC6900 UMTS
Figure 10-1 Operation interface for importing data in Excel
Step 2 In the Select Data Source dialog box, select the csv file in UTF-8 coding. Then the Text Import
Wizard - Step 1 of 3 dialog box is displayed. Figure 10-2 shows the dialog box. Select UTF-8
in File origin.
Figure 10-2 Text import wizard—step 1

BSC6900 UMTS
Step 3 Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed. Figure 10-3
shows the dialog box. Select Comma under Delimiters.
Figure 10-3 Text import wizard—step 2
Step 4 Click Finish. Then the Import Data dialog box is displayed. Figure 10-4 shows the dialog box.
Figure 10-4 Interface after data importation is finished
Step 5 Click OK. Then the file is displayed properly.
----End

BSC6900 UMTS
10.9 Methods for Setting the Explorer Under Citrix Farm

Networking
Under Citrix farm networking, you log in to the LMT on a Citrix client. When you use the M2000
as the proxy server for the login, the LMT may be suspended or the verification code may be
unavailable. When these problems occur, you can check the explorer setting, including the
setting of the explorer proxy server and HTTP 1.1 setting. If the setting is wrong, you can set it
anew.
Context
You can set the explorer under Citrix farm networking in the following ways:
l Script setting: An automatic setting script is placed on the domain control server. After a
Citrix user logs in to the server, the script automatically sets the explorer.
l Manual setting: The explorer is set manually.
The Citrix server works in the farm mode. In the 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
explorer thus may need to be set repeatedly. We therefore recommend setting the explorer using
the script. In this way, each time the user visits the server, automatic setting of the explorer is
performed and repeated settings are avoided.
Procedure
l Script Setting
1. Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
setlocal ENABLEDELAYEDEXPANSION
set uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul
\Internet Settings"
reg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nul
reg add %uu% /v ProxyOverride /t REG_SZ /d "<local>" /f >nul
reg add %uu% /v ProxyEnable /t REG_DWORD /d "1" /f >nul
NOTE
The IE-unset.bat script file implements automatic setting of the explorer for the domain user.
The domain user can change 10.121.49.213:80 in
reg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nul
in the script to the actual IP address of the proxy server and the actual port number.
2. Log in to the primary or a secondary domain control server with the user name of
administrator and place the IE-unset.bat file in the C:\WINDOWS\SYSVOL\sysvol
\citrixtest.com\scripts path on the server.
NOTE
The default installation path on the domain control server is C:\WINDOWS\SYSVOL\sysvol
\citrixtest.com\scripts. The path changes if you install the file elsewhere. Here,
citrixtest.com is taken as an example of the test domain name. The actual domain name depends
on actual conditions.

BSC6900 UMTS
3. For details about establishing a domain user, refer to the Citrix Access Solution User
Guide.
4. Set user script for each domain user.
Assume that there is a user named hong01 in the hongtest unit of the citrixtest.com
domain.
(1) Start Active Directory Users and Computers and double-click hongtest in the
left-side window. In the right-side window, all users in the hongtest unit are
displayed. Figure 10-5 shows the window.
Figure 10-5 Active Directory Users and Computers
(2) In the right-side window, right-click hong01. Choose Properties from the
shortcut menu. Accordingly, the hong01 Properties dialog box is displayed.
Figure 10-6 shows the dialog box.

BSC6900 UMTS
Figure 10-6 hong01 Properties 1
(3) In the hong01 Properties dialog box, click the Profile tag. Type IE-unset.bat
in Logon script, click Apply, and then click OK. Figure 10-7 shows the
window.

BSC6900 UMTS
Figure 10-7 hong01 Properties 2
l Manual Setting
1. Check the proxy server setting of the explorer.
(1) Choose Tools > Internet Options on the tool bar of the IE. Accordingly, the
Internet Options dialog box is displayed.
(2) On the Connections tab, click LAN Settings. Accordingly, the Local Area
Network (LAN) Settings dialog box is displayed.
(3) In the Proxy server area, select Use a proxy server for your LAN (These
settings will not apply to dial-up or VPN connections). , Set Address to the
IP address of the M2000 and set Port to 80.

BSC6900 UMTS
2. Check "HTTP 1.1 settings" of the explorer.

(1) Choose Tools > Internet Options on the tool bar of the IE. Accordingly, the
Internet Options dialog box is displayed.
(2) On the Advanced tab, select Use HTTP 1.1 through proxy connections under
HTTP 1.1 settings, click Apply, and then click OK. Figure 10-8 shows the
window.
Figure 10-8 HTTP 1.1 settings

BSC6900 UMTS
----End
10.10 Unable to Log In To LMT Because IE Default Security

Level Is Too High
In a Windows Server operating system (including Windows Server 2003 and Windows Server
2008), the IE blocks Web programs of sites that are out of the trusted site list to improve system
security. As a result, you may fail to log in to the LMT.
Context
l 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.
Thus, you may fail to log in to the LMT.
l According to the acceptable IE security level, there are the following two solutions:
– When lowering the IE security level on the Windows server is unacceptable, you can
add the LMT site to the trusted sites of the IE by using a configuration startup script.
The system automatically loads the script and configures the IE after a Citrix user logs
in.
– When lowering the IE security level on the Windows server is acceptable, you can
remove the Windows component, Internet Explorer Enhanced Security Configuration.
Procedure
l Setting a configuration startup script
1. Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul

BSC6900 UMTS
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul

\Internet Settings\ZoneMap\EscRanges\Trust"
reg add %uu% /v :Range /t REG_SZ /d "10.141.149.193" /f >nul
reg add %uu% /v http /t REG_DWORD /d "2" /f >nul
NOTE
l The IE-unset.bat script file implements automatic setting of IE trusted sites for Citrix domain
users.
l The domain user can change 10.141.149.193 in reg add %uu% /v :Range REG_SZ /d
"10.141.149.193" /f >nul in the script to the IP address of the network element or the peer IP
address of the network elements that need to be visited.
l If the user needs to set multi-network elements and the network elements don't exisit in a same
peer IP address, multi-scripts need to be prepared and loaded separately.
l Trust in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ZoneMap\EscRanges\Trust" can be named as you wish.
2. Load the startup script.
– Script setting for a single Windows server
(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 10-9, choose
User Configuration > Windows Settings > Scripts(Logon/Logoff).
Figure 10-9 Script

BSC6900 UMTS
(4) Double-click Logon. A dialog box shown in Figure 10-10 is displayed. Click
Show Files and copy the prepared script to the displayed directory. Then close
the dialog box displaying the directory.
Figure 10-10 Logon
(5) Click Add in the dialog box shown in Figure 10-11. A dialog box shown in
Figure 10-11 is displayed.
Figure 10-11 Adding a script

BSC6900 UMTS
(6) In the dialog box shown in Figure 10-11, click Browse to select the prepared
script and click OK. Then close the dialog box.
(7) In the dialog box shown in Figure 10-10, click Apply and confirm to load
the prepared script.
(8) Restart the IE to validate the configuration.
NOTE
The users need to logon 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.
NOTE
l If the organization unit have be set, the users which belong to the organization unit
can all succeed in logging in to the LMT.
l You can rename the group policy object.
(2) Select the created group policy object and click Edit. In the displayed dialog
box shown in Figure 10-12, choose User Configuration > Windows
Settings > Scripts(Logon/Logoff).
Figure 10-12 Script

BSC6900 UMTS
(3) Double-click Logon. A dialog box shown in Figure 10-13 is displayed. Click
Show Files and copy the prepared script to the displayed directory. Then close
the dialog box displaying the directory.
Figure 10-13 Logon
(4) Click Add in the dialog box shown in Figure 10-13. A dialog box shown in
Figure 10-14 is displayed.
Figure 10-14 Adding a script

BSC6900 UMTS
(5) In the dialog box shown in Figure 10-14, click Browse to select the prepared
script and click OK. Then close the dialog box.
(6) In the dialog box shown in Figure 10-13, click Apply and confirm to load
the prepared script.
l Removing Internet Explorer Enhanced Security Configuration
1. Log in to the Windows server with the account of administrator. Choose Start >
Control Panel > Add or Remove Programs. Select Internet Explorer Enhanced
Security Configuration in the displayed dialog box shown in Figure 10-15.
Figure 10-15 Windows components wizard
2. Click Details... in the dialog box shown in . In the displayed dialog box shown in
Figure 10-16, deselect For administrator groups and For all other user groups.

BSC6900 UMTS
Figure 10-16 Internet Explorer Enhanced Security Configuration
3. Click OK and then click Next to remove Internet Explorer Enhanced Security
Configuration. After the removal is complete, click Finish.
4. Restart the IE to validate the configuration.
----End
10.11 Unable to Log In To LMT and Class can't Stand

Automation Operation is Displayed
When the LMT is started in the IE browser, Class can't Stand Automation Operation is
displayed.
Procedure
Step 1 Choose Start > Run.
Step 2 Type regsvr32 msscript.ocx in the displayed dialog box. Then click OK.
Step 3 Repeat Step 1. In the Run dialog box, input regsvr32 dispex.dll, regsvr32 vbscript.dll,
regsvr32 scrrun.dll and regsvr32 urlmon.dll in turn, then click OK.
Step 4 Clear the cache in the browser.

NOTE
----End

BSC6900 UMTS
10.12 LMT Failing to Load the Progress Interface After a

Successful Login
After logging in to the LMT successfully, you may find that the LMT fail to load the progress
interface. This section describes the solution to the problem.
Context
l After logging in to the LMT successfully, you may find that the LMT fail to load the
progress interface.
shows the problem.

l The version of the JRE plug-in is found to be earlier than 1.6.0_11.
l Multiple JRE plug-ins can be installed on one client PC. If a user installs a JRE plug-in of
an earlier version after installing one of a later version and then use the LMT, the functional
JRE plug-in is the one of the earlier version. If the earlier version is earlier than 1.6.0_11,
the preceding problem will arise.
l After you log in to the LMT successfully, an icon as shown in is displayed in the bottom
right corner of the PC desktop. You can query the version of a JRE plug-in by double-
clicking the icon.
Procedure
Step 1 Reinstall a JRE plug-in of a version that is later than 1.6.0_11.
NOTE
You need to restart the IE after reinstalling the JRE plug-in.
----End


GJJ

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GJJ

Uploaded by

Copyright:

Available Formats

BSC6900 UMTS

LMT User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2011-03-28) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 08 (2011-03-28) Huawei Proprietary and Confidential iii

3 Management of Operation Rights

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

iv Huawei Proprietary and Confidential Issue 08 (2011-03-28)

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Issue 08 (2011-03-28) Huawei Proprietary and Confidential v

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Double-click Press the primary mouse button twice continuously and

vi Huawei Proprietary and Confidential Issue 08 (2011-03-28)

About This Document...................................................................................................................iii

3 Management of Operation Rights..........................................................................................3-1

Issue 08 (2011-03-28) Huawei Proprietary and Confidential vii

3.4.1 Querying a Command Group...............................................................................................................3-10

4 Running MML Commands......................................................................................................4-1

viii Huawei Proprietary and Confidential Issue 08 (2011-03-28)

5.5.9 Refreshing the Alarm Window............................................................................................................5-13

Issue 08 (2011-03-28) Huawei Proprietary and Confidential ix

8.1 Concepts Related to Performance Monitoring................................................................................................8-2

x Huawei Proprietary and Confidential Issue 08 (2011-03-28)

Issue 08 (2011-03-28) Huawei Proprietary and Confidential xi

Figure 2-1 LMT window......................................................................................................................................2-7

Issue 08 (2011-03-28) Huawei Proprietary and Confidential xiii

Figure 9-3 Subrack peripheral..............................................................................................................................9-9

xiv Huawei Proprietary and Confidential Issue 08 (2011-03-28)

Table 2-1 Hardware requirements of the LMT PC...............................................................................................2-2

Issue 08 (2011-03-28) Huawei Proprietary and Confidential xv

1 Changes in the BSC6900 UMTS LMT User

6.9 Collecting Log Statistics The description about log is added.

Issue 08 (2011-03-28) Huawei Proprietary and Confidential 1-1

Topic Change Description

2.1 Configuration Requirements of the The description about requirements of Web

Topic Change Description

2.1 Configuration Requirements of the The description about requirements of

1-2 Huawei Proprietary and Confidential Issue 08 (2011-03-28)

Issue 08 (2011-03-28) Huawei Proprietary and Confidential 1-3

About This Chapter

2.1 Configuration Requirements of the LMT PC

Issue 08 (2011-03-28) Huawei Proprietary and Confidential 2-1

2.1 Configuration Requirements of the LMT PC

Table 2-1 Hardware requirements of the LMT PC

CPU 1 2.8 GHz or above 866 MHz