NodeB Commissioning Guide(V200_06)

NodeB V200

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

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase 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 representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

support@huawei.com

Issue 06 (2010-09-10)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

NodeB Commissioning Guide

About This Document

About This Document

Overview This document describes the guidelines for commissioning and verifying the NodeB after it is installed. The commissioning and verification guidelines involves upgrading the software, downloading the data configuration file, and checking the hardware installation and the running status of the NodeB. These guidelines ensure that the NodeB operates as required.

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

Product Version

BTS3900 WCDMA (hereafter referred to as BTS3900)

V200R010

BTS3900A WCDMA (hereafter referred to as BTS3900A)

V200R010

DBS3900 WCDMA (hereafter referred to as DBS3900)

V200R010

iDBS3900 WCDMA (hereafter referred to as iDBS3900)

V200R010

V200R011

V200R011

V200R011

V200R011

Intended Audience This document is intended for field engineers.

Issue 06 (2010-09-10)


iii


About This Document

Organization 1 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 remote commissioning on multiple NodeBs on the M2000 in a central equipment room. The commissioning 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 USB disk and the remote commissioning on the M2000. You can upgrade the software and download the data configuration file by using the USB disk, check the VSWR, and then check the running status 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 status of 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 NodeB commissioning. 6 Communication Ports on the NodeB This section describes the communication ports on the NodeB.

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

Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time.

iv


Issue 06 (2010-09-10)


About This Document

Symbol

Description Provides additional information to emphasize or supplement important points of the main text.

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

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

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

Italic

Book titles are in italics.

Courier New

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

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

Description

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 by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

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

Issue 06 (2010-09-10)


v


About This Document

Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.

>

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

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

Description

Key

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

Key 1+Key 2

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

Key 1, Key 2

Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

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

vi

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

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


Issue 06 (2010-09-10)


Contents

Contents About This Document...................................................................................................................iii 1 Changes in the NodeB Commissioning Guide....................................................................1-1 2 Commissioning the NodeB on the M2000.............................................................................2-1 2.1 Procedure for Commissioning the NodeB on the M2000...............................................................................2-3 2.2 Information Related to the Commissioning of the NodeB on the M2000......................................................2-6 2.2.1 NodeB Commissioning Items................................................................................................................2-6 2.2.2 Introduction to the NodeB Commissioning Window.............................................................................2-7 2.2.3 NodeB Standing Wave Ratio Test Tab Page.........................................................................................2-9 2.3 Automatically Searching for NodeBs...........................................................................................................2-10 2.4 Checking Software Version Information on the Server................................................................................2-11 2.5 Uploading the NodeB Software and BootROM Software............................................................................2-11 2.6 Creating a NodeB Commissioning Project...................................................................................................2-12 2.7 Managing the NodeB Commissioning Project..............................................................................................2-14 2.7.1 Adjusting the Commissioning Object..................................................................................................2-15 2.7.2 Starting or Stopping a NodeB Commissioning Task...........................................................................2-16 2.7.3 Reuploading the NodeB Configuration File.........................................................................................2-16 2.8 Viewing the NodeB Commissioning Progress..............................................................................................2-17 2.9 Obtaining the NodeB Commissioning Report..............................................................................................2-18 2.10 Checking the Running Status of the NodeB................................................................................................2-18 2.11 Testing the NodeB VSWR on the M2000...................................................................................................2-19 2.12 Testing NodeB Services..............................................................................................................................2-20 2.13 Setting the Device Status of the NodeB......................................................................................................2-21

3 Commissioning the NodeB Through the USB Disk+M2000.............................................3-1 3.1 Procedure for Commissioning the NodeB Through the USB+M2000...........................................................3-2 3.2 Preparing the USB Disk for On-Site Commissioning.....................................................................................3-5 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side) .........3-6 3.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-8 3.4.2 Rectifying Common Faults....................................................................................................................3-9 3.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 Issue 06 (2010-09-10)


vii


Contents

4.1 Procedure for Commissioning the NodeB on the LMT..................................................................................4-2 4.2 Upgrading the NodeB Software and Downloading the Data Configuration File............................................4-3 4.2.1 Querying the Active Version of the NodeB...........................................................................................4-3 4.2.2 Upgrading the NodeB BootROM...........................................................................................................4-4 4.2.3 Upgrading the NodeB Software and Downloading the Data Configuration File...................................4-5 4.3 Checking the Running Status of the NodeB....................................................................................................4-6 4.3.1 Commissioning SNTP............................................................................................................................4-7 4.3.2 Checking the Status of a Cell.................................................................................................................4-8 4.3.3 Measuring the RTWP.............................................................................................................................4-8 4.3.4 Monitoring the Output Power of the NodeB........................................................................................4-10 4.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

viii


Issue 06 (2010-09-10)


Figures

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

Issue 06 (2010-09-10)


ix


Tables

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

Issue 06 (2010-09-10)


xi


1

1 Changes in the NodeB Commissioning Guide

Changes in the NodeB Commissioning Guide

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 Software and Downloading the Data Configuration File

The operations of upgrading the NodeB software and downloading the data configuration file on the LMT are optimized.

3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the NodeB Side)

The method of verifying the on-site Voltage Standing Wave Ratio (VSWR) test result on the M2000 is updated. That is, you can verify the on-site VSWR test result through the fault diagnosis function on the M2000 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. Compared with issue 04 (2009-01-22), this issue does not delete any topic. Issue 06 (2010-09-10)


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.

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

Description

3 Commissioning the NodeB Through the USB 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.

Compared with issue 02 (2008-08-15), this issue incorporates the following changes: Topic

Description

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



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)

Compared with issue 01 (2008-03-30), this issue incorporates the following changes:

1-2

Topic

Description

NodeB Commissioning Procedure


Checking the running status of the NodeB

The method is optimized.


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.

Issue 06 (2010-09-10)


1-3


2

2 Commissioning the NodeB on the M2000

Commissioning the NodeB on the M2000

About This Chapter This chapter describes how to commission the NodeB on the M2000. You can perform the remote commissioning on multiple NodeBs on the M2000 in a central equipment room. The commissioning 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 M2000 This section describes how to commission the NodeB on the M2000. After the NodeB hardware is installed, you can commission the NodeB. 2.2 Information Related to the Commissioning of the NodeB on the M2000 Before commissioning the NodeB on the M2000, read the following information carefully: 2.3 Automatically Searching for NodeBs This section describes how to automatically search for NodeBs. The automatic searching function helps you know information about the NodeBs under an RNC such as the total number of NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NodeBs whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated. 2.4 Checking Software Version Information on the Server This 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 to the M2000 by checking the software version information. 2.5 Uploading the NodeB Software and BootROM Software This section describes how to upload the well prepared NodeB software and BootROM software on the M2000 client to the associated path of the M2000 server. 2.6 Creating a NodeB Commissioning Project This section describes how to create a NodeB commissioning project. In this way, the NodeBs that meet the requirements can automatically perform commissioning. In addition, the information about the commissioning process is displayed on the M2000 client. When a commissioning project is created successfully, the M2000 creates a commissioning task for each NodeB in the commissioning project. 2.7 Managing the NodeB Commissioning Project Issue 06 (2010-09-10)


