NodeB Commissioning Guide(V200R013_03)(PDF)-En

NodeB V200R013

Commissioning Guide Issue

03

Date

2011-09-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior 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:

[email protected]

Issue 03 (2011-09-30)

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

i

NodeB Commissioning Guide

About This Document

About This Document

Purpose This document describes the commissioning and initial verification of the NodeB after the NodeB is installed, including upgrading the software package, downloading the data configuration file, and checking hardware status and running status. The commissioning ensures that the NodeB operates properly as designed.

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

Product Version

BTS3900 WCDMA (referred to as BTS3900 in this document)

V200R013

BTS3900A WCDMA (referred to as BTS3900A in this document)

V200R013

BTS3900L WCDMA (referred to as BTS3900L in this document)

V200R013

DBS3900 WCDMA (referred to as DBS3900 in this document)

V200R013

iDBS3900 WCDMA (referred to as iDBS3900 in this document)

V200R013

Intended Audience This document is intended for field engineers and deployment engineers.

Issue 03 (2011-09-30)


ii


About This Document

Organization 1 Changes in NodeB Commissioning Guide This describes the changes in the NodeB Commissioning Guide. 2 Commissioning the NodeB on the M2000 This describes how to commission the NodeB on the M2000. You can perform the remote commissioning on multiple NodeBs on the M2000 in the central equipment room. The commissioning procedures, such as software and configuration upgrade, alarm monitoring, and service verification, 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 configuration through the USB disk, 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 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. Provides additional information to emphasize or supplement important points of the main text.

General Conventions Issue 03 (2011-09-30)


iii


About This Document

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. 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 Issue 03 (2011-09-30)


iv


About This Document

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.

Issue 03 (2011-09-30)

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.


v


Contents

Contents About This Document.....................................................................................................................ii 1 Changes in NodeB Commissioning Guide..............................................................................1 2 Commissioning the NodeB on the M2000................................................................................3 2.1 Procedure for Commissioning the NodeB..........................................................................................................5 2.2 Preparations Before NodeB Commissioning......................................................................................................6 2.2.1 Uploading Data Files...............................................................................................................................10 2.2.2 Setting an NE as a Transfer Server..........................................................................................................14 2.3 Creating NodeB Commissioning Tasks...........................................................................................................16 2.4 Starting NodeB Commissioning Tasks.............................................................................................................17 2.5 Monitoring NodeB Commissioning.................................................................................................................19 2.5.1 Viewing Progress and Status of NodeB Commissioning Tasks..............................................................20 2.5.2 Handling NodeB Alarms.........................................................................................................................20 2.5.3 Performing NodeB Fault Diagnosis........................................................................................................21 2.5.4 Viewing NodeB Service Verification Results.........................................................................................22 2.5.5 Managing NodeB Commissioning Tasks................................................................................................23 2.6 Confirming Completion of NodeB Commissioning.........................................................................................25 2.7 Setting the NodeB Maintenance Mode.............................................................................................................25 2.8 Obtaining NodeB Commissioning Reports......................................................................................................26 2.9 References to NodeB Commissioning..............................................................................................................27 2.9.1 Interface Description: NodeB Commissioning Window.........................................................................27 2.9.2 Parameters for the NodeB Deployment List............................................................................................31 2.9.3 Parameters for NodeB Service Verification Performance Counters.......................................................35

3 Commissioning the NodeB Through the USB Disk+M2000..............................................37 3.1 Procedures for Commissioning the NodeB Through the USB Storage Device and the M2000......................39 3.2 Preparing the USB Storage Device for Local Commissioning........................................................................41 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side)...........43 3.4 Checking the Status of the NodeB Hardware and Rectifying Faults (on the NodeB Side)..............................45 3.4.1 Checking the Status of LEDs...................................................................................................................46 3.4.2 Rectifying Common Faults......................................................................................................................47 3.4.3 Guidelines for Rectifying Faults..............................................................................................................48 3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the NodeB Side)........................................53

4 Commissioning the NodeB on the LMT.................................................................................56 Issue 03 (2011-09-30)


vi


Contents

4.1 Procedure for Commissioning the NodeB on the LMT...................................................................................58 4.2 Upgrading the NodeB Software and Downloading the Data Configuration File.............................................60 4.3 Checking the Running Status of the NodeB.....................................................................................................61 4.3.1 Commissioning SNTP.............................................................................................................................61 4.3.2 Checking the Status of a Cell..................................................................................................................62 4.3.3 Measuring the RTWP..............................................................................................................................63 4.3.4 Monitoring the Output Power of the NodeB...........................................................................................65 4.3.5 Handling NodeB Alarms.........................................................................................................................66 4.4 Testing the NodeB VSWR on the LMT...........................................................................................................66 4.5 Setting the Maximum Output Power of RRU or RFU.....................................................................................67 4.6 Data Sheet for NodeB Commissioning............................................................................................................69

5 Communication Ports on the NodeB.......................................................................................71

Issue 03 (2011-09-30)


vii


1

1 Changes in NodeB Commissioning Guide

Changes in NodeB Commissioning Guide This describes the changes in the NodeB Commissioning Guide.

03 (2011-09-30) This is the third commercial release. Compared with issue 02 (2011-06-10), this issue does not add any topics. Compared with issue 02 (2011-06-10), this issue incorporates the following changes: Topic

Change Description

2.2 Preparations Before NodeB Commissioning

Notes about how to fill out the deployment lists are added.

Compared with issue 02 (2011-06-10), this issue does not remove any topics.

02 (2011-06-10) This is the second commercial release. Compared with issue 01 (2011-04-30), this issue includes the following new topics: l

Setting the Maximum Output Power of RRU or RFU (NodeB)

Compared with issue 01 (2011-04-30), this issue incorporates the following changes: Topic

Change Description

2.1 Procedure for Commissioning the NodeB

The flowchart and related steps are updated.

Compared with issue 01 (2011-04-30), this issue does not remove any topics.

Issue 03 (2011-09-30)


1


1 Changes in NodeB Commissioning Guide

01 (2011-04-30) This is the first commercial release. Compared with issue Draft A (2011-03-30), this issue does not add any topics. Compared with issue Draft A (2011-03-30), this issue incorporates the following changes: Topic

Change Description

4.5 Setting the Maximum Output Power of RRU or RFU

The module models applicable to the function are added.

3.2 Preparing the USB Storage Device for Local Commissioning

Descriptions about the encryption of the configuration file in the USB storage device are added.

Compared with issue Draft A (2011-03-30), this issue does not remove any topics.

Draft A (2011-03-30) This is the draft issue of V200R013. Compared with issue 06 (2010-10-30) of V200R012, this issue includes the following new topics: l

4.5 Setting the Maximum Output Power of RRU or RFU

Compared with issue 06 (2010-10-30) of V200R012, this issue incorporates the following changes: Topic

Change Description

2 Commissioning the NodeB on the M2000

The method of commissioning the NodeB on the M2000 (V200R011) is updated.

Compared with issue 06 (2010-10-30) of V200R012, this issue does not delete any topic.

Issue 03 (2011-09-30)


2


2


Commissioning the NodeB on the M2000

About This Chapter This describes how to commission the NodeB on the M2000. You can perform the remote commissioning on multiple NodeBs on the M2000 in the central equipment room. The commissioning procedures, such as software and configuration upgrade, alarm monitoring, and service verification, can be performed on the M2000. 2.1 Procedure for Commissioning the NodeB When the network transmission works normally, you can commission a NodeB using the NodeB plug-and-play function on the M2000 in a central equipment room. 2.2 Preparations Before NodeB Commissioning This section describes how to prepare for NodeB commissioning. 2.3 Creating NodeB Commissioning Tasks This section describes how to create NodeB commissioning tasks on the M2000 client after making required preparations. 2.4 Starting NodeB Commissioning Tasks This section describes how to start NodeB commissioning tasks. After creating NodeB commissioning tasks, you can set commissioning procedures and start the tasks. Then, the M2000 automatically commissions the NodeBs. 2.5 Monitoring NodeB Commissioning This section describes how to monitor NodeB commissioning on the M2000 to learn about commissioning progress and status and handle exceptions in time. 2.6 Confirming Completion of NodeB Commissioning This section describes how to confirm completion of NodeB commissioning tasks. After NodeBs pass service verification, NodeB commissioning tasks switch to the Waiting for Confirmation state. You need to manually confirm the completion. 2.7 Setting the NodeB Maintenance Mode After the NodeB commissioning is complete, the commissioning personnel must set the NodeB maintenance mode to normal on the M2000 so that the NodeB alarms can be reported to the M2000 for prompt maintenance. 2.8 Obtaining NodeB Commissioning Reports This section describes how to obtain NodeB commissioning reports. A NodeB commissioning report records the details about user operations, commissioning results, and error information. Issue 03 (2011-09-30)


