bsc6900 gsm lmt user guide(v900r011c00_07)

BSC6900 GSMV900R011C00

LMT User Guide

Issue 07

Date 2011-01-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 07 (2011-01-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

OverviewThis document describes the functions and relevant components of the BSC6900 LocalMaintenance Terminal (LMT). It also provides instructions for performing basic operation andmaintenance (OM) tasks of theBSC6900.

Product VersionThe following table lists the product version related to this document.

Product Name Product Version

BSC6900 V900R011C00

Intended AudienceThis document is intended for:

l Network engineersl System engineersl Field engineers

Organization1 Changes in the BSC6900 GSM LMT User Guide

This chapter describes the changes made in theBSC6900 GSM LMT User Guide.

2 Introduction to LMT

The Local Maintenance Terminal (LMT) is a web-based application that provides a graphicaluser interface (GUI) for users for easy operation and maintenance of the BSC6900. Users canperform operations such as alarm management, trace management, performance monitoring,and device maintenance. Users can also run MML commands and read the correspondingexecution results on the LMT.

BSC6900 GSMLMT User Guide About This Document


iii

3 Management of Operation Rights

This chapter describes the management of operation rights, and provides instruction to manageuser accounts and command groups.

4 Running MML Commands

This chapter describes how to run MML commands on the LMT to operate and maintain theBSC6900.

5 Alarm Management

This describes how to manage BSC6900 alarms through the LMT. Alarm management allowsyou to analyze alarms more efficiently and facilitates troubleshooting.

6 Log Management

This chapter describes how to manage the BSC6900 logs through the LMT. Log files can besaved in .txt and .log formats. Only the admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can manage the logs.

7 Trace Management

This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 tracetasks can be performed simultaneously on the same LMT.

8 Performance Monitoring

This chapter describes how to monitor the BSC6900 performance. A maximum of 64 monitoringtasks can be performed simultaneously on the same LMT.

9 Device Panel

This chapter describes how to manage the BSC6900 equipment by using the device andemulation panels. You can use these panels to query for information about the boards, boardports, 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, andboards.

12 FAQ

This chapter describes the frequently asked questions (FAQs) and the corresponding solutions.

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

About This DocumentBSC6900 GSM

LMT User Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

BSC6900 GSMLMT User Guide About This Document


v


{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical 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.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare 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 meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.

About This DocumentBSC6900 GSM

LMT User Guide

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

Contents

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

1 Changes in the BSC6900 GSM LMT User Guide.................................................................1-1

2 Introduction to LMT..................................................................................................................2-12.1 Configuration Requirements of the LMT PC..................................................................................................2-22.2 LMT Login and Exit.......................................................................................................................................2-42.3 Components of the LMT Window..................................................................................................................2-62.4 LMT Software.................................................................................................................................................2-9

2.4.1 Installing LMT Offline Tools...............................................................................................................2-102.4.2 FTP Client............................................................................................................................................2-112.4.3 FTP Server............................................................................................................................................2-132.4.4 LMT Offline MML..............................................................................................................................2-142.4.5 Convert Management System..............................................................................................................2-182.4.6 Performance Browser Tool..................................................................................................................2-192.4.7 Traffic Recording Review Tool...........................................................................................................2-20

2.5 File Manager.................................................................................................................................................2-21

3 Management of Operation Rights..........................................................................................3-13.1 Concepts Related to Operation Rights Management......................................................................................3-2

3.1.1 Principles of Operation Rights Management.........................................................................................3-23.1.2 User Password........................................................................................................................................3-23.1.3 Command Group....................................................................................................................................3-33.1.4 User Type...............................................................................................................................................3-43.1.5 Operation Rights....................................................................................................................................3-43.1.6 Operation Time Limit.............................................................................................................................3-5

3.2 Management of User Accounts.......................................................................................................................3-63.2.1 Creating an External User Account........................................................................................................3-63.2.2 Modifying an External User Account....................................................................................................3-73.2.3 Deleting an External User Account........................................................................................................3-7

3.3 Management of User Passwords.....................................................................................................................3-83.3.1 Defining Login Password Policies.........................................................................................................3-83.3.2 Querying Login Password Policies........................................................................................................3-83.3.3 Changing the Password of the Active User Account.............................................................................3-93.3.4 Changing the Password of an External User Account...........................................................................3-9

BSC6900 GSMLMT User Guide Contents


vii

3.4 Management of Command Groups...............................................................................................................3-103.4.1 Querying a Command Group...............................................................................................................3-103.4.2 Setting the Command Group Name.....................................................................................................3-103.4.3 Changing the Commands in a Command Group.................................................................................3-10

4 Running MML Commands......................................................................................................4-14.1 Concepts Related to MML Commands...........................................................................................................4-3

4.1.1 Introduction to MML Commands..........................................................................................................4-34.1.2 Components of the MML Command Window......................................................................................4-54.1.3 Data Configuration Rights.....................................................................................................................4-64.1.4 Data Configuration Rollback.................................................................................................................4-6

4.2 Running an MML Command..........................................................................................................................4-74.3 Batch Processing MML Commands...............................................................................................................4-8

4.3.1 Immediate Batch Processing of MML Commands................................................................................4-94.3.2 Scheduled Batch Processing of MML Commands................................................................................4-94.3.3 Batch Processing Assistant...................................................................................................................4-11

4.4 Setting MML Parameters..............................................................................................................................4-134.5 Querying the Data Configuration Mode........................................................................................................4-134.6 Querying Data Configuration Rights............................................................................................................4-144.7 Obtaining Data Configuration Rights...........................................................................................................4-154.8 Undoing/Redoing a Data Configuration Action............................................................................................4-164.9 Undoing/Redoing Multiple Data Configuration Actions..............................................................................4-17

5 Alarm Management...................................................................................................................5-15.1 Concepts Related to Alarm Management........................................................................................................5-2

5.1.1 Alarm Type............................................................................................................................................5-25.1.2 Alarm Severity.......................................................................................................................................5-35.1.3 Alarm-Managed Objects........................................................................................................................5-35.1.4 Alarm Box..............................................................................................................................................5-4

5.2 Managing Alarm Logs....................................................................................................................................5-55.2.1 Setting Storage Conditions of Alarm Logs............................................................................................5-55.2.2 Querying Storage Conditions of Alarm Logs........................................................................................5-5

5.3 Managing the Alarm Filter..............................................................................................................................5-55.3.1 Creating an Alarm Filter........................................................................................................................5-65.3.2 Deleting an Alarm Filter........................................................................................................................5-65.3.3 Querying an Alarm Filter.......................................................................................................................5-7

5.4 Managing the Filter of Derived Alarms..........................................................................................................5-75.4.1 Setting the Filter of Derived Alarms......................................................................................................5-75.4.2 Querying the Filter of Derived Alarms..................................................................................................5-8

5.5 Monitoring Alarms..........................................................................................................................................5-85.5.1 Browsing Alarms....................................................................................................................................5-95.5.2 Querying the Alarm Log........................................................................................................................5-95.5.3 Querying Alarm Handling Suggestions...............................................................................................5-105.5.4 Querying Alarm Configuration............................................................................................................5-10

ContentsBSC6900 GSM

LMT User Guide

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

5.5.5 Filtering Fault Alarms..........................................................................................................................5-115.5.6 Setting Alarm Attributes......................................................................................................................5-125.5.7 Manually Clearing an Alarm................................................................................................................5-125.5.8 Removing Alarms................................................................................................................................5-125.5.9 Refreshing the Alarm Window............................................................................................................5-13

5.6 Managing the Alarm Box..............................................................................................................................5-135.6.1 Querying Alarm Box Information........................................................................................................5-145.6.2 Querying Number of Alarms with Different Severities.......................................................................5-145.6.3 Operating the Alarm Box.....................................................................................................................5-145.6.4 Querying the Alarm Box Filter Level..................................................................................................5-15

6 Log Management........................................................................................................................6-16.1 Log Types........................................................................................................................................................6-36.2 Querying Log Storage Conditions...................................................................................................................6-36.3 Setting Log Storage Conditions...................................................................................................................... 6-36.4 Querying Operation Logs................................................................................................................................6-46.5 Exporting Operation Logs...............................................................................................................................6-46.6 Querying Security Logs.................................................................................................................................. 6-56.7 Exporting Security Logs..................................................................................................................................6-56.8 Exporting Running Logs.................................................................................................................................6-66.9 Collecting Log Statistics................................................................................................................................. 6-7

7 Trace Management.....................................................................................................................7-17.1 Concepts Related to Trace Management.........................................................................................................7-2

7.1.1 Trace Principles......................................................................................................................................7-27.1.2 Management of Tracing Operation Rights.............................................................................................7-37.1.3 Trace Mode............................................................................................................................................ 7-3

7.2 GSM Services..................................................................................................................................................7-47.2.1 Tracing Messages on the A Interface.....................................................................................................7-57.2.2 Tracing CS Domain Messages on the Um Interface............................................................................7-177.2.3 Tracing PS Domain Messages on the Um Interface.............................................................................7-197.2.4 Tracing Messages on the Cb Interface.................................................................................................7-217.2.5 Tracing Group Call Messages..............................................................................................................7-227.2.6 Tracing Messages on the Inter-BSC Interface.....................................................................................7-247.2.7 Tracing CS Domain Messages on the Abis Interface...........................................................................7-257.2.8 Tracing PS Domain Messages on the Abis Interface...........................................................................7-347.2.9 Tracing PTP Messages on the Gb Interface.........................................................................................7-367.2.10 Tracing SIG Messages on the Gb Interface........................................................................................7-387.2.11 Tracing CS Domain Messages of a Single Subscriber.......................................................................7-407.2.12 Tracing PS Domain Messages of a Single Subscriber.......................................................................7-427.2.13 Tracing CS Domain Messages on the Ater Interface.........................................................................7-447.2.14 Tracing Messages on the Pb Interface................................................................................................7-467.2.15 Tracing BTS Signaling Messages......................................................................................................7-507.2.16 Tracing Messages on the LB Interface...............................................................................................7-54



ix

7.3 Basic Tracing Operations..............................................................................................................................7-627.3.1 Browsing Traced Messages Online......................................................................................................7-627.3.2 Viewing the Interpretation of the Trace Message................................................................................7-637.3.3 Saving Traced Messages......................................................................................................................7-637.3.4 Browsing Traced Messages Offline.....................................................................................................7-647.3.5 Managing Tracing Tasks......................................................................................................................7-657.3.6 Managing the Trace File......................................................................................................................7-66

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

8.1.1 Monitoring Principles.............................................................................................................................8-28.1.2 Management of Monitoring Operation Rights.......................................................................................8-3

8.2 Common Monitoring.......................................................................................................................................8-48.2.1 Monitoring CPU/DSP Usage.................................................................................................................8-48.2.2 Monitoring Transmission Resources......................................................................................................8-58.2.3 Monitoring BER Seconds.......................................................................................................................8-58.2.4 Monitoring Link Performance................................................................................................................8-6

8.3 GSM Monitoring...........................................................................................................................................8-118.3.1 Monitoring Traffic on GPRS User Plane.............................................................................................8-118.3.2 Monitoring Abis HDLC Utilization.....................................................................................................8-128.3.3 Monitoring Cell Performance...............................................................................................................8-128.3.4 Monitoring DSP Resources..................................................................................................................8-138.3.5 Monitoring BTS IP Link Performance.................................................................................................8-13

8.4 General Operations of Performance Monitoring...........................................................................................8-148.4.1 Browsing the Monitoring Results Online.............................................................................................8-148.4.2 Setting the Display Mode of the Chart.................................................................................................8-158.4.3 Saving Monitoring Results...................................................................................................................8-158.4.4 Browsing Monitoring Results Offline..................................................................................................8-16

8.5 Reference for Performance Monitoring........................................................................................................8-16

9 Device Panel................................................................................................................................9-19.1 Device Panel Operations.................................................................................................................................9-2

9.1.1 Introduction to the Device Panel............................................................................................................9-29.1.2 Starting the Device Panel.......................................................................................................................9-39.1.3 Querying the Status of an E1/T1 Port....................................................................................................9-49.1.4 Querying the CPU Usage.......................................................................................................................9-49.1.5 Querying the BSC Board Information...................................................................................................9-49.1.6 Resetting the BSC Board........................................................................................................................9-59.1.7 Switching Over the BSC Boards............................................................................................................9-69.1.8 Querying the Status and Frequency of the Cavity Combiner ................................................................9-79.1.9 Querying the BTS Board Information....................................................................................................9-79.1.10 Resetting the BTS Board......................................................................................................................9-89.1.11 Maintaining BTS Clock.......................................................................................................................9-89.1.12 Switching Over the BTS Boards..........................................................................................................9-9

ContentsBSC6900 GSM

LMT User Guide

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

9.2 Emulation Panel Operations..........................................................................................................................9-109.2.1 Introduction to the Emulation Panel.....................................................................................................9-119.2.2 Starting the Emulation Panel................................................................................................................9-119.2.3 Querying the Status of an E1/T1 Port..................................................................................................9-129.2.4 Querying the CPU Usage.....................................................................................................................9-139.2.5 Querying the BSC Board Information.................................................................................................9-139.2.6 Resetting the BSC Board......................................................................................................................9-149.2.7 Switching Over the BSC Boards..........................................................................................................9-159.2.8 Querying the Status of an FE Port........................................................................................................9-159.2.9 Querying the Status of a GE Port.........................................................................................................9-169.2.10 Querying the Status of an Optical Port...............................................................................................9-169.2.11 Querying the DSP Status of a DPU....................................................................................................9-179.2.12 Querying Alarm LED Information.....................................................................................................9-17

10 BSC Maintenance...................................................................................................................10-110.1 Concepts Related to BSC Maintenance......................................................................................................10-2

10.1.1 BSC Interface Processing Subsystem................................................................................................10-210.1.2 Loopback............................................................................................................................................10-4

10.2 Browsing Configuration Data.....................................................................................................................10-910.3 Backing Up Data.......................................................................................................................................10-1010.4 Restoring Data...........................................................................................................................................10-1110.5 Maintaining the Equipment.......................................................................................................................10-12

10.5.1 Querying the BSC Board Information.............................................................................................10-1210.5.2 Querying BSC Board Clock Status..................................................................................................10-1310.5.3 Switching Over the BSC Boards......................................................................................................10-1410.5.4 Resetting the BSC Board..................................................................................................................10-1610.5.5 Maintaining Fan Box........................................................................................................................10-1710.5.6 Maintaining the Power Distribution Box.........................................................................................10-19

10.6 Maintaining Transmission and Signaling..................................................................................................10-2010.6.1 Maintaining LAPD Links.................................................................................................................10-2110.6.2 Querying Ater Link Status...............................................................................................................10-2310.6.3 Maintaining SCCP Links.................................................................................................................10-2410.6.4 Maintaining MTP3 Links.................................................................................................................10-2610.6.5 Querying the Status of MTP2 Links................................................................................................10-2810.6.6 Querying MTP2 Link Statistical Information..................................................................................10-2910.6.7 Querying the Electrical Interface Board Port Information...............................................................10-3010.6.8 Querying the Optical Interface Board Port Information..................................................................10-3110.6.9 Looping Back the Interface Board Port............................................................................................10-3310.6.10 Looping Back the Interface Board Port Timeslot..........................................................................10-3410.6.11 Maintaining IP Links......................................................................................................................10-36

10.7 Maintaining BSC User Resources.............................................................................................................10-3710.7.1 Analyzing Voice Logs......................................................................................................................10-3810.7.2 Querying the Status of the Abis Interface Timeslot.........................................................................10-38



xi

10.7.3 Maintaining Ater Interface Resources..............................................................................................10-4010.7.4 Maintaining the Circuits on the A Interface.....................................................................................10-4210.7.5 Querying DSP Resources.................................................................................................................10-4410.7.6 Maintaining DSP Resources.............................................................................................................10-4610.7.7 Querying Single User Resources......................................................................................................10-4710.7.8 Collecting BSC Local Information..................................................................................................10-4810.7.9 Looping Back Remote Speech Channel...........................................................................................10-4910.7.10 Testing the Internal Speech Channel..............................................................................................10-5110.7.11 Looping Back DSP Channel/Link..................................................................................................10-52

10.8 Querying Board Version Information.......................................................................................................10-55

11 BTS Maintenance...................................................................................................................11-111.1 Concepts Related to BTS Maintenance.......................................................................................................11-3

11.1.1 BTS Attributes....................................................................................................................................11-311.1.2 Cell Forced Handover Mode..............................................................................................................11-7

11.2 Query Running Software Version of a Board.............................................................................................11-811.3 Downloading the BTS Software.................................................................................................................11-911.4 Loading the BTS Software........................................................................................................................11-1011.5 Activating BTS Software..........................................................................................................................11-1011.6 Querying BTS Running Status..................................................................................................................11-1111.7 Querying BTS Board Matching Result.....................................................................................................11-1211.8 Querying BTS Attributes..........................................................................................................................11-1311.9 Resetting the BTS by Levels.....................................................................................................................11-1411.10 Browsing BTS Initialization Process Message.......................................................................................11-1611.11 Modifying Administrative State..............................................................................................................11-1711.12 Forced Handover.....................................................................................................................................11-1911.13 Monitoring Channel Status......................................................................................................................11-2011.14 Monitoring Interference Band of Channel..............................................................................................11-2211.15 Maintaining Site......................................................................................................................................11-22

11.15.1 Browsing the BTS Log...................................................................................................................11-2311.15.2 Testing Transmission Performance................................................................................................11-2411.15.3 Querying BTS Transmission State.................................................................................................11-25

11.16 Maintaining the Cell................................................................................................................................11-2611.16.1 Querying Frequency Scan Parameters...........................................................................................11-2611.16.2 Configuring Frequency Scan..........................................................................................................11-27

11.17 Maintaining TRXs...................................................................................................................................11-2811.17.1 Querying the TRX Power Mode....................................................................................................11-2911.17.2 Querying Automatic Power Correction Type................................................................................11-3011.17.3 Testing TRX Loopback..................................................................................................................11-3211.17.4 Testing Channel Loopback.............................................................................................................11-3211.17.5 Testing Idle Timeslots....................................................................................................................11-3411.17.6 Resetting the TRX..........................................................................................................................11-3511.17.7 Querying TRX Timeslot.................................................................................................................11-36

ContentsBSC6900 GSM

LMT User Guide

xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

11.18 Reference for BTS Maintenance.............................................................................................................11-37

12 FAQ...........................................................................................................................................12-112.1 Browser Cache expires................................................................................................................................12-312.2 The LMT gives slow responses to user operations in the Firefox browser.................................................12-412.3 The color of the LMT is not correctly displayed.........................................................................................12-412.4 The verify code cannot be displayed on the LMT login page.....................................................................12-512.5 Installing OS Patches..................................................................................................................................12-512.6 Clicking the menu bar on the LMT has no response...................................................................................12-612.7 Changing the Computer Time During the LMT Use Prohibited................................................................12-712.8 Corrupt Characters Occurring When Opening the csv File in UTF-8 Coding............................................12-712.9 Methods for Setting the Explorer Under Citrix Farm Networking...........................................................12-1012.10 Unable to Log In To LMT Because IE Default Security Level Is Too High..........................................12-1512.11 Unable to Log In To LMT and Class can't Stand Automation Operation is Displayed..........................12-2112.12 LMT Failing to Load the Progress Interface After a Successful Login..................................................12-2212.13 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE......12-23



xiii

Figures

Figure 2-1 LMT window......................................................................................................................................2-7Figure 2-2 FTP client interface..........................................................................................................................2-12Figure 2-3 FTP server interface..........................................................................................................................2-13Figure 2-4 LMT Offline MML Server Interface................................................................................................2-14Figure 2-5 LMT offline MML interface.............................................................................................................2-16Figure 2-6 Interface of the Convert Management System.................................................................................2-18Figure 2-7 Interface of performance browser tool.............................................................................................2-19Figure 2-8 Interface of the Traffic Recording Review Tool .............................................................................2-21Figure 2-9 File manager interface......................................................................................................................2-22Figure 4-1 MML command window....................................................................................................................4-5Figure 4-2 Setting MML Parameters..................................................................................................................4-13Figure 4-3 Subrack data configuration mode.....................................................................................................4-14Figure 4-4 All users enabled with the data configuration rights........................................................................4-15Figure 4-5 Data configuration rights granted to the admin user........................................................................4-16Figure 5-1 Alarm box...........................................................................................................................................5-4Figure 7-1 Principles of the message tracing.......................................................................................................7-2Figure 7-2 Message tracing on the A interface....................................................................................................7-6Figure 7-3 Results of BSSAP message tracing on the A interface.......................................................................7-7Figure 7-4 Message tracing on the A interface....................................................................................................7-8Figure 7-5 Results of SCTP message tracing on the A interface.........................................................................7-9Figure 7-6 Message tracing on the A interface..................................................................................................7-10Figure 7-7 Results of MTP3 message tracing on the A interface.......................................................................7-11Figure 7-8 Message tracing on the A interface..................................................................................................7-12Figure 7-9 Results of MTP2 message tracing on the A interface.......................................................................7-13Figure 7-10 Message tracing on the A interface................................................................................................7-14Figure 7-11 Results of SCTP message tracing on the A interface.....................................................................7-15Figure 7-12 Message tracing on the A interface................................................................................................7-16Figure 7-13 Results of M3UA message tracing on the A interface...................................................................7-17Figure 7-14 CS domain message tracing on the Um interface...........................................................................7-18Figure 7-15 Results of CS domain message tracing on the Um interface..........................................................7-19Figure 7-16 PS domain message tracing on the Um interface...........................................................................7-20Figure 7-17 Results of PS domain message tracing on the Um interface..........................................................7-21Figure 7-18 Message tracing on the Cb interface...............................................................................................7-22

BSC6900 GSMLMT User Guide Figures


xv

Figure 7-19 Group call message tracing.............................................................................................................7-23Figure 7-20 Message tracing on the inter-BSC interface...................................................................................7-24Figure 7-21 CS domain message tracing on the Abis interface......................................................................... 7-26Figure 7-22 Results of RSL message tracing on the Abis interface...................................................................7-27Figure 7-23 CS domain message tracing on the Abis interface......................................................................... 7-28Figure 7-24 Results of ESL message tracing on the Abis interface...................................................................7-28Figure 7-25 CS domain message tracing on the Abis interface......................................................................... 7-29Figure 7-26 Results of EML message tracing on the Abis interface..................................................................7-30Figure 7-27 CS domain message tracing on the Abis interface......................................................................... 7-31Figure 7-28 Results of OML message tracing on the Abis interface.................................................................7-32Figure 7-29 CS domain message tracing on the Abis interface......................................................................... 7-33Figure 7-30 Results of LAPD message tracing on the Abis interface................................................................7-34Figure 7-31 PS domain message tracing on the Abis interface..........................................................................7-35Figure 7-32 Results of PS domain message tracing on the Abis interface.........................................................7-36Figure 7-33 PTP message tracing on the Gb interface.......................................................................................7-37Figure 7-34 Results of PTP message tracing on the Gb interface......................................................................7-38Figure 7-35 SIG message tracing on the Gb interface....................................................................................... 7-39Figure 7-36 Results of SIG message tracing on the Gb interface...................................................................... 7-39Figure 7-37 CS domain message tracing of a single subscriber.........................................................................7-40Figure 7-38 Results of CS domain message tracing of a single subscriber........................................................7-41Figure 7-39 PS domain message tracing of a single subscriber.........................................................................7-43Figure 7-40 Results of PS domain message tracing of a single subscriber........................................................7-44Figure 7-41 CS domain message tracing on the Ater interface..........................................................................7-45Figure 7-42 Results of CS domain message tracing on the Ater interface.........................................................7-45Figure 7-43 Message tracing on the Pb interface...............................................................................................7-47Figure 7-44 Results of Application domain message tracing on the Pb interface .............................................7-48Figure 7-45 Message tracing on the Pb interface...............................................................................................7-49Figure 7-46 Results of LAPD domain message tracing on the Pb interface .....................................................7-50Figure 7-47 BTS signaling trace........................................................................................................................ 7-51Figure 7-48 Results of LAPDm message tracing through BTS signaling trace.................................................7-52Figure 7-49 BTS signaling trace........................................................................................................................ 7-53Figure 7-50 Results of RLC/MAC message tracing through BTS signaling trace............................................7-54Figure 7-51 Message tracing on the LB interface..............................................................................................7-55Figure 7-52 Message tracing on the LB interface..............................................................................................7-56Figure 7-53 Message tracing on the LB interface..............................................................................................7-58Figure 7-54 Message tracing on the LB interface..............................................................................................7-59Figure 7-55 Message tracing on the LB interface..............................................................................................7-61Figure 8-1 CPU usage monitoring........................................................................................................................8-2Figure 8-2 Real-time performance monitoring.....................................................................................................8-3Figure 9-1 Device Panel.......................................................................................................................................9-3Figure 9-2 Emulation panel................................................................................................................................9-11Figure 9-3 Subrack peripheral............................................................................................................................9-12

FiguresBSC6900 GSM

LMT User Guide

xvi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

Figure 10-1 Interfaces between the BSC and other NEs....................................................................................10-2Figure 10-2 Timeslot loopback..........................................................................................................................10-5Figure 10-3 Port loopback..................................................................................................................................10-6Figure 10-4 Remote speech channel loopback in the MSC direction................................................................10-8Figure 10-5 Remote speech channel loopback in the BTS direction.................................................................10-8Figure 10-6 A interface loopback.......................................................................................................................10-9Figure 10-7 Abis interface loopback..................................................................................................................10-9Figure 10-8 Querying results of board status...................................................................................................10-13Figure 10-9 Querying results of BSC Board Clock Status...............................................................................10-14Figure 10-10 Switching over a BSC board......................................................................................................10-16Figure 10-11 Resetting the BSC Board............................................................................................................10-17Figure 10-12 Querying the fan box..................................................................................................................10-18Figure 10-13 Maintaining the Power Distribution Box....................................................................................10-20Figure 10-14 Internal transmission on interface boards...................................................................................10-22Figure 10-15 Results of querying LAPD link status........................................................................................10-23Figure 10-16 Querying Ater Link Status..........................................................................................................10-24Figure 10-17 Maintaining SCCP Links............................................................................................................10-25Figure 10-18 Querying MTP3 Links................................................................................................................10-27Figure 10-19 Maintaining MTP3 Links...........................................................................................................10-28Figure 10-20 Querying the Status of MTP2 Links...........................................................................................10-29Figure 10-21 Querying MTP2 Link Statistical Information............................................................................10-30Figure 10-22 Querying the Electrical Interface Board Port Information.........................................................10-31Figure 10-23 Querying the Optical Interface Board Port Information.............................................................10-32Figure 10-24 Looping Back the Interface Board Port......................................................................................10-33Figure 10-25 Looping Back the Interface Board Port Timeslot.......................................................................10-35Figure 10-26 Maintaining IP Links..................................................................................................................10-36Figure 10-27 Querying the Status of the Abis Interface Timeslot...................................................................10-39Figure 10-28 Results of querying timeslot status on the Ater interface ..........................................................10-41Figure 10-29 Results of querying Ater resources.............................................................................................10-42Figure 10-30 Querying the Circuits on the A Interface....................................................................................10-43Figure 10-31 Results of querying DSP resources............................................................................................10-45Figure 10-32 Results of querying the DSP channel/link status........................................................................10-46Figure 10-33 Maintaining DSP Resources Iterface..........................................................................................10-47Figure 10-34 Remote speech channel loopback...............................................................................................10-50Figure 10-35 DSP channel/link loopback over the A interface .......................................................................10-53Figure 10-36 DSP channel/link loopback over the Abis interface ..................................................................10-54Figure 10-37 Results of querying the status of DSP channel/link loopback....................................................10-54Figure 11-1 Results of querying the running software version of a board.........................................................11-8Figure 11-2 Querying BTS Running Status.....................................................................................................11-12Figure 11-3 Querying BTS Board Matching Result........................................................................................11-13Figure 11-4 Querying BTS Attributes .............................................................................................................11-14Figure 11-5 Resetting the BTS by Levels........................................................................................................11-16

BSC6900 GSMLMT User Guide Figures


xvii

Figure 11-6 Browsing BTS Initialization Process Message.............................................................................11-17Figure 11-7 Modifying Administrative State...................................................................................................11-18Figure 11-8 Forced Handover..........................................................................................................................11-20Figure 11-9 Monitoring Channel Status...........................................................................................................11-21Figure 11-10 Monitoring Interference Band of Channel..................................................................................11-22Figure 11-11 Browsing the BTS Log...............................................................................................................11-23Figure 11-12 Testing Transmission Performance............................................................................................11-24Figure 11-13 Querying BTS Transmission State.............................................................................................11-26Figure 11-14 Querying Frequency Scan Parameters........................................................................................11-27Figure 11-15 Configuring Frequency Scan......................................................................................................11-28Figure 11-16 Querying the TRX Power Mode.................................................................................................11-30Figure 11-17 Querying Automatic Power Correction Type.............................................................................11-31Figure 11-18 Testing Idle Timeslots................................................................................................................11-35Figure 11-19 Resetting the TRX......................................................................................................................11-36Figure 11-20 Results of querying TRX timeslots............................................................................................11-37Figure 12-1 Operation interface for importing data in Excel.............................................................................12-8Figure 12-2 Text import wizard—step 1............................................................................................................12-8Figure 12-3 Text import wizard—step 2............................................................................................................12-9Figure 12-4 Interface after data importation is finished.....................................................................................12-9Figure 12-5 Active Directory Users and Computers........................................................................................12-11Figure 12-6 hong01 Properties 1......................................................................................................................12-12Figure 12-7 hong01 Properties 2......................................................................................................................12-13Figure 12-8 HTTP 1.1 settings.........................................................................................................................12-14Figure 12-9 Script.............................................................................................................................................12-16Figure 12-10 Logon..........................................................................................................................................12-17Figure 12-11 Adding a script............................................................................................................................12-17Figure 12-12 Script...........................................................................................................................................12-18Figure 12-13 Logon..........................................................................................................................................12-19Figure 12-14 Adding a script............................................................................................................................12-19Figure 12-15 Windows components wizard.....................................................................................................12-20Figure 12-16 Internet Explorer Enhanced Security Configuration..................................................................12-21Figure 12-17 Java control panel.......................................................................................................................12-24

FiguresBSC6900 GSM

LMT User Guide

xviii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

Tables

Table 2-1 Hardware requirements of the LMT PC...............................................................................................2-2Table 2-2 Software requirements of the LMT PC................................................................................................2-2Table 2-3 Effective bandwidth requirements of the LMT PC..............................................................................2-3Table 2-4 Components of the LMT window........................................................................................................2-7Table 2-5 Description of LMT online help..........................................................................................................2-9Table 2-6 Components of FTP client interface.................................................................................................. 2-12Table 2-7 Components of FTP server interface..................................................................................................2-14Table 2-8 Description of the LMT offline MML server.................................................................................... 2-15Table 2-9 Description of the LMT offline MML interface................................................................................ 2-16Table 2-10 Components of the Convert Management System interface............................................................2-19Table 2-11 Components of the performance browser tool interface..................................................................2-20Table 2-12 Components of the Traffic Recording Review Tool interface.........................................................2-21Table 2-13 Components on the file manager interface.......................................................................................2-22Table 3-1 Command groups.................................................................................................................................3-3Table 3-2 External user accounts..........................................................................................................................3-4Table 3-3 Examples of operation time limit settings............................................................................................3-6Table 4-1 Actions of the MML commands..........................................................................................................4-3Table 4-2 MML command window......................................................................................................................4-5Table 5-1 Fault alarms and event alarms..............................................................................................................5-2Table 5-2 Alarm severity levels............................................................................................................................5-3Table 5-3 Functions of the buttons.....................................................................................................................5-13Table 7-1 Operations available when browsing traced messages online........................................................... 7-62Table 10-1 Loopback modes for different interface boards............................................................................... 10-6Table 10-2 Results of a DSP channel loopback test.........................................................................................10-53Table 11-1 Site attributes....................................................................................................................................11-3Table 11-2 Cell attributes...................................................................................................................................11-4Table 11-3 TRX attributes..................................................................................................................................11-6Table 11-4 Channel attributes.............................................................................................................................11-7

BSC6900 GSMLMT User Guide Tables


xix

1 Changes in the BSC6900 GSM LMT UserGuide

This chapter describes the changes made in theBSC6900 GSM LMT User Guide.

07 (2011-01-30)This is the seventh commercial release.

Compared with issue 06 (2010-09-15) of V900R011C00, this issue includes the following newtopics:l 12.13 LMT Fails to Function Properly When Error Occurs in Mixed Code Security

Verification of JREl 11.17.7 Querying TRX Timeslotl 10.3 Backing Up Datal 10.4 Restoring Data

Compared with issue 06 (2010-09-15) of V900R011C00, this issue incorporates the followingchanges:

Topic Change Description

2.3 Components of the LMT Window Modify the figure according to the GUI.

Compared with issue 06 (2010-09-15) of V900R011C00, this issue does not exclude any topics.

06 (2010-09-15)This is the sixth commercial release.

Compared with issue 05 (2010-05-31) of V900R011C00, this issue includes the following newtopics:l Types of Messages Traced on Different Interfaces in GSM Servicesl 7.1.3 Trace Model Tracing CS Domain RSL Messages on the Abis Interface

BSC6900 GSMLMT User Guide 1 Changes in the BSC6900 GSM LMT User Guide


1-1

l Tracing CS Domain ESL Messages on the Abis Interfacel Tracing CS Domain EML Messages on the Abis Interfacel Tracing BSSAP Messages on the A Interfacel Tracing MTP3 Messages on the A Interfacel Tracing MTP2 Messages on the A Interfacel Tracing SCTP Messages on the A Interfacel Tracing M3UA Messages on the A Interfacel Tracing CS Domain OML Messages on the Abis Interfacel Tracing CS Domain LAPD Messages on the Abis Interfacel Tracing Application Messages on the Pb Interfacel Tracing LAPD Messages on the Pb Interfacel Tracing LAPDm Messages Through BTS Signaling Tracel Tracing RLC/MAC Messages Through BTS Signaling Tracel Tracing BSSAP-LE Messages on the LB Interfacel Tracing MTP3 Messages on the LB Interfacel Tracing MTP2 Messages on the LB Interfacel Tracing SCTP Messages on the LB Interfacel Tracing M3UA Messages on the LB Interfacel Tracing SCCP Messages on the A Interfacel 12.10 Unable to Log In To LMT Because IE Default Security Level Is Too Highl 12.11 Unable to Log In To LMT and Class can't Stand Automation Operation is

Displayedl 12.12 LMT Failing to Load the Progress Interface After a Successful Loginl 11.15.3 Querying BTS Transmission State



2.1 Configuration Requirements of theLMT PC

The description about requirements of Webbrowser for the LMT PC is modified.

4.3 Batch Processing MML Commands The description about scheduled batchrunning is added.


05 (2010-05-31)This is the fifth commercial release.

Compared with issue 04 (2010-03-25) of V900R011C00, this issue includes the following newtopics:l 12.9 Methods for Setting the Explorer Under Citrix Farm Networking

1 Changes in the BSC6900 GSM LMT User GuideBSC6900 GSM

LMT User Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 07 (2011-01-30)

l 10.7.1 Analyzing Voice Logs



2.1 Configuration Requirements of theLMT PC

The description about requirements ofconnection ports for the LMT PC is added.


04 (2010-03-25)This is the fourth commercial release.

Compared with issue 03 (2009-12-05) of V900R011C00, this issue includes the following newtopics:l 12.7 Changing the Computer Time During the LMT Use Prohibitedl 12.8 Corrupt Characters Occurring When Opening the csv File in UTF-8 Coding



2.3 Components of the LMT Window The description about the Language Settingis added.


03 (2009-12-05)This is the third commercial release.

Compared with issue 02 (2009-10-30) of V900R011C00, this issue includes the following newtopics:l 2.5 File Manager

Compared with issue 02 (2009-10-30) of V900R011C00, this issue does not incorporate anychanges.


02 (2009-10-30)This is the second commercial release.

Compared with issue 01 (2009-07-30) of V900R011C00, this issue includes the following newtopics:l 10.6.8 Querying the Optical Interface Board Port Information

BSC6900 GSMLMT User Guide 1 Changes in the BSC6900 GSM LMT User Guide


1-3

l 10.6.11 Maintaining IP Linksl 10.8 Querying Board Version Informationl 11.7 Querying BTS Board Matching Resultl 12 FAQ

Compared with issue 01 (2009-07-30) of V900R011C00, this issue does not incorporate anychanges.

Compared with issue 01 (2009-07-30) of V900R011C00, this issue excludes the followingtopics:l Device Commissioningl Internal Maintenancel Debugging Test

01 (2009-07-30)This is the first commercial release.

1 Changes in the BSC6900 GSM LMT User GuideBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

2 Introduction to LMT

About This Chapter

The Local Maintenance Terminal (LMT) is a web-based application that provides a graphicaluser interface (GUI) for users for easy operation and maintenance of the BSC6900. Users canperform operations such as alarm management, trace management, performance monitoring,and device maintenance. Users can also run MML commands and read the correspondingexecution results on the LMT.

2.1 Configuration Requirements of the LMT PCThe computer on which the LMT is running is called the LMT PC. The LMT PC must meet therequirements related to hardware, software, connection ports, and communication capability.

2.2 LMT Login and ExitThis describes how to log in to the LMT for NE operations and how to exit it after performingthe operations.

2.3 Components of the LMT WindowYou can log in to the LMT through the web browser to operate and maintain the BSC6900.

2.4 LMT SoftwareThe Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMTOffline Tools, Convert Management System, Performance Browser, and Traffic RecordingReview Tool.

2.5 File ManagerThe file manager is a component of the LMT software suite. It enables file uploading anddownloading between the LMT and the OMU. The functions of the file manager are similar tothose of the FTP client. For example, you can obtain logs and upload data configuration files.

BSC6900 GSMLMT User Guide 2 Introduction to LMT


2-1

2.1 Configuration Requirements of the LMT PCThe computer on which the LMT is running is called the LMT PC. The LMT PC must meet therequirements related to hardware, software, connection ports, and communication capability.

Hardware RequirementsTable 2-1 describes the hardware requirements of the LMT PC.

Table 2-1 Hardware requirements of the LMT PC

Item Quantity

RecommendedConfiguration

MinimumConfiguration

CPU 1 2.8 GHz or above 866 MHz

RAM 1 1 GB 512 MB

Hard disk 1 80 GB 10 GB

Display resolution - 1024 x 768 or above 1024 x 768

CD drive 1 - -

Ethernet adapter 1 10/100 Mbit/s 10/100 Mbit/s

Other devices 5×1 Keyboard, mouse,modem, audio card,and speaker

Keyboard and mouse

Software RequirementsTable 2-2 describes the software requirements of the LMT PC.

Table 2-2 Software requirements of the LMT PC

Item Recommended Configuration

Operating system Windows XP Professional SP2, Windows Server 2003,Windows Server 2008, Windows Vista, or Windows 7.

Default language of theoperating system

Simplified Chinese or English

2 Introduction to LMTBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Item Recommended Configuration

Web browser Internet Explorer 6.0.2900.2180.xpsp_sp2_gdr or laterreleases, Internet Explorer 7.0.5730.13 or later releases,Internet Explorer 8.0.6001.18702 or later releases, orFireFox 3.0 or later releases.NOTEl You need to set the security level of the Web browser to medium

or low. Otherwise, the LMT menus cannot be viewed.

l when you use the FireFox 3.6 or later releases, you need to installa JRE plug-in of a version that later than 1.6.0_18 .

Java plug-in called JavaPlatform Standard EditionRuntime Environment (JRE)

jre-6u11-windows-i586-p-s.exe or later official versionsNOTE

The plug-in can be obtained on the official Java website http://java.com or on Huawei support website http://support.huawei.com.

CAUTIONl 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 the32-bit Web explorer.

Requirements of Connection Ports

Before you visit the LMT through the Web on a PC, ensure that ports 80, 20, and 21 of thefirewall are open if there is a firewall between the PC and the LMT.

NOTE

l Port 80 is the default HTTP port that is used for webpage browsing.

l Ports 20 and 21 are the ports used for FTP file transfer.

Communication Capability Requirements

The LMT PC must support TCP/IP protocols and meet the requirements of effective bandwidthin Table 2-3.

Table 2-3 Effective bandwidth requirements of the LMT PC

Item Protocol RecommendedConfiguration

MinimumConfiguration

Requirements ofeffective bandwidth

HyperText TransferProtocol (HTTP)

Not lower than 2Mbit/s

512 Kbit/s



2-3

NOTE

l Bandwidth affects the speed of webpage visits. You can rapidly visit the LMT on an LMT PC with arecommended configuration. Your visit to the LMT is, however, significantly delayed on an LMT PCwith 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 programscompete with the LMT for bandwidth resources, a serious delay occurs despite a link bandwidth of 2Mbit/s under HTTP.

2.2 LMT Login and ExitThis describes how to log in to the LMT for NE operations and how to exit it after performingthe operations.

ContextYou must install the JAVA Platform Standard Edition Runtime Environment (JRE) programbefore launching the LMT. If no JRE program is installed, a message is displayed when you login to the LMT, prompting you to install the program. Follow the instructions to install theprogram. If the JRE program on the LMT PC is not the latest version, a message is displayed,prompting you to upgrade the program version. In this case, you are advised to uninstall theexisting JRE program and then install the new version. If you cannot log in to the LMT afteryou upgrade the JRE program, restart the web browser and retry.

WARNINGWhen the LMT is running, do not modify the system time or time zone as errors may occur onthe system. Close the LMT window before modifying these values.


LMT User Guide


Issue 07 (2011-01-30)

CAUTIONl The LMT does not support the refreshing function of the browser. If you refresh the window,

you are logged out of the LMT. If you refresh the trace and monitor page, a message indicatingthe script error is displayed.

l When the LMT window is open, do not modify any file folder properties. Otherwise, the IEbrowser is automatically refreshed, and error occurs on the LMT.

l If users open the LMT window through the IE browser, the IE browser must support theHTTP 1.1 protocol. You can refer to the following setting: choose Tools > InternetOptions > Advanced > HTTP 1.1 Settings, select Use HTTP 1.1. If users need to connectLMT through the proxy server, Use HTTP 1.1 through proxy connection must be selected.

l If the LMT is active in the IE browser and you choose Start > Run to start the FTP server,the IE browser closes the LMT window and goes to the login window of the FTP serverdirectly. To avoid this problem, set the IE browser as follows: choose Tools > InternetOptions. In the Advanced tab page, deselect Reuse windows for launching shortcuts inthe Browsing options.

l If the colors on the LMT window cannot be displayed, set the IE browser as follows: chooseTools > Internet Options. In the General tab, click Accessibility. Then, in theFormatting area, deselect Ignore colors specified on Web pages.

l You need to clear the cache and cookies in the browser (see 12.1 Browser Cache expires.)before you roll back or upgrade the LMT version.

l If AVG Internet Security is installed on the LMT PC, the web shield function must bedisabled. If this function is enabled, a dialog box will be displayed, prompting "Disconnected.Please log in again."

Procedure

Step 1 Type the external virtual IP address of the OMU in the address bar of the IE. Press Enter on thekeyboard, or click Go next to the address bar to enter the login window of the BSC6900.



2-5

NOTE

l If another proxy server is already set, you need to add OMU_IP to the IP addresses that do not use the proxyserver under Exceptions. Set the IP addresses under Exceptions by using the following method: ChooseTool > Internet Options on the tool bar of the IE. In the Connection tab page, click LAN Settings. In thedisplayed window, click Advanced. In the displayed Proxy Settings window, specify an IP address thatdoes not use the proxy server under Exceptions. For example, OMU_IP or M2000_IP.

l If users need to connect the LMT to the OMU through the M2000 proxy server and then enter theBSC6900 login window, they can adopt the following two methods:

l Type "M2000_IP/OMU_IP/" or "http://M2000_IP/OMU_IP/login.html" in the address bar of the IE.Then press Enter on the keyboard, or click Go next to the address bar to enter the login window of theBSC6900. Note that "/" must be included in "M2000_IP/OMU_IP/" behind OMU_IP. If another proxyserver is already set, you need to add M2000_IP to the IP addresses that do not use the proxy serverunder Exceptions.

l Set the M2000 proxy server in the IE and type the external virtual IP address of the OMU in the addressbar of the IE. Press Enter on the keyboard, or click Go next to the address bar to enter the login windowof the BSC6900. You can set the M2000 proxy server in the IE by using the following method: ChooseTool > Internet Options on the tool bar of the IE. In the Connection tab page, click LAN Settings.Then specify the IP address and port number of the M2000 server in the Proxy server area. The defaultport number is 80.

l OMU_IP indicates the external virtual IP address of the OMU and M2000_IP indicates the IP address ofthe M2000 server.

Step 2 Specify User Name, Password, and Verify Code.l Set User Type to Local or EMS.l If the verify code is illegible, click Change the verify code for a new code.

Step 3 Click Login.

NOTE

l Before logging in to the BSC6900 as an EMS user, you need to set up a connection between theBSC6900 and the M2000 server.

l If the login fails, click Reset. Specify User Name, Password, and Verify Code again to log in. If thelogin fails again, verify there is a normal connection between the LMT and the OMU.

Step 4 Optional: To lock the LMT window, click Lock on the top bar.

Step 5 To exit the LMT, click Logout in the top right corner of the LMT main page.

----End

2.3 Components of the LMT WindowYou can log in to the LMT through the web browser to operate and maintain the BSC6900.

InterfaceFigure 2-1 shows the LMT window.


LMT User Guide


Issue 07 (2011-01-30)

Figure 2-1 LMT window

Table 2-4 describes components of the LMT window.

Table 2-4 Components of the LMT window

Component Description

Alarm tab You can query active alarms, alarm logs, and alarm configurationon this tab page. For details, see 5 Alarm Management.

Batch tab You can run MML commands in batches on this tab page.

Trace tab You can manage message tracing tasks on this tab page. For details,see 7 Trace Management.

Monitor tab You can monitor performance data on this tab page. For details, see8 Performance Monitoring.

Device Maintenancetab

You can maintain the device panel, base station controllers, andbase stations on this tab page. For details, see 9 Device Panel, 10BSC Maintenance, and 11 BTS Maintenance.

MML tab For details, see 4.1.2 Components of the MML CommandWindow.

Progress tab This tab displays the progress of tasks.NOTE

If this tab is hidden, click Progress on the toolbar to show the Progress tabpage. Then, double-click an entry to view the detailed information. TheProgress Management dialog box is displayed, listing the detailed progressreport.



2-7


FTP Tool Click FTP Tool on the tool bar of the LMT window to downloadthe executable application file SFTPServer.exe. Then double-clickthe executable file to start the FTP server. For details, see 2.4.2 FTPClient and 2.4.3 FTP Server.

Password You can select this tab to change the password of the current useraccount. After changing the password, you need to use the newpassword when logging in again.

File Manager You can select this tab to upload and download files between theLMT and the OMU. For details, see 2.5 File Manager.

Language Setting After you choose a language, input and display in the language aresupported.NOTE

Setting the language does not change the display language of the LMT.

About Displays the version of the current LMT.

Lock You can click it to lock the current operation interface for security.NOTEl After you click Lock on the toolbar, the LMT is locked.

l You can click the web page or press the enter key; then enter thepassword, or type the password and press OK to enter the LMTworkspace.

Logout You can click it to log out the current user without exiting thesystem. Logout of one account user facilitates login of anotheraccount user.

Online HelpThe LMT provides the following two types of online help:

l Online help systeml MML help

Table 2-5 lists the specific help and startup method of online help.


LMT User Guide


Issue 07 (2011-01-30)

Table 2-5 Description of LMT online help

Name Specific Help Startup Method

Onlinehelpsystem

Provides thefollowinginformation:l LMT online

helpl Alarm

referencel Event

reference

If the Microsoft Internet Explorer is used:l Press F1 or click Help on the LMT main page to display

LMT help information.l Press F1 in a displayed dialog box to display help

information about the specific dialog box.If the FireFox Explorer is used, press Help on the LMT mainpage to display LMT help information.

MMLhelp

Provides thefollowinginformationabout an MMLcommand:l Command

functionl Notel Parameterl Examplel Output

description(only forquerycommands)

Type an MML command in the Command Input box. PressEnter or click Assist, and then click the Help Informationtab. Accordingly, help information about the command isdisplayed on the tab page.

2.4 LMT SoftwareThe Local Maintenance Terminal (LMT) software consists of the FTP Client, FTP Server, LMTOffline Tools, Convert Management System, Performance Browser, and Traffic RecordingReview Tool.

2.4.1 Installing LMT Offline ToolsThis describes how to install the LMT offline tools on the LMT PC.

2.4.2 FTP ClientThe FTP client is a component of the LMT offline tool and enables the communication betweenthe LMT and the FTP server according to the FTP protocol. You can obtain logs and uploaddata configuration files through the FTP client.

2.4.3 FTP ServerThe FTP server is a component of the LMT offline tool and provides upload and downloadservices according to the FTP protocol. It is used when uploading and downloading BTS softwareand license file.

2.4.4 LMT Offline MML



2-9

LMT offline MML is a component of the LMT offline tool. It enables users to use MMLfunctions, view MML, make MML scripts, and view LMT Online Help of the correspondingversion offline by means of a browser.

2.4.5 Convert Management SystemThe Convert Management System is a component of the LMT offline tool. It enablescommunication between the OMU and the alarm box and is used to transfer the alarminformation, alarm box control information, and alarm box status information. The ConvertManagement System must be started to connect the LMT to the alarm box. The ConvertManagement System communicates with the OMU through the Ethernet port and to the alarmbox through the serial port.

2.4.6 Performance Browser ToolThe performance browser tool is a component of the LMT offline tool. It is used to parse theperformance descriptive files in the OMU.

2.4.7 Traffic Recording Review ToolThe Traffic Recording Review Tool is a component of the LMT offline tool and is used to reviewthe trace and monitor data.

2.4.1 Installing LMT Offline ToolsThis describes how to install the LMT offline tools on the LMT PC.

Prerequisitel A legal serial number for the LMT software is obtained.l The PC for installing the LMT offline tools complies with the specifications in 2.1

Configuration Requirements of the LMT PC.

Context

CAUTIONIf the setup languages of the LMT and OMU software are different, some functions such as themanagement of user accounts will not be available. Therefore, you are advised to install themin the same language.

Procedure

Step 1 Use the administrator account to log in to the LMT PC.

Step 2 Insert the setup disk into the CD-ROM drive.l The setup program runs automatically.l If the setup program fails to run automatically, double-click setup.bat or setup.vbs in the

directory of the setup disk.


LMT User Guide


Issue 07 (2011-01-30)

NOTEYou can also download the installation package of the LMT offline tool from http://support.huawei.com. Log in to the website, and then choose Support > Software Center > VersionSoftware > Wireless Product Line > Single RAN > MBSC > BSC6900. Then, select the required softwareversion to download.

Step 3 Choose the installation language, and click OK. The installation wizard prompts you that youare installing HUAWEI Local Maintenance Terminal.

Step 4 Click Next. A dialog box is displayed, asking you to read the copyright notice.

Step 5 Read the software certificate declarations. If you accept the agreement terms, select I acceptthese terms, and then click Next. A dialog box is displayed, asking you to specify the installationpath. If you do not accept the agreement terms, click Cancel to quit the installation.

Step 6 Use the default installation path or browse to a new path, and then click Next.

NOTE

The default installation path is D:\HW LMT.

l If the LMT of another version or NE has been installed, the installation path is that of the original LMTsoftware and cannot be altered.

l To alter the installation path, you must uninstall the existing LMT software.

If an LMT software is running, the Warning dialog box is displayed. Click Yes to automatically exit theLMT application. Click No to manually exit the LMT application.

Step 7 Select the software components and then click Next. It is recommended that you select allcomponents. A dialog box is displayed for entering the CD-KEY.

Step 8 Enter the CD-KEY correctly, and then click Next. A dialog box is displayed, asking you toconfirm the installation.

Step 9 Confirm the installation parameters and click Next. A dialog box is displayed, indicating theprogress of copying the files.When the task of copying files is complete, a dialog box is displayed for initializing components.When all programs are installed, a dialog box is displayed, indicating the completion of theinstallation.

Step 10 Click Finish.

NOTE

The installation is complete. When the installation is complete, the LMT Service Manager automaticallystarts.

----End

2.4.2 FTP ClientThe FTP client is a component of the LMT offline tool and enables the communication betweenthe LMT and the FTP server according to the FTP protocol. You can obtain logs and uploaddata configuration files through the FTP client.

Startup

Choose Start > All Programs > HUAWEI Local Maintenance Terminal > FTP Client onthe LMT PC.



2-11

Interface

Figure 2-2 shows the FTP client interface.

Figure 2-2 FTP client interface

Table 2-6 describes the components of the FTP client interface.

Table 2-6 Components of FTP client interface

Number Component Description

1 Menu bar Provides the menus for the operation of the system.

2 Tool bar Provides the shortcut icons for the operation of thesystem.

3 Server input area You can specify the server name, user name, userpassword, port number, and mode in this area.

4 Local directory listwindow

Displays the directory structure of the currentcomputer.

5 Server file list window Lists the files and file folders stored in the connectedFTP server.

6 Local file list window Lists the files and file folders stored in the currentcomputer.

7 Prompt informationwindow

Displays the information such as the connectionstatus of the FTP server and the operationdescriptions.


LMT User Guide


Issue 07 (2011-01-30)

2.4.3 FTP ServerThe FTP server is a component of the LMT offline tool and provides upload and downloadservices according to the FTP protocol. It is used when uploading and downloading BTS softwareand license file.

StartupThere are two ways to start up the FTP server:l Choose Start > All Programs > HUAWEI Local Maintenance Terminal > FTP

Server on the LMT PC.l Click FTP Tool on the tool bar of the LMT window to download the executable application

file SFTPServer.exe.

InterfaceFigure 2-3 shows the FTP server interface.

Figure 2-3 FTP server interface

Table 2-7 describes the components of the FTP server interface.



2-13

Table 2-7 Components of FTP server interface


Port number Indicates the number of the port used by the FTP server tointercept the information on the network. According to the FTPprotocol, the port 21 is used as the default port.

Thread number Indicates the number of clients that can be connected to the FTPserver simultaneously.

2.4.4 LMT Offline MMLLMT offline MML is a component of the LMT offline tool. It enables users to use MMLfunctions, view MML, make MML scripts, and view LMT Online Help of the correspondingversion offline by means of a browser.

Introduction to the LMT Offline MML ServerThis section describes the startup method and interface of the LMT offline MML server.

Startup MethodChoose Start > All Programs > HUAWEI Local Maintenance Terminal > WebLMTOffLine MML on an LMT PC to start the LMT offline MML server.

InterfaceFigure 2-4 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 offlineMML server interface after the LMT offline MML server is started and minimized.

Figure 2-4 LMT Offline MML Server Interface


LMT User Guide


Issue 07 (2011-01-30)

Table 2-8 describes each area of the LMT offline MML server interface.

Table 2-8 Description of the LMT offline MML server

Field Description

Routine tab Displays the server state of LMT offline MML.NOTEl 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

This section describes how to log in to LMT offline MML for relevant operations and how toexit it after performing the operations.

Prerequisite

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 MMLtool is installed on the LMT PC.

If... Then...

The LMT offline MML tool is installed andstarted on the LMT PC.

Enter http://127.0.0.1:Port or http://IPAddress:Port in the browser and the LMToffline MML login window is displayed.

The LMT offline MML tool is not installedon the LMT PC.

Enter http://IPAddress:Port in the browserand the LMT offline MML login window isdisplayed.

NOTE

l IPAddress stands for the IP address of an LMT PC installed with the LMT offline MML tool. Portstands 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 numbertakes effect only after the LMT offline server is stopped and then restarted.



2-15

Step 2 Select OMType, Version, and Pattern in the LMT offline MML login window and clickLogin to log in.

NOTE

l Click the language-switching button in the top right corner of the login window to switch displaylanguage between English and Chinese.

l Click Reset to restore the default setting used during installation.

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 usinga browser, you can view MML, make relevant MML scripts, and obtain LMT Online Help.

Interface

Figure 2-5 shows the LMT offline MML interface.

Figure 2-5 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

Field Description

Navigation Tree Displays the entire set of MML commands. Double-click a MMLcommand to load it to the Command Input box.

Search Enter a keyword to search for an MML command.


LMT User Guide


Issue 07 (2011-01-30)

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

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

Command Input box Displays in the drop-down list all the MML commands availableon the system. You can select an MML command from the drop-down list or type in an MML command for execution.

Parameter area Displays parameters of a current command. You need to setparameter values in the boxes before executing the command. Theparameters displayed in red are mandatory and those in black areoptional.

Help Click Help to obtain LMT Online Help of the correspondingversion.

About Click About to obtain information about the version of LMToffline MML.

Making MML Scripts OfflineThis 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 LMTOffline 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 Inputbox, 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 overwritewhat was saved.

l You can right-click in the Operation Record area and choose an option from the shortcut menu toclear 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 theMML command or all MML commands.

----End



2-17

2.4.5 Convert Management SystemThe Convert Management System is a component of the LMT offline tool. It enablescommunication between the OMU and the alarm box and is used to transfer the alarminformation, alarm box control information, and alarm box status information. The ConvertManagement System must be started to connect the LMT to the alarm box. The ConvertManagement System communicates with the OMU through the Ethernet port and to the alarmbox through the serial port.

FunctionThe Convert Management System performs the following functions:l Forwards the alarm operation instructions from the LMT.l Forwards the alarm information to the alarm box.l Detects the real-time status of the connection between the LMT and the OMU and that

between the LMT and the serial ports of the alarm box, and reports the alarms if any.

StartupChoose Start > All Programs > HUAWEI Local Maintenance Terminal > ConvertManagement System on the LMT PC.

InterfaceFigure 2-6 shows the interface of the Convert Management System.

Figure 2-6 Interface of the Convert Management System

Table 2-10 describes the components of the Convert Management System interface.


LMT User Guide


Issue 07 (2011-01-30)

Table 2-10 Components of the Convert Management System interface




3 Information outputwindow

Displays the real-time output information of theConvert Management System.

2.4.6 Performance Browser ToolThe performance browser tool is a component of the LMT offline tool. It is used to parse theperformance descriptive files in the OMU.

StartupChoose Start > All Programs > HUAWEI Local Maintenance Terminal > PerformanceBrowser Tool on the LMT PC.

InterfaceFigure 2-7 shows the interface of the performance browser tool.

Figure 2-7 Interface of performance browser tool

Table 2-11 describes the components of the performance browser tool interface.



2-19

Table 2-11 Components of the performance browser tool interface




3 Measurementstatistics window

Provides the measurement statistic files in the treestructure.

4 Detailed informationwindow

Provides the detailed information on a selectedperformance file.

2.4.7 Traffic Recording Review ToolThe Traffic Recording Review Tool is a component of the LMT offline tool and is used to reviewthe trace and monitor data.

StartupChoose Start > All Programs > Huawei Local Maintenance Terminal > Traffic RecordingReview Tool on the LMT PC.

InterfaceFigure 2-8 displays the interface of the Traffic Recording Review Tool.


LMT User Guide


Issue 07 (2011-01-30)

Figure 2-8 Interface of the Traffic Recording Review Tool

Table 2-12 describes the components of the Traffic Recording Review Tool interface.

Table 2-12 Components of the Traffic Recording Review Tool interface




3 Service data retrievalwindow

Provides the data related to the trace and monitortasks.

2.5 File ManagerThe file manager is a component of the LMT software suite. It enables file uploading anddownloading between the LMT and the OMU. The functions of the file manager are similar tothose of the FTP client. For example, you can obtain logs and upload data configuration files.

StartupClick File Manager in the tool bar on the LMT main interface.



2-21

InterfaceFigure 2-9 shows the interface of the file manager.

Figure 2-9 File manager interface

Table 2-13 describes the components on the file manager interface.

Table 2-13 Components on the file manager interface


1 Navigation tree Displays the files on the OMU.

2 File manager panel Displays details about the files on the OMU.

3 Processing status area Displays the progress of a task.

NOTE

l To upload files from the LMT PC to the OMU, you can click Upload on the file manger panel.Alternatively, you can right-click files in the file manager panel, and then choose Upload from theshortcut menu.

l To download files from the OMU to the LMT PC, you can click Download on the file manger panel.Alternatively, you can right-click files in the file manager panel, and then choose Download from theshortcut menu.

l To store a file on the LMT PC, you can click Directory to specify a save path.


LMT User Guide


Issue 07 (2011-01-30)

3 Management of Operation Rights

About This Chapter

This chapter describes the management of operation rights, and provides instruction to manageuser accounts and command groups.

3.1 Concepts Related to Operation Rights ManagementThis section describes the principles of managing the operation rights of the BSC6900 LMT interms of user identity, user rights, and operation time limit.

3.2 Management of User AccountsThis section describes how to manage user accounts of the BSC6900 LMT. Instructions areprovided for creating, modifying, and deleting the external user accounts.

3.3 Management of User PasswordsThis section describes how to manage the user password of a BSC6900 LMT user account.Instructions are provided for defining the login password policies, querying the login passwordpolicies, changing the password of the current user, and changing the password of an externaluser account by an authorized user.

3.4 Management of Command GroupsThis section describes how to manage command groups. Instructions are provided for queryingthe command groups, setting the command group name, and modifying the command groupcontents.

BSC6900 GSMLMT User Guide 3 Management of Operation Rights


3-1

3.1 Concepts Related to Operation Rights ManagementThis section describes the principles of managing the operation rights of the BSC6900 LMT interms of user identity, user rights, and operation time limit.

3.1.1 Principles of Operation Rights ManagementThis section describes the principles of managing the operation rights of the BSC6900 LMT interms of user identity, user rights, and operation time limit.

3.1.2 User PasswordThis section describes the BSC6900 LMT user password in terms of password definition, initialpassword setting, and password change.

3.1.3 Command GroupThe BSC6900 provides 15 command groups (G_0 to G_14) with different functions.

3.1.4 User TypeYou can log in to the BSC6900 LMT as the Local user and the EMS user.

3.1.5 Operation RightsThis section describes the operation rights of the built-in administrator account and other externaluser accounts of the BSC6900 LMT.

3.1.6 Operation Time LimitThis section describes the definition, principle, and setting of the time limits for a user to operatethe BSC6900 LMT.

3.1.1 Principles of Operation Rights ManagementThis section describes the principles of managing the operation rights of the BSC6900 LMT interms of user identity, user rights, and operation time limit.

The BSC6900 OM subsystem supports operations by multiple users simultaneously. For thesake of system security, the operation rights are managed and controlled on the basis of thefollowing aspects:l User identity: An operator must enter the correct user name and password to log in to the

system.l Operation rights: Users of different levels are permitted to use different command groups

for menu operations or MML operations.l Operation time limit: It defines the maximum period for a user to perform the operations.

3.1.2 User PasswordThis section describes the BSC6900 LMT user password in terms of password definition, initialpassword setting, and password change.

Definition of User PasswordTo ensure the system security, each user account has a password. The operator must enter a validuser name and password to log in to the LMT and then the OMU.

ADMINISTRATOR-level users can set password complexity. For more information refer toSetting Password Policies.

3 Management of Operation RightsBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

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 useraccount and set the password of that account.

Permissions for Changing Passwords

All users can change their own password. The admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can change the passwords of all external user accounts. Only the adminuser 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 Changingthe Password of an External User Account.

3.1.3 Command GroupThe BSC6900 provides 15 command groups (G_0 to G_14) with different functions.

Table 3-1 describes these command groups.

Table 3-1 Command groups

Command Group Function

G_0 Used to query system information such as the user groups,command groups, logs, NTP, EMS, and time zone.

G_1 Used to manage system information such as user groups, timezone, Daylight Saving Time (DST), and batch configuration.

G_2 Used to query the data configuration information. Thesecommands 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 orto set the alarm level.

G_6 Used to query performance statistics, for example, to query aperformance statistical file or task file.

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

G_8 Used to query the equipment information such as the equipmentstatus. 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 planeor the user plane, for example, to query the trace tasks or to create/delete/start a trace task.



3-3

Command Group Function

G_11 Used to modify the settings of the integrated equipment panels.

G_12 Used to manage the software, for example, patch management.

G_13 Used to query the base station information, for example, to querythe BTS attribute or to query the BTS boards.

G_14 Used to manage the base stations, for example, BTS softwaremanagement or BTS resetting.

For the operations related to command groups, see 3.4 Management of Command Groups.

3.1.4 User TypeYou can log in to the BSC6900 LMT as the Local user and the EMS user.l Local user: This type of account (including the default local admin account) is managed

by the BSC6900 LMT independently. That is, you can log in to the BSC6900 when youinstall the BSC6900 system or when the OMU is disconnected from the M2000.

l EMS user: This type of account is managed by the M2000. They are created, modified,authenticated, and authorized by the M2000. Only authorized EMS users can log in to theBSC6900 using the LMT. The authorized EMS users can also log in to the M2000 serverthrough the M2000 client for BSC6900 operations.

3.1.5 Operation RightsThis section describes the operation rights of the built-in administrator account and other externaluser accounts of the BSC6900 LMT.

Built-In Administrator AccountThe system has a built-in administrator account, also referred to as super administrator. The username 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 AccountsThere are five levels of external user accounts. Each level has distinctive operation rights, asdescribed in Table 3-2.

Table 3-2 External user accounts

Level AssignedCommandGroup

Operation Right Description

GUEST G_0, G_2, G_4,G_6, G_8, andG_13

Data query The operationrights arepredefined by the


LMT User Guide


Issue 07 (2011-01-30)

Level AssignedCommandGroup

Operation Right Description

USER system and cannotbe changed.

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 GUEST-level

l System OM

OPERATOR 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 USER-level

l Data configuration

ADMINISTRATOR

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 Commandgroups areassigned whenthe account iscreated.

Specified when the account iscreated

The operationrights can bechanged. DifferentCUSTOM-levelusers may havedifferent operationrights.

NOTE

l The admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can add or delete anexternal user account.

l An authorized CUSTOM-level user can add users only by running MML commands.

3.1.6 Operation Time LimitThis section describes the definition, principle, and setting of the time limits for a user to operatethe BSC6900 LMT.

Definition of Operation Time Limit

The operation time limit defines the maximum period for a user to perform the operations.

l There is no operation time limit for the admin account. The admin user can operate thesystem anytime.

l The operation time limit of an external user account is specified when the account is created.If no time limit is set, the operator can operate the system anytime.



3-5

Principle of Operation Time LimitThe operation time limit is specified by a combination of date, day, and time.

Table 3-3 provides some examples of operation time limit settings.

Table 3-3 Examples of operation time limit settings

SN Date Day Time Permitted Operation Time

1 2008-08-01to2009-08-01

Monday toFriday

8:00:00 to18:00:00

8:00:00 to 18:00:00 on Mondaythrough Friday from 2008-08-01to 2009-08-01

2 - Saturday andSunday

- Any time on Saturdays andSundays

3 - - - No operation time limit. Theoperator can operate the system atany time.

Permissions to Set the Operation Time LimitThe admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can set or changethe operation time limit of all external user accounts.

3.2 Management of User AccountsThis section describes how to manage user accounts of the BSC6900 LMT. Instructions areprovided for creating, modifying, and deleting the external user accounts.

3.2.1 Creating an External User AccountThis section describes how to create an external user account. You are required to set thepassword, user level, command group (for CUSTOM-level user account only), and operationtime limit for the new user account. Only the admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can perform this operation.

3.2.2 Modifying an External User AccountThis section describes how to modify the attributes of an external user account, including theuser name, user password, user level, operation rights, and operation time limit. The newpassword takes effect upon the next login. Modifications of other attributes take effectimmediately. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level userscan perform this operation.

3.2.3 Deleting an External User AccountThis section describes how to delete an external user account. Only the admin,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

3.2.1 Creating an External User AccountThis section describes how to create an external user account. You are required to set thepassword, user level, command group (for CUSTOM-level user account only), and operation


LMT User Guide


Issue 07 (2011-01-30)

time limit for the new user account. Only the admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can perform this operation.

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

CAUTIONThe new user account cannot be the same as any of the existing ones.

----End

3.2.2 Modifying an External User AccountThis section describes how to modify the attributes of an external user account, including theuser name, user password, user level, operation rights, and operation time limit. The newpassword takes effect upon the next login. Modifications of other attributes take effectimmediately. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level userscan perform this operation.


Procedure

Step 1 Run the MOD OP to modify the attributes of a user account.

----End

3.2.3 Deleting an External User AccountThis section describes how to delete an external user account. Only the admin,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.


Context

CAUTIONThe admin account is the permanent built-in user account and cannot be deleted.



3-7

Procedure

Step 1 Run the RMV OP command to delete an external user account.

----End

3.3 Management of User PasswordsThis section describes how to manage the user password of a BSC6900 LMT user account.Instructions are provided for defining the login password policies, querying the login passwordpolicies, changing the password of the current user, and changing the password of an externaluser account by an authorized user.

3.3.1 Defining Login Password PoliciesThis section describes how to define policies for setting the login passwords. The login passwordpolicies set restrictions on the minimum length and complexity of the password. Only theADMINISTRATOR-level users can define the policies for setting the login passwords.

3.3.2 Querying Login Password PoliciesThis section describes how to query the policies for setting the login passwords.

3.3.3 Changing the Password of the Active User AccountThis section describes how to change the password of the active user account. The new passwordtakes effect upon the next login.

3.3.4 Changing the Password of an External User AccountThis section describes how to change the password of an external user account. Only the admin,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

3.3.1 Defining Login Password PoliciesThis section describes how to define policies for setting the login passwords. The login passwordpolicies set restrictions on the minimum length and complexity of the password. Only theADMINISTRATOR-level users can define the policies for setting the login passwords.


Procedure

Step 1 Run the SET PWDPOLICY command to define the policies for setting the LMT loginpasswords.

----End

3.3.2 Querying Login Password PoliciesThis section describes how to query the policies for setting the login passwords.

PrerequisiteYou have logged in to the LMT.


LMT User Guide


Issue 07 (2011-01-30)

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 AccountThis section describes how to change the password of the active user account. The new passwordtakes effect upon the next login.


Context

CAUTIONExercise caution when changing the password of the admin account. If you forget the password,you cannot log in to the system with the admin account. Contact Huawei for technical supportif needed.

Procedure

Step 1 Click Password on the tool bar of the LMT main page. The Password dialog box is displayed.

Step 2 In the displayed Change Password window, enter the current password in the Old Passwordfield. Enter the new password in the New Password and Confirm Password fields. Then clickOK.

----End

3.3.4 Changing the Password of an External User AccountThis section describes how to change the password of an external user account. Only the admin,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.


Procedure

Step 1 Run the MOD OP to change the password of an external user account.

----End



3-9

3.4 Management of Command GroupsThis section describes how to manage command groups. Instructions are provided for queryingthe command groups, setting the command group name, and modifying the command groupcontents.

3.4.1 Querying a Command GroupThere are 15 command groups G_0 to G_14. Only the admin, ADMINISTRATOR-level, andauthorized CUSTOM-level users can query the information about the command groups.

3.4.2 Setting the Command Group NameOnly the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can renamethe command groups.

3.4.3 Changing the Commands in a Command GroupOnly the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can changethe contents of command groups.

3.4.1 Querying a Command GroupThere are 15 command groups G_0 to G_14. Only the admin, ADMINISTRATOR-level, andauthorized CUSTOM-level users can query the information about the command groups.


ProcedureStep 1 Run the LST CCG to query the command groups.

----End

3.4.2 Setting the Command Group NameOnly the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can renamethe command groups.


ProcedureStep 1 Run the LST CCGN command to query the name of a command group.

Step 2 Run the SET CCGN command to rename a command group.

----End

3.4.3 Changing the Commands in a Command GroupOnly the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can changethe contents of command groups.


LMT User Guide


Issue 07 (2011-01-30)


Procedurel Run the ADD CCG command to add commands to a command group.l Run the RMV CCG command to remove commands from a command group.

----End



3-11

4 Running MML Commands

About This Chapter

This chapter describes how to run MML commands on the LMT to operate and maintain theBSC6900.

4.1 Concepts Related to MML CommandsThis section describes the following concepts related to MML commands: MML commands,components of the MML command window, data configuration rights, and configurationrollback.

4.2 Running an MML CommandThis section describes how to use MML commands for routine configuration and maintenance.

4.3 Batch Processing MML CommandsThis section describes how to run multiple MML commands at a time. By batch processingMML commands, you can perform a function or operation by using a prepared series of MMLcommands.

4.4 Setting MML ParametersYou can set the MML parameters as required.

4.5 Querying the Data Configuration ModeThis section describes how to determine if the data configuration mode of the subrack is effectiveor non-effective.

4.6 Querying Data Configuration RightsThis section describes how to check the control status of the data configuration rights.

4.7 Obtaining Data Configuration RightsYou need to obtain the data configuration rights to perform data configuration, undo/redooperations on the BSC6900 exclusively, or perform data configuration in batch without beingaffected by other users. Only the M2000 users and users of the following levels can obtain thedata configuration rights: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled touse command group G_3 (for data configuration).

4.8 Undoing/Redoing a Data Configuration ActionThis section describes how to undo and redo a single data configuration action.

4.9 Undoing/Redoing Multiple Data Configuration Actions

BSC6900 GSMLMT User Guide 4 Running MML Commands


4-1

This section describes how to undo and redo multiple data configuration actions.

4 Running MML CommandsBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

4.1 Concepts Related to MML CommandsThis section describes the following concepts related to MML commands: MML commands,components of the MML command window, data configuration rights, and configurationrollback.

4.1.1 Introduction to MML CommandsThis describes the MML commands that can be used to operate and maintain the BSC6900.

4.1.2 Components of the MML Command WindowThis section describes the components of the MML command window.

4.1.3 Data Configuration RightsThe management of the data configuration rights enables only one user to perform BSC6900data configuration through the LMT or the M2000 at a time.

4.1.4 Data Configuration RollbackData 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 ornetwork problems, you can perform rollback to restore the configurations so that normaloperation of the BSC6900 is restored as early as possible.

4.1.1 Introduction to MML CommandsThis describes the MML commands that can be used to operate and maintain the BSC6900.

An MML command consists of two parts: action and object. For example, ADD OP, whereinADD is the action and OP is the object. Table 4-1 describes the actions that can be performedthrough MML commands.

Table 4-1 Actions of the MML commands

Action Description

ACT Activate

ADD Add

ADT Audit

BEG Begin

BKP Back up

BLK Block

CHK Check

CLR Clear

CMP Compare

COL Collect

CON Confirm



4-3

Action Description

DEA Deactivate

DSP List

EST Establish

EXP Export

FMT Format

FOC Obtain

INH Inhibit

INS Install

LCK Lock

LOD Load

LOP Loopback test

LST List

MOD Modify

PING Ping

REL Release

REQ Request

RUN Run

RMV Remove

RST Reset

SET Set

STR Start/Open

STP Stop/Close

STA Collect statistics

SWP Swap

SYN Synchronize

TRC Trace

UBL Unblock

UIN Uninhibit

ULD Upload

ULK Unlock


LMT User Guide


Issue 07 (2011-01-30)

4.1.2 Components of the MML Command WindowThis section describes the components of the MML command window.

Figure 4-1 shows the MML command window.

Figure 4-1 MML command window

Table 4-2 describes the components of the MML command window.

Table 4-2 MML command window

Field Description

CommonMaintenance tab

Displays system responses such as execution results. In this area,you can save command execution results and let the systemautomatically scroll the results by clicking Save Results and AutoScroll respectively. You can also clear all the results by clickingClear All.NOTE

The time displayed at the beginning of the returned result is the OMU time.

Operation Record tab Displays commands that have been run.NOTE

The Send Time displayed in the operation record is the time of the LMTPC.

Help Information tab Displays the help information for a command.

Manual editing area Displays the area for manually editing the MML command script.

History Command box Displays the commands that you have run after logging in to thesystem and the relevant parameters.



4-5

Field Description

Command Input box Displays in the drop-down list all the MML commands availableon 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 setparameter values in the boxes before executing the command. Theparameters 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 RightsThe management of the data configuration rights enables only one user to perform BSC6900data configuration through the LMT or the M2000 at a time.

In case of conflicts during data configuration, the OMU manages the configuration rights asfollows:l When the control switch of the data configuration rights is ON, only one user has the data

configuration rights at a time. When the switch is OFF, no control is applied on the dataconfiguration rights. (You can run the SET CMCTRLSW command to set the switch toON or OFF.)

l When a user occupies the data configuration rights for a long time, the administrators cancheck with the user. If the user is not performing data configuration, the administrators canrun the FOC CMCTRL command to obtain the data configuration rights manually.

l If the user with the data configuration rights exits the LMT, the data configuration rightsare released automatically. In this case, another user can also run the REQ CMCTRLcommand to obtain the data configuration rights.

4.1.4 Data Configuration RollbackData 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 ornetwork problems, you can perform rollback to restore the configurations so that normaloperation of the BSC6900 is restored as early as possible.

Definition of Configuration RollbackDuring 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 ADDROLLBACKPOINT command to configure the rollback point.)


LMT User Guide


Issue 07 (2011-01-30)

Operations of Configuration Rollback

CAUTIONData configuration rollback cannot be performed if the data configuration control switch isdisabled (with SET CMCTRLSW), quick configuration mode is enabled (with SETQUICKCFG), or batch configuration is performed (with RUN BATCHFILE).

Data configuration rollback consists of the following types of operations:l Undo a single configuration action: This operation is performed to undo a previous

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

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

configuration actions that have taken effect after a specified rollback point. After the undooperation, the system rolls back to the configuration status at the specified rollback point.

l Redo multiple configuration actions: This operation is performed to redo the multipleconfiguration actions that were undone previously. After the redo operation, the systemrestores either the configuration status at the specified rollback point or the finalconfiguration status before undoing the configurations.

4.2 Running an MML CommandThis section describes how to use MML commands for routine configuration and maintenance.


ContextYou can run an MML command in one of the following ways:l Entering an MML command in the Command Input boxl Selecting a previously-executed command from the History Command boxl Selecting an MML command from the MML Command navigation treel Copying the MML command script to the Manual Edit area

NOTE

You can set the control switch of the data configuration rights to ON by running SET CMCTRLSW. Ifyou do not have data configuration rights, you can only run query commands. To obtain the dataconfiguration rights, see 4.7 Obtaining Data Configuration Rights.

Procedurel Entering an MML command in the Command Input box

1. Enter an MML command in the Command Input box. When you enter the command,you can also select the required command from the drop-down list of suggestedcommands.



4-7

2. Press Enter or click Assist to display the parameters associated with the command.

3. Specify the parameter values to run the command.

4. Press F9 or click Exec to run the command. The result is displayed on the CommonMaintenance tab page.

l Selecting a previously-executed command from the History Command box

1. Select a previously-executed command from the drop-down list of history commands.(Press F7 or click to select the previous command. Press F8 or click toselect the next command.)

2. (Optional) Change the parameter values in the command parameter area.


l Selecting an MML command from the MML Command navigation tree

1. Select an MML command from the MML Command navigation tree, and double-click the command.

2. Specify the parameter values to run the command.


NOTE

l The parameters displayed in red are mandatory, and those in black are optional.

l Place the cursor on the parameter value input box to read the general information about theparameter.

l If the execution of the command fails, the result is displayed in red on the CommonMaintenance tab page.

l Copying the MML command script to the Manual Edit area

1. Copy the script of a MML command with the required parameter values, and paste itin the Manual Edit area.


----End

4.3 Batch Processing MML CommandsThis section describes how to run multiple MML commands at a time. By batch processingMML commands, you can perform a function or operation by using a prepared series of MMLcommands.

Context

A batch file (also called data script file) is a plain text file. It contains a group of command scriptsfor a special task. The system automatically runs the commands in sequence.

Batch running MML commands consists of immediate batch processing and scheduled batchprocessing.

l Immediate batch processing: the batch file is run immediately


LMT User Guide


Issue 07 (2011-01-30)

l Scheduled batch processing: the batch file is automatically run at a moment of a dayspecified by an operator in advance

4.3.1 Immediate Batch Processing of MML CommandsThis section describes how to enable the system to immediately run a batch of MML commandsat a time.

4.3.2 Scheduled Batch Processing of MML CommandsThis section describes how to enable the system to automatically run a batch of MML commandsin a batch file at a moment of a day specified by an operator in advance.

4.3.3 Batch Processing AssistantThis section describes how to use the batch processing assistant function. You can use thefunction to check the format of MML commands in the assistant input area, correctness of theparameters BTSID, CELLID, and TRXID, and relationship between the parameters. You canalso use the function to add MML commands to a batch file or directly overwrite the originalbatch file.

4.3.1 Immediate Batch Processing of MML CommandsThis section describes how to enable the system to immediately run a batch of MML commandsat a time.

Prerequisitel You have logged in to the LMT.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 pre-edited 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 bydefault.

----End

4.3.2 Scheduled Batch Processing of MML CommandsThis section describes how to enable the system to automatically run a batch of MML commandsin a batch file at a moment of a day specified by an operator in advance.

Prerequisitel You have logged in to the LMT.l You have obtained FTP user name and password.



4-9

l You have obtained the data configuration rights. For details, see 4.7 Obtaining DataConfiguration Rights.

Procedure

Step 1 Edit a batch file.

1. Click Batch on the LMT main page. The Batch tab page is displayed.

2. Click New and type a batch of MML commands in the input box.

3. Click Save to save the edited batch file.

Step 2 Upload the MML command script file to the /ftp directory in the OMU active work area. Assumethat 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. There are the following two uploadways:

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 tonavigate to the ftp directory. Then click Upload.

3. In the displayed Select Upload File dialog box, select the BATCHFILE.txt file savedin 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 isthe IP address of the OMU.

4. Enter the FTP user name and password. If the authentication passes, an FTP connectionis 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 ofOMU applications.

5. Enter the cd /mbsc/bam/version_a/ftp command to switch to the directory of OMUactive 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 SUBTSKcommands.

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 ftpdirectory of the OMU active work area; result_add.txt is the name of the result file.

----End


LMT User Guide


Issue 07 (2011-01-30)

4.3.3 Batch Processing AssistantThis section describes how to use the batch processing assistant function. You can use thefunction to check the format of MML commands in the assistant input area, correctness of theparameters BTSID, CELLID, and TRXID, and relationship between the parameters. You canalso use the function to add MML commands to a batch file or directly overwrite the originalbatch file.

Prerequisitel You have logged in to the LMT.l The batch file is ready.l You have obtained the data configuration rights. For details, see 4.7 Obtaining Data

Configuration Rights.

ContextThe editing area for the batch assistant allows 20 lines of commands at most. The batch assistantsupports 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], [id1-idn], 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 thebatch processing assistant.

