NodeB Commissioning Guide(V200_06)

NodeBV200

Commissioning Guide

Issue 06

Date 2010-09-10

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 06 (2010-09-10) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

OverviewThis document describes the guidelines for commissioning and verifying the NodeB after it isinstalled. The commissioning and verification guidelines involves upgrading the software,downloading the data configuration file, and checking the hardware installation and the runningstatus of the NodeB. These guidelines ensure that the NodeB operates as required.

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

Product Name Product Version

BTS3900 WCDMA (hereafter referred toas BTS3900)

V200R010

V200R011

BTS3900A WCDMA (hereafter referred toas BTS3900A)

V200R010

V200R011

DBS3900 WCDMA (hereafter referred toas DBS3900)

V200R010

V200R011

iDBS3900 WCDMA (hereafter referred toas iDBS3900)

V200R010

V200R011

Intended AudienceThis document is intended for field engineers.

NodeBCommissioning Guide About This Document


iii

Organization1 Changes in the NodeB Commissioning Guide

This chapter describes the changes in the NodeB Commissioning Guide.

2 Commissioning the NodeB on the M2000

This chapter describes how to commission the NodeB on the M2000. You can perform the remotecommissioning on multiple NodeBs on the M2000 in a central equipment room. Thecommissioning procedures, such as software upgrade, download of data configuration file,health check, and VSWR check, can be performed on the M2000.

3 Commissioning the NodeB Through the USB Disk+M2000

This chapter describes how to commission the NodeB with the combination of a on-site USBdisk and the remote commissioning on the M2000. You can upgrade the software and downloadthe data configuration file by using the USB disk, check the VSWR, and then check the runningstatus of the NodeB on the M2000.

4 Commissioning the NodeB on the LMT

This chapter describes how to perform the on-site commissioning of the NodeB on the LMT.You can upgrade the software, download the data configuration file, and check the running statusof the NodeB on the NodeB LMT.

5 Data Sheet for NodeB Commissioning

This section provides the data sheet that is used to record the process and results of the NodeBcommissioning.

6 Communication Ports on the NodeB

This section describes the communication ports on the NodeB.

ConventionsSymbol Conventions

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

Symbol Description

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

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

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

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

About This DocumentNodeB

Commissioning Guide

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

Issue 06 (2010-09-10)

Symbol Description

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

General Conventions

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

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

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

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

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

GUI Conventions

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

NodeBCommissioning Guide About This Document


v


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

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

Keyboard Operations

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

Format Description

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

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

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

Mouse Operations

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

Action Description

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

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

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

About This DocumentNodeB

Commissioning Guide

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

Issue 06 (2010-09-10)

Contents

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

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

2 Commissioning the NodeB on the M2000.............................................................................2-12.1 Procedure for Commissioning the NodeB on the M2000...............................................................................2-32.2 Information Related to the Commissioning of the NodeB on the M2000......................................................2-6

2.2.1 NodeB Commissioning Items................................................................................................................2-62.2.2 Introduction to the NodeB Commissioning Window.............................................................................2-72.2.3 NodeB Standing Wave Ratio Test Tab Page.........................................................................................2-9

2.3 Automatically Searching for NodeBs...........................................................................................................2-102.4 Checking Software Version Information on the Server................................................................................2-112.5 Uploading the NodeB Software and BootROM Software............................................................................2-112.6 Creating a NodeB Commissioning Project...................................................................................................2-122.7 Managing the NodeB Commissioning Project..............................................................................................2-14

2.7.1 Adjusting the Commissioning Object..................................................................................................2-152.7.2 Starting or Stopping a NodeB Commissioning Task...........................................................................2-162.7.3 Reuploading the NodeB Configuration File.........................................................................................2-16

2.8 Viewing the NodeB Commissioning Progress..............................................................................................2-172.9 Obtaining the NodeB Commissioning Report..............................................................................................2-182.10 Checking the Running Status of the NodeB................................................................................................2-182.11 Testing the NodeB VSWR on the M2000...................................................................................................2-192.12 Testing NodeB Services..............................................................................................................................2-202.13 Setting the Device Status of the NodeB......................................................................................................2-21

3 Commissioning the NodeB Through the USB Disk+M2000.............................................3-13.1 Procedure for Commissioning the NodeB Through the USB+M2000...........................................................3-23.2 Preparing the USB Disk for On-Site Commissioning.....................................................................................3-53.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side) .........3-63.4 Checking the Status of the NodeBHardware and Rectifying Faults (on the NodeB Side).............................3-8

3.4.1 Checking the Status of LEDs.................................................................................................................3-83.4.2 Rectifying Common Faults....................................................................................................................3-93.4.3 Guidelines for Rectifying Faults..........................................................................................................3-11

3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the NodeB Side).....................................3-15

4 Commissioning the NodeB on the LMT................................................................................4-1

NodeBCommissioning Guide Contents


vii

4.1 Procedure for Commissioning the NodeB on the LMT..................................................................................4-24.2 Upgrading the NodeB Software and Downloading the Data Configuration File............................................4-3

4.2.1 Querying the Active Version of the NodeB...........................................................................................4-34.2.2 Upgrading the NodeB BootROM...........................................................................................................4-44.2.3 Upgrading the NodeB Software and Downloading the Data Configuration File...................................4-5

4.3 Checking the Running Status of the NodeB....................................................................................................4-64.3.1 Commissioning SNTP............................................................................................................................4-74.3.2 Checking the Status of a Cell.................................................................................................................4-84.3.3 Measuring the RTWP.............................................................................................................................4-84.3.4 Monitoring the Output Power of the NodeB........................................................................................4-104.3.5 Handling NodeB Alarms......................................................................................................................4-11

4.4 Testing the NodeB VSWR on the LMT........................................................................................................4-12

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

6 Communication Ports on the NodeB......................................................................................6-1

ContentsNodeB

Commissioning Guide

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

Issue 06 (2010-09-10)

Figures

Figure 2-1 Procedure for commissioning the NodeB on the M2000...................................................................2-4Figure 2-2 NodeB Commissioning Window........................................................................................................2-8Figure 2-3 NodeB Standing Wave Ratio Test tab page....................................................................................... 2-9Figure 3-1 Procedures for commissioning the NodeB through the USB+M2000...............................................3-3Figure 3-2 Plugging the USB disk into the USB port on the WMPT..................................................................3-7Figure 3-3 LED status of common faults.............................................................................................................3-9Figure 3-4 Plugging the USB disk into the USB port on the WMPT................................................................3-16Figure 4-1 Procedures for commissioning the NodeB on the LMT.....................................................................4-2

NodeBCommissioning Guide Figures


ix

Tables

Table 2-1 NodeB commissioning items............................................................................................................... 2-6Table 2-2 Interface components of the NodeB Commissioning window...........................................................2-8Table 2-3 Standing Wave Ratio Test tab page...................................................................................................2-9Table 3-1 LEDs on the USB disk and the WMPT............................................................................................... 3-7Table 3-2 LED status of the functional NodeB....................................................................................................3-8Table 3-3 Methods of rectifying common faults................................................................................................3-10Table 4-1 Fields in the FTP Setting dialog box.................................................................................................. 4-4Table 4-2 Fields in the FTP Setting dialog box.................................................................................................. 4-5Table 4-3 Monitoring items for the RTWP measurement..................................................................................4-10Table 4-4 Monitoring items for the NodeB output power measurement...........................................................4-11Table 5-1 Data Sheet for NodeB Commissioning................................................................................................5-1Table 6-1 Communication ports of the NodeB.................................................................................................... 6-1

NodeBCommissioning Guide Tables


xi

1 Changes in the NodeB CommissioningGuide

This chapter describes the changes in the NodeB Commissioning Guide.

06 (2010-09-10)

This is the fifth commercial release.

Compared with issue 05 (2009-04-15), this issue does not add any topic.

Compared with issue 05 (2009-04-15), this issue incorporates the following changes:

Topic Description

4.2 Upgrading the NodeB Softwareand Downloading the DataConfiguration File

The operations of upgrading the NodeB software anddownloading the data configuration file on the LMTare optimized.

3.5 Testing the NodeB AntennaVSWR Through the USB Disk (Onthe NodeB Side)

The method of verifying the on-site Voltage StandingWave Ratio (VSWR) test result on the M2000 isupdated. That is, you can verify the on-site VSWRtest result through the fault diagnosis function on theM2000 without viewing the main control log.

Compared with issue 05 (2009-04-15), this issue does not delete any topic.

05 (2009-04-15)

This is the fourth commercial release.

Compared with issue 04 (2009-01-22), this issue adds the following topics:l The description of measuring the NodeB VSWR.

Compared with issue 04 (2009-01-22), this issue does not modify any topic.


NodeBCommissioning Guide 1 Changes in the NodeB Commissioning Guide


1-1

04 (2009-01-22)This is the third commercial release.

Compared with issue 03 (2008-12-15), this issue adds the following topics:l The description of the 2 Commissioning the NodeB on the M2000.


Topic Description

3 Commissioning the NodeB Through theUSB Disk+M2000

Descriptions are optimized.


03 (2008-12-15)This is the second commercial release.

Compared with issue 02 (2008-08-15), this issue adds the following topics:l The description of the 4 Commissioning the NodeB on the LMT.


Topic Description

3.4 Checking the Status of theNodeBHardware and Rectifying Faults(on the NodeB Side)

Descriptions are optimized.


