lmt user guide

BSC6900 UMTSV900R013C00

LMT User Guide

Issue Draft B

Date 2011-03-21

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 Draft B (2011-03-21) 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 V900R013C00

Intended AudienceThis document is intended for:

l Network engineersl System engineersl Field engineers

Organization1 Changes in the BSC6900 UMTS LMT User Guide

This chapter describes changes made in the BSC6900 UMTS 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 UMTSLMT 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 for operation and maintenanceof the BSC6900.

5 Alarm/Event Management

This describes how to manage BSC6900 alarms/Events through the LMT. Alarm/Eventmanagement allows you to analyze alarms/events more efficiently and facilitatestroubleshooting.

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 FAQ

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

ConventionsSymbol Conventions

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

Symbol Description

Indicates a hazard with a high level of risk, which if 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.

About This DocumentBSC6900 UMTSLMT User Guide

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

Issue Draft B (2011-03-21)

Symbol Description

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.

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

BSC6900 UMTSLMT User Guide About This Document


v

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 UMTSLMT User Guide

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


Contents

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

1 Changes in the BSC6900 UMTS 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 UMTSLMT 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 Syntax Check........................................................................................................................................4-11

4.4 Setting MML Parameters..............................................................................................................................4-124.5 Querying the Data Configuration Mode........................................................................................................4-134.6 Querying Data Configuration Rights............................................................................................................4-144.7 Obtaining Data Configuration Rights...........................................................................................................4-144.8 Undoing/Redoing a Data Configuration Action............................................................................................4-154.9 Undoing/Redoing Multiple Data Configuration Actions..............................................................................4-16

5 Alarm/Event 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 Flag..............................................................................................................................................5-45.1.5 Alarm Box..............................................................................................................................................5-5

5.2 Managing Alarm Logs....................................................................................................................................5-65.2.1 Setting Storage Conditions of Alarm Logs............................................................................................5-65.2.2 Querying Storage Conditions of Alarm Logs........................................................................................5-7

5.3 Managing the Alarm Filter..............................................................................................................................5-75.3.1 Creating an Alarm Filter........................................................................................................................5-75.3.2 Deleting an Alarm Filter........................................................................................................................5-85.3.3 Querying an Alarm Filter.......................................................................................................................5-8

5.4 Managing the Filter of Derived Alarms..........................................................................................................5-95.4.1 Setting the Filter of Derived Alarms......................................................................................................5-95.4.2 Querying the Filter of Derived Alarms..................................................................................................5-9

5.5 Monitoring Alarms..........................................................................................................................................5-95.5.1 Browsing Alarm/Event.........................................................................................................................5-105.5.2 Querying the Alarm/Event Log............................................................................................................5-115.5.3 Querying Alarm/Event Handling Suggestions.....................................................................................5-12

ContentsBSC6900 UMTSLMT User Guide

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


5.5.4 Querying Alarm/Event Configuration..................................................................................................5-125.5.5 Filtering Fault Alarm/Event.................................................................................................................5-135.5.6 Setting Alarm/Event Attributes............................................................................................................5-145.5.7 Manually Clearing an Alarm/Event.....................................................................................................5-145.5.8 Deleting Alarms/Events.......................................................................................................................5-155.5.9 Refreshing the Alarm/Event Window..................................................................................................5-15

5.6 Managing the Alarm Box..............................................................................................................................5-165.6.1 Querying Alarm Box Information........................................................................................................5-165.6.2 Querying Number of Alarms with Different Severities.......................................................................5-165.6.3 Operating the Alarm Box.....................................................................................................................5-175.6.4 Querying the Alarm Box Filter Level..................................................................................................5-17

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 Device Commissioning...................................................................................................................................7-47.2.1 Capturing Packets...................................................................................................................................7-4

7.3 UMTS Services...............................................................................................................................................7-57.3.1 Tracing Messages on the Iu Interface.....................................................................................................7-67.3.2 Tracing Messages on the Iupc Interface...............................................................................................7-217.3.3 Tracing Messages on the Iur Interface.................................................................................................7-277.3.4 Tracing Messages on the Iub Interface.................................................................................................7-417.3.5 Tracing Messages on the Uu Interface.................................................................................................7-497.3.6 Tracing MNCDT Messages.................................................................................................................7-517.3.7 Tracing UE Messages...........................................................................................................................7-567.3.8 Tracing Cell Messages.........................................................................................................................7-597.3.9 Tracing IOS Messages.........................................................................................................................7-617.3.10 Location Report Control.....................................................................................................................7-66

7.4 Basic Tracing Operations..............................................................................................................................7-687.4.1 Browsing Traced Messages Online......................................................................................................7-697.4.2 Viewing the Interpretation of the Trace Message................................................................................7-70



ix

7.4.3 Saving Traced Messages......................................................................................................................7-707.4.4 Browsing Traced Messages Offline.....................................................................................................7-717.4.5 Managing Tracing Tasks......................................................................................................................7-727.4.6 Managing the Trace File......................................................................................................................7-73

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 BER.....................................................................................................................................8-68.2.5 Monitoring Link Performance................................................................................................................8-7

8.3 UMTS Monitoring.........................................................................................................................................8-198.3.1 Monitoring Connection Performance...................................................................................................8-208.3.2 Monitoring Cell Performance...............................................................................................................8-308.3.3 Monitoring Board Resources...............................................................................................................8-40

8.4 General Operations of Performance Monitoring...........................................................................................8-418.4.1 Browsing the Monitoring Results Online.............................................................................................8-418.4.2 Setting the Display Mode of the Chart.................................................................................................8-428.4.3 Saving Monitoring Results...................................................................................................................8-428.4.4 Browsing Monitoring Results Offline..................................................................................................8-43

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

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-39.1.4 Querying the CPU Usage.......................................................................................................................9-49.1.5 Querying BSC Board Clock Status........................................................................................................9-49.1.6 Querying the BSC Board Information...................................................................................................9-59.1.7 Resetting the BSC Board........................................................................................................................9-59.1.8 Switching Over the BSC Boards............................................................................................................9-69.1.9 Querying the BSC Board Alarm............................................................................................................9-7

9.2 Emulation Panel Operations............................................................................................................................9-89.2.1 Introduction to the Emulation Panel.......................................................................................................9-99.2.2 Starting the Emulation Panel..................................................................................................................9-99.2.3 Querying the Status of an E1/T1 Port..................................................................................................9-109.2.4 Querying the CPU Usage.....................................................................................................................9-119.2.5 Querying BSC Board Clock Status......................................................................................................9-119.2.6 Querying the BSC Board Information.................................................................................................9-12

ContentsBSC6900 UMTSLMT User Guide

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


9.2.7 Resetting the BSC Board......................................................................................................................9-129.2.8 Switching Over the BSC Boards..........................................................................................................9-139.2.9 Querying the Status of an FE Port........................................................................................................9-149.2.10 Querying the Status of a GE Port.......................................................................................................9-159.2.11 Querying the Status of an Optical Port...............................................................................................9-159.2.12 Querying the DSP Status of a DPU....................................................................................................9-169.2.13 Querying Alarm LED Information.....................................................................................................9-16

10 FAQ...........................................................................................................................................10-110.1 The LMT gives slow responses to user operations in the Firefox browser.................................................10-310.2 The color of the LMT is not properly displayed.........................................................................................10-310.3 The verify code is not displayed on the LMT login page...........................................................................10-310.4 Installing OS Patches..................................................................................................................................10-410.5 No response on clicking the menu bar on the LMT....................................................................................10-510.6 Changing the Computer Time During the LMT Use Prohibited................................................................10-510.7 Corrupted characters appears when the csv file is opened in UTF-8 coding..............................................10-610.8 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously..............................10-810.9 Methods for Setting the Explorer Under Citrix Farm Networking.............................................................10-810.10 Unable to Log In To LMT Because IE Default Security Level Is Too High..........................................10-1410.11 LMT Failing to Load the Progress Interface After a Successful Login..................................................10-2010.12 Unable to download and Install the Java/Flash Plug-in When Internet Explorer 8 Is Used...................10-2110.13 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE......10-2210.14 Any Further Operation Performed When Some LMT Web Pages Failing to Update Causes the Web Pagesto Turn Blank....................................................................................................................................................10-23



xi

Figures

Figure 2-1 LMT window......................................................................................................................................2-6Figure 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-12Figure 4-3 Subrack data configuration mode.....................................................................................................4-13Figure 4-4 All users enabled with the data configuration rights........................................................................4-14Figure 4-5 Data configuration rights granted to the admin user........................................................................4-15Figure 5-1 Alarm box...........................................................................................................................................5-6Figure 7-1 Principles of the message tracing.......................................................................................................7-2Figure 7-2 Message tracing on the Iu interface....................................................................................................7-7Figure 7-3 Results of tracing messages on the Iu interface..................................................................................7-8Figure 7-4 Message tracing on the Iu interface....................................................................................................7-9Figure 7-5 Results of tracing MTP3 messages...................................................................................................7-10Figure 7-6 Message tracing on the Iu interface..................................................................................................7-12Figure 7-7 Results of Tracing QAAL2 Messages..............................................................................................7-13Figure 7-8 Message tracing on the Iu interface..................................................................................................7-14Figure 7-9 Message tracing on the Iu interface..................................................................................................7-16Figure 7-10 Results of tracing SCTP messages.................................................................................................7-17Figure 7-11 Message tracing on the Iu interface................................................................................................7-18Figure 7-12 Results of tracing M3UA messages................................................................................................7-19Figure 7-13 Message tracing on the Iu interface................................................................................................7-20Figure 7-14 Results of tracing SCCP messages.................................................................................................7-21Figure 7-15 Message tracing on the Iupc interface............................................................................................7-22Figure 7-16 Message tracing on the Iu interface................................................................................................7-24Figure 7-17 Results of tracing M3UA messages................................................................................................7-25Figure 7-18 Message tracing on the Iu interface................................................................................................7-26

BSC6900 UMTSLMT User Guide Figures


xiii

Figure 7-19 Results of tracing SCCP messages.................................................................................................7-27Figure 7-20 Message tracing on the Iur interface...............................................................................................7-28Figure 7-21 Message tracing on the Iu interface................................................................................................7-30Figure 7-22 Results of tracing MTP3 messages.................................................................................................7-31Figure 7-23 Message tracing on the Iu interface................................................................................................7-32Figure 7-24 Results of Tracing QAAL2 Messages............................................................................................7-33Figure 7-25 Message tracing on the Iu interface................................................................................................7-34Figure 7-26 Message tracing on the Iu interface................................................................................................7-36Figure 7-27 Results of tracing SCTP messages................................................................................................. 7-37Figure 7-28 Message tracing on the Iu interface................................................................................................7-38Figure 7-29 Results of tracing M3UA messages................................................................................................7-39Figure 7-30 Message tracing on the Iu interface................................................................................................7-40Figure 7-31 Results of tracing SCCP messages.................................................................................................7-41Figure 7-32 Message tracing on the Iub interface..............................................................................................7-42Figure 7-33 Results of Tracing Messages on the Iub Interface..........................................................................7-43Figure 7-34 Message tracing on the Iu interface................................................................................................7-44Figure 7-35 Message tracing on the Iu interface................................................................................................7-46Figure 7-36 Results of tracing SCTP messages................................................................................................. 7-47Figure 7-37 Message tracing on the Iu interface................................................................................................7-48Figure 7-38 Results of tracing M3UA messages................................................................................................7-49Figure 7-39 Message tracing on the Uu interface.............................................................................................. 7-50Figure 7-40 Results of message tracing on the Uu interface..............................................................................7-51Figure 7-41 MNCDT message tracing...............................................................................................................7-52Figure 7-42 MNCDT message tracing...............................................................................................................7-53Figure 7-43 MNCDT message tracing...............................................................................................................7-55Figure 7-44 UE message tracing........................................................................................................................7-57Figure 7-45 Results of UE message tracing.......................................................................................................7-58Figure 7-46 Cell message tracing.......................................................................................................................7-60Figure 7-47 Results of cell message tracing.......................................................................................................7-61Figure 7-48 IOS message tracing.......................................................................................................................7-63Figure 7-49 Results of IOS message tracing......................................................................................................7-65Figure 7-50 Location Report Control..............................................................................................................7-67Figure 7-51 Results of Location Report Control................................................................................................7-68Figure 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-9Figure 9-3 Subrack peripheral............................................................................................................................9-10Figure 10-1 Operation interface for importing data in Excel.............................................................................10-6Figure 10-2 Text import wizard-step 1...............................................................................................................10-7Figure 10-3 Text import wizard-step 2...............................................................................................................10-7Figure 10-4 Interface after data importation is finished.....................................................................................10-8

FiguresBSC6900 UMTSLMT User Guide

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


Figure 10-5 Active Directory Users and Computers........................................................................................10-10Figure 10-6 hong01 Properties 1......................................................................................................................10-11Figure 10-7 hong01 Properties 2......................................................................................................................10-12Figure 10-8 HTTP 1.1 settings.........................................................................................................................10-13Figure 10-9 Script.............................................................................................................................................10-15Figure 10-10 Logon..........................................................................................................................................10-16Figure 10-11 Adding a script............................................................................................................................10-16Figure 10-12 Script...........................................................................................................................................10-17Figure 10-13 Logon..........................................................................................................................................10-18Figure 10-14 Adding a script............................................................................................................................10-18Figure 10-15 Windows components wizard.....................................................................................................10-19Figure 10-16 Internet Explorer Enhanced Security Configuration..................................................................10-20Figure 10-17 Java control panel.......................................................................................................................10-23

BSC6900 UMTSLMT User Guide Figures


xv

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-8Table 2-6 Components of FTP client interface..................................................................................................2-12Table 2-7 Components of FTP server interface..................................................................................................2-13Table 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 of 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-15Table 6-1 Description of Logs..............................................................................................................................6-7Table 7-1 Operations available when browsing traced messages online...........................................................7-69

BSC6900 UMTSLMT User Guide Tables


xvii

1 Changes in the BSC6900 UMTS LMT UserGuide

This chapter describes changes made in the BSC6900 UMTS LMT User Guide.

Draft B (2011-03-21)This is the Draft B release of V900R013C00.

Compared with issue Draft A (2011-01-31), this issue includes the following new topics:l 5.1.4 Alarm Flagl 10.14 Any Further Operation Performed When Some LMT Web Pages Failing to

Update Causes the Web Pages to Turn Blank

Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes.

Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.

Draft A (2011-01-31)This is the Draft A release of V900R013C00.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not include any newtopics.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue incorporates the followingchanges:

Content Description

7 Trace Management The description is optimized.

Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not exclude any topics.

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


1-1

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 thefollowing requirements related to hardware, software, connection ports, and communicationcapability.

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

2.3 Components of the LMT WindowYou can log in to the LMT through a 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, which is a component of the LMT application, helps you upload files fromthe LMT to the OMU and download files from the OMU to the LMT. Its functions are similarto those of the FTP client. For example, you can obtain logs and upload data configuration files.

BSC6900 UMTSLMT 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 thefollowing requirements related to hardware, software, connection ports, and communicationcapability.

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 orabove

1024 x 768

CD drive 1 - -

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

Other devices 5 x 1 Keyboard, mouse,modem, audiocard, and speaker

Keyboard andmouse

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 UMTSLMT User Guide

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


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 section describes how to log in to the LMT for NE operations and how to exit it afterperforming the operations.

ContextYou must install the JAVA Platform Standard Edition Runtime Environment (JRE) plug-inbefore using the LMT. If no JRE plug-in is installed, a message is displayed when you log in tothe LMT, prompting you to install the plug-in. Follow the instructions to install the plug-in. Ifthe JRE plug-in on the LMT PC is not the latest version, a message is displayed, prompting youto upgrade the plug-in version. In this case, you are advised to uninstall the existing JRE plug-in and then install a new version. If you cannot log in to the LMT after you upgrade the JREplug-in, restart the 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.




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

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

l If users open the LMT window through the IE browser, do not modify any file folderproperties. Otherwise, the IE browser is automatically refreshed, and error occurs on theLMT.

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 colors cannot be displayed in the LMT window, 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 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, showing "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.

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/" after 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.



2-5

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 a web browser to operate and maintain the BSC6900.

Interface

Figure 2-1 shows the LMT window.

Figure 2-1 LMT window

Table 2-4 describes components of an LMT window.




Table 2-4 Components of the LMT window

Component Description

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

Batch tab You can run MML commands in batches in this tab page. Fordetails, see 4.3 Batch Processing MML Commands.

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

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

Device Maintenancetab

You can maintain the device panel. For details, see 9 DevicePanel.

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

Progress tab You can click the tab to display the progress of a task.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.

FTP Tool You can click it to download the executable application fileSFTPServer.exe. For details, see 2.4.2 FTP Client and 2.4.3 FTPServer.

Password You can click it to change the password of the current user. Afterchanging the password, you need to use the new password whenlogging in again.

File Manager You can click it to upload files from the LMT to the OMU anddownload files from the OMU to the LMT. For details, see 2.5 FileManager.

Language Setting After you choose a language, text can be input and displayed in thelanguage on the LMT.NOTE

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

About You can click it to display the version of the current LMT.

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

l You can click the web page or press the Enter key, type the password,and then click OK or press Enter to enter the LMT workspace again.



2-7


Lockup Setting You can click it to set the waiting time before the LMT screen islocked. If there is no mouse or keyboard operation during thewaiting time, the LMT automatically locks its operation screen andgoes to the locked page. The setting prevents unauthorized usersfrom using others' accounts and performing unauthorizedconfiguration and maintenance.NOTEl After you click Lockup Setting on the toolbar, the Lockup Setting

dialog box is displayed. In the Lockup Setting dialog box, you can setthe time for which the LMT waits before lockup.