Command Typed in the BatchProcessing Assistant Input Area

Generated MML Command

LST BTS: LSTTYPE=BYBTSID,BTSID=2;


LST BTS: LSTTYPE=BYBTSID, BTSID=[4];


LST BTS: LSTTYPE=BYBTSID, BTSID=[1,3];

LST BTS: LSTTYPE=BYBTSID,BTSID=1;LST BTS: LSTTYPE=BYBTSID,BTSID=3;

LST BTS: LSTTYPE=BYBTSID, BTSID=[2,4,6];

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



4-11

Command Typed in the BatchProcessing Assistant Input Area

Generated MML Command

LST BTS: LSTTYPE=BYBTSID, BTSID=[1-4];

LST BTS: LSTTYPE=BYBTSID,BTSID=1;LST BTS: LSTTYPE=BYBTSID,BTSID=2;LST BTS: LSTTYPE=BYBTSID,BTSID=3;LST BTS: LSTTYPE=BYBTSID,BTSID=4;

LST BTS: LSTTYPE=BYBTSID, BTSID=[3-5];

LST BTS: LSTTYPE=BYBTSID,BTSID=3;LST BTS: LSTTYPE=BYBTSID,BTSID=4;LST BTS: LSTTYPE=BYBTSID,BTSID=5;