02 (2008-08-15)This is the first commercial release.

Compared with issue 01 (2008-03-30), this issue adds the following topics:l 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on

the NodeB Side)l 3.4 Checking the Status of the NodeBHardware and Rectifying Faults (on the NodeB

Side)


Topic Description

NodeB Commissioning Procedure Descriptions are optimized.

Checking the running status of the NodeB The method is optimized.

1 Changes in the NodeB Commissioning GuideNodeB

Commissioning Guide

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

Issue 06 (2010-09-10)

Compared with issue 01 (2008-03-30), this issue deletes the following topics:l The upgrade of the NodeB software.

l The download of the NodeB data configuration file.

l The initial activation of the NodeB license.

01 (2008-03-30)This is the draft issue.

NodeBCommissioning Guide 1 Changes in the NodeB Commissioning Guide


1-3

2 Commissioning the NodeB on the M2000

About This Chapter

This chapter describes how to commission the NodeB on the M2000. You can perform the remotecommissioning on multiple NodeBs on the M2000 in a central equipment room. Thecommissioning procedures, such as software upgrade, download of data configuration file,health check, and VSWR check, can be performed on the M2000.

2.1 Procedure for Commissioning the NodeB on the M2000This section describes how to commission the NodeB on the M2000. After the NodeB hardwareis installed, you can commission the NodeB.

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

2.3 Automatically Searching for NodeBsThis section describes how to automatically search for NodeBs. The automatic searchingfunction helps you know information about the NodeBs under an RNC such as the total numberof NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number ofNodeBs whose names are duplicate, and the number of NodeBs whose IP addresses areduplicated.

2.4 Checking Software Version Information on the ServerThis section 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 tothe M2000 by checking the software version information.

2.5 Uploading the NodeB Software and BootROM SoftwareThis section describes how to upload the well prepared NodeB software and BootROM softwareon the M2000 client to the associated path of the M2000 server.

2.6 Creating a NodeB Commissioning ProjectThis section describes how to create a NodeB commissioning project. In this way, the NodeBsthat meet the requirements can automatically perform commissioning. In addition, theinformation about the commissioning process is displayed on the M2000 client. When acommissioning project is created successfully, the M2000 creates a commissioning task for eachNodeB in the commissioning project.

2.7 Managing the NodeB Commissioning Project

NodeBCommissioning Guide 2 Commissioning the NodeB on the M2000


2-1

This chapter describes how to manage the NodeB commissioning project. To improve thecommissioning efficiency, the M2000 provides the NodeB automatic commissioning function.Users only need to monitor the commissioning process. After the NodeB commissioning processis complete, the users obtain and analyze the commission report and check whether thecommissioning process is normal. Through the NodeB commissioning project managementfunction of the M2000, users can modify the commissioning objects, start or stop the NodeBcommissioning task, or upload the NodeB data configuration file required for the commissioningagain.

2.8 Viewing the NodeB Commissioning ProgressThis section describes how to view the NodeB commissioning progress. You can obtain theinformation about the progress of the commissioning project by viewing the NodeBcommissioning project and the NodeB commissioning task within the project.

2.9 Obtaining the NodeB Commissioning ReportThis section describes how to obtain the NodeB commissioning report. You can learn the NodeBcommissioning status by viewing the NE commissioning report on the M2000.

2.10 Checking the Running Status of the NodeBThis section describes how to check the running status of the NodeB by analyzing thecommissioning report of the NodeB.

2.11 Testing the NodeB VSWR on the M2000This section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed. You can test the VSWR of multiple NodeBs on the M2000.

2.12 Testing NodeB ServicesThe service dialing test is to check that the NodeB can provide all kinds of services.

2.13 Setting the Device Status of the NodeBIf the NodeB is in Install status during commissioning, you need to change Device Status ofthe NodeB to Normal to recover the alarm reporting process.

2 Commissioning the NodeB on the M2000NodeB

Commissioning Guide


Issue 06 (2010-09-10)

2.1 Procedure for Commissioning the NodeB on the M2000This section describes how to commission the NodeB on the M2000. After the NodeB hardwareis installed, you can commission the NodeB.

PrerequisiteBefore commissioning the NodeB, the NodeB, RNC, and M2000 must meet the followingrequirements:l NodeBThe hardware of the NodeB, such as the cabinets, cables, antenna system, and

auxiliary devices, is installed and passes the installation check. The NodeB is powered onand passes the power-on check.

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 M2000 server is installed with the mediation software corresponding to the targetversion of the NodeB to be commissioned.

In addition, the following requirements should be met:l The required NodeB software, BootROM software, and data configuration file are ready.

NOTE

l During the deployment of a site, the NodeB may report plenty of alarms that need not be handledby the operator. Such alarms can be automatically cleared. A special alarm handling mechanismis integrated into the NodeB from V200R011C00SPC210. When the NodeB is in a special status,for example, Install, all reported alarms are screened. When Device Status of the NodeB changesto Normal, the alarms that are not cleared in the special status are reported again as commonalarms.

l In the configuration file that is created through the CME, you can set Device Status of theNodeB to Install. For the configuration method, see the NodeB Initial Configuration Guide.When the configuration file is downloaded to the NodeB and becomes effective, DeviceStatus of the NodeB is automatically set to Install. In this status, all reported alarms are screeneduntil the operator sets Device Status of NodeB to Normal.

l The transmission and the remote maintenance channels between the NodeB and the M2000are normal. The M2000 can automatically detect the NodeB to be commissioned.

Commissioning procedureFigure 2-1 shows the procedure for commissioning the NodeB.



2-3

Figure 2-1 Procedure for commissioning the NodeB on the M2000

Procedure

Step 1 Wait till the M2000 automatically detects the NodeB to be commissioned. For details, see 2.3Automatically Searching for NodeBs.


Commissioning Guide


Issue 06 (2010-09-10)

If... Then...

The NodeB to be commissioned issuccessfully detected

Go to Step 2.

The NodeB to be commissioned cannot bedetected

The communication between the M2000 andthe NodeB fails. Contact the maintenanceengineers to commission the transmissionchannels till the M2000 detects the NodeB tobe commissioned.

Step 2 Check whether the NodeB software and BootROM software are uploaded to the M2000 server.For the detailed checking method, see 2.4 Checking Software Version Information on theServer.

If... Then...

The NodeB software and BootROMsoftware are uploaded to the M2000 server

Go to Step 4.

The NodeB software and BootROMsoftware are not uploaded to the M2000server

Go to Step 3.

Step 3 Upload the NodeB software and BootROM software to the M2000 server. For the detaileduploading method, see 2.5 Uploading the NodeB Software and BootROM Software.

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

Step 5 The M2000 performs the specified commissioning items automatically. Check the NodeBcommissioning progress in the NodeB Commissioning window. For details, see 2.8 Viewingthe NodeB Commissioning Progress.

Step 6 Obtain the commissioning report of the NodeB through the M2000. For the detailed procedure,see 2.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.10 Checking the Running Status of the NodeB.

Step 8 Measure the VSWR of the NodeB on the M2000 to check the installation of the antenna system.For details, see 2.11 Testing the NodeB VSWR on the M2000.

Step 9 Set Device Status of the NodeB to Normal on the M2000 to recover the alarm reporting process.For details, see 2.13 Setting the Device Status of the NodeB.

Step 10 Record the commissioning procedures and problems in the 5 Data Sheet for NodeBCommissioning, and then export a commissioning report.

----End



2-5

2.2 Information Related to the Commissioning of the NodeBon the M2000

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

2.2.1 NodeB Commissioning ItemsThis section 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, andhealth check. When setting the NodeB commissioning task, you can choose one or multiplecommissioning items according to the actual requirements.

2.2.2 Introduction to the NodeB Commissioning WindowThis section describes the NodeB commissioning window, which helps you better know thecomponents and function of each component on the window.

2.2.3 NodeB Standing Wave Ratio Test Tab PageThis section describes the components of the NodeB Standing Wave Ratio Test tab page andthe functions of the components.

2.2.1 NodeB Commissioning ItemsThis section 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, andhealth check. When setting the NodeB commissioning task, you can choose one or multiplecommissioning items according to the actual requirements.

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

Table 2-1 NodeB commissioning items

NodeBCommissioning Items

Description

Clocksynchronization

This item is selected by default. Synchronizes the clock informationbetween the NodeB and the M2000.

Downloadingthe BootROM

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

Activating theBootROM

Download the BootROM software, which is saved in the NodeB standbyfile partition, to each board and upgrade the BootRom of each board.

Downloadingthe software

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

Activating thesoftware

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


Commissioning Guide


Issue 06 (2010-09-10)

NodeBCommissioning Items

Description

Downloadingand activatingthe dataconfigurationfile

Download the data configuration files on the server to the relatedNodeB. You can click Upload new config file to upload the savedconfiguration file on the M2000 server.

Health check Checks the operating status of the entire network. The check items consistof the configuration status, cell, IPRAN status, and environment.

2.2.2 Introduction to the NodeB Commissioning WindowThis section describes the NodeB commissioning window, which helps you better know thecomponents and function of each component on the window.

NodeB Commissioning FunctionThe 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 WindowThe NodeB commissioning window consists of the following five parts: Projects, SurveyNodeBs, NodeBs Commissioning Task, NodeB Check Information, and ButtonsButtons, asshown in Figure 2-2.



2-7

Figure 2-2 NodeB Commissioning Window

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