3



You can obtain the report of NodeB commissioning tasks when the tasks are in progress and archive the report when the tasks are complete. 2.9 References to NodeB Commissioning This section describes references to NodeB commissioning, including introduction to deployment list, interface description, and parameter description.

Issue 03 (2011-09-30)


4



2.1 Procedure for Commissioning the NodeB When the network transmission works normally, you can commission a NodeB using the NodeB plug-and-play function on the M2000 in a central equipment room.

Prerequisite Prepare for the commissioning by referring to 2.2 Preparations Before NodeB Commissioning.

Commissioning Flowchart Figure 2-1 shows the procedure for commissioning a NodeB. Figure 2-1 NodeB commissioning flowchart (on the M2000)

Issue 03 (2011-09-30)


5



Procedure Step 1 Create a NodeB commissioning task by referring to 2.3 Creating NodeB Commissioning Tasks. Step 2 Start the NodeB commissioning task. Set the steps to be performed for this commissioning task based on the actual situations. For details, see 2.4 Starting NodeB Commissioning Tasks. Step 3 The M2000 automatically commissions the NodeB based on the commissioning steps set when the commission task is started. During the commissioning process, monitor the commissioning progress, rectify faults (if any) to ensure that the commissioning is successful. For details, see 2.5 Monitoring NodeB Commissioning. Step 4 After the NodeB service verification passes, the Waiting for Confirmation status is displayed for the commission task. Check that the NodeB commissioning is complete. For details, see 2.6 Confirming Completion of NodeB Commissioning. Step 5 Set the NodeB maintenance mode. For details, see 2.7 Setting the NodeB Maintenance Mode. Step 6 Obtain the NodeB commissioning report. For details, see 2.8 Obtaining NodeB Commissioning Reports. Step 7 Optional: Set the maximum output power of an RF unit. For details, see Setting the Maximum Output Power of RRU or RFU (NodeB). ----End

2.2 Preparations Before NodeB Commissioning This section describes how to prepare for NodeB commissioning. Prepare for NodeB commissioning by referring to Table 2-1. NOTE

When Network Address Translation (NAT) is not deployed on the M2000 side, the following IP addresses must be on the same network segment: l

IP address for the M2000 connecting to the NodeB for operation and maintenance.

l

IP address for the FTP server.

l

IP address for the M2000 with a plug-and-play (PnP) task started.

When NAT is deployed on the M2000 side, the following IP addresses used after NAT is performed must be on the same network segment: l

IP address for the M2000 connecting to the NodeB for operation and maintenance.

l

IP address for the FTP server.

l

IP address for the M2000 with a PnP task started.

If the preceding conditions cannot be met, visit the site and use a USB flash drive for the commissioning.

Table 2-1 Preparing for NodeB commissioning

Issue 03 (2011-09-30)

Step

Operation

1

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

6



Step

Operation

2

Check that the controller hardware is installed and commissioned successfully and the controller runs normally. The negotiated data of the NodeB to be commissioned is configured at the controller and recorded.

3

Check that he M2000 is commissioned, it is connected to the corresponding controller, and the configuration synchronization is completed.

4

Check that the M2000 server is installed with an adaptation layer whose version matches the version of the NodeB to be commissioned.

5

Check that the software package of the target NodeB version to be commissioned is obtained from the website http://support.huawei.com/ and uploaded to the M2000 server. For details, see 2.2.1 Uploading Data Files.

6

Prepare the data configuration file of the NodeB to be commissioned. This file can be created and exported using CME, and provided by configuration engineers. For details on how to create the data configuration file, see the NodeB Initial Configuration Guide.

7

The deployment list of the NodeB to be commissioned is ready. For details on preparing the deployment list of the NodeB, see Table 2-2. For details on the parameters in the deployment list, see 2.9.2 Parameters for the NodeB Deployment List.

8

Check that the NodeB relay server is set correctly. For details, see 2.2.2 Setting an NE as a Transfer Server. The NodeB relay server is usually set to the controller that controls the NodeB.

9

Issue 03 (2011-09-30)

Check that the network is normal.


7



Table 2-2 Preparing the deployment list of the NodeB to be commissioned Scenario

Note

Deployment lists are exported from the CME

If the CME has been deployed and you have initially configured eNodeBs on the CME, it is recommended that you use the CME to export eNodeB deployment lists. For details, see Exporting eNodeB EDS Data in M2000 Help. Obtain and open the exported deployment list. Check whether the software version, cold patch, and hot patch are consistent with planned ones. If they are inconsistent, change them as planned. In addition, set other relevant data. NOTE The deployment lists must be exported from the CME of V200R011C00. CAUTION 1. Operators need to change the M2000 IP address and mask on the deployment list to those of the current SingleRAN6.0 NodeB to be deployed. Otherwise, the NodeB cannot connect to the M2000. The connection fails because the route and access control list (ACL) cannot be configured. The configuration fails because the NodeB cannot obtain IP addresses for the M2000 and the FTP server by using Dynamic Host Configuration Protocol (DHCP) and there is no default route. The NodeB may not obtain the IP addresses if they are not included in the NodeB configuration file, the source of imported data. When NAT is deployed on the M2000 side, operators need to change the M2000 IP address and mask on the deployment list to those used after the NAT. 2. Before deployment, operators need to check whether IP addresses for the M2000 and the FTP server are on the same network segment. If they are not, check whether the M2000 can be configured as a relay server. If it can, configure the M2000 as the relay server. If either of the preceding conditions is not met, visit the site and use a USB flash drive for the commissioning.

Issue 03 (2011-09-30)


8



Scenario

Note

Deployment lists are exported from the M2000 client

If the CME has not been deployed, you can export NodeB deployment lists from the NodeB Auto Deployment window on the M2000 client. 1. Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. 2. Click . The Select Directory for Exported File dialog box is displayed. 3. Specify a save path, and then click OK. 4. Open the exported deployment lists, and then add relevant data based on the planned data that is confirmed with the network planning engineers. CAUTION 1. Operators need to change the M2000 IP address and mask on the deployment list to those of the current SingleRAN6.0 NodeB to be deployed. Otherwise, the NodeB cannot connect to the M2000. The connection fails because the route and access control list (ACL) cannot be configured. The configuration fails because the NodeB cannot obtain IP addresses for the M2000 and the FTP server by using Dynamic Host Configuration Protocol (DHCP) and there is no default route. The NodeB may not obtain the IP addresses if they are not included in the NodeB configuration file, the source of imported data. When NAT is deployed on the M2000 side, operators need to change the M2000 IP address and mask on the deployment list to those used after the NAT. 2. Before deployment, operators need to check whether IP addresses for the M2000 and the FTP server are on the same network segment. If they are not, check whether the M2000 can be configured as a relay server. If it can, configure the M2000 as the relay server. If either of the preceding conditions is not met, visit the site and use a USB flash drive for the commissioning.

The planned target version of a base station to be commissioned may be inconsistent with that in the CME deployment list. For example, the current NE version is ***SPC210, and the CME has released the ***SPC210 NE component package. After the NE version is upgraded to ***SPC220, the CME does not release the ***SPC220 component package because the NE model remains unchanged. In such a case, users need to use the ***SPC210 package to create base stations. The baseline version number in the exported deployment list is ***SPC210. Users need to manually change the version number based on the following cases: If...

Then...

The target version of a new base station is ***SPC220

l If the baseline version is not ***SPC220 and the baseline version of ***SPC220 is ***SPC200, change the baseline version to ***SPC200 and change the cold patch to ***SPC220. l If ***SPC220 is the baseline version, change the baseline version to ***SPC220 and do not change the cold patch.

The target version of a new base station is ***SPC210

l If ***SPC210 is not the baseline version and the baseline version of ***SPC210 is ***SPC200, change the baseline version to ***SPC200 and change the cold patch to ***SPC210. l If ***SPC210 is the baseline version, do not modify the deployment list.

Issue 03 (2011-09-30)


9



2.2.1 Uploading Data Files Upload data files that are required for procedures of NodeB commissioning. Data files required for procedures of NodeB commissioning tasks are software versions, cold patches, hot patches, configuration data files, and deployment lists.

Prerequisite You have logged in to the M2000 client.

Context You need to upload data files in the following scenarios: l

