NodeB Commissioning Guide(V200_04)

8/22/2019 NodeB Commissioning Guide(V200_04)

http://slidepdf.com/reader/full/nodeb-commissioning-guidev20004 1/75

NodeB

V200

Commissioning Guide

Issue 04

Date 2009-01-22

Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.



Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any

assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but the statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and Confidential


http://www.huawei.com/



Contents

About This Document.....................................................................................................................1

1 Changes in the NodeB Commissioning Guide....................................................................1-1

2 Commissioning the NodeB (Method 1).................................................................................2-1

2.1 Procedure for Commissioning the NodeB (Method 1)...................................................................................2-2

2.2 Upgrading the NodeB Software and Downloading the Data Configuration File............................................2-4

2.3 Checking the Status of the NodeB Hardware and Rectifying the Faults........................................................2-7

2.3.1 Checking the Status of LEDs.................................................................................................................2-7

2.3.2 Rectifying the Common Faults..............................................................................................................2-8

2.3.3 Guidelines for Rectifying the Faults....................................................................................................2-10

2.4 Checking the Running Status of the NodeB..................................................................................................2-14


3.1 Procedure for Commissioning the NodeB (Method 2)...................................................................................3-2

3.2 Upgrading the NodeB Software......................................................................................................................3-3

3.2.1 Querying the Active Version of the NodeB...........................................................................................3-4

3.2.2 Downloading the NodeB BootROM......................................................................................................3-4

3.2.3 Activating the NodeB BootROM...........................................................................................................3-7

3.2.4 Downloading the NodeB Software........................................................................................................3-9

3.2.5 Activate the NodeB Software...............................................................................................................3-12

3.3 Downloading the NodeB Data Configuration File........................................................................................3-15

3.4 Checking the Running Status of the NodeB..................................................................................................3-17

3.4.1 Commissioning SNTP..........................................................................................................................3-17

3.4.2 Checking the Status of a Cell...............................................................................................................3-18

3.4.3 Measuring the RTWP...........................................................................................................................3-19

3.4.4 Monitoring the Output Power of the NodeB........................................................................................3-20

3.4.5 Handling NodeB Alarms......................................................................................................................3-21


4.1 Flow for Commissioning the NodeB (Method 3)...........................................................................................4-3

4.2 Inf ormation Related to the Commissioning of the NodeB on the M2000......................................................4-5

4.2.1 NodeB Commissioning Items................................................................................................................4-5

4.2.2 Introduction to the NodeB Commissioning Window.............................................................................4-6

4.3 Automatically Searching for NodeBs.............................................................................................................4-8

4.4 Checking Software Version Information on the Server..................................................................................4-9

NodeB

Commissioning Guide Contents

Issue 04 (2009-01-22) Huawei Proprietary and Confidential


i



4.5 Uploading the NodeB Software and BootROM Software..............................................................................4-9

4.6 Creating a NodeB Commissioning Project...................................................................................................4-10

4.7 Managing the NodeB Commissioning Project..............................................................................................4-12

4.7.1 Adjusting the Commissioning Object..................................................................................................4-13

4.7.2 Starting or Stopping a NodeB Commissioning Task...........................................................................4-14

4.7.3 Reuploading the NodeB Configuration File.........................................................................................4-15

4.8 Viewing the NodeB Commissioning Progress..............................................................................................4-15

4.9 Obtaining the NodeB Commissioning Report..............................................................................................4-16

5 Data Sheet for NodeB Commissioning..................................................................................5-1

6 Communication Port for the NodeB.......................................................................................6-1

Index.................................................................................................................................................i-1

Contents

NodeB

Commissioning Guide

ii Huawei Proprietary and Confidential


Issue 04 (2009-01-22)



Figures

Figure 2-1 Flow chart of the NodeB commissioning (method 1)........................................................................2-3

Figure 2-2 Plugging the USB disk into the USB port on the WMPT..................................................................2-6

Figure 2-3 LED status of the common faults.......................................................................................................2-8

Figure 3-1 Flow chart for commissioning the NodeB (method 2).......................................................................3-2

Figure 3-2 Software Update dialog box...............................................................................................................3-5

Figure 3-3 Software Upgrade dialog box...........................................................................................................3-6

Figure 3-4 FTP Setting dialog box.......................................................................................................................3-6

Figure 3-5 Software Update dialog box ........................................................................... ..................................3-8

Figure 3-6 Upgrade BOOTROM dialog box.......................................................................................................3-9

Figure 3-7 Software upgrade dialog box..........................................................................................................3-10

Figure 3-8 Upgrade NodeB Software dialog box............................................................................................3-11

Figure 3-9 FTP Setting dialog box....................................................................................................................3-11

Figure 3-10 Software Update dialog box...........................................................................................................3-13

Figure 3-11 U pgrade NodeB Software dialog box.............................................................................................3-14Figure 3-12 DataConfig File Transfer dialog box..............................................................................................3-15

Figure 3-13 FTP Setting dialog box...................................................................................................................3-16

Figure 3-14 R TWP Measurement dialog box....................................................................................................3-20

Figure 3-15 Output Power Monitoring dialog box.............................................................................................3-21

Figure 4-1 Flow chart of the NodeB commissioning (method 3)........................................................................4-4

Figure 4-2 NodeB Commissioning Window........................................................................................................4-7

NodeB

Commissioning Guide Figures



iii





Tables

Table 2-1 Status of the RUN LED on the WMPT and the LED on the USB disk...............................................2-6

Table 2-2 LED status of the functional NodeB....................................................................................................2-8

Table 2-3 Methods of rectifying the common faults............................................................................................2-9

Table 3-1 Fields in the FTP Setting dialog box..................................................................................................3-7

Table 3-2 Fields in the FTP Setting dialog box................................................................................................3-12

Table 3-3 Fields in the FTP Setting dialog box................................................................................................3-16

Table 4-1 NodeB commissioning items...............................................................................................................4-6

Table 4-2 Interface components of the NodeB Commissioning window...........................................................4-7

Table 5-1 Data sheet for NodeB commissioning..................................................................................................5-1

Table 6-1 Numbers of the communication port for the NodeB services..............................................................6-1

NodeB

Commissioning Guide Tables



v





About This Document

Overview

This document describes the guidelines for commissioning and verifying the NodeB after it is

installed. The commissioning and verification guidelines involves upgrading the software,

downloading the data configuration file, and checking the hardware installation and the running

status of the NodeB. These guidelines ensure that the NodeB operates as required.

Product Version

The following table lists the product versions related to this document.

Product Name Product Version

BTS3900 WCDMA (hereafter referred to

as BTS3900)

V200R010

V200R011

BTS3900A WCDMA (hereafter referred to

as BTS3900A)

V200R010

V200R011

DBS3900 WCDMA (hereafter referred to

as DBS3900)

V200R010

V200R011

iDBS3900 WCDMA (hereafter referred to

as iDBS3900)

V200R010

V200R011

Intended Audience

This document is intended for field engineers.

Change History

For changes in the document, see 1 Changes in the NodeB Commissioning Guide.

Organization

1 Changes in the NodeB Commissioning Guide

This describes the changes in the NodeB Commissioning Guide.

NodeB

Commissioning Guide About This Document



1



2 Commissioning the NodeB (Method 1)

This describes how to commission the NodeB by using method 1. You can upgrade the software

and download the data configuration file from the USB disk, and query the running status of the

NodeB on the M2000 to commission the NodeB.


This describes how to commission the NodeB by using method 2. You can upgrade the software,

download the data configuration file, and query the running state of the NodeB on the NodeB

LMT.


This describes how to commission the NodeB by using method 3. You can perform the remote

commissioning for multiple NodeBs on the M2000 in the equipment room. The commissioning

items such as upgrading the software, downloading the data configuration file, and health check

are performed on the M2000 automatically.

5 Data Sheet for NodeB Commissioning

The data sheet for NodeB commissioning is used to record the process and results of the

commissioning.

6 Communication Port for the NodeB

Conventions

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

avoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, which

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

time.

Provides additional information to emphasize or supplement

important points of the main text.

General Conventions

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

About This Document

NodeB

Commissioning Guide

2 Huawei Proprietary and Confidential


Issue 04 (2009-01-22)



Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Courier New.

Command Conventions

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

Convention DescriptionBoldface 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 by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

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

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

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

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK .

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder .

Keyboard Operations

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

NodeB

Commissioning Guide About This Document



3



Format Description

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

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse Operations

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

Action Description

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

Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

About This Document

NodeB

Commissioning Guide

4 Huawei Proprietary and Confidential


Issue 04 (2009-01-22)



1 Changes in the NodeB Commissioning

Guide

This describes the changes in the NodeB Commissioning Guide.

04 (2009-01-22)

This is the third commercial release.

Compared with issue 03 (2008-12-15), this issue adds the following new topics:

Information related to 4 Commissioning the NodeB (Method 3).

Compared with issue 03 (2008-12-15), this issue incorporates the following changes:

2 Commissioning the NodeB (Method 1) is optimized.

03 (2008-12-15)

This is the second commercial release.


Information related to 3 Commissioning the NodeB (Method 2).


2.3 Checking the Status of the NodeB Hardware and Rectifying the Faults is optimized.

02 (2008-08-15)

This is the first commercial release.


l 2.2 Upgrading the NodeB Software and Downloading the Data Configuration File

l 2.3 Checking the Status of the NodeB Hardware and Rectifying the Faults


l The NodeB commissioning procedure is optimized.

l The method for checking the running status of the NodeB is optimized.

NodeB

Commissioning Guide 1 Changes in the NodeB Commissioning Guide



1-1



Compared with issue 01 (2008-03-30), this issue deletes the following topics:

l Upgrading the NodeB Software

l Downloading the NodeB Data Configuration File

l

Initially Activating the NodeB License

01 (2008-03-30)

This is the field trial release.

1 Changes in the NodeB Commissioning Guide

NodeB

Commissioning Guide

1-2 Huawei Proprietary and Confidential


Issue 04 (2009-01-22)




About This Chapter

This describes how to commission the NodeB by using method 1. You can upgrade the software

and download the data configuration file from the USB disk, and query the running status of the

NodeB on the M2000 to commission the NodeB.

2.1 Procedur e for Commissioning the NodeB (Method 1)

This describes the procedure for commissioning the NodeB. At the local end of the BTS, you

can upgrade the software and download the data configuration file for the NodeB from the USB

disk, and check the status of the LEDs to find whether the equipment is functional. After the

local operation is complete, you can check the operating status of the NodeB on the M2000.

2.2 Upgrading the NodeB Software and Downloading the Data Configuration File

This describes how to upgrade the NodeB software and download the data configuration file.

The NodeB can upgrade the software and download the data configuration file directly from the

USB disk. The software is automatically activated and the NodeB is reset when the data

configuration file is downloaded.

2.3 Checking the Status of the NodeB Hardware and Rectifying the Faults

This describes how to check the NodeB hardware installation and how to rectify the faults. You

can locate the hardware faults regarding external ports and CPRI optical cable connection by

checking the LEDs on the boards of the BBU or the auxiliary devices, and rectify faults in time.

2.4 Checking the Running Status of the NodeB

This describes how to check the running status of the NodeB by analyzing the commissioningreport of the NodeB.

NodeB

Commissioning Guide 2 Commissioning the NodeB (Method 1)



2-1



2.1 Procedure for Commissioning the NodeB (Method 1)

This describes the procedure for commissioning the NodeB. At the local end of the BTS, you

can upgrade the software and download the data configuration file for the NodeB from the USB

disk, and check the status of the LEDs to find whether the equipment is functional. After the

local operation is complete, you can check the operating status of the NodeB on the M2000.

Prerequisite

Before commissioning the NodeB, theNodeB, RNC, and M2000 must meet the following

requirements:

l The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary

devices, is installed and passes the installation check. The NodeB passes a power-on status

check and is powered on.

l The hardware of the RNC is installed and commissioned, and the system works properly.

The negotiated data of the NodeB to be commissioned is configured, and is recorded.

l The adaptation layer which is corresponding to the NodeB to be commissioned is installed

on the M2000 server.

Method 1 of the commissioning should meet the following requirements:

l The USB disk with a LED is ready. The required NodeB software, BootROM software,

and data configuration file are stored in the USB memory disk.

NOTE

The data in the configuration file must be consistent with the actual configuration data.

CAUTION

l It is recommended that you use the USB disk that meets the following requirements:

When the USB disk is not performing the read and write operations, the status of the

LED on the USB disk is ON. When the USB disk is performing the read and write

operations, the status of the LED on the USB disk is blinking.

l You should test the USB disk before using it. Do as follows to test the USB disk: Insert

the USB disk into the PC, and then wait 30 seconds. If the LED on the USB disk is ON,

it indicates that the USB disk is functional. Otherwise, replace the USB disk.

l After the NodeB software, BootROM software, and data configuration file aredownloaded from the PC by the USB disk, unplug the USB disk according to the system

prompt. Otherwise, errors may occur when the USB disk is used.

Flow chart of the Commissioning

Figure 2-1 shows the flow chart of the NodeB commissioning.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Figure 2-1 Flow chart of the NodeB commissioning (method 1)

NOTE

l Local commissioning: refers to the process in which an engineer at the NodeB site upgrades the

software, downloads the data configuration file from the USB disk, and checks the status of the

NodeB hardware.

l Remote commissioning: refers to the operations which an engineer performs in the central equipment

room, such as checking the running status of the NodeB on the M2000 server and obtaining thecommissioning report.

NodeB




2-3



Procedure

Step 1 Perform the next step based on the current NodeB software version and data configuration.

If... Then...

The current software version and data

configuration are inconsistent with those to

be used

Go to Step 2.


configuration are consistent with those to be

used

Go to Step 3.

Step 2 Upgrade the NodeB software and download the data configuration file from the USB disk. For

details, see 2.2 Upgrading the NodeB Software and Downloading the Data Configuration

File.

Step 3 Check whether the NodeB hardware is normal based on the LED status. For details, see 2.3

Checking the Status of the NodeB Hardware and Rectifying the Faults.

Step 4 Wait till the transmission is available.

Step 5 Create the NodeB commissioning project on the M2000. Select Health Check. The M2000

checks the running status of the NodeB automatically. For details about how to create the

NodeB commissioning project, see 4.6 Creating a NodeB Commissioning Project.

Step 6 Obtain the NodeB commissioning report on the M2000. For details, see 4.9 Obtaining the

NodeB Commissioning Report.

Step 7 Check the running status of the NodeB by viewing the NodeB commissioning report. For details,

see 2.4 Checking the Running Status of the NodeB.

Step 8 Record the commissioning process and problems that occur during the commissioning in 5 Data

Sheet for NodeB Commissioning, and then export the commissioning report.

----End

2.2 Upgrading the NodeB Software and Downloading theData Configuration File

This describes how to upgrade the NodeB software and download the data configuration file.The NodeB can upgrade the software and download the data configuration file directly from the

USB disk. The software is automatically activated and the NodeB is reset when the data

configuration file is downloaded.

Prerequisite

l The NodeB passes a power-on status check and is powered on.

l The USB disk is available, and the software to be upgraded and the data configuration file

to be downloaded are stored in the USB disk.

NOTE

The data configuration downloaded from the USB disk must be consistent with the actualconfiguration.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



CAUTION

l It is recommended that you use the USB disk that meets the following requirements:

When the USB disk is not performing the read and write operations, the status of theLED on the USB disk is ON. When the USB disk is performing the read and write

operations, the status of the LED on the USB disk is blinking.

l You should test the USB disk before using it. Do as follows to test the USB disk: Insert

the USB disk into the PC, and then wait 30 seconds. If the LED on the USB disk is ON,

it indicates that the USB disk is functional. Otherwise, replace the USB disk.

l After the NodeB software, BootROM software, and data configuration file are

downloaded from the PC by the USB disk, unplug the USB disk according to the system

prompt. Otherwise, errors may occur when the USB disk is used.

Context

When the USB disk is plugged into the corresponding port on the WMPT of the BBU3900, the

BBU3900 automatically detects the USB disk and installs the USB disk driver. After the

installation, the BBU3900 automatically reads the related software and data configuration file

under the fixed directory and verifies their names and formats.

The file names, formats, and save paths in the USB disk are listed as follows:

l NodeB software\\NodeB\Software\Software.csp

l BootROM software:\\NodeB\Software\Firmware.csp

l Data configuration file:\\NodeB\Configuration\NodeBCfg.xml

You should pay attention to the following situations when you upgrade the software and

download data configuration file from the USB disk:

l By default, the download method of the USB disk is downloading by configuration. The

USB disk supports additional download. For example: When the RRU is not connected to

the BBU3900 through the optical cable, the software related to the RRU are not

downloaded. After the RRU is connected to the BBU3900, the software related to the RRU

are automatically downloaded from the USB disk.

l If there is only the software in the USB disk, the NodeB automatically upgrades the

software.

l

If there is only the data configuration file in the USB disk, the NodeB automaticallydownloads the data configuration file.

l If any of the following situations occurs, the NodeB does not upgrade the software or

download the data configuration file from the USB disk.

– The directory or the file does not exist.

– The file format is not correct.

– The software version to be used is the same as the current software version.

– The data configuration file is consistent with the current configuration.

After plugging the USB disk into the USB port on the WMPT, for the status of the LED on the

USB disk and the RUN LED on the WMPT, see Table 2-1.

NodeB




2-5



Table 2-1 Status of the RUN LED on the WMPT and the LED on the USB disk

Status of the LEDon the USB disk

Status of the RUNLED on the WMPT

Duration

Plug the USB disk

into the USB port and

detect the USB disk

automatically.

ON Blinking (ON for 1s,

OFF for 1s)

About 1 second to 2

seconds

Download the

software and data

configuration file

from the USB disk.

Blinking Blinking (ON for

0.125s, OFF for

0.125s)

About 12 minutes

Activating the

software

ON Blinking (ON for

0.125s, OFF for

0.125s)

About 3 minutes to 4

minutes

Reset the NodeB. ON first, OFF for a

while, and then

blinking

ON first, OFF for a

while, and then

blinking (ON for

0.125s, OFF for

0.125s)

About 2 minutes

The NodeB functions

properly.

ON Blinking (ON for 1s,

OFF for 1s)

-

NOTE

For different versions and configuration, the time for downloading the software and data configuration file

from the USB disk and the time for activating the NodeB software may be differ from the time showed in

the Table 2-1.

Procedure

Step 1 Plug the USB disk into the USB port on the WMPT of the BBU3900, as shown in Figure 2-2.

Figure 2-2 Plugging the USB disk into the USB port on the WMPT


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Step 2 Wait until the software and data configuration file are downloaded, the software is automatically

activated, and the NodeB is reset.

NOTE

l The RUN LED on the WMPT blinks (ON for 0.125s, OFF for 0.125s) during the download of the

software and data configuration file from the USB disk. After the download is complete, the software

is automatically activated and the NodeB is reset. When the NodeB works properly, the RUN LED on

the WMPT blinks (ON for 1s, OFF for 1s).

l The procedure of downloading the software and data configuration file, activating the software, and