l You can click the web page or press the Enter key, type the password,and then click OK or press Enter to enter the LMT workspace again.

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 describes the specific help and startup method of online help.

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 on the LMT to display

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




Name Specific Help Startup Method

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 in 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 section 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 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.

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 Tool



2-9

The 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 section 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 mentioned in2.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 setup 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 thedirectory of the setup disk.

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, a 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 startsautomatically.

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

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

InterfaceFigure 2-2 shows the FTP client interface.



2-11

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.




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.

Startup

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

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

file SFTPServer.exe.

Interface

Figure 2-3 shows the FTP server interface.

Figure 2-3 FTP server interface

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

Table 2-7 Components of FTP server interface


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



2-13


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

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.

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



2-15

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.




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.




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.




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, which is a component of the LMT application, helps you upload files fromthe LMT to the OMU and download files from the OMU to the LMT. Its functions are similarto those of the FTP client. For example, you can obtain logs and upload data configuration files.

Startup MethodClick File Manager on the toolbar of the LMT to start the file manager.



2-21

NOTE

Operators with different operation rights have different rights to access the file manager. For description ofoperation rights, see 3.1.5 Operation Rights.l ADMINISTRATOR-level and admin-level users have full operation rights. They have all of the operation

rights to the file manager.l Users at other levels have only download rights to the file manager. They are not authorized to upload or

delete files.

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

Figure 2-9 File manager interface

Table 2-13 describes each area of the file manager interface.

Table 2-13 Components of the file manager interface


1 Path Switch Area Used to directly navigate to a file folder or file.

2 File Navigation Area Displays files on the OMU in a file tree structure.

3 File List Area Provides detailed information about files on theOMU.

4 File Processing Area Contains file processing buttons.

5 Task List Area Displays task processing information about files.




Path Switch Area

This area is used to directly go to a file folder or file. You can type the path of a required file orfile folder in the text box of the area, and press Enter or click Go to go to the required path.

NOTE

l You can only type a path, for example, /bam/common/log under the Root directory on the file managerserver side.

l Adding a slash (/) in front of the root directory is optional.

File Navigation Area

This area displays file directories on the OMU. You can refresh and reset the entire directorytree by right-clicking the area and choosing Refresh Whole Folder Tree from the shortcutmenu.

File List Area

This area lists files in a selected file folder. You can select and then right-click a file in the areato choose Refresh, Upload, Download, or Delete from the shortcut menu.

File Processing Area

This area contains the following file processing buttons.

l Refresh: Click it to refresh the list of files under the current file folder.

l Upload: Click it to upload a selected file from the LMT PC to the OMU.

l Download: Click it to download a selected file from the OMU to the LMT PC. If thedirectory is specified before the download, the selected file is automatically downloadedto the preset directory.

l Delete: Click it to delete a selected file.

l Directory: Click it to change the target folder for saving a downloaded file. If the directoryis specified before the download, the selected file is automatically downloaded to the presetdirectory.

NOTE

If no new directory is set and the file manager is not closed, the download directory is the one that was set lasttime.

Task List Area

This area displays relevant information about current tasks. You can process tasks in the tasklist area in the following ways:

l Clear Finished Task: Right-click the task list area and choose Clear Finished Task to clearall finished tasks from the task list area.

l Clear Current Task: Select a task to be cleared in the area, right-click it, and choose ClearCurrent Task from the shortcut menu to clear the task from the area.

l Pause Current Task: Select an ongoing upload/download task in the area, right-click it, andchoose Pause Current Task from the shortcut menu to pause the current upload/downloadtask.



2-23

l Continue Current Task: Select a paused upload/download task in the area, right-click it,and choose Continue Current Task from the shortcut menu to continue with the currentupload/download task.

l Set Display Columns: Right-click the area and choose Set Display Columns from theshortcut menu to select information to display.




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 UMTSLMT 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 UMTSLMT User Guide



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 for 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 severity.

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




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 time duration for a user to perform the operations.

l There is no operation time limit for the admin account. The admin user can operate 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




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 added external user account cannot be the same as any of the existing user accounts.

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




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





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 for operation and maintenanceof the BSC6900.

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 UMTSLMT User Guide 4 Running MML Commands


4-1

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

4 Running MML CommandsBSC6900 UMTSLMT User Guide



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 section describes the MML commands that can be used for operation and maintenance ofthe 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 section describes the MML commands that can be used for operation and maintenance ofthe 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



4-3

Action Description

CON Confirm

DEA Deactivate

DSP List

EST Establish

EXP Export

FMT Format

FOC Obtain

HO Hand over

INH Inhibit

INS Install

LCK Lock

LOD Load

LOP Loopback test

LST List

MOD Modify

PING Ping

REL Release

REQ Request

RUN Run

RMV Remove

RST Reset

SET Set

STR Start/Open

STP Stop/Close

STA Collect statistics

SWP Swap

SYN Synchronize

TRC Trace

UBL Unblock

UIN Uninhibit




Action Description

ULD Upload

ULK Unlock

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

Number Field Description

1 CommonMaintenance tab

Displays system responses such as execution results. Inthis area, you can save command execution results andlet the system automatically scroll the results by clickingSave Results and Auto Scroll respectively. You can alsoclear all the results by clicking Clear All.NOTEl The time displayed at the beginning of the returned result is

the OMU time.

l Click Save Results to save the execution result of the MMLcommand. Note that the previous operation result will notbe saved.



4-5

Number Field Description

2 Operation Recordtab

Displays commands that have been run.NOTE

The Send Time displayed in the operation record is the time ofthe LMT PC.

3 Help Informationtab

Displays the help information for a command.

4 Manual editing area A text area for manually editing the MML commandscript.

5 History Commandbox

Displays the commands that you have run after loggingin to the system and the relevant parameters.

6 Command Inputbox

Displays in the drop-down list all the MML commandsavailable on the system. You can select an MMLcommand from the drop-down list or type in an MMLcommand for execution.

7 Parameter area Displays the parameters of the current command. Youneed to set parameter values in the boxes beforeexecuting the command. The parameters in red aremandatory, 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 dataconfiguration 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, administrators can checkwith the user. If the user is not performing data configuration, the administrators can runthe FOC CMCTRL command to revoke 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 or




network 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.)

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 Editing area



4-7

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.

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 in the Common

Maintenance tab page.l Selecting a previously-executed command from the History Command box

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

2. (Optional) Change the parameter values in the command parameter area.3. Press F9 or click Exec to run the command. The result is displayed in the Common

Maintenance tab page.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.3. Press F9 or click Exec to run the command. The result is displayed on the Common

Maintenance tab page.

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 the Common Maintenance tabpage in red.

l Copying the MML command script to the Manual Edit area1. Copy the script of a MML command with the required parameter values, and paste it

in the Manual Edit area.2. Press F9 or click Exec to run the command. The result is displayed in the Common

Maintenance tab page.

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




ContextA 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 immediatelyl Scheduled batch processing: the batch file is automatically run at a moment of a day

specified 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 Syntax CheckThis section describes how to check syntax of the MML commands before running a batch ofMML script commands. This function helps locate incorrect commands, improving maintenanceefficiency.

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.



4-9

Prerequisitel You have logged in to the LMT.l You have obtained FTP user name and password.l You have obtained the data configuration rights. For details, see 4.7 Obtaining Data

Configuration Rights.

Procedure

Step 1 Edit a batch file.1. Click Batch on the LMT main page. The Batch tab page is displayed.2. Click New and type a batch of MML commands in the input box.3. Click Save to save the edited batch file.

Step 2 Upload the MML command script file to the /ftp directory in the OMU active work area. 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 to

navigate to the ftp directory. Then click Upload.3. In the displayed Select Upload File dialog box, select the BATCHFILE.txt file saved

in local disk D and click Open to upload the file.l Through command lines

1. On a local LMT PC, choose Start > Run, enter cmd, and click OK.2. Type the d: command and press Enter to switch the local disk to disk D.3. Enter the ftp IP address command to apply for connection to the OMU. IP address is

the IP address of the OMU.4. Enter the FTP user name and password. If the authentication passes, an FTP connection

is established between the local PC and the OMU.

NOTE

The FTP user name must be the fixed value FtpUsr. The FTP password was set during installation 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

4.3.3 Syntax CheckThis section describes how to check syntax of the MML commands before running a batch ofMML script commands. This function helps locate incorrect commands, improving maintenanceefficiency.

Prerequisitel You have logged in to the LMT.l A batch file is ready.

ContextThe syntax check checks the following types of error:

l Missing colonl Missing semicolonl Incorrect MML commandl No authority to execute a correct MML commandl Redundant parametersl Incorrect parameters

Procedure

Step 1 Click New to create a batch file. Edit MML commands in the command editing area.

NOTE

You can click Open... to open an edited batch file.

Step 2 Click Analyze Syntax to check syntax of the batch file.

NOTE

l If no error exists, a Prompt dialog box is displayed showing no syntactical error. If error exists, aResult Information dialog box is displayed showing the line number and error reason.

l You can go to the command line with syntactical error by double-clicking the information in the ResultInformation dialog box.

l After Analyze Syntax is executed, a mark is displayed in front of command lines with syntactical

error in the batch file. If you move the mouse to the mark, information showing syntactical erroris displayed.

l You can check a MML command line in the batch file for error analysis by selecting it, right-clickingit, and choosing Analyze Current Line from the shortcut menu.



4-11

Step 3 In the Result Information dialog box, click Save As... to save the result.

Step 4 Click Close to end the operation.

----End

Follow-up Procedure

You can clear all syntactical analysis marks in the batch file by right-clicking the batch file areaand choosing Clear Analyze Mark from the shortcut menu.

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

Prerequisite

You have logged in to the LMT.

Procedure

Step 1 Click Setting on the Common Maintenance tab page in the MML window. The MMLSetting 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.

Prerequisite


Context

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

In non-effective mode, the data configured for the subrack takes effect only in the OMU and noton the subrack. In this case, you can run the SET CFGDATAEFFECTIVE command to setthe mode to effective mode, run the FMT DATA command to generate the data configurationfile for the subrack, and then run the RST SUBRACK command to reset the subrack. In thisway, the subrack can load the data configuration from the OMU so that the data takes effect onthe 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.

NOTE

You 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



4-13

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.


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 SETCMCTRLSW 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 dataconfiguration rights at a time.

l After the data configuration is complete, you can release the data configuration rights byrunning the REL CMCTRL command. In this way, another user can run the REQCMCTRL command to obtain the data configuration rights.

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



4-15

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 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 action

1. You can redo an undone action in either of the following ways:– Click Redo on the LMT toolbar.– Run the BEG REDO command.

2. To redo multiple actions, repeat Step 1.

----End

4.9 Undoing/Redoing Multiple Data Configuration ActionsThis section describes how to undo and redo multiple data configuration actions.





l You have obtained the data configuration rights (see 4.7 Obtaining Data ConfigurationRights), and have run multiple configuration commands successfully.

l The quick configuration mode is disabled by running the SET QUICKCFG command.l No batch commands are 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.

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



4-17

5 Alarm/Event Management

About This Chapter

This describes how to manage BSC6900 alarms/Events through the LMT. Alarm/Eventmanagement allows you to analyze alarms/events more efficiently and facilitatestroubleshooting.

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 UMTSLMT User Guide 5 Alarm/Event 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 15 types based on different managed objects.

5.1.4 Alarm FlagThis describes the BSS alarm flags that include: to-alarm-box flag, shield flag, modificationflag, and alarm cleared flag.

5.1.5 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/Event ManagementBSC6900 UMTSLMT User Guide



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 15 types based on different managed objects.l Power system: alarms related to the power systeml Environment system: alarms related to equipment room environment, such as temperature,

humidity, and door sensor



5-3

l Signaling system: alarms related to the signaling system

l Trunk system: alarms related to the trunk system, including trunk circuits and trunk boards

l Hardware system: alarms related to board hardware, such as clock and CPU

l Software system: alarms related to software

l Operating system: alarms generated during the operation of the BSC

l Communication system: alarms related to the communication system, such as alarmsbetween the BSC6900 host and the OMU

l QoS: alarms related to QoS

l Integrity: alarms generated when information is repeated, lost, distorted, disordered, orunexpected

l Operations: alarms related to refusal of operations that are generated when a service isrefused or unavailable, or when an operation procedure is improper

l Physical system: alarms related to cable interference or detection of invasion

l Security: alarms related to violation of security such as failed authentication, breach ofconfidentiality, failed non-repudiation, and unauthorized visit

l Time domain: alarms related to timeout such as information delay and password expiration

l Processing error: alarms caused by other abnormal conditions

5.1.4 Alarm FlagThis describes the BSS alarm flags that include: to-alarm-box flag, shield flag, modificationflag, and alarm cleared flag.

To-Alarm-Box Flag

The to-alarm-box flag controls whether the alarms are reported to the alarm box or not.

l ReportIn Report status, the LMT drives the alarm box to enable the audio and visual alarmfunction.

l Not reportIn Not report status, the alarm box will not be activated when an alarm is generated or whenthe alarm status changes.

NOTE

The to-alarm-box flag is used for fault alarms only. Event alarms are not reported to the alarm box.

Whether alarms are reported to the alarm box depends on the settings of to-alarm-box flag andthe shield severity of the alarm box. Alarms are reported to the alarm box only when the to-alarm-box flag is set to Report and the alarm severity is greater than or equal to the shieldseverity of the alarm box.

Shield Flag

The shield flag is set to shield the alarm information not required. The shield flag can be set toShielded or Unshielded.

l Shielded




A board does not report the alarms whose shield flags are set to Shield to the networkmanager or the alarm box. The server does not save the logs of such alarms.

l UnshieldedA board reports the alarms whose shield flags are set to Shield to the network manager orthe alarm box. The server saves the logs of such alarms.

Modification FlagThe modification flag records the modification status of alarm configuration information. Thestatus of modification flag is Modified or Unmodified.

l ModifiedAfter the alarm configuration is modified through a modification command, themodification flag is set to Modified.

l UnmodifiedWhen an alarm is in default setting or recovered to the default setting, the modification flagis set to Unmodified.

Alarm Cleared FlagThe alarm cleared flag indicates whether a fault alarm is cleared or not. The status of the alarmcleared flag is Not Cleared or Cleared.

l Not ClearedThe fault alarm is not cleared.

l ClearedA recovery alarm is received and the fault alarm is cleared.

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



5-5

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.

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




5-7

ProcedureStep 1 Run the ADD OBJALMSHLD command to create an alarm filter. The successfully added alarm

filter takes effect immediately.NOTE

l The name of the new alarm filter cannot be a duplicate of an existing one. Otherwise, the filter 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.


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

If... Then...

The filter is listed, Go to Step 2.

The filter is not listed, End this operation.

Step 2 Run the RMV OBJALMSHLD command. Select the Object Type and set other parameters asrequired to delete an alarm filter.

----End

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


ProcedureStep 1 Run the LST OBJALMSHLD command, and specify the Query Mode to query the alarm

filtering conditions.

----End




5.4 Managing the Filter of Derived 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).

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-9

5.5.1 Browsing Alarm/EventThis section describes how to browse fault alarms and event alarms on the LMT. Fault alarmsand event alarms are displayed in the Browse Alarm/Event tab page of the Alarm/Eventwindow. The alarm information provides the running status of the system in real time.

5.5.2 Querying the Alarm/Event 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/Event Handling SuggestionsThis section describes how to query the handling suggestions of an alarm.

5.5.4 Querying Alarm/Event ConfigurationThis section describes how to query alarm/event configuration.

5.5.5 Filtering Fault Alarm/EventThis 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/Event AttributesThis section describes how to set the display attributes of the alarms in the Alarm/Event window.

5.5.7 Manually Clearing an Alarm/EventIf a reported alarm can be neglected or the corresponding fault has been rectified, you canmanually set the alarm to a cleared alarm. Only the admin, the OPERATOR-level,ADMINISTRATOR-level, or authorized CUSTOM-level operators can perform this operation.

5.5.8 Deleting Alarms/EventsThis section describes how to delete alarms/Events when browsing alarms or querying alarm/Event logs.

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

5.5.1 Browsing Alarm/EventThis section describes how to browse fault alarms and event alarms on the LMT. Fault alarmsand event alarms are displayed in the Browse Alarm/Event tab page of the Alarm/Eventwindow. The alarm information provides the running status of the system in real time.

Prerequisite


Procedure

Step 1 Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page is displayed.The Normal Alarm, Event, and Engineering alarm tab pages are displayed under the BrowseAlarm/Event tab.

Step 2 Browse alarms in the Browse Alarm/Event tab page.

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




Step 4 To save an alarm record, select the alarm record first. Then right-click it and choose SaveSelect from the shortcut menu. To save all alarm records, right-click anywhere in the alarmdisplay area and choose Save All from the shortcut menu; or directly click Save All.

----End

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

Prerequisite


Context

You can set the following query conditions:l Alarm Typel Alarm Severityl Alarm Timel Special Alarm Flagl Return Amountl Cleared Timel NodeB Typel Alarm-Managed Objectsl Alarm IDl Alarm Serial No.

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


1. Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page isdisplayed.

2. In the Query Alarm/Event Log tab page, click Query Setting. The LogCondition dialog box is displayed.

3. To set the query conditions anew, click Reset. If you only need to set the NodeB typeanew, click Filter By NodeB and click Filter.

NOTE

Click Filter to reset the query conditions.

4. Click Query. The query results are displayed in the Result area.5. To learn more about an alarm, double-click it. The displayed Detail dialog box shows

the details of the alarm.6. To save an alarm record, select the alarm record first. Then right-click it and choose

Save Select from the shortcut menu. To save all alarm records, right-click anywhere



5-11

