NodeB Commissioning Guide(V200R013_03)(PDF)-En

NodeBV200R013

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 writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

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

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes the commissioning and initial verification of the NodeB after theNodeB is installed, including upgrading the software package, downloading the dataconfiguration file, and checking hardware status and running status. The commissioning ensuresthat the NodeB operates properly as designed.

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

Product Name Product Version

BTS3900 WCDMA (referred to asBTS3900 in this document)

V200R013

BTS3900A WCDMA (referred to asBTS3900A in this document)

V200R013

BTS3900L WCDMA (referred to asBTS3900L in this document)

V200R013

DBS3900 WCDMA (referred to asDBS3900 in this document)

V200R013

iDBS3900 WCDMA (referred to asiDBS3900 in this document)

V200R013

Intended AudienceThis document is intended for field engineers and deployment engineers.

NodeBCommissioning Guide About This Document


ii

Organization1 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 remotecommissioning on multiple NodeBs on the M2000 in the central equipment room. Thecommissioning procedures, such as software and configuration upgrade, alarm monitoring, andservice 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 USBdisk and the remote commissioning on the M2000. You can upgrade the software andconfiguration through the USB disk, and then check the running status of the NodeB on theM2000.

4 Commissioning the NodeB on the LMT

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

5 Communication Ports on the NodeB

This section describes the communication ports on the NodeB.

ConventionsSymbol Conventions

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

Symbol Description

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

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

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

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

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

General Conventions



iii

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

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

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

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

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

GUI Conventions

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


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

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

Keyboard Operations



iv

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

Format Description

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

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

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

Mouse Operations

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

Action Description

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

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

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



v

Contents

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

1 Changes in NodeB Commissioning Guide..............................................................................1

2 Commissioning the NodeB on the M2000................................................................................32.1 Procedure for Commissioning the NodeB..........................................................................................................52.2 Preparations Before NodeB Commissioning......................................................................................................6

2.2.1 Uploading Data Files...............................................................................................................................102.2.2 Setting an NE as a Transfer Server..........................................................................................................14

2.3 Creating NodeB Commissioning Tasks...........................................................................................................162.4 Starting NodeB Commissioning Tasks.............................................................................................................172.5 Monitoring NodeB Commissioning.................................................................................................................19

2.5.1 Viewing Progress and Status of NodeB Commissioning Tasks..............................................................202.5.2 Handling NodeB Alarms.........................................................................................................................202.5.3 Performing NodeB Fault Diagnosis........................................................................................................212.5.4 Viewing NodeB Service Verification Results.........................................................................................222.5.5 Managing NodeB Commissioning Tasks................................................................................................23

2.6 Confirming Completion of NodeB Commissioning.........................................................................................252.7 Setting the NodeB Maintenance Mode.............................................................................................................252.8 Obtaining NodeB Commissioning Reports......................................................................................................262.9 References to NodeB Commissioning..............................................................................................................27

2.9.1 Interface Description: NodeB Commissioning Window.........................................................................272.9.2 Parameters for the NodeB Deployment List............................................................................................312.9.3 Parameters for NodeB Service Verification Performance Counters.......................................................35

3 Commissioning the NodeB Through the USB Disk+M2000..............................................373.1 Procedures for Commissioning the NodeB Through the USB Storage Device and the M2000......................393.2 Preparing the USB Storage Device for Local Commissioning........................................................................413.3 Upgrading the NodeB Software and Downloading the Data Configuration File (on the NodeB Side)...........433.4 Checking the Status of the NodeB Hardware and Rectifying Faults (on the NodeB Side)..............................45

3.4.1 Checking the Status of LEDs...................................................................................................................463.4.2 Rectifying Common Faults......................................................................................................................473.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

NodeBCommissioning Guide Contents


vi

4.1 Procedure for Commissioning the NodeB on the LMT...................................................................................584.2 Upgrading the NodeB Software and Downloading the Data Configuration File.............................................604.3 Checking the Running Status of the NodeB.....................................................................................................61

4.3.1 Commissioning SNTP.............................................................................................................................614.3.2 Checking the Status of a Cell..................................................................................................................624.3.3 Measuring the RTWP..............................................................................................................................634.3.4 Monitoring the Output Power of the NodeB...........................................................................................654.3.5 Handling NodeB Alarms.........................................................................................................................66

4.4 Testing the NodeB VSWR on the LMT...........................................................................................................664.5 Setting the Maximum Output Power of RRU or RFU.....................................................................................674.6 Data Sheet for NodeB Commissioning............................................................................................................69

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

NodeBCommissioning Guide Contents


vii

1 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 NodeBCommissioning

Notes about how to fill out the deploymentlists 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:


2.1 Procedure for Commissioning theNodeB

The flowchart and related steps are updated.

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

NodeBCommissioning Guide 1 Changes in NodeB Commissioning Guide


1

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:


4.5 Setting the Maximum Output Power ofRRU or RFU

The module models applicable to the functionare added.

3.2 Preparing the USB Storage Device forLocal Commissioning

Descriptions about the encryption of theconfiguration file in the USB storage deviceare 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 newtopics: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 followingchanges:


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

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

NodeBCommissioning Guide 1 Changes in NodeB Commissioning Guide


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 remotecommissioning on multiple NodeBs on the M2000 in the central equipment room. Thecommissioning procedures, such as software and configuration upgrade, alarm monitoring, andservice verification, can be performed on the M2000.

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

2.2 Preparations Before NodeB CommissioningThis section describes how to prepare for NodeB commissioning.

2.3 Creating NodeB Commissioning TasksThis section describes how to create NodeB commissioning tasks on the M2000 client aftermaking required preparations.

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

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

2.6 Confirming Completion of NodeB CommissioningThis section describes how to confirm completion of NodeB commissioning tasks. After NodeBspass service verification, NodeB commissioning tasks switch to the Waiting forConfirmation state. You need to manually confirm the completion.

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

2.8 Obtaining NodeB Commissioning ReportsThis section describes how to obtain NodeB commissioning reports. A NodeB commissioningreport records the details about user operations, commissioning results, and error information.

