node b lmt user guide for huawei systems

NodeBV200R013

LMT User Guide

Issue 04

Date 2011-09-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes installation and operation methods for the NodeB Local MaintenanceTerminal (LMT).

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

Product Name Product Version

BTS3900 WCDMA (hereinafter referred toas BTS3900)

V200R013

BTS3900A WCDMA (hereinafter referredto as BTS3900A)

V200R013

BTS3900L WCDMA (hereinafter referredto as BTS3900L)

V200R013

DBS3900 WCDMA (hereinafter referred toas DBS3900)

V200R013

Intended AudienceThis document is intended for:

l System engineersl Field engineersl Shift operatorsl Network operators

Organization1 Changes in the NodeB LMT User Guide

NodeBLMT User Guide About This Document


ii

This chapter describes changes in the NodeB LMT User Guide of each issue.

2 Introduction to the NodeB LMT

This chapter describes the functions and configuration requirements of the LMT.

3 Components of the NodeB LMT

The NodeB LMT communicates with the NodeB through a Local Area Network (LAN) or WideArea Network (WAN). You can operate and maintain a NodeB on the LMT. The LMT consistsof the following parts: Local Maintenance Terminal, Trace Viewer, and Monitor Viewer.

4 Installing and Verifying the NodeB LMT Application

This chapter describes how to install and verify the NodeB LMT application.

5 Getting Started with the NodeB LMT

This chapter describes how to get started with the NodeB LMT. Before using the LMT, youmust connect, log on, and configure the LMT.

6 Running NodeB MML Commands

This chapter describes how to run Man Machine Language (MML) commands. You may run asingle MML command or batch commands.

7 Managing NodeB Alarms

This chapter describes how to manage NodeB alarms. You can set properties for the alarmmanagement system, query alarms and resolve problems associated with them.

8 Managing NodeB Equipment

This chapter describes how to manage the NodeB and related boards. The LMT provides theinterface of the device panel and physical topology for the routine maintenance of the NodeB.

9 Managing the Interface Tracings

After creating an interface tracing task, you can browse and save the traced messages.

10 Managing NodeB Common Monitoring

This chapter describes how to monitor the CPU/DSP occupancy of the NodeB. It consists of thefollowing tasks: displaying the CPU/DSP occupancy of the NodeB, browsing and savingmonitoring files. It is useful for reviewing system resources.

11 Managing the NodeB Software

This chapter describes how to upgrade the NodeB software.

12 Managing NodeB Files

This chapter describes how to download and back up the NodeB data configuration file, andhow to upload NodeB log files and the device archive file.

13 Monitoring the NodeB Performance in Real Time

This chapter includes procedures for monitoring the NodeB performance and status in real-timeon the LMT.

14 Managing Interference Detection for the NodeB



iii

By analyzing the spectral and power distribution of sampled data, you can monitor theinterference in the frequency and time domains in radio environments.

15 Commissioning the NodeB Equipment

This chapter describes how to commission the NodeB equipment by sending transparentmessages and performing COM port redirection.

16 Managing NodeB Frequency Spectrum Scanning

This section describes how to manage NodeB frequency spectrum scanning. This task enablesusers to view information about frequency spectrum with information about the time domainand frequency domain during operation collected. This task also enables users to reviewfrequency spectrum history.

ConventionsSymbol Conventions

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

Symbol Description

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

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

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

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

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

General Conventions

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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



iv

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

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

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

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

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

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.



v

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.



vi

Contents

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

1 Changes in the NodeB LMT User Guide..................................................................................1

2 Introduction to the NodeB LMT.................................................................................................42.1 Definitions of the LMT.......................................................................................................................................52.2 Functions of the NodeB LMT............................................................................................................................52.3 Computer Requirements of the LMT.................................................................................................................5

3 Components of the NodeB LMT................................................................................................73.1 NodeB Local Maintenance Terminal..................................................................................................................83.2 Trace Viewer....................................................................................................................................................103.3 Monitor Viewer................................................................................................................................................113.4 TrafficReview...................................................................................................................................................12

4 Installing and Verifying the NodeB LMT Application.......................................................144.1 Installing the NodeB LMT Application............................................................................................................154.2 Verifying the Installed NodeB LMT Application............................................................................................16

5 Getting Started with the NodeB LMT.....................................................................................195.1 Running the NodeB LMT.................................................................................................................................20

5.1.1 Setting the IP Address of the NodeB LMT PC.......................................................................................205.1.2 Locally Connecting the NodeB LMT PC to the NodeB..........................................................................225.1.3 Remotely Connecting the NodeB LMT PC to the NodeB (Through RNC BAM)..................................235.1.4 Remotely Connecting the NodeB LMT PC to the NodeB (Through M2000)........................................245.1.5 Setting the Route from the NodeB LMT PC to the NodeB.....................................................................245.1.6 Locally Logging In to the NodeB on the NodeB LMT...........................................................................255.1.7 Remotely Logging In to the NodeB LMT (Through RNC BAM)..........................................................265.1.8 Remotely Logging In to the NodeB LMT (Through M2000).................................................................27

5.2 Setting the Properties of the NodeB LMT........................................................................................................295.3 Changing the Password for Login to the NodeB LMT....................................................................................305.4 Setting the Information About an Office on the NodeB LMT.........................................................................305.5 Locking the NodeB LMT.................................................................................................................................325.6 Unlocking the NodeB LMT..............................................................................................................................325.7 Exiting from the NodeB LMT..........................................................................................................................33

6 Running NodeB MML Commands..........................................................................................34

NodeBLMT User Guide Contents


vii

6.1 Introduction to NodeB MML Commands........................................................................................................356.2 Running a Single NodeB MML Command......................................................................................................376.3 Running NodeB Batch MML Commands........................................................................................................38

7 Managing NodeB Alarms..........................................................................................................417.1 Concepts Related to NodeB Alarm Management.............................................................................................42

7.1.1 Alarm Types............................................................................................................................................427.1.2 Alarm Logs..............................................................................................................................................427.1.3 Alarm Severity.........................................................................................................................................427.1.4 Alarm Classification Based on Network Management...........................................................................43

7.2 Setting the Properties of the NodeB Alarm Management System...................................................................437.2.1 Setting the Properties of the NodeB Alarm Query Window...................................................................447.2.2 Setting NodeB Alarm Prompt..................................................................................................................457.2.3 Setting the Preferences for Printing Alarms in Real Time......................................................................46

7.3 Handling NodeB Alarms..................................................................................................................................477.3.1 Browsing Alarms.....................................................................................................................................477.3.2 Querying Alarm Logs..............................................................................................................................477.3.3 Manually Recovering an Alarm..............................................................................................................497.3.4 Saving the Information of a NodeB Alarm.............................................................................................497.3.5 Manually Printing Alarm Information.....................................................................................................507.3.6 Querying Alarm Handling Suggestions...................................................................................................507.3.7 Shielding NodeB Alarms.........................................................................................................................517.3.8 Clearing the Alarms.................................................................................................................................537.3.9 Refreshing the Alarm Window................................................................................................................53

8 Managing NodeB Equipment...................................................................................................558.1 Operating the NodeB Device Panel..................................................................................................................56

8.1.1 Introduction to the NodeB Device Panel.................................................................................................568.1.2 Starting the NodeB Device Panel............................................................................................................578.1.3 Showing or Hiding the Legend on the NodeB Device Panel..................................................................578.1.4 Showing or Hiding the Failure Bar on the NodeB Device Panel............................................................58

8.2 Using the Physical Topology............................................................................................................................588.2.1 Introduction to Physical Topology..........................................................................................................598.2.2 Starting the Physical Topology................................................................................................................618.2.3 Showing or Hiding the Legend of the Physical Topology......................................................................61

8.3 NodeB-Level Operations..................................................................................................................................628.3.1 Querying the Active Version of the NodeB............................................................................................628.3.2 Querying the Software Version of the NodeB.........................................................................................628.3.3 Resetting the NodeB................................................................................................................................63

8.4 NodeB Board-Level Operations.......................................................................................................................648.4.1 Introduction to NodeB Board-Oriented Operations................................................................................648.4.2 Querying the State of a NodeB Board.....................................................................................................668.4.3 Querying Active Alarms of NodeB Boards.............................................................................................688.4.4 Querying the Version of a NodeB Board................................................................................................69



viii

8.4.5 Querying the CPU Usage of a NodeB Board..........................................................................................698.4.6 Querying the E1/T1 Link Status..............................................................................................................708.4.7 Querying the E1/T1 Work Mode.............................................................................................................718.4.8 Querying the STM-1 State.......................................................................................................................718.4.9 Querying the STM-1 Working Mode......................................................................................................728.4.10 Blocking/Unblocking a NodeB Board...................................................................................................738.4.11 Resetting a NodeB Board......................................................................................................................748.4.12 Adding and Removing a NodeB Board.................................................................................................758.4.13 Querying the Current Clock Status........................................................................................................758.4.14 Querying the Sequence ID of the RRU.................................................................................................768.4.15 Adding a Sector.....................................................................................................................................778.4.16 Modifying the Emission Power of the RRU..........................................................................................798.4.17 Setting Floor and Position.....................................................................................................................808.4.18 Querying the Board Manufacturing Information...................................................................................808.4.19 Opening the Related Shelf.....................................................................................................................81

9 Managing the Interface Tracings..............................................................................................829.1 Basic Concepts of the Interface Tracing...........................................................................................................849.2 Tracing Iub interface Messages........................................................................................................................849.3 Tracing SCTP Messages...................................................................................................................................859.4 Tracing IP Messages.........................................................................................................................................869.5 Tracing ICP Messages......................................................................................................................................869.6 Tracing SAAL Messages..................................................................................................................................869.7 Tracing User Messages.....................................................................................................................................879.8 Tracing Cell Messages......................................................................................................................................889.9 Tracing PPP Messages......................................................................................................................................889.10 Tracing MP Messages....................................................................................................................................899.11 Tracing MAC Messages.................................................................................................................................899.12 Tracing PTP Messages...................................................................................................................................899.13 Basic Operations of Interface Tracings..........................................................................................................90

9.13.1 Browsing Traced Messages Online.......................................................................................................909.13.2 Querying the Properties of the Tracing Task.........................................................................................919.13.3 Viewing a Message Translation............................................................................................................919.13.4 Automatically Saving Traced Messages................................................................................................929.13.5 Saving Traced Messages Manually.......................................................................................................929.13.6 Suspending a Tracing Task....................................................................................................................939.13.7 Resuming a Tracing Task......................................................................................................................939.13.8 Closing a Tracing Task..........................................................................................................................939.13.9 Browsing a Traced Message Offline.....................................................................................................94

9.14 Interface Reference for Managing the Interface Tracing...............................................................................949.14.1 Interface Reference for IUB Tracing.....................................................................................................959.14.2 Interface Reference for SCTP Tracing..................................................................................................959.14.3 Interface Reference for IP Tracing........................................................................................................95



ix

9.14.4 Interface Reference for ICP Tracing......................................................................................................969.14.5 Interface Reference for SAAL Tracing.................................................................................................979.14.6 Interface Reference for User Tracing....................................................................................................979.14.7 Interface Reference for Cell Tracing.....................................................................................................989.14.8 Interface Reference for PPP Tracing.....................................................................................................999.14.9 Interface Reference for MP Tracing......................................................................................................999.14.10 Interface Reference for MAC Tracing...............................................................................................1009.14.11 Interface Reference for PTP Tracing.................................................................................................1019.14.12 Interface Reference for Trace Viewer...............................................................................................101

10 Managing NodeB Common Monitoring.............................................................................10310.1 Displaying the NodeB CPU/DSP Usage......................................................................................................10410.2 Saving NodeB Monitoring Files...................................................................................................................10510.3 Browsing a NodeB CPU/DSP Monitoring File Offline...............................................................................10610.4 Interface Reference for Managing NodeB Common Monitoring.................................................................106

10.4.1 Interface Reference for Adding a Monitoring Task............................................................................10610.4.2 Interface Reference for CPU/DSP Usage Monitoring.........................................................................107

11 Managing the NodeB Software.............................................................................................10811.1 Overview of the NodeB Software................................................................................................................10911.2 Managing the BootROM Software of the NodeB........................................................................................110

11.2.1 Downloading the NodeB BootROM...................................................................................................11011.2.2 Activating the NodeB BootROM........................................................................................................111

11.3 Upgrading the NodeB Software...................................................................................................................11211.3.1 Downloading the NodeB Software......................................................................................................11211.3.2 Supplying the NodeB Software...........................................................................................................11311.3.3 Activating the NodeB Software...........................................................................................................11411.3.4 Activating Board Software..................................................................................................................11511.3.5 Synchronizing Software Versions of the NodeB.................................................................................116

11.4 Managing the NodeB Cold Patch.................................................................................................................11711.4.1 Downloading the NodeB Cold Patch...................................................................................................11711.4.2 Supplying the NodeB Cold Patch........................................................................................................11811.4.3 Activating NodeB Cold Patch.............................................................................................................11911.4.4 Downloading the Cold Patch for the NodeB BootROM.....................................................................12011.4.5 Activating the Cold Patch for the NodeB BootROM..........................................................................121

11.5 Managing the NodeB Hot Patch...................................................................................................................12211.5.1 Downloading the NodeB Hot Patch....................................................................................................12211.5.2 Activating the NodeB Hot Patch.........................................................................................................12311.5.3 Confirming the NodeB Hot Patch.......................................................................................................12411.5.4 Deactivating the NodeB Hot Patch......................................................................................................12511.5.5 Removing the NodeB Hot Patch.........................................................................................................12511.5.6 Rolling Back the NodeB Hot Patch.....................................................................................................126

11.6 Managing the Multi-Version Software of the NodeB..................................................................................12711.6.1 Downloading the Multi-Version Software of the NodeB....................................................................127



x

11.6.2 Activating the Multi-Version Software of the NodeB.........................................................................12811.7 Interface Reference for Managing NodeB Software....................................................................................129

11.7.1 Interface Reference for Updating the Software...................................................................................12911.7.2 Interface Reference for Supplying NodeB Software...........................................................................13011.7.3 Interface Reference for Synchronizing Version..................................................................................13111.7.4 Interface Reference for Activating Board Software............................................................................13111.7.5 Interface Reference for Upgrading NodeB Software..........................................................................13111.7.6 Interface Reference for Status Description and Progress Indicator.....................................................13311.7.7 Interface Reference for Upgrading BootROM....................................................................................13411.7.8 Interface Reference for Upgrading Patch............................................................................................13411.7.9 Interface Reference for Upgrading NodeB Hot Patch.........................................................................13511.7.10 Interface Reference for Upgrading Multi-Version Software.............................................................13611.7.11 Interface Reference for Setting FTP Server.......................................................................................136

12 Managing NodeB Files...........................................................................................................13812.1 Concepts of NodeB File Management..........................................................................................................139

12.1.1 File Types of the NodeB......................................................................................................................13912.1.2 Obtaining NodeB Files........................................................................................................................141

12.2 Managing the NodeB Data Configuration Files...........................................................................................14112.2.1 Downloading the NodeB Data Configuration File..............................................................................14212.2.2 Backing up the NodeB Data Configuration File.................................................................................142

12.3 Uploading NodeB Files to the FTP Server...................................................................................................14312.3.1 Uploading the NodeB Log File to the FTP Server..............................................................................14312.3.2 Uploading NodeB Device Archive File...............................................................................................145

12.4 Downloading the NodeB Extral Configuration File.....................................................................................14612.5 Interface Reference for Managing the NodeB File.......................................................................................146

12.5.1 Interface Reference for Data Configure File Transfer.........................................................................14612.5.2 Interface Reference for Device Archives Transfer..............................................................................14712.5.3 Interface Reference for Transferring Other Files................................................................................14812.5.4 Interface Reference for Detailed Information About Successful and Failed Files..............................15012.5.5 Interface Reference for Downloading Extral XML configuration file................................................150

13 Monitoring the NodeB Performance in Real Time...........................................................15213.1 Collecting the IP Clock Data........................................................................................................................15413.2 Monitoring the Traffic over the Transmission Ports....................................................................................15413.3 Monitoring the Traffic over the Transmission Links...................................................................................15713.4 Querying the Service Resources of a Cell....................................................................................................15913.5 Measuring the Cell-Level RTWP.................................................................................................................16113.6 Measuring the Board-Level RTWP..............................................................................................................16213.7 Testing the NodeB Clock.............................................................................................................................16313.8 Scanning the Uplink Frequency...................................................................................................................16413.9 Monitoring Output Power of the NodeB......................................................................................................16513.10 Monitoring the Temperature of the NodeB................................................................................................16713.11 Querying the Resources of a NodeB Board................................................................................................168



xi

13.12 Monitoring the Cell Service Throughput....................................................................................................16913.13 Common Operations for Real-time Performance Monitoring on the NodeB.............................................170

13.13.1 Browsing Monitoring Results of NodeB Online...............................................................................17013.13.2 Saving Monitoring Results of the NodeB..........................................................................................17013.13.3 Stopping a Monitoring Task of the NodeB.......................................................................................17113.13.4 Browsing Monitoring Results of the NodeB Offline.........................................................................171

13.14 Interface Reference for Monitoring the NodeB Performance in Real Time..............................................17213.14.1 Interface Reference for Collecting IP Clock Data.............................................................................17213.14.2 Interface Reference for Traffic Monitoring over the Transmission Ports.........................................17213.14.3 Interface Reference for Traffic Monitoring over the Transmission Links........................................17513.14.4 Interface Reference for Querying Cell Service Resources................................................................17713.14.5 Interface Reference for Measuring the Cell RTWP..........................................................................17813.14.6 Interface Reference for Measuring the Board RTWP.......................................................................17813.14.7 Interface Reference for Testing the Clock.........................................................................................17813.14.8 Interface Reference for Scanning the UL Frequency........................................................................17913.14.9 Interface Reference for Monitoring the Output Power......................................................................17913.14.10 Interface Reference for Monitoring the Temperature......................................................................18013.14.11 Interface Reference for Querying the Resources of a Board...........................................................18013.14.12 Interface Reference for the Cell Traffic Throughput Statistics.......................................................181

14 Managing Interference Detection for the NodeB..............................................................18214.1 Interface Reference for Interference Detection............................................................................................184

15 Commissioning the NodeB Equipment..............................................................................18515.1 Starting the Serial Port Redirection..............................................................................................................18615.2 Starting CANBUS Redirection.....................................................................................................................18615.3 Sending Transparent Messages....................................................................................................................18715.4 Interface Reference for Commissioning the NodeB Equipment..................................................................187

15.4.1 Interface Reference for Setting the Serial Port Redirection................................................................18815.4.2 Interface Reference for Transparent Messages....................................................................................18815.4.3 Interface Reference for Setting the Serial Port Redirection................................................................18815.4.4 Interface Reference for SerialCmd .....................................................................................................189

16 Managing NodeB Frequency Spectrum Scanning............................................................19016.1 Interface Reference for FFT Frequency Spectrum Scanning.......................................................................192



xii

1 Changes in the NodeB LMT User Guide

This chapter describes changes in the NodeB LMT User Guide of each issue.

04 (2011-09-30)This is the fourth commercial release.

Compared with 03 (2011-08-30), this issue does not add any information.

Compared with 03 (2011-08-30), this issue incorporates the following changes:

Content Description

14 Managing Interference Detection forthe NodeB

The operations on NodeB offline interferencedetection for a multi-mode base station areadded.

Compared with 03 (2011-08-30), this issue does not exclude any topics.

03 (2011-08-30)This is the third commercial release.



Content Description

13.6 Measuring the Board-Level RTWP Updated the monitoring items and relateddescriptions.


02 (2011-06-10)This is the second commercial release.

NodeBLMT User Guide 1 Changes in the NodeB LMT User Guide


1



Content Description

16 Managing NodeB Frequency SpectrumScanning

Description in note is added.

12.4 Downloading the NodeB ExtralConfiguration File

The section is added: DownLoading theNodeB Extral Configuration File.

12.5.5 Interface Reference forDownloading Extral XML configurationfile

An interface reference for DownloadingExtral XML configuration file is added.


01 (2011-04-10)

This is the initial commercial release.

Compared with Draft A (2011-01-20), this issue does not add any information.

Compared with Draft A (2011-01-20), this issue incorporates the following changes:

Content Description


Description about managing NodeBfrequency spectrum scanning is added.

5.1.6 Locally Logging In to the NodeB onthe NodeB LMT

The section is added: Starting CANBUSRedirection.

15.4 Interface Reference forCommissioning the NodeB Equipment

Serial port commands and interfacereferences for setting serial port redirectionare added.

11.7 Interface Reference for ManagingNodeB Software

Three interface reference sections are added:Supplying NodeB Software, SoftwareSynchronization Status, and ActivatingBoard Software.

13.1 Collecting the IP Clock Data Description about IP clock data is changed.

9 Managing the Interface Tracings Two sections are added: Tracing PPPMessages and Tracing MP Messages.

9.14 Interface Reference for Managing theInterface Tracing

Two interface reference sections are added:Tracing PPP Messages and Tracing MPMessages.

13 Monitoring the NodeB Performance inReal Time

Cell-level measurement of received totalwideband power (RTWP) is added.



2

Content Description

13.14.5 Interface Reference for Measuringthe Cell RTWP

An interface reference for cell-level RTWPmeasurement is added.

8.4.9 Querying the STM-1 Working Mode MML mode about querying the STM-1Working Mode is modified.

8.4.18 Querying the Board ManufacturingInformation

MML mode about querying the BoardManufacturing Information is modified.

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

Draft A (2011-01-20)

This is Draft A of V200R013.

Compared with issue 03 (2010-06-05) of V200R012, this issue does not add any information.

Compared with issue 03 (2010-06-05) of V200R012, this issue incorporates the followingchanges:

Content Description

5.1.6 Locally Logging In to the NodeB onthe NodeB LMT

The procedure for logging in to the NodeBthrough the LMT is updated.

5.1.7 Remotely Logging In to the NodeBLMT (Through RNC BAM)


5.1.8 Remotely Logging In to the NodeBLMT (Through M2000)


9.14.5 Interface Reference for SAALTracing

The interface reference for SAAL tracing isupdated.

13.2 Monitoring the Traffic over theTransmission Ports

Description about the result of trafficmonitoring over ports is modified.

13.3 Monitoring the Traffic over theTransmission Links

Description about the result of trafficmonitoring over transmission links ismodified.

13.14.2 Interface Reference for TrafficMonitoring over the Transmission Ports

The interface reference for traffic monitoringover ports is updated.

13.14.3 Interface Reference for TrafficMonitoring over the Transmission Links

The interface reference for traffic monitoringover transmission links is updated.

Compared with issue 03 (2010-06-05) of V200R012, this issue excludes the following topic:

l NodeB RF performance test (141 test)



3

2 Introduction to the NodeB LMT

About This Chapter

This chapter describes the functions and configuration requirements of the LMT.

2.1 Definitions of the LMTThis section provides definitions of the LMT, LMT PC, and LMT application, which helps usersdifferentiate between them.

2.2 Functions of the NodeB LMTThe NodeB LMT is used for NodeB commissioning, routine maintenance, and troubleshooting.

2.3 Computer Requirements of the LMTThis section describes the hardware and software requirements of the LMT, and thecommunication capability requirements.

NodeBLMT User Guide 2 Introduction to the NodeB LMT


4

2.1 Definitions of the LMTThis section provides definitions of the LMT, LMT PC, and LMT application, which helps usersdifferentiate between them.

LMT

LMT is the operation and maintenance (OM) terminal installed with the Huawei LocalMaintenance Terminal software group, and connected to the actual OM network of the relatedNE. The LMT is used to operate and maintain an NE.

LMT PCThe LMT PC is the hardware of the LMT. It is the computer installed with the LMT application.

LMT ApplicationThe LMT application refers to the Huawei proprietary application, the Huawei LocalMaintenance Terminal software group, which is installed on the LMT PC.

2.2 Functions of the NodeB LMTThe NodeB LMT is used for NodeB commissioning, routine maintenance, and troubleshooting.

The NodeB LMT provides the following functions:

l Graphic user interfaces

l Alarm management, equipment management, message tracing management, softwareManagement, file management, real-time monitoring, equipment commission, andfrequency spectrum scanning

l MML commands are used for overall configuration and maintenance

2.3 Computer Requirements of the LMTThis section describes the hardware and software requirements of the LMT, and thecommunication capability requirements.

Hardware Requirements

Table 2-1 lists the hardware requirements of the computer on which the LMT application resides.

Table 2-1 Hardware Requirements

Item Quantity RecommendedConfiguration

Minimum Configuration

CPU 1 2.8 GHz or better 866 MHz

RAM 1 512 MB 256 MB



5

Item Quantity RecommendedConfiguration

Minimum Configuration

Harddrive

1 80 GB 10 GB

Displayadapterresolution

- 1024 x 768 pixels or better 800 x600 pixels

CD drive 1 - -

Networkadapter

1 10 Mbit/s or 100 Mbit/s 10 Mbit/s or 100 Mbit/s

Others 5 x 1 pixels Keyboard, mouse, modem,audio adapter, sound box

-

Software RequirementsTable 2-2 lists the software requirements of the computer on which the LMT application resides.

Table 2-2 Software requirements

Item Recommended Configuration

Operating system Microsoft Windows XP Professional

Default language of theoperating system

English (United States)

Web browser Microsoft Internet Explorer 5.5 or later

NOTE

To ensure stable operation, install the LMT application on a computer with the recommendedconfigurations.

Communication Capability RequirementsInstall the LMT application on a computer that supports the TCP/IP protocols.



6

3 Components of the NodeB LMT

About This Chapter

The NodeB LMT communicates with the NodeB through a Local Area Network (LAN) or WideArea Network (WAN). You can operate and maintain a NodeB on the LMT. The LMT consistsof the following parts: Local Maintenance Terminal, Trace Viewer, and Monitor Viewer.

3.1 NodeB Local Maintenance TerminalThe LMT is a subsystem of the LMT application. On the graphical user interface (GUI) of theLMT, you can perform tasks such as fault management, file management, equipmentmanagement, message tracing, and real-time monitoring. In addition, the LMT supports manyMML commands for overall configuration and maintenance of the system. To use the LMT foronline OM, ensure that the LMT communicates with the NodeB properly.

3.2 Trace ViewerThe Trace Viewer works in offline mode, and permits you to browse saved messages in .tmfformat.

3.3 Monitor ViewerThe Monitor Viewer works in offline mode, and permits you to browse saved CPU occupancyfiles in .mrf format.

3.4 TrafficReviewThe TrafficReViewer works in offline mode, and permits you to browse saved messages in .mmfformat.

NodeBLMT User Guide 3 Components of the NodeB LMT


7

3.1 NodeB Local Maintenance TerminalThe LMT is a subsystem of the LMT application. On the graphical user interface (GUI) of theLMT, you can perform tasks such as fault management, file management, equipmentmanagement, message tracing, and real-time monitoring. In addition, the LMT supports manyMML commands for overall configuration and maintenance of the system. To use the LMT foronline OM, ensure that the LMT communicates with the NodeB properly.

Interface

Figure 3-1 shows the window of the Local Maintenance Terminal.

Figure 3-1 Local Maintenance Terminal window

Table 3-1 describes the fields in the Local Maintenance Terminal window.

Table 3-1 Fields in the Local Maintenance Terminal window

No. Field Description

1 Menu bar Provides access to most operations of the system.

2 Toolbar Provides shortcut icons for easy operation.



8


3 Navigation pane Lists various objects in a tree structure. It includes theMaintenance, MML Command and Device Panel tabs.

4 Object pane Lists details about each operation.If you select MML Command in the navigation pane, theMML client is displayed in this pane.

5 Output pane Records details about current operation and informationreturned from the system. It includes the Common andMaintenance tabs.

6 Status bar Displays the user name, connection status, and IP address.

Online HelpThe LMT has two types of online help:

l LMT help systeml MML help

Table 3-2 describes the content of the two types of online help and their startup methods.

Table 3-2 Description of the LMT online help

Name Content Startup Method

LocalMaintenanceTerminalhelp system

Provides the followinginformation:l Meanings of the

fields in the dialogbox

l Guidelines foroperations on theLMT

l Details about MMLcommands

l Details about analarm

l Technical terms andabbreviations

l Press F1 or select Help > Help Topics or click

on the toolbar to display the LocalMaintenance Terminal help system.

l In a dialog box, press F1 to display the helpinformation.



9

Name Content Startup Method

MML help Provides the followinginformation about eachMML command:l Functionl Notel Parameterl Examplel Output description

(applicable to thecommands forquerying purposesonly)

l Relevant tasks

Type the MML command in the MML client. Press

Enter or click to display the HelpInformation window.

3.2 Trace ViewerThe Trace Viewer works in offline mode, and permits you to browse saved messages in .tmfformat.

InterfaceSelect Start > All Programs > HUAWEI Local Maintenance Terminal > Trace Viewer. TheOpen dialog box is displayed. Select the trace report from the directory. Click Open. The TraceViewer window is displayed, as shown in Figure 3-2.



10

Figure 3-2 Trace Viewer window

Online Help

Table 3-3 describes the content of the Trace Viewer online help and its startup method.

Table 3-3 Description of the Trace Viewer online help

Content Startup Method

Introduction to the TraceViewer and description onhow to use it

In the Trace Viewer window, press F1, choose Help > Help

Topics, or click on the toolbar to display the helpinformation.

3.3 Monitor ViewerThe Monitor Viewer works in offline mode, and permits you to browse saved CPU occupancyfiles in .mrf format.

Interface

Choose Start > All Programs > HUAWEI Local Maintenance Terminal > MonitorViewer. The Open dialog box is displayed. Select the monitoring files from the directory. ClickOpen, The Monitor Viewer window is displayed, and as shown in Figure 3-3.



11

Figure 3-3 Monitor Viewer window

Online HelpTable 3-4 describes the content of the online help and its startup method.

Table 3-4 Description of the Monitor Viewer online help


Introduction to theMonitor Viewer anddescription on how to useit

In the Monitor Viewer window, press F1, choose Help > Help

Topics or click on the toolbar to display the helpinformation.

3.4 TrafficReviewThe TrafficReViewer works in offline mode, and permits you to browse saved messages in .mmfformat.

InterfaceSelect Start > All Programs > HUAWEI Local Maintenance Terminal > FreqChartFreqChartReview Tool. The Open dialog box is displayed. Select the frequency spectrum

report from the directory. Click Open. The TrafficReviewr window is displayed,Click inthe displayed window and the frequency spectrum information is displayed.,as shown in Figure3-4.



12

Figure 3-4 TrafficReview window