resetting the NodeB can be determined by the status of the RUN LED on the WMPT. For more details,

see Table 2-1. During the procedure, you do not need to observe the status of other LEDs on the WMPT

and status of LEDs on other boards.

Step 3 Unplug the USB disk after you finish all the NodeB local operations including upgrading the

software, downloading the data configuration file, and 2.3 Checking the Status of the NodeB

Hardware and Rectifying the Faults.

----End

2.3 Checking the Status of the NodeB Hardware andRectifying the Faults

This describes how to check the NodeB hardware installation and how to rectify the faults. You

can locate the hardware faults regarding external ports and CPRI optical cable connection by

checking the LEDs on the boards of the BBU or the auxiliary devices, and rectify faults in time.

Prerequisite

l The NodeB passes a power-on status check and is powered on.

l The software is upgraded and the data configuration file is downloaded. The software is

successfully activated and the NodeB is reset.

2.3.1 Checking the Status of LEDs

This describes how to check the status of LEDs. By checking the status of LEDs on the boards

of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 is functional.

2.3.2 Rectifying the Common Faults

This describes how to rectify common faults when the LED indicates faults in the USB disk or

in the boards of the NodeB.

2.3.3 Guidelines for Rectifying the Faults

This describes how to clear the faults according to the Guidelines for Rectifying the Faults.

2.3.1 Checking the Status of LEDs

This describes how to check the status of LEDs. By checking the status of LEDs on the boards

of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 is functional.

LED status of the functional NodeB

If the LED status of the BBU3900 boards and auxiliary devices are the same as that shown inTable 2-2, the NodeB is functional.

NodeB




2-7



Table 2-2 LED status of the functional NodeB

LED Status

LED on the USB disk ON

RUN LED on each BBU board Blinking (ON for 1s and OFF for 1s)

ALM LEDs on the WMPT/WBBP/UTRP/

PMU/AFMU/EMU/EMUA

OFF

CPRI LEDs on the WBBP ON (green)

STATE LED on the UBFA Blinking (green)

VSWR LED on the RRU or the WRFU OFF

LED Status of the Common FaultsNOTE

If the LED indicates faults in the USB disk or in the boards of the NodeB, rectify the faults according to

2.3.2 Rectifying the Common Faults. If the fault is not described in 2.3.2 Rectifying the Common

Faults, rectify the fault according to 2.3.3 Guidelines for Rectifying the Faults.

Figure 2-3 LED status of the common faults

2.3.2 Rectifying the Common Faults

This describes how to rectify common faults when the LED indicates faults in the USB disk or

in the boards of the NodeB.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Context

Table 2-3 Methods of rectifying the common faults

If... You can inferthat... Then...

The LED on the

USB disk is OFF

The NodeB

software fails to be

upgraded from the

USB disk.

Insert the USB disk again, and upgrade the

software.

If the software fails to be upgraded again, record

the problem in the data sheet for the NodeB

commissioning, and then upgrade the software on

the LMT.

RUN LED on

each BBU board

blinks (ON for

0.125s, OFF for

0.125s)

The software is

being loaded or the

board is wrongly

positioned in the

slot of another

board.

Wait five minutes and then check the status of the

RUN LED again.

If the RUN LED still blinks (ON for 0.125s, OFFfor 0.125s), check whether the board is positioned

in the correct slot. If not, reinstall the board.

The ALM LED

on the WMPT,

WBBP, or UTRP

is ON

The board is faulty. Reinstall the board to check whether the fault is

rectified. If the ALM LED still blinks, replace the

board.

The ALM LED

on the active

WMPT blinks

The external port

on the active

WMPT is faulty.

l Check whether the RUN LED on the PMU,

AFMU, EMU, or EMUA blinks (ON for 0.125s,

OFF for 0.125s). If the RUN LED on those

boards blinks (ON for 0.125s, OFF for 0.125s),check whether the RS485 signal cable is

connected properly.

l Check whether the dry contact alarm signal

cable is properly connected to the corresponding

port on the UPEU.

If the fault persists, record the fault and the LED

status of the WMPT in the data sheet for the NodeB

commissioning. Then, rectify the fault on the LMT

or M2000.

A CPRI LED onthe WBBP is ON

(red)

The CPRI opticalcable is improperly

connected, or the

optical module is

out of position.

l

Check whether the optical module is installed.If not, install the optical module.

l Check whether the CPRI optical cable is

improperly connected, for example, the receive

end and the transmit end are reversed. If it is

improperly connected, reinstall it. Then, wait 30

seconds, and then check the status of the CPRI

LED again.


damaged. If it is damaged, replace it.

NodeB




2-9



If... You can inferthat...

Then...

CPRI LED on the

WBBP blinks

(red, ON for

0.25s, OFF for

0.25s)

The RRU or the

WRFU is faulty.

Check whether an ALM LED on the RRU or the

WRFU is ON. If an LED is ON, power on the RRU

or the WRFU again. If the fault persists, replace the

RRU or the WRFU.

CPRI LED on the

WBBP (red, ON

for 1s, OFF for

1s)

There is a VSWR

alarm, an antenna

alarm or an external

alarm on the RRU

or the WRFU.

l Check whether a VSWR LED on the RRU or the

WRFU is OFF. If the VSWR LED is not OFF,

see 2.3.3 Guidelines for Rectifying the

Faults to rectify the fault.

l Check whether a ALM LED on the RRU or the

WRFU blinks. If it blinks, then:

– Check whether the antenna devices are

properly connected to the RRU or the WRFU.

– Check whether there is an external dry

contact alarm on the RRU or the WRFU. If

there is an external dry contact alarm, record

the alarm in the data sheet for the NodeB

commissioning.

2.3.3 Guidelines for Rectifying the Faults

This describes how to clear the faults according to the Guidelines for Rectifying the Faults.

Procedure

Step 1 Check the RUN LED status on each board of the BBU3900, and perform the next step based on

the status of the RUN LED.

If the RUN LEDIs...

You can inferthat...

Then...

Blinking (ON for 1s,

OFF for 1s)

The board works

properly.

Go to Step 2.

ON The power supply is

available but the board is faulty.

Reinstall the board to check whether the fault

is rectified. If the fault persists, replace the board.

Blinking (ON for

0.125s, OFF for

0.125s)

The software is

being loaded or the

board is wrongly

positioned in the slot

of another board.

Wait five minutes and then check the status of

the RUN LED again.

If the RUN LED still blinks (ON for 0.125s,

OFF for 0.125s), check whether the board is

positioned in the correct slot. If not, reinstall

the board.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



If the RUN LEDIs...


Then...

OFF The power supply is

unavailable or the

board is faulty.

l Check whether the NodeB is powered on.

l Reinstall the board to check whether thefault is rectified. If the fault persists, replace

the board.

Step 2 Check the ALM LED status on the active WMPT, and perform the next step based on the status

of the ALM LED.

If the ALM LEDIs...


Then...

OFF The board works

properly.

Go to Step 3.

ON The active WMPT isfaulty.

Reinstall the board to check whether the faultis rectified. If the fault persists, replace the

board.

Blinking The external port on

the active WMPT is

faulty.

If the fault persists, record the fault and the

LED status of the WMPT in the data sheet for

the NodeB commissioning. Then, rectify the

fault on the LMT or M2000.

l Check whether the RUN LEDs on other

boards blink (ON for 0.125s, OFF for

0.125s).

–

If the RUN LEDs on the PMU, AFMU,EMU, or EMUA blink (ON for 0.125s,

OFF for 0.125s), check whether the

RS485 signal cable is properly

connected.

– If the RUN LEDs on the standby WMPT,

WBBP, or UTRP blink (ON for 0.125s,

OFF for 0.125s), reinstall the board to

check whether the fault is cleared.

l Check whether the dry contact alarm signal

cable is properly connected to the

corresponding port on the UPEU.

l Reinstall the active WMPT to check

whether the fault is cleared.

l Reinstall the WBBP or the UTRP to check

whether the fault is cleared.

l If the GPS antenna system is configured,

check whether it is properly connected.

Step 3 Check the ALM LED status of the WBBP, UTRP and standby WMPT, and perform the next

step based on the status of the ALM LED.

NodeB




2-11



If the ALM LEDIs...


Then...

OFF The board works

properly.

Go to Step 4.

ON The board is faulty. Reinstall the board to check whether the fault

is rectified. If the fault persists, replace the

board.

Blinking The ports between

the active WMPT

and the other BBU

boards are faulty.

Reinstall the board to check whether the fault


board.

Step 4 Check the CPRI LED status of the WBBP, and perform the next step based on the status of the

CPRI LED.

If the CPRI LEDIs...


Then...

ON (green) The CPRI optical

cable is properly

connected, and the

RRU or the WRFU

works properly.

Go to Step 5.

OFF The CPRI port is not

configured.

Check whether the optical module is properly

connected to the configured CPRI port. If not,

reinstall the optical module to connect it to the

correct CPRI port.

ON (red) The CPRI optical

cable is improperly

connected, or the

optical module is

out of position.

l Check whether the optical module is

installed. If not, install the optical module.


improperly connected, for example, the

receive end and the transmit end are

reversed. If it is improperly connected,

reinstall it. Then, wait 30 seconds, and then

check the status of the CPRI LED again.


damaged. If it is damaged, replace it.

Blinking at 2 Hz

(red, 0.25s ON,

0.25s OFF)

The RRU or the

WRFU is faulty.

Check whether an ALM LED on the RRU or

the WRFU is ON. If the ALM LED is ON,

power on the RRU or the WRFU again. If the

fault persists, replace the RRU or the WRFU.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



If the CPRI LEDIs...


Then...

Blinking at 0.5 Hz

(red, 1s ON, 1s OFF)