2-1



This chapter describes how to manage the NodeB commissioning project. To improve the commissioning efficiency, the M2000 provides the NodeB automatic commissioning function. Users only need to monitor the commissioning process. After the NodeB commissioning process is complete, the users obtain and analyze the commission report and check whether the commissioning process is normal. Through the NodeB commissioning project management function of the M2000, users can modify the commissioning objects, start or stop the NodeB commissioning task, or upload the NodeB data configuration file required for the commissioning again. 2.8 Viewing the NodeB Commissioning Progress This section describes how to view the NodeB commissioning progress. You can obtain the information about the progress of the commissioning project by viewing the NodeB commissioning project and the NodeB commissioning task within the project. 2.9 Obtaining the NodeB Commissioning Report This section describes how to obtain the NodeB commissioning report. You can learn the NodeB commissioning status by viewing the NE commissioning report on the M2000. 2.10 Checking the Running Status of the NodeB This section describes how to check the running status of the NodeB by analyzing the commissioning report of the NodeB. 2.11 Testing the NodeB VSWR on the M2000 This section describes how to test the VSWR. The VSWR is used to verify if the antenna system is correctly installed. You can test the VSWR of multiple NodeBs on the M2000. 2.12 Testing NodeB Services The service dialing test is to check that the NodeB can provide all kinds of services. 2.13 Setting the Device Status of the NodeB If the NodeB is in Install status during commissioning, you need to change Device Status of the NodeB to Normal to recover the alarm reporting process.

2-2


Issue 06 (2010-09-10)



2.1 Procedure for Commissioning the NodeB on the M2000 This section describes how to commission the NodeB on the M2000. After the NodeB hardware is installed, you can commission the NodeB.

Prerequisite Before commissioning the NodeB, the NodeB, RNC, and M2000 must meet the following requirements: 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 on 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 is recorded.

l

The M2000 server is installed with the mediation software corresponding to the target version 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

l

During the deployment of a site, the NodeB may report plenty of alarms that need not be handled by the operator. Such alarms can be automatically cleared. A special alarm handling mechanism is 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 changes to Normal, the alarms that are not cleared in the special status are reported again as common alarms.

l

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

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

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

Issue 06 (2010-09-10)


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.3 Automatically Searching for NodeBs.

2-4


Issue 06 (2010-09-10)



If...

Then...

The NodeB to be commissioned is successfully detected

Go to Step 2.

The NodeB to be commissioned cannot be detected

The communication between the M2000 and the NodeB fails. Contact the maintenance engineers to commission the transmission channels till the M2000 detects the NodeB to be 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 the Server. If...

Then...

The NodeB software and BootROM software are uploaded to the M2000 server

Go to Step 4.

The NodeB software and BootROM software are not uploaded to the M2000 server

Go to Step 3.

Step 3 Upload the NodeB software and BootROM software to the M2000 server. For the detailed uploading 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 NodeB Commissioning Project. Step 5 The M2000 performs the specified commissioning items automatically. Check the NodeB commissioning progress in the NodeB Commissioning window. For details, see 2.8 Viewing the 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 NodeB Commissioning, and then export a commissioning report. ----End

Issue 06 (2010-09-10)


2-5



2.2 Information Related to the Commissioning of the NodeB on the M2000 Before commissioning the NodeB on the M2000, read the following information carefully: 2.2.1 NodeB Commissioning Items This 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, and health check. When setting the NodeB commissioning task, you can choose one or multiple commissioning items according to the actual requirements. 2.2.2 Introduction to the NodeB Commissioning Window This section describes the NodeB commissioning window, which helps you better know the components and function of each component on the window. 2.2.3 NodeB Standing Wave Ratio Test Tab Page This section describes the components of the NodeB Standing Wave Ratio Test tab page and the functions of the components.

2.2.1 NodeB Commissioning Items This 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, and health check. When setting the NodeB commissioning task, you can choose one or multiple commissioning items according to the actual requirements. For details about NodeB commissioning items, see Table 2-1. Table 2-1 NodeB commissioning items

2-6

NodeB Commissionin g Items

Description

Clock synchronization

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

Downloading the BootROM

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

Activating the BootROM

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

Downloading the software

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

Activating the software

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


Issue 06 (2010-09-10)



NodeB Commissionin g Items

Description

Downloading and activating the data configuration file

Download the data configuration files on the server to the related NodeB. You can click Upload new config file to upload the saved configuration file on the M2000 server.

Health check

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

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

NodeB Commissioning Function The NodeB commissioning has the following functions: l

Manage the NodeB commissioning project and perform the creation, adjustment, and refreshment for the commissioning project.

l

Monitor the NodeB commissioning progress.

l

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

NodeB Commissioning Window The NodeB commissioning window consists of the following five parts: Projects, Survey NodeBs, NodeBs Commissioning Task, NodeB Check Information, and ButtonsButtons, as shown in Figure 2-2.

Issue 06 (2010-09-10)


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 projects created are displayed.

2

Survey NodeBs

On the Survey NodeBs tab page, all the current existing NodeBs are displayed. Enter the name of the NodeB in Search, and then the system directly locates it.

2-8

3

NodeB Check Information

In the NodeB check information area, the detailed information of the NodeB commissioning process is displayed.

4

NodeBs Commissioning Task

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


Issue 06 (2010-09-10)



Number

Field

Description

5

Buttons

The buttons perform different operations and achieve corresponding functions.

2.2.3 NodeB Standing Wave Ratio Test Tab Page This section describes the components of the NodeB Standing Wave Ratio Test tab page and the 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

Issue 06 (2010-09-10)

No.

Field

Description

1

Navigation tree

All the NEs enlisted in the network are displayed in the Root area, such as the RNC and NodeB.

2

Query Result

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


2-9



No.

Field

Description

3

Function buttons

Click different buttons to perform different functions.

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

Prerequisite l

You have logged in to the M2000 client.

l

The RNCs are well connected to the M2000.

l

The NodeB mediation layer is installed on the M2000.

l