Online HelpTable 3-5 describes the content of the TrafficReview online help and its startup method.

Table 3-5 Description of the Trace Viewer online help


Introduction to theTrafficReview anddescription on how to use it

In the TrafficReview window, press F1, choose Help > Help

Topics, or click on the toolbar to display the helpinformation.



13

4 Installing and Verifying the NodeB LMTApplication

About This Chapter

This chapter describes how to install and verify the NodeB LMT application.

4.1 Installing the NodeB LMT ApplicationThis section describes how to install the LMT application on the LMT PC.

4.2 Verifying the Installed NodeB LMT ApplicationThis section describes how to verify the installed LMT application by starting the LMT andchecking the installation path.

NodeBLMT User Guide 4 Installing and Verifying the NodeB LMT Application


14

4.1 Installing the NodeB LMT ApplicationThis section describes how to install the LMT application on the LMT PC.

Prerequisitel The setup disk and instruction provided by Huawei are available.

l A valid CD-KEY to the LMT application is available.

l You have logged into the operating system as an administrator.

Procedure

Step 1 Insert the setup disk into the CD-ROM drive.The setup application is automatically launched. If the system fails to launch the setup, open thedirectory of the setup disk and double-click on setup.exe.

Step 2 Select the language to be used in the installation in the dialog box.

Step 3 Click OK. A dialog box displays the introduction of the installation.

Step 4 Read the introduction, and then click Next. A dialog box displays the copyright notice.

Step 5 Read the agreement and select I accept these terms.

NOTE

The Next button is enabled only after you select I accept these terms.

Step 6 Click Next. The Installation Directory dialog box is displayed.

Step 7 Click Next to use the default installation path. A dialog box displays and requires you to selectthe software components.

You can also customize the installation path.

NOTE

l The default installation path is D:\HW LMT.

l If LMT software of other products is already installed, the installation path cannot be changed.

l If the installation path needs to be changed during this installation, LMT software of other productsmust be uninstalled before beginning this installation.

Step 8 Select the required software components (preferably all), and then click Next. The Please InputCD KEY window is displayed.

Step 9 Enter a valid CD-KEY, and then click Next. The Confirm installation dialog box is displayed.

NOTE

The CD-KEY is supplied together with the installation disc. You can find the key in a SN.TXT file in thesoftware package.

The Next button is available only after you enter a correct CD-KEY.

Step 10 Confirm that all the setup information is correct, and then click Next. A progress indicator isdisplayed, showing the installation progress.



15

Step 11 After all the files are copied, the Initializing Components dialog box is displayed to show theprogress.

Step 12 After the LMT application is installed, the Installation completed dialog box is displayed.

Step 13 Click Finish. The LMT application installation is complete.

NOTE

l To restore the installation files in case of damage, it is recommended that you back up the installationdirectory to a path different from the installation path.

l After the LMT application is installed, the system automatically starts the LMT Service Manager.

l After the LMT application is installed, a dialog box is displayed. Click Yes to start the LMT now, orclick No to start it later.

----End

Follow-up ProcedureAfter installation, you can start the following applications through the HUAWEI LocalMaintenance Terminal program group:

l LMT Service Manager

l Local Maintenance Terminal

l Trace Viewer

l Monitor Viewer

l Uninstall Local Maintenance Terminal

l TrafficReview

4.2 Verifying the Installed NodeB LMT ApplicationThis section describes how to verify the installed LMT application by starting the LMT andchecking the installation path.

ContextTable 4-1 describes the directories in the LMT application installation directory.

Table 4-1 LMT application installation directories

Directory Description

\adaptor\clientadaptor\NodeB\LMTsoftware version\output\realmonitor

Location for saving result files of the real-timeperformance monitor tasks

\client\output\monitor Location for saving the result file of CPU/DSPUsage monitoring task

\client\output\main\NodeB\LMTsoftware version\trace

Location for saving the result file of a tracing task

\adaptor\clientadaptor\NodeB\LMTsoftware version\help

Location for saving the online help of LMT software



16

Directory Description

\uninstall Location for saving the information on uninstalledcomponents

NOTE

l These are the default saving paths.l Some folders are created only when the related task results are saved.

Procedurel To start the LMT of the NodeB, perform the following steps:

1. Check whether is displayed in the status area. If the icon is not displayed, selectStart > All Programs > HUAWEI Local Maintenance Terminal > LMT ServiceManager. The LMT Service Manager is started.

2. Select Start > All Programs > HUAWEI Local Maintenance Terminal > LocalMaintenance Terminal to start the Local Maintenance Terminal. If the UserLogin dialog box is displayed, it indicates that the LMT application is installedsuccessfully.

NOTE

For details about how to log in to the LMT, refer to 5.1.6 Locally Logging In to the NodeBon the NodeB LMT.

l To confirm the installation path, perform the following step:

Open the installation path through Explorer and review the directory structure, as shownin Figure 4-1.

Figure 4-1 Directory structure of the LMT application



17

----End



18

5 Getting Started with the NodeB LMT

About This Chapter

This chapter describes how to get started with the NodeB LMT. Before using the LMT, youmust connect, log on, and configure the LMT.

5.1 Running the NodeB LMTThis section describes how to set the NodeB IP address, connect it to the NodeB, and then logon to the NodeB LMT. When the LMT is running, ensure the hard drive has at least 1 GB offree space.

5.2 Setting the Properties of the NodeB LMTThis section describes how to set the properties of the NodeB LMT. Configuration consists ofthe following tasks: setting the office, setting the time-out duration of MML commands, settingthe system lock time, and running batch MML commands.

5.3 Changing the Password for Login to the NodeB LMTThis section describes how to change the password for logging in to the NodeB. You can log into the NodeB only if the correct password is entered.

5.4 Setting the Information About an Office on the NodeB LMTThis section describes how to set the IP address of the M2000 server or the NodeB.

5.5 Locking the NodeB LMTThis section describes how to lock the NodeB LMT to ensure secure operation. Lock the systemto avoid illegal operations when it is not in use.

5.6 Unlocking the NodeB LMTThis section describes how to unlock the LMT. Once the NodeB LMT is locked, you must logon to it again by entering the correct password.

5.7 Exiting from the NodeB LMTThis section describes how to exit from the NodeB LMT. If you exit the LMT, you willdisconnect the LMT from the NodeB and close the LMT. If you log on to the NodeB throughthe M2000 server, you will also disconnect the LMT from the M2000.

NodeBLMT User Guide 5 Getting Started with the NodeB LMT


19

5.1 Running the NodeB LMTThis section describes how to set the NodeB IP address, connect it to the NodeB, and then logon to the NodeB LMT. When the LMT is running, ensure the hard drive has at least 1 GB offree space.

5.1.1 Setting the IP Address of the NodeB LMT PCThis section describes how to set the IP address of the LMT PC. You must set a correct IP addressfor the LMT PC before logging in to the NodeB.

PrerequisiteThe TCP/IP protocol is configured on the LMT PC.

ContextBefore you perform the maintenance, set the IP address for the LMT PC as follows:l In local maintenance, IP addresses of the LMT PC and the NodeB local maintenance

channel are in the same network segment.l In remote maintenance, IP 1 and IP 2 are in the same network segment, as shown in Figure

5-1. IP 1 stands for the IP address of the LMT PC. IP 2 stands for the IP address of theexternal network composed of the entity directly connected to the LMT PC and the LANwhere the LMT PC is located. For example, the IP address of the RNC BAM externalnetwork.

Figure 5-1 IP addresses in remote maintenance mode

CAUTIONEnsure that the IP address of the LMT PC does not conflict with the IP address of anothercomputer within the same local area network.

ProcedureStep 1 For example, to set the IP address of the LMT PC with the Windows XP operating system,

perform the following steps: Choose Start > Control Panel.



20

If... Then...

The control panel is displayed in categoryview,

Go to Step 2.

The control panel is displayed in classicalview,

Go to Step 3.

Step 2 Click Network and Internet Connections.

Step 3 Double-click Network Connections. The Network Connections window is displayed. Right-click the icon of Local Area Connection.

Step 4 Choose Properties from the shortcut menu. The Local Area Connection Properties dialogbox is displayed.

Step 5 Select Internet Protocol (TCP/IP).

Step 6 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed.

Step 7 Select Use the following IP address.

Step 8 Enter the correct IP address, subnet mask, and default gateway.

If... Then...

The LMT PC is used in local maintenancemode,

Set the IP address, subnet mask, and defaultgateway, as shown in Table 5-1.

The LMT PC is used in remote maintenancemode,

Set the IP address, subnet mask, and defaultgateway, as shown in Table 5-2.

Table 5-1 IP parameters of the LMT PC for commissioning on the NodeB local side

Parameter Description

IP Address The IP address of the LMT PC is in the same network segment as thatof the NodeB local maintenance channel.In local maintenance mode, the default NodeB IP address is 17.21.2.15.

Subnet mask The LMT PC has the same subnet mask as that of the NodeB localmaintenance channel.

Default gateway None

Table 5-2 IP parameters of the LMT PC for commissioning on the NodeB remote side


IP Address The IP address of the LMT PC is in the same network segment as theexternal IP address of RNC BAM.



21


Subnet mask The subnet mask of the LMT PC is the same as the external subnet maskof RNC BAM.

Default gateway The IP address of the BAM external network is the gateway from theLMT to the NodeB.

NOTE

In the same network, the IP address subnet mask are the same, and the subnet address (the result of the IPaddress and the subnet mask logical merge.) are the same as well.

Step 9 Click OK to complete the settings.

----End

5.1.2 Locally Connecting the NodeB LMT PC to the NodeBThis section describes how to connect the LMT PC to the BBU3900 in local maintenance modefor operating and maintaining the NodeB.

PrerequisiteThe IP address of the LMT PC and that of the NodeB local maintenance channel are in the samenetwork segment.

Procedure

Step 1 To connect the LMT PC to the NodeB, perform the following steps:

Connect the Ethernet port of the LMT PC to the maintenance-oriented Ethernet port of theBBU3900 with a crossover cable, as shown in Figure 5-2.



22

Figure 5-2 Connecting LMT PC and BBU3900 in local maintenance mode

(1) BBU3900 (2) Crossover cable (3) LMT PC

Step 2 On the LMT PC, choose Start > Run, and then run the cmd command in the Run dialog box.The command window is displayed.

Step 3 Run ping target_name -t and verify the connection between the LMT PC and the NodeB.Where, target_name represents the IP address of the NodeB local maintenance channel.

----End

5.1.3 Remotely Connecting the NodeB LMT PC to the NodeB(Through RNC BAM)

This section describes how to connect the NodeB LMT PC to RAN OM intranet (that is, theRNC BAM external network) in remote maintenance mode.

PrerequisiteThe IP address of the remote NodeB LMT PC is set and it is in the same network segment asthe external IP address of the RNC BAM.

ProcedureStep 1 Use an Ethernet cable to connect the Ethernet port of the LMT PC to one Ethernet port of the

RAN OM intranet (that is, the RNC BAM external network).


Step 3 Run ping target_name -t and verify the connection between the LMT PC and the communicationgateway. Here, target_name represents the external IP address of the RNC BAM.

----End



23

5.1.4 Remotely Connecting the NodeB LMT PC to the NodeB(Through M2000)

This section describes how to connect the NodeB LMT PC to RAN on the M2000 server inremote maintenance mode.

PrerequisiteThe IP address of the remote NodeB LMT PC is set and it is in the same network segment asthe M2000 server.

Procedure

Step 1 Use an Ethernet cable to connect the Ethernet port of the LMT PC, Ethernet port of the M2000server, and one Ethernet port of the RAN OM intranet (that is, the RNC BAM external network)to the LAN switch.


Step 3 Run ping target_name -t and verify the connection between the LMT PC and the communicationgateway. Where, target_name represents the IP address of the M2000 server.

----End

5.1.5 Setting the Route from the NodeB LMT PC to the NodeBThis section describes how to set the route from the LMT PC to the NodeB in remote maintenancemode. The route from the LMT PC to the NodeB must be set. Otherwise, you cannot log in tothe NodeB on the LMT PC.

Procedure

Step 1 On the LMT PC, choose Start > Run, and then run the cmd command in the dialog box. Thecommand window is displayed.

Step 2 Run ROUTE ADD Networkaddress MASK netmask gatewayaddress in the commandwindow to add a route from the computer to the gateway.

Set Networkaddress, netmask, and gatewayaddress by referring to Table 5-3.

Table 5-3 Description of route parameters


Networkaddress IP address of the NodeB in remote maintenance mode

netmask Subnet mask that is the same as the external subnet mask of RNCBAM

gatewayaddress External IP address of the BAM



24

NOTE

l Different NodeBs correspond to different IP addresses.

l The IP address in the same network segment corresponds to the same subnet mask and subnet address(subnet mask AND IP address).

Step 3 Run ping target_name -t and verify the connection between the LMT PC and the NodeB. Here,target_name represents the IP address of the NodeB OMIP.

----End

5.1.6 Locally Logging In to the NodeB on the NodeB LMTThis section describes how to locally log on to the NodeB on the LMT.

PrerequisiteThe LMT PC is properly connected to the NodeB.

Procedure

Step 1 Select Start > All Programs > Huawei Local Maintenance Terminal > Local MaintenanceTerminal. The User Login dialog box displays.

NOTE

If the LMT is started already, select System > Log Out or click .

Table 5-4 describes the fields in the User Login dialog box.

Table 5-4 Fields in the User Login dialog box

Field Description

User Name Enter the user name of the NodeB. The default user name is admin.The user name is mandatory and case-sensitive.

Password Enter the password of the NodeB. The default password is NodeB. Thepassword consists of 6 to 16 alphanumeric and case-sensitivecharacters.

Office Select the name and IP address of the NodeB that is connected to the

LMT. Click to edit the office information. For details, refer to 5.4Setting the Information About an Office on the NodeB LMT.When you log in to the NodeB locally, the IP address of the office mustbe the same as that of the NodeB local maintenance channel.

Proxy server Leave this field blank. Ensure that you do not select the check box.

Step 2 In the Office area, set IP Address and Office.

Step 3 Enter the user name and password in the dialog box.

Step 4 Click Login to log in to the NodeB.



25

Step 5 If a Switching the language dialog box is displayed, it indicates that the NodeB language doesnot match the LMT language. In this case, change the NodeB language to log on to theNodeB.

CAUTIONThe NodeB will be reset after you switch the NodeB language.

Step 6 Click Yes to switch the NodeB language.

NOTE

If you click No, a dialog box is displayed, prompting The language of NE differs from LMT. You clickOK to log in to the NodeB. But this step leads to the following results:

l The language of the NodeB software message that is reported to the LMT does not match the LMTlanguage.

l When software management operations are performed, message analysis fails.

Step 7 If the Unmatched Version window displays, choose appropriate option according to the needs.

l If you need to download a matched version, and the NodeB has been backed up, selectDownload a matched version. The Version update will reset the NodeB. For moreinformation, see 11 Managing the NodeB Software.

l If you do not need to download a matched version, select Forcibly login using the unmatchedversion. Use Forcible login with caution as it may result in system problems. If you do notneed to download a matched version, select Forcibly login by using the unmatchedversion. Use Forcible login with caution as it may result in system problems.

----End

5.1.7 Remotely Logging In to the NodeB LMT (Through RNC BAM)This section describes how to remotely log on to the NodeB through the RNC BAM.

Prerequisitel The connections between the LMT PC, the RNC BAM, and the NodeB are normal.

l The route from the NodeB LMT PC to the NodeB is set.

Procedure

Step 1 Select Start > All Programs > Huawei Local Maintenance Terminal > Local MaintenanceTerminal. The User Login dialog box displays.

NOTE

If the LMT is started already, select System > Log Out or click .

Table 5-5 describes the fields in the User Login dialog box.



26


Field Description

User Name Enter the user name of the NodeB. The default user name is admin.The user name is mandatory and case-sensitive.

Password Enter the password of the NodeB. The default password is NodeB. Thepassword consists of 6 to 16 alphanumeric and case-sensitivecharacters.

Office Select the name and IP address of the NodeB that is connected to the

LMT. Click to edit the office information. For details, refer to 5.4Setting the Information About an Office on the NodeB LMT.When you log in to the NodeB locally, the IP address of the office mustbe the same as that of the NodeB local maintenance channel.

Proxy server Leave this field blank. Ensure that you do not select the check box.

Step 2 In the Office area, set IP Address and Office.

Step 3 Enter the user name and password in the dialog box.

Step 4 Click Login to log in to the NodeB.

Step 5 If the Unmatched Version window displays, choose appropriate option according to the needs.

l Download a matched version.

l If there is no need for download a matched version, select Forcibly login by using theunmatched version. Forcible login may lead to unknown problems.

----End

5.1.8 Remotely Logging In to the NodeB LMT (Through M2000)This section describes how to log on to the NodeB on the M2000. By performing this task, youcan maintain the NodeB through the M2000 server.

Prerequisitel The active M2000 user has the administration right to the NodeB and a corresponding NE

exists.

l LMT computer, M2000, and the NodeB are connected properly.

ContextThe LMT log in to the NodeB through M2000 via the following two methods:

l Method 1: Set the M2000 as the default gateway, set the route from the LMT PC to theNodeB, and log in to the NodeB.

l Method 2: Log in to the M2000 from the LMT, and then select the NodeB equipment toperform maintenance.



27


Field Description

User Name Enter the user name of the M2000. The user name is mandatory andcase-sensitive.

Password Enter the password of the M2000. The password is case-sensitive, andit should have 6 to 16 digits which must be a combination of alphabetsand numbers.

OfficeClick to edit the office information. For details, refer to 5.4 Settingthe Information About an Office on the NodeB LMT.l If using method 1, select the name and IP address of the NodeB that

connected to the LMT. The IP address of the office is the IP addressof the NodeB remote maintenance channel.

l If using method 2, select the name and IP address of the M2000server. The IP address of the office is the IP address of the M2000server.

Proxy server l In method 1, the M2000 must be configured as the proxy server.l In method 2, this does not need to be set.

Procedurel Method 1:

1. Select Start > All Programs > HUAWEI Local Maintenance Terminal > LocalMaintenance Terminal, and the User Login dialog box displays.For the details in the User Login dialog box, see Table 5-6.

2. Enter the user name and password of the M2000 in the dialog box, and set Office tothe name and IP address of the NodeB that connected to the LMT.

3. Set the proxy server to the M2000.

4. Click Login to log in to the NodeB.

l Method 2:

1. Select Start > All Programs > HUAWEI Local Maintenance Terminal > LocalMaintenance Terminal, and the User Login dialog box displays.For the details in the User Login dialog box, see Table 5-6.

2. Enter the user name and password of the M2000 in the dialog box, and set Office tothe name and IP address of the M2000.

3. Click Login to log in to the M2000.The NodeB List dialog box displays the NodeB equipment list and the correspondingIP address under the M2000.

4. Select the NodeB equipment that need to be maintained in the dialog box, and clickOK to log in to the NodeB.

5. If the Unmatched Version window displays, choose appropriate option according tothe needs.



28

– If there is a need to download a matched version, select Download a matchedversion.

– If there is no need to download a matched version, select Forcibly login by usingthe unmatched version. Forcible login may lead to unknown problems.

----End

5.2 Setting the Properties of the NodeB LMTThis section describes how to set the properties of the NodeB LMT. Configuration consists ofthe following tasks: setting the office, setting the time-out duration of MML commands, settingthe system lock time, and running batch MML commands.

Procedurel Select System > System Setting. In the displayed dialog box, click the Terminal tab,

enable automatic locking the system, and then set the system lock time. If no operation isperformed in the set duration, the terminal will be automatically locked.

l Select System > Office Management to set, modify, or delete office information. Fordetails, refer to 5.4 Setting the Information About an Office on the NodeB LMT.

l Select System > Output Window Setting to set output window setting and save the settingsto a file. Table 5-7 lists parameter settings.

Table 5-7 Parameter settings in the Output Window Setting dialog box

Field Description

PropertiesSetting

Maximum Output Lines The maximum number of lines that can bedisplayed.

Auto scroll to the newmessage

This enables you to see the new message at anytime.

OutputSetting

Export To File The default path is installation directory\client\output\NodeB\LMT version\ilmtframe\Maintenance_YY-MM-DD-HH-MM-SS.txt.

Maximum Amount The total number of commands that can bedelivered to and from the RNC.

Auto Save If this check box is selected, commands andmessages are automatically saved to thespecified files.

Timed Save If this check box is selected, commands andmessages are exported within the scheduledperiod of time.

Start time The start of the scheduled period of time.

End time The end of the scheduled period of time.



29

l Select System > Command Timeout Setting to perform MML command time-out setting.Value range: 20 to 600. Unit: s. The LMT displays the Timeout dialog box if no result isreturned after the time-out duration expires.

l Select System > Batch Commands to run batch MML commands. For details, refer to 6.3Running NodeB Batch MML Commands.

l Select View > Navigation Tree to display or hide the navigation tree.

l Select View > Output Window to display or hide the output window.

l Select View > Command Window to display or hide the command window.

l Select View > System Toolbar to display or hide the toolbar.

----End

5.3 Changing the Password for Login to the NodeB LMTThis section describes how to change the password for logging in to the NodeB. You can log into the NodeB only if the correct password is entered.

Procedure

Step 1 In the Local Maintenance Terminal window, select Authority > Change Password. TheChange Password dialog box is displayed.

Step 2 Enter the old and new passwords in the dialog box.

Step 3 Click OK.

----End

5.4 Setting the Information About an Office on the NodeBLMT

This section describes how to set the IP address of the M2000 server or the NodeB.

ContextTypically, one name is used to identify different IP addresses. A NodeB LMT may have differentoffice information to connect to a specified M2000 server or NodeB.

Procedure

Step 1 Select System > Office Management, and the Office Management dialog box displays.

Table 5-8 Fields in the Office Management dialog box

Field Description

Office The name of NEs to which the NodeB LMT connects. It is a string of 60characters, and can neither contain the symbols: * : < > | ? \ / " &.



30

Field Description

IP Address The IP address of the NEs. It is unique to the Office.In local maintenance mode, the default IP address of the NodeB is17.21.2.15.

NE Type The type of the NE under maintenance: NodeB.

NE Port The port number of the NEs to which the NodeB LMT connects. By default,the port number of the normal connection is 6000, and the port number ofthe SSL connection is 6000.

Connect Type Two modes are possible for the connection between the NodeB LMT andNEs: Normal Connection and SSL Connection.

Proxy Server Used to connect the NodeB LMT to the NEs. The IP address of the proxyserver can be specified.

Start Local Port The starting local port number when the link is established.

End Local Port The ending local port number of the office when the link is established.

Add You can add other M2000 server or NodeB office information by clickingAdd to display the Add dialog box.

Modify You can modify the office information by selecting an office and clickingModify.

Delete You can delete an office by selecting that office and clicking Delete.

Import You can import the office information by clicking Import to display theOpen dialog box. Then select the office file that is backed up during theexport. The format of the imported office file is *.zip.

Export You can back up the office information by clicking Export. The Savedialog box is displayed. Enter a file name, and then specify a path and a filetype.

Find Enter the office information in the Find Office text box, and click Find.

Step 2 Click Add, and the Add dialog box is displayed. Set the parameters.

NOTEIf Connect Type is set to SSL Connection, the SSL Options panel is displayed. Specify the protocol version,algorithm intensity, and authentication mode. Click to hide the SSL Options panel. If you want to have thispanel displayed again, click .

Step 3 Click OK. The system returns to Office Management dialog box.

Step 4 Click Close. The settings are complete.

----End



31

5.5 Locking the NodeB LMTThis section describes how to lock the NodeB LMT to ensure secure operation. Lock the systemto avoid illegal operations when it is not in use.

ContextThe NodeB LMT has two lock modes:

l Lock immediately

l Lock by schedule

NOTE

The lock function locks only the interface of the NodeB LMT without disrupting any operations on theLMT.

Procedurel Lock immediately

1. Select System > Lock, use the shortcut keys Ctrl+Alt+M, or click . The interfaceis locked.

l Lock by schedule

1. Select System > System Setting. A System Setting dialog box is displayed.

2. Select Terminal, and set the lock time in the System Setting dialog box.

3. Select Automatically locked and set the time for the automatic locking.

4. Click OK to complete the settings.

----End

5.6 Unlocking the NodeB LMTThis section describes how to unlock the LMT. Once the NodeB LMT is locked, you must logon to it again by entering the correct password.

ContextThe NodeB LMT is locked and the Terminal Locked dialog box is displayed.

Procedure

Step 1 Press Ctrl+Alt+U. The Unlock Terminal dialog box is displayed.

Step 2 Enter the password, and then click OK to unlock the LMT.

----End



32

5.7 Exiting from the NodeB LMTThis section describes how to exit from the NodeB LMT. If you exit the LMT, you willdisconnect the LMT from the NodeB and close the LMT. If you log on to the NodeB throughthe M2000 server, you will also disconnect the LMT from the M2000.

Procedure

Step 1 Select System > Exit, or click . A Confirmation dialog box is displayed.

Step 2 Click OK.

----End



33

6 Running NodeB MML Commands

About This Chapter

This chapter describes how to run Man Machine Language (MML) commands. You may run asingle MML command or batch commands.

6.2 Running a Single NodeB MML CommandThis section describes how to run a single NodeB MML command.

6.3 Running NodeB Batch MML CommandsThis section describes how to run NodeB batch MML commands. Running batch MMLcommands involves adding a series of commands into a batch file, and then running the file toperform a function or an operation.

NodeBLMT User Guide 6 Running NodeB MML Commands


34

6.1 Introduction to NodeB MML CommandsThis section describes the functions, formats, interfaces, and types of NodeB MML commands.

FunctionsYou can operate and maintain the entire NodeB by using the MML commands. The MMLcommands enable you to perform the following operations:

l System Managementl Equipment Maintenancel Iub interface Managementl Local cell Managementl Alarm Management

FormatAll the MML commands are in the format of "Command Word: Parameter Name=Value;".

The command word is mandatory, whereas the parameter name and value are not.

l An example of an MML command with a command word and parameters: SETALMSHLD: AID=10015, SHLDFLG=UNSHIELDED;

l An example of an MML command with only a command word: LST VER:;

InterfaceIn the Local Maintenance Terminal window, select View > Command Window, as shownin Figure 6-1.



35

Figure 6-1 MML client dialog box

Types

The MML command format is Action + Object. For details, refer to Table 6-1.

Table 6-1 Types of MML commands

Action Meaning

ACT Activate

ADD Add

BLK Block

DLD Download

DSP Display dynamic information

LST List static data

MOD Modify

RMV Remove

RST Reset



36

Action Meaning

SET Set

STP Stop

STR Start

UBL Unblock

ULD Upload

SCN Scan

CLB Calibrate

6.2 Running a Single NodeB MML CommandThis section describes how to run a single NodeB MML command.

Procedurel Entering an MML command in the Command Input box:

1. Enter an MML command in the Command Input box.

2. Press ENTER or click . The parameter show area displays the parameters of thiscommand.

3. Enter parameters in the parameter show area.

4. Press F9 or click to run this command. The common maintenance pane displaysthe execution result.

l Selecting a command in the History command box:1. Select a command in the History command box. Press F8 for the next command and

F7 for the previous command.The parameter show area displays parameters of this command.

2. Modify the values of parameters in the parameter show area.

3. Press F9 or click to run this command.The common maintenance pane displays the execution result.

l Copying an MML command script into the Command Input area:1. Copy an MML command script with complete parameters into the Command

Input box.

2. Press F9 or click to run this command.The common maintenance pane displays the execution result.

l Click the MML Command navigation tree in the navigation pane:1. Double-click on an MML Command from navigation tree.2. Enter parameter values in the parameter show area.

3. Press F9 or click to run this command.



37

The common maintenance pane displays the execution result.

----End

6.3 Running NodeB Batch MML CommandsThis section describes how to run NodeB batch MML commands. Running batch MMLcommands involves adding a series of commands into a batch file, and then running the file toperform a function or an operation.

Prerequisite

Batch MML command files are created.

Context

You can run batch MML commands in either of the following ways:

l Run batch MML commands by schedulel Run batch MML commands immediately

The batch file (also referred to as the data script file) is a file in .txt format. It stores a group ofcommands that can perform a common function or a specific task. Batch files permit you to runseveral commands at once, rather than entering the commands one by one.

Batch MML command files can be created in any of the following three ways:

l Create a file in .txt format and write the commands into the file. Ensure to write onecommand on each line.

l Copy the information in the History Command box in the output pane and save it in ablank file in .txt format.

l Select System > Save Input Commands to save the used commands.

Procedurel To run batch MML commands immediately, perform the following steps:

1. Select System > Batch Commands, or press Ctrl+E. A MML Batch Processingwindow is displayed. Click the Immediate Batch Commands tab, as shown in Figure6-2.

Figure 6-2 Immediate Batch Command tab page



38

2. Click New in Immediate Batch Command, enter batch command in Input Box, orclick Open to select a pre-edited batch command file.

3. Set the parameters.

4. Click Go.

l To run batch MML commands by scheduled, perform the following steps:

1. Select System > Batch Commands, or press Ctrl+E. A MML Batch Processingwindow is displayed. Click the Timing Batch Command tab, as shown in Figure6-3.

Figure 6-3 Timing Batch Command tab page

2. Click the Add, the Add Batch Task dialog box is displayed, as shown in Figure6-4.

Figure 6-4 Add Batch Task dialog box



39

3. Click beside Batch File, and select the batch file.

4. Click beside Execute Time to set executing time.5. Click OK.

CAUTIONEnsure that the MML Batch window is open. Otherwise, the timed task is deleted.

----End



40

7 Managing NodeB Alarms

About This Chapter

This chapter describes how to manage NodeB alarms. You can set properties for the alarmmanagement system, query alarms and resolve problems associated with them.

7.1 Concepts Related to NodeB Alarm ManagementUsers need to learn about NodeB alarms before managing them. This section describes conceptsrelated to NodeB alarms, including alarm types, alarm logs, alarm severity, and alarmclassification based on network management.

7.2 Setting the Properties of the NodeB Alarm Management SystemThis section describes how to set the properties of the NodeB management system including theproperties of alarm query window, alarm prompt, and alarm real-time print.

7.3 Handling NodeB AlarmsThis section describes how to manage NodeB alarms. Instructions are provided to browse alarmlists, query alarm logs, manually recover alarms, save alarm information, manually print alarminformation, query alarm handling suggestions, shield alarms, clear alarms, and refresh the alarmwindow.

NodeBLMT User Guide 7 Managing NodeB Alarms


41