LST BTS: LSTTYPE=BYBTSID,BTSID=all;

LST BTS: LSTTYPE=BYBTSID,BTSID=1;LST BTS: LSTTYPE=BYBTSID,BTSID=2;LST BTS: LSTTYPE=BYBTSID,BTSID=3;LST BTS: LSTTYPE=BYBTSID,BTSID=4;LST BTS: LSTTYPE=BYBTSID,BTSID=5;LST BTS: LSTTYPE=BYBTSID,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. Thebatch processing assistant automatically checks the format of the command, the correctness ofthe parameters BTSID, CELLID, and TRXID, and the relationship between these parameters.

Step 3 If no error occurs, directly go to step Step 4. If an error occurs, a message is displayed. ClickOK, 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 commandto the editing area.

----End


LMT User Guide


Issue 07 (2011-01-30)

4.4 Setting MML ParametersYou can set the MML parameters as required.


ProcedureStep 1 Click Setting on the Common Maintenance tab page in the MML window. The MML

Setting dialog box is displayed, as shown in Figure 4-2.

Figure 4-2 Setting MML Parameters

Step 2 Set the parameters as required.

Step 3 Click OK to save the settings.

----End

4.5 Querying the Data Configuration ModeThis section describes how to determine if the data configuration mode of the subrack is effectiveor non-effective.


ContextIn effective mode, the data configured takes effect immediately on the subrack.



4-13

In non-effective mode, the data configured for the subrack takes effect only in the OMU anddoes not takes effect on the subrack. In this case, you can run the SETCFGDATAEFFECTIVE command to set the mode to effective mode, run the FMT DATAcommand to generate the data configuration file for the subrack, and then run the RSTSUBRACK command to reset the subrack. In this way, the subrack can load the dataconfiguration from the OMU to put the data changes into effect on the subrack.

When a subrack is in non-effective mode, you cannot query, compare, or perform CRC checkon the data between the host and the OMU. In addition, you cannot configure the host data ofthe subrack.

When all the subracks are in non-effective mode, license verification is not performed. When asubrack is switched from the non-effective mode to the effective mode, the OMU checks whetherthe data configuration exceeds the limitations of the license. If the data configuration exceedsthe limitations of the license, the mode switching is not allowed.

If the OMU is newly installed, subrack 0 is in non-effective mode by default. If a subrack isnewly added, it is in non-effective mode by default.

ContextYou can query the data configuration through menu operations or through MML commands.

Procedurel Through menu operations

1. On the main page of the LMT, check the configuration mode of a subrack from thedrop-down list on the tool bar, as shown in Figure 4-3.

Figure 4-3 Subrack data configuration mode

l Through MML commands

1. Run the LST CFGMODE command to check the current data configuration mode.

----End

4.6 Querying Data Configuration RightsThis section describes how to check the control status of the data configuration rights.

Prerequisite

You have logged in to the LMT.


LMT User Guide


Issue 07 (2011-01-30)

ContextYou can query the control status of the data configuration rights through menu operations orthrough MML commands.

If the result indicates that the control status of the data configuration rights is NULL, you caninfer that no one has the data configuration rights currently.


1. In the main page of the LMT, check the configuration mode of a subrack from thedrop-down list on the toolbar.

For example, Figure 4-4 indicates that all users have the data configuration rights.

Figure 4-4 All users enabled with the data configuration rights


1. Run the LST CMCTRL command to check the current control status of the dataconfiguration rights.

----End

4.7 Obtaining Data Configuration RightsYou need to obtain the data configuration rights to perform data configuration, undo/redooperations on the BSC6900 exclusively, or perform data configuration in batch without beingaffected by other users. Only the M2000 users and users of the following levels can obtain thedata configuration rights: admin, ADMINISTRATOR, OPERATOR, and CUSTOM entitled touse command group G_3 (for data configuration).

Prerequisitel You have logged in to the LMT.l You have set the control switch of the data configuration rights to ON by running the SET

CMCTRLSW command.

Contextl By default, the control switch of the data configuration rights is set to OFF. In this case, all

users can perform data configuration of the BSC6900 through the LMT or M2000.l When the control switch of the data configuration rights is ON, only one user has the data

configuration rights at a time.l After the data configuration is complete, you can release the data configuration rights by

running the REL CMCTRL command. In this way, another user can run the REQCMCTRL command to obtain the data configuration rights.



4-15

l If the user with the data configuration rights exits the LMT, the data configuration rightsare released automatically. In this case, another user can also run the REQ CMCTRLcommand to obtain the data configuration rights.

Procedure

Step 1 Check whether the data configuration rights are assigned to another user. For details, see 4.6Querying Data Configuration Rights.l If no user is currently assigned with the data configuration rights, go to Step 2.l If the data configuration rights are already assigned to another user, go to Step 2 after the

user releases the data configuration rights.

Step 2 Run the REQ CMCTRL command to obtain the data configuration rights.

Step 3 Check the CM control state from the drop-down list of the CM control state on the toolbar.Figure 4-5 shows that the data configuration rights are granted to the admin user.

Figure 4-5 Data configuration rights granted to the admin user

NOTE

l After the BSC6900 data configuration rights are already granted to one LMT user, other LMT userscannot obtain it. If you are the admin or ADMINISTRATOR-level user, you can run the FOCCMCTRL command to retrieve the data configuration rights.

l If an LMT user does not access the assigned BSC6900 data configuration rights exclusively, the rightswill be obtained automatically by the M2000 user during the BSC6900 maintenance through theM2000.

----End

4.8 Undoing/Redoing a Data Configuration ActionThis section describes how to undo and redo a single data configuration action.

Prerequisitel You have logged in to the LMT.l You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration

Rights), and have run multiple configuration commands successfully.l The quick configuration mode is disabled by running the SET QUICKCFG command.l No batch commands were performed.

Contextl 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


LMT User Guide


Issue 07 (2011-01-30)

operation of undoing or redoing a configuration action will decrease the efficiency ofrunning the MML commands.

l This function can be performed only with the exclusive operation rights to preventmisoperations.

l This function does not apply to all MML commands. If you run a command that does notsupport this function, the Undo and Redo buttons on the top of the LMT window becomesunavailable. In this case, the previous configuration operations that support this functioncannot be undone or redone. For the lists of commands that support undoing or redoing aconfiguration action, see the descriptions of the ADD ROLLBACKPOINT command.

l Undo a single configuration action: This operation is performed to undo a previousconfiguration action. It is applicable to the latest 10 effective configuration actions.

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

Procedurel Undoing a single configuration action

1. You can undo the latest configuration action in either of the following ways:

– Click Undo on the LMT toolbar.

– Run the BEG UNDO command.2. To undo multiple actions, repeat Step 1.

l Redoing a single configuration action1. 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 ActionsThis section describes how to undo and redo multiple data configuration actions.

Prerequisitel You have logged in to the LMT.l You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration

Rights), and have run multiple configuration commands successfully.l The quick configuration mode is disabled by running the SET QUICKCFG command.l No batch commands were performed.

Contextl 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 theoperation of undoing or redoing multiple configuration actions will decrease the efficiencyof running the MML commands.



4-17

l This function can be performed only with the exclusive operation rights to preventmisoperations.

l This function does not apply to all MML commands. If you run a command that does notsupport this function after you set the rollback point by running the ADDROLLBACKPOINT command, the rollback point is invalidated. That is, you cannot undomultiple configuration actions with the configured rollback point. In this case, you need toremove the configured rollback point and configure a new one. For the lists of commandsthat support undoing or redoing multiple configuration actions, see the descriptions of theADD ROLLBACKPOINT command.

l Undo multiple configuration actions: This operation is performed to undo multipleconfiguration actions that took effect after a specified rollback point. After the undooperation, the system rolls back to the configuration status at the specified rollback point.

l Redo multiple configuration actions: This operation is performed to redo the multipleconfiguration actions that were undone previously. Through this operation, you can rollback the system to the configuration at a specified rollback point or to the configurationbefore the multiple configuration actions were undone.

NOTE

The initial rollback point is the first rollback point set by the user. The final rollback point is setautomatically when the latest configuration command is successfully run. A maximum of 10,000configuration commands can be undone between the initial and final rollback points. If the system findsmore than 10,000 commands between the two rollback points, it does not undo the commands and reportsa failure message.

You can set a maximum of five rollback points. If you release the configuration rights, the OMU activework 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 ROLLBACKPOINTcommand 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


LMT User Guide


Issue 07 (2011-01-30)

5 Alarm Management

About This Chapter

This describes how to manage BSC6900 alarms through the LMT. Alarm management allowsyou to analyze alarms more efficiently and facilitates troubleshooting.

5.1 Concepts Related to Alarm ManagementThis section describes the basic concepts related to the alarm management, including the alarmtype, alarm severity, alarm-managed objects, and alarm box.

5.2 Managing Alarm LogsAlarm logs are used to record details of alarms. They are collected by the OMU and stored inthe OMU database. You need to establish limitations on the number and storage time of alarmlogs to minimize storage requirements on the hard drive.

5.3 Managing the Alarm FilterThis section describes how to filter one or more alarms. The alarms that meet the filteringconditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannotbe queried through the LMT or M2000. You can specify the conditions for filtering the alarmson the LMT.

5.4 Managing the Filter of Derived AlarmsA derived alarm is caused by a root fault. BSC6900 supports filtering of the derived alarms. Thederived alarms are not reported to the LMT by default. Unless otherwise specified, the derivedalarms are not saved on the OMU and cannot be queried through the LMT.

5.5 Monitoring AlarmsIn the Alarm Browse window of the LMT, you can monitor the alarm information sent to theLMT in real time.

5.6 Managing the Alarm BoxThe BSC6900 uses a universal alarm box of Huawei to provide audible and visual indicationswhen an alarm is reported.

BSC6900 GSMLMT User Guide 5 Alarm Management


5-1

5.1 Concepts Related to Alarm ManagementThis section describes the basic concepts related to the alarm management, including the alarmtype, alarm severity, alarm-managed objects, and alarm box.

5.1.1 Alarm TypeThe alarms in the BSC6900 system can be classified into fault alarms and event alarms.

5.1.2 Alarm SeverityThe BSC6900 alarm severity indicates the severity of a fault. The fault alarms and event alarmscan be classified into four severity levels: critical, major, minor, and warning.

5.1.3 Alarm-Managed ObjectsThe alarms can be classified into 10 types based on different managed objects.

5.1.4 Alarm BoxBSC6900 uses the Huawei universal alarm box. The BSC6900 alarm box provides audible andvisual indications based on the alarm severity. It is optional and the BSC6900 can be configuredwith only one alarm box. For details, see the documents delivered with the alarm box.

5.1.1 Alarm TypeThe alarms in the BSC6900 system can be classified into fault alarms and event alarms.

Table 5-1 describes the two types of alarms.

Table 5-1 Fault alarms and event alarms

Alarm Type Description

Fault alarm Alarms caused by hardware faults or the exceptions of major functions, forexample, board failure or link failure. Fault alarms are of higher severitythan event alarms. The fault alarms are classified into active and clearedalarms according to the fault status.

Event alarm Alarms of predefined events during the operation of the devices. The alarmreflects the system condition (for example, congestion) during a specificperiod, which is not necessarily a fault. Some event alarms are generatedrepeatedly and regularly. Event alarms cannot be classified into active andcleared alarms.

The fault alarms are classified into active and cleared alarms according to the fault status.

l Cleared alarm: If a fault is rectified, the corresponding alarm becomes a cleared alarm.

l Active alarm: If the fault is not rectified, the corresponding alarm is an active alarm.

For example, when congestion occurs in a cell, the system reports a fault alarm of cellcongestion. Before the congestion is cleared, the alarm remains active. After the congestion iscleared, the alarm is cleared.

5 Alarm ManagementBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

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 thecapacity of a base station is expanded, operations cause a great number of alarms to be reported. Thereis no special mechanism to handle such alarms. Large in number and short in existence period, thesealarms make real fault alarms inconspicuous and thus disturb normal network monitoring. To solvethe problem discussed above, Huawei puts forward the concept of "engineering alarms". With theconcept, 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 operatoris improved.

5.1.2 Alarm SeverityThe BSC6900 alarm severity indicates the severity of a fault. The fault alarms and event alarmscan be classified into four severity levels: critical, major, minor, and warning.

Table 5-2 describes the four severity levels of alarms.

Table 5-2 Alarm severity levels

Alarm Severity Definition HandlingRequirement

Critical alarm Reporting faults that affect the services providedby the system. These alarms need to be handledimmediately even during non-working hours. Forexample, some equipment or resource breaksdown.

Handle the faultsimmediately toavoid serviceoutage.

Major alarm Reporting faults that affect the Quality of Service(QoS). These alarms need to be handled duringworking hours. For example, the performance ofsome equipment or resource deteriorates.

Handle the faults intime. Otherwise, thesystem may fail toperform some majorfunctions.

Minor alarm Reporting faults that are not serious enough toaffect the QoS. These alarms can be handled asrequired or further observed to prevent them frombecoming critical. For example, you need clearthe obsolete history alarms.

Find and rectify anypotential fault intime.

Warning alarm Reporting faults that are potential threats to thesystem services. These alarms need to be handledaccording to specific situations. For example,OMU startup alarm.

Investigate theproblem andresolved as required.

5.1.3 Alarm-Managed ObjectsThe alarms can be classified into 10 types based on different managed objects.l Power system: alarms related to the power systeml Environment system: alarms related to the equipment room environment, such as

temperature, humidity, and door sensor



5-3

l Signaling system: alarms related to the signaling systeml Trunk system: alarms related to the trunk system, including trunk circuits and trunk boardsl Hardware system: alarms related to a board, such as clock and CPUl Software system: alarms related to the softwarel Operating system: alarms generated during the operation of the systeml Communication system: alarms related to the communication system, such as alarms

between the BSC6900 host and the OMUl QoS: alarms related to QoSl Processing error: alarms caused by other exceptions not listed above

5.1.4 Alarm BoxBSC6900 uses the Huawei universal alarm box. The BSC6900 alarm box provides audible andvisual indications based on the alarm severity. It is optional and the BSC6900 can be configuredwith only one alarm box. For details, see the documents delivered with the alarm box.

Figure 5-1 shows the alarm box.

Figure 5-1 Alarm box

When the BSC6900 reports a fault alarm to the LMT, the alarm box provides audible and visualindications based on the alarm severity. When the LMT receives the fault alarm, the alarm boxgenerates a sound. The sound stops when the alarm is cleared. You can also manually stop thesound on the LMT.

NOTE

The alarm box does not provide any indication for event alarms.


LMT User Guide


Issue 07 (2011-01-30)

5.2 Managing Alarm LogsAlarm logs are used to record details of alarms. They are collected by the OMU and stored inthe OMU database. You need to establish limitations on the number and storage time of alarmlogs to minimize storage requirements on the hard drive.

5.2.1 Setting Storage Conditions of Alarm LogsThis section describes how to set the maximum number of alarm logs and the time limitationsof the logs that can be stored in the OMU database. Only the admin, OPERATOR-level,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

5.2.2 Querying Storage Conditions of Alarm LogsThis section describes how to query the maximum number of alarm logs and the time limitationsof the logs that can be stored in the OMU database.

5.2.1 Setting Storage Conditions of Alarm LogsThis section describes how to set the maximum number of alarm logs and the time limitationsof the logs that can be stored in the OMU database. Only the admin, OPERATOR-level,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.


ProcedureStep 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 LogsThis section describes how to query the maximum number of alarm logs and the time limitationsof the logs that can be stored in the OMU database.


ProcedureStep 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 FilterThis section describes how to filter one or more alarms. The alarms that meet the filteringconditions are not reported to the LMT or M2000. That is, they are saved on the OMU but cannot



5-5

be queried through the LMT or M2000. You can specify the conditions for filtering the alarmson the LMT.

5.3.1 Creating an Alarm FilterThis section describes how to create an alarm filter. Only the admin, OPERATOR-level,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

5.3.2 Deleting an Alarm FilterIf you do not want to filter an alarm through the BSC6900, delete the filters related to this alarm.Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-levelusers can perform this operation.

5.3.3 Querying an Alarm FilterThis section describes how to query the specific alarm filtering conditions.

5.3.1 Creating an Alarm FilterThis section describes how to create an alarm filter. Only the admin, OPERATOR-level,ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

Prerequisite

You have logged in to the LMT with an account authorized for this operation.

Procedure

Step 1 Run the ADD OBJALMSHLD command to create an alarm filter. The successfully added alarmfilter takes effect immediately.

NOTE

l The name of the new alarm filter cannot be a duplicate of an existing one. Otherwise, the filter cannotbe created.

l A maximum of 100 alarm filters can be created in each BSC6900.

Step 2 Run the LST OBJALMSHLD command and enter the parameters to query whether the alarmfilter is successfully created.

----End

5.3.2 Deleting an Alarm FilterIf you do not want to filter an alarm through the BSC6900, delete the filters related to this alarm.Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-levelusers can perform this operation.

Prerequisite


Procedure

Step 1 Run the LST OBJALMSHLD command to check whether the alarm filter to be deleted exists.


LMT User Guide


Issue 07 (2011-01-30)

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 asrequired to delete an alarm filter.

----End

5.3.3 Querying an Alarm FilterThis section describes how to query the specific alarm filtering conditions.


Procedure

Step 1 Run the LST OBJALMSHLD command, and specify the Query Mode to query the alarmfiltering conditions.

----End

5.4 Managing the Filter of Derived AlarmsA derived alarm is caused by a root fault. BSC6900 supports filtering of the derived alarms. Thederived alarms are not reported to the LMT by default. Unless otherwise specified, the derivedalarms are not saved on the OMU and cannot be queried through the LMT.

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

5.4.2 Querying the Filter of Derived AlarmsThis section describes how to query the filter status of the BSC6900 derived alarms.

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

Prerequisitel You have logged in to the LMT with an account authorized for this operation.l You have obtained the data configuration rights (see 4.7 Obtaining Data Configuration

Rights).



5-7

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 AlarmsThis section describes how to query the filter status of the BSC6900 derived alarms.


Procedure

Step 1 Run the LST ALMML command to query the status of the alarm filter switch.

----End

5.5 Monitoring AlarmsIn the Alarm Browse window of the LMT, you can monitor the alarm information sent to theLMT in real time.

5.5.1 Browsing AlarmsThis describes how to browse the fault alarms and event alarms on the LMT. The alarminformation provides the running status of the system in real time.

5.5.2 Querying the Alarm LogThis section describes how to query alarm history from the OMU database. Using this function,you can review the past performance and condition of the system.

5.5.3 Querying Alarm Handling SuggestionsThis section describes how to query the handling suggestions of an alarm.

5.5.4 Querying Alarm ConfigurationThis section describes how to query the alarm configuration.

5.5.5 Filtering Fault AlarmsThis section describes how to filter alarms by sites and specific filter options in the BrowseAlarm tab page. Only the alarms that meet the specified requirements are displayed. All thealarms, however, are reported to the LMT and saved on the OMU.

5.5.6 Setting Alarm AttributesThis section describes how to set the display attributes of the alarms in the Alarm window.

5.5.7 Manually Clearing an AlarmThis section describes how to manually clear an alarm. If a reported alarm can be neglected orthe corresponding fault has been rectified, you can manually set the corresponding alarm as aclear alarm. Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorizedCUSTOM-level users can perform this operation.

5.5.8 Removing AlarmsThis section describes how to remove the alarms on the Browse Alarm or Query Alarm Logwindow.


LMT User Guide


Issue 07 (2011-01-30)

5.5.9 Refreshing the Alarm WindowThis section describes how to manually refresh the alarm information when you browse or querythe alarms.

5.5.1 Browsing AlarmsThis describes how to browse the fault alarms and event alarms on the LMT. The alarminformation provides the running status of the system in real time.


Procedure

Step 1 Click Alarm on the LMT main page to display the Browse Alarm tab page. The Fault,Event, and Engineering alarm tab pages are displayed under the Browse Alarm tab.

Step 2 Browse alarms in the Browse Alarm tab page.

Step 3 To view the details of an alarm, double-click it. The Detail dialog box carrying the detailedinformation about the alarm is displayed.

Step 4 To save an alarm, select corresponding entry, and click Save. Alternatively, right-click thecorresponding entry, and then choose Save Selected Records from the shortcut menu.

----End

5.5.2 Querying the Alarm LogThis 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.


ContextYou can set the following query conditions:l Alarm Typel Alarm Severityl Alarm Timel Special Alarm Flagl Return Amountl Select BTSl Alarm-Managed Objectsl Alarm IDl Alarm Serial No.

You can query the alarm logs through menu operations or through MML commands.



5-9


1. You can set the query conditions on the Query Alarm Log tab page under theAlarm tab.

2. Set the query parameters as required. To reset the query parameters, click Reset.3. Click Query. The query results are displayed in the Result area on the lower part of

the window.4. To learn more about an alarm, double-click it. The displayed Alarm Detailed

Information dialog box shows the details of the alarm.5. To save an alarm, select the corresponding entry, right-click it, and then choose Save

Selected Records from the shortcut menu.6. To save the queried records, click Save.

l Through MML commands1. Run the LST ALMLOG command to query the alarm logs.

----End

5.5.3 Querying Alarm Handling SuggestionsThis section describes how to query the handling suggestions of an alarm.


ContextThe LMT provides the following help information for all alarms:l Alarm meaningl Alarm impactl System actionl Solution

Procedure

Step 1 In the Alarm tab page, double-click an alarm in the Browse Alarm or Query Alarm Log tabpage. The Alarm Detailed Information dialog box is displayed.

Step 2 In the Alarm Detailed Information dialog box, click Solution.... The online help window isdisplayed.

NOTE

You can also right-click an alarm and choose Solution to view the online help of this alarm.

Step 3 Find the handling suggestions or other required information in the online help.

----End

5.5.4 Querying Alarm ConfigurationThis section describes how to query the alarm configuration.


LMT User Guide


Issue 07 (2011-01-30)

Prerequisite


Context

You can set the following query conditions:l Alarm IDl Alarm Severityl Modification Flagl Shield Flagl Return Amount

Procedure

Step 1 Set the query conditions in the Query Alarm Configuration page under the Alarm tab.

Step 2 Set the query conditions as required.

Step 3 Click Query. The query results are displayed in the Result area.

NOTE

If you need to modify the alarm settings, click Modify Alarm Configuration, or right-click the Resultarea and choose Modify Alarm Configuration from the shortcut menu.

----End

5.5.5 Filtering Fault AlarmsThis section describes how to filter alarms by sites and specific filter options in the BrowseAlarm tab page. Only the alarms that meet the specified requirements are displayed. All thealarms, however, are reported to the LMT and saved on the OMU.

Prerequisite


Procedure

Step 1 Click Alarm on the LMT main page. The Browse Alarm tab page is displayed.

Step 2 Click Filter Fault Alarm. The Set Alarm Filtering Conditions dialog box is displayed.

NOTE

The Set Alarm Filtering Conditions dialog box is displayed automatically, the first time you enter theFilter Fault Alarm tab page.

Step 3 In the Set Alarm Filtering Conditions dialog box, set the Alarm ID or Alarm Source. Then,click OK. The alarms that meet the specified requirements are displayed.

----End



5-11

5.5.6 Setting Alarm AttributesThis section describes how to set the display attributes of the alarms in the Alarm window.


ContextYou can set the following alarm attributes:l Set alarm colorsl Set alarm table columnsl Show/Hide tips

Procedure

Step 1 Click Setting on the upper right of the Alarm tab page to set the display attributes of the alarms.

----End

5.5.7 Manually Clearing an AlarmThis section describes how to manually clear an alarm. If a reported alarm can be neglected orthe corresponding fault has been rectified, you can manually set the corresponding alarm as aclear alarm. Only the admin, OPERATOR-level, ADMINISTRATOR-level, and authorizedCUSTOM-level users can perform this operation.


Procedure

Step 1 Run the RMV ALMFLT command to manually clear an alarm.

----End

5.5.8 Removing AlarmsThis section describes how to remove the alarms on the Browse Alarm or Query Alarm Logwindow.


Procedure

Step 1 In the Browse Alarm or Query Alarm Log tab page under the Alarm tab, click Delete AllClear Alarms or Delete All Alarms to delete the alarms as required. Table 5-3 describes thefunctions of the buttons.


LMT User Guide


Issue 07 (2011-01-30)

Table 5-3 Functions of the buttons

Option Description

Delete All Clear Alarms Deletes all the clear alarms in the active window. Available on theQuery Alarm Log tab page.

Delete All Alarms Deletes all alarms in the active window. Available on the BrowseAlarm or Query Alarm Log tab pages.

----End

5.5.9 Refreshing the Alarm WindowThis section describes how to manually refresh the alarm information when you browse or querythe alarms.


Procedure

Step 1 In the Browse Alarm tab page or Query Alarm Log tab page under the Alarm tab, clickRefresh or choose Refresh from the right-click menu to refresh the alarm information.

NOTE

l On the Browse Alarm tab page, the alarms are displayed in real time. Cleared alarms are displayed ingrey and new alarms are added as the window is automatically refreshed. When you refresh the windowmanually, the cleared alarms are removed from the Browse Alarm window.

l On the Query Alarm Log tab page, the alarms are not displayed in real time. When you manuallyrefresh the window, the alarms on the window are updated according to the previous queryingconditions.

----End

5.6 Managing the Alarm BoxThe BSC6900 uses a universal alarm box of Huawei to provide audible and visual indicationswhen an alarm is reported.

5.6.1 Querying Alarm Box InformationThis section describes how to query the version information of the alarm box and the activealarms that drive the alarm box.

5.6.2 Querying Number of Alarms with Different SeveritiesThis section describes how to query the number of alarms corresponding to a specific severityindicated by an alarm LED.

5.6.3 Operating the Alarm BoxThis section describes how to reset the alarm box, stop the alarm sound, and turn off the alarmLED.

5.6.4 Querying the Alarm Box Filter Level



5-13

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

5.6.1 Querying Alarm Box InformationThis section describes how to query the version information of the alarm box and the activealarms that drive the alarm box.

Prerequisitel You have logged in to the LMT.l The BSC6900 is connected to the alarm box.l The Convert Management System is started, and it communicates with the OMU normally.

Procedurel Run the LST BOXVER command to query the version information of the alarm box.l Run the LST BOXALM command to query the active alarms that drive the alarm box.

----End

5.6.2 Querying Number of Alarms with Different SeveritiesThis section describes how to query the number of alarms corresponding to a specific severityindicated by an alarm LED.

Prerequisitel You have logged in to the LMT.l The BSC6900 is connected to the alarm box.l The Convert Management System is started, and it communicates with the OMU normally.

ContextWhen the LMT receives one or more fault alarms from the BSC6900, the corresponding LEDon the alarm box flashes. The flashing LED, however, does not indicate the number of alarmsof 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 BoxThis section describes how to reset the alarm box, stop the alarm sound, and turn off the alarmLED.

Prerequisitel You have logged in to the LMT.


LMT User Guide


Issue 07 (2011-01-30)

l The BSC6900 is connected to the alarm box.l The Convert Management System is started, and it communicates with the OMU normally.

Procedurel Run the RST ALMBOX command to reset the alarm box.l Run the CLR BOXLGT to manually turn off the alarm LEDs.l Run the STP BOXSND command to stop the alarm sound.

----End

5.6.4 Querying the Alarm Box Filter LevelThis 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.

Prerequisitel You have logged in to the LMT.l The BSC6900 is connected to the alarm box.

ContextOnly the admin, OPERATOR-level, ADMINISTRATOR-level, and authorized CUSTOM-leveloperators can set alarm filter level.

Procedurel Run the LST ALMSCRN command to query the filter level on the alarm box.l Run the SET ALMSCRN command to set the filter level on the alarm box.

----End



5-15

6 Log Management

About This Chapter

This chapter describes how to manage the BSC6900 logs through the LMT. Log files can besaved in .txt and .log formats. Only the admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can manage the logs.

6.1 Log TypesThe logs are classified into operation logs, security logs, and running logs.