NodeBCommissioning Guide 2 Commissioning the NodeB on the M2000


3

You can obtain the report of NodeB commissioning tasks when the tasks are in progress andarchive the report when the tasks are complete.

2.9 References to NodeB CommissioningThis section describes references to NodeB commissioning, including introduction todeployment list, interface description, and parameter description.



4

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

Prerequisite

Prepare for the commissioning by referring to 2.2 Preparations Before NodeBCommissioning.

Commissioning Flowchart

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

Figure 2-1 NodeB commissioning flowchart (on the M2000)



5

Procedure

Step 1 Create a NodeB commissioning task by referring to 2.3 Creating NodeB CommissioningTasks.

Step 2 Start the NodeB commissioning task. Set the steps to be performed for this commissioning taskbased 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 whenthe commission task is started. During the commissioning process, monitor the commissioningprogress, rectify faults (if any) to ensure that the commissioning is successful. For details, see2.5 Monitoring NodeB Commissioning.

Step 4 After the NodeB service verification passes, the Waiting for Confirmation status is displayedfor the commission task. Check that the NodeB commissioning is complete. For details, see 2.6Confirming Completion of NodeB Commissioning.

Step 5 Set the NodeB maintenance mode. For details, see 2.7 Setting the NodeB MaintenanceMode.

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

Step 7 Optional: Set the maximum output power of an RF unit. For details, see Setting the MaximumOutput Power of RRU or RFU (NodeB).

----End

2.2 Preparations Before NodeB CommissioningThis 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 mustbe 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 beon 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

Step Operation

1 Check that the NodeB hardware, such as the cabinets, cables, antenna system, andauxiliary devices, is installed and passes the installation check. The NodeB passesa power-on status check and is powered on.



6

Step Operation

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

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

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

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

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

7 The deployment list of the NodeB to be commissioned is ready. For details onpreparing 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 theNodeB Deployment List.

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

9 Check that the network is normal.



7

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

Scenario Note

Deploymentlists areexported fromthe CME

If the CME has been deployed and you have initially configured eNodeBson the CME, it is recommended that you use the CME to export eNodeBdeployment lists. For details, see Exporting eNodeB EDS Data inM2000 Help.Obtain and open the exported deployment list. Check whether the softwareversion, cold patch, and hot patch are consistent with planned ones. If theyare 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 listto those of the current SingleRAN6.0 NodeB to be deployed. Otherwise, theNodeB cannot connect to the M2000. The connection fails because the route andaccess control list (ACL) cannot be configured. The configuration fails becausethe NodeB cannot obtain IP addresses for the M2000 and the FTP server by usingDynamic Host Configuration Protocol (DHCP) and there is no default route. TheNodeB may not obtain the IP addresses if they are not included in the NodeBconfiguration file, the source of imported data. When NAT is deployed on theM2000 side, operators need to change the M2000 IP address and mask on thedeployment list to those used after the NAT.

2. Before deployment, operators need to check whether IP addresses for the M2000and the FTP server are on the same network segment. If they are not, check whetherthe M2000 can be configured as a relay server. If it can, configure the M2000 asthe relay server. If either of the preceding conditions is not met, visit the site anduse a USB flash drive for the commissioning.



8

Scenario Note

Deploymentlists areexported fromthe M2000client

If the CME has not been deployed, you can export NodeB deployment listsfrom 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 AutoDeployment window is displayed.

2. Click . The Select Directory for Exported File dialog box isdisplayed.

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 listto those of the current SingleRAN6.0 NodeB to be deployed. Otherwise, theNodeB cannot connect to the M2000. The connection fails because the route andaccess control list (ACL) cannot be configured. The configuration fails becausethe NodeB cannot obtain IP addresses for the M2000 and the FTP server by usingDynamic Host Configuration Protocol (DHCP) and there is no default route. TheNodeB may not obtain the IP addresses if they are not included in the NodeBconfiguration file, the source of imported data. When NAT is deployed on theM2000 side, operators need to change the M2000 IP address and mask on thedeployment list to those used after the NAT.

2. Before deployment, operators need to check whether IP addresses for the M2000and the FTP server are on the same network segment. If they are not, check whetherthe M2000 can be configured as a relay server. If it can, configure the M2000 asthe relay server. If either of the preceding conditions is not met, visit the site anduse a USB flash drive for the commissioning.

The planned target version of a base station to be commissioned may be inconsistent with thatin the CME deployment list. For example, the current NE version is ***SPC210, and the CMEhas 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 NEmodel remains unchanged. In such a case, users need to use the ***SPC210 package to createbase stations. The baseline version number in the exported deployment list is ***SPC210. Usersneed to manually change the version number based on the following cases:

If... Then...

The target version ofa new base station is***SPC220

l If the baseline version is not ***SPC220 and the baseline versionof ***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 versionto ***SPC220 and do not change the cold patch.

The target version ofa new base station is***SPC210

l If ***SPC210 is not the baseline version and the baseline versionof ***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 thedeployment list.



9

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

PrerequisiteYou have logged in to the M2000 client.

ContextYou 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 proceduresare 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 theM2000 server.

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

Table 2-3 File save paths

File Type Save Path

Softwareversion

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

Cold or hotpatch

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

Configuration data file

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

Deployment list

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

Procedure

Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menuof 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 datafiles as required.



10

If youneed to...

Then...

UploadNEsoftwareversions

l Upload one by oneOne or more software versions corresponding to a certain NE type areuploaded 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.

3. In the Source Path area, click . The dialog box for selectingfiles is displayed. Select files that you want to upload, and then clickOK to return to the NE File Transfer dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the NE File Transfer dialog box. The system startsuploading the software versions.The detailed information about the operations are displayed on the rightof 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 areuploaded 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. Click in the left corner of the dialog box, select an NE type from theNE Type drop-down list, and then select a file type from the File Typedrop-down list.


4. Repeat the preceding two steps to select one or more files correspondingto 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. Thefiles to be uploaded are displayed in the lower part of the dialog box.


7. When Progress is 100%, the software versions are uploaded.



11

If youneed to...

Then...

Uploadcoldpatches