7.1 Concepts Related to NodeB Alarm ManagementUsers need to learn about NodeB alarms before managing them. This section describes conceptsrelated to NodeB alarms, including alarm types, alarm logs, alarm severity, and alarmclassification based on network management.

7.1.1 Alarm TypesThis section describes the alarm types including fault alarms and event alarms.

Table 7-1 describes the alarm types.

Table 7-1 Fault alarms and event alarms

Alarm Types Description

Fault alarms A fault alarm is caused by a hardware malfunction or an anomaly of amajor function. Fault alarms are of higher severity than event alarms.

Event alarms An event alarm indicates a predefined event that happens during therunning of the devices. The alarm represents an instantaneous status ofthe system which may not be a fault. Some event alarms are generatedrepeatedly and regularly. Event alarms are not categorized as active orrecovery alarms.

Fault alarms are categorized as either active or recovery alarms.l If the fault is cleared, the status of the alarm changes to Recovery, and the alarm is called

a recovery alarm.l If the fault persists, the status of the alarm remains Active, and the alarm is called 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 an active one. After thecongestion is cleared, the alarm becomes a recovery one.

NOTE

The record of a recovery alarm is stored in the BAM database and can be queried.

7.1.2 Alarm LogsThe alarm log contains detailed information about each alarm generated by the system.

You can query alarm logs on the NodeB. For more information, refer to 7.3.2 Querying AlarmLogs.

7.1.3 Alarm SeverityThis section describes the alarm severity. It indicates the seriousness of a fault. The alarm severityfor both fault alarms and event alarms can be categorized into four levels: critical, major, minor,and warning.



42

Table 7-2 describes the four severity levels.

Table 7-2 Alarm severity levels

AlarmSeverity

Definition Solution

Critical Reports faults that affect the services provided bythe system. These alarms need immediate attentioneven during off-work periods. Critical alarms canresult in service outage.

Resolve faultsimmediately to avoidservice outage.

Major Reports faults that affect the Quality of Service(QoS). These alarms need attention duringworking hours and may impact the performance ofequipment or resources.

Handle the faults asneeded. Note thesystem may fail toperform some majorfunctions.

Minor Reports faults that are not serious enough to affectthe QoS. Resolve alarms as needed.

Clear faults asneeded.

Warning Reports faults that potentially threaten the systemservices. Resolve alarms as needed.

Determine therunning state of thesystem.

7.1.4 Alarm Classification Based on Network ManagementNodeB alarms are classified by network management.

NodeB alarms can be categorized into the following types:

l Power system alarms: the alarms on the power system (for example, -48 V DC)l Environment system alarms: the alarms on equipment room environment such as the

temperature, the humidity, and the door controll Signaling system alarms: the alarms on channel associated signaling (SS1) and common

channel signaling (SS7)l Trunk system alarms: the alarms on trunk circuits and trunk boardsl Hardware system alarms: the alarms on board parts such as the clock and CPUl Software system alarms: the alarms on softwarel System running alarms: the alarms on system running processesl Communication system alarms: the alarms on communication systemsl QoS alarms: the alarms on QoS

7.2 Setting the Properties of the NodeB Alarm ManagementSystem

This section describes how to set the properties of the NodeB management system including theproperties of alarm query window, alarm prompt, and alarm real-time print.



43

7.2.1 Setting the Properties of the NodeB Alarm Query WindowThis section describes how to set the properties of the NodeB alarm query window. You cancustomize the alarm color of each alarm severity, set the playing duration of fault alarm sounds,and set the initial and maximum display numbers of alarm records.

Procedure

Step 1 Select Fault Management > Alarm Customization. The Alarm Customization dialog box isdisplayed.

Table 7-3 describes the fields in the Alarm Customization dialog box.

Table 7-3 Fields in the Alarm Customization dialog box

Field Description

Alarm Color Critical Fault Set a color for critical faults.

Major Fault Set a color for major faults.

Minor Fault Set a color for minor faults.

Warning Fault Set a color for warning faults.

Recovery Alarm Set a color for recovery faults.

Event Set a color for events.

Fault Alarm Sound Play by Time(s) Set the time length for playing the alarmsound. When the time runs out, thealarm sound automatically stops.

Circularly Play Play the alarm sound repeatedly insteadof playing for a period of time. Forexample, when a major alarm isreported, the corresponding alarmsound is repeatedly played.

Critical Set the sound duration for criticalalarms. By selecting the correspondingcheck box, the fault alarm sound isenabled at the critical severity level.

Major Set the sound duration for major alarms.By selecting the corresponding checkbox, the fault alarm sound is enabled atthe major severity level.

Minor Set the sound duration for minor alarms.By selecting the corresponding checkbox, the fault alarm sound is enabled atthe minor severity level.



44

Field Description

Warning Set the sound duration for warningalarms. By selecting the correspondingcheck box, the fault alarm sound isenabled at the warning severity level.

Initial Display Amount Alarm number displayed the first timethis dialog box is opened.

Max. Display Amount Maximum number of alarms displayedin the fault alarm and event alarmtables.

ToolTips l The values are Enable or Disable.This field is set to Enable by default.

l If this function is enabled, detailedalarm information is displayedwhen you point to an alarm recordin the Alarm Browse dialog boxand Query Alarm Log dialog box.

Step 2 Set the properties of the alarm query window as required.

NOTE

l If you click Default, all the settings are restored to the default state.

l To enable fault alarm sounds, an alarm severity must be selected and the Alarm Browse window isopen.

l If multiple alarm severities are selected, the alarm sound of higher severity alarms is given preference.

l If the Alarm Browse window is open and alarm sounds are repeatedly played, you can select Play byTime(s) and then set the play time. The setting takes effect for subsequent alarms.

l If an alarm sound is repeatedly played, the sound will only stop when all the alarms of that severity arecleared.

l The alarm sounds take effect only for fault alarms. The sounds are from the audio adapter instead ofthe alarm box.

Step 3 Click OK.

----End

7.2.2 Setting NodeB Alarm PromptThis section describes how to set NodeB alarm prompts.

Context

When there are alarms, the NodeB alarm service manager icon blinks.

Procedure

Step 1 Select Fault Management > Fault Alarm Prompt. An alarm service manager icon isdisplayed in the task area.



45

Step 2 Right-click the NodeB Alarm Service Manager to perform the operations listed in the followingtable.

Operation Description

Stop Current Prompt Select this to stop the Alarm Service Managericon blinking.

Fault Alarm Prompt If select this option, the NodeB Alarm ServiceManager icon blinks when there are alarms.

Browse Alarm Select this to display the reported alarm.

----End

7.2.3 Setting the Preferences for Printing Alarms in Real TimeThis section describes how to set the preferences for printing of alarms. Only real-time alarmsthat meet requirements are printed.

Prerequisite

The LMT PC is connected to a printer.

Procedure

Step 1 Select Fault Management > Alarm Realtime Print Set. The Alarm Realtime Print Set dialogbox is displayed, as shown in Figure 7-1.

Figure 7-1 Setting alarm real-time print



46

Step 2 Set the print requirements.

Step 3 Click OK.

----End

7.3 Handling NodeB AlarmsThis section describes how to manage NodeB alarms. Instructions are provided to browse alarmlists, query alarm logs, manually recover alarms, save alarm information, manually print alarminformation, query alarm handling suggestions, shield alarms, clear alarms, and refresh the alarmwindow.

7.3.1 Browsing AlarmsThis section describes how to browse the fault and event alarms that are sent to the LMT anddisplayed in the Browse Alarm window in real time. It is useful for reviewing the operatingstatus of the system.

Procedure

Step 1 Select Fault Management > Browse Alarm. A Browse Alarm window is displayed.

Step 2 To learn the details about an alarm, double-click it. The Alarm Detailed Information dialogbox is displayed.

Step 3 Click a corresponding button according to the need.

Click Previous or

Next to check the details of the previous or next alarm.

Step 4 Click Close to close the dialog box.

----End

7.3.2 Querying Alarm LogsThis section describes how to query alarm logs by specific search conditions. You can also obtaina history of running records of the equipment.

Procedurel GUI mode

1. Select Fault Management > Query Alarm Log, or click . A Query AlarmLog dialog box is displayed.

Set general conditions for alarm query in the General Option tab page. Table 7-4describes the fields in this page.



47

Table 7-4 Fields in the General Option tab page

Field Description

Alarm Type This enables you to specify the alarm types. Value range:Event, Fault Recovered, and Fault Unrecovered. Bydefault, all types are selected.

Alarm Severity This enables you to specify the alarm severity types toquery. Value range: Critical, Major, Minor, and Warning.By default, all types are selected.

Alarm Time This enables you to specify a time range to query alarms.Rules for time specifying:l If you specify a start time without a start date, the

system uses the seventh day before the current day asthe start date.

l If you specify an end time without an end date, thesystem uses the current date as the end date.

Return Amount This enables you to specify the number of records that aredisplayed.

In the Detailed Option tab page, set the following parameters for querying alarms:alarm serial number, alarm ID, and event type.

Table 7-5 describes the fields in the Detailed Option tab page.

Table 7-5 Fields in the Detailed Option tab page

Field Description

Event Type This enables you to specify event types. By default, all typesare selected.

Alarm ID This enables you to specify an alarm ID range.

Alarm Serial No. This enables you to specify a range of the alarm serialnumber.

Module ID Not supported on the NodeB.

In the Physical Option tab page, set the following parameters for querying alarms:subrack number, slot number, and board place.

Table 7-6 describes the fields in the Physical Option tab page.



48

Table 7-6 Fields in the Physical Option tab page

Field Description

Cabinet No. This enables you to specify a cabinet.

Subrack No. This enables you to specify a subrack.

Slot No. This enables you to specify a slot.

Board Place Not supported on the NodeB.

Board Type This enables you to specify a board type.

2. Set the search conditions as required.3. Click OK. The Query Alarm Log window is displayed.4. View the alarm logs in the window.5. Double-click an alarm record to obtain detailed information. The Alarm Detailed

Information dialog box is displayed.6. Close the window.

l MML mode

Run the command LST ALMLOG to query the alarm log.

----End

7.3.3 Manually Recovering an AlarmThis section describes how to manually set a cleared alarm.

ProcedureStep 1 In the Browse Alarm window or the Query Alarm Log window, select an alarm report.

Step 2 Right-click the alarm report.A shortcut menu is displayed.

Step 3 Select Manually Recover Alarm from the shortcut menu.The Confirm dialog box is displayed.

Step 4 Click Yes.The selected alarm is recovered and the color of the alarm changes.

----End

7.3.4 Saving the Information of a NodeB AlarmThis section describes how to save information of a NodeB alarm. You can save part or all ofthe alarm records displayed in the Alarm Browse window or Query Alarm Log dialog box asfiles in .txt, .htm, or .csv formats.

ContextA saved file has the following information: Serial No., Alarm Name, Alarm Severity, Raised/Clear Time, Location Info, Alarm ID, Module ID, Event Type, Alarm Type and NE Name.



49

Procedure

Step 1 Save all or part of the alarm records displayed in the Alarm Browse window or Query AlarmLog dialog box.The Save dialog box is displayed.

Step 2 Right-click the alarm you would like to save, and select Save Selected Alarms or Save AllAlarms from the shortcut menu.

Step 3 Enter a file name and specify a path and a file type.

NOTE

l The default path to save the alarm record is installation directory\client\output\NodeB\ version\alarm.

l The default file name is in the format of ALM-YY-MM-DD-HH-MM-SS.txt. For example, the filename ALM-05-11-07-15-42-37.txt indicates that this file is saved at 15:42:37 on November 7, 2005.

Step 4 Click Save.

----End

7.3.5 Manually Printing Alarm InformationThis section describes how to print a part or all of the alarm records in the Alarm Browse windowor the Query Alarm Log window.

PrerequisiteThe LMT is connected to a printer.

Procedure

Step 1 In the Alarm Browse window or the Query Alarm Log window:l To print all alarms, right-click in the window and choose Print All Alarms from the shortcut

menu.l To print selected alarm records, select the records, right-click, and select Print Selected

Alarms.The Print dialog box is displayed.

Step 2 Set the print requirements.

Step 3 Click Print.

----End

7.3.6 Querying Alarm Handling SuggestionsThis section describes how to query alarm handling suggestions. The LMT provides detailedhelp information for every alarm.

ContextThe LMT provides detailed help information for every alarm, which includes:l Alarm meaning



50

l Impact on systeml System actionl Alarm handling

Procedure

Step 1 In the Browse Alarm window or the Query Alarm Log window, double-click an alarm. TheAlarm Detailed Information dialog box is displayed.

Step 2 In the Alarm Detailed Information dialog box, click F1. The online help window is displayed.

Step 3 Check the information.

----End

7.3.7 Shielding NodeB AlarmsThis section describes how to shield an alarm. Shielding an alarm indicates that the NodeBneither saves that alarm nor reports it to the LMT.

ContextAn unshielded NodeB alarm means that the NodeB saves that alarm and reports it to the LMT.You can query the unshielded alarm.

NOTE

When shielding an alarm that has already been reported:

l It will not shield the alarm report already reported. It will shield the next report of the alarm.

l The NodeB recovers the alarm and the alarm is displayed as recovered.

Procedurel GUI mode

1. Select Fault Management > Query Alarm Configuration. The Query AlarmConfiguration dialog box is displayed.

Table 7-7 describes the fields in the Query Alarm Configuration dialog box.

Table 7-7 Fields in the Query Alarm Configuration dialog box

Field Description

Alarm ID This enables you to specify an alarm ID range.

Alarm Severity This enables you to specify one or multiple alarm severities:Critical, Major, Minor, and Warning.



51

Field Description

Modification Flag This enables you to specify whether you want to query thealarms with modification flag. Value range: Modified,Unmodified, or All.Modified means that the configuration information of thealarms has been changed. If Alarm Severity, Shield Flag, orTo Alarmbox Flag is modified, the modification flag of thealarm is displayed.The NodeB does not support modifying To Alarmbox Flag.Therefore, if Shield Flag of an alarm is modified, itsmodification flag is modified.

Shield Flag This enables you to specify whether you want to query thealarms with shield flag. Value range: Shielded, Unshielded,or All.All means that you can query all the alarms including shieldedand unshielded alarms.

To Alarm BoxFlag

NodeB dose not support this function.

Return Amount This enables you to specify the number of records that aredisplayed.

2. Set the search conditions in the dialog box.

3. Click OK. The Query Alarm Configuration window is displayed with the queryresult.

4. Select an alarm record to be modified in the window. Right-click the alarm record andselect Modify Alarm Configuration on the shortcut menu. The Modify AlarmConfiguration dialog box is displayed.

Table 7-8 describes the fields in the Modify Alarm Configuration dialog box.

Table 7-8 Fields in the Modify Alarm Configuration dialog box

Field Description

Alarm ID This item is unavailable for the NodeB.

Alarm Severity This allows you to modify alarm severity. Value range:Critical, Major, Minor, and Warning.

Shield Flag This enables you to specify whether you want to querythe alarms with a shield flag. Value range: Shielded orUnshielded.

To Alarm Box Flag NodeB dose not support this function.

5. Modify Shield Flag in the dialog box.

6. Click OK. The modification is complete.



52

l MML mode

Run the command SET ALMSHLD to set alarm shielding flag.

----End

7.3.8 Clearing the AlarmsThis section describes how to clear the recovered alarms when browsing or querying alarms.

Procedure

Step 1 Right-click in the Alarm Browse window or Query Alarm Log window. The shortcut menuis displayed.

Step 2 Select the operation from the shortcut menu as needed.

Operation Description

Clear All Recovery Alarms All recovered alarms are cleared from the window.

This function is applied to the Fault Alarm Browsewindow and Query Alarm Log window.

Clear Active Window All recovered alarms in the active window are cleared.

This function is applied to the Fault Alarm Browsewindow and Event Alarm Browse window.

Clear Selected Recovery Alarms The recovered alarms that you select are cleared from thewindow.

This function is applied to Query Alarm Log window.

----End

7.3.9 Refreshing the Alarm WindowThis section describes how to manually refresh the alarm window to update the alarminformation.

Procedure

Step 1 Right-click in the Fault Alarm Browse pane or Query Alarm Log window. The shortcut menuis displayed.

Step 2 Select Manually Refresh.



53

NOTE

l In the Fault Alarm Browse pane, the alarms are displayed in real time. Therefore, the cleared alarmsare no longer displayed in the Alarm Browse window after you manually refresh the window.

l In the Query Alarm Log window, the alarms are not displayed in real time. The alarms are displayedaccording to the original query conditions after the window is manually refreshed.

----End



54

8 Managing NodeB Equipment

About This Chapter

This chapter describes how to manage the NodeB and related boards. The LMT provides theinterface of the device panel and physical topology for the routine maintenance of the NodeB.

8.1 Operating the NodeB Device PanelThis section includes instructions for operating the NodeB device panel.

8.2 Using the Physical TopologyThis section includes instructions for using the physical topology to set device properties andquery current status of the device.

8.3 NodeB-Level OperationsThis section presents the NodeB-level operations, which includes querying active version andsoftware version, and resetting the NodeB.

8.4 NodeB Board-Level OperationsThis section describes the NodeB board-level maintenance and operations in GUI mode or MMLmode.

NodeBLMT User Guide 8 Managing NodeB Equipment


55

8.1 Operating the NodeB Device PanelThis section includes instructions for operating the NodeB device panel.

8.1.1 Introduction to the NodeB Device PanelThe NodeB device panel provides multiple ways to maintain the device. Besides MMLcommands, the GUI-based device panel simplifies and the information of virtual cabinets canbe displayed,visualize the operation and maintenance of the device.

Functions of the Device PanelThe device panel provides graphic user interface according to the actual structure of the NodeB.

In the device panel, select a board in position and right-click the board to display a shortcut menuwith all the available operations. For detailed operations on NodeB boards, see 8.4 NodeBBoard-Level Operations.

Interface of the Device PanelThe panel automatically refreshes to display the board status in real time. Figure 8-1shows theinterface of the device panel for macro NodeBs.

NOTE

This example is for reference only. The actual layout and appearance maybe different.

Figure 8-1 An example of the Device Panel interface



56

The elements of the Device Panel interface are described in Table 8-1.

Table 8-1 Elements in the Physical Topology window


1 Device panel The hardware configuration information and realtime statusof boards in the cabinet are displayed in the device panel,according to the information reported from the NodeB. Inaddition, the operations related to the NodeB can beperformed on the device panel.

2 Legend The legend is a color reference for boards and cables on thedevice panel, which lists the meanings of each color. Eachcolor represents a specific status of the board.

3 Failure Bar The failure bar displays active alarms on the board in realtime.

NOTE

l If the total length of the alarm information exceeds the frame capacity, the failure bar scrolls thedisplay of the information in cycle.

l Alarm information stops scrolling when the cursor moved to the failure bar.

8.1.2 Starting the NodeB Device PanelThis describes how to start the NodeB device panel to operate and maintain the boards in position.

Prerequisitel The LMT has logged in to the NodeB successfully.

Context

Start the device panel before operating and managing the macro NodeB.

Procedurel GUI mode:

1. In the navigation tree of the Local Maintenance Terminal window, click the DevicePanel tab.

2. Select Device Management > Cabinet Name. The device panel is displayed.

----End

8.1.3 Showing or Hiding the Legend on the NodeB Device PanelThis section includes instructions for showing or hiding color reference on the NodeB devicepanel.



57

Prerequisitel The LMT have logged in to the NodeB successfully.

l The device panel is started.

Context

You can make a preliminary decision according to the board status by viewing the color of eachboard.

Procedurel Click at the upper-right corner of the device panel to hide the color reference window

on the device panel.

l Click at the upper-right corner of the device panel to show the color reference windowon the device panel.

----End

8.1.4 Showing or Hiding the Failure Bar on the NodeB Device PanelThe failure bar displays active alarms in real time.

Prerequisitel The LMT have logged in to the NodeB.

l The device panel is started.

Procedure

Step 1 Right-click on the outside edge area of the subrack.A shortcut menu displays.

Step 2 Select Show Failure Bar or Hide Failure Bar from the shortcut menu.

NOTE

l By default, the failure bar is displayed if there is an active alarm.

l If there is no active alarm, the failure bar is not displayed, and the Show Failure Bar option is notavailable.

----End

ResultThe active alarms related to the current device are displayed in the failure bar.

8.2 Using the Physical TopologyThis section includes instructions for using the physical topology to set device properties andquery current status of the device.



58

8.2.1 Introduction to Physical TopologyThe topology management function of the LMT provides a man-machine interface, which usesa physical topology to show messages reported by NEs.

Functions of the Physical TopologyThe physical topology allows you to:l Map equipment nodes, device status, and connection between the nodes.l Set and query the current status of the devices.

Physical Topology WindowThe physical topology window consists of the toolbar, physical topology, and legend. As shownin Figure 8-2.

Figure 8-2 Physical topology window

Table 8-2 describes the elements in the physical topology window.



59

Table 8-2 Description of the physical topology window

Number Field Description

1 Toolbar The toolbar displays buttons of various functions. You canuse these buttons to perform basic operations on thetopology. Table 8-3 lists the functions of these buttons.

2 PhysicalTopology

Based on the information reported by NEs, the physicaltopology displays the configuration and connection statusbetween the RRU and the BBU or the basic cabinet. Youcan use the physical topology to perform operations on theNodeB board.The physical topology displays according to theconfiguration of the on-site NEs.

3 Legend In the physical topology, each board or cable has anindication color to note the current board status andconnections between boards.

Table 8-3 Description of the toolbar button function

Function Description

Selection Interactor After clicking this function button, hold the left mouse button whilemoving the mouse and then release the mouse button to select nodesin an area.

Pan Interactor After clicking this function button, hold the left mouse button andmove the mouse to move the topology.

Zoom In Enlarge the display scale of the topology view.

Zoom Out Narrow the display scale of the topology view.

Zoom on a Rectangle After clicking this function button, hold the left mouse button toenlarge the display scale of the selected area.

Zoom Back Restore the display scale to the default setting.

Airscape Click this function button to display the Airscape dialog box, whichshows the operations in the topology view synchronously.

Select Floor Select the floor and load its topology in the Select Floor dialog box.

Set Floor Background Select a local image and set it to the background of the displayinterface.This function is not available in Whole Building Mode.

Delete CurrentBackground

Delete the current background image and restore it to the last setting.This function is not available in Whole Building Mode.

Refresh Refresh the topology.



60

Function Description

Save Devices Position Click this function button to display the Confirm dialog box andclick Yes to save the current position of the devices.

NOTE

The modification of the topology nodes position can be classified into two types:

l When the modification of the nodes position is on the same floor, move the mouse to move the node,and click Save Devices Position.

l When the modification of the nodes position is not on the same floor, do not move the mouse to movethe node. You can right-click the node and set the floor and position.

8.2.2 Starting the Physical TopologyThis section includes instructions to start the physical topology in order to query the currentstatus of the device.

Prerequisitel The LMT has logged in to the NodeB successfully.

l Ensure the RRU is configured.

Context

For macro NodeBs, the RRU physical topology can be started only when the RRU is configured.

Procedure

Step 1 In the navigation pane, click the Maintenance tab.

Step 2 Double-click Topology Management > RRU Physical Topology. The physical topology isdisplayed.

----End

8.2.3 Showing or Hiding the Legend of the Physical TopologyThis section includes instructions to show and hide color reference of the physical topology onthe device panel.

Prerequisitel The LMT have logged in to the NodeB successfully.

l The physical topology is started. For its start method, refer to 8.2.2 Starting the PhysicalTopology.

Context

Show or hide the legend expands the display area of the physical topology.



61

Procedurel Click to show the legend of the device panel.

l Click to hide the legend of the device panel.

----End

8.3 NodeB-Level OperationsThis section presents the NodeB-level operations, which includes querying active version andsoftware version, and resetting the NodeB.

8.3.1 Querying the Active Version of the NodeBThis presents the procedure to query the active version of the NodeB, which helps to learn theversion of the running NodeB.

Prerequisite

LMT has logged into the NodeB.

Contextl The NodeB version information consists of active software version information, active

software version status, hardware version, and active BootROM version.

l When querying a Macro NodeB, this function only applies to the active WMPT.

l When querying a Distributed NodeB, this function only applies to the active WMPT on theBBU.



2. Select Device Management > Cabinet Name. The NodeB device panel is displayed.3. Select the active WMPT on the device panel, and right-click the board. The shortcut

menu is displayed.4. Select List NodeB Running Version. The Result Information dialog box is

displayed, listing the version information.

l MML mode:

Run the command LST VER.

----End

8.3.2 Querying the Software Version of the NodeBThis presents the procedure to query the software version information of a Macro NodeB or adistributed NodeB.



62

Prerequisite

The LMT has logged in to the NodeB successfully.

Contextl Querying the software version means listing the versions of the NE software and patch.

The version information includes version number, version status (available or not), andwhether it is the current version.

l The software version stored on the NodeB consists of the following items:

– Software version of the active directory

– Software version of the standby directory

– Version of the active patch directory

– Version of the hot patch directoryl You can check the NodeB upgrade history by querying the software version.l When querying a Macro NodeB, this function only applies to the active WMPT.l When querying a Distributed NodeB, this function only applies to the active WMPT on the

BBU.



2. Select Device Management > Cabinet Name. The device panel is displayed.3. Select the active WMPT on the device panel, and right-click the board. The shortcut

menu is displayed.4. Select List NodeB Software Version. The Result Information dialog box is

displayed, listing the version information about the NodeB software and patches.l MML mode:

Run the command LST SOFTWARE.

----End

8.3.3 Resetting the NodeBThis section includes instructions to reset a Macro NodeB or a distributed NodeB.

Context

The NodeB needs be reset after updating some system data or downloading the dataconfiguration file. When a NodeB malfunctions, it must be reset to restore the system to thedefault settings.

l Resetting the WMPT board of a Macro NodeB will reset all boards on the Macro NodeB,and reset the entire macro NodeB.

l Resetting the WMPT on the BBU of the distributed NodeB will reset the BBU, and resetthe entire distributed NodeB.



63

CAUTIONl Resetting the NodeB leads to the resetting of all the boards in the NodeB. At the same time,

the services carried by the NodeB are disrupted. The NodeB needs be restarted.

l When the multi-mode base station works in co-module mode, resetting the NodeB interruptsservices of the other mode.

l When the multi-mode base station supports co-transmission through ports on a board workingin UMTS mode, resetting the NodeB interrupts services of the other mode.



2. Select Device Management > Cabinet Name. The device panel is displayed.

3. Select the WMPT on the device panel, and right-click the board. A shortcut menu isdisplayed.

4. Select Reset Board, and click Yes in the confirmation dialog box appeared.

l MML mode:

Run the command RST NODEB.

----End

Result

CAUTIONAfter the reset, the LMT displays the result. If the reset is successful, the LMT is disconnectedfrom the NodeB. You need to log in to the LMT again to connect to the NodeB.

8.4 NodeB Board-Level OperationsThis section describes the NodeB board-level maintenance and operations in GUI mode or MMLmode.

8.4.1 Introduction to NodeB Board-Oriented OperationsOperations of board management vary according to the NodeB type.

Table 8-4 describes the operations related to boards.



64

Table 8-4 Operations related to boards

NodeBType

Operation Board

MacroNodeB:

Resetting a board All boards except the NCMU and theNPMU

Querying the version of a board

Querying active board alarms

Querying the status of a board

Querying the manufacturinginformation of a board

Querying the CPU usage of a board

Blocking/unblocking a board WBBP, WRFU, and RRU

Querying the E1/T1 link status WMPT/UTRP

Querying the E1/T1 working mode

Querying the NodeB software version WMPT

Querying the active NodeB version

Querying the current clock status

Querying the STM-1 State UTRP

Querying the STM-1 Working Mode

Querying the Device Sequence ID RRU

Adding a sector

Modifying the transmit power

Set Floor and Position

Open Related Shelf

DistributedNodeB

Resetting a board All boards

Displaying the board version

Querying active board alarms

Displaying the board status

Querying the manufacturinginformation of a board

Querying the CPU usage of a board

Blocking/unblocking a board WBBP, WRFU, and RRU

Querying the E1/T1 link status WMPT/UTRP



65

NodeBType

Operation Board

Querying the E1/T1 working mode

Querying the NodeB software version WMPT

Querying the active NodeB version

Querying the current clock status

Querying the STM-1 State UTRP

Querying the STM-1 Working Mode

Querying the Device Sequence ID RRU/BBU

Adding a sector

Modifying the transmit power

Set Floor and Position

Open Related Shelf

8.4.2 Querying the State of a NodeB BoardThis section includes instructions to query the start of a board on a Macro NodeB or a DistributedNodeB.

PrerequisiteYou have logged in to the NodeB LMT.

Context

The state of a board can be active or standby. You can monitor the NodeB running status byquerying the running status of a board.

Table 8-5 describes the board status.

Table 8-5 Board status

Type BoardStatus

Description Remarks

Active/Standbystatus

Active Indicates that the board is active. Active/Standby status is onlyapplied to the WMPT andUTRP. Active/Standby statusof the other boards is None.

Standby Indicates that the board is standby.

None Indicates that the active or standbystatus is not applicable to thisboard.



66

Type BoardStatus

Description Remarks

Availability status

Uninstalled

Indicates that the board isconfigured but not installed.

This type of status indicates thephysical availability of theboard.

Unconfigured

Indicates that the board is installedbut not configured.

Inconsistent

Indicates that the installed board isnot consistent with the configuredone.

StartingUp

Indicates that the board is starting.

Faulty Indicates that there are criticalfaulty alarms on the board.

None The board is not in any of theabove statuses.

Operation status

Enabled Indicates that the board can carrya service.

This type of status indicateswhether the board can carry aservice.

Disabled Indicates that the board cannotcarry any service.

Adminstatus

Blocked Indicates that the board does notneed to carry service.

This type of status indicateswhether the board carries aservice and whether newservices are allowed to be set upon the board.Admin status is only permittedfor the WBBP, RRU, andWRFU. Admin status of theother boards is None.

Unblocked

Indicates that the board allows anew service to be set up on it.

None Indicates that the board is notmanageable.


Macro NodeB board and distributed NodeB BBU board:


2. Double-click Device Management > Main Cabinet. The device panel is displayed.3. Select the board to be queried, and right-click the board. A shortcut menu is displayed.4. Select Display Board Status. A dialog box is displayed, showing the running status

of that board.



67

NOTE

You can also query the board status by checking the board color. For details, refer to 8.1.1Introduction to the NodeB Device Panel.

Distributed NodeB RRU:

1. In the navigation tree of the Local Maintenance Terminal window, click theMaintenance tab.

2. Double-click Topology Management > RRU Physical Topology. The physicaltopology is displayed.

3. Select and right-click the RRU to be queried. The shortcut menu is displayed.4. Select Display Board Status. A dialog box is displayed, showing the running status

of that board.l MML mode:

Run DSP BRD.

----End

8.4.3 Querying Active Alarms of NodeB BoardsThis section includes instructions to query the active alarms of a NodeB board.

Contextl This procedure is used to determine the current state of the board, enabling you to locate

and clear faults on the board.l When a distributed NodeB is queried, the procedures for RRU and BBU are different.


Macro NodeB board and Distributed NodeB BBU board:


2. Select Device Management > Main Cabinet. The NodeB device panel is displayed.3. Select the board to be queried on the device panel.4. Right-click the board. The shortcut menu is displayed.5. Select Query Active Alarms. A dialog box is displayed, showing the fault alarms of

the board that have not cleared.




3. Select and right-click the RRU to be queried. The shortcut menu is displayed.4. Select Query Active Alarms. A dialog box is displayed, showing the fault alarms of

the board that are not cleared.



68

l MML mode

Run the command LST ALMAF.

----End

8.4.4 Querying the Version of a NodeB BoardThis section includes instructions to query the board version of a Macro NodeB or a distributedNodeB.

Contextl This procedure is used to determine the version information of the running boards including

the cabinet number, subrack number, slot number, CPU number, board software version,board hardware version, and BootROM version. This information enables you to check theconsistency between the board version and the NodeB version.

l When a distributed NodeB is queried, the procedures for RRU and BBU are different.

Procedurel GUI mode



2. Select Device Management > Main Cabinet. The NodeB device panel is displayed.3. Select the board to be queried on the device panel.4. Right-click the board. The shortcut menu is displayed.5. Select Display Board Version. A dialog box is displayed, showing the version

information for the board.




3. Right-click the RRU to be queried. The shortcut menu is displayed.4. Select Display Board Version. A dialog box is displayed, showing the version

information for the board.

l MML mode

Run the command DSP BRDVER.

----End

8.4.5 Querying the CPU Usage of a NodeB BoardThis section includes instructions to query the CPU usage on a Macro NodeB and a distributedNodeB.



69

Contextl This function checks the usage of the CPUs and DSPs on the board (including the secondary

CPU), enabling you to determine whether the system is overloaded.l When a distributed NodeB is queried, the procedures RRU and BBU are different.

Procedurel GUI mode



2. Select Device Management > Main Cabinet. The NodeB device panel is displayed.3. Select the board to be queried on the device panel, and right-click the board. The

shortcut menu is displayed.4. Select Display CPU Usage. The CPU/DSP Usage window is displayed, showing the

CPU/DSP usage of the board.




3. Right-click the RRU to be queried. The shortcut menu is displayed.4. Select Display CPU Usage. The CPU/DSP Usage window is displayed, showing the

CPU/DSP usage of the board.l MML mode

Run the command DSP CPUUSAGE.

----End

8.4.6 Querying the E1/T1 Link StatusThis section includes instructions to query the states of the E1/T1 links to determine whetherthe current E1/T1 link is within normal range.


Contextl This operation is only available on the WMPT or UTRP board in a macro NodeB or a BBU

in a distributed NodeB.

Procedurel GUI Mode:




70

2. Double-click Device Management > Main Cabinet. The device panel is displayed.

3. Select the WMPT or UTRP on the device panel, and right-click the board. A shortcutmenu is displayed.

4. Select Display E1/T1 State. The Display E1/T1 State dialog box is displayed.

5. Set the necessary parameters in the dialog box.

6. Click OK. The status of all E1/T1 links of the board is displayed in the dialog box.

l MML Mode:

Run the DSP E1T1 command to query the E1/T1 link status of a specific board.

----End

8.4.7 Querying the E1/T1 Work ModeThis section includes instructions to query the work mode of the E1/T1 links.


Contextl This operation is only available on the WMPT or UTRP board in a macro NodeB or the

BBU in a distributed NodeB.





4. Select Display E1/T1 Work Mode. The Display E1/T1 Work Mode dialog box isdisplayed.


6. Click OK, and the work mode of all E1/T1 links of the board is displayed in the dialogbox.

----End

8.4.8 Querying the STM-1 StateThis section includes instructions to query the state of the STM-1 optical port to determinewhether the current STM-1 port is within normal range.




71

Contextl This operation is only available on the UTRP board in a macro NodeB or the BBU in a

distributed NodeB.





4. Select Display STM-1 State. The Display STM-1 State dialog box is displayed.


6. Click OK. The status of the STM-1 optical port is displayed in the dialog box.

l MML Mode:

Run the DSP STM1 command to query the STM-1 state of a specific board.

----End

8.4.9 Querying the STM-1 Working ModeThis section includes instructions to query the work mode of the STM-1 optical port.


Contextl This operation is only available on the UTRP board in a macro NodeB or the BBU in a

distributed NodeB.





4. Select Display STM-1 Work Mode. The Display STM-1 Work Mode dialog boxis displayed.


6. Click OK, and the work mode of the STM-1 optical port is displayed in the dialogbox.

l MML Mode:



72

Run the DSP STM1 command to query the STM-1 work mode of a specific board.

----End

8.4.10 Blocking/Unblocking a NodeB BoardThis section includes instructions to block or unblock a NodeB board on the LMT.


Contextl This operation helps to perform maintenance without interrupting the system services.

l This task only applies to service processing boards such as the WBBP, WRFU, and RRU.It is not applicable to the WMPT or UTRP boards.

l When a board is blocked, the board is available but cannot process services. Services onthat board are cleared and the subsequent new services are switched to other boards.

l Boards support repeated blocking.




2. Double-click Device Management > Main Cabinet. The device panel interface isdisplayed on the right.

3. Select a board on the device panel, and right-click the board. The shortcut menu isdisplayed.

4. Select Block Board. A dialog box is displayed for your confirmation.

5. Click Yes in the dialog box. The LMT displays the result and refreshes the board colorindicator.




3. Right-click the RRU node. The shortcut menu is displayed.

4. Select Block Board. A dialog box is displayed for your confirmation.




73

NOTE

l You can unblock a board only when it is blocked.

l The procedure for unblocking a board is similar to that for blocking a board. You can unblock aboard by right-clicking a blocked board and then choosing Unblock Board from the shortcutmenu.

l MML mode:

Run the BLK BRD command.

Run the UBL BRD command.

----End

8.4.11 Resetting a NodeB BoardThis section includes instructions to reset a NodeB board.


Context

This operation is required when a board is faulty. The board is initialized and restored after thereset.

CAUTIONl Resetting a board causes the board to restart.l Resetting a board may cause data loss to its services.l Resetting a board may cause it to become unavailable. After it is initialized again, it will be

available for service.l Resetting the active WMPT may result in the entire NodeB reset.l When the multi-mode base station works in co-module mode, resetting the TRX module

interrupts the services of the other mode.l When the multi-mode base station supports co-transmission through ports on a board working

in UMTS mode, resetting the board where ports shared by both modes interrupts the servicesof the other mode.

Procedurel GUI mode



2. Double-click Device Management > Main Cabinet. The device panel interface isdisplayed on the right.



74

3. Select the board to be reset on the device panel, and right-click the board. The shortcutmenu is displayed.

4. Select Reset Board. A dialog box is displayed for your confirmation.






4. Select Reset Board. A dialog box is displayed for your confirmation.


l MML mode:

Run the RST BRD command.

----End

8.4.12 Adding and Removing a NodeB BoardThis section includes instructions to add or remove a NodeB board using MML commands.

Prerequisite

Before adding or removing a NodeB board, ensure the operation will not affect current servicesor other boards. If necessary, back up the NodeB system.

Contextl When the NodeB capacity is changed, this task modifies the data configuration file of the

NodeB directly.

Procedurel Run the command ADD BRD to add a board.

l Run the command RMV BRD to remove a board.

----End

8.4.13 Querying the Current Clock StatusThis section describes how to query the current status of the clock.




75

Contextl This function checks whether the setting changes are correct and whether the clock needs

adjustment.

l This operation is only applicable to the WMPT board.

l The current status of the clock includes:

– The configured clock source

– The status of current clock source

– The clock status

– The DA value of the carrier frequency

– The DA value of the current frequency

– The initial DA value



2. Double-click Device Management > Main Cabinet. The device panel is displayed.3. Select the WMPT on the device panel, and right-click the WMPT board. A shortcut

menu is displayed.4. Select Display Current Clock Status. The current clock status is displayed.

NOTE

The clocks of the active and standby WMPT are independent. Therefore, you can query their statusseparately. In the query result, the clock source and the status of the clock source should be the samein the active WMPT and the standby WMPT. Other parameters in the query results of the activeWMPT and the standby WMPT clocks can be different.

l MML Mode:

Run the DSP CLKSTAT command to query the current clock status.

----End

8.4.14 Querying the Sequence ID of the RRUThis section includes instructions to query the sequence ID of the RRU.

Prerequisite

This procedure may only be executed on a macro NodeB where a RRU has been installed.

Context

This operation is the same in a macro NodeB and a distributed NodeB.

Procedure




76


Step 3 Right-click the RRU node. The shortcut menu is displayed.

Step 4 Select Display Device Sequence ID. The Result Information dialog box is displayed, listingthe result.

----End

8.4.15 Adding a SectorThis section includes instructions to add an RRU to a specified sector.

Prerequisite

Ensure that the site of the specific sector exists. Otherwise, the task will fail.

Contextl The TX/RX mode of distributed sectors is always unidirectional (TX/RX).

l When adding a distributed sector, you can add a group of RRUs with continuous subracknumbers. The cabinet number and slot number of each RRU must be the same. The subracknumber starts from the first RRU to the last RRU.


1. In the navigation pane, click the Maintenance tab.


3. Right-click the RRU node. A shortcut menu is displayed.

4. Choose Add Sector from the shortcut menu.The Add Sector dialog box is displayed. Table 8-6 describes the parameters in thedialog box.

5. Set the parameters, and then click OK.

NOTEParameters are dependent on actual scenarios. Therefore, not all the parameters listed belowwill display in the dialog box.

Table 8-6 Add Sector Parameters


Site No. Indicates the number of the site where the sector is configured.

Sector No. Indicates the number of the sector. Sector No. uniquelyidentifies a sector in a site. A maximum of six sectors can beconfigured on each site.



77


Sector Type Indicates the type of the sector to be added.Sector Type can be set to REMOTE_SECTOR orDIST_SECTOR.

RX AntennaMagnitude

Indicates the number of RX antennas in the sector.This parameter is valid only when Sector Type is set toREMOTE_SECTOR.

Diversity Mode This parameter is valid only when Sector Type is set toREMOTE_SECTOR.Diversity Mode can be set to COMMON_MODE orHALFFREQ.

Cover Type This parameter is valid only when Sector Type is set toREMOTE_SECTOR and Diversity Mode is set toHALFFREQ.Cover Type can be set to SAMEZONE or DIFFZONE.

Cabinet No. ofRRU (Begin)

Indicates the number of the cabinet where the first RRU islocated.This parameter is valid only when Sector Type is set toDIST_SECTOR.

Subrack No. ofRRU (Begin)

Indicates the number of the subrack where the first RRU islocated.This parameter is valid only when Sector Type is set toDIST_SECTOR.

Slot No. of RRU(Begin)

Indicates the number of the slot where the first RRU is located.This parameter is valid only when Sector Type is set toDIST_SECTOR.

Cabinet No. ofRRU (End)

Indicates the cabinet number of the last RRU. The first RRUand the last RRU have the same cabinet number.This parameter is valid only when Sector Type is set toDIST_SECTOR.

Subrack No. ofRRU (End)

Indicates the subrack number of the last RRU. The subracknumber of the last RRU must be equal to or larger than thesubrack number of the first RRU.This parameter is valid only when Sector Type is set toDIST_SECTOR.

Slot No. of RRU(End)

Indicates the slot number of the last RRU. The first RRU andthe last RRU have the same slot number.This parameter is valid only when Sector Type is set toDIST_SECTOR.

l MML Mode:



78

Run the ADD SEC command.

----End

8.4.16 Modifying the Emission Power of the RRUThis section includes instructions to modify the emission power of the RRU.

Procedurel GUI mode




4. Select Change Emissivity.The Change Emissivity dialog box is displayed, and parameter description is asshown in Table 8-7.

5. Set the parameters, and then click OK.

NOTEParameters are dependent on actual scenarios. Therefore, not all the parameters listed belowwill display in the dialog box.

Table 8-7 Change Emissivity Parameters

Field Description

Local Cell ID ID of the local cell

Cabinet No. of RRU Number of the cabinet where the RRU is located.

Subrack No. of RRU Number of the subrack where the RRU is located.

Slot No. of RRU Number of the slot where the RRU is located.

Power Setting Mode Mode to specify the RRU power. You can chooseDEFAULT or ABSOLUTE.l DEFAULT: using the default power specified by the

local celll ABSOLUTE: using the absolute value specific to

this PA

Max RRU Output Power(0.1dBm)

This parameter is valid only when the power settingmode is set to ABSOLUTE.

l MML mode

Run the command MOD RRUOFLOCELL.

----End



79

8.4.17 Setting Floor and PositionThis section includes instructions to set the floor and position.

Contextl This operation can only be performed on the RRU.

l This operation can only be performed in GUI mode. There is no corresponding MMLcommand.

NOTEThe floor and position set here are not the actual floor position, but the topology position. This operationcan easily be done by dragging the node to the position you choose in the GUI after the physical topologyis displayed.

Procedure



Step 3 Select Set Floor and Position.The Set Floor and Position dialog box is displayed, and parameter description is as shown inTable 8-8.

Step 4 Set the parameters, and then click OK.

Table 8-8 Set Floor and Position Parameters

Field Description

Subrack No: Number of the subrack where the RRU is located.

X-Coordinate The X coordinates of the RRU in the physical topology.

Y-Coordinate The Y coordinates of the RRU in the physical topology

Floor Number of the floor where the RRU is located.

----End

8.4.18 Querying the Board Manufacturing InformationThis section includes instructions to query the board manufacturing information including theboard type, bar code, description, manufactured date, vendor's name, and issue number.

Context

This function queries all boards except the slave CPU, UBF, UPEA, UPEB, and UEIU. To querythe backplane, set the parameters as follows: CN=0, SRN=0, SN=255.



80




2. Select Device Management > Main Cabinet. The NodeB device panel is displayed.

3. Select a board on the device panel, and right-click the board. The shortcut menu isdisplayed.

4. Select List Board Manufacturing Information.The List Board Manufacturing Information dialog box is displayed with themanufacturing information of the board.





4. Select List Board Manufacturing Information.The List Board Manufacturing Information dialog box is displayed.

5. Set the Cabinet No. (CN), Subrack No. (SRN), and Slot No. (SN), and click OK.

l MML mode:Run the MML command line DSP BRDMFRINFO.

----End

8.4.19 Opening the Related ShelfThis section provides instructions for opening the shelf or cabinet related to the RRU throughthe physical topology.

Contextl This operation can only be performed on the RRU.

l This operation can only be performed in GUI mode. There is no corresponding MMLcommand.

Procedure



Step 3 Select Open Related Shelf.This will only display the shelf or cabinet information when they exist.

----End



81

9 Managing the Interface Tracings

About This Chapter

After creating an interface tracing task, you can browse and save the traced messages.

9.1 Basic Concepts of the Interface TracingThis section describes the basic concepts of the interface tracing.

9.2 Tracing Iub interface MessagesThis section describes how to trace messages at the Iub interface. Traced messages can beautomatically or manually saved. You can browse the traced messages online or offline.

9.3 Tracing SCTP MessagesThis section describes how to trace SCTP messages. This task is performed to trace theinteraction of SCTP Messages and locate problems that lead to the unavailability of the SCTPlink. Traced messages can be automatically or manually saved. You can browse the tracedmessages online or offline.

9.4 Tracing IP MessagesThis section describes how to trace IP messages. This task is performed to locate problems thatlead to the unavailability of the IP path. Traced messages can be automatically or manuallysaved. You can browse the traced messages online or offline.

9.5 Tracing ICP MessagesThis section describes how to trace ICP messages. This task is performed to trace the interactionof ICP cells on the IMA link and locate problems that lead to the unavailability of theinterconnection between the NodeB and the peer IMA. Traced messages can be automaticallyor manually saved. You can browse the traced messages online or offline.

9.6 Tracing SAAL MessagesThis section describes how to trace SAAL messages. Start the SAAL Protocol Tracing task tomonitor the interaction between messages of the SAAL protocol and locate problems causingSAAL links to be unavailable. Traced messages can be automatically or manually saved. Youcan browse the traced messages online or offline.

9.7 Tracing User MessagesThis section describes how to trace user messages. This task is performed to trace user messagesand locate problems of user messages. Traced messages can be automatically or manually saved.You can browse the traced messages online or offline.

NodeBLMT User Guide 9 Managing the Interface Tracings


82

9.8 Tracing Cell MessagesThis section describes how to trace cell messages. This task is performed to trace cell messagesand locate problems of cell messages. Traced messages can be automatically or manually saved.You can browse the traced messages online or offline.

9.9 Tracing PPP MessagesThis section describes how to trace message interworking of Point-to-Point Protocol (PPP) links.Tracing the messages helps locate problems in PPP interconnection between a NodeB and a peerdevice. The traced messages can be saved automatically or manually and browsed online oroffline.

9.10 Tracing MP MessagesThis section describes how to trace message interworking of Multilink Protocol (MP) links inan MP group. Tracing the messages helps locate problems in MP group interconnection betweena NodeB and a peer device. The traced messages can be saved automatically or manually andbrowsed online or offline.

9.11 Tracing MAC MessagesThis section describes how to trace the MAC messages. Problems related to the Iub interface,OM channel, and packet loss can be located by analyzing the header and content of the datapacket. Traced messages can be automatically or manually saved. You can browse the tracedmessages online or offline.

9.12 Tracing PTP MessagesThis section describes how to trace the PTP messages and locate the PTP message problem.Traced messages can be automatically or manually saved. You can browse the traced messagesonline or offline.

9.13 Basic Operations of Interface TracingsThis section describes the basic operations of interface tracings. You may browse, view, andsave tracing messages. Instructions are also included for resuming or deleting tracing tasks, andtracing task pausing. These operations are available for all message tracing tasks.

9.14 Interface Reference for Managing the Interface TracingThis section provides parameter descriptions for managing the interface tracings.



83

9.1 Basic Concepts of the Interface TracingThis section describes the basic concepts of the interface tracing.

Functions of Message Tracing ManagementMessage tracing management is used to trace interfaces, signaling links, and internal messages.It is used for routine equipment maintenance, debugging, and fault location.

The NodeB provides the following tracing functions:l Tracing the Iub interface signalingl Tracing IP messagesl Tracing SCTP messagesl Tracing ICP messagesl Tracing SAAL messagesl Tracing user messagesl Tracing cell messagesl Tracing MAC messagesl Tracing PTP Messages

Internal Process for Tracing MessagesThis section describes the internal processes for creating a tracing task and reporting tracedmessages from a board to the LMT.

l Creating a tracing task– The operator creates a tracing task on the LMT, and the LMT sends a binary command

to the BAM to create the task.– The BAM assigns an ID to the task and forwards the command to the debugging module

of the specified board.– After receiving the command, the debugging module records the filter parameters of

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

debugging module.l Reporting traced messages

– The service module filters the collected messages according to the filter parameters inthe local filter table and reports the messages that meet the requirements to the BAM.

– The BAM server forwards the messages to the LMT that created the task according tothe task ID.

– The LMT translates the traced messages and displays them on the interface.

9.2 Tracing Iub interface MessagesThis section describes how to trace messages at the Iub interface. Traced messages can beautomatically or manually saved. You can browse the traced messages online or offline.



84

Contextl Four Iub message tracing tasks can be created on the LMT at one time. One message display

window can be created for each tracing task.

l The prompt for a busy system and failure in starting an Iub message tracing task mayoriginate in an overloaded CPU. It is recommended that you start the tracing task 30 secondsafter the CPU overload has cleared.

Procedure

Step 1 In the navigation tree, select Trace Management > Interface Trace Task > Iub.The Standard Signaling Interface Tracing dialog box is displayed. For the parameter details,see 9.14.1 Interface Reference for IUB Tracing.

Step 2 Select the type of message to be reported, and click OK.

The Standard Signaling Interface Tracing window is displayed. You can query the messageflow of the interface from the displayed window.

For the detail operation in the window, see 9.13 Basic Operations of Interface Tracings.

NOTE

YYYY-MM-DD_HH-MM-SS (Tick, one Tick corresponds to 10 ms) represents the task creation time.YYYY, MM, DD, HH, MM, and SS represent year, month, day, hour, minute, and second respectively.

----End

9.3 Tracing SCTP MessagesThis section describes how to trace SCTP messages. This task is performed to trace theinteraction of SCTP Messages and locate problems that lead to the unavailability of the SCTPlink. Traced messages can be automatically or manually saved. You can browse the tracedmessages online or offline.

ContextIn IP transport mode, the lower layer link used by the NCP or a CCP is the SCTP link. Whenthe NCP or a CCP is not functional, you can start the SCTP protocol tracing task to queryinformation on the SCTP link of concern. The SCTP link receives and transmits data frequently.Therefore, starting this tracing task may affect the system performance. You are advised not tostart multiple SCTP tracing tasks simultaneously.

Procedure

Step 1 In the navigation tree, select Trace Management > Interface Trace Task > SCTP.The SCTP Tracing dialog box is displayed. For the parameter details, see 9.14.2 InterfaceReference for SCTP Tracing.

Step 2 Set the corresponding parameters, and click OK.

The message browsing window is displayed. You can query the message flow of the interfacefrom the displayed window.



85


----End

9.4 Tracing IP MessagesThis section describes how to trace IP messages. This task is performed to locate problems thatlead to the unavailability of the IP path. Traced messages can be automatically or manuallysaved. You can browse the traced messages online or offline.

Procedure

Step 1 In the navigation tree, select Trace Management > Interface Trace Task > IP.The IP Tracing dialog box is displayed. For the parameter details, see 9.14.3 InterfaceReference for IP Tracing.




----End

9.5 Tracing ICP MessagesThis section describes how to trace ICP messages. This task is performed to trace the interactionof ICP cells on the IMA link and locate problems that lead to the unavailability of theinterconnection between the NodeB and the peer IMA. Traced messages can be automaticallyor manually saved. You can browse the traced messages online or offline.

Procedure

Step 1 In the navigation tree, select Trace Management > Interface Trace Task > ICP.The ICP Tracing dialog box is displayed. For the parameter details, see 9.14.4 InterfaceReference for ICP Tracing.




----End

9.6 Tracing SAAL MessagesThis section describes how to trace SAAL messages. Start the SAAL Protocol Tracing task tomonitor the interaction between messages of the SAAL protocol and locate problems causingSAAL links to be unavailable. Traced messages can be automatically or manually saved. Youcan browse the traced messages online or offline.



86

Procedure

Step 1 In the navigation tree, double-click Trace Management > Interface Trace Task > SAAL.The SAAL Tracing dialog box is displayed. For the parameter details, see 9.14.5 InterfaceReference for SAAL Tracing.




NOTE

The SAAL Protocol Tracing task is performed to locate the problem that leads to the unavailability of theSAAL link. If there are only outgoing but no incoming NodeB messages, you can infer that the lower layerlink (PVC) or the peer end works abnormally.

----End

9.7 Tracing User MessagesThis section describes how to trace user messages. This task is performed to trace user messagesand locate problems of user messages. Traced messages can be automatically or manually saved.You can browse the traced messages online or offline.

Procedure

Step 1 In the navigation tree, select Trace Management > Interface Trace Task > User. The UserTracing dialog box is displayed, as shown in Figure 9-1.

Figure 9-1 User Tracing dialog box

For the parameter details in the dialog box, see 9.14.6 Interface Reference for User Tracing.

Step 2 Click the Basic tab, and set the corresponding parameters.

Step 3 Click the IUB tab, and select the type of the IUB message to be traced.

Step 4 Click the UU tab, and select the type of the UU message to be traced. Then set the parametersbased on the requirements of the tracing task.

Step 5 Click OK. The message browsing window is displayed. You can query the message flow of theinterface from the displayed window.


----End



87

9.8 Tracing Cell MessagesThis section describes how to trace cell messages. This task is performed to trace cell messagesand locate problems of cell messages. Traced messages can be automatically or manually saved.You can browse the traced messages online or offline.

Procedure

Step 1 In the navigation tree of the Local Maintenance Terminal window, select TraceManagement > Interface Trace Task > Cell. The Cell Tracing dialog box is displayed, asshown in Figure 9-2.

Figure 9-2 Cell Tracing dialog box

For the parameter details in the dialog box, see 9.14.7 Interface Reference for Cell Tracing.

Step 2 Click the Basic tab, and set the corresponding parameters.

Step 3 Click the IUB tab, and select the type of the IUB message to be traced.

Step 4 Click the UU tab, and select the type of the UU message to be traced. Then set the parametersbased on the requirements of the tracing task.

Step 5 Click OK. The message browsing window is displayed. You can query the message flow of theinterface from the displayed window.


----End

9.9 Tracing PPP MessagesThis section describes how to trace message interworking of Point-to-Point Protocol (PPP) links.Tracing the messages helps locate problems in PPP interconnection between a NodeB and a peerdevice. The traced messages can be saved automatically or manually and browsed online oroffline.

Procedure

Step 1 In the navigation pane, choose Trace Management > Interface Trace Task > PPP.The PPP Tracing dialog box is displayed. For description about related parameters, see 9.14.8Interface Reference for PPP Tracing.

Step 2 Set parameters and click OK. View traced messages in the displayed browsing window of tracedmessages.



88

For detailed operations to be performed in the window, see 9.13 Basic Operations of InterfaceTracings.

----End

9.10 Tracing MP MessagesThis section describes how to trace message interworking of Multilink Protocol (MP) links inan MP group. Tracing the messages helps locate problems in MP group interconnection betweena NodeB and a peer device. The traced messages can be saved automatically or manually andbrowsed online or offline.

ProcedureStep 1 In the navigation pane, choose Trace Management > Interface Trace Task > MP.

The MP Tracing dialog box is displayed. For description about related parameters, see 9.14.9Interface Reference for MP Tracing.

Step 2 Set parameters and click OK. View traced messages in the displayed browsing window of tracedmessages.

For detailed operations to be performed in the window, see 9.13 Basic Operations of InterfaceTracings.

----End

9.11 Tracing MAC MessagesThis section describes how to trace the MAC messages. Problems related to the Iub interface,OM channel, and packet loss can be located by analyzing the header and content of the datapacket. Traced messages can be automatically or manually saved. You can browse the tracedmessages online or offline.

ProcedureStep 1 In the navigation pane, double-click Trace Management > Interface Trace Task > MAC.

The MAC Trace dialog box is displayed. For the parameter details in the MAC Trace dialogbox, see 9.14.10 Interface Reference for MAC Tracing.




----End

9.12 Tracing PTP MessagesThis section describes how to trace the PTP messages and locate the PTP message problem.Traced messages can be automatically or manually saved. You can browse the traced messagesonline or offline.



89

Procedure

Step 1 In the navigation pane, double-click Trace Management > Interface Trace Task > PTP.The PTP Trace dialog box is displayed. For the parameter details in the PTP Trace dialog box,see 9.14.11 Interface Reference for PTP Tracing.




----End

9.13 Basic Operations of Interface TracingsThis section describes the basic operations of interface tracings. You may browse, view, andsave tracing messages. Instructions are also included for resuming or deleting tracing tasks, andtracing task pausing. These operations are available for all message tracing tasks.

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

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

Context

You can right-click a traced message in the message browse window, and select an item fromthe shortcut menu to perform the associated operation as listed below.

Operations Description

Stop Trace Task Suspends the tracing task.

Restart Trace Task Restarts the suspended tracing task.

Recreate Trace Task Recreates the tracing task.

Save All Messages Saves all traced messages.

Save Selected Messages Saves selected traced messages.

Auto Scroll Scrolls through the message browse window in real time.

Clear Messages Deletes all messages from the message browse window.

Prompt When OverloadControl Occurs

Displays prompts in the case of overload.



90

Operations Description

Close All xxx MessageTrace Tasks

Closes all the XXX message tracing tasks (xxx stands for thetype of tracing tasks).

Properties Queries the task properties.

Procedure

Step 1 Browse or query the traced messages in the message browse window in real time.

Step 2 To learn about the details of a message, double-click it. The Message Browser dialog box isdisplayed showing details of the message.

----End

9.13.2 Querying the Properties of the Tracing TaskThis section describes how to query the properties of the tracing task in the message browsewindow.

Prerequisitel A tracing task is successfully created.

l Traced messages are reported.

Procedure

Step 1 Right-click in the message browse window, and then choose Property from the shortcut menu.

Step 2 The Trace Properties dialog box is displayed, showing the properties of the tracing task.

Step 3 Click OK to close the window.

----End

9.13.3 Viewing a Message TranslationThis section describes how to view the translation of a message in the message browse window.

Prerequisitel A tracing task is created.

l Traced messages are reported.

Procedure

Step 1 In the message browse window, select and double-click the traced message.

Step 2 The Message Browser window is displayed, showing the details and meaning of the messagein protocol translation format.



91

Step 3 Click on the top right of the window to close it.

----End

9.13.4 Automatically Saving Traced MessagesThis section describes how to enable the automatically saving function, which saves tracedmessages in the local directory as files.

Prerequisitel A tracing task is created.l Traced messages are reported.

Contextl The default save path is LMT installation directory\client\output\NodeB\LMT software

version number\trace.l The default file name is Office name_xxx tracing_YYYY-MM-DD-HH-MM-SS.l The file is automatically saved in .tmf format.

Procedurel When a tracing task is created, Auto Save is selected by default. The default setting is used

to automatically save all messages displayed in the message browse window.

NOTE

l The LMT saves every 5,000 messages in a file. From the 5001st message, the next set of 5,000messages are saved in the file that is named using a serial number. For example, the default nameof the file that contains the 5001st to 10000th SCTP messages is Office name_SCTP_YYYY-MM-DD-HH-MM-SS_1 and so on.

l You can use the Trace Viewer to browse offline the messages saved in .tmf format. For details,refer to 9.13.9 Browsing a Traced Message Offline.

l When a tracing task is created, deselect the Auto Save check box. Once this feature isdeselected, messages displayed in the message browse window are not saved automatically.

----End