Prepare for the commissioning. Upload the required data files to the M2000 server before commissioning as required.

l

The commissioning cannot be started because certain required data files are unavailable. The M2000 automatically checks whether data files required for customized procedures are available. If certain data files are unavailable, the commissioning cannot be started. Upload the required data files that are previously unavailable from the client to the M2000 server.

The data files required for NodeB commissioning need to be saved in specified paths on the M2000 server. For details, see Table 2-3. Table 2-3 File save paths File Type

Save Path

Software version

/export/home/sysm/ftproot/NodeB Type/Software/

Cold or hot patch

/export/home/sysm/ftproot/NodeB Type/Patch/

Configurati on data file

/export/home/sysm/ftproot/adn/AutoDeploymentData/NodeB/CfgData/

Deploymen t list

/export/home/sysm/ftproot/adn/AutoDeploymentData/NodeB/ADList/

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 Click Prepare File&Data. The window for preparing files and data is displayed. Upload data files as required.

Issue 03 (2011-09-30)


10



If you need to...

Then...

Upload NE software versions

l Upload one by one One or more software versions corresponding to a certain NE type are uploaded at a time. 1. On the Software & Cold Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. 2. Select an NE type from the NE Type drop-down list and select a file type from the File Type drop-down list. . The dialog box for selecting 3. In the Source Path area, click files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the software versions are uploaded. l Upload in batches One or more software versions corresponding to one or more NE types are uploaded at a time. 1. On the Software & Cold Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. in the left corner of the dialog box, select an NE type from the 2. Click NE Type drop-down list, and then select a file type from the File Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or more files corresponding to more NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or more files, and then click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the software versions are uploaded.

Issue 03 (2011-09-30)


11



If you need to...

Then...

Upload cold patches

l Upload one by one One or more cold patches corresponding to a certain NE type are uploaded at a time. 1. On the Software & Cold Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. 2. Select an NE type from the NE Type drop-down list and select a file type from the File Type drop-down list. . The dialog box for selecting 3. In the Source Path area, click files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the cold patches are uploaded. l Upload in batches One or more cold patches corresponding to one or more NE types are uploaded at a time. 1. On the Software & Cold Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. in the left corner of the dialog box, select an NE type from the 2. Click NE Type drop-down list, and then select a file type from the File Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or more files corresponding to more NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or more files, and then click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the cold patches are uploaded.

Issue 03 (2011-09-30)


12



If you need to...

Then...

Upload hot patches

l Upload one by one One or more hot patches corresponding to a certain NE type are uploaded at a time. 1. On the Hot Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. 2. Select an NE type from the NE Type drop-down list and select a file type from the File Type drop-down list. . The dialog box for selecting 3. In the Source Path area, click files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the hot patches are uploaded. l Upload in batches One or more hot patches corresponding to one or more NE types are uploaded at a time. 1. On the Hot Patch tab page, click Transfer > From OMC Client to OMC Server. The NE File Transfer dialog box is displayed. in the left corner of the dialog box, select an NE type from the 2. Click NE Type drop-down list, and then select a file type from the File Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload, and then click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or more files corresponding to more NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or more files, and then click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the hot patches are uploaded.

Issue 03 (2011-09-30)


13


If you need to...


Then...

1. On the NE Cinfiguration Data tab page, click Transfer > From OMC Upload Client to OMC Server. The Upload NE Cinfiguration Data dialog box is configurat displayed. ion data files 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select the folder where the configuration data file that you want to upload is saved, click Select. The Upload NE Cinfiguration Data dialog box is displayed. CAUTION The path for saving a NodeB configuration data file to be uploaded must be ..\RNC Name\NodeB name\NodeBCfg.xml on the local PC. An RNC Name folder contains one or more NodeB name folders. A NodeB name folder only contains an XML file. To upload NodeB configuration data files, you must select the RNC Name folder where the files are saved. You can select multiple RNC Name folders at a time. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path.

Upload deployme nt lists

1. On the Deployment List tab page, click Transfer > From OMC Client to OMC Server. The Upload Deployment List dialog box is displayed. 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload, and then click Open to return to the Upload Deployment List dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the Upload Deployment List dialog box. The system starts uploading the software versions. The detailed information about the operations are displayed on the right of the window for preparing files and data, such as Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the deployment lists are uploaded. NOTE If the CME is not deployed, you can click Export Template to export an empty deployment template, fill in the template based on the planned data, and upload the template. The default names of the exported empty deployment list templates are the same. Therefore, you are advised to change the template names after filling in these templates.

----End

2.2.2 Setting an NE as a Transfer Server The file transfer between the M2000 server and NEs is based on the FTP protocol. Therefore, you need to set the FTP server. A firewall always exists between the NEs and the M2000 and thus many NEs cannot establish an FTP connection with the M2000 server. In this case, you

Issue 03 (2011-09-30)


14



need to set a relay server. You can use the M2000 server, the NE, or a third-party FTP server as the relay server.

Context l

The default relay server is the NE itself.

l

The default relay server of the NodeB is the RNC. In IP networking, if OM channels of the NodeB does not pass the RNC, change the relay server to the M2000 or a third-party server.

l

The system sets the NEs that can serve as an FTP server for file transfer M2000 server and an NE.

l

For details on how to set a third-party server, refer to Configuring the Third Party FTP Server.In the File Server Setting window, click the Third Party FTP Server window.

to navigate to

l

If an NE chooses another NE, the M2000 server, or a third-party FTP server as its relay server, the file transfer process can be stopped. If the NE chooses itself as the relay server, the file transfer process cannot be stopped.

l

The typical setting is to use the RNC as the relay server for transferring NodeB data. NOTE

l By default, the relay server of the eNodeB is the M2000. Therefore, you need not set the relay server of the eNodeB. l The eNodeB cannot be set to the relay server.

Procedure Step 1 Choose Software > File Server Settings. The File Server Setting dialog box is displayed. Step 2 Select the type of the target NE from the navigation tree of the dialog box. All the NEs of this type on M2000 are listed in the right pane. NOTE

Click Refresh to refresh the NE information in the list at the right of the File Server Setting dialog box.

Step 3 Select the destination NE from the NE Name list. TIP

You can use Shift or Ctrl to select multiple NEs. Then right-click them and choose Set to set NEs in batches.

Step 4 Click the File Server Name column. The File Server IP box displays the IP address of the relay server that you have set. NOTE

l If you click Refresh, the Confirm dialog box is displayed. Click No to cancel the previous setting for the relay server. l After being authorized to change the FTP password, you can change it if partial NEs serve as the relay server. To change the FTP password, click

under File Server Name.

Step 5 To activate the setting, click Apply. ----End Issue 03 (2011-09-30)


15



2.3 Creating NodeB Commissioning Tasks This section describes how to create NodeB commissioning tasks on the M2000 client after making required preparations.

Prerequisite l

You have logged in to the M2000 client.

l

NodeB commissioning preparations are complete.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 Select deployment lists. . The Import Deployment List dialog box is displayed.

1.

Click

2.

In the Specify Deployment List area, select deployment lists. If you need to...

Then...

Import deployment lists from the M2000 server

Select From Server, and then select deployment lists from the dropdown list.

Import deployment lists from the M2000 client

Select From Client, and then click

to select deployment lists.

Step 3 Click OK. The system starts the import. After the import is complete, the M2000 checks whether any mandatory parameters in the list are empty and whether any parameter values are invalid. In addition, the information indicating whether the import succeeded or failed is displayed on the Operation Information tab page. l If the import is successful, the M2000 automatically creates a commissioning task for each NodeB. The imported NodeB deployment lists are displayed on the Deployment List tab page. l If the import fails, the causes of the failure are displayed on the Operation Information tab page. Step 4 (Optional) Modify data of the imported deployment lists as required. This step is mandatory when you need to modify data of the imported deployment lists. NOTE

You can check whether the parameters in NodeB deployment lists can be modified by referring to 2.9.2 Parameters for the NodeB Deployment List.

1.

Issue 03 (2011-09-30)

Select a commissioning task from the commissioning task list, and double-click the cells containing parameter values to change the values. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

16



You can change ESNs by double-clicking the cells containing ESNs. Alternatively, you can perform the following operations to change the ESNs:

2.

a.

Click

in the ESN value cell. The Bind ESN dialog box is displayed.

b.

Select an ESN that is not bound, and click OK to return to the commissioning task list.

The changed ESNs highlighted in red are displayed in the commissioning task window after the modification.

----End

2.4 Starting NodeB Commissioning Tasks This section describes how to start NodeB commissioning tasks. After creating NodeB commissioning tasks, you can set commissioning procedures and start the tasks. Then, the M2000 automatically commissions the NodeBs.