There is a VSWR

alarm, an antenna

alarm or an external

alarm on the RRU or

the WRFU.

l Check whether a VSWR LED on the RRU

or the WRFU is OFF. If the VSWR LED is

not OFF, see Step 7 to rectify the fault.

l Check whether a ALM LED on the RRU or

the WRFU blinks. If it blinks, then:

– Check whether the antenna devices are

properly connected to the RRU or the

WRFU.

– Check whether there is an external dry

contact alarm on the RRU or the WRFU.

If there is an external dry contact alarm,

record the alarm in the data sheet for the

NodeB commissioning.

Step 5 Check the STATE LED status of the UBFA, and perform the next step based on the status of

the STATE LED.

If the STATE LEDIs...


Then...

Blinking (green) The board works

properly.

Go to Step 6.

Blinking (red) The board is faulty. Reinstall the board to check whether the fault


board.

Step 6 Check the ALM LED status of the PMU, AFMU, EMU or EMUA, and perform the next step

based on the status of the ALM LED.

If the ALM LEDIs...


Then...

OFF The module or the

device works

properly.

Go to Step 7.

ON The module or the

device is faulty.

Reinstall the module or power on the device

again to check whether the fault is cleared. If the fault persists, record the fault and the LED

status in the Data Sheet for NodeB

Commissioning. Then, clear the fault on the

LMT or M2000.

Step 7 Check the VSWR LED status of the RRU or the WRFU, and perform the next step based on the

status of the VSWR LED.

NodeB




2-13



If the VSWR LEDIs...


Then...

OFF No VSWR alarm is

generated.

Go to Step 8.

Blinking (ON for

0.125s, OFF for

0.125s)

There are alarms on

the ANT_TX/RXA

port and ANT_RXB

port.

Check whether the antenna system is properly

connected to the RRU or the WRFU.

ON There is an alarm on

the ANT_TX/RXA

port.

Blinking (ON for 1s,

OFF for 1s)

There is an alarm on

the ANT_RXB port.

Step 8 Check the transmission status of the NodeB.

If... Then...

The NodeB uses the E1

transmission mode

Perform the E1 loopback test. If the ALM LED on the board

with the E1 port blinks, the E1 port at the NodeB side is

properly connected.

The NodeB uses the FE

transmission mode

Check the status of the green indicator on the FE port. If the

green LED blinks, the FE port is properly connected.

----End


This describes how to check the running status of the NodeB by analyzing the commissioning

report of the NodeB.

Prerequisite

l The NodeB hardware installation is checked. The transmission links connected to the RNC

are ready. The current version of the related software and data configuration file is

consistent with the requirement.

l You have logged in to the M2000 client, and created the NodeB. The NodeB commissioning

project is complete, and the NodeB commissioning report is obtained.

NOTE

In the list of commissioned NodeBs, the check report of the NodeB whose Percent is 100% is

complete.

Procedure

Step 1 Open the obtained NodeB commissioning report and check the content of the report. In this way,

you can check the running status of the NodeB.

Step 2 Handle the existing alarms based on the commissioning report.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



If... Then...

An alarm is generated Handle the alarm according to the Alarm

Reference.

An active alarm cannot be cleared Record the alarm in the 5 Data Sheet forNodeB Commissioning.

----End

NodeB




2-15






About This Chapter

This describes how to commission the NodeB by using method 2. You can upgrade the software,

download the data configuration file, and query the running state of the NodeB on the NodeB

LMT.

3.1 Procedur e for Commissioning the NodeB (Method 2)

This describes how to commission the NodeB by using method 2. After the NodeB hardware

installation, you can commission the NodeB.

3.2 Upgrading the NodeB Software

This describes how to upgrade the NodeB software by downloading and activating the NodeBBootROM and NodeB software.

3.3 Downloading the NodeB Data Configuration File

This describes how to download the NodeB data configuration file from the FTP server to the

NodeB. The downloaded data configuration files take effect after the NodeB is reset.


This describes how to check the running status of the NodeB for the purpose of rectifying faults

that occur during the operation and ensuring proper operation of the NodeB.

NodeB




3-1



3.1 Procedure for Commissioning the NodeB (Method 2)This describes how to commission the NodeB by using method 2. After the NodeB hardware


Prerequisite

Before commissioning the NodeB, the NodeB, RNC, and M2000 must meet the following

requirements:






l The version of the M2000 is compatible with the NodeB to be commissioned.

Flow Chart


Figure 3-1 Flow chart for commissioning the NodeB (method 2)


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Procedure

Step 1 Perform the next step based on the current NodeB software version and data configuration.If... Then...


configuration are inconsistent with those to

be used

Go to Step 2.


configuration are consistent with those to be

used

Go to Step 3.

Step 2 Upgrade the NodeB software and download data configuration file on the LMT. For details, see

3.2 Upgrading the NodeB Software and 3.3 Downloading the NodeB Data ConfigurationFile.

Step 3 Check the running status of the NodeB. For details, see 3.4 Checking the Running Status of

the NodeB.



----End

3.2 Upgrading the NodeB Software

This describes how to upgrade the NodeB software by downloading and activating the NodeB

BootROM and NodeB software.

3.2.1 Querying the Active Version of the NodeB

This describes how to query the active version of the NodeB. Before upgrading the NodeB

software, you should query the information of the active software version.

3.2.2 Downloading the NodeB BootROM

This describes how to download the NodeB BootROM software from the FTP server to the

temporary directory on the main processing board and then to the related boards.

3.2.3 Activating the NodeB BootROM

This describes how to activate the NodeB BootROM. Activating the BootROM refers that the

main processing board sends the BootROM update command to all the boards that successfully

download the BootROM, and then updates each board BootROM.

3.2.4 Downloading the NodeB Software

This describes how to download the NodeB software from the FTP server to the NodeB. The

NodeB file directories are the active directory and the standby directory. The active directory

saves the running NodeB software version. The standby directory saves the inactive NodeB

software version. After the NodeB software is downloaded, it is saved in the standby directory.

The NodeB software does not take effect immediately or damage the running software.

3.2.5 Activate the NodeB Software

This describes how to switch the standby directory to the active one, and then download the NodeB software to each board and validate it. You can activate the NodeB software right after

NodeB




3-3



the downloading or later on. After the activation, the NodeB is reset. Thus, all the services are

disrupted.

3.2.1 Querying the Active Version of the NodeB

This describes how to query the active version of the NodeB. Before upgrading the NodeB

software, you should query the information of the active software version.

Procedure

Run the LST SOFTWARE command to query the NodeB software version and NodeB

BootROM version.

----End

3.2.2 Downloading the NodeB BootROM

This describes how to download the NodeB BootROM software from the FTP server to the

temporary directory on the main processing board and then to the related boards.

Prerequisite

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.

Procedure

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

Step 2 Double-click Software Management > Software Update. The Software Update dialog box

is displayed, as shown in Figure 3-2.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Figure 3-2 Software Update dialog box

Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed, as shown in Figure 3-3.

NodeB




3-5



Figure 3-3 Software Upgrade dialog box

NOTE

l The system downloads the BootROM package and then activates it.

l You can choose one step each time and the system proceeds with the task you customize.

Step 5 Click Modify. The FTP Setting dialog box is displayed, as shown in Figure 3-4.

Figure 3-4 FTP Setting dialog box


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Table 3-1 describes the fields in the FTP Setting dialog box.

Table 3-1 Fields in the FTP Setting dialog box

Field Description

Use Built-in FTP Server This enables you to decide whether to use a built-in or

a specified FTP server. The built-in FTP server is

started by default.

Use Specified FTP

Server

IP address The FTP server can be started either from the local

computer installed with the LMT application or from

another computer. Here it refers to the IP address of

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

in to the FTP server.

Step 6 Set the FTP server.

Step 7 Click OK . The FTP Setting dialog box is closed and the Upgrade BOOTROM dialog box is

displayed.

Step 8 Select Download BOOTROM Package and then specify a path to download the BootROM

package.

Step 9 Click Next. A dialog box is displayed for your confirmation.

Step 10 Click Yes. The Upgrading Patch Progress dialog box is displayed. The status and progress of

the patch upgrade is displayed in the dialog box. You may check the process by viewing this

dialog box.

----End

3.2.3 Activating the NodeB BootROM

This describes how to activate the NodeB BootROM. Activating the BootROM refers that the

main processing board sends the BootROM update command to all the boards that successfully

download the BootROM, and then updates each board BootROM.

Context

l 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 Because the BootROM does not affect the NodeB services, you need not reset the

NodeB to make the BootROM effective. The NodeB starts with the upgraded BootROM

during next reset.

l After the BootROM is activated, the NodeB is not reset.

NodeB




3-7



Procedure

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

Step 2 Double-click Software Management > Software Update. The Software Update dialog box

is displayed, as shown in Figure 3-5.


Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed, as shown in Figure 3-6.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Figure 3-6 Upgrade BOOTROM dialog box

NOTE

l The system downloads the BootROM package and then activates it.

l You can choose one step each time and the system proceeds with the task you customize.

Step 5 Select Activate BOOTROM.




dialog box.

----End

3.2.4 Downloading the NodeB Software

This describes how to download the NodeB software from the FTP server to the NodeB. The

NodeB file directories are the active directory and the standby directory. The active directory

saves the running NodeB software version. The standby directory saves the inactive NodeB

software version. After the NodeB software is downloaded, it is saved in the standby directory.The NodeB software does not take effect immediately or damage the running software.

NodeB




3-9



Prerequisite

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.

Procedure

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

Step 2 Choose Software Management > Software Update. The Software Upgrade dialog box is

displayed, as shown inFigure 3-7.