Based on the actual scenario, the NodeB maintenance channel supports the IP protocol stack, ATM protocol stack, and dual stack. The NodeB supports dual maintenance channels. When creating the NodeB, you can set two IP addresses. The primary address is the IP address of the ATM network. The secondary address is the IP address of the IP bearing network. Neither the primary nor the secondary IP addresses can be duplicate with that of other NodeBs, even on a different network. The NodeB can be connected to the network on condition that either of the IP addresses is valid. After the NodeB is disconnected exceptionally, it automatically uses the current IP address to attempt reconnections. If the attempt fails for five times in succession, the NodeB uses the other IP address for the connection.

l

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

Context

The purpose of Dynamic Host Configuration Protocol (DHCP) is to provides configuration information such as IP address to the Internet host in a TCP/IP network. The DHCP server can dynamically assigns IP addresses to an Internet host. l

When the maintenance channel supports the ATM protocol stack, you can validate the remote maintenance channel by using the ATM BOOTP technology.

l

The process for automatically discovering the NodeB is as follows:

l

2-10

1.

The M2000 obtains from the database the information about the NodeB managed by the related RNC, such as NodeBID, NodeB name, and the NodeB IP addresses.

2.

The M2000 obtains from the DHCP the information about the NodeB, such as NodeBID, NodeB name, and the NodeB IP addresses.

3.

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

4.

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

NodeBs can be reparented. Therefore, the NodeBs that need to be deleted are not deleted automatically when they are found automatically. Instead, they are marked as delete status Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 06 (2010-09-10)



and displayed as disconnected. In this case, you need to determine whether the disconnected NodeBs need to be deleted, reparented, or reconnected.

Procedure Step 1 Choose Topology > Main Topology. The Main Topology window is displayed. Step 2 From the topology navigation tree or the topology view, right-click an RNC and choose Search NodeB on the shortcut menu. In the Main Topology window, the system automatically synchronizes the information about the NodeBs managed by a specific RNC, such as the total number of NodeBs under one RNC, the number of NodeBs that connect to the M2000, the number of NEs whose names are duplicate, and the number of NodeBs whose IP addresses are duplicated. NOTE

l

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

l

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

----End

Result The searched NodeBs are displayed on the physical topology view.

2.4 Checking Software Version Information on the Server This 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 to the M2000 by checking the software version information.

Procedure Step 1 Choose Software > Browse. The Software Browser dialog box is displayed. Step 2 In the navigation tree of the NM Server tab page, select the NodeB to be checked. Step 3 In the list on the right, select the Software tab page. You can check the status of the software version information stored on the server. ----End

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

Prerequisite The connection between the client and the M2000 is functional. Issue 06 (2010-09-10)


2-11



Procedure Step 1 Choose Software > Filter Transfer Wizard. The Select General Parameters dialog box is displayed. Step 2 In Direction, select From Client To NM. Step 3 Choose OMC Server > NodeB > NodeB Type > Software in Server Path. Step 4 Click Next. The Select dialog box is displayed. Step 5 Select the folder which the NodeB software and the BootROM software to be upgraded are saved in. Step 6 Click Finish. On the FTP Task tab at the bottom of the Software Browser window, the process of uploading is displayed. NOTE

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

----End

2.6 Creating a NodeB Commissioning Project This section describes how to create a NodeB commissioning project. In this way, the NodeBs that meet the requirements can automatically perform commissioning. In addition, the information about the commissioning process is displayed on the M2000 client. When a commissioning project is created successfully, the M2000 creates a commissioning task for each NodeB in the commissioning project.

Prerequisite l

The connection between the NodeB and the M2000 is functional.

l

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

l

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

Procedure Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. Step 2 Click New. The – Please Select The NodeBs To Be Surveyed dialog box is displayed. Step 3 Set the Project Name and select the NodeBs that need to be commissioned.

2-12


Issue 06 (2010-09-10)


2 Commissioning the NodeB on the M2000 TIP

l

Choose one or multiple conditions from RNC, NodeB Type, Version, and DualMode to regroup the NEs in the NE navigation tree. If you choose one or multiple conditions, but the M2000 fails to obtain the selected conditions, then the NodeB is displayed under a nameless parent node. For example, if the RNC is selected as one condition, but the M2000 fails to obtain the information about the RNC that the NodeB belongs to, then, the NodeB is displayed under a nameless parent node.

l

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

l

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

l

After a commissioning project is created, you can add NodeBs to be commissioned in this commissioning project. For details, see 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, choose a BootRom version from the drop-down list of BootRom Version for each NodeB in the commissioning project. Step 7 Set the software version. If the Software Download or the Software Activate commissioning item is selected, choose a software version from the drop-down list of Software Version for each NodeB in the commissioning 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 are saved. NOTE

3.

l

You need to save the NodeB configuration files in the folder named by the corresponding NodeB, and save the folder in client installation path. The default client installation path is \client \Data\NodeBSurvey\NodeBConfig.

l

You can upload the configuration files in batches.

l

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

Click Upload Config To Server. The NodeB configuration files in the specified save path are uploaded to the server.

Step 9 Click Finish. The system displays the following message: Do you want to run this project now? Step 10 Click Yes to run the commissioning project immediately.

Issue 06 (2010-09-10)


2-13



NOTE

l

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

l

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

l

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

----End

Postrequisite l

To view the commissioning progress of a NodeB commissioning task, see 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 Project This chapter describes how to manage the NodeB commissioning project. To improve the commissioning efficiency, the M2000 provides the NodeB automatic commissioning function. Users only need to monitor the commissioning process. After the NodeB commissioning process is complete, the users obtain and analyze the commission report and check whether the commissioning process is normal. Through the NodeB commissioning project management function of the M2000, users can modify the commissioning objects, start or stop the NodeB commissioning task, or upload the NodeB data configuration file required for the commissioning again. 2.7.1 Adjusting the Commissioning Object This section describes how to adjust the commissioning object. You can add or delete the NodeBs to be commissioned in a commissioning project. The M2000 creates a commissioning task for each NodeB in a commissioning project. If you need to change a commissioning item in a commissioning project, you have to delete this project and create a new commissioning project to meet your requirements. 2.7.2 Starting or Stopping a NodeB Commissioning Task This 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 task when it is required. 2.7.3 Reuploading the NodeB Configuration File This 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. 2-14


Issue 06 (2010-09-10)



2.7.1 Adjusting the Commissioning Object This section describes how to adjust the commissioning object. You can add or delete the NodeBs to be commissioned in a commissioning project. The M2000 creates a commissioning task for each NodeB in a commissioning project. If you need to change a commissioning item in a commissioning project, you have to delete this project and create a new commissioning project to meet your requirements.

Prerequisite Some NodeB commissioning tasks are created.