Prerequisite l


l

NodeB commissioning tasks have been created.

Context A maximum of 500 NodeB commissioning tasks can be started at a time. In which, a maximum of 200 commissioning tasks can be being executed and the rest are waiting to be executed in the queue.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 On the Deployment List tab page, right-click one or more commissioning tasks, and then choose Start from the shortcut menu. The Task Settings dialog box is displayed. Step 3 Select steps in the Select column based on the actual plan to customize steps for commissioning procedures. NOTE

l

: Indicates that the step is mandatory. It cannot be modified.

l

: Indicates the step that is performed by default. You can choose whether to perform it.

l

: Indicates the step that is not performed by default. You can choose whether to perform it.

For details about commissioning procedures and steps, see Table 2-4.

Issue 03 (2011-09-30)


17



Table 2-4 Description of commissioning process No.

Phase

Step

Description

1

Auto Discove ry

Checking OM Channel

When the connection of transmission network is proper, the M2000 automatically creates OM channels to connect to the NodeBs based on the deployment lists, and commissions and maintains NodeBs through this channel.

2

Auto Configu ration

Download Software

The M2000 automatically checks whether the current NodeB versions are the same as the target software versions based on the target version information provided in the deployment lists. If the versions are not the same, the M2000 automatically downloads software from the server to the NodeBs.

Download Configurati on

The M2000 downloads corresponding configuration files from the server to the NodeBs based on the target version information.

Active

Upgrade NodeB software and activate NodeB configuration data.

Testing VSWR

Test voltage standing wave ratio (VSWR) of the NodeBs to verify that the antenna systems of the NodeBs function properly.

3

Testing and Monitor ing

CAUTION Testing VSWR leads to interruption of NodeB services. Therefore, you need to perform this operation during non-busy hours or after NodeB services are segregated.

Monitoring Cell Service Status

Check whether logical cells of these NodeBs are available on the RNC side. You can monitor alarms of the NodeB using the M2000 during the monitoring to locate and handle exceptions in time.

4

Verifyin g Service

Monitoring Performanc e Counter

When logical cells of these NodeBs are available on the RNC side, the M2000 automatically subscribes to the performance counters of the logical cells of these NodeBs and checks whether the NodeB services are running properly based on the counter values.

5

Waiting for Confirm ation

Waiting for Confirmati on

After service verification is complete, the commissioning tasks are in the Waiting for Confirmation state. You need to manually confirm the completion.

Step 4 (Optional) Set the AACP function based on the actual plan.

Issue 03 (2011-09-30)


18


2 Commissioning the NodeB on the M2000 NOTE

The M2000 can remotely allocate a temporary IP address through the AACP function to a NodeB in a network segment of a RAN whose gateway does not support DHCP relays. The NodeB obtains its own IP address by unidirectional broadcasting the DHCP process and configures itself as the DHCP relay for the network segment to provide the DHCP relay function for other NodeBs in the same network segment. The M2000 automatically allocates IP addresses to other NodeBs according to the standard DHCP IP address allocation procedure.

If you need to...

Then...

Enable the AACP function

Select Use AACP during Auto Discovery, which is the default setting.

Disable the AACP function

Clear Use AACP during Auto Discovery.

Step 5 Click OK. The M2000 automatically checks whether the data files required for procedures are available. If...

Then...

1. The Data Preparation Check dialog box is displayed, showing check Not all the results about the required data files. required data files are available l : Indicates that all the required data files are available. l

: Indicates that not all the required data files are available.

2. Click OK. The Data Preparation Check dialog box is closed. 3. Obtain relevant data files based on the check results. For details, see 2.2.1 Uploading Data Files. 4. After the required data files are uploaded, start the commissioning tasks again. All the required data files are available

The M2000 starts commissioning. The selected commissioning tasks switch to the Running state. NOTE If all the required data files are available, the Data Preparation Check dialog box is not displayed.

----End

2.5 Monitoring NodeB Commissioning This section describes how to monitor NodeB commissioning on the M2000 to learn about commissioning progress and status and handle exceptions in time.

Issue 03 (2011-09-30)


19



2.5.1 Viewing Progress and Status of NodeB Commissioning Tasks This section describes how to view progress and status of NodeB commissioning tasks on the M2000 to learn about process of the tasks.

Prerequisite l


l

NodeB commissioning tasks have been created.

Context User admin can view commissioning tasks created by any user, whereas other users can view only the commissioning tasks created by themselves.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 View the status and progress of commissioning tasks in the commissioning task list. TIP

You can quickly view the status of commissioning tasks by using either of the following methods: l In the commissioning task list, the status of the tasks is displayed in Status, the current procedures are displayed in Current Phase, and details about each procedure are displayed in the Description. l In the commissioning task list, select one or more commissioning tasks whose status you want to view, and then click for commissioning procedures.

. The right pane displays execution status of steps

The execution status is displayed in Status, and details are displayed in Description.

. The Statistic dialog box is displayed, counting the number of Step 3 (Optional) Click commissioning tasks in each status. Click OK to close the dialog box. ----End

2.5.2 Handling NodeB Alarms This section describes how to handle NodeB alarms at the monitoring stage. You can use the M2000 to monitor alarms on NodeBs and related alarms on the controllers that manage these NodeBs in real time. All the alarms are categorized by object to help you query required alarms.

Prerequisite l


l

Commissioning tasks are at the monitoring stage, and the completion of the commissioning tasks has not yet been confirmed.

Context Alarms are categorized into the following types by object: physical transmission port alarms, transmission link alarms, antenna alarms, board alarms, cell alarms, software and configuration alarms, external alarms, and other alarms. Other alarms refer to the alarms that cannot be categorized on the basis of specific objects. Issue 03 (2011-09-30)


20


2 Commissioning the NodeB on the M2000 NOTE

The factory maintenance mode of a NodeB is set to NORMAL. Alarms reported by the NodeB in the NORMAL mode will be identified as maintenance mode alarms. After a NodeB is connected to the M2000 for the first time, the maintenance mode of the NodeB is automatically set to the default value of the maintenance mode on the M2000, NORMAL. If you want to monitor alarms in common mode, set the maintenance mode of the NodeB to TESTING.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, right-click a commissioning task for which you want to handle alarms and choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. Step 3 Handle alarms. 1.

Double-click an alarm to be handled in the alarm list in the right pane. The Details dialog box is displayed.

2.

Click the link in Reason and Advice.

3.

Handle exceptions based on the alarm reference.

----End

2.5.3 Performing NodeB Fault Diagnosis This section describes how to perform NodeB fault diagnosis when exceptions occur at the monitoring stage. If the fault causes of physical transmission port alarms, board alarms, and antenna alarms cannot be located on the basis of the alarm information, you can perform fault diagnosis and take troubleshooting measures to handle the alarms.

Prerequisite l


l

Commissioning tasks are at the monitoring stage, and the completion of the commissioning tasks has not yet been confirmed.

l

Fault causes of some physical transmission port alarms, board alarms, or antenna alarms cannot be located.

Context

CAUTION Fault diagnosis on boards and antennas leads to interruption of NodeB services. Therefore, you need to perform the diagnosis during non-busy hours or after NodeB services are segregated. You can perform the following fault diagnosis operations for NodeBs: l

Issue 03 (2011-09-30)

Physical transmission ports: E1/T1 port loopback fault diagnosis on the RNC side and E1/ T1 port loopback fault diagnosis on the RNC peer side Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

21



l

Boards: board hardware fault diagnosis

l

Antennas: antenna fault diagnosis and high-precision VSWR test

After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task and displays the diagnosis progress. After the fault diagnosis is complete, you can obtain the fault diagnosis report. If you delete a fault diagnosis task, the corresponding diagnosis report is deleted accordingly. If you restart the M2000 server, all fault diagnosis tasks and reports are deleted.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, right-click a commissioning task for which you want to perform fault diagnosis, and choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. Step 3 Perform fault diagnosis on physical transmission port, boards, or antennas. 1.

Select an object from the left pane of the displayed window, or select a specific alarm of the object from the alarm list in the right pane, right-click the object or alarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settings dialog box is displayed.

2.

Select a NodeB in the Select NE area, select a diagnosis type in the Select diagnose type area, type diagnosis parameters in the Enter diagnosis parameters area, and click OK. The dialog box for confirming the diagnosis is displayed.

3.

Click Yes. The system starts the fault diagnosis. During the fault diagnosis, a diagnosis task is added to the diagnosis task list.