in the alarm display area and choose Save All from the shortcut menu; or directly clickSave All.

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

----End

5.5.3 Querying Alarm/Event 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/Event tab page, double-click an alarm in the Browse Alarm/Event or QueryAlarm/Event Log tab page. The Detail dialog box is displayed.

Step 2 In the Detail dialog box, click Solution.... The online help window is displayed.

NOTE

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

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

Step 4 To exit the online help, click the Close button of the help window.

----End

5.5.4 Querying Alarm/Event ConfigurationThis section describes how to query alarm/event configuration.


ContextYou can set the following search criteria:l Alarm ID: indicates the ID range of alarms to be queried. If the setting is successful, query

results show configuration of alarms/events only in the range.




l Alarm Severity: indicates the Alarm Severity. If the setting is successful, query resultsshow configuration of alarms/events of only the specified severity. If none of the alarmseverities is selected, query results show configuration of alarms/events of all severityoptions.

l Modification Flag: indicates the Modification Flag. If the setting is successful, queryresults show configuration of alarms/events matching the specified modification flag. IfAll is selected, query results show configuration of alarms/events whose ModificationFlag is set to Unmodified or Modified.

l Shield Flag: indicates the Shield Flag. If the setting is successful, query results showconfiguration of alarms/events matching the specified shield flag. If All is selected, queryresults show configuration of alarms/events whose Shield Flag is set to Shielded orUnshielded.

l To Alarm Box Flag: indicates the To Alarm Box Flag. If the setting is successful, queryresults show configuration of alarms/events matching the specified flag. If All is selected,query results show configuration of alarms/events whose To Alarm Box Flag is set toReport or Not Report.

l Return Amount: indicates the number of alarms to be returned in query results.

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

Step 2 Click the Query Alarm Configuration tab and click Query Setting. The Alarm ConfigurationCondition dialog box is displayed for you to set the search criteria.

Step 3 Set the search criteria as required.

Step 4 Click Query. Query results are displayed in the Result area.NOTE

If you need to modify alarm configuration, choose an configuration item and click Modify AlarmConfiguration, or right-click in the Result area and choose Modify Alarm Configuration from theshortcut menu.

----End

5.5.5 Filtering Fault Alarm/EventThis 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.


ProcedureStep 1 Click Alarm/Event on the LMT main page. The Browse Alarm/Event tab page is displayed.

Step 2 In the Browse Alarm/Event tab page, click Filtrate Setting. The Set Alarm FilteringConditions dialog box is displayed.

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



5-13

NOTE

l Setting Alarm Source Type displays alarm sources of the selected type in the box below.

l You can manually type an alarm source in Selected Source.

l You can manually type an alarm source in Selected Source after selecting Alarm Source Type. Associationdisplay is supported in the input box under Selected Source. For example, if you type 3, all alarm sourcesof the source type starting with 3 are displayed in the box under Selected Source.

----End

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

Prerequisite


Context

You can set the following alarm attributes:

l Set alarm colors

l Set alarm table columns

l Show/Hide tips

Procedure

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

----End

5.5.7 Manually Clearing an Alarm/EventIf a reported alarm can be neglected or the corresponding fault has been rectified, you canmanually set the alarm to a cleared alarm. Only the admin, the OPERATOR-level,ADMINISTRATOR-level, or authorized CUSTOM-level operators can perform this operation.

Prerequisite

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


1. Click Alarm/Event and select an uncleared alarm that needs to be cleared in theBrowse Alarm/Event or the Query Alarm/Event Log tab. Click Clear Alarm. TheConfirm dialog box is displayed.

2. Click OK in the Confirm dialog box. "Manually cleared" is displayed in the ClearedType column.




NOTEYou can also perform the operation through the shortcut menu. Click Alarm/Event and right-click anuncleared alarm that needs to be cleared in the Browse Alarm/Event or Query Alarm/Event Log tab.Choose Clear Alarm from the shortcut menu.

l Through MML commands1. Run the RMV ALMFLT command to manually clear an alarm.

----End

5.5.8 Deleting Alarms/EventsThis section describes how to delete alarms/Events when browsing alarms or querying alarm/Event logs.

Prerequisite


Procedure

Step 1 In the Browse Alarm/Event or Query Alarm/Event Log tab page under the Alarm/Event tab,click Delete Selected Cleared Alarms or Delete All Cleared Alarms to delete the alarms asrequired. Table 5-3 describes the functions of the buttons.

Table 5-3 Functions of the buttons

Option Description

Delete Selected ClearedAlarms

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

Delete All ClearedAlarms

Deletes all the cleared alarms in the active window. Available inthe Browse Alarm/Event or Query Alarm/Event Log tab page.

----End

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

Prerequisite


Procedure

Step 1 In the Browse Alarm/Event tab page or Query Alarm/Event Log tab page under the Alarm/Event tab, click Refresh or choose Refresh from the right-click menu to refresh the alarminformation.



5-15

NOTE

l On the Browse Alarm/Event tab page, the alarms are displayed in real time. Cleared alarms aredisplayed in grey and new alarms are added as the window is automatically refreshed. When you refreshthe window manually, the cleared alarms are removed from the Browse Alarm/Event window.

l On the Query Alarm/Event Log tab page, the alarms are not displayed in real time. When you 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 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.

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.





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.


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.



5-17

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




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 section describes how to use the FTP Client to download to the LMT PC an exportedoperation log that 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 UMTSLMT User Guide 6 Log Management


6-1

6.9 Collecting Log StatisticsThis section describes how to collect the log statistics for fault analysis. There are different typesof logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installationlogs, remote upgrade logs, and alarm logs.

6 Log ManagementBSC6900 UMTSLMT User Guide



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 the BSC6900host records in real time.

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.


Procedure

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

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


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

----End

6.5 Exporting Operation LogsThis section describes how to use the FTP Client to download to the LMT PC an exportedoperation log that is saved in the directory OMU active workspace installation directory\ftp.


Procedure

Step 1 Run the EXP LOG command. Set Log Type to OPTLOG(MML OPERATING LOG) andother parameters as required to export the corresponding log information. When exportingoperation 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-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 time isexported. For example, Start Time for exporting the operation 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-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.

Prerequisite




6-5

Procedure

Step 1 Run the EXP LOG command. Set Log Type to SECLOG(SECURITY LOG) and otherparameters as required to export the corresponding log information. When exporting the securitylogs, 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-SLOG.txt.l If Time Mode is set to RELATIVE_T(Relative Time), the security log within the last N

hour(s) before the command is executed is exported. N stands for the relative time length.For example, if Relative Time is 72, then the log within the latest 72 hours is exported.

l If Time Mode is set to ONTIME(Fixed Time), the security log within the absolute time 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


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 for fault analysis. There are different typesof logs: host logs, OMU logs, database logs, system event logs, operation logs, OMU installationlogs, remote upgrade logs, and alarm logs.


Procedure

Step 1 Run the COL LOG command. Set the required parameters to collect the corresponding logstatistics. For more description of log ,see Table 6-1.

Table 6-1 Description of Logs

Type File Path Description

PFM_RESULT(Performance Result File)

/bam/version_a/ftp/COLLOGINFO/PFM-LOG/

Recording traffic statisticsfrom NEs to the M2000.Used for traffic analyzing.

HOST_PFM_RESULT(Performance Result Filefrom Host)


Recording traffic statisticsfrom boards to the OMU.Used for traffic analyzing.



6-7


ACTIVE_DEF_MEAS_FILE(Active DefaultMeasurement Task File)


Active traffic statisticdefinition file from theM2000 to NEs. Used fortraffic analyzing.

STANDBY_DEF_MEAS_FILE(Standby DefaultMeasurement Task File)


Standby traffic statisticdefinition file from theM2000 to NEs. Used fortraffic analyzing.

PFM_SWITCHS(TheSwitchs Information forPerformance)

/ Reserved parameter value.

HISTORY_ALARM(History Alarm File)

/bam/version_a/ftp/COLLOGINFO/ALM-LOG/

Recording alarms and eventsreported by NEs. Used foralarm and event analysis.

HISTORY_FAULT(HistoryFault File)


Recoding the faults reportedby all NEs. Used for faultanalysis.

ALM_SYSTEM_CFG(TheConfigured Information ofAlarm)


Recording the configurationinformation related to alarmmanagement. Used for alarmand event analysis.

SECURITY_LOG(SecurityLogs)

/bam/version_a/ftp/COLLOGINFO/SEC-LOG/

Security logs of a NE. Usedfor analyzing security-relatedoperations on the NE.

OPT_LOG(Operation Logs) /bam/version_a/ftp/COLLOGINFO/OPT-LOG/

Operation logs of a NE. Usedfor analyzing user operationson the NE.

OMU_LOG(The LogInformation of OMU)

/bam/version_a/ftp/COLLOGINFO/SINGLE-BAM/

Operation and status logs ofthe OMU board. Used foranalyzing OMU faults andstatus.

BSC_CFG_MML(The DataConfigure File of the BSC)

/bam/version_a/ftp/COLLOGINFO/CFG-LOG/ExportCfgmml/

Recording the BSCconfiguration data. Used forconfiguration datarestoration.

CELL_BASIC_INFO(TheBasic Information of Cells)

/bam/version_a/ftp/COLLOGINFO/CFG-LOG/CellBasicInfo/

Recoding the basicinformation of cells under aBSC. Used for checking themapping between cell IDsand internal cell IDs.

BSC_SERIES_NO(TheSeries No. of the BSC)

/bam/version_a/ftp/COLLOGINFO/CFG-LOG/

Recording the EquipmentSerial Number (ESN) of aBSC. Used for license check.





DB_BAK(The Backup Fileof the Database)

/bam/version_a/ftp/COLLOGINFO/CFG-LOG/MysqlDbBak/

Backed up OMU databaseinformation. Used for datarestoration.

MEM_DB_BAK(TheBackup File of the Databasein Memory)

/bam/version_a/ftp/COLLOGINFO/CFG-LOG/MemDbBak/

Backed up OMUmemory database. Used forlocating the inconsistencybetween the memorydatabase and the MYSQLdatabase.

DEBUG_LOG(TheCommon Debug Log)

/bam/common/fam/famlogfmt/

Recording software runningerrors. Used for locating soft-ware defects.

LAST_WORD(The LastWord Log)

/bam/common/fam Recording the loginformation that is generatedbefore a board is abnormallyreset. Used for locating theabnormal board reset.

DSP_DEBUG_LOG(TheDebug Log of DSP)


DSP debug logs. Used forlocating DSP faults.

HOST_LOG(The RunningLog of the Host)

/bam/common/fam/famlog/ Host operation logs.

3G_CHR_LOG(The CHRLog for UMTS)


Recording call faults exceptfaults during call access andcall drops. Used foranalyzing the causes offailures in failed soft or hardhandovers, relocations, orcell updates.

BSC_INFO(The BasicInformation of the BSC)

/bam/version_a/ftp/COLLOGINFO/BSC-LOG/

Recording the BSC softwarepatch information, and thebar code, softwareinformation, hardwareinformation, loadinginformation, and license ofeach board. Used forchecking whether thesoftware versions, data andlicenses of boards are correct.

BIOS_LOG(BIOS Log) /bam/common/fam/famlogfmt/

BIOS system abnormalrunning logs. Used forlocating BIOS faults.



6-9


CALLFAULT_LOG(CALLFAULT Log)


Recording faults during callaccess and call drops. Usedfor analyzing the causes ofcall access failures and calldrops.

PCHR_LOG(PCHR Log) /bam/common/fam/famlogfmt/pchr

Recording detailedinformation of each call,including service access, callrelease, handover, DCCC,and signal quality. Used forKPI analysis and as areference when handling usercomplaints.

SYSFAULT_LOG(SYSFAULT Log)

/bam/common/fam/famlogfmt/sysfault/

Recording severe software/hardware faults such asresource leakages and devicefaults. Used for networkhealth check.

NOTE

l version_a is the active workspace of OMU.

----End




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 Device CommissioningThis section describes how to perform the device commission.

7.3 UMTS ServicesThis section describes how to perform tracing tasks related to UMTS services.

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

BSC6900 UMTSLMT 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 UMTSLMT User Guide



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 Device CommissioningThis section describes how to perform the device commission.

7.2.1 Capturing PacketsThis section describes how to trace messages at the MAC layer. Analysis of packet headers andbodies helps locate transmission channel disconnection and packet loss.

7.2.1 Capturing PacketsThis section describes how to trace messages at the MAC layer. Analysis of packet headers andbodies helps locate transmission channel disconnection and packet loss.

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

Contextl The following problems can be located by capturing packets:

– The BSC does not receive packets.– Packets are received by an interface board but are discarded on the board due to an

interface problem. The packets are thus not sent to other boards of the BSC.– Packets are sent to other non-interface boards but are discarded.

l When packet loss occurs or PPP/MP/Ethernet interconnection cannot be established, youcan check whether correct packets are sent to and received by interface boards by capturingpackets on the panel. Then you can quickly determine where the problem lies, in an interfaceboard or in external transmission.

l When packets are lost between two boards or connection cannot be established betweentwo boards, you can check whether correct packets are sent to and received by interfaceboards and other boards in the system by capturing backplane packets. Then you can quicklydetermine where the problem lies, in an interface board or in another board (DPU/XPUboard) in the system.

l Packet capture in the following scenarios is supported:– Panel Ethernet packet capture– Backplane Ethernet packet capture– Panel and backplane Ethernet packet capture– Panel PPP packet capture– Panel MP packet capture– Panel PPP and backplane Ethernet packet capture– Panel MP and backplane Ethernet packet capture– Panel ATM cell capture– Panel ATM cell capture and backplane Ethernet packet capture

l Only one packet tracing task can be started for each interface board at a time. Tracing ofmultiple interface boards can be started simultaneously.




Procedure

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

Step 2 In the Trace Navigation Tree pane, choose Device Commissioning > Packet Capture. ThePacket Capture dialog box is displayed.

Step 3 In the Packet Capture dialog box, set parameters as required.

NOTE

l Panel Ethernet packet capture and Backplane Ethernet packet capture are both stood. If you only need capturethe Panel Ethernet packet, PortType(Inner) should be set to Inner Invalid. If you only need capture theBackplane Ethernet packet, PortType(Outer) should be set to Outer Invalid.

l In the case of capturing the panel Ethernet packet, you should set PortType(Outer) to be Ethernet and setthe corresponding parameters in Outer tab page.

l In the case of capturing the panel ATM cell packet, you should set PortType(Outer) to be ATM cell andset the corresponding parameters in ATM tab page.

l In the case of capturing the panel PPP/MP Group/HDLC packet, you should set PortType(Outer) to bePPP/MP Group/HDLC and set the corresponding parameters in Basic tab page.

l In the case of capturing the Backplane Ethernet packet, you should set PortType(Inner) to be Ethernetand set the corresponding parameters in Inner tab page.

l In the case of capturing the Backplane Ethernet packet, you should set PortType(Inner) to be Ethernetand set the corresponding parameters in Inner tab page.

l Outer Intercept Length/Inner Intercept Length: This parameter specifies the length of the traced packetto be intercepted. Only the fields of the traced packet within the intercepted length are reported, and theextra fields are not reported. If the length of the traced packet is shorter than the value of this parameter, theentire packet is reported.

Step 4 Click Submit to start packet capture. For the detailed capture period of time, see the value ofTrace Time(OMU Time) in the Packet Capture dialog box.

----End

Follow-up Procedurel You can manage packet capture in Manage Trace File under Trace. You can query, stop,

delete, or restart a packet capture task.l After packet capture is complete, result files are automatically saved in the /bam/common/

fam/trace/ directory on the OMU. You can obtain the files by logging in to the OMU throughFTP.

7.3 UMTS ServicesThis section describes how to perform tracing tasks related to UMTS services.

7.3.1 Tracing Messages on the Iu InterfaceThis section describes how to trace messages on the Iu interface on the LMT.

7.3.2 Tracing Messages on the Iupc InterfaceThis section describes how to trace messages on the Iupc interface on the LMT.

7.3.3 Tracing Messages on the Iur InterfaceThis section describes how to trace messages on the Iur interface on the LMT.

7.3.4 Tracing Messages on the Iub Interface



7-5

This section describes how to trace messages on the Iub interface on the LMT.

7.3.5 Tracing Messages on the Uu InterfaceThis section describes how to trace all or specified types of signaling messages in a specifiedcell over the Uu interface. You can perform this task to identify the failure cause in the followingprocedures: RRC connection setup, radio bearer setup, physical channel reconfiguration, andcell update.

7.3.6 Tracing MNCDT MessagesThis section describes how to detect missing neighboring cell relationship of a cell. Using theMissing Neighbor Cell Detect Trace (MNCDT) function, you can detect missing neighboringcell relationship. MNCDT consists of intra-frequency, inter-frequency, and inter-RAT MNCDT,which are independent of each other.

7.3.7 Tracing UE MessagesThis section describes how to trace UE messages. You can perform this task to analyze the callprocedure failure cause by monitoring interworking of the signaling on each standard interface,interworking of the signaling on the user plane, and uplink and downlink data. In combinationwith a drive test, this task helps to locate problems or deal with complaints from VIP subscribers.

7.3.8 Tracing Cell MessagesThis section describes how to trace cell messages. The UE statistics can be reported in the tracingresult if required. The tracing results of the cell messages provide reference for troubleshootingcommon channel faults when the access success rate is low or zero in the cell.

7.3.9 Tracing IOS MessagesThis section describes how to trace a number of calls that meet the sampling criteria within aspecified range of cells. When creating the task, you can specify the number of calls to be tracedand specify messages to be traced by selecting the event type.

7.3.10 Location Report ControlThis section describes how to trace the results of a location tracing initiated by the CN. You canalso perform this task to simulate CN-initiated location tracing and to trace the results of thelocation tracing.