Table 2-2 Interface components of the NodeB Commissioning window

Number Field Description

1 Projects On the Projects tab page, all the commissioning projectscreated are displayed.

2 Survey NodeBs On the Survey NodeBs tab page, all the current existingNodeBs are displayed.Enter the name of the NodeB in Search, and then the systemdirectly locates it.

3 NodeB CheckInformation

In the NodeB check information area, the detailedinformation of the NodeB commissioning process isdisplayed.

4 NodeBsCommissioningTask

In the NodeBs commissioning task area, all the NodeBcommissioning tasks within the project are displayed.The M2000 creates a commissioning task for each NodeBin the commissioning project.


Commissioning Guide


Issue 06 (2010-09-10)

Number Field Description

5 Buttons The buttons perform different operations and achievecorresponding functions.

2.2.3 NodeB Standing Wave Ratio Test Tab PageThis section describes the components of the NodeB Standing Wave Ratio Test tab page andthe functions of the components.

As shown in Figure 2-3, the NodeB Standing Wave Ratio Test tab page consists of three parts,which are navigation tree, Query Result, and operation buttons.

Figure 2-3 NodeB Standing Wave Ratio Test tab page

Table 2-3 describes the components on the Standing Wave Ratio Test tab page.

Table 2-3 Standing Wave Ratio Test tab page

No. Field Description

1 Navigation tree All the NEs enlisted in the network are displayed in theRoot area, such as the RNC and NodeB.

2 Query Result The queried NodeB VSWR information is displayed in theQuery Result area.



2-9

No. Field Description

3 Function buttons Click different buttons to perform different functions.

2.3 Automatically Searching for NodeBsThis section describes how to automatically search for NodeBs. The automatic searchingfunction helps you know information about the NodeBs under an RNC such as the total numberof NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number ofNodeBs whose names are duplicate, and the number of NodeBs whose IP addresses areduplicated.

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

Contextl 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 IPaddress of the ATM network. The secondary address is the IP address of the IP bearingnetwork. Neither the primary nor the secondary IP addresses can be duplicate with that ofother NodeBs, even on a different network. The NodeB can be connected to the networkon 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 theattempt fails for five times in succession, the NodeB uses the other IP address for theconnection.

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 configurationinformation such as IP address to the Internet host in a TCP/IP network. The DHCP servercan dynamically assigns IP addresses to an Internet host.

l When the maintenance channel supports the ATM protocol stack, you can validate theremote 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 bythe 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 asNodeBID, NodeB name, and the NodeB IP addresses.

3. Using the NodeBIDs, that is, the unique identification of NodeBs, the M2000compares the NodeB information obtained from the database and the DHCP. If theinformation is not consistent, the data from the DHCP server prevails.

4. Create a NodeB on the topology view and establish the connection between the NodeBand 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


Commissioning Guide


Issue 06 (2010-09-10)

and displayed as disconnected. In this case, you need to determine whether the disconnectedNodeBs 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 SearchNodeB on the shortcut menu.In the Main Topology window, the system automatically synchronizes the information aboutthe 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 theNodeB.

----End

Result

The searched NodeBs are displayed on the physical topology view.

2.4 Checking Software Version Information on the ServerThis section 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 tothe 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 softwareversion information stored on the server.

----End

2.5 Uploading the NodeB Software and BootROM SoftwareThis section describes how to upload the well prepared NodeB software and BootROM softwareon the M2000 client to the associated path of the M2000 server.

Prerequisite

The connection between the client and the M2000 is functional.



2-11

Procedure

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

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

Step 6 Click Finish. On the FTP Task tab at the bottom of the Software Browser window, the processof uploading is displayed.

NOTE

When the progress bar displays 100%, you can infer that the software is uploaded successfully. You can querythe information of the software version on the server.

----End

2.6 Creating a NodeB Commissioning ProjectThis section describes how to create a NodeB commissioning project. In this way, the NodeBsthat meet the requirements can automatically perform commissioning. In addition, theinformation about the commissioning process is displayed on the M2000 client. When acommissioning project is created successfully, the M2000 creates a commissioning task for eachNodeB in the commissioning project.

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

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.


Commissioning Guide


Issue 06 (2010-09-10)

TIP

l Choose one or multiple conditions from RNC, NodeB Type, Version, and DualMode to regroup theNEs in the NE navigation tree. If you choose one or multiple conditions, but the M2000 fails to obtainthe selected conditions, then the NodeB is displayed under a nameless parent node. For example, if theRNC is selected as one condition, but the M2000 fails to obtain the information about the RNC thatthe 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 thiscommissioning project. For details, see 2.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 2.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, choosea BootRom version from the drop-down list of BootRom Version for each NodeB in thecommissioning project.

Step 7 Set the software version.If the Software Download or the Software Activate commissioning item is selected, choose asoftware version from the drop-down list of Software Version for each NodeB in thecommissioning project.

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

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 clientinstallation 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 projectnow?

Step 10 Click Yes to run the commissioning project immediately.



2-13

NOTE

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

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

l Delete a commissioning project. Right-click a commissioning project to be deleted, and then choose DeleteProject.The system displays the following message: Do you want to delete this project?Click Yes to delete the project.

----End

Postrequisitel To view the commissioning progress of a NodeB commissioning task, see 2.8 Viewing the

NodeB Commissioning Progress.l To add or to delete the commissioning object in a commissioning project, see 2.7.1

Adjusting the Commissioning Object.l To start or stop a commissioning task in a commissioning project, see 2.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 2.7.3 Reuploading the NodeB Configuration File.l To obtain an NodeB commissioning report, see 2.9 Obtaining the NodeB Commissioning

Report.

2.7 Managing the NodeB Commissioning ProjectThis chapter describes how to manage the NodeB commissioning project. To improve thecommissioning efficiency, the M2000 provides the NodeB automatic commissioning function.Users only need to monitor the commissioning process. After the NodeB commissioning processis complete, the users obtain and analyze the commission report and check whether thecommissioning process is normal. Through the NodeB commissioning project managementfunction of the M2000, users can modify the commissioning objects, start or stop the NodeBcommissioning task, or upload the NodeB data configuration file required for the commissioningagain.

2.7.1 Adjusting the Commissioning ObjectThis section describes how to adjust the commissioning object. You can add or delete the NodeBsto be commissioned in a commissioning project. The M2000 creates a commissioning task foreach 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 projectto meet your requirements.

2.7.2 Starting or Stopping a NodeB Commissioning TaskThis section 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 taskwhen it is required.

2.7.3 Reuploading the NodeB Configuration FileThis section 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.


Commissioning Guide


Issue 06 (2010-09-10)

2.7.1 Adjusting the Commissioning ObjectThis section describes how to adjust the commissioning object. You can add or delete the NodeBsto be commissioned in a commissioning project. The M2000 creates a commissioning task foreach 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 projectto meet your requirements.

PrerequisiteSome NodeB commissioning tasks are created.

Procedure


Step 2 Perform the following operations to adjust the commissioning object according to the actualrequirements.

Adding/Deletinga NodeB

Operation

Adding a NodeB 1. In Projects, right-click the commissioning project to which aNodeB is added, and then choose Add NodeBs To Project fromthe shortcut menu.

2. In – Please Select The NodeBs To Be Surveyed, select one ormultiple NodeBs. Click Next.

3. If you select the CongifFile Download commissioning item whencreating a commissioning task, you can upload the NodeB dataconfiguration files to the server again. For details about how toupload the NodeB configuration files, see 2.7.3 Reuploading theNodeB Configuration File.

Deleting a NodeB Two methods available for deleting a NodeB in a commissioningproject are as follows: Deleting a NodeB through Projects anddeleting a NodeB through Survey NodeBs.To delete a NodeB through Projects, perform the followingoperations:1. In Projects, choose the project from which a NodeB is deleted.2. In the list of commissioning tasks, right-click the NodeB

commissioning task, and then choose Delete NodeBs FromProject.

To delete a NodeB through Survey NodeBs, perform the followingoperations:1. In Survey NodeBs, select a NodeB node according to the NodeB

name. You can locate the required NodeB quickly by entering keywords in the Search text box.

2. In the list of commissioning tasks, right-click the NodeBcommissioning task, and then choose Delete NodeBs FromProject.



2-15

----End

2.7.2 Starting or Stopping a NodeB Commissioning TaskThis section 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 taskwhen it is required.


Contextl Running commissioning tasks cannot be restarted.

l Finished commissioning tasks cannot be stopped.

Procedure


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, andthen choose Start NodeBs Commissioning Task.

Stop Right-click a commissioning task that needs to be stopped, andthen choose Stop NodeBs Commissioning Task.

----End

2.7.3 Reuploading the NodeB Configuration FileThis section 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.


Procedure



Commissioning Guide


Issue 06 (2010-09-10)

Step 2 In Projects, right-click the commissioning project whose configuration files need to be uploadedagain, 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 areplaced.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 asNodeBConfig.

NOTE

The configuration files can be uploaded in batches. Therefore, all the configuration files are uploaded tothe server if you select the directory of the NodeBConfig folder, regardless of one or multiple configurationfiles that you select for the upload.

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

Step 7 Click Finish.

----End

2.8 Viewing the NodeB Commissioning ProgressThis section describes how to view the NodeB commissioning progress. You can obtain theinformation about the progress of the commissioning project by viewing the NodeBcommissioning project and the NodeB commissioning task within the project.