9.13.5 Saving Traced Messages ManuallyThis section describes how to manually save all or part of messages when the tracing task isrunning.

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


version number\trace.l The default file name is Office name_xxx tracing_YYYY-MM-DD-HH-MM-SS.tmf.



92

l You can manually save the messages in the .tmf, .txt or .csv format.

Procedure

Step 1 Right-click the message browse window and select Save All Messages. To save selectedmessages, right-click the messages to be saved and select Save Selected Messages. The Savedialog box is displayed.

Step 2 Enter a file name and specify a path and a file type.

Step 3 Click Save.

----End

9.13.6 Suspending a Tracing TaskThis section describes how to suspend a tracing task when the tracing is not required.

Prerequisite

A tracing task is successfully created.

Procedure

Step 1 Right-click in the message browser window to be paused. The shortcut menu is displayed.

Step 2 Choose Stop Trace Task from the shortcut menu.

----End

9.13.7 Resuming a Tracing TaskThis section describes how to resume a tracing task when you want to continue the tracing task.

PrerequisiteA tracing task is suspended.

Procedure

Step 1 Right-click the message browse window. The shortcut menu is displayed.

Step 2 Select Restart Trace Task from the shortcut menu.

----End

9.13.8 Closing a Tracing TaskThis section describes how to close a tracing task to release system resource when the task isnot needed.

PrerequisiteA tracing task is created.



93

Procedurel Click in the top right corner of the message browse window.l Right-click in the message browse window, and choose Close All xxx Message Trace

Tasks (xxx stands for specific tracing tasks). If an IP tracing task needs to be closed, chooseClose All IP Message Trace Tasks.

----End

9.13.9 Browsing a Traced Message OfflineThis section describes how to use the Trace Viewer to browse offline messages that are savedin .tmf format.

PrerequisiteA traced message is saved.

ContextYou can find the .txt or .csv files in the save directory. Double-click a file to read the tracedmessages.

Procedure

Step 1 Select any of the following methods to start the Trace Viewer:

Method1:

On the LMT, select View > Trace Viewer.

Method2: On the LMT, click on the toolbar.

Method3:

Select Start > All Programs > Huawei Local Maintenance Terminal > TraceViewer. The Open dialog box is displayed.

Step 2 Select a file. The default save path for the files is installation directory\client\output\NodeB\LMT software version number\trace.

Step 3 Click Open. The content of the message is displayed in the Trace Viewer window.

Step 4 Browse these messages, or double-click one to view its details.For the function reference of the shortcut menu in the Trace Viewer window, see 9.14.12Interface Reference for Trace Viewer.

Step 5 To review other saved results, choose File > Open. In the Open dialog box, you may select andopen files.

----End

9.14 Interface Reference for Managing the Interface TracingThis section provides parameter descriptions for managing the interface tracings.



94

9.14.1 Interface Reference for IUB TracingThis section describes the interface reference for the standard signaling tracing.

Field Description

ReportMessage Type

All the Iub tracing message types are listed including the NBAP andALCAP messages.Filter out messages of minor significance by clearing the check box beforethe message type.

Auto Save Select Autosave. The messages are automatically saved in the default path,or you can specify the path. Messages are saved one at a time in the messagefile.

9.14.2 Interface Reference for SCTP TracingThis section describes the interface reference for the SCTP tracing.

Field Description

Cabinet No. Indicates the cabinet number of the board of which the SCTP messages aretraced.

Subrack No. Indicates the subrack number of the board of which the SCTP messages aretraced.

Slot No. Indicates the slot number of the board of which the SCTP messages aretraced.

Sctp LinkNo. Indicates the number of the SCTP link to be traced.

Sctp TraceType

This parameter can be set to Packet and Chunk.

Direction This parameter can be set to Receive, Send, and RS.

Autosave When Autosave is selected, the messages are automatically saved in thedefault path. You can also specify another path for saving the reportedmessages.

9.14.3 Interface Reference for IP TracingThis section describes the interface reference for IP tracing.

Field Name Notes

Cabinet No. Cabinet number of the board in which the IP messages aretraced.



95

Field Name Notes

Subrack No. Subrack number of the board in which the IP messages aretraced.

Slot No. Slot number of the board in which the IP messages aretraced.

Direction This can be set to Out, In, or Both.

Protocol This can be set to All, UDP, or SCTP.

Intercept Select This determines whether the message is reported afterintercept selection.This can be set to Intercept Length Appointed orIntercept Length Not Appointed.

Intercept Length This specifies the upper limit intercept length of thereported message.This parameter is valid only when Intercept Select is set toIntercept Length Appointed.Value range: 28 to 1500. Default value: 60.

IP PacketIn Max

JudgementCondition

This specifies the judgment condition on the length of datapacket to be obtained in the NodeB incoming direction.This can be set to Equals ,Less than or All.

Packet Length This specifies the length of the data packet to be obtainedin the NodeB incoming direction.Value range: 0 to 3000. Default value: 1500.

IP PacketOut Max

JudgementCondition

This specifies the judgment condition on the length of datapacket to be obtained in the NodeB outgoing direction.This can be set to Equals ,Less than or All.

Packet Length This specifies the length of the data packet to be obtainedin the NodeB outgoing direction.Value range: 0 to 3000. Default value: 1500.

Local IP Address Local IP address to be traced. The default value is 0, whichmeans that all IP can be traced.

Peer IP Address Peer IP address to be traced. The default value is 0, whichmeans that all IP can be traced.

Autosave Select Autosave, and the reported messages areautomatically saved in the default path. You may alsospecify the path for saving the reported messages.

9.14.4 Interface Reference for ICP TracingThis section describes the interface reference for the ICP tracing.



96

Field Description

CabinetNumber

Cabinet number of the board in which the ICP messages are traced.

SubrackNumber

Subrack number of the board in which the ICP messages are traced.

Slot Number Slot number of the board in which the ICP messages are traced.

Sub-BoardType

E1_COVERBOARDis selected automatically.

IMA GroupNumber

The number of the IMA group.Value range:0~3

Direction Value range:In,OutorBoth

Auto Save Select Autosave, and the reported messages are automatically saved in thedefault path. You may also specify the path for saving the reportedmessages.

9.14.5 Interface Reference for SAAL TracingThis section describes the interface reference for the SAAL tracing.

Field Description

Link Number Indicates the link number of the SAALmessages to be traced.

Trace Message Type This parameter can be set to Select All, ClearAll, and Custom.

Autosave Select Autosave, and the reported messagesare automatically saved in the default path.You may also specify the path for saving thereported messages.

9.14.6 Interface Reference for User TracingThis section describes the interface reference for user tracing.

Table 9-1 describes parameter settings in the Basic tab page.

Table 9-1 Interface reference in the Basic tab page

Field Description

Trace MethodConfiguration

Select CRNCID, Chain Time, or IMSI.



97

Field Description

ParameterConfiguration

Specify the CRNCID if the CRNCID tracing method is selected.

Specify the tracing duration, number of users to be traced, tracing starttime, and tracing end time if the Chain Time tracing method is selected.The tracing duration ranges from 0 to 60 and its default value is 60.The default tracing start time and tracing end time are current time.

Specify the IMSI if the IMSI tracing method is selected.

AutoSave The traced messages are automatically saved in the specified folder ifthis field is selected.

Table 9-2 describes parameter settings in the IUB tab page.

Table 9-2 Interface reference in the IUB tab page

Field Description

Trace item Select items to be traced on the Iub interface.

Parameter Set parameters based on the tracing items of the message type.

Table 9-3 describes parameter settings in the UU tab page.

Table 9-3 Interface reference in the UU tab page

Field Description

Trace Item Select items to be traced on the Uu interface.

Parameter Set parameters based on the tracing items of the message type.

9.14.7 Interface Reference for Cell TracingThis section describes the interface reference for cell tracing.

Field Name Notes

Cell ID The ID of the cell to be traced.

Tracing Type This can be set to Cell or All Uses.

InformationLevel

This can be set to Key Information and Detail Information.



98

Field Name Notes

Autosave Select Autosave to automatically save the tracing results to a specifiedfolder.

9.14.8 Interface Reference for PPP TracingThis section describes the interface reference for the PPP tracing.

Field Description

Cabinet No. The value range is from 0 to 7.

Subrack No. The value range is from 0 to 1.

Slot No. The value range is from 0 to 7.

SubBoardType Indicates the type of the subboard of whichthe PPP messages are traced.

PPP LinkNo. The value range is from 0 to 15.

Direction This parameter can be set to Receive, Send,and RS.

Autosave When Autosave is selected, the messages areautomatically saved in the default path.

9.14.9 Interface Reference for MP TracingThis section describes the interface reference for the MP tracing.

Field Description

Cabinet No. Indicates the cabinet number of the board ofwhich the MP messages are traced.

Subrack No. Indicates the subrack number of the board ofwhich the MP messages are traced.

Slot No. Indicates the slot number of the board ofwhich the MP messages are traced.

SubBoardType E1Boardis selected automatically.

MpGroupNo Indicates the number of the MP group to betraced.

Direction This parameter can be set to Receive, Send,and RS.



99

Field Description

Autosave When Autosave is selected, the messages areautomatically saved in the default path. Youcan also specify another path for saving thereported messages.

9.14.10 Interface Reference for MAC TracingThis section describes the interface reference for the MAC tracing.

Field Name Notes

Cabinet No. Cabinet number of the board in which the MAC messages aretraced.

Subrack No. Subrack number of the board in which the MAC messages aretraced.

Slot No. Slot number of the board in which the MAC messages are traced.

Direction This can be set to Out, In, or Both.

VLAN Tag VLAN Tag can be set to Tagged and Untagged.

VLANID This parameter is valid only when VLAN Tag is set to Tagged.Value range: 1 to 4094.

VLAN Priority This parameter is valid only when VLAN Tag is set to Tagged.VLAN Priority can be set to All, or 0 to 7.

Local MAC Address The format is ##-##-##-##-##-##, and Local MAC Address is notset by default.

Peer MAC Address The format is ##-##-##-##-##-##, and Peer MAC Address is notset by default.

Frame Type Frame Type can be set to All, ARP, RARP, IP, 802.1ag, or802.3ah.

Frame Flow UpperThreshold

This specifies the maximum number of frames allowed to bereported in one second.Value range: 10 to 200. Default value: 10.

Minimum FrameLength

This specifies the minimum length of the frame that can beobtained. The minimum frame length must be shorter than themaximum frame length.Value range: 16 to 1518. Default value: 16.



100

Field Name Notes

Maximum FrameLength

This specifies the maximum length of the frame that can beobtained. The maximum frame length must be longer than theminimum frame length.Value range: 16 to 1518. Default value: 1518.

Intercept Select This specifies whether the message is reported after interceptselection.Intercept Select can be set to Intercept Length Appointed orIntercept Length Not Appointed.

Intercept Length This specifies the intercept length of the reported message.This parameter is valid only when Intercept Select is set toIntercept Length Appointed.Value range: 42 to 1518. Default value: 74. Unit: byte.

Autosave Select this check box to automatically save the tracing results to aspecified folder.

9.14.11 Interface Reference for PTP TracingThis section describes the interface reference for the PTP tracing.

Field Name Notes

Cabinet No. Cabinet number of the board in which the PTPmessages are traced.

Subrack No. Subrack number of the board in which thePTP messages are traced.

Slot No. Slot number of the board in which the PTPmessages are traced.

PTP clock link No. PTP clock link number of the board in whichthe PTP messages are traced.

Autosave Select this check box to automatically savethe tracing results to a specified folder.

9.14.12 Interface Reference for Trace ViewerThis section describes the interface reference for the trace viewer.

Right-click in the Trace Viewer window, the shortcut menu is displayed. Table 9-4 lists thefunction reference.



101

Table 9-4 Interface reference for the shortcut menu

Field Description

Save AllMessages

Messages are saved in .tmf or .txt format.

Save SelectedMessages

Selected messages are saved in .tmf or .txt format.

Select Left Sideto Compare

List the selected messages on the left.

Compare Compare the selected messages. (This is valid only when you select twoor more messages.)

UndoComparison

Cancel the comparison between the selected messages.

Filter Filter the messages according to the field, type, algorithm, and filteringparameters. The filtered messages are not displayed in the browsewindow.

Filter By column Display only the messages in the selected columns.

Undo Filtering Cancel the filtering. Display all messages.

Find Search for messages that satisfy the conditions in terms of type, content,matching mode, and searching direction.

Properties The properties of Trace Viewer. These include save type, file name, username, office name, task type, and creation time of the task.



102

10 Managing NodeB Common Monitoring

About This Chapter

This chapter describes how to monitor the CPU/DSP occupancy of the NodeB. It consists of thefollowing tasks: displaying the CPU/DSP occupancy of the NodeB, browsing and savingmonitoring files. It is useful for reviewing system resources.

10.1 Displaying the NodeB CPU/DSP UsageThis section describes how to display the NodeB CPU/DSP usage. CPU/DSP usage reflects theuse of system resources.

10.2 Saving NodeB Monitoring FilesUsers can save CPU/DSP usage in files to the LMT PC after creating or starting a CPU/DSPusage monitoring task. This section describes how to save NodeB monitoring files.

10.3 Browsing a NodeB CPU/DSP Monitoring File OfflineThis section describes how to use the Monitor Viewer to browse offline monitoring messagessaved in .tmf format.

10.4 Interface Reference for Managing NodeB Common MonitoringThis section describes the interface reference for NodeB common monitoring.

NodeBLMT User Guide 10 Managing NodeB Common Monitoring


103

10.1 Displaying the NodeB CPU/DSP UsageThis section describes how to display the NodeB CPU/DSP usage. CPU/DSP usage reflects theuse of system resources.

Prerequisite

You have logged in to the NodeB LMT.

Context

Results of the CPU usage test are as follows:

l When the NodeB works properly and does not carry any services, the CPU usage of allboards should stay between 5% and 10%.

l When the NodeB carries services, the CPU usage of all boards increases to less than 75%.If the CPU usage increases to more than 75%, the alarm is raised.

l It is normal for the CPU usage to stay at 100% for a few seconds.

l If 100% of CPU usage lasts longer, the CPU may be faulty. For example, the CPU is faultyif usage lasts over one minute even though the NodeB does not carry service.

Procedure

Step 1 In the navigation tree of the Local Maintenance Terminal window, click the Maintenancetab.

Step 2 Double-click Common Monitoring > CPU/DSP Usage. The system displays the CPU/DSPUsage window in the right pane and the Add Task dialog box.

NOTE

The CPU/DSP Usage window consists of two parts. The top part contains two tab pages, displaying themonitoring result in List and Chart. The bottom part of window displays the lists of all monitored tasks.For the detail of the shortcut menu operation in the CPU/DSP Usage window, see 10.4.2 InterfaceReference for CPU/DSP Usage Monitoring.

For the parameter details in the Add Task dialog box, see 10.4.1 Interface Reference forAdding a Monitoring Task.

Step 3 Set the query conditions in the dialog box.

Step 4 Click Add to add a monitored task with the specified query conditions.

Step 5 Click Close to close the Add Task dialog box and return to the CPU/DSP Usage window.CPU/DSP usage is displayed by list and chart.

NOTEFor ease of differentiation, different colors are used to represent different tasks.

Step 6 To end the task, choose one of the following methods:

l Method 1: Directly close the task monitoring window to end all monitoring tasks of the activewindow.



104

l Method 2: Right-click the task in the task list below the graph area and then choose DeleteTask from the shortcut menu.

----End

10.2 Saving NodeB Monitoring FilesUsers can save CPU/DSP usage in files to the LMT PC after creating or starting a CPU/DSPusage monitoring task. This section describes how to save NodeB monitoring files.

Contextl When the current monitoring file exceeds the system limit, a new monitoring file is created.

All files of one monitoring task are associated by indexes. The index value increases as thenumber of new monitoring files grows.

l Default save path: LMT installation directory\client\output\monitor.l Default file name: Cpu Review_YYYY-MM-DD_HH-MM-SS-Index.l The file is automatically saved in .mrf format.

NOTE

l YYYY-MM-DD_HH-MM-SS represents the task creation time. YYYY, MM, DD, HH, MM and SSstand for year, month, day, hour, minute, and second respectively.

l Indexes include multiple monitoring files within a monitoring task. The first file has no index value.The index values of the files (except the first file) start from 1 in an ascending order.

Procedurel To save the monitoring result when the monitoring task is created, perform the following

steps:1. Open the Add Task dialog box.

For the parameter details in the Add Task dialog box, see 10.4.1 Interface Referencefor Adding a Monitoring Task.

2. Select the corresponding Cabinet No.Subrack No. and Slot No.. Then, click Add tocreate a monitoring task.

3. Specify the path for saving monitoring files. The default save path is installationdirectory\client\output\monitor.

4. Click Start Saving to start saving the result in real time.

NOTE

Click Stop Saving to stop the saving.

l To save the monitoring result when the CPU/DSP usage monitoring task is started, performthe following steps:1. Right-click in the task information pane at the bottom of the CPU/DSP Usage

window.

For the detail of other shortcut menu operations in the CPU/DSP Usage window, see10.4.2 Interface Reference for CPU/DSP Usage Monitoring.

2. Select Start Saving Review Data in the displayed shortcut menu to start saving thereal-time results.



105

NOTE

During the saving progress, click Stop Saving Review Data to terminate the saving task.

----End

10.3 Browsing a NodeB CPU/DSP Monitoring File OfflineThis section describes how to use the Monitor Viewer to browse offline monitoring messagessaved in .tmf format.

Prerequisite

Monitoring files are saved.

Procedure

Step 1 Select any of the following methods to start the Monitor Viewer:

l Method 1: On the LMT, select View > Monitor Viewer.

l Method 2: On the LMT, click on the toolbar.

l Method 3: Select Start > All Programs > HUAWEI Local Maintenance Terminal >Monitor Viewer. The Open dialog box is displayed.

Step 2 Select the monitoring file to be browsed in the dialog box.

Step 3 Click Open or double-click the file. The Monitor Viewer window displays the result data inlist or in chart.

Step 4 Click the List tab or the Chart tab to review the information in different modes.

Step 5 To review other saved results, select File > Open. In the Open dialog box, select and open filesto read the monitoring messages that are saved in the files.

----End

10.4 Interface Reference for Managing NodeB CommonMonitoring

This section describes the interface reference for NodeB common monitoring.

10.4.1 Interface Reference for Adding a Monitoring TaskThis section provides the interface reference for adding a monitoring task.

Field Description

Cabinet No. Number of the Cabinet to be monitored:Baseband subrack number, or the Subrack number of the RRU.



106

Field Description

Subrack No. Number of the subrack to be monitored:Baseband subrack number, or the Subrack number of the RRU.

Slot No. Number of the slot to be monitored:The slot number of the RRU, or the board in the basebandsubrack.

Show line graph orhistogram

If this check box is selected, the monitoring results aredisplayed on the chart tab page.

Save Review Data In this area, the monitoring data is saved to an .mrf file.

10.4.2 Interface Reference for CPU/DSP Usage MonitoringThis section describes the parameters used for CPU/DSP usage monitoring.

Right-click on the List tab page in the CPU/DSP Usage window. Then you can perform thefollowing operations through the shortcut menu:l Sets auto scrolll Sets display properties

Right-click on the Chart tab page in the CPU/DSP Usage window. Then you can perform thefollowing operations through the shortcut menu:l Sets auto scrolll Switches the display model Shows or hiding gridl Sets Y axis display range

Right-click in the task information pane at the bottom of the CPU/DSP Usage window. Thenyou can perform the following operations through the shortcut menu:l Adds a taskl Deletes a taskl Starts saving review datal Stops saving review datal Sets display properties



107

11 Managing the NodeB Software

About This Chapter

This chapter describes how to upgrade the NodeB software.

11.1 Overview of the NodeB SoftwareTo add new functions or rectify defects, the NodeB software needs to be upgraded when theNodeB is running.

11.2 Managing the BootROM Software of the NodeBThis section describes how to manage the BootROM software by upgrading the software of allthe boards of the NodeB.

11.3 Upgrading the NodeB SoftwareThis section describes how to upgrade the NodeB software from a previous version to a newversion. Before beginning the upgrade, record details of the previous version and downloadsoftware for the upgrade.

11.4 Managing the NodeB Cold PatchThis section describes how to use the patch package to upgrade a specified board or module onthe NodeB for optimizing a function or clearing a defect. Services on the board are interrupted,as patching results in a board reset.

11.5 Managing the NodeB Hot PatchThis section describes how to manage the hot, or online, patch. The patch clears function defectswithout interrupting system operation.

11.6 Managing the Multi-Version Software of the NodeBThis section describes how to manage the NodeB combined software, permitting the upgrade oftwo or more software versions at one time.

11.7 Interface Reference for Managing NodeB SoftwareThis section provides interface reference for managing the software.

NodeBLMT User Guide 11 Managing the NodeB Software


108

11.1 Overview of the NodeB SoftwareTo add new functions or rectify defects, the NodeB software needs to be upgraded when theNodeB is running.

NodeB Software to Be Upgradedl BootROMl NodeB softwarel Cold patchl Hot patch

Procedure of the NodeB Software UpgradeTo upgrade the software, download the software and activate it.

Resumable Download Supported by the NodeBIf... Then

There is a resumable download task in thesoftware package

The system automatically displays the taskstatus and download progress in the SoftwareUpdate dialog box.

There is no resumable download task Update the software in the SoftwareUpdate dialog box.

Introduction to the NodeB SoftwareSoftware Description

BootROM l The BootROM refers to the software bound with hardware. It providesbasic device functionality, and can be started and updated manually.

l The BootROM is a re-writable storage medium, which is used to storebinary data, that is, the machine codes.

l All the boards on the NodeB are equipped with the BootROM.l The file name of the BootROM is Firmware.csp.

NodeB software The file name of the NodeB software is Software.csp.

Cold patch l The NodeB cold patch is an upgrade to a specific board or module thatimproves functions and resolves problems.

l The file name of the cold patch is SwCPatch.csp.

Hot patch l The hot patch, also known as the online patch, clears function detectswithout disruption to the system.

l The file name of the hot patch is SwHPatch.csp.



109

11.2 Managing the BootROM Software of the NodeBThis section describes how to manage the BootROM software by upgrading the software of allthe boards of the NodeB.

ContextNOTE

l Downloading the BootROM and activating the BootROM are integrated into one step. You canperform the two in one operation.

l The NodeB does not reset after the BootROM is upgraded, nor does it affect services. Therefore, itis unnecessary to manually reset the NodeB or board to make the BootROM software effective afterthe upgrade. The NodeB starts the upgraded BootROM during the next resetting of NodeB or boards.

11.2.1 Downloading the NodeB BootROMThis section describes how to download the NodeB BootROM software from the FTP server tothe temporary directory on the main processing board and then to the related boards.

Prerequisitel The FTP server works properly and is correctly connected to the NodeB in the same intranet.l There is no firewall between the FTP server and the NodeB.l The FTP user can access the specified directory.

Procedure


Step 2 Double-click Software Management > Software Update. The Software Update dialog boxis displayed.For the Software Update dialog box reference, see 11.7.1 Interface Reference for Updatingthe Software.

Step 3 Select Upgrade BootROM in the dialog box.

Step 4 Click Next. The Upgrade BootROM dialog box is displayed.

For the Upgrade BootROM dialog box reference, see 11.7.7 Interface Reference forUpgrading BootROM.

Step 5 Click Modify and set the FTP server in the FTP Setting dialog box.

For the details of the FTP Setting dialog box, see 11.7.11 Interface Reference for Setting FTPServer.

Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade BootROM dialog box isdisplayed.

Step 7 Select Download BootROM Package and then specify a path to download the BootROMpackage.



110

NOTE

l The system downloads the BootROM package and then activates it.

l You can select one step each time and the system proceeds with the task you customize.

Step 8 Click Next. A dialog box is displayed for your confirmation.

Step 9 Click Yes. The Upgrading Patch Progress dialog box is displayed. The status and progress ofthe patch upgrade is displayed in the dialog box. You may check the process by viewing thisdialog box.

----End

11.2.2 Activating the NodeB BootROMThis section describes how to activate the NodeB BootROM. During activation, the mainprocessing board sends update commands to all the boards that successfully download theBootROM software.

Contextl Before the activation, the system checks the BootROM versions of the boards. It activates

the board BootROM only when there is an upgraded BootROM version.l As the BootROM does not affect NodeB services, reset of the NodeB is not required. The

NodeB starts with the upgraded BootROM during next reset.l After the BootROM is activated, the NodeB is not reset.

Procedure



Step 3 Select Upgrade BootROM in the dialog box.

Step 4 Click Next. The Upgrade BootROM dialog box is displayed.

For the Upgrade BootROM dialog box reference, see 11.7.7 Interface Reference forUpgrading BootROM.

Step 5 Select Activate BootROM.

NOTE

l The system downloads the BootROM package and then activates it.

l You can select one step at a time. The system proceeds with the task you customize.



----End



111

11.3 Upgrading the NodeB SoftwareThis section describes how to upgrade the NodeB software from a previous version to a newversion. Before beginning the upgrade, record details of the previous version and downloadsoftware for the upgrade.

Prerequisitel Upgrading BootROM is complete.l The LMT has already been upgraded to the corresponding version to the NodeB software

version.

Contextl If upgrading the NodeB software fails, roll back to the previous software version of

NodeB. The version rollback procedure for the NodeB is the same as that for activating theNodeB software. The difference is that you have to select the software version of theNodeB before the upgraded version.

l The system integrates Backing up the NodeB Data Configuration File, Downloading theNodeB Software, and Activating the NodeB Software into one dialog box. You can selectall three options to perform the three steps in a time.

11.3.1 Downloading the NodeB SoftwareThis section describes how to download the NodeB software from the FTP server to theNodeB. The NodeB file directories are the active directory and the standby directory. The activedirectory saves the running NodeB software version. The standby directory saves the inactiveNodeB software version. After the NodeB software is downloaded, it is saved in the standbydirectory. The NodeB software does not take effect immediately or damage the running software.


Procedure

Step 1 In the navigation tree of the Local Maintenance Terminal window, click the MaintenanceTab.

Step 2 Select Software Management > Software Update. The Software Upgrade dialog box isdisplayed.For the Software Update dialog box reference, see 11.7.1 Interface Reference for Updatingthe Software.

Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed.For the Upgrade NodeB Software dialog box reference, see 11.7.5 Interface Reference forUpgrading NodeB Software.



112

Step 5 Click Modify, and set the FTP server in the FTP Setting dialog box.


Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade NodeB Software dialog boxis displayed.

Step 7 Select Backup Data Configuration File, Download NodeB Software Package, andDownload by Configuration to specify a directory for backing up the file and a directory fordownloading the NodeB software package.

NOTE

l Backup Data Configuration File is optional. It is recommended that you select the option.

l When the configuration and initial configuration changes or the configuration file encounters an error,click Download Data Configuration File to download the data configuration file again. Then, clickEffective Data Configuration File to confirm its validity before activating the NodeB software.

l It is recommended that you select Download by Configuration. If it is not selected, a dialog box isdisplayed to note this may cause the software download to fail. Click OK to start the download of thesoftware. Click Cancel to review selections.

l When downloading by configuration, only required board software packages are downloaded. Thisreduces the total volume of data to be downloaded, shortens the download time, and saves storage spaceon the NodeB.


Step 9 Click Yes. The upgrade progress dialog box is displayed. The status and progress of the patchupgrade is displayed in the dialog box.

----End

11.3.2 Supplying the NodeB SoftwareSupplying the NodeB software means manually downloading the software of the board that isnewly added and is in position.

Prerequisitel The NodeB software package file is already saved in the source path.

l The FTP server works properly and is correctly connected to the NodeB in the same intranet.

l There is no firewall between the FTP server and the NodeB.

l The FTP user can access the specified directory.

Context

When downloading the NodeB software, select Download by Configuration. Then, theNodeB can automatically download the required board software in the case of any change in theNodeB configuration (for example, a board is added) from the following two paths:

l The last download path of the active NodeB software package

l The M2000 server



113

NOTE

After the board software is automatically downloaded, it is automatically activated.If the board software fails to be downloaded automatically, the NodeB reports a Board VersionMismatch alarm, which indicates that you need to manually download the board software. The manuallydownloaded board software is stored in the active directory of the NodeB. Then, you need to run the ACTSOFTWARE command to activate the board software.

Procedure


Step 2 Select Software Management > Software Update. The Software Update dialog box isdisplayed.For the Software Update dialog box reference, see 11.7.1 Interface Reference for Updatingthe Software.

Step 3 Select Supply NodeB Software in the dialog box.

Step 4 Click Next. The Supply NodeB Software dialog box is displayed.

For the Supply NodeB Softwaredialog box reference, see 11.7.2 Interface Reference forSupplying NodeB Software.



Step 6 Click OK. The FTP Setting dialog box is closed and the Supply NodeB Software dialog boxis displayed.

Step 7 Click Browse on the right of Software Directory and specify a directory for downloading thesoftware package.If you have or know the specific path of the NodeB cold patch, select this Supplying PatchSoftware check box and specify the path in the Patch Directory.


Step 9 Click Yes. The status and progress of the process are displayed in the dialog box. You may checkthe process by viewing this dialog box.

----End

11.3.3 Activating the NodeB SoftwareThis section describes how to switch the standby directory to the active one, and then downloadthe NodeB software to each board to validate it. You can activate the NodeB software right afterthe download, or later on. After the activation, the NodeB is reset and services are disrupted.

Procedure


Step 2 Double-click Software Management > Software Update. The Software Update dialog boxis displayed.



114

For the Software Update dialog box reference, see 11.7.1 Interface Reference for Updatingthe Software.

Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed.For the Upgrade NodeB Software dialog box reference, see 11.7.5 Interface Reference forUpgrading NodeB Software.

Step 5 Select Activate NodeB Software and select the NodeB software version to be upgraded in theVersion box.

NOTE

l The Version box is displayed only when Download NodeB Software is not selected.

l When the configuration and initial configuration changes or the configuration file encounters an error,click Download Data Configuration File to download the data configuration file again. Then, clickEffective Data Configuration File to confirm its validity before activating the NodeB software.


Step 7 Click Yes. The Upgrading Patch Progress dialog box is displayed, showing the status andprogress of the patch upgrade.

NOTE

l The NodeB is reset and the new NodeB software version is started when NodeB software is activated.

l Reactivate the NodeB software version in the standby file directory or reinstall the NodeB softwareupon activation failure.

CAUTIONl Resetting of the NodeB will reset all boards, and services will be disrupted. You must restart