Procedure Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. Step 2 Perform the following operations to adjust the commissioning object according to the actual requirements. Adding/Deleting a NodeB

Operation

Adding a NodeB

1. In Projects, right-click the commissioning project to which a NodeB is added, and then choose Add NodeBs To Project from the shortcut menu. 2. In – Please Select The NodeBs To Be Surveyed, select one or multiple NodeBs. Click Next. 3. If you select the CongifFile Download commissioning item when creating a commissioning task, you can upload the NodeB data configuration files to the server again. For details about how to upload the NodeB configuration files, see 2.7.3 Reuploading the NodeB Configuration File.

Deleting a NodeB

Two methods available for deleting a NodeB in a commissioning project are as follows: Deleting a NodeB through Projects and deleting a NodeB through Survey NodeBs. To delete a NodeB through Projects, perform the following operations: 1. In Projects, choose the project from which a NodeB is deleted. 2. In the list of commissioning tasks, right-click the NodeB commissioning task, and then choose Delete NodeBs From Project. To delete a NodeB through Survey NodeBs, perform the following operations: 1. In Survey NodeBs, select a NodeB node according to the NodeB name. You can locate the required NodeB quickly by entering key words in the Search text box. 2. In the list of commissioning tasks, right-click the NodeB commissioning task, and then choose Delete NodeBs From Project.

Issue 06 (2010-09-10)


2-15



----End

2.7.2 Starting or Stopping a NodeB Commissioning Task This 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 task when it is required.


Context l

Running commissioning tasks cannot be restarted.

l

Finished commissioning tasks cannot be stopped.

Procedure Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. Step 2 In Projects, choose the commissioning project where the NodeB commissioning task exists. On the Survey NodeBs tab page, you can select the NodeB nodes according to the NodeB name. Step 3 In the commissioning task list in the right pane, start or stop a commissioning task as required. Operation Type

Procedure

Start

Right-click a commissioning task that needs to be restarted, and then choose Start NodeBs Commissioning Task.

Stop

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

----End

2.7.3 Reuploading the NodeB Configuration File This 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 Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. 2-16


Issue 06 (2010-09-10)



Step 2 In Projects, right-click the commissioning project whose configuration files need to be uploaded again, and then choose Upload Config. Step 3 In – Please Select The NodeBs To Be Surveyed, click Next. The – Configuration Setting window is displayed. Step 4 Click Upload new config file. Step 5 In Choose Config Directory, specify the directory where the NodeB configuration files are placed. The NodeB configuration files are saved in the folders named by the corresponding NodeB name. All the folders that save the NodeB configuration files are saved in a parent folder, such as NodeBConfig. NOTE

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

Step 6 Click Upload Config To Server. The mapping NodeB configuration files are uploaded to the server. Step 7 Click Finish. ----End

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


Procedure Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. You can query the status and progress of a commissioning project and those of a commissioning task within the project. Step 2 View the status of a commissioning project. The Projects tab page lists all the commissioning projects on the M2000. A commissioning project can be in one of the following three status: Waiting, Running, and Finished. Step 3 View the progress of a commissioning task.

Issue 06 (2010-09-10)


2-17



NOTE

l

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

l

On the NodeB Check Information tab page, monitor the detailed information about a NodeB commissioning task. You can also right-click the blank area on this tab page, and then choose Clean All Messages to delete all the commissioning information displayed in this field.

l

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

----End

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


Procedure Step 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is displayed. Step 2 In Projects, right-click the project whose NodeB commissioning report is required, and then choose Get Project Report. The browser automatically opens and displays the content of the commissioning report. The check items of the commissioning report consist of configuration status, cells, IPRAN status, and environment. You can learn the entire commissioning process by analyzing the commissioning report. NOTE

l

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

l

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

----End

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

Prerequisite

2-18

l

The NodeB hardware installation is checked. The transmission links connected to the RNC are ready. The current version of the related software and data configuration file is consistent with the requirement.

l

You have logged in to the M2000 client, and created the NodeB. The NodeB commissioning project is complete, and the NodeB commissioning report is obtained. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 06 (2010-09-10)


2 Commissioning the NodeB on the M2000 NOTE

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

Procedure Step 1 Open the obtained NodeB commissioning report and check the content of the report. In this way, you can check the running status of the NodeB. Step 2 Handle the existing alarms based on the commissioning report. If...

Then...

An alarm is generated

Handle the alarm according to the Alarm Reference.

An active alarm cannot be cleared

Record the alarm in the 5 Data Sheet for NodeB Commissioning.

----End

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

Prerequisite l

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 power amplifier (PA), affecting the normal operation of the system. The normal VSWR ranges from 1 to 2.0. The VSWR less than 1.5 is preferred.

CAUTION 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 Choose Maintenance > Standing Wave Ratio Test > Standing Wave Ratio Test. The Standing Wave Ratio Test tab page is displayed. Issue 06 (2010-09-10)


2-19



NOTE

l

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

l

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

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

CAUTION The navigation tree on the right pane of the Standing Wave Ratio Test tab page cannot refresh the NE information automatically. Therefore, you need to click Refresh to manually refresh the NE information. Step 3 Click Query. Then click Yes in the displayed dialog box. The system displays a message VSWR query will impact the system service greatly! 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 M2000 Operator Guide.

----End

Postrequisite 1.

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

2.

Ensure that the NodeB services resume.

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

Prerequisite

2-20

l

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 CELL at the RNC to verify them. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 06 (2010-09-10)



l

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

l

Check voice service.

Procedure

l

Test method

Expected result

UE calls local fixed line telephone

Voice is clear without obvious noise.

Local fixed line telephone calls UE


UE 1 calls UE 2


Check CS streaming service. Test method

Expected result

UE 1 originates video service to UE 2

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

l

Check PS service. Test method

Expected result

UE activates data service and browses web pages

Web browsing is normal.

----End

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

Context l

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 Mode Alarm Filter tab page is displayed. Issue 06 (2010-09-10)


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

2-22


Issue 06 (2010-09-10)


3


Commissioning the NodeB Through the USB Disk+M2000

About This Chapter This chapter describes how to commission the NodeB with the combination of a on-site USB disk and the remote commissioning on the M2000. You can upgrade the software and download the data configuration file by using the USB disk, check the VSWR, and then check the running status of the NodeB on the M2000. 3.1 Procedure for Commissioning the NodeB Through the USB+M2000 On the NodeB side, you can upgrade the NodeB software and data configurations from the USB disk, check whether the hardware status is normal according to the LED status, and check whether the NodeB VSWR meets the requirements. After the operations on the NodeB side are complete, check the running status of the NodeB on the M2000. 3.2 Preparing the USB Disk for On-Site Commissioning The 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 NodeB Side) The NodeB supports software upgrade and data configuration file downloading directly from the USB disk. After the download, the NodeB automatically activates the software, and then resets. 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 connection by 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 system is correctly installed. You can test the VSWR through the USB disk on the NodeB side.