Procedure

Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box isdisplayed.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 commissioningproject can be in one of the following three status: Waiting, Running, and Finished.

Step 3 View the progress of a commissioning task.



2-17

NOTE

l If you click a commissioning project under the Waiting node or under the Running node, the window inthe right pane displays the information about all the commissioning tasks contained in this commissioningproject. The information consists of NodeB Name, Current Status, and Percent.

l On the NodeB Check Information tab page, monitor the detailed information about a NodeBcommissioning task. You can also right-click the blank area on this tab page, and then choose Clean AllMessages 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

2.9 Obtaining the NodeB Commissioning ReportThis section describes how to obtain the NodeB commissioning report. You can learn the NodeBcommissioning status by viewing the NE commissioning report on the M2000.


Procedure


Step 2 In Projects, right-click the project whose NodeB commissioning report is required, and thenchoose Get Project Report.

The browser automatically opens and displays the content of the commissioning report. Thecheck items of the commissioning report consist of configuration status, cells, IPRAN status,and environment. You can learn the entire commissioning process by analyzing thecommissioning report.

NOTE

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

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

----End

2.10 Checking the Running Status of the NodeBThis section describes how to check the running status of the NodeB by analyzing thecommissioning report of the NodeB.

Prerequisitel 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 isconsistent with the requirement.

l You have logged in to the M2000 client, and created the NodeB. The NodeB commissioningproject is complete, and the NodeB commissioning report is obtained.


Commissioning Guide


Issue 06 (2010-09-10)

NOTE

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

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.

If... Then...

An alarm is generated Handle the alarm according to the AlarmReference.

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

----End

2.11 Testing the NodeB VSWR on the M2000This section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed. You can test the VSWR of multiple NodeBs on the M2000.

Prerequisitel The configuration of the NodeB is complete, and the transmission is available.

l The NodeB does not provide any service or the services are isolated.

Context

An excessively large VSWR results in a short transmission distance and may damage the poweramplifier (PA), affecting the normal operation of the system. The normal VSWR ranges from 1to 2.0. The VSWR less than 1.5 is preferred.

CAUTIONTesting the VSWR interrupts the NodeB services. Therefore, you are advised to test the VSWRin low traffic hours or after the NodeB services are isolated.

Procedure

Step 1 Choose Maintenance > Standing Wave Ratio Test > Standing Wave Ratio Test. TheStanding Wave Ratio Test tab page is displayed.



2-19

NOTE

l For the components of the Standing Wave Ratio Test tab page, see 2.2.3 NodeB Standing Wave RatioTest Tab Page.

l The VSWR threshold of the NodeB and the displayed color can be set. For detailed operations, see theM2000 Operator Guide.

Step 2 In the navigation tree on the right pane of the Standing Wave Ratio Test tab page, choose oneor more NodeBs to be tested.

CAUTIONThe navigation tree on the right pane of the Standing Wave Ratio Test tab page cannot refreshthe NE information automatically. Therefore, you need to click Refresh to manually refresh theNE information.

Step 3 Click Query. Then click Yes in the displayed dialog box.The system displays a message VSWR query will impact the system servicegreatly! Please confirm to continue or not.

Step 4 View the query result.1. During the query, the system displays the progress in the VSWR Query dialog box. Click

Detail to see the detailed information about the progress.2. When the progress reaches 100%, click Close to close the VSWR Query dialog box. Then,

the query result is displayed on the Query Result tab page.

NOTE

You can print out the query result or save it into the local computer. For detailed operations, see the M2000Operator Guide.

----End

Postrequisite1. Verify that the antenna system is correctly installed based on the measured VSWR.2. Ensure that the NodeB services resume.

2.12 Testing NodeB ServicesThe service dialing test is to check that the NodeB can provide all kinds of services.

Prerequisitel Two UEs with USIM cards are available.

l The two UEs under test are registered to HLR.

l The RNC works well.

l The CS domain and PS domain at CN side work well.

l All the logical cells of NodeB at RNC side are normal. Execute the command DSP CELLat the RNC to verify them.


Commissioning Guide


Issue 06 (2010-09-10)

l All the logical cells of NodeB at NodeB side are normal. Execute the command DSPLOCELL at the NodeB to verify them.

Procedurel Check voice service.

Test method Expected result

UE calls local fixed linetelephone

Voice is clear without obvious noise.

Local fixed linetelephone calls UE

Voice is clear without obvious noise.

UE 1 calls UE 2 Voice is clear without obvious noise.

l Check CS streaming service.


UE 1 originates videoservice to UE 2

Voice is clear.Video is continuous.Voice and video are synchronized.

l Check PS service.


UE activates data serviceand browses web pages

Web browsing is normal.

----End

2.13 Setting the Device Status of the NodeBIf the NodeB is in Install status during commissioning, you need to change Device Status ofthe NodeB to Normal to recover the alarm reporting process.

Contextl When you change Device Status of the NodeB to Normal on the M2000, the alarms that

are not cleared in Install status are reported again as common alarms to the M2000.l With the function of querying the special status of an NE, you can understand the current

status of the NodeB. For detailed operations, see the M2000 Operator Guide.

Procedure

Step 1 Choose Monitor > Settings > Maintenance Mode Alarm Filter. The Maintenance ModeAlarm Filter tab page is displayed.



2-21

Step 2 Click Setting.... The Setting Maintenance Mode Alarm Filter dialog box is displayed.

Step 3 Select the NodeB that is commissioned and set its Device Status to Normal.NOTE

For detailed parameter setting methods, see the M2000 Operator Guide.

Step 4 Click OK to recover the NodeB to the normal status.

----End


Commissioning Guide


Issue 06 (2010-09-10)

3 Commissioning the NodeB Through theUSB Disk+M2000

About This Chapter

This chapter describes how to commission the NodeB with the combination of a on-site USBdisk and the remote commissioning on the M2000. You can upgrade the software and downloadthe data configuration file by using the USB disk, check the VSWR, and then check the runningstatus of the NodeB on the M2000.

3.1 Procedure for Commissioning the NodeB Through the USB+M2000On the NodeB side, you can upgrade the NodeB software and data configurations from the USBdisk, check whether the hardware status is normal according to the LED status, and checkwhether the NodeB VSWR meets the requirements. After the operations on the NodeB side arecomplete, check the running status of the NodeB on the M2000.

3.2 Preparing the USB Disk for On-Site CommissioningThe USB disk should be ready before it is used for on-site commissioning.

3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeBSide)The NodeB supports software upgrade and data configuration file downloading directly fromthe USB disk. After the download, the NodeB automatically activates the software, and thenresets.

3.4 Checking the Status of the NodeBHardware and Rectifying Faults (on the NodeB Side)This section describes how to check the BBU3900 hardware installation and how to rectify faults.You can locate the hardware faults regarding external ports and CPRI optical cable connectionby checking the LEDs on the boards or the auxiliary devices, and rectify faults in time.

3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the NodeB Side)This section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed. You can test the VSWR through the USB disk on the NodeB side.

NodeBCommissioning Guide 3 Commissioning the NodeB Through the USB Disk+M2000


3-1

3.1 Procedure for Commissioning the NodeB Through theUSB+M2000

On the NodeB side, you can upgrade the NodeB software and data configurations from the USBdisk, check whether the hardware status is normal according to the LED status, and checkwhether the NodeB VSWR meets the requirements. After the operations on the NodeB side arecomplete, check the running status of the NodeB on the M2000.

PrerequisiteBefore commissioning the NodeB, the NodeB, RNC, and M2000 should meet followingrequirements:l NodeBThe hardware such as the cabinets, cables, antenna system, and auxiliary devices,

is installed and passes the installation check. The NodeB passes a power-on status checkand 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 recorded.

l The M2000 server is installed with the mediation software corresponding to the targetversion of the NodeB to be commissioned.

The USB disk for on-site commissioning should be ready for this commissioning. For details,see 3.2 Preparing the USB Disk for On-Site Commissioning.

NOTE

l During the deployment of a site, the NodeB may report plenty of alarms that require no care of theoperators. Such alarms can be automatically cleared. A special alarm handling mechanism is integratedinto the NodeB from V200R011C00SPC210. When the NodeB is in a special state, for example, newlydeployed, all reported alarms are screened. When the NodeBSpecial Status changes into theNormal state, the alarms that are not cleared in the special state are reported as common alarms.

l In the initial configuration file that is created through the CME, you can set Special Status of theNodeB to Installing. For the setting method, see the NodeB Initial Configuration Guide.

l When the configuration file is downloaded to the NodeB and becomes effective, the state of theNodeBSpecial Status is automatically set to Installing. In this status, all reported alarms are screeneduntil the operator sets Special Status of NodeB to Normal.

Commissioning proceduresFigure 3-1 shows the procedures for commissioning the NodeB.

3 Commissioning the NodeB Through the USB Disk+M2000NodeB

Commissioning Guide


Issue 06 (2010-09-10)

Figure 3-1 Procedures for commissioning the NodeB through the USB+M2000



3-3

NOTE

l On-site operation on the NodeB side: Indicates that the field engineer commissions the NodeB at theNodeB side, including upgrading the software and downloading the data configuration file from theUSB disk, and checking the NodeB hardware status.

l Remote operation: indicates that the engineer commissions the NodeB on the M2000 in the centralequipment room, including checking the running status of the NodeB on the M2000, and obtainingthe commissioning report.

Procedure

