Bsc6900 Umts Lmt User Guide(v900r014c00_07)(PDF)-En

BSC6900 UMTSV900R014C00

LMT User Guide

Issue 07

Date 2013-04-15

HUAWEI TECHNOLOGIES CO., LTD.

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 07 (2013-04-15) 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 V900R014C00

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


ii

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 .csv 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. When OMU boards perform an active/standby switchover, monitoring can be restarted only 30 minutes after the switchover.

8 Performance Monitoring

This chapter describes how to monitor the BSC6900 performance. A maximum of 64 monitoringtasks can be performed simultaneously on the same LMT. When OMU boards perform an active/standby switchover, monitoring can be restarted only 30 minutes after the switchover.

9 Device Panel

This chapter describes how to manage the BSC6900 equipment by using the device andemulation panels. You can use these panels to query for information about the boards, boardports, board links, and board alarms.

10 BSC Maintenance

This chapter describes how to maintain the BSC equipment, Backing Up Data and RestoringData, and Fault Management Assistant.

11 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 or medium level of riskwhich, if not avoided, could result in death or serious injury.



iii

Symbol Description

Indicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated 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.



iv


[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

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


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Keyboard Operations

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

Format Description

Key Press the key. For example, press Enter and press Tab.

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

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

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

Action Description

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

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

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



v

Contents

About This Document.....................................................................................................................ii

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

2 Introduction to LMT.....................................................................................................................62.1 Configuration Requirements of the LMT PC.....................................................................................................72.2 Logging In to and Logging Out of the LMT......................................................................................................92.3 Components of the LMT Window....................................................................................................................122.4 LMT Software..................................................................................................................................................15

2.4.1 Installing LMT Offline Tools..................................................................................................................152.4.2 FTP Client................................................................................................................................................172.4.3 FTP Server...............................................................................................................................................182.4.4 LMT Offline MML..................................................................................................................................202.4.5 Convert Management System..................................................................................................................242.4.6 Performance Browser Tool......................................................................................................................252.4.7 TrafficRecording Review Tool................................................................................................................26

2.5 File Manager.....................................................................................................................................................27

3 Management of Operation Rights............................................................................................303.1 Concepts Related to Operation Rights Management........................................................................................31

3.1.1 Principles of Operation Rights Management...........................................................................................313.1.2 User Password.........................................................................................................................................313.1.3 Command Group.....................................................................................................................................313.1.4 User Type................................................................................................................................................323.1.5 Operation Rights......................................................................................................................................333.1.6 Operation Time Limit..............................................................................................................................34

3.2 Management of User Accounts........................................................................................................................353.2.1 Creating an External User Account.........................................................................................................353.2.2 Modifying an External User Account......................................................................................................353.2.3 Deleting an External User Account.........................................................................................................36

3.3 Management of User Passwords.......................................................................................................................363.3.1 Defining Login Password Policies..........................................................................................................363.3.2 Querying Login Password Policies..........................................................................................................363.3.3 Changing the Password of the Active User Account..............................................................................373.3.4 Changing the Password of an External User Account.............................................................................37

BSC6900 UMTSLMT User Guide Contents


vi

3.4 Management of Command Groups...................................................................................................................373.4.1 Querying a Command Group..................................................................................................................383.4.2 Setting the Command Group Name.........................................................................................................383.4.3 Changing the Commands in a Command Group.....................................................................................38

4 Running MML Commands........................................................................................................394.1 Concepts Related to MML Commands............................................................................................................41

4.1.1 Introduction to MML Commands............................................................................................................414.1.2 Components of the MML Command Window........................................................................................424.1.3 Data Configuration Rights.......................................................................................................................444.1.4 Data Configuration Rollback...................................................................................................................44

4.2 Running an MML Command...........................................................................................................................454.3 Batch Processing MML Commands.................................................................................................................46

4.3.1 Immediate Batch Processing of MML Commands.................................................................................474.3.2 Scheduled Batch Processing of MML Commands..................................................................................474.3.3 Syntax Check...........................................................................................................................................48

4.4 Setting MML Parameters..................................................................................................................................494.5 Querying the Data Configuration Mode...........................................................................................................504.6 Querying Data Configuration Rights................................................................................................................514.7 Obtaining Data Configuration Rights...............................................................................................................524.8 Undoing/Redoing a Data Configuration Action...............................................................................................534.9 Undoing/Redoing Multiple Data Configuration Actions.................................................................................54

5 Alarm/Event Management.........................................................................................................565.1 Concepts Related to Alarm Management.........................................................................................................57

5.1.1 Alarm Type..............................................................................................................................................575.1.2 Alarm Severity.........................................................................................................................................575.1.3 Alarm-Event Type...................................................................................................................................585.1.4 Alarm Flag...............................................................................................................................................595.1.5 Alarm Box...............................................................................................................................................60

5.2 Managing Alarm Logs......................................................................................................................................615.2.1 Setting Storage Conditions of Alarm Logs..............................................................................................615.2.2 Querying Storage Conditions of Alarm Logs..........................................................................................61

5.3 Managing the Alarm Filter...............................................................................................................................615.3.1 Creating an Alarm Filter..........................................................................................................................615.3.2 Deleting an Alarm Filter..........................................................................................................................625.3.3 Querying an Alarm Filter........................................................................................................................62

5.4 Managing the Filter of Derived Alarms...........................................................................................................635.4.1 Setting the Filter of Derived Alarms.......................................................................................................635.4.2 Querying the Filter of Derived Alarms....................................................................................................63

5.5 Monitoring Alarms...........................................................................................................................................635.5.1 Browsing Alarm/Event............................................................................................................................645.5.2 Querying the Alarm/Event Log...............................................................................................................645.5.3 Querying Alarm/Event Handling Suggestions........................................................................................65



vii

5.5.4 Querying Alarm/Event Configuration.....................................................................................................665.5.5 Filtering Fault Alarm/Event.....................................................................................................................675.5.6 Setting Alarm/Event Attributes...............................................................................................................675.5.7 Manually Clearing an Alarm/Event.........................................................................................................685.5.8 Deleting Alarms/Events...........................................................................................................................685.5.9 Refreshing the Alarm/Event Window.....................................................................................................69

5.6 Managing the Alarm Box.................................................................................................................................695.6.1 Querying Alarm Box Information...........................................................................................................695.6.2 Querying Number of Alarms with Different Severities..........................................................................705.6.3 Operating the Alarm Box........................................................................................................................705.6.4 Querying the Alarm Box Filter Level......................................................................................................70

6 Log Management.........................................................................................................................726.1 Log Types.........................................................................................................................................................746.2 Querying Log Storage Conditions....................................................................................................................746.3 Setting Log Storage Conditions........................................................................................................................746.4 Querying Operation Logs.................................................................................................................................756.5 Exporting Operation Logs................................................................................................................................756.6 Querying Security Logs....................................................................................................................................766.7 Exporting Security Logs...................................................................................................................................776.8 Obtaining Running Logs..................................................................................................................................776.9 Collecting Log Statistics...................................................................................................................................79

7 Trace Management......................................................................................................................837.1 Concepts Related to Trace Management..........................................................................................................84

7.1.1 Trace Principles.......................................................................................................................................847.1.2 Management of Tracing Operation Rights..............................................................................................857.1.3 Trace Mode..............................................................................................................................................85

7.2 Device Commissioning.....................................................................................................................................857.2.1 Tracing OS Messages..............................................................................................................................857.2.2 Tracing Redirected Messages..................................................................................................................867.2.3 Capturing Packets....................................................................................................................................87

7.3 UMTS Services.................................................................................................................................................917.3.1 Tracing Messages on the Iu Interface......................................................................................................917.3.2 Tracing Messages on the Iupc Interface................................................................................................1057.3.3 Tracing Messages on the Iur Interface...................................................................................................1117.3.4 Tracing Messages on the Iub Interface..................................................................................................1257.3.5 Tracing Messages on the Uu Interface..................................................................................................1337.3.6 Tracing MNCDT Messages...................................................................................................................1357.3.7 Tracing UE Messages............................................................................................................................1407.3.8 Tracing Cell Messages...........................................................................................................................1477.3.9 Tracing IOS Messages...........................................................................................................................150

7.4 Basic Tracing Operations...............................................................................................................................1567.4.1 Browsing Traced Messages Online.......................................................................................................157



viii

7.4.2 Viewing the Interpretation of the Trace Message..................................................................................1587.4.3 Saving Traced Messages.......................................................................................................................1587.4.4 Browsing Traced Messages Offline......................................................................................................1597.4.5 Managing Tracing Tasks.......................................................................................................................1607.4.6 Managing the Trace File........................................................................................................................161

8 Performance Monitoring..........................................................................................................1628.1 Concepts Related to Performance Monitoring...............................................................................................163

8.1.1 Monitoring Principles............................................................................................................................1638.1.2 Management of Monitoring Operation Rights......................................................................................164

8.2 Common Monitoring......................................................................................................................................1658.2.1 Monitoring CPU/DSP Usage.................................................................................................................1658.2.2 Monitoring Transmission Resources.....................................................................................................1658.2.3 Monitoring BER Seconds......................................................................................................................1678.2.4 Monitoring BER....................................................................................................................................1688.2.5 Monitoring Link Performance...............................................................................................................169

8.3 UMTS Monitoring..........................................................................................................................................1838.3.1 Monitoring Connection Performance....................................................................................................1838.3.2 Monitoring Cell Performance................................................................................................................1948.3.3 Monitoring Board Resources.................................................................................................................204

8.4 General Operations of Performance Monitoring............................................................................................2058.4.1 Browsing the Monitoring Results Online..............................................................................................2058.4.2 Setting the Display Mode of the Chart..................................................................................................2068.4.3 Saving Monitoring Results....................................................................................................................2068.4.4 Browsing Monitoring Results Offline...................................................................................................206

8.5 Reference for Performance Monitoring..........................................................................................................207

9 Device Panel...............................................................................................................................2109.1 Device Panel Operations................................................................................................................................211

9.1.1 Introduction to the Device Panel...........................................................................................................2119.1.2 Starting the Device Panel......................................................................................................................2119.1.3 Querying the Status of an E1/T1 Port....................................................................................................2129.1.4 Querying the CPU/DSP Usage..............................................................................................................2129.1.5 Querying BSC Board Clock Status.......................................................................................................2139.1.6 Querying the BSC Board Information...................................................................................................2139.1.7 Resetting the BSC Board.......................................................................................................................2149.1.8 Switching Over the BSC Boards...........................................................................................................2159.1.9 Querying the BSC Board Alarm............................................................................................................216

9.2 Emulation Panel Operations...........................................................................................................................2169.2.1 Introduction to the Emulation Panel......................................................................................................2169.2.2 Starting the Emulation Panel.................................................................................................................2179.2.3 Querying the Status of an E1/T1 Port....................................................................................................2189.2.4 Querying the CPU/DSP Usage..............................................................................................................2189.2.5 Querying BSC Board Clock Status.......................................................................................................219



ix

9.2.6 Querying the BSC Board Information...................................................................................................2209.2.7 Resetting the BSC Board.......................................................................................................................2209.2.8 Switching Over the BSC Boards...........................................................................................................2219.2.9 Querying the Status of an FE Port.........................................................................................................2229.2.10 Querying the Status of a GE Port........................................................................................................2239.2.11 Querying the Status of an Optical Port................................................................................................2239.2.12 Querying the DSP Status of a DPU.....................................................................................................2249.2.13 Querying Alarm LED Information......................................................................................................224

10 BSC Maintenance....................................................................................................................22510.1 Backing Up Data..........................................................................................................................................22610.2 Restoring Data..............................................................................................................................................22710.3 Fault Management Assistant........................................................................................................................22810.4 OS Maintenance...........................................................................................................................................229

11 FAQ............................................................................................................................................23111.1 Slow Responses in the Firefox Browser.......................................................................................................23511.2 LMT Colors Cannot Be Displayed...............................................................................................................23511.3 What Can I Do if the Verification Code Cannot Be Displayed on the LMT Login Page?..........................23511.4 Installing OS Patches....................................................................................................................................23611.5 No Response When Clicking the Menu Bar on the LMT............................................................................23711.6 Changing the Computer Time During the LMT Use Prohibited..................................................................23811.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding......................................23811.8 Maximum Number of LMT Clients That Can Be Started on One PC Simultaneously...............................24111.9 How Do I Set the Browser Under Citrix Farm Networking?.......................................................................24111.10 Unable to Log In To LMT Because IE Default Security Level Is Too High.............................................24611.11 Unable to Download or Install the Java or Flash Plug-in and Two File Manager Windows Displayed WindowsIE8 or Any Later Version Is Used........................................................................................................................25211.12 LMT Fails to Function Properly When Error Occurs in Mixed Code Security Verification of JRE.........25311.13 Any Further Operation Performed When Some LMT Web Pages Fail to Update Causes the Web Pages toTurn Blank............................................................................................................................................................25411.14 Configuring the HTTPS Login Mode.........................................................................................................25511.15 What Do I Do if the Error "Certificate Invalid" Is Displayed During an HTTPS Login...........................25611.16 Error 'Mismatched Address' Is Displayed During an HTTPS Login.........................................................26511.17 What Do I Do if Tracing and Monitoring Functions Cannot Be Used?.....................................................26711.18 What Do I Do If There Is No Response or Any Error Message After a Tracing or Monitoring Task Is Created?..............................................................................................................................................................................27211.19 What Do I Do If the File Manager Functions Improperly?........................................................................27411.20 What Do I Do If BTS Nodes Cannot Be Displayed Under Device Navigation Tree.................................27511.21 What Do I Do if the Alarm/Event Function Becomes Unavailable?..........................................................27611.22 What Do I Do if the Message 'Class doesn't support Automation' Is Displayed in an IE Browser?..........27711.23 What Do I Do if Java Installation Fails......................................................................................................27811.24 What Do I Do if the LMT Login Web Page Cannot Be Opened with the PC OMU Installed?.................27811.25 What Do I Do if Changing Settings for the Next-Generation Java Plug-in Fails?.....................................279



x

11.26 Error Message"This user session already exists" Upon Login to LMT.....................................................28311.27 The "Are You Sure You Want to Quit the Page?" Dialog Box Is Displayed.............................................28411.28 Unable to Save Tracking and Monitoring Data..........................................................................................28411.29 Slow Response During an LMT Login.......................................................................................................28511.30 Unclear Grids in the Tables in the MML Online Help...............................................................................28611.31 MML Command Failed to Be Executed or No Response to Tracing Tasks After the Browser Is Upgraded toIE8........................................................................................................................................................................287



xi

1 Changes in the BSC6900 UMTS LMT UserGuide

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

07 (2013-04-15)

This is the seventh commercial release of V900R014C00.

Compared with issue 06 (2013-03-25), this issue does not include any new topics.

Compared with issue 06 (2013-03-25), this issue includes the following incorporate changes:

Content Description

Monitoring the Outer Loop Power Control Changed Enhanced Outer Loop PowerControl to Outer Loop Power Control.

Compared with issue 06 (2013-03-25), this issue does not exclude any topics.

06 (2013-03-25)

This is the sixth commercial release of V900R014C00.



Content Description

2.4.3 FTP Server Added the description: the default passwordof FTP server is hwbs@com.

8.3.3 Monitoring Board Resources Changed the unit of the Y coordinate on theMonitoring Board Resources GUI windowfrom KB to Erl.

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


1


05 (2012-12-31)

This is the fifth commercial release of V900R014C00.

Compared with issue 04 (2012-11-07), this issue includes the following new topics:

11.31 MML Command Failed to Be Executed or No Response to Tracing Tasks After theBrowser Is Upgraded to IE8


Content Description

2.1 Configuration Requirements of theLMT PC

Added FireFox 10.X to recommendedconfiguration of web browser; add thedescription of not adjust the size of thebrowser window when using the LMT.

6 Log Management Modified the log files formats from .logto .csv.

11.15 What Do I Do if the Error"Certificate Invalid" Is Displayed Duringan HTTPS Login

Added the solution of Certificate Invaliddisplayed when access the LMT through theM2000 proxy with dual IP addresses.


04 (2012-11-07)

This is the fourth commercial release of V900R014C00.



Content Description

2.2 Logging In to and Logging Out of theLMT

Added the maximum number of local usersand EMS users who can log in to the LMT.

11.14 Configuring the HTTPS Login Mode Modified the HTTPS Login Mode.

7.2.3 Capturing Packets Added the description of packet capturing logand VLAN Tag.

7.2.2 Tracing Redirected Messages Added the description of onlyADMINISTRATOR-level users areauthorized for performing TracingRedirected Messages.

2.4.3 FTP Server Deleted the description of the port 21 is usedas the default port.



2

Content Description

EmergencyDiag Changed the COM Redirection toEmergencyDiag.

2.5 File Manager Added the recommended maximum numberof files downloaded and uploaded when thebandwidth is 2 Mbit/s.

2.1 Configuration Requirements of theLMT PC

Added the configuration requirements ofusing IE8 or later versions.


03 (2012-08-30)This is the third commercial release of V900R014C00.


11.29 Slow Response During an LMT Login

11.30 Unclear Grids in the Tables in the MML Online Help

Compared with issue 02 (2012-06-30), this issue does not incorporate any changes.


02 (2012-06-30)This is the second commercial release of V900R014C00.


7.2.1 Tracing OS Messages

7.2.2 Tracing Redirected Messages

10.4 OS Maintenance

Compared with issue 01 (2012-04-26), this issue does not incorporate any changes.


01 (2012-04-26)This is the first commercial release of V900R014C00.

Compared with issue Draft B (2012-03-26), this issue includes the following new topics:

11.26 Error Message"This user session already exists" Upon Login to LMT

11.27 The "Are You Sure You Want to Quit the Page?" Dialog Box Is Displayed

11.28 Unable to Save Tracking and Monitoring Data

Compared with issue Draft B (2012-03-26), this issue does not incorporate any changes.



3

Compared with issue Draft B (2012-03-26), this issue does not exclude any topics.

Draft B (2012-03-26)

This is the Draft B release of V900R014C00.

Compared with issue Draft A (2012-02-15) of V900R014C00, this issue does not include anynew topics.

Compared with issue Draft A (2012-02-15) of V900R014C00, this issue includes the followingincorporate changes:

Content Description

2.2 Logging In to and LoggingOut of the LMT

The default mode of logging in to LMT is changed fromHTTP to HTTPS.

2.1 ConfigurationRequirements of the LMT PC

Added a note: FireFox 4.0 or later releases is notsupported.

Compared with issue Draft A (2012-02-15) of V900R014C00, this issue does not exclude anytopics.

Draft A (2012-02-15)

This is the Draft A release of V900R014C00.

Compared with issue 06 (2012-01-05) of V900R013C00, this issue includes the following newtopics:

10.3 Fault Management Assistant

Compared with issue 06 (2012-01-05) of V900R013C00, this issue includes the followingincorporate changes:

Content Description

2.3 Components of the LMTWindow

Language Setting is modified to System setting.

2.3 Components of the LMTWindow

Language Setting is modified to System setting.

7.4.1 Browsing TracedMessages Online

By default, each message browser is displayed inmaximized mode. To compare results displayed inmultiple message browsers, set Windows to Cascade,Horizontal or Vertical.

Tracing Messages on the IubInterface

The parameter CPUS subsystem is replaced by NodeBTrace Type.The QAAL2 tab page is deleted.



4

Content Description

Tracing Messages on the IurInterfaceTracing Messages on the IuInterface

The QAAL2 tab page is deleted.

7.3.7 Tracing UE Messages7.3.8 Tracing Cell Messages7.3.9 Tracing IOS Messages

The method of viewing TXT (Command Code) messagesis changed.

Compared with issue 06 (2012-01-05) of V900R013C00, this issue does not exclude any topics.



5

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 Logging In to and Logging Out of the LMTThis section describes how to log in to the LMT for operations and how to log out of it after theoperations are complete.

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


6

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/Vista/7, Windows Server 2003/2008

Default language of theoperating system

Simplified Chinese or English



7

Item Recommended Configuration

Web browser Internet Explorer (IE) 6, 7, or 8 (IE 8 is recommended.);FireFox 3.X and 10.XNOTEl 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 versions, you need to installa JRE plug-in of a version that later than 1.6.0_18.

l If IE8 or later versions is used, you neeed to choose Tools >Compatibility View Settings. In the displayed CompatibilityView Settings dialog box, select Display all websites inCompatibility View.

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 LMT login window. Later officialversions can be obtaied on the official Java website http://java.com

Flash plug-in called AdobeFlash Player

Flash Player 10.1.82 or later official versionsNOTE

The plug-in can be obtained on LMT login window. Later officialversions can be obtaied on the official Java website http://adobe.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 the

32-bit Web explorer.l Do not adjust the size of the browser window when you are using the LMT. Otherwise, the

layout of the LMT interface may be abnormal.

Requirements of Connection Ports

Before you visit the LMT through the Web on a PC, ensure that ports 80, 20, 21, and 443 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 Web page browsing.

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

l Port 443 is the default HTTPS port that is used for HTTPS login Mode.

Communication Capability Requirements

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



8

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

NOTE

l Bandwidth affects the speed of Web page 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 Logging In to and Logging Out of the LMTThis section describes how to log in to the LMT for operations and how to log out of it after theoperations are complete.

Contextl You have installed the JAVA Platform Standard Edition Runtime Environment (JRE)

program before using the LMT. If no JRE plug-in is installed, a message is displayed whenyou log in to the LMT, prompting you to install the plug-in. Follow the instructions to installthe plug-in. If the JRE plug-in on the LMT PC is not the latest version, a message isdisplayed, prompting you to upgrade the plug-in version. In this case, you are advised touninstall the existing JRE plug-in and then install a new version. If you cannot log in to theLMT after you upgrade the JRE program, restart the web browser and retry.

l A maximum of 32 local users and EMS users can log in to the LMT.

WARNINGWhen the LMT is running, do not modify the system time and time zone. Otherwise, severeerrors may occur in the system. Close the LMT window before you modify the system time andtime zone.



9

CAUTIONl Do not use refresh the browser on the LMT. Refreshing the main page, you will be logged

out of the LMT. Refreshing the tracing or monitoring page, a message indicating a scripterror will be displayed.

l If you log in to the LMT through the IE browser, do not modify any file folder properties.Otherwise, the IE browser is automatically refreshed, and error occurs on the LMT.

l Before logging in to the LMT through the IE browser, enable the IE browser to support HTTP1.1 as follows: In the IE browser, choose Tools > Internet Options > Advanced > HTTP1.1 Setting and select Use HTTP 1.1. If the IE browser is configured with login to the LMTthrough a proxy server, select Use HTTP 1.1 through proxy connection.

l Before logging in to the LMT in the Internet Explorer (IE) browser, perform the followingoperations:l Choose Tools > Internet Options in the IE browser and click the Privacy tab in the

Internet Options dialog box. On the Privacy tab page, move the slider in the Settingsfield to the middle until Medium is displayed on the right of the slider. Then, clickSites. The Per Site Privacy Actions dialog box is displayed. In the Address of Website text box, enter the IP address of each website that is allowed to use cookies, and clickAllow.

l You are also advised to perform the following operations: Choose Tools > InternetOptions in the IE browser and click the General tab in the Internet Options dialog box.Clear the Delete browsing history on exit check box on the General tab page.

l If the LMT is active in the 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 fromthe 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 page, click Accessibility. Then, in theFormatting area, deselect Ignore colors specified on Web pages.

l If AVG Internet Security is installed on an LMT PC, the web shield function must be disabled.Otherwise, a dialog box will be displayed, showing "Disconnected. Please log in again."

Procedure

Step 1 Enter the LMT login page by using one of the following modes:



10

Mode ModeDescription

Operation

Mode 1: directconnection

The LMT directlyconnects to theOMU without usingany proxy server.

Type the external virtual IP address of the OMU inthe Address bar of the IE browser. Press Enter onthe keyboard, or click Go next to the Address bar toenter the login window of the BSC6900.NOTE

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

Mode 2:connectionthrough theM2000 that isconfigured asthe proxy server

The LMT connectsto the OMU throughthe M2000 that isconfigured as theproxy server for thebrowser.NOTE

This mode isrecommended whenthe M2000 proxyserver needs to beused to connect tothe OMU.

Set the M2000 proxy server in the browser and typethe external virtual IP address of the OMU in theAddress bar of the browser. Press Enter on thekeyboard, or click Go next to the Address bar toenter the login window of the BSC6900. You canset the M2000 proxy server in the browser by usingthe following method: Choose Tool > InternetOptions on the tool bar of the browser. In theConnection tab page, click LAN Settings. Thenspecify the IP address and port number of theM2000 server in the Proxy server area. The defaultport number is 80.

Mode 3:connectionthrough theM2000 withboth IPaddressesentered

The LMT connectsto the OMU throughthe M2000 with IPaddresses of bothM2000 and OMUentered in thebrowser.NOTE

This mode is usedonly when theexplorer isconfigured with aproxy server, whichis not the M2000 andcannot be changed.

Type "M2000_IP/OMU_IP/" (for example,10.141.130.146/10.141.151.208/) or "http://M2000_IP/OMU_IP/login.html" in the Address barof the IE browser. Press Enter on the keyboard, orclick Go next to the Address bar to enter the loginwindow of the BSC6900. Note that "/" must beincluded in "M2000_IP/OMU_IP/" behind"OMU_IP." If another proxy server is already set,you need to add M2000_IP to the IP addresses thatdo not use the proxy server under Exceptions.NOTE

OMU_IP indicates the external virtual IP address of theOMU and M2000_IP indicates the IP address of theM2000 server.

Step 2 Specify User Name, Password, and Verify Code.

l Set User Type to Local or EMS.

l If the verify code is illegible, click Change the verify code for a new code.

l It is recommended that you change the password at your first login and then change thepassword every three months.



11

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, check whether the connection between the LMT and the OMU is normal.

Step 4 Optional: To lock the LMT window, click Lock in the top right corner of the LMT main page.

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

l HTTPS is the default mode. You can log in to the LMT through the HTTP Secure (HTTPS) mode. Basedon HTTP, HTTPS introduces SSL or TLS to ensure security.

l Before logging in to the LMT through HTTPS, configure the HTTPS login mode and certificate files byreferring to 11.14 Configuring the HTTPS Login Mode.

l In HTTPS mode, if you need to connect to the OMU with the M2000 as the proxy server, you are advisedto adopt mode 2. Visiting the OMU by adopting mode 3 takes four times the time taken by adopting mode2.

l To log in to the LMT through HTTPS, enter https://the external virtual IP address of the OMU, forexample, https://10.141.115.219, in the Address bar of the browser.

l Correct errors displayed during the login by referring to 11.15 What Do I Do if the Error "CertificateInvalid" Is Displayed During an HTTPS Login and 11.16 Error 'Mismatched Address' Is DisplayedDuring an HTTPS Login.

l After entering the HTTPS login page, which is the same as the HTTP login page, perform the same operationsfor a login.

----End

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

InterfaceFigure 2-1 shows the LMT window.

Figure 2-1 LMT window



12

Table 2-4 describes components of an LMT window.

Table 2-4 Components of the LMT window

Component Description

Alarm/Event 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

To display the Progress tab page, click Progress on the toolbar. Then,double-click an entry to view the detailed information. The ProgressManagement dialog box is displayed, listing the detailed progress report.

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.



13


System Setting After clicking it, a dialog box containing three areas is displayed.The three areas are named Language Setting, Auto Lock and Resultfile Save Path.l Choosing a language in the Language Setting area allows text

in this language to be input and displayed on the LMT. Settingthe language does not change the display language of the LMT.

l In the Auto Lock area, the time for the LMT to wait beforelocking the screen can be specified. If there is no mouse orkeyboard operation during the time, the LMT automaticallylocks its operation screen and goes to the locked page. Thesetting prevents unauthorized users from using others' accountsand performing unauthorized configuration and maintenance.

l In the Result file Save Path area, the save path for all operationresult files can be specified. The system default save path is C:\Web LMT\MBSC\output.

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.

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.



14

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.

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. Help information about the command is displayed in thetab 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 TrafficRecordingReview Tool.

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

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

2.1 Configuration Requirements of the LMT PC.



15

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.

NOTE

Contact Huawei engineers who can obtain the installation package by performing the following operation:

Log in to http://support.huawei.com, and then choose Support > Software Center > VersionSoftware > Wireless Product Line > SingleRAN > 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 enable the system toautomatically exit the LMT application. Click No to manually exit the LMT application.

Step 7 Select the software components and then click Next. It is recommended that you select 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.



16

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 suite and enables the LMT to communicatewith the FTP server according to the FTP protocol. You can obtain logs and upload dataconfiguration files through the FTP client.

Startup

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

Interface

Figure 2-2 shows the FTP client interface.

Figure 2-2 FTP client interface

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



17

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 Includes the server name, user name, user password,port number, and mode in this area.NOTE

To query the port number, run the LST FTPSSRVcommand to query the setting for the Command Port ofFTPS Server. If an incorrect port number is used, the LMTcannot be connected to the FTP server.

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 suite and provides FTP upload and downloadservice. It is used when users upload and download BTS software and license files.

StartupTo start up the FTP server, perform the following operation:l Click FTP Tool on the tool bar of the LMT window to download the executable application

file SFTPServer.exe. Then double-click the executable file to start the FTP server.

NOTE

Users cannot use the FTP server if they log in to the LMT through a proxy server.

InterfaceFigure 2-3 shows the FTP server interface.



18

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


User name The user name of the FTP server is admin by default.

Password The password of the FTP server is hwbs@com by default.NOTE

To change the password, enter the old password to perform security check.

Working directory Working directory after the FTP server is started.NOTE

You are only allowed to visit files under the directory when using the FTPclient.

Port number Indicates the number of the port used by the FTP server to interceptthe information on the network.NOTE

To query the port number, run the LST FTPSSRV command to query thesetting for the Command Port of FTPS Server. If an incorrect port numberis used, the LMT cannot be connected to the FTP server.

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



19

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



20

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 Tool

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

Prerequisites

LMT offline MML server is started.

Procedure

Step 1 Select a method for logging in to LMT offline MML based on whether the LMT offline 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.



21

NOTE

l You can switch display language between English and Chinese by clicking the language-switchingbutton in the top right corner of the login window.

l You can restore the default setting used during installation by clicking Reset.

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

----End

Introduction to the LMT Offline MML Interface

This section describes the LMT offline MML interface. Logging in to LMT offline MML 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 an MMLcommand to load it to the Command Input box.

Search Enter a keyword to search for an MML command.



22

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

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

Making MML Scripts Offline

This section describes how to make MML scripts offline.

Procedure

Step 1 Log in to LMT offline MML. For detailed operations, see Logging In to and Out of 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



23

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.



24

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.



25

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 TrafficRecording Review ToolThe TrafficRecording 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 > TrafficRecordingReview Tool on the LMT PC.

InterfaceFigure 2-8 displays the interface of the TrafficRecording Review Tool.

Figure 2-8 Interface of the TrafficRecording Review Tool



26

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

Table 2-12 Components of the TrafficRecording 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.

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 operationrights to the file manager.

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

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



27

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.



28

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.

When the bandwidth is 2 Mbit/s, it is recommended that the number of files downloaded at the same time donot exceed 100 and that of files uploaded do not exceed 10.

Task List Area

This area displays relevant information about current tasks. You can process tasks in the 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.

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.



29

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


30

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.

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.

Initial Password SettingThe 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 PasswordsAll 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.



31

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.

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 the



32

BSC6900 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 thesystem and cannotbe changed.USER G_0, G_2, G_4,

G_6, G_7, G_8,G_9, G_10,G_11, G_12,G_13, and G_14

l Operation rights of 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



33

Level AssignedCommandGroup

Operation Right Description

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

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.



34

Permissions to Set the Operation Time Limit

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

PrerequisitesYou 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



35

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.

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.


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.



36

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


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.

NOTE

It is recommended that you change the password at your first login and then change the password every threemonths.

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



37

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.


Procedure

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


Procedure

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

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

----End

3.4.3 Changing the Commands in a Command 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



38

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


39

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



40

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.

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

Table 4-1 Actions of the MML commands

Action Description

ACT Activate

ADD Add

ADT Audit

BEG Begin

BKP Back up

BLK Block

CHK Check

CLR Clear

CMP Compare

COL Collect

CON Confirm

DEA Deactivate

DSP List

EST Establish

EXP Export

FMT Format

FOC Obtain

HO Hand over

INH Inhibit



41

Action Description

INS Install

LCK Lock

LOD Load

LOP Loopback test

LST List

MOD Modify

PING Ping

REL Release

REQ Request

RUN Run

RMV Remove

RST Reset

SET Set

STR Start/Open

STP Stop/Close

STA Collect statistics

SWP Swap

SYN Synchronize

TRC Trace

UBL Unblock

UIN Uninhibit

ULD Upload

ULK Unlock

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

Figure 4-1 shows the MML command window.



42

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.

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.



43

Number Field Description

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 data

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

l When a user occupies the data configuration rights for a long time, 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 ornetwork problems, you can perform rollback to restore the configurations so that normaloperation of the BSC6900 is restored as early as possible.

Definition of Configuration RollbackDuring data configuration, a rollback point is used to mark a data configuration action.

You can select a rollback point corresponding to the expected data configuration status,permitting a rollback to any point of the configuration. (You can run the ADDROLLBACKPOINT command to configure the rollback point.)



44

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

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.



45

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 CommonMaintenance tab page.

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

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

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


l Selecting an MML command from the MML Command navigation tree

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

2. Specify the parameter values to run the command.

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

1. Copy the script of an MML command with the required parameter values, and pasteit in the Manual Edit area.


----End

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

Context

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

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

l Immediate batch processing: The batch file is run immediately.



46

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

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

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

Prerequisitesl 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:



47

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. You can run the MOD FTPPWD command to change the password.

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

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

ContextThe syntax check checks the following types of error:

l Missing colon



48

l Missing semicolon

l Incorrect MML command

l No authority to execute a correct MML command

l Redundant parameters

l 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 an MML command line in the batch file for error analysis by selecting it, right-clickingit, and choosing Analyze Current Line from the shortcut menu.

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

Step 4 Click Close to end the operation.

----End

Follow-up Procedure

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

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

Prerequisites

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.



49

Figure 4-2 Setting MML Parameters

Step 2 Set the parameters as required.

Step 3 Click OK to save the settings.

----End

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


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

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.



50

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

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



51


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

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

CMCTRLSW command.

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

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

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

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

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.

ProcedureStep 1 Check whether the data configuration rights are assigned to another user. For details, see 4.6

Querying Data Configuration Rights.l If no user is currently assigned with the data configuration rights, go to Step 2.l If the data configuration rights are already assigned to another user, go to Step 2 after the

user releases the data configuration rights.

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

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

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



52

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.

Prerequisitesl 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



53

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.

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



54

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



55

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


56

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.

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.

NOTE

l The record of a cleared alarm is stored in the OMU database and can be queried.l In scenarios where equipment is being deployed, commissioned, upgraded, swapped, cut over, or the

capacity of a base station is expanded, operations cause a great number of alarms to be reported. Thereis no special mechanism to handle such alarms. Large in number and short in existence period, thesealarms make real fault alarms inconspicuous and therefore disturb normal network monitoring. Tosolve the problem discussed above, Huawei puts forward the concept of "engineering alarms". Withthe concept, alarms in scenarios of engineering maintenance are identified and handled as special cases.In this way, delicacy management of alarms is implemented and fault OM efficiency of the 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 severities: critical, major, minor, and warning.

Table 5-2 describes the four severities of alarms.



57

Table 5-2 Alarm severities

Alarm Severity Definition HandlingRequirement

Critical 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 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 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 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-Event TypeThe alarms can be classified into 15 types based on different event type.

l Power: alarms related to the power system

l Environment: alarms related to equipment room environment, such as temperature,humidity, and door sensor

l Signaling: alarms related to the signaling system

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

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

l Software: alarms related to software

l Running: alarms generated during the operation of the BSC

l Communication: alarms related to the communication system, such as alarms between theBSC6900 host and the OMU

l QoS: alarms related to QoS

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

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

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



58

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 expirationl 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 ShieldedA 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 Flag

The 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 Unmodified



59

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

Alarm Cleared Flag

The 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 Cleared

The fault alarm is not cleared.

l Cleared

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

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.



60

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.


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.



61


Procedure

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

NOTE

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

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

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

----End

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


Procedure

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

If... Then...

The filter is listed, Go to Step 2.

The filter is not listed, End this operation.

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

----End

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




62

Procedure

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

----End

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

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

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

Prerequisites


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.



63

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.


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.


ContextYou can set the following query conditions:l Alarm Typel Alarm Severityl Alarm Timel Maintenance Mode 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.



64


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

Prerequisites


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.



65

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 results

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

Procedure

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

Step 2 Click the Query Alarm Configuration tab and click Query Setting. The Alarm 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 a configuration item and click Modify AlarmConfiguration, or right-click in the Result area and choose Modify Alarm Configuration from theshortcut menu.

----End



66

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.

Prerequisites


Procedure

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

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.

Prerequisites


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



67

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.



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.


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.



68

----End

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

Prerequisites


Procedure

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

NOTE

l On the Browse Alarm/Event tab page, the alarms are displayed in real time. Cleared alarms aredisplayed in gray 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.

Prerequisitesl 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



69

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.

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



70

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

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

----End



71

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 .csv 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 File Manager or FTP Client tool to download to the LMTPC an exported operation log that is saved in the directory OMU active workspace installationdirectory\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 Obtaining Running Logs

BSC6900 UMTSLMT User Guide 6 Log Management


72

This section describes how to use File Manager or FTP Client to download to the LMT PC arunning log uploaded to bam\common\fam\famlog.

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, security logs, alarm logs and others.



73

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.




74

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 File Manager or FTP Client tool to download to the LMTPC an exported operation log that is saved in the directory OMU active workspace installationdirectory\ftp.

Prerequisitesl You have logged in to the LMT with an account authorized for this operation.l You are authorized to download files from the OMU to the LMT PC.

Procedurel Using File Manager

1. Run the EXP LOG command to export the corresponding operation log. In this step,set Log Type to OPTLOG(Operation Log) and other parameters to appropriatevalues.

NOTE

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

2. Click File Manager on the LMT main page to start the file manager.3. In the File Navigation Area, type OMU active workspace installation directory

\ftp. In the File List Area, select the operation log exported in Step 1. Then, clickDownload to download the log to the LMT PC.



75

l Using FTP Client1. Run the EXP LOG command to export the corresponding operation log. In this step,

set Log Type to OPTLOG(Operation Log) and other parameters to appropriatevalues.

NOTE

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

2. Choose Start > All Programs > Huawei Local Maintenance Terminal > FTPClient. The FTP Client is started.

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

NOTE

The FTP user name and password is set when the OMU is installed. The FTP user name isFtpUsr by default.

4. Click Enter to connect the OMU. The connecting status is displayed in theConnection tips pane.

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

6. Based on the file name, double-click the operation log file to download it to the LMTPC.

7. When the download is complete, choose System > Exit or click the close button toexit the FTP Client.

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


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



76

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.


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 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 are 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 security 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.8 Obtaining Running LogsThis section describes how to use File Manager or FTP Client to download to the LMT PC arunning log uploaded to bam\common\fam\famlog.



77

Prerequisites

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

Procedurel Using File Manager

1. Run the ULD LOGTOOMU command and enter the subrack number to upload thecorresponding running log to the OMU.

NOTE

l The running log is named in the format BSCID_subrack number/Log/yyyy/mm/dd/hh/mm/ss.zip. For example, if a running log of Extended Processing Subrack (EPS) 3 isuploaded to the OMU of BSC 1 at 17:19:47 of November 7, 2011, the log is namedBSC0001_03Log20111107171947.zip. BSC0001_03Log20111107171947.zip indicatesthat the log has been uploaded and compressed. BSC0001_03Log20111107171947.tmpindicates that the log is being uploaded.

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

2. Click File Manager on the LMT main page to start the file manager.

3. In the File Navigation Area, choose corresponding nodes to navigate to bam\common\fam\famlog. In the File List Area, select the running log uploaded in Step1. Then, click Download to download the log to the LMT PC.

l Using FTP Client

1. Run the ULD LOGTOOMU command and enter the subrack number to upload thecorresponding running log to the OMU.

NOTE

l The running log is named in the format BSCID_subrack number/Log/yyyy/mm/dd/hh/mm/ss.zip. For example, if a running log of EPS 3 is uploaded to the OMU of BSC 1 at17:19:47 of November 7, 2011, the log is named BSC0001_03Log20111107171947.zip.BSC0001_03Log20111107171947.zip indicates that the log has been uploaded andcompressed. BSC0001_03Log20111107171947.tmp indicates that the log is beinguploaded.

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

2. Choose Start > All Programs > Huawei Local Maintenance Terminal > FTPClient. The FTP Client is started.

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

NOTE

The FTP user name and password are set when the OMU is installed. The FTP user name isFtpUsr by default.

4. Click Enter to connect to the OMU. The connecting status is displayed in theConnection tips pane.

5. After the connection is set up successfully, choose corresponding nodes to navigateto bam\common\fam\famlog in the server file list pane. All files in the path aredisplayed in the server file list pane.

6. Based on the file name, double-click the running log to be downloaded to downloadit to the LMT PC.



78

7. When the download is complete, choose System > Exit or click the close button toexit the FTP Client.

----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, security logs, alarm logs and others.

Prerequisites


Procedure

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

NOTE

l version_a is the active workspace of OMU. When the active workspace of the OMU is version_b, thestorage path of the following logs changes into version_b accordingly.

l The log files that are not compressed in the BZ2 format in the OMU active workspace installation directory\common\fam\famlog and the OMU active workspace installation directory\common\fam\famlogfmt directories will not be saved.

Table 6-1 Description about logs

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.

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(SwitchInformation forPerformance)

/ Reserved parameter value.



79


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.



80


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.

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.



81


SYSFAULT_LOG(SYSFAULT Log)

/bam/common/fam/famlogfmt/sysfault/

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

----End



82

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. When OMU boards perform an active/standby switchover, monitoring can be restarted only 30 minutes after the switchover.

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


83

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.

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.3. After receiving the command, the debugging module records the filter parameters of the

trace data in the filter table and notifies the service module.4. The service module updates the local filter table according to the message from the

debugging module.

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



84

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

7.2.1 Tracing OS MessagesThis section describes how to trace messages between the exchange module of the OMU andinternal modules of a board or between internal modules of different boards.




85

Context

This task can be performed to trace the sent and received messages between two modules ormessages sent from and received by the same module.

CAUTIONOnly ADMINISTRATOR-level users are authorized for performing Tracing OS Messagesbecause it involves private information of users.

Procedure

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

Step 2 On the Trace Navigation Tree pane, expand Trace > Device Commissioning. Double-clickOS Trace.

Step 3 In the OS Trace dialog box, set the parameters as required, and click Submit. The trace datapane displays the traced message flow.

----End

7.2.2 Tracing Redirected MessagesThis section describes how to redirect the messages printed through the serial port of a specifiedsubsystem to the message browse window of the LMT.

Prerequisites


Context

CAUTIONFor a subsystem, only one task of tracing redirected messages can be started. When manymessages are printed through the serial port, the task of tracing redirected messages may affectthe performance of the system.Only ADMINISTRATOR-level users are authorized for performing Tracing RedirectedMessages.

Procedure


Step 2 On the Trace Navigation Tree pane, expand Trace > Device Commissioning. Double-clickRedirected Trace.



86

Step 3 In the Redirected Trace dialog box, set the parameters as required, and click Submit. The tracedata pane displays the traced message flow.

----End

7.2.3 Capturing PacketsThis section describes how to capture packets and helps locate transmission channeldisconnection and packet loss by analyzing the packet header.

Prerequisitesl You have logged in to the LMT.

l The communication between the LMT and the BSC is normal.

Contextl The following problems can be located by capturing packets:

– the controller does not receive the packet.

– After entering the interface board, the packet is discarded by the board without beingsent to other boards in the system.

– The packet is sent to other non-interface boards, which then discard the packet.

l When packets are discarded between two boards or connection cannot be establishedbetween two boards, you can check whether the correct packets are sent to and received byinterface boards and other boards in the system by capturing backplane packets. Then youcan quickly determine where the problem lies, which may be in an interface board or anyother board (DPU/XPU board) in the system.

l The following types of packet capturing are supported:

– Panel Ethernet packet capturing.

– Backplane Ethernet packet capturing.

– Panel Ethernet + backplane Ethernet packet capturing.

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

l Only the header of the user plane packet can be captured, not including the payload of thepacket.

Procedure

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

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

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

Step 4 Click Submit, to start capturing packets. For the specific capturing duration, see the value ofTrace Time (OMU time) in the Packet Capture interface.



87

NOTE

l Panel Ethernet packet capture and backplane Ethernet packet capture can be supported simultaneously. Ifyou only need to capture the panel Ethernet packet, set PortType(Inner) to Inner Invalid or set PortType(Outer) to Outer Invalid.

l To capture panel Ethernet packets, set PortType (Outer) to Ethernet Frame, and set the parameters in theOuter tab.

l To capture panel Ethernet packets, set PortType (Inner) to Ethernet Frame, and set the parameters in theInner tab.

InterfaceParameter

Description

Basic Mode: just enter the basic parameters (subrack number and physical slot number) tostart the packet capturing function. Therefore, this is defined as the basic mode. Under thebasic mode, only Panel Ethernet packet capturing is supported, and backplane Ethernet packetcapturing is not supported.

Subrack No Indicates the number of the subrack which houses the interface board.

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

Port No Indicates the number of the port on the interface board panel.

Scene Select Indicates the scene under which packets are captured are differentiatedby protocol type.

Intercept Length Each Ethernet frame captured (especially for long packets) is reduced tothe "Intercept length" of the packet, the rest of which is not submitted. Ifthe captured packet is shorter than the "Intercept length", the actual lengthcaptured prevails.

VLAN Tag Indicates whether the data packet carries a VLAN ID.Tagged: The data packet carries a VLAN ID.Untagged: The data packet does not carry a VLAN ID.Tagged/Untagged: The data packet carries or does not carry a VLANID.For the FG2a and GOUa, VLAN Tag can be set only to TaggedorUntagged. That is, you cannot capture packets with VLAN IDs and thosewith no VLAN IDs at the same time.

Trace Time Start Time: The start time and end time of the trace task.Trace Time (min) : duration of the tracing task. The unit is minutes.

Advanced Mode: in addition to the basic parameters (subrack number and physical slotnumber), several other parameters are required to start the packet capturing function, whichis defined as the advanced mode. The advanced mode supports panel Ethernet packetcapturing, backplane Ethernet packet capturing and panel Ethernet + backplane Ethernetpacket capturing.



88

InterfaceParameter

Description

PortType (Outer) Indicates capturing of packets at the port of the interface board panel.Outer Intercept length: Each Ethernet frame captured (especially forlong packets) is reduced to the "Intercept Length" of the packet, the restof which is not submitted. If the captured packet is shorter than the"Intercept Length", the actual length captured prevails.

Outer PortNumber

Indicates the number of the port on the interface board panel.

Outer TraceDirection

l In: tracing packets entering the port of the interface board panel fromthe outside.

l Out: tracing packets sent from the port of the interface board panel.l Both: tracing packets in the two directions simultaneously.

Outer PeerMACAddress

Specifies the peer MAC address of the Ethernet frame to be captured.This is the destination MAC address of the packet when "Out" is selectedfor the "outer trace direction"; or the source MAC address when "In" isselected for the "outer trace direction".If left blank, it indicates capturing of all packets at the peer MAC address.

Outer LocalIP Address

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

Outer PeerIP Address

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

Local UserDatagramProtocol(UDP) PortNo

Specifies the local User Datagram Protocol (UDP) port number of the IPpacket to be captured.This is the source User Datagram Protocol (UDP) port number of thepacket when the "Out" is selected for the "outer trace direction"; or thedestination User Datagram Protocol (UDP) port number when the "In"is selected for the "outer trace direction".If left blank, it indicates capturing of all packets at the local UserDatagram Protocol (UDP) port.



89

InterfaceParameter

Description

Peer UserDatagramProtocol(UDP) PortNo

Specifies the peer User Datagram Protocol (UDP) port number of the IPpacket to be captured.This is the destination User Datagram Protocol (UDP) port number ofthe packet when the "Out" is selected for the "outer trace direction"; orthe source User Datagram Protocol (UDP) port number when the "In" isselected for the "outer trace direction".If left blank, it indicates capturing of all packets at the peer UserDatagram Protocol (UDP) port.

PortType (Inner) Indicates capturing of packets at the port of the interface boardbackplane.Inner Intercept length: Each Ethernet frame captured (especially forlong packets) is reduced to the "Intercept length" of the packet, the restof which is not submitted. If the captured packet is shorter than the"Intercept length", the actual length captured prevails.

Inner PortNumber

The number of the port on the interface board backplane.

Inner TraceDirection

l In: tracing the packets entering the interface board backplane fromthe SCU board.

l Out: tracing packets sent from the interface board backplane to theSCU board.

l Both: tracing packets in the two directions simultaneously.

Inner PeerMACAddress

Specifies the peer MAC address of the Ethernet frame to be captured.This is the destination MAC address of the packet when the "Out" isselected for the "inner trace direction"; or the source MAC address whenthe "In" is selected for the "inner trace direction".If left blank, it indicates capturing of all packets at the peer MAC address.

Inner Peer IPAddress

Specifies the peer IP address of the IP packet to be captured.This is the destination IP address of the packet when the "Out" is selectedfor the "inner trace direction"; or the source IP address when the "In" isselected for the "inner trace direction".If left blank, it indicates capturing of all packets at the peer IP address.

----End

Follow-up Procedurel You can manage packet capture in Manage Trace File on the Trace tab. You can query,

stop, delete or restart a packet capture task.l After packet capturing is complete, packet capturing log files (for example, /bam/common/

fam/trace/16778026_ packet capturing _20120927_201909.log.zip) are created and savedon the OMU.



90

NOTE

Packet capturing results are created after the task is complete.

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.

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. TheIu Interface Trace dialog box is displayed, as shown in Figure 7-2.



91

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.

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.



92

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 MessagesThis section describes how to trace Message Transfer Part Level 3 (MTP3) messages, whichcan be traced on the Iu interface. The traced messages include upper layer user messages suchas QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling link testmessages, 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

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

Procedure





93


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



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


----End






94

Figure 7-5 Results of tracing MTP3 messages




Tracing QAAL2 MessagesThis section describes how to trace QAAL2 messages, which can be traced on the Iu interface.QAAL2 message tracing helps to monitor interworking of QAAL2 messages and locateestablishment failure and abnormal release of channels on the AAL2 user plane on the Iuinterface.


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

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

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




95


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,

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

----End






96

Figure 7-7 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 interface. SAAL message tracing helps to monitor interworking of SAALmessages on the Iu interface and locate unavailable SAAL links.


ContextNOTE

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

Procedure





97


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSAAL under Trace Type.l Active CPUS Subsystem: only one CPUS subsystem can be selected for SAAL tracing.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

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,



98

task time, RFN, subrack number, slot number, subsystem number, message direction,message type, message source, user ID, and message content.




Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iu interface. SCTP message tracing helps to monitor interworkingof SCTP messages on the Iu interface and locate unavailable 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.

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

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

Procedure





99


Step 3 In the Iu Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP under Trace Type.l Active CPUS Subsystem: only one CPUS subsystem can be selected for SCTP tracing.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


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, including



100

the 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



about the traced message.

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

Tracing M3UA Messages

This section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iu interface. M3UA message tracing facilitates troubleshooting of theproblem that M3UA links are unavailable but the corresponding IP links are available.

Prerequisites


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

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

Procedure





101


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,


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





102


Figure 7-12 Results of tracing M3UA messages




Tracing SCCP MessagesThis section describes how to trace Signaling Connection Control Part (SCCP) messages, whichcan be traced on the Iu interface. SCCP messages include the connection-oriented messages andthe connectionless messages. SCCP message tracing helps to monitor interworking of SCCPmessages and locate establishment failure and abnormal release of channels on the Iu interface.


ContextNOTE

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

Procedure





103


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






104

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

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.



105

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



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



106

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 MessagesThis section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iupc interfaces. M3UA message tracing facilitates troubleshooting of theproblem that M3UA links are unavailable but the corresponding IP links are 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


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iupc Interface Trace. TheIupc Interface Trace dialog box is displayed, as shown in Figure 7-16.



107


Step 3 In the Iupc 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





108






Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iupc interfaces. SCTP message tracing helps to monitor interworkingof SCTP messages on the Iupc interfaces and locate unavailable SCTP links.




NOTE


Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Iupc Interface Trace. TheIupc Interface Trace dialog box is displayed, as shown in Figure 7-18.



109


Step 3 In the Iupc Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP under Trace Type.l Active CPUS Subsystem: only one CPUS subsystem can be selected for SCTP tracing.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


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



----End



– A window shown in Figure 7-19 is displayed if the Report trace mode is selected. Themessage browsing window displays information about each traced message, including



110







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 Interface

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

Prerequisites


Context

For 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. TheIur Interface Trace dialog box is displayed, as shown in Figure 7-20.



111

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.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


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






112





Tracing MTP3 MessagesThis section describes how to trace Message Transfer Part Level 3 (MTP3) messages, whichcan be traced on the Iur interfaces. The traced messages include upper layer user messages suchas QAAL2 and Signaling Connection Control Part (SCCP) messages, MTP3 signaling link testmessages, 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

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

Procedure





113


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



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


----End






114

Figure 7-22 Results of tracing MTP3 messages




Tracing QAAL2 MessagesThis section describes how to trace QAAL2 messages, which can be traced on the Iur interfaces.QAAL2 message tracing helps to monitor interworking of QAAL2 messages and locateestablishment failure and abnormal release of channels on the AAL2 user plane on the Iurinterfaces.





NOTE






115


Step 3 In the Iur 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,


----End






116





Tracing SAAL MessagesThis section describes how to trace Signaling ATM Adaptation Layer (SAAL) messages, whichcan be traced on the Iur interfaces. SAAL message tracing helps to monitor interworking ofSAAL messages on the Iur interfaces and locate unavailable SAAL links.


ContextNOTE


Procedure





117


Step 3 In the Iur Interface Trace dialog box, set parameters in the default Basic tab page and selectSAAL under Trace Type.l Active CPUS Subsystem: only one CPUS subsystem can be selected for SAAL tracing.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

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


----End






118





Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iur interfaces. SCTP message tracing helps to monitor interworkingof SCTP messages on the Iur interfaces and locate unavailable SCTP links.




NOTE


Procedure





119


Step 3 In the Iur Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP under Trace Type.l Active CPUS Subsystem: only one CPUS subsystem can be selected for SCTP tracing.l DPC Configuration: can be set to All DPC or Specified DPC. If Specified DPC is selected,


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

NOTE



----End



– A window shown in Figure 7-27is displayed if the Report trace mode is selected. Themessage browsing window displays information about each traced message, including



120







Tracing M3UA Messages

This section describes how to trace MTP3-User Adaptation Layer (M3UA) messages, whichcan be traced on the Iur interfaces. M3UA message tracing facilitates troubleshooting of theproblem that M3UA links are unavailable but the corresponding IP links are available.

Prerequisites


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





121


Step 3 In the Iur 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





122






Tracing SCCP MessagesThis section describes how to trace Signaling Connection Control Part (SCCP) messages, whichcan be traced on the Iur interfaces. SCCP messages include the connection-oriented messagesand the connectionless messages. SCCP message tracing helps to monitor interworking of SCCPmessages and locate establishment failure and abnormal release of channels on the Iur interfaces.


ContextNOTE

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

Procedure





123


Step 3 In the Iur 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






124





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


ContextFor 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. TheIub Interface Trace dialog box is displayed, as shown in Figure 7-32.



125

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 selectNBAP under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.l NodeB Trace Type

– All NodeB: traces NodeB Application Part (NBAP) messages of all NodeBs.– All Ports of a NodeB: traces NBAP messages of a specified NodeB on all ports. Both

NodeB Control Ports (NCPs) and Communication Control Ports (CCPs) are to be traced.– Specified Port of a NodeB: traces NBAP messages of a specified NodeB on a specified

type of port. Either NCPs or CCPs are to be traced.

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


----End






126

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 Iub interfaces. SAAL message tracing helps to monitor interaction of SAALmessages on the Iub interface and locate faulty SAAL links.


ContextNOTE


Procedure





127


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


l NodeB Trace Type

– All NodeB: traces NodeB Application Part (NBAP) messages of all NodeBs.

– All Ports of a NodeB: traces NBAP messages of a specified NodeB on all ports. BothNodeB Control Ports (NCPs) and Communication Control Ports (CCPs) are to be traced.

– Specified Port of a NodeB: traces NBAP messages of a specified NodeB on a specifiedtype of port. Either NCPs or CCPs are to be traced.

Step 4 On the SAAL tab page, specify SAAL Link No. and select Trace Object.

l Subrack No. of SAAL: indicates the number of the subrack where the SAAL link to be tracedis located.

l Slot No. of SAAL: indicates the number of the slot where the SAAL link to be traced islocated.

l SAAL Link No.: indicates the number of the SAAL link to be traced.

NOTE

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


----End



128


– No traced message will be displayed on the LMT if the Save to OMU trace mode isselected. You can view the tracing result saved on the OMU by referring to BrowsingTraced Messages Offline.

– A window is displayed if the Report trace mode is selected. The message browserdisplays information about each traced message, including the task number, task time,RFN, subrack number, slot number, subsystem number, message direction, messagetype, message source, user ID, and message content.


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

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

Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messages,which can be traced on the Iub interfaces. SCTP message tracing helps to monitor interworkingof SCTP messages on the Iub interfaces and locate unavailable SCTP links.




NOTE


Procedure





129


Step 3 In the Iub Interface Trace dialog box, set parameters in the default Basic tab page and selectSCTP under Trace Type.l For description of Trace Mode, see 7.1.3 Trace Mode.l NodeB Trace Type

– All NodeB: traces NodeB Application Part (NBAP) messages of all NodeBs.– All Ports of a NodeB: traces NBAP messages of a specified NodeB on all ports. Both

NodeB Control Ports (NCPs) and Communication Control Ports (CCPs) are to be traced.– Specified Port of a NodeB: traces NBAP messages of a specified NodeB on a specified

type of port. Either NCPs or CCPs are to be traced.

Step 4 In the SCTP tab page, specify SCTP Link No. and select SCTP Message.l Subrack No. of SCTP: indicates the number of the subrack where the SCTP link to be traced

is located.l Slot No. of SCTP: indicates the number of the slot where the SCTP link to be traced is located.l SCTP Link No.: indicates the number of the SCTP link to be traced.

NOTE



----End




130


– A window shown in Figure 7-36is 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.





Tracing QAAL2 MessagesThis section describes how to trace QAAL2 messages, which can be traced on the Iub interface.QAAL2 message tracing helps to monitor interworking of QAAL2 messages and locateestablishment failure and abnormal release of channels on the AAL2 user plane on the Iubinterface.





NOTE




131

Procedure




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

----End






132





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.

Procedure




133

Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > Uu Interface Trace. TheUu 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






134

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 MessagesThis section describes how to trace messages indicating missing intra-frequency neighboringcell relationship.

Prerequisitesl You have logged in to the LMT with an account authorized for this operation.l The parameter switch for detecting missing neighboring cell relationship is set to ON. The

setting can be queried by running the LST UNCELLDETECTSWITCH command.

Procedure




135

Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > MNCDT Trace. TheMNCDT 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.



----End










136

Tracing Inter-Frequency MNCDT MessagesThis 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 relationshipl Downlink UARFCN: indicates the downlink UARFCN of the cell to be traced for detecting

missing neighboring relationshipl Start of Primary Scrambling Code: indicates the minimum scrambling code for an

MNCDT task



137

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 MessagesThis section describes how to trace messages indicating missing inter-RAT neighboring cellrelationship.



Procedure





138


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 to which the overlapping UARFCNs between bandsDCS1800 and PCS1900 are attributed. It can be set either DCS1800 or PCS1900 if theneighbor cell is not DCS1800 or PCS1900 cell.

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



139







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.


CAUTIONAs private information of users is revealed during the tracing, only G1 command group users(ADMINISTRATOR and CUSTOM users with G1 command group permission) are allowed toperform UE tracing task.

ContextWhen initiating UE tracing, users need to select interfaces and types of message to be traced andidentify a UE by IMSI, MSISDN, IMEI, TMSI, or P-TMSI. Users can trace signaling messagesof the UE on Iu, Iur, Iub, and Uu interfaces or on a specified interface.

There is no way to avoid that some user data such as International Mobile Subscriber Identity(IMSI) will be used during problem location and resolution. This function provides ananonymous data processing method. You are recommended to comply with local laws whenexecuting the task and take ample measures to fully protect user data, such as enabling theanonymous function and deleting the folder that saves track records after you finish processingdata.

NOTE

A maximum of 12 UE tracing tasks can be performed simultaneously and a maximum of six tasks fortracing internal messages can be performed simultaneously.



140

Procedure


Step 2 Under Trace Navigation Tree, choose Trace > UMTS Services > UE Trace. The UE Tracedialog 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/MSISDN/IMEI/TMSI/P-TMSI: identifies the UE to be traced. Choosing to trace the

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



141

NOTE

l When entering IMSI, check whether IMSI data to be entered must be anonymous by running the LSTUSERIDANONSWITCH command and querying User Identity Anonymity Switch.

l If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and anonymous IMSIdata must be entered in IMSI. The anonymous IMSI data is the IMSI data encrypted by theHMACUtil using the cipher key.

l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI datais directly entered in IMSI.

l Change the anonymous policy and cipher key on the M2000 by choosing Monitor > Signaling >Anonymous Policy Management > Anonymous Cypher Key Management. For details, see M2000Fault Management User Guide.

l If you change the anonymous policy or cipher key of a started tracing task, you need to restart the tracingtask. Otherwise, the tracing task becomes invalid.

l For details about how to obtain the HMACUtil, contact Huawei technical support.

l Filter traced messages by setting parameters in the IUR, IUB, IU, and UU tab pages.l Monitor tab page: includes 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.

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

l Debug Mode: indicates a maintenance mode used for tracing communication messagesbetween units of the RNC. Tracing tasks configured on Other, Other1, and Bind tab pagestake effect only when Debug Mode is selected.

– Other tab page

– Layer 2 data transfer Periodic Report: Selecting it enables statistics on packetsreceived and sent at layer 2 to be periodically reported to the LMT.



142

– Transport Data Periodic Report: Selecting it enables statistics on packets receivedand sent by interface boards to be periodically reported to the LMT. Analysis of thesestatistics helps users to determine whether a fault occurs on the RNC side.

– Report Period: indicates the period for reporting Layer 2 data transfer PeriodicReport.

– L2 Data Report area: includes parameters that enable statistics on packets receivedand sent at layer 2 to be reported to the LMT.– L2 SRB Data Report: enables packets received in the UL and sent in the DL on

the control plane at the Frame Protocol (FP) layer to be reported to the LMT inmessages.

– Report time(s): indicates the period for reporting L2 Data Report.– L2 TRB Packet Header Report(IUB interface): Selecting it enables frame

headers received in the UL or sent in the DL on the user plane at the FP layer tobe reported to the LMT.

– L2 TRB Packet Header Report(IU interface): Selecting it enables packet TCP/IP headers sent in the UL or received in the DL on the user plane at the RLC layerto be reported to the LMT.

– Auto Ping: Selecting it enables the RAN to send the UE Internet Control MessageProtocol (ICMP) packets. This function helps users to determine whether datadisconnection exists between a server and the RNC or a low rate on the server sidecauses the low UE rate.– Ping Interval (0.1ms): indicates the interval at which ICMP packets are sent.– Packet Length(bytes): indicates the payload length of the ICMP packets.

– Voice Analysis: When this check box is selected, the LMT records the test results ofvoice frames over the Iu interface, for example, the frame type, mean opinion score(MOS), and speech noise detection result. Based on the recorded test results, themaintenance personnel can judge the voice quality. The MOS is saved in the followingpath by default: /bam/common/fam/speechmos/.– Sampling No.: This parameter indicates the voice quality sample to be used.

Currently, the valid value range of this parameter is 0 to 8. The value of thisparameter depends on the selected test tool. It is set to 0 only when no voice qualitysample is used. In this case, no test tool is required.

– QAAL2_protocol_tracing: Selecting it enables tracing of real-time QAAL2 standardprotocol messages. Information elements carried in the messages help determinewhether QAAL2 message interaction between NEs is successful.

– RT_BASIC_INFO: Selecting it enables the following information to be traced: Real-time RRC service state of the UE such as CELL_DCH and CELL_FACH, connectionmode over the Iu interface (idle or connected mode), the homing RNC (SRNC orDRNC), and cells in the active set of the UE.

– RT_COMM_CONTEXT_INFO: Selecting it enables tracing of real-timeinformation such as the serving NodeB, communication context ID of the controllingradio network controller (CRNC), URNTI, CRNTI, and UE ID.

– RT_INST_RESOURCE_INFO: Selecting it enables tracing of real-time index ofresources that are allocated to the UE, for example, system memory.

– RT_RAB_PARA_INFO: Selecting it enables tracing of real-time radio access bearer(RAB) information such as traffic class, maximum rate, and guaranteed bit rate (GBR).

– SCCP Protocol tracing: Selecting it enables tracing of real-time SCCP standardprotocol messages. SCCP is short for Signaling Connection Control Part. Information



143

elements carried in the messages help determine whether SCCP message interactionbetween NEs is successful.

– Other1 tab page– Internal Event: Selecting it enables tracing of internal events, communication

messages between RNC units.– FP PM Report: Selecting it enables transmission statistics at the FP layer to be

reported to the LMT.– IUUP Uplink Loop: Selecting it enables Iu user plane (IuUP) data that would be

transmitted to the CN to be transmitted in the downlink direction. This function isused for isolating other network elements during problem analysis, which facilitateslocation of speech quality problems.

– IUUP Downlink Loop: Selecting it enables IuUP data received from the CN to bereturned to the CN. This function is used for isolating other network elements duringproblem analysis, which facilitates location of speech quality problems.

– PDCP Trace: Selecting it enables information about Packet Data ConvergenceProtocol (PDCP) header compression to be reported to the LMT.

– FP Trace: Selecting it enables control frames on the IuUP or at the FP layer to bereported to the LMT.

– L2 FL protocol Trace Report: Selecting it enables protocol parameters on the userplane to be reported to the LMT.

– Flow Trace: Selecting it enables specified data flow of the UE on the interface boardto be reported in packets to the LMT. If RNC data flow is blocked, the problem maylie in the RNC, the interface board, or the peer end. You can use this function to excludesome problems.

CAUTIONNote that selecting BackPanel Trace or FrontPanel Trace may lead to flow control,so exercise caution in this selection.

– Flow Trace Interface Type: indicates the interface to have its data flow traced.– Flow Trace Bearer Type: indicates the channel to have its data flow traced.– Flow Trace Service Type: indicates the service to have its data flow traced.– BackPanel Trace: traces data flow sent or received on the backplane of the

interface board.– BackPanel Trace: traces data flow sent or received on the panel of the interface

board.– Bind tab page: is used for binding the UE to a DSP or path or transmission resource pool.

This helps users to determine whether a DSP or path fault exists.– DSP

– Subrack No.: indicates the number of the subrack corresponding to the DSP.– Slot No.: indicates the number of the slot corresponding to the DSP.– DSP No.: indicates the number of the DSP.

– Iub



144

– Path ANI No.: indicates the Adjacent Node Identifier (ANI) corresponding to theIub path.

– Type: indicates the transport type of the Iub path.

– Path ID: indicates the number of the Iub path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound channel identifier (CID) on theIub path in ATM transmission mode or the number of the bound User DatagramProtocol (UDP) port in IP transmission mode.

– Iucs

– Path ANI No.: indicates the ANI corresponding to the Iu-CS path.

– Type: indicates the transport type of the Iu-CS path.

– Path ID: indicates the number of the Iu-CS path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iu-CS path in ATMtransmission mode or the number of the bound UDP port in IP transmission mode.

– Iur

– Path ANI No.: indicates the ANI corresponding to the Iur path.

– Type: indicates the transport type of the Iur path.

– Path ID: indicates the number of the Iur path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iur path in ATMtransmission mode or the number of the bound UDP port in IP transmission mode.

– Iups

– Path ANI No.: indicates the ANI corresponding to the Iu-PS path.

– Type: indicates the transport type of the Iu-PS path.

– Path ID: indicates the number of the Iu-PS path.

– Message Setting: Clicking this node in the navigation tree enables users to selectmessages that need to be traced during UE tracing, cell tracing, and IOS tracing. Tracingthese messages in real time on the LMT facilitates debugging and problem analysis. Thisfunction takes effect only when the debug mode is selected.

– UI_FAM_UT_CELL_INFO: Selecting it enables the LMT to display values ofreceived total wideband power (RTWP) and transmitted carrier power (TCP) in a cell.Analysis of these values helps users to determine whether an admission request isdenied because of heavy load and insufficient resources on the Uu interface.

– UI_FAM_UT_CTRL_TBL: Selecting it enables the LMT to display mappingbetween UE IDs of the UE and internal units of the RNC.

– UI_FAM_UT_GTPU_DATA_FWD_MSG: Selecting it enables the LMT to displaystatistics on packets received and sent at the GPRS Tunneling Protocol for User Plane(GTPU) layer.

– UI_FAM_UT_INTRA_MSG: Selecting it enables the LMT to displaycommunication messages between internal units of the RNC.

– UI_FAM_UT_L2_TXT_FWD_MSG: Selecting it enables the LMT to display real-time information such as the RLC state, FP synchronization information, andinformation about HS-DSCH capacity allocation.

– UI_FAM_UT_PRINT_INFO: Selecting it enables the LMT to display real-time loginformation, including text messages. The text messages can be of the TXT or TXT(Command Code) type.



145

– UI_FAM_UT_REAL_TIME_INFO: Selecting it enables the LMT to display real-time information such as information about cell admission and cell load control.

– UI_FAM_UT_RPRT_CELL_EVENT_INFO: Selecting it enables the LMT todisplay the number of UEs in a cell and the propagation delay from the NodeB to theUEs.

– UI_FAM_UT_STANDARD_MSG: Selecting it enables the LMT to display UEmessages traced on standard interfaces.

– UI_FAM_UT_STATE_TRANS: Selecting it enables the LMT to track statetransitions of the UE.

CAUTIONDebug Mode: indicates a mode intended for Huawei technical support personnel formaintenance. For use of it, contact Huawei technical support personnel.



----End



NOTE

The file that saves messages traced by a UE tracing task is named in a different way from the file thatsaves messages traced by other types of tracing task. The least significant four digits of the tracednumber (IMSI, TMSI, IMEI, or MSISDN) are saved in the file name. If there are fewer than four digits,use the digits in the file name without needing to add more digits to reach four digits. For example, ifthe least significant four digits of a UE IMSI are 1234, messages traced by a UE tracing task of thisUE are saved in a file named UE_YYYY-MM-DD-HH-MM-SS-1234_Serial number.tmf.




146

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.

l To view detailed description of TXT (Command Code) messages, right-click in the blankarea on the right and choose Update Text from the shortcut menu. The text messages updateonce each time users choose Update Text. They do not automatically update.





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



147


ContextYou 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 performed to trace NBAP common messageson the 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 SCCPCHs.


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

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, either the

USER_VOLUME event or the PROPAGATION_DELAY event. If you select theUSER_VOLUME event, some custom messages reflecting statistics about UEs in a cell will



148

be reported. The value ranges from 1000 to 10000 given in 10 ms. If you select thePROPAGATION_DELAY event, propagation delay in messages will be reported. Thevalue ranges from 1 to 80.

l FMR tab page: includes the following filter criteria:

– Service Data Trace area: includes different types of service data to be traced.

– SCCPCH ID: indicates 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(100ms): is in the unit of 100 ms and needs to be specified if FP DataPeriodic Report or Transport Data Periodic Report is selected in the FMR tab page.

l IUB tab page: includes messages to be traced on the Iub interface.

l Debug Mode: indicates a maintenance mode used for tracing communication messagesbetween units of the RNC. Tracing tasks configured on Other and Bind tab pages take effectonly when Debug Mode is selected.

– Bind tab page: is used for binding the UE to a DSP. This helps users to determine whethera DSP fault exists.

– DSP

– Subrack No.: indicates the number of the subrack corresponding to the DSP.

– Slot No.: indicates the number of the slot corresponding to the DSP.

– DSP No.: indicates the number of the DSP.

– Other tab page

– SIG Trace Event area: includes internal transport events of the RNC to be traced.

– CDR_SIG_QAAL2_PDU_MSG: Selecting it enables tracing of real-time QAAL2standard protocol messages. Information elements carried in the messages helpdetermine whether QAAL2 message interaction between NEs is successful.

– Cell_SIG_AL_STREAMING_RDPT: Selecting it enables specified data flow of thecell on the interface board to be reported to the LMT.

– Transport Channel Type: indicates the type of transport channel to have its dataflow traced.

– SCCPCH ID: indicates the ID of the Secondary Common Control PhysicalChannel (S-CCPCH).




----End




149



Figure 7-47 Results of cell message tracing


NOTETo view detailed description of TXT (Command Code) messages, right-click in the blank area on the right andchoose Update Text from the shortcut menu. The text messages update once each time users choose UpdateText. They do not automatically update.




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.

Prerequisites




150

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. The IOSTrace dialog box is displayed, as shown in Figure 7-48.



151

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 VIP IMSI: Run the ADD UVIPIMSI command to add the VIP IMSI.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: includes RAB parameters. If the BSC6900 receives an RAB ASSIGNMENTREQUEST message of a call that matches the specified RAB parameters in the specifiedcell, the call is traced. If a call sets up multiple RAB links, the call is traced if one of the RABlinks meets the specified RAB parameters.

l RRC tab page: includes the RRC establishment cause. If the BSC6900 receives anRRC_CONN_REQ message of a call that matches the specified RRC establishment causein the specified cell, the call is traced.



152

– RRC(ms): indicates the period of reporting measurement results of PCPICH Ec/No andReceived 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

– 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

– 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: includes performance counters to be monitored during tracing of a singleUE

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



153

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

l Debug Mode: indicates a maintenance mode used for tracing communication messagesbetween units of the RNC. Tracing tasks configured on Other, Other1, and Bind tab pagestake effect only when Debug Mode is selected.

– Other tab page

– Layer 2 data transfer Periodic Report: To enable statistics on packets received andsent at layer 2 to be periodically reported to the LMT, specify the parameter value.

– L2 Data Report area: includes parameters that enable statistics on packets receivedand sent at layer 2 to be reported to the LMT.

– L2 SRB Data Report: enables packets received in the UL and sent in the DL onthe control plane at the Frame Protocol (FP) layer to be reported to the LMT inmessages.

– Report time(s): indicates the period for reporting L2 Data Report.

– L2 TRB Packet Header Report(IUB interface): Selecting it enables frameheaders received in the UL or sent in the DL on the user plane at the FP layer tobe reported to the LMT.

– L2 TRB Packet Header Report(IU interface): Selecting it enables packet TCP/IP headers sent in the UL or received in the DL on the user plane at the RLC layerto be reported to the LMT.

– QAAL2_protocol_tracing: Selecting it enables tracing of real-time QAAL2 standardprotocol messages. Information elements carried in the messages help determinewhether QAAL2 message interaction between NEs is successful.

– RT_BASIC_INFO: Selecting it enables the following information to be traced: Real-time RRC service state of the UE such as CELL_DCH and CELL_FACH, connectionmode over the Iu interface (idle or connected mode), the homing RNC (SRNC orDRNC), and cells in the active set of the UE.

– RT_COMM_CONTEXT_INFO: Selecting it enables tracing of real-timeinformation such as the serving NodeB, communication context ID of the controllingradio network controller (CRNC), URNTI, CRNTI, and UE ID.

– RT_INST_RESOURCE_INFO: Selecting it enables tracing of real-time index ofresources that are allocated to the UE, for example, system memory.

– RT_RAB_PARA_INFO: Selecting it enables tracing of real-time radio access bearer(RAB) information such as traffic class, maximum rate, and guaranteed bit rate (GBR).

– SCCP Protocol tracing: Selecting it enables tracing of real-time SCCP standardprotocol messages. SCCP is short for Signaling Connection Control Part. Informationelements carried in the messages help determine whether SCCP message interactionbetween NEs is successful.

– Other1 tab page

– Internal Event: Selecting it enables tracing of internal events, communicationmessages between RNC units.

– FP PM Report: Selecting it enables transmission statistics at the FP layer to bereported to the LMT.

– IUUP Uplink Loop: Selecting it enables Iu user plane (IuUP) data that would betransmitted to the CN to be transmitted in the downlink direction. This function is



154

used for isolating other network elements during problem analysis, which facilitateslocation of speech quality problems.

– IUUP Downlink Loop: Selecting it enables IuUP data received from the CN to bereturned to the CN. This function is used for isolating other network elements duringproblem analysis, which facilitates location of speech quality problems.

– FP Trace: Selecting it enables control frames on the IuUP or at the FP layer to bereported to the LMT.

– Bind tab page: is used for binding the call samples to a path. This helps users to determinewhether a path fault exists.

– Iub Path

– Path ANI No.: indicates the Adjacent Node Identifier (ANI) corresponding to theIub path.

– Path Type: indicates the transport type of the Iub path.

– Path ID: indicates the number of the Iub path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound channel identifier (CID) on theIub path in ATM transmission mode or the number of the bound User DatagramProtocol (UDP) port in IP transmission mode.

– Iucs Path

– Path ANI No.: indicates the ANI corresponding to the Iu-CS path.

– Path Type: indicates the transport type of the Iu-CS path.

– Path ID: indicates the number of the Iu-CS path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iu-CS path in ATMtransmission mode or the number of the bound UDP port in IP transmission mode.

– Iur Path

– Path ANI No.: indicates the ANI corresponding to the Iur path.

– Path Type: indicates the transport type of the Iur path.

– Path ID: indicates the number of the Iur path.

– CID/UDP PORT(I1,I2,I3...): indicates the bound CID on the Iur path in ATMtransmission mode or the number of the bound UDP port in IP transmission mode.

– Iups GTPU

– Path ANI No.: indicates the ANI corresponding to the Iu-PS GTPU.

– Path ID: indicates the path number of the Iu-PS GTPU.




----End



155




Figure 7-49 Results of IOS message tracing


NOTETo view detailed description of TXT (Command Code) messages, right-click in the blank area on the right andchoose Update Text from the shortcut menu. The text messages update once each time users choose UpdateText. They do not automatically update.




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



156

7.4.1 Browsing Traced Messages OnlineThis section describes how to browse traced messages online in a message browser after a tracingtask is created.

Prerequisitesl A tracing task is successfully created.

l Traced messages are reported.

Contextl By default, each message browser is displayed in maximized mode. To compare results

displayed in multiple message browsers, set Windows to Cascade, Horizontal orVertical.

Each of the windows is configured with a default minimum width, which ensures thecomparison effect when multiple windows are tiled vertically. With this configuration, amaximum of six windows can be displayed in a monitor with the resolution of 1280x1024.Other windows are hidden behind the displayed windows.

The cascaded or tiled window arrangements take effect only at every setting ofWindows to Cascade, Horizontal, or Vertical. After such a setting, a new messagebrowser will still be displayed in maximized mode.

l A maximum of 2000 messages can be displayed in a message browser. Newly tracedmessages will replace old ones if displayed messages in a message browser reach 2000.

Procedure

Step 1 Browse or view traced messages in a message browser in real time. Right-click in the messagebrowser and choose an item from the shortcut menu to perform the associated operation asdescribed in Table 7-1.

Table 7-1 Operations available when browsing traced messages online

Shortcut Description

Stop Trace Task Suspend the tracing task.

Restart Trace Task Resume the tracing task.

Save All Messages... Saves all traced messages displayed in the message browser.

Save Selected Messages... Save the selected messages.

Auto Scroll Enable messages in the message browser to automaticallyrefresh themselves in real time and scroll themselves upward.

Clear Messages Clear all displayed messages from the message browserwithout affecting the saved messages.

Property... Query properties of the tracing task.



157

Step 2 To view details of a message, double-click it. The Message Browser dialog box is displayed,showing details of the message.

----End

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

Prerequisitesl 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 traced messages in a file to an LMT PC.

Prerequisitesl A tracing task is started.l Traced messages are reported.

ContextThe name of the file containing saved messages cannot exceed 100 characters, including the filename extension.

There are two ways of saving the traced results: automatic and manual.

Procedurel Automatic saving of traced messages

Select Save File when creating a tracing task. All traced messages of this task to bedisplayed in the message browser will be automatically saved in .tmf format.

The default save path is C:\Web LMT\MBSC\output\trace\tmfFile on the LMT PC.



158

NOTE

l The LMT saves every 5,000 messages in a file. Messages starting from 5,001 are saved in anotherfile with a serial number and the serial number is increased by one for every subsequent 5,000messages. For example, the 5001st to 10000th messages traced on the interface are saved in file'sname-1.tmf format by default. YYYY, MM, DD, HH, MM, and SS represent the year, month,day, hour, minute, and second, respectively.

l The file saving messages traced by a UE tracing task is named in a different way from the filesaving messages traced by other types of tracing task. The least significant four digits of thetraced number (IMSI, TMSI, IMEI, or MSISDN) are saved in the file name. If there are fewerthan four digits, use the digits in the file name without needing to add more digits to reach fourdigits. For example, if the least significant four digits of a UE IMSI are 1234, messages tracedby a UE tracing task of this UE are saved in a file named UE_YYYY-MM-DD-HH-MM-SS-1234_Serial number.tmf.

l You can use the Traffic Recording Review Tool to browse messages saved in .tmf format offline.For details, see 7.4.4 Browsing Traced Messages Offline.

l Manual saving of traced messages

When a tracing task is running, you can manually save all or some of the messages in themessage browser in .tmf, .txt, or .csv format.

1. To save all messages, right-click in the message browser and choose Save AllMessages from the shortcut menu. To save some messages displayed in the messagebrowser, select them, right-click, and choose Save Selected Messages from theshortcut menu. The Save dialog box is displayed.

2. Enter a file name, and specify the file type and save path.

The default save path is C:\Web LMT\MBSC\output\trace\tmfFile. The default filename is in IP address_Tracing type_YYYY-MM-DD-HH-MM-SS.tmf format.

3. Click Save to save the file in the specified path.

----End

7.4.4 Browsing Traced Messages OfflineThis section describes how to use the TrafficRecording Review Tool to browse offline, the tracedmessages that are saved in .tmf format.

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

ProcedureStep 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecording

Review Tool.

Step 2 The Open dialog box is displayed, prompting you to select the target file. Browse to the 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 theTrafficRecording Review Tool window.



159

NOTE

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

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

Step 5 To view the contents of more files, choose File > Open. In the Open dialog box, select and 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 TrafficRecordingReview 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.



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.



160

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



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

Manage Trace File dialog box is displayed.3. In the displayed Manage Trace File tab page, set the parameters in the Search

Configure area, and then click Query to read the information about the trace filessaved on the OMU.

4. To upload a trace file to the LMT PC, select the target file listed in the Result area,set the parameters in the Upload configure area, and then click Upload.

l Through MML commands1. Run the LST TRCRST command to query the trace files.

----End



161

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. When OMU boards perform an active/standby switchover, monitoring can be restarted only 30 minutes after the switchover.

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 section describes the parameters used for performance monitoring.

BSC6900 UMTSLMT User Guide 8 Performance Monitoring


162

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.

Principles of CPU Usage MonitoringFigure 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 MonitoringFigure 8-2 shows the principle of monitoring other real-time performances, which is similar tothe principle of message tracing.



163

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.

NOTE

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



164

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.

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


Procedure




165

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 Transport Resource RealTime monitoring dialog box, set the parameters as required,and click Submit.

Statistic Item Description

Admitted Bandwidth(3G Total)

Admitted bandwidth for 3G services at the transport layer on theuser plane. The admitted bandwidth consists of bandwidth used forsetting up the common channel and bandwidth for guaranteed bitrate (GBR). When calculating the bandwidth for GBR, bandwidthat the radio layer needs to be converted to that at the transport layer.

Available Bandwidth Bandwidth available currently. It equals Total Bandwidth minusAdmitted Bandwidth(3G Total) minus Admitted Bandwidth(2G Total) minus signaling bandwidth. Admitted Bandwidth(2GTotal) is valid when 2G and 3G services share the same port.To query the signaling bandwidth, run the DSPIPLOGICPORT command. The signaling bandwidth cannot bequeried when Transport Object Type is set to Physical Port.

Total Bandwidth When Auto adjust bandwidth switch is set to OFF(OFF) in theADD IPLOGICPORT command, Total Bandwidth equalsconfigured bandwidth. To query configured bandwidth, run theDSP IPLOGICPORT command. When Auto adjust bandwidthswitch is set to ON(ON), Total Bandwidth fluctuates betweenMax bandwidth [64kbps] and Min bandwidth [64kbps] basedon transmission quality indicated by IPPM detection.

OLC Threshold Overload control (OLC) start threshold. It equals configuredbandwidth minus overload congestion remain bandwidth.To query the configured bandwidth, run the DSPIPLOGICPORT command.To query the overload congestion remain bandwidth, run the ADDTRMLOADTH command. Note that when Threshold type is setto PERCENTAGE(Percentage), the overload congestion remainbandwidth equals the configured bandwidth multiplied by thecongestion remain ratio.

OLC Clear Threshold OLC end threshold. It equals configured bandwidth minusoverload congestion clear remain bandwidth.To query the configured bandwidth, run the DSPIPLOGICPORT command.To query the overload congestion clear remain bandwidth, run theADD TRMLOADTH command. Note that when Thresholdtype is set to PERCENTAGE(Percentage), the overloadcongestion clear remain bandwidth equals the configuredbandwidth multiplied by the overload congestion clear remainratio.



166

Statistic Item Description

Reserved Thresholdfor Handover

Threshold for reserving bandwidth for handovers. It equalsconfigured bandwidth minus handover reserved bandwidth.To query the configured bandwidth, run the DSPIPLOGICPORT command.To query the handover reserved bandwidth, run the ADDTRMLOADTH command. Note that when Threshold type is setto PERCENTAGE(Percentage), the handover reservedbandwidth equals the configured bandwidth multiplied by thehandover reserved ratio.

Congestion Threshold Congestion start threshold. It equals configured bandwidth minuscongestion remain bandwidth.To query the configured bandwidth, run the DSPIPLOGICPORT command.To query the congestion remain bandwidth, run the ADDTRMLOADTH command. Note that when Threshold type is setto PERCENTAGE(Percentage), the congestion remainbandwidth equals the configured bandwidth multiplied by thecongestion remain ratio.

Congestion ClearThreshold

Congestion end threshold. It equals configured bandwidth minuscongestion clear remain bandwidth.To query the configured bandwidth, run the DSPIPLOGICPORT command.To query the congestion clear remain bandwidth, run the ADDTRMLOADTH command. Note that when Threshold type is setto PERCENTAGE(Percentage), the congestion clear remainbandwidth equals the configured bandwidth multiplied by thecongestion clear remain ratio.

----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, Bit Error Rate (calculated by CRC Errors).Based on the data, you can evaluate the operating condition of the transmission network andfind out the causes for the bit errors in combination with the performance of the peer end. TheAEUa/PEUa/AOUc/POUc board supports this function.




167

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 therefore 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. The result andprinciple of these two tasks are the same.

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 and

timeslot-level testing.

Procedure

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

Step 2 Under Monitor Navigation Tree, choose Monitor > Common Monitoring > BERMonitoring. 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



168

8.2.5 Monitoring Link PerformanceThis section describes how to monitor link performance. For the same monitoring item, you canstart a maximum of six monitoring tasks simultaneously. One monitoring task corresponds toone link performance monitoring window. If six tasks are started, when you want to terminateone of the six monitoring tasks, you must ensure that the link performance monitoring windowfor this monitoring task is closed. Otherwise, this monitoring task will continue to occupyresources. As a result, new monitoring tasks cannot be started.

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



169

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

Prerequisites


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.

Procedure



Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to UNI Link. Set otherparameters 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 Fractional ATM Link Traffic

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

Prerequisites




170

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



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

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.


----End

Monitoring the SAAL Link Traffic

This section describes how to monitor the traffic on a specified SAAL path in real time. Thereal-time traffic on the specified SAAL path is displayed in the form of list and chart. Based onthe transmit/receive statistics on the SAAL of the CPUS subsystem, you can confirm the packetloss, locate the SAAL disconnection or intermittence problem. You can also predict thecongestion by comparing the traffic with the configured bandwidth.

Prerequisites


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




171


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

NOTE



----End

Monitoring the IPoA PVC TrafficThis section describes how to monitor the traffic on a specified IPOA PVC in real time. Thereal-time traffic on the specified IPOA PVC is displayed in the form of list and chart. If the IPOAPVC carries the OML for the ATM-based BTS, you can perform this task to observe the trafficand bandwidth utilization when the NodeB is loading data and to locate the fault in the NodeBstartup and data loading processes. If the IPOA PVC carries the IP path over the Iu-PS interface,you can perform this function to observe the traffic flow and locate the connection and congestionstatus 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



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

NOTE



----End



172

Monitoring the AAL2 Path Traffic

This section describes how to monitor the traffic on a specified AAL2 path in real time. Thereal-time traffic on the specified AAL2 path is displayed in the form of list and chart. Based onthe layer 2 transmit/receive statistics obtained from the CDT trace, you can confirm the packetloss and evaluate the traffic condition. In addition, you can predict the congestion based on thetraffic conditions on the link.

Prerequisites


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



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

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.

Prerequisites




173

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.For the FG2c, GOUc boards, if the physical port carries a logical port and Monitor Type for thelink performance monitoring task is set to QoS, the queue statistics of the physical port does notinclude the service data traffic on the logical port but only the service data traffic on the physicalport.

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 FE/GE. Set otherparameters 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 PPP Link TrafficThis 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.


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.



174

For the POUc boards, if the physical port carries a logical port and Monitor Type for the linkperformance monitoring task is set to QoS, the queue statistics of the physical port does notinclude the service data traffic on the logical port but only the service data traffic on the physicalport.

Procedure



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

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.

Prerequisites


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.

For the POUc boards, if the physical port carries a logical port and Monitor Type for the linkperformance monitoring task is set to QoS, the queue statistics of the physical port does notinclude the service data traffic on the logical port but only the service data traffic on the physicalport.



175

Procedure



Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to MLPPP Group. Setother parameters as required, and then click Submit.

NOTE



----End

Monitoring the SCTP Link TrafficThis section describes how to monitor the traffic on a specified SCTP path at the SCTP layer inreal time. The real-time traffic on the specified SCTP path is displayed in the form of list andchart. Based on the transmit/receive statistics on the SCTP of the CPUS subsystem, you canconfirm the packet loss, locate the SCTP disconnection or intermittence problem. In addition,you can predict the congestion based on the traffic conditions on the link.


Context

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

Procedure



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



176

NOTE


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



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

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 traffic



177

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

Prerequisites


Procedure



Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Logical Port. 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 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. Therefore, you can locate thefault in the NodeB startup and data loading processes.

Prerequisitesl The LMT is running normally.

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

Procedure



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



178

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.

Prerequisites


Procedure



Step 3 In the displayed Link Performance Monitoring dialog box, set Monitor Item to Logic PortBandwidth. 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 Port

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

Prerequisites




179

Context

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

Procedure



Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to Non-ChannelizedATM Optical Port. Set other parameters as required, and then click Submit.

NOTE


In the chart, the X coordinate represents the time in RFNs (1 RFN = 10 ms), 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.



180

Step 3 In the Link Performance Monitoring dialog box, set Monitor Item to IPPM. Set otherparameters as required, and then click 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.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 utilizationof 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.


Context

CAUTIONThe trunk group to be monitored is configured successfully.

ProcedureStep 1 Click Monitor on the LMT main page. The Monitor tab page 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

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.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 IPPOOL LOCAL IP TrafficThis section describes how to monitor traffic on the specified local port in IP transmissionresource pool networking in real time, which is displayed by lists and charts. The statistics



181

facilitate fault diagnosis and transmission quality evaluation. With usage of the local portestimated, users can be reminded to take measures to prevent congestion.


Procedure



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

NOTE

After the monitoring task has started, a monitoring window is displayed showing the real-time monitoringresult by lists and charts. The task name and related parameters are displayed on the title bar of the window.

In the chart, the X coordinate represents hour: minute: second. The Y coordinate represents the RX andTX traffic in the unit of bit/s.

----End

Monitoring IPPOOL PM TrafficThis section describes how to monitor traffic on the specified IP PM link in IP transmissionresource pool networking in real time, which is displayed by lists and charts. Together withstatistics on the IPPM link on the transmitting and receiving sides, the function can be used toconfirm packet loss and locate disconnection or intermittence in IP pool networking. Thefunction can also be used to predict congestion based on the traffic conditions on the link.


Context

CAUTIONThe IP PM link to be monitored is activated.

Procedure



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



182

NOTE

After the monitoring task has started, a monitoring window is displayed showing the real-time monitoringresult by lists and charts. The task name and related parameters are displayed on the title bar of the window.

In the chart, the X coordinate represents hour: minute: second. The Y coordinate represents the RX andTX traffic in the unit of bit/s.

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

Monitoring P-CPICH Ec/No and RSCPThis 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.


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 that

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

NOTE

l This task applies to only monitoring connections established on dedicated channels. An ongoing 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.



183

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.

NOTE

l There is no way to avoid that some user data such as International Mobile Subscriber Identity (IMSI)will be used during problem location and resolution. This function provides an anonymous dataprocessing method. You are recommended to comply with local laws when executing the task and takeample measures to fully protect user data, such as enabling the anonymous function and deleting thefolder that saves track records after you finish processing data.

l When entering IMSI, check whether IMSI data to be entered must be anonymous by running the LSTUSERIDANONSWITCH command and querying User Identity Anonymity Switch.

l If User Identity Anonymity Switch is ON, the anonymous policy is enabled, and anonymous IMSIdata must be entered in IMSI. The anonymous IMSI data is the IMSI data encrypted by theHMACUtil using the cipher key.

l If User Identity Anonymity Switch is OFF, the anonymous policy is disabled, and user IMSI datais directly entered in IMSI.

l Change the anonymous policy and cipher key on the M2000 by choosing Monitor > Signaling >Anonymous Policy Management > Anonymous Cypher Key Management. For details, see M2000Fault Management User Guide.

l If you change the anonymous policy or cipher key of a started tracing task, you need to restart themonitoring task. Otherwise, the monitoring task becomes invalid.

l For details about how to obtain the HMACUtil, contact Huawei technical support.

----End

Monitoring SIR of the Uplink RLS

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

Prerequisites




184

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.

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 Outer Loop Power ControlThis section describes how to monitor the outer loop power control. The following items aremonitored: the target UL RLS SIR, BER of the UL physical channel, BER filter values of theUL transport channel, BLER of the UL transport channel, E-DCH average times ofretransmission, and E-DCH retransmission probability.


Procedure



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



185

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


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.

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.



186

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


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.

Procedure



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.



187

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 Power

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

Prerequisites


Context

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

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



188

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

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 in



189

acknowledgment 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


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



190

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 ULthroughput and UL bandwidth (unit: bit/s).l If the UL bandwidth varies with the UL throughput, you can infer that the dynamic channel configuration

function is normal.l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristics

of UL service source by observing the variation of UL throughput.

----End

Monitoring DL Throughput and BandwidthThis 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.


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 throughputmeasurement 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 DLThroughput & Bandwidth. 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 DLthroughput and DL bandwidth (unit: bit/s).l If the DL bandwidth increases/decreases with the increase/decrease of DL throughput, you can infer that

the dynamic channel configuration function is normal.l If the dynamic channel configuration function is not enabled, you can learn the rate variation characteristics

of DL service source by observing the variation of DL throughput.

----End



191

Monitoring Handover DelayThis section describes how to monitor the handover delay.

PrerequisitesYou have logged in to the LMT with an account with authorized operation rights.

ContextHandover delay refers to the time taken by each handover. During this period of time, theBSC6900 performs a handover decision, initiates the handover (including the soft handover andthe hard handover), and completes the handover.

This task can be performed to monitor the handover delay of only a UE in the CELL_DCH state.An ongoing task is stopped if the UE transits from the CELL_DCH state to the CELL_FACHstate or idle mode. The task is restarted if the UE transits from the CELL_FACH state or idlemode back to the CELL_DCH state.

A maximum of five handover delay monitoring tasks can be started simultaneously. This taskcan monitor the delay of an intra-frequency or inter-frequency handover but not an inter-RAThandover.

Procedure


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

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

MonitoringResults

Description

HO Delay(ms) Time taken by each handover

HO Interval(ms) Time difference between the end of the last handover and the end ofthe current handover

NOTE

A monitoring window is displayed, indicating the real-time monitoring results in the form of lists andcharts.

In the chart, the X-coordinate represents the hour:minute:second. The Y-coordinate represents the handoverdelay and handover interval (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 the



192

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

Prerequisites


Context

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

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

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

Prerequisites


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.



193

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


ContextThe 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



194

Monitoring UL RX Total Wideband Power of a Cell

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

Prerequisites


Context

The 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 hour: minute: second. The Y-coordinate represents the cell UL RX totalwideband power (unit: dBm).

----End

Monitoring DL TX Power in a Cell

This section describes how to monitor the DL transmit (TX) power of a specified cell. 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.

Prerequisites


Context

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



195

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


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 Cell

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

Prerequisites


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


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.



196


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


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

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.



197

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.

Prerequisites


Context

The methods for measuring the cell load vary with CAC algorithms (CAC algorithm 1 or CACalgorithm 2). Run MOD UCELLALGOSWITCH to set the DL CAC algorithm of a cell. RunLST UCELLALGOSWITCH to query the DL 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.



198

Prerequisites


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.

Prerequisites


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.

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.



199

Prerequisites


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.

Prerequisites


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


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

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



200

Prerequisites


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


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

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

Prerequisites


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.



201

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.

Prerequisites


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.

Prerequisites




202

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.

Prerequisites


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

Monitoring the FDPCH SYMBOL

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

Prerequisites




203

Context

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

Prerequisites


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.



204

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

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

Prerequisitesl 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

– 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



205

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.



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.



Procedure

Step 1 To automatically save the monitoring results, ensure that the Save File check box is selectedwhen you create the task. The default save path is C:/Web LMT/MBSC/output/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.

Prerequisites

The monitoring results are saved to files.



206

Procedure

Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > TrafficRecordingReview Tool.

Step 2 Open the directory where the monitoring results are saved. The default save path is C:/WebLMT/MBSC/output/monitor. Select the result file corresponding to the monitoring task.

Step 3 Click Open or double-click the file. The TrafficRecording Review Tool window is displayed,providing the monitoring results in chart and list.

Step 4 Click the List tab or the Chart tab to view the data in different modes.

Step 5 To view other saved results, choose File > Open. In the Open dialog box, select the target filesto read the details.

----End

8.5 Reference for Performance MonitoringThis section 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.

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.



207


FE/GE FE/GE PortNo.

Indicates the number of the FE/GE port. Toquery the number of the FE/GE port, run theLST 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.



208


TrunkGroup

Trunk GroupNo.

Indicates the number of the trunk group. Toquery the trunk group, run the LSTETHTRK command.

IPPOOLLOCAL IP

Local IPAddress

To query the local IP address, run the LSTIPPOOLIP command.

IPPOOLPM

Local IPAddressPeer IPAddressPriority

Is the same as Currently bound SIP, the IPaddress currently bound to the adjacent node.To query Currently bound SIP, run the DSPADJNODE command.To query the peer IP address, run the DSPADJNODEDIP command.To query the priority, run the LSTIPPOOLPM command and view the settingfor Per-Hop Behavior.



209

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


210

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.

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.

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.



211

Prerequisites


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.1.3 Querying the Status of an E1/T1 PortThis section describes how to query the status of an E1/T1 port.


l The boards are in position.

Procedure

Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel(see 9.2.2 Starting the Emulation Panel).

Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, 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

9.1.4 Querying the CPU/DSP UsageThis section describes how to query the CPU/DSP usage of a board.



Context

You can query the CPU/DSP usage through menu operations or through MML commands.


1. Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulationpanel (see 9.2.2 Starting the Emulation Panel).



212

2. Right-click a board in position in the device panel or emulation panel, and then chooseCPU/DSP Usage Query from the shortcut menu. The CPU/DSP Usage window isdisplayed, showing the real-time CPU/DSP usage.

l Through MML commands1. Run the DSP CPUUSAGE command to query the CPU/DSP usage.

----End

9.1.5 Querying BSC Board Clock StatusThis section describes how to query the clock status of a BSC board.


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

9.1.6 Querying the BSC Board InformationThis section describes how to query the status of a BSC board.

Prerequisitesl You have logged in to the LMT.l The boards are in position.

ContextYou can query the status of a board through menu operations or through MML commands.




213

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.


1. Run the DSP BRD command to query the information about the BSC board.

----End

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.



Context

CAUTIONl If the standby board is not available or is faulty, resetting the board will disrupt the ongoing

services. Therefore, perform this operation with caution.

l Resetting the board may affect the ongoing services. Therefore, you are advised to 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.



214



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

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.

Prerequisitesl You have logged in to the LMT.l Before you perform the switchover, ensure that the standby board is present and running

normally without any critical or major alarms.

Context

CAUTIONl If the board switchover fails, the configuration data is not affected but the services will be

disrupted. Therefore, perform this task 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 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.



215

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.


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

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

The emulation panel displays the running status of the ports of each board and provides right-click menus as shown in Figure 9-2.



216

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.


Procedure


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.



217

Figure 9-3 Subrack peripheral

----End

9.2.3 Querying the Status of an E1/T1 PortThis section describes how to query the status of an E1/T1 port.



Procedure

Step 1 Start the BSC device panel (see 9.1.2 Starting the Device Panel) or start the emulation panel(see 9.2.2 Starting the Emulation Panel).

Step 2 On the device panel or emulation panel, right-click the E1/T1 interface board to be queried, 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

9.2.4 Querying the CPU/DSP UsageThis section describes how to query the CPU/DSP usage of a board.



218



Context

You can query the CPU/DSP usage through menu operations or through MML commands.


1. Start the BSC 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 chooseCPU/DSP Usage Query from the shortcut menu. The CPU/DSP Usage window isdisplayed, showing the real-time CPU/DSP usage.


1. Run the DSP CPUUSAGE command to query the CPU/DSP usage.

----End

9.2.5 Querying BSC Board Clock StatusThis section describes how to query the clock status of a BSC board.

Prerequisites


Context

You can query the clock status of a BSC board through menu operations or through 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.


1. Run the DSP CLK command to query the clock status of a BSC board.

----End



219

9.2.6 Querying the BSC Board InformationThis section describes how to query the status of a BSC board.


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

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


Context

CAUTIONl If the standby board is not available or is faulty, resetting the board will disrupt the ongoing

services. Therefore, perform this operation with caution.l Resetting the board may affect the ongoing services. Therefore, you are advised to perform

the switchover when the traffic load is light, for example, in the middle of the night.

l Resetting the 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 standby



220

board 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

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

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



221

Context

CAUTIONl If the board switchover fails, the configuration data is not affected but the services will be

disrupted. Therefore, perform this task 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 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.



222

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.



223


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.



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



224

10 BSC Maintenance

About This Chapter

This chapter describes how to maintain the BSC equipment, Backing Up Data and RestoringData, and Fault Management Assistant.

10.1 Backing Up DataThis section describes how to back up system data on the OMU. The system data includesconfiguration data, alarm configuration data, and performance configuration data.

10.2 Restoring DataThis section describes how to restore configuration data on the OMU.

10.3 Fault Management AssistantThis section describes how to use the Fault Management Assistant function for rapid faultdiagnosis. The faults that can be diagnosed include RRC connection setup faults, CS servicesetup faults, PS service setup faults, paging faults, and a large number of unavailable cells. Withthis function, the LMT analyzes counters, alarms, and logs of a site where a fault occurs byfollowing the diagnosis rules, and then sends an analysis report to guide users in rapidtroubleshooting.

10.4 OS MaintenanceThe OS debugging function provides commands for querying the operating system (OS)information and commands for system debugging. The OS information refers to timer resources,memory resources, tasks, messages and queues, reset records, IPCs, MOTs and startup records.

BSC6900 UMTSLMT User Guide 10 BSC Maintenance


225

10.1 Backing Up DataThis section describes how to back up system data on the OMU. The system data includesconfiguration data, alarm configuration data, and performance configuration data.


Contextl When the database system crashes or an upgrade fails, start the tool used for backing up

and restoring system data in the mbsc\bam\common\services\omu_backup_linkerdirectory. With the latest backup data, you can recover the system.

l If you need to recover only OMU configuration data, run the RTR DB command and selecta corresponding data backup file for data recovery.


1. Click Device Maintenance on the LMT main page. The Device Maintenance tabpage is displayed.

2. Under Device Navigation Tree, right-click the BSC node and choose BackupData from the short-cut menu. The Backup Data dialog box is displayed withinformation about backup files saved in the OMU active workspace installationdirectory\data\backup directory.

3. In the displayed Backup Data dialog box, click Backup to back up system data onthe OMU.

NOTE

l The default directory for saving backup files is OMU active workspace installation directory\data\backup. If such a directory does not exist, it will be created automatically.

l If the name of a backup file is not typed, the file is named BKPDB_#_*.bak automatically.Here, "#" stands for the detailed version information of the working OMU and "*" stands forthe current system time when the backup is performed. When the number of backup files in thebackup directory exceeds 30, the earliest backup file is automatically deleted.

l The following special characters are forbidden in the file name: "\", "/", ":", "*", "?", ""," "<",">", "|", "(", ")", "&" and "$".

l Backup files cannot be saved in a network path, for example, \\10.161.162.25.

l No space is allowed in the file name or the saving directory. For example, "BK2009 09 08.bak"is an illegal file name.

4. In the displayed Backup Data dialog box, select a backup file and clickDownLoad to download the backup file to a local path on the LMT PC.

NOTE

Click Refresh to refresh backup files saved in the OMU active workspace installation directory\data\backup directory in the Backup Data dialog box.

l Through an MML command1. Run the LST BKPFILE command to query data backup files saved in the OMU

active workspace installation directory\data\backup directory.



226

2. Run the BKP DB command to back up system data on the OMU.

----End

10.2 Restoring DataThis section describes how to restore configuration data on the OMU.


Context

CAUTIONl Restoring data overwrites OMU data, so restore data with caution.

l Versions of data backup files must be the same as the OMU version.

l Alarm information and operation logs are not restored. Their data remains unchanged.

l After restoring OMU data, run the RST BSC command to reset the BSC.


1. Click Device Maintenance on the LMT main page. The Device Maintenance tabpage is displayed.

2. Under Device Navigation Tree, right-click the BSC node and choose RestoreData from the short-cut menu. The Restore Data dialog box is displayed withinformation about data backup files saved in the OMU active workspace installationdirectory\data\backup directory.

3. Optional: In the displayed Restore Data dialog box, click Upload to upload a backupfile on the LMT PC to the OMU.

NOTE

Click Refresh to refresh backup files saved in the OMU active workspace installation directory\data\backup directory in the Restore Data dialog box.

4. In the displayed Restore Data dialog box, click Restore Data to restore configurationdata on the OMU.

l Through an MML command

1. Run the LST BKPFILE command to query data backup files saved in the OMUactive workspace installation directory\data\backup directory.

2. Run the RTR DB command to restore configuration data on the OMU.

----End



227

10.3 Fault Management AssistantThis section describes how to use the Fault Management Assistant function for rapid faultdiagnosis. The faults that can be diagnosed include RRC connection setup faults, CS servicesetup faults, PS service setup faults, paging faults, and a large number of unavailable cells. Withthis function, the LMT analyzes counters, alarms, and logs of a site where a fault occurs byfollowing the diagnosis rules, and then sends an analysis report to guide users in rapidtroubleshooting.

Prerequisitesl You have logged in to the LMT.l Communication between the LMT and the BSC is normal.

Contextl This function is used when faults occur and persist at a site and site maintenance personnel

cannot directly use the counters, alarms, and logs for fault analysis.l This function occupies resources of the OMU board. Therefore this function cannot be

started or is stopped when a certain condition is met:– This function cannot be started when free space available on the OMU board is less than

500 MB.– This function is stopped when more than 95% of OMU memory is occupied and this

function occupies more than 200 MB OMU memory.

ProcedureStep 1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is

displayed.

Step 2 Under Device Navigation Tree, right-click the BSC node and choose Fault ManagementAssistant from the short-cut menu. The Fault Management Assistant dialog box isdisplayed, as shown in Figure 10-1.

Figure 10-1 Fault Management Assistant dialog box



228

Step 3 Select a scenario option in the displayed Fault Management Assistant dialog box.

Step 4 Click Start and wait for the fault diagnosis report.

----End


– A new browser window is displayed with the fault analysis report presented on a webpage. To save the diagnosis report in a file, click the "Save" button on the web page.

– A fault diagnosis report covers the following:

– KPI and counter change trend chart containing three curves illustrating KPI andcounter changes that occurred during the eight hours of today, yesterday, and lastweek, respectively. The X-coordinate represents hour:minute, the left Y-coordinaterepresents the counter value in the unit of the corresponding counter, and the rightY-coordinate represents the KPI value in percentages, as shown in Figure 10-2.

– KPI statistics

– Fault causes

– Fault rectification advice

– Operation log

Figure 10-2 Example fault diagnosis report

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

10.4 OS MaintenanceThe OS debugging function provides commands for querying the operating system (OS)information and commands for system debugging. The OS information refers to timer resources,memory resources, tasks, messages and queues, reset records, IPCs, MOTs and startup records.



229


Context

CAUTIONOnly ADMINISTRATOR-level users are authorized for performing OS Maintenancing becauseit involves private information of users.

Procedure


Step 2 Under Device Navigation Tree, right-click the BSC node and choose OS Maintenance fromthe short-cut menu. The OS Maintenance dialog box is displayed.

Step 3 In the OS Maintenance dialog box, set the parameters as required, and click Submit. The LMTreturns the detailed information.

NOTE

The returned information can be text and binary messages. You can view the text messages directly. Fora binary message, double-click it to read the detailed explanation.

----End



230

11 FAQ

About This Chapter

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

11.1 Slow Responses in the Firefox BrowserRunning in the Firefox browser, the LMT gives slow responses. For example, it takes about 30seconds to maximize the window of a trace task in the Trace tab page. In this case, check whetherthe add-on extension Live Margins is installed.

11.2 LMT Colors Cannot Be DisplayedWhen 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.

11.3 What Can I Do if the Verification Code Cannot Be Displayed on the LMT Login Page?The verification code cannot be displayed when you try to log in to the LMT using an InternetExplorer (IE) browser in Windows Server 2008 or Windows Vista. When this problem occurs,check the settings related to the protected mode of the browser.

11.4 Installing OS PatchesIn a Microsoft Windows operating system (OS), you need to install patch KB944338, KB938397or KB960714 if the OS and IE are in a certain version.

11.5 No Response When Clicking the Menu Bar on the LMTWhen the LMT Web page is browsed through IE, there is no response or a Web page script erroroccurs when you click the menu bar. To be specific, when you click the menu bar or buttons orright-click the Web page, 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 Web page. In this case, checkthe proxy settings in IE.

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

11.7 Corrupted Characters Appearing When the csv File Is Opened in UTF-8 Coding

BSC6900 UMTSLMT User Guide 11 FAQ


231

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.

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

11.9 How Do I Set the Browser Under Citrix Farm Networking?Under Citrix farm networking, when you use the M2000 proxy server to log in to the LMT ona Citrix client, the LMT may be suspended, the verification code may be unavailable, orinitialization of the MML navigation tree may fail. When these problems occur, check thebrowser settings, including the setting of the browser proxy server and the HTTP 1.1 setting. Ifeither setting is wrong, reset it.

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

11.11 Unable to Download or Install the Java or Flash Plug-in and Two File Manager WindowsDisplayed Windows IE8 or Any Later Version Is UsedIf users log in to the LMT in IE8 or later versions, an error message displays when they aredownloading or installing a Java or Flash plug-in, or two file manager windows are displayed.To solve the problem, disable SmartScreen Filter of IE8.

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

11.13 Any Further Operation Performed When Some LMT Web Pages Fail 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.

11.14 Configuring the HTTPS Login ModeThis section describes how to configure the HTTPS login mode and a security certificate. Userscan log in to the LMT through either HTTP or HTTPS. The login mode is configurable.

11.15 What Do I Do if the Error "Certificate Invalid" Is Displayed During an HTTPS LoginThe LMT certificate and the certificate used to access the LMT through the M2000 proxy withdual IP addresses are not granted by any commercial organization. Therefore, they are not trustedby a browser such as IE by default. In such a scenario, the SSL certificate negotiation isperformed when you visit the LMT in HTTPS mode. If the organization for issuing the currentcertificate is not in the default trust list of Microsoft, the Certificate Invalid error is displayedon the browser. This error does not impair the LMT functions. This section describes how tocorrect the error Certificate Invalid displayed during a login to the LMT through HTTPS. Tocorrect this error, add the root certificate of the certificate in use to the Trusted RootCertification Authorities list.

11.16 Error 'Mismatched Address' Is Displayed During an HTTPS LoginA user uses an IP address rather than a domain name to access the LMT. Therefore, theMismatched Address error is displayed on the browser during an HTTPS login. This error does



232

not impair the LMT functions. This section describes how to correct the error "MismatchedAddress" displayed during a login to the LMT through HTTPS. To correct this error, deselectthe Warn about certificate address mismatch* option.

11.17 What Do I Do if Tracing and Monitoring Functions Cannot Be Used?Tracing and monitoring functions cannot be used after a successful login to the LMT. Solve thisproblem by using the following methods.

11.18 What Do I Do If There Is No Response or Any Error Message After a Tracing orMonitoring Task Is Created?Some time after a successful login to the LMT, you may suddenly find that batch processingfails with no error message. Alternatively, after a tracing or monitoring task is created, the taskpage is not opened. There is no response or any error message. The NE task list shows that thistask has been successfully created. If you open a new browser and log in to the LMT again, thetask nevertheless can be successfully created. If either of the previous problems occurs, performthe following operations:

11.19 What Do I Do If the File Manager Functions Improperly?When the file manager functions improperly or cannot be used, perform the followingoperations:

11.20 What Do I Do If BTS Nodes Cannot Be Displayed Under Device Navigation TreeAfter a successful login to the LMT, you may find that BTS nodes cannot be displayed underDevice Navigation Tree. After upgrading the browser, you find that the nodes can be displayednormally. This problem occurs because data under Device Navigation Tree on the LMT iscompressed whereas Internet Explorer 6 SP2 does not support compression of chunked data.Solve this problem by using either of the following methods.

11.21 What Do I Do if the Alarm/Event Function Becomes Unavailable?When starting or using the Alarm/Event function after a successful login to the LMT, the pagemay become white with an exclamation mark displayed in the center. The exclamation mark iscircled in gray, as shown in the following figure: Solve this problem by using the followingmethods.

11.22 What Do I Do if the Message 'Class doesn't support Automation' Is Displayed in an IEBrowser?After clicking Login in an Internet Explorer (IE) browser, you find a blank window displayedand login unable to continue. In the bottom left corner of the IE browser, a yellow error icon isdisplayed. The icon says "Class doesn't support Automation". To solve the problem, performthe following steps:

11.23 What Do I Do if Java Installation FailsDuring Java installation, the message "Error 25099, Unzipping core files failed." is displayed.To solve the problem, perform the following steps:

11.24 What Do I Do if the LMT Login Web Page Cannot Be Opened with the PC OMU Installed?With the PC OMU installed in Windows 7, the LMT login web page cannot be opened. Inaddition, the LMT process cannot be found in the task manager.

11.25 What Do I Do if Changing Settings for the Next-Generation Java Plug-in Fails?When changing settings for Enable the next-generation Java Plug-in, you are prompted witha message indicating that the changing fails because one or more browsers are running. As amatter of fact, no browser is running. The following figure shows the message: To solve theproblem, perform the following steps.

11.26 Error Message"This user session already exists" Upon Login to LMT



233

The interface displays an error message "This user session already exists" upon login to LMT.Solve the problem by using the method described in the procedure part.

11.27 The "Are You Sure You Want to Quit the Page?" Dialog Box Is DisplayedAfter successful login to the LMT in the IE8 or IE9 browser, the "are you sure you want to quitthe page?" dialog box is displayed when the alarm feature is enabled. Solve the problem by usingthe method described in the procedure part.

11.28 Unable to Save Tracking and Monitoring DataWhen a tracking or monitoring task (such as the UE tracking task) is running on the LMT, it ispossible that the vast amounts of tracking or monitoring data cannot be saved even with sufficienthard disk space. Solve the problem by using the method described in the procedure part.

11.29 Slow Response During an LMT LoginThe LMT responses slowly when the users are trying to log in to the LMT. To solve the problem,perform the following steps:

11.30 Unclear Grids in the Tables in the MML Online HelpThe grids in the tables are not clear in MML online help when users log in to the LMT by somecomputers. To solve the problem, perform the following steps.

11.31 MML Command Failed to Be Executed or No Response to Tracing Tasks After theBrowser Is Upgraded to IE8After the browser is upgraded from IE6 to IE8, some cache files cannot be removed. As a result,the system displays a Please check the MML macro configure file! message when an MMLcommand is executed, or there is no response after tracing tasks are created. To solve thisproblem, you need to manually remove cache files and cookies.



234

11.1 Slow Responses in the Firefox BrowserRunning in the Firefox browser, the LMT gives slow responses. For example, it takes about 30seconds to maximize the window of a trace task in the Trace tab page. In this case, check whetherthe 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

11.2 LMT Colors Cannot Be DisplayedWhen 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

11.3 What Can I Do if the Verification Code Cannot BeDisplayed on the LMT Login Page?

The verification code cannot be displayed when you try to log in to the LMT using an InternetExplorer (IE) browser in Windows Server 2008 or Windows Vista. When this problem occurs,check the settings related to the protected mode of the browser.

ContextIf the protected mode is enabled for the IE browser in Windows Server 2008 or Windows Vista,many security restrictions are imposed. For example, JavaScript and Applet cannot be run.Therefore, you must disable the protected mode. Otherwise, the LMT web page cannot bedisplayed.



235

Procedure

Step 1 Enter the external virtual IP address of the OMU in the address box of the IE browser. PressEnter on the keyboard, or click Go next to the address bar to display the login window of theBSC6900.

Step 2 Check whether "Internet | Protected Mode: Off" is displayed in the bottom right corner of thewindow.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 Clear Enable Protected Mode in the Security level for this zone area. Click Sites. The Trustedsites dialog box is displayed.

Step 6 Type the external virtual IP address of the OMU in the Add this website to the zone text box,and then click Add. The external virtual IP address of the OMU is added to the Trusted siteslist.

NOTE

If the M2000 proxy server is used for the login to the LMT, add the IP address of the M2000 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.

If IE9 is used, in addition to the previous settings, choose Tools > Compatibility View Settings. In thedisplayed Compatibility View Settings dialog box, select Display all websites in Compatibility View.

----End

11.4 Installing OS PatchesIn a Microsoft Windows operating system (OS), you need to install patch KB944338, KB938397or KB960714 if the OS and IE are in a certain version.

Contextl Patch KB960714 solves the problem of Java console output error. Therefore, 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. Therefore, the LMT running rate can be increased.l If Windows 7 operating system is used, Windows patches do not need to be installed.

Procedure

Step 1 In the Windows OS, open the Control Panel window. Double-click the Add or RemovePrograms icon.



236

Step 2 In the displayed Add or Remove Programs window, select Show updates. Check whetherpatches KB944338, KB938397 and KB960714 are present in the list of Currently installedprograms.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 SP3 IE6/IE7

Windows Server 2003 SP1/SP2 IE6/IE7

Windows Vista IE7

l Patch KB944338 needs to be installed when the OS version is Windows 2000 SP4 or

Windows Server 2003 SP1/SP2.l When the Windows 2003 operating system is used, the service pack KB938397 needs to be

installed. This service pack ensures that the Windows 2003 operating system supports theSHA256 algorithm. After the service pack is installed, the LMT can work properly.

NOTE

l To download patch KB944338 or KB960714, go to http://www.microsoft.com/downloads.

l To download patch KB938397, go to http://support.microsoft.com/?kbid=938397.

l Download a suitable patch according to the OS version and IE version.

----End

11.5 No Response When Clicking the Menu Bar on the LMTWhen the LMT Web page is browsed through IE, there is no response or a Web page script erroroccurs when you click the menu bar. To be specific, when you click the menu bar or buttons orright-click the Web page, 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 Web page. In this case, checkthe proxy settings in IE.

Context

Do not modify the settings of the IE when you have logged in to the LMT. Set the proxy serverwhen necessary before you log in to the LMT.

Procedure

Step 1 Choose Tools > Internet Options on the tool bar of IE. The Internet Options dialog box isdisplayed.



237

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

11.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 timefails to refresh normally; tracing data and monitoring data fail to refresh normally; progressmanagement fails to refresh normally.

11.7 Corrupted Characters Appearing 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 11-1 shows the dialog box.



238

Figure 11-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 11-2 shows the dialog box. Select UTF-8in File origin.

Figure 11-2 Text import wizard-step 1



239

Step 3 Click Next. Then the Text Import Wizard - Step 2 of 3 dialog box is displayed. Figure 11-3shows the dialog box. Select Comma under Delimiters.

Figure 11-3 Text import wizard-step 2

Step 4 Click Finish. Then the Import Data dialog box is displayed. Figure 11-4 shows the dialog box.

Figure 11-4 Interface after data importation is finished

Step 5 Click OK. Then the file is displayed properly.

----End



240

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

11.9 How Do I Set the Browser Under Citrix FarmNetworking?

Under Citrix farm networking, when you use the M2000 proxy server to log in to the LMT ona Citrix client, the LMT may be suspended, the verification code may be unavailable, orinitialization of the MML navigation tree may fail. When these problems occur, check thebrowser settings, including the setting of the browser proxy server and the HTTP 1.1 setting. Ifeither setting is wrong, reset it.

ContextYou can set the browser under Citrix farm networking in the following ways:l Script setting: An automatic setting script is placed on the domain control server. After a

Citrix user logs in to the server, the script automatically sets the browser.l Manual setting: The browser is set manually.

The Citrix server works in the farm mode. In farm mode, the primary Citrix server and secondaryCitrix servers work in cooperation to achieve load balancing. When a Citrix user logs in to theCitrix server on a Citrix client, the server in use may vary. The proxy server of the browsertherefore may need to be set again and again. We therefore recommend setting the browser usingthe script. With the script, each time the user visits the server, automatic setting of the browseris performed.

The following procedure uses Internet Explorer (IE) as an example.

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



241

\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 browser for the domain user.The domain user can change 10.121.49.213:80 in reg add %uu% /v ProxyServer /tREG_SZ /d "10.121.49.213:80" /f >nul in the script to the actual IP address of the proxyserver 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 an example of the domain name. The actual domain name may be different.

3. For details about how to create a domain user, refer to the Citrix Access Solution UserGuide.

4. Apply the script to the domain user.Assume that there is a user named hong01 in the hongtest unit of the citrixtest.comdomain.

a. Start Active Directory Users and Computer and double-click hongtest in theleft-side pane. In the right-side pane, all users in the hongtest unit are displayed,as shown in Figure 11-5.

Figure 11-5 Active Directory Users and Computers

b. In the right-side pane, right-click hong01. Choose Properties from the shortcut

menu. The hong01 Properties dialog box shown in Figure 11-6 is displayed.



242

Figure 11-6 Displayed hong01 Properties dialog box

c. In the hong01 Properties dialog box, click the Profile tab. Type IE-unset.bat

in Logon script, click Apply, and then click OK. Figure 11-7 shows thewindow.



243

Figure 11-7 Applying the script in the hong01 Properties dialog box

l Manual Setting

1. Check the proxy server setting of the browser.

a. Choose Tools > Internet Options on the tool bar of the IE. The InternetOptions dialog box is displayed.

b. On the Connections tab page, click LAN Settings. The Local Area Network(LAN) Settings dialog box is displayed.

c. In the Proxy server area, select Use a proxy server for your LAN (Thesesettings will not apply to dial-up or VPN connections). Set Address of theproxy server to the IP address of the M2000 and Port to 80.



244

2. Check HTTP 1.1 settings of the browser.a. Choose Tools > Internet Options on the tool bar of the IE. The Internet

Options dialog box is displayed.b. On the Advanced tab page, select Use HTTP 1.1 through proxy connections

under HTTP 1.1 settings, click Apply, and then click OK. Figure 11-8 showsthe window.

Figure 11-8 HTTP 1.1 settings

----End



245

11.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.Therefore, 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 >nulreg add %uu% /v ProxyHttp1.1 /t REG_DWORD /d "1" /f >nulsetlocal ENABLEDELAYEDEXPANSIONset uu="HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion



246

\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 exist 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

a. Log in to the Windows server with the account of administrator. ChooseStart > Run.

b. Type gpedit.msc in the displayed dialog box. Then click OK. The GroupPolicy Object Editor dialog box is displayed.

c. In the Group Policy Object Editor dialog box shown in Figure 11-9, chooseUser Configuration > Windows Settings > Scripts(Logon/Logoff).

Figure 11-9 Script

d. Double-click Logon. A dialog box shown in Figure 11-10 is displayed. Click

Show Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.



247

Figure 11-10 Logon

e. Click Add in the dialog box shown in Figure 11-11. A dialog box shown in

Figure 11-11 is displayed.

Figure 11-11 Adding a script

f. In the dialog box shown in Figure 11-11, click Browse to select the prepared

script and click OK. Then close the dialog box.



248

g. In the dialog box shown in Figure 11-10, click Apply and confirm to loadthe prepared script.

h. Restart the IE to validate the configuration.

NOTE

The users need to log in to the Citrix client to validate the configuration in the single Citrixnetwork.

– Script setting in a Citrix Farm network

a. 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 has be set, the users which belong to the organization unit canall succeed in logging in to the LMT.

l You can rename the group policy object.

b. Select the created group policy object and click Edit. In the displayed dialogbox shown in Figure 11-12, choose User Configuration > WindowsSettings > Scripts(Logon/Logoff).

Figure 11-12 Script

c. Double-click Logon. A dialog box shown in Figure 11-13 is displayed. Click

Show Files and copy the prepared script to the displayed directory. Then closethe dialog box displaying the directory.



249

Figure 11-13 Logon

d. Click Add in the dialog box shown in Figure 11-13. A dialog box shown in

Figure 11-14 is displayed.

Figure 11-14 Adding a script

e. In the dialog box shown in Figure 11-14, click Browse to select the prepared

script and click OK. Then close the dialog box.



250

f. In the dialog box shown in Figure 11-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 11-15.

Figure 11-15 Windows components wizard

2. Click Details... in the dialog box shown in Figure 11-15. In the displayed dialog box

shown in Figure 11-16, deselect For administrator groups and For all other usergroups.



251

Figure 11-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

11.11 Unable to Download or Install the Java or Flash Plug-in and Two File Manager Windows Displayed Windows IE8or Any Later Version Is Used

If users log in to the LMT in IE8 or later versions, an error message displays when they aredownloading or installing a Java or Flash plug-in, or two file manager windows are displayed.To solve the problem, disable SmartScreen Filter of IE8.

ContextSmartScreen Filter is a new function of IE8 and later versions. It prevents users from visitingphishing websites and prevents plug-ins from being installed automatically.

SmartScreen Filter causes an error message to be displayed when users are downloading theJava or Flash plug-in during login to the LMT.

In addition, two file manager windows displays after clicking File Manager.



252

Procedure

Step 1 On the menu bar of the IE browser, choose Safety > SmartScreen Filter > Turn OffSmartScreen Filter.

Step 2 In the displayed Microsoft SmartScreen Filter dialog box, select Turn off SmartScreenFilter and click OK to turn off the SmartScreen filter.

----End

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

PrerequisitesThe 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 11-17 are provided. Changing the default option as described below solves the previousproblem.



253

Figure 11-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

11.13 Any Further Operation Performed When Some LMTWeb Pages Fail 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



254

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

11.14 Configuring the HTTPS Login ModeThis section describes how to configure the HTTPS login mode and a security certificate. Userscan log in to the LMT through either HTTP or HTTPS. The login mode is configurable.

Prerequisitesl You have logged in to the LMT using a Built-In Administrator Account or External

User Accounts.

Context

HTTPS is Hypertext Transfer Protocol Secure. Based on HTTP, HTTPS introduces SSL (orTLS) to ensure transmission security. To put it simply, HTTPS is a combination of HTTP andSSL. To enter the HTTPS login mode, enter https://Website to be visited + Port No in the Addressbar of the browser. The default port No. is 443. Use the default port No. to enter the LMT loginpage.

Procedure

Step 1 Change the login mode

1. Log in to the LMT through HTTPS.

2. Run the MML command SET WEBLOGINPOLICY. In this step, set POLICY toHTTPS.

Step 2 Run the MML command RST OMUMODULE to restart the LMT so that the change take effect.In this step, set TG to ACTIVE and MNAME to weblmt.



255

CAUTION1. Running this command disconnects all online users from the LMT.

2. Normally, the restart is complete within 5 seconds. After the restart is complete, the changetake effect when users log in to the LMT again.

----End

11.15 What Do I Do if the Error "Certificate Invalid" IsDisplayed During an HTTPS Login

The LMT certificate and the certificate used to access the LMT through the M2000 proxy withdual IP addresses are not granted by any commercial organization. Therefore, they are not trustedby a browser such as IE by default. In such a scenario, the SSL certificate negotiation isperformed when you visit the LMT in HTTPS mode. If the organization for issuing the currentcertificate is not in the default trust list of Microsoft, the Certificate Invalid error is displayedon the browser. This error does not impair the LMT functions. This section describes how tocorrect the error Certificate Invalid displayed during a login to the LMT through HTTPS. Tocorrect this error, add the root certificate of the certificate in use to the Trusted RootCertification Authorities list.

Contextl Using an IE browser

1. After https://the external virtual IP address of the OMU, for example, https://10.141.115.219, is entered in the Address bar of the browser, a dialog box shown inFigure 11-18 or Figure 11-19 is displayed.

Figure 11-18 Dialog box showing "There is a problem with this website's securitycertificate" (IE7 or later versions)



256

Figure 11-19 Dialog box showing "Security Alert"(IE6)

2. Click Continue to this webpage(not recommended) in Figure 11-18 or Yes in

Figure 11-19 to enter the LMT login page. In the Address bar of the browser, anCertificate Error message is shown.

3. After clicking Certificate Error, An Certificate Invalid dialog box is shown.l Using a Firefox browser

1. After https://the external virtual IP address of the OMU, for example, https://10.141.115.219, is entered in the Address bar of the browser, a dialog box shown inFigure 11-20 is displayed. (The following figure uses Firefox3.0 as an example. Thedialog box varies with browser versions but has the same information.)



257

Figure 11-20 Dialog box showing "This Connection is Untrusted"

l Connection Through the M2000

1. After connecting through the M2000 with both IP addresses, an Certificate Invaliddialog box is shown.

Procedure

Step 1 Using an IE browserIn the Certificate Invalid dialog box, click View certificates to view the current certificate. Ifthe certificate displays Issued to: MBSC Certificate and Issued by: Huawei WirelessNetwork Product CA, as shown in Figure 11-21, perform the following steps:



258

Figure 11-21 MBSC Certificate

1. Download the certificate file rootca.pem by the 2.4.2 FTP Client and save this file to alocal path. (The certificate file is saved in the following directory: /bam/version_a/ftp/cert/default_cert. In this path, version_a is the active workspace of the OMU. If the activeworkspace of the OMU is version_b, change the directory to /bam/version_b/ftp/cert/default_cert.)

2. Double-click rootca.pem and the content of this file is displayed, as shown in Figure11-22. Create a .txt file, cut the content following -----END CERTIFICATE----- in therootca.pem file, and then paste it into this new .txt file. Save this new .txt file and renameit as rootca2.pem. The rootca2.pem is the new certificate file.



259

Figure 11-22 Content in the rootca.pem file

3. In the menu of the IE browser, choose Tools > Internet Options > Content tab and click

Certificate on this tab page, the Certificate dialog box is displayed.4. In the Certificates > Personal tab, and click Import on this tab page, the Certificate

Import Wizard dialog box is displayed.5. In the displayed Certificate Import Wizard dialog box, click Next, to import the certificate

file rootca.pem. Then click Next, choose Place all certificates in the following store, andthen click Browse. In the displayed dialog box, choose Trusted Root CertificationAuthorities and click Next to start the certificate file import.

6. Import the certificate file rootca2.pem.



260

7. Restart the browser so that the reconfiguration can take effect. If the error MismatchedAddress is displayed when you log in to the LMT after the browser is restarted, refer to"FAQ" in 11.16 Error 'Mismatched Address' Is Displayed During an HTTPS Loginfor troubleshooting.

8. Restart the browser so that the reconfiguration can take effect.

Step 2 Using an IE browserIn the Certificate Invalid dialog box, click View certificates to view the current certificate. Ifthe certificate displays Issued to: server and Issued by: hwca, as shown in Figure 11-23,perform the following steps:

Figure 11-23 Server Certificate

1. Click Install Certificate and Next. A dialog box shown in Figure 11-24 is displayed.



261

Figure 11-24 Certificate Import Wizard dialog box

2. In the Certificate Import Wizard dialog box, select Place all certificates in the following

store and click Browse. In the displayed dialog box, select Trusted Root CertificationAuthorities and click OK.

3. In the Certificate Import Wizard dialog box, click Next, Finish, and OK.4. Restart the browser so that the reconfiguration can take effect.

Step 3 Using an IE browserIn the Certificate Invalid dialog box, click View certificates. If the displayed information aboutthe current certificate is different from the information in the preceding conditions, import theroot certificate of the current certificate. Perform the following steps:1. Obtain the root certificate from the organization issuing the current certificate.2. In the menu of the IE browser, choose Tools > Internet Options > Content tab and click

Certificate on this tab page, the Certificate dialog box is displayed.3. In the Certificates > Personal tab, and click Import on this tab page, the Certificate

Import Wizard dialog box is displayed.4. In the displayed Certificate Import Wizard dialog box, click Next to import the certificate

file. Then click Next, choose Place all certificates in the following store, and then clickBrowse. Choose Trusted Root Certification Authorities and click Next to import thecertificate file.

5. Restart the browser to make the reconfiguration takes effect.

Step 4 Using a Firefox browser1. Click Add Exception shown in Figure 11-20. The Add Security Exception dialog box is

displayed, as shown in Figure 11-25.



262

Figure 11-25 Add Security Exception dialog box

2. Click Confirm Security Exception. After the website is added as a security exception, no

security error will be displayed during a login to the LMT using Firefox.3. Restart the browser to make the reconfiguration takes effect.

Step 5 Connection Through the M2000The certification path of the M2000 is shown as Figure 11-26.



263

Figure 11-26 Certification Path of the M2000

1. Choose General > Install Certificate in the Certificate dialog box. And Certificate

Import Wizard dialog box is displayed.2. Click Next in the Certificate Import Wizard dialog box and Certificate Store dialog box

is displayed. Then choose Place all Certificates in the following store.3. Click Browse, the Select Certificate Store dialog box is displayed. Then choose Trusted

Root Certification Authorities.4. Click OK, the Completing the Certificate Import Wizard dialog box is displayed.5. Click Finish, the Security Warning dialog box is displayed.6. Choose Yes in the Security Warning dialog box. The import was successful message is

displayed. Then Click OK.



264

7. Restart the browser to make the reconfiguration takes effect.

----End

11.16 Error 'Mismatched Address' Is Displayed During anHTTPS Login

A user uses an IP address rather than a domain name to access the LMT. Therefore, theMismatched Address error is displayed on the browser during an HTTPS login. This error doesnot impair the LMT functions. This section describes how to correct the error "MismatchedAddress" displayed during a login to the LMT through HTTPS. To correct this error, deselectthe Warn about certificate address mismatch* option.

Context1. Enter https://the external virtual IP address of the OMU, for example, https://

10.141.115.219, in the Address bar of the browser. A dialog box shown in the Figure11-27 or Figure 11-28is displayed.

Figure 11-27 Dialog box showing "There is a problem with this website's securitycertificate"(IE7 or later versions)



265

Figure 11-28 Dialog box showing "Security Alert"(IE6)

2. Click Continue to this webpage(not recommended) in Figure 11-27 or Yes in Figure

11-28 to enter the LMT login page. In the Address bar of the browser, an CertificateError message is shown.

3. Click Certificate Error. An Mismatched Address error dialog box is shown.

Procedure

Step 1 Choose Tools > Internet Options on the Menu bar of the browser. Click the Advanced tab inthe displayed dialog box shown in Figure 11-29.



266

Figure 11-29 Internet Options dialog box

Step 2 In the Internet Options dialog box, deselect Warn about certificate address mismatch* andclick OK.

NOTE

The reconfiguration takes effect after the browser is restarted.

----End

11.17 What Do I Do if Tracing and Monitoring FunctionsCannot Be Used?

Tracing and monitoring functions cannot be used after a successful login to the LMT. Solve thisproblem by using the following methods.

ContextAn error message is displayed, as shown in Figure 11-30.



267

Figure 11-30 Application Error

After clicking Details, detailed error information is displayed. You need to correct the errorbased on the error type as follows:l If the "java.lang.ClassNotFoundException" error is displayed, perform steps 1 and 2.

l If the "netscape.javascript.JSException" error is displayed, perform step 3.

l If this problem occurs in Citrix Farm networking, you need to perform related steps on theCitrix Farm server rather than on the local PC. If you have no permission to log in to theCitrix Farm server, you cannot directly access Windows Control Panel on the Citrix Farmserver. To access it, right-click the Java icon on Windows system tray on the local PC andchoose Open Control Panel from the short-cut menu. The following figure shows thewindow:



268

l If this problem cannot be solved by performing the following steps, uninstall and reinstallJava.

l This problem is caused by a Java defect. For details about this defect, visit http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6967414.

Procedure

Step 1 Enable the next-generation Java plug-in again.1. Open Control Panel in the Windows operating system and double-click Java. The Java

Control Panel dialog box is displayed. In the Java Control Panel dialog box, click theAdvanced tab, clear Enable the next-generation Java Plug-in (requires browserrestart) under Java Plug-in and click OK.

2. Select Enable the next-generation Java Plug-in (requires browser restart) by referringto step a and click OK. Figure 11-31 shows the window.



269

Figure 11-31 Enabling the next-generation Java plug-in

3. Restart the browser to enable the new setting to take effect.

Step 2 Delete temporary Java files.1. If this problem persists after performing step 1, delete temporary Java files.2. Open Control Panel in the Windows operating system and double-click Java. The Java

Control Panel dialog box is displayed.3. In the displayed Java Control Panel dialog box, click Setting. The Temporary Files

Settings dialog box is displayed. Check the amount of disk space set for storing temporaryfiles, as shown in Figure 11-32.



270

Figure 11-32 Checking the amount of disk space set for storing temporary files

4. Check the amount of disk space used for storing temporary Java files in the directory where

temporary Java files are saved. The part marked in red frame in Figure 11-33 shows thedirectory. This amount is greater than the preset one.



271

Figure 11-33 Directory where temporary Java files are saved

5. Delete folders in this directory manually or by clicking Delete Files shown in the figure

above.

NOTEBefore deleting folders in this directory, close all running LMT clients.

6. Log in to the LMT again to check whether this problem is solved.

Step 3 Install Windows operating system patch KB960714.1. 11.4 Installing OS Patches

----End

11.18 What Do I Do If There Is No Response or Any ErrorMessage After a Tracing or Monitoring Task Is Created?

Some time after a successful login to the LMT, you may suddenly find that batch processingfails with no error message. Alternatively, after a tracing or monitoring task is created, the taskpage is not opened. There is no response or any error message. The NE task list shows that thistask has been successfully created. If you open a new browser and log in to the LMT again, thetask nevertheless can be successfully created. If either of the previous problems occurs, performthe following operations:



272

Procedure

Step 1 Open Control Panel in the Windows operating system and double-click Java. The JavaControl Panel dialog box is displayed.

Step 2 In the displayed Java Control Panel dialog box, click the Advanced tab, choose SecurityMixedcode (sandboxed vs. trusted) security verification, and select Disable verification (notrecommended). Figure 11-34 shows the dialog box.

Figure 11-34 Java Control Panel dialog box

Step 3 Close all browsers and log in to the LMT again.

----End



273

11.19 What Do I Do If the File Manager FunctionsImproperly?

When the file manager functions improperly or cannot be used, perform the followingoperations:

Procedurel If you use HTTPS to log in to the LMT, check that Do not save encrypted pages to

disk is cleared. Selecting this security option causes the file manager to be unavailable.Therefore, clear this option as follows:

1. Open the Internet Options dialog box, click the Advanced tab, and clear Do not saveencrypted pages to disk. Figure 11-35 shows the dialog box.

Figure 11-35 Internet Options dialog box

l Check that temporary Java files are saved on the computer. If they are not, the file managerfunctions improperly. Perform the following operations:

1. Open Control Panel in the Windows operating system and double-click Java. TheJava Control Panel dialog box is displayed.



274

2. In the displayed Java Control Panel dialog box, click Setting. The Temporary FilesSettings dialog box is displayed. Select Keep temporary files on my computershown in Figure 11-36.

Figure 11-36 Temporary Files Settings dialog box

----End

11.20 What Do I Do If BTS Nodes Cannot Be DisplayedUnder Device Navigation Tree

After a successful login to the LMT, you may find that BTS nodes cannot be displayed underDevice Navigation Tree. After upgrading the browser, you find that the nodes can be displayednormally. This problem occurs because data under Device Navigation Tree on the LMT iscompressed whereas Internet Explorer 6 SP2 does not support compression of chunked data.Solve this problem by using either of the following methods.

ContextBTS nodes cannot be displayed under Device Navigation Tree, as shown in Figure 11-37.



275

Figure 11-37 BTS nodes cannot be displayed

Procedurel Method 1: For the operating system Windows XP Service Pack 2 or 3, install the KB982381

patch. To download this patch, visit http://www.microsoft.com/downloads.l Method 2: Upgrade the browser. You are advised to upgrade it to Internet Explorer 8.

----End

11.21 What Do I Do if the Alarm/Event Function BecomesUnavailable?

When starting or using the Alarm/Event function after a successful login to the LMT, the pagemay become white with an exclamation mark displayed in the center. The exclamation mark iscircled in gray, as shown in the following figure: Solve this problem by using the followingmethods.

ContextThe page of alarm/event function become white, as shown in Figure 11-38.



276

Figure 11-38 Alarm/Event Function

Procedurel Method 1: Check that the flash player is of a version supported by the LMT, Flash Player

10.1.82 or later. Flash Player 10.1.82 is available on the LMT login web page. For laterversions, visit http://adobe.com. If installing the flash player fails and a message sayingthat the version is not the latest one is displayed, perform the following steps:1. Download and install the flash player of the latest version.2. Choose StartRun and enter regedit to open Registry Editor. Navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\FlashPlayer\SafeVersions, delete the item with the DWORD value of 10.0, and reinstall the flashplayer.

l Method 2: Check that the browser type is supported by the LMT, Internet Explorer orFirefox. For details about the supported browser versions, see 2.1 ConfigurationRequirements of the LMT PC.

----End

11.22 What Do I Do if the Message 'Class doesn't supportAutomation' Is Displayed in an IE Browser?

After clicking Login in an Internet Explorer (IE) browser, you find a blank window displayedand login unable to continue. In the bottom left corner of the IE browser, a yellow error icon isdisplayed. The icon says "Class doesn't support Automation". To solve the problem, performthe following steps:

Contextl This problem occurs because some registration components are missing from the IE

browser. To solve this problem, register the following components again:– msscript.ocx– dispex.dll



277

– vbscript.dll– scrrun.dll– urlmon.dll

Procedure

Step 1 In Windows, choose StartRun and enter RegSvr32 msscript.ocx. To register the othercomponents again, replace the typed component in italics.

Step 2 After registering all the components again, clear the cache memory of the IE browser.

Step 3 Log in to the LMT again.

----End

11.23 What Do I Do if Java Installation FailsDuring Java installation, the message "Error 25099, Unzipping core files failed." is displayed.To solve the problem, perform the following steps:

Procedure

Step 1 Delete all files in the Java installation path. The default installation path is C:\Program Files\Java\jre6\.

Step 2 If step 1 fails because files are locked or in use, restart the system and repeat step 1.

Step 3 Reinstall Java.

----End

11.24 What Do I Do if the LMT Login Web Page Cannot BeOpened with the PC OMU Installed?

With the PC OMU installed in Windows 7, the LMT login web page cannot be opened. Inaddition, the LMT process cannot be found in the task manager.

ContextPort 80 is the default port for LMT login. This problem occurs because port 80 is occupied bya default HTTP service in Windows 7.

To confirm the cause, run the netstat –naop tcp command at the Windows 7 command promptto check whether port 80 is occupied. If it is occupied by a process with the PID of 4, as shownin the following figure, the problem occurs due to the cause.



278

This process is a system process and therefore cannot be closed directly. To close it, performthe following steps:

Procedure

Step 1 In Windows, choose StartRun and enter regedit to open Registry Editor.

Step 2 Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP.

Step 3 Change the DWORD value of Start to 0.

Step 4 Restart the PC and log in to the LMT again.

----End

11.25 What Do I Do if Changing Settings for the Next-Generation Java Plug-in Fails?

When changing settings for Enable the next-generation Java Plug-in, you are prompted witha message indicating that the changing fails because one or more browsers are running. As amatter of fact, no browser is running. The following figure shows the message: To solve theproblem, perform the following steps.

ContextChanging Settings for Next-Generation Java Plug-in Fails, the error message is shown inFigure 11-39.



279

Figure 11-39 Unable to change Java Plug-in settings

This problem is caused by a Java defect. The setting changing fails not because browsers arerunning but because the user has no permission to perform the operation.

To change the settings, the user must belong to the Power Users group or have more rights.

Perform the following steps to grant the user more rights.

ProcedureStep 1 Log in to the operating system (OS) using an administrator-level account authorized for the

administrator's operations. Right-click My computer and choose Manage from the shortcutmenu.

Step 2 In the Computer Management window, choose System toolsLocal Users andGroupsGroups and double-click Power Users in the right pane of the window, as shown in thefollowing figure:

Step 3 In the displayed window, click Add, add the user account to the Power Users group, and clickOK, as shown in the following figures:



280



281

Step 4 Use an administrator-level account to delete the Windows folder in C:\Documents and Settings\User account\Local Settings\Application Data\Microsoft\Windows shown in the followingfigure:

Step 5 Use the user account to log in the OS again after the previous steps are complete. The useraccount now has permission to change settings for Enable the next-generation Java Plug-in.

NOTE

After changing the settings, you can restore the user rights. To restore the user rights, log in to OS using anadministrator-level account again and remove the user account from the Power Users group by referring to steps1 through 3. The change of the user rights does not affect settings for Enable the next-generation Java Plug-in.

----End



282

11.26 Error Message"This user session already exists" UponLogin to LMT

The interface displays an error message "This user session already exists" upon login to LMT.Solve the problem by using the method described in the procedure part.

ContextTo enhance system security, the client browser uses Cookie to store the session information ofusers who have successfully logged in. Due to the session Cookie mechanism, the userencounters the following problems when using LMT:

l Problem 1: For the same NE, the user desires to log in to multiple LMTs. After successfullylogging in to the first LMT, the user logs in to the second LMT of the NE, and the interfacedisplays "this user session already exists". This is because all browser windows opened bythe same user share the same session under the session sharing mechanism of IE8 or IE9and Firefox enabled by default. As a result, when the user attempts to repeatedly log in tothe LMTs of the same NE, the system determines a repeated login of the same user session.For the IE6/7 browser in which each browser window uses independent sessions, thisproblem does not arise.

l Problem 2: The LMT interface displays the error "this user session already exists", whilethe user has not carried out the operation described in Problem 1. This is because theprevious session information remains valid due to an abnormal exit from LMT. As a result,the LMT determines a repeated login attempt when the same user tries to login to the LMT.This problem arises when the browser automatically recovers from breaking down duringuse of the LMT, or when the pop-up LMT window is blocked by the browser pop-up blockerenabled.

Procedurel For Problem 1, the following method is used:

1. In the menu bar of the IE browser, click File > New Session, to start a new IE browserwindow and log in to the LMT.

NOTE

This method applies only to the IE8 or IE9 browser, not Firefox. Users of the Firefox browser canlog in to only one LMT of a single NE.

l For Problem 2, the following method is used:1. The IE6/7 browser user needs to close the browser window of the current LMT login

interface, and the IE8/9 and Firefox users need to close all opened browser windowsto invalidate the old sessions.

2. If the pop-up blocker is enabled for the browser, disable it.3. Restart the browser and log in to LMT.

----End



283

11.27 The "Are You Sure You Want to Quit the Page?" DialogBox Is Displayed

After successful login to the LMT in the IE8 or IE9 browser, the "are you sure you want to quitthe page?" dialog box is displayed when the alarm feature is enabled. Solve the problem by usingthe method described in the procedure part.

Procedure

Step 1 Open the Internet Explorer, and then choose Tools > Internet Options from the menu bar. TheInternet Options dialog box is displayed. Click Advanced, and uncheck Automatic Recoveryfrom Page Layout Error.

Step 2 Restart the browser and log in to LMT again.

----End

11.28 Unable to Save Tracking and Monitoring DataWhen a tracking or monitoring task (such as the UE tracking task) is running on the LMT, it ispossible that the vast amounts of tracking or monitoring data cannot be saved even with sufficienthard disk space. Solve the problem by using the method described in the procedure part.

ContextThis problem arises when the operating system enables the system recovery function thatmonitors changes of the files on the hard disk and consumes some hard disk space. Withinsufficient hard disk space, the system displays "Insufficient hard disk space", and if a trackingor monitoring task is running on the LMT, it is likely that the tracking or monitoring data cannotbe saved.

Procedure

Step 1 Log in to the operating system (OS) using an administrator-level account authorized for theadministrator's operations. Right-click My computer and choose Properties.

Step 2 In the "System Properties" window, click System Recovery, select Disable System Recoveryon All Drivers, and click Submit, as shown in Figure 11-40.



284

Figure 11-40 System properties dialog box

----End

11.29 Slow Response During an LMT LoginThe LMT responses slowly when the users are trying to log in to the LMT. To solve the problem,perform the following steps:

Procedure

Step 1 In the Windows 2003 and Windows XP operating system (OS), choose Start > ControlPanel, and then click Add/Remove Programs, the Windows Components Wizard dialog boxis displayed.

Step 2 In the Windows Components Wizard dialog box, deselect Upload Root Certificates, as shownin the following figure. Then click Next to complete the modification.



285

----End

11.30 Unclear Grids in the Tables in the MML Online HelpThe grids in the tables are not clear in MML online help when users log in to the LMT by somecomputers. To solve the problem, perform the following steps.

ContextThe grids in the tables are not clear in MML online help, as shown in Figure 11-41.



286

Figure 11-41 Unclear Grids in the Tables in the MML Online Help

Procedure

Step 1 In the menu of the IE browser, choose Tools > Compatibility View Settings. In the displayedCompatibility View Settings dialog box, select Display all websites in Compatibility View.

Step 2 Restart the browser and log in to the LMT to check the MML online help. The problem is solved.

----End

11.31 MML Command Failed to Be Executed or No Responseto Tracing Tasks After the Browser Is Upgraded to IE8

After the browser is upgraded from IE6 to IE8, some cache files cannot be removed. As a result,the system displays a Please check the MML macro configure file! message when an MMLcommand is executed, or there is no response after tracing tasks are created. To solve thisproblem, you need to manually remove cache files and cookies.

Contextl When MML commands are executed, the system displays a Please check the MML macro

configure file! message, as shown in Figure 11-42.



287

Figure 11-42 System message "Please check the MML macro configure file!"

l There is no response after tracing tasks are created.

Procedure

Step 1 On the menu bar of the IE browser, choose Tool > Internet Options. The Internet Optionsdialog box is displayed.

Step 2 Click General > Browsing history and click Delete. The Delete Browsing History dialog boxis displayed.

Step 3 In the Delete Browsing History dialog box, deselect the Preserve Favorites website data.

Step 4 Select Cookies and Temporary Internet files, and then click Delete and close the DeleteBrowsing History dialog box.

Step 5 Click the General tab and click Setting in Browsing history. The Temporary Internet Filesand History Settings dialog box is displayed.

Step 6 Click View files in the Temporary Internet Files and History Settings dialog box, remove alldisplayed files, and close the Internet Options dialog box.

----End



288

Bsc6900 Umts Lmt User Guide(v900r014c00_07)(PDF)-En

Documents

Transcript of Bsc6900 Umts Lmt User Guide(v900r014c00_07)(PDF)-En