7.3.1 Tracing Messages on the Iu InterfaceThis section describes how to trace messages on the Iu interface on the LMT.

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


ContextYou can start the Iu interface tracing on the LMT to monitor interworking of the signalingmessages on the Iu interface.

When starting a tracing task, you can make the following choices:




l Tracing the messages processed by a specified CPUS subsysteml Tracing the required types of messagel Tracing all types of messagesl Tracing signaling messages at the transport network layer

For each subsystem, a maximum of six tracing tasks can be performed on the Iu interfacesimultaneously. Therefore, the maximum number of tracing tasks that can be performed on theIu interface is the number of subsystems multiplied by six.

Procedure


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

Figure 7-2 Message tracing on the Iu interface

Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectIU under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,

DPC(HEX) needs to be specified.



7-7

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

Step 4 In the IU tab page, select Message Type.

Step 5 Click Submit.

----End

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 tracing messages on the Iu 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.4 Basic Tracing Operations.

Tracing MTP3 Messages

This section describes how to trace Message Transfer Part Level 3 (MTP3) messages, whichcan be traced on the Iu and Iur interfaces. The traced messages include upper layer user messagessuch as QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling linktest messages, and MTP3 signaling network management messages.





ContextMTP3 message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting the problem that MTP3 links are unavailable but the corresponding SAAL linksare available can be facilitated.

NOTE

l A maximum of six MTP3 message tracing tasks can be performed in a subsystem simultaneously.l The following steps take MTP3 message tracing on the Iu interface as an example.l Steps for MTP3 message tracing on the other interfaces are similar to those for the tracing on the Iu

interface.

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





7-9

Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectMTP3 under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,

DPC(HEX) needs to be specified.l For description of Trace Mode, see 7.1.3 Trace Mode.

Step 4 In the MTP3 tab page, select Message Type.


----End




Figure 7-5 Results of tracing MTP3 messages



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

Tracing QAAL2 MessagesThis section describes how to trace QAAL2 messages, which can be traced on the Iu, Iur, andIub interfaces. QAAL2 message tracing helps to monitor interworking of QAAL2 messages andlocate establishment failure and abnormal release of channels on the AAL2 user planerespectively on the Iu, Iur, and Iub interfaces.





ContextQAAL2 message tracing determines whether the failure or abnormal release occurs at the localor peer end by checking whether an ESTABLISH_REQUEST message is sent and checking thereturned messages.l If the RNC does not send an ESTABLISH_REQUEST message, the problem occurs

generally at the local end, namely RNC, because of insufficient bandwidth or incorrectconfiguration of the ATM address.

l If the RNC sends an ESTABLISH_REQUEST message and receives anRELEASE_CONFIRM message from the peer end, you can infer that the problem occursat the peer end.

NOTE

l A maximum of six QAAL2 message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take QAAL2 message tracing on the Iu interface as an example.

l Steps for QAAL2 message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.

Procedure





7-11


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectQAAL2 under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


Step 4 In the QAAL2 tab page, set QAAL2 Trace Type.

NOTE

You can set QAAL2 Trace Type to select QAAL2 message tracing on a specified interface, a type of interface,or all interfaces.


----End







Figure 7-7 Results of Tracing QAAL2 Messages





Tracing SAAL Messages

This section describes how to trace Signaling ATM Adaptation Layer (SAAL) messages, whichcan be traced on the Iu, Iur, and Iub interfaces. SAAL message tracing helps to monitorinterworking of SAAL messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SAAL links.

Prerequisite


ContextNOTE

l A maximum of six SAAL message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take SAAL message tracing on the Iu interface as an example.

l Steps for SAAL message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.



7-13

Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSAAL under Trace Type.

l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,DPC(HEX) needs to be specified.


Step 4 In the SAAL tab page, specify Signaling Link ID and select Trace Object.

NOTE

To query the SAAL link ID, run the LST SAALLNK command.


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





Tracing SCTP Messages

This section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iu, Iur, and Iub interfaces. SCTP message tracing helps to monitorinterworking of SCTP messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SCTP links.

Prerequisite


Context

As the NCP/CCP/M3UA function unit uses SCTP links as lower layer links in IP transport, youcan start SCTP message tracing to check whether the NCP/CCP/M3UA function unit worksimproperly.

As data is frequently received by and sent to SCTP links, starting SCTP message tracing affectssystem performance to a certain extent. It is not recommended that multiple SCTP messagetracing tasks be started simultaneously.

NOTE

l A maximum of six SCTP message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take SCTP message tracing on the Iu interface as an example.

l Steps for SCTP message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.

Procedure





7-15


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP under Trace Type.



Step 4 In the SCTP tab page, specify SCTP Link No. and select SCTP Message.

NOTE

To query the SCTP link number, run the LST SCTPLNK command.


----End






– A window shown in Figure 7-10is 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-10 Results of tracing SCTP messages




Tracing M3UA MessagesThis section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iu and Iur interfaces. M3UA message tracing helps to facilitatetroubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available.


ContextM3UA message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available can be facilitated.

NOTE

l A maximum of six M3UA message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take M3UA message tracing on the Iu interface as an example.

l Steps for M3UA message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.

Procedure




7-17



Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectM3UA under Trace Type.



Step 4 In the M3UA tab page, select M3UA Message and set other parameters.

NOTE

l Before tracing M3UA messages, you need to configure its lower layer links, SCTP links and then configureM3UA links.

l To query an M3UA link set number, an M3UA link number, and more information about M3UA links, runthe LST M3LNK command.


----End







Figure 7-12 Results of tracing M3UA messages





Tracing SCCP Messages

This section describes how to trace Signaling Connection Control Part (SCCP) messages, whichcan be traced on the Iu and Iur interfaces. SCCP messages include the connection-orientedmessages and the connectionless messages. SCCP message tracing helps to monitorinterworking of SCCP messages and locate establishment failure and abnormal release ofchannels respectively on the Iu and Iur interfaces.

Prerequisite


ContextNOTE

l A maximum of six SCCP message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take SCCP message tracing on the Iu interface as an example.

l Steps for SCCP message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.



7-19

Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSCCP under Trace Type.




----End







Figure 7-14 Results of tracing SCCP messages




7.3.2 Tracing Messages on the Iupc InterfaceThis section describes how to trace messages on the Iupc interface on the LMT.

Tracing Messages on the Iupc InterfaceThis section describes how to trace the signaling messages over the Iupc (Iu Position Calculation)interface, including the connection-oriented messages. You can perform this task to identify thecause of the failure in the following scenarios: PCAP Position Initiations, PCAP PositionActivation.


ContextYou can start the Iupc interface tracing on the LMT to monitor the interworking of signalingmessages over the Iupc interface.

When starting a tracing task, you can select the following operations:l Tracing the messages processed by the specified CPUS subsysteml Tracing the required types of messagel Tracing all types of messagesl Tracing signaling messages at the transport network layer



7-21

For each subsystem, a maximum of six Iupc interface tracing tasks can be performedsimultaneously.

Procedure


Step 2 On the Trace Navigation Tree pane, choose Trace > UMTS Services > Iupc InterfaceTrace. The Iupc Interface Trace dialog box is displayed, as shown in Figure 7-15.

Figure 7-15 Message tracing on the Iupc interface

Step 3 In the Iupc Interface Trace dialog box, set parameters in the default Basic tab page and selectIUPC under Trace Type.



Step 4 In the IUPC tab page, select the message type.


----End







NOTE

In the message browse window of Iupc Interface Tracing, the number in the InformationSource column represents the DPC of the neighboring RNC. You can query more informationabout the DPC by running the command LST N7DPC.


Tracing M3UA Messages

This section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iu and Iur interfaces. M3UA message tracing helps to facilitatetroubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available.

Prerequisite


Context

M3UA message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available can be facilitated.

NOTE




Procedure





7-23






NOTE




----End











Tracing SCCP MessagesThis section describes how to trace Signaling Connection Control Part (SCCP) messages, whichcan be traced on the Iu and Iur interfaces. SCCP messages include the connection-orientedmessages and the connectionless messages. SCCP message tracing helps to monitorinterworking of SCCP messages and locate establishment failure and abnormal release ofchannels respectively on the Iu and Iur interfaces.


ContextNOTE




Procedure





7-25


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSCCP under Trace Type.




----End











7.3.3 Tracing Messages on the Iur InterfaceThis section describes how to trace messages on the Iur interface on the LMT.

Tracing Messages on the Iur InterfaceThis section describes how to trace the signaling messages over the Iur interface, including theconnection-oriented messages and the connectionless messages. You can perform this task toidentify the failure cause in the following procedures on the Iur interface: radio link setup, radiolink addition, radio link deletion, resource release on common transport channel, DL powercontrol, and paging.


ContextFor each subsystem, a maximum of six Iur interface tracing tasks can be performedsimultaneously. Therefore, the maximum number of tracing tasks that can be performed on theIur interface is the number of subsystems multiplied by six.

Procedure


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



7-27

Figure 7-20 Message tracing on the Iur interface

Step 3 In the Iur Interface Trace dialog box, set parameters in the default Basic tab page and selectIUR under Trace Type.



Step 4 In the IUR tab page, select Message Type.

NOTE

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


----End










Tracing MTP3 MessagesThis section describes how to trace Message Transfer Part Level 3 (MTP3) messages, whichcan be traced on the Iu and Iur interfaces. The traced messages include upper layer user messagessuch as QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling linktest messages, and MTP3 signaling network management messages.


ContextMTP3 message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting the problem that MTP3 links are unavailable but the corresponding SAAL linksare available can be facilitated.

NOTE

l A maximum of six MTP3 message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take MTP3 message tracing on the Iu interface as an example.

l Steps for MTP3 message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.

Procedure





7-29


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectMTP3 under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


Step 4 In the MTP3 tab page, select Message Type.


----End







Figure 7-22 Results of tracing MTP3 messages





Tracing QAAL2 Messages

This section describes how to trace QAAL2 messages, which can be traced on the Iu, Iur, andIub interfaces. QAAL2 message tracing helps to monitor interworking of QAAL2 messages andlocate establishment failure and abnormal release of channels on the AAL2 user planerespectively on the Iu, Iur, and Iub interfaces.

Prerequisite


Context

QAAL2 message tracing determines whether the failure or abnormal release occurs at the localor peer end by checking whether an ESTABLISH_REQUEST message is sent and checking thereturned messages.

l If the RNC does not send an ESTABLISH_REQUEST message, the problem occursgenerally at the local end, namely RNC, because of insufficient bandwidth or incorrectconfiguration of the ATM address.

l If the RNC sends an ESTABLISH_REQUEST message and receives anRELEASE_CONFIRM message from the peer end, you can infer that the problem occursat the peer end.

NOTE

l A maximum of six QAAL2 message tracing tasks can be performed in a subsystem simultaneously.

l The following steps take QAAL2 message tracing on the Iu interface as an example.

l Steps for QAAL2 message tracing on the other interfaces are similar to those for the tracing on the Iuinterface.



7-31

Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectQAAL2 under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


Step 4 In the QAAL2 tab page, set QAAL2 Trace Type.

NOTE

You can set QAAL2 Trace Type to select QAAL2 message tracing on a specified interface, a type of interface,or all interfaces.


----End







Figure 7-24 Results of Tracing QAAL2 Messages




Tracing SAAL MessagesThis section describes how to trace Signaling ATM Adaptation Layer (SAAL) messages, whichcan be traced on the Iu, Iur, and Iub interfaces. SAAL message tracing helps to monitorinterworking of SAAL messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SAAL links.




7-33

ContextNOTE




Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSAAL under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,





Step 4 In the SAAL tab page, specify Signaling Link ID and select Trace Object.NOTE



----End







Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iu, Iur, and Iub interfaces. SCTP message tracing helps to monitorinterworking of SCTP messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SCTP links.


ContextAs the NCP/CCP/M3UA function unit uses SCTP links as lower layer links in IP transport, youcan start SCTP message tracing to check whether the NCP/CCP/M3UA function unit worksimproperly.


NOTE






7-35

Procedure








NOTE



----End












Tracing M3UA Messages

This section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iu and Iur interfaces. M3UA message tracing helps to facilitatetroubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available.

Prerequisite


Context

M3UA message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available can be facilitated.



7-37

NOTE




Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectM3UA under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,






NOTE




----End









Tracing SCCP Messages

This section describes how to trace Signaling Connection Control Part (SCCP) messages, whichcan be traced on the Iu and Iur interfaces. SCCP messages include the connection-orientedmessages and the connectionless messages. SCCP message tracing helps to monitorinterworking of SCCP messages and locate establishment failure and abnormal release ofchannels respectively on the Iu and Iur interfaces.

Prerequisite




7-39

ContextNOTE




Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSCCP under Trace Type.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,






----End









7.3.4 Tracing Messages on the Iub InterfaceThis section describes how to trace messages on the Iub interface on the LMT.

Tracing Messages on the Iub Interface

This section describes how to trace the signaling messages over the Iub interface, that is, theNodeB Application Part (NBAP) messages. You can perform this task to identify the failurecause in the following procedures on the Iub interface: radio link setup, radio linkreconfiguration, resource audit, cell setup, cell reconfiguration, common transport channel setup,and system information update.

Prerequisite




7-41

Context

For each subsystem, a maximum of six Iub interface tracing tasks can be performedsimultaneously. Therefore, the maximum number of tracing tasks that can be performed on theIub interface is the number of subsystems multiplied by six.

Procedure


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

Figure 7-32 Message tracing on the Iub interface

Step 3 In the Iub Interface Trace dialog box, set parameters in the default Basic tab page and selectIUB under Trace Type.


Step 4 In the IUB tab page, select Message Type and set other parameters.


----End







Figure 7-33 Results of Tracing Messages on the Iub Interface




Tracing SAAL MessagesThis section describes how to trace Signaling ATM Adaptation Layer (SAAL) messages, whichcan be traced on the Iu, Iur, and Iub interfaces. SAAL message tracing helps to monitorinterworking of SAAL messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SAAL links.


ContextNOTE






7-43

Procedure




Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSAAL under Trace Type.



Step 4 In the SAAL tab page, specify Signaling Link ID and select Trace Object.

NOTE



----End











Tracing SCTP Messages

This section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iu, Iur, and Iub interfaces. SCTP message tracing helps to monitorinterworking of SCTP messages respectively on the Iu, Iur, and Iub interfaces and locateunavailable SCTP links.

Prerequisite


Context

As the NCP/CCP/M3UA function unit uses SCTP links as lower layer links in IP transport, youcan start SCTP message tracing to check whether the NCP/CCP/M3UA function unit worksimproperly.


NOTE




Procedure





7-45






NOTE



----End











Tracing M3UA MessagesThis section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iu and Iur interfaces. M3UA message tracing helps to facilitatetroubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available.


ContextM3UA message tracing can check whether Originating Signaling Point Code (OPC), DestinationSignaling Point Code (DPC), and Signaling Link Selection Code (SLS) in Signaling Link TestMessage (SLTM) messages match each other and the negotiated data. In this way,troubleshooting of the problem that M3UA links are unavailable but the corresponding IP linksare available can be facilitated.

NOTE




Procedure




7-47







NOTE




----End











7.3.5 Tracing Messages on the Uu InterfaceThis section describes how to trace all or specified types of signaling messages in a specifiedcell over the Uu interface. You can perform this task to identify the failure cause in the followingprocedures: RRC connection setup, radio bearer setup, physical channel reconfiguration, andcell update.


ContextYou can start the Uu interface tracing on the LMT to monitor interworking of signaling messageson the Uu interface.

When starting a tracing task, you can make the following choices:l Tracing messages of one or multiple BSC6900s and the cellsl Tracing all types of messages on the Uu interfacel Tracing the specified types of messages

A maximum of six Uu interface tracing tasks can be performed simultaneously. Each Uuinterface tracing task targets at a maximum of 32 cells.



7-49

Procedure


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

Figure 7-39 Message tracing on the Uu interface

Step 3 In the Uu Interface Trace dialog box, specify RNCID:CellID under Cell Config and set otherparameters.l RNC ID indicates the RNC ID of the cell to be traced. To query it, run the LST

URNCBASIC command.l CellID needs to be set to the ID of the cell sending and receiving messages. The parameter

can be queried by running the LST UCELL command.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End







Figure 7-40 Results of message tracing on the Uu interface





7.3.6 Tracing MNCDT MessagesThis section describes how to detect missing neighboring cell relationship of a cell. Using theMissing Neighbor Cell Detect Trace (MNCDT) function, you can detect missing neighboringcell relationship. MNCDT consists of intra-frequency, inter-frequency, and inter-RAT MNCDT,which are independent of each other.

Tracing Intra-Frequency MNCDT Messages

This section describes how to trace messages indicating missing intra-frequency neighboringcell relationship.

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



7-51

l The parameter switch for detecting missing neighboring cell relationship is set to ON. Thesetting can be queried by running the LST UNCELLDETECTSWITCH command.

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > MNCDT Trace.Accordingly, the MNCDT Trace dialog box is displayed, as shown in Figure 7-41.

Figure 7-41 MNCDT message tracing

Step 3 In the MNCDT Trace dialog box, set Detection Type to Intra Freq.l For description of Trace Mode, see 7.1.3 Trace Mode.


----End











Tracing Inter-Frequency MNCDT Messages

This section describes how to trace messages indicating missing inter-frequency neighboringcell relationship.



Procedure




Step 3 In the MNCDT Trace dialog box, set Detection Type to Inter Freq.

l Uplink UARFCN: indicates the uplink UTRA Absolute Radio Frequency Channel Number(UARFCN) of the cell to be traced for detecting missing neighboring relationship



7-53