Step 1 Insert the USB disk into the USB port on the WMPT of the NodeB. Choose appropriate operationbased on the active software version and data configuration of the NodeB.

If ... Then ...

The active software version and dataconfiguration are inconsistent with those tobe used

Go to Step 2.

The current software version and dataconfiguration are consistent with those to beused

Go to Step 4.

Step 2 Upgrade the NodeB software and download the data configuration file. For details, see 3.3Upgrading the NodeB Software and Downloading the Data Configuration File (on theNodeB Side) .

Step 3 Check the NodeB hardware status based on the LED state. For details, see 3.4 Checking theStatus of the NodeBHardware and Rectifying Faults (on the NodeB Side).

Step 4 Measure the NodeB VSWR. According to the CPRI LED status, check whether the VSWR isnormal. For details, see 3.5 Testing the NodeB Antenna VSWR Through the USB Disk (Onthe NodeB Side).

Step 5 Remove the USB disk.

Step 6 Wait till the transmission is available.

Step 7 Create a NodeB commissioning project on the M2000. Select Health Check. The M2000automatically checks the running status of the NodeB. For the detailed procedure for creating aNodeB commissioning project on the M2000, see 2.6 Creating a NodeB CommissioningProject.

Step 8 Obtain the commissioning report of the NodeB through the M2000. For the detailed procedure,see 2.9 Obtaining the NodeB Commissioning Report.

Step 9 Check the running status of the NodeB by viewing the NodeB commissioning report. For details,see 2.10 Checking the Running Status of the NodeB.

Step 10 Check the VSWR of the NodeB on the M2000 to check the installation of the antenna system.For details, see 2.11 Testing the NodeB VSWR on the M2000.

Step 11 Set the NodeB to the common state on the M2000 to recover the alarm reporting process. Fordetails, see 2.13 Setting the Device Status of the NodeB.


Commissioning Guide


Issue 06 (2010-09-10)

Step 12 Record the commissioning process and problems in the 5 Data Sheet for NodeBCommissioning, and then export a commissioning report.

----End

3.2 Preparing the USB Disk for On-Site CommissioningThe USB disk should be ready before it is used for on-site commissioning.

Procedure

Step 1 Prepare the USB disk with a LED that meets the following requirements: when there is no reador write operation on the USB disk, the LED on the USB disk is on; when there is any read orwrite operation on the USB disk, the LED on the USB disk is blinking.

Step 2 Check the compatibility of the USB disk with the NodeB. Do as follows to test the USB disk:Insert the USB disk into the USB port on the WMPT of a NodeB that runs normally, and waitfor 3 seconds. If the LED on the USB disk blinks once, it indicates that the USB disk is functional.If the USB disk fails the preceding test, replace the USB disk.

Step 3 Save the related files to the specified path of the USB disk.1. Prepare the NodeB software package, data configuration file, and VSWR check script file.

l Obtain the NodeB software package from the support website.

l The data configuration file can be made and exported through the CME. This is usuallyperformed by configuration engineers.

l The VSWR check script can be customized. The file name is STRVSWR.dat. The filecontent is as follows:[Config]VSWRTHD = aWhere, a indicates the VSWR threshold and can be set as required. The recommendedvalue is 1.5.

2. Store the files to the following path.l NodeB software: \\NodeB\Software\Software.csp

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

l VSWR check script file: \\NodeB\VswrTest\STRVSWR.dat

CAUTIONAfter you have saved the files from the PC into the USB disk, unplug the USB diskfollowing the system prompt. If not, errors may occur when you access the USB disk.

----End



3-5

3.3 Upgrading the NodeB Software and Downloading theData Configuration File (on the NodeB Side)

The NodeB supports software upgrade and data configuration file downloading directly fromthe USB disk. After the download, the NodeB automatically activates the software, and thenresets.

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

l The qualified USB disk is ready. For details, see 3.2 Preparing the USB Disk for On-SiteCommissioning.

ContextWhen the USB disk is plugged into the corresponding port on the WMPT in the BBU3900, theBBU3900 automatically detects the USB disk and installs the USB disk driver. After theinstallation, the NodeB automatically reads the software and data configuration file in the fixeddirectories of the USB disk and verifies their names and formats.

Pay attention to the following situations when upgrading the software and downloading dataconfiguration file from the USB disk:l By default, the NodeB downloads the software and data configuration file from the USB

disk by configuration. The NodeB also supports the supplementary download. For example,When the RRU is not connected to the BBU3900 through the optical cable, the softwareand data configuration file related to the RRU are not downloaded. After the RRU isconnected, the software and data configuration file related to the RRU are automaticallydownloaded from the USB disk.

l If the USB disk saves only the software, the NodeB automatically upgrades the software.

l If the USB disk is only saved with the data configuration file, the NodeB automaticallydownloads the data configuration file.

l In any of the following situations, the NodeB does not upgrade the software or downloadthe data configuration file from the USB disk.– The directory or the file does not exist.

– The file format is illegal.

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

– The data to be used in the configuration file is the same as the active configuration data.

Procedure

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


Commissioning Guide


Issue 06 (2010-09-10)

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

Step 2 The NodeB automatically downloads the software and data configuration file, and activates thesoftware. After the activation, the NodeB resets. Wait until the NodeB reset is complete. Fordetails on the status of the LED on the USB disk and the status of the RUN LED on the WMPTin this process, see Table 3-1.

Table 3-1 LEDs on the USB disk and the WMPT

Status of the LEDon the USB Disk

State of the RUNLED on theWMPT

Duration

When the USB disk isplugged into thecorresponding port onthe WMPT, theWMPT automaticallydetects the USB disk.

On Blinking (on for 1sand off for 1s)

About 1s to 2s

The WMPTdownloads thesoftware and dataconfiguration filefrom the USB disk.

Blinking Blinking (on for0.125s and off for0.125s)

About 12 minutes

The WMPT activatesthe software.

On Blinking (on for0.125s and off for0.125s)

About 3 to 4 minutes

The NodeB resets. On first, off for awhile, and thenblinking

On first, off for awhile, and thenblinking (on for0.125s and off for0.125s)

About 2 minutes

The NodeB runsnormally.

On Blinking (on for 1sand off for 1s)

-



3-7

NOTE

The time for downloading software and data configuration file from the USB disk and the time for theNodeB to activate the software may differ from those in Table 3-1, according to the version andconfiguration.

----End

3.4 Checking the Status of the NodeBHardware andRectifying Faults (on the NodeB Side)

This section describes how to check the BBU3900 hardware installation and how to rectify faults.You can locate the hardware faults regarding external ports and CPRI optical cable connectionby checking the LEDs on the boards 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 from the USB disk.The software is successfully activated and the NodeB is reset.

3.4.1 Checking the Status of LEDsThis section describes how to check the status of LEDs. By checking the status of LEDs on theboards of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 isfunctional.

3.4.2 Rectifying Common FaultsThis section describes how to rectify common faults when the LED indicates faults on the USBdisk or on the boards of the NodeB.

3.4.3 Guidelines for Rectifying FaultsThis section provides the guidelines for rectifying faults according to the guidelines for rectifyingfaults.

3.4.1 Checking the Status of LEDsThis section describes how to check the status of LEDs. By checking the status of LEDs on theboards of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 isfunctional.

LED status of the functional NodeB

When all the LED status of the BBU3900 boards and auxiliary devices coincide with those listedin Table 3-2, the NodeB is functional.

Table 3-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)


Commissioning Guide


Issue 06 (2010-09-10)

LED Status

ALM LEDs on the WMPT/WBBP/UTRP/PMU/AFMU/EMU/EMUA

Off

CPRI LEDs on the WBBP Steady 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 on the USB disk or on the boards of the NodeB, rectify the faults by referringto 3.4.2 Rectifying Common Faults. If the fault is not described in 3.4.2 Rectifying Common Faults,rectify the fault by referring to3.4.3 Guidelines for Rectifying Faults.

Figure 3-3 LED status of common faults

3.4.2 Rectifying Common FaultsThis section describes how to rectify common faults when the LED indicates faults on the USBdisk or on the boards of the NodeB.



3-9

Context

Table 3-3 Methods of rectifying common faults

If... You can InferThat...

Then...

The LED on theUSB disk is off

The NodeBsoftware fails to beupgraded from theUSB disk.

Insert the USB disk again, and upgrade thesoftware.If the software fails to be upgraded again, recordthe problem in the data sheet for the NodeBcommissioning, and then upgrade the software onthe LMT.

RUN LED oneach BBU boardblinks (on for0.125s and off for0.125s)

The software isbeing loaded or theboard is wronglypositioned in theslot of anotherboard.

Wait for five minutes and then check the status ofthe RUN LED again.If the RUN LED still blinks (on for 0.125s and offfor 0.125s), check whether the board is positionedin the correct slot. If not, reinstall the board.

The ALM LEDon the WMPT,WBBP, or UTRPis on

The board is faulty. Reinstall the board to check whether the fault isrectified. If the ALM LED still blinks, replace theboard.

The ALM LEDon the activeWMPT blinks

The external porton the activeWMPT is faulty.

l Check whether the RUN LED on the PMU,AFMU, EMU, or EMUA blinks (on for 0.125sand off for 0.125s). If the RUN LED on thoseboards blinks (on for 0.125s and off for 0.125s),check whether the RS485 signal cable isconnected properly.

l Check whether the dry contact alarm signalcable is properly connected to the correspondingport on the UPEU.