4.

Right-click a diagnosis task in the diagnosis task list, and choose Diagnose Report from the shortcut menu to view diagnosis results.

----End

2.5.4 Viewing NodeB Service Verification Results This section describes how to view NodeB service verification results at the service verification stage. The M2000 automatically subscribes to the performance counters of logical cells of the NodeBs on the RNC side and checks whether the NodeB services are running properly based on counter values. At this stage, you can check whether each cell of the NodeB has passed service verification and view the accumulated value of each counter.

Prerequisite l


l

Commissioning tasks are at the service verification stage, and the completion of the commissioning tasks has not yet been confirmed.

Issue 03 (2011-09-30)


22



Context l

During the service verification, the performance measurement period is the shortest measurement period supported by the RNC. By default, the shortest measurement period is 5 minutes.

l

If the value of a single performance counter is not zero during the service verification, this counter has passed service verification.

l

If all performance counters of a cell have passed the verification, this cell has passed service verification.

l

If all logical cells of a NodeB on the RNC side have passed the verification, this NodeB has passed service verification.

l

After a NodeB passes the service verification, the NodeB commissioning task switches to the Waiting for Confirmation state. You need to manually confirm the completion. NOTE

Performance data collected for service verification is saved on the M2000 for 14 days. After 14 days, the M2000 automatically deletes the data to release system resources.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, select a commissioning task for which you want to view service verification results, right-click the tasks, and choose Open Service Verification Window from the shortcut menu. The service verification window is displayed. Step 3 View service verification results and perform corresponding operations. The accumulated values of the counters, which are collected in the time range between the start of service verification and the restart of commissioning or the confirmation of commissioning completion, are displayed in the service verification window. l If cells corresponding to all counters once display , service verification is successful. You can confirm the completion of the commissioning. l If the cell corresponding to a certain counter always displays , services related to this counter are running abnormally. You need to rectify the faults. ----End

2.5.5 Managing NodeB Commissioning Tasks This section describes how to manage NodeB commissioning tasks. After creating or starting NodeB commissioning tasks, you can delete, restart, pause, resume, or cancel the selected tasks.

Prerequisite l


l

NodeB commissioning tasks have been created or started.

Context For details about operations on commissioning tasks, see Table 2-5. Issue 03 (2011-09-30)


23



Table 2-5 Operations on commissioning tasks Opera tion

Description

Delete

You can perform this operation on commissioning tasks in any state.

Restart

You can perform this operation on commissioning tasks in the Running, Abnormal, Paused, or Waiting for Confirmation state.

Pause

You can perform this operation on commissioning tasks in the Running state.

Resum e

You can perform this operation on commissioning tasks in the Paused state.

Cancel

You can perform this operation on commissioning tasks in the Running, Abnormal, or Paused state.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 On the Deployment List tab page, select one or more commissioning tasks and perform operations as required. If you need to...

Then...

Restart tasks

Right-click the tasks, and then choose Restart from the shortcut menu. The tasks return to the Running state.

Pause tasks Right-click the tasks, and then choose Pause from the shortcut menu. The tasks are in the Paused state. Resume tasks

Right-click the tasks, and then choose Resume from the shortcut menu. The tasks resume to where they are paused and proceeds.

Cancel tasks

Right-click the tasks, and then choose Cancel from the shortcut menu. The tasks return to the Waiting for start state.

Delete tasks

1. Right-click the tasks, and then choose Delete from the shortcut menu. The Confirm dialog box is displayed. 2. Click OK. The system starts deleting the tasks.

----End

Issue 03 (2011-09-30)


24



2.6 Confirming Completion of NodeB Commissioning This section describes how to confirm completion of NodeB commissioning tasks. After NodeBs pass service verification, NodeB commissioning tasks switch to the Waiting for Confirmation state. You need to manually confirm the completion.

Prerequisite l


l

NodeB commissioning tasks are in the Waiting for Confirmation state.

l

All the alarms have been handled, and all the faults been rectified.

l

If some alarms are still not cleared during the commissioning, it is recommended that you do not confirm the commissioning tasks. After you confirm the commissioning tasks, alarm detected during the commissioning cannot be viewed on the basis of a single NodeB.

l

If some alarms are still not cleared during the commissioning, and you have confirmed the completion, the uncleared alarms will be reported to the M2000 again as normal mode alarms.

Context

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, select one or more commissioning tasks for which you want to confirm completion. Right-click the tasks, and then choose Confirm Completion from the shortcut menu to confirm the completion. After the commissioning is complete, the M2000 stops the following services: l Monitoring alarms on the NodeBs and relevant alarms on the RNCs that manage these NodeBs l Subscribing to the service verification performance counters of the NodeBs ----End

2.7 Setting the NodeB Maintenance Mode After the NodeB commissioning is complete, the commissioning personnel must set the NodeB maintenance mode to normal on the M2000 so that the NodeB alarms can be reported to the M2000 for prompt maintenance.

Prerequisite l


l

The NodeB commissioning is complete.

Issue 03 (2011-09-30)


25



Procedure Step 1 On the M2000 client, choose Maintenance > Maintenance Mode, and then click tool bar.

on the

Step 2 Set NE Mode to NORMAL and select Instant. The NodeB maintenance mode is modified. ----End

2.8 Obtaining NodeB Commissioning Reports This section describes how to obtain NodeB commissioning reports. A NodeB commissioning report records the details about user operations, commissioning results, and error information. You can obtain the report of NodeB commissioning tasks when the tasks are in progress and archive the report when the tasks are complete.

Prerequisite l


l

Commissioning tasks are running.

Context The exported commissioning report records the information about only the selected commissioning tasks. After you manually delete a commissioning task, the generated commissioning report does not contain the information about this task. The commissioning report can be stored for a maximum of 30 days. The start date is specified as the date when the commissioning report is generated for the first time.

Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, select one or more commissioning tasks for which you want to export the report, right-click the tasks, and then choose Export Deployment Report from the shortcut menu. A dialog box is displayed, asking you whether to export alarm data at the same time. If...

Then...

You need to export alarm data

Click Yes. The Save dialog box is displayed.

You do not Click No. The Save dialog box is displayed. need to export alarm data Step 3 Specify a save path, and then click Save. Issue 03 (2011-09-30)


26



You can customize a filename for the commissioning report. If you do not specify a filename, the M2000 names and saves the file based on the naming convention NodeB_Auto_Deployment_Report_user name_YYYYMMDDHHMMSS.zip. For example, NodeB_Auto_Deployment_Report_admin_20100812202524.zip. Step 4 Optional: (Optional) Decompress the generated report file. In the decompressed folder, doubleclick index.html to view the commissioning report. If you choose to export alarm data at the same time in Step 2, the file containing the alarm data is saved in the alarm sub-folder. ----End

2.9 References to NodeB Commissioning This section describes references to NodeB commissioning, including introduction to deployment list, interface description, and parameter description.

2.9.1 Interface Description: NodeB Commissioning Window This section describes the elements of the NodeB Auto Deployment window and the function of each element.

Main Window Figure 2-2 shows the main window for NodeB commissioning. Table 2-6 describes the window. Figure 2-2 Main window for NodeB commissioning

Issue 03 (2011-09-30)


27



Table 2-6 Description of main window for NodeB commissioning Area No.

Element Name

Description

1

Toolbar

Provides shortcut icons for NodeB commissioning operations. Hover your mouse pointer over an icon on the toolbar. A message will be displayed, showing the meaning of this icon.

2

Commissioni ng task list

Displays all the commissioning tasks and their progress. You can right-click a task, and then choose the corresponding menu item from the shortcut menu to perform an operation. NOTE User admin can view commissioning tasks created by any user, whereas other users can view only the commissioning tasks created by themselves.

3

Operation results

Records the results of operations.

4

Shortcut menu

You can right-click a task, and then choose the corresponding menu item from the shortcut menu to perform an operation.

Alarm Monitoring Window Figure 2-3 shows the alarm monitoring window for NodeB commissioning. Table 2-7 describes the window. Figure 2-3 Alarm monitoring window for NodeB commissioning

Issue 03 (2011-09-30)


28



Table 2-7 Description of alarm monitoring window for NodeB commissioning Area No.

Element Name

Description

1

Alarm object tree

After selecting an object type, you can view all alarms of this object type in the alarm list in the right pane.

2

Alarm list

After an object type is selected, all alarms of this object type are displayed in the alarm list.

3

Diagnosis task list

Displays the details about diagnosis tasks. You can right-click an object in the alarm object tree or an alarm in the alarm list, and then choose Diagnose from the shortcut menu to create a diagnosis task.