l Downlink UARFCN: indicates the downlink UARFCN of the cell to be traced for detectingmissing neighboring relationship

l Start of Primary Scrambling Code: indicates the minimum scrambling code for anMNCDT task

l End of Primary Scrambling Code: indicates the maximum scrambling code for an MNCDTtask. End of Primary Scrambling Code must be not less than Start of Primary ScramblingCode.



----End








Tracing Inter-RAT MNCDT Messages

This section describes how to trace messages indicating missing inter-RAT neighboring cellrelationship.



Procedure







Step 3 In the MNCDT Trace dialog box, set Detection Type to Inter RAT.

l Start of NCC: indicates the start of the Network Color Code (NCC) for the cell to be tracedfor detecting missing neighboring cell relationship. The parameter value ranges from 0 to 7.

l End of NCC: indicates the end of the NCC for the cell to be traced for detecting missingneighboring cell relationship. The parameter value ranges from 0 to 7. End of NCC must begreater than Start of NCC.

l Start of BCC: indicates the start of the Base Transceiver Station Color Code (BCC) for thecell to be traced for detecting missing neighboring cell relationship. The parameter valueranges from 0 to 7.

l End of BCC: indicates the end of the BCC for the cell to be traced for detecting missingneighboring cell relationship. The parameter value ranges from 0 to 7. End of BCC must begreater than Start of BCC.

l Band Indicator: indicates the band for overlapping frequencies of DCS 1800 and PCS 1900.

l Start of BCCH ARFCN: indicates the minimum Absolute Radio Frequency ChannelNumber (ARFCN) for an MNCDT task

l End of BCCH ARFCN: indicates the maximum ARFCN for an MNCDT task



----End




7-55







7.3.7 Tracing UE MessagesThis section describes how to trace UE messages. You can perform this task to analyze the callprocedure failure cause by monitoring interworking of the signaling on each standard interface,interworking of the signaling on the user plane, and uplink and downlink data. In combinationwith a drive test, this task helps to locate problems or deal with complaints from VIP subscribers.

Prerequisite


CAUTIONAs private information of users is revealed during UE tracing, only admin users orADMINISTRATOR users are allowed to perform the tracing.

Context

The UE tracing task is to trace signaling messages of a UE on the Iu, Iur, Iub, and Uu interfaces.The UE can be specified by IMSI, TMSI, P-TMSI, or IMEI.

NOTE

A maximum of 12 UE tracing tasks can be performed simultaneously.

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. Accordingly,the UE Trace dialog box is displayed, as shown in Figure 7-44.




Figure 7-44 UE message tracing

Step 3 In the displayed UE Trace dialog box, set the parameters as required.l IMSI/IMEI/TMSI/P-TMSI: identifies the UE. You can choose to trace the UE by its IMSI,

IMEI, TMSI, or P-TMSI. Choosing to trace the UE by the TMSI, you need to specify LAC,MCC, and MNC. Choosing to trace the UE by the P-TMSI, you need to specify LAC, RAC,MCC, and MNC.

l Filter traced messages by setting parameters in the IUR, IUB, IU, and UU tab pages.l Monitor tab page: indicates performance counters to be monitored during tracing of a single

UE– Uplink SIR: Selecting the counter starts monitoring of uplink Signal to Interference Ratio

(SIR) during tracing of a single UE. The counter is reported periodically. The period ofreporting the monitoring reports ranges from 0.1s to 60s.

– Uplink Tx Power: Selecting the counter starts monitoring of uplink transmit powerduring tracing of a single UE. The counter is reported periodically. The period of reportingthe monitoring reports ranges from 0.25s to 64s.

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



7-57

– Downlink Tx Code Power: Selecting the counter starts monitoring of downlink codetransmit power during tracing of a single UE. The counter is reported periodically. Theperiod of reporting the monitoring reports ranges from 0.1s to 60s.

– PCPICH Ec/No RSCP: Selecting the counter starts monitoring of PCPICH Ec/No andReceived Signal Code Power (RSCP) during tracing of a single UE. The counter isreported periodically. The period of reporting the monitoring reports ranges from 0.1s to60s.

– AMR Mode: Selecting the counter starts monitoring of AMR mode during tracing of asingle UE. The counter is reported periodically. If AMR mode changes, the current modeis reported.

– RTWP(0.4s): Selecting the counter starts monitoring of received total wideband power(RTWP) received for the cell serving the current UE. The counter is reported every 0.4second.

– TRX Transmit Power(0.4s): Selecting the counter starts monitoring of downlinktransmit power transmitted for the cell serving the current UE. The counter is reportedevery 0.4 second.


----End




Figure 7-45 Results of UE message tracing




NOTE

l If you trace a UE by specifying the IMSI and the IMSI is carried in the RRC CONNECTIONREQUEST message sent by the UE for network access, the UE tracing task traces all themessages that are sent after the RRC CONNECTION REQUEST message.

l Assume that you trace a UE by specifying the IMSI and the IMSI is not carried in the RRCCONNECTION REQUEST message but only carried in the RANAP COMMON IDmessage. If CDT_MSG_FULL_TRACE is set to ON, the UE tracing task traces the messagesthat are sent after the RANAP COMMON ID message, and the messages sent before theRANAP COMMON ID message are buffered and reported. If CDT_MSG_FULL_TRACEis set to OFF, the messages sent before the RANAP COMMON ID message are discardedinstead.





7.3.8 Tracing Cell MessagesThis section describes how to trace cell messages. The UE statistics can be reported in the tracingresult if required. The tracing results of the cell messages provide reference for troubleshootingcommon channel faults when the access success rate is low or zero in the cell.

Prerequisite


Context

You can specify a cell by entering Cell ID and specify a message type to be traced by selectinga trace event. The cell message tracing task can be used to trace NBAP common messages onthe Iub interface of a specified cell and to report the UE statistics as required. The cell to betraced must be activated.

NOTE

l A maximum of six cell tracing tasks can be performed simultaneously.

l Each cell tracing task targets only one cell.

l Each cell tracing task targets a maximum of two S-CCPCHs.

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Cell Trace. Accordingly,the Cell Trace dialog box is displayed, as shown in Figure 7-46.



7-59

Figure 7-46 Cell message tracing

Step 3 Set parameters in the Cell Trace dialog box.

l Cell ID: indicates the index of a cell.

l USER_VOLUME/PROPAGATION_DELAY: indicates the event to be traced, includingthe USER_VOLUME event or PROPAGATION_DELAY event. If you select theUSER_VOLUME event, some custom messages reflecting statistics about UEs in a cell willbe reported. The value ranges from 1000 to 10000 with the unit of 10 ms. If you select thePROPAGATION_DELAY event, propagation delay in messages will be reported. Thevalue ranges from 1 to 80 with the unit of times.

l FMR tab page: The following filtering conditions are specified in the FMR tab page.

– Service Data Trace: specifies different types of data report in the area

– SCCPCH ID: specifies the IDs of the SCCPCHs to be traced. You can choose to tracetwo SCCPCHs at the same time by specifying two SCCPCH IDs.

– Report Period: If FP Data Periodic Report or Transport Data Periodic Report isselected in the FMR tab page, Report Period(100ms) needs to be specified.

l You can select messages to be traced on the Iub interface in the IUB tab page.



----End







Figure 7-47 Results of cell message tracing





7.3.9 Tracing IOS MessagesThis section describes how to trace a number of calls that meet the sampling criteria within aspecified range of cells. When creating the task, you can specify the number of calls to be tracedand specify messages to be traced by selecting the event type.

Prerequisite




7-61

ContextAssume that the specified number of continuous calls is N. If N calls are already being traced,the system does not trace any newly accessed calls. If the number becomes less than N becauseof the termination of a traced call, the system automatically traces a new call.

A maximum of six IOS tracing tasks can be performed simultaneously. Each task targets amaximum of 30 calls and 32 cells.

You need to specify the number of successive calls to be traced, tracing cell range, samplingcriteria, and tracing time. The calls that meet the sampling criteria are traced within the specifiedtracing time. When creating a new call tracing task, you can define the sampling criteria bysetting the RAB parameter constraints and the RRC Est Cause. Once the call meets the criteria,the tracing of the call is not stopped even if the RAB parameters of the RRC establishment causeare changed during the call. If the initial settings of the RAB parameters or the RRCestablishment cause value of a call does not meet the criteria, the BSC6900 does not trace thecall even if these parameters are modified to meet the criteria during the call. You can specifythe message types to be traced by selecting the event types. You can also select one or morecells to trace.

CAUTIONThe IOS tracing task involves a large amount of trace information, which affects the systemoperation. Therefore, the maximum number of simultaneously traced calls set in the Max callssimultaneously traced area in the IOS dialog box should not be too high. In addition, you areadvised not to trace all events at a time. Furthermore, you should minimize the frequencies ofperforming this task and the number of tasks performed simultaneously.

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > IOS Trace. Accordingly,the IOS Trace dialog box is displayed, as shown in Figure 7-48.




Figure 7-48 IOS message tracing

Step 3 In the displayed IOS Trace dialog box, set parameters and filter traced messages in other tabpages.l Call Count: indicates the maximum number of calls that can be traced simultaneously after

a tracing task is started. The value ranges from 1 to 30.l Cell ID: You can type the ID of one cell or IDs of multiple cells.l Event Type: indicates types of event to be traced. The event types classify all messages

related to calls. You can select or clear all event types by clicking Select All or Clear All.You can restore the setting to the original one by clicking Reset.

l RAB tab page: RAB parameters are specified in the tab page. If the BSC6900 receives anRAB ASSIGNMENT REQUEST message of a call that matches the specified RABparameters in the specified cell, the call is traced. If a call sets up multiple RAB links, thecall is traced if one of the RAB links meets the specified RAB parameters.

l RRC tab page: The RRC establishment cause is specified in the tab page. If the BSC6900receives an RRC_CONN_REQ message of a call that matches the specified RRCestablishment cause in the specified cell, the call is traced.– RRC(ms): indicates the period of reporting measurement results of PCPICH Ec/No and

Received Signal Code Power (RSCP) when forward power control tracing is selected orPCPICH Ec/No RSCP in the Monitor tab page is selected for IOS tracing



7-63

– UE Internal RRC(ms): indicates the period of reporting measurement results of UEtransmit power when forward power control tracing is selected or UE Tx Power in theMonitor tab page is selected for IOS tracing

– UE Quality RRC(ms): indicates the period of reporting measurement results of downlinkBlock Error Rate (BLER) when forward power control tracing is selected or DownlinkBLER in the Monitor tab page is selected for IOS tracing

– NBAP Common (ms): indicates the period of reporting results of cell commonmeasurement that is selected in the Monitor tab page of IOS Trace

– NBAP Special RRC(ms): indicates the period of reporting measurement results ofdownlink code transmit power in the SRNC cell when forward power control tracing isselected or Downlink Tx Code Power in the Monitor tab page is selected for IOS tracing

– RNSAP Special RRC(ms): indicates the period of reporting measurement results ofdownlink code transmit power in the DRNC cell when forward power control tracing isselected or Downlink Tx Code Power in the Monitor tab page is selected for IOS tracing

– RRC Located Type: indicates the type of location measurement during IOS tracing– RRC Located Cycle(ms): indicates the period of reporting results of location

measurement during IOS tracing– RTT Special NBAP(ms): indicates the period of reporting results of Round Trip Time

(RTT) measurement in the SRNC cell when forward power control tracing is selected orthe Monitor tab page is configured for IOS tracing

– RRC Est Cause: indicates call establishment causes and filters UEs to be traced in thecell based on the call establishment causes

l Monitor tab page: indicates performance counters to be monitored in tracing of a single UE– Uplink SIR: Selecting the counter starts monitoring of uplink Signal to Interference Ratio

(SIR) during tracing of a single UE. The counter is reported periodically. The period ofreporting the monitoring reports ranges from 0.1s to 60s.

– Uplink Tx Power: Selecting the counter starts monitoring of uplink transmit powerduring tracing of a single UE. The counter is reported periodically. The period of reportingthe monitoring reports ranges from 0.25s to 64s.

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

– Downlink Tx Code Power: Selecting the counter starts monitoring of downlink codetransmit power during tracing of a single UE. The counter is reported periodically. Theperiod of reporting the monitoring reports ranges from 0.1s to 60s.

– PCPICH Ec/No RSCP: Selecting the counter starts monitoring of PCPICH Ec/No andReceived Signal Code Power (RSCP) during tracing of a single UE. The counter isreported periodically. The period of reporting the monitoring reports ranges from 0.1s to60s.

– AMR Mode: Selecting the counter starts monitoring of AMR mode during tracing of asingle UE. The counter is reported periodically. If AMR mode changes, the current modeis reported.

– RTWP(0.4s): Selecting the counter starts monitoring of received total wideband power(RTWP) received for the cell serving the current UE. The counter is reported every 0.4second.




– TRX Transmit Power(0.4s): Selecting the counter starts monitoring of downlinktransmit power transmitted for the cell serving the current UE. The counter is reportedevery 0.4 second.



----End




Figure 7-49 Results of IOS message tracing







7-65

7.3.10 Location Report ControlThis section describes how to trace the results of a location tracing initiated by the CN. You canalso perform this task to simulate CN-initiated location tracing and to trace the results of thelocation tracing.


ContextBased on different settings, this task can simulate location tracing in different scenarios.

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Location ReportControl. Accordingly, the Location Report Control dialog box is displayed, as shown inFigure 7-50.




Figure 7-50 Location Report Control

Step 3 Set parameters in the Location Report Control dialog box.

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

l Location Report Control: After it is selected, you can simulate CN-initiated location tracingby setting the parameters: Event, Report Area, Horizontal Accuracy Code, Interval, VerticalAccuracy Code, Response Time Type, Locating Priority, and Client Type.

l Event: indicates the type of event to be traced.

l Report Area: indicates the type of area to be located.

l Horizontal Accuracy Code: indicates the horizontal accuracy requirement for the reportedresult. The value ranges from 0 to 1800000.

l Interval: indicates the interval between two location requests. The value ranges from 0 to1440 with the unit of 10s.



7-67

l Vertical Accuracy Code: indicates the vertical accuracy requirement for the reported result.The value ranges from 0 to 990.

l Response Time Type: indicates the response time type of the location protection timer.l Locating Priority: indicates the priority of the UE to be located.l Client Type: indicates the type of service that requests location or purpose of requesting

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


----End




Figure 7-51 Results of Location Report Control

NOTE

l Right-click on the Location Monitor Info tab page, and then choose Save as Excel to savethe location results as an Excel file.

l The Location Time Delay Info tab page reflects the variation of the location delay in listand in chart.

l Right-click in the chart on the Location Time Delay Info tab page, and then choose Set Yaxis display range to adjust the display range of the Y coordinate axis.




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




7.4.1 Browsing Traced Messages OnlineThis section describes how to browse the traced messages online in the message browse windowafter the tracing task is created.

7.4.2 Viewing the Interpretation of the Trace MessageThis section describes how to view the interpretation of a trace message.

7.4.3 Saving Traced MessagesThis section describes how to save the trace message file to the local computer.

7.4.4 Browsing Traced Messages OfflineThis section describes how to use the Traffic Recording Review Tool to browse offline, thetraced messages that are saved in .tmf format.

7.4.5 Managing Tracing TasksThis section describes how to manage tracing tasks.

7.4.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.4.1 Browsing Traced Messages OnlineThis section describes how to browse the traced messages online in the message browse windowafter the 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.

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 out of the browsewindow without affecting the saving of the messages.

Property Query the task properties.



7-69

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.4.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.4.3 Saving Traced MessagesThis section describes how to save the trace message file to the local computer.

Prerequisitel A tracing task is started.

l Trace messages are reported.

Context

The length of the name(including the extension) of the file storing the tracing results cannotexceed 100 characters.

There are two ways of saving tracing results: auto saving and manual saving.

Procedurel Automatically saving the trace messages

If Save File is selected when a tracing task is created, all messages are displayed in themessage browse window in .tmf format by default.

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 offline the messages saved in .tmfformat. For details, see 7.4.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.4.4 Browsing Traced Messages OfflineThis section describes how to use the Traffic Recording Review Tool to browse offline, thetraced messages that are saved in .tmf format.

PrerequisiteThe traced messages are saved in .tmf format.

ContextYou can find the .txt or .csv files in the saved 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.

Step 3 Click Open or double-click the file. The contents of the file are displayed in the TrafficRecording Review Tool window.

NOTE

The time format is YYYY-MM-DD HH:MM:SS(Tick). The unit of Tick is 10 ms.

Step 4 Browse the messages or double-click a specific one to read the details.



7-71

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 By Byte from the shortcutmenu,

Set the filter to selectively display theinformation.

You choose Filter By Column from theshortcut menu,

Filter the information by column toselectively display the information.

You choose Find from the shortcut menu, Locate the message that you want.

----End

7.4.5 Managing Tracing TasksThis section describes how to manage tracing tasks.

Prerequisitel A tracing task is successfully created.l Trace messages are reported.


1. Click Trace on the LMT main page. The Trace tab page is displayed.2. On the Trace Navigation Tree pane, choose the Manage Trace Task. The Manage

Trace Task dialog box is displayed.3. In the displayed Manage Trace Task tab page, set the parameters as required, and

click Query to query the information about the trace tasks.4. To stop, restart, or delete a trace task, select the target task listed in the Result area,

and then click Stop, Restart, or Delete.NOTE

l The tasks whose Trace Mode is Report Messages listed in the query result can only bedeleted on the 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.4.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, choose the Manage Trace File node. The Manage TraceFile dialog box is displayed.

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



7-73

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 UMTS MonitoringThis section describes the performance monitoring of the UMTS 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 UMTSLMT 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 section describes the principles of real-time performance monitoring, including themonitoring of the 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 on the BSC6900.