If the fault persists, record the fault and the LEDstatus of the WMPT in the data sheet for the NodeBcommissioning. Then, rectify the fault on the LMTor M2000.

A CPRI LED onthe WBBP issteady red

The CPRI opticalcable is improperlyconnected, or theoptical module isout of position.

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

l Check whether the CPRI optical cable isimproperly connected, for example, the receiveend and the transmit end are reversed. If it isimproperly connected, reinstall it. Then, wait for30 seconds, and check the status of the CPRILED again.

l Check whether the CPRI optical cable isdamaged. If it is damaged, replace it.


Commissioning Guide


Issue 06 (2010-09-10)

If... You can InferThat...

Then...

CPRI LED on theWBBP blinks red(on for 0.25s andoff for 0.25s)

The RRU or theWRFU is faulty.

Check whether an ALM LED on the RRU or theWRFU is on. If an LED is on, power on the RRUor the WRFU again. If the fault persists, replace theRRU or the WRFU.

CPRI LED on theWBBP blinks red(on for 1s and offfor 1s)

There is a VSWRalarm, an antennaalarm or an externalalarm on the RRUor the WRFU.

l Check whether a VSWR LED on the RRU or theWRFU is off. If the VSWR LED is not off, see3.4.3 Guidelines for Rectifying Faults torectify the fault.

l Check whether a ALM LED on the RRU or theWRFU 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. Ifthere is an external dry contact alarm, recordthe alarm in the data sheet for the NodeBcommissioning.

3.4.3 Guidelines for Rectifying FaultsThis section provides the guidelines for rectifying faults according to the guidelines for rectifyingfaults.

Procedure

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

If the RUN LEDIs...

You can InferThat...

Then...

Blinking (on for 1sand off for 1s)

The board worksproperly.

Go to Step 2.

On The power supply isavailable but theboard is faulty.

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

Blinking (on for0.125s and off for0.125s)

The software isbeing loaded or theboard is wronglypositioned in the slotof another board.

Wait for five minutes and then check the statusof the RUN LED again.If the RUN LED still blinks (on for 0.125s andoff for 0.125s), check whether the board ispositioned in the correct slot. If not, reinstallthe board.



3-11

If the RUN LEDIs...


Then...

Off The power supply isunavailable or theboard is faulty.

l Check whether the NodeB is powered on.

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

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

If the ALM LEDIs...


Then...

Off The board worksproperly.

Go to Step 3.

On The active WMPT isfaulty.


Blinking The external port onthe active WMPT isfaulty.

If the fault persists, record the fault and theLED status of the WMPT in the data sheet forthe NodeB commissioning. Then, rectify thefault on the LMT or M2000.l Check whether the RUN LEDs on other

boards blink (on for 0.125s and off for0.125s).– If the RUN LEDs on the PMU, AFMU,

EMU, or EMUA blink (on for 0.125s andoff for 0.125s), check whether the RS485signal cable is properly connected.

– If the RUN LEDs on the standby WMPT,WBBP, or UTRP blink (on for 0.125s andoff for 0.125s), reinstall the board tocheck whether the fault is rectified.

l Check whether the dry contact alarm signalcable is properly connected to thecorresponding port on the UPEU.

l Reinstall the active WMPT to checkwhether the fault is rectified.

l Reinstall the WBBP or the UTRP to checkwhether the fault is rectified.

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 nextstep based on the status of the ALM LED.


Commissioning Guide


Issue 06 (2010-09-10)

If the ALM LEDIs...


Then...

Off The board worksproperly.

Go to Step 4.

On The board is faulty. Reinstall the board to check whether the faultis rectified. If the fault persists, replace theboard.

Blinking The ports betweenthe active WMPTand the other BBUboards are faulty.


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

If the CPRI LEDIs...


Then...

Steady green The CPRI opticalcable is properlyconnected, and theRRU or the WRFUworks properly.

Go to Step 5.

Off The CPRI port is notconfigured.

Check whether the optical module is properlyconnected to the configured CPRI port. If not,reinstall the optical module to connect it to thecorrect CPRI port.

Steady red The CPRI opticalcable is improperlyconnected, or theoptical module isout of position.

l Check whether the optical module isinstalled. If not, install the optical module.

l Check whether the CPRI optical cable isimproperly connected, for example, thereceive end and the transmit end arereversed. If it is improperly connected,reinstall it. Then, wait for 30 seconds, andcheck the status of the CPRI LED again.

l Check whether the CPRI optical cable isdamaged. If it is damaged, replace it.

Blinking red (on for0.25s and off for0.25s)

The RRU or theWRFU is faulty.

Check whether an ALM LED on the RRU orthe WRFU is on. If the ALM LED is on, poweron the RRU or the WRFU again. If the faultpersists, replace the RRU or the WRFU.



3-13

If the CPRI LEDIs...


Then...

Blinking red (on for1s and off for 1s)

There is a VSWRalarm, an antennaalarm or an externalalarm on the RRU orthe WRFU.

l Check whether a VSWR LED on the RRUor the WRFU is off. If the VSWR LED isnot off, see Step 7 to rectify the fault.

l Check whether a ALM LED on the RRU orthe WRFU blinks. If it blinks, then:– Check whether the antenna devices are

properly connected to the RRU or theWRFU.

– Check whether there is an external drycontact alarm on the RRU or the WRFU.If there is an external dry contact alarm,record the alarm in the data sheet for theNodeB commissioning.

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

If the STATE LEDIs...


Then...

Blinking green The board worksproperly.

Go to Step 6.

Blinking red The board is faulty. Reinstall the board to check whether the faultis rectified. If the fault persists, replace theboard.

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

If the ALM LEDIs...


Then...

Off The module or thedevice worksproperly.

Go to Step 7.

On The module or thedevice is faulty.

Reinstall the module or power on the deviceagain to check whether the fault is rectified. Ifthe fault persists, record the fault and the LEDstatus in the Data Sheet for NodeBCommissioning. Then, rectify the fault on theLMT or M2000.

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


Commissioning Guide


Issue 06 (2010-09-10)

If the VSWR LEDIs...


Then...

Off No VSWR alarm isgenerated.

Go to Step 8.

On for 0.125s and offfor 0.125s

There are alarms onthe ANT_TX/RXAport and ANT_RXBport.

Check whether the antenna system is properlyconnected to the RRU or the WRFU.

On There is an alarm onthe ANT_TX/RXAport.

On for 1s and off for1s

There is an alarm onthe ANT_RXB port.

Step 8 Check the transmission status of the NodeB.

If... Then...

The NodeB uses the E1transmission mode

Perform the E1 loopback test. If the ALM LED on the boardwith the E1 port blinks, the E1 port at the NodeB side isproperly connected.

The NodeB uses the FEtransmission mode

Check the status of the green LED on the FE port. If thegreen LED blinks, the FE port is properly connected.

----End

3.5 Testing the NodeB Antenna VSWR Through the USBDisk (On the NodeB Side)

This section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed. You can test the VSWR through the USB disk on the NodeB side.

Prerequisitel The NodeB is powered on and passes the power-on check.

l The USB disk for on-site commissioning is ready. For details, see 3.2 Preparing the USBDisk for On-Site Commissioning.

Contextl When the USB disk is plugged into the corresponding port on the WMPT in the

BBU3900, the BBU3900 automatically detects the USB disk and installs the USB diskdriver. After the installation, the NodeB automatically reads the software and dataconfiguration file from the designated directories of the USB disk and verifies their namesand formats.



3-15

l When the system reads the VSWR script file STRVSWR.dat, the NodeB starts testing theVSWR.

l When the VSWR test through the USB disk on the NodeB side and the VSWR test on theM2000 side are performed at the same time: If the VSWR test through the USB disk onthe NodeB side is started before the VSWR test on the M2000 side, the M2000 displaysthat the NodeB is performing the VSWR test. If the VSWR test on the M2000 side is startedbefore the VSWR test through the USB disk on the NodeB side, the NodeB does not performthe VSWR test through the USB disk and records the failure result to the main control log.Meanwhile, the LED on the USB disk is off.

CAUTIONl Testing the VSWR interrupts the NodeB services. Therefore, you are advised to test the

VSWR in low traffic hours or after the NodeB services are isolated.

Procedure

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

CAUTIONl After the NodeB software and configurations are upgraded through the USB disk, remove

the USB disk and then plug it back into the USB port to start the VSWR test.l Before the VSWR test is started, the NodeB should run properly and the CPRI LED on the

WBBP should be steady green.

Figure 3-4 Plugging the USB disk into the USB port on the WMPT

Step 2 Wait for the NodeB to automatically test the VSWR. When the USB disk LED is off, the VSWRtest is complete. Observe the status of the CPRI LED on the WBBP.l If the CPRI LED blinks red (on for 1s and off for 1s), the RRU or WRFU has the VSWR

alarm. Clear the alarm by referring to step 4 in 3.4.3 Guidelines for Rectifying Faults. Then,go to Step 3.


Commissioning Guide


Issue 06 (2010-09-10)

l If the CPRI LED is steady green, the test result is normal and there is no VSWR alarm.Unplug the USB disk and end the VSWR test.

NOTE

After the VSWR test through the USB disk is complete on site, verify the test result by testing theantenna VSWR of the NodeB on the M2000. For details, see 2.11 Testing the NodeB VSWR on theM2000.