6.2 Querying Log Storage ConditionsThis section describes how to query the conditions for storing the operation logs and securitylogs, including the time limit and storage capacity of the logs.

6.3 Setting Log Storage ConditionsThis 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 anentry that has crossed the specified time limit or the earliest entry when the number of savedlogs exceeds the specified capacity.

6.4 Querying Operation LogsThis section describes how to query an operation log from the OMU database. By performingthis task, you can obtain information about the BSC6900 operations.

6.5 Exporting Operation LogsThis describes how to use the FTP Client to download to the LMT PC an exported operation logthat is saved in the directory OMU active workspace installation directory\ftp.

6.6 Querying Security LogsThis section describes how to query the security logs from the OMU database. By performingthis task, you can learn about the security events such as login, logout, and authorization in theBSC6900.

6.7 Exporting Security LogsThis section describes how to use the FTP Client to download to the LMT PC an exported securitylog that is saved in the directory OMU active workspace installation directory\ftp.

6.8 Exporting Running LogsThis section describes how to use the FTP Client to download to the LMT PC an exported runninglog that is saved in the bam\common\fam\famlog directory.

BSC6900 GSMLMT User Guide 6 Log Management


6-1

6.9 Collecting Log StatisticsThis section describes how to collect the log statistics to locate the fault. There are differenttypes of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMUinstallation logs, remote upgrade logs, and alarm logs.

6 Log ManagementBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

6.1 Log TypesThe logs are classified into operation logs, security logs, and running logs.

Operation LogThe BSC6900 operation log refers to all the real-time operation information recorded in theOMU database.

The operation log is mainly used to analyze the association between the device faults andoperations.

Security LogThe 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 LogThe running log refers to the system running information that the BSC6900 host records in realtime.

The running log is used for fault location, routine inspection, and device monitoring.

6.2 Querying Log Storage ConditionsThis section describes how to query the conditions for storing the operation logs and securitylogs, including the time limit and storage capacity of the logs.


ProcedureStep 1 Run the LST LOGLIMIT command to query the conditions for storing the logs.

----End

6.3 Setting Log Storage ConditionsThis 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 anentry that has crossed the specified time limit or the earliest entry when the number of savedlogs exceeds the specified capacity.




6-3

Procedure

Step 1 Run the SET LOGLIMIT command. Set the Time Limit and Counts Limit, and then choosea Log Type.

NOTE

l Time Limit ranges from 7 to 365 days and the default setting is 30 days.

l Counts Limit ranges from 10,000 to 50,000 entries, and the default setting is 50,000 entries.

----End

6.4 Querying Operation LogsThis section describes how to query an operation log from the OMU database. By performingthis task, you can obtain information about the BSC6900 operations.

Prerequisite


Procedure

Step 1 Run the LST OPTLOG command, and set the query parameters as required to query thecorresponding log information.

NOTE

If no query parameter is set, the LMT lists the latest 64 operation logs.

----End

6.5 Exporting Operation LogsThis describes how to use the FTP Client to download to the LMT PC an exported operation logthat is saved in the directory OMU active workspace installation directory\ftp.

Prerequisite


Procedure

Step 1 Run the EXP LOG command. Set Log Type to OPTLOG(Operating Log) and otherparameters as required to export the corresponding log information. When exporting operationlogs, you can name the file or use the default name provided by the system. The default nameof the exported file is MBSC-start time-end time-OLOG.txt.l If Time Mode is set to RELATIVE_T(Relative Time), the operation log within the latest

N hours is exported. N stands for the relative time length. For example, if Relative Time is72, then the log within the latest 72 hours is exported.

l If Time Mode is set to ONTIME(Fixed Time), the operation log within the absolute timeis exported. For example, Start Time for exporting the operation log is 2007-06-11 17:32:46


LMT User Guide


Issue 07 (2011-01-30)

and End Time is 2007-06-12 17:32:46. The default file name is MBSC-Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-OLOG.txt.

The default save path for the exported logs is OMU active workspace installation directory\FTP on the OMU active workspace.

Step 2 Choose Start > All Programs > Huawei Local Maintenance Terminal > FTP Client. TheFTP Client is started.

Step 3 In the server entry bar on the FTP Client, enter the external virtual IP address of the OMU, theFTP 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 bydefault.

Step 4 Click Enter to connect the OMU. The connecting status is displayed in the Connection tipspane.

Step 5 After the connection is successful, in the server file list pane, double-click OMU activeworkspace 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 FTPClient.

----End

6.6 Querying Security LogsThis section describes how to query the security logs from the OMU database. By performingthis task, you can learn about the security events such as login, logout, and authorization in theBSC6900.

Prerequisite


Procedure

Step 1 Run the LST SECLOG command, and set the query parameters as required to query the securitylogs.

NOTE

If no query parameter is set, the LMT lists the security logs of the current day.

----End

6.7 Exporting Security LogsThis section describes how to use the FTP Client to download to the LMT PC an exported securitylog that is saved in the directory OMU active workspace installation directory\ftp.



6-5

Prerequisite


Procedure

Step 1 Run the EXP LOG command. Set Log Type to SECLOG(SECURITY LOG) and otherrequirements as required to export the corresponding log information. When exporting thesecurity logs, you can name the file or use the default name provided by the system. The defaultname of the exported file is MBSC-start time-end time-SLOG.txt.

l If Time Mode is set to RELATIVE_T(Relative Time), the security log within the last Nhour(s) before the command is executed is exported. N stands for the relative time length.For example, if Relative Time is 72, then the log within the latest 72 hours is exported.

l If Time Mode is set to ONTIME(Fixed Time), the security log within the absolute time isexported. For example, Start Time for exporting the security log is 2007-06-11 17:32:46and End Time is 2007-06-12 17:32:46. The default file name is MBSC-Y2007M06D11H17N32S46-Y2007M06D12H17N32S46-SLOG.txt.

The default save path for the exported logs is OMU active workspace installation directory\FTP on the OMU active workspace.


Step 3 In the server entry bar on the FTP Client, enter the external virtual IP address of the OMU, theFTP user name, and the password.

NOTE



Step 5 After the connection is successful, in the server file list pane, double-click OMU activeworkspace installation directory\ftp. The server file list pane displays the files in the directory.

Step 6 Based on the file name, double-click the security log file to download it to the LMT PC.


----End

6.8 Exporting Running LogsThis section describes how to use the FTP Client to download to the LMT PC an exported runninglog that is saved in the bam\common\fam\famlog directory.

Prerequisite



LMT User Guide


Issue 07 (2011-01-30)

Procedure

Step 1 Run the ULD LOGTOOMU command. Enter the subrack number, and export thecorresponding log information.

NOTE

l The format of the file name is subrack number/Log/yyyy/mm/dd/hh/mm/ss.log. For example, forthe running log of the No. 3 EPS that is uploaded to the OMU at 2008-11-07 17:19:47, the file nameis 03Log20081107171947.log.

l By default, the uploaded running logs are saved in the bam\common\fam\famlog directory.


Step 3 In the server entry bar on the FTP Client, enter the external virtual IP address of the OMU, theuser name, and the password.

NOTE



Step 5 After the connection is successful, in the server file list pane, double-click bam\common\fam\famlog. The server file list pane displays the files in the directory.

Step 6 Based on the file name, double-click the running log file to download it to the LMT PC.


----End

6.9 Collecting Log StatisticsThis section describes how to collect the log statistics to locate the fault. There are differenttypes of logs: host logs, OMU logs, database logs, system event logs, operation logs, OMUinstallation logs, remote upgrade logs, and alarm logs.


Procedure

Step 1 Run the COL LOG command. Set the required parameters to collect the corresponding logstatistics.

----End



6-7

7 Trace Management

About This Chapter

This chapter describes how to manage message tracing on the BSC6900. A maximum of 64 tracetasks can be performed simultaneously on the same LMT.

7.1 Concepts Related to Trace ManagementTrace management is performed during routine maintenance of equipment, and traces messageson interfaces and signaling links to verify data and locate faults. Do not start excessive tracingtasks when traffic is high, as it slows the LMT responses. In this case, set Trace Mode to SaveTo OMU before beginning a tracing task.

7.2 GSM ServicesThis section describes how to perform tracing tasks related to GSM services.

7.3 Basic Tracing OperationsThe basic operations of message tracing apply to all the BSC6900 message tracing tasks.

BSC6900 GSMLMT User Guide 7 Trace Management


7-1

7.1 Concepts Related to Trace ManagementTrace management is performed during routine maintenance of equipment, and traces messageson interfaces and signaling links to verify data and locate faults. Do not start excessive tracingtasks when traffic is high, as it slows the LMT responses. In this case, set Trace Mode to SaveTo OMU before beginning a tracing task.

7.1.1 Trace PrinciplesThis describes the principles of message tracing. It also describes how to create or close messagetracing tasks and the internal process for the service module to report traced messages to theLMT.

7.1.2 Management of Tracing Operation RightsYou must have the relevant rights to perform message tracing operations.

7.1.3 Trace ModeThis section describes trace modes of signaling tracing on an interface on a BSC LMT. Tracemodes determine where to save results of signaling tracing and knowledge of trace modesfacilitates finding of tracing results.

7.1.1 Trace PrinciplesThis describes the principles of message tracing. It also describes how to create or close messagetracing tasks and the internal process for the service module to report traced messages to theLMT.

Principles of the Message TracingFigure 7-1 shows the principles of the message tracing.

Figure 7-1 Principles of the message tracing

Internal Procedure for Creating a Tracing Task1. 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.

7 Trace ManagementBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

3. After receiving the command, the debugging module records the filter parameters of thetrace data in the filter table and notifies the service module.

4. The service module updates the local filter table according to the message from thedebugging module.

Internal Procedure for Closing a Tracing Task1. When you close a tracing task on the LMT, the LMT sends a binary command to the OMU

to delete the task.2. The OMU forwards the command to the specified board according to the task ID.3. The debugging module and service module delete the task from the filter table.

Internal Procedure for the Service Module to Report Traced Messages to the LMT1. 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 RightsYou 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 touse command group G_10 can perform the tracing tasks online.

NOTE

Group G_10 consists of binary commands for creating tracing and monitoring tasks.

7.1.3 Trace ModeThis section describes trace modes of signaling tracing on an interface on a BSC LMT. Tracemodes determine where to save results of signaling tracing and knowledge of trace modesfacilitates finding of tracing results.

The trace modes of signaling tracing on an interface are divided into the following two types:

l ReportIn this mode, the trace results are reported in real time. The OMU sends the traced messagesto an LMT PC directly, and the output file is automatically saved to the LMT PC in the*.tmf format.

l Save to OMUIn this mode, you can set the trace interval. The traced messages are saved on the OMUand are not reported to the LMT PC. The output file is saved to the OMU in the *.tmfformat. The default path is \mbsc\bam\common\fam\trace directory of the OMU.

You can view tracing results saved on the OMU by referring to Browsing Traced MessagesOffline.



7-3

7.2 GSM ServicesThis section describes how to perform tracing tasks related to GSM services.

7.2.1 Tracing Messages on the A InterfaceThe A interface is the interface between a BSC6900 and an MSC. This section describes howto trace the BSSAP, MTP2, MTP3, SCCP, SCTP, and M3UA messages on the A interface. Youcan perform this task to locate a fault in the following scenarios: timeslot assignment failure,abnormal releases, location update failure, and handover failure.

7.2.2 Tracing CS Domain Messages on the Um InterfaceThe Um interface is the interface between a BTS and MSs. This section describes how to tracethe 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.

7.2.3 Tracing PS Domain Messages on the Um InterfaceThe Um interface is the interface between a BTS and MSs. This section describes how to tracePS domain messages on the Um Interface, including the DUMMY messages, system informationmessages, null paging messages, and data block messages. You can perform this task to locatea fault when PS assignment failure and abnormal TBF release occur.

7.2.4 Tracing Messages on the Cb InterfaceThe Cb interface is the interface between a BSC and a CBC. This section describes how to tracesignaling messages on the Cb interface. You can perform this task to locate a fault in thefollowing scenarios: message query failure, BIND failure, and SOCKET connection failure.

7.2.5 Tracing Group Call MessagesThis section describes how to trace messages of Voice Group Call Service (VGCS) and VoiceBroadcast Service (VBS) on the A, Abis, or Um interface. You can perform this task to locatea fault in the following scenarios: timeslot assignment failure, call termination rejection, or callsetup rejection.

7.2.6 Tracing Messages on the Inter-BSC InterfaceThis section describes how to trace common measurement messages or message interactions onthe inter-BSC interface. You can perform this task to locate a fault during the commonmeasurement procedures such as initialization request failure or common measurementindication failure.

7.2.7 Tracing CS Domain Messages on the Abis InterfaceThe Abis interface is the interface between a BSC6900 and a BTS. This section describes howto trace RSL, ESL, EML, OML, and LAPD messages in the CS domain over the 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.

7.2.8 Tracing PS Domain Messages on the Abis InterfaceThe Abis interface is the interface between a BSC6900 and a BTS. This section describes howto trace the PS domain messages on the Abis interface, based on cells or TRXs. You can performthis task to locate a fault in the PS domain channel failure.

7.2.9 Tracing PTP Messages on the Gb InterfaceThe Gb interface is the interface between a BSC6900 and an SGSN. This section describes howto trace the point to point (PTP) messages on the Gb interface by the NSEI or BVCI. You canperform this task to locate a fault in the following scenarios: attach rejection, PDP contextactivation rejection, and PS packet loss or disconnection.


LMT User Guide


Issue 07 (2011-01-30)

7.2.10 Tracing SIG Messages on the Gb InterfaceThe Gb interface is the interface between a BSC6900 and an SGSN. This section describes howto trace signaling messages on the Gb interface by the NSEI. You can perform this task to locatea fault in the PS domain in the case of a SIG BVC failure or abnormal PTP status.

7.2.11 Tracing CS Domain Messages of a Single SubscriberThis section describes how to trace signaling messages on the A/Abis/Um interface of a specifiedsubscriber. The user can be specified by the IMSI, IMEI, TMSI, MSISDN, CELLID, or channel.

7.2.12 Tracing PS Domain Messages of a Single SubscriberThis 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 thesubscriber by the IMSI or TLLI. You can perform this task to locate a fault in the PS domain inthe following procedures: PS service channel assignment failure, abnormal TBF release, and PSpacket loss or disconnection.

7.2.13 Tracing CS Domain Messages on the Ater InterfaceThis section describes how to trace signaling messages on the Ater interface. When the TCsubrack is configured on the MSC side, the BM subrack communicates with the TC subrack onthe Ater interface.

7.2.14 Tracing Messages on the Pb InterfaceThe Pb interface is the interface between a BSC6900 and a PCU. This section describes how totrace the messages on the Pb interface You can perform this task to locate the cause of theabnormal cell status or PS channel fault when the external PCU is configured.

7.2.15 Tracing BTS Signaling MessagesThis section describes how to trace and analyze BTS signaling messages (from both CS and PSdomains) within a TRX.

7.2.16 Tracing Messages on the LB InterfaceThe LB interface is the interface between a BSC6900 and a SMLC(Serving Mobile LocationCenter). This section describes how to trace the BSSAP-LE, MTP2, MTP3, SCCP, SCTP, andM3UA messages on the LB interface. You can perform this task to locate a fault in the followingscenarios: timeslot assignment failure, abnormal releases, location update failure, and handoverfailure.

7.2.1 Tracing Messages on the A InterfaceThe A interface is the interface between a BSC6900 and an MSC. This section describes howto trace the BSSAP, MTP2, MTP3, SCCP, SCTP, and M3UA messages on the A interface. Youcan perform this task to locate a fault in the following scenarios: timeslot assignment failure,abnormal releases, location update failure, and handover failure.


l The communication between the BSC6900 and the MSC is normal.

Context

You can start this task on the LMT to monitor the interworking of signaling messages over theA interface.

To start a tracing task, you can select the following operations:



7-5

l Tracing the messages processed by a specified CPUS subsysteml Tracing a specific type of messages (all being signaling messages at the transport network

layer, except BSSAP messages)

Tracing BSSAP Messages on the A InterfaceThis section describes how to trace Base Station Subsystem Application Part (BSSAP) messagesby site on the A interface through the LMT. BSSAP messages include BSSMAP, DTAP, paging,and other messages.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.

Procedure

Step 1 Click Trace on the LMT main page. The Trace tab page is displayed.

Step 2 On Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace. Accordingly,the A Interface Trace dialog box is displayed, as shown in Figure 7-2.

Figure 7-2 Message tracing on the A interface

Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP 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 Trace Mode.

Step 4 In the BSSAP tab page, set parameters under Message Type and Cell.


LMT User Guide


Issue 07 (2011-01-30)

NOTE

l Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.

Step 5 Click Submit.

----End

Resultl Successful operation

– No traced message is displayed on the LMT if the Save to OMU trace mode is selected.You can view the tracing result saved on the OMU by referring to Browsing TracedMessages Offline.

– A window shown in Figure 7-3 is displayed if the Report trace mode is selected. Themessage browsing window displays information about each traced message, includingthe task number, task time, RFN, subrack number, slot number, subsystem number,message direction, message type, message source, user ID, and message content.

Figure 7-3 Results of BSSAP message tracing on the A interface

l If the tracing fails, a dialog box is displayed with the failure cause.

Follow-up Procedurel You can double-click a result in the displayed result area to view the detailed information

about the traced message.

l You can perform required operations by referring to 7.3 Basic Tracing Operations.

Tracing SCCP Messages on the A Interface

This section describes how to trace SCCP messages on the A interface through the LMT.


l The communication between the BSC6900 and the BTS is normal.



7-7

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > A Interface Trace.Accordingly, the A Interface Trace dialog box is displayed, as shown in Figure 7-4.


Step 3 In the A Interface Trace dialog box, set parameters in the Basic tab page and select SCTPunder Trace Type.

l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LSTN7DPC command.

l For description of Trace Mode, see 7.1.3 Trace Mode.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-5 Results of SCTP message tracing on the A interface



about the traced message.l You can perform required operations by referring to 7.3 Basic Tracing Operations.

Tracing MTP3 Messages on the A InterfaceThis section describes how to trace Message Transfer Part Level 3 (MTP3) messages on the Ainterface through the LMT. MTP3 messages include SNM, SLT, and DATA messages.


Procedure





7-9


Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and selectMTP3 under Trace Type.l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST


Step 4 In the MTP3 tab page, set parameters under Message Type.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-7 Results of MTP3 message tracing on the A interface




Tracing MTP2 Messages on the A InterfaceThis section describes how to trace Message Transfer Part Level 2 (MTP2) messages by subrack,slot, and link numbers on the A interface through the LMT. MTP2 messages include LSSU andMSU messages.


Procedure





7-11


Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and selectMTP2 under Trace Type.l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST


Step 4 In the MTP2 tab page, set parameters under Message Type and Position.

NOTE

l Subrack No., Slot No.: respectively indicate the number of the subrack and slot that house an A interfaceboard. They can be queried by selecting Display Logic Function on the BSC Device Panel.

l Link No.: You can query it by running the LST MTP3LKS command.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-9 Results of MTP2 message tracing on the A interface




Tracing SCTP Messages on the A InterfaceThis section describes how to trace SCTP signaling messages on the A interface in A over IPmode through the LMT. The tracing is performed by subrack, slot, CPU, and link numbers.SCTP messages include control, DATA, and heartbeat messages.


Procedure





7-13


Step 3 In the A Interface Trace dialog box, set parameters in Basic and select SCTP in TraceType.l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST


Step 4 In the SCTP tab page, set parameters under SCTP Message and Parameter Configuration.

NOTE

l SCTP Link No.: query it by running the LST SCTPLNK command.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-11 Results of SCTP message tracing on the A interface




Tracing M3UA Messages on the A InterfaceThis section describes how to trace M3UA signaling messages on the A interface in A over IPmode through the LMT. The tracing is performed by link or link set number. M3UA messagesinclude management messages, transmission messages, SS7 management messages, ASPservice maintenance messages, ASP status maintenance messages, and route selected keywordmessages.


Procedure





7-15


Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and selectM3UA under Trace Type.l DPC (HEX): indicates the destination signaling point to be traced. To query the DPC, run

the LST N7DPC command.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 In the M3UA tab page, set parameters under M3UA Message and Parameter Configuration.

NOTE

l Link Set No.: indicates the number of an M3UA link set. To query it, run the LST M3LKS command.

l Link No.: indicates the number of an M3UA link. To query it, run the LST M3LNK command.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-13 Results of M3UA message tracing on the A interface





7.2.2 Tracing CS Domain Messages on the Um InterfaceThe Um interface is the interface between a BTS and MSs. This section describes how to tracethe 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.



Context

You can start this task on the LMT to monitor the interworking of signaling messages over theUm interface.

To start a tracing task, you can select the following operations:

l Tracing by the cell or TRX

l Tracing the required types of message

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Um Interface CSTrace. The Um Interface CS Trace dialog box is displayed, as shown in Figure 7-14.



7-17

Figure 7-14 CS domain message tracing on the Um interface

Step 3 In the Um Interface CS Trace dialog box, set the parameters as required.

l Filter Flag can be set to Cell or TRX. When Cell is selected, you can set the cell to be tracedby specifying Cell ID. When TRX is selected, you can set the cell to be traced by specifyingTRX ID.


l TRX ID: indicates the number of a TRX. You can query it by running the LST GTRXcommand.



----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-15 Results of CS domain message tracing on the Um interface




7.2.3 Tracing PS Domain Messages on the Um InterfaceThe Um interface is the interface between a BTS and MSs. This section describes how to tracePS domain messages on the Um Interface, including the DUMMY messages, system informationmessages, null paging messages, and data block messages. You can perform this task to locatea fault when PS assignment failure and abnormal TBF release occur.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the SGSN is normal.l The communication between the BSC6900 and the BTS is normal.

ContextA 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 PSTrace. The Um Interface PS Trace dialog box is displayed, as shown in Figure 7-16.



7-19

Figure 7-16 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 cell to be traced byspecifying TRX ID.

l Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.l TRX ID: indicates the number of a TRX. You can query it by running the LST GTRX

command.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End





LMT User Guide


Issue 07 (2011-01-30)

Figure 7-17 Results of PS domain message tracing on the Um interface




7.2.4 Tracing Messages on the Cb InterfaceThe Cb interface is the interface between a BSC and a CBC. This section describes how to tracesignaling messages on the Cb interface. You can perform this task to locate a fault in thefollowing scenarios: message query failure, BIND failure, and SOCKET connection failure.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the CBC is normal.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Cb InterfaceTrace. The Cb Interface Trace dialog box is displayed, as shown in Figure 7-18.



7-21

Figure 7-18 Message tracing on the Cb interface

Step 3 In the Cb interface Trace dialog box, set the parameters as required.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End



– A window is displayed if the Report trace mode is selected. The message browsingwindow displays information about each traced message, including the task number,task time, RFN, subrack number, slot number, subsystem number, message direction,message type, message source, user ID, and message content.




7.2.5 Tracing Group Call MessagesThis section describes how to trace messages of Voice Group Call Service (VGCS) and VoiceBroadcast Service (VBS) on the A, Abis, or Um interface. You can perform this task to locate


LMT User Guide


Issue 07 (2011-01-30)

a fault in the following scenarios: timeslot assignment failure, call termination rejection, or callsetup rejection.

Prerequisitel You have logged in to the LMT.l Group call services are performed in the test network.

ContextGroup call services include the voice group call services (VGCS) and voice broadcast services(VBS).

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Group CallTrace. The Group Call Trace dialog box is displayed, as shown in Figure 7-19.

Figure 7-19 Group call message tracing

Step 3 In the Group Call Trace dialog box, set the parameters as required.l Group Call Number: indicates the group call number to be specifiedl For description of Trace Mode, see 7.1.3 Trace Mode.


----End



7-23







7.2.6 Tracing Messages on the Inter-BSC InterfaceThis section describes how to trace common measurement messages or message interactions onthe inter-BSC interface. You can perform this task to locate a fault during the commonmeasurement procedures such as initialization request failure or common measurementindication failure.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and other BSCs is normal.

ProcedureStep 1 Click Trace on the LMT main page. The Trace tab page is displayed.

Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BSC Trace. TheBSC Trace dialog box is displayed, as shown in Figure 7-20.

Figure 7-20 Message tracing on the inter-BSC interface


LMT User Guide


Issue 07 (2011-01-30)

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


Step 4 Click Submit. View the traced message flow in the message browsing window.

----End







7.2.7 Tracing CS Domain Messages on the Abis InterfaceThe Abis interface is the interface between a BSC6900 and a BTS. This section describes howto trace RSL, ESL, EML, OML, and LAPD messages in the CS domain over the 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.


ContextIf you select LAPD as the trace type are in the Basic tab page, the signaling messages over theAbis 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 performedsimultaneously.

Tracing CS Domain RSL Messages on the Abis InterfaceThis section describes how to trace Radio Signaling Link (RSL) messages on the Abis interfacethrough the LMT. RSL messages present the interactive call signaling procedure between the



7-25

BSC and the BTS. Tracing RSL messages is an important way of tracing a call process. RSLmessages include measurement reports, channel request messages, paging messages, RLMmessages, and TRXM messages.


Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Abis InterfaceCS Trace. The Abis Interface CS Trace dialog box is displayed, as shown in Figure 7-21.

Figure 7-21 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 andselect RSL under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

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. Toquery 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 queryit, run the LST GCELL command.


----End


LMT User Guide


Issue 07 (2011-01-30)




Figure 7-22 Results of RSL message tracing on the Abis interface





Tracing CS Domain ESL Messages on the Abis Interface

This section describes how to trace Extend Signaling Link (ESL) messages by site on the Abisinterface through the LMT. ESL messages include public messages and operation andmaintenance messages.



Procedure





7-27


Step 3 In the displayed Abis Interface CS Trace dialog box, set parameters in the Basic tab page andselect ESL under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

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




Figure 7-24 Results of ESL message tracing on the Abis interface


LMT User Guide


Issue 07 (2011-01-30)




Tracing CS Domain EML Messages on the Abis InterfaceThis section describes how to trace Extend Maintenance Link (ESL) messages by site on theAbis interface through the LMT. ESL messages include public messages and operation andmaintenance messages.


Procedure




Step 3 In the displayed Abis Interface CS Trace dialog box, set parameters in the Basic tab page andselect EML under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.



7-29

Step 4 In the EML 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




Figure 7-26 Results of EML message tracing on the Abis interface




Tracing CS Domain OML Messages on the Abis InterfaceThis section describes how to trace operation and maintenance link (OML) messages by site onthe Abis interface through the LMT. OML messages include public messages and operation andmaintenance messages.



LMT User Guide


Issue 07 (2011-01-30)


Procedure




Step 3 In the displayed Abis Interface CS Trace dialog box, set parameters in the Basic tab page andselect OML under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 In the OML 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






7-31

Figure 7-28 Results of OML message tracing on the Abis interface




Tracing CS Domain LAPD Messages on the Abis InterfaceThis section describes how to trace Link Access Procedure on the D channel (LAPD) messageson the Abis interface through the LMT. LAPD links include RSL, EML, OML, and ESL. Thetracing can be performed by site or TRX.


Procedure




LMT User Guide


Issue 07 (2011-01-30)


Step 3 In the displayed Abis Interface CS Trace dialog box, set parameters in the Basic tab page andselect LAPD under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 In the LAPD 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.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 queryresult. 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.


----End






7-33

Figure 7-30 Results of LAPD message tracing on the Abis interface




7.2.8 Tracing PS Domain Messages on the Abis InterfaceThe Abis interface is the interface between a BSC6900 and a BTS. This section describes howto trace the PS domain messages on the Abis interface, based on cells or TRXs. You can performthis task to locate a fault in the PS domain channel failure.


ContextA maximum of five tasks, of tracing the PS messages on the Abis interface, can be startedsimultaneously.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Abis InterfacePS Trace. The Abis Interface PS Trace dialog box is displayed, as shown in Figure 7-31.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-31 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 queriedby running the LST GCELL command.

l When the TRX-TN message type is selected, you need to specify TRX ID and TimeslotNo.. They can be queried by running the LST GTRX command. The timeslot number is theone corresponding to the PDCH.

l Report Mode: indicates the message report mode. When MAC Report is selected, messagesare 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






7-35

Figure 7-32 Results of PS domain message tracing on the Abis interface





7.2.9 Tracing PTP Messages on the Gb InterfaceThe Gb interface is the interface between a BSC6900 and an SGSN. This section describes howto trace the point to point (PTP) messages on the Gb interface by the NSEI or BVCI. You canperform this task to locate a fault in the following scenarios: attach rejection, PDP contextactivation rejection, and PS packet loss or disconnection.


l The communication between the BSC6900 and the SGSN is normal.

l The NSE has been configured, and the cell has been bound with the BVC(s).

Context

A maximum of five tasks, of tracing the PTP messages on the Gb interface, can be startedsimultaneously.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Gb Interface PTPTrace. The Gb Interface PTP Trace dialog box is displayed, as shown in Figure 7-33.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-33 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 queriedby running the LST PTPBVC command.



----End






7-37

Figure 7-34 Results of PTP message tracing on the Gb interface





7.2.10 Tracing SIG Messages on the Gb InterfaceThe Gb interface is the interface between a BSC6900 and an SGSN. This section describes howto trace signaling messages on the Gb interface by the NSEI. You can perform this task to locatea fault in the PS domain in the case of a SIG BVC failure or abnormal PTP status.


l The communication between the BSC6900 and the SGSN is normal.

l The NSEI has been configured.

Context

A maximum of six tasks, of tracing the SIG messages on the Gb interface, can be startedsimultaneously.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Gb Interface SIGTrace. The Gb Interface SIG Trace dialog box is displayed, as shown in Figure 7-35.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-35 SIG message tracing on the Gb interface

Step 3 In the Gb Interface SIG Trace dialog box, set the parameters as required.l NSEI: is NSE identifier. It can be queried by running the LST NSE command.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End




Figure 7-36 Results of SIG message tracing on the Gb interface






7-39

7.2.11 Tracing CS Domain Messages of a Single SubscriberThis section describes how to trace signaling messages on the A/Abis/Um interface of a specifiedsubscriber. The user can be specified by the IMSI, IMEI, TMSI, MSISDN, CELLID, or channel.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.l The communication between the BSC6900 and the MSC is normal.

ContextA maximum of 16 tasks, of tracing the CS messages of a single subscriber, can be startedsimultaneously.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Single User CSTrace. The Single User CS Trace dialog box is displayed, as shown in Figure 7-37.

Figure 7-37 CS domain message tracing of a single subscriber

Step 3 In the Single User CS Trace dialog box, set the parameters as required.l CDT Mode: If you select the CDT mode, you can trace interfaces between internal modules.l Debug Mode: If you select the debug mode, you can trace stream data in Abis over IP, Ater

over IP, and A over IP scenarios. Interface boards need to be selected in the Other tab page.l Location Flag: indicates information such as cell ID and TA.


LMT User Guide


Issue 07 (2011-01-30)

NOTE

l If you trace the user messages through the MSISDN, you are advised to set the MSISDN to that of thepeer 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 calledMS. For example, if 54321 is displayed on the called MS, set the MSISDN to 54321.

l If you trace the user messages by the TMSI or IMSI, you must check the reassignment policies on theMSC side:

l If TMSI is carried, you can trace the MS through the TMSI.

l If IMSI is carried, you can trace the MS through the IMSI.

l If you trace the user messages by the IMEI, you must check whether the IMEI is available to the MSC.

l If you trace the user messages by the CELLID, all calls in the cell are traced.

l If you trace the user messages by the CHANINFO, the call carried by the specific channel is traced.


----End




Figure 7-38 Results of CS domain message tracing of a single subscriber






7-41


7.2.12 Tracing PS Domain Messages of a Single SubscriberThis 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 thesubscriber by the IMSI or TLLI. You can perform this task to locate a fault in the PS domain inthe following procedures: PS service channel assignment failure, abnormal TBF release, and PSpacket loss or disconnection.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.l The communication between the BSC6900 and the SGSN is normal.

ContextA maximum of five tasks, of tracing the PS messages of a single subscriber, can be startedsimultaneously.

Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Single User PSTrace. The Single User PS Trace dialog box is displayed, as shown in Figure 7-39.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-39 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 tothe MS. In this case, run this command to query the new TLLI for the tracing operation.

l Report Mode: indicates the message report mode. When Trace Um Datablock Message isselected, Um datablock messages are reported. When MAC Report is selected, messagesare 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




7-43



Figure 7-40 Results of PS domain message tracing of a single subscriber





7.2.13 Tracing CS Domain Messages on the Ater InterfaceThis section describes how to trace signaling messages on the Ater interface. When the TCsubrack is configured on the MSC side, the BM subrack communicates with the TC subrack onthe Ater interface.



Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click Ater InterfaceCS Trace. The Ater Interface CS Trace dialog box is displayed, as shown in Figure 7-41.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-41 CS domain message tracing on the Ater interface

Step 3 In the Ater Interface CS Trace dialog box, set the parameters as required.l Ater Signaling Channel ID: indicates the number of the Ater signaling link. It can be queried

by running the LST ATERSL command.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End




Figure 7-42 Results of CS domain message tracing on the Ater interface



7-45




7.2.14 Tracing Messages on the Pb InterfaceThe Pb interface is the interface between a BSC6900 and a PCU. This section describes how totrace the messages on the Pb interface You can perform this task to locate the cause of theabnormal cell status or PS channel fault when the external PCU is configured.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the PCU is normal.l The external PCU is configured.

ContextA maximum of 16 Pb interface tracing tasks can be started simultaneously.

Tracing Application Messages on the Pb InterfaceThis section describes how to trace signaling messages related to application by cell on the Pbinterface through the LMT. The messages include paging, chaos, PCIC check, and othermessages.


Procedure


Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > Pb Interface Trace. The PbInterface Trace dialog box is displayed, as shown in Figure 7-43.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-43 Message tracing on the Pb interface

Step 3 In the displayed Pb Interface Trace dialog box, set parameters in the Basic tab page and selectApplication under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 In the Application tab page, set parameters under PCU Number, Message Type and Cells.l PCU Number: it can be queried by running the LST PCU command.l Cell ID: indicates the index of a cell. To query it, run the LST GCELL command.


----End






7-47

Figure 7-44 Results of Application domain message tracing on the Pb interface

–




Tracing LAPD Messages on the Pb InterfaceThis section describes how to trace LAPD messages by link on the Pb interface through theLMT.


Procedure


Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > Pb Interface Trace. The PbInterface Trace dialog box is displayed, as shown in Figure 7-45.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-45 Message tracing on the Pb interface

Step 3 In the displayed Pb Interface Trace dialog box, set parameters in the Basic tab page and selectLAPD under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 Set parameters in the LAPD tab page.l When Selection Mode is set to Location, you need to specify Subrack No., Slot No., Port

No., and Timeslot No. one by one. Subrack No. and Slot No. are respectively the numberof the subrack and slot that house a Pb signaling link board. Port No. and Timeslot No. arerespectively the number of a Pb signaling link port and timeslot.

l Pbsl No.: indicates the number of a Pb signaling link. To query it, run the LST PBSLcommand.


----End






7-49

Figure 7-46 Results of LAPD domain message tracing on the Pb interface




7.2.15 Tracing BTS Signaling MessagesThis section describes how to trace and analyze BTS signaling messages (from both CS and PSdomains) within a TRX.


ContextA maximum of 16 tracing tasks, of the BTS signaling messages, can be started simultaneously.

Tracing LAPDm Messages Through BTS Signaling TraceThis section describes how to trace LAPDm messages within a TRX by TRX or timeslot numberthrough BTS signaling trace.


Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BTS SignalingTrace. The BTS Signaling Trace dialog box is displayed, as shown in Figure 7-47.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-47 BTS signaling trace

Step 3 In the displayed BTS Signaling Trace dialog box, set parameters in the Basic tab page andselect LAPDm under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

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.


----End






7-51

Figure 7-48 Results of LAPDm message tracing through BTS signaling trace




Tracing RLC/MAC Messages Through BTS Signaling TraceThis section describes how to trace RLC/MAC messages within a TRX by TRX or timeslotnumber through BTS signaling trace on the LMT.


Procedure


Step 2 Unfold Trace > GSM Services under Trace Navigation Tree. Double-click BTS SignalingTrace. The BTS Signaling Trace dialog box is displayed, as shown in Figure 7-49.


LMT User Guide


Issue 07 (2011-01-30)

Figure 7-49 BTS signaling trace

Step 3 In the displayed BTS Signaling Trace dialog box, set parameters in the Basic tab page andselect RLC/MAC under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.

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






7-53

Figure 7-50 Results of RLC/MAC message tracing through BTS signaling trace




7.2.16 Tracing Messages on the LB InterfaceThe LB interface is the interface between a BSC6900 and a SMLC(Serving Mobile LocationCenter). This section describes how to trace the BSSAP-LE, MTP2, MTP3, SCCP, SCTP, andM3UA messages on the LB interface. You can perform this task to locate a fault in the followingscenarios: timeslot assignment failure, abnormal releases, location update failure, and handoverfailure.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.

ContextYou can start this task on the LMT to monitor the interworking of signaling messages on theLB interface.

To start a tracing task, you can select the following operations:l Tracing the messages processed by a specified CPUS subsysteml 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 InterfaceThis section describes how to trace BSSAP-LE messages by cell on the LB interface throughthe LMT. BSSAP-LE messages include BSSMAP-LEmsg, DTAP-LEmsg, and other messages.


LMT User Guide


Issue 07 (2011-01-30)



Procedure