Issue 06 (2010-09-10)


3-1



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

Prerequisite Before commissioning the NodeB, the NodeB, RNC, and M2000 should meet following requirements: 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 check and is powered on.

l

The hardware of the RNC is installed and commissioned, and the system works properly. The negotiated data of the NodeB to be commissioned is configured and recorded.

l

The M2000 server is installed with the mediation software corresponding to the target version 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 the operators. Such alarms can be automatically cleared. A special alarm handling mechanism is integrated into the NodeB from V200R011C00SPC210. When the NodeB is in a special state, for example, newly deployed, all reported alarms are screened. When the NodeBSpecial Status changes into the Normal 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 the NodeB 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 the NodeBSpecial Status is automatically set to Installing. In this status, all reported alarms are screened until the operator sets Special Status of NodeB to Normal.

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

3-2


Issue 06 (2010-09-10)



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

Issue 06 (2010-09-10)


3-3



NOTE

l

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

l

Remote operation: indicates that the engineer commissions the NodeB on the M2000 in the central equipment room, including checking the running status of the NodeB on the M2000, and obtaining the commissioning report.

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

Then ...

The active software version and data configuration are inconsistent with those to be used

Go to Step 2.

The current software version and data configuration are consistent with those to be used

Go to Step 4.

Step 2 Upgrade the NodeB software and download the data configuration file. For details, see 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side) . Step 3 Check the NodeB hardware status based on the LED state. For details, see 3.4 Checking the Status 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 is normal. For details, see 3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the 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 M2000 automatically checks the running status of the NodeB. For the detailed procedure for creating a NodeB commissioning project on the M2000, see 2.6 Creating a NodeB Commissioning Project. 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. For details, see 2.13 Setting the Device Status of the NodeB. 3-4


Issue 06 (2010-09-10)



Step 12 Record the commissioning process and problems in the 5 Data Sheet for NodeB Commissioning, and then export a commissioning report. ----End

3.2 Preparing the USB Disk for On-Site Commissioning The 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 read or write operation on the USB disk, the LED on the USB disk is on; when there is any read or write 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 wait for 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 usually performed by configuration engineers.

l

The VSWR check script can be customized. The file name is STRVSWR.dat. The file content is as follows: [Config] VSWRTHD = a

Where, a indicates the VSWR threshold and can be set as required. The recommended value 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

CAUTION After you have saved the files from the PC into the USB disk, unplug the USB disk following the system prompt. If not, errors may occur when you access the USB disk. ----End

Issue 06 (2010-09-10)


3-5



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

Prerequisite l

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

Context 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 disk driver. After the installation, the NodeB automatically reads the software and data configuration file in the fixed directories of the USB disk and verifies their names and formats. Pay attention to the following situations when upgrading the software and downloading data configuration 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 software and data configuration file related to the RRU are not downloaded. After the RRU is connected, the software and data configuration file related to the RRU are automatically downloaded 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 automatically downloads the data configuration file.

l

In any of the following situations, the NodeB does not upgrade the software or download the data configuration file from the USB disk. –

The directory or the file does not exist.

–

The file format is 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.

3-6


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 the software. After the activation, the NodeB resets. Wait until the NodeB reset is complete. For details on the status of the LED on the USB disk and the status of the RUN LED on the WMPT in this process, see Table 3-1. Table 3-1 LEDs on the USB disk and the WMPT Status of the LED on the USB Disk

Issue 06 (2010-09-10)

State of the RUN LED on the WMPT

Duration

When the USB disk is On plugged into the corresponding port on the WMPT, the WMPT automatically detects the USB disk.

Blinking (on for 1s and off for 1s)

About 1s to 2s

The WMPT downloads the software and data configuration file from the USB disk.

Blinking

Blinking (on for 0.125s and off for 0.125s)

About 12 minutes

The WMPT activates the software.

On


About 3 to 4 minutes

The NodeB resets.

On first, off for a while, and then blinking

On first, off for a while, and then blinking (on for 0.125s and off for 0.125s)

About 2 minutes

The NodeB runs normally.

On


-


3-7


3 Commissioning the NodeB Through the USB Disk+M2000 NOTE

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

----End

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 connection by 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 LEDs This section describes how to check the status of LEDs. By checking the status of LEDs on the boards of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 is functional. 3.4.2 Rectifying Common Faults This section describes how to rectify common faults when the LED indicates faults on the USB disk or on the boards of the NodeB. 3.4.3 Guidelines for Rectifying Faults This section provides the guidelines for rectifying faults according to the guidelines for rectifying faults.

3.4.1 Checking the Status of LEDs This section describes how to check the status of LEDs. By checking the status of LEDs on the boards of the BBU3900 or the auxiliary devices, you can determine whether the BBU3900 is functional.

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

3-8

LED

Status

LED on the USB disk

On

RUN LED on each BBU board



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

If the LED indicates faults on the USB disk or on the boards of the NodeB, rectify the faults by referring to 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 Faults This section describes how to rectify common faults when the LED indicates faults on the USB disk or on the boards of the NodeB.

Issue 06 (2010-09-10)


3-9



Context Table 3-3 Methods of rectifying common faults If...

You can Infer That...

Then...

The LED on the USB disk is off

The NodeB software fails to be upgraded from the USB disk.

Insert the USB disk again, and upgrade the software.

RUN LED on each BBU board blinks (on for 0.125s and off for 0.125s)

The software is being loaded or the board is wrongly positioned in the slot of another board.

Wait for five minutes and then check the status of the RUN LED again.

The ALM LED on the WMPT, WBBP, or UTRP is on

The board is faulty.

Reinstall the board to check whether the fault is rectified. If the ALM LED still blinks, replace the board.

The ALM LED on the active WMPT blinks

The external port on the active WMPT is faulty.

l

Check whether the RUN LED on the PMU, AFMU, EMU, or EMUA blinks (on for 0.125s and off for 0.125s). If the RUN LED on those boards blinks (on for 0.125s and off for 0.125s), check whether the RS485 signal cable is connected properly.

l

Check whether the dry contact alarm signal cable is properly connected to the corresponding port on the UPEU.

If the software fails to be upgraded again, record the problem in the data sheet for the NodeB commissioning, and then upgrade the software on the LMT.

If the RUN LED still blinks (on for 0.125s and off for 0.125s), check whether the board is positioned in the correct slot. If not, reinstall the board.