Step 3 Unplug the USB disk first and then plug it back into the USB port. When the USB disk LED isoff, observe the CPRI LED on the WBBP to check whether the VSWR is normal.l If the CPRI LED blinks red (on for 1s and off for 1s), the fault persists. Repeat Step 2 to

Step 3.l If the CPRI LED is steady green, the test result is normal and there is no VSWR alarm.

Unplug the USB disk and end the VSWR test.

----End



3-17

4 Commissioning the NodeB on the LMT

About This Chapter

This chapter describes how to perform the on-site commissioning of the NodeB on the LMT.You can upgrade the software, download the data configuration file, and check the running statusof the NodeB on the NodeB LMT.

4.1 Procedure for Commissioning the NodeB on the LMTThis section describes how to commission the NodeB on the LMT. You can upgrade theNodeB software, download the data configuration file, and check the running status of theNodeB on the LMT.

4.2 Upgrading the NodeB Software and Downloading the Data Configuration FileAfter the BootROM, software, and data configuration file of the NodeB are downloaded andactivated, the NodeB automatically resets and then the software and data configuration takeeffect.

4.3 Checking the Running Status of the NodeBThis chapter describes how to check the running status of the NodeB for the purpose of rectifyingfaults that occur during the operation and ensuring proper operation of the NodeB.

4.4 Testing the NodeB VSWR on the LMTThis section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed.

NodeBCommissioning Guide 4 Commissioning the NodeB on the LMT


4-1

4.1 Procedure for Commissioning the NodeB on the LMTThis section describes how to commission the NodeB on the LMT. You can upgrade theNodeB software, download the data configuration file, and check the running status of theNodeB on the LMT.

PrerequisiteBefore commissioning the NodeB, the NodeB, RNC, and M2000 should meet the followingrequirements:l The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary

devices, is completely installed and passes the installation check. The NodeB is poweredon and passes the power-on check.

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

Commissioning ProceduresFigure 4-1 shows the procedures for commissioning the NodeB.

Figure 4-1 Procedures for commissioning the NodeB on the LMT

4 Commissioning the NodeB on the LMTNodeB

Commissioning Guide


Issue 06 (2010-09-10)

Procedure

Step 1 Choose an appropriate operation based on the active software version and data configuration ofthe NodeB.

If ... Then ...

The active software version and dataconfiguration are inconsistent with those tobe used

Go to Step 2.

The active software version and dataconfiguration are consistent with those to beused

Go to Step 3.

Step 2 Upgrade the NodeB software and download the data configuration file on the LMT. For details,see 4.2 Upgrading the NodeB Software and Downloading the Data Configuration File.

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

Step 4 Check the NodeB VSWR on the LMT. For details, see 4.4 Testing the NodeB VSWR on theLMT.

Step 5 Record the commissioning process and problems in the 5 Data Sheet for NodeBCommissioning, and then export a commissioning report.

----End

4.2 Upgrading the NodeB Software and Downloading theData Configuration File

After the BootROM, software, and data configuration file of the NodeB are downloaded andactivated, the NodeB automatically resets and then the software and data configuration takeeffect.

4.2.1 Querying the Active Version of the NodeBThis section describes how to query the active version of the NodeB. Before upgrading theNodeB software, you should query the information of the active software version.

4.2.2 Upgrading the NodeB BootROMThis describes how to upgrade the NodeB BootROM software.

4.2.3 Upgrading the NodeB Software and Downloading the Data Configuration FileThis section describes how to upgrade the NodeB software and download the data configurationfile.

4.2.1 Querying the Active Version of the NodeBThis section describes how to query the active version of the NodeB. Before upgrading theNodeB software, you should query the information of the active software version.



4-3

Procedurel Run the LST VER command to query the NodeB software version and NodeB BootROM

version.

----End

4.2.2 Upgrading the NodeB BootROMThis describes how to upgrade the NodeB BootROM software.

Prerequisitel The FTP server works properly and is correctly connected to the NodeB on 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 tree of the Local Maintenance Terminal window, click the Maintenancetab.

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

Step 3 Select Upgrade BootROM in the dialog box.

Step 4 Click Next. The Upgrade BootROM dialog box is displayed.

Step 5 Click Modify and set the FTP server in the FTP Setting dialog box.

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

Table 4-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 ora specified FTP server. The built-in FTP server isstarted by default.

Use Specified FTPServer

IP address The FTP server can be started either from the localcomputer installed with the LMT application or fromanother computer. Here it refers to the IP address ofthe FTP server.

User Name This enables you to specify the user name for loggingin to the FTP server.

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

Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade BootROM dialog box isdisplayed.


Commissioning Guide


Issue 06 (2010-09-10)

Step 7 Select Download BootROM Package and then specify a path to download the BootROMpackage.

Step 8 Select Activate BootROM.

NOTE

The system downloads the BootROM package and then activates it.

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 ofthe patch upgrade is displayed in the dialog box. You may check the process by viewing thisdialog box.

----End

4.2.3 Upgrading the NodeB Software and Downloading the DataConfiguration File

This section describes how to upgrade the NodeB software and download the data configurationfile.

Prerequisitel The FTP server works properly and is correctly connected to the NodeB in the same intranet.

l There is no firewall between the FTP server and the NodeB.

l The FTP user can access the specified directory.

Procedure

Step 1 In the navigation tree of the Local Maintenance Terminal window, click the MaintenanceTab.

Step 2 Select Software Management > Software Update. The Software Upgrade dialog box isdisplayed.

Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed.

Step 5 Click Modify, and set the FTP server in the FTP Setting dialog box.

Table 4-2 describes the fields in the FTP Setting dialog box.

Table 4-2 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 ora specified FTP server. The built-in FTP server isstarted by default.



4-5

Field Description

Use Specified FTPServer

IP address The FTP server can be started either from the localcomputer installed with the LMT application or fromanother computer. Here it refers to the IP address ofthe FTP server.

User Name This enables you to specify the user name for loggingin to the FTP server.

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

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

Step 7 Select Downloading Data Configuration File, Download NodeB Software Package,Download by Configuration, Effective Data Configuration File, and Activate NodeBSoftware in sequence, and set the directory for downloading the data configuration file andNodeB software package.

NOTE

l You are advised to select Download by Configuration. If it is not selected, a dialog box is displayed,prompting that this may cause software download failure. Click OK to start downloading the software.Click Cancel to select again, and download the software by configuration.

l If you select Download by Configuration, the NodeB selectively downloads required board softwarepackages from the relay server according to the configured board type. In this manner, the total amountof data to be downloaded is reduced, thus reducing download time and saving storage space.

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

Step 9 Click Yes. The upgrading progress dialog box is displayed. The status and progress of the patchupgrade is displayed in the dialog box. You may check the process by viewing this dialog box.

CAUTIONl The NodeB is automatically reset, and the new version of the NodeB software is enabled

after the activation.l If the software activation fails, the NodeB software cannot operate properly. You need to

reactivate the NodeB software in the standby file directory or reinstall the NodeB software.

----End

4.3 Checking the Running Status of the NodeBThis chapter describes how to check the running status of the NodeB for the purpose of rectifyingfaults that occur during the operation and ensuring proper operation of the NodeB.

4.3.1 Commissioning SNTPThis section describes how to commission the Simple Network Time Protocol (SNTP) tosynchronize the time between NEs. The task facilitates the centralized maintenance andmanagement.


Commissioning Guide


Issue 06 (2010-09-10)

4.3.2 Checking the Status of a CellThis section describes how to check the status of a local cell or a logical cell. The task helps youto identify the running status of the active cell and perform OM on the cell.

4.3.3 Measuring the RTWPThis section describes how to measure the Received Total Wideband Power (RTWP). TheRTWP is the received wideband power in a UL channel band measured at the access point ofthe UMTS Terrestrial Radio Network Access (UTRAN). You can calibrate the gain of UL RFchannels through RTWP measurement. The RTWP measurement does not affect ongoingservices.

4.3.4 Monitoring the Output Power of the NodeBThis section describes how to monitor the output power of the NodeB, including the typicaloutput power and output power of each carrier.

4.3.5 Handling NodeB AlarmsThis section describes how to check active alarms and clear the alarms if any.

4.3.1 Commissioning SNTPThis section describes how to commission the Simple Network Time Protocol (SNTP) tosynchronize the time between NEs. The task facilitates the centralized maintenance andmanagement.

ContextApplication 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 system configuration.l On the RNC side: Start the SNTP server through 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.

Parameter ID Parameter Name Description

SW Switch of Time Sync Specifies whether synchronization isrequired.Value range: ON (synchronizationrequired), OFF (synchronization notrequired)Default value: none

IP SNTP Server IP Address Value range: 0.0.0.1 to 255.255.255.254Default value: none



4-7

Parameter ID Parameter Name Description

SP Synchronization Period Value range: 1 to 525600Unit: minuteDefault 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 successfulsynchronization of the SNTP client to the SNTP server, and whether the synchronization issuccessful.

If... Then...

The synchronization is successful End this task.

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

l Whether the IP address of the NodeB is correct

After the faults are rectified, go to Step 2 to set theparameters again.

----End

4.3.2 Checking the Status of a CellThis section describes how to check the status of a local cell or a logical cell. The task helps youto identify the running status of the active cell and perform OM on the cell.

Procedure

Step 1 Run the DSP LOCELL command to check the status of all local and logical cells of theNodeB.

If... Then...

The information about faults is displayed Rectify the faults based on the information.

No information about faults is displayed End the task.

----End