8.1.1 Monitoring PrinciplesThis section describes the principles of real-time performance monitoring, including themonitoring of the CPU usage and other real-time performances.

Principles of CPU Usage Monitoring

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

Figure 8-1 CPU usage monitoring

The internal procedure of monitoring the CPU usage is as follows:

1. When you create a task for monitoring the CPU usage on the LMT, the LMT sends a 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 UMTSLMT User Guide



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 on the BSC6900.

Operators of the following levels can perform real-time performance monitoring of the BSC: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 real-time monitoring.



8-3

NOTE

Group G_10 consists of binary commands used for tracing and monitoring.

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 section describes how to monitor the transmission resources on the Iub interface.

8.2.3 Monitoring BER SecondsThis section describes how to detect the BER seconds on an E1/T1 port to monitor thetransmission quality of the link corresponding to the port. If any bit error occurs on the E1/T1port, you can start this task to obtain data such as Errored Second, Severely Errored Second,Unavailable Second, Frame Errors, CRC Errors. Based on these data, you can evaluate theoperating condition of the transmission network and find out the causes for the bit errors incombination with the performance of the peer end. The AEUa/PEUa/AOUc/POUc boardsupports this function.

8.2.4 Monitoring BERThis section describes how to monitor bit error rate (BER), thereby evaluating transport networkquality.

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

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 section describes how to monitor the transmission resources on the Iub interface.


l The board under monitoring is functional.

Procedure


Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > TransportResource RealTime monitoring. The Transport Resource RealTime monitoring dialog boxis displayed.

Step 3 In the 8.5 Reference for Performance Monitoring dialog box, set the parameters as required,and click Submit.

NOTE


----End

8.2.3 Monitoring BER SecondsThis section describes how to detect the BER seconds on an E1/T1 port to monitor thetransmission quality of the link corresponding to the port. If any bit error occurs on the E1/T1port, you can start this task to obtain data such as Errored Second, Severely Errored Second,Unavailable Second, Frame Errors, CRC Errors. Based on these data, you can evaluate theoperating condition of the transmission network and find out the causes for the bit errors incombination with the performance of the peer end. The AEUa/PEUa/AOUc/POUc boardsupports this function.


l The board under monitoring is functional.



8-5

Procedure


Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > BERSMonitoring. The BERS Monitoring dialog box is displayed.

Step 3 In the displayed BERS Monitoring dialog box, set the parameters as required, and clickSubmit.

NOTE


----End

8.2.4 Monitoring BERThis section describes how to monitor bit error rate (BER), thereby evaluating transport networkquality.


Contextl Using this function disrupts transmission of an IMA group, UNI link, fractional ATM link,

fractional IMA link, MP group, or PPP link carried on a board. Services carried on thecorresponding port are thus affected.

l Before starting BER monitoring, you need to configure local loopback at the local end orconfigure remote loopback at the peer end. Or you can connect the transmitting end to thereceiving end using a loopback connector.

l BER monitoring and a loopback test cannot be performed simultaneously.

l Only one BER monitoring task can be started for one board at a time.

l You must set E1/T1 port loopback before starting BER monitoring of an E1/T1 port andtimeslot-level testing.

Procedure

Step 1 Click Monitor in the LMT home page. Accordingly, the Monitor tab page is displayed.

Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > BERMonitoring. Accordingly, the BER Monitoring dialog box is displayed.

Step 3 In the displayed BER Monitoring dialog box, set the parameters as required, and clickSubmit.

NOTE

After the monitoring task is started, a monitoring window is displayed, showing the real-time monitoring resultby list or chart. The task name and related parameters are displayed on the title bar of the window.

----End




8.2.5 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 the IMA Group TrafficThis section describes how to monitor the traffic on a specified IMA group in real time. Thereal-time traffic on the specified IMA group is displayed in the form of list and chart. Based onthe statistics from the two ends of the IMA group, you can confirm the IE loss, locate the fault,and evaluate the network transmission quality. You can also compare the actual traffic volumewith the user volume and obtain the utilization of the port. In addition, you can evaluate thebandwidth condition and decide whether to add a link to the IMA group for capacity expansion.


Context

CAUTIONThe IMA group must be successfully set up and connected to the peer end before this task isperformed. This task is stopped if the monitored IMA group is deleted.

Procedure


Step 2 On the Monitor Navigation Tree pane, choose Monitor > Common Monitoring > LinkPerformance Monitoring. The Link Performance Monitoring dialog box is displayed.

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

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.In the chart, the X coordinate represents the hour: minute: second. The Y coordinate represents the RX and TXtraffic in bit/s.

----End

Monitoring the UNI Link TrafficThis section describes how to monitor the traffic on a specified UNI link in real time. The real-time traffic on the specified UNI link is displayed in the form of list and chart. Based on thestatistics from the two ends of the UNI link, you can confirm the IE loss, locate the fault, andevaluate the network transmission quality. You can also compare the actual traffic volume withthe user volume and obtain the utilization of the port. In addition, you can evaluate the bandwidthcondition and decide whether to modify the UNI to IMA.



8-7


Context

CAUTIONThe UNI 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.

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


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


----End

Monitoring the Fractional ATM Link TrafficThis section describes how to monitor the traffic on a specified fractional ATM link in real time.The real-time traffic on the specified fractional ATM link is displayed in the form of list andchart. Based on statistics obtained from two ends of the fractional ATM link, you can confirmthe IE loss, locate the fault, and evaluate the network transmission quality. You can also comparethe actual traffic volume with the user volume carried by the current port and obtain the utilizationof the port. In addition, you can evaluate the bandwidth condition and decide whether to modifythe FRAC ATM to IMA to expand the bandwidth.


Context

CAUTIONThe FRAC ATM link must be successfully set up and connected to the peer end before this taskis performed. This task is stopped if the monitored link is deleted.




Procedure




NOTE

After the monitoring task is started, a monitoring window is displayed, showing real-time monitoring results inlist and chart. The task name and related parameters are indicated in the title bar of the window.

In the chart, the X coordinate represents the hour: minute: second. The Y coordinate represents the RX and TXtraffic in bit/s.

----End

Monitoring the SAAL Link Traffic

This section describes how to monitor the traffic on a specified SAAL path at the IP layer of theinterface board in real time. The real-time traffic on the specified SAAL path is displayed in theform of list and chart. Based on the transmit/receive statistics on the SAAL of the CPUSsubsystem, you can confirm the packet loss, locate the SAAL disconnection or intermittenceproblem. You can also predict the congestion by comparing the traffic with the configuredbandwidth.

Prerequisite


Context

CAUTIONThe SAAL 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



----End

Monitoring the IPoA PVC TrafficThis section describes how to monitor the traffic on a specified IPOA PVC at the IP layer of aninterface board in real time. The real-time traffic on the specified IPOA PVC is displayed in theform of list and chart. If the IPOA PVC carries the OML for the ATM-based BTS, you canperform this task to observe the traffic and bandwidth utilization when the NodeB is loadingdata and to locate the fault in the NodeB startup and data loading processes. If the IPOA PVCcarries the IP path over the Iu-PS interface, you can perform this function to observe the trafficflow and locate the connection and congestion status of the upper layer link.


Context

CAUTIONThe IPoA PVC 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 the AAL2 Path TrafficThis section describes how to monitor the traffic on a specified AAL2 path at the IP layer of theinterface board in real time. The real-time traffic on the specified AAL2 path is displayed in the




form of list and chart. Based on the layer 2 transmit/receive statistics obtained from the CDTtrace, you can confirm the packet loss and evaluate the traffic condition. In addition, you canpredict the congestion based on the traffic conditions on the link.

Prerequisite


Context

CAUTIONThe AAL2 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




NOTE



----End

Monitoring FE/GE Traffic

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

Prerequisite




8-11

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




NOTE

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

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 section describes how to monitor the traffic on a specified MLPPP link group in real time.The real-time traffic on the specified MLPPP link group is displayed in the form of list and chart.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.

Prerequisite


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






8-13

NOTE


----End

Monitoring the SCTP Link TrafficThis section describes how to monitor the traffic on a specified SCTP path at the IP layer of theinterface board in real time. The real-time traffic on the specified SCTP path is displayed in theform of list and chart. Based on the transmit/receive statistics on the SCTP of the CPUSsubsystem, you can confirm the packet loss, locate the SCTP disconnection or intermittenceproblem. 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.




NOTE

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.In the chart, the X coordinate represents the hour: minute: second. The Y coordinate represents the RX and TXtraffic in kbit/s.

----End

Monitoring the IP Path TrafficThis section describes how to monitor the traffic on a specified IP path at the IP layer of theinterface board in real time. The real-time traffic on the specified IP path is displayed in the formof list and chart. Based on the layer 2 statistics obtained from the CDT trace, you can confirmthe packet loss and evaluate the user data flow conditions. In addition, you can predict thecongestion based on the traffic conditions on the link.





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




NOTE



----End

Monitoring Traffic on a Logical PortThis 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.


Procedure





8-15


NOTE


In the chart, the X coordinate represents the hour: minute: second. The Y coordinate represents the real-timetraffic of the current logical port in bit/s.

----End

Monitoring OAM Traffic

This section describes how to monitor the RX and TX traffic on the operation and maintenance(OAM) channel at the IP layer of an interface board in a specified NodeB. The OAM traffic onthe current NodeB is displayed in the form of list and chart. You can perform this task to observethe traffic and bandwidth usage when the NodeB is loading data. Thus, you can locate the faultin the NodeB startup and data loading processes.

Prerequisitel The LMT is running normally.

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

Procedure




NOTE


In the chart, the X coordinate represents the hour: minute: second. The Y coordinate represents the RX and TXtraffic of the NodeB OM channel in bit/s.

----End

Monitoring the Bandwidth of a Logical Port

This section describes how to monitor the bandwidth changes on a logical port after the 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





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 hour: minute: second. The Y coordinate represents the bandwidthin bit/s.

----End

Monitoring Traffic on Non-Channelized Optical ATM PortThis section describes how to monitor the traffic on a specified non-channelized ATM opticalport in real time. The real-time traffic on this port is displayed in the form of list and chart. Basedon the statistics on the non-channelized ATM optical ports at both ends, you can check the IEloss, locate the fault, and evaluate the network transmission quality. You can also compare theactual traffic volume with the user volume and obtain the utilization of the port. In addition, youcan evaluate the bandwidth condition and decide whether capacity expansion is required.


Context

CAUTIONThe specified non-channelized ATM optical port is connected to the peer end.

Procedure






8-17

NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms), and the Y coordinate representsthe RX and TX traffic in the unit of bit/s.

----End

Monitoring the IPPM TrafficThis section describes how to monitor the traffic on a specified IPPM link in real time. The real-time traffic on the specified IPPM link is displayed in the form of list and chart. Together withthe statistics at both ends of the IPPM link, the function can be used to confirm the packet loss,and locate the IPPM disconnection or intermittence problem. The function can also be used topredict the congestion based on the traffic conditions on the link.


Context

CAUTIONThe IPPM link to be monitored is activated.

Procedure


Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > LinkPerformance Monitoring. The Link Performance Monitoring dialog box is displayed.

Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPM. Set otherparameters as required, and then click Submit.

NOTE


In the chart, the X coordinate represents the time; the Y coordinate represents the monitoring results in such aunit as bps or pps, depending on the report result.

----End

Monitoring the Trunk GroupThis section describes how to monitor the traffic on a specified trunk group in real time. Thereal-time traffic on the specified trunk group is displayed in the form of list and chart. Togetherwith the statistics at both ends of the trunk group, the function can be used to confirm the IEloss, help locate the fault, and evaluate the transmission network quality. The function can bealso used to compare the actual traffic volume with the user volume and obtain the utilization




of the port. In addition, the function can be used to evaluate the bandwidth condition and decidewhether to add a link to the trunk group for capacity expansion.

Prerequisite


Context

CAUTIONThe trunk group to be monitored is configured successfully.

Procedure


Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > LinkPerformance Monitoring. The Link Performance Monitoring dialog box is displayed.

Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to TRUNKGroup. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X coordinate represents the time; the Y coordinate represents the monitoring results in such aunit as bps or pps, depending on the report result.

----End

8.3 UMTS MonitoringThis section describes the performance monitoring of the UMTS services.

8.3.1 Monitoring Connection PerformanceThis section describes how to monitor the performance of the physical connections of the UEduring a conversation. A maximum of six monitoring tasks can be performed simultaneouslyfor each monitoring item.

8.3.2 Monitoring Cell PerformanceThis section describes how to monitor the cell performance, such as the common measurementstatistics and number of UEs on the common channel. For the same monitoring item, you canstart a maximum of six tasks simultaneously.

8.3.3 Monitoring Board ResourcesThis section describes how to monitor the licensed Erlang value and the PS user plane throughputof a specified board in real time.



8-19

8.3.1 Monitoring Connection PerformanceThis section describes how to monitor the performance of the physical connections of the UEduring a conversation. A maximum of six monitoring tasks can be performed simultaneouslyfor each monitoring item.

Monitoring P-CPICH Ec/No and RSCP

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

Prerequisite


Context

CAUTIONBefore running this monitoring task, you need to perform one of the following operations:

l Run SET UCORRMALGOSWITCH to set Handover algorithm switch. Ensure thatSOFT_HANDOVER_SWITCH is selected.

l Run MOD UCELLMEAS to set Intra-freq Meas Ctrl Info Ind to REQUIRE.

NOTE

l This task applies to only monitoring connections established on dedicated channels. An ongoing taskis stopped if the monitored connection is released or transited from the dedicated channel to the commonchannel. The task is restarted if the monitored connection is transited from the common channel backto the dedicated channel.

l This task is performed to monitor only the real-time data of the cells in the active set. The data of othercells is not reported. Therefore, the monitoring results reflect the variation of the number of cells inthe active set in real time.

l A maximum of three cells in the active set can be monitored in each task.

Procedure


Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > ConnectionPerformance Monitoring. The Connection Performance Monitoring dialog box is displayed.

Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to P-CPICH Ec/No and RSCP. Set other parameters as required, and then click Submit.




NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.

In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported P-CPICH Ec/No (unit: dB) and RSCP (unit: dBm).

l RSCP stands for Received Signal Code Power. It is the received power on one code measured on the P-CPICH. The reference point for measurement of the RSCP is at the antenna connector of the UE. If the P-CPICH uses transmit diversity, you need to measure the RSCP of each antenna and sum up all of the RSCPvalues. Then you can obtain the total RSCP of the P-CPICH.

l Ec/No refers to the ratio of received energy per chip to noise spectral density. Like RSCP/RSSI, Ec/No isalso measured on the P-CPICH. The reference point for measurement is also at the antenna connector of theUE. If the P-CPICH adopts transmit diversity, the total Ec value of all antennas must be measured to calculatethe Ec/No.

----End

Monitoring SIR of the Uplink RLSThis section describes how to monitor in real time the SIR values of the uplink radio link sets(RLSs) used by the UE. By performing this task, you can learn about the uplink radio link qualityand the quality variations.


ContextNOTE

Each task can monitor only one UE. The monitoring result includes the number of cells in the active setand the signal strength of each cell. From the monitoring result, you can know whether the currentconnection is at the edge or the center of the cell.

Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to ULSIR. Set other parameters as required, and then click Submit.



8-21

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window. The monitoring results reflect the variation of the numberof the RLSs in real time.

In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reportedSIR of the UL RLSs (unit: dB).

The calculation formula of SIR is (RSCP/ISCP) x SF, where:

l RSCP stands for Received Signal Code Power. It is the received power on one code.

l ISCP stands for Interference Signal Code Power. Only the non-orthogonal part of received interferencesignals is measured.

l SF stands for the spreading factor of the DPCCH.

The measurement is performed on the DPCCH selected after radio links are combined on the NodeB. Incompressed mode, the SIR during the transmit intervals is not measured. The NodeB reports the measured SIRvalues on the uplink to the BSC6900.

----End

Monitoring the Enhanced Outer Loop Power Control

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

Prerequisite


Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item toOLPC. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. Two small charts are respectively used todescribe the five monitoring items.

l The first small chart shows the output interface of the SIR target values of the UL RLSs, BLER of the ULtransport channel, and BER of the UL physical channel. The left Y-coordinate represents the SIR targetvalues of the UL RLSs (range: -10 to 18, unit: dB). The right Y-coordinate represents the BLER of the ULtransport channel (range: 0 to 1, unit: BLER) and BER of the UL physical channel (range: 0 to 1, unit: BER).

l The second small chart shows the output interface of the E-DCH average times of retransmission and E-DCH retransmission probability. The left Y-coordinate represents the E-DCH average times ofretransmission (range: 0 to 16, unit: none). The right Y-coordinate represents the E-DCH retransmissionprobability (range: 0 to 1, unit: none).

----End




Monitoring the SIR Error Values of UL RLSs

This section describes how to monitor the real-time SIR error values of radio link sets (RLSs)of the current connection. By performing this task, you can observe whether the SIR can keepup with the variation of the target values and estimate the UL inner loop power control function.If the SIR error values vary all the time but converge around 0 dB, you can infer that the ULinner loop power control converges. Otherwise, the UL inner loop power control does notconverge.

Prerequisite


Context

This task applies to only monitoring connections established on dedicated channels. An ongoingtask is stopped if the monitored connection is released or transited from the dedicated channelto the common channel. The task is restarted if the monitored connection is transited from thecommon channel back to the dedicated channel.

Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to ULSIR Error. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window. The monitoring results reflect the variation of the numberof the RLSs in real time.

In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reportedSIR error values (SIRerror) of the UL RLSs.

l SIRerror (unit: dB) is reported to the BSC6900 by the NodeB. The calculation formula is SIRerror = SIR -SIRtarget_ave.