l Upload one by oneOne or more cold patches corresponding to a certain NE type are uploaded ata 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




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






7. When Progress is 100%, the cold patches are uploaded.



12

If youneed to...

Then...

Uploadhotpatches

l Upload one by oneOne or more hot patches corresponding to a certain NE type are uploaded ata 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




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






7. When Progress is 100%, the hot patches are uploaded.



13

If youneed to...

Then...

Uploadconfiguration datafiles

1. On the NE Cinfiguration Data tab page, click Transfer > From OMCClient to OMC Server. The Upload NE Cinfiguration Data dialog box isdisplayed.

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 isdisplayed. Select the folder where the configuration data file that you want toupload is saved, click Select. The Upload NE Cinfiguration Data dialog boxis displayed.CAUTION

The path for saving a NodeB configuration data file to be uploaded must be ..\RNCName\NodeB name\NodeBCfg.xml on the local PC. An RNC Name folder containsone or more NodeB name folders. A NodeB name folder only contains an XML file. Toupload NodeB configuration data files, you must select the RNC Name folder where thefiles 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 DestinationPath area. You can only view the path.

Uploaddeployment lists

1. On the Deployment List tab page, click Transfer > From OMC Client toOMC 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 isdisplayed. Select files that you want to upload, and then click Open to returnto the Upload Deployment List dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload Deployment List dialog box. The system startsuploading the software versions.The detailed information about the operations are displayed on the right ofthe window for preparing files and data, such as Operation, Status, SourceFile 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 emptydeployment template, fill in the template based on the planned data, and upload thetemplate.

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 ServerThe 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 andthus many NEs cannot establish an FTP connection with the M2000 server. In this case, you



14

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

Contextl 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 theNodeB 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 andan 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 to navigate tothe Third Party FTP Server window.

l If an NE chooses another NE, the M2000 server, or a third-party FTP server as its relayserver, 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 serverof 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 thistype 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 inbatches.

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



15

2.3 Creating NodeB Commissioning TasksThis section describes how to create NodeB commissioning tasks on the M2000 client aftermaking required preparations.

Prerequisitel You have logged in to the M2000 client.l NodeB commissioning preparations are complete.

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

1. Click . The Import Deployment List dialog box is displayed.2. In the Specify Deployment List area, select deployment lists.

If you needto...

Then...

Importdeploymentlists from theM2000 server

Select From Server, and then select deployment lists from the drop-down list.

Importdeploymentlists from theM2000 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 listare empty and whether any parameter values are invalid. In addition, the information indicatingwhether 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 eachNodeB. The imported NodeB deployment lists are displayed on the Deployment List tabpage.

l If the import fails, the causes of the failure are displayed on the Operation Information tabpage.

Step 4 (Optional) Modify data of the imported deployment lists as required. This step is mandatorywhen you need to modify data of the imported deployment lists.

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

1. Select a commissioning task from the commissioning task list, and double-click the cellscontaining parameter values to change the values.



16

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

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.2. The changed ESNs highlighted in red are displayed in the commissioning task window

after the modification.

----End

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

Prerequisitel You have logged in to the M2000 client.l NodeB commissioning tasks have been created.

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

Procedure


Step 2 On the Deployment List tab page, right-click one or more commissioning tasks, and then chooseStart 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 commissioningprocedures.

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.



17

Table 2-4 Description of commissioning process

No. Phase Step Description

1 AutoDiscovery

CheckingOMChannel

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

2 AutoConfiguration

DownloadSoftware

The M2000 automatically checks whether the currentNodeB versions are the same as the target softwareversions based on the target version information providedin the deployment lists. If the versions are not the same,the M2000 automatically downloads software from theserver to the NodeBs.

DownloadConfiguration

The M2000 downloads corresponding configuration filesfrom the server to the NodeBs based on the target versioninformation.

Active Upgrade NodeB software and activate NodeBconfiguration data.

3 TestingandMonitoring

TestingVSWR

Test voltage standing wave ratio (VSWR) of the NodeBsto verify that the antenna systems of the NodeBs functionproperly.CAUTION

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

MonitoringCell ServiceStatus

Check whether logical cells of these NodeBs are availableon the RNC side.You can monitor alarms of the NodeB using the M2000during the monitoring to locate and handle exceptions intime.

4 VerifyingService

MonitoringPerformance Counter

When logical cells of these NodeBs are available on theRNC side, the M2000 automatically subscribes to theperformance counters of the logical cells of these NodeBsand checks whether the NodeB services are runningproperly based on the counter values.

5 WaitingforConfirmation

Waiting forConfirmation

After service verification is complete, the commissioningtasks are in the Waiting for Confirmation state. Youneed to manually confirm the completion.

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



18

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

If you needto...

Then...

Enable theAACPfunction

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

Disable theAACPfunction

Clear Use AACP during Auto Discovery.

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

If... Then...

Not all therequired datafiles are available

1. The Data Preparation Check dialog box is displayed, showing checkresults about the required data files.

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 requireddata files areavailable

The M2000 starts commissioning. The selected commissioning tasksswitch to the Running state.NOTE

If all the required data files are available, the Data Preparation Check dialog boxis not displayed.

----End

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



19

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

Prerequisitel You have logged in to the M2000 client.l NodeB commissioning tasks have been created.

ContextUser admin can view commissioning tasks created by any user, whereas other users can viewonly the commissioning tasks created by themselves.

ProcedureStep 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 . The right pane displays execution status of stepsfor commissioning procedures.The execution status is displayed in Status, and details are displayed in Description.

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

----End

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

Prerequisitel You have logged in to the M2000 client.l Commissioning tasks are at the monitoring stage, and the completion of the commissioning

tasks has not yet been confirmed.

ContextAlarms are categorized into the following types by object: physical transmission port alarms,transmission link alarms, antenna alarms, board alarms, cell alarms, software and configurationalarms, external alarms, and other alarms. Other alarms refer to the alarms that cannot becategorized on the basis of specific objects.



20

NOTE

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

Procedure