Service Verification Window Figure 2-4 shows the NodeB service verification window of NodeBs. Table 2-8 describes the window. Figure 2-4 NodeB service verification window

Issue 03 (2011-09-30)


29



Table 2-8 Description of NodeB service verification window Area No.

Element Name

Description

1

Verification result list

Displays service verification results of objects.

Window for Uploading Data Files Figure 2-5 shows the window for uploading data files. Table 2-9 describes the window. Figure 2-5 Window for uploading NodeB data files

Table 2-9 Description of Window for uploading NodeB data files

Issue 03 (2011-09-30)

Area No.

Element Name

Description

1

File list

Displays the files on the M2000 server.

2

Button

Provides buttons for operations on uploading data files.

3

Tab named after a data file type

Displays tabs named after data file types that are required for commissioning.

4

Operation results

Displays the operation results about uploading data files.


30



2.9.2 Parameters for the NodeB Deployment List This section describes the parameters that are contained in the NodeB deployment list. Table 2-10 describes the parameters for the NodeB deployment list. NOTE

l If the deployment list is exported from the CME: l Mandatory or not: Indicates whether a parameter is mandatory or not. After the deployment list is imported, the M2000 checks whether any mandatory parameter values are in the list are empty or invalid. l Exported by Default or not: Indicates whether the parameter value is exported by default when you use the CME to export the deployment list. l Configurable or not: Indicates whether the parameter values in the deployment list that is exported from the CME can be configured in the auto-deployment window after being imported to the M2000. l If the deployment list is exported from the M2000, you only need to configure the deployment list by referring to the Mandatory or not column in Table 2-10.

Table 2-10 Parameters for the NodeB deployment list Parameter Field

Description

Mandatory or not

Exported by Default or not

Configurable or not

RNC ID

ID of the RNC to which the NodeB belongs

Yes

Yes

No

RNC Name

Name of the RNC to which the NodeB belongs

No

Yes

No

NodeB ID

ID of the NodeB

Yes

Yes

No

NodeB Name

Name of the NodeB

Yes

Yes

No

NodeB ESN1

Electronic serial number (ESN) on the BBU mounting ear

No

l Yes if this parameter is configured on the CME

Yes

l No if this parameter is not configured on the CME

Issue 03 (2011-09-30)


31



Parameter Field

Description

Mandatory or not


Configurable or not

NodeB ESN2

Reserved parameter. You do not need to configure it.

No


Yes

l No if this parameter is not configured on the CME NodeB OM IP address

IP address of the NodeB OM channel

Yes

Yes

No

NodeB OM IP Subnet mask

IP subnet mask of the NodeB OM channel

Yes

Yes

No

NodeB Interface IP address

IP address of the NodeB interface board (If the port type of the NodeB is ETH or TRUNK, this parameter is mandatory)

No


No

IP subnet mask of the NodeB interface board (If the port type of the NodeB is ETH or TRUNK, this parameter is mandatory)

No

Next hop IP address from the NodeB to the DHCP server

No

NodeB Interface IP Subnet mask

NodeB Next Hop IP address to DHCP Server

l No if this parameter is not configured on the CME l Yes if this parameter is configured on the CME

No

l No if this parameter is not configured on the CME l Yes if this parameter is configured on the CME

No


Issue 03 (2011-09-30)


32



Parameter Field

Description

Mandatory or not


Configurable or not

NodeB Next Hop IP address to AACP Server

Next hop IP address from the NodeB to the AACP server

No


No

l No if this parameter is not configured on the CME M2000 IP address

IP address of the M2000

No


No

l No if this parameter is not configured on the CME M2000 IP Subnet mask

IP subnet mask of the M2000

No


No

l No if this parameter is not configured on the CME NodeB OM VLAN ID

VLAN ID of the NodeB

No


No

l No if this parameter is not configured on the CME NodeB OM VLAN Priority

VLAN priority of the NodeB

No


No


Issue 03 (2011-09-30)


33



Parameter Field

Description

Mandatory or not


Configurable or not

NodeB OM Next Hop IP address

Next hop IP address of the NodeB OM channel

No


No

l No if this parameter is not configured on the CME NodeB Type

Type of the NodeB to be commissioned

Yes

Yes

No

NodeB Software Version

Target software version of the NodeB

No


Yes

l No if this parameter is not configured on the CME NodeB Cold Patch Version

Target cold patch version of the NodeB

No


Yes

l No if this parameter is not configured on the CME NodeB Hot Patch Version

Target hot patch version of the NodeB

No


Yes


Issue 03 (2011-09-30)


34



Parameter Field

Description

Mandatory or not


Configurable or not

NodeB Configuration File CRC

CRC value of the NodeB data configuration file

No


No

l No if this parameter is not configured on the CME Contact

Contact of the onsite engineers

No

Not exported

Yes

2.9.3 Parameters for NodeB Service Verification Performance Counters This section describes the parameters of the performance counters that are monitored at the service verification stage during NodeB commissioning. Table 2-11 describes the service performance counters of monitored NodeBs at the service verification stage during NodeB commissioning. Table 2-11 Parameters of performance counters

Issue 03 (2011-09-30)

Parameter

Description

Uu Connection Verification

Total number of successful radio resource control (RRC) setups. If the value of this counter is not zero, the air interface is available.

AMR Verification

Number of successful radio access bearer (RAB) setups for conversation AMR services. If the value of this counter is not zero, AMR services are available.

VP Verification

Number of successful RAB setups for CS conversation VP services. If the value of this counter is not zero, VP services are available.

PS Conversation Verification

Number of successful PS conversational service setups. If the value of this counter is not zero, PS conversational services are available.

PS Streaming Verification

Number of successful PS streaming service setups. If the value of this counter is not zero, PS streaming services are available.

PS Interactive Verification

Number of successful PS interaction service setups. If the value of this counter is not zero, PS interaction services are available.

PS Background Verification

Number of successful PS background service setups. If the value of this counter is not zero, PS background services are available.


35


Issue 03 (2011-09-30)


Parameter

Description

HSDPA Verification

Number of successful HSDPA RAB setups. If the value of this counter is not zero, HSDPA services are available.

HSUPA Verification

Number of successful HSUPA RAB setups. If the value of this counter is not zero, HSUPA services are available.


36


3

3 Commissioning the NodeB Through the USB Disk+M2000

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 configuration through the USB disk, and then check the running status of the NodeB on the M2000.

Context

CAUTION The Maintenance Mode of a NodeB is TESTING by default. After the NodeB commissioning is complete, manually set the Maintenance Mode to NORMAL on the M2000 so that the NodeB alarms can be reported to the M2000. 3.1 Procedures for Commissioning the NodeB Through the USB Storage Device and the M2000 On the NodeB side, you can upgrade the software and data configuration through the USB storage device, check the hardware status based on the LED status, and then check the VSWR of the antenna. On the M2000 side, you can perform fault diagnosis and service verification for the NodeB. 3.2 Preparing the USB Storage Device for Local Commissioning The USB storage device must be ready before it is used for local commissioning. The device contains the the NodeB software package, data configuration file, and antenna VSWR detection script. The software package is used for NodeB upgrade, and the data configuration file is used for NodeB initialization, and the antenna VSWR detection script is used for automatic VSWR detection of the NodeB at the local end. 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side) The NodeB supports direct downloading of software and data configuration file from the USB disk. After the downloading, the NodeB automatically activates the software, and then resets. Issue 03 (2011-09-30)


37



3.4 Checking the Status of the NodeB Hardware 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 03 (2011-09-30)


38



3.1 Procedures for Commissioning the NodeB Through the USB Storage Device and the M2000 On the NodeB side, you can upgrade the software and data configuration through the USB storage device, check the hardware status based on the LED status, and then check the VSWR of the antenna. On the M2000 side, you can perform fault diagnosis and service verification for the NodeB.

Prerequisite Before the NodeB commissioning, the NodeB, RNC, and M2000 meet the following requirements: l

The hardware, such as 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 negotiation data of 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 storage device for on-site commissioning is ready for use. For details, see 3.2 Preparing the USB Storage Device for Local Commissioning.

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

Issue 03 (2011-09-30)


39



Figure 3-1 NodeB commissioning procedures through the USB storage device and the M2000

NOTE

l

On-site NodeB commissioning: Indicates that the field engineer performs the NodeB commissioning on-site, involving upgrading the software and downloading the data configuration file from the USB storage device, checking the NodeB hardware status, and checking the VSWR.

l