Step 2 Under Trace Navigation Tree, choose Trace > GSM Services > LB Interface Trace.Accordingly, the LB Interface Trace dialog box is displayed, as shown in Figure 7-51.

Figure 7-51 Message tracing on the LB interface

Step 3 In the LB Interface Trace dialog box, set parameters in Basic the tab page and select BSSAP-LE under Trace Type.

l DPC (HEX): indicates the destination signaling point to be traced. To query the DPC, runthe LST N7DPC command.


Step 4 In the BSSAP tab page, set parameters under Message Type and Cell.

NOTE



----End




7-55






Tracing MTP3 Messages on the LB InterfaceThis section describes how to trace Message Transfer Part Level 3 (MTP3) messages on the LBinterface through the LMT. MTP3 messages include SNM, SLT, and DATA messages.


Procedure





LMT User Guide


Issue 07 (2011-01-30)

Step 3 In the LB Interface Trace dialog box, set parameters in Basic and select MTP3 in TraceType.



Step 4 In the MTP3 tab page, set parameters under Message Type.


----End








Tracing MTP2 Messages on the LB Interface

This section describes how to trace Message Transfer Part Level 2 (MTP2) messages by subrack,slot, and link number on the LB interface through the LMT. MTP2 messages include LSSU andMSU messages.



Procedure





7-57


Step 3 In the A Interface Trace dialog box, set parameters in the default Basic tab page and selectMTP2 under Trace Type.



Step 4 In the MTP2 tab page, set parameters under Message Type and Position.

NOTE

l Subrack No., Slot No.: query them by running the Display Board Status(DSP BRD) command

l Link No.: query it by running the Display MTP3 Signalling Link Set State(DSP MTP3LKS) command.


----End






LMT User Guide


Issue 07 (2011-01-30)



Tracing SCTP Messages on the LB InterfaceThis section describes how to trace SCTP signaling messages on the LB interface in LB over IPmode through the LMT. The tracing is performed by subrack, slot, CPU, or link number. SCTPmessages include control, DATA, and heartbeat messages.


Procedure




Step 3 In the LB Interface Trace dialog box, set parameters in the Basic tab page and select SCTPunder Trace Type.l DPC (HEX): indicates the destination signaling point to be traced. To query it, run the LST




7-59

Step 4 In the SCTP tab page, set parameters under SCTP Message and Parameter Configuration.

NOTE

l SCTP Link No.: query it by running the LST SCTPLNK command.


----End







Tracing M3UA Messages on the LB InterfaceThis section describes how to trace M3UA signaling messages on the LB interface in LB overIP mode through the LMT. The tracing is performed by link or link set number. M3UA messagesinclude management messages, transmission messages, SS7 management messages, ASPservice maintenance messages, ASP status maintenance messages, and route selected keywordmessages.


Procedure




LMT User Guide


Issue 07 (2011-01-30)


Step 3 In the LB Interface Trace dialog box, set parameters in the Basic tab page and select M3UAunder Trace Type.



Step 4 In the M3UA tab page, set parameters under M3UA Message and Parameter Configuration.

NOTE

l Link Set No.: indicates the number of an M3UA link set. To query it, run the LST M3LKS command.

l Link No.: indicates the number of an M3UA link. To query it, run the LST M3LNK command.


----End







7-61



7.3 Basic Tracing OperationsThe basic operations of message tracing apply to all the BSC6900 message tracing tasks.

7.3.1 Browsing Traced Messages OnlineThis describes how to browse the traced messages online, in the message browse window, afterthe tracing task is created.

7.3.2 Viewing the Interpretation of the Trace MessageThis section describes how to view the interpretation of a trace message.

7.3.3 Saving Traced MessagesThis describes how to save the trace message file to the local computer.

7.3.4 Browsing Traced Messages OfflineThis describes how to use the Traffic Recording Review Tool to browse offline, the tracedmessages that are saved in .tmf format.

7.3.5 Managing Tracing TasksThis section describes how to manage tracing tasks.

7.3.6 Managing the Trace FileThis section describes how to query the trace files on the OMU and upload the trace files ontothe LMT PC as required.

7.3.1 Browsing Traced Messages OnlineThis describes how to browse the traced messages online, in the message browse window, afterthe tracing task is created.

Prerequisitel A tracing task is successfully created.l Traced messages are reported.

Procedure

Step 1 Browse or query the traced messages in the message browse window in real time. You can right-click in the message browse window and then choose an item from the shortcut menu to performthe 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 task.

Restart Trace Task Resume the task.


LMT User Guide


Issue 07 (2011-01-30)

Shortcut Description

Save All Messages... Save all trace messages.

Save Selected Messages... Save the selected trace messages.

Auto Scroll The messages in the window are automatically refreshed inreal time and are scrolled upward.

Clear Messages All the displayed messages are cleared from the browsewindow without affecting the saving of the messages.

Property.... Query the task properties.

Step 2 To view the details of a message, double-click it. The Message Browser dialog box is displayed,showing the details of the message.

----End

7.3.2 Viewing the Interpretation of the Trace MessageThis section describes how to view the interpretation of a trace message.

Prerequisitel A tracing task is successfully created.

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 meaningof the message in protocol translation format.

----End

7.3.3 Saving Traced MessagesThis describes how to save the trace message file to the local computer.

Prerequisitel A tracing task is started.


Context

The length of the file name (including the extension) used for storing the tracing results cannotexceed 100 characters.

There are two ways of saving the trace results: auto saving and manual saving.



7-63

Procedurel Automatically saving the trace messages

If Save File is selected when a tracing task is created, all messages displayed in the messagebrowse window are saved in .tmf format.

The default save path is C:\Web LMT\output\MBSC\trace\tmfFile on the LMT PC.

NOTE

l The LMT saves every 5,000 messages in a file, that is, it saves messages starting from 1 to 5,000in one file, and so on. Note that the messages starting from 5,001 are saved in another file witha serial number, wherein the serial number is increased by one for every 5,000 messages. Forexample, the default save name of the traced 5001st to 10000th OS messages is OS_YYYY-MM-DD-HH-MM-SS.tmf.

l You can use the Traffic Recording Review Tool to browse the messages saved in .tmf formatoffline. For details, see 7.3.4 Browsing Traced Messages Offline.

l Manually saving the trace messages

When the tracing task is running, you can manually save all or part of the messages in themessage browse window in .tmf, .txt, or .csv format.

1. Right-click in the message browse window, and choose Save All Messages from theshortcut menu. You can also select the messages to be saved in the message browsewindow. Then, right-click the messages and choose Save Selected Messages fromthe shortcut menu. The Save dialog box is displayed.

2. Enter a file name, and specify the file type and save path.

The default save path is C:\Web LMT\output\MBSC\trace\tmfFile. The default filename is IP address_Trace type_YYYY-MM-DD-HH-MM-SS.tmf.

3. Click Save to save the file in the specified path.

----End

7.3.4 Browsing Traced Messages OfflineThis describes how to use the Traffic Recording Review Tool to browse offline, the tracedmessages that are saved in .tmf format.

PrerequisiteThe traced messages are saved in .tmf format.

ContextYou can find the .txt or .csv files in the save directory. You can double-click them to read thetraced messages.

Procedure

Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Traffic RecordingReview Tool.

Step 2 The Open dialog box is displayed, prompting you to select the target file. Browse to the folderwhere the trace files are saved, and select the target file.


LMT User Guide


Issue 07 (2011-01-30)

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 Browser the messages or double-click a specific one to read the details.

Step 5 To view the contents of more files, choose File > Open. In the Open dialog box, select and openfiles to view the traced messages that are saved in the files.

Step 6 You can further perform the following operations by right-clicking in the Traffic RecordingReview Tool window.

If... Then...

You choose Save All Messages from theshortcut menu,

All the messages are saved in the windowin .tmf or .txt format.

You choose Save Selected Messages fromthe shortcut menu,

The selected messages are saved in .tmf or .txtformat.

You choose Filter from the shortcut menu, Set the filter to selectively display theinformation.

You choose Filter By Column from theshortcut menu,

Filter the information by column to selectivelydisplay the information.

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

You choose Properties from the shortcutmenu,

View the properties of the task that the tracingresult corresponds to.

----End

7.3.5 Managing Tracing TasksThis section describes how to manage tracing tasks.

Prerequisitel A tracing task is successfully created.



1. Click Trace on the LMT main page. The Trace tab page is displayed.

2. On the Trace Navigation Tree pane, expand the Trace node. Double-click ManageTrace Task.



7-65

3. In the displayed Manage Trace Task tab page, set the parameters as required, andclick Query to query the information about the trace tasks.

4. To stop, restart, or delete a trace task, select the target task listed in the Result area,and then click Stop, Restart, or Delete.

NOTE

l The tasks whose Trace Mode is Report listed in the query result can only be deleted onthe LMT where it was started.

l The tasks whose Create Type is Net Create listed in the query result are created by theOMU according to the command from the BSC. Such tasks can only be deleted by theadmin or ADMINISTRATOR-level users.

l Through MML commands1. Run the LST TRCRST command to query the trace tasks.

----End

7.3.6 Managing the Trace FileThis section describes how to query the trace files on the OMU and upload the trace files ontothe LMT PC as required.

Prerequisitel A tracing task is successfully created.l Trace messages are reported.

Procedure


Step 2 On the Trace Navigation Tree pane, expand the Trace node. Double-click Manage TraceFile.

Step 3 In the displayed Manage Trace File tab page, set the parameters in the Search Configure area,and then click Query to read the information about the trace files saved on the OMU.

Step 4 To upload a trace file to the LMT PC, select the target file listed in the Result area, set theparameters in the Upload configure area, and then click Upload.

----End


LMT User Guide


Issue 07 (2011-01-30)

8 Performance Monitoring

About This Chapter

This chapter describes how to monitor the BSC6900 performance. A maximum of 64 monitoringtasks can be performed simultaneously on the same LMT.

8.1 Concepts Related to Performance MonitoringThis section describes the concepts related to the BSC6900 performance monitoring: monitoringprinciples and monitoring rights management.

8.2 Common MonitoringThis section describes the common performance monitoring.

8.3 GSM MonitoringThis section describes the performance monitoring of the GSM services.

8.4 General Operations of Performance MonitoringThis section describes the general operations applicable to all performance monitoring tasksconducted on the BSC6900.

8.5 Reference for Performance MonitoringThis describes the parameters used for performance monitoring.

BSC6900 GSMLMT User Guide 8 Performance Monitoring


8-1

8.1 Concepts Related to Performance MonitoringThis section describes the concepts related to the BSC6900 performance monitoring: monitoringprinciples and monitoring rights management.

8.1.1 Monitoring PrinciplesThis describes the principles of real-time performance monitoring, including the monitoring ofthe CPU usage and other real-time performances.

8.1.2 Management of Monitoring Operation RightsYou must have the required rights to perform real-time monitoring operations on theBSC6900.

8.1.1 Monitoring PrinciplesThis describes the principles of real-time performance monitoring, including the monitoring ofthe 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 binarycommand querying the CPU usage to the maintenance module of the OMU periodically.

2. The OMU sends the corresponding command to the maintenance and configuration moduleof the specified board.

3. The board collects data according to the commands, and reports it to the OMU.

4. The OMU sends the data to the LMT.

Principle of Real-time Performance Monitoring

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

8 Performance MonitoringBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Figure 8-2 Real-time performance monitoring

The internal procedure for creating a real-time monitoring task, other than the CPU usagemonitoring, is as follows:

1. When you create a monitoring task on the LMT, the LMT sends a binary command to theOMU to create the task.

2. The OMU assigns a number to the task and sends the command to the debugging moduleof the specified board.

3. After receiving the command, the debugging module records the filter parameters in thefilter table and notifies the service module.

4. The service module updates the local filter table according to the messages from thedebugging 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 theOMU 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 reportsthe 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 RightsYou must have the required rights to perform real-time monitoring operations on theBSC6900.

Operators of the following levels can perform the real-time performance monitoring tasks:admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use commandgroup G_10.

That is, except GUEST-level users and CUSTOM users that are not entitled to command groupG_10, all the other levels of users can perform the real-time monitoring.



8-3

NOTE

Group G_10 consists of binary commands for creating tracing and monitoring tasks.

8.2 Common MonitoringThis section describes the common performance monitoring.

8.2.1 Monitoring CPU/DSP UsageThis section describes how to query the CPU/DSP usage of a board.

8.2.2 Monitoring Transmission ResourcesThis describes how to monitor the transmission resources on the Abis interface.

8.2.3 Monitoring BER SecondsThis describes how to detect the BER seconds on an E1/T1 port to monitor the transmissionquality of the link corresponding to the port. If any bit error occurs on the E1/T1 port, you canstart this task to obtain data such as BERS, critical BERS, unavailable seconds, frame errors,CRC errors. Based on these data, you can evaluate the operating condition of the transmissionnetwork and find out the causes for the bit errors in combination with the performance of thepeer end. The AEUa/PEUa/EIUa/OIUa/POUc board supports this function.

8.2.4 Monitoring Link PerformanceThis section describes how to monitor the link performance. For the same monitoring item, youcan start a maximum of six tasks simultaneously.

8.2.1 Monitoring CPU/DSP UsageThis section describes how to query the CPU/DSP usage of a board.

Prerequisitel You have logged in to the LMT with an account authorized for this operation.l The board under monitoring is functional.

Context

CAUTIONThis operation affects the CPU usage. Therefore, if the CPU usage reaches 80% or higher, youare advised to set the monitoring period to five seconds.

Procedure

Step 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.

Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > CPU/DSPUsage Monitoring. The CPU/DSP Usage Monitoring dialog box is displayed.

Step 3 In the displayed CPU/DSP Usage Monitoring dialog box, set the parameters as required, andclick Submit.


LMT User Guide


Issue 07 (2011-01-30)

NOTE

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring resultby list and chart. The task name and related parameters are displayed on the title bar of the window.

----End

8.2.2 Monitoring Transmission ResourcesThis describes how to monitor the transmission resources on the Abis interface.


Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > Common Monitoring. Double-click Transport Resource RealTime monitoring.

Step 3 In the 8.5 Reference for Performance Monitoring dialog box, set the parameters as required,and click Submit.

NOTE

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoringresult by list and chart. The task name and related parameters are displayed on the title bar of the window.

----End

8.2.3 Monitoring BER SecondsThis describes how to detect the BER seconds on an E1/T1 port to monitor the transmissionquality of the link corresponding to the port. If any bit error occurs on the E1/T1 port, you canstart this task to obtain data such as BERS, critical BERS, unavailable seconds, frame errors,CRC errors. Based on these data, you can evaluate the operating condition of the transmissionnetwork and find out the causes for the bit errors in combination with the performance of thepeer end. The AEUa/PEUa/EIUa/OIUa/POUc board supports this function.


Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > Common Monitoring. Double-click BERS Monitoring.

Step 3 In the displayed BERS Monitoring dialog box, set the parameters as required, and clickSubmit.



8-5

NOTE

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoringresult by list and chart. The task name and related parameters are displayed on the title bar of the window.

----End

8.2.4 Monitoring Link PerformanceThis section describes how to monitor the link performance. For the same monitoring item, youcan start a maximum of six tasks simultaneously.

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


Context

CAUTIONThe FE/GE port must be successfully configured and connected to the peer end before this taskis performed. This task is stopped if the monitored link is deleted.

Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > Common Monitoring. Double-click Link Performance Monitoring.

Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to 8.5 Reference forPerformance Monitoring. Set other parameters as required, and then click Submit.

NOTE

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoringresult in the form of list and chart. The task name and related parameters are displayed on the title bar ofthe window.

In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate representsthe RX and TX traffic in bit/s.

----End


LMT User Guide


Issue 07 (2011-01-30)

Monitoring the PPP Link Traffic

This section describes how to monitor the traffic on a specified PPP link in real time. The real-time traffic on the specified PPP link is displayed in the form of list and chart. This task can beperformed to achieve the following functions by comparing the statistics from the two ends ofthe PPP link: to confirm the packet loss, locate the fault, and evaluate the network transmissionquality; to compare the total traffic with the traffic carried by the current port and obtain theutilization of the port; and to check the bandwidth condition based on which the user can decidewhether to expand the bandwidth or modify the PPP to MLPPP.

Prerequisite


Context

CAUTIONThe PPP link must be successfully set up and connected to the peer end before this task isperformed. This task is stopped if the monitored link is deleted.

Procedure




NOTE



----End

Monitoring Traffic on the MLPPP Link Group

This describes how to monitor the traffic on a specified MLPPP link group in real time. Thereal-time traffic on the specified MLPPP link group is displayed in the form of list and chart.Based on the statistics from the two ends of the MLPPP link, you can confirm the packet loss,locate the fault, and evaluate the transmission network quality. You can also compare the actualtraffic volume with the user volume carried by the current port and obtain the utilization of theport. In addition, you can evaluate the bandwidth condition and decide whether to add a link toexpand the bandwidth.



8-7


Context

CAUTIONThe MLPPP group must be successfully configured and connected to the peer end before thistask is performed. This task is stopped if the monitored MLPPP link group is deleted.

Procedure




NOTE



----End

Monitoring the SCTP Link TrafficThis describes how to monitor the traffic on a specified SCTP path at the IP layer of the interfaceboard in real time. The real-time traffic on the specified SCTP path is displayed in the form oflist and chart. Based on the transmit/receive statistics on the SCTP of the CPUS subsystem, youcan 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.


Context

CAUTIONThe SCTP link must be successfully set up and connected to the peer end before this task isperformed. This task is stopped if the monitored link is deleted.


LMT User Guide


Issue 07 (2011-01-30)

Procedure




NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate representsthe RX and TX traffic in kbit/s.

----End

Monitoring the IP Path Traffic

This describes how to monitor the traffic on a specified IP path at the IP layer of the interfaceboard in real time. The real-time traffic on the specified IP path is displayed in the form of listand chart. Based on the layer 2 statistics obtained from the CDT trace, you can confirm thepacket loss and evaluate the user data flow conditions. In addition, you can predict the congestionbased on the traffic conditions on the link.

Prerequisite


Context

CAUTIONThe IP path must be successfully set up and connected to the peer end before this task isperformed. This task is stopped if the monitored link is deleted.

Procedure






8-9

NOTE

After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring resultsin list and chart. The task name and related parameters are indicated in the title bar of the window.


----End

Monitoring Traffic on a Logical Port

This section describes how to monitor the traffic on a specified logical port. You can monitoran entire port, where the monitoring result displays the real-time traffic of the current logicalport. You can also monitor only the specified priority of the port, where the monitoring resultdisplays the TX traffic of the specified priority of the current logical port. Based on the trafficstatistics at the logical port, you can confirm the packet loss at the logical port and locate thefault. You can also compare the actual traffic volume with the user volume and obtain theutilization of the port. In addition, you can evaluate the bandwidth condition and decide whetherto expand the configuration bandwidth of the logical port.

Prerequisite


Procedure




NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate representsthe real-time traffic of the current logical port in bit/s.

----End

Monitoring the Bandwidth of a Logical Port

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

Prerequisite



LMT User Guide


Issue 07 (2011-01-30)

Procedure



Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to 8.5 Referencefor Performance Monitoring. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate representsthe bandwidth in bit/s.

----End

8.3 GSM MonitoringThis section describes the performance monitoring of the GSM services.

8.3.1 Monitoring Traffic on GPRS User PlaneThis describes how to monitor the GPRS user plane traffic on a DSP of the built-in PCU,including the uplink and downlink traffic on the Um and Gb interfaces. You can perform thistask to know the DSP load conditions on the Um interface and the Gb interface.

8.3.2 Monitoring Abis HDLC UtilizationThis describes how to monitor the average TX/RX rate on the HDLC link. By performing thistask, you can learn about the resource utilization.

8.3.3 Monitoring Cell PerformanceThis describes how to monitor the performance of a GSM cell, including the uplink and downlinkRX level, UL and DL RX quality, MS and BTS TX power, and CS service rate. By performingthis task, you can evaluate the performance of the cell through the traced measurement reportsduring a call of a specific MS in a cell.

8.3.4 Monitoring DSP ResourcesThis describes how to monitor the DSP usage and the number of transmission service types ofthe system.

8.3.5 Monitoring BTS IP Link PerformanceThis section describes how to monitor the performance of IP links in a BTS.

8.3.1 Monitoring Traffic on GPRS User PlaneThis describes how to monitor the GPRS user plane traffic on a DSP of the built-in PCU,including the uplink and downlink traffic on the Um and Gb interfaces. You can perform thistask to know the DSP load conditions on the Um interface and the Gb interface.

Prerequisitel You have logged in to the LMT with an account authorized for this operation.l The DPUd board that supports the built-in PCU is present.



8-11

Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-clickGPRS Flux Monitoring.

Step 3 In the GPRS Flux Monitoring dialog box, set the parameters as required, and click Submit.

NOTE


----End

8.3.2 Monitoring Abis HDLC UtilizationThis describes how to monitor the average TX/RX rate on the HDLC link. By performing thistask, you can learn about the resource utilization.

Prerequisitel You have logged in to the LMT with an account authorized for this operation.

l The BTS must support HDLC services.


Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-clickAbis HDLC Transport Usage Monitoring.

Step 3 In the Abis HDLC Transport Usage Monitoring dialog box, set the parameters as required,and click Submit.

NOTE


----End

8.3.3 Monitoring Cell PerformanceThis describes how to monitor the performance of a GSM cell, including the uplink and downlinkRX level, UL and DL RX quality, MS and BTS TX power, and CS service rate. By performingthis task, you can evaluate the performance of the cell through the traced measurement reportsduring a call of a specific MS in a cell.

Prerequisite



LMT User Guide


Issue 07 (2011-01-30)

Context

CAUTIONOnly the cell performance related to the CS services can be monitored. The cell performancerelated to the PS services are not available.

ProcedureStep 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.

Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-clickCell Performance Monitoring.

Step 3 In the displayed 8.5 Reference for Performance Monitoring dialog box, set the parameters asrequired, and click Submit.

NOTE


----End

8.3.4 Monitoring DSP ResourcesThis describes how to monitor the DSP usage and the number of transmission service types ofthe system.

Prerequisitel You have logged in to the LMT with an account authorized for this operation.l The DPUa or DPUc board is in position.

ProcedureStep 1 Click Monitor on the LMT main page. The Monitor tab page is displayed.

Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-clickDSP Resource Monitoring.

Step 3 In the DSP Resource Monitoring dialog box, set the parameters as required, and clickSubmit.

NOTE


----End

8.3.5 Monitoring BTS IP Link PerformanceThis section describes how to monitor the performance of IP links in a BTS.



8-13

Prerequisite


Procedure


Step 2 On the Monitor Navigation Tree pane, expand Monitor > GSM Monitoring. Double-clickBTS IP Link Performance Monitoring.

Step 3 In the BTS IP Link Performance Monitoring dialog box, set the parameters as required, andclick Submit.

NOTE

l Set Monitor Item to FE/GE, PPP, or MLPPP to monitor the corresponding layer layer 2 links.

l Set Monitor Item to IP_FE/GE, IP_PPP, or IP_MLPPP to monitor the corresponding layer layer 3 links.

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring resultin the form of list and chart. The task name and related parameters are displayed on the title bar of the window.

----End

8.4 General Operations of Performance MonitoringThis section describes the general operations applicable to all performance monitoring tasksconducted on the BSC6900.

8.4.1 Browsing the Monitoring Results OnlineThis describes how to browse online and query the monitoring results that are dynamicallydisplayed in the monitoring window in real time.

8.4.2 Setting the Display Mode of the ChartThis section describes how to set the display mode of the chart in the real-time monitoringwindow after a monitoring task is started. Below the Chart tab page in the window, you can setthe display properties such as the line color, line type, and line width.

8.4.3 Saving Monitoring ResultsThis section describes how to save the monitoring results to local files.

8.4.4 Browsing Monitoring Results OfflineThis section describes how to browse the monitoring results of the CPU usage and BERseconds in offline mode.

8.4.1 Browsing the Monitoring Results OnlineThis describes how to browse online and query the monitoring results that are dynamicallydisplayed in the monitoring window in real time.

Prerequisitel A performance monitoring task is started.

l Monitoring results are reported.


LMT User Guide


Issue 07 (2011-01-30)

Procedurel 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 theshortcut menu:– Setting auto scroll– Showing or hiding the grid– Switching the display mode– Setting the display range of the Y axis

l Right-click on the List tab page in the real-time performance monitoring window. Then,you can perform the following operations by selecting the corresponding item from theshortcut menu:

Setting auto scrolll 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 thecorresponding 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 ChartThis section describes how to set the display mode of the chart in the real-time monitoringwindow after a monitoring task is started. Below the Chart tab page in the window, you can setthe display properties such as the line color, line type, and line width.

Prerequisitel A performance monitoring task is started.l Monitoring results are reported.

Procedure

Step 1 In the task information pane at the bottom of the window, click the property boxes of the LineColor, Line Type, or Line Width column.

Step 2 Select the required properties from the drop-down lists.

NOTE

l The setting of the display properties applies only to the current monitoring task.

l If data is displayed on the List tab page but no chart is displayed on the Chart tab page during the real-time monitoring, set the display properties of the chart.

----End

8.4.3 Saving Monitoring ResultsThis section describes how to save the monitoring results to local files.



8-15

Prerequisitel A performance monitoring task is started.

l Monitoring results are reported.

Procedure

Step 1 To automatically save the monitoring results, ensure that the Auto Save check box is selectedwhen you create the task. The default save path is C:\Web LMT\output\MBSC\monitor.

----End

8.4.4 Browsing Monitoring Results OfflineThis section describes how to browse the monitoring results of the CPU usage and BERseconds in offline mode.

Prerequisite

The monitoring results are saved to files.

Procedure

Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Traffic RecordingReview Tool.

Step 2 Open the directory where the monitoring results are saved. The default save path is C:\Web LMT\output\MBSC\monitor. Select the result file corresponding to the monitoring task.

Step 3 Click Open or double-click the file. The Traffic Recording Review Tool window is displayed,providing the monitoring results in chart and list.

Step 4 Click the List tab or the Chart tab to view the data in different modes.

Step 5 To view other saved results, choose File > Open. In the Open dialog box, select the target filesto read the details.

----End

8.5 Reference for Performance MonitoringThis describes the parameters used for performance monitoring.

Monitor Item Parameter Description

Transport ResourceRealTime Monitoring

IP Logic PortHDLC Link

Indicates the number of the IP logical port. Toquery the number of the IP logical port, run theLST IPLOGICPORT command.Indicates the number of the HDLC link. Toquery the HDLC link, run the DSPHDLCLNK command.


LMT User Guide


Issue 07 (2011-01-30)

Monitor Item Parameter Description

LinkPerformanceMonitoring

FE/GE FE/GE PortNo.

Indicates the number of the FE/GE port. Toquery the number of the FE/GE port, run theDSP ETHPORT command.

PPP Link PPP Link No. Indicates the number of the PPP link. To querythe PPP link, run the LST PPPLNKcommand.

MLPPPGroup

MLPPP GroupNo.

Indicates the number of the MLPPP group. Toquery the number of the MLPPP group, run theLST MPGRP command.

SCTP Link SCTP Link No. Indicates the number of the SCTP link. Toquery the SCTP link, run the LSTSCTPLNK command.

IP Path Adjacent NodeIDIP PATHSymbol

Indicates the number of the adjacent node ofthe IP path. To query the adjacent node of theIP path, run the LST IPPATH command.

LogicalPort

Port No. Indicates the number of a logical port. Toquery the IP logical port, run the LSTIPLOGICPORT command.

LogicalPortBandwidth

Logical PortNo.

Indicates the number of a logical port. Toquery the IP logical port, run the LSTIPLOGICPORT command.

FE/GEPPP LinkMLPPPGroupLogicalPort

Priority GroupNo.

Indicates the priority queue number. (valuerange: 0-5).

GSM Cell PerformanceMonitoring

Monitor Type You can choose to monitor the following itemsof the cell:l UL/DL RxLev: uplink and downlink

receive levell UL/DL RxQual: uplink and downlink

receive qualityl MS/BTS Tx power: transmit power of the

MS and BTSl CS service rate



8-17

9 Device Panel

About This Chapter

This chapter describes how to manage the BSC6900 equipment by using the device andemulation panels. You can use these panels to query for information about the boards, boardports, board links, and board alarms.

9.1 Device Panel OperationsThis section describes the operations of the BSC6900 device panel, including how to start anduse it and how to query the status of the boards.

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

BSC6900 GSMLMT User Guide 9 Device Panel


9-1

9.1 Device Panel OperationsThis section describes the operations of the BSC6900 device panel, including how to start anduse it and how to query the status of the boards.

9.1.1 Introduction to the Device PanelIn addition to MML commands, the LMT also provides the graphical device panel to facilitatedevice maintenance.

9.1.2 Starting the Device PanelThis section describes how to start the device panel.

9.1.3 Querying the Status of an E1/T1 PortThis describes how to query the status of an E1/T1 port.

9.1.4 Querying the CPU UsageThis describes how to query the CPU usage of a board.

9.1.5 Querying the BSC Board InformationThis describes how to query the status of a BSC board.

9.1.6 Resetting the BSC BoardThis describes how to reset the BSC board, the CPU on the XPUa board, and the DSP on theDPU board. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level userscan perform this operation.

9.1.7 Switching Over the BSC BoardsThis describes how to switch over the active BSC board and the standby BSC board. When theactive board is faulty, you can switch all the services over to the standby board to ensure thenormal operation of the system. Only the admin, ADMINISTRATOR-level, and authorizedCUSTOM-level users can perform this operation.

9.1.8 Querying the Status and Frequency of the Cavity CombinerThis section describes how to query the status and frequency of the cavity combiner on theDFCU/DFCB board in the BTS3012 and BTS3012AE.

9.1.9 Querying the BTS Board InformationThis section describes how to query the detailed information about a BTS board.

9.1.10 Resetting the BTS BoardThis section describes how to reset a faulty BTS board.

9.1.11 Maintaining BTS ClockThis section describes how to query the clock information about the BTS board.

9.1.12 Switching Over the BTS BoardsThis section describes how to switch over the active BTS board and the standby BTS board.Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can performthis operation.

9.1.1 Introduction to the Device PanelIn addition to MML commands, the LMT also provides the graphical device panel to facilitatedevice maintenance.

9 Device PanelBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

The device panel is automatically refreshed, showing board status in real time through the boardcolors and alarm indicators on the board.

On the device panel, you can right-click a board in position and choose operations from theshortcut menu. For example, you can query the board status. Figure 9-1 shows the device panel.

Figure 9-1 Device Panel

The alarm indicators represent the alarm status of a board, and the board colors indicate therunning status of the board. See the color descriptions shown on the right of the device panel forthe specific meanings of the alarm indicators and board colors.

l If the tab page under Device Maintenance is not in full view, click . The drop-down listis displayed. Choose the required menu to display the corresponding tab page.

l After you add or delete a BTS or cell, a Click to Refresh button is displayed on the bottomof the device navigation tree. Click Click to Refresh to refresh the navigation tree.

l Right-click the peripheral of the rack, and choose Refresh Shelf to refresh the rack.

l Below the color descriptions of the board, choose Display Logic Function. Then, the logicfunctions of the boards are displayed.

9.1.2 Starting the Device PanelThis section describes how to start the device panel.

Prerequisite


Procedure

Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page isdisplayed.

Step 2 The BSC Device Panel tab is displayed.



9-3

Step 3 Click BSC under Device Navigation Tree. Click the required BTS, and the corresponding BTSDevice Panel tab is displayed on the right.

----End


Prerequisitel You have logged in to the LMT.l The boards are in position.

ProcedureStep 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see

9.2.2 Starting the Emulation Panel).

Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, andchoose Query E1/T1 Port Status from the shortcut menu. The Query Optical Interface BoardPort Information is displayed, showing the details about the E1/T1 port.

----End



ContextYou can query the CPU usage through menu operations or through MML commands.


1. Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulationpanel (see 9.2.2 Starting the Emulation Panel).

2. Right-click a board in position in the device panel or emulation panel, and then chooseDisplay CPU Usage from the shortcut menu. The CPU Usage window is displayed,showing the real-time CPU usage.

l Through MML commands1. Run the DSP CPUUSAGE command to query the CPU usage.

----End



LMT User Guide


Issue 07 (2011-01-30)


ContextYou can query the status of a board through menu operations or through MML commands.



2. Right-click a board in position in the device panel or emulation panel, and then chooseQuery BSC Board Information from the shortcut menu. The Query BSC BoardInformation dialog box is displayed, showing details of the board.

l Through MML commands1. Run the DSP BRD command to query the information about the BSC board.

----End



Context

CAUTIONl If the standby board is not available or the standby board is faulty, resetting the board will

disrupt the ongoing services. Thus, perform this operation with caution.l Resetting the board may affect the ongoing services. Therefore, you are advised to perform

the switchover when the traffic load is light, for example, in the middle of the night.

l Resetting the BoardThe board resetting is mandatory during software upgrade and software loading. Resettingthe board will reload the programs and data files. If the active board is reset and the standbyboard is working normally, the services processed by the active board will be switched overto the standby board first, and then the standby board (the original active board) is resetafter the switchover. If an SCUa board is reset while its standby board is not available oris faulty, the entire subrack is reset.



9-5

l Reset the CPU

Each XPUa board has four CPUs numbered from 0 to 3. Other types of boards have oneCPU each. If CPU 0 of the XPUa board is reset, the entire board is reset.

l Resetting the DSP

Each DPU board has 22 DSPs numbered from 0 to 21. Each DSP can be reset separately.



2. Right-click a board in position in the device panel or emulation panel, and then chooseReset BSC Board.

3. In the displayed Reset BSC Board dialog box, set the parameters as required, andthen click Reset.


1. Run the RST BRD command to reset a BSC board.

----End



l Before you perform the switchover, ensure that the standby board is present and runningnormally without any critical or major alarms.

Context

CAUTIONl If the board switchover fails, the configuration data is not affected but the services will be

disrupted. Thus, perform this task with caution.

l Resetting the board may affect the ongoing services. Thus, you are advised to perform theswitchover when the traffic load is light, for example, in the middle of the night.

l All boards configured in active/standby mode support switchover operations. Only the activeboard can initiate the switchover, except the OMUa board. The OMUa board also supportsswitchover initiated by the standby board.

You can query the status of a board through menu operations or through MML commands.


LMT User Guide


Issue 07 (2011-01-30)



2. Right-click a board in position in the device panel or emulation panel, and then chooseSwitch BSC Board.

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


1. Run the SWP BRD command to switch over the BSC boards.

----End

9.1.8 Querying the Status and Frequency of the Cavity CombinerThis section describes how to query the status and frequency of the cavity combiner on theDFCU/DFCB board in the BTS3012 and BTS3012AE.



Context



1. Start the BTS device panel (see 9.1.2 Starting the Device Panel).2. In the BTS device panel, right-click the target DFCU/DFCB board and choose Query

Status and Frequency of Cavity Combiner from the shortcut menu. The query resultis displayed in the Query Status and Frequency of Cavity Combiner dialog box.


1. Run the DSP BTSCAVSTAT command to query the status and frequency of thecavity combiner.

----End

9.1.9 Querying the BTS Board InformationThis section describes how to query the detailed information about a BTS board.





9-7



1. Start the BTS device panel (see 9.1.2 Starting the Device Panel).2. Right-click a board in position in the BTS device panel, and then choose Query Board

Information. The Query Board Information dialog box is displayed, showingdetails of the board.

3. To query the basic attributes of the BTS board, choose View Site Board from theright-click shortcut menu.

l Through MML commands1. Run the DSP BTSBRD command to query the information about the BTS board.

----End

9.1.10 Resetting the BTS BoardThis section describes how to reset a faulty BTS board.


ContextYou can reset a board through menu operations or through MML commands.


1. Start the BTS device panel (see 9.1.2 Starting the Device Panel).2. Right-click a board in position in 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.l Through MML commands

1. Run the RST BTSBRD command to reset a BTS board.

----End

9.1.11 Maintaining BTS ClockThis section describes how to query the clock information about the BTS board.



LMT User Guide


Issue 07 (2011-01-30)


Context



1. Start the BTS device panel (see 9.1.2 Starting the Device Panel).

2. Right-click the main processing board in the BTS device panel, and then chooseMaintain Clock from the shortcut menu.

3. In the displayed Maintain Clock dialog box, set the parameters as required, and clickQuery.


1. Run the LST BTSCLK command to query the BTS clock information.

----End

9.1.12 Switching Over the BTS BoardsThis section describes how to switch over the active BTS board and the standby BTS board.Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can performthis operation.



Context

CAUTIONl If the board switchover fails, the communication link will be disconnected and the dynamic

service data will be lost (the configuration data is not affected). Thus, perform this task withcaution.


l Board switchover affects the ongoing services. Thus, you are advised to perform theswitchover when the service load is low, for example, in the middle of the night.

Only the BTS3012, BTS3012AE, and BTS3012II supports the switchover of DTMU/DPTUboards.

You can reset a BTS board through menu operations or through MML commands.



9-9


1. Start the BTS device panel (see 9.1.2 Starting the Device Panel).2. Right-click the target board in the BTS device panel, and then choose Switch

Board from the shortcut menu.3. In the displayed Switch Board dialog box, set the parameters as required, and then

click Switch to switch over the boards.l Through MML commands

1. Run the SWP BTSBRD command to switch over the BTS boards.

----End

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

9.2.1 Introduction to the Emulation PanelThe LMT provides the emulation panel for each subrack. The emulation subrack has the sameports as the real subrack and helps to ascertain the status of each board.