Step 2 In the commissioning task list, right-click a commissioning task for which you want to handlealarms and choose Open Monitor Window from the shortcut menu. The alarm monitoringwindow 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 DiagnosisThis section describes how to perform NodeB fault diagnosis when exceptions occur at themonitoring stage. If the fault causes of physical transmission port alarms, board alarms, andantenna alarms cannot be located on the basis of the alarm information, you can perform faultdiagnosis and take troubleshooting measures to handle the alarms.

Prerequisitel You have logged in to the M2000 client.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

CAUTIONFault diagnosis on boards and antennas leads to interruption of NodeB services. Therefore, youneed 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 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



21

l Boards: board hardware fault diagnosisl Antennas: antenna fault diagnosis and high-precision VSWR test

After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task anddisplays the diagnosis progress. After the fault diagnosis is complete, you can obtain the faultdiagnosis 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 2 In the commissioning task list, right-click a commissioning task for which you want to performfault diagnosis, and choose Open Monitor Window from the shortcut menu. The alarmmonitoring 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 chooseDiagnose from the shortcut menu. The Diagnosis parameter settings dialog box isdisplayed.

2. Select a NodeB in the Select NE area, select a diagnosis type in the Select diagnosetype area, type diagnosis parameters in the Enter diagnosis parameters area, and clickOK. 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 ResultsThis section describes how to view NodeB service verification results at the service verificationstage. The M2000 automatically subscribes to the performance counters of logical cells of theNodeBs on the RNC side and checks whether the NodeB services are running properly basedon counter values. At this stage, you can check whether each cell of the NodeB has passed serviceverification and view the accumulated value of each counter.

Prerequisitel You have logged in to the M2000 client.l Commissioning tasks are at the service verification stage, and the completion of the

commissioning tasks has not yet been confirmed.



22

Contextl During the service verification, the performance measurement period is the shortest

measurement period supported by the RNC. By default, the shortest measurement periodis 5 minutes.

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

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

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

l After a NodeB passes the service verification, the NodeB commissioning task switches tothe 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, theM2000 automatically deletes the data to release system resources.

Procedure


Step 2 In the commissioning task list, select a commissioning task for which you want to view serviceverification results, right-click the tasks, and choose Open Service Verification Window fromthe 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 startof service verification and the restart of commissioning or the confirmation of commissioningcompletion, are displayed in the service verification window.

l If cells corresponding to all counters once display , service verification is successful. Youcan confirm the completion of the commissioning.

l If the cell corresponding to a certain counter always displays , services related to thiscounter are running abnormally. You need to rectify the faults.

----End

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

Prerequisitel You have logged in to the M2000 client.l NodeB commissioning tasks have been created or started.

ContextFor details about operations on commissioning tasks, see Table 2-5.



23

Table 2-5 Operations on commissioning tasks

Operation

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.

Resume

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 2 On the Deployment List tab page, select one or more commissioning tasks and performoperations as required.

If youneed to...

Then...

Restarttasks

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

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

Resumetasks

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

Canceltasks

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

Deletetasks

1. Right-click the tasks, and then choose Delete from the shortcut menu. TheConfirm dialog box is displayed.

2. Click OK. The system starts deleting the tasks.

----End



24

2.6 Confirming Completion of NodeB CommissioningThis section describes how to confirm completion of NodeB commissioning tasks. After NodeBspass service verification, NodeB commissioning tasks switch to the Waiting forConfirmation state. You need to manually confirm the completion.

Prerequisitel You have logged in to the M2000 client.

l NodeB commissioning tasks are in the Waiting for Confirmation state.

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

Contextl 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, alarmdetected 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 thecompletion, the uncleared alarms will be reported to the M2000 again as normal modealarms.

Procedure


Step 2 In the commissioning task list, select one or more commissioning tasks for which you want toconfirm completion. Right-click the tasks, and then choose Confirm Completion from theshortcut 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 theseNodeBs

l Subscribing to the service verification performance counters of the NodeBs

----End

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

Prerequisitel You have logged in to the M2000 client.

l The NodeB commissioning is complete.



25

Procedure

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

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

----End

2.8 Obtaining NodeB Commissioning ReportsThis section describes how to obtain NodeB commissioning reports. A NodeB commissioningreport 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 andarchive the report when the tasks are complete.

Prerequisitel You have logged in to the M2000 client.l Commissioning tasks are running.

ContextThe exported commissioning report records the information about only the selectedcommissioning tasks. After you manually delete a commissioning task, the generatedcommissioning 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 specifiedas the date when the commissioning report is generated for the first time.

Procedure


Step 2 In the commissioning task list, select one or more commissioning tasks for which you want toexport the report, right-click the tasks, and then choose Export Deployment Report from theshortcut menu. A dialog box is displayed, asking you whether to export alarm data at the sametime.

If... Then...

You need toexport alarmdata

Click Yes. The Save dialog box is displayed.

You do notneed to exportalarm data

Click No. The Save dialog box is displayed.

Step 3 Specify a save path, and then click Save.



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 conventionNodeB_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, double-click 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 datais saved in the alarm sub-folder.

----End

2.9 References to NodeB CommissioningThis section describes references to NodeB commissioning, including introduction todeployment list, interface description, and parameter description.

2.9.1 Interface Description: NodeB Commissioning WindowThis section describes the elements of the NodeB Auto Deployment window and the functionof 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



27

Table 2-6 Description of main window for NodeB commissioning

Area No. ElementName

Description

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

2 Commissioning task list

Displays all the commissioning tasks and their progress. Youcan right-click a task, and then choose the corresponding menuitem 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 bythemselves.

3 Operationresults

Records the results of operations.

4 Shortcutmenu

You can right-click a task, and then choose the correspondingmenu 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 describesthe window.

Figure 2-3 Alarm monitoring window for NodeB commissioning



28

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

AreaNo.

ElementName

Description

1 Alarm objecttree

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

2 Alarm list After an object type is selected, all alarms of this object type aredisplayed in the alarm list.

3 Diagnosistask list

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

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

Figure 2-4 NodeB service verification window



29

Table 2-8 Description of NodeB service verification window

AreaNo.

ElementName

Description

1 Verificationresult 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

AreaNo.

ElementName

Description

1 File list Displays the files on the M2000 server.