l Where, SIRtarget_ave represents the average of SIRtarget within a period that is equal to the time for calculatingthe SIR in the above formula of SIRerror.

l In compressed mode, SIRtarget equals to SIRcm_target. The SIRtarget_ave in the transmission gap is notcalculated. The average of SIRtarget is an arithmetical average. The unit of SIRtarget_ave is dB.

----End

Monitoring DL Code TX Power

This section describes how to monitor the variation of the DL code TX power of each radio linkof the current connection in real time. By performing this task, you can analyze the DL powerconsumption. If the DL code TX power increases, even approximately up to the maximum valueconfigured in the signaling message, it indicates that the link experiences a degraded quality.



8-23


ContextThis task applies to only monitoring connections established on dedicated channels. An ongoingtask is stopped if the monitored connection is released or transited from the dedicated channelto the common channel. The task is restarted if the monitored connection is transited from thecommon channel back to the dedicated channel.



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to DLTx Code Power. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window. The monitoring results reflect the variation of the numberof the radio links involved in the current connection in real time.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported DLcode TX power (unit: dBm).Code TX power refers to the NodeB TX power on one channelization code that is on one given scrambling codeon one given carrier. The DL code TX power can be measured on the DPCCH of any radio link outgoing fromthe UTRAN and indicates the pilot bit power of the DPCCH.In compressed mode, the TX power measurement should cover all timeslots, including those during the transmitintervals. The reference point for measurement is at the antenna connector. If transmit diversity is adopted, theDL code TX power is the total of the code TX powers of all antennas.

----End

Monitoring the UE TX PowerThis section describes how to monitor in real time the variation of the UE TX power on thecurrent connection. By performing this task, you can analyze the UL quality of the radio link.If the UE TX power increases, even reaching the limit of the UE capability, you can infer thatthe radio link experiences a degraded UL quality.


ContextUE TX power refers to the UE TX power in a carrier. The reference point for measurement ofthe UE TX power is at the antenna connector of the UE.





Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to UETx Power. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported UETX power (unit: dBm).

----End

Monitoring UL TrafficThis section describes how to monitor in real time the variation in the UL traffic (that is, thebuffered data volume at the UE side) on the current connection. By performing this task, youcan analyze the transmission performance of UL traffic. The UL traffic is measured by the UEand reported to the BSC6900 on the basis of the transport channel.


ContextTraffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to betransmitted or retransmitted from the RLC entity on each logical channel. If RLC is in AM mode,the BO value includes the control Protocol Data Unit (PDU) and the PDU outside the transmitwindow, excluding the PDUs for which no ACK is received.

This task can monitor the connections of PS domain interactive and background services on bothcommon channels and dedicated channels.

Procedure



Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to UL Traffic. Setother parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported ULtraffic on the UL physical channel (unit: byte).

----End



8-25

Monitoring DL TrafficThis section describes how to monitor in real time the variation in the DL traffic (that is, thebuffered data volume on the MSC side) on the current connection. By performing this task, youcan analyze the transmission performance of DL traffic. The DL traffic is measured at theBSC6900 on the basis of transport channel.


ContextTraffic volume refers to the Buffer Occupy (BO) value. BO is the number of data bytes to betransmitted or retransmitted from the RLC entity on each logical channel. If RLC is inacknowledgment mode, the BO value includes the control Protocol Data Unit (PDU) and thePDU outside the transmit window, excluding the PDUs for which no ACK is received.


Procedure



Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to DL Traffic. Setother parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported DLtraffic (unit: byte).

----End

Monitoring UL Throughput and BandwidthThis section describes how to monitor in real time the rate variations on the UL transport accessstratum and non-access stratum of the current connection. By performing this task, you cananalyze the function of dynamic channel configuration and characteristics of the service sourcerate variations.


ContextThroughput refers to the amount of data transmitted on a transport channel in a unit of time.Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculatedaccording to RLC payload. The bandwidth changes in RB reconfiguration. The throughput




measurement involves RLC headers, and therefore, the measured peak throughput is higher thanthe bandwidth.


Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to ULThroughput & Bandwidth. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported ULthroughput and UL bandwidth (unit: bit/s).

l If the UL bandwidth varies with the UL throughput, you can infer that the dynamic channel configurationfunction is normal.

l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristicsof UL service source by observing the variation of UL throughput.

----End

Monitoring DL Throughput and Bandwidth

This section describes how to monitor in real time the rate variations on the DL transport accessstratum and non-access stratum of the current connection. By performing this task, you cananalyze the function of dynamic channel configuration and characteristics of the service sourcerate variations.

Prerequisite


Context

Throughput refers to the amount of data transmitted on a transport channel in a unit of time.Throughput is measured on the MAC-d. Bandwidth refers to the maximum rate calculatedaccording to RLC payload. The bandwidth changes in RB reconfiguration. The throughputmeasurement involves RLC headers, and therefore, the measured peak throughput is higher thanthe bandwidth.


Procedure




8-27


Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to DLThroughput & Bandwidth. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reported DLthroughput and DL bandwidth (unit: bit/s).

l If the DL bandwidth increases/decreases with the increase/decrease of DL throughput, you can infer thatthe dynamic channel configuration function is normal.

l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristicsof DL service source by observing the variation of DL throughput.

----End

Monitoring Handover Delay

This section describes how to monitor the handover delay performance. By performing this task,you can observe and obtain the time taken by each handover (including the intra-frequencyhandover and inter-frequency handover) of the current connection.

Prerequisite


Context

Handover delay refers to the period during which the BSC6900 receives a measurement report,the handover decision is made, the handover is initiated, and the handover is completed.


At most five handover delay monitoring tasks can be started simultaneously. This task canmonitor only intra-frequency handover and inter-frequency handover but cannot monitor inter-RAT handover.

Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item toHandover Delay. Set other parameters as required, and then click Submit.




NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X coordinate represents the hour: minute: second. The Y-coordinate represents the interval ofeach successful handover (unit: ms).

----End

Monitoring the BLER of the DL Transport ChannelThis section describes how to monitor in real time the variation in the BLER values measuredon all transport channels of the current connection. By performing this task, you can analyze theDL quality of the radio link. If the BLER of the DL transport channel increases, you can inferthat the DL quality declines. If the BLER decreases, you can infer that the DL quality is improved.


ContextThe BLER of the DL transport channel is measured at the UE. The BLER is used for outer looppower control.


Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to DLBLER. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window. The monitoring results reflect the variation of the numberof traffic transport channels in real time. The number of signaling transport channels is always 1.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the reportedBLER of the DL transport channel (unit: %).

----End

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




8-29

Context

The monitoring is valid only when the traced UE has an AMR service in process.

The narrowband AMR has eight available rates, that is, eight available modes: 12.2 kbit/s, 10.2kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s.

The wideband AMR has nine available rates, that is, nine available modes: 23.85 kbit/s, 23.05kbit/s, 19.85 kbit/s, 18.25 kbit/s, 15.85 kbit/s, 14.25 kbit/s, 12.65 kbit/s, 8.85 kbit/s, and 6.60kbit/s.

Procedure



Step 3 In the displayed Connection Performance Monitoring dialog box, set Monitor Item to AMRMode. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X coordinate represents the hour: minute: second. The Y-coordinate represents the maximumAMR rate in the uplink and downlink (unit: kbit/s).

----End

8.3.2 Monitoring Cell PerformanceThis section describes how to monitor the cell performance, such as the common measurementstatistics and number of UEs on the common channel. For the same monitoring item, you canstart a maximum of six tasks simultaneously.

Monitoring Cell P-CPICH TX Power

The monitoring is performed on the PCPICH TX power of a specified cell. By performing thistask, you can observe and judge in real time whether the pilot power is normal.

Prerequisite


Context

The value range of the P-CPICH TX power can be obtained by running the LST UPCPICHcommand. If the pilot power is outside the range, you can infer that the power is abnormal.

Procedure





Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > CellPerformance Monitoring. The Cell Performance Monitoring dialog box is displayed.

Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to PCPICHTxPower. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the P-CPICHpower (unit: dBm).

----End

Monitoring UL RX Total Wideband Power of a CellThis section describes how to monitor the UL RX total wideband power (RTWP) in a specifiedcell. By performing this task, you can observe the UL load level in real time. The UL RX totalwideband power is measured and reported by the related NodeB.


ContextThe CAC procedure measures the UL load by the UL load factor (UL load factor = 1 - cellbackground noise/UL RX total wideband power). The background noise of the cell approximatesto a constant, which can be set through the command ADD UCELLCAC or MODUCELLCAC. Therefore, the UL RX total wideband power can also be used to measure therelative level of the UL load of the cell.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to RTWP. Setother parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents thehour: minute: second. The Y-coordinate represents the cell UL RXtotal wideband power (unit: dBm).

----End

Monitoring DL TX Power in a CellThis section describes how to monitor the DL transmit (TX) power of a specified cell. Byperforming this task, you can observe the DL load level in real time. The DL TX power of a cellis measured and reported by the related NodeB.



8-31


ContextThe CAC procedure uses the ratio of the DL carrier TX power to the maximum TX power ofthe cell to measure the DL load of the cell. When setting up a cell, you can run ADDUCELLSETUP to set the maximum TX power. After the cell is set up, you can run MODUCELL to modify it.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell DLCarrier TX Power. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ratio of theDL TX carrier power to the maximum TX power of the cell (unit: %).

----End

Monitoring User Volume in CellThis section describes how to monitor in real time the number of users on the common channel,dedicated channel, HSDPA channel, and HSUPA channel in a specified cell. You can also learnabout the distribution of the users in the cell.


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell UserNumber. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the number ofcell users.

----End




Monitoring Node Synchronization

This section describes how to monitor the time difference between RNC Frame Number (RFN)and NodeB Frame Number (BFN) of the specified cell and the time taken for nodesynchronization. By performing this task, you can observe the float between the RFN and BFNin real time. If the difference between RFN and BFN varies too rapidly, you can infer that thereare some problems on the transmission between the BSC6900 and the NodeB.

Prerequisite


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Node Sync.Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the timedifference between RFN and BFN and the time taken by the NodeB to finish node synchronization (unit: ms).

----End

Monitoring UL CAC

This section describes how to monitor the UL Call Admission Control (CAC) procedure of aspecified cell. By performing this task, you can observe the variation in the predicted values andmeasured values of the UL load and judge the prediction accuracy of the UL CAC algorithm.

Prerequisite


Context

The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CACalgorithm 2). Run MOD UCELLALGOSWITCH to set the UL CAC algorithm of a cell. RunLST UCELLALGOSWITCH to query the UL CAC algorithm of a cell.

l CAC algorithm 1 measures the UL load by the UL load factor (UL load factor = 1 - cellbackground noise/UL RX total wideband power). You can run the command ADDUCELLCAC or MOD UCELLCAC to set the cell background noise.

l CAC algorithm 2 uses the ratio of the current number to the maximum number of ULequivalent users to measure the load of the cell. By default, algorithm 2 is used to measurethe UL load of the cell.



8-33

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to UL CAC. Setother parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predictedvalues and measured values of the load (unit: %).

----End

Monitoring DL CAC

This section describes how to monitor the DL Call Admission Control (CAC) procedure of aspecified cell. By performing this task, you can observe the variation of the predicted values andmeasured values of the DL load and judge the prediction accuracy of the DL CAC algorithm.

Prerequisite


Context

The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CACalgorithm 2). Run MOD UCELLALGOSWITCH to set the UL CAC algorithm of a cell. RunLST UCELLALGOSWITCH to query the UL CAC algorithm of a cell.

l CAC algorithm 1 uses the ratio of the DL carrier TX power to the maximum TX power ofthe cell to measure the DL load of the cell. By default, algorithm 1 is used to measure theDL load of the cell. The maximum TX power is a constant. You can run ADDUCELLSETUP to set it.

l CAC algorithm 2 uses the ratio of the current DL equivalent number of users to themaximum DL equivalent number of users.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL CAC. Setother parameters as required, and then click Submit.




NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predictedvalues and measured values of the load (unit: %).

----End

Monitoring the Number of UL Equivalent Users

This section describes how to monitor the number of UL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of UL equivalent users.

Prerequisite


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to UL TotalEquivalent User Number. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predictedvalues and measured values of the number of UL equivalent users.

----End

Monitoring the Number of DL Equivalent Users

This section describes how to monitor the number of DL equivalent users in a specified cell. Byperforming this task, you can observe the variation in the number of DL equivalent users.

Prerequisite


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to DL TotalEquivalent User Number. Set other parameters as required, and then click Submit.



8-35

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the predictedvalues and measured values of the number of DL equivalent users.

----End

Monitoring the Cell Code Tree

This section describes how to monitor the DL channel OVSF code tree of a specified cell. Byperforming this task, you can observe the code usage in real time.

Prerequisite


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to Cell CodeTree. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in chart. The task name is indicatedin the title bar of the window.

In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the codes.

----End

Monitoring the Minimum Required Power of the HS-DSCH

This section describes how to monitor in real time the minimum required power of the HS-DSCHof a specified cell. By performing this task, you can observe the ratio of the minimum requiredpower to the maximum TX power on the HS-DSCH in the cell.

Prerequisite


Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCHMin Power Requirement. Set other parameters as required, and then click Submit.




NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ratio of therequired power to the maximum TX power of the cell (unit: ‰).

----End

Monitoring the Bit Rate Provided by the HS-DSCHThis section describes how to monitor the bit rate on the HS-DSCH of a specified cell. Byperforming this task, you can observe the variation in the transmission rate on the HS-DSCH inreal time.


ContextNOTE

Before performing the bit rate monitoring on the HS-DSCH, ensure that the HSDPA_PBR_MEAS of thecell is selected (that is, set to 1). Otherwise, "Measurement not available" is displayed when you create themeasurement task.Run the LST UCELLALGOSWITCH command on the MML client to query the state ofHSDPA_PBR_MEAS switch. If the queried result is HSDPA PBR MEAS ALGORITHM:OFF, run theMOD UCELLALGOSWITCH command to set it to 1.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to HS-DSCHProvide Bitrate. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in the form of list and chart. Thetask name is indicated in the title bar of the window.In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:bit/s).

----End

Monitoring the Bit Rate Provided by the E-DCHThis section describes how to monitor the bit rate on the enhanced dedicated channel (E-DCH)for HSUPA services. By performing this task, you can observe the variation in the transmissionrate on the E-DCH in real time.




8-37

ContextNOTE

Before performing the bit rate monitoring on the E-DCH, ensure that the HSUPA_PBR_MEAS of the cellis switched on (that is, set to 1). Otherwise, "Measurement not available" is displayed when you create themeasurement task.

Run the LST UCELLALGOSWITCH command query the state of HSUPA_PBR_MEAS switch. If thequeried result is HSUPA PBR MEAS ALGORITHM:OFF, run the MOD UCELLALGOSWITCHcommand to set it to ON.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to E-DCHProvide Bitrate. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the bit rate (unit:bit/s).

----End

Monitoring UL Throughput of a Cell

This section describes how to monitor the UL throughput of a cell. Throughput refers to themaximum traffic rate that an entity can endure without discarding the frames.

Prerequisite


Procedure



Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell ULThroughput. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the ULthroughput of the cell.

----End




Monitoring DL Throughput of a Cell

This section describes how to monitor the DL throughput of a cell. Throughput refers to themaximum traffic rate that an entity can endure without discarding the frames.

Prerequisite


Procedure



Step 3 In the Connection Performance Monitoring dialog box, set Monitor Item to Cell DLThroughput. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the DLthroughput of the cell.

----End

Monitoring Cell CE

This section describes how to monitor the channel element (CE) conditions of the local cell, thelocal cell group, and the corresponding NodeB. Based on the monitoring result, the BSC6900determines whether a UE can access the network.

Prerequisite


Procedure



Step 3 In the Cell Performance Monitoring dialog box, set Monitor Item to Cell CE. Set otherparameters as required, and then click Submit.

NOTE


In the chart, the X-coordinate represents the hour: minute: second. The Y-coordinate represents the number ofCEs of the cell.

----End



8-39

Monitoring the FDPCH SYMBOLThis section describes how to monitor the condition of the F-DPCH SYMBOL, including theF-DPCH code, SYMBOL No., and timeslot format corresponding to the occupied SYMBOL.


ContextThe F-DPCH carries the Transport Power Control (TPC) information of HSDPA services anduses the spreading factor SF256.

Procedure



Step 3 In the displayed Cell Performance Monitoring dialog box, set Monitor Item to FDPCHSYMBOL. Set other parameters as required, and then click Submit.

NOTE

A monitoring window is displayed, showing the real-time monitoring results in chart. The task name is indicatedin the title bar of the window.

l In the static view of the FDPCH SYMBOL monitoring, you can view the condition of the SYMBOLcorresponding to the F-DPCH code. The numbers in the grids indicate the timeslot formats.

l In the dynamic view of the FDPCH SYMBOL monitoring, the X-coordinate represents the time, and the Y-coordinate represents the F-DPCH code, position of the F-DPCH SYMBOL, and timeslot format.

----End

8.3.3 Monitoring Board ResourcesThis section describes how to monitor the licensed Erlang value and the PS user plane throughputof a specified board in real time.


ContextNOTE

l This task can be performed only through menu operations and applies to only the boards that are inposition and running properly.

l This function supports the monitoring of the SPUa board only.

Procedure





Step 2 On the Monitor Navigation Tree pane, choose Monitor > UMTS Monitoring > BoardResource Monitoring. The Board Resource Monitoring dialog box is displayed.

Step 3 In the Board Resource Monitoring dialog box, set the parameters as required, and clickSubmit.

NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms). The Y coordinate represents theRX and TX traffic in kbit/s.

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

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