the NodeB.l When the multi-mode base station works in co-module mode, resetting the TRX module

interrupts the services of the other mode.l When the multi-mode base station supports co-transmission through ports on a board working

in UMTS mode, resetting the board where ports shared by both modes interrupts the servicesof the other mode.

----End

11.3.4 Activating Board SoftwareThis section describes how to activate the software on a single board or a type of boards. Thetarget version of the software to be activated is the relevant version in the active file directory.

ContextActivate the board software in the following cases:

l A single board or a type of boards fails to be activated during the NodeB software activation.l A single board or a type of boards is added or replaced after the NodeB software activation,

which cause failure in automatic activation.



115

CAUTIONl Activating board software results the board to reset.l When the multi-mode base station works in co-module mode, resetting the TRX module

interrupts the services of the other mode.l When the multi-mode base station supports co-transmission through ports on a board

working in UMTS mode, resetting the board where ports shared by both modes interruptsthe services of the other mode.

ProcedureStep 1 In the navigation tree of the Local Maintenance Terminal window, click the Maintenance

tab.


Step 3 Select Activate Board in the dialog box.

Step 4 Click Next. The Activate Board dialog box is displayed.For the Activate Boarddialog box reference, see 11.7.4 Interface Reference for ActivatingBoard Software

Step 5 In the dialog box, select A type of boards or Single board.NOTE

If you select Single board, you must specify Cabinet No., Subrack No. and Slot No..



----End

11.3.5 Synchronizing Software Versions of the NodeBThis section describes how to synchronize software versions of the NodeB. It refers to the backupof the activated NodeB software and BootROM software in the standby directory after theupgraded NodeB software runs successfully for 2-3 days. In this case, the version in the standbydirectory can be used should the NodeB software and the BootROM software in the activedirectory become faulty.


1. In the navigation pane of the Local Maintenance Terminal window, click theMaintenance tab.

2. Double-click Software Management > Software Update. The Software Updatedialog box is displayed.



116

For the Software Update dialog box reference, see 11.7.1 Interface Reference forUpdating the Software.

3. Select Synchronize Version in the dialog box.

4. Click Next. The Synchronize Version dialog box is displayed.For the Synchronize Versiondialog box reference, see11.7.3 Interface Referencefor Synchronizing Version

5. Click Next. A dialog box is displayed for your confirmation.

6. Click Yes. The Synchronizing Version Progress dialog box is displayed, showingthe status and progress of synchronization.

l MML mode:

Run the command SYN SOFTWARE.

----End

11.4 Managing the NodeB Cold PatchThis section describes how to use the patch package to upgrade a specified board or module onthe NodeB for optimizing a function or clearing a defect. Services on the board are interrupted,as patching results in a board reset.

11.4.1 Downloading the NodeB Cold PatchThis section describes how to download a patch package from the FTP server to the NodeB. Thepatch package is stored in the standby file directory of the NodeB.

Prerequisitel The FTP server works properly and is correctly connected to the NodeB in the same intranet.

l There is no firewall between the FTP server and the NodeB.

l The FTP user can access the specified directory.

Procedure

Step 1 In the navigation pane of the Local Maintenance Terminal window, click the Maintenancetab.


Step 3 Select Upgrade Patch in the dialog box.

Step 4 Click Next. The Upgrade Patch dialog box is displayed.

For the Upgrade Patch dialog box reference, see 11.7.8 Interface Reference for UpgradingPatch.




117


Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade Patch dialog box is displayed.

Step 7 Select Download Patch Software Package to specify a directory for downloading the patchpackage.

NOTE

The system downloads the patch package and then activates it.



----End

11.4.2 Supplying the NodeB Cold PatchThis section describes how to supply the NodeB software. Supplying the NodeB software meansmanually downloading the software of the board that is newly added and is in position.

Prerequisitel The running software version of NodeB is the cold patch version.l The FTP server works properly and is connected to the NodeB in the same intranet.l There is no firewall between the FTP server and the NodeB.l The FTP user can access the specified directory.

ContextBy default, the NodeB cold patch is downloaded by configuration. If the NodeB configurationchanges (for example, a new board is added), the NodeB download the required board softwareand cold patch software from the last default download path.

NOTE

After the board software and cold patch software are automatically downloaded, they take effect immediatelywithout being activated. If the automatic downloading fails, the NodeB reports the Board Software Auto-SupplyFailure alarm for you to manually download the board software and cold patch software. Then you can supplythe NodeB software by downloading the available new board software. After the software is automaticallydownloaded, perform 11.3.4 Activating Board Software to validate the software.

Procedure

Step 1 In the navigation pane, click the Maintenance Tab.

Step 2 Double-click Software Management > Software Update. The Software Update dialog boxis displayed.

Step 3 Select Supply NodeB Software.

Step 4 Click Next. The Supply NodeB Software dialog box is displayed.

Table 11-1 describes the fields in the Supply NodeB Software dialog box.



118

Table 11-1 Fields in the Supply NodeB Software dialog box

Field Name Notes

FTP Setting This enables you to set the FTP server for downloading theNodeB software and cold patch software.Click Modify on the right to set the FTP server.

Software Directory This specifies the path that stores the NodeB software package.Click Browse and select a directory for the software package.

Patch Directory This specifies the path that stores the NodeB cold patch.Click Browse and select a directory for the cold patch.

Step 5 The FTP server is set up on the M2000.1. Click Modify. In the FTP Setting dialog box, set the FTP server.

For the details of the FTP Setting dialog box, see 11.7.11 Interface Reference for SettingFTP Server.

2. Click OK.

Step 6 Specify a path to download the software package. Click Browse on the right and select a directoryfor the software package.

Step 7 Select Supplying Patch Software.

Step 8 Specify a path to download the cold patch software package. Click Browse on the right andselect a directory for the cold patch software package.



----End

11.4.3 Activating NodeB Cold PatchThis section describes how to activate the NodeB cold patch. Activating the NodeB cold patchmeans downloading the patch in the standby file directory to the target board and updating thepatch version of the target board.



119

Context

CAUTIONl Activating cold patch leads to the reset of the related board. Therefore, services on that board

are disrupted.

l When the multi-mode base station works in co-module mode, resetting the TRX moduleinterrupts the services of the other mode.

l When the multi-mode base station supports co-transmission through ports on a board workingin UMTS mode, resetting the board where ports shared by both modes interrupts the servicesof the other mode.

Procedure






Step 5 Select Activate Patch.

NOTE




NOTE

If the activation of a board fails, locate the problem. After the fault is cleared, the cold patch is automaticallyloaded to the board.

----End

11.4.4 Downloading the Cold Patch for the NodeB BootROMThis section describes how to download the cold patch for the NodeB BootROM from the FTPserver to the NodeB. The patch package is saved in the standby file directory of the NodeB.



120


Procedure








Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade Patch dialog box is displayed.

Step 7 Select Download Patch Software Package to specify a directory for downloading the patchpackage.

NOTE

l The system downloads the patch package and then activates it.

l If you select Download by Configuration, all the board software required according to the currentNodeB configuration is downloaded.



----End

11.4.5 Activating the Cold Patch for the NodeB BootROMThis section describes how to activate the cold patch for the NodeB BootROM. Activating thecold patch for the NodeB BootROM means downloading the BootROM patch that is saved inthe NodeB patch area to the target board and updating the patch version of the target board.

Prerequisitel You have logged in to the NodeB LMT.l The cold patch for the BootROM is downloaded.



121

ContextThe cold patch for the BootROM is downloaded and saved in the board memory. Therefore, youneed to download the patch and activate it after the board is reset.

Procedure






Step 5 Select Activate Patch.

NOTE



Step 7 Click Yes. The status and progress of the procedure are displayed in the Interface of Indicatingthe Status and the Progress. You can check the procedure by viewing this dialog box.

----End

11.5 Managing the NodeB Hot PatchThis section describes how to manage the hot, or online, patch. The patch clears function defectswithout interrupting system operation.

11.5.1 Downloading the NodeB Hot PatchThis section describes how to download a patch package from the FTP server to the NodeB.


Procedure




122


Step 3 Select Upgrade NodeB Hot Patch in the dialog box.

Step 4 Click Next. The Upgrade NodeB Hot Patch dialog box is displayed.

For the Upgrade NodeB Hot Patch dialog box reference, see 11.7.9 Interface Reference forUpgrading NodeB Hot Patch.

Step 5 Click Modify in the dialog box, and set the FTP server in the FTP Setting dialog box.


Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade NodeB Hot Patch dialogbox is displayed.

Step 7 Select Upgrade NodeB Hot Patch to specify a directory for downloading the hot patch package.

NOTE

The above steps are performed in order to: Download Hot Patch Software Package, Activate Hot Patch,and then Confirm Hot Patch.



----End

11.5.2 Activating the NodeB Hot PatchThis section describes how to activate the NodeB hot patch. Activating the NodeB hot patchmeans downloading the patch in the standby file directory on the main controlling board to thetarget board and updating the patch version of the target board.

Procedure






Step 5 Select Activate Hot Patch.



123

NOTE

The steps above are performed in order: download hot patch software package, activate hot patch, and thenconfirm hot patch.



NOTE

If the activation of a board fails, locate the problem and then activate the hot patch of that board again.

----End

11.5.3 Confirming the NodeB Hot PatchThis section describes how to confirm the NodeB hot patch. The activated NodeB hot patchrunning on the board is still in trial state. After a period of trial running, you can confirm theNodeB hot patch to enable its stable running if the patch is running properly.

Procedure






Step 5 Select Confirm Hot Patch.

NOTE

The steps above are performed in order: download hot patch software package, activate hot patch, and thenconfirm hot patch.



NOTE

If the confirmation of a board fails, locate the problem and then confirm the hot patch of that board again.

After confirming the NodeB hot patch, you cannot deactivate the hot patches.

----End



124

11.5.4 Deactivating the NodeB Hot PatchThis section describes how to deactivate the NodeB hot patch. The activated NodeB hot patchrunning on the board is still in trial state. After a period of trial running, you can deactivate theNodeB hot patch to stop the trial running if an exception occurs.

Procedure




Step 4 Click Next. The Upgrade NodeB Hot Patch dialog box is displayed.For the Upgrade NodeB Hot Patch dialog box reference, see 11.7.9 Interface Reference forUpgrading NodeB Hot Patch.

Step 5 Select Deactivate Hot Patch.



NOTE

If the deactivation of a board fails, locate the problem and then deactivate the hot patch of that board again.

----End

11.5.5 Removing the NodeB Hot PatchThis section describes how to remove the NodeB hot patch that is deactivated, activated, orrunning.

ContextAfter the hot patch is removed, the NodeB hot patch file is removed from the standby directoryand active directory. You need to download the hot patch again to perform such operations asactivating the patch.

Procedure





125



Step 5 Select Remove Hot Patch.



NOTE

If you cannot remove the boards, locate the problem and then try to remove the hot patch of that boardagain.

----End

11.5.6 Rolling Back the NodeB Hot PatchThis section describes how to roll back the NodeB hot patch. Rolling back the hot patch meansrecovering the status of the activated hot patch before the latest loading.

Procedure





Step 5 Select Roll Back Hot Patch.


Step 7 Click Yes. A dialog box is displayed, showing the status and progress of the patch rollback.Check whether the operation is successfully complete.

NOTE

l When you perform the rollback operation, the currently used hot patch stops running and the lastactivated version comes into use again. In addition, the reused hot patch should keep the state (activeor running) the same as that before the last upgrade.

l If no hot patch is activated on the network element before, perform the rollback operation to delete thecurrently used hot patch.

l The hot patch can be rolled back only once.

----End



126

11.6 Managing the Multi-Version Software of the NodeBThis section describes how to manage the NodeB combined software, permitting the upgrade oftwo or more software versions at one time.

ContextThe upgrading multi-version software of the NodeB is applied in the case of upgrading two ormore than two software versions at a time. The upgrading of multi-version software can beapplied in the following scenarios:

Serial No. Multi-version software upgrade

1 NodeB software + Cold patch software

2 NodeB software + Hot patch software

3 Cold patch software + Hot patch software

4 NodeB software + Cold patch software + Hot patch software

The downloading and activating of multi-version software can be performed independently. Theactivation of software may lead to the NodeB resetting and service interruption. You candownload the software in daytime, and activate the software in a time with least traffic at night.

CAUTIONThe upgrade of the multi-version software can be performed when the versions of the NodeBsoftware, cold path software, and hot patch software are matching with each other. Otherwise,error information The selected software version cannot be used together is displayed.

11.6.1 Downloading the Multi-Version Software of the NodeBThis section describes how to download the multi-version software of the NodeB, which refersto download the NodeB software, cold patch software, or hot patch software to be upgradedfrom the FTP server to the standby directory of the NodeB file.

Prerequisitel The FTP server works properly and is connected to the NodeB in the same intranet.l There is no firewall between the FTP server and the NodeB.l The FTP user can access the specified directory.



127

Context

CAUTIONThe multi-version software can be downloaded when the version of the NodeB software, coldpath software, and hot patch software are matching with each other. Otherwise, error informationThe selected software version cannot be used together is displayed.

Procedure



Step 3 Select Upgrade multi-version software in the dialog box.

Step 4 Click Next. The Upgrade multi-version software dialog box is displayed.For the parameter details in the Upgrade multi-version software dialog box, see 11.7.10Interface Reference for Upgrading Multi-Version Software.

Step 5 Set the FTP server.1. Click Modify. In the FTP Setting dialog box, set the FTP server.

For the details of the FTP Setting dialog box, see 11.7.11 Interface Reference for SettingFTP Server.

2. Click OK to complete the FTP sever setup, and return to the Upgrade multi-versionsoftware dialog box.

Step 6 Specify the corresponding software path according to the actual requirement of the multi-versionsoftware to be upgraded. Click Browse on the right and select a directory for the correspondingsoftware package.



----End

11.6.2 Activating the Multi-Version Software of the NodeBThis section describes how to switch the multi-version software of the standby directory to theactive one, and then download the multi-version software to each board and validate it. Afterthe activation, the NodeB is reset and all the services are disrupted.

PrerequisiteThe multi-version software of the NodeB is downloaded.



128

Procedure

Step 1 Click the Maintenance tab in the navigation tree.


Step 3 Select Upgrade multi-version software in the dialog box.

Step 4 Click Next. The Upgrade multi-version software dialog box is displayed.For the parameter details in the Upgrade multi-version software dialog box, see 11.7.10Interface Reference for Upgrading Multi-Version Software.

Step 5 Select Act Multi-Version software in the dialog box.



NOTE

l The NodeB is reset and the new NodeB software version is started when the multi-version softwareNodeB is activated.

l If the software activation fails, the NodeB software cannot operate properly. Roll back to the previoussoftware version according to the actual requirement.

CAUTIONl Resetting the NodeB leads to the resetting of all the boards in the NodeB. At the same time,

the services carried by the NodeB are disrupted. The NodeB needs to be restarted.

l When the multi-mode base station works in co-module mode, resetting the TRX moduleinterrupts the services of the other mode.

l When the multi-mode base station supports co-transmission through ports on a board workingin UMTS mode, resetting the board where ports shared by both modes interrupts the servicesof the other mode.

----End

11.7 Interface Reference for Managing NodeB SoftwareThis section provides interface reference for managing the software.

11.7.1 Interface Reference for Updating the SoftwareThis section describes the interface reference for Software Update window.



129

Field Name Notes

Upgrading BootROM software Upgrading BootROM software includesdownloading and activating BootROMsoftware package.This task includes the main operations inupgrading BootROM software.

Upgrading NodeB software Upgrading NodeB software includes backingup data configuration files, downloading andactivating NodeB software package.This task includes the main operations inupgrading NodeB software.

Supply NodeB Software Upgrading some boards' software includesdownloading and activating the boards'software.

Upgrading patch Upgrading patch includes downloading andactivating patch software package.This task includes all operations in upgradingpatch.

Upgrading hot patch of NodeB Upgrading hot patch of NodeB includesupgrading, deactivating, removing hot patch,and rolling back hot patch.This task includes all operations in upgradingBootROM software.

Upgrading multi-version software Upgrading multi-version software includesdownloading the software package, coldpatch software package, and hot patchsoftware package of the matching version,and activating this version.This task includes the operation in upgradingthe basic software version of the NodeB andthe basic software patch version of the NodeBat a time.

Synchronize software This enables you to back up the version of theupgraded NodeB software that runs properlyfor a period. This operation is regarded as thelast step during the whole NodeB softwareupgrade procedure.

Activate board This enables you to activate the boardsoftware and the related BootROM software.

11.7.2 Interface Reference for Supplying NodeB SoftwareThis section describes the interface reference for Supplying NodeB Software dialog box.



130

Field Name Notes

FTP Setting This enables you to set the FTP server for downloading theNodeB software and cold patch software.Click Modify on the right to set the FTP server.

Software Directory This specifies the path that stores the NodeB software package.Click Browse and select a directory for the software package.

Supplying Patch Software If you have or know the specific path of the NodeB cold patch,select this check box and specify the path in the PatchDirectory.

Patch Directory This specifies the path that stores the NodeB cold patch.Click Browse and select a directory for the cold patch.

11.7.3 Interface Reference for Synchronizing VersionThis section describes the interface reference for Synchronizing Version dialog box.

If... Then...

The synchronization status isSynchronizing or Synchronized,

The operation is complete.

The synchronization status is NotSynchronized,

Click Next.

11.7.4 Interface Reference for Activating Board SoftwareThis section describes the interface reference for activating board software.

Field Description

ActivateSoftware

A type ofboards

Select this option to activate software for a type of boards at atime.Select the type of boards to be activated from the Board typedrop-down list.

Singleboard

Select this option to activate software for a single board at atime.Specify Cabinet No., Subrack No., and Slot No..

11.7.5 Interface Reference for Upgrading NodeB SoftwareThis section provides the interface reference for upgrading the NodeB software.



131

Field Description

FTP Setting This enables you to set the FTP server for downloading the NodeBsoftware.The FTP server that is in use is shown in the box for your reference.The FTP server can be a built-in server or a user-specified server.To set the FTP server, click Modify on the right side of the element.

BackUp DataConfiguration File

This enables you to upload the configuration file from the NodeB tothe FTP server.To specify a path for the file upload, click Browse under Backup DataConfiguration File.Select the path to back up the active data configuration file of theNodeB.If you have already backed up the file, you can skip this step.In case of upgrade failure, you can reload the backup configurationfile in the FTP server to guarantee stable operation of the NodeB.

Downloading theData ConfigurationFile

This enables you to download the data configuration file from theserver to the NodeB and overwrite the previous data configurationfile.To specify a path for the downloading data configuration file, clickBrowse.This operation is optional. The data configuration file has a fixedname of NodeBCfg.xml. Therefore, you only need to specify the pathin which the file would be saved.

Download NodeBSoftware Package

This enables you to download the NodeB software package from theFTP server to the NodeB standby directory. Performing this operationdoes not affect the NodeB operation.Click Browse under Download NodeB Software Package. Select thedirectory of the package in the FTP server.The system will start the download after backing up the configurationfile.This operation is mandatory for the NodeB software upgrade. TheNodeB software package has a fixed name of NodeB.pck. Therefore,you only need to specify the path in which the file would be saved.

Download byConfiguration

When downloading by configuration, only required board softwarepackages are downloaded. This reduces the total volume of data to bedownloaded, shortens the download time, and saves storage space onthe NodeB.This step is optional. By selecting Download by Configuration, youcan download the required board software of the boards in positionaccording to the current NodeB configuration. Otherwise, all theboard software will be downloaded.By default, the check box is selected.

Effective DataConfiguration File

By selecting Effective Data Configuration File, you can make thedownloaded data configuration file take effect.



132

Field Description

Activate NodeBSoftware

This enables you to download the unpacked software package in theNodeB standby directory to each board, and then activate the package.You must reset the NodeB after conducting this operation. If youselect Activate NodeB Software, the NodeB software will beactivated right after the NodeB software package is downloaded.l If you select both Download NodeB Software Package and

Activate NodeB Software, the software to be activated is theNodeB software package downloaded from the FTP server. Youneed not to select the version.

l If you select Activate NodeB Software without selectingDownload NodeB Software Package, the system will list all theNodeB software versions. Select the version to be activated in theactive and standby directories from the Version drop-down list.

11.7.6 Interface Reference for Status Description and ProgressIndicator

This section describes the interface reference for status description and progress indicator.

Field Description

Previous This button is enabled only after completing the task or the task is stoppedby the user.Click this button to return to previous interface for task settings.

Return toDirectory

This button is available only after the task to be completed in this page iscompleted or the user stops the task.Click this button to return to the software update window.

Cancel When the LMT is downloading a software package (NodeB softwarepackage or BootROM software package), click this button to stop thedownloading.When the LMT is activating or backing up data configuration files, thebutton changes to Close. Clicking this button leads to exit from the softwareupgrading, but the activating or the backing up continues.

View DetailedInformation

This operation is available only after the activation is successful.Click this button to view detailed activation result. The displayed resultincludes the boards that have activated successfully or failed to activate.The boards in the failure board list must be activated again. You must checkthe causes to failure and activate these failed boards again.



133

NOTE

l The task result of the software upgrade interface is depends on your settings. The running status andprogress indicator are displayed only when you start a task.

l By clicking Cancel button while downloading, the system returns a failure code of 75. Thedownloading task is eliminated and the button changes to Close. When you click this Close button,the dialog box is closed.

11.7.7 Interface Reference for Upgrading BootROMThis section describes the interface reference for upgrading BootROM.

Field Description

FTP Setting This enables you to set the FTP server for uploading and downloadingBootROM software package. The FTP server in use is shown in the box foryour reference. It can be a built-in server or a user-specified server. ClickModify on the right to set the FTP server.

DownloadBootROMPackage

This enables you to download the BootROM software package from theFTP server to the temporary directory on the NodeB main processing boardand then to the related boards. It does not affect the running of the NodeB.Click Browse to locate the directory of the BootROM software package inthe FTP server. Select this check box to download the BootROM softwarepackage. This operation is mandatory for the BootROM upgrade. Becausethe BootROM software package has a fixed file name of NBRom.pck, youonly need to specify the path of it.

ActivateBootROM

This enables you to activate the BootROM software right after theBootROM software package is downloaded. The BootROM softwareversion to be activated is the version of the BootROM software packagedownloaded to the boards.

11.7.8 Interface Reference for Upgrading PatchThis section describes the interface reference for upgrading patches.

Field Description

FTP Setting This enables you to set the FTP server for downloading the patch. TheFTP server in use is shown in the box for your reference. It can be a built-in server or a user-specified server. Click Modify on the right to set theFTP server.

Patch Type This enables you to select one from the following patch types for theupgrade: Software or BootROM.



134

Field Description

Download PatchSoftwarePackage

This enables you to download the patch package from the FTP server tothe NodeB standby file directory. This does not affect the running of theNodeB. To locate the path of the package in the FTP server, clickBrowse. Select this check box to download the patch package. Thisoperation is mandatory for the patch upgrade. The patch package has afixed file name, which is NBPatch.pck. Therefore, you only need tospecify its path.

Activate Patch This enables you to activate the patch right after the patch package isdownloaded.

11.7.9 Interface Reference for Upgrading NodeB Hot PatchThis section describes the interface reference for upgrading NodeB hot patch.

Field Description

FTP Setting This enables you to set the FTP server for downloading the hot patch.The FTP server in use is shown in the box for your reference. It can be abuilt-in server or a user-specified server.Click Modify on the right to set the FTP server.

Download HotPatch SoftwarePackage

This enables you to download hot patch package from the FTP server tothe temporary hot patch file directory on the WMPT. Performing thisoperation does not affect the NodeB operation.To locate the path of the hot patch package in the FTP server, clickBrowse.Select this check box to download the hot patch package. This operationis mandatory for the hot patch upgrade.Because the hot patch package has a fixed file name of NBHPatch.pck,you only need to specify the path of it.

Activate HotPatch

This enables you to activate the hot patch right after the patch package isdownloaded. After the activation, the patch works in trial running state.

Confirm HotPatch

This enables you to confirm the hot patch software when the hot patchactivation is complete. After the confirmation, the hot patch software runsproperly.

Deactivate HotPatch

Select this check box to deactivate the hot patch that is already effective.

Remove HotPatch

Select this option to remove the hot patch that already runs.

Back Patch Select this check box to roll back the current hot patch and recover thestatus of the activated hot patch before the latest loading.



135

11.7.10 Interface Reference for Upgrading Multi-Version SoftwareThis section describes the interface reference for upgrading multi-version software.

Field Name Notes

FTP Setting This enables you to set the FTP server fordownloading NodeB software.The FTP server that is in use is shown in thebox for your reference. The FTP server canbe a built-in server or a user-specified server.Click Modify on the right to set the FTPserver.

Download Multi-Version Software This enables you to download the specifiedmulti-version software package to thestandby directory of the NodeB.

Software Version This parameter needs to be set when theNodeB software package is included in themulti-version software package to bedownloaded.Click Browse, and select the directory of theNodeB software package.

Cold Patch This parameter needs to be set when the coldpatch software package is included in themulti-version software package to bedownloaded.Click Browse, and select the directory of thecold patch software package.

Hot Patch This parameter needs to be set when the hotpatch software package is included in themulti-version software package to bedownloaded.Click Browse, and select the directory of thehot patch software package.

Act Multi-Version software This enables you to activate the downloadedmulti-version software package at a time.This operation leads to the resetting ofNodeB.

NOTE

The multi-version software can be downloaded when the versions of Software Version, Cold Patch, andHot Patch software are matching with each other.

11.7.11 Interface Reference for Setting FTP ServerThis section describes the interface reference for FTP Setting dialog box.



136

Field Description

Use Built-in FTP Server This enables you to decide whether to use a built-in ora specified FTP server. The built-in FTP server isstarted by default.

Use Specified FTPServer

IP address The FTP server can be started either from the localcomputer installed with the LMT application or fromanother computer. Here it refers to the IP address ofthe FTP server.

User Name This enables you to specify the user name for loggingin to the FTP server.

Password This enables you to specify the password for loggingin to the FTP server.



137

12 Managing NodeB Files

About This Chapter

This chapter describes how to download and back up the NodeB data configuration file, andhow to upload NodeB log files and the device archive file.

12.1 Concepts of NodeB File ManagementThis section describes file types of the NodeB and where to obtain the files.

12.2 Managing the NodeB Data Configuration FilesThis section describes how to download and back up the data configuration files of theNodeB.

12.3 Uploading NodeB Files to the FTP ServerThis section describes how to upload the NodeB files to the FTP server. After the NodeB filesare uploaded, you can save, browse, and modify the files.

12.4 Downloading the NodeB Extral Configuration FileThis section describes how to download the NodeB extral configuration file from the FTP serverto the NodeB. The downloaded extral configuration files take effect after activating.

12.5 Interface Reference for Managing the NodeB FileThis section describes the interface reference for managing the NodeB file.

NodeBLMT User Guide 12 Managing NodeB Files


138

12.1 Concepts of NodeB File ManagementThis section describes file types of the NodeB and where to obtain the files.

12.1.1 File Types of the NodeBThis section describes NodeB file types and operations supported by the types.

One-Click LogA one-click log consists of all types of log saved on a board, including the running log, cell log,operation log, call log, and debugging log.

The one-click log is in binary format and can be uploaded to the FTP server.

Security LogA security log records information about security-related events such as login and logout.

The security log is in binary format and can be uploaded to the FTP server.

Running LogA running log records key events happening when the system is running, for example, boardstarting.

The running log file is in binary format and can be uploaded to the FTP server.

Operation LogAn operation log records information about operations on and maintenance of NodeB.

The operation log is in txt format and can be uploaded to the FTP server.

Configuration Failure LogA configuration log records configuration information about each parameter. A configurationfailure log records a failed upgrade.

The configuration failure log is in binary format and can be uploaded to the FTP server.

Failure LogA fault log records key information about system failures such as system breakdown.

The failure log file is in binary format and can be uploaded to the FTP server.

Configuration LogA configuration log records configuration information about each parameter running on thesystem.

The configuration log is in binary format and can be uploaded to the FTP server.



139

Canbus LogA controller area network BUS (Canbus) log file records information about maintenance andfault alarms of boards, which facilitates fault location and troubleshooting.

The Canbus log is in txt format and can be uploaded to the FTP server.

Alarm LogAn alarm log records detailed information about alarms reported by the system.

The alarm log file is in binary format and can be uploaded to the FTP server.

Internal Fault LogAn internal fault log records system fault information within the system.

The fault log file is in binary format and can be uploaded to the FTP server.

Local Fault LogA local fault log records detailed information board faults at the board.

The fault log file is in binary format and can be uploaded to the FTP server.

Test Result LogA test result log records results of tests performed by users.

The test result log is in binary format and can be uploaded to the FTP server.

Transmission Quality Report LogA transmission quality report log records information about system transmission quality.

The transmission quality report log is in binary format and can be uploaded to the FTP server.

Debugging LogA debugging log records all types of failure information and other key information during systemoperation.

The debugging log is in binary format and can be uploaded to the FTP server.

BSP Health Check LogA board support package (BSP) health check log records the result reports of health checks onall types of hardware components that is performed by the BSP.

The BSP health check log is in binary format and can be uploaded to the FTP server.

DSP Memory LogA digital signal processor (DSP) memory log records the mirror image of DSP memory whenthe DSP in a board fails to work.

The DSP memory log is in binary format and can be uploaded to the FTP server.



140

DSP Log

A DSP log records information when the DSP in a board is running.

The DSP log is in binary format and can be uploaded to the FTP server.

RTWP Routine Test Log

A Received Total Wideband Power (RTWP) routine test log records the corresponding RTWPinformation after the routine test is started.

The RTWP routine test log is in binary format and can be uploaded to the FTP server.

BSP Log

A BSP log records all types of failure information and other key information during BSPoperation.

The BSP log is in binary format and can be uploaded to the FTP server.

Serial Port Redirection Log

A serial port redirection log records information about serial port output of a board after theboard is disconnected from the main control board.

The serial port redirection log is in binary format and can be uploaded to the FTP server.

Board Replacement Log

A board replacement log records electronic labels of NodeB boards that were and are in use.

The Board Replacement Log is in binary format and can be uploaded to the FTP server.

Temperature Log

A temperature log records temperature of each board collected periodically.

A temperature log is in binary format and can be uploaded to the FTP server.

12.1.2 Obtaining NodeB FilesThis section describes how to obtain NodeB files for browsing.

You can obtain and browse the files in either of the following ways:

l Browse the files by logging in to the FTP server after uploading the files to the server.l Browse the operation log on the M2000.