2 Button Provides buttons for operations on uploading data files.

3 Tab named aftera data file type

Displays tabs named after data file types that are required forcommissioning.

4 Operationresults

Displays the operation results about uploading data files.



30

2.9.2 Parameters for the NodeB Deployment ListThis 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 isimported, the M2000 checks whether any mandatory parameter values are in the list are empty orinvalid.

l Exported by Default or not: Indicates whether the parameter value is exported by default when youuse the CME to export the deployment list.

l Configurable or not: Indicates whether the parameter values in the deployment list that is exportedfrom the CME can be configured in the auto-deployment window after being imported to theM2000.

l If the deployment list is exported from the M2000, you only need to configure the deployment list byreferring to the Mandatory or not column in Table 2-10.

Table 2-10 Parameters for the NodeB deployment list

ParameterField

Description Mandatoryor not

Exported byDefault or not

Configurableor not

RNC ID ID of the RNC towhich theNodeB belongs

Yes Yes No

RNC Name Name of theRNC to whichthe NodeBbelongs

No Yes No

NodeB ID ID of the NodeB Yes Yes No

NodeB Name Name of theNodeB

Yes Yes No

NodeB ESN1 Electronic serialnumber (ESN)on the BBUmounting ear

No l Yes if thisparameter isconfigured onthe CME

l No if thisparameter isnotconfigured onthe CME

Yes



31

ParameterField



Configurableor not

NodeB ESN2 Reservedparameter. Youdo not need toconfigure it.



Yes

NodeB OM IPaddress

IP address of theNodeB OMchannel

Yes Yes No

NodeB OM IPSubnet mask

IP subnet maskof the NodeBOM channel

Yes Yes No

NodeBInterface IPaddress

IP address of theNodeB interfaceboard (If the porttype of theNodeB is ETHor TRUNK, thisparameter ismandatory)



No

NodeBInterface IPSubnet mask

IP subnet maskof the NodeBinterface board(If the port typeof the NodeB isETH orTRUNK, thisparameter ismandatory)



No

NodeB NextHop IP addressto DHCPServer

Next hop IPaddress from theNodeB to theDHCP server



No



32

ParameterField



Configurableor not

NodeB NextHop IP addressto AACPServer

Next hop IPaddress from theNodeB to theAACP server



No

M2000 IPaddress

IP address of theM2000



No

M2000 IPSubnet mask

IP subnet maskof the M2000



No

NodeB OMVLAN ID

VLAN ID of theNodeB



No

NodeB OMVLAN Priority

VLAN priorityof the NodeB



No



33

ParameterField



Configurableor not

NodeB OMNext Hop IPaddress

Next hop IPaddress of theNodeB OMchannel



No

NodeB Type Type of theNodeB to becommissioned

Yes Yes No

NodeBSoftwareVersion

Target softwareversion of theNodeB



Yes

NodeB ColdPatch Version

Target coldpatch version ofthe NodeB



Yes

NodeB HotPatch Version

Target hot patchversion of theNodeB



Yes



34

ParameterField



Configurableor not

NodeBConfigurationFile CRC

CRC value ofthe NodeB dataconfigurationfile



No

Contact Contact of theonsite engineers

No Not exported Yes

2.9.3 Parameters for NodeB Service Verification PerformanceCounters

This section describes the parameters of the performance counters that are monitored at theservice verification stage during NodeB commissioning.

Table 2-11 describes the service performance counters of monitored NodeBs at the serviceverification stage during NodeB commissioning.

Table 2-11 Parameters of performance counters

Parameter Description

Uu ConnectionVerification

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

AMRVerification

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

VPVerification

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

PSConversationVerification

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

PS StreamingVerification

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

PS InteractiveVerification

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

PS BackgroundVerification

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



35

Parameter Description

HSDPAVerification

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

HSUPAVerification

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



36

3 Commissioning the NodeB Through theUSB Disk+M2000

About This Chapter

This chapter describes how to commission the NodeB with the combination of a on-site USBdisk and the remote commissioning on the M2000. You can upgrade the software andconfiguration through the USB disk, and then check the running status of the NodeB on theM2000.

Context

CAUTIONThe Maintenance Mode of a NodeB is TESTING by default. After the NodeB commissioningis complete, manually set the Maintenance Mode to NORMAL on the M2000 so that the NodeBalarms can be reported to the M2000.

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

3.2 Preparing the USB Storage Device for Local CommissioningThe USB storage device must be ready before it is used for local commissioning. The devicecontains the the NodeB software package, data configuration file, and antenna VSWR detectionscript. The software package is used for NodeB upgrade, and the data configuration file is usedfor NodeB initialization, and the antenna VSWR detection script is used for automatic VSWRdetection of the NodeB at the local end.

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

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


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 connectionby checking the LEDs on the boards or the auxiliary devices, and rectify faults in time.

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



38

3.1 Procedures for Commissioning the NodeB Through theUSB Storage Device and the M2000

On the NodeB side, you can upgrade the software and data configuration through the USBstorage device, check the hardware status based on the LED status, and then check the VSWRof the antenna. On the M2000 side, you can perform fault diagnosis and service verification forthe NodeB.

PrerequisiteBefore the NodeB commissioning, the NodeB, RNC, and M2000 meet the followingrequirements: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 poweredon.

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 targetversion of the NodeB to be commissioned.

The USB storage device for on-site commissioning is ready for use. For details, see 3.2Preparing the USB Storage Device for Local Commissioning.

Commissioning proceduresFigure 3-1 shows the NodeB commissioning procedures.



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 commissioningon-site, involving upgrading the software and downloading the data configuration file from the USBstorage device, checking the NodeB hardware status, and checking the VSWR.

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

Procedurel On-site end of the NodeB

1. Insert the USB storage device into the USB port on the WMPT of the NodeB. Selectan appropriate operation based on the active software version and data configurationof the NodeB.



40

If ... Then ...

The active software version and dataconfiguration are inconsistent withthose in the USB storage device

Go to Step 2.

The active software version and dataconfiguration are consistent with thosein 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 ConfigurationFile (on the NodeB Side).

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

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.

l Remote end of the NodeB