9.2.2 Starting the Emulation PanelThis section describes how to start the emulation panel.






9.2.8 Querying the Status of an FE PortThis section describes how to query the status of an FE port.

9.2.9 Querying the Status of a GE PortThis section describes how to query the status of a GE port on the SCUa board.

9.2.10 Querying the Status of an Optical PortThis section describes how to query the status of an optical port.

9.2.11 Querying the DSP Status of a DPU


LMT User Guide


Issue 07 (2011-01-30)

This section describes how to query the DSP status of a DPU board.

9.2.12 Querying Alarm LED InformationThis section describes how to query the details of alarms indicated by an alarm LED.

9.2.1 Introduction to the Emulation PanelThe LMT provides the emulation panel for each subrack. The emulation subrack has the sameports as the real subrack and helps to ascertain the status of each board.

The emulation panel displays the running status of the ports of each board and provides right-click menus as shown in Figure 9-2.

Figure 9-2 Emulation panel

The emulation panel has the following features:

l It displays the running status of the device directly.

l You can query the board status and port status through the right-click menus.

9.2.2 Starting the Emulation PanelThis section describes how to start the emulation panel.

Prerequisite




9-11

ProcedureStep 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is

displayed.

Step 2 Click BSC6900 under Device Navigation Tree. The BSC Device Panel is displayed on theright pane.

Step 3 To display the emulation panel of a subrack, select the corresponding rack and double-click theperipheral of the subrack, as shown in Figure 9-3.

Figure 9-3 Subrack peripheral

----End



ProcedureStep 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see

9.2.2 Starting the Emulation Panel).

Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, andchoose Query E1/T1 Port Status from the shortcut menu. The Query Optical Interface BoardPort Information is displayed, showing the details about the E1/T1 port.

----End


LMT User Guide


Issue 07 (2011-01-30)



ContextYou can query the CPU usage through menu operations or through MML commands.



2. Right-click a board in position in the device panel or emulation panel, and then chooseDisplay CPU Usage from the shortcut menu. The CPU Usage window is displayed,showing the real-time CPU usage.

l Through MML commands1. Run the DSP CPUUSAGE command to query the CPU usage.

----End






2. Right-click a board in position in the device panel or emulation panel, and then chooseQuery BSC Board Information from the shortcut menu. The Query BSC BoardInformation dialog box is displayed, showing details of the board.

l Through MML commands1. Run the DSP BRD command to query the information about the BSC board.

----End



9-13



Context


disrupt the ongoing services. Thus, perform this operation with caution.l Resetting the board may affect the ongoing services. Therefore, you are advised to perform

the switchover when the traffic load is light, for example, in the middle of the night.

l Resetting the BoardThe board resetting is mandatory during software upgrade and software loading. Resettingthe board will reload the programs and data files. If the active board is reset and the standbyboard is working normally, the services processed by the active board will be switched overto the standby board first, and then the standby board (the original active board) is resetafter the switchover. If an SCUa board is reset while its standby board is not available oris faulty, the entire subrack is reset.

l Reset the CPUEach XPUa board has four CPUs numbered from 0 to 3. Other types of boards have oneCPU each. If CPU 0 of the XPUa board is reset, the entire board is reset.

l Resetting the DSPEach DPU board has 22 DSPs numbered from 0 to 21. Each DSP can be reset separately.



2. Right-click a board in position in the device panel or emulation panel, and then chooseReset BSC Board.

3. In the displayed Reset BSC Board dialog box, set the parameters as required, andthen click Reset.

l Through MML commands1. Run the RST BRD command to reset a BSC board.

----End


LMT User Guide


Issue 07 (2011-01-30)


Prerequisitel You have logged in to the LMT.l Before you perform the switchover, ensure that the standby board is present and running

normally without any critical or major alarms.

Context


disrupted. Thus, perform this task with caution.l Resetting the board may affect the ongoing services. Thus, you are advised to perform the

switchover when the traffic load is light, for example, in the middle of the night.l All boards configured in active/standby mode support switchover operations. Only the active

board can initiate the switchover, except the OMUa board. The OMUa board also supportsswitchover initiated by the standby board.




2. Right-click a board in position in the device panel or emulation panel, and then chooseSwitch BSC Board.

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

l Through MML commands1. Run the SWP BRD command to switch over the BSC boards.

----End

9.2.8 Querying the Status of an FE PortThis section describes how to query the status of an FE port.




9-15

l The boards are in position.

ContextYou can query the status of an FE port through menu operations or through MML commands.


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 PortStatus window is displayed, showing the details of the FE port status.

l Through MML commands1. Run the DSP ETHPORT to query the status of the FE port.

----End

9.2.9 Querying the Status of a GE PortThis section describes how to query the status of a GE port on the SCUa board.


ContextYou can query the status of a GE port through menu operations or through MML commands.


1. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).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 EthernetPort Status window is displayed, showing the details of the GE port status.

l Through MML commands1. Run the DSP GEPORT command to query the status of the GE port.

----End

9.2.10 Querying the Status of an Optical PortThis section describes how to query the status of an optical port.



LMT User Guide


Issue 07 (2011-01-30)

ContextYou can query the status of an optical port through menu operations or through MML commands.


1. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).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 displayedQuery Optical Port Status and Performance window, specify the parameters asrequired, and click Submit to query the detailed information about the optical port.

l Through MML commands1. Run the DSP OPT to query the status of the optical port.

----End

9.2.11 Querying the DSP Status of a DPUThis section describes how to query the DSP status of a DPU board.

Prerequisitel You have logged in to the LMT.l The board is in the specified slot.

ContextYou can query the DSP status of a DPU board through menu operations or through MMLcommands.


1. Start the emulation panel (see 9.2.2 Starting the Emulation Panel).2. On the emulation panel, right-click the required port on the DPU board, and choose

Query DSP Status from the shortcut menu. The displayed Query DSP Status showsthe details about the DSP status.

l Through MML commands1. Run the DSP DSP command to query the DSP status of the DPU board.

----End

9.2.12 Querying Alarm LED InformationThis section describes how to query the details of alarms indicated by an alarm LED.




9-17

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 AlarmIndicator Info from the shortcut menu. The Query Alarm Indicator Info window is displayed,showing the details of alarms indicated by the alarm LED.

----End


LMT User Guide


Issue 07 (2011-01-30)

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 MaintenanceThis section describes the basic concepts related to the BSC maintenance: BSC interfaceprocessing subsystem and loopback.

10.2 Browsing Configuration DataThis describes how to browse the configuration data, including the configuration data of BSCs,BTSs, TRXs, and channels.

10.3 Backing Up DataThis section describes how to back up system data on the OMU. The system data includesconfiguration data, alarm configuration data, and performance configuration data.

10.4 Restoring DataThis section describes how to restore configuration data on the OMU.

10.5 Maintaining the EquipmentThis section describes how to maintain the BSC equipment.

10.6 Maintaining Transmission and SignalingThis section describes how to maintain the signaling link and the ports on the interface boards.In the Device Navigation Tree, right-click the BSC6900 node, and choose MaintainTransmission and Signaling from the shortcut menu to perform the relevant tasks.

10.7 Maintaining BSC User ResourcesThis section describes how to maintain the user resources, including the port timeslot, interfacecircuit, TC resources, call resources, DSP channel or link, external speech channel, and internalspeech channel. In the Device Navigation Tree, right-click the BSC6900 node, and chooseMaintain User Resources from the shortcut menu to perform the relevant tasks.

10.8 Querying Board Version InformationThis section describes how to query the information about the software version, hardwareversion, and patch version of the board.

BSC6900 GSMLMT User Guide 10 BSC Maintenance


10-1

10.1 Concepts Related to BSC MaintenanceThis section describes the basic concepts related to the BSC maintenance: BSC interfaceprocessing subsystem and loopback.

10.1.1 BSC Interface Processing SubsystemThe BSC interface processing subsystem consists of the following logical units: Abis interfaceprocessing unit, A interface processing unit, Ater interface processing unit, Pb interfaceprocessing unit, Gb interface processing unit, and Cb interface processing unit.

10.1.2 LoopbackYou can perform loopback on a transmission device or a transmission channel by using hardwareor software.

10.1.1 BSC Interface Processing SubsystemThe BSC interface processing subsystem consists of the following logical units: Abis interfaceprocessing unit, A interface processing unit, Ater interface processing unit, Pb interfaceprocessing 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 theBTS over the Abis interface, to the PCU over the Pb interface, to the SGSN over the Gb interface,and to the CBC over the Cb interface. The MPS/EPS subrack is connected to the TC subrackover the Ater interface within the BSC.

10 BSC MaintenanceBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

NOTE

Based on the PCU type and the configuration mode of the BSC subracks, the BSC provides the followinginterfaces:

l When the built-in PCU is used, the BSC provides the Gb interface.

l When the external PCU is used, the BSC provides the Pb interface.

l In BM/TC separated configuration mode, the BSC provides the Ater interface.

Abis Interface Processing UnitThe BSC provides the Abis interface to communicate with the BTS. The Abis interfaceprocessing unit can be the EIUa/OIUa, FG2a/GOUa, and PEUa boards. The Abis interfaceprocessing unit performs the following functions:

l Provides E1/T1 ports, STM-1 ports, and FE/GE portsl Receives and transmits the signaling and traffic signals between the BSC and the BTSl Converts internal protocolsl Processes HDLC and IP protocolsl Forwards signaling to the service control subsysteml Forwards traffic signals to the service processing subsystem

A Interface Processing UnitThe BSC provides the A interface to communicate with the MSC/MGW. The A interfaceprocessing unit can be the EIUa/OIUa and FG2a/GOUa boards. The A interface processing unitperforms the following functions:l Provides E1/T1 ports, STM-1 ports, and FE/GE portsl Receives and transmits the signaling and traffic signals between the BSC and the MSC/

MGWl Converts internal protocolsl Performs the IP protocol processing if IP transmission is used over the A interface, and

performs the MTP2 protocol processing if the BM and the TC are configured in the samesubrack

l Forwards the signaling from the core network (CN) to the GE switching subsysteml Forwards the traffic signals from the CN to the GE switching subsystem or to the TDM

switching subsystem

Ater Interface Processing UnitIn BM/TC separated configuration mode, the BM and the TC communicate with each other overthe Ater interface. The Ater interface processing unit can be the EIUa/OIUa board. The Aterinterface processing unit performs the following functions:l Provides E1/T1 ports and STM-1 portsl Receives and transmits signaling and traffic signals between the BM subrack and the TC

subrackl Processes HDLC and PPP protocolsl Processes the MTP2 protocoll Forwards signaling to the GE switching subsystem



10-3

l Forwards traffic signals to the TDM switching subsystem

Pb Interface Processing UnitWhen the external PCU is used, the BSC provides the Pb interface to enable the communicationbetween the BSC and the PCU. The Pb interface processing unit can be the EIUa/OIUa board.The Pb interface processing unit performs the following functions:l Provides E1/T1 ports and STM-1 portsl Receives and transmits signaling and traffic signals between the BSC and the PCUl Forwards signaling to the GE switching subsysteml Forwards traffic signals to the TDM switching subsystem

Gb interface processing unitWhen the built-in PCU is used, the BSC provides the Gb interface to enable the communicationbetween the BSC and the SGSN. The Ater interface processing unit can be the EIUa/OIUa board.The Gb interface processing unit performs the following functions:l Provides E1/T1 ports and FE/GE portsl Receives and transmits signaling and traffic signals between the BSC and the SGSNl Processes the signaling according to the FR/IP protocoll Forwards signaling and traffic signals to the GE switching subsystem

Cb Interface Processing UnitThe BSC and the CBC communicate with each other over the Cb interface. The Cb interfaceprocessing unit is the XPUa board. The Cb interface processing unit performs the followingfunctions:l Provides FE/GE portsl Receives and transmits the signaling between the BSC and the CBCl Forwards signaling to the GE switching subsystem

10.1.2 LoopbackYou can perform loopback on a transmission device or a transmission channel by using hardwareor software.

You can ascertain whether the hardware is working properly and the software parameters areset correctly, based on the operating status of the transmission equipment, channels, services,and signaling interworking, after the self-loopback. Loopback test is the common method forlocating transmission faults and faults in trunk parameter setting.

Remember to disable the loopback after the test. Otherwise, services are not supported on thechannels under the loopback test.

Loopback is classified into timeslot loopback, port loopback, and speech loopback.

Timeslot loopbackTimeslot loopback is used to loop back data carried by a timeslot in the specified direction, asshown in Figure 10-2. When mute, bad speech quality, or noise occurs in a conversation, youcan start a timeslot loopback to locate the fault.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-2 Timeslot loopback

You can set the loopback direction by selecting a loopback mode. By doing this, you can analyzewhether the fault is on the system side or on the transmission lines or whether it is a transmissionproblem or software problem.

Timeslot loopback mode:

l Remote loopbackThe signals received on a timeslot are sent out without being processed. Remote loopbackrefers to the loopback performed on the MSC side.

l Local loopbackThe signals that should be placed in the sending direction are placed in the receivingdirection as the received data. Local loopback is performed on the BSC side.

Port loopbackPort loopback is used to loop back the data received or transmitted at a port in the specifieddirection, as shown in Figure 10-3. You can perform the port loopback to locate a fault of a linkdisconnection, link intermittence, or mute problem.



10-5

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 Loopback Mode

EIU/OIU

E1/T1 Local Loopback: All the signals that should be placed in thesending direction are placed in the receiving direction and returnedas the received data. The signals are not sent to the ports on thepeer interface board through physical links.Remote Loopback: All the ports that have received signals sendthe signals back. The board where the ports are located does notprocess signals.Payload Loopback: A board processes the signals received fromports and then sends the signals back through the ports.

STM-1

Optical board

Regenerator Section Line-side: All the ports that have receivedsignals send the signals back. The board where the ports are locateddoes not process signals.


LMT User Guide


Issue 07 (2011-01-30)

Interface Board Loopback Mode

Regenerator Section System Side: All the signals that should beplaced in the sending direction are placed in the receiving directionand returned as the received data. The signals are not sent to theports on the peer interface board through physical links.

Opticaltributary

Lower Order Path Line-side Loopback: A board processes thesignals received from ports and then sends the signals back throughthe ports.

Optical Tributary Line-side Loopback: All the ports that havereceived signals send the signals back. The board where the portsare located does not process signals.

Optical Tributary System Side Loopback: All the signals thatshould be placed in the sending direction are placed in the receivingdirection and returned as the received data. The signals are not sentto the ports on the peer interface board through physical links.

IP-based interfaceboards/transmissionoptimization interfaceboards

Local Loopback: All the signals that should be placed in thesending direction are placed in the receiving direction and returnedas the received data. The signals are not sent to the ports on thepeer interface board through physical links.

Speech LoopbackOn a speech channel, you can locate the segment where a speech problem occurs by comparingthe loopback speech with the original speech.

Speech loopback mode:

l Remote speech channel loopbackRemote speech channel loopback aims to locate a remote speech channel fault by loopingback a speech channel on the A or Abis interface. After excluding the possibility that thefault is on the remote speech channel, test the internal speech channel to locate the fault.A remote speech channel loopback can be performed in the direction of the MSC or BTS.Assuming that a remote speech channel loopback is performed on the A interface, theloopback can be classified into the following two types:– In the MSC direction: Speech sent from the MSC to MS A undergoes a loopback on

the A interface board towards the MSC but is still sent to MS A. Normally, after sucha loopback, MS A can hear MS B; MS B can hear itself but cannot hear MS A. If MSB cannot hear itself after the loopback, it indicates that the fault is on the MSC side oron the A interface. If MS A cannot hear MS B either, locate the fault by performing aremote speech channel loopback in the BTS direction or performing a DSP speechchannel loopback. Figure 10-4 shows the process of a remote speech channel loopbackin the MSC direction.

– In the BTS direction: Speech sent from the MS A to the MSC undergoes a loopback onthe A interface board towards the BTS but is still sent to the MSC. Normally, after sucha loopback, MS A cannot hear MS B but can hear itself; MS B can hear MS A. If MSA cannot hear itself after the loopback, it indicates that the fault is on the BSS side. IfMS B cannot hear MS A either, locate the fault by performing a remote speech channel



10-7

loopback in the MSC direction or performing a DSP speech channel loopback. Figure10-5 shows the process of a remote speech channel loopback in the BTS direction.

Figure 10-4 Remote speech channel loopback in the MSC direction

Figure 10-5 Remote speech channel loopback in the BTS direction

l DSP speech channel loopback

– In the DSP speech channel loopback over the A interface, the loopback point is set atthe RX port of the DSP that receives the data from the A interface. Then, the dataprocessed by the DSP is sent to the MS, and the data received from the A interface issent out as the source data. Therefore, the bi-directional loopback to both the MS andthe MSC is achieved on the DSP, as shown in Figure 10-6.

– In the DSP speech channel loopback over the Abis interface, the loopback point is setat the RX port of the DSP that receives the data from the Abis interface. Then, the dataprocessed by the DSP is sent to the MSC, and the data received from the Abis interfaceis sent out as the source data. Therefore, the bi-directional loopback to both the MS andthe MSC is achieved on the DSP, as shown in Figure 10-7.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-6 A interface loopback

Figure 10-7 Abis interface loopback

10.2 Browsing Configuration DataThis describes how to browse the configuration data, including the configuration data of BSCs,BTSs, TRXs, and channels.

Prerequisite


Procedure


Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Browse ConfigurationData. The Browse Configuration Data tab page is displayed.



10-9

Step 3 In the Browse Items navigation tree, select the items to be browsed and click Browse. Thecorresponding configuration data is displayed on the right area.

Step 4 To view the complete information, click Browse All. The linked form is displayed, showing thefull information about the configuration data.

Step 5 To create a new template of browsing items, click New. In the displayed New dialog box, setthe 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 DataThis section describes how to back up system data on the OMU. The system data includesconfiguration data, alarm configuration data, and performance configuration data.


Contextl 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_linkerdirectory. With the latest backup data, you can recover the system.

l If you need to recover only OMU configuration data, run the RTR DB command and selecta corresponding data backup file for data recovery.


1. Click Device Maintenance on the LMT main page. The Device Maintenance tabpage is displayed.

2. In the BSC Maintenance tab page, choose BSC Maintenance > Backup Data. TheBackup Data dialog box is displayed with information about backup files saved inthe OMU active workspace installation directory\data\backup directory.

3. In the displayed Backup Data dialog box, click Backup to back up system data onthe OMU.

NOTE

l The default directory for saving backup files is OMU active workspace installation directory\data\backup. If such a directory does not exist, it will be created automatically.

l If the name of a backup file is not typed, the file is named BKPDB_#_*.bak automatically.Here, "#" stands for the detailed version information of the working OMU and "*" stands forthe current system time when the backup is performed. When the number of backup files in thebackup directory exceeds 30, the earliest backup file is automatically deleted.

l The following special characters are forbidden in the file name: "\", "/", ":", "*", "?", ""," "<",">", "|", "(", ")", "&" and "$".

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.


LMT User Guide


Issue 07 (2011-01-30)

4. In the displayed Backup Data dialog box, select a backup file and clickDownLoad to download the backup file to a local path on the LMT PC.

NOTE

Click Refresh to refresh backup files saved in the OMU active workspace installation directory\data\backup directory in the Backup Data dialog box.

l Through an MML command1. 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 DataThis section describes how to restore configuration data on the OMU.


Context

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



2. In the BSC Maintenance tab page, choose BSC Maintenance > Restore Data. TheRestore Data dialog box is displayed with information about data backup files savedin the OMU active workspace installation directory\data\backup directory.

3. Optional: In the displayed Restore Data dialog box, click Upload to upload a backupfile on the LMT PC to the OMU.

NOTE

Click Refresh to refresh backup files saved in the OMU active workspace installation directory\data\backup directory in the Restore Data dialog box.

4. In the displayed Restore Data dialog box, click Restore Data to restore configurationdata on the OMU.

l Through an MML command



10-11

1. Run the LST BKPFILE command to query data backup files saved in the OMUactive workspace installation directory\data\backup directory.

2. Run the RTR DB command to restore configuration data on the OMU.

----End

10.5 Maintaining the EquipmentThis section describes how to maintain the BSC equipment.


10.5.2 Querying BSC Board Clock StatusThis describes how to query the clock status of the BSC board.



10.5.5 Maintaining Fan BoxThis describes how to query the attributes of a fan box and how to reset a faulty fan box.

10.5.6 Maintaining the Power Distribution BoxThis describes how to maintain the power distribution box (PDB) and reset the faulty PDB. Ifthe PDB is faulty and the main processing board is normal, you can reset the PDB to restore thefunctions of power supply detection and overvoltage protection.



Context





LMT User Guide


Issue 07 (2011-01-30)

2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >Query BSC Board Information. The Query BSC Board Information dialog boxis displayed.

3. In the Query BSC Board Information dialog box, set the parameters as required,and click Query. The operation result is displayed, as shown in Figure 1.

NOTE

On the device panel, you can also perform this operation by right-clicking a board and thenchoose 9.1.5 Querying the BSC Board Information from the shortcut menu.

Figure 10-8 Querying results of board status


1. Run the DSP BRD command to query the information about the BSC board.

----End

10.5.2 Querying BSC Board Clock StatusThis describes how to query the clock status of the BSC board.

Prerequisite




10-13



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >Query BSC Board Clock Status. The Query BSC Board Clock Status dialog boxis displayed.

3. In the Query BSC Board Clock Status dialog box, set the parameters as required,and click Query. The query result is displayed, as shown in Figure 1.

Figure 10-9 Querying results of BSC Board Clock Status


1. Run the DSP CLK command to query the clock status of the BSC board.

----End




LMT User Guide


Issue 07 (2011-01-30)


Context


disrupted. Thus, perform this task with caution.l Resetting the board may affect the ongoing services. Thus, you are advised to perform the

switchover when the traffic load is light, for example, in the middle of the night.l All boards configured in active/standby mode support switchover operations. Only the active

board can initiate the switchover, except the OMUa board. The OMUa board also supportsswitchover initiated by the standby board.

You can switch over the active BSC board and the standby BSC board through menu operationsor through MML commands.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >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 clickSwitch to switch over the boards. The operation result is displayed, as shown in Figure1.

NOTE

On the device panel, you can also perform this operation by right-clicking a board and thenchoose 9.1.7 Switching Over the BSC Boards from the shortcut menu.



10-15

Figure 10-10 Switching over a BSC board


1. Run the SWP BRD command to switch over the BSC boards.

----End



l The boards are present and work normally.

Context


disrupt the ongoing services. Thus, perform this operation with caution.

l Resetting the board may affect the ongoing services. Therefore, you are advised to performthe switchover when the traffic load is light, for example, in the middle of the night.

You can reset the BSC board through menu operations or through MML commands.


LMT User Guide


Issue 07 (2011-01-30)



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >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 clickReset to reset the board. The operation result is displayed, as shown in Figure 1.

NOTE

On the device panel, you can also perform this operation by right-clicking a board and thenchoose 9.1.6 Resetting the BSC Board from the shortcut menu.

Figure 10-11 Resetting the BSC Board


1. Run the RST BRD command to reset a BSC board.

----End

10.5.5 Maintaining Fan BoxThis describes how to query the attributes of a fan box and how to reset a faulty fan box.

Prerequisite




10-17



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device >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 clickApply. To reset the fan box, choose the Reset operation, and click Apply. The queryresult is displayed, as shown in Figure 1.

NOTE

l On the device panel, you can also perform this operation by right-clicking a board and thenchoose Maintain Fan Box from the shortcut menu.

l The maintenance of the independent fan subrack is the same as that of the fan box.

Figure 10-12 Querying the fan box


LMT User Guide


Issue 07 (2011-01-30)


1. Run the DSP FAN command to query the status of the fan box.

----End

10.5.6 Maintaining the Power Distribution BoxThis describes how to maintain the power distribution box (PDB) and reset the faulty PDB. Ifthe PDB is faulty and the main processing board is normal, you can reset the PDB to restore thefunctions of power supply detection and overvoltage protection.


ContextThe power distribution box provides the lightning protection processing and overcurrentprotection processing for the power input to the cabinet and then supplies the power outputs tothe other subsystems of the cabinet. The PDB also detects the states of the input voltage and theoutput voltage and generates the alarm signals if the state is abnormal.

Procedure


Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device > MaintainPower 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, andclick Apply. To reset the PDB, select Reset from the Operation drop-down list, and clickApply. The operation result is displayed, as shown in Figure 1.



10-19

Figure 10-13 Maintaining the Power Distribution Box

----End

10.6 Maintaining Transmission and SignalingThis section describes how to maintain the signaling link and the ports on the interface boards.In the Device Navigation Tree, right-click the BSC6900 node, and choose MaintainTransmission and Signaling from the shortcut menu to perform the relevant tasks.

10.6.1 Maintaining LAPD LinksThis section describes how to locate an LAPD link fault in TDM transmission mode. Byperforming this task, you can query the status of LAPD links of the following types: operationand maintenance link (OML), radio signaling link (RSL), extended maintenance link (EML),extended signaling link (ESL), and download maintenance link (DML). You can also query the


LMT User Guide


Issue 07 (2011-01-30)

status of LAPD links of the PCU-BSC signaling link (PBSL) type when the external PCU isconfigured. You can also reset or perform loopback tests on LAPD links.

10.6.2 Querying Ater Link StatusThis section describes how to query the status of the Ater interface OML when the TC subrackis configured on the MSC side.

10.6.3 Maintaining SCCP LinksThis describes how to maintain an SCCP link. By monitoring the status of the DPCs andsubsystems, you can know whether the SCCP signaling link works normally.

10.6.4 Maintaining MTP3 LinksThis section describes how to query the link status, route status, and DSP status of MTP3 links,and how to activate, deactivate, disable, and enable MTP3 links based on the query result.

10.6.5 Querying the Status of MTP2 LinksThis describes how to query the status of an MTP2 link.

10.6.6 Querying MTP2 Link Statistical InformationThis section describes how to query the statistical information about an MTP2 link.

10.6.7 Querying the Electrical Interface Board Port InformationThis section describes how to query the port status of the electrical interface board, includingE1/T1 attributes and E1/T1 performance statistics.

10.6.8 Querying the Optical Interface Board Port InformationThis section describes how to query the port information about an optical interface board.

10.6.9 Looping Back the Interface Board PortThis describes how to query the loopback information of the electric interface boards, includingthe loopback port, loopback mode, and loopback status.

10.6.10 Looping Back the Interface Board Port TimeslotThis describes how to query the loopback mode and loopback status of the timeslot loopbackon the ports of the interface boards.

10.6.11 Maintaining IP LinksThis section describes how to query the status of IP links, including the PPP link, MLPPP link,and MLPPP link group.

10.6.1 Maintaining LAPD LinksThis section describes how to locate an LAPD link fault in TDM transmission mode. Byperforming this task, you can query the status of LAPD links of the following types: operationand maintenance link (OML), radio signaling link (RSL), extended maintenance link (EML),extended signaling link (ESL), and download maintenance link (DML). You can also query thestatus of LAPD links of the PCU-BSC signaling link (PBSL) type when the external PCU isconfigured. You can also reset or perform loopback tests on LAPD links.

Prerequisite


Context

Figure 10-14 shows the internal transmission on the interface boards.



10-21

Figure 10-14 Internal transmission on interface boards

When the service incurs errors, you can query the status of LAPD links. If the status of links isFaulty, perform the loopback test to loop back the signals sent by the CPU, and determinewhether the transmission on the CPU of the corresponding board is normal based on the tracedsignaling flow.

The loopback test can be line loopback, LVDS loopback, and MCC loopback. These threeloopback tests help to locate the fault.

l As shown in Figure 10-14, line loopback is performed at the port of the interface board. Ifthe line loopback is successful, then you can infer that the transmission within the BSC isnormal. Thus, the fault lies in the transmission network or the peer end.

l As shown in Figure 10-14, the LVDS loopback is performed between the LVDS logicmodule and the TDM module. If the LVDS loopback is successful, then you can infer thatthe transmission between the XPU and the LVDS logical module of the interface board isnormal. Thus, the fault lies in the part between the LVDS logical module and the peer end.

l As shown in Figure 10-14, MCC loopback is performed between the CPU and the LVDSlogical module. If the MCC loopback is successful, then you can infer that the transmissionbetween the XPU and the CPU is normal. Thus, the fault lies in the part between the CPUand the peer end.

NOTE

Here, if loopback frames can be traced through signaling tracing on the relevant links, the loopback issuccessful.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Maintain LAPD Link. The Maintain LAPD Linktab page is displayed.

3. Set LAPD Link Type and BTS Type and click Query. The LAPD link query resultsof the selected BTSs are displayed, as shown in Figure 10-15.

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.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-15 Results of querying LAPD link status

4. Select the target link in the Query Result area, set the parameters in the LoopbackType area, and click Loop Test or Reset.

NOTE

l When the Loopback Type is set to Line Loop, a loopback failure alert message is displayedif you click Loop Test to perform the loopback test. In this case, you need to manuallydisconnect the E1 link to the peer end and then connect the RX port to the TX port at thelocal 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 onlythe 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

10.6.2 Querying Ater Link StatusThis section describes how to query the status of the Ater interface OML when the TC subrackis configured on the MSC side.


l The HDLC link is configured.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Query Ater Link Status. The Query Ater LinkStatus dialog box is displayed.

3. Click Query to query the status of the Ater link. The operation result is displayed, asshown in Figure 1.



10-23

Figure 10-16 Querying Ater Link Status


1. Run the LST ATERSL command to query the status of an Ater signaling link.

----End

10.6.3 Maintaining SCCP LinksThis describes how to maintain an SCCP link. By monitoring the status of the DPCs andsubsystems, you can know whether the SCCP signaling link works normally.


l The XPUa board in the subrack corresponding to the DPC is functional.

Contextl 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).

l The subsystem number defined by the LMT is of the following types: 1, 1 (local), 254, and254 (local). The values 1 and 1 (local) refers to the peer end and the local end of the SCCPmanagement subsystem respectively. The values 254 and 254 (local) refers to the peer endand the local end of the SCCP service subsystem respectively.

l You are prohibited to enable or disable the management subsystem. You can enable ordisable only the service subsystem.




LMT User Guide


Issue 07 (2011-01-30)

2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Maintain SCCP Link. The Maintain SCCP Linkdialog box is displayed.

3. In the DPC and Subsystem Operation tab pages, set the parameters in the Locationand Operation area to maintain the SCCP link as required. The operation result isdisplayed, as shown in Figure 1.

NOTE

Select Query, Inhibit, or Uninhibit from the Operation drop-down list to perform thecorresponding operation.

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-25

10.6.4 Maintaining MTP3 LinksThis section describes how to query the link status, route status, and DSP status of MTP3 links,and how to activate, deactivate, disable, and enable MTP3 links based on the query result.

Prerequisitel You have logged in to the LMT.l The XPUa board that controls the MTP3 links is functional.l The MTP3 links are configured.

ContextYou can query the status of the MTP3 link by link signaling set or by destination signaling point(DSP).l Query by link signaling set

Each MTP3 link has a unique link number. One interface board corresponds to multiplelinks. You can specify a board and a link number to query the status of an MTP3 link.

l Query by DSPOne DSP code (DPC) can be used by multiple MTP3 links. You can query the status ofmultiple MTP3 links by querying the corresponding DPC.

The operations related to an MTP3 link are as follows:l Activating: This operation is performed to set up a new MTP3 link.l Deactivating: This operation is performed to remove the MTP3 links and the MTP2 links.l Disabling: This operation is performed to disable the MTP3 links, but the MTP2 links are

still available.l Enabling: This operation is performed to enable the MTP3 links.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Maintain MTP3 Link. The Maintain MTP3 Linkdialog box is displayed.

3. In the MTP3 Link State, MTP3 Route State, and MTP3 State Between SP tabpages, set the required parameters, and click Query to query the status of the MTP3links, MTP3 routes, or MTP3 signaling points respectively. The operation result isdisplayed, as shown in Figure 1.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-18 Querying MTP3 Links

4. In the MTP3 Operation tab page, set the parameters in the Location area, and click

Apply. The operation result is displayed, as shown in Figure 1.

NOTE

The parameter Operation can be Activate, Deactivate, Inhibit, or Uninhibit.



10-27

Figure 10-19 Maintaining MTP3 Links


1. You can maintain an MTP3 link as follows.– Run the DSP MTP3LNK to query the status of MTP3 links.– Run the DSP MTP3RT to query the status of MTP3 route.– Run the DSP N7DPC command to query the status of the specified DPCs.– Run the ACT MTP3LNK command to activate MTP3 links.– Run the DEA MTP3LNK command to deactivate MTP3 links.– Run the INH MTP3LNK command to inhibit MTP3 links.– Run the UIN MTP3LNK command to uninhibit MTP3 links.

----End

10.6.5 Querying the Status of MTP2 LinksThis describes how to query the status of an MTP2 link.

Prerequisitel You have logged in to the LMT.l The EIUa or the OIUa boards are functional.


LMT User Guide


Issue 07 (2011-01-30)



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Query MTP2 Link Status. The Query MTP2 LinkStatus dialog box is displayed.

3. Set parameters in the Location area, and then click Query. The operation result isdisplayed, as shown in Figure 1.

Figure 10-20 Querying the Status of MTP2 Links


1. Run the DSP MTP2LNK command to query the status of an MTP2 link.

----End

10.6.6 Querying MTP2 Link Statistical InformationThis section describes how to query the statistical information about an MTP2 link.

Prerequisitel You have logged in to the LMT.l The EIUa or the OIUa boards are functional.




10-29


2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Query MTP2 Link Statistical Information. TheQuery MTP2 Link Statistical Information dialog box is displayed.

3. Set parameters in the Location area, and then click Query. The operation result isdisplayed, as shown in Figure 1.

Figure 10-21 Querying MTP2 Link Statistical Information


1. Run the DSP MTP2LNKSTCS to query the statistical information about an MTP2link.

----End

10.6.7 Querying the Electrical Interface Board Port InformationThis section describes how to query the port status of the electrical interface board, includingE1/T1 attributes and E1/T1 performance statistics.

Prerequisitel You have logged in to the LMT.l The electrical interface board to be queried runs properly.



LMT User Guide


Issue 07 (2011-01-30)


2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Query Electrical Interface Board PortInformation. The Query Electrical Interface Board Port Information dialog boxis displayed.

3. Set the port location information, and click Query to query the port information ofthe interface board. The operation result is displayed, as shown in Figure 1.

Figure 10-22 Querying the Electrical Interface Board Port Information


1. Run the DSP E1T1 command to query the port status of electrical interface boards.

----End

10.6.8 Querying the Optical Interface Board Port InformationThis section describes how to query the port information about an optical interface board.




10-31

l The optical interface board to be queried runs properly.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Query Optical Interface Board PortInformation. The Query Optical Interface Board Port Information dialog box isdisplayed.

3. Set the port location information, and click Query to query the port information aboutthe optical interface board. The operation result is displayed, as shown in Figure 1.

NOTE

J0 Display Mode and J1 Display Mode indicate the type of the overhead byte of the opticalport. You can choose to set the display modes to Hex Mode or String Mode. To query theoverhead byte of an optical port, run the DSP OPTOH command.

Figure 10-23 Querying the Optical Interface Board Port Information


1. Run the DSP OPT command to query the port information about an optical interfaceboard.

----End


LMT User Guide


Issue 07 (2011-01-30)

10.6.9 Looping Back the Interface Board PortThis describes how to query the loopback information of the electric interface boards, includingthe loopback port, loopback mode, and loopback status.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.l All the interface boards are functional.

ContextIf the loopback at the port of an interface board fails, you can infer that the transmission fromor to the interface board fails. Thus, you can locate the fault on the transmission link.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Interface Board Port Loopback. The InterfaceBoard Port Loopback dialog box is displayed.

3. Set the parameters in the Location area, and then click Query to query the loopbackresult. The operation result is displayed, as shown in Figure 1.

Figure 10-24 Looping Back the Interface Board Port



10-33

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 statusfails to be queried.

6. Click Stop to end the optical port loopback.l Through MML commands

1. You can set the loopback mode of the interface boards as follows.– Run the SET E1T1LOP command to set the loopback mode of the electrical

interface board ports.– Run the SET OPTLOP command to set the loopback mode of the optical interface

board ports.

----End

10.6.10 Looping Back the Interface Board Port TimeslotThis describes how to query the loopback mode and loopback status of the timeslot loopbackon the ports of the interface boards.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.l All the interface boards are functional.



2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Interface Board Port Timeslot Loopback. TheInterface Board Port Timeslot Loopback dialog box is displayed.

3. Set the parameters in the Location area, and then click Query to query the loopbackresult. The operation result is displayed, as shown in Figure 1.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-25 Looping Back the Interface Board Port Timeslot

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 statusfails to be queried.

6. Click Stop to stop the loopback.l Through MML commands

1. You can set and query the loopback attributes of the timeslot carried by the ports ofthe interface boards as follows.– Run the DSP E1T1TS command to query the loopback attributes of electrical

interface ports.– Run the DSP OPTLOP command to query the loopback attributes of electrical

interface ports.– Run the SET E1T1LOP command to set the loopback mode of the electrical

interface board port timeslots.– Run the SET OPTLOP command to set the loopback mode of the optical interface

board port timeslots.

----End



10-35

10.6.11 Maintaining IP LinksThis section describes how to query the status of IP links, including the PPP link, MLPPP link,and MLPPP link group.




