Bsc6910 GSM LMT User Guide (v100r015c00 - 08) (PDF) - en

BSC6910 GSM
V100R015C00
LMT User Guide

Issue
08
Date
2014-06-09
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

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

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

Address:
Huawei Industrial Base

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

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

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

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

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

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

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

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 08 (2014-06-09)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.

iv
BSC6910 GSM
LMT User Guide
About This Document
Convention
Description
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

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

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

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

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

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

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

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

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

BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
About This Document
Action
Description
Click
Select and release the primary mouse button without moving

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

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

vi
BSC6910 GSM
LMT User Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the BSC6910 GSM LMT User Guide....................................................................1
2 Introduction to LMT.....................................................................................................................5
2.1 Configuration Requirements of the LMT PC.................................................................................................................6
2.2 Logging In to and Logging Out of the LMT..................................................................................................................8
2.3 Components of the LMT Window................................................................................................................................12
2.4 LMT Software..............................................................................................................................................................16
2.4.1 Installing LMT Offline Tools....................................................................................................................................16
2.4.2 FTP Client..................................................................................................................................................................18
2.4.3 FTP Server.................................................................................................................................................................19
2.4.4 LMT Offline MML....................................................................................................................................................21
2.4.5 Convert Management System....................................................................................................................................25
2.4.6 Performance Browser Tool........................................................................................................................................26
2.4.7 TrafficRecording Review Tool..................................................................................................................................27
2.5 User-defined Command Group....................................................................................................................................28
2.6 File Manager.................................................................................................................................................................30
3 Management of Operation Rights............................................................................................35

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

vii
BSC6910 GSM
LMT User Guide
Contents
3.3.3 Changing the Password of the Active User Account................................................................................................42

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

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

viii
BSC6910 GSM
LMT User Guide
Contents
5.5 Monitoring Alarms.......................................................................................................................................................71

5.5.1 Browsing Alarm/Event..............................................................................................................................................71
5.5.2 Querying the Alarm/Event Log.................................................................................................................................71
5.5.3 Querying Alarm/Event Handling Suggestions..........................................................................................................72
5.5.4 Querying Alarm/Event Configuration.......................................................................................................................73
5.5.5 Filtering Fault Alarm/Event.......................................................................................................................................74
5.5.6 Setting Display Attributes for Alarms/Events...........................................................................................................74
5.5.7 Manually Clearing an Alarm/Event...........................................................................................................................77
5.5.8 Deleting Alarms/Events.............................................................................................................................................77
5.5.9 Refreshing the Alarm/Event Window.......................................................................................................................78
5.6 Managing the Alarm Box.............................................................................................................................................78
5.6.1 Querying Alarm Box Information.............................................................................................................................78
5.6.2 Querying Number of Alarms with Different Severities............................................................................................79
5.6.3 Operating the Alarm Box..........................................................................................................................................79
5.6.4 Querying the Alarm Box Filter Level........................................................................................................................80
6 Log Management.........................................................................................................................81
6.1 Log Types.....................................................................................................................................................................83
6.2 Querying Log Storage Conditions................................................................................................................................83
6.3 Setting Log Storage Conditions....................................................................................................................................83
6.4 Querying Operation Logs.............................................................................................................................................84
6.5 Exporting Operation Logs............................................................................................................................................84
6.6 Querying Security Logs................................................................................................................................................85
6.7 Exporting Security Logs...............................................................................................................................................85
6.8 Obtaining Running Logs..............................................................................................................................................86
6.9 Collecting Log Statistics...............................................................................................................................................88
7 Trace Management......................................................................................................................94
7.1 Concepts Related to Trace Management......................................................................................................................95
7.1.1 Trace Principles.........................................................................................................................................................95
7.1.2 Management of Tracing Operation Rights................................................................................................................96
7.1.3 BSC Interface Signaling Tracing Mode....................................................................................................................96
7.2 Device Commissioning.................................................................................................................................................97
7.2.1 Tracing OS Messages................................................................................................................................................97
7.2.2 Tracing Redirected Messages....................................................................................................................................98
7.2.3 Capturing Packets......................................................................................................................................................98
7.2.4 AC Tracing..............................................................................................................................................................102
7.2.5 DHCP Tracing.........................................................................................................................................................104
7.3 GSM Services.............................................................................................................................................................105
7.3.1 Tracing Messages on the A Interface......................................................................................................................106
7.3.2 Tracing CS Domain Messages on the Um Interface...............................................................................................112
7.3.3 Tracing PS Domain Messages on the Um Interface................................................................................................114
7.3.4 Tracing Messages on the Cb Interface.....................................................................................................................116
Issue 08 (2014-06-09)

ix
BSC6910 GSM
LMT User Guide
Contents
7.3.5 Tracing Messages on the Inter-BSC Interface.........................................................................................................117

7.3.6 Tracing CS Domain Messages on the Abis Interface..............................................................................................118
7.3.7 Tracing PS Domain Messages on the Abis Interface..............................................................................................130
7.3.8 Tracing PTP Messages on the Gb Interface............................................................................................................132
7.3.9 Tracing SIG Messages on the Gb Interface.............................................................................................................134
7.3.10 Tracing NS Signal Messages on the Gb Interface.................................................................................................135
7.3.11 Tracing CS Domain Messages of a Single Subscriber..........................................................................................137
7.3.12 Tracing PS Domain Messages of a Single Subscriber..........................................................................................140
7.3.13 Tracing BTS Signaling Messages..........................................................................................................................143
7.3.14 Tracing Messages on the LB Interface..................................................................................................................147
7.4 Basic Tracing Operations...........................................................................................................................................153
7.4.1 Browsing Traced Messages Online.........................................................................................................................153
7.4.2 Viewing the Interpretation of the Trace Message....................................................................................................154
7.4.3 Saving Traced Messages.........................................................................................................................................155
7.4.4 Browsing Traced Messages Offline........................................................................................................................156
7.4.5 Managing Tracing Tasks.........................................................................................................................................157
7.4.6 Managing the Trace File..........................................................................................................................................157
8 Performance Monitoring..........................................................................................................159
8.1 Concepts Related to Performance Monitoring...........................................................................................................160
8.1.1 Monitoring Principles..............................................................................................................................................160
8.1.2 Management of Monitoring Operation Rights........................................................................................................161
8.2 Common Monitoring..................................................................................................................................................162
8.2.1 Monitoring CPU Usage...........................................................................................................................................162
8.2.2 Monitoring CPU Usage on Subsystems..................................................................................................................163
8.2.3 Monitoring Transmission Resources.......................................................................................................................163
8.2.4 Monitoring BER Seconds........................................................................................................................................169
8.2.5 Monitoring BER......................................................................................................................................................171
8.2.6 Monitoring Link Performance.................................................................................................................................172
8.3 GSM Monitoring........................................................................................................................................................182
8.3.1 Monitoring Traffic on GPRS User Plane................................................................................................................183
8.3.2 Monitoring Cell Performance..................................................................................................................................183
8.3.3 Monitoring CS UP Resources..................................................................................................................................184
8.3.4 Monitoring BTS IP Link Performance....................................................................................................................185
8.3.5 Monitoring Spectrum Scan......................................................................................................................................187
8.3.6 Clock Test................................................................................................................................................................189
8.3.7 Monitoring DTF Test...............................................................................................................................................191
8.3.8 Monitoring Intermodulation Interference in Frequency Scanning Mode................................................................192
8.4 General Operations of Performance Monitoring........................................................................................................194
8.4.1 Browsing the Monitoring Results Online................................................................................................................194
8.4.2 Setting the Display Mode of the Chart....................................................................................................................194
8.4.3 Saving Monitoring Results......................................................................................................................................195
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
Contents
8.4.4 Browsing Monitoring Results Offline.....................................................................................................................195

8.5 Reference for Performance Monitoring......................................................................................................................196
9 Device Panel...............................................................................................................................198
9.1 Device Panel Operations............................................................................................................................................199
9.1.1 Introduction to the Device Panel.............................................................................................................................199
9.1.2 Starting the Device Panel........................................................................................................................................200
9.1.3 Querying the Status of an E1/T1 Port......................................................................................................................200
9.1.4 Querying the CPU Usage........................................................................................................................................200
9.1.5 Querying BSC Board Clock Status.........................................................................................................................201
9.1.6 Querying the BSC Board Information.....................................................................................................................202
9.1.7 Resetting the BSC Board.........................................................................................................................................203
9.1.8 Switching Over the BSC Boards.............................................................................................................................205
9.1.9 Querying the BSC Board Alarm..............................................................................................................................207
9.1.10 Querying the BTS Board Information...................................................................................................................207
9.1.11 Resetting the BTS Board.......................................................................................................................................208
9.1.12 Maintaining BTS Clock.........................................................................................................................................208
9.2 Emulation Panel Operations.......................................................................................................................................209
9.2.1 Introduction to the Emulation Panel........................................................................................................................209
9.2.2 Starting the Emulation Panel...................................................................................................................................210
9.2.3 Querying the Status of an E1/T1 Port......................................................................................................................211
9.2.4 Querying the CPU Usage........................................................................................................................................211
9.2.5 Querying BSC Board Clock Status.........................................................................................................................212
9.2.6 Querying the BSC Board Information.....................................................................................................................213
9.2.7 Resetting the BSC Board.........................................................................................................................................214
9.2.8 Switching Over the BSC Boards.............................................................................................................................216
9.2.9 Querying the BSC Board Alarm..............................................................................................................................218
9.2.10 Querying the Status of an FE Port.........................................................................................................................218
9.2.11 Querying the Status of a GE Port..........................................................................................................................219
9.2.12 Querying the Status of an Optical Port..................................................................................................................219
9.2.13 Querying Alarm LED Information........................................................................................................................220
9.3 Activating BTS...........................................................................................................................................................220
9.4 Deactivating BTS.......................................................................................................................................................221
9.5 Querying the BTS Alarm............................................................................................................................................221
10 BSC Maintenance....................................................................................................................223
10.1 Concepts Related to BSC Maintenance....................................................................................................................225
10.1.1 BSC Interface Processing Subsystem....................................................................................................................225
10.1.2 Loopback...............................................................................................................................................................226
10.2 Browsing Configuration Data...................................................................................................................................230
10.3 Backing Up Data......................................................................................................................................................231
10.4 Restoring Data..........................................................................................................................................................232
10.5 Diagnosing Fault.......................................................................................................................................................233
Issue 08 (2014-06-09)

xi
BSC6910 GSM
LMT User Guide
Contents
10.6 Batch Configuration.................................................................................................................................................235

10.7 OS Maintenance.......................................................................................................................................................237
10.8 Maintaining the Equipment......................................................................................................................................237
10.8.1 Querying the BSC Board Information...................................................................................................................238
10.8.2 Resetting the BSC Board.......................................................................................................................................239
10.8.3 Switching Over the BSC Boards...........................................................................................................................240
10.8.4 Querying BSC Board Clock Status.......................................................................................................................242
10.8.5 Maintaining Fan Box.............................................................................................................................................243
10.8.6 Maintaining the Power Distribution Box...............................................................................................................244
10.9 Maintaining Transmission and Signaling.................................................................................................................246
10.9.1 Maintaining LAPD Links......................................................................................................................................246
10.9.2 Maintaining SCCP Links.......................................................................................................................................248
10.9.3 Querying the Optical Interface Board Port Information........................................................................................249
10.9.4 Looping Back the Interface Board Port.................................................................................................................250
10.9.5 Looping Back the Interface Board Port Timeslot..................................................................................................252
10.10 Maintaining BSC User Resources..........................................................................................................................253
10.10.1 Voice Log Analysis.............................................................................................................................................253
10.10.2 Querying the Status of the Abis Interface Timeslot............................................................................................255
10.10.3 Querying Subsystem Resources..........................................................................................................................256
10.10.4 Querying Single User Resources.........................................................................................................................257
10.10.5 Collecting BSC Local Information......................................................................................................................258
10.10.6 Looping Back Remote Speech Channel..............................................................................................................259
10.10.7 Looping Back Subsystem Channel/Link.............................................................................................................261
10.11 Querying Board Version Information.....................................................................................................................263
11 BTS Maintenance.....................................................................................................................264
11.1 Concepts Related to BTS Maintenance....................................................................................................................267
11.1.1 BTS Attributes.......................................................................................................................................................267
11.1.2 Cell Forced Handover Mode.................................................................................................................................271
11.2 Query Running Software Version of a Board..........................................................................................................272
11.3 Downloading the BTS Software...............................................................................................................................273
11.4 Loading the BTS Software.......................................................................................................................................274
11.5 Activating BTS Software..........................................................................................................................................274
11.6 Querying BTS Running Status.................................................................................................................................275
11.7 Querying BTS Board Matching Result....................................................................................................................276
11.8 Querying BTS Attributes..........................................................................................................................................277
11.9 Resetting the BTS by Levels....................................................................................................................................278
11.10 Browsing BTS Initialization Process Message.......................................................................................................280
11.11 Changing Administrative State...............................................................................................................................281
11.12 Forced Handover....................................................................................................................................................283
11.13 Monitoring Channel Status.....................................................................................................................................283
11.14 Monitoring Interference Band of Channel..............................................................................................................285
Issue 08 (2014-06-09)

xii
BSC6910 GSM
LMT User Guide
Contents
11.15 Frequency Band Scan.............................................................................................................................................286

11.16 Querying the Failure Cause of Configuration Alarms............................................................................................288
11.17 Call Test..................................................................................................................................................................289
11.18 Antenna Feeder Intermodulation Test....................................................................................................................291
11.19 EmergencyDiag......................................................................................................................................................292
11.20 Customizing a Message..........................................................................................................................................294
11.21 Maintaining Site.....................................................................................................................................................296
11.21.1 Browsing the BTS Log........................................................................................................................................296
11.21.2 Testing Transmission Performance.....................................................................................................................297
11.21.3 Querying BTS Transmission State......................................................................................................................298
11.22 Maintaining the Cell...............................................................................................................................................299
11.22.1 Querying Frequency Scan Parameters.................................................................................................................299
11.22.2 Configuring Frequency Scan...............................................................................................................................300
11.23 Maintaining TRXs..................................................................................................................................................302
11.23.1 Querying the TRX Power Mode..........................................................................................................................302
11.23.2 Querying Automatic Power Correction Type......................................................................................................303
11.23.3 Testing TRX Loopback.......................................................................................................................................304
11.23.4 Testing Channel Loopback..................................................................................................................................305
11.23.5 Testing Idle Timeslots.........................................................................................................................................307
11.23.6 Resetting the TRX...............................................................................................................................................308
11.23.7 Querying TRX Timeslot......................................................................................................................................309
11.23.8 Enabling RF Data Collection Function for a TRX..............................................................................................310
11.24 Reference for BTS Maintenance............................................................................................................................312
12 FAQ............................................................................................................................................314
12.1 Slow Responses in the Firefox Browser...................................................................................................................319
12.2 LMT Colors Cannot Be Displayed...........................................................................................................................319
12.3 The Verification Code Cannot Be Displayed on the LMT Login Page...................................................................319
12.4 Installing OS Patches................................................................................................................................................320
12.5 No Response When Clicking the Menu Bar on the LMT........................................................................................321
12.6 Changing the Computer Time During the LMT Use Prohibited..............................................................................322
12.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding..................................................322
12.8 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously...........................................325
12.9 How to Set the Browser Under Citrix Farm Networking.........................................................................................325
12.10 Unable to Log In To LMT Because IE Default Security Level Is Too High.........................................................329
12.11 Unable to Download or Install the Java or Flash Plug-in and Two File Manager Windows Displayed Windows IE8
or Any Later Version Is Used...........................................................................................................................................336
12.12 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE.....................337
12.13 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes the Web Pages to Turn Blank
..........................................................................................................................................................................................338
12.14 Configuring the HTTPS Login Mode.....................................................................................................................339
12.15 The Error "Certificate Invalid" Is Displayed During an HTTPS Login.................................................................340
12.16 The Error 'Mismatched Address' Is Displayed During an HTTPS Login..............................................................349
Issue 08 (2014-06-09)

xiii
BSC6910 GSM
LMT User Guide
Contents
12.17 Tracing and Monitoring Functions Cannot Be Used..............................................................................................351

12.18 No response when click the control component or right-click during the tracing and monitoring processes........356
12.19 Interfaces for Performing Tracing or Monitoring Tasks Blinking.........................................................................357
12.20 Unable to Save Tracking and Monitoring Data......................................................................................................358
12.21 The File Manager Functions Improperly................................................................................................................359
12.22 BTS Nodes Cannot Be Displayed Under Device Navigation Tree........................................................................361
12.23 The Alarm/Event Function Becomes Unavailable.................................................................................................362
12.24 Incorrect Display of the Path for Downloading BTS Software..............................................................................363
12.25 The Message 'Class doesn't support Automation' Is Displayed in an IE Browser.................................................364
12.26 Java Installation Fails.............................................................................................................................................364
12.27 The LMT Login Web Page Cannot Be Opened with the PC OMU Installed........................................................365
12.28 Changing Settings for the Next-Generation Java Plug-in Fails..............................................................................365
12.29 Error Message"This user session already exists" Upon Login to LMT.................................................................370
12.30 The "Are You Sure You Want to Quit the Page" Dialog Box Is Displayed..........................................................371
12.31 Slow Response During an LMT Login...................................................................................................................371
12.32 Unclear Grids in the Tables in the MML Online Help...........................................................................................372
12.33 The "App Center" Web Page Is Automatically Displayed When Firefox Is Used to Browse the LMT................373
12.34 "Permission Denied" or "Access Denied" is Displayed When IE Is Used to Browse the LMT............................374
12.35 MML Command Failed to Be Executed or No Response to Tracing Tasks After the Browser Is Upgraded to IE8
..........................................................................................................................................................................................375
12.36 How to Handle Error Message Displayed on the LMT..........................................................................................376
12.37 Tracing File Not Being Uploaded to the Specified Directory................................................................................377
12.38 Settings on the LMT Failing to Take Effective......................................................................................................378
Issue 08 (2014-06-09)

xiv
BSC6910 GSM
LMT User Guide
Changes in the BSC6910 GSM LMT User

Guide
This chapter describes the changes made in the BSC6910 GSM LMT User Guide.
08 (2014-06-09)
This is the eighth commercial release of V100R015C00.
Compared with 07 (2014-03-28), this issue includes the following new topic:
l
Information Collection
Compared with 07 (2014-03-28), this issue does not incorporate any changes.
Compared with 07 (2014-03-28), this issue does not exclude any topics.
07 (2014-03-28)
This is the seventh commercial release of V100R015C00.
Compared with 06 (2014-01-20), this issue does not include any new topics.
Compared with 06 (2014-01-20), this issue incorporates the following changes:
Content
Description
2.1 Configuration
Requirements of the LMT PC
Deleted the description about the Windows XP operating

system as the recommended configuration from section
"Software Requirements" because Microsoft has stopped
maintaining the Windows XP operating system.
Added the following browser versions that are supported
by the LMT: Internet Explorer 10, FireFox 17.x, and
FireFox 24.x.
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
06 (2014-01-20)
This is the sixth commercial release of V100R015C00.
Compared with 05 (2013-11-15), this issue includes the following new topics:
l
12.38 Settings on the LMT Failing to Take Effective
Compared with 05 (2013-11-15), this issue does not incorporate any changes.
05 (2013-11-15)
This is the fifth commercial release of V100R015C00.
Content
Description
Tracing MTP2 Messages on the

A Interface
Modified the description of the parameters Subrack

No., Slot No., and Link ID.
7.3.11 Tracing CS Domain

Messages of a Single
Subscriber
Modified the description of the parameter Algorithmic

Trace.
04 (2013-07-30)
This is the fourth commercial release of V100R015C00.
l
Monitoring the PPP Link Traffic
Monitoring Traffic on the MLPPP Link Group

Content
Description
8.5 Reference for Performance

Monitoring
Added the MP Group physical port and PPP Link physical

port.
8.2.3 Monitoring Transmission

Resources
Modified the description of the statistical item Admitted

Bandwidth(2G Total) to "Total admitted bandwidth for
2G services at the transport layer on the user plane and
control plane. The 2G services consist of 2G CS and PS
services".
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
03 (2013-06-25)
This is the third commercial release of V100R015C00.
l
11.7 Querying BTS Board Matching Result

Content
Description
7.3.11 Tracing CS Domain

Messages of a Single
Subscriber
Added the description of the operation for setting Trace

object symbol type to IMEI.
11.16 Querying the Failure

Cause of Configuration Alarms
Modified the BTS type of Querying the Failure Cause

of Configuration Alarms to the BTS3900 series type
that are not in normalization mode.
02 (2013-05-30)
This is the second commercial release of V100R015C00.
Content
Description
2.1 Configuration
Requirements of the LMT PC
Modified the requirements of Java Platform Standard

Edition Runtime Environment and Adobe Flash Player.
Added the description that the browser window is
displayed at 100% level.
2.6 File Manager
Added the descriptions of Set Search Criteria and Delete

Search Criteria.
8.2.3 Monitoring Transmission

Resources
Added the description of RealTimeFluxBw and

RealTimeQueueFlux.
11.18 Antenna Feeder

Intermodulation Test
Added the description that only base stations of versions

earlier than V100R008C00 support the antenna feeder
intermodulation test.
10.5 Diagnosing Fault
Added the description about the scenario options of fault

analysis.
Issue 08 (2014-06-09)

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

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

Event Log
10.9.4 Looping Back the
Interface Board Port
Added the descriptions of the board types supported by

the function.
10.9.5 Looping Back the

Interface Board Port Timeslot
10.9.3 Querying the Optical
Interface Board Port
Information
11.6 Querying BTS Running
Status
Added the function of querying cell management

status in the Select Status area.
7.2.5 DHCP Tracing
Changed PID to DHCP Product ID.
Added the description about how the states of

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

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

filer manager to downloading the certificate by the FTP
client.
Compared with Draft A (2013-02-27), this issue does not exclude any topics.
Draft A (2013-02-27)
This is the Draft A release of V100R015C00.
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
Introduction to LMT
About This Chapter

The Local Maintenance Terminal (LMT) is a web-based application that provides a graphical
user interface (GUI) for users for easy operation and maintenance of the BSC6910. Users can
perform operations such as alarm management, trace management, performance monitoring,
and device maintenance. Users can also run MML commands and read the corresponding
execution results on the LMT.
2.1 Configuration Requirements of the LMT PC
The computer on which the LMT is running is called the LMT PC. The LMT PC must meet the
following requirements related to hardware, software, connection ports, and communication
capability.
2.2 Logging In to and Logging Out of the LMT
This section describes how to log in to the LMT for operations and how to log out of it after the
operations are complete.
2.3 Components of the LMT Window
You can log in to the LMT through a web browser to operate and maintain the BSC6910.
2.4 LMT Software
The Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMT
Offline Tools, Convert Management System, Performance Browser, and TrafficRecording
Review Tool.
User-defined Command Group is used to add commands to a specified command group so that
an admin user can add operation authorities for authority-limited users.
2.6 File Manager
The file manager, which is a component of the LMT application, helps you upload files from
the LMT to the OMU and download files from the OMU to the LMT. Its functions are similar
to those of the FTP client. For example, you can obtain logs and upload data configuration files.
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
2.1 Configuration Requirements of the LMT PC

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

operating system
Simplified Chinese or English

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

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

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

Flash Player
Flash Player 11.1.102 is recommended.
NOTE
The plug-in can be obtained on LMT login window.
NOTE
The plug-in can be obtained on LMT login window.
NOTICE
l You are advised to run the LMT on a PC with the recommended configurations to ensure
stable operation.
l The LMT in the current version can be used only in the 32-bit operating system and with the
32-bit Web explorer.
l Ensure that the browser window is zoomed at 100% level when you are using the LMT.
Otherwise, the layout of the LMT interface may be abnormal. If the layout of the LMT
interface is abnormal, check whether the browser window is zoomed at 100% level by
viewing the scaling icon at the lower right corner of the IE browser window.
Requirements of Connection Ports

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

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

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

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

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

This section describes how to log in to the LMT for operations and how to log out of it after the
operations are complete.
Context
l
You have installed the JAVA Platform Standard Edition Runtime Environment (JRE)
program before using the LMT. If no JRE plug-in is installed, a message is displayed when
you log in to the LMT, prompting you to install the plug-in. Follow the instructions to install
the plug-in. If the JRE plug-in on the LMT PC is not the latest version, a message is
displayed, prompting you to upgrade the plug-in version. In this case, you are advised to
uninstall the existing JRE plug-in and then install a new version. If you cannot log in to the
LMT after you upgrade the JRE program, restart the web browser and retry.
A maximum of 32 local users and EMS users can log in to the LMT.
CAUTION
When the LMT is running, do not modify the system time and time zone. Otherwise, severe
errors may occur in the system. Close the LMT window before you modify the system time and
time zone.
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
NOTICE
l Do not use refresh the browser on the LMT. Refreshing the main page, you will be logged
out of the LMT. Refreshing the tracing or monitoring page, a message indicating a script
error will be displayed.
l If you log in to the LMT through the IE browser, do not modify any file folder properties.
Otherwise, the IE browser is automatically refreshed, and error occurs on the LMT.
l Before logging in to the LMT through the IE browser, enable the IE browser to support HTTP
1.1 as follows: In the IE browser, choose Tools > Internet Options > Advanced > HTTP
1.1 Setting and select Use HTTP 1.1. If the IE browser is configured with login to the LMT
through a proxy server, select Use HTTP 1.1 through proxy connection.
l Before logging in to the LMT in the Internet Explorer (IE) browser, perform the following
operations:
l Choose Tools > Internet Options in the IE browser and click the Privacy tab in the
Internet Options dialog box. On the Privacy tab page, move the slider in the Settings
field to the middle until Medium is displayed on the right of the slider. Then, click
Sites. The Per Site Privacy Actions dialog box is displayed. In the Address of Web
site text box, enter the IP address of each website that is allowed to use cookies, and click
Allow.
l You are also advised to perform the following operations: Choose Tools > Internet
Options in the IE browser and click the General tab in the Internet Options dialog box.
Clear the Delete browsing history on exit check box on the General tab page.
l If the LMT is active in the IE6 browser and you choose Start > Run to start the FTP server,
the IE browser closes the LMT window and goes to the login window of the FTP server
directly. To avoid this problem, set the IE browser as follows: choose Tools > Internet
Options. In the Advanced tab page, deselect Reuse windows for launching shortcuts from
the Browsing options.
l If colors cannot be displayed in the LMT window, set the IE6 browser as follows: choose
Tools > Internet Options. In the General tab page, click Accessibility. Then, in the
Formatting area, deselect Ignore colors specified on Web pages.
l If AVG Internet Security is installed on an LMT PC, the web shield function must be disabled.
Otherwise, a dialog box will be displayed, showing "Disconnected. Please log in again."
Procedure
Step 1 Enter the LMT login page by using one of the following modes:
Issue 08 (2014-06-09)

BSC6910 GSM
LMT User Guide
Mode
Mode
Description
Operation
Mode 1: direct
connection
The LMT directly

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

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

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

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

browser by using the following method: Choose
Tool > Internet Options on the tool bar of the
browser. In the Connection tab page, click LAN
Settings. Then specify the IP address and port
number of the M2000 server in the Proxy
server area. The default port number is 80.
2. Type the external virtual IP address of the OMU
in the Address bar of the browser. Press Enter
on the keyboard, or click Go next to the Address
bar to enter the login window of the BSC6910.
Type "M2000_IP/OMU_IP/" (for example,
10.141.130.146/10.141.151.208/) or "http://
M2000_IP/OMU_IP/login.html" in the Address bar
of the IE browser. Press Enter on the keyboard, or
click Go next to the Address bar to enter the login
window of the BSC6910. Note that "/" must be
included in "M2000_IP/OMU_IP/" behind
"OMU_IP." If another proxy server is already set,
you need to add M2000_IP to the IP addresses that
do not use the proxy server under Exceptions.
NOTE
OMU_IP indicates the external virtual IP address of the
OMU and M2000_IP indicates the IP address of the
M2000 server.

10
BSC6910 GSM
LMT User Guide
NOTE
l When you are logging in to the LMT using the second or third method, settings on the M2000 and on the
NE side must be consistent with the setting mapping listed in the following table. Otherwise, the login fails.
l You can run the LST WEBLOGINPOLICY command to query the policy for login to LMT and data
transmission.
l For details about querying and configuring the M2000 security connection mode, see section Configuring
M2000 Security Connection in M2000 Commissioning Guide.
M2000 Security Connection Mode
Policy for Login to LMT and Data

Transmission
Common Mode
Only COMPATIBLE(Both HTTP and

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

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

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

l Set User Type to Local or EMS.
l If the verify code is illegible, click Refresh for a new code.
l It is recommended that you change the password at your first login and then change the
password every three months.
Step 3 Click Login.
NOTE
l Before logging in to the BSC6910 as an EMS user, you need to set up a connection between the
BSC6910 and the M2000 server.
l If the login fails, click Reset. Specify User Name, Password, and Verify Code again to log in. If the
login fails again, check whether the connection between the LMT and the OMU is normal.
Step 4 Optional: To lock the LMT window, click Lock in the top right corner of the LMT main page.
Step 5 To exit the LMT, click Logout in the top right corner of the LMT main page.
Issue 08 (2014-06-09)

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

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

12
BSC6910 GSM
LMT User Guide
Table 2-4 Components of the LMT window

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

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

Window.
Progress tab
You can click the tab to display the progress of a task. eGBTS does
not support this function.
NOTE
To display the Progress tab page, click Progress on the toolbar. Then,
double-click an entry to view the detailed information. The Progress
Management dialog box is displayed, listing the detailed progress report.
Issue 08 (2014-06-09)
FTP Tool
You can click it to download the executable application file

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

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

13
BSC6910 GSM
LMT User Guide
Component
Description
Obtain
Documentation List
Choose Obtain Documentation List on the LMT. The

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

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

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

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

page to display LMT help information.
l Press F1 or click Help on the LMT main page to display

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

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

15
BSC6910 GSM
LMT User Guide
2.4 LMT Software

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

This section describes how to install the LMT offline tools on the LMT PC.
Prerequisites
l
A valid serial number for the LMT software is obtained.
The PC for installing the LMT offline tools complies with the specifications mentioned in
2.1 Configuration Requirements of the LMT PC.
Using setup disk
Procedure
1.
Use the administrator account to log in to the LMT PC.
2.
Insert the setup disk into the CD-ROM drive.

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

l If the LMT of another version or NE has been installed, the installation path is that of the
original LMT software and cannot be altered.
l To alter the installation path, you must uninstall the existing LMT software.
If an LMT software is running, a Warning dialog box is displayed. Click Yes to enable the
system to automatically exit the LMT application. Click No to manually exit the LMT
application.
Issue 08 (2014-06-09)
7.
Select the software components and then click Next. It is recommended that you select
all components. A dialog box is displayed for entering the CD-KEY.
8.
Enter the CD-KEY correctly, and then click Next. A dialog box is displayed, asking
you to confirm the installation.
9.
Confirm the installation parameters and click Next. A dialog box is displayed,
indicating the progress of copying the files.
16
BSC6910 GSM
LMT User Guide
When the task of copying files is complete, a dialog box is displayed for initializing
components. When all programs are installed, a dialog box is displayed, indicating
the completion of the installation.
10. Click Finish.
NOTE
The installation is complete. When the installation is complete, the LMT Service Manager starts
automatically.
Using installation package of the LMT offline tools

You can also contact Huawei engineers to download the installation package of the LMT
offline tools from http://support.huawei.com by performing the following operation: Log
in to the website, and then choose Support > Software Center > Version Software >
Wireless Product Line > SingleRAN > MBSC > BSC6910. Then, select the required
software version to download. After downloading the LMT offline tools, you need to check
the integrity of the LMT offline tools by using Hash values. To check the integrity of the
LMT offline tools, perform the following steps:
1.
Download the Hash compressed package (with the name "Product Version
Number Hash List.rar") from the same directory as the installation package of the
LMT offline tools. The Hash compressed package contains the file "Product Version
Number Hash List.mht". Decompress the Hash compressed package to obtain this
file. Then, open this file to obtain the Hash value for the installation package of the
LMT offline tools. The SHA-256 column in Figure 2-2 shows the calculated Hash
value.
Figure 2-2 Hash value for the installation package of the LMT offline tools
2.
Contact Huawei engineers to download the Hash value calculation tool by performing
the following operation: Log in to the website http://support.huawei.com. Choose
Software Center > Version Software > Wireless Product Line > Single RAN >
SRAN O&M tools. Then, download the Hash value calculation tool
hashmyfiles-1.8.5.rar.
3.
Decompress hashmyfiles-1.8.5.rar to obtain HashMyFiles.exe. Run

HashMyFiles.exe. Choose file > Add Files. In the displayed dialog box, choose the
installation package of the LMT offline tools. The SHA-256 column in Figure 2-3
shows the calculated Hash value.
Figure 2-3 Hash value calculated by the Hash value calculation tool
Issue 08 (2014-06-09)

17
BSC6910 GSM
LMT User Guide
4.
Compare the Hash values obtained in Step 1 and Step 3. If the Hash values are the
same, the installation package of the LMT offline tools is complete, and you can
continue subsequent operations. If the Hash values are different, contact Huawei
engineers.
----End
2.4.2 FTP Client

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

18
BSC6910 GSM
LMT User Guide
Table 2-6 Components of FTP client interface

Number
Component
Description
Menu bar
Provides the menus for the operation of the system.
Tool bar
Provides the shortcut icons for the operation of the

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

port number, and mode in this area.
NOTE
To query the port number, run the LST FTPSSRV
command to query the setting for the Command Port of
FTPS Server. If an incorrect port number is used, the LMT
cannot be connected to the FTP server.
Local directory list

window
Displays the directory structure of the current

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

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

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

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

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

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

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

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

NOTE
You are only allowed to visit files under the directory when using the FTP
client.
Port number
Indicates the number of the port used by the FTP server to intercept
the information on the network.
NOTE
To query the port number, run the LST FTPSSRV command to query the
setting for the Command Port of FTPS Server. If an incorrect port number
is used, the LMT cannot be connected to the FTP server.
Issue 08 (2014-06-09)

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

server simultaneously.
2.4.4 LMT Offline MML

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

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

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

21
BSC6910 GSM
LMT User Guide
Table 2-8 Description of the LMT offline MML server

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

NOTE
l Click Hide to minimize the LMT offline MML server to the bottom
right corner of the LMT PC.
l Click Stop to stop the LMT offline MML server.
l Click Start to start the LMT offline MML server.
l Click Open Browser to enter the login window of LMT offline MML.
Config tab
Click it to configure the server port.
About tab
Displays information about LMT offline MML.
Logging In to and Out of LMT Offline MML Tool

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

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

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

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

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

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

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

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

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

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

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

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

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

offline MML.
Making MML Scripts Offline

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

24
BSC6910 GSM
LMT User Guide
2.4.5 Convert Management System

The Convert Management System is a component of the LMT offline tool. It enables
communication between the OMU and the alarm box and is used to transfer the alarm
information, alarm box control information, and alarm box status information. The Convert
Management System must be started to connect the LMT to the alarm box. The Convert
Management System communicates with the OMU through the Ethernet port and to the alarm
box through the serial port.
Function
The Convert Management System performs the following functions:
l
Forwards the alarm operation instructions from the LMT.
Forwards the alarm information to the alarm box.
Detects the real-time status of the connection between the LMT and the OMU and that
between the LMT and the serial ports of the alarm box, and reports the alarms if any.
Startup
NOTE
The Convert Management System cannot start if Microsoft Visual C++ 2005 SP1 Redistributable Package
(X86) is not installed on the LMT PC. Download this package from www.microsoft.com.
Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Convert
Management System on the LMT PC.
Interface
Figure 2-8 shows the interface of the Convert Management System.
Figure 2-8 Interface of the Convert Management System
Issue 08 (2014-06-09)

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

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

Convert Management System.
2.4.6 Performance Browser Tool

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

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

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

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

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

performance file.
2.4.7 TrafficRecording Review Tool

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

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

system.
Service data retrieval

window
Provides the data related to the trace and monitor

tasks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

31
BSC6910 GSM
LMT User Guide
Path Switch Area

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

This area lists all file directories that can be viewed and operated by users on the server. After
right-click on a selected folder, a short-cut menu containing items Refresh Whole Folder
Tree, Set Search Criteria, and Delete Search Criteria is displayed.
l
You can refresh the folder tree by clicking Refresh Whole Folder Tree to obtain the latest
folder organizations.
If you choose Set Search Criteria, the Set Search Criteria dialog box is displayed, as
shown in Figure 2-14. Select the required search criteria, enter the correct search criteria,
and then click Confirm. The search criteria setting is complete.
Figure 2-14 Set Search Criteria dialog box
Modified time: The value range is from 2000 to 2038. If both Start time and End
time are set, the value of End time must be greater than the value of Start time.
Files can be searched by File name. The file name has a maximum of 50 bytes containing
only English letters, numbers, dots ., and underscores _.
Issue 08 (2014-06-09)

32
BSC6910 GSM
LMT User Guide
NOTE
l For easy differentiation, the icon of the folder for which the search criteria has been set is
displayed as
l After the search criteria is applied, only files meeting the search criteria under the folder are
displayed in the file manager.
l The search criteria takes effect only for the current folder, not its sub-folders.
l If no search criteria is selected, all files will be displayed after Confirm is clicked, similar to the
result of clicking Delete Search Criteria.
You can delete the search criteria set for a folder by clicking Delete Search Criteria.
File List Area

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

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

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

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

34
BSC6910 GSM
LMT User Guide
Management of Operation Rights
About This Chapter

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

35
BSC6910 GSM
LMT User Guide
3.1 Concepts Related to Operation Rights Management

3.1.1 Principles of Operation Rights Management

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

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

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

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

All users can change their own password. The admin, ADMINISTRATOR-level, and authorized
CUSTOM-level users can change the passwords of all external user accounts. Only the admin
user can change the password of the admin account.
For details, see 3.3.3 Changing the Password of the Active User Account and 3.3.4 Changing
the Password of an External User Account.
Issue 08 (2014-06-09)

36
BSC6910 GSM
LMT User Guide
3.1.3 Command Group

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

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

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

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

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

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

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

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

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

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

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

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

37
BSC6910 GSM
LMT User Guide
3.1.4 User Type

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

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

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

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

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

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

G_4, G_5, G_6,
G_7, G_8, G_9,
G_10, G_11,
G_12, G_13,
and G_14
l Operation rights of USERlevel
OPERATOR
Issue 08 (2014-06-09)
l System OM
l Data configuration

38
BSC6910 GSM
LMT User Guide
Level
Assigned
Command
Group
Operation Right
ADMINISTRA
TOR
G_0, G_1, G_2,

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

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

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

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

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

39
BSC6910 GSM
LMT User Guide
Table 3-3 Examples of operation time limit settings

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

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

Sundays
No operation time limit. The

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

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

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

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

40
BSC6910 GSM
LMT User Guide
3.2.2 Modifying an External User Account

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

This section describes how to delete an external user account. Only the admin,
ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.
Prerequisites
Context
NOTICE
The admin account is the permanent built-in user account and cannot be deleted.
Procedure
Step 1 Run the RMV OP command to delete an external user account.
----End
3.3 Management of User Passwords

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

41
BSC6910 GSM
LMT User Guide
3.3.1 Defining Login Password Policies

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

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

This section describes how to change the password of the active user account. The new password
takes effect from the next login.
Prerequisites
Procedure
Step 1 Click Password on the tool bar of the LMT main page. The Password dialog box is displayed.
Step 2 In the displayed Change Password window, enter the current password in the Old Password
field. Enter the new password in the New Password and Confirm Password fields. Then click
OK.
NOTE
It is recommended that you change the password at your first login and then change the password every three
months.
----End
Issue 08 (2014-06-09)

42
BSC6910 GSM
LMT User Guide
3.3.4 Changing the Password of an External User Account

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

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

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

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can rename
the command groups.
Prerequisites
Procedure
Step 1 Run the LST CCGN command to query the name of a command group.
Step 2 Run the SET CCGN command to rename a command group.
----End
Issue 08 (2014-06-09)

43
BSC6910 GSM
LMT User Guide
3.4.3 Changing the Commands in a Command Group

Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can change
the contents of command groups.
Prerequisites
Procedure
l
Run the ADD CCG command to add commands to a command group.
Run the RMV CCG command to remove commands from a command group.
----End
Issue 08 (2014-06-09)

44
BSC6910 GSM
LMT User Guide
Running MML Commands
About This Chapter

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

45
BSC6910 GSM
LMT User Guide
4.9 Undoing/Redoing Multiple Data Configuration Actions

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

46
BSC6910 GSM
LMT User Guide
4.1 Concepts Related to MML Commands

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

This section describes the MML commands that can be used for operation and maintenance of
the BSC6910.
An MML command consists of two parts: action and object. For example, ADD OP, wherein
ADD is the action and OP is the object. Table 4-1 describes the actions that can be performed
through MML commands.
Table 4-1 Actions of the MML commands
Issue 08 (2014-06-09)
Action
Description
ACT
Activate
ADD
Add
ADT
Audit
BEG
Begin
BKP
Back up
BLK
Block
CHK
Check
CLR
Clear
CMP
Compare
COL
Collect
CON
Confirm
DEA
Deactivate
DSP
List
EST
Establish
EXP
Export
FMT
Format
FOC
Obtain
INH
Inhibit
47
BSC6910 GSM
LMT User Guide
Action
Description
INS
Install
LCK
Lock
LOD
Load
LOP
Loopback test
LST
List
MOD
Modify
PING
Ping
REL
Release
REQ
Request
RUN
Run
RMV
Remove
RST
Reset
SET
Set
STR
Start/Open
STP
Stop/Close
STA
Collect statistics
SWP
Swap
SYN
Synchronize
TRC
Trace
UBL
Unblock
UIN
Uninhibit
ULD
Upload
ULK
Unlock
4.1.2 Components of the MML Command Window

This section describes the components of the MML command window.
Figure 4-1 shows the MML command window.
Issue 08 (2014-06-09)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

52
BSC6910 GSM
LMT User Guide
4.3.1 Immediate Batch Processing of MML Commands

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

This section describes how to enable the system to automatically run a batch of MML commands
in a batch file at a moment of a day specified by an operator in advance.
Prerequisites
l
You have obtained FTP user name and password.
Procedure
Step 1 Edit a batch file.
1.
Click Batch on the LMT main page. The Batch tab page is displayed.
2.
Click New and type a batch of MML commands in the input box.
3.
Click Save to save the edited batch file.
Step 2 Upload the MML command script file to the /ftp directory in the OMU active work area. Assume
that the MML command script file BATCHFILE.txt saved in disk D is uploaded to the /mbsc/
bam/version_a/ftp directory in the OMU active work area. When the active workspace of the
OMU is version_a, the following path changes into version_a. When the active workspace of
the OMU is version_b, the following path changes into version_b accordingly. There are the
following two upload ways:
Issue 08 (2014-06-09)

53
BSC6910 GSM
LMT User Guide
l Through File Manager on the LMT

1.
Start File Manager by referring to File Manager.
2.
Choose Root > bam > version_a > ftp in the left area of the displayed window to
navigate to the ftp directory. Then click Upload.
3.
In the displayed Select Upload File dialog box, select the BATCHFILE.txt file saved
in local disk D and click Open to upload the file.
l Through command lines

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

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

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

This section describes how to use the batch processing assistant function. You can use the
function to check the format of MML commands in the assistant input area, correctness of the
parameters BTSID, CELLID, and TRXID, and relationship between the parameters. You can
also use the function to add MML commands to a batch file or directly overwrite the original
batch file.
Prerequisites
l
The batch file is ready.
Issue 08 (2014-06-09)

54
BSC6910 GSM
LMT User Guide
Context
The editing area for the batch assistant allows 20 lines of commands at most. The batch assistant
supports only the MML commands that contain the parameters BTSID, CELLID, and TRXID.
The parameters can be typed according to the following forms: id1, [id1], [id1, id2, id3], [id1idn], all.
Assume that a BSC is configured with six BTSs whose IDs are 1, 2, 3, 4, 5, and 6 respectively.
The following table takes the LST BTS command as an example to illustrate the function of the
batch processing assistant.
Command Typed in the Batch
Processing Assistant Input Area
Generated MML Command
LST BTS: LSTTYPE=BYBTSID,

BTSID=2;

BTSID=2;
LST BTS: LSTTYPE=BYBTSID, BTSID=

[4];

BTSID=4;

[1,3];

BTSID=1;
BTSID=3;

[2,4,6];

BTSID=2;
BTSID=4;
BTSID=6;

[1-4];

BTSID=1;
BTSID=2;
BTSID=3;
BTSID=4;

[3-5];

BTSID=3;
BTSID=4;
BTSID=5;
Issue 08 (2014-06-09)

55
BSC6910 GSM
LMT User Guide
Command Typed in the Batch

Processing Assistant Input Area
Generated MML Command

BTSID=all;

BTSID=1;
BTSID=2;
BTSID=3;
BTSID=4;
BTSID=5;
BTSID=6;
Procedure
Step 1 Click Open Assistant to enable the batch processing assistant function.
Step 2 Enter the batch command in the displayed manual editing area. Click Generate MML. The
batch processing assistant automatically checks the format of the command, the correctness of
the parameters BTSID, CELLID, and TRXID, and the relationship between these parameters.
Step 3 If no error occurs, directly go to Step 4. If an error occurs, a message is displayed. Click OK,
and the assistant will rectify the incorrect MML command automatically.
Step 4 The Batch dialog box is displayed. Click Add or Overwrite to add a correct MML command
to the editing area.
----End
4.3.4 Syntax Check

This section describes how to check syntax of the MML commands before running a batch of
MML script commands. This function helps locate incorrect commands, improving maintenance
efficiency.
Prerequisites
l
A batch file is ready.
Context
The syntax check checks the following types of error:
l
Missing colon
Missing semicolon
Issue 08 (2014-06-09)

56
BSC6910 GSM
LMT User Guide
Incorrect MML command
No authority to execute a correct MML command
Redundant parameters
Incorrect parameters
Procedure
Step 1 Click New to create a batch file. Edit MML commands in the command editing area.
NOTE
You can click Open... to open an edited batch file.
Step 2 Click Analyze Syntax to check syntax of the batch file.

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

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

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

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

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

This section describes how to determine if the data configuration mode of the BSC6910 system
is effective or non-effective.
Prerequisites
Context
In effective mode, the data configured takes effect immediately on the BSC6910 system.
In non-effective mode, the data configured for the subrack takes effect only in the OMU and not
on the subrack. In this case, you can run the SET CFGDATAEFFECTIVE command to set
the mode to effective mode, run the FMT DATA command to generate the data configuration
file for the subrack, and then run the RST SUBRACK command to reset the subrack. In this
way, the subrack can load the data configuration from the OMU so that the data takes effect on
the subrack.
When the BSC6910 system is in non-effective mode, you cannot query, compare, or perform
CRC check on the data between the host and the OMU. In addition, you cannot configure the
host data of the subrack.
Issue 08 (2014-06-09)

58
BSC6910 GSM
LMT User Guide
When the BSC6910 system are in non-effective mode, license verification is not performed.
When the BSC6910 system is switched from the non-effective mode to the effective mode, the
OMU checks whether the data configuration exceeds the limitations of the license. If the data
configuration exceeds the limitations of the license, the mode switching is not allowed.
NOTE
You can query the data configuration through menu operations or through MML commands.
Procedure
l
Through menu operations

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

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

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

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

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

59
BSC6910 GSM
LMT User Guide
4.7 Obtaining Data Configuration Rights

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

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

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

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

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

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

This section describes how to undo and redo multiple data configuration actions.
Prerequisites
l
You have obtained configuration rights (by running the LCK CMCTRL command).
The quick configuration mode is disabled by running the SET QUICKCFG command.
Issue 08 (2014-06-09)

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

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

62
BSC6910 GSM
LMT User Guide
Alarm/Event Management
About This Chapter

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

63
BSC6910 GSM
LMT User Guide
5.1 Concepts Related to Alarm Management

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

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

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

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

64
BSC6910 GSM
LMT User Guide
Table 5-2 describes the four severities of alarms.

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

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

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

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

time. Otherwise, the
system may fail to
perform some major
functions.
Minor
Reporting faults that are not serious enough to

affect the QoS. These alarms can be handled as
required or further observed to prevent them from
becoming critical. For example, you need clear
the obsolete history alarms.
Find and rectify any

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

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

The alarms can be classified into 15 types based on different event type.
l
Power: alarms related to the power system
Environment: alarms related to equipment room environment, such as temperature,

humidity, and door sensor
Signaling: alarms related to the signaling system
Trunk: alarms related to the trunk system, including trunk circuits and trunk boards
Hardware: alarms related to board hardware, such as clock and CPU
Software: alarms related to software
Running: alarms generated during the operation of the BSC
Communication: alarms related to the communication system, such as alarms between the
BSC6910 host and the OMU
QoS: alarms related to QoS
Integrity: alarms generated when information is repeated, lost, distorted, disordered, or

unexpected
Issue 08 (2014-06-09)

65
BSC6910 GSM
LMT User Guide
Operational: alarms related to refusal of operations that are generated when a service is
refused or unavailable, or when an operation procedure is improper
Physical: alarms related to cable interference or detection of invasion
Security: alarms related to violation of security such as failed authentication, breach of

confidentiality, failed non-repudiation, and unauthorized visit
Time domain: alarms related to timeout such as information delay and password expiration
Processing error: alarms caused by other abnormal conditions
5.1.4 Alarm Flag

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

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

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

BSC6910 uses the Huawei universal alarm box. The BSC6910 alarm box provides audible and
visual indications based on the alarm severity. It is optional and the BSC6910 can be configured
with only one alarm box. For details, see the documents delivered with the alarm box.
Figure 5-1 shows the alarm box.
Figure 5-1 Alarm box
When the BSC6910 reports a fault alarm to the LMT, the alarm box provides audible and visual
indications based on the alarm severity. When the LMT receives the fault alarm, the alarm box
generates a sound. The sound stops when the alarm is cleared. You can also manually stop the
sound on the LMT.
Issue 08 (2014-06-09)

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

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

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

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

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

68
BSC6910 GSM
LMT User Guide
5.3.1 Creating an Alarm Filter

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

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

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

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

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

This section describes how to set the filter of the BSC6910 derived alarms. You can set the filter
of the derived alarms to ON or OFF. Only the admin, OPERATOR-level, ADMINISTRATORlevel, and authorized CUSTOM-level users can perform this operation.
Prerequisites
l
You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration
Rights).
Procedure
Step 1 Run the SET ALMML command to enable or disable the filter of the derived alarms.
----End
5.4.2 Querying the Filter of Derived Alarms

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

70
BSC6910 GSM
LMT User Guide
5.5 Monitoring Alarms

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

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

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

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

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

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

72
BSC6910 GSM
LMT User Guide
Context
The LMT provides the following help information for all alarms:
l
Alarm meaning
Alarm impact
System action
Solution
Procedure
Step 1 In the Alarm/Event tab page, double-click an alarm in the Browse Alarm/Event or Query
Alarm/Event Log tab page. The Detail dialog box is displayed.
Step 2 In the Detail dialog box, click Solution.... The online help window is displayed.
NOTE
You can also click to select an alarm. Then right-click the alarm and choose Solution from the shortcut
menu to view the online help of this alarm.
Step 3 Find the handling suggestions or other required information in the online help.
Step 4 To exit the online help, click the Close button of the help window.
----End
5.5.4 Querying Alarm/Event Configuration

This section describes how to query alarm/event configuration.
Prerequisites
Context
You can set the following search criteria:
l
Alarm ID: indicates the ID range of alarms to be queried. If the setting is successful, query
results show configuration of alarms/events only in the range.
Alarm Severity: indicates the Alarm Severity. If the setting is successful, query results
show configuration of alarms/events of only the specified severity. If none of the alarm
severities is selected, query results show configuration of alarms/events of all severity
options.
Modification Flag: indicates the Modification Flag. If the setting is successful, query
results show configuration of alarms/events matching the specified modification flag. If
All is selected, query results show configuration of alarms/events whose Modification
Flag is set to Unmodified or Modified.
Shield Flag: indicates the Shield Flag. If the setting is successful, query results show
configuration of alarms/events matching the specified shield flag. If All is selected, query
results show configuration of alarms/events whose Shield Flag is set to Shielded or
Unshielded.
To Alarm Box Flag: indicates the To Alarm Box Flag. If the setting is successful, query
results show configuration of alarms/events matching the specified flag. If All is selected,
Issue 08 (2014-06-09)

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

This section describes how to filter alarms by sites and specific filter options on the Browse
Alarm/Event tab page. All the alarms, however, are reported to the LMT and saved on the OMU.
Prerequisites
Procedure
Step 1 Click Alarm/Event on the LMT. The Alarm/Event tab page is displayed.
Step 2 On the Browse Alarm/Event tab page, click Filtrate Setting. The Set Alarm Filtering
Conditions dialog box is displayed.
Step 3 In the Set Alarm Filtering Conditions dialog box, specify Alarm Source or Alarm ID. Then
click OK. Alarms that meet the specified conditions are displayed.
NOTE
l Setting Alarm Source Type displays alarm sources of the selected type in the box below.
l You can manually type an alarm source in Selected Source.
l You can manually type an alarm source in Selected Source after selecting Alarm Source Type. Association
display is supported in the input box under Selected Source. For example, if you type 3, all alarm sources
of the source type starting with 3 are displayed in the box under Selected Source.
----End
5.5.6 Setting Display Attributes for Alarms/Events

This section describes how to set the display attributes for alarms and events in the Setting dialog
box. After you set the display attributes, the settings take effect on alarms/events on the following
Issue 08 (2014-06-09)

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

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

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

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

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

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

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

76
BSC6910 GSM
LMT User Guide
5.5.7 Manually Clearing an Alarm/Event

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

1.
Click Alarm/Event and select an uncleared alarm that needs to be cleared in the
Browse Alarm/Event or the Query Alarm/Event Log tab. Click Clear Alarm. The
Confirm dialog box is displayed.
2.
Click OK in the Confirm dialog box. "Manually cleared" is displayed in the Cleared
Type column.
NOTE
You can also perform the operation through the shortcut menu. Click Alarm/Event and right-click an
uncleared alarm that needs to be cleared in the Browse Alarm/Event or Query Alarm/Event Log tab.
Choose Clear Alarm from the shortcut menu.

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

This section describes how to delete alarms/Events when browsing alarms or querying alarm/
Event logs.
Prerequisites
Procedure
Step 1 In the Browse Alarm/Event or Query Alarm/Event Log tab page under the Alarm/Event tab,
click Delete Selected Cleared Alarms or Delete All Cleared Alarms to delete the alarms as
required. Table 5-3 describes the functions of the buttons.
Table 5-3 Functions of the buttons
Issue 08 (2014-06-09)
Option
Description
Delete Selected Cleared

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

77
BSC6910 GSM
LMT User Guide
Option
Description
Delete All Cleared

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

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

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

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

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

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

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

This section describes how to reset the alarm box, stop the alarm sound, and turn off the alarm
LED.
Prerequisites
l
Run the RST ALMBOX command to reset the alarm box.
Run the CLR BOXLGT to manually turn off the alarm LEDs.
Run the STP BOXSND command to stop the alarm sound.
Procedure
----End
Issue 08 (2014-06-09)

79
BSC6910 GSM
LMT User Guide
5.6.4 Querying the Alarm Box Filter Level

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

80
BSC6910 GSM
LMT User Guide
6 Log Management
Log Management
About This Chapter

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

81
BSC6910 GSM
LMT User Guide
6 Log Management
6.8 Obtaining Running Logs

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

82
BSC6910 GSM
LMT User Guide
6 Log Management
6.1 Log Types

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

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

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

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

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

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

84
BSC6910 GSM
LMT User Guide
6 Log Management
Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. The
FTP Client is started.
Step 3 In the server entry bar on the FTP Client, enter the external virtual IP address of the OMU, the
FTP user name, and the password.
NOTE
The FTP user name and password is set when the OMU is installed. The FTP user name is FtpUsr by
default.
Step 4 Click Enter to connect the OMU. The connecting status is displayed in the Connection tips
pane.
Step 5 After the connection is successful, in the server file list pane, double-click OMU active
workspace installation directory\ftp. The server file list pane displays the files in the directory.
Step 6 Based on the file name, double-click the operation log file to download it to the LMT PC.
Step 7 When the download is complete, choose System > Exit or click the close button to exit the FTP
Client.
----End
6.6 Querying Security Logs

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

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

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

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

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

86
BSC6910 GSM
LMT User Guide
6 Log Management
NOTE
l The running log is named in the format BSCID_subrack number/Log/yyyy/mm/dd/hh/

mm/ss.zip. For example, if a running log of Extended Processing Subrack (EPS) 3 is
uploaded to the OMU of BSC 1 at 17:19:47 of November 7, 2011, the log is named
BSC0001_03Log20111107171947.zip. BSC0001_03Log20111107171947.zip indicates
that the log has been uploaded and compressed. BSC0001_03Log20111107171947.tmp
indicates that the log is being uploaded.
l By default, the uploaded running logs are saved in bam\common\fam\famlog on the
OMU.
2.
Click File Manager on the LMT main page to start the file manager.
3.
In the File Navigation Area, choose corresponding nodes to navigate to bam

\common\fam\famlog. In the File List Area, select the running log uploaded in Step
1. Then, click Download to download the log to the LMT PC.
Using FTP Client

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

mm/ss.zip. For example, if a running log of EPS 3 is uploaded to the OMU of BSC 1 at
17:19:47 of November 7, 2011, the log is named BSC0001_03Log20111107171947.zip.
BSC0001_03Log20111107171947.zip indicates that the log has been uploaded and
compressed. BSC0001_03Log20111107171947.tmp indicates that the log is being
uploaded.
l By default, the uploaded running logs are saved in bam\common\fam\famlog on the
OMU.
2.
Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP
Client. The FTP Client is started.
3.
In the server entry bar on the FTP Client, enter the external virtual IP address of the
OMU, the FTP user name, and the password.
NOTE
The FTP user name and password are set when the OMU is installed. The FTP user name is
FtpUsr by default.
4.
Click Enter to connect to the OMU. The connecting status is displayed in the
Connection tips pane.
5.
After the connection is set up successfully, choose corresponding nodes to navigate

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

87
BSC6910 GSM
LMT User Guide
6 Log Management
6.9 Collecting Log Statistics

This section describes how to collect the log statistics for fault analysis. There are different types
of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installation
logs, remote upgrade logs, security logs, alarm logs and others.
Prerequisites
Procedure
Step 1 Run the COL LOG command. Set the required parameters to collect the corresponding log
statistics. For more description about logs, see Table 6-1.
NOTE
l When the active workspace of the OMU is version_a, the storage path of the following logs changes into
version_a. When the active workspace of the OMU is version_b, the storage path of the following logs
changes into version_b accordingly.
l The log files that are not compressed in the BZ2 format in the OMU active workspace installation directory
\common\fam\famlog and the OMU active workspace installation directory\common\fam
\famlogfmt directories will not be saved.
Table 6-1 Description about logs
Issue 08 (2014-06-09)
Type
File Path
Description
PFM_NOM_RESULT
(Normal Performance Result
File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Recording the normal-period

traffic statistics reported by
an NE to the M2000 for
summarizing the traffic
statistics.
PFM_RESULT
(Performance Result File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
Recording traffic statistics

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

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

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

definition file from the
M2000 to NEs. Used for
traffic analyzing.

88
BSC6910 GSM
LMT User Guide
6 Log Management
Type
File Path
Description
PFM_SWITCHS(Switch
Information for
Performance)
Reserved parameter value.
HISTORY_ALARM
(History Alarm File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
Recording alarms and events

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

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

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

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

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

version_a/ftp/
COLLOGINFO/
SINGLE-BAM/
Operation and status logs of

the OMU board. Used for
analyzing OMU faults and
status.
l Active/Standby Mode
Active OMU
/bam/version_a/ftp/
COLLOGINFO/
ACTIVE-BAM/
Standby OMU
/bam/version_a/ftp/
COLLOGINFO/
STANDBY-BAM/
Issue 08 (2014-06-09)

89
BSC6910 GSM
LMT User Guide
6 Log Management
Type
File Path
Description
OMU_SIM_LOG(The
Simple Log of OMU)
l Independent Mode: /bam/

version_a/ftp/
COLLOGINFO/
SINGLE-SIM-BAM/
Recording information same

as the OMU_LOG except
information about scheduled
tasks and the standby
workspace.
l Active/Standby Mode
Active OMU
/bam/version_a/ftp/
COLLOGINFO/
Active-SIM-BAM/
Standby OMU
/bam/version_a/ftp/
COLLOGINFO/
STANDBY-SIMBAM/
Issue 08 (2014-06-09)
BSC_CFG_MML(The Data
Configure File of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
ExportCfgmml/
Recording the BSC

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

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

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

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

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

information. Used for data
restoration.
MEM_DB_BAK(The
Backup File of the Database
in Memory)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
MemDbBak/
Backed up OMU
memory database. Used for
locating the inconsistency
between the memory
database and the MYSQL
database.
BTS_BASIC_INFO(The
Basic Information of Sites)
mbsc\bam\version_a\ftp
\COLLOGINFO\BTS-LOG
Recording basic information

of BTS boards, BTS
attributes, and BTS
compressed logs. Used for
analyzing basic BTS
information.

90
BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
6 Log Management
Type
File Path
Description
BTS_CHECK_LOG(The
Examination File of BTS)
\COLLOGINFO\BTS-LOG
Recording BTS logs,

including temperature logs,
board replacing logs,
compressed logs, normal
logs, and frequency scan
logs.
BTS_DEBUG_LOG(The
Debug File of BTS)
\COLLOGINFO\BTS-LOG
Recording BTS logs,

including temperature logs,
board replacing logs,
compressed logs, normal
logs, and frequency scan
logs.
BTS_CHR_LOG(The CHR
Log of BTS)
TRX_LOG(The TRX Log)
BTS_NET_TABLE(The Net
Table Information of BTS)
DEBUG_LOG(The
Common Debug Log)
/bam/common/fam/
famlogfmt/
Recording software running

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

information that is generated
before a board is abnormally
reset. Used for locating the
abnormal board reset.
HOST_LOG(The Running
Log of the Host)
/bam/common/fam/famlog/
Host operation logs.
2G_CHR_LOG(The CHR
Log for GSM)
/bam/common/fam/
famlogfmt/gchr/
Recording the occupied

system resources, status
change times, and signaling
of a call. Used for analyzing
whether the call procedure is
normal.
CHR_LOG(The CHR Log)
/bam/common/fam/
famlogfmt/
Recording abnormal
information at the transport
layer during the call of a
single user.

91
BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
6 Log Management
Type
File Path
Description
2G_UNILATERAL_CONNECT(The Unilateral
Connection Log for GSM)
/bam/common/fam/
famlogfmt/
Recording the duration of

and the system resources
used by the call with
problems such as one-way
audio and cross talk. Used for
analyzing the causes of voice
faults.
BSC_INFO(The Basic
Information of the BSC)
/bam/version_a/ftp/
COLLOGINFO/BSC-LOG/
Recording the BSC software

patch information, and the
bar code, software
information, hardware
information, loading
information, and license of
each board. Used for
checking whether the
software versions, data and
licenses of boards are correct.
GCSR_LOG(The CHR Log

for Single User of GSM CS)
/bam/common/fam/
famlogfmt/
Recording the basic

information of abnormal
calls, such as call initiating
time, site in which the call is
initiated, cell, and frequency
GPSR_LOG(The CHR Log

for Single User of GSM PS)
/bam/common/fam/
famlogfmt/gphr/
Recording the basic

information (such as cell
index, CGI, IMSI, and
TLLI), internal messages,
and messages over the Um,
Abis, and Gb interfaces for a
call. Used for locating faults
during a 2G PS call.
AIDG_LOG(A Interface
Dial Diagnose Log)
/bam/common/fam/
famlogfmt/
Recording the A interface

diagnose log generated
during dialing tests. Used for
locating the call problems
caused by transmission
failure on the A interface.
BIOS_LOG(BIOS Log)
/bam/common/fam/
famlogfmt/
BIOS system abnormal

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

access and call drops. Used
for analyzing the causes of
call access failures and call
drops.

92
BSC6910 GSM
LMT User Guide
6 Log Management
Type
File Path
Description
PCHR_LOG(PCHR Log)
/bam/common/fam/
famlogfmt/pchr
Recording detailed
information of each call,
including service access, call
release, handover, DCCC,
and signal quality. Used for
KPI analysis and as a
reference when handling user
complaints.
SYSFAULT_LOG
(SYSFAULT Log)
/bam/common/fam/
famlogfmt/sysfault/
Recording severe software/

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

93
BSC6910 GSM
LMT User Guide
7 Trace Management
Trace Management
About This Chapter

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

94
BSC6910 GSM
LMT User Guide
7 Trace Management
7.1 Concepts Related to Trace Management

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

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

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

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

1.
When you close a tracing task on the LMT, the LMT sends a binary command to the OMU
to delete the task.
2.
The OMU forwards the command to the specified board according to the task ID.
Issue 08 (2014-06-09)

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

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

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

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

This is an instant tracing mode. The tracing results are sent to the LMT PC from the OMU.
In this tracing mode, you can select Save File to save the tracing result file to the LMT PC
in .tmf format. The LMT analyzes the tracing result file and displays the analysis results
in the window.
Save to OMU
You can set Trace Period (OMU Time) for a tracing task in this mode. The tracing start
time and tracing end time refer to the time on the OMU. The tracing end time must be later
than the tracing start time. The tracing result file is saved on the OMU in .zip format and
is not sent to the LMT PC. The default save path is \mbsc\bam\common\fam\trace.
Report File
The tracing result file is temporarily saved on the OMU in .zip format. Then, it is transferred
to the specified directory on the LMT PC through the FTP server.
You can query the saved tracing result file according to the operations in Browsing Traced
Messages Offline.
Issue 08 (2014-06-09)

96
BSC6910 GSM
LMT User Guide
7 Trace Management
7.2 Device Commissioning

This section describes how to perform the device commission.
7.2.1 Tracing OS Messages

This section describes how to trace messages between the exchange module of the OMU and
internal modules of a board or between internal modules of different boards.
Prerequisites
Context
This task can be performed to trace the sent and received messages between two modules or
messages sent from and received by the same module.
NOTICE
Only ADMINISTRATOR-level users are authorized for performing Tracing OS Messages
because it involves private information of users.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab page is displayed.
Step 2 On the Trace Navigation Tree pane, expand Trace > Device Commissioning. Double-click
OS Trace.
Step 3 In the OS Trace dialog box, set the parameters as required, and click Submit. The trace data
pane displays the traced message flow.
l Trace Type: You can set this parameter to Trace Sender or Trace Receiver to trace the
messages sent or received by the sender or receiver, respectively.
l IP Type: You can set this parameter to All, OMU, or Specified IP. If this parameter is set
to All, you need to set Module Name. If this parameter is set to Specified IP, you need to
set Subrack No., Slot No., Subsystem No., and Module Name.
l Subrack No.: indicates the number of the subrack where the traced subsystem is located.
l Slot No.: indicates the number of the slot where the traced subsystem is located.
l Subsystem No.: indicates the number of the traced subsystem.
l Module Name: indicates the traced functional module.
----End
Issue 08 (2014-06-09)

97
BSC6910 GSM
LMT User Guide
7 Trace Management
7.2.2 Tracing Redirected Messages

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

This section describes how to capture packets and helps locate transmission channel
disconnection and packet loss by analyzing the packet header.
Prerequisites
l
The communication between the LMT and the BSC is normal.
The following problems can be located by capturing packets:
Context
the controller does not receive the packet.
After entering the interface board, the packet is discarded by the board without being
sent to other boards in the system.
The packet is sent to other non-interface boards, which then discard the packet.
Issue 08 (2014-06-09)

98
BSC6910 GSM
LMT User Guide
7 Trace Management
When packets are discarded between two boards or connection cannot be established
between two boards, you can check whether the correct packets are sent to and received by
interface boards and other boards in the system by capturing backplane packets. Then you
can quickly determine where the problem lies, which may be in an interface board or any
other board in the system.
The following types of packet capturing are supported:

Panel Ethernet packet capturing.
Backplane Ethernet packet capturing.
Panel Ethernet + backplane Ethernet packet capturing.
Only one packet tracing task can be started for each interface board at a time. Tracing of
multiple interface boards can be started simultaneously.
Only the header of the user plane packet can be captured, not including the payload of the
packet.
Procedure
Step 1 Click Trace on the LMT main page. The Trace tab is displayed.
Step 2 In the Trace Navigation Tree pane, choose Trace Management > Device Commissioning >
Packet Capture. The Packet Capture dialog box is displayed.
Step 3 In the Packet Capture dialog box, set parameters as required.
Step 4 Click Submit, to start capturing packets. For the specific capturing duration, see the value of
Trace Time (OMU time) in the Packet Capture interface.
NOTE
l Panel Ethernet packet capture and backplane Ethernet packet capture can be supported simultaneously. If
you only need to capture the panel Ethernet packet, set PortType(Inner) to Inner Invalid or set PortType
(Outer) to Outer Invalid.
l To capture panel Ethernet packets, set PortType (Outer) to Ethernet Frame, and set the parameters in the
Outer tab.
l To capture panel Ethernet packets, set PortType (Inner) to Ethernet Frame, and set the parameters in the
Inner tab.
Interface
Parameter
Description
Basic Mode: just enter the basic parameters (subrack number and physical slot number) to
start the packet capturing function. Therefore, this is defined as the basic mode.
Issue 08 (2014-06-09)
Subrack No
Indicates the number of the subrack which houses the interface board.
Physical Slot No
Indicates the number of the physical slot which houses the interface
board.
Port No
Indicates the number of the port on the interface board panel.
Scene Select
Indicates the scene under which packets are captured are differentiated
by protocol type.

99
BSC6910 GSM
LMT User Guide
7 Trace Management
Interface
Parameter
Description
Intercept Length
Each Ethernet frame captured (especially for long packets) is reduced to

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

Tagged: The data packet carries a VLAN ID.
Untagged: The data packet does not carry a VLAN ID.
Tagged&Untagged: The data packet carries or does not carry a VLAN
ID.
Trace Time
Start Time: The start time and end time of the trace task.
Trace Time (minute) : duration of the tracing task. The unit is minutes.
Advanced Mode: in addition to the basic parameters (subrack number and physical slot
number), several other parameters are required to start the packet capturing function, which
is defined as the advanced mode. The advanced mode supports panel Ethernet packet
capturing, backplane Ethernet packet capturing and panel Ethernet + backplane Ethernet
packet capturing.
PortType (Outer)
Indicates capturing of packets at the port of the interface board panel.

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

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

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

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

100
BSC6910 GSM
LMT User Guide
7 Trace Management
Interface
Parameter
Description
Outer Peer IP
Address
Specifies the peer IP address of the IP packet to be captured.

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

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

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

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

101
BSC6910 GSM
LMT User Guide
7 Trace Management
Interface
Parameter
Description
Inner Peer IP
Address
Specifies the peer IP address of the IP packet to be captured.

This is the destination IP address of the packet when the "Out" is selected
for the "inner trace direction"; or the source IP address when the "In" is
selected for the "inner trace direction".
If left blank, it indicates capturing of all packets at the peer IP address.
----End
Follow-up Procedure
l
You can manage packet capture in Manage Trace File on the Trace tab. You can query,
stop, delete or restart a packet capture task.
After packet capturing is complete, packet capturing log files (for example, /bam/common/
fam/trace/16778026_ packet capturing _20120927_201909.log.zip) are created and saved
on the OMU.
NOTE
Packet capturing results are created after the task is complete.
7.2.4 AC Tracing
This section describes how to trace signaling messages over the interface between controller and
access point controller (AC).
Prerequisites
l
The Local Maintenance Terminal (LMT) has been started.
You have logged in to the LMT with an account with authorized operation rights.
Procedure
Step 2 In the Trace Navigation Tree, unfold Trace > Device Commissioning and double-click AC
Trace. The AC Trace dialog box is displayed, as shown in Figure 7-2.
Issue 08 (2014-06-09)

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

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

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

103
BSC6910 GSM
LMT User Guide
7 Trace Management
7.2.5 DHCP Tracing

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

l Subrack No.: indicates the number of the subrack housing the board to be traced.
l Slot No.: indicates the number of the slot housing the board to be traced. Specify the slot
number in scenarios with independent boards. In scenarios with active and standby boards,
the slot number should be an even number.
Issue 08 (2014-06-09)

104
BSC6910 GSM
LMT User Guide
7 Trace Management
l Board Type: indicates the type of the board to be traced. The board type is automatically
displayed after the slot number is specified. It can also be queried by running the LST BRD
command.
l Port Type: You can set this parameter to ETHPORT, ETHTRK, PPPLNK, or MPGRP.
It is recommended that this parameter not be set or set to the actual port type.
l Port No./Link No./Group No.: indicates the number of the port, link, or port group to be
traced. If this field is not specified, the entire board will be traced. It is recommended that
users should not specify this field.
l DHCP Product ID: indicates the type of base station to be traced. There are four options:
BTS, NODEB, SRAN, and OTHER.
BTS: indicates the GSM base station.
NODEB: indicates the UMTS base station.
SRAN: indicates the SRAN base station.
NOTE
To trace SRAN base station, select NODEB and SRAN.
OTHER: indicates other base stations.

l ESN: indicates the electronic serial number. At least one ESN is carried in DHCP packets.
If two ESNs are carried, one is a main ESN and the other is an optional ESN. If an optional
ESN is typed in this field, DHCP packets carrying this ESN will be traced. However, the
main ESN is always displayed on the parsing interface. If this field is left blank, all DHCP
packets will be traced.
For descriptions about Trace Mode, see 7.1.3 BSC Interface Signaling Tracing Mode.
----End
Result
l
The operation succeeds.

Messages Offline.
RFN, trace type, direction, message type, PID, subrack number, slot number, subsystem
number, and content.
Follow-up Procedure
l
You can perform required operations by referring to 7 Trace Management.
7.3 GSM Services

This section describes how to perform tracing tasks related to GSM services.
Issue 08 (2014-06-09)

105
BSC6910 GSM
LMT User Guide
7 Trace Management
7.3.1 Tracing Messages on the A Interface

The A interface is the interface between a BSC6910 and an MSC. This section describes how
to trace the BSSAP, SCTP, and M3UA messages on the A interface. You can perform this task
to locate a fault in the following scenarios: timeslot assignment failure, abnormal releases,
location update failure, and handover failure.
Prerequisites
l
The communication between the BSC6910 and the MSC is normal.
Context
You can start this task on the LMT to monitor the interworking of signaling messages over the
A interface.
To start a tracing task, you can select the following operations:
l
Tracing a specific type of messages (all being signaling messages at the transport network
layer, except BSSAP messages)
Tracing BSSAP Messages on the A Interface

This section describes how to trace Base Station Subsystem Application Part (BSSAP) messages
by site on the A interface through the LMT. BSSAP messages include BSSMAP, DTAP, paging,
and other messages.
Prerequisites
l
The communication between the BSC6910 and the BTS is normal.
Context
A maximum of sixteen A interface tracing tasks can be started simultaneously.
Procedure
Step 2 On Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. The A
Interface Trace dialog box is displayed, as shown in Figure 7-4.
Issue 08 (2014-06-09)

106
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-4 Message tracing on the A interface
Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and select
BSSAP under Trace Type.
l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST
N7DPC command.
l For description of Trace Mode, see 7.1.3 BSC Interface Signaling Tracing Mode.
Step 4 In the BSSAP tab page, set parameters under Message Type and Cell.
NOTE
l Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.

----End
Result
l
Successful operation
Messages Offline.
RFN, message type, direction, message type, message source, subrack number, slot
number, subsystem number, and message content.
Follow-up Procedure
l
You can perform required operations by referring to 7.4 Basic Tracing Operations.
Issue 08 (2014-06-09)

107
BSC6910 GSM
LMT User Guide
7 Trace Management
Tracing SCCP Messages on the A Interface

SCCP messages (including connection-oriented messages and connectionless messages) can be
traced over the LB interface. By starting a SCCP tracing task over the LB interface, you can
monitor the SCCP message interconnection status and locate problems regarding LB connection
establishment failures and abnormal releases.
Prerequisites
l
Context
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. The A
Step 3 In the A Interface Trace dialog box, set parameters in the Basic tab page and select SCCP
under Trace Type.
N7DPC command.
----End
Issue 08 (2014-06-09)

108
BSC6910 GSM
LMT User Guide
7 Trace Management
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing SCTP Messages on the A Interface

This section describes how to trace SCTP signaling messages on the A interface in A over IP
mode through the LMT. The tracing is performed by link ID. SCTP messages include control,
DATA, and heartbeat messages.
Prerequisites
l
Context
Procedure
Step 2 On Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. The A
Issue 08 (2014-06-09)

109
BSC6910 GSM
LMT User Guide
7 Trace Management
Step 3 In the A Interface Trace dialog box, set parameters in Basic and select SCTP in Trace
Type.
N7DPC command.
Step 4 In the SCTP tab page, set parameters under SCTP Message and Parameter Configuration.
NOTE
l SCTP Link ID: query it by running the LST SCTPLNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Issue 08 (2014-06-09)

110
BSC6910 GSM
LMT User Guide
7 Trace Management
Tracing M3UA Messages on the A Interface

This section describes how to trace M3UA signaling messages on the A interface in A over IP
mode through the LMT. The tracing is performed by link or link set index. M3UA messages
include management messages, transmission messages, SS7 management messages, ASP
service maintenance messages, ASP status maintenance messages, and route selected keyword
messages.
Prerequisites
l
Context
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. The A
Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and select
M3UA under Trace Type.
l DPC (HEX): indicates the destination signaling point to be traced. To query the DPC, run
the LST N7DPC command.
Step 4 In the M3UA tab page, set parameters under M3UA Message and Parameter Configuration.
Issue 08 (2014-06-09)

111
BSC6910 GSM
LMT User Guide
7 Trace Management
NOTE
l M3UA Trace Type: Set this parameter to Specified Link or Link Set. If this parameter is set to Link
Set, a large number of messages are traced.
l Signaling Link Set Index: indicates the number of an M3UA link set. To query it, run the LST M3LKS
command.
l Signaling Link ID: indicates the number of an M3UA link. To query it, run the LST M3LNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l
7.3.2 Tracing CS Domain Messages on the Um Interface

The Um interface is the interface between a BTS and MSs. This section describes how to trace
the layer 3 signaling messages in the CS domain on the Um interface, based on cells or TRXs.
You can perform this task to locate a fault in the following scenarios: timeslot assignment failure,
abnormal releases, and handover failure.
Prerequisites
l
Context
A maximum of sixteen CS tracing tasks on the Um interface can be started simultaneously.
You can start this task on the LMT to monitor the interworking of signaling messages over the
Um interface.
l
Tracing by the cell or TRX
Tracing the required types of message
Issue 08 (2014-06-09)

112
BSC6910 GSM
LMT User Guide
7 Trace Management
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Um Interface CS
Trace. The Um Interface CS Trace dialog box is displayed, as shown in Figure 7-8.
Figure 7-8 CS domain message tracing on the Um interface
Step 3 In the Um Interface CS Trace dialog box, set the parameters as required.
l Trace Type: Select Paging, Other, or both Paging and Other for this parameter. If
Paging is selected, only the paging messages are traced. If Other is selected, the messages
except the paging messages are traced. If both Paging and Other are selected, all messages
are traced.
l Filter Flag: This parameter can be set to Cell or TRX. When this parameter is set to Cell,
you can set the cell to be traced by specifying Cell ID. When this parameter is set to TRX,
you can set the TRX to be traced by specifying TRX ID.
l TRX ID: indicates the number of a TRX. You can query it by running the LST GTRX
command.
----End
Result
l
Issue 08 (2014-06-09)
113
BSC6910 GSM
LMT User Guide
7 Trace Management
Messages Offline.
l
Follow-up Procedure
l
7.3.3 Tracing PS Domain Messages on the Um Interface

The Um interface is the interface between a BTS and MSs. This section describes how to trace
PS domain messages on the Um Interface, including the DUMMY messages, system information
messages, null paging messages, and data block messages. You can perform this task to locate
a fault when PS assignment failure and abnormal TBF release occur.
Prerequisites
l
The communication between the BSC6910 and the SGSN is normal.
The configuration type of PCU is Built-in PCU.
Context
A maximum of five PS tracing tasks on the Um interface can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Um Interface PS
Trace. The Um Interface PS Trace dialog box is displayed, as shown in Figure 7-9.
Issue 08 (2014-06-09)

114
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-9 PS domain message tracing on the Um interface
Step 3 In the Um Interface PS Trace dialog box, set parameters as required.

l Trace Type can be set to Cell or TRX. When Cell is selected, you can set the cell to be
traced by specifying Cell ID. When TRX is selected, you can set the TRX to be traced by
specifying TRX ID.
l TRX ID: indicates the number of a TRX. You can query it by running the LST GTRX
command.
----End
Result
l
Messages Offline.
l
Issue 08 (2014-06-09)
115
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.4 Tracing Messages on the Cb Interface

The Cb interface is the interface between a BSC and a CBC. This section describes how to trace
signaling messages on the Cb interface. You can perform this task to locate a fault in the
following scenarios: message query failure, BIND failure, and SOCKET connection failure.
Prerequisites
l
The communication between the BSC6910 and the CBC is normal.
Context
A maximum of sixteen Cb interface tracing tasks can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Cb Interface
Trace. The Cb Interface Trace dialog box is displayed, as shown in Figure 7-10.
Figure 7-10 Message tracing on the Cb interface

----End
Result
l
Issue 08 (2014-06-09)
116
BSC6910 GSM
LMT User Guide
7 Trace Management
Messages Offline.
l
Follow-up Procedure
l
7.3.5 Tracing Messages on the Inter-BSC Interface

This section describes how to trace common measurement messages or message interactions on
the inter-BSC interface. You can perform this task to locate a fault during the common
measurement procedures such as initialization request failure or common measurement
indication failure.
Prerequisites
l
The communication between the BSC6910 and other BSCs is normal.
Context
A maximum of sixteen Inter-BSC Interface tracing tasks can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BSC Trace. The
BSC Trace dialog box is displayed, as shown in Figure 7-11.
Issue 08 (2014-06-09)

117
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-11 Message tracing on the inter-BSC interface
Step 3 In the BSC Trace dialog box, set the parameters as required.
l DPC: indicates the destination signaling point to be traced. To query a DPC, run the LST
N7DPC command.
Step 4 Click Submit. View the traced message flow in the message browsing window.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
7.3.6 Tracing CS Domain Messages on the Abis Interface

The Abis interface is the interface between a BSC6910 and a BTS. This section describes how
to trace RSL, ESL, EML, OML, LAPD, SCTP, and CSL messages in the CS domain over the
Issue 08 (2014-06-09)

118
BSC6910 GSM
LMT User Guide
7 Trace Management
Abis interface. You can perform this task to locate a fault in the following scenarios: Abis wrong
indication, channel activation failure, and BTS connection failure.
Prerequisites
l
Context
If you select LAPD as the trace type are in the Basic tab page, the signaling messages over the
Abis interface are traced. Otherwise, the service messages over the Abis interface are traced.
For each subsystem, a maximum of 16 Abis interface tracing tasks can be performed
simultaneously.
Tracing CS Domain RSL Messages on the Abis Interface

This section describes how to trace Radio Signaling Link (RSL) messages on the Abis interface
through the LMT. RSL messages present the interactive call signaling procedure between the
BSC and the BTS. Tracing RSL messages is an important way of tracing a call process. RSL
messages include measurement reports, channel request messages, paging messages, RLM
messages, and TRXM messages.
Prerequisites
l
Context
A maximum of sixteen CS tracing tasks on the Abis interface can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Abis Interface
CS Trace. The Abis Interface CS Trace dialog box is displayed, as shown in Figure 7-12.
Issue 08 (2014-06-09)

119
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-12 CS domain message tracing on the Abis interface
Step 3 In the displayed Abis Interface CS Trace dialog box, set parameters in the Basic tab page and
select RSL under Trace Type.
Step 4 In the RSL tab page, set parameters under Message Type and Trace Target.
NOTE
You need to set Filter Flag under Trace Target.

l When Filter Flag is set to TRX, you need to specify TRX ID. TRX ID: indicates the number of a TRX. To
query it, run the LST GTRX command.
l When Filter Flag is set to Cell, you need to specify Cell ID. Cell ID: indicates the index of a cell. To query
it, run the LST GCELL command.

----End
Result
l
Messages Offline.
window displays information about each traced message,including the number, time,
Issue 08 (2014-06-09)

120
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
Tracing CS Domain ESL Messages on the Abis Interface

This section describes how to trace Extend Signaling Link (ESL) messages by site on the Abis
interface through the LMT. ESL messages include public messages and operation and
maintenance messages. eGBTS does not support this function.
Prerequisites
l
Context
Procedure
select ESL under Trace Type.
Issue 08 (2014-06-09)

121
BSC6910 GSM
LMT User Guide
7 Trace Management
Step 4 In the ESL tab page, set parameters under Message Type and Site.
l Site ID: indicates the number of a BTS. You can query it by running the LST BTS command.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing CS Domain EML Messages on the Abis Interface

This section describes how to trace Extend Maintenance Link (EML) messages by site on the
Abis interface through the LMT. EML messages include public messages and operation and
Prerequisites
l
Context
Procedure
Issue 08 (2014-06-09)

122
BSC6910 GSM
LMT User Guide
7 Trace Management
select EML under Trace Type.
Step 4 In the EML tab page, set parameters under Message Type and Site.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Issue 08 (2014-06-09)

123
BSC6910 GSM
LMT User Guide
7 Trace Management
Tracing CS Domain OML Messages on the Abis Interface

This section describes how to trace operation and maintenance link (OML) messages by site on
the Abis interface through the LMT. OML messages include public messages and operation and
Prerequisites
l
Context
Procedure
select OML under Trace Type.
Step 4 In the OML tab page, set parameters under Message Type and Site.
Issue 08 (2014-06-09)

124
BSC6910 GSM
LMT User Guide
7 Trace Management

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing CS Domain LAPD Messages on the Abis Interface

This section describes how to trace Link Access Procedure on the D channel (LAPD) messages
on the Abis interface through the LMT. LAPD links include RSL, EML, OML, and ESL. The
tracing can be performed by site or TRX. eGBTS does not support this function.
Prerequisites
l
Context
Procedure
Issue 08 (2014-06-09)

125
BSC6910 GSM
LMT User Guide
7 Trace Management
select LAPD under Trace Type.
Step 4 In the LAPD tab page, set parameters under the tab page.
l LAPD Link Type: Set this parameter to RSL, EML, OML, ESL, or DML.
OML: operation and maintenance link (ONL). Each BTS is configured with an OML.
EML: extended maintenance link (EML). When the BTS uses Abis over IP or HDLC
transmission mode, it is configured with an EML for loading BTS software and uploading
log files.
DML: dynamic maintenance link. During BTS software loading, in addition to the OML
and EML, transmission resources configured for RSLs and traffic channels may be
dynamically preempted to set up temporary extended links. These extended links
accelerate software loading. After the loading is complete, these extended links are
released, the transmission resources are reallocated to RSLs or traffic channels, and
therefore transmission resources on the Abis interface restore to normal.
RSL: signaling link configured for a TRX. Each TRX is configured with one link.
ESL: extended signaling link (ESL). If Flex Abis Mode is set to FLEX_ABIS(Flex
Abis), each BTS is configured with one ESL to transmit the Abis timeslot dynamic
connection message.
l TRX ID:indicates the number of a TRX. You can query it by running the LST GTRX
command.
l Direction: indicates whether it is a forward ring or reverse ring. To query the ring
configuration, run the LST BTS command and check the setting of Config ring in the query
result. If Config ring is set to Yes, you can start tracing in the Forward or Reverse direction.
Otherwise, you can only start tracing in the Forward direction.
Issue 08 (2014-06-09)

126
BSC6910 GSM
LMT User Guide
7 Trace Management

----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing CS Domain SCTP Messages on the Abis Interface

This task is performed to trace the SCTP messages over the Abis interface. SCTP messages
include control messages, data messages, and heartbeat messages.
Prerequisites
l
Context
Procedure
Issue 08 (2014-06-09)

127
BSC6910 GSM
LMT User Guide
7 Trace Management
select SCTP under Trace Type.
l For description of Trace Mode, see Trace Mode.
Step 4 In the SCTP tab page, set parameters under the tab page.
NOTE
SCTP Link ID: You can query it by running the LST SCTPLNK command.

----End
Result
l
Messages Offline.
window displays information about each traced message, including the task number,
task time, RFN, subrack number, slot number, subsystem number, trace type, message
direction, message type, report condition, call ID, and message content.
Follow-up Procedure
l
You can perform required operations by referring to Basic Tracing Operations.
Issue 08 (2014-06-09)

128
BSC6910 GSM
LMT User Guide
7 Trace Management
Tracing CS Domain CSL Messages on the Abis Interface

This task is performed to trace the CSL messages over the Abis interface.
Prerequisites
l
Context
Procedure
select CSL under Trace Type.
Step 4 In the CSL tab page, set parameters under the tab page.
----End
Issue 08 (2014-06-09)

129
BSC6910 GSM
LMT User Guide
7 Trace Management
Result
l
Messages Offline.
Follow-up Procedure
l
7.3.7 Tracing PS Domain Messages on the Abis Interface

The Abis interface is the interface between a BSC6910 and a BTS. This section describes how
to trace the PS domain messages on the Abis interface, based on cells or TRXs. You can perform
this task to locate a fault in the PS domain channel failure.
Prerequisites
l
Context
A maximum of five PS tracing tasks on the Abis interface can be started simultaneously.
Procedure
PS Trace. The Abis Interface PS Trace dialog box is displayed, as shown in Figure 7-19.
Issue 08 (2014-06-09)

130
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-19 PS domain message tracing on the Abis interface
Step 3 In the Abis Interface PS Trace dialog box, set parameters as required.
l When the Cell message type is selected, you need to specify Cell ID. Cell ID can be queried
by running the LST GCELL command.
l When the TRX-TN message type is selected, you need to specify TRX ID and Timeslot
No.. They can be queried by running the LST GTRX command. The timeslot number is the
one corresponding to the PDCH.
l Report Mode: indicates the message report mode. When MAC Report is selected, messages
are reported in the message format of the Um interface. When TRAU Report is selected,
messages are reported in the message format of the Abis interface, namely using binary codes.
----End
Result
l
Messages Offline.
Issue 08 (2014-06-09)

131
BSC6910 GSM
LMT User Guide
7 Trace Management
l
Follow-up Procedure
l
7.3.8 Tracing PTP Messages on the Gb Interface

The Gb interface is the interface between a BSC6910 and an SGSN. This section describes how
to trace point to point (PTP) messages on the Gb interface by NSEI or BVCI. You can perform
this task to locate a fault in the following scenarios: Attach rejection, PDP context activation
rejection, and PS packet loss.
Prerequisites
l
The LMT has been started.
The NSE has been configured, and the cell has been bound with the BVC(s).
Context
A maximum of five PTP tracing tasks on the Gb interface can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Gb Interface PTP
Trace. The Gb Interface PTP Trace dialog box is displayed, as shown in Figure 7-20.
Issue 08 (2014-06-09)

132
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-20 PTP message tracing on the Gb interface
Step 3 In the Gb Interface PTP Trace dialog box, set the parameters as required.
l When the CELL trace type is selected, you need to specify Cell ID. Cell ID can be queried
by running the LST GCELL command.
l When the tracing is based on NSEI-BVCI, you need to specify NSEI and BVCI. NSE
identifier (NSEI) and PTP BSSGP virtual connection identifier (PTP BVCI) can be queried
by running the LST PTPBVC command.
----End
Result
l
No traced message will be displayed on the LMT if the Save to OMU trace mode is
selected. You can view the tracing result saved on the OMU by referring to Browsing
Traced Messages Offline.
Issue 08 (2014-06-09)

133
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
You can double-click a message in the displayed result area to view detailed information
You can perform further operations by referring to 7.4 Basic Tracing Operations.
7.3.9 Tracing SIG Messages on the Gb Interface

The Gb interface is the interface between a BSC6910 and an SGSN. This section describes how
to trace signaling messages on the Gb interface by the NSEI. You can perform this task to locate
a fault in the PS domain in the case of a SIG BVC failure or abnormal PTP status.
Prerequisites
l
The NSEI has been configured.
Context
A maximum of six SIG tracing tasks on the Gb interface can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Gb Interface SIG
Trace. The Gb Interface SIG Trace dialog box is displayed, as shown in Figure 7-21.
Figure 7-21 SIG message tracing on the Gb interface
Step 3 In the Gb Interface SIG Trace dialog box, set the parameters as required.
Issue 08 (2014-06-09)

134
BSC6910 GSM
LMT User Guide
7 Trace Management
l NSEI: is NSE identifier. It can be queried by running the LST NSE command.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
7.3.10 Tracing NS Signal Messages on the Gb Interface

The Gb interface is the interface between a BSC6910 and an SGSN.This task traces NS signal
messages on the BSC side. Performing this task helps optimize the tracing of Gb interface
protocol stack and locate abnormal NS signal messages over the Gb interface.
Prerequisites
l
The NSEI has been configured.
Context
A maximum of five tasks, of tracing the NS Signal messages on the Gb interface, can be started
simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Gb Interface NS
Signal Trace. The Gb Interface NS Signal Trace dialog box is displayed, as shown in Figure
7-22.
Issue 08 (2014-06-09)

135
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-22 NS Signal message tracing on the Gb interface
Step 3 In the Gb Interface NS Signal Trace dialog box, set the parameters as follows:
l Trace Type: When this parameter is set to NSEI, you must set NSEI Identifier. When this
parameter is set to NSEI + Local NSVL, you must set NSEI Identifier and Local NSVL
ID. When this parameter is set to NSEI + Remote NSVL, you must set NSEI Identifier and
Remote NSVL ID.
l NSE Identifier: This parameter can be queried by running the LST NSE command.
l Local NSVL ID: indicates the local NSVL ID, which can be queried by running the LST
NSVLLOCAL command.
l Remote NSVL ID: indicates the remote NSVL ID, which can be queried by running the
LST NSVLREMOTE command.
l For details about Trace Mode, see 7.1.3 BSC Interface Signaling Tracing Mode.
----End
Result
l
Messages Offline.
l
Issue 08 (2014-06-09)
136
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
7.3.11 Tracing CS Domain Messages of a Single Subscriber

This section describes how to trace signaling messages on the A, Abis, or Um interface of a
specified subscriber. The subscriber to be traced can be identified by IMSI, IMEI, TMSI,
MSISDN, CELLID, or a channel.
Prerequisites
NOTICE
As private information of users is revealed during the tracing, only G1 command group users
(ADMINISTRATOR and CUSTOM users with G1 command group permission) are allowed to
perform a single-user CS tracing task.
Context
At the most, 16 tasks of tracing CS messages of a single subscriber can be started simultaneously.
There is no way to avoid that some user data such as International Mobile Subscriber Identity
(IMSI) will be used during problem location and resolution. This function provides an
anonymous data processing method. You are recommended to comply with local laws when
executing the task and take ample measures to fully protect user data, such as enabling the
anonymous function and deleting the folder that saves track records after you finish processing
data.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Single User CS
Trace. The Single User CS Trace dialog box is displayed, as shown in Figure 7-23.
Issue 08 (2014-06-09)

137
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-23 CS domain message tracing of a single subscriber
Step 3 In the Single User CS Trace dialog box, set the parameters as required.
NOTE
l If you choose to trace messages by MSISDN, set the MSISDN to that of the peer end:
l (Recommended) To trace the calling MS, set the MSISDN to that of the called MS. For example,
if the MS calls 12345, then set the MSISDN to 12345.
l To trace the called MS, set the MSISDN to that of the calling MS, which is displayed on the called
MS. For example, if 54321 is displayed on the called MS, set the MSISDN to 54321.
l If you trace the user messages by TMSI or IMSI, you must check the reassignment policies on the MSC
side:
l If TMSI is carried, you can trace the MS by TMSI.
l If IMSI is carried, you can trace the MS by IMSI.
l If you choose to trace the user messages by IMEI, you must check whether the IMEI is available to the
MSC.
l If you choose to trace the user messages by IMEI,
l If no message is reported when the IMEI is 14 digits, add 0 to the end of the IMEI and try again.
l If no messages can be traced using the 15-digit IMEI, check whether the 15-digit IMEI is correct.
l If incorrect, enter the correct one and try again.
l If correct, change the last digit of the IMEI to 0 and try again.
l If you choose to trace the user messages by CELLID, all calls in the cell are traced. You are advised
to set Trace Interval(10s) to the maximum value 65535. This ensures that all traced signaling can be
displayed on the LMT.
l If you choose to trace the user messages by CHANINFO, the call carried on the specified channel is
traced.
Issue 08 (2014-06-09)

138
BSC6910 GSM
LMT User Guide
7 Trace Management
NOTE
l When entering IMSI, check whether IMSI data to be entered must be anonymous by running the LST
USERIDANONSWITCH command and querying User Identity Anonymity Switch.
l If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and anonymous IMSI data
must be entered in IMSI. The anonymous IMSI data is the IMSI data encrypted by the HMACUtil using
the cipher key.
l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI data is
directly entered in IMSI.
l Change the anonymous policy and cipher key on the M2000 by choosing Trace and Maintenance >
Signaling Trace > Anonymous Policy Management > Anonymous Cypher Key Management
(application style) or Trace and Maintenance > Monitor > Signaling Trace > Anonymous Policy
Management > Anonymous Cypher Key Management (traditional style). For details, see M2000 Fault
Management User Guide.
l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the tracing
task. Otherwise, the tracing task becomes invalid.
l For details about how to obtain the HMACUtil, contact Huawei technical support.
l CDT Mode: If you select the CDT mode, you can trace interfaces between internal modules
of the BSC.
l Debug Mode: If you select the debug mode, you can trace stream data in A over IP scenarios.
Interface boards need to be selected in the Other tab page.
NOTE
Debug Mode is intended for Huawei technical support personnel for maintenance. For use of it, contact
Huawei technical support personnel.
l Location Flag: indicates information such as cell ID and TA.

l Algorithmic Trace: traces algorithmic traces for a single subscriber in the CS domain. This
function is used for internal fault diagnosis and the identification type for the traced subscriber
must be TMSI, IMEI, IMSI, MSISDN, or CELLID.
l User Plane Trace: , as shown in Figure 7-24.
Frame Control Info: traces control messages related to speech frame.
Issue 08 (2014-06-09)

139
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-24 User Plane Tracing

----End
Result
l
No traced message will be displayed on the LMT if the Save to OMU trace mode is
selected. You can view the tracing result saved on the OMU by referring to Browsing
Traced Messages Offline.
Follow-up Procedure
l
You can double-click a message in the displayed result area to view detailed information
You can perform further operations by referring to 7.4 Basic Tracing Operations.
7.3.12 Tracing PS Domain Messages of a Single Subscriber

This section describes how to trace signaling messages and internal messages on the Gb/Abis/
Um interface or the data block on the Um interface of a specified subscriber. You can trace the
subscriber by the IMSI or TLLI. You can perform this task to locate a fault in the PS domain in
Issue 08 (2014-06-09)

140
BSC6910 GSM
LMT User Guide
7 Trace Management
the following procedures: PS service channel assignment failure, abnormal TBF release, and PS
packet loss.
Prerequisites
l
NOTICE
As private information of users is revealed during the tracing, only G1 command group users
(ADMINISTRATOR and CUSTOM users with G1 command group permission) are allowed to
perform a single-user PS tracing task.
Context
A maximum of five tasks, of tracing the PS messages of a single subscriber, can be started
simultaneously.
There is no way to avoid that some user data such as International Mobile Subscriber Identity
(IMSI) will be used during problem location and resolution. This function provides an
anonymous data processing method. You are recommended to comply with local laws when
executing the task and take ample measures to fully protect user data, such as enabling the
anonymous function and deleting the folder that saves track records after you finish processing
data.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Single User PS
Trace. The Single User PS Trace dialog box is displayed, as shown in Figure 7-25.
Issue 08 (2014-06-09)

141
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-25 PS domain message tracing of a single subscriber
Step 3 In the Single User PS Trace dialog box, set the parameters as required.
l The Trace Um Datablock Message can be selected only when Um Interface is selected
under Trace Interface Type.
If you start the trace with the IMSI, you must check the reassignment policies on the MSC
side. If IMSI is carried, you can trace the MS through the IMSI.
If you start the trace with the TLLI, you must query the TLLI of the MS by running the
DSP MSCONTEXT command. During the PS service, the TLLI may be reassigned to
the MS. In this case, run this command to query the new TLLI for the tracing operation.
Issue 08 (2014-06-09)

142
BSC6910 GSM
LMT User Guide
7 Trace Management
NOTE
l When entering IMSI, check whether IMSI data to be entered must be anonymous by running the LST
USERIDANONSWITCH command and querying User Identity Anonymity Switch.
l If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and anonymous IMSI
data must be entered in IMSI. The anonymous IMSI data is the IMSI data encrypted by the
HMACUtil using the cipher key.
l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI data
is directly entered in IMSI.
l Change the anonymous policy and cipher key on the M2000 by choosing Trace and Maintenance >
Signaling Trace > Anonymous Policy Management > Anonymous Cypher Key Management
(application style) or Trace and Maintenance > Monitor > Signaling Trace > Anonymous Policy
Management > Anonymous Cypher Key Management (traditional style). For details, see M2000
Fault Management User Guide.
l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the tracing
task. Otherwise, the tracing task becomes invalid.
l For details about how to obtain the HMACUtil, contact Huawei technical support.
l Report Mode: indicates the message report mode. When Trace Um Datablock Message is
selected, Um datablock messages are reported. When MAC Report is selected, messages
are reported in the message format of the Um interface. When TRAU Report is selected,
messages are reported in the message format of the Abis interface, namely using binary codes.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
7.3.13 Tracing BTS Signaling Messages

This section describes how to trace and analyze BTS signaling messages (from both CS and PS
domains) within a TRX.
Issue 08 (2014-06-09)

143
BSC6910 GSM
LMT User Guide
7 Trace Management
Prerequisites
l
Context
A maximum of 16 tracing tasks, of the BTS signaling messages, can be started simultaneously.
Tracing LAPDm Messages Through BTS Signaling Trace

This section describes how to trace LAPDm messages within a TRX by TRX or timeslot number
through BTS signaling trace.
Prerequisites
l
Context
A maximum of sixteen BTS Signaling tracing tasks can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BTS Signaling
Trace. The BTS Signaling Trace dialog box is displayed, as shown in Figure 7-26.
Figure 7-26 BTS signaling trace
Step 3 In the displayed BTS Signaling Trace dialog box, set parameters in the Basic tab page and
select LAPDm under Trace Type.
Issue 08 (2014-06-09)

144
BSC6910 GSM
LMT User Guide
7 Trace Management
Step 4 Set parameters in the LAPDm tab page.
l TRX ID: indicates the number of the TRX. To query it, run the LST GTRX command.
l Timeslot No.: indicates the number of the channel whose signaling needs to be traced.
l Sub-Timeslot No.: indicates the number of the sub-channel whose signaling needs to be
traced.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing RLC/MAC Messages Through BTS Signaling Trace

This section describes how to trace RLC/MAC messages within a TRX by TRX or timeslot
number through BTS signaling trace on the LMT.
Prerequisites
l
Context
A maximum of sixteen BTS Signaling tracing tasks can be started simultaneously.
Procedure
Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BTS Signaling
Trace. The BTS Signaling Trace dialog box is displayed, as shown in Figure 7-27.
Issue 08 (2014-06-09)

145
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-27 BTS signaling trace
Step 3 In the displayed BTS Signaling Trace dialog box, set parameters in the Basic tab page and
select RLC/MAC under Trace Type.
Step 4 Set parameters in the RLC/MAC tab page.
l TRX ID: indicates the number of the TRX. To query it, run the LST GTRX command.
l Timeslot No.: indicates the timeslot number of the PDCH
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Issue 08 (2014-06-09)

146
BSC6910 GSM
LMT User Guide
7 Trace Management
7.3.14 Tracing Messages on the LB Interface

The LB interface is the interface between a BSC6910 and an SMLC (Serving Mobile Location
Center). This section describes how to trace the BSSAP-LE, SCTP, and M3UA messages on the
LB interface. You can perform this task to locate a fault in the following scenarios: timeslot
assignment failure, abnormal releases, location update failure, and handover failure.
Prerequisites
l
Context
You can start this task on the LMT to monitor the interworking of signaling messages on the
LB interface.
l
Tracing a specific type of messages (all being signaling messages at the transport network
layer, except BSSAP-LE messages)
Tracing BSSAP-LE Messages on the LB Interface

This section describes how to trace BSSAP-LE messages by cell on the LB interface through
the LMT. BSSAP-LE messages include BSSMAP-LEmsg, DTAP-LEmsg, and other messages.
Prerequisites
l
Context
A maximum of sixteen LB interface tracing tasks can be started simultaneously.
Procedure
Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > LB Interface Trace. The LB
Issue 08 (2014-06-09)

147
BSC6910 GSM
LMT User Guide
7 Trace Management
Figure 7-28 Message tracing on the LB interface
Step 3 In the LB Interface Trace dialog box, set parameters in Basic the tab page and select BSSAPLE under Trace Type.
l DPC (HEX): indicates the destination signaling point to be traced. To query the DPC, run
the LST N7DPC command.
Step 4 In the BSSAP tab page, set parameters under Message Type and Cell.
NOTE

----End
Result
l
Messages Offline.
Issue 08 (2014-06-09)

148
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
Tracing SCCP Messages on the LB Interface

SCCP messages (including connection-oriented messages and connectionless messages) can be
traced over the LB interface. By starting a SCCP tracing task over the LB interface, you can
monitor the SCCP message interconnection status and locate problems regarding LB connection
establishment failures and abnormal releases.
Prerequisites
l
Context
Procedure
Step 3 In the LB Interface Trace dialog box, set parameters in the Basic tab page and select SCCP
under Trace Type.
Issue 08 (2014-06-09)

149
BSC6910 GSM
LMT User Guide
7 Trace Management
N7DPC command.
----End
Result
l
Messages Offline.
Follow-up Procedure
l
Tracing SCTP Messages on the LB Interface

This section describes how to trace SCTP signaling messages on the LB interface in LB over IP
mode through the LMT. The tracing is performed by link ID. SCTP messages include control,
DATA, and heartbeat messages.
Prerequisites
l
Context
Procedure
Issue 08 (2014-06-09)

150
BSC6910 GSM
LMT User Guide
7 Trace Management
Step 3 In the LB Interface Trace dialog box, set parameters in the Basic tab page and select SCTP
under Trace Type.
N7DPC command.
Step 4 In the SCTP tab page, set parameters under SCTP Message and Parameter Configuration.
NOTE
l SCTP Link ID: query it by running the LST SCTPLNK command.

----End
Result
l
Messages Offline.
Issue 08 (2014-06-09)

151
BSC6910 GSM
LMT User Guide
7 Trace Management
Follow-up Procedure
l
Tracing M3UA Messages on the LB Interface

This section describes how to trace M3UA signaling messages on the LB interface in LB over
IP mode through the LMT. The tracing is performed by link ID or link set index. M3UA messages
include management messages, transmission messages, SS7 management messages, ASP
service maintenance messages, ASP status maintenance messages, and route selected keyword
messages.
Prerequisites
l
Context
Procedure
Issue 08 (2014-06-09)

152
BSC6910 GSM
LMT User Guide
7 Trace Management
Step 3 In the LB Interface Trace dialog box, set parameters in the Basic tab page and select M3UA
under Trace Type.
N7DPC command.
Step 4 In the M3UA tab page, set parameters under M3UA Message and Parameter Settings.
NOTE
l M3UA Trace Type: Set this parameter to Specified Link or Link Set. If this parameter is set to Link
Set, a large number of messages are traced.
l Link Set Index: indicates the number of an M3UA link set. To query it, run the LST M3LKS command.
l Link ID: indicates the number of an M3UA link. To query it, run the LST M3LNK command.

----End
Result
l
Messages Offline.
Follow-up Procedure
l
7.4 Basic Tracing Operations

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

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

153
BSC6910 GSM
LMT User Guide
7 Trace Management
Context
l
By default, each message browser is displayed in maximized mode. To compare results

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

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

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

without affecting the saved messages.
Property...
Query properties of the tracing task.
Step 2 To view details of a message, double-click it. The Message Browser dialog box is displayed,
showing details of the message.
----End
7.4.2 Viewing the Interpretation of the Trace Message

This section describes how to view the interpretation of a trace message.
Issue 08 (2014-06-09)

154
BSC6910 GSM
LMT User Guide
7 Trace Management
Prerequisites
l
Trace messages are reported.
Procedure
Step 1 In the message browse window, select and double-click the trace message.
Step 2 The Message Browser window is displayed. The dialog box displays the details and meaning
of the message in protocol translation format.
----End
7.4.3 Saving Traced Messages

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

Select Save File when creating a tracing task. All traced messages of this task to be
displayed in the message browser will be automatically saved in .tmf format.
The default save path is C:\Web LMT\MBSC\output\trace\tmfFile on the LMT PC.
NOTE
l The LMT saves every 5,000 messages in a file. Messages starting from 5,001 are saved in another
file with a serial number and the serial number is increased by one for every subsequent 5,000
messages. For example, the 5001st to 10000th messages traced on the interface are saved in file's
name-1.tmf format by default. YYYY, MM, DD, HH, MM, and SS represent the year, month,
day, hour, minute, and second, respectively.
l You can use the Traffic Recording Review Tool to browse messages saved in .tmf format offline.
For details, see 7.4.4 Browsing Traced Messages Offline.
Manual saving of traced messages

When a tracing task is running, you can manually save all or some of the messages in the
message browser in .tmf, .txt, or .csv format.
1.
Issue 08 (2014-06-09)
To save all messages, right-click in the message browser and choose Save All
Messages from the shortcut menu. To save some messages displayed in the message
155
BSC6910 GSM
LMT User Guide
7 Trace Management
browser, select them, right-click, and choose Save Selected Messages from the
shortcut menu. The Save dialog box is displayed.
2.
Enter a file name, and specify the file type and save path.
The default save path is C:\Web LMT\MBSC\output\trace\tmfFile. The default file
name is in IP address_Tracing type_YYYY-MM-DD-HH-MM-SS.tmf format.
3.
Click Save to save the file in the specified path.
----End
7.4.4 Browsing Traced Messages Offline

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

shortcut menu,
All the messages are saved in the window

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

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

format.

156
BSC6910 GSM
LMT User Guide
7 Trace Management
If...
Then...
You choose Filter By Byte from the shortcut

menu,
Set the filter to selectively display the

information.
You choose Filter By Column from the

shortcut menu,
Filter the information by column to

selectively display the information.
You choose Find from the shortcut menu,
Locate the message that you want.
----End
7.4.5 Managing Tracing Tasks

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

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

This section describes how to query the trace files on the OMU and upload the trace files onto
the LMT PC as required.
Issue 08 (2014-06-09)

157
BSC6910 GSM
LMT User Guide
7 Trace Management
Prerequisites
l
Procedure
1.
Click Trace on the LMT main page. The Trace tab page is displayed.
2.
On the Trace Navigation Tree pane, choose the Manage Trace File node. The
Manage Trace File dialog box is displayed.
3.
In the displayed Manage Trace File tab page, set the parameters in the Search
Configure area, and then click Query to read the information about the trace files
saved on the OMU.
4.
To upload a trace file to the LMT PC, select the target file listed in the Result area,
set the parameters in the Upload configure area, and then click Upload.

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

158
BSC6910 GSM
LMT User Guide
Performance Monitoring
About This Chapter

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

159
BSC6910 GSM
LMT User Guide
8.1 Concepts Related to Performance Monitoring

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

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

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

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

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

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

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

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

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

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

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

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

This section describes how to monitor the transmission resources on the Abis interface.
Issue 08 (2014-06-09)

163
BSC6910 GSM
LMT User Guide
Prerequisites
l
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Transport
Resource RealTime monitoring. The Transport Resource RealTime monitoring dialog box
is displayed.
Step 3 In the Transport Resource RealTime monitoring dialog box, set the parameters as required,
and click Submit.
l Statistic Period(s): Specifies the duration of the measurement period for monitoring.
l Transport Object Type: Specifies the type of the transport object to be monitored. It can
be set to IP Logic Port, Physical Port. For detailed settings, see Table 8-1.
Table 8-1 Detailed settings of Transport Object Type
Transport Object Type
Description
IP Logic Port
Indicates the number of the IP logical port.

Logic Port No. must be specified.
l Logic Port No.: Indicates the logical
port number. To query the logical port
number, run the LST
IPLOGICPORT command.
Physical Port
Indicates the number of the physical port.

Physical Port Type must be specified.
l MP Group: Indicates the number of the
physical port carrying an MP link in the
MP group. To query MP Group, run the
LST MPGRP command.
l PPP Link: Indicates the number of the
physical port carrying the PPP link. To
query PPP Link, run the LST
PPPLNK command.
l Subrack No.: Indicates the number of the subrack where the transport object to be monitored
is located.
l Slot No.: Indicates the number of the slot where the transport object to be monitored is
located.
l OP Index No.: Indicates the monitored operator of the transport object.
l Statistic Type: Indicates the statistic type displayed in the monitoring report. It can be set
to Bandwidth(Original) or Bandwidth(Statistic). Then, you can select Uplink or
Downlink to view the uplink or downlink statistics. If you have selected Bandwidth
Issue 08 (2014-06-09)

164
BSC6910 GSM
LMT User Guide
(Original), the bandwidths allocated to different services are displayed. If you have selected
Bandwidth(Statistic), the total bandwidth used by all services is displayed.
Bandwidth(Original): Displays the actual bandwidths allocated to different services
when the UE is performing a voice service or data service. Table 8-2 shows the related
statistic items.
Bandwidth(Statistic): Displays the total bandwidths of those allocated to different
services. Table 8-3 shows the related statistic items.
Uplink/Downlink: Displays the statistics of the bandwidths in the uplink or downlink.
Table 8-2 Bandwidth(Original)
Statistic Item
(Original)
Description
OLC Clear Threshold
Overload control (OLC) end threshold. It equals configured

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

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

Admitted Bandwidth(3G Total) minus Admitted Bandwidth
(2G Total) minus signaling bandwidth. Admitted Bandwidth(2G
Total) is valid when 2G and 3G services share the same port.
Admitted Bandwidth
(LOW PRI, 2G CS,
Data, FR)
Bandwidth for admitting 2G CS data FR services with low

priorities. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(LOW PRI, 2G CS,
Data, HR)
Bandwidth for admitting 2G CS data HR services with low

admitting services.
Admitted Bandwidth
(LOW PRI, 2G CS,
Voice, AMR, FR)
Bandwidth for admitting 2G CS voice AMR FR services with low

admitting services.
Admitted Bandwidth
(LOW PRI, 2G CS,
Voice, AMR, HR)
Bandwidth for admitting 2G CS voice AMR HR services with low

admitting services.

165
BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
Statistic Item
(Original)
Description
Admitted Bandwidth
(LOW PRI, 2G CS,
Voice, Not AMR, FR)
Bandwidth for admitting 2G CS voice AMR FR services with low

admitting services.
Admitted Bandwidth
(LOW PRI, 2G CS,
Voice, Not AMR, HR)
Bandwidth for admitting 2G CS non-AMR voice HR services with

low priorities. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(LOW PRI, 2G PS,
Uplink)
Bandwidth for admitting low-priority 2G PS services in the uplink.

It is valid only when reserved bandwidth is used for admitting
services.
Admitted Bandwidth
(LOW PRI, 2G PS,
Downlink)
Bandwidth for admitting low-priority 2G PS services in the

downlink. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Data, FR)
Bandwidth for admitting 2G CS data FR services with high

admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Data, HR)
Bandwidth for admitting 2G CS data HR services with high

admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Voice, AMR, FR)
Bandwidth for admitting 2G CS voice AMR FR services with high

admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Voice, AMR, HR)
Bandwidth for admitting 2G CS voice AMR HR services with high

admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Voice, Not AMR, FR)
Bandwidth for admitting 2G CS non-AMR voice FR services with

high priorities. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(HIGH PRI, 2G CS,
Voice, Not AMR, HR)
Bandwidth for admitting 2G CS non-AMR voice HR services with

high priorities. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(HIGH PRI, 2G PS,
Uplink)
Bandwidth for admitting high-priority 2G PS services in the

uplink. It is valid only when reserved bandwidth is used for
admitting services.
Admitted Bandwidth
(HIGH PRI, 2G PS,
Downlink)
Bandwidth for admitting high-priority 2G PS services in the

downlink. It is valid only when reserved bandwidth is used for
admitting services.

166
BSC6910 GSM
LMT User Guide
Statistic Item
(Original)
Description
Reserved Threshold
for Handover
Threshold for reserving bandwidth for handovers. It equals

configured bandwidth minus handover reserved bandwidth.
To query the handover reserved bandwidth, run the ADD
to PERCENTAGE(Percentage), the handover reserved
handover reserved ratio.
RealTimeFluxBw
Real-time traffic on a port.
Realtime Bandwidth
Bandwidth detected on a port.
RealTimeQueueFlux
Real-time traffic in the service queues on a port.
Congestion Clear
Threshold
Congestion end threshold. It equals configured bandwidth minus

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

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

ADD IPLOGICPORT command, Total Bandwidth equals
configured bandwidth. When Auto adjust bandwidth switch is
set to ON(ON), Total Bandwidth fluctuates between Max
bandwidth [64kbps] and Min bandwidth [64kbps] based on
transmission quality indicated by IPPOOLPM detection.
Table 8-3 Statistic Item(Statistic)
Issue 08 (2014-06-09)
Statistic Item
(Statistic)
Description
Admitted Bandwidth
(2G CS)
Bandwidth for admitting 2G CS services. It equals Admitted

Bandwidth(2G CS, HIGH PRI) plus Admitted Bandwidth(2G
CS, LOW PRI).
Admitted Bandwidth
(2G CS, HIGH PRI)
Bandwidth for admitting high-priority 2G CS services.

167
BSC6910 GSM
LMT User Guide
Statistic Item
(Statistic)
Description
Admitted Bandwidth
(2G CS, LOW PRI)
Bandwidth for admitting low-priority 2G CS services.
Admitted Bandwidth
(2G PS)
Bandwidth for admitting 2G PS services. It equals Admitted

Bandwidth(2G PS, HIGH PRI) plus Admitted Bandwidth(2G
PS, LOW PRI).
Admitted Bandwidth
(2G PS, HIGH PRI)
Bandwidth for admitting high-priority 2G PS services.
Admitted Bandwidth
(2G PS, LOW PRI)
Bandwidth for admitting low-priority 2G PS services.
Admitted Bandwidth
(2G Total)
Total admitted bandwidth for 2G services at the transport layer on

the user plane and control plane. The 2G services consist of 2G CS
and PS services.
Available Bandwidth
Bandwidth available currently. It equals Total Bandwidth minus

Admitted Bandwidth(3G Total) minus Admitted Bandwidth
(2G Total) minus signaling bandwidth. Admitted Bandwidth(2G
Total) is valid when 2G and 3G services share the same port.
Congestion Clear
Threshold
Congestion end threshold. It equals configured bandwidth minus

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

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

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

168
BSC6910 GSM
LMT User Guide
Statistic Item
(Statistic)
Description
OLC Threshold
Overload control (OLC) start threshold. It equals configured

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

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

ADD IPLOGICPORT command, Total Bandwidth equals
configured bandwidth. When Auto adjust bandwidth switch is
set to ON(ON), Total Bandwidth fluctuates between Max
bandwidth [64kbps] and Min bandwidth [64kbps] based on
transmission quality indicated by IPPOOLPM detection.
----End
8.2.4 Monitoring BER Seconds

This section describes how to detect the BER seconds on an E1/T1 port to monitor the
transmission quality of the link corresponding to the port. If any bit error occurs on the E1/T1
port, you can start this task to obtain data such as Errored Second, Severely Errored Second,
Unavailable Second, Frame Errors, CRC Errors, Bit Error Rate (calculated by CRC Errors).
Based on the data, you can evaluate the operating condition of the transmission network and
find out the causes for the bit errors in combination with the performance of the peer end. The
POUc board supports this function.
Prerequisites
l
Issue 08 (2014-06-09)

169
BSC6910 GSM
LMT User Guide
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > BERS
Monitoring. The BERS Monitoring dialog box is displayed.
Step 3 In the displayed BERS Monitoring dialog box, set the parameters as required, and click
Submit.
l Subrack No.: indicates the number of the subrack where the E1/T1 link is located.
l Slot No.: indicates the number of the slot where the E1/T1 link is located.
l E1/T1 Link No.: indicates the number of the E1/T1 link.
You can query the settings of the preceding parameters by running the LST E1T1 command.
----End
Result
l
The list shows the real-time monitoring results of Errored Second(s), Errored Second
Ratio(Percent), Severely Errored Second(s), Severely Errored Second Ratio
(Percent), Unavailable Second(s), Frame Errors, CRC Errors, and Error bit receiving
rate.
BER seconds (s) of the monitored link.
NOTE
Related parameters:
l Errored Second: Time interval of one second during which a given digital signal is received with one
or more errors.
l Severely Errored Second: A one-second period which has a bit error ratio >=110-3 or at least one
defect. Time interval of one second during which a given digital signal is received with an error ratio
greater than 1x10-3.
l Unavailable Second: A link is unavailable if 10 consecutive severe error seconds occur. A link is
available if 10 consecutive non-severe error seconds occur. The duration from 10 seconds before a link
becomes unavailable to 10 seconds before the link resumes available is the unavailable duration.
l Frame Errors: indicates the number of received frames that contain an error in the frame payload in
one direction of a single connection.
l CRC Errors: indicates the number of error bits detected in the CRC check.
l Errored Second: indicates the number of BER seconds.
l Severely Errored Second: indicates the number of severe BER seconds.
l Errored Second Ratio: indicates the ratio of erroneous second (ES) events to total seconds in the
available time during a fixed measurement interval.
l Severely Errored Second Ratio: indicates the ratio of severely erroneous second (SES) events to total
seconds in the available time during a fixed measurement interval.
Issue 08 (2014-06-09)

170
BSC6910 GSM
LMT User Guide
8.2.5 Monitoring BER

This section describes how to monitor bit error rate (BER), thereby evaluating transport network
quality.
Prerequisites
Context
l
Using this function interrupts transmission of an IMA group, UNI link, fractional ATM
link, carried on a board. Services carried on the corresponding port are therefore affected.
Before starting BER monitoring, you need to configure local loopback at the local end or
configure remote loopback at the peer end. Or you can connect the transmitting end to the
receiving end using a loopback connector.
BER monitoring and a loopback test cannot be performed simultaneously. The result and
principle of these two tasks are the same.
Only one BER monitoring task can be started for one board at a time.
Procedure
Step 1 Click Monitor in the LMT home page. The Monitor tab page is displayed.
Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > BER
Monitoring. The BER Monitoring dialog box is displayed.
Step 3 In the displayed BER Monitoring dialog box, set the parameters as required, and click
Submit.
l Subrack No.: indicates the number of the subrack where the E1/T1 link is located.
l Slot No.: indicates the number of the slot where the E1/T1 link is located.
l Board Type: indicates the type of the board where the E1/T1 link is located.
l Test Time by Minute: indicates the duration of the monitoring task.
l Period(S): indicates the period in which the monitoring results are reported.
l Port No.: indicates the number of the port where the E1/T1 link is located.
l Timeslot No.: indicates the timeslot on the E1/T1 link. This parameter needs to be set for
only interface boards using electrical ports.
You can query the settings of Subrack No., Slot No., Board Type, and Port No. by running
the LST E1T1 command.
----End
Result
monitoring results by list or chart. The task name and related parameters are displayed on the
Issue 08 (2014-06-09)

171
BSC6910 GSM
LMT User Guide
The list shows the real-time monitoring results of Unit BER(UNIT:1E-05) and Total BER
(UNIT:1E-05).
BER (1E-05) of the monitored link.
NOTE
Related parameters:
l Bit Error Ratio: Ratio of received bits that contain errors. BER is an important index used to measure
the communications quality of a network
l Unit BER: indicates the BER in a specified period
l Total BER: indicates the BER in a complete monitoring period
8.2.6 Monitoring Link Performance

This section describes how to monitor link performance. For the same monitoring item, you can
start a maximum of six monitoring tasks simultaneously. One monitoring task corresponds to
one link performance monitoring window. If six tasks are started, when you want to terminate
one of the six monitoring tasks, you must ensure that the link performance monitoring window
for this monitoring task is closed. Otherwise, this monitoring task will continue to occupy
resources. As a result, new monitoring tasks cannot be started.
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.
Prerequisites
Context
NOTICE
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.
For the FG2c, FG2d, GOUc, and GOUd boards, if the physical port carries a logical port and
Monitor Type for the link performance monitoring task is set to QoS, the queue statistics of the
physical port does not include the service data traffic on the logical port but only the service data
traffic on the physical port.
Issue 08 (2014-06-09)

172
BSC6910 GSM
LMT User Guide
Procedure
Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > Link
Performance Monitoring. The Link Performance Monitoring dialog box is displayed.
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to FE/GE. Set other
parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the FE/GE link is located.
l Slot No.: indicates the number of the slot where the FE/GE link is located.
l Monitor Type: You can set this parameter to Port or QoS.
l FE/GE Port No.: indicates the number of the port where the FE/GE link is located.
l Priority Group No.: If Monitor Type is set to QoS, you need to set this parameter to specify
the priority queue of a packet on the FE/GE port.
You can query the settings of the preceding parameters by running the LST ETHPORT
command.
----End
Result
l
When Monitor Type is set to Port, the list shows the real-time monitoring results of Rx
Traffic(bps), Tx Traffic(bps), Packet receiving number, Error packet receiving rate
(1/10000), Packet receiving speed(pps), and Packet sending speed(pps). When Monitor
Type is set to QoS, the list shows the real-time monitoring results of Tx Traffic(bps) and
Packet sending speed(pps).
In the chart, the X coordinate represents the hour: minute: second. The Y coordinate
represents the RX and TX traffic in bit/s.
Monitoring the PPP Link Traffic

This section describes how to monitor the traffic on a specified PPP link in real time. The realtime 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.
Prerequisites
Issue 08 (2014-06-09)

173
BSC6910 GSM
LMT User Guide
Context
NOTICE
The PPP 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.
For the POUc boards, if the physical port carries a logical port and Monitor Type for the link
performance monitoring task is set to QoS, the queue statistics of the physical port does not
include the service data traffic on the logical port but only the service data traffic on the physical
port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to PPP Link. Set other
l Subrack No.: indicates the number of the subrack where the PPP link is located.
l Slot No.: indicates the number of the slot where the PPP link is located.
l Monitor Type: You can set this parameter to Link or QoS.
l PPP Link No.: indicates the number of the PPP link.
the priority queue of a packet on the PPP link.
You can query the settings of the preceding parameters by running the LST PPPLNK command.
----End
Result
l
When Monitor Type is set to Link, the list shows the real-time monitoring results of Rx
(1/10000), Packet receiving speed(pps), Packet sending speed(pps), and Physics
Bandwidth Ratio(Percentage). When Monitor Type is set to QoS, the list shows the realtime monitoring results of Tx Traffic(bps) and Packet sending speed(pps).
Monitoring Traffic on the MLPPP Link Group

This section 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.
Issue 08 (2014-06-09)

174
BSC6910 GSM
LMT User Guide
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.
Prerequisites
Context
NOTICE
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.
For the POUc boards, if the physical port carries a logical port and Monitor Type for the link
performance monitoring task is set to QoS, the queue statistics of the physical port does not
include the service data traffic on the logical port but only the service data traffic on the physical
port.
Procedure
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to MLPPP Group. Set
other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the MLPPP group is located.
l Slot No.: indicates the number of the slot where the MLPPP link is located.
l Monitor Type: You can set this parameter to MLPPP Group or QoS.
l MLPPP Group No.: indicates the number of the MLPPP group.
the priority queue of a packet on the MLPPP group.
You can query the settings of the preceding parameters by running the LST MPGRP command.
----End
Result
l
Issue 08 (2014-06-09)
When Monitor Type is set to MLPPP Group, the list shows the real-time monitoring
results of Rx Traffic(bps), Tx Traffic(bps), Packet receiving number, Error packet
175
BSC6910 GSM
LMT User Guide
receiving rate(1/10000), Packet receiving speed(pps), Packet sending speed(pps), and

Physics Bandwidth Ratio(Percentage). When Monitor Type is set to QoS, the list shows
the real-time monitoring results of Tx Traffic(bps) and Packet sending speed(pps).
l
Monitoring the SCTP Link Traffic

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

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

176
BSC6910 GSM
LMT User Guide
Monitoring Traffic on a Logical Port

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

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

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

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

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

This section describes how to monitor the traffic on a specified trunk group in real time. The
real-time traffic on the specified trunk group is displayed in the form of list and chart. Together
with the statistics at both ends of the trunk group, the function can be used to confirm the IE
loss, help locate the fault, and evaluate the transmission network quality. The function can be
also used to compare the actual traffic volume with the user volume and obtain the utilization
of the port. In addition, the function can be used to evaluate the bandwidth condition and decide
whether to add a link to the trunk group for capacity expansion.
Issue 08 (2014-06-09)

179
BSC6910 GSM
LMT User Guide
Prerequisites
Context
NOTICE
The trunk group to be monitored is configured successfully.
Procedure
Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to TRUNK
Group. Set other parameters as required, and then click Submit.
l Subrack No.: indicates the number of the subrack where the TRUNK group is located.
l Slot No.: indicates the number of the slot where the TRUNK group is located.
l TRUNK Group No.: indicates the number of the TRUNK group.
You can query the settings of the preceding parameters by running the LST ETHTRK
command.
----End
Result
l
The list shows the real-time monitoring results of Rx Traffic(bps), Tx Traffic(bps),

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

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

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

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

181
BSC6910 GSM
LMT User Guide
Context
NOTICE
The 10GE 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
Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to 10GE. Set other
l Subrack No.: indicates the number of the subrack where the 10GE link is located.
l Slot No.: indicates the number of the slot where the 10GE link is located.
l 10GE Port No.: indicates the number of the port where the 10GE link is located.
the priority queue of a packet on the 10GE port.
You can query the settings of Subrack No., Slot No., and 10GE Port No. by running the LST
ETHPORT command.
----End
Result
l
When Monitor Type is set to Port, the list shows the real-time monitoring results of Rx
(1/10000), Packet receiving speed(pps), and Packet sending speed(pps). When Monitor
Type is set to QoS, the list shows the real-time monitoring results of Tx Traffic(bps) and
Packet sending speed(pps).
8.3 GSM Monitoring

This section describes the performance monitoring of the GSM services.
Issue 08 (2014-06-09)

182
BSC6910 GSM
LMT User Guide
8.3.1 Monitoring Traffic on GPRS User Plane

This section describes how to monitor the GPRS user plane traffic on a UP subsystem of the
built-in PCU, including the uplink and downlink traffic on the Um and Gb interfaces. You can
perform this task to learn the UP subsystem load conditions on the Um and Gb interfaces.
Prerequisites
l
Context
A maximum of sixty-four GPRS User Plane Monitoring tasks can be started simultaneously.
Procedure
Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-click
GPRS Flux Monitoring.
Step 3 In the GPRS Flux Monitoring dialog box, set the parameters as required, and click Submit.
l Monitor Type: Set this parameter to Subrack/Slot or UP No.. If this parameter is set to
Subrack/Slot, Subrack No. and Slot No. need to be specified. If this parameter is set to UP
No., UP No. needs to be specified.
l Subrack No.: indicates the number of the subrack accommodating the GPU board.
l Slot No.: indicates the number of the slot accommodating the GPU board. If this parameter
is set to ALL, all DPU boards processing PS services in a subrack can be monitored.
l UP No.: indicates the number of the UP subsystem processing PS services.
l Monitor Period(s): indicates the sampling period for monitoring the traffic on the GPRS
user plane.
NOTE
After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring result
in the form of list and chart. The task name and related parameters are displayed on the title bar of the window.
----End
8.3.2 Monitoring Cell Performance

This section describes how to monitor the performance of a GSM cell, including the uplink and
downlink RX level, UL and DL RX quality, MS and BTS TX power, and CS service rate. By
performing this task, you can evaluate the performance of the cell through the traced
measurement reports during a call of a specific MS in a cell.
Prerequisites
Issue 08 (2014-06-09)

183
BSC6910 GSM
LMT User Guide
Context
NOTICE
Only the cell performance related to the CS services can be monitored. The cell performance
related to the PS services is unavailable.
A maximum of sixty-four Cell Performance Monitoring tasks can be started simultaneously.
Procedure
Cell Performance Monitoring.
Step 3 In the displayed Cell Performance Monitoring dialog box, set the parameters as required, and
click Submit.
l Trace Object Type: Set this parameter to TMSI, IMSI, MSISDN, or IMEI.
NOTE
l TMSI: temporary mobile subscriber identity. Regarding security of mobile subscribers, the TMSI is
transmitted over the Um interface instead of IMSI.
l IMSI: international mobile subscriber identity, which uniquely identifies a subscriber.
l MSISDN: mobile station international ISDN number. ISDN is short for integrated services digital
network. This number indicates a number dialed when a call is initiated to a mobile subscriber in the
PLMN.
l IMEI: international mobile equipment identity, which uniquely identifies an MS.
l TMSI(Hex)/IMSI/MSISDN/IMEI(14 or 15 digits?): TMSI, IMSI, MSISDN, or IMEI

can be specified for this parameter based on the actual situation.
l Monitor Type: Set this parameter to UL/DL RxLevel, UL/DL RxQuality, MS/BTS Tx
power, or CS Rate.
l Monitor Period(s): period for reporting the monitor result.
NOTE
----End
8.3.3 Monitoring CS UP Resources

This section describes how to monitor the CS UP usage and the number of transmission service
types of the system.
Prerequisites
l
Issue 08 (2014-06-09)
184
BSC6910 GSM
LMT User Guide
Context
A maximum of sixty-four CS UP Resources Monitoring tasks can be started simultaneously.
Procedure
CS UP Resource Monitoring.
Step 3 In the CS UP Resource Monitoring dialog box, set the parameters as required, and click
Submit.
NOTE
in the form of table and chart. The task name and related parameters are displayed on the title bar of the window.
In the chart, the horizontal coordinate indicates the time and the vertical coordinate indicates the number of
speech channels processed by the DSP in real time.
In the table, the number of speech channels processed by the DSP is displayed in real time, which can be used
to evaluate the load processed by the DSP.
----End
8.3.4 Monitoring BTS IP Link Performance

This section describes how to monitor the performance of IP links in a BTS. eGBTS does not
support this function.
Prerequisites
Context
NOTICE
The GTMUa board does not support this function.
A maximum of sixty-four BTS IP Link Performance Monitoring tasks can be started
simultaneously.
Procedure
BTS IP Link Performance Monitoring.
Step 3 In the BTS IP Link Performance Monitoring dialog box, set the parameters as required, and
click Submit.
Issue 08 (2014-06-09)

185
BSC6910 GSM
LMT User Guide
l Monitor Item: This parameter can be set to FE/GE, PPP, MLPPP, IP_FE/GE, IP_PPP,
IP_MLPPP, TUNNEL, ETHOAM_LOSS_PACKET, or
ETHOAM_DELAY_JITTER.
FE/GE: layer 2 link on the Ethernet port, which can be queried by running the LST
BTSETHPORT command.
PPP: layer 2 PPP link, which can be queried by running the LST BTSPPPLNK
command.
MLPPP: layer 2 MLPPP link, which can be queried by running the LST BTSMPGRP
command.
IP_FE/GE: layer 3 link on the Ethernet port, which can be queried by running the LST
BTSETHPORT command.
IP_PPP: layer 3 PPP link, which can be queried by running the LST BTSPPPLNK
command.
IP_MLPPP: layer 3 MLPPP link, which can be queried by running the LST
BTSMPGRP command.
TUNNEL: layer 3 tunnel link, which can be queried by running the LST
BTSTUNNEL command.
ETHOAM_LOSS_PACKET: Ethernet packet loss. When this item is monitored, the
ACT BTSETHDM command must be executed.
ETHOAM_DELAY_JITTER: round trip delay jitter. When this item is monitored, the
ACT BTSETHLM command must be executed.
NOTE
After the monitoring task is started successfully, the real-time monitoring window is displayed. The title bar
shows the task name and relevant parameters. The real-time monitoring result can be queried in form of
table and chart.
l BTS Index: index of the BTS corresponding to the monitor item.

l Cabinet No.: number of the cabinet corresponding to the monitor item.
l Subrack No.: number of the subrack corresponding to the monitor item.
l Slot No.: number of the slot corresponding to the monitor item.
l Port No.: Ethernet port No. This parameter needs to be specified when Monitor Item is set
to FE/GE or IP_FE/GE.
l MLPPP Group No.: MLPPP group No. This parameter needs to be specified when Monitor
Item is set to MLPPP or IP_MLPPP.
l Signaling Link ID: PPP link No. This parameter needs to be specified when Monitor
Item is set to PPP or IP_PPP.
l Tunnel ID: tunnel No. This parameter needs to be specified when Monitor Item is set to
TUNNEL.
l Session ID: measurement session No., which corresponds to SESSIONID in the ACT
BTSETHLM or ACT BTSETHDM command. This parameter needs to be specified when
Monitor Item is set to ETHOAM_LOSS_PACKET or ETHOAM_DELAY_JITTER.
----End
Issue 08 (2014-06-09)

186
BSC6910 GSM
LMT User Guide
Result
After the monitoring task is started successfully, the real-time monitoring window is displayed.
The title bar shows the task name and relevant parameters. The real-time monitoring results are
displayed in the form of table.
l
In the table, real-time monitoring results of the received traffic (bit/s), received error
packets, total received packets, sent traffic (bit/s), total packets sent in a reporting period,
discarded packets in a reporting period, received error packets in a reporting period, and
total packets in a reporting period are displayed.
NOTE
The relevant parameters are as follows:

l
Rx Traffic(bps): traffic received on a BTS port per second (unit: bit/s).
Rx Error Packet: number of error packets received on a BTS port in a reporting period.
Rx Total Packet: total number of packets received on a BTS port in a reporting period.
Tx Traffic(bps): traffic sent on a BTS port per second (unit: bit/s).
Tx Total Packet per period: total number of packets sent on a BTS port in a reporting period.
Tx Discard Packet per period: number of packets discarded on a BTS port in a reporting period.
Rx Error Packet per period: number of error packets received on a BTS port in a reporting period.
Rx Total Packet per period: number of packets received on a BTS port in a reporting period.
The reporting period is 1s.
8.3.5 Monitoring Spectrum Scan

This section describes how to monitor spectrum scan. By scanning frequencies in a specified
band, the Received Signal Strength Indicator (RSSI) value is obtained and reported to the LMT.
Based on the reported value, an approximate spectrogram is obtained. Obtaining the spectrogram
remotely by using the LMT facilitates remote preliminary troubleshooting of interference.
eGBTS does not support this function.
Prerequisites
l
For Off-line Spectrum Scan:

The LMT works properly.
Communication between the LMT and the BSC is normal.
The RX channel of the TRX to be scanned is in the available state.
The TRX to be scanned is not the BCCH TRX.
During a channel-level test, the No. of the channel to be tested cannot be the same as
that of the channel carrying BCCH, CCCH, or CBCH. In addition, at least two SDCCHs
must be used for tests.
The bandwidth range to undergo spectrum scan does not exceed the one supported by
the TRX.
All other tests related to the TRX are stopped before a spectrum scan is started.
NOTE
Off-line Spectrum Scan function is intended for Huawei technical support personnel. For use of it, contact
Huawei Customer Service Center.
l
Issue 08 (2014-06-09)
For Frequency Time Domain Scan:

187
BSC6910 GSM
LMT User Guide
The LMT works properly.

Communication between the LMT and the BSC is normal.
The RX channel of the TRX to be scanned is in the available state.
The RX channel must be TCHF/TCHH/PDCH.
Context
NOTICE
l Only one spectrum scan task can be performed simultaneously in each base station.
l Off-line spectrum scan consists of channel-level spectrum scan and TRX-level spectrum
scan. When the spectrum of a channel is scanned, channels of all TRXs in the same cell with
the same timeslot number as that of the channel are all blocked. The TRX carrying the channel
is also blocked. When the spectrum of a TRX is scanned, all TRXs in the same cell except
the BCCH TRX are blocked.
l For Off-line Spectrum Scan, starting the scanned cell after a spectrum scan is complete
triggers a level-2 reset. The reset lasts for about 15 to 20 seconds.
Procedure
Step 2 Under Monitor Navigation Tree, choose Monitor > GSM Monitoring > Spectrum Scan
Monitoring. The Spectrum Scan Monitoring dialog box is displayed.
Step 3 In the displayed Spectrum Scan Monitoring dialog box, set parameters as required.
l Monitor Item: select Off-line Spectrum Scan or Frequency Time Domain Scan.
Performing wideband offline spectrum scanning in a common cell may block the cell.
Performing wideband offline spectrum scanning in a multi-site cell subsite may lead to call
drops in all subsites of the cell and block the cell. A level-2 reset is performed after a scan.
It scans frequencies within a frequency band. Scanning spectrum on line does not block cells
or disrupt ongoing services. However, only frequencies in use can be scanned.
l Site: indicates the site name of the cell to have its spectrum scanned. To query the site index,
run the LST BTS command.
l Cell: indicates the name of the cell to have its spectrum scanned. To query the cell index,
run the LST GCELL command.
l Location Group Number:indicates the NO. of the location group to have its spectrum scanned.
To query the cell index, run the LST BTSLOCGRP command.
l TRX: uniquely identifies within a BSC6910 the TRX of non-BCCH channels to have their
spectrum scanned. To query the TRX index, run the LST GTRX command.
l Channel No.: indicates the channel number of the TCH or PDCH to have its spectrum
scanned.
l Duration(Minute): indicates the lasting time of the scan.
l Test Type: Off-line spectrum scan supports channel-level spectrum scan and TRX-level
spectrum scan.
Issue 08 (2014-06-09)

188
BSC6910 GSM
LMT User Guide
l RBW: indicates resolution bandwidth that determines scan precision.

l Start Frequency(0.1M)/End Frequency(0.1M): indicates the start and end frequencies to be
scanned. Frequencies in the range of the start frequency to the end frequency are scanned.
As their unit is 0.1M, the start and end frequencies are the typed values multiplied by 0.1.
Step 4 Click Submit to start the monitoring. Figure 8-3 shows the results.
NOTE
l After the monitoring task has started, a monitoring window is displayed showing the real-time
monitoring result by list or chart. The task name and related parameters are displayed on the title bar
of the window.
l Right-click in the result diagram and select set marker point. In the displayed window, you can specify
three frequencies and view their power values.
l Right-click in the result diagram and select show marker point by sequence diagram. In the displayed
window, specify a frequency and you can see power change of the specified frequency at different
points of time.
l Right-click in the result diagram and select keep maximum value. In the displayed window, the
maximum power of frequencies within the frequency range and test time range is displayed.
Figure 8-3 Results of monitoring spectrum scan
----End
8.3.6 Clock Test

This section describes how to monitor a site clock. This function enables easier maintenance
and testing of the site clock. This function provides optimized measures for facilitating rapid
location of clock problems. Two monitoring options are provided on the LMT: Network Dither
and Phase/Frequency Discrimination. When a clock fault occurs, monitor Network Dither to
determine whether the fault is caused by transmission or the clock algorithm; monitor Phase/
Issue 08 (2014-06-09)

189
BSC6910 GSM
LMT User Guide
Frequency Discrimination to optimize the clock algorithm. eGBTS does not support this
function.
Prerequisites
l
The test base station is a BTS3900 series base station such as DBS3900 GSM, BTS3900
GSM, BTS3900A GSM, DBS3036, BTS3036, BTS3036A, BTS3900L GSM, BTS3900B
GSM, BTS3900E GSM and BTS3900AL.
Frequency discrimination: The clock algorithm enables frequency difference between the
clock reference and the Oven Controlled Crystal Oscillator (OCXO) in use to be
periodically reported during frequency synchronization. The frequency discrimination
value symbolizes the difference between the two frequencies. The unit is ppb and one
thousand ppb equals one ppm.
Phase discrimination: Each time CPU interruption is triggered for phase discrimination,
the logical algorithm interrupts CPU and thereby enables phase difference between the
clock reference and the OCXO in use to be reported to software during time
synchronization. The phase discrimination value symbolizes the difference between the
two phases. The unit is ns.
Dither: Monitoring of dither reflects periodical fluctuation in the reference frequency.

Large fluctuation may cause the clock unable to be locked.
Context
NOTICE
An alarm reporting a great frequency deviation will be generated when the frequency
discrimination value is large or dither is serious. In this case, there is great frequency difference
between the base station clock and the clock server. As a result, the clock is unable to be locked
for clock synchronization, which greatly affects ongoing services.
Procedure
Step 2 Under Monitor Navigation Tree, choose Monitor > GSM Monitoring > Clock Test. The
Clock Test dialog box is displayed.
Step 3 In the displayed Clock Test dialog box, set parameters as required.
l Monitor Item: select PDV NetWork Dither or Phase/Frequency Discrimination.
l Site: indicates the index of the site to have its site clock monitored. To query the site index,
run the LST BTS command.
l Duration (10 min): indicates the duration for monitoring the BTS clock. The unit of this
parameter is 10 minutes.
NOTE
The PDV NetWork Dither item cannot be performed on BTSs that support Abis over TDM transmission.
Step 4 Click Start to start the monitoring. Figure 8-4 or Figure 8-5 shows the results.
Issue 08 (2014-06-09)

190
BSC6910 GSM
LMT User Guide
NOTE
l When Phase/Frequency Discrimination is selected, the corresponding phase/frequency

discrimination value is displayed in the monitoring result diagram. To be more specific, a frequency
discrimination value is displayed during frequency synchronization and a phase discrimination value
is displayed during phase synchronization.
l In the diagram showing results of network dither, MIN TP1/MAX TP1 indicates the minimum/
maximum uplink delay in transmitting packets from the IP clock server to an IP client. MIN TP2/MAX
TP2 indicates the minimum/maximum downlink delay in transmitting packets from an IP client to the
IP clock server.
l You can click
to select the path to save the monitoring files.
Figure 8-4 Clock Test (phase/frequency discrimination)
Figure 8-5 Clock Test (network dither)
----End
8.3.7 Monitoring DTF Test

This section describes how to monitor the DTF test. eGBTS does not support this function.
Issue 08 (2014-06-09)

191
BSC6910 GSM
LMT User Guide
Prerequisites
Procedure
DTF Test.
Step 3 In the DTF Test dialog box, set the parameters as required, and click Submit.
NOTE
----End
8.3.8 Monitoring Intermodulation Interference in Frequency

Scanning Mode
This task traverses and checks intermodulation counters of all frequencies in the receive
bandwidth and presents the check results in diagrams.
Prerequisites
l
You have logged in to the local maintenance terminal (LMT) using an authorized account.
Context
Intermodulation interference monitoring in frequency scanning mode can replace the functions
of a passive intermodulation analyzer. It monitors interference impacts of different frequencies
within the downlink receive bandwidth based on the hardware capability of RF modules.
NOTE
Ensure that the following conditions are met before monitoring intermodulation interference.
l
The RF module connected to the antenna port does not generate a major alarm. Otherwise, stop monitoring.
The start and end monitoring frequencies must be within the frequency range supported by the RF module.
Procedure
Step 2 In the Monitor Navigation Tree pane, choose Monitor > GSM Monitoring, and double-click
Frequency Scanning Intermodulation Interference Detection.The Frequency Scanning
Intermodulation Interference Detection dialog box is displayed, as shown in Figure 8-6.
Issue 08 (2014-06-09)

192
BSC6910 GSM
LMT User Guide
Figure 8-6 Frequency Scanning Intermodulation Interference Detection dialog box
Step 3 In the displayed Frequency Scanning Intermodulation Interference Detection dialog box,
set parameters as follows:
l Site: set Site to the ID of the site serving the cell requiring frequency scanning. You can run
the LST BTS command to query the site ID.
l Cabinet No.:set Cabinet No. to the No. of the cabinet where the RRU performing
intermodulation interference detection in frequency scanning mode is installed.
l Subrack No.:set Subrack No. to the No. of the subrack where the RRU performing
intermodulation interference detection in frequency scanning mode is installed.
l Slot No.:set Slot No. to the No. of the slot where the RRU performing intermodulation
interference detection in frequency scanning mode is installed.
l Antenna Tributary No.:set Antenna Tributary No. to the No. of the antenna tributary on
the RXU.
l Low Frequency(0.1MHz)/High Frequency(0.1MHz):set Start Freq(0.1MHz) and End
Freq(0.1MHz) to the start and end frequencies, respectively. The two parameters together
identify the frequency scanning range (unit 0.1 MHz).
NOTE
If users do not specify the parameters, the BSC sets the parameters to appropriate values based on module
types.
l Frequency Step(0.1MHz):set Freq Step(0.1MHz) to the transmit frequency step for

intermodulation interference in frequency scanning mode.
NOTE
If users do not specify the parameters, the BSC sets the parameters to appropriate values based on module
types.
Issue 08 (2014-06-09)

193
BSC6910 GSM
LMT User Guide
Step 4 Click Submit. A real-time performance monitoring window is displayed. You can view the
frequency scanning intermodulation interference monitoring results on the Chart or List tab
page.
----End
8.4 General Operations of Performance Monitoring

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

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

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

194
BSC6910 GSM
LMT User Guide
Prerequisites
l
Procedure
Step 1 In the task information pane at the bottom of the window, click the property boxes of the Line
Color, Line Type, or Line Width column.
Step 2 Select the required properties from the drop-down lists.
NOTE
l The setting of the display properties applies only to the current monitoring task.
l If data is displayed on the List tab page but no chart is displayed on the Chart tab page during the realtime monitoring, set the display properties of the chart.
----End
8.4.3 Saving Monitoring Results

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

This section describes how to browse the monitoring results of the CPU usage and BER
seconds in offline mode.
Prerequisites
The monitoring results are saved to files.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecording
Review Tool.
Step 2 Open the directory where the monitoring results are saved. The default save path is C:/Web
LMT/MBSC/output/monitor. Select the result file corresponding to the monitoring task.
Issue 08 (2014-06-09)

195
BSC6910 GSM
LMT User Guide
Step 3 Click Open or double-click the file. The TrafficRecording Review Tool window is displayed,
providing the monitoring results in chart and list.
Step 4 Click the List tab or the Chart tab to view the data in different modes.
Step 5 To view other saved results, choose File > Open. In the Open dialog box, select the target files
to read the details.
----End
8.5 Reference for Performance Monitoring

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

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

l To query the number of the MP Group
physical port , run the LST MPGRP
command.
l To query the number of the PPP Link
physical port , run the LST PPPLNK
command.
Link
Performanc
e
Monitoring
Issue 08 (2014-06-09)
FE/GE
FE/GE Port
No.
Indicates the number of the FE/GE port. To

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

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

query the number of the MLPPP group, run the
LST MPGRP command.
10GE
10GE Port No.
Indicates the number of the 10GE port. To

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

query the SCTP link, run the LST
SCTPLNK command.
Logical
Port
Port No.
Indicates the number of a logical port. To

query the IP logical port, run the LST

196
BSC6910 GSM
LMT User Guide
Monitor Item
Parameter
Description
Logical
Port
Bandwidth
Logical Port
No.
Indicates the number of a logical port. To

query the IP logical port, run the LST
FE/GE
Priority Group
No.
Indicates the priority queue number. (value

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

ATM optical port. To query the optical port,
run the LST OPT command.
Trunk
Group
Trunk Group
No.
Indicates the number of the trunk group. To

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

IPPOOLIP command.
Monitor Type
You can choose to monitor the following items

of the cell:
Logical
Port
GSM Cell Performance

Monitoring
l UL/DL RxLevel: uplink receive level of

the BTS and downlink receive level of the
MS in the cell whose performance is
monitored.
l UL/DL RxQuality: uplink receive quality
of the BTS and downlink receive quality of
the MS in the cell whose performance is
monitored.
l MS/BTS Tx power: transmit power of the
MS and BTS
l CS Rate: rate of a single channel.
Issue 08 (2014-06-09)

197
BSC6910 GSM
LMT User Guide
9 Device Panel
Device Panel
About This Chapter

This chapter describes how to manage the BSC6910 equipment by using the device and
emulation panels. You can use these panels to query for information about the boards, board
ports, board links, and board alarms.
9.1 Device Panel Operations
This section describes the operations of the BSC6910 device panel, including how to start and
use it and how to query the status of the boards.
9.2 Emulation Panel Operations
This section describes the operations of the BSC6910 emulation panel. By performing this task,
you can learn about how to start and use it, and how to query the status of the boards.
9.3 Activating BTS
This section describes how to activate a BTS. Only the user admin, users at ADMINISTRATOR
level, or users at CUSTOM level with related rights can activate a BTS.
9.4 Deactivating BTS
This section describes how to deactivate a BTS. Only the user admin, users at
ADMINISTRATOR level, or users at CUSTOM level with related rights can deactivate a BTS.
9.5 Querying the BTS Alarm
This section describes how to query the BTS alarm.
Issue 08 (2014-06-09)

198
BSC6910 GSM
LMT User Guide
9 Device Panel
9.1 Device Panel Operations

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

In addition to MML commands, the LMT also provides the graphical device panel to facilitate
device maintenance. eGBTS does not support this function.
The device panel is automatically refreshed, showing board status in real time with the help of
board colors and alarm indicators on the board.
On the device panel, you can right-click a board in position and choose operations from the
shortcut menu. For example, you can query the board status. Figure 9-1 shows the device panel.
Figure 9-1 Device Panel
Alarm indicators represent the alarm status of a board, and board colors indicate the running
status of a board. See the color descriptions shown on the right side of the device panel for
specific meanings of alarm indicators and board colors.
l
. The drop-down
If the tab page under Device Maintenance is not in full view, click
list is displayed. Choose the required menu to display the corresponding tab page.
You can right-click the peripheral frame of a rack, and choose Refresh Shelf from the
shortcut menu to refresh the rack.
If you select Display Logic Function under the color descriptions of the board, the logic
functions of boards are displayed on the device panel.
NOTE
When a UPEU/UEIU/USCU/FAN board reports a minor or higher-level alarm, the board is displayed red
on the LMT. Users need to check whether the board functions normally based on the alarm. For other BTS
boards, the BTS determines the board color and status based on the impacts caused by a specific alarm.
Issue 08 (2014-06-09)

199
BSC6910 GSM
LMT User Guide
9 Device Panel
9.1.2 Starting the Device Panel

This section describes how to start the device panel.
Prerequisites
Procedure
Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is
displayed.
Step 2 The BSC device panel is displayed in the BSC Device Panel tab page.
Step 3 Unfold BSC under Device Navigation Tree. Click the required BTS, and the corresponding
BTS device panel is displayed in the BTS Device Panel tab page on the right.
NOTE
For the BTS3900E, If the dot on the board of the topology structure panel is in green
main processing board. If the dot on the board of the topology structure panel is in gray
a non-main processing board.
, this board is a
, this board is
----End
9.1.3 Querying the Status of an E1/T1 Port

This section describes how to query the status of an E1/T1 port.
Prerequisites
l
The boards are in position.
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel
(see 9.2.2 Starting the Emulation Panel).
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, and
choose Query E1/T1 Port Status from the shortcut menu. The displayed Query E1/T1 Port
Status shows the details about the E1/T1 port.
----End
9.1.4 Querying the CPU Usage

Issue 08 (2014-06-09)

200
BSC6910 GSM
LMT User Guide
9 Device Panel
Prerequisites
l
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
l

1.
Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation
panel (see 9.2.2 Starting the Emulation Panel).
2.
Right-click a board in position in the device panel or emulation panel, and then choose
CPU Usage Query from the shortcut menu. The CPU Usage window is displayed,
showing the real-time CPU usage.

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

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

1.
Open the device panel (see 9.1.2 Starting the Device Panel) or open the emulation
2.
Query BSC Board Clock Status from the shortcut menu. The Query BSC Board
Clock Status dialog box is displayed.
3.
In the Query BSC Board Clock Status dialog box, set the parameters as required,
and click Query.

1.
Issue 08 (2014-06-09)
Click Device Maintenance on the LMT main page. The Device Maintenance tab
page is displayed.
201
BSC6910 GSM
LMT User Guide
9 Device Panel
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >
Query BSC Board Clock Status. The Query BSC Board Clock Status dialog box
is displayed.
3.
and click Query.
Figure 9-2 Querying results of BSC Board Clock Status

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

This section describes how to query the status of a BSC board.
Prerequisites
l
Context
You can query the status of a board through menu operations or through MML commands.
Procedure
l
Issue 08 (2014-06-09)

1.
Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation
2.
Query BSC Board Information from the shortcut menu. The Query BSC Board
Information dialog box is displayed, showing details of the board.
202
BSC6910 GSM
LMT User Guide
9 Device Panel

1.
page is displayed.
2.
Query BSC Board Information. The Query BSC Board Information dialog box
is displayed.
3.
In the Query BSC Board Information dialog box, set the parameters as required,
and click Query.
Figure 9-3 Querying results of board status

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

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

203
BSC6910 GSM
LMT User Guide
9 Device Panel
Context
NOTICE
l If the standby board is not available or is faulty, resetting the board will disrupt the ongoing
services. Therefore, perform this operation with caution.
l Resetting the board 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 SCUb board is reset while its standby board is not available or
is faulty, the entire subrack is reset.
Procedure
l
Issue 08 (2014-06-09)

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

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

204
BSC6910 GSM
LMT User Guide
9 Device Panel
Figure 9-4 Resetting the BSC Board

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

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

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

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

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

206
BSC6910 GSM
LMT User Guide
9 Device Panel
Figure 9-5 Switching over a BSC board

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

This section describes how to query the BSC board alarm.
Prerequisites
l
Procedure
Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see
9.2.2 Starting the Emulation Panel).
Step 2 Right-click a board in position in the device panel or the emulation panel, and then choose Query
Board Alarm from the shortcut menu. The alarm information is displayed.
----End
9.1.10 Querying the BTS Board Information

This section describes how to query the detailed information about a BTS board. eGBTS does
Prerequisites
l
Issue 08 (2014-06-09)

207
BSC6910 GSM
LMT User Guide
9 Device Panel
Context
Procedure
l

1.
Start the BTS device panel (see 9.1.2 Starting the Device Panel).
2.
Right-click a board in position on the BTS device panel, and then choose Query Board
Information. The Query Board Information dialog box is displayed, showing
details of the board.
3.
To query the basic attributes of the BTS board, choose View Site Board from the
right-click shortcut menu.

1.
Run the DSP BTSBRD command to query the information about the BTS board.
----End
9.1.11 Resetting the BTS Board

This section describes how to reset a faulty BTS board. eGBTS does not support this function.
Prerequisites
l
Context
You can reset a board through menu operations or through MML commands.
Procedure
l

1.
2.
Right-click a board in position on the BTS device panel, and then choose Reset
Board.
3.
In the displayed Reset Board dialog box, set the parameters as required, and then
click Reset to reset the board.

1.
Run the RST BTSBRD command to reset a BTS board.
----End
9.1.12 Maintaining BTS Clock

This section describes how to query the clock information about the BTS board. eGBTS does
Issue 08 (2014-06-09)

208
BSC6910 GSM
LMT User Guide
9 Device Panel
Prerequisites
l
Context
Procedure
l

1.
2.
Right-click the main processing board on the BTS device panel, and then choose
Maintain Clock from the shortcut menu.
3.
In the displayed Maintain Clock dialog box, set the parameters as required, and click
Query.

1.
Run the LST BTSCLK command to query the BTS clock information.
----End
9.2 Emulation Panel Operations

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

The LMT provides the emulation panel for each subrack. The emulation subrack has the same
ports as those of the real subrack and helps to ascertain the status of each board.
The emulation panel displays the running status of the ports of each board and provides rightclick menus as shown in Figure 9-6.
Issue 08 (2014-06-09)

209
BSC6910 GSM
LMT User Guide
9 Device Panel
Figure 9-6 Emulation panel
The emulation panel has the following features:

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

This section describes how to start the emulation panel.
Prerequisites
Procedure
displayed.
Step 2 Click BSC6910 under Device Navigation Tree. The BSC Device Panel is displayed on the
right pane.
Issue 08 (2014-06-09)

210
BSC6910 GSM
LMT User Guide
9 Device Panel
Step 3 To display the emulation panel of a subrack, select the corresponding rack and double-click the
peripheral of the subrack, as shown in Figure 9-7.
Figure 9-7 Subrack peripheral
----End
9.2.3 Querying the Status of an E1/T1 Port

This section describes how to query the status of an E1/T1 port.
Prerequisites
l
Procedure
Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel
(see 9.2.2 Starting the Emulation Panel).
Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, and
choose Query E1/T1 Port Status from the shortcut menu. The displayed Query E1/T1 Port
Status shows the details about the E1/T1 port.
----End
9.2.4 Querying the CPU Usage

Issue 08 (2014-06-09)

211
BSC6910 GSM
LMT User Guide
9 Device Panel
Prerequisites
l
Context
You can query the CPU usage through menu operations or through MML commands.
Procedure
l

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

1.
Run the DSP CPUUSAGE command to query the CPU usage.
----End

Prerequisites
Context
commands.
Procedure
l

1.
2.
3.
and click Query.

1.
Issue 08 (2014-06-09)
page is displayed.
212
BSC6910 GSM
LMT User Guide
9 Device Panel
2.
is displayed.
3.
and click Query.

1.
----End

Prerequisites
l
Context
Procedure
l
Issue 08 (2014-06-09)

1.
2.
213
BSC6910 GSM
LMT User Guide
9 Device Panel

1.
page is displayed.
2.
is displayed.
3.
and click Query.

1.
----End

operation.
Prerequisites
l
Issue 08 (2014-06-09)

214
BSC6910 GSM
LMT User Guide
9 Device Panel
Context
NOTICE
l
Resetting the Board

Procedure
l
Issue 08 (2014-06-09)

1.
2.
Reset BSC Board.
3.
then click Reset.

1.
page is displayed.
2.
3.

215
BSC6910 GSM
LMT User Guide
9 Device Panel

1.
----End

Prerequisites
l
Issue 08 (2014-06-09)

216
BSC6910 GSM
LMT User Guide
9 Device Panel
Context
NOTICE
Procedure
l
Issue 08 (2014-06-09)

1.
2.
Switch BSC Board.
3.

1.
page is displayed.
2.
3.
1.

217
BSC6910 GSM
LMT User Guide
9 Device Panel

1.
----End
9.2.9 Querying the BSC Board Alarm

This section describes how to query the BSC board alarm.
Prerequisites
l
Procedure
Step 2 Right-click a board in position in the device panel or the emulation panel, and then choose Query
Board Alarm from the shortcut menu. The alarm information is displayed.
----End
9.2.10 Querying the Status of an FE Port

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

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

1.
Start the emulation panel (see 9.2.2 Starting the Emulation Panel).
2.
On the emulation panel of the subrack, right-click the FE port to be queried, and choose
Display Ethernet Port Status from the shortcut menu. The Display Ethernet Port
Status window is displayed, showing the details of the FE port status.

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

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

1.
2.
On the emulation panel of the subrack, right-click the GE port to be queried, and
choose Display Ethernet Port Status from the shortcut menu. The Display Ethernet
Port Status window is displayed, showing the details of the GE port status.

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

This section describes how to query the status of an optical port. POUc board supports this
function.
Prerequisites
l
Issue 08 (2014-06-09)

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

1.
2.
On the emulation panel, right-click the optical port to be queried, and choose Query
Optical Port Status and Performance from the shortcut menu. In the displayed
Query Optical Port Status and Performance window, specify the parameters as
required, and click Submit to query the detailed information about the optical port.

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

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

This section describes how to activate a BTS. Only the user admin, users at ADMINISTRATOR
level, or users at CUSTOM level with related rights can activate a BTS.
Prerequisites
l
The BTS is not activated.
Context
You can activate a BTS board through menu operations or through MML commands.
Issue 08 (2014-06-09)

220
BSC6910 GSM
LMT User Guide
9 Device Panel
Procedure
l

1.
page is displayed.
2.
In Device Navigation Tree, select the expected BTS, right-click it, and then choose
Activate BTS from the shortcut menu. In the displayed dialog box, click OK to
activate the BTS.

1.
Run the ACT BTS command to activate a BTS.
----End
9.4 Deactivating BTS

This section describes how to deactivate a BTS. Only the user admin, users at
ADMINISTRATOR level, or users at CUSTOM level with related rights can deactivate a BTS.
Prerequisites
l
The BTS is activated.
Context
You can deactivate a BTS through menu operations or through MML commands.
Procedure
l

1.
page is displayed.
2.
In Device Navigation Tree, select the required BTS, right-click it, and then choose
Deactivate BTS from the shortcut menu. In the displayed dialog box, click OK to
deactivate the BTS.

1.
Run the DEA BTS command to deactivate a BTS.
----End
9.5 Querying the BTS Alarm

This section describes how to query the BTS alarm.
Prerequisites
l
Issue 08 (2014-06-09)

221
BSC6910 GSM
LMT User Guide
9 Device Panel
Procedure
Step 2 In the Device Navigation Tree tab page, right-click the BTS whose alarm is to be queried. Then
choose Query BTS Alarm from the shortcut menu. The alarm information is displayed.
----End
Issue 08 (2014-06-09)

222
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10
BSC Maintenance
About This Chapter

This chapter describes how to maintain the BSC equipment, transmission and signaling links,
and user resources.
10.1 Concepts Related to BSC Maintenance
This section describes the basic concepts related to the BSC maintenance: BSC interface
processing subsystem and loopback.
10.2 Browsing Configuration Data
This section describes how to browse the configuration data, including the configuration data
of BSCs, BTSs, TRXs, and channels.
10.3 Backing Up Data
This section describes how to back up system data on the OMU. The system data includes
configuration data, alarm configuration data, and performance configuration data.
10.4 Restoring Data
This section describes how to restore configuration data on the OMU.
This function is used when faults occur and persist at a site and site maintenance personnel
cannot directly use the counters, alarms, and logs for fault analysis. This section describes how
to use the Fault Management Assistant function for rapid fault diagnosis. With this function, the
LMT analyzes counters, alarms, and logs of a site where a fault occurs by following the diagnosis
rules, and then sends an analysis report to guide users in rapid troubleshooting.
10.6 Batch Configuration
This task is performed to deliver batch configuration script files. Such files can be generated by
the CME or manually generated by operators.
10.7 OS Maintenance
The OS debugging function provides commands for querying the operating system (OS)
information and commands for system debugging. The OS information refers to timer, memory,
task, message, reset record, IPC info, MOT info and start record.
10.8 Maintaining the Equipment
This section describes how to maintain the BSC equipment.
Issue 08 (2014-06-09)

223
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10.9 Maintaining Transmission and Signaling

This section describes how to maintain the signaling link and the ports on the interface boards.
In the Device Navigation Tree, right-click the BSC node, and choose Maintain Transmission
and Signaling from the shortcut menu to perform the relevant tasks.
10.10 Maintaining BSC User Resources
This section describes how to maintain the user resources, including the port timeslot, interface
circuit, TC resources, call resources, subsystem channel or link, external speech channel. In the
Device Navigation Tree, right-click the BSC node, and choose Maintain User Resources from
the shortcut menu to perform the relevant tasks.
10.11 Querying Board Version Information
This section describes how to query the information about the software version, hardware
version, and patch version of the board.
Issue 08 (2014-06-09)

224
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10.1 Concepts Related to BSC Maintenance

This section describes the basic concepts related to the BSC maintenance: BSC interface
processing subsystem and loopback.
10.1.1 BSC Interface Processing Subsystem

The BSC interface processing subsystem consists of the following logical units: Abis interface
processing unit, A interface processing unit, Gb interface processing unit, and Cb interface
processing unit.
Figure 10-1 shows the interfaces between the BSC and other NEs.
Figure 10-1 Interfaces between the BSC and other NEs
As shown in Figure 10-1, the BSC is connected to the MSC/MGW over the A interface, to the
BTS over the Abis interface, to the SGSN over the Gb interface, and to the CBC over the Cb
interface.
Abis Interface Processing Unit

The BSC provides the Abis interface to communicate with the BTS. The Abis interface
processing unit performs the following functions:
l
Provides FE/GE/10GE ports
Receives and transmits the signaling and traffic signals between the BSC and the BTS
Converts internal protocols
Processes IP protocols
Issue 08 (2014-06-09)

225
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Forwards signaling to the service control subsystem
Forwards traffic signals to the service processing subsystem
A Interface Processing Unit

The BSC provides the A interface to communicate with the MSC/MGW. The A interface
l
Receives and transmits the signaling and traffic signals between the BSC and the MSC/
MGW
Converts internal protocols
Forwards the signaling from the core network (CN) to the GE switching subsystem
Forwards the traffic signals from the CN to the GE switching subsystem or to the TDM
switching subsystem
Gb interface processing unit

The BSC provides the Gb interface to enable the communication between the BSC and the
SGSN. The Gb interface processing unit performs the following functions:
l
Receives and transmits signaling and traffic signals between the BSC and the SGSN
Processes the signaling according to the IP protocol
Forwards signaling and traffic signals to the GE switching subsystem
Cb Interface Processing Unit

The BSC and the CBC communicate with each other over the Cb interface. The Cb interface
l
Receives and transmits the signaling between the BSC and the CBC
Forwards signaling to the GE switching subsystem
10.1.2 Loopback
You can perform loopback on a transmission device or a transmission channel by using hardware
or software.
You can ascertain whether the hardware is working properly and the software parameters are
set correctly, based on the operating status of the transmission equipment, channels, services,
and signaling interworking, after the self-loopback. Loopback test is a common method for
locating transmission faults and faults in trunk parameter setting.
Remember to disable the loopback after the test. Otherwise, services will not be supported on
the channels under the loopback test.
Loopback is classified into timeslot loopback, port loopback, and speech loopback.
NOTE
Only support TDM loopback.
Issue 08 (2014-06-09)

226
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Timeslot Loopback
Timeslot loopback is used to loop back data carried by the timeslot in the specified direction, as
shown in Figure 10-2. In the scenarios where Bad speech quality, sound mute or noise is
experienced during a conversation, timeslot loopback can be started to locate the fault.
Figure 10-2 Timeslot loopback
You can set the loopback direction by selecting a loopback mode. By doing this, you can analyze
whether the fault is on the system side or on the transmission lines or whether it is a transmission
problem or software problem.
Timeslot loopback mode:
l
Remote loopback
The signals received on a timeslot are sent out without being processed. Remote loopback
refers to the loopback performed on the MSC side.
Local loopback
The signals that should be placed in the sending direction are placed in the receiving
direction as the received data. Local loopback is performed on the BSC side.
Port Loopback
Port loopback is used to loop back the data received or transmitted by the port in the specified
direction, as shown in Figure 10-3.
Issue 08 (2014-06-09)

227
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Figure 10-3 Port loopback
Table 10-1 shows the loopback modes for different interface boards.
Table 10-1 Loopback modes for different interface boards
Interface Board
POUc
STM-1
Loopback Mode
Optical
port
Regenerator Section Line-side: All the ports that have

received signals send the signals back. The board where the
ports are located does not process signals.
Regenerator Section System Side: All the signals that
should be placed in the sending direction are placed in the
receiving direction and returned as the received data. The
signals are not sent to the ports on the peer interface board
through physical links.
Optical
tributary
Lower Order Path Line-side Loopback: A board processes

the signals received from ports and then sends the signals
back through the ports.
Optical Tributary Line-side Loopback: All the ports that
have received signals send the signals back. The board
where the ports are located does not process signals.
Optical Tributary System Side Loopback: All the signals
that should be placed in the sending direction are placed in
the receiving direction and returned as the received data.
The signals are not sent to the ports on the peer interface
board through physical links.
Issue 08 (2014-06-09)

228
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Interface Board
Loopback Mode
IP-based interface boards
Local Loopback: All the signals that should be placed in

the sending direction are placed in the receiving direction
and returned as the received data. The signals are not sent
to the ports on the peer interface board through physical
links.
Speech Loopback
On a speech channel, you can locate the segment where the speech problem occurs by comparing
the loopback speech with the original speech.
Speech loopback mode:
l
Remote speech channel loopback

You can locate the speech channel fault by performing the remote speech channel loopback
on the A interface and the Abis interface. If the fault is not on the remote speech channel,
you can test the internal speech channel to locate the fault, as shown in Figure 10-4 and
Figure 10-5.
Figure 10-4 Remote speech channel loopback-bts
Figure 10-5 Remote speech channel loopback-msc
l
Issue 08 (2014-06-09)
UP speech channel loopback

229
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
In the UP speech channel loopback over the A interface, the loopback point is set at the
RX port of the UP that receives the data from the A interface. Then, the data processed
by the UP is sent to the MS, and the data received from the A interface is sent out as
the source data. Therefore, the bi-directional loopback to both the MS and the MSC on
the UP is achieved, as shown in Figure 10-6.
In the UP speech channel loopback over the Abis interface, the loopback point is set at
the RX port of the UP that receives the data from the Abis interface. Then, the data
processed by the UP is sent to the MSC, and the data received from the Abis interface
is sent out as the source data. Therefore, the bi-directional loopback to both the MS and
the MSC on the UP is achieved, as shown in Figure 10-7.
Figure 10-6 A interface loopback
Figure 10-7 Abis interface loopback
10.2 Browsing Configuration Data

This section describes how to browse the configuration data, including the configuration data
of BSCs, BTSs, TRXs, and channels.
Prerequisites
Issue 08 (2014-06-09)

230
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Procedure
displayed.
Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Browse Configuration
Data. The Browse Configuration Data tab page is displayed.
Step 3 In the Browse Items navigation tree, select the items to be browsed and click Browse (or doubleclick the items to be browsed). The corresponding configuration data is displayed on the right
area.
Step 4 Click Save As to save the corresponding configuration data.
Step 5 To create a new template of browsing items, click New. In the displayed New dialog box, set
the Template Name and select the browsing items as required. Then, click OK.
Step 6 To modify or delete a template, select the template and click Modify or Delete.
----End
10.3 Backing Up Data

This section describes how to back up system data on the OMU. The system data includes
configuration data, alarm configuration data, and performance configuration data.
Prerequisites
l
When the database system crashes or an upgrade fails, start the tool used for backing up
and restoring system data in the mbsc\bam\common\services\omu_backup_linker
directory. With the latest backup data, you can recover the system.
If you need to recover only OMU configuration data, run the RTR DB command and select
a corresponding data backup file for data recovery.
Context
Procedure
Issue 08 (2014-06-09)
1.
page is displayed.
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Backup Data. The
Backup Data dialog box is displayed with information about backup files saved in
the OMU active workspace installation directory\data\backup directory.
3.
In the displayed Backup Data dialog box, click Backup to back up system data on
the OMU.

231
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTE
l The default directory for saving backup files is OMU active workspace installation directory
\data\backup. If such a directory does not exist, it will be created automatically.
l If the name of a backup file is not typed, the file is named BKPDB_#_*.bak automatically.
Here, "#" stands for the detailed version information of the working OMU and "*" stands for
the current system time when the backup is performed. When the number of backup files in the
backup directory exceeds 30, the earliest backup file is automatically deleted.
l The following special characters are forbidden in the file name: \\ / : * ? \" < > | ( ) & $ , %%
+++ = ; blank character
l Backup files cannot be saved in a network path, for example, \\10.161.162.25.
l No space is allowed in the file name or the saving directory. For example, "BK2009 09 08.bak"
is an illegal file name.
4.
In the displayed Backup Data dialog box, select a backup file and click
DownLoad to download the backup file to a local path on the LMT PC.
NOTE
Click Refresh to refresh backup files saved in the OMU active workspace installation directory
\data\backup directory in the Backup Data dialog box.
Through an MML command

1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the BKP DB command to back up system data on the OMU.
----End
10.4 Restoring Data

This section describes how to restore configuration data on the OMU.
Prerequisites
l
Context
NOTICE
l Restoring data overwrites OMU data, so restore data with caution.
l Versions of data backup files must be the same as the OMU version.
l Alarm information and operation logs are not restored. Their data remains unchanged.
l After restoring OMU data, run the RST BSC command to reset the BSC.
Procedure
l
Issue 08 (2014-06-09)

232
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
1.
page is displayed.
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Restore Data. The
Restore Data dialog box is displayed with information about data backup files saved
in the OMU active workspace installation directory\data\backup directory.
3.
Optional: In the displayed Restore Data dialog box, click Upload to upload a backup
file on the LMT PC to the OMU.
NOTE
Click Refresh to refresh backup files saved in the OMU active workspace installation directory
\data\backup directory in the Restore Data dialog box.
4.
l
In the displayed Restore Data dialog box, click Restore Data to restore configuration
data on the OMU.

1.
Run the LST BKPFILE command to query data backup files saved in the OMU
active workspace installation directory\data\backup directory.
2.
Run the RTR DB command to restore configuration data on the OMU.
----End

This function is used when faults occur and persist at a site and site maintenance personnel
cannot directly use the counters, alarms, and logs for fault analysis. This section describes how
to use the Fault Management Assistant function for rapid fault diagnosis. With this function, the
LMT analyzes counters, alarms, and logs of a site where a fault occurs by following the diagnosis
rules, and then sends an analysis report to guide users in rapid troubleshooting.
Context
NOTE
Do not run the COL LOG, EXP LOG, and EXP ALMLOG commands at the same time during the process
of the rapid fault diagnosis because this way may cause the failure of rapid fault diagnosis.
This function occupies resources of the OMU board. Therefore this function cannot be
started or is stopped when a certain condition is met:
This function cannot be started when free space available on the OMU board is less than
500 MB.
This function is stopped when more than 95% of OMU memory is occupied and this
function occupies more than 500 MB OMU memory.
Procedure
Step 1 Click FMA on the LMT main page. The FMA tab page is displayed.
Step 2 Under FMA, double-click Fault Diagnosis. The Fault Diagnosis dialog box is displayed. Select
the fault scenarios requiring fault management.
Step 3 Click Start and wait for the diagnosis report.
Issue 08 (2014-06-09)

233
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Table 10-2 GSM fault analysis scenario options

Scenario Options
Items
Traffic
GSM CS Traffic
The communication of the A interface is

interrupted.
GSM GB Traffic
The communication of the Gb interface is

interrupted.
GSM A Interface
Interruption
The CS service traffic decreases

significantly.
GSM GB Interface
Interruption
A board frequently fails to work.
GSM BSC Board Repeat

Fault
The traffic over the Gb interface decreases

significantly.
Transmission
Others
----End
Result
l
A new browser window is displayed with the fault analysis report presented on a web
page.
Table 10-3 Button Functions
Button Name
Description
Save Report
When using the IE browser, click this button to save the

diagnosis report as an html page. On the saved html page,
the log GUI does not provide the query or filtering function.
When using the FireFox browser, there will be no Save
Report button and you can use the save function of the
browser itself to save the diagnosis report.
Download Source
Data
Download the original data of the diagnosis report that is

generated by the NE.
A fault diagnosis report covers the following:
Issue 08 (2014-06-09)

234
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Table 10-4 Contents of the diagnosis report

Item
Description
KPI and counter change

trend chart
l Containing three curves illustrating KPI and

counter changes that occurred during the eight
hours of today, yesterday, and last week,
respectively. The X-coordinate represents
hour:minute, the left Y-coordinate represents the
counter value in the unit of the corresponding
counter, and the right Y-coordinate represents the
KPI value in percentages.
NOTE
Performance measurement has two states in short
measurement periods: ENABLED and DISABLED. If no
counters are measured, performance measurement is in
DISABLED state.
When the Fault Management Assistant function for rapid
fault diagnosis is enabled to analyze performance statistics,
performance statistics during a sampling period of eight
hours cannot be obtained if the measurement states are
different in a short measurement period during the sampling
period and in the current short period. For example, if the
measurement state was DISABLED during a sampling
period last Wednesday and the measurement state changed
to ENABLED on this Monday, only two curves illustrating
KPI and counter changes that occurred during the same eight
hours of this Tuesday and Wednesday are displayed in the
KPI and counter change trend chart of this Wednesday.
Fault analysis report
Including KPI statistics, Fault causes and Fault

rectification advice.
Operation logs of last 24

hours
Running the MML command EXP LOG to export the

operation log.
Unsuccessful operation
A dialog box is displayed with the failure cause.
10.6 Batch Configuration

This task is performed to deliver batch configuration script files. Such files can be generated by
the CME or manually generated by operators.
Prerequisites
l
The LMT communicates properly with the BSC.
Issue 08 (2014-06-09)

235
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Context
l
Batch configuration must be performed in accordance with the function of the CME script
executor to quickly validate patch configuration script files on the BSC.
Batch configuration includes the Preactivate and Activate functions.

Preactivate is performed to check whether the data in the configuration scripts is valid
and whether the data conflicts with that on the live network before data activation. This
helps users rectify script faults in advance and prevents activation failures.
Activate includes the check functions of Preactivate. It is also performed to validate
configuration scripts on the NE.
Compared with batch processing, batch configuration can validate configuration scripts in
a shorter time. The validating speed of batch configuration is the same as that of the RUN
BATCHFILE command.
During batch configuration, the BSC is managed independently and the MML commands
from other LMT cannot be executed.
Procedure
Step 1 On the LMT, click Device Maintenance. The Device Maintenance tab page is displayed.
Step 2 On the BSC Maintenance tab page, choose BSC Maintenance > Batch Configuration. The
Batch Configuration dialog box is displayed, as shown in Figure 10-8.
Figure 10-8 Batch Configuration dialog box
Step 3 In the displayed Batch Configuration dialog box, configure the FTP Server related parameters
and select a batch configuration script file.
Step 4 Click Activate or Preactivate and wait until the configuration command takes effect on the
BSC.
----End
Issue 08 (2014-06-09)

236
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Result
l
Successful operation:
The progress of the activation and preactivation related commands are displayed in the
progress bar.
Upload the file. The execution results of activation and preactivation related commands
are displayed in the message area.
Failed operation: The failure cause is displayed in the message area.
10.7 OS Maintenance
The OS debugging function provides commands for querying the operating system (OS)
information and commands for system debugging. The OS information refers to timer, memory,
task, message, reset record, IPC info, MOT info and start record.
Prerequisites
Context
NOTICE
Only ADMINISTRATOR-level users are authorized for performing OS Maintenancing because
it involves private information of users.
Procedure
displayed.
Step 2 Under Device Navigation Tree, right-click the BSC node and choose OS Maintenance from
the short-cut menu. The OS Maintenance dialog box is displayed.
Step 3 In the OS Maintenance dialog box, set the parameters as required, and click Submit. The LMT
returns the detailed information.
NOTE
The returned information can be text and binary messages. You can view the text messages directly. For
a binary message, double-click it to read the detailed explanation.
----End
10.8 Maintaining the Equipment

This section describes how to maintain the BSC equipment.
Issue 08 (2014-06-09)

237
BSC6910 GSM
LMT User Guide
10 BSC Maintenance

Prerequisites
l
Context
Procedure
l

1.
2.

1.
page is displayed.
2.
is displayed.
3.
and click Query.
Issue 08 (2014-06-09)

238
BSC6910 GSM
LMT User Guide
10 BSC Maintenance

1.
----End

operation.
Prerequisites
l
Context
NOTICE
l
Resetting the Board

Procedure
l

1.
2.
Reset BSC Board.
3.
then click Reset.

1.
Issue 08 (2014-06-09)
page is displayed.
239
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
2.
3.

1.
----End

Prerequisites
l
Issue 08 (2014-06-09)

240
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Context
NOTICE
Procedure
l
Issue 08 (2014-06-09)

1.
2.
Switch BSC Board.
3.

1.
page is displayed.
2.
3.
1.

241
BSC6910 GSM
LMT User Guide
10 BSC Maintenance

1.
----End

Prerequisites
Context
commands.
Procedure
l
l
Issue 08 (2014-06-09)

1.
2.
3.
and click Query.

242
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
1.
page is displayed.
2.
is displayed.
3.
and click Query.

1.
----End
10.8.5 Maintaining Fan Box

This describes how to query the attributes of a fan box and how to reset a faulty fan box.
Prerequisites
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
Maintain Fan Box. The Maintain Fan Box dialog box is displayed.
3.
To query the information about the fan box, choose the Query operation, and click
Apply. To reset the fan box, choose the Reset operation, and click Apply. The query
result is displayed, as shown in Figure 1.
243
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTE
l On the device panel, you can also perform this operation by right-clicking a board and then
choose Maintain Fan Box from the shortcut menu.
Figure 10-13 Querying the fan box
----End
10.8.6 Maintaining the Power Distribution Box

This describes how to maintain the power distribution box (PDB) and reset the faulty PDB. If
the PDB is faulty and the main processing board is normal, you can reset the PDB to restore the
functions of power supply detection and overvoltage protection.
Prerequisites
Context
The power distribution box provides the surge protection processing and overcurrent protection
processing for the power input to the cabinet and then supplies the power outputs to the other
Issue 08 (2014-06-09)

244
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
subsystems of the cabinet. The PDB also detects the states of the input voltage and the output
voltage and generates the alarm signals if the state is abnormal.
Procedure
displayed.
Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device > Maintain
Power Distribution Box. The Maintain Power Distribution Box dialog box is displayed.
Step 3 To query the information about the PDB, select Query from the Operation drop-down list, and
click Apply. To reset the PDB, select Reset from the Operation drop-down list, and click
Apply.
Figure 10-14 Maintaining the Power Distribution Box
----End
Issue 08 (2014-06-09)

245
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10.9 Maintaining Transmission and Signaling

This section describes how to maintain the signaling link and the ports on the interface boards.
In the Device Navigation Tree, right-click the BSC node, and choose Maintain Transmission
and Signaling from the shortcut menu to perform the relevant tasks.
10.9.1 Maintaining LAPD Links

This section describes how to locate an LAPD link fault in TDM transmission mode. By
performing this task, you can query the status of LAPD links of the following types: operation
and maintenance link (OML), radio signaling link (RSL), extended maintenance link (EML),
and extended signaling link (ESL). You can also reset or perform loopback tests on LAPD
links.This funtion is not supported by this version. eGBTS does not support this function.
Prerequisites
Context
Figure 10-15 shows the internal transmission on the interface boards.
Figure 10-15 Internal transmission on interface boards
When the service incurs errors, you can query the status of LAPD links. If the status of links is
Faulty, perform the loopback test to loop back the signals sent by the CPU, and determine
whether the transmission on the CPU of the corresponding board is normal based on the traced
signaling flow.
The loopback test can be line loopback and timeslot loopback. These loopback tests help to
locate the fault.
l
As shown in Figure 10-15, line loopback is performed at the port of the interface board. If
the line loopback is successful, then you can infer that the transmission within the BSC is
normal. Therefore, the fault lies in the transmission network or the peer end.
As shown in Figure 10-15,timeslot loopback is performed on the TDM module close to

the CPU. If the loopback is successful, the transmission between the GPU and the CPU is
normal. The problem lies between the TDM module close to the port on the interface board
and the peer end.
Issue 08 (2014-06-09)

246
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTE
Here, if loopback frames can be traced through signaling tracing on the relevant links, the loopback is
successful.
Procedure
l

1.
page is displayed.
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Maintain
Transmission and Signaling > Maintain LAPD Link. The Maintain LAPD Link
tab page is displayed.
3.
Set LAPD Link Type and BTS Type and click Query. The LAPD link query results
of the selected BTSs are displayed, as shown in Figure 10-16.
NOTE
l If you need to save the query result, right-click Save as... in the Query Result list area.
l You can select and filter query results by right-clicking Select all, Clear all, Select by Status
> Normal, Select by Status > Faulty, or Select by Status > Congested.
Figure 10-16 Results of querying LAPD link status
4.
Select the target link in the Query Result area, set the parameters in the Loopback
Type area, and click Loop Test or Reset.
NOTE
l When the Loopback Type is set to Line Loop, a loopback failure alert message is displayed
if you click Loop Test to perform the loopback test. In this case, you need to manually
disconnect the E1 link to the peer end and then connect the RX port to the TX port at the
local end. This disrupts the link communication.
l If you select all links, you can loop back and reset all links.
l If you select only some of the links in the Query Result area, you loop back or reset only
the selected links.

1.
You can maintain an LAPD link as follows:

Run the DSP LAPDLNK command to query the status of an LAPD link.
Run the LOP LAPDLNK command to perform a loopback test of an LAPD link.
Run the RST LAPDLNK command to reset an LAPD link.
----End
Issue 08 (2014-06-09)

247
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10.9.2 Maintaining SCCP Links

This describes how to maintain an SCCP link. By monitoring the status of the DPCs and
subsystems, you can know whether the SCCP signaling link works normally.
Prerequisites
l
The EGPUa and EXPUa board in the subrack corresponding to the DPC is functional.
The SCCP can also perform routing and network management functions. The routing
function is based on the address information such as the DSP and the Sub-System Number
(SSN).
The subsystem number defined by the LMT is of the following types: 1, 1 (local), 254, and
254 (local). The values 1 and 1 (local) refers to the peer end and the local end of the SCCP
management subsystem respectively. The values 254 and 254 (local) refers to the peer end
and the local end of the SCCP service subsystem respectively.
You are prohibited to enable or disable the management subsystem. You can enable or
disable only the service subsystem.
Context
Procedure
1.
page is displayed.
2.
Transmission and Signaling > Maintain SCCP Link. The Maintain SCCP Link
dialog box is displayed.
3.
In the DPC and Subsystem Operation tab pages, set the parameters in the Location
and Operation area to maintain the SCCP link as required. The operation result is
displayed, as shown in Figure 1.
NOTE
Select Query, Inhibit, or Uninhibit from the Operation drop-down list to perform the
corresponding operation.
Issue 08 (2014-06-09)

248
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Figure 10-17 Maintaining SCCP Links

1.
You can maintain an SCCP link as follows:

Run the DSP N7DPC command to query the status of the specified DPCs.
Run the INH N7DPC command to inhibit a specified DPC.
Run the UIN N7DPC command to uninhibit a specified DPC.
Run the DSP SSN command to query the status of the SCCP subsystem.
----End
10.9.3 Querying the Optical Interface Board Port Information

This section describes how to query the port information about an optical interface board.
POUc board supports this function.
Prerequisites
l
The optical interface board to be queried runs properly.
Procedure
Issue 08 (2014-06-09)

249
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
1.
page is displayed.
2.
Transmission and Signaling > Query Optical Interface Board Port
Information. The Query Optical Interface Board Port Information dialog box is
displayed.
3.
Set the port location information, and click Query to query the port information about
the optical interface board. The operation result is displayed, as shown in Figure 1.
NOTE
J0 Incepted Value Display Mode and J1 Incepted Value Display Mode indicate the type of
the overhead byte of the optical port. You can choose to set the display modes to Hex Mode
or String Mode. To query the overhead byte of an optical port, run the DSP OPTOH command.
Figure 10-18 Querying the Optical Interface Board Port Information

1.
Run the DSP OPT command to query the port information about an optical interface
board.
----End
10.9.4 Looping Back the Interface Board Port

This describes how to query the loopback information of the electric interface boards, including
the loopback port, loopback mode, and loopback status. POUc board supports this function.
Prerequisites
l
All the interface boards are functional.
Issue 08 (2014-06-09)

250
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Context
If the loopback at the port of an interface board fails, you can infer that the transmission from
or to the interface board fails. Therefore, you can locate the fault on the transmission link.
Procedure
l

1.
page is displayed.
2.
Transmission and Signaling > Interface Board Port Loopback. The Interface
Board Port Loopback dialog box is displayed.
3.
Set the parameters in the Location area, and then click Query to query the loopback
result. The operation result is displayed, as shown in Figure 1.
Figure 10-19 Looping Back the Interface Board Port
4.
Set Loopback Mode and select query results.
5.
Click Start to perform the loopback.

NOTE
You cannot start loopback for the port that is already in loopback state or whose loopback status
fails to be queried.
6.
l

1.
Issue 08 (2014-06-09)
Click Stop to end the optical port loopback.

You can set the loopback mode of the interface boards as follows:
251
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Run the SET OPTLOP command to set the loopback mode of the optical interface
board ports.
----End
10.9.5 Looping Back the Interface Board Port Timeslot

This describes how to query the loopback mode and loopback status of the timeslot loopback
on the ports of the interface boards. POUc board supports this function.
Prerequisites
l
All the interface boards are functional.
Procedure
1.
page is displayed.
2.
Transmission and Signaling > Interface Board Port Timeslot Loopback. The
Interface Board Port Timeslot Loopback dialog box is displayed.
3.
Set the parameters in the Location area, and then click Query to query the loopback
result. The operation result is displayed, as shown in Figure 1.
Figure 10-20 Looping Back the Interface Board Port Timeslot
Issue 08 (2014-06-09)

252
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
4.
Set Loopback Mode and select query results.
5.
Click Start to perform the loopback.

NOTE
You cannot start loopback for the port timeslot that is already in loopback state or whose status
fails to be queried.
6.
l
Click Stop to stop the loopback.

1.
You can set and query the loopback attributes of the timeslot carried by the ports of
the interface boards as follows:
Run the DSP OPTLOP command to query the loopback attributes of electrical
interface ports.
Run the SET OPTLOP command to set the loopback mode of the optical interface
board port timeslots.
----End
10.10 Maintaining BSC User Resources

This section describes how to maintain the user resources, including the port timeslot, interface
circuit, TC resources, call resources, subsystem channel or link, external speech channel. In the
Device Navigation Tree, right-click the BSC node, and choose Maintain User Resources from
the shortcut menu to perform the relevant tasks.
10.10.1 Voice Log Analysis

This section describes how to analyze voice logs. Automatic analysis of one-way audio voice
logs facilitates location of the faulty node causing one-way audio.
Prerequisites
Context
The BSC automatically saves voice analysis logs to \mbsc\bam\common\fam\famlogfmt\.A
file whose name contains CDIG is a voice analysis log.
Procedure
displayed.
Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Maintain User Resources >
Voice Log Analysis. The Voice Log Analysis dialog box is displayed.
Step 3 Set parameters in the Voice Log Analysis dialog box and click Analyze. The analysis result is
displayed in report form, as shown in Figure 10-21.
Issue 08 (2014-06-09)

253
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Figure 10-21 Voice Log Analysis
l Different analysis types apply to different scenarios:

Today: applies to quick analysis of one-way audio logs for a current day. Not requiring
users to specify Time Last, the system obtains logs of the current day from the OMU.
The current day here is the same as the current day on an LMT client.
History: applies to analysis of logs for a maximum of 30 days. Users need to specify
Time Last. Logs generated from the start time to the end time are obtained from the OMU
for analysis. Users can obtain history logs of a day simply by setting the start time and
end time to the same day.
l Different log types apply to different scenarios:
Level-1 one-way audio: applies when the BSC transcoder records calls with a high frame
error rate based on analysis of the TRAU frame structure and the BSC outputs the logs.
Level-2 one-way audio: applies when the receiving unit of the BSC transcoder does not
receive the test TRAU frames sent by the transmitting unit of the BSC code and the logs
are output.
IP one-way audio: applies when the BSC measures receiving of user-level IP packets in
an IP network structure, records calls whose packet error rate or packet loss rate is higher
than the configured threshold, and outputs the logs.
BSS crosstalk: applies to a TDM network structure when the BSC records calls where
crosstalk occurs and output the logs. The BSC determines crosstalk based on analysis of
TRAU frames.
Short calls: applies when the BSC analyzes call duration, records calls that last less than
the configured threshold, and outputs the logs.
Issue 08 (2014-06-09)

254
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTICE
The analysis result is based on analysis of many logs reporting one-way audio. If the total number
of logs is less than 10 in a measurement period, the logs are not analyzed.
NOTE
l The analysis result form contains the log type, fault node, fault times, detailed information about the
fault node, total number of logs, and analysis period of time.
l Only the top three types of fault nodes in the descending order of number are displayed in the analysis
result. If the number of fault node types is less than three, all the fault node types are displayed.
Step 4 Click Save and specify the file name to save the analysis result.
----End
10.10.2 Querying the Status of the Abis Interface Timeslot

This describes how to query the status of the Abis interface timeslot, such as timeslot number,
timeslot type, and timeslot state of the Abis interface circuits. eGBTS does not support this
function.
Prerequisites
l
The Abis interface boards are working normally.
Context
The BSC can provide 256 timeslots of 8 kbit/s or 128 timeslots of 16 kbit/s on the Abis interface.
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Maintain User
Resources > Query Abis Interface Timeslot Status. The Query Abis Interface
Timeslot Status dialog box is displayed.
3.
Set the parameters in the Location area, and then click Query to query the status of
the Abis interface timeslots. The operation result is displayed, as shown in Figure 1.

255
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Figure 10-22 Querying the Status of the Abis Interface Timeslot

1.
Run the DSP ABISTS to query the status of Abis interface timeslots.
----End
10.10.3 Querying Subsystem Resources

This section describes how to query the information about the subsystem resources and the PS
resources.
Prerequisites
l
A static PDCH has been configured.
Procedure
Issue 08 (2014-06-09)
1.
page is displayed.
2.
Resources > Query Subsystem Resources. The Query Subsystem Resources
3.
Set parameters in the DSP Resource Info tab page and click Query to query the
Subsystem resource status. Figure 10-23 shows the results.
256
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Only the subsystem with the type of GUPCS supports querying subsystem
resources.
The subsystem No. can be queried by running the LST SUBSYS command.
Figure 10-23 Results of querying Subsystem resources
----End
10.10.4 Querying Single User Resources

This section describes how to query the usage of single-user resources in the CS or PS domain.
The resources include the common information and mobile information about the MS and the
information about BM subrack.
Prerequisites
l
The MS is in a call.
Procedure
displayed.
Query Single-User Resources. The Query Single-User Resources dialog box is displayed.
Issue 08 (2014-06-09)

257
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
Step 3 In the Query Single-User Resources dialog box, set the parameters as required, and click
Query to query the user resources.
NOTE
l If you query the user messages through MSISDN, you are advised to set MSISDN to that of the peer
end:
l (Recommended) To query the calling MS, set the MSISDN to that of the called MS. For example,
if the MS calls 12345, then set the MSISDN to 12345.
l To query the called MS, set the MSISDN to that of the calling MS. The MSISDN of the calling
MS is displayed on the screen of the called MS. For example, if 54321 is displayed on the called
MS, set the MSISDN to 54321.
l If you query the user messages through TMSI or IMSI, you must determine the reassignment strategy
on the MSC side:
l If TMSI is carried, you can query the MS by the TMSI.
l If TMSI is carried, you can query the MS by the IMSI.
l If you query the user messages by IMEI, you must determine whether the IMEI is available to the
MSC.
----End
10.10.5 Collecting BSC Local Information

This section describes how to collect the BSC or BTS statistics, including the performance
statistics, logs, and alarm files.
Prerequisites
Context
NOTICE
Only one task can be created at one time.
You can collect the BSC local information through menu operations or through MML
commands.
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
In the BSC Maintenance tab page, choose Maintain BSC > Maintain User
Resources > Collect BSC Local Information. The Collect BSC Local
Information tab page is displayed.
3.
Set the time period for collecting the statistics in the Time Setting area.
258
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTE
If you select All Time, the LMT retrieves the time limit from the configuration file. The time
limit is 30 days by default.
4.
Select the fault type from the Fault List in the Set Basic Information area to collect
the required fault statistics. The corresponding file type is automatically selected. You
can select more file types from the File Type List to collect the corresponding
statistical files.
NOTE
If you select BTS Fault from the Fault List, the Select Sites area is activated so that you can
further specify the target BTS to collecting the statistics.
5.
Set the FTP server parameters in the Upload configure area, and click Execute to
collect the BSC statistics. The progress of collecting the statistics is displayed in the
Progress(%) bar, and the collected files are displayed in the Result tab page.
NOTE
l Enter the IP address of the FTP server in the FTP Server IP box, specify the path for saving
the uploaded files on the FTP server in the Upload Path box. For the default FTP User
Name and FTP Password, see 2.4.3 FTP Server.
l If you select The common debug log in the File Type List, the Subrack No. in the
Setting area can be specified. Otherwise, the file of all the subracks are uploaded by default.
6.
To upload the collected logs from the OMU to the FTP server, click Upload. Then,
you can retrieve the files in the specified upload path.
7.
To delete the collected logs, click Delete File.

1.
Run the COL LOG command to collect the log files.
2.
Run the LST LOGRSTINFO command to query the collected files.
----End
10.10.6 Looping Back Remote Speech Channel

This section describes how to start or end the remote speech channel loopback and how to query
the status of the current remote speech channel loopback.
Prerequisites
l
The MS is in conversion.
Context
This feature is applicable to the IP networking and TDM networking scenarios.
The speech in a system can be transmitted in sending direction and receiving direction. Each
direction has its own channel. On a speech channel, you can locate the segment where the speech
problem occurs by comparing the loopback speech with the original speech.
You can detect the speech channel fault by performing the remote speech channel loopback on
the A interface and the Abis interface.
Issue 08 (2014-06-09)

259
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
The loopback can be remote loopback or local loopback. That is, the loopback can be performed
in the direction towards the MSC or in the direction towards the MS.
For example, Figure 10-24 shows the loopback on the Abis interface board, UP board, and A
interface board in the direction of MSC in an IP network. If the result of the loopback on the A
interface board is normal, then you can infer that the speech problem is not introduced by the
BSC but by the CN or peer end. If the result of UP loopback is normal but that of the A interface
board is abnormal, then you can infer that the speech problem is located between the UP and
the A interface, and so forth.
Figure 10-24 Remote speech channel loopback
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
Resources > Remote Speech Channel Loopback. The Remote Speech Channel
Loopback dialog box is displayed.
3.
In the Remote Speech Channel Loopback dialog box, set the parameters as required,
and click Start. A message is displayed, prompting you that the loopback is
successfully started.

260
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
NOTE
l If you query the user messages through MSISDN, you are advised to set MS ID to that of
the peer end:
l (Recommended) To query the calling MS, set the MS ID to that of the called MS. For
example, if the MS calls 12345, then set the MS ID to 12345.
l To query the called MS, set the MS ID to that of the calling MS, which is displayed
on the called MS. For example, if 54321 is displayed on the called MS, set the MSISDN
to 54321.
l If you query the user messages through TMSI or IMSI, you must determine the
reassignment strategy on the MSC side:
l If TMSI is carried, you can query the MS by the TMSI.
l If TMSI is carried, you can query the MS by the IMSI.
l If you query the user messages by IMEI, you must determine whether the IMEI is available
to the MSC.
4.
After the loopback is started, click Query to query the remote speech channel
loopback.
5.
Click Cancel stop the remote speech loopback.

NOTE
To end a remote speech loopback, select IMSI, IMEI, TMSI, or MSIDSN in the MS Type
area to ensure that the parameter setting in the MS Type area is the same as that is previously
set for the loopback.
If different MS IDs are used for one MS to perform the remote speech channel loopback, you
need to use corresponding MS ID to end the remote speech channel loopback.

1.
You can query, start, or end the remote speech channel loopback as follows:
Run the DSP CALLRESLOP command to query remote speech channel.
Run the STR CALLRESLOP command to start looping back remote speech
channel.
Run the STP CALLRESLOP command to stop looping back remote speech
channel.
----End
10.10.7 Looping Back Subsystem Channel/Link

This section describes how to loop back the Subsystem speech channel. By performing this task,
you can see whether the speech problem is caused by codec error of the internal speech
processing unit of the BSC.
Prerequisites
Context
When looping back consecutive paths of a Subsystem on the EGPUa whose logical function is
GCUP board, you can choose to loop the speech signals from the MSC or BTS through the TC
subrack or not through the TC subrack. Therefore, you can determine whether the fault resides
in the DSP.
Issue 08 (2014-06-09)

261
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
The DSP speech loopback can be performed on the A interface and the Abis interface.
l
A interface loopback:
It supports the loopback towards the MSC and towards the BTS. The loopback towards the
MSC does not go through the TC subrack whereas the loopback towards the BTS goes
through the TC subrack.
Abis interface loopback:

It supports the loopback towards the MSC and towards the BTS. The loopback towards the
MSC goes through the TC subrack whereas the loopback towards the BTS does not go
through the TC subrack.
If user B hears its own voice after a Subsystem speech loopback on the A interface whereas it
cannot hear its own voice after a Subsystem speech loopback on the Abis interface, then you
can infer that the fault resides in the TC subrack.
Similarly, if user A hears its own voice after the Abis interface loopback whereas it cannot hear
its own voice after the A interface loopback, then you can infer that the fault resides in the TC
subrack.
Table 10-5 shows the results of a subsystem channel loopback test in normal cases.
Table 10-5 Results of a Subsystem channel loopback test
Loopback Mode/Test MS
A (Under the Local BSC)
B (Not Under the Local

BSC)
A interface loopback
Hears voices of A not B
Hears voices of B not A
Abis interface loopback
Hears voices of A not B
Hears voices of B not A
Procedure
displayed.
Subsystem Channel/Link Loopback. The Subsystem Channel/Link Loopback dialog box
is displayed.
Step 3 Set parameters under Channel Setting and Operation Setting, and then click Query to query
the status of subsystem channel/link loopback.
Step 4 Click Start and confirm to start a loopback.
NOTE
Avoid the movement of the MS that may trigger the handover during this test. If the bearer Subsystem
channel changes due to handover, you need to query the information about the new Subsystem channel
and then perform the loopback on the new Subsystem channel.
Step 5 Click Stop to stop the loopback.

----End
Issue 08 (2014-06-09)

262
BSC6910 GSM
LMT User Guide
10 BSC Maintenance
10.11 Querying Board Version Information

This section describes how to query the information about the software version, hardware
version, and patch version of the board.
Prerequisites
l
The target board works normally.
Procedure
1.
page is displayed.
2.
In the BSC Maintenance tab page, choose BSC Maintenance > Query Software >
Query Board Version Information.
3.
In the Query Board Version Information dialog box, set the parameters as required,
and click Query.

1.
Run the LST PATCH or DSP PATCH command to query the patch version.
----End
Issue 08 (2014-06-09)

263
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11
BTS Maintenance
About This Chapter

This chapter describes how to maintain the BTS, including the BTS versions, equipment, and
boards.
11.1 Concepts Related to BTS Maintenance
This section describes the basic concepts related to the BTS maintenance: BTS attributes and
cell forcible handover mode.
11.2 Query Running Software Version of a Board
This function is used to query the type, software version, and clock status of a board. You can
query the board running software version of several BTSs at a time. eGBTS does not support
this function.
11.3 Downloading the BTS Software
This section describes how to download the BTS software from the FTP Server to the OMU.
11.4 Loading the BTS Software
This section describes how to load the BTS software on the OMU to the main processing board
of the BTS. eGBTS does not support this function.
11.5 Activating BTS Software
This describes how to activate the version software loaded onto the board. eGBTS does not
11.6 Querying BTS Running Status
This section describes how to query the operating status of a BTS and cells under the same BSC
to determine whether the BTS operates normally. You can query the operating status of multiple
BTSs at one time.
This describes how to query whether the actual BTS board type matches with the configured
one. This operation is applicable to multiple BTSs simultaneously. eGBTS does not support this
function.
11.8 Querying BTS Attributes
This describes how to query the BTS working status and attributes to verify the software and
hardware configuration of a BTS. eGBTS does not support this function.
Issue 08 (2014-06-09)

264
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11.9 Resetting the BTS by Levels

This section describes how to reset a BTS, cell, or TRX to update the configuration data when
the BTS, cell, or TRX is faulty.
11.10 Browsing BTS Initialization Process Message
This section describes how to browse the initialization process of all the BTSs to see whether
the BTS is reset. If the initialization fails, this message shows the failure cause that helps to
locate the fault. eGBTS does not support this function.
11.11 Changing Administrative State
This section describes how to change the administrative state of a cell, TRX, and channel. When
maintaining a base station, users can change the administrative state of a cell to the blocked state.
With the administrative state changed, MSs of this blocked cell are forcibly handed over to
another cell working properly and new call requests for this cell are rejected. This prevents call
drops caused by improper operation and maintenance. Before blocking an entire base station,
users need to block all the cells served by the base station.
11.12 Forced Handover
This section describes how to hand over the services in the cell, on the TRX, or on a channel
forcibly over to another cell, TRX, or channel.
11.13 Monitoring Channel Status
This describes how to monitor the occupation of all the channels and sub-channels.
11.14 Monitoring Interference Band of Channel
This describes how to detect the interference band rank on the idle channel to monitor the
interference conditions on the channel.
11.15 Frequency Band Scan
This section describes how to test the ambient noise within a certain frequency band. The result
obtained from a frequency band scan enables network planning engineers to plan frequencies
and therefore avoid interference in practical deployment. The frequency band scan also
facilitates discovery of interference source when interference occurs at a certain frequency.
11.16 Querying the Failure Cause of Configuration Alarms
This section describes how to query the detailed failure cause of TRX Config Mismatch
Alarm. This function enables the detailed failure cause of all board configuration alarms under
a BTS to be reported. This facilitates quick location and troubleshooting of alarms. eGBTS does
11.17 Call Test
This section describes how to perform a call test. The call test traverses all channels when a BTS
is newly deployed or after cutover and commissioning are complete. A test MS is used to perform
a call test in each cell to be tested under a BTS. This test is performed to detect problems such
as incorrect connection of antenna feeders, main/diversity problems, uplink and downlink
imbalance, one-way audio, and no audio. During a conversation, a forced handover of the calling
MS is performed for at a certain interval. When all idle channels are tested, a call test is complete.
11.18 Antenna Feeder Intermodulation Test
This section describes how to analyze the intermodulation interference in the uplink on the basis
of the difference between the scanned results of uplink frequencies before and after power
transmission. eGBTS does not support this function. Only base stations of versions earlier than
V100R008C00 support the antenna feeder intermodulation test.
11.19 EmergencyDiag
Issue 08 (2014-06-09)

265
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
This section describes how to customize a message for EmergencyDiag. This custom message
complying with Huawei message format is sent from the BSC to a base station and users can
obtain information from the response message sent from the base station. The EmergencyDiag
function enables users to remotely connect to the COM port on the main control board. This
function is used in problem location and query of board running status. This function is intended
for only Huawei engineers. COM ports are used only for signal output. eGBTS does not support
this function.
11.20 Customizing a Message
This section describes how to customize a message that is sent from the BSC to a base station
and complies with Huawei message format. This function enables users to remotely perform
operation and maintenance on a base station by obtaining information from the response message
sent from the base station. This accelerates problem location. Note that this function is intended
for only Huawei engineers. eGBTS does not support this function.
11.21 Maintaining Site
This section describes how to maintain the sites.
11.22 Maintaining the Cell
This section describes how to maintain the cells.
11.23 Maintaining TRXs
This section describes how to maintain the TRXs.
11.24 Reference for BTS Maintenance
This section describes the parameters used for BTS maintenance.
Issue 08 (2014-06-09)

266
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11.1 Concepts Related to BTS Maintenance

This section describes the basic concepts related to the BTS maintenance: BTS attributes and
cell forcible handover mode.
11.1.1 BTS Attributes

The BTS attributes consist of the site attributes, cell attributes, TRX attributes, and channel
attributes.
Site Attributes
Table 11-1 lists the site attributes.
Table 11-1 Site attributes
Attribute Name
Description
OML attribute
Port number, timeslot number, and sub-timeslot number of the OML

link.
Operation state
Whether the current site is available.
Terminal
equipment ID
Terminal equipment ID according to the LAPD protocol. The attribute

here indicates the equipment ID of the current site, that is, the terminal
equipment identifier (TEI) of the OML.
Clock attribute
BTS clock status and information related to the clock parameters.
Extended alarm
configuration
Configuration of the extended alarms of the current site.
Software
configuration
Software configuration of the current site.
Hardware
configuration
Hardware configuration of the current site.
Power system type
Power system type of the BTS cabinet.
High temperature
derating parameter.
High temperature derating parameter of the BTS cabinet.
SFP work mode
SFP port connection information of the BTS.
TOP switching
parameters
Port and timeslot involved in TOP switching on the backplane of the

BTS.
Cell Attributes
Table 11-2 lists the cell attributes.
Issue 08 (2014-06-09)

267
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Table 11-2 Cell attributes

Attribute
Name
Description
Administrative
state
Administrative state of the current cell.
BCCH
ARFCN
Frequency of the main BCCH of the current cell.
Base station
identity code
Consisting of BSIC, NCC, BCC.
Cell airinterface timer
Duration of timer T3105. This attribute is used in asynchronous cell

handover. Unit: ms
CCCH load
indicating
period
Interval for sending the overload messages.
CCCH load
threshold
Ratio of number of successful random accesses to total number of collisions

within the time.
Connection
failure criterion
Detailed criterion for determining the connection failure.
Interference
average
parameter
Average time for obtaining the interference level. The default value is 20
multiframe.
Interference
level threshold
The interference can be divided into six ranks according to the interference
signal level. The level value for dividing each rank is called interference
level threshold.
The BTS determines which rank the current interference level is in and
reports this information to the BSC based on the radio resource indication.
Issue 08 (2014-06-09)
Max. TA
Maximum timing advance of the most distant area of a cell. This attribute
can identify the actual coverage of a cell.
NY1
Maximum times of sending physical messages.
Operation state
Whether the current site is available.
Overload
period
The BTS calculates the channel usage at a fixed interval to check whether
the channel is overloaded. The interval is determined by the overloading
period. Unit: seconds
RACH Busy
Threshold
Determining the level threshold of random access. Unit: dBm
RACH load
average
timeslots
Measuring the average loading timeslot number for random access channel.

268
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Attribute
Name
Description
Starting frame
No.
The frame starting command can be run in the case of this frame number.
If you want to run the command immediately, set the frame number to
65535.
The value range of frame number is 0 to 42432, and 65535.
T200
Consisting of the following parameters:

SDCCH: timeout duration of T200 on the SDCCH at the Um port
FACCH/Full rate: timeout duration of T200 on the FACCH or full-rate
channel at the Um port
FACCH/Half rate: timeout duration of T200 on the FACCH or half-rate
channel at the Um port
SACCH with TCH SAPI0: timeout duration of T200 on the SACCH when
the TCH at the Um port supports the SAPI0 service
SACCH with SDCCH: timeslot duration of the T200 on the SACCH with
SDCCH.
SDCCH SAIP3: value of T200 when the SDCCH supports the SAPI3
service
SACCH with TCH SAPI3: timeout duration of T200 on the SACCH when
the TCH at the Um port supports the SAPI3 service
Issue 08 (2014-06-09)
VSWR
threshold
VSWR threshold of the RF voltage, including the VSWR threshold when

an antenna incurs a fault and the VSWR threshold when an antenna is not
correctly adjusted.
Available state
Current status of the cell.
Hop Mode
Determining whether to use the FH mode and the type of FH mode if used.
Extended type
& extended
offset
Extended type and extended offset of the current cell.
Frame offset
The default value of this attribute is 0. This indicates that the cell is not
offset. If the value is not 0, the handover mode must be changed from
synchronous to asynchronous.
Interfere Band
Stat Algorithm
Type
When the frequency point scanning function is enabled, interference band

statistic algorithm I or interference band statistic algorithm II is used.
Uplink
frequency
point scanning
result type
Uplink frequency point scanning result type.
Diversity
transmitter
delay
Diversity transmitter delay of the current cell.

269
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
TRX Attributes
Table 11-3 lists the TRX attributes.
Table 11-3 TRX attributes
Attribute
Name
Description
Administrative
state
Administrative state of the current TRX.
ARFCN list
List of channel numbers based on which the channel works. In non-FH

mode, each channel corresponds to only one channel number. In FH mode,
all the available channel numbers are listed in the ARFCN list.
Power Level
The static power is divided into five levels. The value set here indicates the
power level of the current TRX.
Output power
threshold
Maximum static output power.
Maximum RC
power
reduction
Maximum power reduction of each level.
Operation state
Whether the TRX is available.
Available state
Current status of the TRX.
8PSK
modulation
power
attenuation
level
Power attenuation levels of the EDGE TRX. There are 50 levels, and the
attenuation between levels is 0.2 dB.
RSL attribute
Port number, timeslot number, and sub-timeslot number of the RSL link.
Terminal
equipment ID
Information about the terminal equipment.
Channel Attributes
Table 11-4 lists the channel attributes.
Issue 08 (2014-06-09)

270
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Table 11-4 Channel attributes

Attribute
Name
Description
Administrativ
e state
Administrative state of the current channel.
ARFCN list
List of channel numbers based on which the channel works.

In the case of none FH, each channel has one channel number. In FH, all the
available channel numbers are listed in the ARFCN list.
Operation
state
Whether the channel is available.
Channel
combination
Combination type of the current channel.
HSN
Numbers of 64 kinds of FH. The number 0 indicates the FH in sequence.

Other values indicate the FH of pseudo-random sequence.
Mobile
allocation
index offset
FP offset when the TRXs are in FH in the same cell.
TSC
Demodulation part for estimating the channel feature to correctly decode the
valid information. There are eight kinds of training sequence codes.
Available
state
Current status of the channel.
11.1.2 Cell Forced Handover Mode

This section describes the cell forced handover function of the BSC. The target cell can be
selected by the BSC according to the measurement report or be specified by the user.
The forced handover is classified into the following types:
l
Free
Handing over an MS from one channel to another. The target cell can be specified through
the LMT as required.
Intra-cell
Handing over an MS from one channel to another. The success rate of this type of handover
is high. Lock or shut down a faulty channel or the TRX that bears the faulty channel before
the handover.
Outgoing Cell
Handing over all MSs in a cell to another cell.
Outgoing Site
Handing over all MSs in a cell to a cell that belongs to another base station.
l
Issue 08 (2014-06-09)
Outgoing BSC
271
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Handing over all MSs in a cell to a cell under control of another BSC.
l
Outgoing System
Handing over all MSs in a cell to a cell in different network system, for example, from a
GSM cell to a UMTS cell.
Specified Cell
Handing over all MSs in a cell to a specific target cell.
NOTE
Here, the target cell is specified by the user. In other cases, the target cell is determined by the BSC.
11.2 Query Running Software Version of a Board

This function is used to query the type, software version, and clock status of a board. You can
query the board running software version of several BTSs at a time. eGBTS does not support
this function.
Prerequisites
l
Procedure
1.
page is displayed.
2.
In the BTS Maintenance tab page, choose BTS Maintenance > Query Board
Running Software Version. The Query Board Running Software Version tab page
is displayed.
3.
In the Query Board Running Software Version tab page, set the parameters as
required, and then click Start to query the running software version of the board.
Figure 11-1 shows the results. If you need to save the query result, right-click Save
as... in the Query Result list area.
Figure 11-1 Results of querying the running software version of a board
Issue 08 (2014-06-09)

272
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
4.
Click Stop to stop the query.

NOTE
You can also query the running software version of the board in the following way: Start the BTS
device panel by referring to Starting the Device Panel. Then on the BTS device panel, right-click
the main control board of the BTS and choose Query Software Version from the shortcut menu.

1.
Run the DSP BTSBRD command to query the running software version of a BTS
board.
----End
11.3 Downloading the BTS Software

This section describes how to download the BTS software from the FTP Server to the OMU.
Prerequisites
l
The corresponding BTS software is available on the LMT PC.
The FTP server is running normally.
Context
You can visit the website http://support.huawei.com to request the BTS software.
NOTICE
The name of the file to be downloaded must be in English and the file must not be in use.
Otherwise, the downloading fails.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Download BTS
Software. The Download BTS Software tab page is displayed.
3.
In the Download Files tab page, click Browse... and select the target BTS software.
Then, click Add File to add the file to the download list.
4.
In the FTPServer Setting area, set the parameters as required, and click Download
to start software downloading.
NOTE
FTP Server IP indicates the IP address of the FTP server. For the default FTP User Name
and FTP Password, see 2.4.3 FTP Server.
Issue 08 (2014-06-09)

273
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
5.
l
To query the BTS software on the OMU, click Query in the Files on OMU tab page.

1.
Run the DLD BTSSW command to download the BTS software.
----End
11.4 Loading the BTS Software

This section describes how to load the BTS software on the OMU to the main processing board
of the BTS. eGBTS does not support this function.
Prerequisites
l
The corresponding BTS software is available on the LMT PC.
Context
The LMT supports loading of multiple BTS software, which reduces the BTS upgrade time and
increases the upgrade efficiency.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Load BTS
Software. The Load BTS Software dialog box is displayed.
3.
In the Load BTS Software dialog box, specify the site type and software type, and
then click Next.
4.
Select the BTS software to be loaded, and click Next to start loading the software.
5.
The result is displayed in the Load BTS Software dialog box. Click Finish to exit
the operation.

1.
Run the LOD BTSSW command to load the BTS software.
----End
11.5 Activating BTS Software

This describes how to activate the version software loaded onto the board. eGBTS does not
Prerequisites
l
Issue 08 (2014-06-09)

274
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
The software version to be activated is different from the running version.
The BTS software has been loaded into the flash memory of the BTS board successfully.
The BTS software can be run only after being activated.
Auto Download Active Function Switch is set to OFF by running the MML command SET
BTSAUTODLDACTINFO.
Context
NOTE
l The LMT supports activation of multiple BTS software simultaneously. On the BTS, the software on
the main control board must be activated after the activation of the software on non-main control boards.
l The LMT does not support activation of the main processing board of a single BTS. When you activate
the software of the main processing board, the main processing boards of all the BTSs managed by the
LMT are activated. When you activate the software of the non-main processing board, you can activate
the software of one or more boards as required.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Activate BTS
Software. The Activate BTS Software dialog box is displayed.
3.
In the Activate BTS Software dialog box, specify the site type and software type,
and then click Next.
4.
Select the BTS software to be activated, and click Next to start the software activation.
5.
The result is displayed in the Activate BTS Software dialog box. Click Finish to exit
the operation.

1.
Run the ACT BTSSW command to activate the BTS software.
----End
11.6 Querying BTS Running Status

This section describes how to query the operating status of a BTS and cells under the same BSC
to determine whether the BTS operates normally. You can query the operating status of multiple
BTSs at one time.
Prerequisites
l
Procedure
Issue 08 (2014-06-09)

275
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
1.
page is displayed.
2.
In the BTS Maintenance tab page, BTS Maintenance > Query BTS Running
Status. The Query BTS Running Status tab page is displayed.
3.
In the Query BTS Running Status tab page, set the parameters as required, and then
click Start to query the operating status of the BTS. The operation result is displayed,
as shown in Figure 1.
NOTE
l In the Device Navigation Tree, right-click the target BTS node, and choose Query BTS
Running Status from the shortcut menu.
l If Object Type is set to cell and Cell Management Status is selected in the Select
Status area, the cell management status can be queried, which is Lock, Unlock, or
Shutting Down.
Figure 11-2 Querying BTS Running Status

1.
You can query the operating status of the BTSs and cells under the same BSC with
the following command.
Run the DSP BTSSTAT command to query the operating status of the BTS.
Run the DSP GCELLSTAT command to query the operating status of the cell.
----End

This describes how to query whether the actual BTS board type matches with the configured
one. This operation is applicable to multiple BTSs simultaneously. eGBTS does not support this
function.
Prerequisites
l
Issue 08 (2014-06-09)

276
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
NOTICE
This function does not support BTS3900 series base station such as DBS3900 GSM, BTS3900
GSM, BTS3900A GSM, DBS3036, BTS3036, BTS3036A, BTS3900L GSM, BTS3900B GSM,
BTS3900E GSM and BTS3900AL.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, select BTS Maintenance > Query Board Match. The
Query Board Match tab page is displayed.
Step 3 In the Query Board Match tab page, select BTS Type and add a Candidate BTS to the Selected
BTS as required.
Step 4 Click Query. The query result is displayed in the Query Result area. The operation result is
Figure 11-3 Querying BTS Board Matching Result
----End
11.8 Querying BTS Attributes

This describes how to query the BTS working status and attributes to verify the software and
hardware configuration of a BTS. eGBTS does not support this function.
Prerequisites
l
Issue 08 (2014-06-09)

277
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Procedure
1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Query BTS
Attributes. The Query BTS Attributes tab page is displayed.
3.
In the Query BTS Attributes tab page, set the parameters as required, and then click
Query. The operation result is displayed, as shown in Figure 1.
NOTE
In the Device Navigation Tree, right-click the BTS node, and choose Query BTS
Attributes from the shortcut menu.
Figure 11-4 Querying BTS Attributes

1.
Run the DSP BTSATTR command to query the attributes of the BTS.
----End
11.9 Resetting the BTS by Levels

This section describes how to reset a BTS, cell, or TRX to update the configuration data when
the BTS, cell, or TRX is faulty.
Prerequisites
l
Issue 08 (2014-06-09)

278
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
NOTICE
l Resetting a BTS will initialize the BTS, reload the data, and disrupt the ongoing services
under the BTS. Therefore, perform this operation with caution.
l Resetting a cell will initialize the cell, reload the data, and disrupt the ongoing services in
the cell. Therefore, perform this operation with caution.
l Resetting a TRX will reset the TRX board and disrupt the ongoing services carried by the
TRX. Therefore, perform this operation with caution.
l If the multimode base station works in co-module mode, level-3 or level 4 reset on the GSM
side will disrupt services carried on the TRX boards in co-module mode on other sides except
GSM. Therefore, perform this operation with caution.
l
Resetting the BTS by Levels

Resetting the BTS is classified into level-3 resetting or level-4 resetting.
The working principle of level-3 resetting and level-4 resetting at the BTS side is the
same. That is, in both operations, the BTS obtains data from the BSC6910 for the
resetting.
The working principles of the level-3 and level-4 resetting at the BSC6910 side are
different in terms of whether to reset the BTS with the updated configuration data. That
is, if the BTS is under level-3 resetting, the BTS is reset directly with the current data.
If the BTS is under level-4 resetting, the BTS is reset directly with updated data in the
GPU board.
Resetting the Cell by Levels

Resetting the cell is classified into level-3 resetting or level-4 resetting.
The working principle of level-3 resetting and level-4 resetting at the BTS side is the
same. That is, in both operations, the BTS obtains data from the BSC6910 and then
resets all boards in the cell.
The working principles of the level-3 and level-4 resetting at the BSC6910 side are
different in terms of whether to reset the cell with the updated configuration data. That
is, if the cell is under level-3 resetting, the cell is reset directly with the current
configuration data. If the cell is under level-4 resetting, the mutual-aid status is
initialized and then the cell is reset with the updated configuration data.
Resetting the TRX

Resetting the TRX does not involve the operation of the BSC6910. The BTS resets the
TRX boards directly.
Procedure
l

1.
Issue 08 (2014-06-09)
page is displayed.
279
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
2.
In the BTS Maintenance tab page, select BTS Maintenance > Reset BTS by
Levels. The Reset BTS by Levels dialog box is displayed. The operation result is
Figure 11-5 Resetting the BTS by Levels
3.
In the displayed Reset BTS by Levels dialog box, set the parameters as required, and
then click Reset.
NOTE
In the Device Navigation Tree, right-click the BTS node, and choose Reset BTS by Levels
from the shortcut menu.

1.
You can reset a BTS, cell, or TRX as follows:

Run the RST BTS command to reset a BTS.
Run the RST GCELL command to reset a cell.
Run the RST TRX command to reset a TRX.
----End
11.10 Browsing BTS Initialization Process Message

This section describes how to browse the initialization process of all the BTSs to see whether
the BTS is reset. If the initialization fails, this message shows the failure cause that helps to
locate the fault. eGBTS does not support this function.
Prerequisites
l
Issue 08 (2014-06-09)

280
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
l
The initialization process message is reported by the BTS automatically.
There are numerous process messages. The messages are displayed in strings not in
percentage.
An LMT can display the process messages of all BTSs of the current BSC.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Browse BTS Initialization
Progress. The Browse BTS Initialization Progress dialog box is displayed.
Step 3 To browse the initialization process messages that meet the filtering conditions, set Site and
Cell. The operation result is displayed, as shown in Figure 1.
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Browse BTS Initialization
Progress from the shortcut menu.
Figure 11-6 Browsing BTS Initialization Process Message
----End
11.11 Changing Administrative State

This section describes how to change the administrative state of a cell, TRX, and channel. When
maintaining a base station, users can change the administrative state of a cell to the blocked state.
With the administrative state changed, MSs of this blocked cell are forcibly handed over to
another cell working properly and new call requests for this cell are rejected. This prevents call
drops caused by improper operation and maintenance. Before blocking an entire base station,
users need to block all the cells served by the base station.
Issue 08 (2014-06-09)

281
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Prerequisites
l
Communication between the BSC6910 and the base station is normal.
Context
There are three administrative states: blocked, unblocked, and shutdown. An object can be
blocked or shut down only when the upper-level object is unlocked. If an object is blocked or
shut down, all the lower-level objects are blocked or shut down. For example, blocking a cell
locks all the TRXs and channels under the cell.
l
Blocked: If a cell, TRX, or channel is blocked, it becomes unavailable for services. Ongoing
calls under the blocked cell, TRX, or cell are forcibly handed over to another cell, TRX,
or channel without being interrupted. If the forced handover fails, however, call drops may
occur. New calls, however, cannot access the blocked cell, TRX, or channel.
Unblocked: If a cell, TRX, or channel is unblocked, it becomes available for services.
Shutdown: If a cell, TRX, or channel is shut down, ongoing calls under the blocked cell,
TRX, or cell are not affected. New calls, however, cannot access the cell, TRX, or channel.
Block or shut down an object in the following cases:

l
When dynamic data configuration that may affect the ongoing services (for example,
changing the channel type) is required, you need to block or shut down the target object
before dynamic data configuration.
When the speech quality of a cell, TRX, or channel is unsatisfactory and the relevant
hardware device needs to be replaced, you need to block or shut down the target object
before replacing the hardware device.
Procedure
1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Modifying
Administrative State. The Modifying Administrative State dialog box is displayed.
3.
In the Modifying Administrative State dialog box, set the parameters as required,
and click Apply.

1.
You can change the administrative state of a cell, TRX, or channel as follows:
Run the SET GCELLADMSTAT command to change the administrative state
of a cell.
Run the SET GTRXADMSTAT command to change the administrative state of
a TRX.
Run the SET GTRXCHANADMSTAT command to change the administrative
state of a channel.
----End
Issue 08 (2014-06-09)

282
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11.12 Forced Handover

This section describes how to hand over the services in the cell, on the TRX, or on a channel
forcibly over to another cell, TRX, or channel.
Prerequisites
l
Context
NOTE
In the Device Navigation Tree, right-click the cell or TRX node, and choose Forced Handover from the
shortcut menu.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, choose BTS Maintenance > Forced
Handover. The Forced Handover dialog box is displayed.
3.
In the Forced Handover dialog box, set the parameters as required, and click
Apply.
NOTE
If you select Specified Cell in the Switch Mode area, the Specify the Cell area is activated.
You can set the information of the cell for handover in this area.

1.
Run the SET FHO command to configure the handover parameters.
----End
11.13 Monitoring Channel Status

This describes how to monitor the occupation of all the channels and sub-channels.
Prerequisites
l
Context
NOTE
In the Device Navigation Tree, right-click the site, cell or TRX node, and choose Monitor Channel
Status from the shortcut menu.
Issue 08 (2014-06-09)

283
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, choose BTS Maintenance > Monitor Channel
Status. The Monitor Channel Status tab page is displayed.
3.
In the displayed Monitor Channel Status tab page, set the parameters as required,
and then click Start to monitor the channel status. The operation result is displayed,
NOTE
l Each dot in a column represents a sub-channel of the corresponding channel. The SDCCH
channel has eight sub-channels, the full-rate TCH has only one sub-channel, and the halfrate TCH has two sub-channels.
l The sub-channel status is indicated with different colors.
l Green indicates that the channel is in the normal state. If you move the cursor to the
corresponding indicator, you can read the current channel type, applied bandwidth, and
available bandwidth from the pop-up information, wherein the applied bandwidth and
the available bandwidth are equal and both bandwidths are greater than or equal to 16
kbit/s. The number of the uplink or downlink TBF blocks are proportional to the MSs
that can be multiplexed on the current channel.
l Red indicates that the channel is abnormal. If you move the cursor to the corresponding
indicator, you can read the current channel type, applied bandwidth, and available
bandwidth from the pop-up information, wherein the applied bandwidth is not equal
to the available bandwidth or both bandwidths are 0 kbit/s.
l Blue indicates that the channel is blocked. If you move the cursor to the corresponding
indicator, you can read the current channel type and the channel status, wherein the
channel status is Locked.
l Yellow indicates that the channel is blocked. You can perform PDCH loopback
detection in this status. For detail, see step 4.
l If a TRX number is marked with *, the TRX is in TRX mutual aid state.
Figure 11-7 Monitoring Channel Status
4.
Issue 08 (2014-06-09)
Optional: If the status of the subchannel is yellow, you can perform PDCH loopback
detection.
284
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
NOTE
l The built-in PCU is supported and the Abis interface works in fixed TDM mode.
l A loopback test cannot be performed on an odd-numbered PDCH in a dual-timeslot
extended cell.
l 3900 series base stations of GBSS14.0 and later versions support PDCH loopback tests.
a.On the Monitor Channel Status tab page, right-click the PDCH to be looped
back and choose Start Loop from the shortcut menu. The Start Loop dialog box
is displayed.
NOTICE
1. A PDCH cannot provide services during a loopback test. Therefore, stop the
loopback test immediately after you obtain the loopback result.
2. If the link occupied by the PDCH is faulty over the Abis interface during a
loopback test, the loopback test automatically stops.
3. If a PS cell resets during a loopback test, the test automatically stops.
b.In the Start Loop dialog box, set the related parameters and click Ok to start a
loopback test.
l

1.
Run the DSP CHNSTAT command to monitor the channel status.
2.
Optional: Run the following commands to perform PDCH loopback operations.

Run the STR PDCHLOOPTST command to start a PDCH loopback test.
Run the DSP PDCHLOOPTST command to query the PDCH loopback test
result.
Run the STP PDCHLOOPTST command to stop a PDCH loopback test.
----End
11.14 Monitoring Interference Band of Channel

This describes how to detect the interference band rank on the idle channel to monitor the
interference conditions on the channel.
Prerequisites
l
Procedure
1.
Issue 08 (2014-06-09)
page is displayed.
285
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
2.
In the BTS Maintenance tab page, choose BTS Maintenance > Monitor Channel
Interference Band. The Monitor Channel Interference Band tab page is displayed.
3.
In the displayed Monitor Channel Interference Band tab page, set the parameters
as required, and then click Start to monitor the interference band of the channel. The
operation result is displayed, as shown in Figure 1.
NOTE
In the Device Navigation Tree, right-click the BTS node, and choose Monitor Channel
Interference Band from the shortcut menu.
Figure 11-8 Monitoring Interference Band of Channel

1.
Run the DSP CHNJAM command to monitor the interference band of the channel.
----End
11.15 Frequency Band Scan

This section describes how to test the ambient noise within a certain frequency band. The result
obtained from a frequency band scan enables network planning engineers to plan frequencies
and therefore avoid interference in practical deployment. The frequency band scan also
facilitates discovery of interference source when interference occurs at a certain frequency.
Prerequisites
l
Context
NOTICE
The frequency band scan will reset the TRX, therefore disrupting ongoing services.
Issue 08 (2014-06-09)

286
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Frequency Band Scan. The
Frequency Band Scan tab page is displayed.
Step 3 Set parameters in the Frequency Band Scan tab page.
l Site, TRX No.: indicates the site and the number of TRXs to undergo a frequency band scan.
TRX No. uniquely identifies a TRX within one BSC6910.
l Frequency Band: indicates the type of TRX frequency band. You can query it by running the
DSP BTSBRD command.
l Start, End: indicates the start frequency and end frequency of a scan. The two frequencies
define the scan range. A scan is performed from the start frequency to the end frequency.
l Time Length
Hour, Minute: indicates the time length for a scan expressed in hours and minutes. The
length of Minute must be a multiple of 10.
NOTE
In the frequency band scan result, the unit of "Time Length" is 10 min. For example, if the value of
"Time Length" is 1, the test duration of frequency band scan is 10 min (1 x 10 min). Specifically, the
test duration of frequency band scan equals "Time Length" multiplied by 10 (min).
The formula for calculating the frequency band scan is as follows: Frequency band scan duration =
(Hour x 60 + Minute)/10. For example, if Hour is set to 1 and Minute is set to 30, the value of "Time
Length" in the frequency band scan result is 9 ((1 x 60 + 30)/10).
Step 4 In the Start tab page, select the task to undergo a scan and click Apply to start the scan.
NOTE
You can select multiple tasks to undergo a scan while holding down the Ctrl key.
Only one scan task for a TRX can be performed in a cell at a time.
Scan tasks in different cells can be performed simultaneously. A maximum of eight scan tasks can be performed
at a time.
Step 5 After the scan is complete, the scan result is displayed in the Result column, as shown in Figure
11-9.
Figure 11-9 Completion of a frequency band scan
Issue 08 (2014-06-09)

287
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
----End
Follow-up Procedure
After the scan is complete, the scan result is generated in a directory of the OMU, for example,
\\10.141.122.221\mbsc\bam\common\fam\famlogfmt\BSC0000_[BTSS]
00Log20100519084200.log.zip.
11.16 Querying the Failure Cause of Configuration Alarms

This section describes how to query the detailed failure cause of TRX Config Mismatch
Alarm. This function enables the detailed failure cause of all board configuration alarms under
a BTS to be reported. This facilitates quick location and troubleshooting of alarms. eGBTS does
Prerequisites
l
The BTS type is BTS3900 series.
Context
Configuration alarms of TRX resources are managed in a hierarchical way for BTSs of the
BTS3900 series type that are not in normalization mode. Each alarm type consists of multiple
alarm branches. Each alarm branch consists of multiple alarm items. Each alarm option is related
to multiple alarm causes or alarm sampling points.
As the alarm system is hierarchical and large, users can only obtain information about alarm
branches on a maintenance terminal. No more information about bottom alarms is available. As
a result, it is difficult for users to identify specific configuration failure causes and clear alarms
accordingly.
With the help of this function, maintenance personnel can directly query information about alarm
sampling points when TRX Config Mismatch Alarm occur. This facilitates location of faults.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Query Failure Cause of
Config Alarm. The Query Failure Cause of Config Alarm dialog box is displayed.
Step 3 In the Query Failure Cause of Config Alarm dialog box, select BTS Type and Candidate
BTS and then click Start to query the failure cause of configuration alarms, as shown in Figure
11-10. Query results are displayed in the Query Result area.
Issue 08 (2014-06-09)

288
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Figure 11-10 Querying the Failure Cause of Configuration Alarms
----End
11.17 Call Test

This section describes how to perform a call test. The call test traverses all channels when a BTS
is newly deployed or after cutover and commissioning are complete. A test MS is used to perform
a call test in each cell to be tested under a BTS. This test is performed to detect problems such
as incorrect connection of antenna feeders, main/diversity problems, uplink and downlink
imbalance, one-way audio, and no audio. During a conversation, a forced handover of the calling
MS is performed for at a certain interval. When all idle channels are tested, a call test is complete.
Prerequisites
l
Two MSs are ready.
Context
During the call test, the calling MS only handles the forced handovers that are triggered by the
start of this test.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Call Test. The Call Test tab
page is displayed.
Issue 08 (2014-06-09)

289
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Step 3 Set parameters in the Call Test tab page.

l Test Object
BTS, Cell: indicates the target BTS and cell to be tested
l Time Settings
Stay Time(Second): indicates the period of time when a call stays on the new channel
after a forced handover to a new channel
Waiting Time(Minute): indicates the waiting time between starting the call test and
initiating a call. Waiting time is set to prevent testing staff from delaying the call test for
long after this function is started. The setting of waiting time protects the BTS against the
delay.
l Call Position
Latitude, Longitude: indicates the latitude and longitude where testing staff are located
l Dialed Number: indicates the number to be dialed
Step 4 Click Start and then Yes to start a call test.
NOTE
After starting the call test, you need to dial the number within the time specified by Waiting Time.
Step 5 When the call test traverses all cells, Figure 11-11 is displayed, showing that the call test is
complete.
Figure 11-11 Completion of a call test
Issue 08 (2014-06-09)

290
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
----End
Follow-up Procedure
After a call test is complete, the test result is generated in a directory of the OMU, for example,
\\10.161.101.201\mbsc\bam\common\bts\log\cltlog\20090716_165746_0001.cltlog.
11.18 Antenna Feeder Intermodulation Test

This section describes how to analyze the intermodulation interference in the uplink on the basis
of the difference between the scanned results of uplink frequencies before and after power
transmission. eGBTS does not support this function. Only base stations of versions earlier than
V100R008C00 support the antenna feeder intermodulation test.
Prerequisites
l
Context
Passive antenna feeder intermodulation results in interference when the transmit power of the
BTS exceeds a certain value. Interference disappears once the BTS stops transmitting. Based on
the characteristics of passive antenna feeder intermodulation, an antenna feeder intermodulation
test is performed. Frequencies are scanned for analysis of interference both when a TRX is turned
on and turned off. Test results of the two situations are compared to determine whether uplink
intermodulation interference exists.
NOTICE
Using this function disrupts services in the entire cell.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Antenna Feeder
Intermodulation Test. The Antenna Feeder Intermodulation Test tab page is displayed.
Step 3 Set parameters in the Antenna Feeder Intermodulation Test tab page.
l Test Object
Site, Cell, TRX No.: indicates the site, cell, and number of the TRX to undergo the antenna
feeder intermodulation test. TRX No. uniquely identifies a TRX within one BSC6910.
l Frequency Band: indicates the type of TRX frequency band. You can query it by running the
DSP BTSBRD command.
Issue 08 (2014-06-09)

291
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
l Start, End: indicates the start frequency and end frequency of a scan. The two frequencies
define the scan range. A scan is performed from the starting frequency to the end frequency.
l Frequency Band Scan Duration
Hour, Minute: indicates the time length for a frequency band scan expressed in hours and
minutes. The length of Minute must be an integer multiple of 10. Two scan tests start in
sequence during the test. The time length of the test is about twice as long as Frequency
Band Scan Duration.
Step 4 Click Start to start the test.
NOTE
You can view the intermodulation test status in the Test Status tab page.
----End
Follow-up Procedure
After the intermodulation test is complete, the test result is generated in a directory of the OMU,
for example, \\10.161.101.201\mbsc\bam\common\fam\famlogfmt\BSC0000_[BTSS]
00Log20100519084200.log.zip
NOTICE
Result generation takes time. It is recommended to wait until the next day to view the test result.
11.19 EmergencyDiag
This section describes how to customize a message for EmergencyDiag. This custom message
complying with Huawei message format is sent from the BSC to a base station and users can
obtain information from the response message sent from the base station. The EmergencyDiag
function enables users to remotely connect to the COM port on the main control board. This
function is used in problem location and query of board running status. This function is intended
for only Huawei engineers. COM ports are used only for signal output. eGBTS does not support
this function.
Prerequisites
l
You have run the SND BTSDBGPARA command with EmergencyDiag Switch set to
ON(ON).
NOTE
EmergencyDiag Switch is automatically set to OFF(OFF) if no operation is performed within one hour
after it is set to ON(ON).
Issue 08 (2014-06-09)

292
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > EmergencyDiag. The
EmergencyDiag dialog box is displayed.
Step 3 Set parameters in the EmergencyDiag dialog box.
l Site: indicates the site that a custom message needs to be sent to.
l Message Type: type of the custom message, Custom or Transparent. You can set it only
to Transparent.
l Board Type: indicates the type of base station board. Set it to GTMU.
l Board No.: indicates the number of the board.
l Custom Message: indicates a user-defined message complying with the message format
defined by Huawei.
NOTICE
Before typing other customized messages, enable users to connect to the COM port on the
main control board.
You can send a customized redirStart message, which is case sensitive, to connect to the
COM port on the main control board.
Step 4 Click Send to send the custom message to the base station, as shown in Figure 11-12. The
response message sent from the base station will be displayed in the Message List area.
Issue 08 (2014-06-09)

293
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Figure 11-12 EmergencyDiag
Step 5 After EmergencyDiag is complete, send a customized redirStop message to stop the connection
to the COM port on the main control port.
Step 6 Run the command SND BTSDBGPARA and set the Custom Message Switch to OFF
(OFF).
----End
11.20 Customizing a Message

This section describes how to customize a message that is sent from the BSC to a base station
and complies with Huawei message format. This function enables users to remotely perform
operation and maintenance on a base station by obtaining information from the response message
sent from the base station. This accelerates problem location. Note that this function is intended
for only Huawei engineers. eGBTS does not support this function.
Prerequisites
l
You have run the SND BTSDBGPARA command with Custom Message Switch set to
ON(ON).
Issue 08 (2014-06-09)

294
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
NOTE
Custom Message Switch is automatically set to OFF(OFF) if no operation is performed within one hour
after it is set to ON(ON).
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Custom Message. The Custom
Message dialog box is displayed.
Step 3 Set parameters in the Custom Message dialog box.
l Site: indicates the site that a custom message needs to be sent to.
l Message Type: type of the custom message, Custom or Transparent. Generally, set it to
Transparent.
l Custom Message: indicates a user-defined message complying with Huawei message
format.
Step 4 Click Send to send the custom message to the base station, as shown in Figure 11-13.
Figure 11-13 Custom Message
Step 5 Run the command SND BTSDBGPARA and set the Custom Message Switch to OFF
(OFF).
----End
Issue 08 (2014-06-09)

295
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11.21 Maintaining Site

This section describes how to maintain the sites.
11.21.1 Browsing the BTS Log

This describes how to browse the BTS log. eGBTS does not support this function.
Prerequisites
l

NOTE
GBTS14.0 and later versions do not support this function.
Procedure
displayed.
Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Maintain Site > Browse BTS
Log. The Browse BTS Log tab page is displayed.
Step 3 In the displayed Browse BTS Log tab page, set the parameters as required, and click Start to
browse BTS logs. The operation result is displayed, as shown in Figure 1.
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Browse BTS Log from the
shortcut menu.
Figure 11-14 Browsing the BTS Log
----End
Issue 08 (2014-06-09)

296
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
11.21.2 Testing Transmission Performance

This section describes how to test the E1 self-loopback function to locate the transmission fault
in a BTS. The E1 self-loopback function is used to test the error codes on a timeslot of a
transmission link other than the OML. The E1 self-loopback test affects the ongoing services
on the target timeslot. eGBTS does not support this function.
Prerequisites
l
Context
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Test Transmission
Performance from the shortcut menu.
NOTICE
E1 self-loopback cannot be used to test the error codes on a timeslot of an OML. E1 self-loopback
affects services on the timeslot that is being tested, and IASU self-loopback affects services
carried on all E1 ports.
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Maintain Site > Test
Transmission Performance. The Test Transmission Performance dialog box is
displayed. The operation result is displayed, as shown in Figure 1.

297
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Figure 11-15 Testing Transmission Performance
3.
In the Test Transmission Performance dialog box, set the parameters as required,
and click Start to test transmission performance.
NOTE
For the E1 self-loopback test, set Port to the target E1 port number of the TMU board. each
TMU has four E1 ports numbered from 0 to 3. Loopback Mode can be E1 Loopback or
Timeslot Loopback. If you choose E1 Loopback, all the timeslots on the specified E1 port
are tested. The maximum test duration can be 60 minutes. If you choose Timeslot
Loopback, you can specify the timeslot number. Only one timeslot can be tested each time.
The maximum test duration can be 1,440 minutes.

1.
You can run the following commands to start and stop the transmission performance
test respectively.
Run the STR TRANSPERFTST command to start a transmission performance
test.
Run the STP TRANSPERFTST command to stop the transmission performance
test.
----End
Result
You can view the testing result saved on the PC by referring to Monitoring BER.
11.21.3 Querying BTS Transmission State

This section describes how to query transmission link state of a BTS that is activated. eGBTS
does not support this function.
Issue 08 (2014-06-09)

298
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Prerequisites
l
Context
NOTE
l In the Device Navigation Tree, right-click the target BTS node, and choose Query BTS Transmission
State from the shortcut menu.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Maintain Site >
Query BTS Transmission State. The Query BTS Transmission State dialog box
is displayed.
3.
In the Query BTS Transmission State tab page, set the parameters as required and
then click Query to query the transmission state of the BTS. The operation result is
Figure 11-16 Querying BTS Transmission State

1.
Run the LST BTSCONNECT command to query BTS connection information.
2.
Run the DSP BTSTMUPORTSTATUS command to query the status of the BTS
TMU port.
----End
11.22 Maintaining the Cell

This section describes how to maintain the cells.
11.22.1 Querying Frequency Scan Parameters

This section describes how to query the parameters related to the frequency scan, including the
maximum and average values of the main receiver level and the diverse receiver levels. You can
Issue 08 (2014-06-09)

299
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
perform this task to evaluate the interference condition on the uplink frequency. eGBTS does
Prerequisites
l
The frequency scan has been started (see 11.22.2 Configuring Frequency Scan).
Context
Each TRX has two receivers, wherein one is the main receiver and the other is the diverse
receiver. The main receiver level indicates the voltage level of the uplink signals carried on the
main receiver of the TRX. The diverse receiver level indicates the voltage level of the uplink
signals carried on the diverse receiver of the TRX.
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Maintain Cell >
Query Frequency Scan. The Query Frequency Scan tab page is displayed.
3.
In the displayed Query Frequency Scan tab page, set the parameters as required to
read the corresponding scan result of the frequencies. The operation result is displayed,
Site: indicates the site name of the cell to have its frequency scanned. To query the
site index, run the LST BTS command.
Cell: indicates the name of the cell to have its frequency scanned. To query the
cell index, run the LST GCELL command.
Location Group Number:indicates the NO. of the location group to have its
frequency scanned. To query the cell index, run the LST BTSLOCGRP
command. In a multi-site cell scenario, frequency scanning can be performed in a
single subsite group or all subsite groups.
NOTE
In the Device Navigation Tree, right-click the target cell node, and choose Query Frequency
Scan from the shortcut menu.
Figure 11-17 Querying Frequency Scan Parameters
----End
11.22.2 Configuring Frequency Scan

This describes how to configure the start time of scanning multiple frequencies in a cell and the
scan duration. eGBTS does not support this function.
Issue 08 (2014-06-09)

300
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Prerequisites
Procedure
l

1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Maintain Cell >
Configure Frequency Scan. The Configure Frequency Scan dialog box is
displayed. The operation result is displayed, as shown in Figure 1.
Figure 11-18 Configuring Frequency Scan
3.
In the displayed Configure Frequency Scan dialog box, set the parameters as
required, and click Start to validate the configured data.
Site: indicates the site name of the cell to have its frequency scanned. To query the
site index, run the LST BTS command.
Cell: indicates the name of the cell to have its frequency scanned. To query the
Location Group Number:indicates the NO. of the location group to have its
frequency scanned. To query the cell index, run the LST BTSLOCGRP
command. In a multi-site cell scenario, frequency scanning can be performed in a
single subsite group or all subsite groups.
Issue 08 (2014-06-09)

301
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
NOTE
In the Device Navigation Tree, right-click the target cell node, and choose Configure
Frequency Scan from the shortcut menu.

1.
Run the SET GCELLFREQSCAN command to configure the parameters related to

frequency scan.
----End
11.23 Maintaining TRXs

This section describes how to maintain the TRXs.
11.23.1 Querying the TRX Power Mode

This section describes how to query the theoretical maximum power mode supported by a TRX
and the current power mode of the TRX. eGBTS does not support this function.
Prerequisites
l
Procedure
1.
page is displayed.
2.
In the BTS Maintenance tab page, select BTS Maintenance > Maintain TRX >
Query TRX Power Mode. The Query TRX Power Mode dialog box is displayed.
3.
In the Query TRX Power Mode dialog box, set the parameter as required, and then
click Query to query the power mode. The operation result is displayed, as shown in
Figure 1.
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Query TRX
Power Mode from the shortcut menu.
Issue 08 (2014-06-09)

302
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Figure 11-19 Querying the TRX Power Mode

1.
Run the DSP TRXPWR command to query the power mode of a TRX.
----End
11.23.2 Querying Automatic Power Correction Type

This section describes how to query the automatic power correction type of a TRX board.
Automatic power correction implements compensations to the in-band fluctuation according to
the power template, therefore ensuring the stable output power on frequencies in the same
frequency band. This function is enabled by default for all boards. eGBTS does not support this
function.
Prerequisites
l
Procedure
1.
Issue 08 (2014-06-09)
page is displayed.
303
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
2.
Query Automatic Power Correction Type. The Query Automatic Power
Correction Type dialog box is displayed.
3.
In the Query Automatic Power Correction Type dialog box, set the parameter as
required, and then click Query to query the automatic power correction type. The
operation result is displayed, as shown in Figure 1.
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Query Automatic
Power Correction Type from the shortcut menu.
Figure 11-20 Querying Automatic Power Correction Type

1.
Run the DSP BTSAUPWCRT command to query the automatic power correction
type of a TRX.
----End
11.23.3 Testing TRX Loopback

This describes how to test the TRX loopback. Through this task, you can learn about the TRX
performance and the channel transmission conditions and locate the speech channel problems.
Issue 08 (2014-06-09)

304
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Prerequisites
l
Context
The TRX loopback test involves BIU loopback test and TRX self-loopback test.
l
The BIU loopback test is performed to check the timeslot transmission conditions on the
BTS internal data bus DBUS corresponding to the TRX signaling channel. The TRX sends
the data on the signaling channel to the corresponding signaling timeslot on the BTS internal
DBUS. Then, the data is looped within the TMU so that the TRX receives the signaling
data previously sent by itself. After the TRX receives the data, it compares the data with
the sent data and reports the BER to the LMT. Therefore, you can learn about the signaling
link quality of the BTS internal DBUS.
The TRX self-loopback test is performed to check the TRX conditions. It is performed
automatically by the TRX. You need not set Duration(Second) in this case.
Procedure
1.
page is displayed.
2.
In the BTS Maintenance tab page, choose BTS Maintenance > Maintain TRX >
Test TRX Loopback. The Test TRX Loopback dialog box is displayed.
3.
In the Test TRX Loopback dialog box, set the parameters as required, and then click
Start to test TRX loopback.
NOTE
In the Device Navigation Tree, right-click the target BTS node, and choose Test TRX
Loopback from the shortcut menu.

1.
You can run the following commands to start and stop the TRX loopback test
respectively.
Run the STR BTSTST command to start a TRX loopback test.
Run the STP BTSTST command to stop the TRX loopback test.
----End
11.23.4 Testing Channel Loopback

This describes how to test the transmission capability of the traffic channel and the speech
channel. This task involves TRX RF self-loopback test and BIU self-loopback test on the traffic
channel, and BTS speech loopback test and TRX speech loopback test on the speech channel.
Prerequisites
l
Issue 08 (2014-06-09)

305
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
NOTE
l In the case of TRX RF self-loopback test of a channel numbered n, the channel (n+5)mod8 of all TRXs
in the cell is affected when no frequency hopping occurs. When the RF frequency hopping occurs, the
same channel n of other TRXs in the same frequency hopping group is affected. This test is not
applicable to the baseband frequency hopping.
l The speech channel loopback test must be performed during a conversation. This loopback test can
only be performed between TCHH timeslots from different TCH channels.
Channel loopback tests include TRX RF Self-Loop Test, BIU Loop Test, BTS Voice Loop
Test, and TRX Voice Loop Test.
l
TRX RF Self-Loop Test

This test is performed to evaluate the quality of the RX and TX channels. The TRX RF
self-loopback starts from the DSP, passes the BBU, loops back from the RRU, and then
passes the BBU again to come back to the DSP. The DSP then compares the data with the
original data to learn the RX and TX channel quality of the BTS.
BIU Loop Test

This test is performed to check the timeslot transmission conditions on the BTS internal
data bus DBUS corresponding to the TRX traffic channel. The TRX sends the data on the
traffic channel to the corresponding traffic timeslot on the BTS internal DBUS. Then, the
data is looped within the TMU so that the TRX receives the data previously sent by itself.
After the TRX receives the data, it compares the data with the sent data and reports the
BER to the LMT. Therefore, you can learn about the traffic link quality of the BTS internal
DBUS.
BTS Voice Loop Test

This test is performed to evaluate the connection of the TRX speech channel between the
Um interface and the DBUS within the BTS. The TMU loops back the DBUS timeslot of
the speech channel to be tested. If the TX end receives its own voice signal, you can infer
that the channel connection is normal; otherwise, the connection is disrupted.
TRX Voice Loop Test

This test is performed to evaluate the connection of the TRX speech channel between the
Um interface and the DSP. The DSP encodes and then sends the data. If the TX end receives
its own voice signal, you can infer that the channel connection is normal; otherwise, the
connection is disrupted.
Procedure
l

1.
page is displayed.
2.
Test Channel Loopback. The Test Channel Loopback dialog box is displayed.
3.
In the Test Channel Loopback dialog box, set the parameters as required, and click
Start to test channel loopback.
NOTE
In the Device Navigation Tree, right-click the target TRX node, and choose Test Channel
Loopback from the shortcut menu.
Issue 08 (2014-06-09)

306
BSC6910 GSM
LMT User Guide
11 BTS Maintenance

1.
You can run the following commands to start or stop the operation.
Run the STR BTSTST command to start a channel loopback test.
Run the STP BTSTST command to stop the channel loopback test.
----End
11.23.5 Testing Idle Timeslots

This describes how to test the idle timeslots in the network to test the maximum interference
capacity of the network. eGBTS does not support this function.
Prerequisites
l
Context
In the network optimization stage, you need to perform this task to test the maximum interference
capacity of the network. By this test, dummy bursts are sent on all the idle timeslots in a specific
area. The test duration is predefined to 1 to 24 hours before the test and stopped by the software
automatically. You can also stop the test manually during the process.
Procedure
l

1.
page is displayed.
2.
Test Idle Timeslot. The Test Idle Timeslot dialog box is displayed.
3.
In the Test Idle Timeslot dialog box, set the parameters as required, and click Start
to test idle timeslots. The operation result is displayed, as shown in Figure 1.
Site: indicates the site name of the cell to have its idle timeslot tested. To query
the site index, run the LST BTS command.
Cell: indicates the name of the cell to have its idle timeslot tested. To query the
Location Group Number:indicates the NO. of the location group to have its idle
timeslot tested. To query the cell index, run the LST BTSLOCGRP command.
In a multi-site cell scenario, idle timeslot tests can be performed in a single subsite
group or all subsite groups.
NOTICE
Dynamic configuration (such as adding or deleting TRXs, switching over active
and standby TRXs) will stop all idle timeslot tests in a multi-site cell.
Issue 08 (2014-06-09)

307
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
TRX No.: uniquely identifies within a BSC6910 the TRX of non-BCCH channels
to have their idle timeslot tested. To query the TRX number, run the LST
GTRX command.
Figure 11-21 Testing Idle Timeslots

1.
You can start or stop the operation by running the following commands:
Run the STR TRXBURSTTST command to start testing the idle timeslots.
Run the STP TRXBURSTTST command to stop testing the idle timeslots.
----End
11.23.6 Resetting the TRX

This section describes how to reset a faulty TRX in a specified BTS. For 3900 series base stations,
a TRX is reset by re-initializing the TRX.
Prerequisites
l
Issue 08 (2014-06-09)

308
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
NOTICE
l If a TRX on a double-transceiver or multi-carrier board is reset, the ongoing services carried
by all TRXs on the board are not affected.
l If a TRX on a single-transceiver board is reset, the ongoing services carried by the TRX are
interrupted, and the board is reset. The service interruption time is determined by the board
resetting time.
l Exercise caution when resetting a TRX on a single-transceiver board, because this operation
will interrupt ongoing services.
Procedure
l

1.
page is displayed.
2.
Reset TRX. The Reset TRX dialog box is displayed. The operation result is
Figure 11-22 Resetting the TRX
3.
In the Reset TRX dialog box, set the parameters as required, and then click Reset.
NOTE
In the Device Navigation Tree, right-click the target TRX node, and choose Reset TRX from
the shortcut menu.

1.
Run the RST TRX command to reset a TRX of a BTS.
----End
11.23.7 Querying TRX Timeslot

This section describes how to query timeslot information of channels corresponding to a TRX.
Issue 08 (2014-06-09)

309
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Prerequisites
l
Procedure
1.
page is displayed.
2.
Query TRX Timeslot. The Query TRX Timeslot dialog box is displayed.
NOTE
You can also perform the task by right-clicking a site, cell, and TRX node under Device
Navigation Tree and then choosing Query TRX Timeslot from the shortcut menu.
3.
Set parameters in the Query TRX Timeslot dialog box and then click Query to query
timeslot information of channels corresponding to the TRX. Figure 11-23 shows the
query result.
Figure 11-23 Results of querying TRX timeslots

1.
Run the LST GTRXCHAN command to query timeslot information of channels

corresponding to a TRX.
----End
11.23.8 Enabling RF Data Collection Function for a TRX

This task is performed to enable the RF data collection function for a TRX. This function collects
the data of all nodes on the RF channel where the specified TRX is located and generates files
on the TRX module. This enables R&D engineers to obtain the required data and analyze the
status of all nodes on the RF channel. eGBTS does not support this function.
Prerequisites
l
Issue 08 (2014-06-09)

310
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Context
Introduction to collection data:
Collection Type
Sub-Collection Type
0: software data collection
0-255: reserved
1: data collection in an intermediate

frequency (IF) digital domain
The high-order 4 bit of a sub-collection type

represents a channel. (F represents that the
RRU traverses all channels delivered by the
main control board.) The low-order 4 bit
represents a collection node No..
0: collecting TRX common processing data
1: collecting TRX IQ data
14: detailed check on TRX data
For example, 0x10 (16) represents the data
collection data of node 0 on channel 1.
2: data collection in an IF analog domain
The high-order 4 bit of a sub-collection type

represents a channel. The low-order 4 bit
represents an operation type. The detailed
meanings are as follows:
0: collecting important data
1: suspending DPD
2: recovering DPD
3: direct DPD
For example, 0x10 (16) represents the
important collection data on channel 1.
NOTE
A reserved value indicates that no function is implemented. It is used for future function extension.
Procedure
l
Issue 08 (2014-06-09)

1.
page is displayed.
2.
In the BTS Maintenance tab page, choose BTS Maintenance > TRX RF
Sampling. The TRX RF Sampling dialog box is displayed, as shown in Figure
11-24.

311
BSC6910 GSM
LMT User Guide
11 BTS Maintenance
Figure 11-24 TRX RF Sampling
3.
In the TRX RF Sampling dialog box, set associated parameters as follows:

Site: indicates the site index of the cell to have its TRX data collected. To query
the site index, run the LST BTS command.
Cell Name: indicates the index of the cell to have its TRX data collected. To query
the cell index, run the LST GCELL command.
TRX No.: uniquely identifies within a BSC6910 the TRX of non-BCCH channels
to have their TRX data collected. To query the TRX number, run the LST
GTRX command.
Location Group No.:indicates the NO. of the location group to have its TRX data
collected. To query the cell index, run the LST BTSLOCGRP command.
Sampling Type:set Sampling Type to the type of the data to be collected by
referring to Background.
Sub Sampling Type:set Sub Sampling Type to the type of the sub-data to be
collected by referring to Background.
4.
4. Click Start to enable the RF data collection function for a TRX.
----End
Follow-up Procedure
After the RF data collection function is disabled for a TRX, you can run the STR BTSLOG
command with Command Parameter set to RFSTUFF to obtain the generated file, and run the
ULD BTSLOG command to upload the file to the specified FTP server.
11.24 Reference for BTS Maintenance

This section describes the parameters used for BTS maintenance.
Issue 08 (2014-06-09)

312
BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
11 BTS Maintenance
Maintenanc
e Item
Parameter
Description
Querying
BTS
RUNNING
Status
Normal OML
Indicates whether the OML link between the current

site and BSC is normal.
BTS Initialized
Indicates whether the current site is initialized.
Cell Initialized
Indicates whether the current cell is initialized.
BCCH Mutual Aid
Indicates that whether mutual aid is enabled between

the BCCH TRX and other TRXs when the BCCH TRX
is faulty.
BT Hop Mutual
Aid
Indicates that whether mutual aid is enabled when the

TRX participating in the baseband frequency hopping
is faulty in a cell.
Local
Management
Rights
Indicates whether the BTS maintenance is performed

through the E1 port or serial port.
Frequency
Scanning
Indicates whether the uplink frequency scanning is

performed.
TMU Not
Activated Cause
Indicates the cause why the automatic TMU activation

fails when the running version of the BTS TMU
specified by the BSC is inconsistent with the
configured one.

313
BSC6910 GSM
LMT User Guide
12 FAQ
12
FAQ
About This Chapter

This chapter describes some frequently asked questions (FAQs) and the corresponding solutions.
12.1 Slow Responses in the Firefox Browser
Running in the Firefox browser, the LMT gives slow responses. For example, it takes about 30
seconds to maximize the window of a trace task in the Trace tab page. In this case, check whether
the add-on extension Live Margins is installed.
12.2 LMT Colors Cannot Be Displayed
When the LMT is started in the IE browser, the colors are not properly displayed. For example,
the colors indicating the status of the boards and alarms are not displayed, or the background
color of the LMT is not differentiated from that of the IE browser. In this case, check the color
settings of the browser.
12.3 The Verification Code Cannot Be Displayed on the LMT Login Page
The verification code cannot be displayed when you try to log in to the LMT using an Internet
Explorer (IE) browser in Windows Server 2008 or Windows Vista. When this problem occurs,
check the settings related to the protected mode of the browser.
12.4 Installing OS Patches
In a Microsoft Windows operating system (OS), you need to install patch KB944338, KB938397
or KB960714 if the OS and IE are in a certain version.
12.5 No Response When Clicking the Menu Bar on the LMT
When you browse the LMT web page, there is no response or a script error dialog box is
displayed. To be specific, when you click the menu bar or buttons or right-click the web page,
there is no response or a dialog box is displayed, indicating a script error, for example,
Permission Denied or Access Denied. In this case, check the proxy settings in the browser.
12.6 Changing the Computer Time During the LMT Use Prohibited
Changing the computer time during the LMT use is prohibited. Changing the computer time
causes some functions of the LMT to stop functioning normally. For example, the OMU time
fails to refresh normally; tracing data and monitoring data fail to refresh normally; progress
management fails to refresh normally.
12.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding
Issue 08 (2014-06-09)

314
BSC6910 GSM
LMT User Guide
12 FAQ
If a csv file in UTF-8 coding is saved on the LMT with non-English characters in it and the csv
file is opened in the Excel format by using the regular method, all the non-English characters
are displayed as corrupted characters. In this case, open the csv file by using the import method
in Excel.
12.8 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously
You can have multiple LMT clients started on one PC. Starting too many LMT clients
simultaneously, however, affects maintenance performance.
12.9 How to Set the Browser Under Citrix Farm Networking
Under Citrix farm networking, when you use the M2000 proxy server to log in to the LMT on
a Citrix client, the LMT may be suspended, the verification code may be unavailable, or
initialization of the MML navigation tree may fail. When these problems occur, check the
browser settings, including the setting of the browser proxy server and the HTTP 1.1 setting. If
either setting is wrong, reset it.
12.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.
12.11 Unable to Download or Install the Java or Flash Plug-in and Two File Manager Windows
Displayed Windows IE8 or Any Later Version Is Used
If users log in to the LMT in IE8 or later versions, an error message displays when they are
downloading or installing a Java or Flash plug-in, or two file manager windows are displayed.
To solve the problem, disable SmartScreen Filter of IE8.
12.12 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification
of JRE
This section describes how to solve the problem that the LMT does not respond or responds
incorrectly when users perform a function on the LMT.
12.13 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes
the Web Pages to Turn Blank
Some LMT Web pages fail to update when batch processing, tracing, or monitoring is in use.
Any further operation causes the Web pages to turn blank. If you restart the function, the Web
page returns to normal. To prevent this problem, perform the following operations to add an
environment variable.
12.14 Configuring the HTTPS Login Mode
This section describes how to configure the HTTPS login mode and a security certificate. Users
can log in to the LMT through either HTTP or HTTPS. The login mode is configurable.
12.15 The Error "Certificate Invalid" Is Displayed During an HTTPS Login
The LMT certificate and the certificate used to access the LMT through the M2000 proxy with
dual IP addresses are not granted by any commercial organization. Therefore, they are not trusted
by a browser such as IE by default. In such a scenario, the SSL certificate negotiation is
performed when you visit the LMT in HTTPS mode. If the organization for issuing the current
certificate is not in the default trust list of Microsoft, the Certificate Invalid error is displayed
on the browser. This error does not impair the LMT functions. This section describes how to
correct the error Certificate Invalid displayed during a login to the LMT through HTTPS. To
correct this error, add the root certificate of the certificate in use to the Trusted Root
Certification Authorities list.
12.16 The Error 'Mismatched Address' Is Displayed During an HTTPS Login
Issue 08 (2014-06-09)

315
BSC6910 GSM
LMT User Guide
12 FAQ
A user uses an IP address rather than a domain name to access the LMT. Therefore, the
Mismatched Address error is displayed on the browser during an HTTPS login. This error does
not impair the LMT functions. This section describes how to correct the error "Mismatched
Address" displayed during a login to the LMT through HTTPS. To correct this error, deselect
the Warn about certificate address mismatch* option.
12.17 Tracing and Monitoring Functions Cannot Be Used
Tracing and monitoring functions cannot be used after a successful login to the LMT. Solve this
problem by using the following methods.
12.18 No response when click the control component or right-click during the tracing and
monitoring processes
Some time after a successful login to the LMT, you may suddenly find that batch processing
fails with no error message. Alternatively, after a tracing or monitoring task is created, the task
page is not opened. There is no response or any error message. The NE task list shows that this
task has been successfully created. There is no response when you click saving files in the tracing
or monitoring interface. There is no detailed parsing information when you double-click a tracing
or monitoring message. There is no response when you right-click the window for displaying
tracing or monitoring results. There is no response when you right-click the window for
displaying tracing or monitoring results and choose Save All Messages and Save Selected
Messages from the shortcut menu. If you open a new browser and log in to the LMT again, the
task nevertheless can be successfully created. If either of the previous problems occurs, perform
the following operations:
12.19 Interfaces for Performing Tracing or Monitoring Tasks Blinking
Interfaces for performing tracing or monitoring tasks blink.
12.20 Unable to Save Tracking and Monitoring Data
When a tracking or monitoring task (such as the UE tracking task) is running on the LMT, it is
possible that the vast amounts of tracking or monitoring data cannot be saved even with sufficient
hard disk space. Solve the problem by using the method described in the procedure part.
12.21 The File Manager Functions Improperly
When the file manager functions improperly or cannot be used, perform the following
operations:
12.22 BTS Nodes Cannot Be Displayed Under Device Navigation Tree
After a successful login to the LMT, you may find that BTS nodes cannot be displayed under
Device Navigation Tree. After upgrading the browser, you find that the nodes can be displayed
normally. This problem occurs because data under Device Navigation Tree on the LMT is
compressed whereas Internet Explorer 6 SP2 does not support compression of chunked data.
Solve this problem by using either of the following methods.
12.23 The Alarm/Event Function Becomes Unavailable
When starting or using the Alarm/Event function after a successful login to the LMT, the page
may become white with an exclamation mark displayed in the center. The exclamation mark is
circled in gray, as shown in the following figure: Solve this problem by using the following
methods.
12.24 Incorrect Display of the Path for Downloading BTS Software
After you log in to the LMT using Microsoft Internet Explorer (IE), enter the Download BTS
Software tab page, click Browse on the Download Files tab page, and select the BTS software
to be downloaded, you may find that the downloading path is displayed incorrectly. When this
occurs, check whether Include local directory path when uploading files to a sever is
prohibited.
Issue 08 (2014-06-09)

316
BSC6910 GSM
LMT User Guide
12 FAQ
12.25 The Message 'Class doesn't support Automation' Is Displayed in an IE Browser

After clicking Login in an Internet Explorer (IE) browser, you find a blank window displayed
and login unable to continue. In the bottom left corner of the IE browser, a yellow error icon is
displayed. The icon says "Class doesn't support Automation". To solve the problem, perform
the following steps:
12.26 Java Installation Fails
During Java installation, the message "Error 25099, Unzipping core files failed." is displayed.
To solve the problem, perform the following steps:
12.27 The LMT Login Web Page Cannot Be Opened with the PC OMU Installed
With the PC OMU installed in Windows 7, the LMT login web page cannot be opened. In
addition, the LMT process cannot be found in the task manager.
12.28 Changing Settings for the Next-Generation Java Plug-in Fails
When changing settings for Enable the next-generation Java Plug-in, you are prompted with
a message indicating that the changing fails because one or more browsers are running. As a
matter of fact, no browser is running. The following figure shows the message: To solve the
problem, perform the following steps.
12.29 Error Message"This user session already exists" Upon Login to LMT
The interface displays an error message "This user session already exists" upon login to LMT.
Solve the problem by using the method described in the procedure part.
12.30 The "Are You Sure You Want to Quit the Page" Dialog Box Is Displayed
After successful login to the LMT in the IE8 or IE9 browser, the "are you sure you want to quit
the page?" dialog box is displayed when the alarm feature is enabled. Solve the problem by using
the method described in the procedure part.
12.31 Slow Response During an LMT Login
The LMT responses slowly when the users are trying to log in to the LMT. To solve the problem,
perform the following steps:
12.32 Unclear Grids in the Tables in the MML Online Help
The grids in the tables are not clear in MML online help when users log in to the LMT by some
computers. To solve the problem, perform the following steps.
12.33 The "App Center" Web Page Is Automatically Displayed When Firefox Is Used to Browse
the LMT
When you use Firefox to browse the LMT, if you press F1 or click FTP Tool on the LMT web
page, the App Center web page is automatically displayed. In this case, disable the App
Center on the Add-ons Manager page.
12.34 "Permission Denied" or "Access Denied" is Displayed When IE Is Used to Browse the
LMT
When you log in to the LMT through IE, a Permission Denied or Access Denied message is
displayed.
12.35 MML Command Failed to Be Executed or No Response to Tracing Tasks After the
Browser Is Upgraded to IE8
After the browser is upgraded from IE6 to IE8, some cache files cannot be removed. As a result,
the system displays a Please check the MML macro configure file! message when an MML
command is executed, or there is no response after tracing tasks are created. To solve this
problem, you need to manually remove cache files and cookies.
12.36 How to Handle Error Message Displayed on the LMT
Issue 08 (2014-06-09)

317
BSC6910 GSM
LMT User Guide
12 FAQ
The error message Problems with this Web page might prevent it from being displayed
properly or functioning properly. is displayed in the Internet Explorer during the logging in
of the LMT.
12.37 Tracing File Not Being Uploaded to the Specified Directory
If you close the UE Trace or IOS Trace dialog box during the UE tracing or IOS tracing, the
tracing result file being generated cannot be uploaded to the specified directory. This problem
occurs in the following scenario: In the UE Trace or IOS Trace dialog box, Debug is selected
and Trace Mode is set to Report File. To solve the problem, perform the steps in Procedure.
After a successful login to the LMT, the previous settings, such as system settings, do not take
effect. To solve this problem, perform the following steps:
Issue 08 (2014-06-09)

318
BSC6910 GSM
LMT User Guide
12 FAQ
12.1 Slow Responses in the Firefox Browser

Running in the Firefox browser, the LMT gives slow responses. For example, it takes about 30
seconds to maximize the window of a trace task in the Trace tab page. In this case, check whether
the add-on extension Live Margins is installed.
Procedure
Step 1 Start the Firefox, choose Tool > Add-ons. The Add-ons window is displayed.
Step 2 In the Extensions tab page, select Live Margins, and click Disable. The message "Restart
Firefox to complete your changes" is prompted.
Step 3 Click Restart Firefox to validate the changes.
----End
12.2 LMT Colors Cannot Be Displayed

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

LMT Login Page
The verification code cannot be displayed when you try to log in to the LMT using an Internet
Explorer (IE) browser in Windows Server 2008 or Windows Vista. When this problem occurs,
check the settings related to the protected mode of the browser.
Context
If the protected mode is enabled for the IE browser in Windows Server 2008 or Windows Vista,
many security restrictions are imposed. For example, JavaScript and Applet cannot be run.
Therefore, you must disable the protected mode. Otherwise, the LMT web page cannot be
displayed.
Issue 08 (2014-06-09)

319
BSC6910 GSM
LMT User Guide
12 FAQ
Procedure
Step 1 Enter the external virtual IP address of the OMU in the address box of the IE browser. Press
Enter on the keyboard, or click Go next to the address bar to display the login window of the
BSC6910.
Step 2 Check whether "Internet | Protected Mode: Off" is displayed in the bottom right corner of the
window.
l If yes, the task is complete.
l If no, go to Step 3.
box is displayed.
Step 4 On the Security tab page, select Trusted sites in the Select a Web content zone to specify its
security settings area.
Step 5 Clear Enable Protected Mode in the Security level for this zone area. Click Sites. The Trusted
sites dialog box is displayed.
Step 6 Type the external virtual IP address of the OMU in the Add this website to the zone text box,
and then click Add. The external virtual IP address of the OMU is added to the Trusted sites
list.
NOTE
If the M2000 proxy server is used for the login to the LMT, add the IP address of the M2000 to the Trusted
sites list.
NOTE
Restart the browser to validate the modifications.

If IE9 is used, in addition to the previous settings, choose Tools > Compatibility View Settings. In the
displayed Compatibility View Settings dialog box, select Display all websites in Compatibility View.
----End

In a Microsoft Windows operating system (OS), you need to install patch KB944338, KB938397
or KB960714 if the OS and IE are in a certain version.
Context
l
Patch KB960714 solves the problem of Java console output error. Therefore, the Java
application can be loaded successfully on the LMT.
Patch KB944338 improves the performance of the LMT by increasing the speed of visiting
a web page. Therefore, the LMT running rate can be increased.
If Windows 7 operating system is used, Windows patches do not need to be installed.
Issue 08 (2014-06-09)

320
BSC6910 GSM
LMT User Guide
12 FAQ
Procedure
Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or Remove
Programs icon.
Step 2 In the displayed Add or Remove Programs window, select Show updates. Check whether
patches KB944338, KB938397 and KB960714 are present in the list of Currently installed
programs.
l If the patches are present, the task is complete.
l If the patches are not present, go to Step 3.
Step 3 Determine whether a Windows patch needs to be installed according to the OS version and IE
version.
l Patch KB960714 needs to be installed when the OS version and IE version are combined in
the following ways:
OS Version
IE Version
Windows 2000 SP4
IE5/IE6 SP1
Windows XP SP3
IE6/IE7
Windows Server 2003 SP1/SP2
IE6/IE7
Windows Vista
IE7
l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4 or
Windows Server 2003 SP1/SP2.
l When the Windows 2003 operating system is used, the service pack KB938397 needs to be
installed. This service pack ensures that the Windows 2003 operating system supports the
SHA256 algorithm. After the service pack is installed, the LMT can work properly.
NOTE
l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.

l To download patch KB938397, go to http://support.microsoft.com/?kbid=938397.
l Download a suitable patch according to the OS version and IE version.
----End
12.5 No Response When Clicking the Menu Bar on the LMT

When you browse the LMT web page, there is no response or a script error dialog box is
displayed. To be specific, when you click the menu bar or buttons or right-click the web page,
there is no response or a dialog box is displayed, indicating a script error, for example,
Permission Denied or Access Denied. In this case, check the proxy settings in the browser.
Context
Do not modify the settings of the browser when you have logged in to the LMT. Before you log
in to the LMT, set the proxy server when necessary.
Issue 08 (2014-06-09)

321
BSC6910 GSM
LMT User Guide
12 FAQ
Procedure
l
IE
1.
Choose Tool > Internet Options on the tool bar of the IE browser. The Internet
Options dialog box is displayed.
2.
On the Connections tab page, click LAN Settings. The Local Area Network (LAN)
Settings dialog box is displayed.
3.
In the Proxy server area, select Use a proxy server for your LAN (These settings
will not apply to dial-up or VPN connections). Type the IP address and port number
of the proxy server in the corresponding text boxes, and then click Advanced. The
Proxy settings dialog box is displayed.
4.
In the Exceptions area, type the external virtual IP address of the OMU in the text
box, and then click OK. Close the Internet Options dialog box.
Firefox
1.
Choose Tools > Options on the tool bar of the Firefox browser. The Options dialog
box is displayed.
2.
In the Options dialog box, click Advanced. On the Network tab page, click
Settings. The Connection Settings dialog box is displayed.
3.
In the Connection Settings dialog box, select Manual proxy configuration. Type
server address and port number in the HTTP proxy area. Then select Use this proxy
server for all protocols.
4.
In the No Proxy for area, type the OMU external virtual IP address and click OK.
Then close the Options dialog box.
----End
12.6 Changing the Computer Time During the LMT Use

Prohibited
Changing the computer time during the LMT use is prohibited. Changing the computer time
causes some functions of the LMT to stop functioning normally. For example, the OMU time
fails to refresh normally; tracing data and monitoring data fail to refresh normally; progress
management fails to refresh normally.
12.7 Corrupted Characters Appearing When the csv File Is

Opened in UTF-8 Coding
If a csv file in UTF-8 coding is saved on the LMT with non-English characters in it and the csv
file is opened in the Excel format by using the regular method, all the non-English characters
are displayed as corrupted characters. In this case, open the csv file by using the import method
in Excel.
Procedure
Step 1 On the menu bar of Excel, choose Data > Import External Data > Import Data. Then the
Select Data Source dialog box is displayed. Figure 12-1 shows the dialog box.
Issue 08 (2014-06-09)

322
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-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 12-2 shows the dialog box. Select UTF-8
in File origin.
Figure 12-2 Text import wizard-step 1
Issue 08 (2014-06-09)

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

----End
Issue 08 (2014-06-09)

324
BSC6910 GSM
LMT User Guide
12 FAQ
12.8 Maximum Number of LMT Clients That Can Be Started

on One PC Simultaneously
You can have multiple LMT clients started on one PC. Starting too many LMT clients
simultaneously, however, affects maintenance performance.
In normal maintenance, the maximum number of LMT clients that can be started on one PC
simultaneously is as follows:
l
One PC with 2 GB memory can start 16 LMT clients simultaneously.
One PC with 1 GB memory can start 8 LMT clients simultaneously.
One PC with 512 MB memory can start 4 LMT clients simultaneously.
12.9 How to Set the Browser Under Citrix Farm Networking

Under Citrix farm networking, when you use the M2000 proxy server to log in to the LMT on
a Citrix client, the LMT may be suspended, the verification code may be unavailable, or
initialization of the MML navigation tree may fail. When these problems occur, check the
browser settings, including the setting of the browser proxy server and the HTTP 1.1 setting. If
either setting is wrong, reset it.
Context
You can set the browser under Citrix farm networking in the following ways:
l
Script setting: An automatic setting script is placed on the domain control server. After a
Citrix user logs in to the server, the script automatically sets the browser.
Manual setting: The browser is set manually.
The Citrix server works in the farm mode. In farm mode, the primary Citrix server and secondary
Citrix servers work in cooperation to achieve load balancing. When a Citrix user logs in to the
Citrix server on a Citrix client, the server in use may vary. The proxy server of the browser
therefore may need to be set again and again. We therefore recommend setting the browser using
the script. With the script, each time the user visits the server, automatic setting of the browser
is performed.
The following procedure uses Internet Explorer (IE) as an example.
Procedure
l
Script Setting
1.
Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
setlocal ENABLEDELAYEDEXPANSION
set uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul
\Internet Settings"
Issue 08 (2014-06-09)

325
BSC6910 GSM
LMT User Guide
12 FAQ
reg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nul
reg add %uu% /v ProxyOverride /t REG_SZ /d "<local>" /f >nul
reg add %uu% /v ProxyEnable /t REG_DWORD /d "1" /f >nul
NOTE
The IE-unset.bat script file implements automatic setting of the browser for the domain user.
The domain user can change 10.121.49.213:80 in reg add %uu% /v ProxyServer /t
REG_SZ /d "10.121.49.213:80" /f >nul in the script to the actual IP address of the proxy
server and the actual port number.
2.
Log in to the primary or a secondary domain control server with the user name of
administrator and place the IE-unset.bat file in the C:\WINDOWS\SYSVOL\sysvol
\citrixtest.com\scripts path on the server.
NOTE
The default installation path on the domain control server is C:\WINDOWS\SYSVOL\sysvol

\citrixtest.com\scripts. The path changes if you install the file elsewhere. Here,
citrixtest.com is an example of the domain name. The actual domain name may be different.
3.
For details about how to create a domain user, refer to the Citrix Access Solution User
Guide.
4.
Apply the script to the domain user.

Assume that there is a user named hong01 in the hongtest unit of the citrixtest.com
domain.
a.
Start Active Directory Users and Computer and double-click hongtest in the
left-side pane. In the right-side pane, all users in the hongtest unit are displayed,
as shown in Figure 12-5.
Figure 12-5 Active Directory Users and Computers
b.
Issue 08 (2014-06-09)
In the right-side pane, right-click hong01. Choose Properties from the shortcut
menu. The hong01 Properties dialog box shown in Figure 12-6 is displayed.

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

327
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-7 Applying the script in the hong01 Properties dialog box
Manual Setting
1.
2.
Issue 08 (2014-06-09)
Check the proxy server setting of the browser.

a.
Choose Tools > Internet Options on the tool bar of the IE. The Internet
b.
On the Connections tab page, click LAN Settings. The Local Area Network
(LAN) Settings dialog box is displayed.
c.
In the Proxy server area, select Use a proxy server for your LAN (These
settings will not apply to dial-up or VPN connections). Set Address of the
proxy server to the IP address of the M2000 and Port to 80.
Check HTTP 1.1 settings of the browser.

a.
Choose Tools > Internet Options on the tool bar of the IE. The Internet
b.
On the Advanced tab page, select Use HTTP 1.1 through proxy connections
under HTTP 1.1 settings, click Apply, and then click OK. Figure 12-8 shows
the window.

328
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-8 HTTP 1.1 settings
----End
12.10 Unable to Log In To LMT Because IE Default Security

Level Is Too High
In a Windows Server operating system (including Windows Server 2003 and Windows Server
2008), the IE blocks Web programs of sites that are out of the trusted site list to improve system
security. As a result, you may fail to log in to the LMT.
Context
l
Issue 08 (2014-06-09)
When you try to log in to the LMT by entering the IP address in the IE address bar, the
following web page will be displayed for your wanted page is out of the trusted site list.
Therefore, you may fail to log in to the LMT.

329
BSC6910 GSM
LMT User Guide
12 FAQ
According to the acceptable IE security level, there are the following two solutions:
When lowering the IE security level on the Windows server is unacceptable, you can
add the LMT site to the trusted sites of the IE by using a configuration startup script.
The system automatically loads the script and configures the IE after a Citrix user logs
in.
When lowering the IE security level on the Windows server is acceptable, you can
remove the Windows component, Internet Explorer Enhanced Security Configuration.
Procedure
l
Setting a configuration startup script

1.
Prepare a script.
Type the following script content in a notepad and save it as IE-unset.bat.
@echo off
\Internet Settings"
reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul
reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nul
\Internet Settings\ZoneMap\EscRanges\Trust"
reg add %uu% /v :Range /t REG_SZ /d "10.141.149.193" /f >nul
reg add %uu% /v http /t REG_DWORD /d "2" /f >nul
NOTE
l The IE-unset.bat script file implements automatic setting of IE trusted sites for Citrix domain
users.
l The domain user can change 10.141.149.193 in reg add %uu% /v :Range REG_SZ /d
"10.141.149.193" /f >nul in the script to the IP address of the network element or the peer IP
address of the network elements that need to be visited.
l If the user needs to set multi-network elements and the network elements don't exist in a same
peer IP address, multi-scripts need to be prepared and loaded separately.
l Trust in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings\ZoneMap\EscRanges\Trust" can be named as you wish.
Issue 08 (2014-06-09)

330
BSC6910 GSM
LMT User Guide
12 FAQ
2.
Load the startup script.

Script setting for a single Windows server
a.
Log in to the Windows server with the account of administrator. Choose

Start > Run.
b.
Type gpedit.msc in the displayed dialog box. Then click OK. The Group
Policy Object Editor dialog box is displayed.
c.
In the Group Policy Object Editor dialog box shown in Figure 12-9, choose
User Configuration > Windows Settings > Scripts(Logon/Logoff).
Figure 12-9 Script
d.
Issue 08 (2014-06-09)
Double-click Logon. A dialog box shown in Figure 12-10 is displayed. Click

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

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

332
BSC6910 GSM
LMT User Guide
12 FAQ
g.
In the dialog box shown in Figure 12-10, click Apply and confirm to load
the prepared script.
h.
Restart the IE to validate the configuration.

NOTE
The users need to log in to the Citrix client to validate the configuration in the single Citrix
network.
Script setting in a Citrix Farm network

a.
Log in to the primary or secondary Citrix domain control server with the
account of administrator. Choose Start > Programs > Administrative
Tools > Active Directory Users and Computer. Select an organization unit
and then right-click Properties. Click the Group Policy tab page in the
displayed dialog box and click New to create a group policy object.
NOTE
l If the organization unit has be set, the users which belong to the organization unit can
all succeed in logging in to the LMT.
l You can rename the group policy object.
b.
Select the created group policy object and click Edit. In the displayed dialog
box shown in Figure 12-12, choose User Configuration > Windows
Settings > Scripts(Logon/Logoff).
Figure 12-12 Script
c.
Issue 08 (2014-06-09)
Double-click Logon. A dialog box shown in Figure 12-13 is displayed. Click

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

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

334
BSC6910 GSM
LMT User Guide
12 FAQ
f.
l
In the dialog box shown in Figure 12-13, click Apply and confirm to load
the prepared script.
Removing Internet Explorer Enhanced Security Configuration

1.
Log in to the Windows server with the account of administrator. Choose Start >
Control Panel > Add or Remove Programs. Select Internet Explorer Enhanced
Security Configuration in the displayed dialog box shown in Figure 12-15.
Figure 12-15 Windows components wizard
2.
Issue 08 (2014-06-09)
Click Details... in the dialog box shown in Figure 12-15. In the displayed dialog box
shown in Figure 12-16, deselect For administrator groups and For all other user
groups.

335
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-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
12.11 Unable to Download or Install the Java or Flash Plugin and Two File Manager Windows Displayed Windows IE8
or Any Later Version Is Used
If users log in to the LMT in IE8 or later versions, an error message displays when they are
downloading or installing a Java or Flash plug-in, or two file manager windows are displayed.
To solve the problem, disable SmartScreen Filter of IE8.
Context
SmartScreen Filter is a new function of IE8 and later versions. It prevents users from visiting
phishing websites and prevents plug-ins from being installed automatically.
SmartScreen Filter causes an error message to be displayed when users are downloading the
Java or Flash plug-in during login to the LMT.
In addition, two file manager windows displays after clicking File Manager.
Issue 08 (2014-06-09)

336
BSC6910 GSM
LMT User Guide
12 FAQ
Procedure
Step 1 On the menu bar of the IE browser, choose Safety > SmartScreen Filter > Turn Off
SmartScreen Filter.
Step 2 In the displayed Microsoft SmartScreen Filter dialog box, select Turn off SmartScreen
Filter and click OK to turn off the SmartScreen filter.
----End
12.12 LMT Fails to Function Properly When Error Occurs in

Mixed Code Security Verification of JRE
This section describes how to solve the problem that the LMT does not respond or responds
incorrectly when users perform a function on the LMT.
Prerequisites
The LMT does not respond or responds incorrectly when users manage progress, process MML
commands in batches, trace messages, or perform monitoring. Viewing the displayed message
on the Java control panel, users find that the following error is reported:
java.lang.SecurityException: class "com.swimap.lmt.util.mml.MMLHandler"'s signer
information does not match signer information of other classes in the same package
at
java.lang.ClassLoader.checkCerts(ClassLoader.java:807) at
java.lang.ClassLoader.preDefineClass(ClassLoader.java:488) .......
Context
Java Runtime Environment (JRE for short) is a compulsory third-party component for the LMT
to run. Mixed code security verification is introduced in version 1.6.0_19 of JRE. With the
function, codes are verified. If codes are found to be untrustable, four operation options displayed
in Figure 12-17 are provided. Changing the default option as described below solves the previous
problem.
Issue 08 (2014-06-09)

337
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-17 Java control panel
Procedure
Step 1 Open Control Panel in the operating system and double-click JAVA. The Java Control
Panel dialog box is displayed.
Step 2 In the Advanced tab page, choose Security > Mixed code (sandboxed vs. trusted) security
verification and click Disable verification (not recommended).
Step 3 Click OK to save the new setting.
----End
12.13 Any Further Operation Performed When Some LMT

Web Pages Fail to Update Causes the Web Pages to Turn
Blank
Some LMT Web pages fail to update when batch processing, tracing, or monitoring is in use.
Any further operation causes the Web pages to turn blank. If you restart the function, the Web
Issue 08 (2014-06-09)

338
BSC6910 GSM
LMT User Guide
12 FAQ
page returns to normal. To prevent this problem, perform the following operations to add an
environment variable.
Procedure
Step 1 On the LMT PC, select My Computer and right-click Properties from the shortcut menu. The
System Properties dialog box is displayed.
Step 2 In the System Properties dialog box, click the Advanced tab and click Environment
Variables. The Environment Variables dialog box is displayed.
Step 3 In the Environment Variables dialog box, click New. The New User Variable dialog box is
displayed.
Step 4 In the New User Variable dialog box, set Variable name to
JPI_PLUGIN2_NO_HEARTBEAT and Variable value to 1. Then click OK.
Step 5 In the Environment Variables dialog box, click OK.
Step 6 In the System Properties dialog box, click OK to finish adding the environment variable.
----End
12.14 Configuring the HTTPS Login Mode

This section describes how to configure the HTTPS login mode and a security certificate. Users
can log in to the LMT through either HTTP or HTTPS. The login mode is configurable.
Prerequisites
l
You have logged in to the LMT using a Built-In Administrator Account or External
User Accounts.
Context
HTTPS is Hypertext Transfer Protocol Secure. Based on HTTP, HTTPS introduces SSL (or
TLS) to ensure transmission security. To put it simply, HTTPS is a combination of HTTP and
SSL. To enter the HTTPS login mode, enter https://Website to be visited + Port No in the Address
bar of the browser. The default port No. is 443. Use the default port No. to enter the LMT login
page.
Procedure
Step 1 Change the login mode
1.
Log in to the LMT through HTTPS.
2.
Run the MML command SET WEBLOGINPOLICY. In this step, set POLICY to
HTTPS.
Step 2 Run the MML command RST OMUMODULE to restart the LMT so that the change take effect.
In this step, set TG to ACTIVE and MNAME to weblmt.
Issue 08 (2014-06-09)

339
BSC6910 GSM
LMT User Guide
12 FAQ
NOTICE
1. Running this command disconnects all online users from the LMT.
2. Normally, the restart is complete within 5 seconds. After the restart is complete, the change
take effect when users log in to the LMT again.
----End
12.15 The Error "Certificate Invalid" Is Displayed During an

HTTPS Login
The LMT certificate and the certificate used to access the LMT through the M2000 proxy with
dual IP addresses are not granted by any commercial organization. Therefore, they are not trusted
by a browser such as IE by default. In such a scenario, the SSL certificate negotiation is
performed when you visit the LMT in HTTPS mode. If the organization for issuing the current
certificate is not in the default trust list of Microsoft, the Certificate Invalid error is displayed
on the browser. This error does not impair the LMT functions. This section describes how to
correct the error Certificate Invalid displayed during a login to the LMT through HTTPS. To
correct this error, add the root certificate of the certificate in use to the Trusted Root
Certification Authorities list.
Context
l
Using an IE browser
1.
After https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, is entered in the Address bar of the browser, a dialog box shown in
Figure 12-18 or Figure 12-19 is displayed.
Figure 12-18 Dialog box showing "There is a problem with this website's security
certificate" (IE7 or later versions)
Issue 08 (2014-06-09)

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

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

1.
Issue 08 (2014-06-09)
After https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, is entered in the Address bar of the browser, a dialog box shown in
Figure 12-20 is displayed. (The following figure uses Firefox3.0 as an example. The
dialog box varies with browser versions but has the same information.)

341
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-20 Dialog box showing "This Connection is Untrusted"
Connection Through the M2000

1.
After connecting through the M2000 with both IP addresses, an Certificate Invalid
dialog box is shown.
Procedure
Step 1 Using an IE browser
In the Certificate Invalid dialog box, click View certificates to view the current certificate. If
the certificate displays Issued to: MBSC Certificate and Issued by: Huawei Wireless
Network Product CA, as shown in Figure 12-21, perform the following steps:
Issue 08 (2014-06-09)

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

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

344
BSC6910 GSM
LMT User Guide
12 FAQ
"FAQ" in 12.16 The Error 'Mismatched Address' Is Displayed During an HTTPS

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

In the Certificate Invalid dialog box, click View certificates to view the current certificate. If
the certificate displays Issued to: server and Issued by: hwca, as shown in Figure 12-23,
Figure 12-23 Server Certificate
1.
Issue 08 (2014-06-09)
Click Install Certificate and Next. A dialog box shown in Figure 12-24 is displayed.

345
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-24 Certificate Import Wizard dialog box
2.
In the Certificate Import Wizard dialog box, select Place all certificates in the following
store and click Browse. In the displayed dialog box, select Trusted Root Certification
Authorities and click OK.
3.
In the Certificate Import Wizard dialog box, click Next, Finish, and OK.
4.
Restart the browser so that the reconfiguration can take effect.

In the Certificate Invalid dialog box, click View certificates. If the displayed information about
the current certificate is different from the information in the preceding conditions, import the
root certificate of the current certificate. Perform the following steps:
1.
Obtain the root certificate from the organization issuing the current certificate.
2.
In the menu of the IE browser, choose Tools > Internet Options > Content tab and click
Certificate on this tab page, the Certificate dialog box is displayed.
3.
In the Certificates > Personal tab, and click Import on this tab page, the Certificate
4.
In the displayed Certificate Import Wizard dialog box, click Next to import the certificate
file. Then click Next, choose Place all certificates in the following store, and then click
Browse. Choose Trusted Root Certification Authorities and click Next to import the
certificate file.
5.
Restart the browser to make the reconfiguration takes effect.
Step 4 Using a Firefox browser

1.
Issue 08 (2014-06-09)
Click Add Exception shown in Figure 12-20. The Add Security Exception dialog box is
displayed, as shown in Figure 12-25.
346
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-25 Add Security Exception dialog box
2.
Click Confirm Security Exception. After the website is added as a security exception, no
security error will be displayed during a login to the LMT using Firefox.
3.
Step 5 Connection Through the M2000

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

347
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-26 Certification Path of the M2000
1.
Choose General > Install Certificate in the Certificate dialog box. And Certificate
2.
Click Next in the Certificate Import Wizard dialog box and Certificate Store dialog box
is displayed. Then choose Place all Certificates in the following store.
3.
Click Browse, the Select Certificate Store dialog box is displayed. Then choose Trusted
Root Certification Authorities.
4.
Click OK, the Completing the Certificate Import Wizard dialog box is displayed.
5.
Click Finish, the Security Warning dialog box is displayed.
6.
Choose Yes in the Security Warning dialog box. The import was successful message is
displayed. Then Click OK.
Issue 08 (2014-06-09)

348
BSC6910 GSM
LMT User Guide
12 FAQ
7.
----End
12.16 The Error 'Mismatched Address' Is Displayed During

an HTTPS Login
A user uses an IP address rather than a domain name to access the LMT. Therefore, the
Mismatched Address error is displayed on the browser during an HTTPS login. This error does
not impair the LMT functions. This section describes how to correct the error "Mismatched
Address" displayed during a login to the LMT through HTTPS. To correct this error, deselect
the Warn about certificate address mismatch* option.
Context
1.
Enter https://the external virtual IP address of the OMU, for example, https://
10.141.115.219, in the Address bar of the browser. A dialog box shown in the Figure
12-27 or Figure 12-28is displayed.
Figure 12-27 Dialog box showing "There is a problem with this website's security
certificate"(IE7 or later versions)
Issue 08 (2014-06-09)

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

12-28 to enter the LMT login page. In the Address bar of the browser, an Certificate
Error message is shown.
3.
Click Certificate Error. An Mismatched Address error dialog box is shown.
Procedure
Step 1 Choose Tools > Internet Options on the Menu bar of the browser. Click the Advanced tab in
the displayed dialog box shown in Figure 12-29.
Issue 08 (2014-06-09)

350
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-29 Internet Options dialog box
Step 2 In the Internet Options dialog box, deselect Warn about certificate address mismatch* and
click OK.
NOTE
The reconfiguration takes effect after the browser is restarted.
----End
12.17 Tracing and Monitoring Functions Cannot Be Used

Tracing and monitoring functions cannot be used after a successful login to the LMT. Solve this
problem by using the following methods.
Context
An error message is displayed, as shown in Figure 12-30.
Issue 08 (2014-06-09)

351
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-30 Application Error
After clicking Details, detailed error information is displayed. You need to correct the error
based on the error type as follows:
l
If the "java.lang.ClassNotFoundException" error is displayed, perform steps 1 and 2.
If the "netscape.javascript.JSException" error is displayed, perform step 3.
If this problem occurs in Citrix Farm networking, you need to perform related steps on the
Citrix Farm server rather than on the local PC. If you have no permission to log in to the
Citrix Farm server, you cannot directly access Windows Control Panel on the Citrix Farm
server. To access it, right-click the Java icon on Windows system tray on the local PC and
choose Open Control Panel from the short-cut menu. The following figure shows the
window:
Issue 08 (2014-06-09)

352
BSC6910 GSM
LMT User Guide
12 FAQ
If this problem cannot be solved by performing the following steps, uninstall and reinstall
Java.
This problem is caused by a Java defect. For details about this defect, visit http://
bugs.sun.com/bugdatabase/view_bug.do?bug_id=6967414.
Procedure
Step 1 Enable the next-generation Java plug-in again.
1.
Open Control Panel in the Windows operating system and double-click Java. The Java
Control Panel dialog box is displayed. In the Java Control Panel dialog box, click the
Advanced tab, clear Enable the next-generation Java Plug-in (requires browser
restart) under Java Plug-in and click OK.
2.
Select Enable the next-generation Java Plug-in (requires browser restart) by referring
to step a and click OK. Figure 12-31 shows the window.
Issue 08 (2014-06-09)

353
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-31 Enabling the next-generation Java plug-in
3.
Restart the browser to enable the new setting to take effect.
Step 2 Delete temporary Java files.

1.
If this problem persists after performing step 1, delete temporary Java files.
2.
Open Control Panel in the Windows operating system and double-click Java. The Java
Control Panel dialog box is displayed.
3.
In the displayed Java Control Panel dialog box, click Setting. The Temporary Files
Settings dialog box is displayed. Check the amount of disk space set for storing temporary
files, as shown in Figure 12-32.
Issue 08 (2014-06-09)

354
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-32 Checking the amount of disk space set for storing temporary files
4.
Check the amount of disk space used for storing temporary Java files in the directory where
temporary Java files are saved. The part marked in red frame in Figure 12-33 shows the
directory. This amount is greater than the preset one.
Figure 12-33 Directory where temporary Java files are saved
Issue 08 (2014-06-09)

355
BSC6910 GSM
LMT User Guide
12 FAQ
5.
Delete folders in this directory manually or by clicking Delete Files shown in the figure
above.
NOTE
Before deleting folders in this directory, close all running LMT clients.
6.
Log in to the LMT again to check whether this problem is solved.
Step 3 Install Windows operating system patch KB960714.

1.
----End
12.18 No response when click the control component or

right-click during the tracing and monitoring processes
Some time after a successful login to the LMT, you may suddenly find that batch processing
fails with no error message. Alternatively, after a tracing or monitoring task is created, the task
page is not opened. There is no response or any error message. The NE task list shows that this
task has been successfully created. There is no response when you click saving files in the tracing
or monitoring interface. There is no detailed parsing information when you double-click a tracing
or monitoring message. There is no response when you right-click the window for displaying
tracing or monitoring results. There is no response when you right-click the window for
displaying tracing or monitoring results and choose Save All Messages and Save Selected
Messages from the shortcut menu. If you open a new browser and log in to the LMT again, the
task nevertheless can be successfully created. If either of the previous problems occurs, perform
the following operations:
Procedure
Step 1 Open Control Panel in the Windows operating system and double-click Java. The Java
Control Panel dialog box is displayed.
Step 2 In the displayed Java Control Panel dialog box, click the Advanced tab, choose SecurityMixed
code (sandboxed vs. trusted) security verification, and select Disable verification (not
recommended). Figure 12-34 shows the dialog box.
Issue 08 (2014-06-09)

356
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-34 Java Control Panel dialog box
Step 3 Close all browsers and log in to the LMT again.

----End
12.19 Interfaces for Performing Tracing or Monitoring Tasks

Blinking
Interfaces for performing tracing or monitoring tasks blink.
Context
Java Applet in the IE browser is incompatible with HTML elements when they are stacked
together. As a result, interfaces (stacked in the Java Applet) for performing tracing and
Issue 08 (2014-06-09)

357
BSC6910 GSM
LMT User Guide
12 FAQ
monitoring tasks blink. This problem does not affect the function but deteriorates user
experience.
Procedure
l
To avoid this problem, use the following methods:

1.
This problem occurs only on the IE browser. Use the Firefox browser to avoid this
problem.
2.
This problem occurs only on Java later than the version of 1.6.21. Visit
www.oracle.com and download Java SE Runtime Environment 6u21 or an earlier
version to avoid this problem.
----End
12.20 Unable to Save Tracking and Monitoring Data

When a tracking or monitoring task (such as the UE tracking task) is running on the LMT, it is
possible that the vast amounts of tracking or monitoring data cannot be saved even with sufficient
hard disk space. Solve the problem by using the method described in the procedure part.
Context
This problem arises when the operating system enables the system recovery function that
monitors changes of the files on the hard disk and consumes some hard disk space. With
insufficient hard disk space, the system displays "Insufficient hard disk space", and if a tracking
or monitoring task is running on the LMT, it is likely that the tracking or monitoring data cannot
be saved.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account authorized for the
administrator's operations. Right-click My computer and choose Properties.
Step 2 In the "System Properties" window, click System Recovery, select Disable System Recovery
on All Drivers, and click Submit, as shown in Figure 12-35.
Issue 08 (2014-06-09)

358
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-35 System properties dialog box
----End
12.21 The File Manager Functions Improperly

When the file manager functions improperly or cannot be used, perform the following
operations:
Procedure
l
If you use HTTPS to log in to the LMT, check that Do not save encrypted pages to
disk is cleared. Selecting this security option causes the file manager to be unavailable.
Therefore, clear this option as follows:
1.
Issue 08 (2014-06-09)
Open the Internet Options dialog box, click the Advanced tab, and clear Do not save
encrypted pages to disk. Figure 12-36 shows the dialog box.

359
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-36 Internet Options dialog box
Issue 08 (2014-06-09)
Check that temporary Java files are saved on the computer. If they are not, the file manager
functions improperly. Perform the following operations:
1.
Open Control Panel in the Windows operating system and double-click Java. The
Java Control Panel dialog box is displayed.
2.
In the displayed Java Control Panel dialog box, click Setting. The Temporary Files
Settings dialog box is displayed. Select Keep temporary files on my computer
shown in Figure 12-37.

360
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-37 Temporary Files Settings dialog box
Check whether the browser agency has been set. If yes, eliminate the setting.
Using IE browser
1.
Choose Tools > Internet Options. The Internet Options dialog box is displayed.
2.
In the displayed Internet Options dialog box, choose Connections > LAN
settings.
3.
In the displayed Local Area Network(LAN) Settings dialog box, deselect Use a
proxy server for your LAN(These settings will not apply to dial-up or VPN
connections) and Bypass proxy server for local addresses.
4.
Click OK. The setting is complete.
Using FireFox browser

1.
Choose Options > Advanced > Network > Settings. The Connection Settings dialog
box is displayed.
2.
In the displayed Connection Settings dialog box, select No proxy.
3.
Click OK. The setting is complete.
----End
12.22 BTS Nodes Cannot Be Displayed Under Device

Navigation Tree
After a successful login to the LMT, you may find that BTS nodes cannot be displayed under
Device Navigation Tree. After upgrading the browser, you find that the nodes can be displayed
normally. This problem occurs because data under Device Navigation Tree on the LMT is
Issue 08 (2014-06-09)

361
BSC6910 GSM
LMT User Guide
12 FAQ
compressed whereas Internet Explorer 6 SP2 does not support compression of chunked data.
Solve this problem by using either of the following methods.
Context
BTS nodes cannot be displayed under Device Navigation Tree, as shown in Figure 12-38.
Figure 12-38 BTS nodes cannot be displayed
Procedure
l
Method 1: For the operating system Windows XP Service Pack 2 or 3, install the KB982381
patch. To download this patch, visit http://www.microsoft.com/downloads.
Method 2: Upgrade the browser. You are advised to upgrade it to Internet Explorer 8.
----End
12.23 The Alarm/Event Function Becomes Unavailable

When starting or using the Alarm/Event function after a successful login to the LMT, the page
may become white with an exclamation mark displayed in the center. The exclamation mark is
circled in gray, as shown in the following figure: Solve this problem by using the following
methods.
Context
The page of alarm/event function become white, as shown in Figure 12-39.
Issue 08 (2014-06-09)

362
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-39 Alarm/Event Function
Procedure
l
Method 1: Check that the flash player is of a version supported by the LMT, Flash Player
10.1.82 or later. Flash Player 10.1.82 is available on the LMT login web page. For later
versions, visit http://adobe.com. If installing the flash player fails and a message saying
that the version is not the latest one is displayed, perform the following steps:
1.
Download and install the flash player of the latest version.
2.
Choose StartRun and enter regedit to open Registry Editor. Navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer
\SafeVersions, delete the item with the DWORD value of 10.0, and reinstall the flash
player.
Method 2: Check that the browser type is supported by the LMT, Internet Explorer or
Firefox. For details about the supported browser versions, see 2.1 Configuration
Requirements of the LMT PC.
----End
12.24 Incorrect Display of the Path for Downloading BTS

Software
After you log in to the LMT using Microsoft Internet Explorer (IE), enter the Download BTS
Software tab page, click Browse on the Download Files tab page, and select the BTS software
to be downloaded, you may find that the downloading path is displayed incorrectly. When this
occurs, check whether Include local directory path when uploading files to a sever is
prohibited.
Procedure
box is displayed.
Issue 08 (2014-06-09)

363
BSC6910 GSM
LMT User Guide
12 FAQ
Step 2 On the Security tab page, click Custom Level. The Security Setting - Local Intranet Zone
Step 3 In the Miscellaneous area, enable Include local directory path when uploading files to a
server, and click OK.
----End
12.25 The Message 'Class doesn't support Automation' Is

Displayed in an IE Browser
After clicking Login in an Internet Explorer (IE) browser, you find a blank window displayed
and login unable to continue. In the bottom left corner of the IE browser, a yellow error icon is
displayed. The icon says "Class doesn't support Automation". To solve the problem, perform
Context
l
This problem occurs because some registration components are missing from the IE
browser. To solve this problem, register the following components again:
msscript.ocx
dispex.dll
vbscript.dll
scrrun.dll
urlmon.dll
Procedure
Step 1 In Windows, choose StartRun and enter RegSvr32 msscript.ocx. To register the other
components again, replace the typed component in italics.
Step 2 After registering all the components again, clear the cache memory of the IE browser.
Step 3 Log in to the LMT again.
----End
12.26 Java Installation Fails

During Java installation, the message "Error 25099, Unzipping core files failed." is displayed.
To solve the problem, perform the following steps:
Procedure
Step 1 Delete all files in the Java installation path. The default installation path is C:\Program Files
\Java\jre6\.
Step 2 If step 1 fails because files are locked or in use, restart the system and repeat step 1.
Issue 08 (2014-06-09)

364
BSC6910 GSM
LMT User Guide
12 FAQ
Step 3 Reinstall Java.

----End
12.27 The LMT Login Web Page Cannot Be Opened with the
PC OMU Installed
With the PC OMU installed in Windows 7, the LMT login web page cannot be opened. In
addition, the LMT process cannot be found in the task manager.
Context
Port 80 is the default port for LMT login. This problem occurs because port 80 is occupied by
a default HTTP service in Windows 7.
To confirm the cause, run the netstat naop tcp command at the Windows 7 command prompt
to check whether port 80 is occupied. If it is occupied by a process with the PID of 4, as shown
in the following figure, the problem occurs due to the cause.
This process is a system process and therefore cannot be closed directly. To close it, perform
Procedure
Step 1 In Windows, choose StartRun and enter regedit to open Registry Editor.
Step 2 Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP.
Step 3 Change the DWORD value of Start to 0.
Step 4 Restart the PC and log in to the LMT again.
----End
12.28 Changing Settings for the Next-Generation Java Plugin Fails

When changing settings for Enable the next-generation Java Plug-in, you are prompted with
a message indicating that the changing fails because one or more browsers are running. As a
Issue 08 (2014-06-09)

365
BSC6910 GSM
LMT User Guide
12 FAQ
matter of fact, no browser is running. The following figure shows the message: To solve the
problem, perform the following steps.
Context
Changing Settings for Next-Generation Java Plug-in Fails, the error message is shown in
Figure 12-40.
Figure 12-40 Unable to change Java Plug-in settings
This problem is caused by a Java defect. The setting changing fails not because browsers are
running but because the user has no permission to perform the operation.
To change the settings, the user must belong to the Power Users group or have more rights.
Perform the following steps to grant the user more rights.
Procedure
Step 1 Log in to the operating system (OS) using an administrator-level account authorized for the
administrator's operations. Right-click My computer and choose Manage from the shortcut
menu.
Step 2 In the Computer Management window, choose System toolsLocal Users and
GroupsGroups and double-click Power Users in the right pane of the window, as shown in the
following figure:
Issue 08 (2014-06-09)

366
BSC6910 GSM
LMT User Guide
12 FAQ
Step 3 In the displayed window, click Add, add the user account to the Power Users group, and click
OK, as shown in the following figures:
Issue 08 (2014-06-09)

367
BSC6910 GSM
LMT User Guide
Issue 08 (2014-06-09)
12 FAQ

368
BSC6910 GSM
LMT User Guide
12 FAQ
Step 4 Use an administrator-level account to delete the Windows folder in C:\Documents and Settings
\User account\Local Settings\Application Data\Microsoft\Windows shown in the following
figure:
Step 5 Use the user account to log in the OS again after the previous steps are complete. The user
account now has permission to change settings for Enable the next-generation Java Plug-in.
NOTE
After changing the settings, you can restore the user rights. To restore the user rights, log in to OS using an
administrator-level account again and remove the user account from the Power Users group by referring to steps
1 through 3. The change of the user rights does not affect settings for Enable the next-generation Java Plugin.
----End
Issue 08 (2014-06-09)

369
BSC6910 GSM
LMT User Guide
12 FAQ
12.29 Error Message"This user session already exists" Upon

Login to LMT
The interface displays an error message "This user session already exists" upon login to LMT.
Solve the problem by using the method described in the procedure part.
Context
To enhance system security, the client browser uses Cookie to store the session information of
users who have successfully logged in. Due to the session Cookie mechanism, the user
encounters the following problems when using LMT:
l
Problem 1: For the same NE, the user desires to log in to multiple LMTs. After successfully
logging in to the first LMT, the user logs in to the second LMT of the NE, and the interface
displays "this user session already exists". This is because all browser windows opened by
the same user share the same session under the session sharing mechanism of IE8 or IE9
and Firefox enabled by default. As a result, when the user attempts to repeatedly log in to
the LMTs of the same NE, the system determines a repeated login of the same user session.
For the IE6/7 browser in which each browser window uses independent sessions, this
problem does not arise.
Problem 2: The LMT interface displays the error "this user session already exists", while
the user has not carried out the operation described in Problem 1. This is because the
previous session information remains valid due to an abnormal exit from LMT. As a result,
the LMT determines a repeated login attempt when the same user tries to login to the LMT.
This problem arises when the browser automatically recovers from breaking down during
use of the LMT, or when the pop-up LMT window is blocked by the browser pop-up blocker
enabled.
For Problem 1, the following method is used:
Procedure
1.
In the menu bar of the IE browser, click File > New Session, to start a new IE browser
window and log in to the LMT.
NOTE
This method applies only to the IE8 or IE9 browser, not Firefox. Users of the Firefox browser can
log in to only one LMT of a single NE.
For Problem 2, the following method is used:

1.
The IE6/7 browser user needs to close the browser window of the current LMT login
interface, and the IE8/9 and Firefox users need to close all opened browser windows
to invalidate the old sessions.
2.
If the pop-up blocker is enabled for the browser, disable it.
3.
Restart the browser and log in to LMT.
----End
Issue 08 (2014-06-09)

370
BSC6910 GSM
LMT User Guide
12 FAQ
12.30 The "Are You Sure You Want to Quit the Page" Dialog
Box Is Displayed
After successful login to the LMT in the IE8 or IE9 browser, the "are you sure you want to quit
the page?" dialog box is displayed when the alarm feature is enabled. Solve the problem by using
the method described in the procedure part.
Procedure
Step 1 Open the Internet Explorer, and then choose Tools > Internet Options from the menu bar. The
Internet Options dialog box is displayed. Click Advanced, and uncheck Automatic Recovery
from Page Layout Error.
Step 2 Restart the browser and log in to LMT again.
----End
12.31 Slow Response During an LMT Login

The LMT responses slowly when the users are trying to log in to the LMT. To solve the problem,
Procedure
Step 1 In the Windows 2003 and Windows XP operating system (OS), choose Start > Control
Panel, and then click Add/Remove Programs, the Windows Components Wizard dialog box
is displayed.
Step 2 In the Windows Components Wizard dialog box, deselect Upload Root Certificates, as shown
in the following figure. Then click Next to complete the modification.
Issue 08 (2014-06-09)

371
BSC6910 GSM
LMT User Guide
12 FAQ
----End
12.32 Unclear Grids in the Tables in the MML Online Help

The grids in the tables are not clear in MML online help when users log in to the LMT by some
computers. To solve the problem, perform the following steps.
Context
The grids in the tables are not clear in MML online help, as shown in Figure 12-41.
Issue 08 (2014-06-09)

372
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-41 Unclear Grids in the Tables in the MML Online Help
Procedure
Step 1 In the menu of the IE browser, choose Tools > Compatibility View Settings. In the displayed
Compatibility View Settings dialog box, select Display all websites in Compatibility View.
Step 2 Restart the browser and log in to the LMT to check the MML online help. The problem is solved.
----End
12.33 The "App Center" Web Page Is Automatically

Displayed When Firefox Is Used to Browse the LMT
When you use Firefox to browse the LMT, if you press F1 or click FTP Tool on the LMT web
page, the App Center web page is automatically displayed. In this case, disable the App
Center on the Add-ons Manager page.
Procedure
Step 1 On the Firefox browser, choose Tools > Add-ons. The Add-ons Manager page is displayed.
Step 2 On the Extensions tab page, locate App Center and click Disable. The App Center will
be disabled if you restart Firebox message is displayed.
Step 3 Click Restart now. The settings will take effect after the restart.
----End
Issue 08 (2014-06-09)

373
BSC6910 GSM
LMT User Guide
12 FAQ
12.34 "Permission Denied" or "Access Denied" is Displayed

When IE Is Used to Browse the LMT
When you log in to the LMT through IE, a Permission Denied or Access Denied message is
displayed.
Prerequisites
The LMT cannot be visited due to errors in IE. An error message is displayed in the status bar,
Figure 12-42 Error message in IE
Double-click the error message. A Permission Denied or Access Denied message is displayed.
Context
The causes are as follows:
l
The IE settings are modified when you log in to the LMT through IE, such as the settings
of the proxy. In this case, the access rights to the LMT page files are changed, leading to
access failures.
Automatic configuration in the Local Area Network (LAN) Settings dialog box is
enabled, as shown in Figure 2. If Automatic configuration is enabled, some uniform
resource locators (URLs) will be allocated to other security domains. Different security
domains have different restrictions on access rights. As a result, access failures occur.
Issue 08 (2014-06-09)

374
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-43 Automatic configuration enabled
Procedure
l
Method 1: Don't modify IE settings when you log in to the LMT through IE.
Method 2: Log out of the LMT when the Permission Denied or Access Denied message
is displayed. Restart IE and log in to the LMT again.
----End
12.35 MML Command Failed to Be Executed or No Response

to Tracing Tasks After the Browser Is Upgraded to IE8
After the browser is upgraded from IE6 to IE8, some cache files cannot be removed. As a result,
the system displays a Please check the MML macro configure file! message when an MML
command is executed, or there is no response after tracing tasks are created. To solve this
problem, you need to manually remove cache files and cookies.
Context
l
Issue 08 (2014-06-09)
When MML commands are executed, the system displays a Please check the MML macro
configure file! message, as shown in Figure 12-44.

375
BSC6910 GSM
LMT User Guide
12 FAQ
Figure 12-44 System message "Please check the MML macro configure file!"
There is no response after tracing tasks are created.
Procedure
Step 1 On the menu bar of the IE browser, choose Tool > Internet Options. The Internet Options
Step 2 Click General > Browsing history and click Delete. The Delete Browsing History dialog box
is displayed.
Step 3 In the Delete Browsing History dialog box, deselect the Preserve Favorites website data.
Step 4 Select Cookies and Temporary Internet files, and then click Delete and close the Delete
Browsing History dialog box.
Step 5 Click the General tab and click Setting in Browsing history. The Temporary Internet Files
and History Settings dialog box is displayed.
Step 6 Click View files in the Temporary Internet Files and History Settings dialog box, remove all
displayed files, and close the Internet Options dialog box.
----End
12.36 How to Handle Error Message Displayed on the LMT

The error message Problems with this Web page might prevent it from being displayed
properly or functioning properly. is displayed in the Internet Explorer during the logging in
of the LMT.
Context
If the Internet Explorer has insufficient buffer or is upgraded, the Internet Explorer cannot obtain
new files from a base station after the base station is upgraded. The Internet Explorer obtains
files about the base station in the original version from the buffer, which is inconsistent with the
information about the base station in the current version.
Procedure
l
Issue 08 (2014-06-09)
Internet Explorer Browser

376
BSC6910 GSM
LMT User Guide
12 FAQ
1.
Open the Internet Explorer, and choose Tools > Internet Options from the menu bar.
The Internet Options dialog box is displayed.
2.
On the General tab page, click Delete in the Browsing history area. The Delete
Browsing History dialog box is displayed.
3.
Clear the Preserve Favorites website data check box, select the Cookie and
Temporary Internet files check boxes, and click Delete.
4.
Close the Delete Browsing History dialog box.
5.
On the General tab page, click Settings in the Browsing history area. The
Temporary Internet Files and History Settings dialog box is displayed.
6.
Click View objects and delete all displayed files.
7.
Close the displayed window and the Internet Options dialog box.
Firefox Browser
1.
Open the Firefox browser, and choose Tools > Clear Private Data from the menu
bar.
2.
In the displayed Clear Private Data dialog box, select the Cache, Cookies, and
Offline Website Data check boxes, and click Clear Private Data Now.
----End
12.37 Tracing File Not Being Uploaded to the Specified

Directory
If you close the UE Trace or IOS Trace dialog box during the UE tracing or IOS tracing, the
tracing result file being generated cannot be uploaded to the specified directory. This problem
occurs in the following scenario: In the UE Trace or IOS Trace dialog box, Debug is selected
and Trace Mode is set to Report File. To solve the problem, perform the steps in Procedure.
Context
A tracing task may generate multiple tracing files, which depends on the traced messages.
If you close the trace dialog box, the last tracing file cannot be uploaded to the specified directory.
The last tracing file refers to the one being generated. The generated tracing files can be uploaded.
Procedure
Step 1 In the Trace Navigation Tree, double-click Manage Trace Task. The Manage Trace Task
tab page is displayed.
Step 2 Query the UE tracing or IOS tracing task being performed, select a task, and click Delete. The
preceding settings enable the tracing result file being generated to be uploaded to the specified
directory.
----End
Issue 08 (2014-06-09)

377
BSC6910 GSM
LMT User Guide
12 FAQ

After a successful login to the LMT, the previous settings, such as system settings, do not take
effect. To solve this problem, perform the following steps:
Procedure
l
Internet Explorer Browser

1.
Open the Internet Explorer, and choose Tools > Internet Options from the menu bar.
The Internet Options dialog box is displayed.
2.
On the General tab page, click Delete in the Browsing history area. The Delete
Browsing History dialog box is displayed.
3.
Clear the Preserve Favorites website data check box, select the Cookie and
Temporary Internet files check boxes, and click Delete.
4.
Close the Delete Browsing History dialog box.
5.
On the General tab page, click Settings in the Browsing history area. The
Temporary Internet Files and History Settings dialog box is displayed.
6.
Click View objects and delete all displayed files.
7.
Close the displayed window and the Internet Options dialog box.
Firefox Browser
1.
Open the Firefox browser, and choose Tools > Clear Private Data from the menu
bar.
2.
In the displayed Clear Private Data dialog box, select the Cache, Cookies, and
Offline Website Data check boxes, and click Clear Private Data Now.
----End
Issue 08 (2014-06-09)

378

Bsc6910 GSM LMT User Guide (v100r015c00 - 08) (PDF) - en

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Bsc6910 GSM LMT User Guide (v100r015c00 - 08) (PDF) - en

Diunggah oleh

Hak Cipta:

Format Tersedia

BSC6910 GSM

LMT User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

3 Management of Operation Rights

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

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

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

About This Document

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Huawei Proprietary and Confidential

About This Document

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

3 Management of Operation Rights............................................................................................35

Huawei Proprietary and Confidential

3.3.3 Changing the Password of the Active User Account................................................................................................42

4 Running MML Commands........................................................................................................45

Huawei Proprietary and Confidential

5.5 Monitoring Alarms.......................................................................................................................................................71

Huawei Proprietary and Confidential

7.3.5 Tracing Messages on the Inter-BSC Interface.........................................................................................................117

Huawei Proprietary and Confidential

8.4.4 Browsing Monitoring Results Offline.....................................................................................................................195

Huawei Proprietary and Confidential

10.6 Batch Configuration.................................................................................................................................................235

Huawei Proprietary and Confidential

11.15 Frequency Band Scan.............................................................................................................................................286

Huawei Proprietary and Confidential

12.17 Tracing and Monitoring Functions Cannot Be Used..............................................................................................351

Huawei Proprietary and Confidential

1 Changes in the BSC6910 GSM LMT User Guide

Changes in the BSC6910 GSM LMT User

Deleted the description about the Windows XP operating

Huawei Proprietary and Confidential

1 Changes in the BSC6910 GSM LMT User Guide

12.38 Settings on the LMT Failing to Take Effective

Tracing MTP2 Messages on the

Modified the description of the parameters Subrack

7.3.11 Tracing CS Domain