12.2 Managing the NodeB Data Configuration FilesThis section describes how to download and back up the data configuration files of theNodeB.



141

12.2.1 Downloading the NodeB Data Configuration FileThis section describes how to download the NodeB data configuration file from the FTP serverto the NodeB. The downloaded data configuration files take effect after the NodeB is reset.

Procedurel GUI mode

1. In the navigation pane, click the Maintenance tab.2. Double-click Software Management > Data Config File Transfer. The Data

Config File Transfer dialog box is displayed.For the parameter details in the Data Config File Transfer dialog box, see 12.5.1Interface Reference for Data Configure File Transfer.

3. Select the Download (FTP Server to NodeB).4. Click Modify in the dialog box. The FTP Setting dialog box is displayed.

Table 12-1 describes the fields in the FTP Setting dialog box.

Table 12-1 Fields in the FTP Setting dialog box

Field Description

Use Built-in FTP Server Enables you to decide whether to use a built-inor a specified FTP server. The built-in FTPserver is started by default.


IP address The FTP server can be started either from thelocal computer installed with the LMTapplication or from another computer. Here itrefers to the IP address of the FTP server.

UserName

Enables you to specify the user name forlogging in to the FTP server.

Password Enables you to specify the password forlogging in to the FTP server.

5. Set the FTP server.6. Click OK. The FTP Setting dialog box is closed.7. Set the other corresponding parameters in the Data Config File Transfer dialog box.8. Click Start.

l MML mode

Run the command DLD CFGFILE.

----End

12.2.2 Backing up the NodeB Data Configuration FileThis section describes how to back up the NodeB data configuration file. Backing up theNodeB data configuration file means uploading the data configuration file from the NodeB tothe FTP server, where you can browse the data anytime.



142

Procedurel GUI mode

1. In the navigation pane, click the Maintenance tab.2. Double-click Software Management > Data Config File Transfer. The Data

Config File Transfer dialog box is displayed.For the parameter details in the Data Config File Transfer dialog box, see 12.5.1Interface Reference for Data Configure File Transfer.

3. Select the Upload (NodeB to FTP server).4. Click Modify in the dialog box. The FTP Setting dialog box is displayed.



Field Description

Use Built-in FTP Server Enables you to decide whether to use a built-inor a specified FTP server. The built-in FTP serveris started by default.


IPaddress

The FTP server can be started either from thelocal computer installed with the LMTapplication or from another computer. Here itrefers to the IP address of the FTP server.

UserName

Enables you to specify the user name for loggingin to the FTP server.

Password

Enables you to specify the password for loggingin to the FTP server.

5. Set the FTP server.6. Click OK. The FTP Setting dialog box is closed.7. Set the other corresponding parameters in the Data Config File Transfer dialog box.8. Click Start.

l MML mode

Run the command ULD CFGFILE.

----End

12.3 Uploading NodeB Files to the FTP ServerThis section describes how to upload the NodeB files to the FTP server. After the NodeB filesare uploaded, you can save, browse, and modify the files.

12.3.1 Uploading the NodeB Log File to the FTP ServerThis section describes how to upload a NodeB log file to the FTP server.



143

Prerequisitel The FTP server works properly and is correctly connected to the NodeB in the same intranet.l There is no firewall between the FTP server and the NodeB.l The user name and password for the specified FTP server are correct and ensure that you

have the permission to read the data in the specified directory.



2. Double-click Software Management > Other File Transfer. The Other FileTransfer dialog box is displayed.For the parameter details in the Other File Transfer dialog box, see 12.5.3 InterfaceReference for Transferring Other Files.

3. Select the log file type from the File Description drop-down list.4. Click Modify. The FTP Setting dialog box is displayed.



Field Description

Use Built-in FTP Server Enables you to decide whether to use a built-in ora specified FTP server. The built-in FTP server isstarted by default.


IPaddress

The FTP server can be started either from the localcomputer installed with the LMT application orfrom another computer. Here it refers to the IPaddress of the FTP server.

UserName

Enables you to specify the user name for loggingin to the FTP server.

Password


5. Set the FTP server.6. Click OK. The FTP Setting dialog box is closed and the Other File Transfer dialog

box is displayed.7. Set the other parameters in the dialog box.8. Click Start.

NOTE

After the upload is complete, detailed information of the successful or failed uploading file isavailable from the subsequent dialog box. For details, see 12.5.4 Interface Reference forDetailed Information About Successful and Failed Files.

l MML mode



144

Run the command ULD FILE.

----End

12.3.2 Uploading NodeB Device Archive FileThis section describes how to upload a NodeB device archive file to the FTP server.

Prerequisitel The FTP server works properly and is correctly connected to the NodeB in the same intranet.l There is no firewall between the FTP server and the NodeB.l The user name and password for logging in to the specified FTP server are correct. Ensure

that you have the permission to read the data in the specified directory.

ContextThe default name of the NodeB device archive file is NodeBDevFile.xml.

Procedurel GUI mode

1. In the navigation pane, click the Maintenance tab.2. Double-click Software Management > Device Archives Transfer. The Device

Archives Transfer dialog box is displayed.For the parameter details in the Device Archives Transfer dialog box, see 12.5.2Interface Reference for Device Archives Transfer.

3. In the Transfer Type area, select both Export Device File and Upload Device Fileand then click Start. The device archive file is generated and then uploaded.

NOTE

If you only want to upload the generated device archive file, select only Upload Device File.

4. Click Browse and specify the directory for saving the device archive file.5. Click Modify. The FTP Setting dialog box is displayed.



Field Description

Use Built-in FTP Server Enables you to decide whether to use a built-inor a specified FTP server. The built-in FTPserver is started by default.


IPaddress

The FTP server can be started either from thelocal computer installed with the LMTapplication or from another computer. Here itrefers to the IP address of the FTP server.

UserName

Enables you to specify the user name forlogging in to the FTP server.



145

Field Description

Password


6. Set the FTP server.

7. Click OK. The FTP Setting dialog box is closed, and the Device ArchivesTransfer dialog box is displayed.

8. Click Start.

l MML mode

1. Run the command EXP DEVFILE to export archive file.

2. Run the command ULD DEVFILE to upload archive file.

----End

12.4 Downloading the NodeB Extral Configuration FileThis section describes how to download the NodeB extral configuration file from the FTP serverto the NodeB. The downloaded extral configuration files take effect after activating.

Procedure


Step 2 Double-click Software Management > DownLoad Extral XML configuration file. TheDownLoad Extral XML configuration file dialog box is displayed.For the parameter details in the DownLoad Extral XML configuration file dialog box, see12.5.5 Interface Reference for Downloading Extral XML configuration file.

Step 3 Set the corresponding parameters in the DownLoad Extral XML configuration file dialog box.

Step 4 Click Next. The DownLoad Extral XML configuration file dialog box is displayed.The statusand progress of the patch upgrade is displayed in the dialog box.Then,A dialog box is displayedfor your confirmation.

Step 5 On the displayed dialog box,click Yes.

----End

12.5 Interface Reference for Managing the NodeB FileThis section describes the interface reference for managing the NodeB file.

12.5.1 Interface Reference for Data Configure File TransferThis section describes the interface reference for transferring data configuration files.



146

Field Description

ParameterSetting

TransferType

By default, Upload(NodeB toFTP Server) is selected,indicating that theNodeBCfg.xml is uploaded tothe FTP server.

In the Compress Flag area,select an option to decidewhether to compress the dataconfiguration file or not. Tosave space, select Compress.l Uncompress: The uploaded

data configuration file is notcompressed.

l Compress: The uploadeddata configuration file iscompressed. Applying thisoperation consumes moreCPU resource.

Select Download (FTP Serverto NodeB) to download theconfiguration file ofNodeBCfg.xml from the FTPserver to the NodeB.

In the Effective DataConfiguration File area, youmay choose to reset the NodeBimmediately or later. Resettingthe NodeB activates the dataconfiguration file.l Reset Promptly: The

NodeB is immediately resetand the data configurationfile is validated.

l Reset Later: The NodeB ismanually reset later tovalidate the dataconfiguration file.

DirectoryName

Enables you to specify the directory of the configuration file in theFTP server. The configuration file has a fixed file name.l If you select Upload (NodeB to FTP Server), it is the

destination path.l If you select Download (FTP Server to NodeB), it is the

source path.

FTPSetting

Enables you to set the FTP server for downloading the patch. TheFTP server in use is displayed for reference.Click Modify on the right to set the FTP server.

Transferstatus

Status Active status of the started task of the data configuration file

Progress Transfer progress of the data configuration file

12.5.2 Interface Reference for Device Archives TransferThis section describes the interface reference for transferring archive files.



147

Field Description

ParameterSetting

Transfer Type l If you select Export Device File, the system creates adevice archive file automatically. The name of the fileis NodeBDevFile.xml.

l If you select Upload Device File, the device archivefiles are uploaded from the NodeB to the FTP server.

If both Export Device File and Upload Device File areselected, the device archive files are created and uploaded.

UploadDestinationFile(*.xml)

Indicates a device archive file, which has an extensionof .xml. When you select Upload Device File in theTransfer Type area, this option is available.

FTP Setting Enables you to specify the FTP server that stores data filesto be uploaded. The FTP server in use is displayed forreference.Click Modify on the right to set the FTP server.

Operationstatus

Status Indicates the transfer status of the device archive file.

Progress Indicates the transfer progress of the device archive file.

12.5.3 Interface Reference for Transferring Other FilesThis provides the interface reference for transferring other files.

Field Description

Parameter Setting Transfer Type By default, Upload(NodeB to FTP Server) isselected. This indicates that the NodeB data filesare uploaded to the FTP server. This enables youto save, browse, and modify the file.



148

Field Description

File Description This enables you to specify the type of the log fileto be uploaded. The types are listed as follows:l BRDLOGl SECLOGl RUNLOGl OPRLOGl BAKOTHERl EXPTl CDMl CANBUSLOGl ALMLOGl CFLTLOGl LFLTLOGl TSTRSLTl TQRLOGl DBGLOGl BSPREPORTl DSP Mem Logl DSP Logl RTWP Test Logl BSP Logl SOLLOGl CBDLOGl BDTLOG

Destination File orDirectory

This enables you to specify the path or file inwhich data files are saved on the FTP server.

FTP Setting This enables you to specify the FTP server thatstores data files to be uploaded or downloaded.The FTP server that is in use is shown in the boxfor your reference.To specify an FTP server, click Modify.

Upload Mode Indicates whether the compressed mode is usedfor uploading files.

Transfer status Status Indicates the transfer status of the device archivefile.

Progress Indicates the transfer progress of the devicearchive file.



149

12.5.4 Interface Reference for Detailed Information AboutSuccessful and Failed Files

This section describes the interface reference for detailed information about successful and failedfiles.

Field Description

Successful Files List File Name Name of files that aresuccessfully uploaded.

File Description Description of files that aresuccessfully uploaded.

Failed Files List File Name Name of files where uploadinghas failed.

File Description Description of files whereuploading has failed.

Failure Cause Cause of uploading failure.

12.5.5 Interface Reference for Downloading Extral XMLconfiguration file

This section provides the interface reference for downloading extral XML configuration file.

Field Description

FTP Setting This enables you to set the FTP server for downloading the NodeBsoftware.The FTP server that is in use is shown in the box for your reference.The FTP server can be a built-in server or a user-specified server.To set the FTP server, click Modify on the right side of the element.

DownLoad ConfigFile

This enables you to download the extral configuration file from theFTP server to the NodeB.To specify a path for the downloading extral configuration file, clickBrowse.This operation is mandatory.

Pra_Activate Select this option to pre-activate the extral configuration file.This operation is optional.

UpLoad The ResultFile Of Pra_Activate

After pre-activation is completed in scenarios where the check box isselected, the pre-activation result file is uploaded to the FTP server.This operation is optional.NOTE

The item can be performed only after Pra_Activate is selected.



150

Field Description

Activate Select this option to activate the extral configuration file.This operation is mandatory.

UpLoad The ResultFile Of Activate

After activation is completed in scenarios where the check box isselected, the activation result file is uploaded to the FTP server.This operation is optional.NOTE

The item can be performed only after Activate is selected.

End BatchFile(MustSelect)

The extral configuration file is performed in the batch processingprocess. This task is used to end the batch processing process.This operation is mandatory.



151

13 Monitoring the NodeB Performance inReal Time

About This Chapter

This chapter includes procedures for monitoring the NodeB performance and status in real-timeon the LMT.

13.1 Collecting the IP Clock DataThis section describes how to collect the IP clock data on the Iub interface to analyze thefluctuation of the IP packets report.Data related to frequency and phase discrimination isincluded in the collected data.

13.2 Monitoring the Traffic over the Transmission PortsThis section describes how to monitor the traffic over the transmission ports. By performing thistask, you can view the current overall bandwidth consumption of the ports in real time.Monitoring ports consists of physical ports and transmission resource groups. The types ofphysical port to be monitored are ETH, ETHTRK, PPP, MPGROUP, IMA, UNI, FRAATM,IMALNK, and STM-1.

13.3 Monitoring the Traffic over the Transmission LinksThis section describes how to monitor the traffic over the transmission links. By performing thistask, you can monitor the traffic of the data streams transmitted and received by the NodeB inreal time to review overall bandwidth consumption of various services. The types of transmissionlink that can be monitored are PVC in ATM transmission and OM channel/SCTP/IPPATH inIP transmission.

13.4 Querying the Service Resources of a CellThis section describes how to query the resources of a cell. By performing this task, you canlearn about the service status of the cell in real time. For example, you can review the numberof UEs, number of UL CEs in use, and number of DL CEs in use.

13.5 Measuring the Cell-Level RTWPThe Received Total Wideband Power (RTWP) is the received wideband power in an uplinkchannel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.This section describes how to measure the cell-level RTWP. You can calibrate the gain of uplinkRF channels through the cell-level RTWP measurement. The NodeB RTWP test has impact onthe services.

NodeBLMT User Guide 13 Monitoring the NodeB Performance in Real Time


152

13.6 Measuring the Board-Level RTWPThe Received Total Wideband Power (RTWP) is the received wideband power in an uplinkchannel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.This section describes how to measure the board-level RTWP. You can calibrate the gain ofuplink RF channels through the board-level RTWP measurement. The NodeB RTWP test hasimpact on the services.

13.7 Testing the NodeB ClockThis section describes how to test the clock of the NodeB. The quality of the clock source iscrucial to the system operation. Thus, you must handle the clock alarm once it is generated. Theclock test has no impact on the system or the service.

13.8 Scanning the Uplink FrequencyThis section describes how to scan the uplink frequency. The uplink frequency scanning helpsyou examine electromagnetic environment around the NodeB and internal interference of theNodeB. The RRU or WRFU scans the frequency continuously, calculates the strength of receivedsignals, and reports the results. It is recommended that the uplink frequency be scanned beforecell configuration.

13.9 Monitoring Output Power of the NodeBThis section describes how to monitor output power of the NodeB, including the typical outputpower and carrier output power.

13.10 Monitoring the Temperature of the NodeBThis section describes how to monitor the temperature of the NodeB. By performing this task,you can monitor the temperature of both the MTRU and the internal power amplifier.

13.11 Querying the Resources of a NodeB BoardThis section describes how to query the resources of a NodeB board. By querying the serviceresources of a cell, you can learn about the service status of the board in real time, including thetotal service resources, occupied service resources, and idle service resources.

13.12 Monitoring the Cell Service ThroughputThis section describes how to learn the distribution of the users in the cell by monitoring thenumber of users in the cell UL and DL in real time.

13.13 Common Operations for Real-time Performance Monitoring on the NodeBCommon operations for real-time performance monitoring on the NodeB includes online/offlinebrowsing of the monitoring result, saving the monitoring result, and ending the monitoring task.

13.14 Interface Reference for Monitoring the NodeB Performance in Real TimeThis section describes the interface reference for the real-time specific monitoring of NodeB.



153

13.1 Collecting the IP Clock DataThis section describes how to collect the IP clock data on the Iub interface to analyze thefluctuation of the IP packets report.Data related to frequency and phase discrimination isincluded in the collected data.

Procedure


Step 2 Select Realtime Specific Monitoring > IP Clock Data Gather Monitoring. The IP ClockData Gather dialog box is displayed.

For the parameter details in the IP Clock Data Gather dialog box, see 13.14.1 InterfaceReference for Collecting IP Clock Data.

Step 3 Set the corresponding parameters in the dialog box.

Step 4 Click OK. A window is displayed, showing the current monitoring task in graph.

Step 5 To stop this test task, use either of the following methods:l Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed

in the window.l Method 2: Right-click the task on the monitoring task list and choose Delete Task from the

shortcut menu. The curve displayed for the task is deleted together with the task.

----End

ResultTable 13-1 describes the monitoring items.

Table 13-1 Monitoring items for the IP clock data collecting

Item Description

Clock Data Max Indicates the maximum value of the clock data on the IP clocklink.

Clock Data Min Indicates the minimum value of the clock data on the IP clocklink.

13.2 Monitoring the Traffic over the Transmission PortsThis section describes how to monitor the traffic over the transmission ports. By performing thistask, you can view the current overall bandwidth consumption of the ports in real time.Monitoring ports consists of physical ports and transmission resource groups. The types ofphysical port to be monitored are ETH, ETHTRK, PPP, MPGROUP, IMA, UNI, FRAATM,IMALNK, and STM-1.



154

Prerequisite


Contextl The traffic monitoring of the monitored objects over four ports can be started on a board.

l Only one monitoring task can be started for one monitored object over the same port.

Procedure


Step 2 Select Realtime Specific Monitoring > IUB Port Flux Stat Monitoring. The IUB Port FluxStat Monitoring dialog box is displayed.

Step 3 Set the corresponding parameters. For details, see 13.14.2 Interface Reference for TrafficMonitoring over the Transmission Ports.


Step 5 To stop this monitoring task, use either of the following methods:

l Method 1: Close the task monitoring window to stop all monitoring tasks displayed in thewindow.

l Method 2: Right-click the task on the monitoring task list and select Delete Task from theshortcut menu. The curve displayed for the task is deleted together with the task.

----End

Result

The monitoring item varies with the type of physical port to be monitored. Table 13-2 lists thephysical port types and monitoring items.

Table 13-2 Physical port types and monitoring items

Port Type Physical Port Type Monitoring Item

PHYSICAL_PORT ETH/ETHTRK/PPP/MPGRP

l RX Rate of IP portl TX Rate of IP portl RX Packet Discard Rate

of IP Levell TX Packet Discard Rate

of IP Levell RX Packet Discard Rate

of Link Levell TX Packet Discard Rate

of Link Level



155

Port Type Physical Port Type Monitoring Item

IMA/UNI/FRAATM/IMALNK/STM-1

l RX Rate of ATMl TX Rate of ATMl RX HCS Error Rate of

ATM Port

RSCGRP ETH/ETHTRK/PPP/MPGRP

TX Rate of IP logical port

IMA/UNI/FRAATM/IMALNK/STM-1

TX Rate

Table 13-3 describes the monitoring items.

Table 13-3 Monitoring items for traffic over the transmission ports

Monitoring Item Description

RX Rate of ATM Receive rate on the monitored portUnit: cps or bps

TX Rate of ATM Transmit rate on the monitored portUnit: cps or bps

RX HCS Error Rate of ATM Port Receive packet error rate on the monitoredportUnit: cps or bps

RX Rate of IP port Receive rate on the monitored portUnit: pps or bps

TX Rate of IP port Transmit rate on the monitored portUnit: pps or bps

RX Packet Discard Rate of IP Level Receive packet loss rate at the IP layer on themonitored portUnit: ‰

TX Packet Discard Rate of IP Level Transmit packet loss rate at the IP layer on themonitored portUnit: ‰

RX Packet Discard Rate of Link Level Receive packet loss rate at the link layer onthe monitored portUnit: ‰

TX Packet Discard Rate of Link Level Transmit packet loss rate at the link layer onthe monitored portUnit: ‰



156


TX Rate of IP logical port Transmit rate on the monitored portUnit: pps or bps

TX Rate Transmit rate on the monitored portUnit: cps or bps

13.3 Monitoring the Traffic over the Transmission LinksThis section describes how to monitor the traffic over the transmission links. By performing thistask, you can monitor the traffic of the data streams transmitted and received by the NodeB inreal time to review overall bandwidth consumption of various services. The types of transmissionlink that can be monitored are PVC in ATM transmission and OM channel/SCTP/IPPATH inIP transmission.

Prerequisite


Contextl Four simultaneous monitoring tasks over the transmission links can be started on a board.

l Only one monitoring task can be started for one monitored object over the same link.

l A maximum of six PVC links can be monitored in the same monitoring task for the ATM-based links.

l A maximum of six PVC data streams, involving one OM channel, two SCTP links, andthree IP paths, can be monitored in the same monitoring task for the IP-based links.

Procedure


Step 2 Select Realtime Specific Monitoring > IUB Link Flux Stat Monitoring. The IUB Link FluxStat Monitoring dialog box is displayed.

Step 3 Set the corresponding parameters. For details, see 13.14.3 Interface Reference for TrafficMonitoring over the Transmission Links.


Step 5 To stop this monitoring task, use either of the following methods:

l Method 1: Close the task monitoring window to stop all monitoring tasks displayed in thewindow.


----End



157

ResultThe monitoring item varies with the type of transmission link to be monitored. Table 13-4 listslink types and monitoring items.

Table 13-4 Link types and monitoring items

Link Type Monitoring Item

PVC l RX Rate of PVI xl TX Rate of PVI xNOTE

The value of x ranges from 1 to 6.

OM(TCP) l RX Rate of TCPl TX Rate of TCP

SCTP l RX Rate of SCTP yl TX Rate of SCTP yl Receive Error Packets of SCTP yl Retransmit Ratio of SCTP yNOTE

The value of y ranges from 1 to 2.

IPPATH l RX Rate of IPPATH zl TX Rate of IPPATH zIf Include IPPM Statisticis is selected, thefollowing item is exported in the monitoringresult.l Average RTT Delay of IPPATH zl TX Packet Discard Rate of IPPATH zl TX Time Jitter of IPPATH zNOTEl The value of z ranges from 1 to 3.

l If Include IPPM Statisticisis selected, theIPPM must be actived, otherwise the operationwill fault.


Table 13-5 Monitoring items for traffic over the transmission links


RX Rate of PVI x Receive rate at the PVI linkUnit: cps or bps



158


TX Rate of PVI x Transmit rate at the PVI linkUnit: cps or bps

RX Rate of TCP Receive rate at the TCP linkUnit: pps or bps

TX Rate of TCP Transmit rate at the TCP linkUnit: pps or bps

RX Rate of SCTP y Receive rate at the SCTP linkUnit: pps or bps

TX Rate of SCTP y Transmit rate at the SCTP linkUnit: pps or bps

Receive Error Packets of SCTP y Number of received error packets at the SCTPlinkUnit: pps

Retransmit Ratio of SCTP y Retransmission rate of packets at the SCTPlinkUnit: ‰

RX Rate of IPPATH z Receive rate at the IPPATH linkUnit: pps or bps

TX Rate of IPPATH z Transmit rate at the IPPATH linkUnit: pps or bps

Average RTT Delay of IPPATH z Average delay of uplink and downlinkUnit: ms

TX Packet Discard Rate of IPPATH z Average transmit packet loss rate on theuplinkUnit: ‰

TX Time Jitter of IPPATH z Average jitter of transmitted packets on theuplinkUnit: ms

13.4 Querying the Service Resources of a CellThis section describes how to query the resources of a cell. By performing this task, you canlearn about the service status of the cell in real time. For example, you can review the numberof UEs, number of UL CEs in use, and number of DL CEs in use.



159

Prerequisite

A logical cell is already set up.

Contextl UL resources refer to UL demodulation resources and UL decoding resources, measured

in points.l DL resources refer to DL modulation resources and DL coding resources, measured in

points.

NOTE

The resources consumed by a single instance of the 12.2 kbit/s voice service are defined as one point. Forthe other services, the consumed resources can be converted into points based on this criterion.

Procedure

Step 1 In the navigation tree, click the Maintenance tab.

Step 2 Select Realtime Specific Monitoring > Cell Service Resource Query. The Cell ServiceResource Query dialog box is displayed.

For the parameter details in the Cell Service Resource Query dialog box, see 13.14.4 InterfaceReference for Querying Cell Service Resources.




in the window.l Method 2: Right-click the task on the monitoring task list and select Delete Task from the


----End

Result


Table 13-6 Monitoring items for the cell service resources query

Item Description

User Number Indicates the number of UEs carried by the cell, including R99and HSPA users.

Used UL CE Number Indicates the UL CEs consumed by all UEs in thecorresponding cell.

Used DL CE Number Indicates the DL CEs consumed by all UEs in thecorresponding cell.



160

13.5 Measuring the Cell-Level RTWPThe Received Total Wideband Power (RTWP) is the received wideband power in an uplinkchannel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.This section describes how to measure the cell-level RTWP. You can calibrate the gain of uplinkRF channels through the cell-level RTWP measurement. The NodeB RTWP test has impact onthe services.

Procedure


Step 2 Double-click Realtime Specific Monitoring > Cell RTWP. The Cell RTWP dialog box isdisplayed.For the parameter details in the Cell RTWP dialog box, see 13.14.5 Interface Reference forMeasuring the Cell RTWP.


Step 4 Click OK. A monitoring window is displayed, showing the current monitoring task in graphs.

Step 5 To stop this test task, use either of the following methods:

l Method 1: Close the task monitoring window directly to stop all monitoring tasks displayedin the window.


----End

Result


Table 13-7 Monitoring items for the cell-level RTWP measurement

Item Description

Local Cell ID ID of the cell under the NodeB.

Cell ID ID of the cell under the RNC.

Runtime Cell RTWP(0.1dBm)

Cell-level real-time received total wideband power (RTWP).

NOTE

l One RF module can be configured with one to four carriers. The system outputs the RTWP value ofthe corresponding carrier based on the actual configuration.

l One carrier may be configured with main and diversity RX.



161

13.6 Measuring the Board-Level RTWPThe Received Total Wideband Power (RTWP) is the received wideband power in an uplinkchannel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.This section describes how to measure the board-level RTWP. You can calibrate the gain ofuplink RF channels through the board-level RTWP measurement. The NodeB RTWP test hasimpact on the services.

Context

Analyses of the board-level RTWP measurement are as follows:

l If the NodeB is disconnected from the antenna system or a matched load, the RTWP isapproximately -108 dBm. If the NodeB is connected to the antenna system (with TMAswitched on) or a matched load, the RTWP is approximately -105 dBm.

l If the services are normal and the uplink load reaches 75%, the RTWP is 6 dB higher thanthe RTWP when the NodeB does not carry any service.

NOTE

l When the reported RTWP is valid, the curve is normal. The vertical axis corresponds to the reportedRTWP with the unit of 0.1 dBm.

l When the reported RTWP is invalid, abnormal RTWP curves are displayed. The RTWP for the mainantenna forms a horizontal line at -112 dBm on the vertical axis. The RTWP for the diversity antennaforms a horizontal line at -111.5 dBm on the vertical axis. The error may lie in the absent MTRU orRRU, a broken link, or a faulty channel. In this case, clear the fault first.

Procedure


Step 2 Double-click Realtime Specific Monitoring > Board RTWP. The Board RTWP dialog boxis displayed.For the parameter details in the Board RTWP dialog box, see 13.14.6 Interface Reference forMeasuring the Board RTWP.






----End

Result




162

Table 13-8 Monitoring items for the board-level RTWP measurement

Item Description

Carrier n Rx Receive Freq Indicates the center frequency in the UL of carrier n. Unit: 0.2MHz

Carrier n Primary RTWP(0.1dBm)

Indicates the RTWP value for the main antenna in the UL ofcarrier n.

Carrier n Secondary RTWP(0.1dBm)

Indicates the RTWP value for the diversity antenna in the ULof carrier n.

NOTE

l The value of n ranges from 0 to 5 (One RF module can be configured with one to six carriers). Thesystem outputs the RTWP value of the corresponding carrier based on the actual configuration.

l One carrier may be configured with main and diversity RX.

13.7 Testing the NodeB ClockThis section describes how to test the clock of the NodeB. The quality of the clock source iscrucial to the system operation. Thus, you must handle the clock alarm once it is generated. Theclock test has no impact on the system or the service.

PrerequisiteThe reference clock source for the NodeB is configured.

ContextThe reference standards for the clock test are as follows:

l For the GPS and BITS clock sources, the reporting period of the DA value is two minutesin normal conditions. In the case of jitter or large frequency offset, the reporting periodmay be longer than 2 minutes. Note that it is normal that the first reporting period is not 2minutes.

l For the LINE clock source, the reporting period of the DA value is 30 minutes in normalconditions. In the case of jitter or large frequency offset, the reporting period may be longerthan 30 minutes. Note that it is normal that the first reporting period is not 30 minutes.

NOTE

l The reporting period of the phase discrimination value is different from that of the DA value. Thereporting period of the phase discrimination value is 1s, while the reporting period of the DA valuevaries according to the type of the clock sources.

l In general, the phase discrimination value is from -10 to +10 when the clock module is functional.When the clock module malfunctions and a large frequency offset exists, the phase discriminationvalue is from -128 to +127.



163

Procedure


Step 2 Select Realtime Specific Monitoring > Clock Test. The Clock Test dialog box is displayed.

For the parameter details in the Clock Test dialog box, see 13.14.7 Interface Reference forTesting the Clock.






----End

Result


Table 13-9 Monitoring items for the NodeB clock test

Item Description

Phase Discrimination Indicates the monitored phase offset of the current clock.

13.8 Scanning the Uplink FrequencyThis section describes how to scan the uplink frequency. The uplink frequency scanning helpsyou examine electromagnetic environment around the NodeB and internal interference of theNodeB. The RRU or WRFU scans the frequency continuously, calculates the strength of receivedsignals, and reports the results. It is recommended that the uplink frequency be scanned beforecell configuration.

Prerequisite

The MTRU/MRRU must be blocked before the RX frequency scanning starts.

Context

Reference criteria for test results of the uplink frequency scanning are as follows:

l If the NodeB is disconnected from the antenna system and the curve jumps higher than-108 dBm, there is internal interference from the NodeB.



164

l If the NodeB is connected to the antenna system with the TMA powered on and theattenuation values of RF channels are configured to compensate the TMA gain and feederloss and if the curve jumps higher than -105 dBm, there must be external interference.

l The shapes of the jumps tell the interference type in normal cases.– A triangular or trapezium jump: There is tone interference. The peak of the jump is the

central frequency of the interference.– A rectangle jump or a jump added with a rectangle: There is individual broadband