2. In the BSC Maintenance tab page, choose BSC Maintenance > MaintainTransmission and Signaling > Maintain IP Link. The Maintain IP Link dialogbox is displayed.

3. In the Maintain IP Link dialog box, set the parameters as required, and clickQuery to query the status of an IP link. The operation result is displayed, as shownin Figure 1.

Figure 10-26 Maintaining IP Links


1. You can query the status of an IP link as follows.– Run the LST PPPLNK or DSP PPPLNK command to query the status of a PPP

link.


LMT User Guide


Issue 07 (2011-01-30)

– Run the LST MPLNK orDSP MPLNK command to query the status of an MLPPPlink.

– Run the LST MPGRP orDSP MPGRP command to query the status of an MLPPPgroup.

----End

10.7 Maintaining BSC User ResourcesThis section describes how to maintain the user resources, including the port timeslot, interfacecircuit, TC resources, call resources, DSP channel or link, external speech channel, and internalspeech channel. In the Device Navigation Tree, right-click the BSC6900 node, and chooseMaintain User Resources from the shortcut menu to perform the relevant tasks.

10.7.1 Analyzing Voice LogsThis section describes how to enable the system to automatically analyze the one-way audiologs of the voice logs. The one-way audio log analysis helps quickly identify the node whereone-way audio occurs. Note that both current voice logs and history voice logs can be analyzed.

10.7.2 Querying the Status of the Abis Interface TimeslotThis 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.

10.7.3 Maintaining Ater Interface ResourcesThis section describes how to maintain the Ater interface resources. When the TC subrack isconfigured on the MSC side, the MPS/EPS communicates with the TC subrack over the Aterinterface.

10.7.4 Maintaining the Circuits on the A InterfaceThis section describes how to query the circuit state on the A interface, and how to block,unblock, and reset the A interface circuits based on the query results.

10.7.5 Querying DSP ResourcesThis section describes how to query the information about the DSP resources and the DSP linkstatus.

10.7.6 Maintaining DSP ResourcesThis task describes how to query or modify the DSP status (Inhibited or Uninhibited).

10.7.7 Querying Single User ResourcesThis 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 theinformation about BM subrack and TC subrack.

10.7.8 Collecting BSC Local InformationThis section describes how to collect the BSC or BTS statistics, including the performancestatistics, logs, and alarm files.

10.7.9 Looping Back Remote Speech ChannelThis section describes how to start or end the remote speech channel loopback and how to querythe status of the current remote speech channel loopback.

10.7.10 Testing the Internal Speech ChannelThis section describes how to test the internal speech channels to locate the speech service faultin the BSC.



10-37

10.7.11 Looping Back DSP Channel/LinkThis section describes how to loop back the DSP speech channel. By performing this task, youcan see whether the speech problem is caused by codec error of the internal speech processingunit of the BSC.

10.7.1 Analyzing Voice LogsThis section describes how to enable the system to automatically analyze the one-way audiologs of the voice logs. The one-way audio log analysis helps quickly identify the node whereone-way audio occurs. Note that both current voice logs and history voice logs can be analyzed.



Procedurel In GUI mode

1. On the LMT, click Device Maintenance. The Device Maintenance tab page isdisplayed.

2. Click BSC Maintenance > Maintain User Resources > Voice log Analysis. TheVoice log Analysis dialog box is displayed.

3. Specify the related parameters, and then click Analyze. The analysis result is displayedin the form of a report. Click Save and specify a name for the report. The analysisresult is saved.

NOTE

l Today: When Today is selected, the system quickly analyzes all the one-way audio logs thatare generated on that day. That is, operators do not need to specify Time Last, and the systemautomatically obtains the voice logs that are generated on that day from the OMU. Here, "thatday" refers to the day set on the LMT.

History: When History is selected, operators need to specify Time Last. The system obtainsthe voice logs that are generated during the period of time specified by Time Last from theOMU and then analyzes the logs. The system can analyze the logs for a maximum of 30 daysat a time. If operators need to analyze the voice logs for only a day, operators can specify TimeLast accordingly.

l The analysis result is provided based on the analysis of a great number of one-way audio logs.If, therefore, the number of logs that meet the requirements is smaller than 11, the system doesnot analyze the logs.

l The analysis result involves Fault Type, Fault Unit, Fault Times, Fault Detail Information,number of logs, and time last. Fault Unit are of six types, namely, Cell Id, TrxId, Abis InterfaceBoard, Switching Unit, TC Unit, and A Interface Unit.

l Only the three types of fault units whose number of one-way audio occurrences rank the top 3are displayed in the analysis result. If the actual number of the types of fault units involved issmaller than three, the actual types of fault units are displayed.

----End

10.7.2 Querying the Status of the Abis Interface TimeslotThis 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.


LMT User Guide


Issue 07 (2011-01-30)

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.l The EIUa/OIUa, FG2a/GOUa, or PEUa boards are working normally.

Context

One EIUa board has 32 ports. Each of them corresponds to a site. The BSC can provide 256timeslots of 8 kbit/s or 128 timeslots of 16 kbit/s on the Abis interface.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Query Abis Interface Timeslot Status. The Query Abis InterfaceTimeslot Status dialog box is displayed.

3. Set the parameters in the Location area, and then click Query to query the status ofthe Abis interface timeslots. The operation result is displayed, as shown in Figure 1.

Figure 10-27 Querying the Status of the Abis Interface Timeslot




10-39

1. Run the DSP ABISTS to query the status of Abis interface timeslots.

----End

10.7.3 Maintaining Ater Interface ResourcesThis section describes how to maintain the Ater interface resources. When the TC subrack isconfigured on the MSC side, the MPS/EPS communicates with the TC subrack over the Aterinterface.

Prerequisitel You have logged in to the LMT with an account authorized for this operation.l The TC subrack is configured on the MSC side.

Procedurel To set Ater resources, do as follows:


2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Maintain Ater Interface Resources. The Maintain Ater InterfaceResources dialog box is displayed.

3. In the Set Ater Resources tab page, set parameters in the Location area and clickQuery to query status of timeslots on the Ater interface. Figure 10-28 shows theresults.

NOTE

l If links need to be blocked, select one or more links, and click Block.

l If links need to be unblocked, select one or more links, and click Unblock.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-28 Results of querying timeslot status on the Ater interface

l To query Ater resources, do as follows:


2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Maintain Ater Interface Resources. The Maintain Ater InterfaceResources dialog box is displayed.

3. In the Query Ater Resources tab page, set parameters in the Location area and clickQuery to query Ater resources. Figure 10-29 shows the results.



10-41

Figure 10-29 Results of querying Ater resources

----End

10.7.4 Maintaining the Circuits on the A InterfaceThis section describes how to query the circuit state on the A interface, and how to block,unblock, and reset the A interface circuits based on the query results.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.l All the EIUa/OIUa boards are functional.

ContextThe BSC supports 32 circuits of 64 kbit/s on the A interface. You can query the status of these32 circuits and block, unblock, or reset any circuit on the LMT.


LMT User Guide


Issue 07 (2011-01-30)

CAUTIONYou can reset the A interface circuits, that is, the A interface circuits of the entire BSC or the Ainterface circuits between two signaling links of the MSC. This operation may affect the services.Therefore, perform this task with caution.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Maintain A Interface Resources. The Maintain A InterfaceResources dialog box is displayed.

3. In the Maintain A Interface Circuit dialog box, set the parameters as required, andclick Query to query the status of A interface circuits. The operation result isdisplayed, as shown in Figure 1.

Figure 10-30 Querying the Circuits on the A Interface

4. Select one or more query results, and click Block, Unblock, or Reset as required.



10-43

l Through MML commands1. You can maintain the A interface circuits as follows.

– Run the DSP ACIC to query the status of A interface circuits.– Run the RST ACIC command to reset A interface circuits.– Run the UBL ACIC command to uninhibit A interface circuits.– Run the BLK ACIC command to inhibit A interface circuits.

----End

10.7.5 Querying DSP ResourcesThis section describes how to query the information about the DSP resources and the DSP linkstatus.

Prerequisitel You have logged in to the LMT.l The DPU board is functional.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Query DSP Resources. The Query DSP Resources dialog box isdisplayed.

3. Set parameters in the DSP Resource Info tab page and click Query to query the DSPresource status. Figure 10-31 shows the results.


LMT User Guide


Issue 07 (2011-01-30)

Figure 10-31 Results of querying DSP resources

4. Set parameters in the DSP Channel/Link Status tab page and click Query to query

the DSP channel/link status. Figure 10-32 shows the results.



10-45

Figure 10-32 Results of querying the DSP channel/link status


1. Run the DSP DSPLINK command to query the status of a DSP link.

----End

10.7.6 Maintaining DSP ResourcesThis task describes how to query or modify the DSP status (Inhibited or Uninhibited).

Prerequisitel You have logged in to the LMT.l The DPU board is functional.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Maintain DSP Resources. The Maintain DSP Resources dialog boxis displayed.


LMT User Guide


Issue 07 (2011-01-30)

3. In the displayed Maintain DSP Resources dialog box, set the parameters in theLocation area, and click Query. The operation result is displayed, as shown in Figure1.

Figure 10-33 Maintaining DSP Resources Iterface

4. Select one or more DSPs, and choose an option from Inhibit Option. Then, click

Inhibit or Uninhibit to modify the DSP status.l Through MML commands

1. You can maintain the DSP resources as follows.

– Run the INH DSP command to inhibit the DSP.

– Run the UIN DSP command to uninhibit the DSP.

----End

10.7.7 Querying Single User ResourcesThis 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 theinformation about BM subrack and TC subrack.




10-47

l The communication between the BSC6900 and the MSC is normal.l The MS is in a call.

Procedure


Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Maintain User Resources >Query Single-User Resources. The Query Single-User Resources dialog box is displayed.

Step 3 In the Query Single-User Resources dialog box, set the parameters as required, and clickQuery 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 peerend:

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 callingMS is displayed on the screen of the called MS. For example, if 54321 is displayed on the calledMS, set the MSISDN to 54321.

l If you query the user messages through TMSI or IMSI, you must determine the reassignment strategyon 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 theMSC.

l If you select TLLI, you query the TLLI of the MS performing PS services. You can run the DSPMSCONTEXT command to query the TLLI of the MS.

----End

10.7.8 Collecting BSC Local InformationThis section describes how to collect the BSC or BTS statistics, including the performancestatistics, logs, and alarm files.

Prerequisite


Context

CAUTIONOnly one task can be created at one time.

You can collect the BSC local information through menu operations or through MMLcommands.


LMT User Guide


Issue 07 (2011-01-30)



2. In the BSC Maintenance tab page, choose Maintain BSC > Maintain UserResources > Collect BSC Local Information. The Collect BSC LocalInformation tab page is displayed.

3. Set the time period for collecting the statistics in the Time Setting area.

NOTE

If you select All Time, the LMT retrieves the time limit from the configuration file. The timelimit is 30 days by default.

4. Select the fault type from the Fault List in the Set Basic Information area to collectthe required fault statistics. The corresponding file type is automatically selected. Youcan select more file types from the File Type List to collect the correspondingstatistical files.

NOTE

If you select BTS Fault from the Fault List, the Select Sites area is activated so that you canfurther specify the target BTS to collecting the statistics.

5. Set the FTP server parameters in the Upload configure area, and click Execute tocollect the BSC statistics. The progress of collecting the statistics is displayed in theProgress(%) 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 savingthe uploaded files on the FTP server in the Upload Path box. FTP User Name and FTPPassword are admin by default. You can also change the default settings on the FTP server.

l If you select The common debug log in the File Type List, the Subrack No. in theSetting 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.7.9 Looping Back Remote Speech ChannelThis section describes how to start or end the remote speech channel loopback and how to querythe status of the current remote speech channel loopback.



l The MS is in conversion.



10-49

ContextThe speech in a system can be transmitted in sending direction and receiving direction. Eachdirection has its own channel. On a speech channel, you can locate the segment where the speechproblem occurs by comparing the loopback speech with the original speech.

You can detect the speech channel fault by performing the remote speech channel loopback onthe A interface and the Abis interface. If it is the internal problem that results in the speechchannel fault, you can start the internal testing to locate fault.

The loopback can be remote loopback or local loopback. That is, the loopback can be performedin the direction towards the MSC or in the direction towards the MS.

For example, Figure 10-34 shows the loopback on the Abis interface board, DPU board, and Ainterface board in the direction of MSC in a IP network. If the result of the loopback on the Ainterface board is normal, then you can infer that the speech problem is not introduced by theBSC but by the CN or peer end. If the result of DPU loopback is normal but that of the A interfaceboard is abnormal, then you can infer that the speech problem is located between the DPU andthe A interface, and so forth.

Figure 10-34 Remote speech channel loopback



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Remote Speech Channel Loopback. The Remote Speech ChannelLoopback 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 issuccessfully started.


LMT User Guide


Issue 07 (2011-01-30)

NOTE

l If you query the user messages through MSISDN, you are advised to set MS ID to that ofthe peer end:

l (Recommended) To query the calling MS, set the MS ID to that of the called MS. Forexample, 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 displayedon the called MS. For example, if 54321 is displayed on the called MS, set the MSISDNto 54321.

l If you query the user messages through TMSI or IMSI, you must determine thereassignment 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 availableto the MSC.

4. After the loopback is started, click Query to query the remote speech channelloopback.

5. Click Cancel stop the remote speech loopback.

NOTE

To end a remote speech loopback, select IMSI, IMEI, TMSI, or MSIDSN in the MS Typearea to ensure that the parameter setting in the MS Type area is the same as that is previouslyset for the loopback.

If different MS IDs are used for one MS to perform the remote speech channel loopback, youneed to use corresponding MS ID to end the remote speech channel loopback.

l Through MML commands1. 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.7.10 Testing the Internal Speech ChannelThis section describes how to test the internal speech channels to locate the speech service faultin the BSC.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the MSC is normal.l The MS is in conversion.

ContextFor each CS connection, the BSC internal speech channel consists of multiple TDM paths. Thus,you can perform the internal speech channel test to check the status of each path and locate thespeech fault.



10-51

For example, in the case of TDM transmission in BM/TC combined mode, two TDM paths areused in the BSC for each CS connection: one from the Abis interface to the DSP, and the otherfrom the DSP to the A interface. If the speech problem is located within the BSC, the specificfaulty path can be located through the internal speech channel test.



2. In the BSC Maintenance tab page, choose BSC Maintenance > Maintain UserResources > Test Internal Speech Channel. The Test Internal Speech Channeldialog box is displayed.

3. In the Test Internal Speech Channel dialog box, set the parameters as required, andclick Start to start testing the internal speech channels.

NOTE

l If you query the user messages through MSISDN, you are advised to set MSISDN to thatof 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 isdisplayed on the called MS, set the MSISDN to 54321.

l If you query the user messages through TMSI or IMSI, you must determine thereassignment 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 availableto the MSC.

l Through MML commands1. Run the CHK INNSPCH command to test the internal speech channels.

----End

10.7.11 Looping Back DSP Channel/LinkThis section describes how to loop back the DSP speech channel. By performing this task, youcan see whether the speech problem is caused by codec error of the internal speech processingunit of the BSC.


ContextDSP stands for the chip used for digital signal processing. The DSP is configured in only theDPU board for process the arithmetic and codec algorithms.

When looping back consecutive paths of a DSP on the DPU board, you can choose to loop thespeech signals from the MSC or BTS through the TC subrack or not through the TC subrack.Thus, you can determine whether the fault resides in the DSP.


LMT User Guide


Issue 07 (2011-01-30)

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 theMSC does not go through the TC subrack whereas the loopback towards the BTS goesthrough the TC subrack.

l Abis interface loopback:

It supports the loopback towards the MSC and towards the BTS. The loopback towards theMSC goes through the TC subrack whereas the loopback towards the BTS does not gothrough the TC subrack.

If user B hears its own voice after a DSP speech loopback on the A interface whereas it cannothear its own voice after a DSP speech loopback on the Abis interface, then you can infer thatthe fault resides in the TC subrack.

Similarly, if user A hears its own voice after the Abis interface loopback whereas it cannot hearits own voice after the A interface loopback, then you can infer that the fault resides in the TCsubrack.

Table 10-2 shows the results of a DSP channel loopback test in normal cases.

Table 10-2 Results of a DSP channel loopback test

Loopback Mode/Test MS A (Under the Local BSC) B (Not Under the LocalBSC)

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

Figure 10-35 and Figure 10-36 shows the direction of speech flows in TDM transmission modeafter DSP channel/link loopback is performed over the A and Abis interfaces respectively.

Figure 10-35 DSP channel/link loopback over the A interface



10-53

Figure 10-36 DSP channel/link loopback over the Abis interface


displayed.

Step 2 In the BSC Maintenance tab page, choose BSC Maintenance > Maintain User Resources >DSP Channel/Link Loopback. The DSP Channel/Link Loopback dialog box is displayed.

Step 3 Set parameters under Channel Setting and Operation Setting, and then click Query to querythe status of DSP channel/link loopback. Figure 10-37 shows the results.

Figure 10-37 Results of querying the status of DSP channel/link loopback


LMT User Guide


Issue 07 (2011-01-30)

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 DSP channelchanges due to handover, you need to query the information about the new DSP channel and then performthe loopback on the new DSP channel.

Step 5 Click Stop to stop the loopback.

----End

10.8 Querying Board Version InformationThis section describes how to query the information about the software version, hardwareversion, and patch version of the board.

Prerequisitel You have logged in to the LMT.l The target board works normally.



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.

l Through MML commands1. Run the LST PATCH or DSP PATCH command to query the patch version.

----End



10-55

11 BTS Maintenance

About This Chapter

This chapter describes how to maintain the BTS, including the BTS versions, equipment, andboards.

11.1 Concepts Related to BTS MaintenanceThis describes the basic concepts related to the BTS maintenance: BTS attributes and cellforcible handover mode.

11.2 Query Running Software Version of a BoardThis function is used to query the type, software version, and clock status of a board. You canquery the board running software version of several BTSs at a time.

11.3 Downloading the BTS SoftwareThis section describes how to download the BTS software from the LMT PC to the FTP server.

11.4 Loading the BTS SoftwareThis section describes how to load the BTS software on the OMU to the main processing boardof the BTS.

11.5 Activating BTS SoftwareThis describes how to activate the version software loaded onto the board.

11.6 Querying BTS Running StatusThis section describes how to query the operating status of a BTS and cells under the same BSCto determine whether the BTS operates normally. You can query the operating status of multipleBTSs at one time.

11.7 Querying BTS Board Matching ResultThis describes how to query whether the actual BTS board type matches with the configuredone. This operation is applicable to multiple BTSs simultaneously.

11.8 Querying BTS AttributesThis describes how to query the BTS working status and attributes to verify the software andhardware configuration of a BTS.

11.9 Resetting the BTS by LevelsThis describes how to reset a BTS, cell, or TRX to update the configuration data when the BTS,cell, or TRX is faulty.

BSC6900 GSMLMT User Guide 11 BTS Maintenance


11-1

11.10 Browsing BTS Initialization Process MessageThis section describes how to browse the initialization process of all the BTSs to see whetherthe BTS is reset. If the initialization fails, this message shows the failure cause that helps tolocate the fault.

11.11 Modifying Administrative StateThis section describes how to change the administrative state of the cell, TRX, and channel.

11.12 Forced HandoverThis section describes how to hand over the services in the cell, on the TRX, or on a channelforcibly over to another cell, TRX, or channel. When you maintain the BTS device, you needto perform this operation to hand over the services to another normal working area so as to avoidcall drops.

11.13 Monitoring Channel StatusThis describes how to monitor the occupation of all the channels and sub-channels.

11.14 Monitoring Interference Band of ChannelThis describes how to detect the interference band rank on the idle channel to monitor theinterference conditions on the channel.

11.15 Maintaining SiteThis section describes how to maintain the sites.

11.16 Maintaining the CellThis section describes how to maintain the cells.

11.17 Maintaining TRXsThis section describes how to maintain the TRXs.

11.18 Reference for BTS MaintenanceThis section describes the parameters used for BTS maintenance.

11 BTS MaintenanceBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

11.1 Concepts Related to BTS MaintenanceThis describes the basic concepts related to the BTS maintenance: BTS attributes and cellforcible handover mode.

11.1.1 BTS AttributesThe BTS attributes consist of the site attributes, cell attributes, TRX attributes, and channelattributes.

11.1.2 Cell Forced Handover ModeThis section describes the cell forced handover function of the BSC. The target cell can beselected by the BSC according to the measurement report or be specified by the user.

11.1.1 BTS AttributesThe BTS attributes consist of the site attributes, cell attributes, TRX attributes, and channelattributes.

Site AttributesTable 11-1 lists the site attributes.

Table 11-1 Site attributes

Attribute Name Description

Manufacture ID Manufacturer information about the BTS to be queried.

OML attribute Port number, timeslot number, and sub-timeslot number of the OMLlink.

Operation state Whether the current site is available.

Terminalequipment ID

Terminal equipment ID according to the LAPD protocol. The attributehere indicates the equipment ID of the current site, that is, the terminalequipment identifier (TEI) of the OML.

Clock attribute BTS clock status and information related to the clock parameters.

Extended alarmconfiguration

Configuration of the extended alarms of the current site.

Softwareconfiguration

Software configuration of the current site.

Power system type Power system type of the BTS cabinet.

SFP work mode SFP port connection information of the BTS.

TOP switchingparameters

Port and timeslot involved in TOP switching on the backplane of theBTS.

Hardwareconfiguration

Hardware configuration of the current site.



11-3

Cell AttributesTable 11-2 lists the cell attributes.

Table 11-2 Cell attributes

AttributeName

Description

Administrativestate

Administrative state of the current cell.

BCCHARFCN

Frequency of the main BCCH of the current cell.

Base stationidentity code

Consisting of BSIC, NCC, BCC.

Cell air-interface timer

Duration of timer T3105. This attribute is used in asynchronous cellhandover. Unit: ms

CCCH loadindicatingperiod

Interval for sending the overload messages.

CCCH loadthreshold

Ratio of number of successful random accesses to total number of collisionswithin the time.

Connectionfailure criterion

Detailed criterion for determining the connection failure.

Interferenceaverageparameter

Average time for obtaining the interference level. The default value is 20multiframe.

Interferencelevel threshold

The interference can be divided into six ranks according to the interferencesignal level. The level value for dividing each rank is called interferencelevel threshold.The BTS determines which rank the current interference level is in andreports this information to the BSC based on the radio resource indication.

Max. TA Maximum timing advance of the most distant area of a cell. This attributecan identify the actual coverage of a cell.

NY1 Maximum times of sending physical messages.

Operation state Whether the current site is available.

Overloadperiod

The BTS calculates the channel usage at a fixed interval to check whetherthe channel is overloaded. The interval is determined by the overloadingperiod. Unit: seconds

RACH BusyThreshold

Determining the level threshold of random access. Unit: dBm


LMT User Guide


Issue 07 (2011-01-30)

AttributeName

Description

RACH loadaveragetimeslots

Measuring the average loading timeslot number for random access channel.

Starting frameNo.

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 to65535.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 portFACCH/Full rate: timeout duration of T200 on the FACCH or full-ratechannel at the Um portFACCH/Half rate: timeout duration of T200 on the FACCH or half-ratechannel at the Um portSACCH with TCH SAPI0: timeout duration of T200 on the SACCH whenthe TCH at the Um port supports the SAPI0 serviceSACCH with SDCCH: timeslot duration of the T200 on the SACCH withSDCCH.SDCCH SAIP3: value of T200 when the SDCCH supports the SAPI3serviceSACCH with TCH SAPI3: timeout duration of T200 on the SACCH whenthe TCH at the Um port supports the SAPI3 service

VSWRthreshold

VSWR threshold of the RF voltage, including the VSWR threshold whenan antenna incurs a fault and the VSWR threshold when an antenna is notcorrectly 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& extendedoffset

Extended type and extended offset of the current cell.

Frame offset The default value of this attribute is 0. This indicates the cell is not offset.If the value is not 0, the handover mode must be changed from synchronousto asynchronous. If the value is 255, the BTS does not send this attribute.For BTS3001C and BTS2X BTSs, the value of this attribute is fixed to 255.The BTS3X, BTS3002C and double-transceiver BTSs can predict the frameoffset according to the value of frame offset parameter.

Interfere BandStat AlgorithmType

When the frequency point scanning function is enabled, interference bandstatistic algorithm I or interference band statistic algorithm II is used.



11-5

AttributeName

Description

Uplinkfrequencypoint scanningresult type

Uplink frequency point scanning result type.

TRX AttributesTable 11-3 lists the TRX attributes.

Table 11-3 TRX attributes

AttributeName

Description

Administrativestate

Administrative state of the current TRX.

ARFCN list List of channel numbers based on which the channel works. In non-FHmode, 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 thepower level of the current TRX.

Output powerthreshold

Maximum static output power.

Maximum RCpowerreduction

Maximum power reduction of each level.

Operation state Whether the TRX is available.

Available state Current status of the TRX.

8PSKmodulationpowerattenuationlevel

Power attenuation levels of the EDGE TRX. There are 50 levels, and theattenuation between levels is 0.2 dB.

RSL attribute Port number, timeslot number, and sub-timeslot number of the RSL link.

Terminalequipment ID

Information about the terminal equipment.

Channel AttributesTable 11-4 lists the channel attributes.


LMT User Guide


Issue 07 (2011-01-30)

Table 11-4 Channel attributes

AttributeName

Description

Administrative 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 theavailable channel numbers are listed in the ARFCN list.

Operationstate

Whether the channel is available.

Channelcombination

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.

Mobileallocationindex offset

FP offset when the TRXs are in FH in the same cell.

TSC Demodulation part for estimating the channel feature to correctly decode thevalid information. There are eight kinds of training sequence codes.

Availablestate

Current status of the channel.

11.1.2 Cell Forced Handover ModeThis section describes the cell forced handover function of the BSC. The target cell can beselected by the BSC according to the measurement report or be specified by the user.

The forced handover is classified into the following types:

l FreeHanding over an MS from one channel to another. The target cell can be specified throughthe LMT as required.

l Intra-cellHanding over an MS from one channel to another. The success rate of this type of handoveris high. Lock or shut down a faulty channel or the TRX that bears the faulty channel beforethe handover.

l Outgoing CellHanding over all MSs in a cell to another cell.

l Outgoing SiteHanding over all MSs in a cell to a cell that belongs to another base station.

l Outgoing BSCHanding over all MSs in a cell to a cell under control of another BSC.



11-7

l Outgoing SystemHanding over all MSs in a cell to a cell in different network system, for example, from aGSM cell to a UMTS cell.

l Specified CellHanding 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 BoardThis function is used to query the type, software version, and clock status of a board. You canquery the board running software version of several BTSs at a time.





2. In the BTS Maintenance tab page, choose BTS Maintenance > Query BoardRunning Software Version. The Query Board Running Software Version tab pageis displayed.

3. In the Query Board Running Software Version tab page, set the parameters asrequired, 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 Saveas... in the Query Result list area.

Figure 11-1 Results of querying the running software version of a board

4. Click Stop to stop the query.


LMT User Guide


Issue 07 (2011-01-30)

NOTE

You can also query the running software version of the board in the following way: Start the BTSdevice panel by referring to Starting the Device Panel. Then in the BTS device panel, right-clickthe main control board of the BTS and choose Query Software Version from the shortcut menu.

l Through an MML command1. Run the DSP BTSBRD command to query the running software version of a BTS

board.

----End

11.3 Downloading the BTS SoftwareThis section describes how to download the BTS software from the LMT PC to the FTP server.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.l The corresponding BTS software is available on the LMT PC.l The FTP server is running normally.

ContextYou can visit the website http://support.huawei.com to request the BTS software.

CAUTIONThe name of the file to be downloaded must be in English and the file must not be in use.Otherwise, the downloading fails.



2. In the BTS Maintenance tab page, select BTS Maintenance > Download BTSSoftware. 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 Downloadto start software downloading.

NOTE

FTP Server IP indicates the IP address of the FTP server. FTP User Name and FTPPassword are admin by default, and you can change them on the FTP server.

5. To query the BTS software on the OMU, click Query in the Files on OMU tab page.l Through MML commands



11-9

1. Run the DLD BTSSW command to download the BTS software.

----End

11.4 Loading the BTS SoftwareThis section describes how to load the BTS software on the OMU to the main processing boardof the BTS.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.l The corresponding BTS software is available on the LMT PC.

ContextThe LMT supports loading of multiple BTS software, which reduces the BTS upgrade time andincreases the upgrade efficiency.



2. In the BTS Maintenance tab page, select BTS Maintenance > Load BTSSoftware. The Load BTS Software dialog box is displayed.

3. In the Load BTS Software dialog box, specify the site type and software type, andthen 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.l Through MML commands

1. Run the LOD BTSSW command to load the BTS software.

----End

11.5 Activating BTS SoftwareThis describes how to activate the version software loaded onto the board.

Prerequisitel You have logged in to the LMT.l The communication between the BSC6900 and the BTS is normal.l The software version to be activated is different from the running version.l The BTS software has been loaded into the flash memory of the BTS board successfully.l The BTS software can be run only after being activated.


LMT User Guide


Issue 07 (2011-01-30)

l Auto Download Active Function Switch is set to OFF by running the MML command SETBTSAUTODLDACTINFO.

ContextNOTE

l The LMT supports activation of multiple BTS software simultaneously. You must activate the softwareof the main processing board first and then the software of other boards.

l The LMT does not support activation of the main processing board of a single BTS. When you activatethe software of the main processing board, the main processing boards of all the BTSs managed by theLMT are activated. When you activate the software of the non-main processing board, you can activatethe software of one or more boards as required.



2. In the BTS Maintenance tab page, select BTS Maintenance > Activate BTSSoftware. 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.l Through MML commands

1. Run the ACT BTSSW command to activate the BTS software.

----End

11.6 Querying BTS Running StatusThis section describes how to query the operating status of a BTS and cells under the same BSCto determine whether the BTS operates normally. You can query the operating status of multipleBTSs at one time.




2. In the BTS Maintenance tab page, BTS Maintenance > Query BTS RunningStatus. The 11.18 Reference for BTS Maintenance tab page is displayed.

3. In the Query BTS Running Status tab page, set the parameters as required, and thenclick Start to query the operating status of the BTS. The operation result is displayed,as shown in Figure 1.



11-11

NOTE

In the Device Navigation Tree, right-click the target BTS node, and choose Query BTSRunning Status from the shortcut menu.

Figure 11-2 Querying BTS Running Status


1. You can query the operating status of the BTSs and cells under the same BSC withthe 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

11.7 Querying BTS Board Matching ResultThis describes how to query whether the actual BTS board type matches with the configuredone. This operation is applicable to multiple BTSs simultaneously.



Procedure


Step 2 In the BTS Maintenance tab page, select BTS Maintenance > Query Board Match. TheQuery 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 SelectedBTS as required.

Step 4 Click Query. The query result is displayed in the Query Result area. The operation result isdisplayed, as shown in Figure 1.


LMT User Guide


Issue 07 (2011-01-30)

Figure 11-3 Querying BTS Board Matching Result

----End

11.8 Querying BTS AttributesThis describes how to query the BTS working status and attributes to verify the software andhardware configuration of a BTS.




2. In the BTS Maintenance tab page, select BTS Maintenance > Query BTSAttributes. The Query BTS Attributes tab page is displayed.

3. In the Query BTS Attributes tab page, set the parameters as required, and then clickQuery. The operation result is displayed, as shown in Figure 1.

NOTE

In the Device Navigation Tree, right-click the BTS node, and choose Query BTSAttributes from the shortcut menu.



11-13

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 LevelsThis describes how to reset a BTS, cell, or TRX to update the configuration data when the BTS,cell, or TRX is faulty.


Context

CAUTIONl Resetting a BTS will initiate all the sites, reload the data, and disrupt the ongoing services

under the BTS. Thus, perform this operation with caution.l Resetting a cell will initiate all the cell, reload the data, and disrupt the ongoing services in

the cell. Thus, perform this operation with caution.l Resetting a TRX will initiate all the cell and disrupt the ongoing services carried by the TRX.

Thus, perform this operation with caution.

l Resetting the BTS by Levels– Resetting the BTS is classified into level-3 resetting or level-4 resetting.


LMT User Guide


Issue 07 (2011-01-30)

– The working principle of level-3 resetting and level-4 resetting at the BTS side is thesame. That is, in both operations, the BTS obtains data from the BSC6900 for theresetting.

– The working principles of the level-3 and level-4 resetting at the BSC6900 side aredifferent in terms of whether to reset the BTS with the updated configuration data. Thatis, 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 theXPU board.

l 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 BSC6900 and thenresets all boards in the cell.

– The working principles of the level-3 and level-4 resetting at the BSC6900 side aredifferent in terms of whether to reset the cell with the updated configuration data. Thatis, if the cell is under level-3 resetting, the cell is reset directly with the currentconfiguration data. If the cell is under level-4 resetting, the mutual-aid status isinitialized and then the cell is reset with the updated configuration data.

l Resetting the TRXResetting the TRX does not involve the operation of the BSC6900. The BTS resets theTRX boards directly.



2. In the BTS Maintenance tab page, select BTS Maintenance > Reset BTS byLevels. The Reset BTS by Levels dialog box is displayed. The operation result isdisplayed, as shown in Figure 1.



11-15

Figure 11-5 Resetting the BTS by Levels

3. In the displayed Reset BTS by Levels dialog box, set the parameters as required, andthen click Reset.

NOTE

In the Device Navigation Tree, right-click the BTS node, and choose Reset BTS by Levelsfrom 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 MessageThis section describes how to browse the initialization process of all the BTSs to see whetherthe BTS is reset. If the initialization fails, this message shows the failure cause that helps tolocate the fault.




LMT User Guide


Issue 07 (2011-01-30)

Contextl The initialization process message is reported by the BTS automatically.l There are numerous process messages. The messages are displayed in strings not in

percentage.l An LMT can display the process messages of all BTSs of the current BSC.


displayed.

Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Browse BTS InitializationProgress. The Browse BTS Initialization Progress dialog box is displayed.

Step 3 To browse the initialization process messages that meet the filtering conditions, set Site andCell. 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 InitializationProgress from the shortcut menu.

Figure 11-6 Browsing BTS Initialization Process Message

----End

11.11 Modifying Administrative StateThis section describes how to change the administrative state of the cell, TRX, and channel.


ContextThe administrative state can be "Lock", "Unlock", and "Shutdown". An object can be blockedor shutdown only when the upper-level object is unlocked. If an object is locked or shut down,



11-17

all the lower-level objects are locked or shut down. For example, locking a cell locks all theTRXs and channels under the cell.l Lock: If you lock cell, TRX, or channel, it is unavailable for services. The calls under the

locked cell, TRX, or cell are forcibly handed over to another cell, TRX, or channel withoutdisruption. If the forced handover fails, however, call drops may occur. In addition, newcalls cannot access the locked cell, TRX, or channel.

l Unblock: If you unblock a cell, TRX, or channel, it becomes available for services.l Shutdown: If you shut down a cell, TRX, or channel,the ongoing calls under the locked

cell, TRX, or cell are not affected. New calls, however, cannot access the locked cell, TRX,or channel.

In the following cases, you can lock or shut down an object.l In the case that dynamic data configuration that may affect the services (for example,

modifying the channel type) is required, you need to lock or shut down the target objectbefore dynamic data configuration.

l In case the speech quality of a cell, TRX, or channel is not satisfactory and the relevanthardware device needs to be replaced, you need to lock or shut down the target object beforethe replacing the hardware device.



2. In the BTS Maintenance tab page, select BTS Maintenance > ModifyingAdministrative 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. The operation result is displayed, as shown in Figure 1.

Figure 11-7 Modifying Administrative State


LMT User Guide


Issue 07 (2011-01-30)


1. You can maintain the administrative state of a cell, TRX, or channel as follows:– Run the SET GCELLADMSTAT command to modify the administrative state

of a cell.– Run the SET GTRXADMSTAT command to modify the administrative state of

a TRX.– Run the SET GTRXCHANADMSTATcommand to modify the administrative

state of a channel.

----End

11.12 Forced HandoverThis section describes how to hand over the services in the cell, on the TRX, or on a channelforcibly over to another cell, TRX, or channel. When you maintain the BTS device, you needto perform this operation to hand over the services to another normal working area so as to avoidcall drops.


ContextNOTE

In the Device Navigation Tree, right-click the cell or TRX node, and choose Forced Handover from theshortcut menu.



2. In the BTS Maintenance tab page, choose BTS Maintenance > ForcedHandover. The Forced Handover dialog box is displayed. The operation result isdisplayed, as shown in Figure 1.



11-19

Figure 11-8 Forced Handover

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.

l Through MML commands1. Run the SET FHO command to configure the handover parameters.

----End

11.13 Monitoring Channel StatusThis describes how to monitor the occupation of all the channels and sub-channels.


ContextNOTE

In the Device Navigation Tree, right-click the site, cell or TRX node, and choose Monitor ChannelStatus from the shortcut menu.


LMT User Guide


Issue 07 (2011-01-30)



2. In the BTS Maintenance tab page, choose BTS Maintenance > Monitor ChannelStatus. 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,as shown in Figure 1.

NOTE

l Each dot in a column represents a sub-channel of the corresponding channel. The SDCCHchannel has eight sub-channels, the full-rate TCH has only one sub-channel, and the half-rate TCH has two sub-channels.

l The sub-channel status is indicated with different colors.