Remote NodeB commissioning: Indicates that the engineer performs the NodeB commissioning on the M2000 in the central equipment room, involving fault diagnosis and service verification of the NodeB.

Procedure l

On-site end of the NodeB 1.

Issue 03 (2011-09-30)

Insert the USB storage device into the USB port on the WMPT of the NodeB. Select an appropriate operation based on the active software version and data configuration of the NodeB. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

40


l


If ...

Then ...

The active software version and data configuration are inconsistent with those in the USB storage device

Go to Step 2.

The active software version and data configuration are consistent with those in the USB storage device

Go to Step 4.

2.

The NodeB automatically upgrades the software and data configuration. For details, see 3.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side).

3.

Check the NodeB hardware status based on the LED status. For details, see 3.4 Checking the Status of the NodeB Hardware and Rectifying Faults (on the NodeB Side).

4.

Measure the VSWR of the NodeB. Check the VSWR based on the CPRI LED status. For details, see 3.5 Testing the NodeB Antenna VSWR Through the USB Disk (On the NodeB Side).

5.

Remove the USB storage device.

Remote end of the NodeB 1.

Wait till the transmission is available.

2.

Create the NodeB commissioning tasks. For details, see 2.3 Creating NodeB Commissioning Tasks.

3.

Start the NodeB commissioning tasks and specify the commissioning steps as required. For details, see 2.4 Starting NodeB Commissioning Tasks.

4.

The M2000 automatically performs the NodeB commissioning by following the specified commissioning steps. During the NodeB commissioning, you should focus on the commissioning progress and troubleshoot any fault immediately. For related operations, see 2.5 Monitoring NodeB Commissioning.

5.

After the NodeBs pass the service verification, the status of the commissioning tasks changes to Waiting for Acknowledgment. In this case, you need to acknowledge the NodeB commissioning tasks. For details, see 2.6 Confirming Completion of NodeB Commissioning.

6.

Obtain the commissioning reports of the NodeBs. For details, see 2.8 Obtaining NodeB Commissioning Reports.

----End

3.2 Preparing the USB Storage Device for Local Commissioning The USB storage device must be ready before it is used for local commissioning. The device contains the the NodeB software package, data configuration file, and antenna VSWR detection script. The software package is used for NodeB upgrade, and the data configuration file is used for NodeB initialization, and the antenna VSWR detection script is used for automatic VSWR detection of the NodeB at the local end. Issue 03 (2011-09-30)


41



Procedure Step 1 Prepare a USB storage device with a LED. The requirements are as follows: When there is no read or write operation on the USB storage device, the LED on the USB storage device is ON; when there is any read or write operation on the USB storage device, the LED is blinking. The capacity of the USB storage device is larger than 1 GB. Step 2 Check the compatibility of the USB storage device with the NodeB. Do as follows to test the USB storage device: Insert the USB storage device into the USB port on the WMPT of a NodeB that runs normally, and wait for 3 seconds. If the LED on the USB storage device blinks once, it indicates that the USB storage device is functional. If the USB storage device fails the preceding test, replace the USB storage device. You are advised to contact Huawei engineers to obtain the USB storage device. Step 3 Save the related files to the specified directory of the USB storage device. 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 directory. 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 storage device, unplug the USB storage device following the system prompt. If not, errors may occur when you access the USB storage device. Step 4 Optional: The USB protector tool is used to encrypt the data stored in the USB storage device to prevent information leakage or unauthorized data access. 1.

Choose Start > Program > iManager M2000 Client > Start USB Protector Tool. The USB Security Protection Tool program is started.

2.

Choose Setting > Set Security Policies. The Set Security Policies dialog box is displayed. In the Set Security Policies dialog box, set Save Path to the NodeB, and set Protection Algorithm based on the actual situation. Click OK.

3.

Click Open Directory at the lower part of the USB Security Protection Tool dialog box, and then navigate to the NodeB directory of the USB storage device. Click Add Files at the lower part of the USB Security Protection Tool dialog box, select the

Issue 03 (2011-09-30)


42



NodeBCfg.xml file to be encrypted in the NodeB\Configuration, and then click Excute Protect. The file encryption is complete. ----End

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

Prerequisite l

The NodeB is powered on and has passed the power-on check.

l

The USB disk for local commissioning is ready. For details, see 3.2 Preparing the USB Storage Device for Local Commissioning.

CAUTION If the BTS was once upgraded, you must power cycle the BTS before upgrading it by using a USB storage device.

Context When the USB disk is plugged into the corresponding port on the WMPT, 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. After reading the software package and data configuration file, the NodeB checks the whether the active software version and configuration data are consistent with those in the USB disk. If they are inconsistent, the software and configuration upgrade is automatically started. If they are consistent, the upgrade is not performed. Note the following situations when the software and configurations are upgraded 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, If 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 is only saved with 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.

Issue 03 (2011-09-30)


43



– The directory or the file does not exist. – The file format is illegal. – The software version saved in the USB disk is the same as the active software version. – The configuration in the configuration file saved in the USB disk is the same as the active configuration.

Procedure Step 1 Plug the USB disk into the USB port on the WMPT of the BBU3900, as shown in Figure 3-2. 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, activates the software, and then resets. 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 Event

Issue 03 (2011-09-30)

Status of the LED on the USB Disk

Status of the RUN LED on the WMPT

Duration

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

Blinking slowly (ON for 1s and OFF for 1s)

About 1 second to 2 seconds

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

Blinking fast (ON for 0.125s and OFF for 0.125s)

About 12 minutes

Blinking


44



Event

Status of the LED on the USB Disk

Status of the RUN LED on the WMPT

Duration

The NodeB runs normally

ON

Blinking slowly (ON for 1s and OFF for 1s)

You can infer that the software of the NodeB is upgraded successfully if this state lasts more than one minute.

NOTE

l Do not remove the USB disk before the NodeB upgrades the software and runs normally. Otherwise, the file loading or file parsing fails. l After the software and data configuration file are downloaded, it takes three to four minutes for the software activation and takes about two minutes for the NodeB resetting. Do not pay attention to the status of LEDs during these two periods. Pay special attention to the status of LEDs in three phases listed in Table 3-1. l 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 the table, according to the version and configuration. l The upgrade or configuration fails if any of the following phenomena occurs: l After the USB disk is inserted, the RUN LED on the WMPT blinks slowly (ON for 1s and OFF for 1s) and the LED on the USB disk is persistently on. l During the upgrade, the LED on the USB disk is off, and the RUN LED on the WMPT blinks slowly (ON for 1s and OFF for 1s). l The LED on the USB disk is off during the data configuration. Ensure that the hardware of the USB disk is not faulty, and then check whether the version software and data configuration file are saved in the correct directory.

----End

3.4 Checking the Status of the NodeB Hardware 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.

Issue 03 (2011-09-30)


45



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 LED

Status

LED on the USB disk

On

RUN LED on each BBU board

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

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

Off

CPRI LEDs on the WBBP

Steady green

STATE LED on the FAN

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

Issue 03 (2011-09-30)


46



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.

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.

Power cycle the NodeB, and insert the USB disk again, then 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.

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.

l Check whether the dry contact alarm signal cable is properly connected to the corresponding port on the UPEU. If the fault persists, record the fault and the LED status of the WMPT in the data sheet for the NodeB commissioning. Then, rectify the fault on the LMT or M2000.

Issue 03 (2011-09-30)


47



If...


Then...

A CPRI LED on the WBBP is 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.

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 describes how to check the board status and provides guidelines for rectifying faults by observing the indicator status.

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 03 (2011-09-30)

If the RUN LED Is...


Then...

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

The board works properly.

Go to Step 2.


48



If the RUN LED Is...


Then...

On

The power supply is available but the board is faulty.

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

Blinking (on for 0.125s 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.

Off

The power supply is unavailable or the board is faulty.

l Check whether the NodeB is powered on.

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.

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

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

Issue 03 (2011-09-30)

If the ALM LED Is...


Then...

Off


Go to Step 3.

On

The active WMPT is faulty.



49



If the ALM LED Is...


Then...

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. 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. Issue 03 (2011-09-30)


50



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)

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.

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 FAN, and perform the next step based on the status of the STATE LED.

Issue 03 (2011-09-30)


51



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

Issue 03 (2011-09-30)


52



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 Storage Device for Local 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.

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.

Context

Issue 03 (2011-09-30)


53



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. l When a Voltage Standing Wave Ratio (VSWR) test is started on a TRX module that works in co-module mode in a multi-mode base station, or a VSWR test is started on TRX modules that work in different modes but share the same antenna system, services of both modes of the base station are disrupted.

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 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. 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 Testing the NodeB VSWR on the M2000.