8-41

– 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 scroll

l Right-click on the task information pane at the bottom of the real-time performancemonitoring 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.

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 Port Indicates the number of the IP logical port. Toquery the number of the IP logical port, runthe LST IPLOGICPORT command.

LinkPerformanceMonitoring

IMA Group IMA GroupNo.

Indicates the number of the IMA group. Toquery the IMA group, run the LSTIMAGRP command.

UNI link UNI Link No. Indicates the number of the UNI link. Toquery the UNI link, run the LST UNILNKcommand.



8-43


FractionalATM Link

FRAC LinkNo.

Indicates the number of the fractional ATMlink. To query the number of the fractionalATM link, run the LST FRALNK commandand set Link type to FRAATM.

SAAL Link SAAL LinkNo.

Indicates the number of the SAAL link. Toquery the SAAL link, run the LSTSAALLNK command.

IPoA PVC IP AddressPing Peer IPAddress

Indicates the local and peer IP addresses of theIPoA PCV. To query these IP addresses, runthe LST IPOAPVC command.

AAL2 Path Adjacent NodeIDAAL2 PATHSymbol

Indicates the ID of the adjacent node to anAAL2 path and the AAL2 path symbol. Toquery the adjacent node ID and the AAL2 pathsymbol, run the LST AAL2PATH command.

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, runthe LST 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 ATM logical port, run the LSTATMLOGICPORT command.To query theIP logical port, run the LSTIPLOGICPORT command.

OAM NodeB ID Indicates the NodeB ID. To query the NodeBID, run the LST UNODEB command.

LogicalPortBandwidth

Logical PortNo.

Indicates the number of a logical port. Toquery the ATM logical port, run the LSTATMLOGICPORT command.To query theIP logical port, run the LSTIPLOGICPORT command.





FE/GEPPP LinkMLPPPGroupLogicalPort

Priority GroupNo.

Indicates the priority queue number. (valuerange: 0-5).

Non-Channelized ATMOpticalPort

Optical PortNo.

Indicates the number of the non-channelizedATM optical port. To query the optical port,run the LST OPT command.

IPPM Adjacent NodeIDIP Path ID

Indicates the ID of the node adjacent to anIPPM and the IP path ID. To query the two,run the LST IPPM command.

TrunkGroup

Trunk GroupNo.

Indicates the number of the trunk group. Toquery the trunk group, run the LSTETHTRK command.



8-45

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 UMTSLMT 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 section describes how to query the status of an E1/T1 port.

9.1.4 Querying the CPU UsageThis section describes how to query the CPU usage of a board.

9.1.5 Querying BSC Board Clock StatusThis section describes how to query the clock status of a BSC board.

9.1.6 Querying the BSC Board InformationThis section describes how to query the status of a BSC board.

9.1.7 Resetting the BSC BoardThis section describes how to reset the BSC board, the CPU on the SPUa/SPUb board, and theDSP on the DPU board. Only the admin, ADMINISTRATOR-level, and authorized CUSTOM-level users can perform this operation.

9.1.8 Switching Over the BSC BoardsThis section describes how to switch over the active BSC board and the standby BSC board.When the active board is faulty, you can switch all the services over to the standby board toensure the normal operation of the system. Only the admin, ADMINISTRATOR-level, andauthorized CUSTOM-level users can perform this operation.

9.1.9 Querying the BSC Board AlarmThis section describes how to query the BSC board alarm.

9.1.1 Introduction to the Device PanelIn addition to MML commands, the LMT also provides the graphical device panel to facilitatedevice maintenance.

The device panel is automatically refreshed, showing board status in real time with the help ofboard colors 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.

9 Device PanelBSC6900 UMTSLMT User Guide



Figure 9-1 Device Panel

Alarm indicators represent the alarm status of a board, and board colors indicate the runningstatus of a board. See the color descriptions shown on the right side of the device panel forspecific meanings of 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 You can right-click the peripheral frame of a rack, and choose Refresh Shelf from theshortcut menu to refresh the rack.

l If you select Display Logic Function under the color descriptions of the board, the logicfunctions of boards are displayed on the device panel.

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 is displayed in the BSC Device Panel tab page.

----End




9-3

Prerequisitel You have logged in to the LMT.l The boards are in position.

ProcedureStep 1 Start the BTS 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 displayed Query E1/T1 PortStatus shows the details about the E1/T1 port.

----End



ContextYou can query the CPU usage through menu operations or through MML commands.


1. Start the BTS 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



ContextYou can query the clock status of a BSC board through menu operations or through MMLcommands.





1. Open the device panel (see 9.1.2 Starting the Device Panel) or open 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 chooseQuery BSC Board Clock Status from the shortcut menu. The Query BSC BoardClock Status dialog box is displayed.

3. In the Query BSC Board Clock Status dialog box, set the parameters as required,and click Query.

l Through MML commands1. Run the DSP CLK command to query the clock status of a BSC board.

----End



ContextYou can query the status of a board 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 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-5

Context

CAUTIONl If the standby board is not available or 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 performthe switchover when the traffic load is light, for example, in the middle of the night.

l Resetting the Board

The board resetting is mandatory during software upgrade and software loading. 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/SCUb board is reset while its standby board is not availableor is faulty, the entire subrack is reset.

l Reset the CPU

Each SPUa board has four CPUs numbered from 0 to 3. Each SPUb board has four CPUsnumbered from 0 to 3. Other types of boards have one CPU each. If CPU 0 of the SPUa/SPUb board is reset, the entire board is reset.

l Resetting the DSP

Each DSP can be reset separately:

– Each DPUb board has 22 DSPs numbered from 0 to 21.

– Each DPUe board has 28 DSPs numbered from 0 to 27.



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 OMU board. The OMUa board also supportsswitchover initiated by the standby board.

You can switch over 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 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.1.9 Querying the BSC Board AlarmThis section describes how to query the BSC board alarm.


l The boards are in position.

Procedure

Step 1 Start the device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel (see9.2.2 Starting the Emulation Panel).



9-7

Step 2 Right-click a board in position in the device panel or the emulation panel, and then choose QueryBoard Alarm from the shortcut menu. Accordingly, the alarm information is displayed.

----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 those of 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.9 Querying the Status of an FE PortThis section describes how to query the status of an FE port.

9.2.10 Querying the Status of a GE PortThis section describes how to query the status of a GE port on the SCUa board.

9.2.11 Querying the Status of an Optical PortThis section describes how to query the status of an optical port.

9.2.12 Querying the DSP Status of a DPUThis section describes how to query the DSP status of a DPU board.

9.2.13 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 those of the real subrack and helps to ascertain the status of each board.

The emulation panel displays the running status of the ports of each board and provides 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


Procedure

Step 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page isdisplayed.



9-9

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



Procedure

Step 1 Start the BTS 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 displayed Query E1/T1 PortStatus shows the details about the E1/T1 port.

----End






ContextYou can query the CPU usage through menu operations or through MML commands.


1. Start the BTS 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



ContextYou can query the clock status of a BSC board through menu operations or through MMLcommands.


1. Open the device panel (see 9.1.2 Starting the Device Panel) or open 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 chooseQuery BSC Board Clock Status from the shortcut menu. The Query BSC BoardClock Status dialog box is displayed.

3. In the Query BSC Board Clock Status dialog box, set the parameters as required,and click Query.




9-11

1. Run the DSP CLK command to query the clock status of a BSC board.

----End



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 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/SCUb board is reset while its standby board is not availableor is faulty, the entire subrack is reset.

l Reset the CPUEach SPUa board has four CPUs numbered from 0 to 3. Each SPUb board has four CPUsnumbered from 0 to 3. Other types of boards have one CPU each. If CPU 0 of the SPUa/SPUb board is reset, the entire board is reset.

l Resetting the DSPEach DSP can be reset separately:– Each DPUb board has 22 DSPs numbered from 0 to 21.– Each DPUe board has 28 DSPs numbered from 0 to 27.



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


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.



9-13

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 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 OMU board. The OMUa board also supportsswitchover initiated by the standby board.

You can switch over 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 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.9 Querying the Status of an FE PortThis section describes how to query the status of an FE port.


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.10 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.11 Querying the Status of an Optical PortThis section describes how to query the status of an optical port.


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.



9-15


1. Run the DSP OPT to query the status of the optical port.

----End

9.2.12 Querying the DSP Status of a DPUThis section describes how to query the DSP status of a DPU board.


l The board is in the specified slot.

Context

You 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 chooseQuery DSP Status from the shortcut menu. The displayed Query DSP Status showsthe details about the DSP status.


1. Run the DSP DSP command to query the DSP status of the DPU board.

----End

9.2.13 Querying Alarm LED InformationThis section describes how to query the details of alarms indicated by an alarm LED.


l The boards are in position.

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




10 FAQ

About This Chapter

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

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

10.2 The color of the LMT is not properly displayed.When the LMT is started in the IE browser, the colors are not properly displayed. For example,the colors indicating the status of the boards and alarms are not displayed, or the backgroundcolor of the LMT is not differentiated from that of the IE browser. In this case, check the colorsettings of the browser.

10.3 The verify code is not displayed on the LMT login page.The verify code is not displayed when you try to log in to the LMT through the IE browser inthe Windows Server 2008 or Windows Vista system. In this case, check the settings related tothe protection mode of the browser.

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

10.5 No response on clicking the menu bar on the LMT.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.

10.6 Changing the Computer Time During the LMT Use ProhibitedChanging 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.

10.7 Corrupted characters appears when the csv file is opened in UTF-8 coding

BSC6900 UMTSLMT User Guide 10 FAQ


10-1

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 corrupted characters. In this case, open the csv file by using the import methodin Excel.

10.8 Maximum Number of LMT Clients That Can Be Started on One PC SimultaneouslyYou can have multiple LMT clients started on one PC. Starting too many LMT clientssimultaneously, however, affects maintenance performance.

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

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

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

10.12 Unable to download and Install the Java/Flash Plug-in When Internet Explorer 8 Is UsedIf you browse LMT using Internet Explorer 8 (IE8), an error is displayed when you aredownloading and installing the Java/Flash plug-in. In this case, you need to turn off SmartScreenFilter.

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

10.14 Any Further Operation Performed When Some LMT Web Pages Failing to Update Causesthe Web Pages to Turn BlankSome LMT Web pages fail to update when batch processing, tracing, or monitoring is in use.Any further operation causes the Web pages to turn blank. If you restart the function, the Webpage returns to normal. To prevent this problem, perform the following operations to add anenvironment variable.

10 FAQBSC6900 UMTSLMT User Guide



10.1 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

10.2 The color of the LMT is not properly displayed.When the LMT is started in the IE browser, the colors are not properly displayed. For example,the colors indicating the status of the boards and alarms are not displayed, or the 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

10.3 The verify code is not displayed on the LMT login page.The verify code is not displayed when you try to log in to the LMT through the IE browser inthe Windows Server 2008 or Windows Vista system. In this case, check the settings related tothe 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.



10-3

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

Restart the browser to validate the modifications.

----End

10.4 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.l Patch KB944338 improves the performance of the LMT by increasing the speed of visiting

a web page. Thus, the LMT running rate can be increased.

Procedure

Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or 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 in

the following ways:




OS Version IE Version

Windows 2000 SP4 IE5/IE6 SP1

Windows XP SP2/SP3 IE6/IE7

Windows Server 2003 SP1/SP2 IE6/IE7

Windows Vista IE7

l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4, Windows

XP SP1/SP2, or Windows Server 2003 SP1/SP2.NOTE

l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.l Download a suitable patch according to the OS version and IE version.

----End

10.5 No response on clicking the menu bar on the LMT.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.

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

ProcedureStep 1 Choose Tools > Internet Options on the tool bar of IE. The Internet Options dialog box is

displayed.

Step 2 On the Connections tab page, click LAN Settings. The LAN Settings dialog box is displayed.

Step 3 In the Proxy server area, select Use a proxy server for your LAN (These settings will 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

10.6 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 time



10-5

fails to refresh normally; tracing data and monitoring data fail to refresh normally; progressmanagement fails to refresh normally.

10.7 Corrupted characters appears when the csv file isopened 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 corrupted characters. In this case, open the csv file by using the import methodin Excel.

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 10-1 shows the dialog box.

Figure 10-1 Operation interface for importing data in Excel

Step 2 In the Select Data Source dialog box, select the csv file in UTF-8 coding. Then the Text ImportWizard - Step 1 of 3 dialog box is displayed. Figure 10-2 shows the dialog box. Select UTF-8in File origin.




Figure 10-2 Text import wizard-step 1

Step 3 Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed. Figure 10-3shows the dialog box. Select Comma under Delimiters.

Figure 10-3 Text import wizard-step 2



10-7

Step 4 Click Finish. Then the Import Data dialog box is displayed. Figure 10-4 shows the dialog box.

Figure 10-4 Interface after data importation is finished

Step 5 Click OK. Then the file is displayed properly.

----End

10.8 Maximum Number of LMT Clients That Can Be Startedon One PC Simultaneously

You can have multiple LMT clients started on one PC. Starting too many LMT clientssimultaneously, however, affects maintenance performance.

In normal maintenance, the maximum number of LMT clients that can be started on one PCsimultaneously is as follows:l One PC with 2 GB memory can start 16 LMT clients simultaneously.l One PC with 1 GB memory can start 8 LMT clients simultaneously.l One PC with 512 MB memory can start 4 LMT clients simultaneously.

10.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 aCitrix 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.

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 10-5 shows the window.



10-9

Figure 10-5 Active Directory Users and Computers

(2) In the right-side window, right-click hong01. Choose Properties from the

shortcut menu. Accordingly, the hong01 Properties dialog box is displayed.Figure 10-6 shows the dialog box.




Figure 10-6 hong01 Properties 1

(3) In the hong01 Properties dialog box, click the Profile tag. Type IE-unset.bat

in Logon script, click Apply, and then click OK. Figure 10-7 shows thewindow.



10-11

Figure 10-7 hong01 Properties 2

l Manual Setting

1. Check the proxy server setting of the explorer.

(1) Choose Tools > Internet Options on the tool bar of the IE. Accordingly, 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.




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 10-8 shows thewindow.

Figure 10-8 HTTP 1.1 settings



10-13

----End

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




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 10-9, chooseUser Configuration > Windows Settings > Scripts(Logon/Logoff).

Figure 10-9 Script



10-15

(4) Double-click Logon. A dialog box shown in Figure 10-10 is displayed. ClickShow Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.

Figure 10-10 Logon

(5) Click Add in the dialog box shown in Figure 10-11. A dialog box shown in

Figure 10-11 is displayed.

Figure 10-11 Adding a script




(6) In the dialog box shown in Figure 10-11, click Browse to select the preparedscript and click OK. Then close the dialog box.

(7) In the dialog box shown in Figure 10-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 10-12, choose User Configuration > WindowsSettings > Scripts(Logon/Logoff).

Figure 10-12 Script



10-17

(3) Double-click Logon. A dialog box shown in Figure 10-13 is displayed. ClickShow Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.

Figure 10-13 Logon

(4) Click Add in the dialog box shown in Figure 10-13. A dialog box shown in

Figure 10-14 is displayed.

Figure 10-14 Adding a script




(5) In the dialog box shown in Figure 10-14, click Browse to select the preparedscript and click OK. Then close the dialog box.

(6) In the dialog box shown in Figure 10-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 10-15.

Figure 10-15 Windows components wizard

2. Click Details... in the dialog box shown in . In the displayed dialog box shown in

Figure 10-16, deselect For administrator groups and For all other user groups.



10-19

Figure 10-16 Internet Explorer Enhanced Security Configuration

3. Click OK and then click Next to remove Internet Explorer Enhanced Security

Configuration. After the removal is complete, click Finish.4. Restart the IE to validate the configuration.

----End

10.11 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 ofan 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

10.12 Unable to download and Install the Java/Flash Plug-in When Internet Explorer 8 Is Used

If you browse LMT using Internet Explorer 8 (IE8), an error is displayed when you aredownloading and installing the Java/Flash plug-in. In this case, you need to turn off SmartScreenFilter.

Context

SmartScreen Filter is a new function in IE8. It prevents you from visiting phishing Web sitesand prevents malicious plug-ins from being installed automatically. SmartScreen Filter,however, leads to the installation error when you install the Java/Flash plug-in on the LMT.



10-21

Procedure

Step 1 Choose Safety > SmartScreen Filter > Turn Off SmartScreen Filter on an IE Web page.

Step 2 In the displayed Microsoft SmartScreen Filter dialog box, select Turn off SmartScreenFilter and click OK to turn off SmartScreen Filter.

----End

10.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 10-17 are provided. Changing the default option as described below solves the previousproblem.




Figure 10-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

10.14 Any Further Operation Performed When Some LMTWeb Pages Failing to Update Causes the Web Pages to TurnBlank

Some LMT Web pages fail to update when batch processing, tracing, or monitoring is in use.Any further operation causes the Web pages to turn blank. If you restart the function, the Web



10-23

page returns to normal. To prevent this problem, perform the following operations to add anenvironment variable.

Procedure

Step 1 On the LMT PC, select My Computer and right-click Properties from the shortcut menu. TheSystem Properties dialog box is displayed.

Step 2 In the System Properties dialog box, click the Advanced tab and click EnvironmentVariables. The Environment Variables dialog box is displayed.

Step 3 In the Environment Variables dialog box, click New. The New User Variable dialog box isdisplayed.

Step 4 In the New User Variable dialog box, set Variable name toJPI_PLUGIN2_NO_HEARTBEAT and Variable value to 1. Then click OK.

Step 5 In the Environment Variables dialog box, click OK.

Step 6 In the System Properties dialog box, click OK to finish adding the environment variable.

----End




lmt user guide

Documents