4.3.3 Measuring the RTWPThis section describes how to measure the Received Total Wideband Power (RTWP). TheRTWP is the received wideband power in a UL channel band measured at the access point ofthe UMTS Terrestrial Radio Network Access (UTRAN). You can calibrate the gain of UL RF


Commissioning Guide


Issue 06 (2010-09-10)

channels through RTWP measurement. The RTWP measurement does not affect ongoingservices.

PrerequisiteYou have logged in to the NodeB LMT.

Context

The reference standards for the RTWP measurement are as follows:

l If the NodeB is disconnected from the antenna system or carries a matched load, the reportedRTWP is about -108 dBm. If the NodeB is connected to the antenna system with the TMAstarted or carries a matched load, the reported RTWP is about -105 dBm.

l If the services are normal and the UL load reaches 75%, the RTWP is 6 dB higher than theRTWP measured when the NodeB carries no service.

NOTE

l If the reported RTWP is valid, a normal RTWP curve is displayed. The values on the vertical axiscorrespond to the reported RTWP values with the unit of 0.1 dBm.

l If the reported RTWP is invalid, an abnormal RTWP curve is displayed. The RTWP values for themain antenna form a horizontal line at the point marked -1120 (-112 dBm) on the vertical axis. TheRTWP values for the diversity antenna form a horizontal line at the point marked -1115 (-111.5 dBm)on the vertical axis. This error may lie in the absent WRFU, RHUB, RRU, broken link, or faultychannel. Rectify the faults.

Procedure


Step 2 Select Realtime Specific Monitoring > RTWP Measurement. The RTWP Measurementdialog box is displayed.

For the details of the parameters in the RTWP Measurement dialog box, see Interface Referencefor Measuring the RTWP.

Step 3 Set the corresponding parameters in the dialog box.

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

Step 5 To stop this test task, use one of the following methods:

l Method 1: Close the task monitoring window directly to stop all monitoring tasks displayedin the window.

l Method 2: Right-click the task on the monitoring task list and select Delete Task from theshortcut menu. The curve displayed for the task is deleted together with the task.

----End

Result

Table 4-3 describes the monitoring items.



4-9

Table 4-3 Monitoring items for the RTWP measurement

Item Description

Carrier 0 Rx Receive Freq The center frequency in the UL of carrier 0. Unit: 0.2 MHz

Carrier 0 Primary RTWP(0.1dBm)

The RTWP value for the main antenna in the UL of carrier 0.

Carrier 0 Secondary RTWP(0.1dBm)

The RTWP value for the diversity antenna in the UL of carrier0.

Carrier 1 Rx Receive Freq1 The center frequency in the UL of carrier 1. Unit: 0.2 MHz















NOTE

l One RF module can be configured with one to four carriers. The system outputs the RTWP value ofthe corresponding carrier based on the actual configuration.

l One carrier may be configured with main and diversity RX.

4.3.4 Monitoring the Output Power of the NodeBThis section describes how to monitor the output power of the NodeB, including the typicaloutput power and output power of each carrier.

PrerequisiteYou have logged in to the NodeB LMT.

Context

After the task is started, the system periodically reports the monitored typical power and theoutput power of each carrier according to the time interval.


Commissioning Guide


Issue 06 (2010-09-10)

The output power of the NodeB is associated with the configuration and specified services. Ifthe pilot power and typical output power are configured, the output power of the WRFU or RRUis about 3 dB greater than the pilot power when the NodeB carries no services. If the outputpower of the WRFU or RRU is considerably lower than the pilot power, the output power of theNodeB is abnormal.

The pilot power of the WRFU or RRU can be set to 33 dBm. The typical power can be set to 43dBm.

Procedure


Step 2 Select Realtime Specific Monitoring > Output Power Monitoring. The Output PowerMonitoring dialog box is displayed.

For the parameter details in the Output Power Monitoring dialog box, see Interface Referencefor Monitoring the Output Power

Step 3 Set the corresponding parameters in the dialog box.

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

Step 5 To stop this test task, use either of the following methods:l Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed

in the window.l Method 2: Right-click the task on the monitoring task list and select Delete Task from the

shortcut menu. The curve displayed for the task is deleted together with the task.

----End

ResultTable 4-4 describes the monitoring items.

Table 4-4 Monitoring items for the NodeB output power measurement

Item Description

Carrier Output Power(Channel No: X; Carrier No:Y; Unit: 0.1dBm)

Indicates the output power of Y carrier in X channel.The carrier output power is the actual output power of theRRU.

Channel Output Power(Channel No: X; Unit:0.1dBm)

Indicates the typical output power in X channel correspondingto the RF module.The channel output power is the ideal output power, which isthe theoretical output power.

4.3.5 Handling NodeB AlarmsThis section describes how to check active alarms and clear the alarms if any.



4-11

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 based on the alarm online help.

An active alarm related to the NodeBcannot be cleared

Record it in 5 Data Sheet for NodeBCommissioning.

----End

4.4 Testing the NodeB VSWR on the LMTThis section describes how to test the VSWR. The VSWR is used to verify if the antenna systemis correctly installed.

Prerequisitel You have logged in to the NodeB LMT.

l The NodeB does not provide any service or the services are isolated.

Context

An excessively large VSWR results in a short transmission distance and reduced cell coverage,affecting the normal operation of the system. The normal VSWR ranges from 1 to 2.0. TheVSWR less than 1.5 is preferred.

CAUTIONl Testing the VSWR interrupts the NodeB services. Therefore, you are advised to test the

VSWR in low traffic hours or after the NodeB services are isolated.

Procedure

Step 1 Run the STR VSWRTEST command to test the NodeB VSWR.

----End

Postrequisite1. Verify that the antenna system is correctly installed based on the measured VSWR.

2. Ensure that the NodeB services resume.


Commissioning Guide


Issue 06 (2010-09-10)

5 Data Sheet for NodeB Commissioning

This section provides the data sheet that is used to record the process and results of the NodeBcommissioning.

Table 5-1 Data Sheet for NodeB Commissioning

Site Name

NodeB Model

Commission Time

CommissioningEngineer

CommissioningResult

□ Successful; □ Failed

Commissioning Item Conclusion HandlingExceptional Cases

CommissioningPreparation Phase

Faults in NodeB hardwareinstallation are cleared.

□ Yes; □ No

Transmission links between theNodeB and the RNC are ready.

□ Yes; □ No

Negotiation data of the NodeBto be commissioned is added tothe RNC.

□ Yes; □ No

The required NodeB software,BootROM software, and dataconfiguration file are ready.

□ Yes; □ No

CommissioningPhase

The NodeB software,BootROM software aresuccessfully upgraded.

□ Yes; □ No

The data configuration file issuccessfully downloaded.

□ Yes; □ No

NodeBCommissioning Guide 5 Data Sheet for NodeB Commissioning


5-1

The NodeB hardware status ischecked.

□ Yes; □ No

The running status of theNodeB is checked.

□ Yes; □ No

The NodeB VSWR is checked. □ Yes; □ No

Problem Description Impact

Unsolved ProblemsAfterCommissioning

Component P/N

Faulty BoardRecord

5 Data Sheet for NodeB CommissioningNodeB

Commissioning Guide


Issue 06 (2010-09-10)

6 Communication Ports on the NodeB

This section describes the communication ports on the NodeB.

Table 6-1 describes the communication ports on the NodeB.

Table 6-1 Communication ports of the NodeB

Protocol

A Side ASidePortNumber(RX)

B Side B SidePortNumber(TX)

Service AuthorityManagement

TCP

NodeB 6000

LMT 1024to65535

For the LMT todeliver themaintenancecommand to theNodeB

User name/password

TCP

NodeB 6001

LMT 1024to65535

For the NodeB toreport alarm

None

TCP

NodeB 6006

LMT 1024to65535

For maintenance, theformat is BIN.

None

TCP

NodeB 6007

M2000server

1024to65535

For M2000;integration port forMML, alarm, andBIN

User name/password

TCP

NodeB 20 Site debugconsole

1024to65535

For FTP; debugmode; localmaintenance FE portonly

None

NodeBCommissioning Guide 6 Communication Ports on the NodeB


6-1

Protocol

A Side ASidePortNumber(RX)

B Side B SidePortNumber(TX)

Service AuthorityManagement

TCP


1024to65535

For FTP; debugmode; localmaintenance FE portonly

User name/password

TCP


1024to65535

For telnet; debugmode; localmaintenance FE portonly

User name/password

UDP

NodeB 67/68

M2000server orany otherDHCPserver

67/68 For DHCP services None

UDP

M2000 serveror any otherDHCP server

67/68

NodeB 67/68 For DHCP services None

UDP

M2000 server,RNC BAM, orany other SNTPserver

123 NodeB 1024to65535

For synchronizingSNTP clock

None

TCP

LMT, M2000server, RNCBAM, or anyother FTPserver

20 NodeB 1024to65535

For FTP; upload thedata configurationfile and logs from theNodeB to the FTPserver, anddownload the dataconfiguration fileand softwarepackages from theFTP server to theNodeB

None

TCP

LMT, M2000server, RNCBAM, or anyother FTPserver

21 NodeB 1024to65535

For FTP control User name/password

6 Communication Ports on the NodeBNodeB

Commissioning Guide


Issue 06 (2010-09-10)

NodeB Commissioning Guide(V200_06)

Documents

Transcript of NodeB Commissioning Guide(V200_06)