Issue 03 (2011-09-30)


54



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 03 (2011-09-30)


55


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.

Context

CAUTION The Maintenance Mode of a NodeB is TESTING by default. After the NodeB commissioning is complete, manually set the Maintenance Mode to NORMAL on the M2000 so that the NodeB alarms can be reported to the M2000.See2.7 Setting the NodeB Maintenance Mode. 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 This section describes how to upgrade the NodeB software, download the data configuration file, and activate the NodeB on the LMT. The software and the configuration data take effect after the NodeB resets automatically. 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. 4.5 Setting the Maximum Output Power of RRU or RFU Set the maximum output power of the RF unit on site, according to the local regulations on power specifications. Issue 03 (2011-09-30)


56



4.6 Data Sheet for NodeB Commissioning This section provides the NodeB data sheet that is used to record the process and results of NodeB commissioning.

Issue 03 (2011-09-30)


57



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.

Issue 03 (2011-09-30)


58



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

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

Issue 03 (2011-09-30)

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.


59



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 Optional: Set the maximum output power of the RRU or RFU on site. For details, see 4.5 Setting the Maximum Output Power of RRU or RFU. Step 6 Record the commissioning process and problems in the 4.6 Data Sheet for NodeB Commissioning, and then export a commissioning report. ----End

4.2 Upgrading the NodeB Software and Downloading the Data Configuration File This section describes how to upgrade the NodeB software, download the data configuration file, and activate the NodeB on the LMT. The software and the configuration data take effect after the NodeB resets automatically.

Prerequisite l

You have logged in to the NodeB LMT.

l

The FTP server functions properly and is connected to the NodeB in the same Intranet.

l

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

l

The FTP user can access a specified directory.

Procedure Step 1 In the navigation tree of the NodeB LMT window, click the MML Commands tab. Run the LST VER command to query the active software version. If...

Then...

The active software version is consistent with the target software version,

Download only the data configuration file and check that it takes effect.

The active software version is inconsistent with the target software version,

Download the target version software package and data configuration file, check that the data configuration file takes effect, and activate the NodeB.

Step 2 Click the Maintenance tab in the navigation tree. Step 3 Choose Software Management > Software Update. The Software Update dialog box is displayed. Issue 03 (2011-09-30)


60



Step 4 Select Upgrade NodeB Software in the dialog box. Click Next. The Update NodeB Software dialog box is displayed. Step 5 Select Downloading the 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 6 Click Next. A confirmation dialog box is displayed. Step 7 Click Yes. A dialog box is displayed, indicating the status and the progress of the procedure.

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.

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. Issue 03 (2011-09-30)


61



l On the M2000 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

Specifies the IP address of SNTP Server. Value range: 0.0.0.1 to 255.255.255.254 Default value: none

SP

Synchronization Period

Specifies the synchronization period. Value range: 1 to 525600 Default value: none

Step 3 Run the LST SNTPCLTPARA command to check the parameters of the SNTP client. Step 4 Run the LST LATESTSUCCDATE 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. Issue 03 (2011-09-30)


62



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 describes how to measure the Received Total Wideband Power (RTWP). The RTWP is the received wideband power in an 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.

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 (that is -112 dBm) on the vertical axis. The RTWP values for the diversity antenna form a horizontal line at the point marked -1115 (that is -111.5 dBm) on the vertical axis. This error may lie in the absent WRFU, RHUB, or RRU, broken link, or faulty channel. Rectify the fault.

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 parameter details 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 either of the following methods: Issue 03 (2011-09-30)


63



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-1 describes the monitoring items. Table 4-1 Monitoring items for the RTWP measurement

Issue 03 (2011-09-30)

Item

Description

Carrier 0 Rx Receive Freq

Indicates the center frequency in the UL of carrier 0. Unit: 0.2 MHz

Carrier 0 Primary RTWP (0.1dBm)

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

Carrier 0 Secondary RTWP (0.1dBm)

Indicates the RTWP value for the diversity antenna in the UL of carrier 0.

Carrier 1 Rx Receive Freq1



















64


4 Commissioning the NodeB on the LMT 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 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 set time interval. 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-2 describes the monitoring items. Issue 03 (2011-09-30)


65



Table 4-2 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.

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 4.6 Data Sheet for NodeB Commissioning.

NOTE

When an NE is under maintenance operations such as construction, upgrade, commissioning, and expansion, the NE may fail to function properly within a short time period and therefore report a large number of alarms to the M2000. Most of these alarms such as reset, switchover, and link disconnection alarms are of high severities and are automatically cleared after the maintenance operations are finished. To avoid these alarms from affecting normal network monitoring, the M2000 defines all the alarms reported during NE maintenance as maintenance mode alarms and specifies a mechanism to handle them. The commissioning personnel can handle active alarms after restoring the normal state of the NodeB. For details , see M2000 Feature Description About Maintenance Mode Management or Feature Description About the Maintenance Mode Alarm.

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

Issue 03 (2011-09-30)


66



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. l When a Voltage Standing Wave Ratio (VSWR) test is started on a TRX module that works in co-module mode in a multi-mode base station, or a VSWR test is started on TRX modules that work in different modes but share the same antenna system, services of both modes of the base station are disrupted.

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

Follow-up Procedure 1.

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

2.

Ensure that the NodeB services resume.

4.5 Setting the Maximum Output Power of RRU or RFU Set the maximum output power of the RF unit on site, according to the local regulations on power specifications.

Prerequisite l

The RF unit is connected properly.

l

The LMT communicates properly with the NodeB.

l

You have obtained the maximum output power of the NodeB. The maximum output power of the RF unit is specified by the local operator.

l

After setting the maximum output power of an RF unit, reset the RF unit manually to make the setting take effect.

Context

Issue 03 (2011-09-30)


67



l

If a BTS has multiple RF units, you need to manually reset each RF unit after setting the maximum output power. In the case of cascaded RF units, you must start the setting from the lowest-level RF unit to minimize the impact on the ongoing services.

l

If the maximum output power to be set exceeds the hardware capability of the RF unit, the setting is not allowed.

l

Before returning a functional RF unit to the spare part warehouse, you must set its maximum output power to 0 and manually reset the RF unit. This operation is not required if the faulty RF units are returned.

l

The function is applicable to only RRU3928, RRU3828, MRFUd, WRFUd and MRFU V2 (P900M).

Procedure Step 1 Run the DSP RRU command to query the cabinet/subrack/slot number, TX channel number, and maximum output power of the RF unit. Step 2 Run the LOC RRUTC command to set the maximum output power of the RF unit. NOTE

The LOC RRUTC command is used to set the maximum output power of one RF unit at a time. In the case of cascaded RF units, you must start the setting from the lowest-level RF unit to minimize the impact on the ongoing services. If the maximum output power exceeds the power specifications supported by the RF unit, do not set the maximum output power.

Step 3 Run the RST BRD command to reset the RF unit. NOTE

The RST BRD command is used to reset one RF unit at a time.

Step 4 Run the DSP TXBRANCH command to check that the maximum output power of each RF unit is set successfully. If...

Then...

The maximum TX power of each RF unit is set successfully

End this task.

The maximum TX power of each RF unit is not set successfully

Check whether the maximum output power exceeds the power specifications supported by the RF unit. Set the maximum output power again. If the setting of the maximum output power still fails, contact Huawei for technical support.

NOTE

Before return the RF unit to the warehouse, run the LOC RRUTC command and set TXMAXPWR to 0. This operation is not required if the faulty RF units are returned.

----End

Issue 03 (2011-09-30)


68



4.6 Data Sheet for NodeB Commissioning This section provides the NodeB data sheet that is used to record the process and results of NodeB commissioning. Table 4-3 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 03 (2011-09-30)

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

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


Handling Abnormal Cases

69



Unsolved Problems After Commissioning

Component

P/N

Faulty Board Record

Issue 03 (2011-09-30)


70


5 Communication Ports on the NodeB

5

Communication Ports on the NodeB

This section describes the communication ports on the NodeB. Table 5-1 describes the communication ports on the NodeB. Table 5-1 Communication ports of the NodeB

Issue 03 (2011-09-30)

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


71


Issue 03 (2011-09-30)

5 Communication Ports on the NodeB

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

DHCP server

67

NodeB

68

For DHCP services

None

UD P

DHCP client

68

NodeB

67

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


72

NodeB Commissioning Guide(V200R013_03)(PDF)-En

Recommend Documents