Figure 3-7 Software upgrade dialog box

Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed, as shown in Figure 3-8.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Figure 3-8 Upgrade NodeB Software dialog box

Step 5 Click Modify. The FTP Setting dialog box is displayed, as shown in Figure 3-9.


NodeB




3-11





Field Description

Use Built-in FTP Server This enables you to decide whether to use a built-in or a

specified FTP server. The built-in FTP server is selected

by default.

Use Specified FTP

Server

IP

Address

The FTP server can be started either from the local

computer installed with the LMT application or from

another computer. Here it refers to the IP address of the

FTP server.

User

Name

This enables you to specify the user name for logging in

to the FTP server.

Password This enables you to specify the password for logging in

to the FTP server.

Step 6 Set the FTP server.

Step 7 Click OK . The FTP Setting dialog box is closed and the Upgrade NodeB Software dialog box

is displayed.

Step 8 Select Backup Data Configuration File, Download NodeB Software Package, and

Download by Configuration to specify a directory for backing up the file and a directory for

downloading the NodeB software package.

NOTE

l Backup Data Configuration File is optional. It is recommended that you choose 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. Meanwhile

click Effective 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, the dialog box is

displayed to prompt that this may cause the software download failure. Click OK to start the

downloading of the software. Click Cancel to select again, and download the software by configuration.

l Downloading by configuration indicates that you can download all the board software package required

according to the current NodeB configuration. This reduces the total volume of data during

downloading, shortens the time of downloading the software, and saves the storage space for the NodeB.




dialog box.

----End

3.2.5 Activate the NodeB Software

This describes how to switch the standby directory to the active one, and then download the

NodeB software to each board and validate it. You can activate the NodeB software right after

the downloading or later on. After the activation, the NodeB is reset. Thus, all the services aredisrupted.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Procedure

Step 1 Click the Maintenance tab.

Step 2 Double-click Software Management > Software Update. The Software Update dialog boxis displayed, as shown in Figure 3-10.


Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed, as shown in Figure 3-11.

NodeB




3-13



Figure 3-11 Upgrade NodeB Software dialog box

Step 5 Select Activate NodeB Software and select the NodeB software version to be upgraded in the

Version 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. And click

Effective Data Configuration File to confirm its validity before activating the NodeB software.




dialog box.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



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 software

upon activation failure.

----End

3.3 Downloading the NodeB Data Configuration File

This describes how to download the NodeB data configuration file from the FTP server to the

NodeB. The downloaded data configuration files take effect after the NodeB is reset.

Procedure

l In GUI mode

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

2. Double-click Software Management > Data Config File Transfer. The Data

Configuration File Transfer dialog box is displayed, as shown in Figure 3-12.

Figure 3-12 DataConfig File Transfer dialog box

NodeB




3-15



3. Select the Download (FTP Server to NodeB).

4. Click Modify in the dialog box. The FTP Setting dialog box is displayed, as shown

in Figure 3-13.




Field Description

Use Built-in FTP Server This enables you to decide whether to use a

built-in or a specified FTP server. The built-in

FTP server is started by default.

Use Specified FTP

Server

IP address The FTP server can be started either from the

local computer installed with the LMT

application or from another computer. Here it

refers to the IP address of the FTP server.

User

Name

This enables you to specify the user name for

logging in to the FTP server.

Password This enables you to specify the password for logging in to the FTP server.

5. Set the FTP server.

6. Click OK . The FTP Setting dialog box is closed and the DataConfig File

Transfer dialog box is displayed.

7. Set the other parameters in the dialog box.

8. Click Start.

l In MML mode

Run the command DLD CFGFILE.

----End


NodeB

Commissioning Guide



Issue 04 (2009-01-22)




This describes how to check the running status of the NodeB for the purpose of rectifying faults

that occur during the operation and ensuring proper operation of the NodeB.

3.4.1 Commissioning SNTP

This describes how to commission the Simple Network Time Protocol (SNTP) to synchronize

the time between NEs. The task facilitates the centralized maintenance and management.

3.4.2 Checking the Status of a Cell

This describes how to check the status of a local cell or a logical cell. The task helps you to learn

the running state of the active cell and perform OM on the cell.

3.4.3 Measuring the RTWP

The Received Total Wideband Power (RTWP) is the received wideband power in an uplink

channel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.

This describes how to measure the RTWP. You can calibrate the gain of uplink RF channels

through RTWP measurement. The NodeB RTWP test has no negative effect on the services.

3.4.4 Monitoring the Output Power of the NodeB

This describes how to monitor the output power of the NodeB. The output power test measures

the output power of the NodeB, including the typical output power and output power of each

carrier.

3.4.5 Handling NodeB Alarms

This describes how to check active alarms and clear the alarms if any.

3.4.1 Commissioning SNTP

This describes how to commission the Simple Network Time Protocol (SNTP) to synchronize

the time between NEs. The task facilitates the centralized maintenance and management.

Context

Application of the SNTP can synchronize the time (year/month/date/hour/minute/second)

between multiple SNTP clients in real time by using a unique SNTP server.

Procedure

Step 1 Start the SNTP server. An SNTP server can be on the RNC side or on the M2000 server side,

which is determined by the actual condition.

l On the RNC side: Start the SNTP server on the security and monitor manager on the BAM

server.

l On the M2000 server side: The Sun operating system has the self-contained SNTP services.

For details, refer to the M2000 Administrator Guide.

Step 2 Run the SET SNTPCLTPARA command to set the parameters of the SNTP client.

NodeB




3-17



Parameter ID Parameter Name Description

SW Switch of Time Sync Indicates whether synchronization is

required.

Value range: ON (synchronizationrequired), OFF (synchronization not

required)

Default value: none

IP SNTP Server IP Address Value range: 0.0.0.1 to 255.255.255.254

Default value: none

SP Synchronization Period

(minute)

Value range: 1 to 525600

Unit: minute

Default value: none

Step 3 Run the LST SNTPCLTPARA command to check the parameters of the SNTP client.

Step 4 Run the LST SNTPCLTLATESTSUCCDATE command to query the time of latest successful

synchronization of the SNTP client to the SNTP server, and whether the synchronization is

successful.

If... Then...

The synchronization is successful End this task.

The synchronization fails Check the following items:l Whether the SNTP server is started

l Whether the IP address of the NodeB is correct

After the faults are rectified, go to Step 2 to set the

parameters again.

----End

3.4.2 Checking the Status of a Cell

This describes how to check the status of a local cell or a logical cell. The task helps you to learnthe running state of the active cell and perform OM on the cell.

Procedure

Run the DSP LOCELL command to check the status of all local and logical cells of the

NodeB.

If... Then...

The information prompting faults is

displayed

Rectify the faults according to the

information.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



If... Then...

No information prompting faults is

displayed

End the task.

----End

3.4.3 Measuring the RTWP

The Received Total Wideband Power (RTWP) is the received wideband power in an uplink

channel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point.

This describes how to measure the RTWP. You can calibrate the gain of uplink RF channels

through RTWP measurement. The NodeB RTWP test has no negative effect on the services.

PrerequisiteYou have logged in to the NodeB LMT.

Context

Analyses of the RTWP measurement are as follows:

l If the NodeB is not connected to the antenna and feeder system or a matched load, the

RTWP is about –108 dBm. If the NodeB is connected to the antenna and feeder system

(with TMA switched on) or a matched load, the RTWP is about –105 dBm.

l If the services are normal and the uplink load reaches 75%, the RTWP is 6 dB higher than

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

RTWP with the unit of 0.1 dBm.

l When the reported RTWP is invalid, abnormal RTWP curves are displayed. The RTWP for the main

antenna forms a horizontal line at –1120 dBm on the vertical axis. The RTWP for the diversity antenna

forms a horizontal line at –1115 dBm on the vertical axis. The error may lie in the absent WRFU/

RRU/RHUB,a broken link, or a faulty channel. In this case, clear the fault first.

Procedure

Step 1 In the navigation pane of the Local Maintenance Terminal window, click the Maintenancetab.

Step 2 Double-click Realtime Specific Monitoring > RTWP Measurement . The RTWP

Measurement dialog box is displayed, as shown in Figure 3-14.

NodeB




3-19



Figure 3-14 RTWP Measurement dialog box

Step 3 Set the parameters in the dialog box.

Step 4 Click OK . A monitor window is displayed, showing the current monitoring task in graphs.

Step 5 Stop the test in one of the following ways:

If... Then...

You close the monitoring window, All the displayed monitoring tasks are

stopped.

Right-click the task in the task list area and

then choose Delete Task from the shortcut

menu,

The task and its chart are deleted.

----End

3.4.4 Monitoring the Output Power of the NodeB

This describes how to monitor the output power of the NodeB. The output power test measures

the output power of the NodeB, including the typical output power and output power of each

carrier.

Prerequisite

You have logged in to the NodeB LMT.

Context

After the task is started, the system periodically reports the typical output power and each carrier

according to the set reporting interval.

Configuration of the NodeB output power depends on the specified services. If the pilot power

and typical output power are configured, the difference between the WRFU output power andthe pilot power is not large when the NodeB does not carry services. The RRU output should


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



approximates to the pilot power plus 3 dBm. If the RRU output power is lower than the pilot

power by a large amount, the NodeB output power must be abnormal.

WRFU/RRU: The pilot power can be 33 dBm and the typical power can be 43 dBm.

Procedure

Step 1 In the navigation pane of the Local Maintenance Terminal window, click the Maintenance

tab.

Step 2 Double-click Realtime Specific Monitoring > Output Power Monitoring. The Output

Power Monitoring dialog box is displayed, as shown in Figure 3-15.

Figure 3-15 Output Power Monitoring dialog box