If the fault persists, record the fault and the LED status of the WMPT in the data sheet for the NodeB commissioning. Then, rectify the fault on the LMT or M2000. A CPRI LED on the WBBP is steady red

3-10

The CPRI optical cable is improperly connected, or the optical module is out of position.

l

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

l

Check whether the CPRI optical cable is improperly connected, for example, the receive end and the transmit end are reversed. If it is improperly connected, reinstall it. Then, wait for 30 seconds, and check the status of the CPRI LED again.

l

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


Issue 06 (2010-09-10)



If...


Then...

CPRI LED on the WBBP blinks red (on for 0.25s and off for 0.25s)

The RRU or the WRFU is faulty.

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

CPRI LED on the WBBP blinks red (on for 1s and off for 1s)

There is a VSWR alarm, an antenna alarm or an external alarm on the RRU or the WRFU.

l

Check whether a VSWR LED on the RRU or the WRFU is off. If the VSWR LED is not off, see 3.4.3 Guidelines for Rectifying Faults to rectify the fault.

l

Check whether a ALM LED on the RRU or the WRFU blinks. If it blinks, then: –

Check whether the antenna devices are properly connected to the RRU or the WRFU.

–

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

3.4.3 Guidelines for Rectifying Faults This section provides the guidelines for rectifying faults according to the guidelines for rectifying faults.

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

Issue 06 (2010-09-10)

If the RUN LED Is...


Then...


The board works properly.

Go to Step 2.

On

The power supply is available but the board is faulty.

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


The software is being loaded or the board is wrongly positioned in the slot of another board.

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


3-11



If the RUN LED Is...


Then...

Off

The power supply is unavailable or the board is faulty.

l

Check whether the NodeB is powered on.

l


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


Then...

Off


Go to Step 3.

On

The active WMPT is faulty.


Blinking

The external port on the active WMPT is faulty.

If the fault persists, record the fault and the LED status of the WMPT in the data sheet for the NodeB commissioning. Then, rectify the fault on the LMT or M2000. l

Check whether the RUN LEDs on other boards blink (on for 0.125s and off for 0.125s). –

If the RUN LEDs on the PMU, AFMU, EMU, or EMUA blink (on for 0.125s and off for 0.125s), check whether the RS485 signal cable is properly connected.

–

If the RUN LEDs on the standby WMPT, WBBP, or UTRP blink (on for 0.125s and off for 0.125s), reinstall the board to check whether the fault is rectified.

l

Check whether the dry contact alarm signal cable is properly connected to the corresponding port on the UPEU.

l

Reinstall the active WMPT to check whether the fault is rectified.

l

Reinstall the WBBP or the UTRP to check whether 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 next step based on the status of the ALM LED.

3-12


Issue 06 (2010-09-10)



If the ALM LED Is...


Then...

Off


Go to Step 4.

On



Blinking

The ports between the active WMPT and the other BBU boards are faulty.


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


Then...

Steady green

The CPRI optical cable is properly connected, and the RRU or the WRFU works properly.

Go to Step 5.

Off

The CPRI port is not configured.

Check whether the optical module is properly connected to the configured CPRI port. If not, reinstall the optical module to connect it to the correct CPRI port.

Steady red

The CPRI optical cable is improperly connected, or the optical module is out of position.

l

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

l

Check whether the CPRI optical cable is improperly connected, for example, the receive end and the transmit end are reversed. If it is improperly connected, reinstall it. Then, wait for 30 seconds, and check the status of the CPRI LED again.

l

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

Blinking red (on for 0.25s and off for 0.25s)

Issue 06 (2010-09-10)

The RRU or the WRFU is faulty.

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


3-13



If the CPRI LED Is...


Then...

Blinking red (on for 1s and off for 1s)

There is a VSWR alarm, an antenna alarm or an external alarm on the RRU or the WRFU.

l

Check whether a VSWR LED on the RRU or the WRFU is off. If the VSWR LED is not off, see Step 7 to rectify the fault.

l

Check whether a ALM LED on the RRU or the WRFU blinks. If it blinks, then: –

Check whether the antenna devices are properly connected to the RRU or the WRFU.

–

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

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


Then...

Blinking green


Go to Step 6.

Blinking red



Step 6 Check the ALM LED status of the PMU, AFMU, EMU or EMUA, and perform the next step based on the status of the ALM LED. If the ALM LED Is...


Then...

Off

The module or the device works properly.

Go to Step 7.

On

The module or the device is faulty.

Reinstall the module or power on the device again to check whether the fault is rectified. If the fault persists, record the fault and the LED status in the Data Sheet for NodeB Commissioning. Then, rectify the fault on the LMT or M2000.

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


Issue 06 (2010-09-10)



If the VSWR LED Is...


Then...

Off

No VSWR alarm is generated.

Go to Step 8.

On for 0.125s and off for 0.125s

There are alarms on the ANT_TX/RXA port and ANT_RXB port.

Check whether the antenna system is properly connected to the RRU or the WRFU.

On

There is an alarm on the ANT_TX/RXA port.

On for 1s and off for There is an alarm on 1s the ANT_RXB port.

Step 8 Check the transmission status of the NodeB. If...

Then...

The NodeB uses the E1 transmission mode

Perform the E1 loopback test. If the ALM LED on the board with the E1 port blinks, the E1 port at the NodeB side is properly connected.

The NodeB uses the FE transmission mode

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

----End

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 system is correctly installed. You can test the VSWR through the USB disk on the NodeB side.

Prerequisite l

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 USB Disk for On-Site Commissioning.

l

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 disk driver. After the installation, the NodeB automatically reads the software and data configuration file from the designated directories of the USB disk and verifies their names and formats.

Context

Issue 06 (2010-09-10)


3-15



l

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

l

When the VSWR test through the USB disk on the NodeB side and the VSWR test on the M2000 side are performed at the same time: If the VSWR test through the USB disk on the NodeB side is started before the VSWR test on the M2000 side, the M2000 displays that the NodeB is performing the VSWR test. If the VSWR test on the M2000 side is started before the VSWR test through the USB disk on the NodeB side, the NodeB does not perform the 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.

CAUTION l

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.

CAUTION l

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 VSWR test is complete. Observe the status of the CPRI LED on the WBBP. l

3-16

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. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 06 (2010-09-10)

NodeB Commissioning Guide 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 the antenna VSWR of the NodeB on the M2000. For details, see 2.11 Testing the NodeB VSWR on the M2000.

Step 3 Unplug the USB disk first and then plug it back into the USB port. When the USB disk LED is off, 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

Issue 06 (2010-09-10)


3-17


4