1. Wait till the transmission is available.

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

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

4. The M2000 automatically performs the NodeB commissioning by following thespecified commissioning steps. During the NodeB commissioning, you should focuson the commissioning progress and troubleshoot any fault immediately. For relatedoperations, see 2.5 Monitoring NodeB Commissioning.

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

6. Obtain the commissioning reports of the NodeBs. For details, see 2.8 ObtainingNodeB Commissioning Reports.

----End

3.2 Preparing the USB Storage Device for LocalCommissioning

The USB storage device must be ready before it is used for local commissioning. The devicecontains the the NodeB software package, data configuration file, and antenna VSWR detectionscript. The software package is used for NodeB upgrade, and the data configuration file is usedfor NodeB initialization, and the antenna VSWR detection script is used for automatic VSWRdetection of the NodeB at the local end.



41

Procedure

Step 1 Prepare a USB storage device with a LED. The requirements are as follows: When there is noread 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. Thecapacity 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 theUSB storage device: Insert the USB storage device into the USB port on the WMPT of aNodeB that runs normally, and wait for 3 seconds. If the LED on the USB storage device blinksonce, it indicates that the USB storage device is functional. If the USB storage device fails thepreceding test, replace the USB storage device. You are advised to contact Huawei engineers toobtain 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 usuallyperformed by configuration engineers.

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

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

CAUTIONAfter you have saved the files from the PC into the USB storage device, unplug the USBstorage device following the system prompt. If not, errors may occur when you access theUSB storage device.

Step 4 Optional: The USB protector tool is used to encrypt the data stored in the USB storage deviceto prevent information leakage or unauthorized data access.

1. Choose Start > Program > iManager M2000 Client > Start USB Protector Tool. TheUSB 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 ProtectionAlgorithm 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 atthe lower part of the USB Security Protection Tool dialog box, select the



42

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

----End

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

The NodeB supports direct downloading of software and data configuration file from the USBdisk. After the downloading, the NodeB automatically activates the software, and then resets.

Prerequisitel 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 USBStorage Device for Local Commissioning.

CAUTIONIf the BTS was once upgraded, you must power cycle the BTS before upgrading it by using aUSB storage device.

Context

When the USB disk is plugged into the corresponding port on the WMPT, the BBU3900automatically detects the USB disk and installs the USB disk driver. After the installation, theNodeB automatically reads the software and data configuration file in the fixed directories ofthe USB disk and verifies their names and formats.

After reading the software package and data configuration file, the NodeB checks the whetherthe active software version and configuration data are consistent with those in the USB disk. Ifthey are inconsistent, the software and configuration upgrade is automatically started. If theyare consistent, the upgrade is not performed.

Note the following situations when the software and configurations are upgraded from the USBdisk:

l By default, the NodeB downloads the software and data configuration file from the USBdisk 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 anddata 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 downloadedfrom the USB disk.

l If the USB disk is only saved with the software, the NodeB automatically upgrades thesoftware.

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

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



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 thesoftware, and then resets. For details on the status of the LED on the USB disk and the status ofthe RUN LED on the WMPT in this process, see Table 3-1.

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

Event Status of the LEDon the USB Disk

Status of the RUNLED on theWMPT

Duration

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

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

About 1 second to 2seconds

The NodeBdownloads thesoftware and dataconfiguration filefrom the USB disk.

Blinking Blinking fast (ONfor 0.125s and OFFfor 0.125s)

About 12 minutes



44

Event Status of the LEDon the USB Disk

Status of the RUNLED on theWMPT

Duration

The NodeB runsnormally

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