Step 3 Set the parameters in the dialog box.

Step 4 Click OK . A monitor window is displayed, showing the current monitoring task in graphs.

Step 5 Stop the test in one of the following ways:

If... Then...

You close the monitoring window, All the displayed monitoring tasks are

stopped.

Right-click the task in the task list area and

then choose Delete Task from the shortcut

menu,

The task and its chart are deleted.

----End

3.4.5 Handling NodeB Alarms

This describes how to check active alarms and clear the alarms if any.

NodeB




3-21



Procedure

Step 1 Run the LST ALMAF command to query the active alarms.

Step 2 Clear the alarms related to the NodeB.

If... Then...

An active NodeB alarm exists Clear the alarm according to the alarm online help.

An active alarm related to the NodeB

cannot be cleared

Record it in 5 Data Sheet for NodeB

Commissioning.

----End


NodeB

Commissioning Guide



Issue 04 (2009-01-22)




About This Chapter

This describes how to commission the NodeB by using method 3. You can perform the remote

commissioning for multiple NodeBs on the M2000 in the equipment room. The commissioning

items such as upgrading the software, downloading the data configuration file, and health check

are performed on the M2000 automatically.

4.1 Flow for Commissioning the NodeB (Method 3)

This describes the flow for commissioning the NodeB in method 3. After the NodeB hardware


4.2 Information Related to the Commissioning of the NodeB on the M2000Before commissioning the NodeB on the M2000, read the following information carefully:

4.3 Automatically Searching for NodeBs

This describes how to automatically search for NodeBs. The automatic searching function helps

you know inf ormation about the NodeBs under an RNC such as the total number of NodeBs

under one RNC, the number of NodeBs that connect to the M2000, the number of NodeBs whose

names are du plicate, and the number of NodeBs whose IP addresses are duplicated.

4.4 Checking Software Version Information on the Server

This describes how to check the software version information saved on the M2000 server. You

can check whether the required NodeB software and BootROM software are uploaded to the

M2000 by checking the software version information.

4.5 Uploading the NodeB Software and BootROM Software

This describes how to upload the well prepared NodeB software and BootROM software on the

M2000 client to the associated path of the M2000 server.

4.6 Creating a NodeB Commissioning Project

This describes how to create a NodeB commissioning project. In this way, the NodeBs that meet

the requirements can automatically perform commissioning. In addition, the information about

the commissioning process is displayed on the M2000 client. When a commissioning project is

created successfully, the M2000 creates a commissioning task for each NodeB in the

commissioning project.

4.7 Managing the NodeB Commissioning Project

This describes how to manage the NodeB commissioning project. To improve thecommissioning efficiency, the M2000 provides the NodeB automatic commissioning function.

NodeB




4-1



Users only need to monitor the commissioning process. After the NodeB commissioning process

is complete, the users obtain and analyze the commission report and check whether the

commissioning process is normal. Through the NodeB commissioning project management

function of the M2000, users can modify the commissioning objects, start or stop the NodeB

commissioning task, or upload the NodeB data configuration file required for the commissioning

again.

4.8 Viewing the NodeB Commissioning Progress

This describes how to view the NodeB commissioning progress. You can obtain the information

about the progress of the commissioning project by viewing the NodeB commissioning project

and the NodeB commissioning task within the project.

4.9 Obtaining the NodeB Commissioning Report

This describes how to obtain the NodeB commissioning report. You can learn the NodeB

commissioning status by viewing the NE commissioning report on the M2000.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



4.1 Flow for Commissioning the NodeB (Method 3)

This describes the flow for commissioning the NodeB in method 3. After the NodeB hardware


Prerequisite

Before commissioning the NodeB, the NodeB, RNC, and M2000 must meet the following

requirements:






l The adaptation layer which is corresponding to the NodeB to be commissioned is installed

on the M2000 server.

Method 3 of the commissioning should meet the following requirements:

l The required NodeB software, BootROM software, and data configuration file are

prepared.

l The transmission and remote OM channel of the NodeB is operational. The NodeB to be

commissioned can be automatically detected on the M2000.

Flow chart of the Commissioning


NodeB




4-3



Figure 4-1 Flow chart of the NodeB commissioning (method 3)

Procedure

Step 1 The M2000 detects the NodeB to be commissioned automatically. For details, see 4.3

Automatically Searching for NodeBs.

If... Then...

The NodeB to be commissioned is detected

automatically

Go to Step 2.

The M2000 fails to detect the NodeB to be

commissioned

The network is faulty. Contact the field

engineers to perform the transmission

commission till the M2000 can detect the

NodeB to be commissioned automatically.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Step 2 Check whether the NodeB software and BootROM software are uploaded to the M2000 server.

For details ,see 4.4 Checking Software Version Information on the Server.

If... Then...

The NodeB software and BootROMsoftware package are uploaded to the M2000

Go to Step 4.

The NodeB software and BootROM

software package fail to be uploaded to the

M2000

Go to Step 3.

Step 3 Upload the NodeB software and BootROM software to the M2000 server. For details, see 4.5

Uploading the NodeB Software and BootROM Software.

Step 4 Create the NodeB commissioning project on the M2000. For details, see 4.6 Creating a NodeB

Commissioning Project.

Step 5 The M2000 performs the specified commissioning items automatically. You can check thecommissioning progress of the NodeB in the NodeB commissioning window. For details, see

4.8 Viewing the NodeB Commissioning Progress.

Step 6 Obtain the NodeB commissioning report. For details, see 4.9 Obtaining the NodeB

Commissioning Report.

Step 7 Check the running status of the NodeB by viewing the NodeB commissioning report. For details,

see 2.4 Checking the Running Status of the NodeB.



----End

4.2 Information Related to the Commissioning of the NodeBon the M2000

Before commissioning the NodeB on the M2000, read the following information carefully:

4.2.1 NodeB Commissioning Items

This describes the NodeB commissioning items that can be performed on the M2000. The items

include the download of the software and configuration files, software activation, and health

check. When setting the NodeB commissioning task, you can choose one or multiple

commissioning items according to the actual requirements.

4.2.2 Introduction to the NodeB Commissioning Window

This describes the NodeB commissioning window, which helps you better know the components

and function of each component on the window.

4.2.1 NodeB Commissioning Items

This describes the NodeB commissioning items that can be performed on the M2000. The items

include the download of the software and configuration files, software activation, and health

check. When setting the NodeB commissioning task, you can choose one or multiple

commissioning items according to the actual requirements.

For details about NodeB commissioning items, see Table 4-1.

NodeB




4-5



Table 4-1 NodeB commissioning items

NodeBCommissioning Items

Description

Clock

synchronization

This item is selected by default. Synchronizes the clock information

between the NodeB and the M2000.

Downloading

the BootROM

Download the BootROM software on the server to the related NodeB.

Activating the

BootROM

Download the BootROM software, which is saved in the NodeB standby

file partition, to each board and upgrade the BootRom of each board.

Downloading

the software

Download the NodeB software on the server to the related NodeB.

Activating thesoftware

Download the software, which is saved in the NodeB standby file partition, to each board to make the software take effect.

Downloading

and activating

the data

configuration

file

Download the data configuration files on the server to the related

NodeB. You can click Upload new config file to upload the saved

configuration file on the M2000 server.

Health check Checks the operating status of the entire network. The check items consist

of the configuration status, cell, IPRAN status, and environment.

4.2.2 Introduction to the NodeB Commissioning Window

This describes the NodeB commissioning window, which helps you better know the components

and function of each component on the window.

NodeB Commissioning Function

The NodeB commissioning has the following functions:

l Manage the NodeB commissioning project and perform the creation, adjustment, and

refreshment for the commissioning project.

l Monitor the NodeB commissioning progress.

l Obtain the commissioning report and query the running status of the NodeB.

NodeB Commissioning Window

The NodeB commissioning window consists of the following five parts: Projects, Survey

NodeBs, NodeBs Commissioning Task, NodeB Check Information, and ButtonsButtons, as

shown in Figure 4-2.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Figure 4-2 NodeB Commissioning Window

Table 4-2 shows the interface components of the NodeB Commissioning window.

Table 4-2 Interface components of the NodeB Commissioning window

Number Field Description

1 Projects On the Projects tab page, all the commissioning projects

created are displayed.

2 Survey NodeBs On the Survey NodeBs tab page, all the current existing NodeBs are displayed.

Enter the name of the NodeB in Search, and then the system

directly locates it.

3 NodeB Check

Information

In the NodeB check information area, the detailed

information of the NodeB commissioning process is

displayed.

4 NodeBs

Commissioning

Task

In the NodeBs commissioning task area, all the NodeB

commissioning tasks within the project are displayed.

The M2000 creates a commissioning task for each NodeB

in the commissioning project.

NodeB




4-7



Number Field Description

5 Buttons The buttons perform different operations and achieve

corresponding functions.

4.3 Automatically Searching for NodeBs

This describes how to automatically search for NodeBs. The automatic searching function helps

you know information about the NodeBs under an RNC such as the total number of NodeBs

under one RNC, the number of NodeBs that connect to the M2000, the number of NodeBs whose

names are duplicate, and the number of NodeBs whose IP addresses are duplicated.

Prerequisite

l You have logged in to the M2000 client.

l The RNCs are well connected to the M2000.

l The NodeB mediation layer is installed on the M2000.

Context

l Based on the actual scenario, the NodeB maintenance channel supports the IP protocol

stack, ATM protocol stack, and dual stack. The NodeB supports dual maintenance channels.

When creating the NodeB, you can set two IP addresses. The primary address is the IP

address of the ATM network. The secondary address is the IP address of the IP bearing