4 Commissioning the NodeB on the LMT

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 status of the NodeB on the NodeB LMT. 4.1 Procedure for Commissioning the NodeB on the LMT This section describes how to commission the NodeB on the LMT. You can upgrade the NodeB software, download the data configuration file, and check the running status of the NodeB on the LMT. 4.2 Upgrading the NodeB Software and Downloading the Data Configuration File After the BootROM, software, and data configuration file of the NodeB are downloaded and activated, the NodeB automatically resets and then the software and data configuration take effect. 4.3 Checking the Running Status of the NodeB This chapter describes how to check the running status of the NodeB for the purpose of rectifying faults that occur during the operation and ensuring proper operation of the NodeB. 4.4 Testing the NodeB VSWR on the LMT This section describes how to test the VSWR. The VSWR is used to verify if the antenna system is correctly installed.

Issue 06 (2010-09-10)


4-1



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

Prerequisite Before commissioning the NodeB, the NodeB, RNC, and M2000 should meet the following requirements: 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 powered on 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 Procedures Figure 4-1 shows the procedures for commissioning the NodeB. Figure 4-1 Procedures for commissioning the NodeB on the LMT

4-2


Issue 06 (2010-09-10)



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

Then ...

The active software version and data configuration are inconsistent with those to be used

Go to Step 2.

The active software version and data configuration are consistent with those to be used

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 of the NodeB. Step 4 Check the NodeB VSWR on the LMT. For details, see 4.4 Testing the NodeB VSWR on the LMT. Step 5 Record the commissioning process and problems in the 5 Data Sheet for NodeB Commissioning, and then export a commissioning report. ----End

4.2 Upgrading the NodeB Software and Downloading the Data Configuration File After the BootROM, software, and data configuration file of the NodeB are downloaded and activated, the NodeB automatically resets and then the software and data configuration take effect. 4.2.1 Querying the Active Version of the NodeB This section describes how to query the active version of the NodeB. Before upgrading the NodeB software, you should query the information of the active software version. 4.2.2 Upgrading the NodeB BootROM This describes how to upgrade the NodeB BootROM software. 4.2.3 Upgrading the NodeB Software and Downloading the Data Configuration File This section describes how to upgrade the NodeB software and download the data configuration file.

4.2.1 Querying the Active Version of the NodeB This section describes how to query the active version of the NodeB. Before upgrading the NodeB software, you should query the information of the active software version. Issue 06 (2010-09-10)


4-3



Procedure l

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

----End

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

Prerequisite l

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 Maintenance tab. Step 2 Double-click Software Management > Software Update. The Software Update dialog box is 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 or a specified FTP server. The built-in FTP server is started by default.

Use Specified FTP Server

IP address

The FTP server can be started either from the local computer installed with the LMT application or from another computer. Here it refers to the IP address of the FTP server.

User Name This enables you to specify the user name for logging in to the FTP server. Password

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

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


Issue 06 (2010-09-10)



Step 7 Select Download BootROM Package and then specify a path to download the BootROM package. 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 of the patch upgrade is displayed in the dialog box. You may check the process by viewing this dialog box. ----End

4.2.3 Upgrading the NodeB Software and Downloading the Data Configuration File This section describes how to upgrade the NodeB software and download the data configuration file.

Prerequisite l

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

l

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

l

The FTP user can access the specified directory.

Procedure Step 1 In the navigation tree of the Local Maintenance Terminal window, click the Maintenance Tab. Step 2 Select Software Management > Software Update. The Software Upgrade dialog box is displayed. 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

Issue 06 (2010-09-10)

Field

Description

Use Built-in FTP Server

This enables you to decide whether to use a built-in or a specified FTP server. The built-in FTP server is started by default.


4-5



Field

Description

Use Specified FTP Server

IP address

The FTP server can be started either from the local computer installed with the LMT application or from another computer. Here it refers to the IP address of the FTP server.

User Name This enables you to specify the user name for logging in to the FTP server. Password

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

Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade NodeB Software dialog box is displayed. Step 7 Select Downloading Data Configuration File, Download NodeB Software Package, Download by Configuration, Effective Data Configuration File, and Activate NodeB Software in sequence, and set the directory for downloading the data configuration file and NodeB 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 software packages from the relay server according to the configured board type. In this manner, the total amount of 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 patch upgrade is displayed in the dialog box. You may check the process by viewing this dialog box.

CAUTION l

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 NodeB This chapter describes how to check the running status of the NodeB for the purpose of rectifying faults that occur during the operation and ensuring proper operation of the NodeB. 4.3.1 Commissioning SNTP This section describes how to commission the Simple Network Time Protocol (SNTP) to synchronize the time between NEs. The task facilitates the centralized maintenance and management. 4-6


Issue 06 (2010-09-10)



4.3.2 Checking the Status of a Cell This section describes how to check the status of a local cell or a logical cell. The task helps you to identify the running status of the active cell and perform OM on the cell. 4.3.3 Measuring the RTWP This section describes how to measure the Received Total Wideband Power (RTWP). The RTWP is the received wideband power in a UL channel band measured at the access point of the UMTS Terrestrial Radio Network Access (UTRAN). You can calibrate the gain of UL RF channels through RTWP measurement. The RTWP measurement does not affect ongoing services. 4.3.4 Monitoring the Output Power of the NodeB This section describes how to monitor the output power of the NodeB, including the typical output power and output power of each carrier. 4.3.5 Handling NodeB Alarms This section describes how to check active alarms and clear the alarms if any.

4.3.1 Commissioning SNTP This section describes how to commission the Simple Network Time Protocol (SNTP) to synchronize the time between NEs. The task facilitates the centralized maintenance and management.

Context Application of the SNTP can synchronize the time (year/month/date/hour/minute/second) between multiple SNTP clients in real time by using a unique SNTP server.

Procedure Step 1 Start the SNTP server. An SNTP server can be on the RNC side or on the M2000 server side, which is determined by the 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 is required. Value range: ON (synchronization required), OFF (synchronization not required) Default value: none

IP

SNTP Server IP Address

Value range: 0.0.0.1 to 255.255.255.254 Default value: none

Issue 06 (2010-09-10)


4-7



Parameter ID

Parameter Name

Description

SP

Synchronization Period

Value range: 1 to 525600 Unit: minute Default value: none

Step 3 Run the LST SNTPCLTPARA command to check the parameters of the SNTP client. Step 4 Run the LST SNTPCLTLATESTSUCCDATE command to query the time of latest successful synchronization of the SNTP client to the SNTP server, and whether the synchronization is successful. If...

Then...

The synchronization is successful End this task. The synchronization fails

Check the following items: l

Whether the SNTP server is running

l

Whether the IP address of the NodeB is correct

After the faults are rectified, go to Step 2 to set the parameters again. ----End