interference. The central point of the upper side of the rectangle is the interferencefrequency.

ProcedureStep 1 In the navigation pane of the Local Maintenance Terminal window, click the Maintenance

tab.

Step 2 Double-click Realtime Specific Monitoring > RX Frequency Scanning. The RX FrequencyScanning dialog box is displayed.

For the parameter details in the RX Frequency Scanning dialog box, see 13.14.8 InterfaceReference for Scanning the UL Frequency.


Step 4 Click OK. A dialog box prompts you to start the uplink frequency scanning.

Step 5 Click Yes. A new window is displayed, showing the monitoring chart of the current task.

Step 6 Stop the test in one of the following ways.l Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed



----End


Table 13-10 Monitoring items for the RX frequency scanning

Item Description

Current Frequency Indicates the frequency that is currently being scanned.

Primary RTWP(0.1dBm) Indicates the RTWP value for the main antenna.

Secondary RTWP(0.1dBm) Indicates the RTWP value for the diversity antenna.

13.9 Monitoring Output Power of the NodeBThis section describes how to monitor output power of the NodeB, including the typical outputpower and carrier output power.



165

ContextAfter the task has started, the system periodically reports the monitored typical power and theoutput power of each carrier according to the set time interval.

Configuration of the NodeB output power depends on the specified services.

The output power of the NodeB is associated with the configuration and specified services. Ifthe pilot power and typical output power are configured, the output power of the WRFU or RRUis about 3 dB greater than the pilot power when the NodeB carries no services. If the outputpower of the WRFU or RRU is considerably lower than the pilot power, the output power of theNodeB is abnormal.

The pilot power of the WRFU or RRU can be set to 33 dBm. The typical power can be set to 43dBm.

Procedure


Step 2 Double-click Realtime Specific Monitoring > Output Power Monitoring. The Output PowerMonitoring dialog box is displayed.

For the parameter details in the Output Power Monitoring dialog box, see 13.14.9 InterfaceReference for Monitoring the Output Power.






----End


Table 13-11 Monitoring items for the NodeB output power measurement

Item Description

Carrier Output Power(Channel No: X; Carrier No:Y; Unit: 0.1dBm)

Indicates the output power of Y carrier in X channel. Thecarrier output power is the actual output power of the RRU.

Channel Output Power(Channel No: X; Unit:0.1dBm)

Indicates the typical output power in X channel correspondingto the RF module. The channel output power is the ideal outputpower, which is the theoretical output power.



166

13.10 Monitoring the Temperature of the NodeBThis section describes how to monitor the temperature of the NodeB. By performing this task,you can monitor the temperature of both the MTRU and the internal power amplifier.

Context

After the task has started, the system periodically reports the temperature of the WMPT, UTRP,WRFU, RRU, and internal power amplifier, according to the set time interval. This alarm israised when the working temperature of the power module is beyond the limit.

Procedure


Step 2 Double-click Realtime Specific Monitoring > Temperature Monitoring. The TemperatureMonitoring dialog box is displayed.

For the parameter details in the Temperature Monitoring dialog box, see 13.14.10 InterfaceReference for Monitoring the Temperature.



Step 5 Stop the test in one of the following ways.



----End

Result


Table 13-12 Monitoring items for the NodeB temperature measurement

Item Description

Board Temperature(Celsius)

Indicates the temperature of the monitored unit.

PA Temperature(Celsius) Indicates the temperature of the internal PA of the monitoredunit.



167

13.11 Querying the Resources of a NodeB BoardThis section describes how to query the resources of a NodeB board. By querying the serviceresources of a cell, you can learn about the service status of the board in real time, including thetotal service resources, occupied service resources, and idle service resources.

PrerequisiteLMT has logged into the NodeB.

The board to be queried is not blocked.

ContextThe occupancy of the board service resource is presented in percentage by dividing the occupiednumber by the total number. The resource occupancy consists of the following parts:

l Resource occupancy for demodulating the DSPl Resource occupancy for decoding the DSPl Resource occupancy for encoding the DSP

NOTE

l This query is only for the available DSPs. Those unavailable DSPs are not displayed.

l The resources for a 12.2 kbit/s voice service channel are regarded as a point. Other service channelresources can be converted into points based on this criterion.

Procedure


Step 2 Select Realtime Specific Monitoring > Board Service Resource Query. The Board ServiceResource Query dialog box is displayed.

For the parameter details in the Board Service Resource Query dialog box, see 13.14.11Interface Reference for Querying the Resources of a Board.






----End




168

Table 13-13 Monitoring items for NodeB board service resources query

Item Description

Encoding DSPX Indicates resources used to encode the DSP of thecorresponding service board.

Demodulating DSPX Indicates resources used to demodulate the DSP of thecorresponding service board.

Decoding DSPX Indicates resources used to decode the DSP of thecorresponding specific service board.

NOTE

X represents the number of the corresponding service board, which can use the serial number of the currentlyavailable DSPs.

13.12 Monitoring the Cell Service ThroughputThis section describes how to learn the distribution of the users in the cell by monitoring thenumber of users in the cell UL and DL in real time.

Procedure


Step 2 Select Realtime Specific Monitoring > Cell Through Out Statistic. The Cell Through OutStatistic dialog box is displayed.

For the parameter details in the Cell Through Out Statistic dialog box, see 13.14.12 InterfaceReference for the Cell Traffic Throughput Statistics.






----End

Result




169

Table 13-14 Monitoring items for the cell service throughput measurement

Item Description

Ul R99 Throughput(bps) Indicates the UL throughput of the R99 services in the specificcell.

Ul Hspa Throughput(bps) Indicates the UL throughput of the HSPA services in thespecific cell.

Dl R99 Throughput(bps) Indicates the DL throughput of the R99 services in the specificcell.

13.13 Common Operations for Real-time PerformanceMonitoring on the NodeB

Common operations for real-time performance monitoring on the NodeB includes online/offlinebrowsing of the monitoring result, saving the monitoring result, and ending the monitoring task.

13.13.1 Browsing Monitoring Results of NodeB OnlineThis section describes how to browse or query the monitoring results displayed in theperformance monitoring window in real time.

Prerequisitel The real-time performance monitoring task has started.l Monitoring results are reported by the system.

Procedurel Right-click on the List tab page in the real-time performance monitoring window. You can

perform the following operation through the shortcut menu:– Sets auto scroll

l Right-click on the Chart tab page in the real-time performance monitoring window. Youcan perform the following operations through the shortcut menu:– Sets auto scroll– Shows or hiding grid– Sets Y axis display range– Switches the display mode

l Right-click in the task information pane at the bottom of the real-time performancemonitoring window. You can perform the following operation through the shortcut menu:– Adds/Deletes tasks

----End

13.13.2 Saving Monitoring Results of the NodeBThis section describes how to save the monitoring results of NodeB in files for later query.



170

Prerequisitel The real-time performance monitoring task has started.

l Monitoring results are reported by the system.

Contextl The default save path is LMT installation directory\adaptor\clientadaptor\NodeB\LMT

software version number\output\realmonitor.

l The default file name is MonitoringItem_Year_Month_Day_Hour_Minute_Second_Corresponding Parameter

l The extension name of the file automatically saved is .txt.

Procedure

Step 1 When creating a monitoring task, select the Auto Save check box in the dialog box for settingparameters. By default, the check box is selected.

Step 2 Click OK to save the monitoring results in the specified path.

----End

13.13.3 Stopping a Monitoring Task of the NodeBThis section describes how to stop a monitoring task that occupies resources when the monitoringtask is no longer needed.

Prerequisite

A tracing task has been successfully created.

Procedure

l Click in the right upper corner of the monitoring window to stop monitoring.

l Right-click the task in the task list below the graph area and then choose Delete Task fromthe shortcut menu.

----End

13.13.4 Browsing Monitoring Results of the NodeB OfflineThis section describes how to browse NodeB monitoring results offline on the LMT. It helps inreviewing the operation history and locating the faults.

Prerequisite

The monitoring results are saved in files.



171

Procedure

Step 1 Open the directory where the monitoring results are saved. The default path for the files isinstallation directory\adaptor\clientadaptor\NodeB\LMT software version numberoutput\realmonitor. To name the files, refer to Saving NodeB Monitoring Results.

Step 2 Double-click the file to open it.

Step 3 Review the information.

----End

13.14 Interface Reference for Monitoring the NodeBPerformance in Real Time

This section describes the interface reference for the real-time specific monitoring of NodeB.

13.14.1 Interface Reference for Collecting IP Clock DataThis section provides the interface reference for collecting the IP clock data.

Field Description

Cabinet No. Value: Master cabinet.

Subrack No. Subrack number of the BBU. Value: 0.

Slot No. Slot number of the WMPT.

Auto Save If this check box is selected, the monitoring data file isautomatically saved.

Text File Name Name of a .txt file to save the measurement data.

13.14.2 Interface Reference for Traffic Monitoring over theTransmission Ports

This section describes the interface reference for traffic monitoring over the transmission ports.


ParameterSetting

Protocol Type This parameter can be set to IP or ATM.

Cabinet No. The fixed value of this parameter is 0~7.

Subrack No. This parameter indicates the subrack number of the BBU,with a fixed value of 0~1.

Slot No. This parameter indicates the slot number of the WMPT orUTRP.The value range is from 0 to 73.



172


Sub Board Type If Protocol Type is set to ATM, this parameter can be setto:l E1_COVERBOARD or UNCHANNELED_COV-

ERBOARD when Slot No. is from 0 to 52.l BASE_BOARD or BACK_BOARD when Slot No. is

6 or 7.l BASE_BOARD or BACK_BOARD when Slot No. is

3.If Protocol Type is set to IP, this parameter can be set to:l E1_COVERBOARD orETH_COVERBOARD

when Slot No. is from 0 to 52.l BASE_BOARD or BACK_BOARD when Slot No. is

6 or 7.l BASE_BOARD or BACK_BOARD when Slot No. is

3.

Port Type This parameter can be set to PHYSICAL_PORT orRSCGRP.

Physical PortType

If Protocol is set to ATM, this parameter can be set to:l IMA, UNI, FRAATM, or IMALNK when Sub Board

Type is BASE_BOARDl UNI, FRAATM, or IMALNK when Sub Board

Type is BACK_BOARDl IMA, UNI, FRAATM, or IMALNK when Sub Board

Type is E1_COVERBOARDl STM-1 when Sub Board Type is

UNCHANNELED_COVERBOARDIf Protocol is set to IP, this parameter can be set to:l PPP, MPGRP, or ETH when Sub Board Type is

BASE_BOARDl PPP when Sub Board Type is BACK_BOARDl ETH or ETHTRK when Sub Board Type is

ETH_COVERBOARDl PPP or MPGRP when Sub Board Type is

E1_COVERBOARD



173


Port No. In the case that Protocol is set to ATM,l If Sub Board Type is set to BASE_BOARD, this

parameter can be set to:– 0 or 1 when Port Type is IMA– 0 to 3 when Port Type is UNI– 0 to 3 when Port Type is FRAATM– 0 to 3 when Port Type is IMALNK

l If Sub Board Type is set to BACK_BOARD, thisparameter can be set to:– 0 to 3 when Port Type is UNI– 0 to 3 when Port Type is FRAATM– 0 to 3 when Port Type is IMALNK

l If Sub Board Type is set to E1_COVERBOARD, thisparameter can be set to:– 0 to 3 when Port Type is IMA– 0 to 7 when Port Type is UNI– 0 to 7 when Port Type is FRAATM– 0 to 7 when Port Type is IMALNK

l If Sub Board Type is set to UNCHANNELED_COV-ERBOARD, this parameter can be set to:– 0 when Port Type is STM-1

In the case that Protocol is set to IP,l If Sub Board Type is set to BASE_BOARD, this

parameter can be set to:– 0 to 11 when Port Type is PPP– 0 or 1 when Port Type is MPGRP– 0 or 1 when Port Type is ETH

l If Sub Board Type is set to BACK_BOARD, thisparameter can be set to:– 0 to 11 when Port Type is PPP

l If Sub Board Type is set to E1_COVERBOARD, thisparameter can be set to:– 0 to 11 when Port Type is PPP– 0 to 3 when Port Type is MPGRP

l If Sub Board Type is set to ETH_COVERBOARD,this parameter can be set to:– 0 to 3 when Port Type is ETH– 0 or 1 when Port Type is ETHTRK



174


Unit This parameter can be set to cps or bps when ProtocolType is set to ATM.This parameter can be set to pps or bps when ProtocolType is set to IP.

ReportingPeriod(s)

This parameter indicates the periods for reporting themonitoring tasks, with a fixed value of 1.

Include IPDiscard Packet'sInformation

This parameter is valid only when Protocol Type is set toIP.When this parameter is selected, the RX and the TX PacketDiscard Rate on the IP layer is exported in the monitoringresult. The unit of Packet Discard Rate is ‰.

Include LinkDiscard Packet'sInformation

This parameter is valid only when Protocol Type is set toIP.When this parameter is selected, the RX and the TX PacketDiscard Rate on the link layer is exported in the monitoringresult. The unit of Packet Discard Rate is ‰.

Choose Resource Group This parameter is valid only when Port Type is set toRSCGRP.The resource groups are invariably classified into fourgroups: Resource Group 0, Resource Group 1, ResourceGroup 2, and Resource Group 3. You can select a propergroup based on the resource group number allocated to you.


Text File Name This parameter indicates the name of a .txt file to save themeasurement data.

13.14.3 Interface Reference for Traffic Monitoring over theTransmission Links

This section describes the interface reference for traffic monitoring over the transmission links.


ParameterSetting

Protocol Type This parameter can be set to IP or ATM.

Cabinet No. The fixed value of this parameter is 0~7.

Subrack No. This parameter indicates the subrack number of the BBU,with a fixed value of 0~1.



175


Slot No. This parameter indicates the slot number of the WMPT orUTRP.The value range is from 0 to 73.

Sub Board Type If Protocol Type is set to ATM. This parameter can be setto:E1_COVERBOARD or UNCHANNELLED_COVER-BOARD when Slot No. is from 0 to 52BASE_BOARD or BACK_BOARD when Slot No. is 6or 7.BASE_BOARDor BACK_BOARD when Slot No. is 3.

Physical PortType

If Protocol Type is set to ATM. This parameter can be setto:IMA, UNI, or FRAATM when Sub Board Type isBASE_BOARDUNI, or FRAATM when Sub Board Type isBACK_BOARDIMA, UNI, or FRAATM when Sub Board Type isE1_COVERBOARDUNCHANNELLED_COVERBOARD when SubBoard Type is STM-1

Port No. This parameter is valid only when Protocol Type is set toATM.l If Sub Board Type is set to BASE_BOARD, this

parameter can be set to:– 0 or 1 when Port Type is IMA– 0 to 3 when Port Type is UNI– 0 to 3 when Port Type is FRAATM

l If Sub Board Type is set to BACK_BOARD, thisparameter can be set to:– 0 to 3 when Port Type is UNI– 0 to 3 when Port Type is FRAATM

l If Sub Board Type is set to E1_COVERBOARD, thisparameter can be set to:– 0 to 3 when Port Type is IMA– 0 to 7 when Port Type is IMALNK– 0 to 7 when Port Type is UNI

l If Sub Board Type is set to UNCHANNELED_COV-ERBOARD, this parameter can be set to:– 0 when Port Type is STM-1



176


Unit This parameter can be set to cps, or bps, or when ProtocolType is set to ATM.This parameter can be set to pps or bps when ProtocolType is set to IP.

Report Period(s) This parameter indicates the periods for reporting themonitoring tasks, with a fixed value of 1.

Include IPPMStatistic

This parameter is valid only when Protocol Type is set toIP.If this parameter is selected, the IPPM is detected andreported.

ATM Parameter This parameter is valid only when Protocol Type is set toATM.A maximum of six PVC links can be monitoredsimultaneously. You can select the corresponding PVCindexes and set VPI and VCI attributes according to thePVC links to be monitored.

IPParameter

TCP The IP link traffic monitoring function enables monitoringof a maximum of one OM channel, two SCTP links, andthree IP paths at the same time.If this parameter is selected, the specified OM channel canbe monitored. In this case, you must set Local IP, RemoteIP, and the priority of DSCP.

SCTP1/SCTP2 If an SCTP index is selected and number of the SCTP linkis specified, the traffic monitoring task over the SCTP linkis started.

IPPATH1/IPPATH2/IPPATH3

If an IP path index is selected and ID of the IP path isspecified, the traffic monitoring task over the IP path isstarted.


Text File Name This parameter indicates the name of a .txt file to save themeasurement data.

13.14.4 Interface Reference for Querying Cell Service ResourcesThis section describes the interface reference for querying the cell service resources.

Field Description

Local Cell ID This is the target Cell ID.



177

Field Description

Text File Name This parameter indicates the name of a .txt file to save the measurementdata.

13.14.5 Interface Reference for Measuring the Cell RTWPThis section provides the interface reference for measuring the Cell RTWP.

Field Description

Cell ID ID of the cell to be measured.

Reporting Period(s) Reporting period of measurement reports. Value: 1s.

Auto Save If this check box is selected, the testing data file is automaticallysaved.


13.14.6 Interface Reference for Measuring the Board RTWPThis section provides the interface reference for measuring the Board RTWP.

Field Description

Cabinet No. Value: Master cabinet.

Subrack No. Subrack number of the WRFU/RRU.

Slot No. Slot number of the WRFU/RRU.

Reporting Period(s) Reporting period of measurement reports. Value: 1s.

Auto Save If this check box is selected, the testing data file is automaticallysaved.


13.14.7 Interface Reference for Testing the ClockThis section provides the interface reference for testing the clock.

Field Description

Cabinet No. Value range: 0~7 .

Subrack No. Subrack number of the BBU. Value: 0~1.



178

Field Description

Slot No. Slot number of the WMPT. Value range: 6 to73.

Auto Save If this check box is selected, the testing datafile is automatically saved.

Text File Name Name of a .txt file to save the measurementdata.

13.14.8 Interface Reference for Scanning the UL FrequencyThis section provides the interface reference for scanning the UL frequency.

Field Description

Cabinet No. Value range: 0~62

Subrack No. Indicates the number of the subrack where the WRFU or RRUis configured.

Slot No. Indicates the number of the slot where the WRFU or RRU isconfigured.

Start RF Frequency(200KHz)

Indicates the start frequency of the frequency scanning.

End RF Frequency(200KHz)

Indicates the end frequency of the frequency scanning.

Scanning FrequencyInterval(200KHz)

Value range: 1 to 25.

Scanning Time Interval(0.1s)

Value range: 2 to 600.

Auto Save If this check box is selected, the scanning data file isautomatically saved.

Text File Name Indicates the name of a .txt file to save the scanning data.

13.14.9 Interface Reference for Monitoring the Output PowerThis section provides the interface reference for monitoring the output power.

Field Description

Cabinet No. Value: 0 ~ 62.

Subrack No. Subrack number of the WRFU/RRU.



179

Field Description

Slot No. Slot number of the WRFU/RRU.

Reporting Period(s) Interval between two measurement data reports. Value range: 2seconds to 3,600 seconds.

Auto Save If this check box is selected, the monitoring data file is automaticallysaved.


13.14.10 Interface Reference for Monitoring the TemperatureThis section provides the interface reference for monitoring the temperature.


Cabinet No. Value: 0 ~ 62.

Subrack No. Subrack number of the WMPT/WRFU/RHUB/RRU.

Slot No. Slot number of the WMPT/WRFU/RHUB/RRU.

Report Period (s) Value range: 2 seconds ~ 3600 seconds.

Auto Save If the check box is selected, the monitoring records areautomatically saved in the specified path.


13.14.11 Interface Reference for Querying the Resources of a BoardThis section provides the interface reference for querying the resources of a board.

Field Description

Cabinet No. Value range: 0~7.

Subrack No. Subrack number of the BBU. Value range: 0~1.

Slot No. Slot number of the WBBP. Value range: 0~5.


Text File Name Name of a .txt file to save the monitoring data.



180

13.14.12 Interface Reference for the Cell Traffic ThroughputStatistics

This section provides the interface reference for the cell traffic throughput statistics.


Local Cell ID ID of the local cell.

Auto Save If the check box is selected, the monitoringrecords are automatically saved in thespecified path.

Text File Name Name of a .txt file to save the measurementdata.



181

14 Managing Interference Detection for theNodeB

About This Chapter

By analyzing the spectral and power distribution of sampled data, you can monitor theinterference in the frequency and time domains in radio environments.


Context

l When a local cell exists, the monitored frequency must be consistent with the uplinkfrequency configured for the local cell.

l If a local cell does not exist, the start frequency and end frequency must be within thefrequency band supported by the RRU.

l Interference detection is performed on RF modules. To perform NodeB offline interferencedetection on a SDR-based RF module of a multi-mode base station, perform the followingsteps(For a GSM+UMTS (GU) base station):

1. On the NodeB, run the BLK BRD command to block the RF module.2. On the BSC, run the DEA BTS command to deactivate the base station on the GSM

side.3. Wait 30 minutes and perform NodeB offline interference detection.

After NodeB offline interference detection is performed, unblock the RF module and activatethe cell and base station.

Procedure


Step 2 Double-click Interference Check. The Interference Check dialog box is displayed.

NodeBLMT User Guide 14 Managing Interference Detection for the NodeB


182

Step 3 Set the corresponding parameters in the Interference Check dialog box. For details about theparameters, see 14.1 Interface Reference for Interference Detection.

Step 4 Click OK.A window is displayed, showing the real-time detection data in the form of a list and graph. Inthe graph, the horizontal axis represents the frequency (MHz), and the vertical axis representsthe amplitude (dBm).

NOTE

l The detection result can have an acceptable error within ±5 dB.

l You can select Show Power Graph to open a window that shows the power data in a graph. In thegraph, the horizontal axis represents the relative time (ms), and the vertical axis represents the amplitude(dBm).

----End

14.1 Interface Reference for Interference DetectionThis section provides the interface reference for interference detection.



183

14.1 Interface Reference for Interference DetectionThis section provides the interface reference for interference detection.

Field Description

Cabinet No. Value range: 0~62.

Subrack No. Number of the subrack where the RRU/WRFU is configured

Slot No. Number of the slot where the RRU/WRFU is configured

Band Range Band I to band IX can be selected.

Start Frequency No. Start frequency number for the detection

End Frequency No. End frequency number for the detection

Start Frequency (MHz) Start frequency that the system automatically calculates accordingto the start frequency No.

End Frequency (MHz) End frequency that the system automatically calculates accordingto the end frequency No.

Module Type[Compensator]

Module type for the detection

File Path Path to the directory where the sampling files are saved. Twosampling files are downloaded each time.

FTP Setting The value can be Default Server or Third-Party Server.

IP This field is set by the user and relevant only if Third-PartyServer is selected from the FTP Setting drop-down list.

User Name This field is set by the user and relevant only if Third-PartyServer is selected from the FTP Setting drop-down list.

Password This field is set by the user and relevant only if Third-PartyServer is selected from the FTP Setting drop-down list.



184

15 Commissioning the NodeB Equipment

About This Chapter

This chapter describes how to commission the NodeB equipment by sending transparentmessages and performing COM port redirection.

15.1 Starting the Serial Port RedirectionYou can start the serial port redirection to obtain the operating status of the system for clearingthe faults in a board.

15.2 Starting CANBUS RedirectionThis section describes the procedure for starting CANBUS redirection to learn the running stateof the system for further diagnosis of board faults.

15.3 Sending Transparent MessagesThis section describes how to send transparent message. Transparent messages are categorizedinto simulated and board test messages. The transparent messages are sent directly from theLMT to the host without processing. The response from the host provides information forlocating faults and commissioning.

15.4 Interface Reference for Commissioning the NodeB EquipmentThis section describes the interface reference for commissioning the NodeB equipment.

NodeBLMT User Guide 15 Commissioning the NodeB Equipment


185

15.1 Starting the Serial Port RedirectionYou can start the serial port redirection to obtain the operating status of the system for clearingthe faults in a board.

Contextl The default save path of the output information is LMT installation directory\client\output

\NodeB\LMT software version\NodeB test.l The default file name is Commredirect_year-month-day-hour-minute-second.l The file is automatically saved in .txt format.l There are two types of serial port redirection, which are out-band serial port redirection

and non out-band serial port redirection. When the BBU Board Maintenance Link Failurealarm is reported, the serial port information of the disconnected board can be traced onlythrough the out-band serial port redirection. In normal cases, the non out-band serial portredirection is recommended, because you can specify a program module of the board toperform the serial port redirection.

l The serial port redirection can be simultaneously performed on a maximum of 10 boards.For each board, a maximum of one users can start the serial port redirection task at the sametime.

l The information of each task is displayed on a new tab page that is arranged in cascadingmode in the window.

Procedure

Step 1 On the LMT, select Test > Start CommRedirect. The Config Command Redirect dialog boxis displayed.

Step 2 Set the parameters in the dialog box. For the parameter details, see 15.4.1 Interface Referencefor Setting the Serial Port Redirection.

Step 3 Click OK. A dialog box is displayed. The information in the displayed dialog box helps to locatethe fault(s) in a specified board.

----End

15.2 Starting CANBUS RedirectionThis section describes the procedure for starting CANBUS redirection to learn the running stateof the system for further diagnosis of board faults.


version number\NodeB test.l The default file name is . Commredirect_year-month-day-hour-minute-second.txt.l The extension name of the file automatically saved is .txt.l The COM port redirection can be performed simultaneously on 10 boards maximum. For

each board, a maximum of one users are allowed to start this task simultaneously.



186

l The information of each task is displayed on a new tab page that is arranged in cascadingmode in the window.

Procedure

Step 1 In the Local Maintenance Terminal window, select Test > CANBUS Redirect. The ConfigCommand Redirect dialog box is displayed.

Step 2 Set the corresponding parameters in the dialog box. For the parameter details, see15.4.3Interface Reference for Setting the Serial Port Redirection.

Step 3 Click OK.If information about the corresponding serial port is displayed on the maintenance console, theredirection has succeeded.

Step 4 In the Local Maintenance Terminal window, select Test > SerialCmd. The SerialCmd dialogbox is displayed, see 15.4.4 Interface Reference for SerialCmd .

Step 5 Type the serial port command. The execution result is displayed in the serial port redirectionwindow. Locate the board fault based on the execution result.

----End

15.3 Sending Transparent MessagesThis section describes how to send transparent message. Transparent messages are categorizedinto simulated and board test messages. The transparent messages are sent directly from theLMT to the host without processing. The response from the host provides information forlocating faults and commissioning.

ContextNOTE

The function of an analog message is to trigger an event. To obtain the response from the host, use theCOM port redirection or message tracing function.

Procedure

Step 1 Select Test > Transparent Message. The Transparent Message dialog box is displayed.

Step 2 Set the corresponding parameters in the dialog box. For the parameter details, see 15.4.2Interface Reference for Transparent Messages.

Step 3 Click OK. A dialog box is displayed, indicating whether the messages are sent successfully.

----End

15.4 Interface Reference for Commissioning the NodeBEquipment

This section describes the interface reference for commissioning the NodeB equipment.



187

15.4.1 Interface Reference for Setting the Serial Port RedirectionThis section describes the parameters for the serial port redirection.

Field Description

Cabinet No. Indicates the cabinet number of the board.

Frame No. Indicates the frame number of the board.

Slot No. Indicates the slot number of the board.

Cpu ID CPU number of the board.

15.4.2 Interface Reference for Transparent MessagesThis section describes the interface reference for sending transparent messages.

Field Description

Message Type You can choose: Board Test and Simulative Message.

Sender CPU ID The sender CPU ID is valid when the message type is SimulativeMessage.

Sender PID The sender PID is valid when the message type is Simulative Message.

Receiver CPU ID CPU ID of the receiver

Receiver PID PID of the receiver

Message Body Content of the message is displayed in hex format.

15.4.3 Interface Reference for Setting the Serial Port RedirectionThis section describes the parameters for the CANBUS redirection.

Field Description




Redirect Type This can be set to Board or CBUS.

Baud Rate Default value: BAUD_9600.

Cpu ID CPU number of the board.



188

15.4.4 Interface Reference for SerialCmdThis section describes the parameters for the SerialCmd.

Field Description




Message Body Type the serial port command.



189


About This Chapter

This section describes how to manage NodeB frequency spectrum scanning. This task enablesusers to view information about frequency spectrum with information about the time domainand frequency domain during operation collected. This task also enables users to reviewfrequency spectrum history.

ContextHigh-precision online carrier scanning scans cell frequencies in current use for interference,including a small number of frequency sidebands. Wideband online carrier scanning scans acontinuous frequency spectrum within a certain range, including all frequencies in current useand the frequency spectrum between the frequencies. All-spectrum scanning scans offline anentire frequency spectrum that an RF can work on.

NOTEThe cell must be deactivated before offline frequency spectrum scanning. For a multi-mode cell, all cellsin different modes must be deactivated.

ProcedureStep 1 In the navigation pane of the Local Maintenance Terminal window, click the Maintenance

tab.

Step 2 Double-click Spectrum > FFT Frequency Scan. The FFT Frequency Scan dialog box isdisplayed.

For detailed description of parameters in the FFT Frequency Scan dialog box, see16.1Interface Reference for FFT Frequency Spectrum Scanning.

Step 3 Set parameters in the dialog box.

Step 4 Click OK and the frequency spectrum scanning result is displayed in the Chart tab page.

Step 5 Review saved frequency spectrum information by using the frequency spectrum review tool.

----End

NodeBLMT User Guide 16 Managing NodeB Frequency Spectrum Scanning


190

16.1 Interface Reference for FFT Frequency Spectrum ScanningThis section describes the interface reference for FFT frequency spectrum scanning.



191

16.1 Interface Reference for FFT Frequency SpectrumScanning

This section describes the interface reference for FFT frequency spectrum scanning.

Field Description

Cabinet No. Number of the cabinet housing the TRX board to bescanned.

Subrack No. Number of the subrack housing the TRX board to bescanned.

Slot No. Number of the slot housing the TRX board to bescanned.

Scan Mode Select CARRIER_MODE,CHANNEL_CURRENT_BAND_MODE, orCHANNEL_FULL_BAND_MODE.

Scan Width Value range: 15 to 300. Default value: 100. Unit: kHz.As stipulated by protocols, the minimum accuracy is100 kHz. You are advised to retain the default value100 kHz for this parameter.

Auto Save When Autosave is selected, the frequency spectruminformation are automatically saved in the default path.You can also specify another path for saving thereported messages.



192

node b lmt user guide for huawei systems

Documents