network. Neither the primary nor the secondary IP addresses can be duplicate with that of

other NodeBs, even on a different network. The NodeB can be connected to the network

on condition that either of the IP addresses is valid. After the NodeB is disconnectedexceptionally, it automatically uses the current IP address to attempt reconnections. If the

attempt fails for five times in succession, the NodeB uses the other IP address for the

connection.

l The IP address of the IP bearing network can be dynamically assigned by the DHCP server.

The purpose of Dynamic Host Configuration Protocol (DHCP) is to provides configuration

information such as IP address to the Internet host in a TCP/IP network. The DHCP server

can dynamically assigns IP addresses to an Internet host.

l When the maintenance channel supports the ATM protocol stack, you can validate the

remote maintenance channel by using the ATM BOOTP technology.

l The process for automatically discovering the NodeB is as follows:

1. The M2000 obtains from the database the information about the NodeB managed by

the related RNC, such as NodeBID, NodeB name, and the NodeB IP addresses.

2. The M2000 obtains from the DHCP the information about the NodeB, such as

NodeBID, NodeB name, and the NodeB IP addresses.

3. Using the NodeBIDs, that is, the unique identification of NodeBs, the M2000

compares the NodeB information obtained from the database and the DHCP. If the

information is not consistent, the data from the DHCP server prevails.

4. Create a NodeB on the topology view and establish the connection between the NodeB

and the M2000.

l

NodeBs can be reparented. Therefore, the NodeBs that need to be deleted are not deletedautomatically when they are found automatically. Instead, they are marked as delete status


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



and displayed as disconnected. In this case, you need to determine whether the disconnected

NodeBs need to be deleted, reparented, or reconnected.

Procedure

Step 1 Choose Topology > Main Topology. The Main Topology window is displayed.

Step 2 From the topology navigation tree or the topology view, right-click an RNC and choose Search

NodeB on the shortcut menu.

In the Main Topology window, the system automatically synchronizes the information about

the NodeBs managed by a specific RNC, such as the total number of NodeBs under one RNC,

the number of NodeBs that connect to the M2000, the number of NEs whose names are duplicate,

and the number of NodeBs whose IP addresses are duplicated.

NOTE

l If the RNCs are disconnected from the M2000, Search NodeB becomes dimmed.

l For the RNCs in the multi-server load-sharing system, you also need to select the NE partition of the

NodeB.

----End

Result

The searched NodeBs are displayed on the physical topology view.

4.4 Checking Software Version Information on the Server

This describes how to check the software version information saved on the M2000 server. You

can check whether the required NodeB software and BootROM software are uploaded to the

M2000 by checking the software version information.

Procedure

Step 1 Choose Software > Browse. The Software Browser dialog box is displayed.

Step 2 In the navigation tree of the NM Server tab page, select the NodeB to be checked.

Step 3 In the list on the right, select the Software tab page. You can check the status of the software

version information stored on the server.

----End

4.5 Uploading the NodeB Software and BootROM Software

This describes how to upload the well prepared NodeB software and BootROM software on the

M2000 client to the associated path of the M2000 server.

Prerequisite

The connection between the client and the M2000 is functional.

NodeB




4-9



Procedure

Step 1 Choose Software > Filter Transfer Wizard. The Select General Parameters dialog box is

displayed.

Step 2 In Direction, select From Client To NM.

Step 3 Choose OMC Server > NodeB > NodeB Type > Software in Server Path.

Step 4 Click Next. The Select dialog box is displayed.

Step 5 Select the folder which the NodeB software and the BootROM software to be upgraded are saved

in.

Step 6 Click Finish. On the FTP Task tab at the bottom of the Software Browser window, the process

of uploading is displayed.

NOTE

When the progress bar displays 100%, you can infer that the software is uploaded successfully. You can query

the information of the software version on the server.

----End

4.6 Creating a NodeB Commissioning Project

This describes how to create a NodeB commissioning project. In this way, the NodeBs that meet

the requirements can automatically perform commissioning. In addition, the information about

the commissioning process is displayed on the M2000 client. When a commissioning project is

created successfully, the M2000 creates a commissioning task for each NodeB in the


Prerequisite

l The connection between the NodeB and the M2000 is functional.

l The data configuration file of the NodeB to be commissioned is ready.

l The NodeB software and BootROM software are uploaded to the M2000.

Procedure

Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is

displayed.

Step 2 Click New. The – Please Select The NodeBs To Be Surveyed dialog box is displayed.

Step 3 Set the Project Name and select the NodeBs that need to be commissioned.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



TIP

l Choose one or multiple conditions from RNC, NodeB Type, Version, and DualMode to regroup the

NEs in the NE navigation tree. If you choose one or multiple conditions, but the M2000 fails to obtain

the selected conditions, then the NodeB is displayed under a nameless parent node. For example, if the

RNC is selected as one condition, but the M2000 fails to obtain the information about the RNC that

the NodeB belongs to, then, the NodeB is displayed under a nameless parent node.

l Enter the name of the NodeB in Search, and then the system directly locates it.

l You can choose multiple NodeBs for commissioning from a commissioning project.

l After a commissioning project is created, you can add NodeBs to be commissioned in this

commissioning project. For details, see 4.7.1 Adjusting the Commissioning Object.

l The NodeB whose commissioning tasks are created is not displayed on the NE navigation tree in the

- Please Select The NodeBs To Be Surveyed dialog box.

Step 4 Click Next. The – Configuration Setting dialog box is displayed.

Step 5 In Operation Setting, select the commissioning items.

l For details about the commissioning items, see 4.2.1 NodeB Commissioning Items.

l You can select all the operation items by selecting All.

Step 6 Set the BootROM version.

If the BootRom Download or the BootRom Activate commissioning item is selected, choose

a BootRom version from the drop-down list of BootRom Version for each NodeB in the


Step 7 Set the software version.

If the Software Download or the Software Activate commissioning item is selected, choose a

software version from the drop-down list of Software Version for each NodeB in the


Step 8 Upload the data configuration file.

1. Click Upload new config file.

2. In Choose Config File Directory, find the folder where the NodeB configuration files are

saved.

NOTE

l You need to save the NodeB configuration files in the folder named by the corresponding NodeB,

and save the folder in client installation path. The default client installation path is \client\Data

\NodeBSurvey\NodeBConfig.

l You can upload the configuration files in batches.

l You can upload one or multiple NodeB configuration files to the server if you choose client

installation path.

3. Click Upload Config To Server.

The NodeB configuration files in the specified save path are uploaded to the server.

Step 9 Click Finish.

The system displays the following message: Do you want to run this project

now?

Step 10 Click Yes to run the commissioning project immediately.

NodeB




4-11



NOTE

l If performed immediately, the project is under the Running node; If not performed immediately, the project

is under the Waiting node.

l Right-click a commissioning project that is not started, and then choose Run Project Now to manually

perform this commissioning project.

l Delete a commissioning project. Right-click a commissioning project to be deleted, and then choose Delete

Project.

The system displays the following message: Do you want to delete this project?

Click Yes to delete the project.

----End

Postrequisite

l To view the commissioning progress of a NodeB commissioning task, see 4.8 Viewing the

NodeB Commissioning Progress.

l To add or to delete the commissioning object in a commissioning project, see 4.7.1

Adjusting the Commissioning Object.

l To start or stop a commissioning task in a commissioning project, see 4.7.2 Starting or

Stopping a NodeB Commissioning Task .

l To upload the NodeB data configuration files required by the ConfigFile Download

commissioning item again, see 4.7.3 Reuploading the NodeB Configuration File.

l To obtain an NodeB commissioning report, see 4.9 Obtaining the NodeB Commissioning

Report.

4.7 Managing the NodeB Commissioning ProjectThis describes how to manage the NodeB commissioning project. To improve the

commissioning efficiency, the M2000 provides the NodeB automatic commissioning function.

Users only need to monitor the commissioning process. After the NodeB commissioning process

is complete, the users obtain and analyze the commission report and check whether the

commissioning pr ocess is normal. Through the NodeB commissioning project management

function of the M2000, users can modify the commissioning objects, start or stop the NodeB

commissioning task, or upload the NodeB data configuration file required for the commissioning

again.

4.7.1 Adjusting the Commissioning Object

This describes how to adjust the commissioning object. You can add or delete the NodeBs to becommissioned in a commissioning project. The M2000 cr eates a commissioning task for each

NodeB in a commissioning project. If you need to change a commissioning item in a

commissioning pr oject, you have to delete this project and create a new commissioning project

to meet your requirements.

4.7.2 Starting or Stopping a NodeB Commissioning Task

This describes how to stop or start a commissioning task according to your requirements. You

can stop the commissioning task that is not required for the moment and restart the task when it

is required.

4.7.3 Reuploading the NodeB Configuration File

This describes how to upload the NE configuration files to the server again. In this way, the NodeB data configuration files on the server can be updated.


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



4.7.1 Adjusting the Commissioning Object

This describes how to adjust the commissioning object. You can add or delete the NodeBs to be

commissioned in a commissioning project. The M2000 creates a commissioning task for each

NodeB in a commissioning project. If you need to change a commissioning item in acommissioning project, you have to delete this project and create a new commissioning project

to meet your requirements.

Prerequisite

Some NodeB commissioning tasks are created.

Procedure


displayed.

Step 2 Perform the following operations to adjust the commissioning object according to the actual

requirements.

Adding/Deleting a NodeB

Operation

Adding a NodeB 1. In Projects, right-click the commissioning project that you want to

add a NodeB to, and then choose Add NodeBs To Project from

the shortcut menu.

2. In – Please Select The NodeBs To Be Surveyed, select one or

multiple NodeBs. Click Next.