4.3.2 Checking the Status of a Cell This section describes how to check the status of a local cell or a logical cell. The task helps you to 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 the NodeB. 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 RTWP This section describes how to measure the Received Total Wideband Power (RTWP). The RTWP is the received wideband power in a UL channel band measured at the access point of the UMTS Terrestrial Radio Network Access (UTRAN). You can calibrate the gain of UL RF 4-8


Issue 06 (2010-09-10)



channels through RTWP measurement. The RTWP measurement does not affect ongoing services.

Prerequisite You 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 reported RTWP is about -108 dBm. If the NodeB is connected to the antenna system with the TMA started 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 the RTWP 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 axis correspond 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 the main antenna form a horizontal line at the point marked -1120 (-112 dBm) on the vertical axis. The RTWP 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 faulty channel. Rectify the faults.

Procedure Step 1 In the navigation tree of the Local Maintenance Terminal window, click the Maintenance tab. Step 2 Select Realtime Specific Monitoring > RTWP Measurement. The RTWP Measurement dialog box is displayed. For the details of the parameters in the RTWP Measurement dialog box, see Interface Reference for 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 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

Result Table 4-3 describes the monitoring items. Issue 06 (2010-09-10)


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

Carrier 1 Rx Receive Freq1


















NOTE

l

One RF module can be configured with one to four carriers. The system outputs the RTWP value of the 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 NodeB This section describes how to monitor the output power of the NodeB, including the typical output power and output power of each carrier.

Prerequisite You have logged in to the NodeB LMT.

Context After the task is started, the system periodically reports the monitored typical power and the output power of each carrier according to the time interval. 4-10


Issue 06 (2010-09-10)



The output power of the NodeB is associated with the configuration and specified services. If the pilot power and typical output power are configured, the output power of the WRFU or RRU is about 3 dB greater than the pilot power when the NodeB carries no services. If the output power of the WRFU or RRU is considerably lower than the pilot power, the output power of the NodeB is abnormal. The pilot power of the WRFU or RRU can be set to 33 dBm. The typical power can be set to 43 dBm.

Procedure Step 1 In the navigation tree of the Local Maintenance Terminal window, click the Maintenance tab. Step 2 Select Realtime Specific Monitoring > Output Power Monitoring. The Output Power Monitoring dialog box is displayed. For the parameter details in the Output Power Monitoring dialog box, see Interface Reference for 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

Result Table 4-4 describes the monitoring items. Table 4-4 Monitoring items for the NodeB output power measurement Item

Description

Carrier Output Power

Indicates the output power of Y carrier in X channel.

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

The carrier output power is the actual output power of the RRU.

Channel Output Power

Indicates the typical output power in X channel corresponding to the RF module.

(Channel No: X; Unit: 0.1dBm)

The channel output power is the ideal output power, which is the theoretical output power.

4.3.5 Handling NodeB Alarms This section describes how to check active alarms and clear the alarms if any. Issue 06 (2010-09-10)


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 NodeB cannot be cleared

Record it in 5 Data Sheet for NodeB Commissioning.

----End

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

Prerequisite l

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. The VSWR less than 1.5 is preferred.

CAUTION l

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

Postrequisite

4-12

1.

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

2.

Ensure that the NodeB services resume. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 06 (2010-09-10)


5 Data Sheet for NodeB Commissioning

5

Data Sheet for NodeB Commissioning

This section provides the data sheet that is used to record the process and results of the NodeB commissioning. Table 5-1 Data Sheet for NodeB Commissioning Site Name NodeB Model Commission Time Commissioning Engineer Commissioning Result

□ Successful; □ Failed

Commissioning Item Commissioning Preparation Phase

Commissioning Phase

Issue 06 (2010-09-10)

Conclusion Faults in NodeB hardware installation are cleared.

□ Yes; □ No

Transmission links between the NodeB and the RNC are ready.

□ Yes; □ No

Negotiation data of the NodeB to be commissioned is added to the RNC.

□ Yes; □ No

The required NodeB software, BootROM software, and data configuration file are ready.

□ Yes; □ No

The NodeB software, BootROM software are successfully upgraded.

□ Yes; □ No

The data configuration file is successfully downloaded.

□ Yes; □ No


Handling Exceptional Cases

5-1


5 Data Sheet for NodeB Commissioning

The NodeB hardware status is checked.

□ Yes; □ No

The running status of the NodeB is checked.

□ Yes; □ No

The NodeB VSWR is checked.

□ Yes; □ No

Problem Description

Impact

Component

P/N

Unsolved Problems After Commissioning

Faulty Board Record

5-2


Issue 06 (2010-09-10)


6 Communication Ports on the NodeB

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

Issue 06 (2010-09-10)

Pro toc ol

A Side

A Sid e Port Nu mb er (RX )

B Side

B Side Port Num ber (TX)

Service

Authority Manageme nt

TC P

NodeB

600 0

LMT

1024 to 65535

For the LMT to deliver the maintenance command to the NodeB

User name/ password

TC P

NodeB

600 1

LMT

1024 to 65535

For the NodeB to report alarm

None

TC P

NodeB

600 6

LMT

1024 to 65535

For maintenance, the format is BIN.

None

TC P

NodeB

600 7

M2000 server

1024 to 65535

For M2000; integration port for MML, alarm, and BIN

User name/ password

TC P

NodeB

20

Site debug console

1024 to 65535

For FTP; debug mode; local maintenance FE port only

None


6-1


6 Communication Ports on the NodeB

6-2

Pro toc ol

A Side

A Sid e Port Nu mb er (RX )

B Side

B Side Port Num ber (TX)

Service

Authority Manageme nt

TC P

NodeB

21

Site debug console

1024 to 65535

For FTP; debug mode; local maintenance FE port only

User name/ password

TC P

NodeB

23

Site debug console

1024 to 65535

For telnet; debug mode; local maintenance FE port only

User name/ password

UD P

NodeB

67/6 8

M2000 server or any other DHCP server

67/68

For DHCP services

None

UD P

M2000 server or any other DHCP server

67/6 8

NodeB

67/68

For DHCP services

None

UD P

M2000 server, RNC BAM, or any other SNTP server

123

NodeB

1024 to 65535

For synchronizing SNTP clock

None

TC P

LMT, M2000 server, RNC BAM, or any other FTP server

20

NodeB

1024 to 65535

For FTP; upload the data configuration file and logs from the NodeB to the FTP server, and download the data configuration file and software packages from the FTP server to the NodeB

None

TC P

LMT, M2000 server, RNC BAM, or any other FTP server

21

NodeB

1024 to 65535

For FTP control

User name/ password


Issue 06 (2010-09-10)

NodeB Commissioning Guide(V200_06)

Recommend Documents