You can infer that thesoftware of theNodeB is upgradedsuccessfully if thisstate lasts more thanone 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 thesoftware activation and takes about two minutes for the NodeB resetting. Do not pay attention to thestatus of LEDs during these two periods. Pay special attention to the status of LEDs in three phaseslisted in Table 3-1.

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

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 OFFfor 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 blinksslowly (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 softwareand data configuration file are saved in the correct directory.

----End

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

This section describes how to check the BBU3900 hardware installation and how to rectify faults.You can locate the hardware faults regarding external ports and CPRI optical cable connectionby checking the LEDs on the boards or the auxiliary devices, and rectify faults in time.

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



45

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

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

Table 3-2 LED status of the functional NodeB

LED Status

LED on the USB disk On

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

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 FaultsNOTE

If the LED indicates faults on the USB disk or on the boards of the NodeB, rectify the faults by referringto 3.4.2 Rectifying Common Faults. If the fault is not described in 3.4.2 Rectifying Common Faults,rectify the fault by referring to3.4.3 Guidelines for Rectifying Faults.

Figure 3-3 LED status of common faults



46

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

Context

Table 3-3 Methods of rectifying common faults

If... You can InferThat...

Then...

The LED on theUSB disk is off

The NodeBsoftware fails to beupgraded from theUSB disk.

Power cycle the NodeB, and insert the USB diskagain, then upgrade the software.If the software fails to be upgraded again, recordthe problem in the data sheet for the NodeBcommissioning, and then upgrade the software onthe LMT.

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

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

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

The ALM LEDon the WMPT,WBBP, or UTRPis on

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

The ALM LEDon the activeWMPT blinks

The external porton the activeWMPT is faulty.

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

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

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



47

If... You can InferThat...

Then...

A CPRI LED onthe WBBP issteady red

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

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

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

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

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

The RRU or theWRFU is faulty.

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

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

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

l Check whether a VSWR LED on the RRU orthe WRFU is off. If the VSWR LED is not off,see 3.4.3 Guidelines for Rectifying Faults torectify the fault.

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

properly connected to the RRU or theWRFU.

– Check whether there is an external drycontact alarm on the RRU or the WRFU. Ifthere is an external dry contact alarm, recordthe alarm in the data sheet for the NodeBcommissioning.

3.4.3 Guidelines for Rectifying FaultsThis section describes how to check the board status and provides guidelines for rectifying faultsby observing the indicator status.

Procedure

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

If the RUN LEDIs...

You can InferThat...

Then...

Blinking (on for 1sand off for 1s)

The board worksproperly.

Go to Step 2.



48

If the RUN LEDIs...


Then...

On The power supply isavailable but theboard is faulty.

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

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

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

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

Off The power supply isunavailable or theboard is faulty.

l Check whether the NodeB is powered on.l Reinstall the board to check whether the

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

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

If the ALM LEDIs...


Then...

Off The board worksproperly.

Go to Step 3.

On The active WMPT isfaulty.




49

If the ALM LEDIs...


Then...

Blinking The external port onthe active WMPT isfaulty.

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

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

EMU, or EMUA blink (on for 0.125sand off for 0.125s), check whether theRS485 signal cable is properlyconnected.

– If the RUN LEDs on the standbyWMPT, WBBP, or UTRP blink (on for0.125s and off for 0.125s), reinstall theboard to check whether the fault isrectified.

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

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

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

l If the GPS antenna system is configured,check whether it is properly connected.

Step 3 Check the ALM LED status of the WBBP, UTRP and standby WMPT, and perform the nextstep based on the status of the ALM LED.

If the ALM LEDIs...


Then...

Off The board worksproperly.

Go to Step 4.

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

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


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



50

If the CPRI LEDIs...


Then...

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

Go to Step 5.

Off The CPRI port is notconfigured.

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

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

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

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

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

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

The RRU or theWRFU is faulty.

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

Blinking red (on for1s and off for 1s)

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

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

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

properly connected to the RRU or theWRFU.

– Check whether there is an external drycontact alarm on the RRU or theWRFU. If there is an external drycontact alarm, record the alarm in thedata sheet for the NodeBcommissioning.

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



51

If the STATE LEDIs...


Then...

Blinking green The board worksproperly.

Go to Step 6.

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

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

If the ALM LEDIs...


Then...

Off The module or thedevice worksproperly.

Go to Step 7.

On The module or thedevice is faulty.

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

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

If the VSWR LEDIs...


Then...

Off No VSWR alarm isgenerated.

Go to Step 8.

On for 0.125s and offfor 0.125s

There are alarms onthe ANT_TX/RXAport and ANT_RXBport.

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

On There is an alarm onthe ANT_TX/RXAport.

On for 1s and off for1s

There is an alarm onthe ANT_RXB port.

Step 8 Check the transmission status of the NodeB.



52

If... Then...

The NodeB uses the E1transmission mode

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

The NodeB uses the FEtransmission mode

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

----End

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

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

Prerequisitel The NodeB is powered on and passes the power-on check.l The USB disk for on-site commissioning is ready. For details, see 3.2 Preparing the USB

Storage Device for Local Commissioning.

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

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

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

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



53

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

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

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

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

the USB disk and then plug it back into the USB port to start the VSWR test.

l Before the VSWR test is started, the NodeB should run properly and the CPRI LED on theWBBP should be steady green.

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

Step 2 Wait for the NodeB to automatically test the VSWR. When the USB disk LED is off, the VSWRtest is complete. Observe the status of the CPRI LED on the WBBP.

l If the CPRI LED blinks red (on for 1s and off for 1s), the RRU or WRFU has the VSWRalarm. 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 theantenna VSWR of the NodeB on the M2000. For details, see Testing the NodeB VSWR on the M2000.



54

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

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

Unplug the USB disk and end the VSWR test.

----End



55

4 Commissioning the NodeB on the LMT

About This Chapter

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

Context

CAUTIONThe Maintenance Mode of a NodeB is TESTING by default. After the NodeB commissioningis complete, manually set the Maintenance Mode to NORMAL on the M2000 so that the NodeBalarms can be reported to the M2000.See2.7 Setting the NodeB Maintenance Mode.

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

4.2 Upgrading the NodeB Software and Downloading the Data Configuration FileThis section describes how to upgrade the NodeB software, download the data configurationfile, and activate the NodeB on the LMT. The software and the configuration data take effectafter the NodeB resets automatically.

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

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

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

NodeBCommissioning Guide 4 Commissioning the NodeB on the LMT


56

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



57

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

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

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

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

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



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

If ... Then ...

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

Go to Step 2.

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

Go to Step 3.



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

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

Step 5 Optional: Set the maximum output power of the RRU or RFU on site. For details, see 4.5 Settingthe Maximum Output Power of RRU or RFU.

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

----End

4.2 Upgrading the NodeB Software and Downloading theData Configuration File

This section describes how to upgrade the NodeB software, download the data configurationfile, and activate the NodeB on the LMT. The software and the configuration data take effectafter the NodeB resets automatically.

Prerequisitel 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 theLST VER command to query the active software version.

If... Then...

The active software version is consistent withthe target software version,

Download only the data configuration fileand check that it takes effect.

The active software version is inconsistentwith the target software version,

Download the target version softwarepackage and data configuration file, checkthat 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 isdisplayed.



60

Step 4 Select Upgrade NodeB Software in the dialog box. Click Next. The Update NodeB Softwaredialog box is displayed.

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

NOTE

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

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

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

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

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

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

----End

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

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

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

Procedure

Step 1 Start the SNTP server. An SNTP server can be on the RNC side or on the M2000 server side,which is determined by the system configuration.l On the RNC side: Start the SNTP server through the security and monitor manager on the

BAM server.



61

l On the M2000 side: The Sun operating system has the self-contained SNTP services. Fordetails, refer to the M2000 Administrator Guide.

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

Parameter ID Parameter Name Description

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

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

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

If... Then...

The synchronization is successful End this task.

The synchronization fails Check the following items:l Whether the SNTP server is runningl Whether the IP address of the NodeB is correct

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

----End

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

Procedure

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



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 RTWPThis describes how to measure the Received Total Wideband Power (RTWP). The RTWP is thereceived wideband power in an UL channel band measured at the access point of the UMTSTerrestrial Radio Network Access (UTRAN). You can calibrate the gain of UL RF channelsthrough RTWP measurement. The RTWP measurement does not affect ongoing services.

PrerequisiteYou have logged in to the NodeB LMT.

ContextThe reference standards for the RTWP measurement are as follows:

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

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

NOTE

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

l If the reported RTWP is invalid, an abnormal RTWP curve is displayed. The RTWP values for themain antenna form a horizontal line at the point marked -1120 (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, brokenlink, or faulty channel. Rectify the fault.

Procedure

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

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

For the parameter details in the RTWP Measurement dialog box, see Interface Reference forMeasuring 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:



63

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

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

----End

ResultTable 4-1 describes the monitoring items.

Table 4-1 Monitoring items for the RTWP measurement

Item Description

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

Carrier 0 Primary RTWP(0.1dBm)

Indicates the RTWP value for the main antenna in the UL ofcarrier 0.

Carrier 0 Secondary RTWP(0.1dBm)

Indicates the RTWP value for the diversity antenna in the ULof carrier 0.

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

















64

NOTE

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

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

4.3.4 Monitoring the Output Power of the NodeBThis describes how to monitor the output power of the NodeB, including the typical output powerand output power of each carrier.

PrerequisiteYou have logged in to the NodeB LMT.

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

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

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

Procedure

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

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

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

Step 3 Set the corresponding parameters in the dialog box.

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

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

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

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

----End

ResultTable 4-2 describes the monitoring items.



65

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

Item Description

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

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

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

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

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

Procedure

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

Step 2 Clear the alarms related to the NodeB.

If... Then...

An active NodeB alarm exists Clear the alarm based on the alarm online help.

An active alarm related to the NodeBcannot be cleared

Record it in 4.6 Data Sheet for NodeBCommissioning.

NOTEWhen an NE is under maintenance operations such as construction, upgrade, commissioning, andexpansion, the NE may fail to function properly within a short time period and therefore report a largenumber of alarms to the M2000. Most of these alarms such as reset, switchover, and link disconnectionalarms 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 reportedduring NE maintenance as maintenance mode alarms and specifies a mechanism to handle them. Thecommissioning personnel can handle active alarms after restoring the normal state of the NodeB. Fordetails , see M2000 Feature Description About Maintenance Mode Management or Feature DescriptionAbout the Maintenance Mode Alarm.

----End

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



66

Prerequisitel You have logged in to the NodeB LMT.

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

Context

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

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

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

l When a Voltage Standing Wave Ratio (VSWR) test is started on a TRX module that worksin co-module mode in a multi-mode base station, or a VSWR test is started on TRX modulesthat work in different modes but share the same antenna system, services of both modes ofthe base station are disrupted.

Procedure

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

----End

Follow-up Procedure1. 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 RFUSet the maximum output power of the RF unit on site, according to the local regulations on powerspecifications.

Prerequisitel 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 powerof the RF unit is specified by the local operator.

Contextl After setting the maximum output power of an RF unit, reset the RF unit manually to make

the setting take effect.



67

l If a BTS has multiple RF units, you need to manually reset each RF unit after setting themaximum output power. In the case of cascaded RF units, you must start the setting fromthe 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, thesetting is not allowed.

l Before returning a functional RF unit to the spare part warehouse, you must set its maximumoutput power to 0 and manually reset the RF unit. This operation is not required if the faultyRF 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 thecase of cascaded RF units, you must start the setting from the lowest-level RF unit to minimize the impacton the ongoing services.

If the maximum output power exceeds the power specifications supported by the RF unit, do not set themaximum 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 unitis set successfully.

If... Then...

The maximum TX power ofeach RF unit is setsuccessfully

End this task.

The maximum TX power ofeach RF unit is not setsuccessfully

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

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

----End



68

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

Table 4-3 Data Sheet for NodeB Commissioning

Site Name

NodeB Model

Commission Time

CommissioningEngineer

CommissioningResult

□ Successful; □ Failed

Commissioning Item Conclusion Handling AbnormalCases

CommissioningPreparation Phase

Faults in NodeB hardwareinstallation are cleared.

□ Yes; □ No

Transmission links between theNodeB and the RNC are ready.

□ Yes; □ No

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

□ Yes; □ No

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

□ Yes; □ No

CommissioningPhase

The NodeB software,BootROM software aresuccessfully upgraded.

□ Yes; □ No

The data configuration file issuccessfully downloaded.

□ Yes; □ No

The NodeB hardware status ischecked.

□ Yes; □ No

The running status of theNodeB is checked.

□ Yes; □ No

The NodeB VSWR is checked. □ Yes; □ No

Problem Description Impact



69

Unsolved ProblemsAfterCommissioning

Component P/N

Faulty BoardRecord



70

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

Protocol

A Side ASidePortNumber(RX)

B Side B SidePortNumber(TX)

Service AuthorityManagement

TCP

NodeB 6000

LMT 1024to65535

For the LMT todeliver themaintenancecommand to theNodeB

User name/password

TCP

NodeB 6001

LMT 1024to65535

For the NodeB toreport alarm

None

TCP

NodeB 6006

LMT 1024to65535

For maintenance, theformat is BIN.

None

TCP

NodeB 6007

M2000server

1024to65535

For M2000;integration port forMML, alarm, andBIN

User name/password

TCP

NodeB 20 Site debugconsole

1024to65535

For FTP; debugmode; localmaintenance FE portonly

None

NodeBCommissioning Guide 5 Communication Ports on the NodeB


71

Protocol

A Side ASidePortNumber(RX)

B Side B SidePortNumber(TX)

Service AuthorityManagement

TCP


1024to65535

For FTP; debugmode; localmaintenance FE portonly

User name/password

TCP


1024to65535

For telnet; debugmode; localmaintenance FE portonly

User name/password

UDP

DHCP server 67 NodeB 68 For DHCP services None

UDP

DHCP client 68 NodeB 67 For DHCP services None

UDP

M2000 server,RNC BAM, orany other SNTPserver

123 NodeB 1024to65535

For synchronizingSNTP clock

None

TCP

LMT, M2000server, RNCBAM, or anyother FTPserver

20 NodeB 1024to65535

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

None

TCP

LMT, M2000server, RNCBAM, or anyother FTPserver

21 NodeB 1024to65535

For FTP control User name/password

NodeBCommissioning Guide 5 Communication Ports on the NodeB


72

Documents

NodeB Commissioning Guide(V200R013_03)(PDF)-En