l Green indicates that the channel is in normal state. If you move the cursor to thecorresponding indicator, you can read the current channel type, applied bandwidth, andavailable bandwidth from the pop-up information, wherein the applied bandwidth andthe available bandwidth are equal and both bandwidths are greater than or equal to 16kbit/s. The number of the uplink or downlink TBF blocks are proportional to the MSsthat can be multiplexed on the current channel.

l Red indicates that the channel is abnormal. If you move the cursor to the correspondingindicator, you can read the current channel type, applied bandwidth, and availablebandwidth from the pop-up information, wherein the applied bandwidth is not equalto 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 correspondingindicator, you can read the current channel type and the channel status, wherein thechannel status is Locked.

l If a TRX number is marked with *, the TRX is in TRX mutual aid state.

Figure 11-9 Monitoring Channel Status


1. Run the DSP CHNSTAT command to monitor the channel status.

----End



11-21

11.14 Monitoring Interference Band of ChannelThis describes how to detect the interference band rank on the idle channel to monitor theinterference conditions on the channel.




2. In the BTS Maintenance tab page, choose BTS Maintenance > Monitor ChannelInterference Band. The Monitor Channel Interference Band tab page is displayed.

3. In the displayed Monitor Channel Interference Band tab page, set the parametersas required, and then click Start to monitor the interference band of the channel. Theoperation result is displayed, as shown in Figure 1.

NOTE

In the Device Navigation Tree, right-click the BTS node, and choose Monitor ChannelInterference Band from the shortcut menu.

Figure 11-10 Monitoring Interference Band of Channel


1. Run the DSP CHNJAM command to monitor the interference band of the channel.

----End

11.15 Maintaining SiteThis section describes how to maintain the sites.


LMT User Guide


Issue 07 (2011-01-30)

11.15.1 Browsing the BTS LogThis describes how to browse the BTS log.

11.15.2 Testing Transmission PerformanceThis section describes how to test the E1 self-loopback function and the IASU self-loopbackfunction to locate the transmission fault in a BTS. The E1 self-loopback function is used to testthe error codes on a timeslot of a transmission link other than the OML. The E1 self-loopbacktest affects the ongoing services on the target timeslot, whereas the IASU self-loopback testaffects services on all timeslots carried by the target E1 port.

11.15.3 Querying BTS Transmission StateThis section describes how to query transmission link state of a BTS that is activated.

11.15.1 Browsing the BTS LogThis describes how to browse the BTS log.


Procedure


Step 2 In the BTS Maintenance tab page, choose BTS Maintenance > Maintain Site > Browse BTSLog. 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 tobrowse 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 theshortcut menu.

Figure 11-11 Browsing the BTS Log



11-23

----End

11.15.2 Testing Transmission PerformanceThis section describes how to test the E1 self-loopback function and the IASU self-loopbackfunction to locate the transmission fault in a BTS. The E1 self-loopback function is used to testthe error codes on a timeslot of a transmission link other than the OML. The E1 self-loopbacktest affects the ongoing services on the target timeslot, whereas the IASU self-loopback testaffects services on all timeslots carried by the target E1 port.



Context

Only the BTS3002C, BTS3006C, and BTS3002E support the IASU self-loopback test.

NOTE

In the Device Navigation Tree, right-click the target BTS node, and choose Test TransmissionPerformance from the shortcut menu.



2. In the BTS Maintenance tab page, select BTS Maintenance > Maintain Site > TestTransmission Performance. The Test Transmission Performance dialog box isdisplayed. The operation result is displayed, as shown in Figure 1.

Figure 11-12 Testing Transmission Performance


LMT User Guide


Issue 07 (2011-01-30)

NOTE

At the base_level ofDevice Navigation Tree, select the right fast menuTest TransmissionPerformance. The Test Transmission Performance dialog box is displayed.

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. In theBTS3012 and BTS3012AE, each TMU has eight E1 ports numbered from 0 to 7. In theBTS3012 and BTS3012AE, each TMU has four E1 ports numbered from 0 to 3. LoopbackMode can be E1 Loopback or Timeslot Loopback. If you choose E1 Loopback, all thetimeslots on the specified E1 port are tested. The maximum test duration can be 60 minutes. Ifyou choose Timeslot Loopback, you can specify the timeslot number. Only one timeslot canbe tested each time. The maximum test duration can be 1,440 minutes.For the IASU self-loopback test, set Port to the port number of the TMU board. Each boardsupports self-loopback tests of four E1 ports. The test duration can be 1 to 60 minutes.

l Through MML commands1. 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 STR TRANSPERFTST command to stop the transmission performance

test.

----End

11.15.3 Querying BTS Transmission StateThis section describes how to query transmission link state of a BTS that is activated.


ContextNOTE

l In the Device Navigation Tree, right-click the target BTS node, and choose Query BTS TransmissionState from the shortcut menu.

l BTS transmission state cannot be queried for the BTS3X.



2. In the BTS Maintenance tab page, select BTS Maintenance > Maintain Site >Query BTS Transmission State. The Query BTS Transmission State dialog boxis displayed.

3. In the Query BTS Transmission State tab page, set the parameters as required andthen click Query to query the transmission state of the BTS. The operation result isdisplayed, as shown in Figure 1.



11-25

Figure 11-13 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 BTSTMU port.

----End

11.16 Maintaining the CellThis section describes how to maintain the cells.

11.16.1 Querying Frequency Scan ParametersThis section describes how to query the parameters related to the frequency scan, including themaximum and average values of the main receiver level and the diverse receiver levels. You canperform this task to evaluate the interference condition on the uplink frequency.

11.16.2 Configuring Frequency ScanThis describes how to configure the start time of scanning multiple frequencies in a cell and thescan duration.

11.16.1 Querying Frequency Scan ParametersThis section describes how to query the parameters related to the frequency scan, including themaximum and average values of the main receiver level and the diverse receiver levels. You canperform this task to evaluate the interference condition on the uplink frequency.


l The frequency scan has been started (see 11.16.2 Configuring Frequency Scan).

Context

Each TRX has two receivers, wherein one is the main receiver and the other is the diversereceiver. The main receiver level indicates the voltage level of the uplink signals carried on themain receiver of the TRX. The diverse receiver level indicates the voltage level of the uplinksignals carried on the diverse receiver of the TRX.


LMT User Guide


Issue 07 (2011-01-30)



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 toread the corresponding scan result of the frequencies. The operation result is displayed,as shown in Figure 1.

NOTE

In the Device Navigation Tree, right-click the target cell node, and choose Query FrequencyScan from the shortcut menu.

Figure 11-14 Querying Frequency Scan Parameters


1. Run the LST GCELLFREQSCAN command to query the parameters related tofrequency scan.

----End

11.16.2 Configuring Frequency ScanThis describes how to configure the start time of scanning multiple frequencies in a cell and thescan duration.




2. In the BTS Maintenance tab page, select BTS Maintenance > Maintain Cell >Configure Frequency Scan. The Configure Frequency Scan dialog box isdisplayed. The operation result is displayed, as shown in Figure 1.



11-27

Figure 11-15 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.

NOTE

In the Device Navigation Tree, right-click the target cell node, and choose ConfigureFrequency Scan from the shortcut menu.

l Through MML commands1. Run the SET GCELLFREQSCAN command to configure the parameters related to

frequency scan.

----End

11.17 Maintaining TRXsThis section describes how to maintain the TRXs.

11.17.1 Querying the TRX Power ModeThis section describes how to query the theoretical maximum power mode supported by a TRXand the current power mode of the TRX.

11.17.2 Querying Automatic Power Correction TypeThis 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 tothe power template, thus ensuring the stable output power on frequencies in the same frequencyband. This function is enabled by default for all boards.


LMT User Guide


Issue 07 (2011-01-30)

11.17.3 Testing TRX LoopbackThis describes how to test the TRX loopback. Through this task, you can learn about the TRXperformance and the channel transmission conditions and locate the speech channel problems.

11.17.4 Testing Channel LoopbackThis describes how to test the transmission capability of the traffic channel and the speechchannel. This task involves TRX RF self-loopback test and BIU self-loopback test on the trafficchannel, and BTS speech loopback test and TRX speech loopback test on the speech channel.

11.17.5 Testing Idle TimeslotsThis describes how to test the idle timeslots in the network to test the maximum interferencecapacity of the network.

11.17.6 Resetting the TRXThis section describes how to reset a faulty TRX in a specified BTS.

11.17.7 Querying TRX TimeslotThis section describes how to query timeslot information of channels corresponding to a TRX.

11.17.1 Querying the TRX Power ModeThis section describes how to query the theoretical maximum power mode supported by a TRXand the current power mode of the TRX.




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 thenclick Query to query the power mode. The operation result is displayed, as shown inFigure 1.

NOTE

In the Device Navigation Tree, right-click the target BTS node, and choose Query TRXPower Mode from the shortcut menu.



11-29

Figure 11-16 Querying the TRX Power Mode


1. Run the DSP TRXPWR command to query the power mode of a TRX.

----End

11.17.2 Querying Automatic Power Correction TypeThis 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 tothe power template, thus ensuring the stable output power on frequencies in the same frequencyband. This function is enabled by default for all boards.





LMT User Guide


Issue 07 (2011-01-30)


2. In the BTS Maintenance tab page, select BTS Maintenance > Maintain TRX >Query Automatic Power Correction Type. The Query Automatic PowerCorrection Type dialog box is displayed.

3. In the Query Automatic Power Correction Type dialog box, set the parameter asrequired, and then click Query to query the automatic power correction type. Theoperation result is displayed, as shown in Figure 1.

NOTE

In the Device Navigation Tree, right-click the target BTS node, and choose Query AutomaticPower Correction Type from the shortcut menu.

Figure 11-17 Querying Automatic Power Correction Type


1. Run the DSP BTSAUPWCRT command to query the automatic power correctiontype of a TRX.

----End



11-31

11.17.3 Testing TRX LoopbackThis describes how to test the TRX loopback. Through this task, you can learn about the TRXperformance and the channel transmission conditions and locate the speech channel problems.



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 theBTS internal data bus DBUS corresponding to the TRX signaling channel. The TRX sendsthe data on the signaling channel to the corresponding signaling timeslot on the BTS internalDBUS. Then, the data is looped within the TMU so that the TRX receives the signalingdata previously sent by itself. After the TRX receives the data, it compares the data withthe sent data and reports the BER to the LMT. Thus, you can learn about the signaling linkquality of the BTS internal DBUS.

l The TRX self-loopback test is performed to check the TRX conditions. It is performedautomatically by the TRX. You need not set Duration(Second) in this case.



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 clickStart to test TRX loopback.

NOTE

In the Device Navigation Tree, right-click the target BTS node, and choose Test TRXLoopback from the shortcut menu.


1. You can run the following commands to start and stop the TRX loopback testrespectively.

– Run the STR BTSTST command to start a TRX loopback test.

– Run the STP BTSTST command to stop the TRX loopback test.

----End

11.17.4 Testing Channel LoopbackThis describes how to test the transmission capability of the traffic channel and the speechchannel. This task involves TRX RF self-loopback test and BIU self-loopback test on the trafficchannel, and BTS speech loopback test and TRX speech loopback test on the speech channel.


LMT User Guide


Issue 07 (2011-01-30)


ContextNOTE

l In the case of TRX RF self-loopback test of a channel numbered n, the channel (n+5)mod8 of all TRXsin the cell is affected when no frequency hopping occurs. When the RF frequency hopping occurs, thesame channel n of other TRXs in the same frequency hopping group is affected. This test is notapplicable to the baseband frequency hopping.

l The BTS3001C and the BTS3002C do not support the loopback test on the speech channel.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 LoopTest, 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 RFself-loopback starts from the DSP, passes the BBU, loops back from the RRU, and thenpasses the BBU again to come back to the DSP. The DSP then compares the data with theoriginal data to learn the RX and TX channel quality of the BTS.

l BIU Loop TestThis test is performed to check the timeslot transmission conditions on the BTS internaldata bus DBUS corresponding to the TRX traffic channel. The TRX sends the data on thetraffic channel to the corresponding traffic timeslot on the BTS internal DBUS. Then, thedata 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 theBER to the LMT. Thus, you can learn about the traffic link quality of the BTS internalDBUS.

l BTS Voice Loop TestThis test is performed to evaluate the connection of the TRX speech channel between theUm interface and the DBUS within the BTS. The TMU loops back the DBUS timeslot ofthe speech channel to be tested. If the TX end receives its own voice signal, you can inferthat the channel connection is normal; otherwise, the connection is disrupted.

l TRX Voice Loop TestThis test is performed to evaluate the connection of the TRX speech channel between theUm interface and the DSP. The DSP encodes and then sends the data. If the TX end receivesits own voice signal, you can infer that the channel connection is normal; otherwise, theconnection is disrupted.



2. In the BTS Maintenance tab page, choose BTS Maintenance > Maintain TRX >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 clickStart to test channel loopback.



11-33

NOTE

In the Device Navigation Tree, right-click the target TRX node, and choose Test ChannelLoopback from the shortcut menu.

l Through MML commands1. 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.17.5 Testing Idle TimeslotsThis describes how to test the idle timeslots in the network to test the maximum interferencecapacity of the network.


ContextIn the network optimization stage, you need to perform this task to test the maximum interferencecapacity of the network. By this test, dummy bursts are sent on all the idle timeslots in a specificarea. The test duration is predefined to 1 to 24 hours before the test and stopped by the softwareautomatically. You can also stop the test manually during the process.



2. In the BTS Maintenance tab page, select BTS Maintenance > Maintain TRX >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 Startto test idle timeslots. The operation result is displayed, as shown in Figure 1.


LMT User Guide


Issue 07 (2011-01-30)

Figure 11-18 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.17.6 Resetting the TRXThis section describes how to reset a faulty TRX in a specified BTS.



Context

CAUTIONl Resetting the board disrupts the ongoing services. Thus, perform this task with caution.

l If one TRX of the DTRU is reset, the operation of the other TRX is also affected.



11-35



2. In the BTS Maintenance tab page, choose BTS Maintenance > Maintain TRX >Reset TRX. The Reset TRX dialog box is displayed. The operation result isdisplayed, as shown in Figure 1.

Figure 11-19 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 fromthe shortcut menu.

l Through MML commands1. Run the RST TRX command to reset a TRX of a BTS.

----End

11.17.7 Querying TRX TimeslotThis section describes how to query timeslot information of channels corresponding to a TRX.




2. In the BTS Maintenance tab page, choose BTS Maintenance > Maintain TRX >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 DeviceNavigation Tree and then choosing Query TRX Timeslot from the shortcut menu.


LMT User Guide


Issue 07 (2011-01-30)

3. Set parameters in the Query TRX Timeslot dialog box and then click Query to querytimeslot information of channels corresponding to the TRX. Figure 11-20 shows thequery result.

Figure 11-20 Results of querying TRX timeslots


1. Run the LST GTRXCHAN command to query timeslot information of channelscorresponding to a TRX.

----End

11.18 Reference for BTS MaintenanceThis section describes the parameters used for BTS maintenance.

Maintenance Item

Parameter Description

QueryingBTSRUNNINGStatus

Normal OML Indicates whether the OML link between the currentsite 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 betweenthe BCCH TRX and other TRXs when the BCCH TRXis faulty.

BT Hop MutualAid

Indicates that whether mutual aid is enabled when theTRX participating in the baseband frequency hoppingis faulty in a cell.

LocalManagementRights

Indicates whether the BTS maintenance is performedthrough the E1 port or serial port.

FrequencyScanning

Indicates whether the uplink frequency scanning isperformed.



11-37

Maintenance Item

Parameter Description

TMU NotActivated Cause

Indicates the cause why the automatic TMU activationfails when the running version of the BTS TMUspecified by the BSC is inconsistent with theconfigured one.


LMT User Guide


Issue 07 (2011-01-30)

12 FAQ

About This Chapter

This chapter describes the frequently asked questions (FAQs) and the corresponding solutions.

12.1 Browser Cache expires.After the LMT software is upgraded or rolled back, a warning message is displayed as follows:"Warning: the temporary files have expired, you must clear the browser's temporary files andcookies, then refresh to re-open the browser." In this case, you need to clear the cache, cookies,and Java Applet.

12.2 The LMT gives slow responses to user operations in the Firefox browser.When the LMT runs in the Firefox browser, it gives slow responses. For example, it takes about30 seconds to maximize the window of a trace task in the Trace tab page. In this case, checkwhether the add-on extension Live Margins is installed.

12.3 The color of the LMT is not correctly displayed.When the LMT is started in the IE browser, the colors are not correctly displayed. For example,the colors indicating the status of the boards and alarms are not displayed, or the backgroundcolor of the LMT is not differentiated from that of the IE browser. In this case, check the colorsettings of the browser.

12.4 The verify code cannot be displayed on the LMT login page.The verify code cannot be displayed when you try to log in to the LMT through the IE browserin the Windows Server 2008 or Windows Vista system. In this case, check the settings relatedto the protection mode of the browser.

12.5 Installing OS PatchesIn a Microsoft Windows operating system (OS), you need to install patch KB944338 orKB960714 if the OS and IE are in a certain version.

12.6 Clicking the menu bar on the LMT has no response.When the LMT webpage is browsed through IE, there is no response or a webpage script erroroccurs when you click the menu bar. To be specific, when you click the menu bar or buttons orright-click the webpage, there is no response or a dialog box is displayed, indicating a scripterror, for example, you are rejected or have no right to access the webpage. In this case, checkthe proxy settings in IE.

12.7 Changing the Computer Time During the LMT Use Prohibited

BSC6900 GSMLMT User Guide 12 FAQ


12-1

Changing the computer time during the LMT use is prohibited. Changing the computer timecauses some functions of the LMT to stop functioning normally. For example, the OMU timefails to refresh normally; tracing data and monitoring data fail to refresh normally; progressmanagement fails to refresh normally.

12.8 Corrupt Characters Occurring When Opening the csv File in UTF-8 CodingIf a csv file in UTF-8 coding is saved on the LMT with non-English characters in it and the csvfile is opened in the Excel format by using the regular method, all the non-English charactersare displayed as corrupt characters. In this case, open the csv file by using the import method inExcel.

12.9 Methods for Setting the Explorer Under Citrix Farm NetworkingUnder Citrix farm networking, you log in to the LMT on a Citrix client. When you use the M2000as the proxy server for the login, the LMT may be suspended or the verification code may beunavailable. When these problems occur, you can check the explorer setting, including thesetting of the explorer proxy server and HTTP 1.1 setting. If the setting is wrong, you can set itanew.

12.10 Unable to Log In To LMT Because IE Default Security Level Is Too HighIn a Windows Server operating system (including Windows Server 2003 and Windows Server2008), the IE blocks Web programs of sites that are out of the trusted site list to improve systemsecurity. As a result, you may fail to log in to the LMT.

12.11 Unable to Log In To LMT and Class can't Stand Automation Operation is DisplayedWhen the LMT is started in the IE browser, Class can't Stand Automation Operation isdisplayed.

12.12 LMT Failing to Load the Progress Interface After a Successful LoginAfter logging in to the LMT successfully, you may find that the LMT fail to load the progressinterface. This section describes the solution to the problem.

12.13 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verificationof JREThis section describes how to solve the problem that the LMT does not respond or respondsincorrectly when users perform a function on the LMT.

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

12.1 Browser Cache expires.After the LMT software is upgraded or rolled back, a warning message is displayed as follows:"Warning: the temporary files have expired, you must clear the browser's temporary files andcookies, then refresh to re-open the browser." In this case, you need to clear the cache, cookies,and Java Applet.

Procedurel To clear the cache and cookies in the Firefox browser, do as follows:

1. Choose Tools > Clear Private Data in the Firefox browser.2. In the displayed Clear Private Data dialog box, select Cache, Cookies, and Offline

Website Data, and then click Clear Private Data Now.

NOTE

In this section, FireFox V3.0 is taken as an example. The previous steps are only for reference, andmay be changed based on the actual version of FireFox.

l To clear the cache and cookies in the IE 6.0 browser, do as follows:1. Choose Tool > Internet Options on the tool bar of the IE browser. The Internet

Options dialog box is displayed.2. In the General tab page, click Delete Cookies. A dialog box is displayed, prompting

you to confirm the operation. Click OK.3. In the General tab page, click Delete Files. A dialog box is displayed, prompting you

to confirm the operation. Select Delete all offline content and click OK.4. In the Internet Options dialog box, click OK to exit the dialog box.


Options dialog box is displayed.2. On the General tab page, click Delete. The Delete Browsing History dialog box is

displayed.3. To delete the files, click Delete Files, and then click OK in the confirmation dialog

box. To delete the cookies, click Delete Cookies, and then click OK in theconfirmation dialog box.

4. In the Delete Browsing History dialog box, click OK and exit the InternetOptions dialog box.


Options dialog box is displayed.2. On the General tab page, click Delete. The Delete Browsing History dialog box is

displayed.3. In the Delete Browsing History dialog box, choose Temporary Internet Files and

Cookies. Click Delete.4. In the Internet Options dialog box, click OK to exit the dialog box.

l To clear Java Applet, do as follows:1. Choose Start > Control Panel.



12-3

2. Double-click the Java icon. The Java Control Panel dialog box is displayed.

3. In the General tab page, click Settings. The Temporary Files Settings dialog box isdisplayed.

4. Click Delete Files. In the displayed Delete Temporary Files dialog box, selectApplications and Applets and Trace and Log Files. Click OK.

5. In the Java Control Panel dialog box, click OK to exit the panel.

NOTE

Restart the browser to validate the modifications.

----End

12.2 The LMT gives slow responses to user operations in theFirefox browser.

When the LMT runs in the Firefox browser, it gives slow responses. For example, it takes about30 seconds to maximize the window of a trace task in the Trace tab page. In this case, checkwhether 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 "RestartFirefox to complete your changes" is prompted.

Step 3 Click Restart Firefox to validate the changes.

----End

12.3 The color of the LMT is not correctly displayed.When the LMT is started in the IE browser, the colors are not correctly displayed. For example,the colors indicating the status of the boards and alarms are not displayed, or the backgroundcolor of the LMT is not differentiated from that of the IE browser. In this case, check the colorsettings of the browser.

Procedure

Step 1 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialogbox 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 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

12.4 The verify code cannot be displayed on the LMT loginpage.

The verify code cannot be displayed when you try to log in to the LMT through the IE browserin the Windows Server 2008 or Windows Vista system. In this case, check the settings relatedto the protection mode of the browser.

ContextIf the protected mode is enabled for the IE browser in the Windows Server 2008 or WindowsVista system, there are many security restrictions. For example, JavaScript and Applet cannotbe run. Therefore, you need to turn off the protected mode. Otherwise, the LMT web page cannotbe displayed.

Procedure

Step 1 Enter the external virtual IP address of the OMU in the address bar on the IE. Press Enter onthe keyboard, or click Go next to the address bar to display the login window of the BSC6900.

Step 2 Check whether "Internet | Protected Mode: Off" is displayed on the bottom right of the window.l If yes, the task is complete.l If no, go to Step 3.

Step 3 Choose Tool > Internet Options on the tool bar of the IE browser. The Internet Options dialogbox is displayed.

Step 4 On the Security tab page, select Trusted sites in the Select a Web content zone to specify itssecurity settings area.

Step 5 Deselect Enable Protected Mode. Click Sites. The Trusted sites dialog box is displayed.

Step 6 Type the external virtual IP address of the OMU in the Add this Web site to the zone text box,and then click Add. Thus, the external virtual IP address of the OMU is added to the Trustedsites list.

Step 7 In the Internet Options dialog box, click OK to exit the dialog box.

NOTE


----End

12.5 Installing OS PatchesIn a Microsoft Windows operating system (OS), you need to install patch KB944338 orKB960714 if the OS and IE are in a certain version.

Contextl Patch KB960714 solves the problem of Java console output error. Thus, the Java application

can be loaded successfully on the LMT.



12-5

l Patch KB944338 improves the performance of the LMT by increasing the speed of visitinga web page. Thus, the LMT running rate can be increased.

Procedure

Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or RemovePrograms icon.

Step 2 In the displayed Add or Remove Programs window, select Show updates. Check whetherpatches KB944338 and KB960714 are present in the list of Currently installed programs.

l If the patches are present, the task is complete.

l If the patches are not present, go to Step 3.

Step 3 Determine whether a Windows patch needs to be installed according to the OS version and IEversion.

l Patch KB960714 needs to be installed when the OS version and IE version are combined inthe following ways:

OS Version IE Version

Windows 2000 SP4 IE5/IE6 SP1

Windows XP SP2/SP3 IE6/IE7

Windows Server 2003 SP1/SP2 IE6/IE7

Windows Vista IE7

l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4, WindowsXP SP1/SP2, or Windows Server 2003 SP1/SP2.

NOTE

l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.

l Download a suitable patch according to the OS version and IE version.

----End

12.6 Clicking the menu bar on the LMT has no response.When the LMT webpage is browsed through IE, there is no response or a webpage script erroroccurs when you click the menu bar. To be specific, when you click the menu bar or buttons orright-click the webpage, there is no response or a dialog box is displayed, indicating a scripterror, for example, you are rejected or have no right to access the webpage. In this case, checkthe proxy settings in IE.

Context

Do not modify the settings of the IE when you have logged in to the LMT. Set the proxy serverwhen necessary before you log in to the LMT.

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Procedure

Step 1 Choose Tools > Internet Options on the tool bar of IE. The Internet Options dialog box isdisplayed.

Step 2 On the Connections tab page, click LAN Settings. The LAN Settings dialog box is displayed.

Step 3 In the Proxy server area, select Use a proxy server for your LAN (These settings will notapply to dial-up or VPN connections). Type the IP address and port number of the proxy serverin the corresponding text boxes, and then click Advanced. The Proxy settings dialog box isdisplayed.

Step 4 In the Exceptions area, type the external virtual IP address of the OMU in the text box, and thenclick OK. Close the Internet Options dialog box.

----End

12.7 Changing the Computer Time During the LMT UseProhibited

Changing the computer time during the LMT use is prohibited. Changing the computer timecauses some functions of the LMT to stop functioning normally. For example, the OMU timefails to refresh normally; tracing data and monitoring data fail to refresh normally; progressmanagement fails to refresh normally.

12.8 Corrupt Characters Occurring When Opening the csvFile 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 csvfile is opened in the Excel format by using the regular method, all the non-English charactersare displayed as corrupt characters. In this case, open the csv file by using the import method inExcel.

Procedure

Step 1 On the menu bar of Excel, choose Data > Import External Data > Import Data. Then theSelect Data Source dialog box is displayed. Figure 12-1 shows the dialog box.



12-7

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 ImportWizard - Step 1 of 3 dialog box is displayed. Figure 12-2 shows the dialog box. Select UTF-8in File origin.

Figure 12-2 Text import wizard—step 1

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Step 3 Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed. Figure 12-3shows 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



12-9

12.9 Methods for Setting the Explorer Under Citrix FarmNetworking

Under Citrix farm networking, you log in to the LMT on a Citrix client. When you use the M2000as the proxy server for the login, the LMT may be suspended or the verification code may beunavailable. When these problems occur, you can check the explorer setting, including thesetting of the explorer proxy server and HTTP 1.1 setting. If the setting is wrong, you can set itanew.

ContextYou can set the explorer under Citrix farm networking in the following ways:l Script setting: An automatic setting script is placed on the domain control server. After a

Citrix user logs in to the server, the script automatically sets the explorer.l Manual setting: The explorer is set manually.

The Citrix server works in the farm mode. In the farm mode, the primary Citrix server andsecondary Citrix servers work in cooperation to achieve load balancing. When a Citrix user logsin to the Citrix server on a Citrix client, the server in use may vary. The proxy server of theexplorer thus may need to be set repeatedly. We therefore recommend setting the explorer usingthe script. In this way, each time the user visits the server, automatic setting of the explorer isperformed and repeated settings are avoided.

Procedurel Script Setting

1. Prepare a script.Type the following script content in a notepad and save it as IE-unset.bat.@echo offsetlocal ENABLEDELAYEDEXPANSIONset uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings"reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nulreg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nulsetlocal ENABLEDELAYEDEXPANSIONset uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings"reg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nulreg add %uu% /v ProxyOverride /t REG_SZ /d "<local>" /f >nulreg add %uu% /v ProxyEnable /t REG_DWORD /d "1" /f >nul

NOTEThe IE-unset.bat script file implements automatic setting of the explorer for the domain user.The domain user can change 10.121.49.213:80 inreg add %uu% /v ProxyServer /t REG_SZ /d "10.121.49.213:80" /f >nulin 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 ofadministrator and place the IE-unset.bat file in the C:\WINDOWS\SYSVOL\sysvol\citrixtest.com\scripts path on the server.

NOTEThe default installation path on the domain control server is C:\WINDOWS\SYSVOL\sysvol\citrixtest.com\scripts. The path changes if you install the file elsewhere. Here,citrixtest.com is taken as an example of the test domain name. The actual domain name dependson actual conditions.

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

3. For details about establishing a domain user, refer to the Citrix Access Solution UserGuide.

4. Set user script for each domain user.Assume that there is a user named hong01 in the hongtest unit of the citrixtest.comdomain.

(1) Start Active Directory Users and Computers and double-click hongtest in theleft-side window. In the right-side window, all users in the hongtest unit aredisplayed. Figure 12-5 shows the window.

Figure 12-5 Active Directory Users and Computers

(2) In the right-side window, right-click hong01. Choose Properties from the

shortcut menu. Accordingly, the hong01 Properties dialog box is displayed.Figure 12-6 shows the dialog box.



12-11

Figure 12-6 hong01 Properties 1

(3) In the hong01 Properties dialog box, click the Profile tag. Type IE-unset.bat

in Logon script, click Apply, and then click OK. Figure 12-7 shows thewindow.

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Figure 12-7 hong01 Properties 2

l Manual Setting

1. Check the proxy server setting of the explorer.

(1) Choose Tools > Internet Options on the tool bar of the IE. Accordingly, theInternet Options dialog box is displayed.

(2) On the Connections tab, click LAN Settings. Accordingly, the Local AreaNetwork (LAN) Settings dialog box is displayed.

(3) In the Proxy server area, select Use a proxy server for your LAN (Thesesettings will not apply to dial-up or VPN connections). , Set Address to theIP address of the M2000 and set Port to 80.



12-13

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

(1) Choose Tools > Internet Options on the tool bar of the IE. Accordingly, theInternet Options dialog box is displayed.

(2) On the Advanced tab, select Use HTTP 1.1 through proxy connections underHTTP 1.1 settings, click Apply, and then click OK. Figure 12-8 shows thewindow.

Figure 12-8 HTTP 1.1 settings

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

----End

12.10 Unable to Log In To LMT Because IE Default SecurityLevel Is Too High

In a Windows Server operating system (including Windows Server 2003 and Windows Server2008), the IE blocks Web programs of sites that are out of the trusted site list to improve systemsecurity. As a result, you may fail to log in to the LMT.

Contextl When you try to log in to the LMT by entering the IP address in the IE address bar, the

following web page will be displayed for your wanted page is out of the trusted site list.Thus, you may fail to log in to the LMT.

l According to the acceptable IE security level, there are the following two solutions:– When lowering the IE security level on the Windows server is unacceptable, you can

add the LMT site to the trusted sites of the IE by using a configuration startup script.The system automatically loads the script and configures the IE after a Citrix user logsin.

– When lowering the IE security level on the Windows server is acceptable, you canremove the Windows component, Internet Explorer Enhanced Security Configuration.

Procedurel 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 offsetlocal ENABLEDELAYEDEXPANSIONset uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings"reg add %uu% /v EnableHttp1_1 /t REG_DWORD /d "1" /f >nul



12-15

reg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nulsetlocal ENABLEDELAYEDEXPANSIONset uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscRanges\Trust"reg add %uu% /v :Range /t REG_SZ /d "10.141.149.193" /f >nulreg 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 domainusers.

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 IPaddress of the network elements that need to be visited.

l If the user needs to set multi-network elements and the network elements don't exisit in a samepeer IP address, multi-scripts need to be prepared and loaded separately.

l Trust in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings\ZoneMap\EscRanges\Trust" can be named as you wish.

2. Load the startup script.– Script setting for a single Windows server

(1) Log in to the Windows server with the account of administrator. ChooseStart > Run.

(2) Type gpedit.msc in the displayed dialog box. Then click OK. The GroupPolicy Object Editor dialog box is displayed.

(3) In the Group Policy Object Editor dialog box shown in Figure 12-9, chooseUser Configuration > Windows Settings > Scripts(Logon/Logoff).

Figure 12-9 Script

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

(4) Double-click Logon. A dialog box shown in Figure 12-10 is displayed. ClickShow Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.

Figure 12-10 Logon

(5) 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



12-17

(6) In the dialog box shown in Figure 12-11, click Browse to select the preparedscript and click OK. Then close the dialog box.

(7) In the dialog box shown in Figure 12-10, click Apply and confirm to loadthe prepared script.

(8) Restart the IE to validate the configuration.

NOTE

The users need to logon to the Citrix client to validate the configuration in the single Citrixnetwork.

– Script setting in a Citrix Farm network

(1) Log in to the primary or secondary Citrix domain control server with theaccount of administrator. Choose Start > Programs > AdministrativeTools > Active Directory Users and Computer. Select an organization unitand then right-click Properties. Click the Group Policy tab page in thedisplayed dialog box and click New to create a group policy object.

NOTE

l If the organization unit have be set, the users which belong to the organization unitcan all succeed in logging in to the LMT.

l You can rename the group policy object.

(2) Select the created group policy object and click Edit. In the displayed dialogbox shown in Figure 12-12, choose User Configuration > WindowsSettings > Scripts(Logon/Logoff).

Figure 12-12 Script

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

(3) Double-click Logon. A dialog box shown in Figure 12-13 is displayed. ClickShow Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.

Figure 12-13 Logon

(4) 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



12-19

(5) In the dialog box shown in Figure 12-14, click Browse to select the preparedscript and click OK. Then close the dialog box.

(6) In the dialog box shown in Figure 12-13, click Apply and confirm to loadthe prepared script.

l Removing Internet Explorer Enhanced Security Configuration1. Log in to the Windows server with the account of administrator. Choose Start >

Control Panel > Add or Remove Programs. Select Internet Explorer EnhancedSecurity Configuration in the displayed dialog box shown in Figure 12-15.

Figure 12-15 Windows components wizard

2. Click Details... in the dialog box shown in . In the displayed dialog box shown in

Figure 12-16, deselect For administrator groups and For all other user groups.

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

Figure 12-16 Internet Explorer Enhanced Security Configuration

3. Click OK and then click Next to remove Internet Explorer Enhanced SecurityConfiguration. After the removal is complete, click Finish.

4. Restart the IE to validate the configuration.

----End

12.11 Unable to Log In To LMT and Class can't StandAutomation Operation is Displayed

When the LMT is started in the IE browser, Class can't Stand Automation Operation isdisplayed.

Procedure

Step 1 Choose Start > Run.

Step 2 Type regsvr32 msscript.ocx in the displayed dialog box. Then click OK.

Step 3 Repeat Step 1. In the Run dialog box, input regsvr32 dispex.dll, regsvr32 vbscript.dll,regsvr32 scrrun.dll and regsvr32 urlmon.dll in turn, then click OK.

Step 4 Clear the cache in the browser.

NOTE


----End



12-21

12.12 LMT Failing to Load the Progress Interface After aSuccessful Login

After logging in to the LMT successfully, you may find that the LMT fail to load the progressinterface. This section describes the solution to the problem.

Contextl After logging in to the LMT successfully, you may find that the LMT fail to load the

progress interface.

shows the problem.l The version of the JRE plug-in is found to be earlier than 1.6.0_11.l Multiple JRE plug-ins can be installed on one client PC. If a user installs a JRE plug-in of

an earlier version after installing one of a later version and then use the LMT, the functionalJRE plug-in is the one of the earlier version. If the earlier version is earlier than 1.6.0_11,the preceding problem will arise.

l After you log in to the LMT successfully, an icon as shown in is displayed in the bottomright corner of the PC desktop. You can query the version of a JRE plug-in by double-clicking the icon.

Procedure

Step 1 Reinstall a JRE plug-in of a version that is later than 1.6.0_11.

NOTE

You need to restart the IE after reinstalling the JRE plug-in.

----End

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

12.13 LMT Fails to Function Properly When Error Occurs inMixed Code Security Verification of JRE

This section describes how to solve the problem that the LMT does not respond or respondsincorrectly when users perform a function on the LMT.

PrerequisiteThe LMT does not respond or responds incorrectly when users manage progress, process MMLcommands in batches, trace messages, or perform monitoring. Viewing the displayed messageon 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) .......

ContextJava Runtime Environment (JRE for short) is a compulsory third-party component for the LMTto run. Mixed code security verification is introduced in version 1.6.0_19 of JRE. With thefunction, codes are verified. If codes are found to be untrustable, four operation options displayedin Figure 12-17 are provided. Changing the default option as described below solves the previousproblem.



12-23

Figure 12-17 Java control panel

Procedure

Step 1 Open Control Panel in the operating system and double-click JAVA. The Java ControlPanel dialog box is displayed.

Step 2 In the Advanced tab page, choose Security > Mixed code (sandboxed vs. trusted) securityverification and click Disable verification (not recommended).

Step 3 Click OK to save the new setting.

----End

12 FAQBSC6900 GSM

LMT User Guide


Issue 07 (2011-01-30)

bsc6900 gsm lmt user guide(v900r011c00_07)

Documents