3. If you select the CongifFile Download commissioning item when

creating a commissioning task, you can upload the NodeB data

configuration files to the server again. For details about how to

upload the NodeB configuration files, see 4.7.3 Reuploading the

NodeB Configuration File.

NodeB




4-13



Adding/Deleting a NodeB

Operation

Deleting a NodeB Two methods available for deleting a NodeB in a commissioning

project are as follows: Deleting a NodeB through Projects and

deleting a NodeB through Survey NodeBs.

To delete a NodeB through Projects, perform the following

operations:

1. In Projects, choose the project that you want to delete a NodeB.

2. In the list of commissioning tasks, right-click the NodeB

commissioning task, and then choose Delete NodeBs From

Project.

To delete a NodeB through Survey NodeBs, perform the following

operations:

1. In Survey NodeBs, select a NodeB node according to the NodeB

name. You can locate the required NodeB quickly by entering key

words in the Search text box.

2. In the list of commissioning tasks, right-click the NodeB

commissioning task, and then choose Delete NodeBs From

Project.

----End

4.7.2 Starting or Stopping a NodeB Commissioning Task

This describes how to stop or start a commissioning task according to your requirements. You

can stop the commissioning task that is not required for the moment and restart the task when itis required.

Prerequisite


Context

l Running commissioning tasks cannot be restarted.

l Finished commissioning tasks cannot be stopped.

Procedure


displayed.

Step 2 In Projects, choose the commissioning project where the NodeB commissioning task exists.

On the Survey NodeBs tab page, you can select the NodeB nodes according to the NodeB name.

Step 3 In the commissioning task list in the right pane, start or stop a commissioning task as required.

Operation Type Procedure

Start Right-click a commissioning task that needs to be restarted, and

then choose Start NodeBs Commissioning Task .


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Operation Type Procedure

Stop Right-click a commissioning task that needs to be stopped, and

then choose Stop NodeBs Commissioning Task .

----End

4.7.3 Reuploading the NodeB Configuration File

This describes how to upload the NE configuration files to the server again. In this way, the

NodeB data configuration files on the server can be updated.

Prerequisite


ProcedureStep 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is

displayed.

Step 2 In Projects, right-click the commissioning project whose configuration files need to be uploaded

again, and then choose Upload Config.

Step 3 In – Please Select The NodeBs To Be Surveyed, click Next.

The – Configuration Setting window is displayed.

Step 4 Click Upload new config file.

Step 5 In Choose Config Directory, specify the directory where the NodeB configuration files are

placed.

The NodeB configuration files are saved in the folders named by the corresponding NodeB name.

All the folders that save the NodeB configuration files are saved in a parent folder, such as

NodeBConfig .

NOTE

The configuration files can be uploaded in batches. Therefore, all the configuration files are uploaded to

the server if you select the directory of the NodeBConfig folder, regardless of one or multiple configuration

files that you select for the upload.

Step 6 Click Upload Config To Server. The mapping NodeB configuration files are uploaded to the

server.

Step 7 Click Finish.

----End

4.8 Viewing the NodeB Commissioning ProgressThis describes how to view the NodeB commissioning progress. You can obtain the information

about the progress of the commissioning project by viewing the NodeB commissioning project

and the NodeB commissioning task within the project.

Prerequisite


NodeB




4-15



Procedure


displayed.

You can query the status and progress of a commissioning project and those of a commissioningtask within the project.

Step 2 View the status of a commissioning project.

The Projects tab page lists all the commissioning projects on the M2000. A commissioning

project can be in one of the following three status: Waiting, Running, and Finished.

Step 3 View the progress of a commissioning task.

NOTE

l If you click a commissioning project under the Waiting node or under the Running node, the window in

the right pane displays the information about all the commissioning tasks contained in this commissioning

project. The information consists of NodeB Name, Current Status, and Percent.

l On the NodeB Check Information tab page, monitor the detailed information about a NodeB

commissioning task. You can also right-click the blank area on this tab page, and then choose Clean All

Messages to delete all the commissioning information displayed in this field.

l Click Refresh to refresh the information in the NodeB Commissioning window in real time.

----End

4.9 Obtaining the NodeB Commissioning Report

This describes how to obtain the NodeB commissioning report. You can learn the NodeB

commissioning status by viewing the NE commissioning report on the M2000.

Prerequisite


Procedure


displayed.

Step 2 In Projects, right-click the project whose NodeB commissioning report is required, and then

choose Get Project Report.

The browser automatically opens and displays the content of the commissioning report. The

check items of the commissioning report consist of configuration status, cells, IPRAN status,

and environment. You can learn the entire commissioning process by analyzing the

commissioning report.

NOTE

l The NodeB commissioning report is complete only when 100% is displayed in the Percent area of a

commissioning task.

l You can save the commissioning report to the specified path through the save as function of the browser.

----End


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



5Data Sheet for NodeB Commissioning

The data sheet for NodeB commissioning is used to record the process and results of the

commissioning.

Table 5-1 Data sheet for NodeB commissioning

Site Name

NodeB Model

Commissioning

Time

Commissioning

Personnel

Commissioning

Result

□ Successful;□ Failed

Item Conclusion Handling

Exceptional Cases

Commissioning

Preparation

Faults in NodeB hardware

installation are cleared.

□Yes;□No

Transmission links between the

NodeB and the RNC are ready.

□Yes;□No

Negotiation data of the NodeB

to be commissioned is added to

the RNC.

□Yes;□No

Commissioning

phase (method 1)

NodeB Local Operation

The NodeB software and

BootROM software are

upgraded from the USB disk,

and the data configuration file

is downloaded from the USB

disk.

□Yes;□No

NodeB

Commissioning Guide 5 Data Sheet for NodeB Commissioning



5-1



The status of the NodeB

hardware is checked.

□Yes;□No

NodeB Remote Operation

The data configuration file of the NodeB is downloaded once

more on the M2000.

□Yes;□No

The running status of the

NodeB is checked.

□Yes;□No

Commissioning

phase (method 2)

The NodeB software and

BootROM software are

upgraded on the LMT.

□Yes;□No

The data configuration file is

downloaded on the LMT.

□Yes;□No

The running status of the

NodeB is checked.

□Yes;□No

Problem Description Impact

Open Problems

During

Commissioning

Component P/N

Faulty Board

Record

5 Data Sheet for NodeB Commissioning

NodeB

Commissioning Guide



Issue 04 (2009-01-22)




Table 6-1 shows the communication port for the NodeB

Table 6-1 Numbers of the communication port for the NodeB services

Protocol

Side A Side APorts(Listening)

Side B SideBPorts(Launch)

Service Authentication

LocalPort

TC

P

NodeB 600

0

LMT 1024

to

6553

5

For LMT to

deliver

maintenance

commands and for

NodeB to

respond.

User name

and

password

No

TC

P

NodeB 600

1

LMT 1024

to

6553

5

For the NodeB to

report alarm data.

None No

TC

P

NodeB 600

6

LMT 1024

to

6553

5

For Maintenance,

the format is BIN.

None No

TC

P

NodeB 600

7

M2000 1024

to655

35

For M2000,

integration port

for MML,

ALARM and

BIN.

User name

and

password

No

NodeB

Commissioning Guide 6 Communication Port for the NodeB



6-1



Protocol

Side A Side APorts

(Listening)

Side B SideBPorts(Lau

nch)


LocalPort

TC

P

NodeB 20 Debug

console

of the

site

1024

to655

35

For FTP, debug

mode, local

maintenance FE

port.

None No

TC

P

NodeB 21 Debug

console

of the

site

1024

to655

35

For FTP, debug

mode, local

maintenance FE

port.

User name

and

password

No

TC

P

NodeB 23 Debug

console

of the

site

1024

to655

35

For remote login,

commissioning

mode, and local

maintenance FE

port.

User name

and

password

No

U

DP

NodeB 67/

68

The

M2000

or any of

the

DHCPserver

67/68 For the DHCP

service

None No

U

DP

The M2000 or

any of the

DHCP server

67/

68

NodeB 67/68 For the DHCP

service

None No

U

DP

The M2000,

RNC BAM,

or any of the

DHCP server

123 NodeB 1024

to

6553

5

For synchronizing

the SNTP clock

None No

TC

P

The LMT,

M2000, RNC

BAM, or any

of the FTP

server

20 NodeB 1024

to655

35

For FTP: Upload

the configuration

file and logs from

the Node B to the

FTP server;

Download the

configuration file

and software

packages to the

Node B from the

FTP server.

None No


NodeB

Commissioning Guide



Issue 04 (2009-01-22)



Protocol

Side A Side APorts

(Listening)

Side B SideBPorts(Lau

nch)


LocalPort

TC

P

The LMT,

M2000, RNC

BAM, or any

of the FTP

server

21 NodeB 1024

to

6553

5

For file transfer

control

User name

and

password

No

NodeB

Commissioning Guide 6 Communication Port for the NodeB



6-3





Index

A

activatingBootROM software, 3-7

NodeB software, 3-13

B

BootROM softwareactivating, 3-7downloading, 3-4

C

checkingLED status, 2-7running status, 2-14, 3-17

commissioningmethod 1, 2-1method 2, 3-1 procedure, 2-2, 3-2, 4-3

D

data configuration filedownloading, 2-4, 3-15

downloadingBootROM software, 3-4data configuration file, 2-4, 3-15 NodeB software, 3-9

M

measuringRTWP, 3-19

monitoring

P

procedure, 2-2, 3-2, 4-3

R

rectifyingcommon fault, 2-8detailed procedure, 2-10

U

upgradingsoftware, 2-4

NodeB

Commissioning Guide Index

Documents

NodeB Commissioning Guide(V200_04)