eNodeB Commissioning Guide(V100R002C00 03)

eNodeB V100R002C00

Commissioning Guide Issue

03

Date

2010-08-10

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

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

Website:

http://www.huawei.com

Email:

[email protected]

Issue 03 (2010-08-10)

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

i

eNodeB Commissioning Guide

About This Document

About This Document

Purpose The eNodeB Commissioning Guide describes the commissioning and verification to be performed after the eNodeB installation. Commissioning ensures that the eNodeB works properly as designed. This document also describes three commissioning modes for the eNodeB, which are the remote commissioning on the M2000, local commissioning through the USB storage device, and local commissioning on the LMT.

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

Product Version

DBS3900 LTE

V100R002C00

DBS3900 TDLTE

V100R002C00

BTS3900 LTE

V100R002C00

BTS3900A LTE

V100R002C00

BTS3900L LTE

V100R002C00

Intended Audience This document is intended for: l

eNodeB installation engineers

l

Field engineers

Organization 1 Changes in eNodeB Commissioning Guide Issue 03 (2010-08-10)


iii


About This Document

This chapter describes the changes in the eNodeB Commissioning Guide. 2 Commissioning Prerequisites The section describes the prerequisites of the eNodeB commissioning. 3 Commissioning Mode The eNodeB supports three commissioning modes, namely, remote commissioning on the M2000, local commissioning through the USB storage device, and local commissioning on the LMT. The commissioning mode is selected based on site conditions. Generally, remote commissioning on the M2000 is recommended. 4 Remote eNodeB Commissioning on the M2000 This chapter describes how to commission the eNodeB on the M2000. Multiple eNodeBs can be commissioned remotely on the M2000. 5 Local eNodeB Commissioning Through the USB Storage Device In the local eNodeB commissioning through the USB storage device, you can upgrade the eNodeB software and data configuration file by using the USB storage device, and check the running status of the eNodeB by the LEDs. Then, create the eNodeB commissioning task on the M2000 server. 6 Local eNodeB Commissioning on the LMT In the local eNodeB commissioning on the LMT, you can upgrade the eNodeB software, download the configuration file, perform the ALD commissioning, and check the running status of the eNodeB on the LMT. Then, establish the OM channel between the eNodeB and the M2000 through the M2000 server. 7 eNodeB Commissioning Reference This chapter describes the communication ports on the eNodeB, and provides the eNodeB commissioning data sheet.

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

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

iv


Issue 03 (2010-08-10)


About This Document

Symbol

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

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

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

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

Italic

Book titles are in italics.

Courier New

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

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

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

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

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[ x | y | ... ]

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

{ x | y | ... }*

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

[ x | y | ... ]*

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

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

Issue 03 (2010-08-10)


v


About This Document

Convention

Description

Boldface

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

>

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

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

Description

Key

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

Key 1+Key 2

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

Key 1, Key 2

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

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

vi

Action

Description

Click

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

Double-click

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

Drag

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


Issue 03 (2010-08-10)


Contents

Contents About This Document...................................................................................................................iii 1 Changes in eNodeB Commissioning Guide.........................................................................1-1 2 Commissioning Prerequisites..................................................................................................2-1 3 Commissioning Mode...............................................................................................................3-1 4 Remote eNodeB Commissioning on the M2000...................................................................4-1 4.1 Remote eNodeB Commissioning on the M2000.............................................................................................4-3 4.2 Preparations for the Remote eNodeB Commissioning on the M2000............................................................4-6 4.2.1 Preparations for Remote eNodeB Commissioning on the M2000.........................................................4-7 4.2.2 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the M2000 .........................................................................................................................................................................4-9 4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment.................................4-10 4.2.4 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the M2000...............4-13 4.2.5 Configuring the Security Equipment....................................................................................................4-14 4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000...........................................................................................................................................................4-18 4.2.7 Importing the Site Common Information Through the USB Storage Device......................................4-21 4.3 Creating the eNodeB Commissioning Task on the M2000...........................................................................4-24 4.4 Managing the eNodeB Commissioning Task................................................................................................4-28 4.4.1 Viewing the eNodeB Commissioning Progress...................................................................................4-28 4.4.2 Pausing/Retrying the eNodeB Commissioning Task...........................................................................4-30 4.4.3 Restarting/Deleting the eNodeB Commissioning Task.......................................................................4-30 4.5 Obtaining the eNodeB Commissioning Report on the M2000.....................................................................4-31 4.6 Checking the Running Status of the eNodeB on the M2000........................................................................4-31 4.6.1 eNodeB Health Check..........................................................................................................................4-32 4.6.2 Handling the eNodeB Alarms..............................................................................................................4-34 4.7 Commissioning the TMA on the M2000......................................................................................................4-35 4.8 Commissioning the Antenna System on the M2000.....................................................................................4-36 4.9 Commissioning the Environment Monitoring Equipment on the M2000.....................................................4-36 4.9.1 Setting the Environment Alarm Parameters.........................................................................................4-37 4.9.2 Checking for the External Environment Alarms..................................................................................4-38 4.10 Setting the Maximum TX Power of RRU or RFU......................................................................................4-39 4.11 Testing the Basic Services of the eNodeB..................................................................................................4-40 Issue 03 (2010-08-10)


vii


Contents

4.12 Acknowledging the eNodeB Commissioning on the M2000......................................................................4-41

5 Local eNodeB Commissioning Through the USB Storage Device...................................5-1 5.1 Local eNodeB Commissioning Through the USB Storage Device................................................................5-2 5.2 Preparations for the Local eNodeB Commissioning Through the USB Storage Device................................5-5 5.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning Through the USB Storage Device................................................................................................................................................5-6 5.2.2 Configuring the Security Equipment......................................................................................................5-7 5.2.3 Obtaining the Digital Certificate Required for the eNodeB Commissioning Through the USB Storage Device..............................................................................................................................................................5-9 5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device .......................................................................................................................................................................5-10 5.3 Downloading and Activating the Software and Data Configuration File Through the USB Storage Device .............................................................................................................................................................................5-11 5.4 Checking the Status of LEDs........................................................................................................................5-15

6 Local eNodeB Commissioning on the LMT..........................................................................6-1 6.1 Local eNodeB Commissioning on the LMT...................................................................................................6-3 6.2 Preparations for the Local eNodeB Commissioning on the LMT..................................................................6-6 6.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the LMT .........................................................................................................................................................................6-7 6.2.2 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the LMT....................6-8 6.2.3 Configuring the Security Equipment......................................................................................................6-9 6.2.4 Configuring the FTP Server.................................................................................................................6-11 6.2.5 Downloading the Digital Certificate on the LMT................................................................................6-13 6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...................6-14 6.4 Downloading the License for eNodeB Commissioning on the LMT...........................................................6-16 6.5 Commissioning the ALD on the LMT..........................................................................................................6-16 6.5.1 Commissioning the RET Antenna........................................................................................................6-17 6.5.1.1 Querying the Active Software Version of the RET Antenna............................................................6-18 6.5.1.2 Downloading the RET Antenna Software.........................................................................................6-19 6.5.1.3 Downloading the Data Configuration File of the RET Antenna.......................................................6-19 6.5.1.4 Calibrating the RET Antenna............................................................................................................6-20 6.5.2 Commissioning the TMA.....................................................................................................................6-20 6.6 Commissioning the Antenna System on the LMT........................................................................................6-21 6.7 Commissioning the Environment Monitoring Equipment on the LMT........................................................6-22 6.7.1 Setting the Environment Alarm Parameters.........................................................................................6-22 6.7.2 Checking for the External Environment Alarms..................................................................................6-23 6.8 Setting the Maximum TX Power of RRU or RFU........................................................................................6-24 6.9 Handling the eNodeB Alarms on the LMT...................................................................................................6-25 6.10 Querying the Running Status of the eNodeB on the LMT..........................................................................6-25 6.11 Testing the Basic Services of the eNodeB..................................................................................................6-26 6.12 Establishing the OM Channel Between the M2000 and the eNodeB.........................................................6-27 6.13 Setting the eNodeB Status...........................................................................................................................6-30

7 eNodeB Commissioning Reference........................................................................................7-1 viii


Issue 03 (2010-08-10)


Contents

7.1 Data Sheet for eNodeB Commissioning......................................................................................................... 7-2 7.2 Communication Ports on the eNodeB.............................................................................................................7-5

Issue 03 (2010-08-10)


ix


Figures

Figures Figure 2-1 Commissioning network without the security GW............................................................................ 2-1 Figure 2-2 Commissioning network with the security GW................................................................................. 2-2 Figure 4-1 Procedure of remote eNodeB commissioning on the M2000.............................................................4-4 Figure 4-2 Flowchart of preparations for remote eNodeB commissioning on the M2000 without the security GW ...............................................................................................................................................................................4-7 Figure 4-3 Flowchart of preparations for remote eNodeB commissioning on the M2000 with the security GW ...............................................................................................................................................................................4-8 Figure 4-4 Location of the ESN...........................................................................................................................4-9 Figure 4-5 Inserting the USB storage device.....................................................................................................4-22 Figure 4-6 eNodeB Auto Deployment tab page...............................................................................................4-25 Figure 4-7 Import dialog box............................................................................................................................4-26 Figure 4-8 Set Stepsdialog box..........................................................................................................................4-27 Figure 4-9 eNodeB Auto Deployment tab page...............................................................................................4-30 Figure 5-1 Procedure of local eNodeB commissioning through the USB storage device................................... 5-3 Figure 5-2 Location of the ESN...........................................................................................................................5-6 Figure 5-3 Inserting the USB storage device.....................................................................................................5-13 Figure 5-4 LED status of the common faults.....................................................................................................5-16 Figure 6-1 Procedure of local eNodeB commissioning on the LMT...................................................................6-4 Figure 6-2 Location of the ESN...........................................................................................................................6-7 Figure 6-3 FTP Server Configuration tab page...............................................................................................6-12 Figure 6-4 FTP server configuration dialog box.............................................................................................6-12 Figure 6-5 Download and Activate Software interface...................................................................................6-15 Figure 6-6 Procedures for commissioning the RET antenna..............................................................................6-17 Figure 6-7 Main Topology tab page..................................................................................................................6-28 Figure 6-8 Create Topo Object dialog box......................................................................................................6-29

Issue 03 (2010-08-10)


xi


Tables

Tables Table 4-1 eNodeB commissioning procedure on the M2000...............................................................................4-5 Table 4-2 Information related to the eNodeB.......................................................................................................4-9 Table 4-3 Tools required for the remote commissioning on the M2000............................................................4-10 Table 4-4 eNodeB software and files required for automatic eNodeB deployment...........................................4-11 Table 4-5 Security GW configuration................................................................................................................4-15 Table 4-6 Descriptions of customized information............................................................................................4-17 Table 4-7 Required digital certificate.................................................................................................................4-19 Table 4-8 Configuration items of the common configuration information in the external template.................4-19 Table 4-9 Automatic eNodeB commissioning process......................................................................................4-29 Table 4-10 eNodeB health checklist...................................................................................................................4-32 Table 5-1 eNodeB commissioning procedure through the USB storage device..................................................5-4 Table 5-2 Information related to the eNodeB.......................................................................................................5-6 Table 5-3 Tools required for the local commissioning through the USB storage device.....................................5-7 Table 5-4 Security GW configuration..................................................................................................................5-7 Table 5-5 LED status of the functional eNodeB................................................................................................5-15 Table 6-1 eNodeB commissioning procedure on the LMT..................................................................................6-5 Table 6-2 Information related to the eNodeB.......................................................................................................6-7 Table 6-3 Tools required for the local eNodeB commissioning on the LMT......................................................6-8 Table 6-4 Security GW configuration..................................................................................................................6-9 Table 6-5 Preparations for commissioning the RET antenna.............................................................................6-18 Table 6-6 Extended alarm ports..........................................................................................................................6-23 Table 6-7 eNodeB device checklist....................................................................................................................6-26 Table 7-1 Data sheet for eNodeB commissioning................................................................................................7-2 Table 7-2 Communication ports on the eNodeB..................................................................................................7-5

Issue 03 (2010-08-10)


xiii


1

1 Changes in eNodeB Commissioning Guide

Changes in eNodeB Commissioning Guide This chapter describes the changes in the eNodeB Commissioning Guide.

03 (2010-08-10) This is the commercial issue. Compared with issue 02 (2010-07-30), this issue includes the following new topics: l

4.10 Setting the Maximum TX Power of RRU or RFU

02 (2010-07-30) This is the commercial issue. Compared with issue 01 (2010-05-20), this issue includes the following new topics: l

4.8 Commissioning the Antenna System on the M2000

l

6.6 Commissioning the Antenna System on the LMT

Compared with issue 01 (2010-05-20), this issue includes the following changes:

Issue 03 (2010-08-10)

Topic

Change Description

5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device

The save path of files in the USB storage device is changed.

4.1 Remote eNodeB Commissioning on the M2000

The procedure of remote eNodeB commissioning on the M2000 is modified. The operations of Commissioning the Antenna System on the M2000 is added.

5.1 Local eNodeB Commissioning Through the USB Storage Device

The procedure of local eNodeB commissioning through the USB storage device is modified. The operations of Commissioning the Antenna System on the M2000 is added.


1-1



Topic

Change Description

6.1 Local eNodeB Commissioning on the LMT

The procedure of local eNodeB commissioning on the LMT is modified. The operations of Commissioning the Antenna System on the LMT is added.

Compared with issue 01 (2010-05-20), no information is deleted in this issue.

01 (2010-05-20) This is the draft issue. Compared with V100R001 issue 04 (2010-03-31), this issue includes the following new topics: l

4.1 Remote eNodeB Commissioning on the M2000

l

4.2.1 Preparations for Remote eNodeB Commissioning on the M2000

l

4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment

l

4.2.5 Configuring the Security Equipment

l

4.4 Managing the eNodeB Commissioning Task

l

4.4.1 Viewing the eNodeB Commissioning Progress

l

4.4.2 Pausing/Retrying the eNodeB Commissioning Task

l

4.4.3 Restarting/Deleting the eNodeB Commissioning Task

l

4.5 Obtaining the eNodeB Commissioning Report on the M2000

l

4.6.1 eNodeB Health Check

l

4.12 Acknowledging the eNodeB Commissioning on the M2000

l

5.1 Local eNodeB Commissioning Through the USB Storage Device

l

5.2.2 Configuring the Security Equipment

l

6.1 Local eNodeB Commissioning on the LMT

l

6.13 Setting the eNodeB Status

Compared with V100R001 issue 04 (2010-03-31), this issue includes the following changes:

1-2

Topic

Change Description

2 Commissioning Prerequisites

The title Introduction to Commissioning is changed to Commissioning Prerequisites. The figure for eNodeB commissioning network with the security GW is modified.

4 Remote eNodeB Commissioning on the M2000

The flowchart for the remote eNodeB commissioning on the M2000 is deleted.

4.2 Preparations for the Remote eNodeB Commissioning on the M2000

The flowchart of preparations for remote eNodeB commissioning on the M2000 is deleted.


Issue 03 (2010-08-10)



Topic

Change Description

4.3 Creating the eNodeB Commissioning Task on the M2000

The title eNodeB Self-Deployment and Commissioning on the M2000 is changed to Creating the eNodeB Commissioning Task on the M2000. The background information about automatic eNodeB deployment is added, and the procedure for creating the eNodeB commissioning task is modified.

4.6 Checking the Running Status of the eNodeB on the M2000

The background information and procedure for checking the running status of the eNodeB are deleted.

4.6.2 Handling the eNodeB Alarms

The procedure for checking for eNodeB alarms is modified.

5 Local eNodeB Commissioning Through the USB Storage Device

The flowchart for the local eNodeB commissioning through the USB storage device is deleted.

6 Local eNodeB Commissioning on the LMT

The flowchart for the local eNodeB commissioning on the LMT is deleted.

7.1 Data Sheet for eNodeB Commissioning

The Data Sheet for eNodeB Commissioning is modified.

Compared with V100R001 issue 04 (2010-03-31), the following topics are deleted in this issue:

Issue 03 (2010-08-10)

Topic

Cause of Deletion

Uploading the eNodeB software package

This topic is described in 4.3 Creating the eNodeB Commissioning Task on the M2000.

Uploading the ALD software and data configuration file

The procedure for uploading the RET software and data configuration file is described in 4.3 Creating the eNodeB Commissioning Task on the M2000. The procedure for uploading the TMA software is described in 4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment.

Configuring the public DHCP server

This topic is described in 4.2.5 Configuring the Security Equipment.

Downloading the license on the M2000

This topic is described in 4.3 Creating the eNodeB Commissioning Task on the M2000 and 4.4.1 Viewing the eNodeB Commissioning Progress.

Commissioning the RET on the M2000

This topic is described in 4.3 Creating the eNodeB Commissioning Task on the M2000 and 4.4.1 Viewing the eNodeB Commissioning Progress.


1-3



2

Commissioning Prerequisites

The section describes the prerequisites of the eNodeB commissioning.

Requirements for the Equipment Status l

All parts of the equipment and related cables are installed properly. For details, see the associated installation guide.

l

Hardware check is performed before the eNodeB equipment is powered on.

Requirements for the network To smoothly commission the eNodeB, the network equipment must meet the following requirements: l

The eNodeB is connected to the core network equipment MME or S-GW, which is configured with the interconnection data required for commissioning and can provide the basic functions of the core network.

l

The M2000 server is installed with the mediation software corresponding to the target version of the eNodeB to be commissioned.

Figure 2-1 and Figure 2-2 show the typical commissioning network. Figure 2-1 Commissioning network without the security GW

Issue 03 (2010-08-10)


2-1



Figure 2-2 Commissioning network with the security GW

NOTE

2-2

l

The lines in the preceding figures indicate only the connections but not the quantity and types of cables.

l

Figure 2-1 shows a typical application of the commissioning network without the security GW. The eNodeB, MME, S-GW, and M2000 are located in a trusted domain, and they can communicate with each other directly.

l

Figure 2-2 shows a typical application of the commissioning network with the security GW. The eNodeB is located on a network whose trusted domain is different from the network where the MME, S-GW, and M2000 are located. Therefore, the eNodeB communicates with the MME, S-GW, and M2000 through the security GW.


Issue 03 (2010-08-10)


3 Commissioning Mode

3

Commissioning Mode

The eNodeB supports three commissioning modes, namely, remote commissioning on the M2000, local commissioning through the USB storage device, and local commissioning on the LMT. The commissioning mode is selected based on site conditions. Generally, remote commissioning on the M2000 is recommended.

Three Commissioning Modes and Application Scenarios Commissioning Mode

Application Scenario

Remote commissioning on the M2000

l

The eNodeB is properly connected to the M2000 server.

l

Site swapping (permissible eNodeB downtime ≥ 1 hour)

l

Site deployment

l

The connection between the eNodeB and the M2000 server is not established yet.

l

There is a USB storage device.

l

Site swapping (permissible eNodeB downtime < 1 hour)

l

Site deployment

l

The connection between the eNodeB and the M2000 server is not established yet.

l

The eNodeB deployment through the USB storage device fails, or there is no USB storage device.

l

Site swapping (permissible eNodeB downtime < 1 hour)

l

Site deployment

Local eNodeB commissioning through the USB storage device

Local eNodeB commissioning on the LMT

Issue 03 (2010-08-10)


3-1


4


Remote eNodeB Commissioning on the M2000

About This Chapter This chapter describes how to commission the eNodeB on the M2000. Multiple eNodeBs can be commissioned remotely on the M2000. 4.1 Remote eNodeB Commissioning on the M2000 This section describes the procedure of remote eNodeB commissioning on the M2000. 4.2 Preparations for the Remote eNodeB Commissioning on the M2000 Before the remote eNodeB commissioning on the M2000, you need to obtain the related eNodeB information and tools. When the security GW is deployed in the network, you need to obtain the required digital certificate, configure the security equipment, and configure the public Dynamic Host Configuration Protocol (DHCP) server. If the public DHCP server cannot be configured, you can import the common information of the site to the eNodeB by using the USB storage device on site. 4.3 Creating the eNodeB Commissioning Task on the M2000 After the preparations for eNodeB commissioning are complete, create the eNodeB commissioning task on the M2000. This task will be automatically performed by the M2000. The M2000 supports automatic commissioning of multiple eNodeBs. 4.4 Managing the eNodeB Commissioning Task After the eNodeB commissioning task is created, you can view the commissioning progress, pause and resume the commissioning task, and restart or delete the commissioning task. 4.5 Obtaining the eNodeB Commissioning Report on the M2000 The eNodeB commissioning report includes the operation details, results, and error information obtained during commissioning. It also includes the eNodeB health check report. The eNodeB commissioning report can be viewed during the commissioning task for handling problems in time, or be obtained after the commissioning task for report archiving. 4.6 Checking the Running Status of the eNodeB on the M2000 This chapter describes how to perform the health check and alarm check on the eNodeB through the M2000. 4.7 Commissioning the TMA on the M2000 Issue 03 (2010-08-10)


4-1



This section describes how to commission the Tower Mounted Amplifier (TMA). The main process of TMA commissioning is loading the TMA software. After the load is complete, the TMA is automatically reset. The software takes effect after the TMA is reset. 4.8 Commissioning the Antenna System on the M2000 Commissioning the antenna system helps to check for problems in the installed antenna system. 4.9 Commissioning the Environment Monitoring Equipment on the M2000 This section describes how to check the environment monitoring equipment on the M2000. After the environment monitoring equipment is connected, you need to commission it so that it functions properly. 4.10 Setting the Maximum TX Power of RRU or RFU Set the maximum TX power of the RRU or RFU on site, according to the local regulations on power specifications. 4.11 Testing the Basic Services of the eNodeB This section describes how to test the basic services of the eNodeB. 4.12 Acknowledging the eNodeB Commissioning on the M2000 After the eNodeB health check is complete, the status of the commissioning task changes to Awaiting_ack. In this case, you need to acknowledge the eNodeB commissioning.

4-2


Issue 03 (2010-08-10)



4.1 Remote eNodeB Commissioning on the M2000 This section describes the procedure of remote eNodeB commissioning on the M2000. Figure 4-1 shows the procedure of remote eNodeB commissioning on the M2000.

Issue 03 (2010-08-10)


4-3



Figure 4-1 Procedure of remote eNodeB commissioning on the M2000

4-4


Issue 03 (2010-08-10)



Table 4-1 eNodeB commissioning procedure on the M2000 St ep

Mandat ory/ Option al

1

Local and remote cooperative operations

Make preparations for the remote eNodeB commissioning, which involves obtaining the eNodeB information and commissioning tools, configuring the security equipment, obtaining the eNodeB software and files required for automatic deployment, and obtaining the digital certificates. For details, see 4.2 Preparations for the Remote eNodeB Commissioning on the M2000.

Mandato ry

2

Remote operations on the M2000

Create the eNodeB commissioning task on the M2000, which involves uploading the required software and files, importing the EDS file, and checking the ESN binding. For details, see 4.3 Creating the eNodeB Commissioning Task on the M2000.

Mandato ry

3

Manage the eNodeB commissioning task on the M2000. For details, see 4.4 Managing the eNodeB Commissioning Task.

Mandato ry

4

Obtain the eNodeB commissioning report. For details, see 4.5 Obtaining the eNodeB Commissioning Report on the M2000.

Mandato ry

5

Learn the running status of the eNodeB by viewing the eNodeB commissioning report. For details, see 4.6 Checking the Running Status of the eNodeB on the M2000.

Mandato ry

6

Commission the TMA on the M2000. For details, see 4.7 Commissioning the TMA on the M2000.

Optional

7

Commission the antenna system on the M2000. For details, see 4.8 Commissioning the Antenna System on the M2000.

Optional

After the environment monitoring equipment is connected, perform the commissioning and enable the environment monitoring equipment to function properly. For details, see 4.9 Commissioning the Environment Monitoring Equipment on the M2000.

Optional

9

Setting the Maximum TX Power of RRU or RFU. For details, see 4.10 Setting the Maximum TX Power of RRU or RFU.

Optional

10

Verify the basic services of the eNodeB. For details, see 4.11 Testing the Basic Services of the eNodeB.

Mandato ry

8

Issue 03 (2010-08-10)

Operation



4-5



St ep

11

Operation


Mandat ory/ Option al

After the eNodeB commissioning is complete, confirm the eNodeB commissioning task. For details, see 4.12 Acknowledging the eNodeB Commissioning on the M2000.

Mandato ry

4.2 Preparations for the Remote eNodeB Commissioning on the M2000 Before the remote eNodeB commissioning on the M2000, you need to obtain the related eNodeB information and tools. When the security GW is deployed in the network, you need to obtain the required digital certificate, configure the security equipment, and configure the public Dynamic Host Configuration Protocol (DHCP) server. If the public DHCP server cannot be configured, you can import the common information of the site to the eNodeB by using the USB storage device on site. 4.2.1 Preparations for Remote eNodeB Commissioning on the M2000 This section describes the procedure of preparations for remote eNodeB commissioning on the M2000. 4.2.2 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the M2000 Before the remote eNodeB commissioning on the M2000, you need to arrange for the related eNodeB information and tools. 4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment Before the automatic eNodeB deployment on the M2000, the required eNodeB software and files should be ready. 4.2.4 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the M2000 When the security GW is deployed in the network, the eNodeB and the security GW need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate consists of the operator's cross certificate signed by Huawei, operator's root certification authority (CA) certificate (or certificate chain with the root CA certificate), and operator's certificate revocation list (CRL) at the eNodeB side, and Huawei root CA certificate and Huawei CRL file at the security GW side. 4.2.5 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the digital certificate or pre-shared key is adopted for authentication, the customized parameters, such as the IP address of the security GW and the IP address of the M2000 server, should be set on the public DHCP server. In this way, a security channel between the eNodeB and the security GW can be set up, and the eNodeB can be connected to the M2000. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server.

4-6


Issue 03 (2010-08-10)



4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000 When the security GW is deployed on the network, you need to save the required files in the specified directory of the USB storage device, and then import the files to the eNodeB by using the USB storage device. 4.2.7 Importing the Site Common Information Through the USB Storage Device When the security GW is deployed in the network, you can import the common configuration information to the eNodeB by using the USB storage device if the customized parameters cannot be configured through the public DHCP server.

4.2.1 Preparations for Remote eNodeB Commissioning on the M2000 This section describes the procedure of preparations for remote eNodeB commissioning on the M2000.

Preparations for Remote eNodeB Commissioning on the M2000 Without the Security GW Figure 4-2 shows the flowchart of preparations for remote eNodeB commissioning on the M2000 without the security GW. Figure 4-2 Flowchart of preparations for remote eNodeB commissioning on the M2000 without the security GW

Preparations for Remote eNodeB Commissioning on the M2000 With the Security GW Figure 4-3 shows the flowchart of preparations for remote eNodeB commissioning on the M2000 with the security GW. Issue 03 (2010-08-10)


4-7



Figure 4-3 Flowchart of preparations for remote eNodeB commissioning on the M2000 with the security GW

4-8


Issue 03 (2010-08-10)



4.2.2 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the M2000 Before the remote eNodeB commissioning on the M2000, you need to arrange for the related eNodeB information and tools.

Procedure Step 1 Collect the information related to the eNodeB, as described in Table 4-2. Table 4-2 Information related to the eNodeB Item

Source or Remarks

eNodeB name

Planned by the operator.

eNodeB ID


eNodeB Electronic Serial Number (ESN)

ESN identifies an NE uniquely. During network deployment, the installation engineer reports the mapping relation between the location of each site and the ESN to the staff at the maintenance center. Before delivery, the ESN is attached to the BBU of the eNodeB, as shown in Figure 4-4.

Figure 4-4 Location of the ESN

Step 2 Arrange for the tools required for the remote commissioning on the M2000, as described in Table 4-3.

Issue 03 (2010-08-10)


4-9



Table 4-3 Tools required for the remote commissioning on the M2000 Tool

Description

USB storage device (optional, required when you import the common information on site)

l

The USB storage device is equipped with an indicator that indicates the data transmission status.

l

Capacity ≥ 256 MB

l

Recommended models: Netac U208, Netac U180, Netac U215, and Netac U210.

l

The USB storage device has no additional function. The additional functions include but are not limited to encryption, antivirus, bootstrap, MP3, MP4, and smart mobile phone.

l

The common information to be imported to the eNodeB is saved in the USB storage device. For details about the common information, see 4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000.

Testing UE

The testing UE is functional and is registered in the Home Subscriber Server (HSS).

----End

4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment Before the automatic eNodeB deployment on the M2000, the required eNodeB software and files should be ready.

Prerequisite The M2000 server and client are running properly.

Context Table 4-4 describes the eNodeB software and files required for automatic eNodeB deployment.

4-10


Issue 03 (2010-08-10)



Table 4-4 eNodeB software and files required for automatic eNodeB deployment

Issue 03 (2010-08-10)

eNodeB Software or File

Obtaining Method


eNodeB software package

Download the software package from http:// support.huawei.com/ and save it to the local computer. A digital signature is already labeled on the software package. If the software package is modified by someone, a warning will be prompted during software upload to the M2000. In this situation, you are required to obtain the correct software package.

Remote eNodeB commissioning on the M2000

eNodeB data configuration file

The name of the data configuration file should be M2000.xml. The file name is case sensitive. Complete the configuration by referring to the eNodeB Initial Configuration Guide and then save the data configuration file in a specified directory on the M2000 server.

Remote eNodeB commissioning on the M2000

Easy Deployment System (EDS) file

The name of the EDS file is EDS_(project name)_(time).csv. This file contains information such as the NE ID, NE name, and IP address of the NE. Complete the configuration by referring to the eNodeB Initial Configuration Guide and then save the data configuration file in a specified directory on the M2000 server. Or the EDS file can be created manually and saved on the local computer.

All scenarios

eNodeB commissionin g license

Apply for the commissioning license by referring to the license application guide, and save the commissioning license to the local computer. The license application guide can be downloaded from http:// support.huawei.com/.

If some eNodeB functions or specifications are limited by the default license, a commissioning license needs to be installed. The commissioning license has a time limit. You should replace the commissioning license with a commercial license after the eNodeB commissioning is complete.


4-11


4-12


eNodeB Software or File

Obtaining Method


RET antenna software

The RET antenna software is provided by the Antenna Line Device (ALD) manufacturer. Save the RET antenna software to the local computer.

If the eNodeB and the 3G base station share the antenna system, the antenna system is managed on the 3G side. In some cases, the antenna system is managed by a third party. Therefore, RET antenna commissioning on the eNodeB side is not required. If the antenna system is managed by the eNodeB, RET antenna commissioning on the eNodeB side is mandatory.

RET antenna data configuration file

The RET antenna data configuration file is provided by the ALD manufacturer. Save the RET antenna data configuration file to the local computer. The configuration data varies with the manufacturer and RET antenna model.

Same as above.

RET antenna commissionin g data template

Download the template from http:// support.huawei.com/. Configure the commissioning data by referring to the help page in the commissioning data template, and then save the commissioning data to the local computer.

Same as above.

OMIP data template

Download the template from http:// support.huawei.com/. The OMIP resources are provided by the telecom operator. Configure the data by referring to the help page in the OMIP data template, and then save the data to the local computer.

The OMIP data template is required when the M2000 automatically allocates the OMIP address.

Tower Mounted Amplifier (TMA) software

The TMA software is provided by the ALD manufacturer. Save the TMA software to the local computer.

If the eNodeB and the 3G base station share the TMA, the TMA is managed on the 3G side. In some cases, the TMA is managed by a third party. Therefore, TMA commissioning on the eNodeB side is not required. If the TMA is managed by the eNodeB, TMA commissioning on the eNodeB side is mandatory.


Issue 03 (2010-08-10)



The FTP server information saved on the M2000 server is as follows: l

FTP server IP address: IP address of the M2000 server

l

FTP user name: ftpuser

l

FTP password: ftpuser

l

Source directory on the FTP server: \export\home\sysm\ftproot\

Procedure Step 1 Obtain the eNodeB software and files required for automatic eNodeB deployment according to Table 4-4. Step 2 Upload the TMA software to the M2000 server. 1.

On the local computer, choose Start > Run. The Run dialog box is displayed.

2.

Type ftp://M2000 server IP address in the Run dialog box. Click OK. The directory of the M2000 server is displayed.

3.

Right-click in the blank area and select Login As... from the shortcut menu. The Log On As dialog box is displayed.

4.

Type the user name and password for FTP login to the M2000 server.

5.

Click Login to log in to the M2000 server. Save the TMA software in the ftproot directory.

----End

4.2.4 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the M2000 When the security GW is deployed in the network, the eNodeB and the security GW need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate consists of the operator's cross certificate signed by Huawei, operator's root certification authority (CA) certificate (or certificate chain with the root CA certificate), and operator's certificate revocation list (CRL) at the eNodeB side, and Huawei root CA certificate and Huawei CRL file at the security GW side.

Prerequisite l

The operator already obtains the cross certificate signed by Huawei if cross certification is used. NOTE

Before Huawei signs a cross certificate for an operator, the operator needs to provide a cross certificate request file. The cross certificate request file is based on the PKCS#10 format, and it can be generated from the operator's root or subordinate CA used to grant certificates for the eNodeB, security GW, and M2000. l

Issue 03 (2010-08-10)

The CR/CRL database is deployed on the server of the DeMilitarized Zone (DMZ) of the operator, and supports FTP. Thus, the files on the CR/CRL database can be downloaded in FTP mode.


4-13



Context NOTE

The cross certificates involved in this document are signed by Huawei for the operator. If the operator's certificate chain with the root CA certificate is used instead of the operator's root CA certificate, you can replace the operator's root CA certificate in this document with the operator's certificate chain with the root CA certificate.

Procedure Step 1 Obtain the digital certificate required for the eNodeB. 1.

2.

3.

Confirm with the operator's CA administrator that the cross certificate and operator's CRL file are saved on the CR/CRL server of the DMZ. If ...

Then ...

The cross certificate and operator's CRL file are saved on the CR/CRL server

Record the save path of the cross certificate and operator's CRL file. Go to step Step 1.2.

The cross certificate and operator's CRL file are not saved on the CR/CRL server, or cannot be downloaded from the CR/ CRL server

Go to step Step 1.3.

Specify the save path of the cross certificate and operator's CRL file on the public DHCP server, so that the eNodeB can obtain the save path upon startup. For details, see 4.2.5 Configuring the Security Equipment. If ...

Then ...

The configuration of the public DHCP server is successful

Go to step Step 2.

The configuration of the public DHCP server fails

Go to step Step 1.3.

Ask the operator for the cross certificate, operator's root CA certificate, and operator's CRL file. Save the files to the USB storage device, and then perform the task 4.2.7 Importing the Site Common Information Through the USB Storage Device. NOTE

You can save either or both of the cross certificate and operator's root CA certificate to the USB storage device.

Step 2 Obtain the digital certificate required for the security GW. Ensure that Huawei root CA certificate and Huawei CRL file are configured on the security GW. ----End

4.2.5 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the digital certificate or pre-shared key is adopted for authentication, 4-14


Issue 03 (2010-08-10)



the customized parameters, such as the IP address of the security GW and the IP address of the M2000 server, should be set on the public DHCP server. In this way, a security channel between the eNodeB and the security GW can be set up, and the eNodeB can be connected to the M2000. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server.

Prerequisite l

The Quidway S6500 Series Ethernet Switches Operation Manual is ready, and can be downloaded from http://support.huawei.com/.

l

The infoX AAA Commissioning Guide is ready, and can be downloaded from http:// support.huawei.com/.

l

If the IEEE 802.1x authentication is adopted, the operator should use the authentication access equipment that supports 802.1x authentication and the corresponding AAA server that supports Extensible Authentication Protocol (EAP).

l

Table 4-5 describes the configuration items that you need to pay special attention to when the security GW is used.

Context

Table 4-5 Security GW configuration Item

Description

IP address

Both the public security GW and the serving security GW should be configured with the IP address of the interface for the untrusted domain on the eNodeB side and IP address of the interface for the trusted domain on the EPC side.

Route

l

Public security GW: The routes to the M2000, eNodeB, and temporary OM IP address should be configured.

l

Serving security GW: The routes to the M2000, S-GW, MME, IP address of the interface to the eNodeB, S1 signaling, S1 services, and OM IP address should be configured.

ike local name

The public security GW and serving security GW should be configured.

ike proposal

l

The authentication method item should be digital certificate mode or pre-shared key mode according to the actual network.

l

The authentication algorithm item must be SHA1.

l

The encryption algorithm item must be AES.

l

The DH group item must be DH group2.

acl

Issue 03 (2010-08-10)

It is recommended that you configure permit ip.


4-15


l


Item

Description

ike peer

l

Public security GW: The key or certificate domain should be configured according to the authentication mode specified in the ike proposal. The local id type item must be name, the remote name item must be p-segw, the ike proposal item should be configured according to previous configurations, and the ike version item can be V1 or V2. The ip pool item should be configured to allocate the temporary OM IP for the eNodeB.

l

Serving security GW: The key or certificate domain should be configured according to the authentication mode specified in the ike proposal. The local id type item must be name, the remote name item must be s-segw, the ike proposal item should be configured according to previous configurations, and the ike version item can be V1 or V2.

ipsec proposal

The encapsulation mode item must be tunnel, the transform item must be esp, the esp authentication item must be shal, and the esp encryption item must be aes.

ipsec policytemplate

The public security GW and serving security should be set to the template mode. The Acl should be configured according to previous configurations. If the public security GW and serving security GW are the same, different acl values must be configured. The psf group must be DH group2. The public security GW and serving security GW must correspond to different ike peer values. The ipsec proposal item should be configured according to previous configurations.

ipsec policy

This item must be configured according to the template in the ipsec policy-template.

ipsec binding to port

The policy can be bound to the planned port according to the configuration in the ipsec policy.

The purposes of configuring the public DHCP server are as follows: –

After obtaining the customized information through the message from the eNodeB to the public DHCP server, the public DHCP server can identify Huawei eNodeB.

–

Then, the public DHCP server returns the customized information to the eNodeB.

The public DHCP server needs to configure the information for identifying Huawei eNodeB and the customized information related to Huawei equipment. The customized information provides necessary configuration information for setup of the DHCP server with the security GW deployed, as described in Table 4-5.

4-16


Issue 03 (2010-08-10)



Table 4-6 Descriptions of customized information Fiel d ID

Field

Field Lengt h (Unit: Byte)

Description

Configurati on Scenario

18

IP address of the public security GW

4

This is the IP address of the public security GW used to establish the IPSec channel.

Pre-shared key or digital certificate

19

Domain name of the public security GW

1-64

This is the domain name of the public security GW used to establish the IPSec channel.


22

IP address of the CR/CRL server

4

This is the IP address of the server used to download the CRL and cross certificate.

Digital certificate

23

CR/CRL server access user name

1-32

This is the user name used to access the CR/CRL server.

Digital certificate

24

CR/CRL server access password

1-16

This is the password used to access the CR/CRL server.

Digital certificate

25

Path of the cross certificate on the CR/CRL server

1-64

This is the path for saving the cross certificate on the CR/ CRL server.

Digital certificate

26

Path of the CRL file on the CR/CRL server

1-64

This is the save path of the operator's CRL file on the CR/ CRL server.

Digital certificate

28

DHCP server IP address provided by the M2000

4

This is the IP address of the DHCP server that is provided by the M2000.


29

DHCP server domain name provided by the M2000

1-64

This is the DHCP server domain name provided by the M2000.


31

Local name of the public security GW

1-32

This is the local ID of the public security GW.


l

When the authentication access equipment is used, the authentication mode of Radius (remote authentication dial-in user service) and the authentication method of EAP should be configured, because certificate authentication is adopted at present.

l

When the AAA server is used, the CA certificates of terminal users should be uploaded, and the file names of the user certificate and private key should be configured for the AAA server.

Issue 03 (2010-08-10)


4-17



Procedure Step 1 Check the configuration of the security GW according to Table 4-5. Step 2 For details about the customized fields required for the pre-shared key and digital certificate, see Table 4-6. The public DHCP server may vary with different operators. Configure the public DHCP server according to the customized information in the context information. Step 3 Configure the authentication access equipment. The authentication access equipment may vary with different operators. The example here describes a typical configuration of an authentication access equipment. Take the Quidway S6500 series Ethernet switch as an example. Run the dot1x command to enable the global 802.1x feature. Run the dot1x [ interface interfacelist ] command to enable the 802.1x feature on a specified port. Run the dot1x authenticationmethod { chap | pap | eap } command to set the EAP authentication method. For details, see the Quidway S6500 Series Ethernet Switches Operation Manual. Step 4 Configure the eNodeB CA certificate for the AAA server. The AAA server may vary with different operators. The following descriptions take infoX AAA as an example. For details, see the infoX AAA Commissioning Guide. 1.

Upload the CA certificate of a terminal user to the iscc2/config/secert directory of infoX AAA.

2.

Change the file names of the user certificate and private key in the SCPCFG.INI file. Ensure that the file names are consistent with the file names of the user certificate and private key uploaded in step Step 4.1.

----End

4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000 When the security GW is deployed on the network, you need to save the required files in the specified directory of the USB storage device, and then import the files to the eNodeB by using the USB storage device.

Prerequisite

4-18

l

The USB storage device is ready.

l

The external template is available (containing the common configuration information).

l

The digital certificate required for importing the common configuration information to the eNodeB is saved in the USB storage device. For details on the digital certificate, see Table 4-7.


Issue 03 (2010-08-10)



Table 4-7 Required digital certificate Digital certificate

Description

The cross certificate granted by Huawei or the operator's root CA certificate

When the digital certificate is required for authentication, you must obtain the cross certificate or the operator's root CA certificate if the cross certificate cannot be downloaded from the CR/CRL server of the operator, or if the cross certificate can be downloaded but the CR/CRL server parameter or the path of the cross certificate on the CR/CRL server is not specified in the common configuration file. In other cases, the cross certificate and the operator's root CA certificate are not necessary.

Operator's CRL file

When the digital certificate is required for authentication, you must obtain the operator's CRL file if the CRL file cannot be downloaded from the CR/CRL server of the operator, or if the CRL file can be downloaded but the CR/CRL server parameter or the path of the CRL file on the CR/CRL server is not specified in the common configuration file. In other cases, the operator's CRL file is not necessary.

Context The common configuration files can be configured and exported through the external template (containing the common configuration information). Table 4-8 describes the configuration items. The external template can be downloaded from http://support.huawei.com/. The name of the common configuration file should be PreInfo.xml. The file name is case sensitive. Table 4-8 Configuration items of the common configuration information in the external template

Issue 03 (2010-08-10)

Item

Description

Configuration Scenario

Address Type of Public SeGW

The address of the public security GW such as the IP address or domain name can be configured. The IP address is recommended.


Public SeGW IP

The IP address of the public security GW is configured. If the Address Type of Public SeGW is set to IP address, this item must be configured.


URL of Public SeGW

The domain name of the public security GW is configured. If the Address Type of Public SeGW is set to Domain name, this item must be configured.


Local Name of Public SeGW

This item must be configured. It indicates the local ID of the public security GW. This item is consistent with the public security GW.



4-19



4-20

Item

Description


Address Type of DHCP Server on M2000

The address of the DHCP server, such as the IP address or domain name, provided by the M2000 can be configured. The IP address is recommended.


IP Address of DHCP Server on M2000

The IP address of the DHCP server provided by the M2000 is configured. If Address Type of DHCP Server on M2000 is set to IP address, this item must be configured.


URL of DHCP Server on M2000

The domain name of the DHCP server provided by the M2000 is configured. If Address Type of DHCP Server on M2000 is set to Domain name, this item must be configured.


IP Address of CR/CRL Server

The IP address of the CR/CRL server used to download the CRL and cross certificate is configured.

Digital certificate

User Name for CR/CRL Server Access

The user name used to access the CR/CRL server is configured.

Digital certificate

Password for CR/CRL Server Access

The password used to access the CR/CRL server is configured.

Digital certificate

Path of CRL File

The relative path and name of the operator's CRL file on the CR/CRL server is configured.

Digital certificate

Path of Cross-Certificate

The relative path and name of the cross certificate on the CR/CRL server is configured.

Digital certificate

VLAN ID for DHCP

The VLAN ID used during the DHCP establishment is configured. Whether to configure this item depends on the actual network.


Authentication Mode

The authentication mode such as the preshared key or digital certificate is configured.


Preshared Key

This item must be configured when the authentication mode is set to the preshared key. The pre-shared keys for the public security GW, serving security GW, and this item must be consistent.

Pre-shared key


Issue 03 (2010-08-10)



Item

Description


Path of Root Certificate on USB Disk

The save path of the root CA certificate in the USB storage device is eNodeB/ Certificates/CACert/. The file name can be customized and the save path is case sensitive.

Digital certificate

Path of Cross-Certificate on USB Disk

The save path of the cross certificate in the USB storage device is /eNodeB/ Certificates/CrossCACert/. The file name can be customized and the save path is case sensitive.

Digital certificate

Path of CRL File on USB Disk

The save path of the CRL file in the USB storage device is eNodeB/Certificates/ CRL/. The file name can be customized and the save path is case sensitive.

Digital certificate

Procedure Step 1 For details about how to configure the parameters on the USB Parameter for Sites tab page in the external template (containing the common configuration information), see the Help for USB Parameter page in the external template. Step 2 Click Export XML File on the USB Parameter for Sites page to export the PreInfor.xml file. Step 3 Save the required files in the specified paths of the USB storage device.The save path is case sensitive. File

Specified File Path in the USB Storage Device

Common configuration file

usb:\eNodeB\

Cross certificate granted by Huawei (optional)

usb:\eNodeB\Certificates\CrossCACert\

Operator's root CA certificate

usb:\eNodeB\Certificates\CACert\

Operator's CRL file

usb:\eNodeB\Certificates\CRL\

----End

4.2.7 Importing the Site Common Information Through the USB Storage Device When the security GW is deployed in the network, you can import the common configuration information to the eNodeB by using the USB storage device if the customized parameters cannot be configured through the public DHCP server. Issue 03 (2010-08-10)


4-21



Prerequisite The USB storage device is ready for use. The required files are saved in the USB storage device. For details, see 4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000.

CAUTION When you save the required files to the USB storage device, ensure that the locking switch on the USB storage device is disabled. In other words, the USB storage device should be writable.

Context When the LMPT of the BBU3900 is started, it automatically detects the USB storage device, reads the related software and configuration file in the USB storage device, and verifies the names and formats. The common configuration file, eNodeB software for local commissioning, and data configuration file can be saved in the same USB storage device. If the software package is saved in the USB storage device, the digital certificate must be contained. In this case, perform operations by referring to 5 Local eNodeB Commissioning Through the USB Storage Device. The file importing through the USB storage device fails if either of the following two cases occurs: l

The directory or the file does not exist.

l

Errors occur when the eNodeB reads or processes the files in the USB storage device.

Procedure Step 1 Insert the USB storage device into the USB port on the LMPT of the BBU3900, as shown in Figure 4-5. Figure 4-5 Inserting the USB storage device

4-22


Issue 03 (2010-08-10)



Step 2 Check whether the eNodeB is powered on. If ...

Then ...

The eNodeB is not powered on

Power on the eNodeB. The eNodeB automatically detects the USB storage device during startup.

The eNodeB is powered on

Power off the eNodeB and power it on again. The eNodeB automatically detects the USB storage device during startup.

Step 3 After the eNodeB startup is complete, it automatically processes the common configuration file and loads all the certificates and CRL files in the USB storage device. Check the running status of the indicator on the USB storage device. If ...

It Indicates That ...

The indicator on the USB storage device is blinking

The eNodeB is processing the common configuration file and loading all the certificates and CRL files in the USB storage device.

The indicator on the USB storage device is off

The common configuration information cannot be imported to the eNodeB. In this case, reinsert or replace the USB storage device, power off the eNodeB and power it on again, and then import the common configuration information to the eNodeB by using the USB storage device. If the fault persists, perform the local eNodeB commissioning on the LMT.

The indicator on the USB storage device is blinking for about one minute, and then is on steadily

The common information is successfully imported to the eNodeB.

WARNING During the file loading through the USB storage device, do not remove the USB storage device or reset the eNodeB. After the files are loaded to the eNodeB, the eNodeB is automatically connected to the M2000. Step 4 Confirm that the common information is successfully imported to the eNodeB, and then remove the USB storage device. ----End

Issue 03 (2010-08-10)


4-23



4.3 Creating the eNodeB Commissioning Task on the M2000 After the preparations for eNodeB commissioning are complete, create the eNodeB commissioning task on the M2000. This task will be automatically performed by the M2000. The M2000 supports automatic commissioning of multiple eNodeBs.

Prerequisite l

The M2000 server and client are connected and are running properly. You have logged in to the M2000 client.

l

If the eNodeB and M2000 server are not in the same network segment, the router or switch between the eNodeB and M2000 server must be configured as DHCP Relay. NOTE

l

If there is no security GW, you should set the IP address of the DHCP server of the M2000 on the DHCP Relay.

l

If there is a security GW, you should set the IP address of the public DHCP server on the DHCP Relay. In addition, set the IP address of the DHCP server of the M2000 on the security GW.

l

The eNodeB name, eNodeB ID, and ESN are collected.

l

The eNodeB is powered on.

l

The software and files required for eNodeB automatic deployment are ready. For details, see 4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment.

Context After the eNodeB is powered on, it sends the DHCP message to the M2000 requesting for the OM IP address. The DHCP message contains the eNodeB ESN and the GPS information of the eNodeB. If the eNodeB ID is not preset and a laptop is available on site, you can run the MOD ENODEB command to set the eNodeB ID on the LMT. If the eNodeB ID is successfully set, the DHCP message will contain the eNodeB ID. The EDS file, which is the self-configuration file, includes the eNodeB ID, electronic serial number (ESN), and GPS information about the eNodeB. This file is used to be bound to the eNodeB. The eNodeB ID is unique and is used to identify an eNodeB. In an EDS file, the eNodeB ID is mandatory and the GPS information and ESN are optional. The self-configuration data imported to the M2000 is bound with the ESN automatically in the following scenarios:

4-24

l

If the EDS file contains the ESN of the eNodeB, the ESN reported by the eNodeB and the imported self-configuration data on the M2000 are automatically bound in the case that the ESN reported by the eNodeB is consistent with the ESN in the EDS file.

l

If the M2000 receives the message containing the eNodeB ID, the imported selfconfiguration data and the ESN reported by the eNodeB are automatically bound after the mapping between the eNodeB ID reported by the eNodeB and the eNodeB ID in the EDS file.

l

If the M2000 receives the message containing the eNodeB location information, which is within the error of 100 m compared with the latitude and longitude predefined in the EDS file, the imported self-configuration data and the ESN reported by the eNodeB are Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-08-10)



automatically bound after the mapping between the GPS information reported by the eNodeB and the location information in the EDS file. If automatic binding fails, the information about the new eNodeB will be displayed in the Reported ESN tab page below the eNodeB Auto Deployment tab page. The user can obtain the ESN/eNodeB ID from the field engineer, and then binds the ESN/eNodeB ID and the imported self-configuration data.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed, as shown in Figure 4-6. Figure 4-6 eNodeB Auto Deployment tab page

Step 2 Upload the software and files required for eNodeB commissioning on the M2000. 1.

Click on the eNodeB Auto Deployment tab page. The Prepare File&Data dialog box is displayed.

2.

In the NE Software Version area, click Add. The Add dialog box is displayed. Specify the related parameters in the displayed dialog box, such as NE type, version type, and local file path.

3.

In the RET Software area, click the local PC.

4.

In the RET Data area, click uploaded in the local PC.

5.

In the RET Template area, click be uploaded in the local PC.

6.

In the Test License area, click uploaded in the local PC.

7.

In the Prepare File&Data dialog box, click OK to return to the eNodeB Auto Deployment tab page.

8.

View the file uploading progress on the Prepare File&Data tab page below the eNodeB Auto Deployment tab page.

Issue 03 (2010-08-10)

and select one or more RET files to be uploaded in and select one or more RET data configuration files to be and select the RET commissioning data template to and select the eNodeB commissioning license to be


4-25


9.


Click in the eNodeB Auto Deployment tab page. The Open dialog box is displayed. Select the OM IP data template to be uploaded in the local PC.

Step 3 Import the EDS file. 1.

on the upper left of the eNodeB Auto Deployment tab page. The Import dialog Click box is displayed, as shown in Figure 4-7. Figure 4-7 Import dialog box

4-26

2.

According to the save path of the EDS file, select Import File from Client or Import File from Server to import the EDS file to the M2000 server. The EDS file to be imported from the client is stored in the local computer. The EDS file to be imported from the server is stored at a specified directory of the server.

3.

Click Advanced. The Set Steps dialog box is displayed, as shown in Figure 4-8.


Issue 03 (2010-08-10)



Figure 4-8 Set Stepsdialog box

4.

Set the commissioning steps and then click OK. The Import dialog box is displayed. NOTE

If the eNodeB software and data configuration are already upgraded to the target version through the USB storage device on site, click Advanced when importing the EDS file on the M2000, and then clear the DownloadSoftware, DownloadData, and ActSoftware check boxes in the displayed Set Steps dialog box. In this case, these cleared steps are skipped in the automatic eNodeB commissioning.

5.

Click OK to import the EDS file. The basic configuration information about each new eNodeB is displayed in the eNodeB Auto Deployment tab page.

Step 4 Check whether the imported self-configuration data and the ESN reported by the eNodeB are automatically bound.

Issue 03 (2010-08-10)


4-27



If ...

Then ...

The ESN field on the eNodeB Auto Deployment tab page indicates the ESN of the new eNodeB

The imported self-configuration data and ESN are automatically bound. The eNodeB software and data configuration file are automatically downloaded from the M2000 server to the eNodeB. The eNodeB commissioning task is created.

The ESN field on the eNodeB Auto

The imported self-configuration data and ESN are not automatically bound. The eNodeB software and data configuration file cannot be automatically downloaded from the M2000 server to the eNodeB. Go to step Step 5.

Deployment tab page indicates

Step 5 According to the eNodeB ID and ESN reported by the field engineer, manually bind the ESN and the self-configuration data that is imported. 1.

In the eNodeB Auto Deployment tab page, select the corresponding eNodeB and click . The Bind ESN dialog box is displayed.

2.

Select the target ESN of the eNodeB, and then click OK. After the binding succeeds, the ESN information is displayed in the eNodeB Auto Deployment tab page. The eNodeB automatically downloads the software and data configuration file from the M2000 server.

Step 6 Repeat step Step 5 to manually bind all ESNs of the eNodeBs that are not automatically bound to the imported self-configuration data. ----End

4.4 Managing the eNodeB Commissioning Task After the eNodeB commissioning task is created, you can view the commissioning progress, pause and resume the commissioning task, and restart or delete the commissioning task. 4.4.1 Viewing the eNodeB Commissioning Progress After the eNodeB commissioning task is created, the user can view the task progress and related information to handle problems during the eNodeB commissioning. 4.4.2 Pausing/Retrying the eNodeB Commissioning Task During the automatic eNodeB commissioning on the M2000, the commissioning task can be paused and retried as required. 4.4.3 Restarting/Deleting the eNodeB Commissioning Task During the automatic eNodeB commissioning on the M2000, a commissioning task can be deleted and a terminated commissioning task can be restarted as required.

4.4.1 Viewing the eNodeB Commissioning Progress After the eNodeB commissioning task is created, the user can view the task progress and related information to handle problems during the eNodeB commissioning. 4-28


Issue 03 (2010-08-10)



Prerequisite The eNodeB commissioning task is created.

Context Table 4-9 describes the automatic eNodeB commissioning process. Table 4-9 Automatic eNodeB commissioning process eNodeB Commiss ioning Process

Description

Automatic deploymen t

After the eNodeB ESN and imported EDS file are bound together, the M2000 automatically allocates the IP address for the eNodeB. In this way, the OM channel can be established automatically between the M2000 and the eNodeB for remote commissioning and routine maintenance. After the M2000 discovers an eNodeB, the M2000 automatically sets the eNodeB to TESTING mode. Thus, all alarms generated during the eNodeB commissioning are not reported on the M2000.

Automatic configurati on

Automatic configuration includes the steps listed as follows. If you deselect a step when importing the EDS file, or if the file related to a step does not exist, the automatic eNodeB commissioning skips this step and proceeds. l

Downloading the eNodeB software

l

Downloading the data configuration file

l

Activating the eNodeB software and data configuration file

l

Supplementing the software automatically

l

Updating the license file

l

Commissioning the RET antenna

Testing and verificatio n

The M2000 automatically performs the eNodeB health check, which involves checking for active alarms.

eNodeB deploymen t complete

After the testing and verification is complete, the user decides whether to end the eNodeB commissioning based on the actual situations. When the eNodeB commissioning is complete, the M2000 restores the eNodeB to the normal state. Thus, the eNodeB alarms can be reported as usual.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed, as shown in Figure 4-9.

Issue 03 (2010-08-10)


4-29



Figure 4-9 eNodeB Auto Deployment tab page

Step 2 View Current Step and Current Step Progress of the commissioning task. Click the Step Execution tab page, and view Status, Progress, and Details of the steps of each phase. ----End

4.4.2 Pausing/Retrying the eNodeB Commissioning Task During the automatic eNodeB commissioning on the M2000, the commissioning task can be paused and retried as required.

Prerequisite The automatic eNodeB deployment is in progress or is paused.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed. Step 2 Right-click a commissioning task and choose Pause or Retry from the shortcut menu. NOTE

More than one commissioning task can be paused or retried at a time.

----End

Result l

When you choose Pause from the shortcut menu, the commissioning task stops after the current step is complete.

l

When you choose Retry from the shortcut menu, the commissioning task proceeds at the paused step.

4.4.3 Restarting/Deleting the eNodeB Commissioning Task During the automatic eNodeB commissioning on the M2000, a commissioning task can be deleted and a terminated commissioning task can be restarted as required. 4-30


Issue 03 (2010-08-10)



Prerequisite The eNodeB commissioning task is created.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed. Step 2 Right-click one or multiple commissioning tasks and choose Restart or Delete from the shortcut menu. ----End

4.5 Obtaining the eNodeB Commissioning Report on the M2000 The eNodeB commissioning report includes the operation details, results, and error information obtained during commissioning. It also includes the eNodeB health check report. The eNodeB commissioning report can be viewed during the commissioning task for handling problems in time, or be obtained after the commissioning task for report archiving.

Prerequisite The eNodeB commissioning task is in progress.

Context The exported commissioning report records the information about only the selected commissioning task. If a commissioning task is deleted manually, the corresponding commissioning report cannot be generated.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed. Step 2 Select one or more commissioning tasks. Step 3 Click

to view the automatic deployment report, which includes the health check report.

----End

4.6 Checking the Running Status of the eNodeB on the M2000 This chapter describes how to perform the health check and alarm check on the eNodeB through the M2000. 4.6.1 eNodeB Health Check Issue 03 (2010-08-10)


4-31



The eNodeB health can be decided on the basis of the health check report in the eNodeB commissioning report. 4.6.2 Handling the eNodeB Alarms After the eNodeB health check is complete, check for active alarms and clear them to ensure normal operation of the eNodeB.

4.6.1 eNodeB Health Check The eNodeB health can be decided on the basis of the health check report in the eNodeB commissioning report.

Prerequisite eNodeB health check is complete in the eNodeB commissioning task.

Context Table 4-10 describes the eNodeB health checklist. Table 4-10 eNodeB health checklist

4-32

Check Item

Check Sub-Item

Description

eNodeB software version check

eNodeB software version check

Check the active eNodeB software, including the version and running status.

Environment status check

RRU temperature check

Check the temperature of the RRU.

Environment temperature and humidity check

Check the temperature and humidity of the environment.

eNodeB type check

eNodeB type check

Check the eNodeB type in data configuration.

Data configuration check

Consistency check on the data configuration

Check the consistency between the effective data applied to modules and the configured data in the database.

Active alarm query

Check for active alarms of an NE.

Cell status check

Cell status check

Check the cell status.

MBTS alarm check

Inter-system communication alarm check

Check the status of inter-system communication.

Inter-system BBU board parameter settings conflict alarm check

Check the consistency of intersystem parameter settings for the BBU board.

Inter-system cabinet configuration conflict alarm check

Check the consistency of intersystem configurations for the cabinet.


Issue 03 (2010-08-10)



Check Item

Hardware status check

Interface status check

Issue 03 (2010-08-10)

Check Sub-Item

Description

Inter-system monitoring device parameter settings conflict alarm check

Check the consistency of intersystem parameter settings for the monitoring device.

Inter-system board object configuration conflict alarm check

Check the consistency of intersystem configurations for the board object.

Inter-system RF unit parameter settings conflict alarm check

Check the consistency of intersystem parameter settings for the RF unit.

Inter-system site-level configuration conflict alarm check

Check the consistency of intersystem configurations on site level.

Inter-system control rights conflict alarm check

Check the consistency of intersystem control rights.

RF unit working mode and board capability mismatch alarm check

Check the matching between the RF unit working mode and the board capability.

CPU usage check

Check the CPU usage.

Transmit channel check

Check the status of the transmit channel.

Receive channel check

Check the status of the receive channel.

RRU status check

Check the status of an RF unit.

Board status check

Check the status of a board.

X2-interface link check

Check the status of the current X2 interface and the information about the peer eNodeB.

S1-interface link check

Check the parameters of the current S1 interface and the information about the peer MME.

GE/FE port status check

Check the parameter settings of the Ethernet port.

E1/T1 port status check

Check the parameter settings of the E1/T1 port.

Remote maintenance channel status check

Check the data configuration on all the remote maintenance channels of the eNodeB.


4-33


Check Item

Clock status check


Check Sub-Item

Description

SCTP link status check

Check the parameter settings of the SCTP link.

IP Path status check

Check the parameter settings related to IP Path.

CPRI port status check

Check the parameter settings of the CPRI port.

Clock status check

Check the current clock of the main cabinet, including the current reference clock, clock quality, clock priority, clock working mode, and status of the phase-locked loop.

Procedure Step 1 Open the eNodeB commissioning report and view the health check report. Learn the running status of the eNodeB. Step 2 If the result of the eNodeB health check fails, check for active alarms and rectify the related faults by referring to the eNodeB Alarm Reference. If all active alarms are cleared but the health check still fails, contact Huawei for technical support. ----End

4.6.2 Handling the eNodeB Alarms After the eNodeB health check is complete, check for active alarms and clear them to ensure normal operation of the eNodeB.

Procedure Step 1 Check for active alarms. There are two methods of checking for active alarms, which are as follows: l

On the M2000 client, choose Monitor > Browse Alarm List. Specify the filtering conditions in the displayed Filter dialog box to list active alarms. For details, see Browsing the Alarm List in the M2000 Online Help.

l

On the M2000 client, choose Topology > Main Topology. In the Main Topology tab page, right-click the eNodeB and choose Query Alarm/Event > Alarm List from the shortcut menu. Double-click an active alarm.

Step 2 Handle the alarm according to the relevant handling suggestions or by referring to the eNodeB Alarm Reference. ----End

4-34


Issue 03 (2010-08-10)



4.7 Commissioning the TMA on the M2000 This section describes how to commission the Tower Mounted Amplifier (TMA). The main process of TMA commissioning is loading the TMA software. After the load is complete, the TMA is automatically reset. The software takes effect after the TMA is reset.

Prerequisite l

The TMA software is uploaded to the M2000 server. For details, see 4.2.3 Obtaining the eNodeB Software and Files for Automatic eNodeB Deployment.

l


l

The FTP user can access the specified directory.

l

You have enabled the FTP transmission port on the firewall between the eNodeB and the M2000 server.

l

The files from the FTP server are transferred in plain text by default.

l

The TMA is one part of the antenna system and is used to amplify the received weak signals.

l

The software of the TMA is supplied by the ALD vendor.

l

If the incorrect TMA software is loaded, the TMA may fail to operate normally.

Context

Procedure Step 1 Run the SCN ALD command to scan the ALD that is connected with the RRU. Step 2 Run the DSP TMASUBUNIT command to check whether the TMA is working. If the TMA is not working, contact Huawei for technical support. Step 3 Run the DSP ALDVER command to query the software version of the TMA to be commissioned. NOTE

You can also check the version information about all ALDs if you run this command without specifying any parameter.

If ...

Then ...

The active software version is the target software version

End this task.

The active software version is not the target software version

Go to step 4.

Step 4 Run the DLD ALDSW command to download the software of the TMA to be commissioned. Step 5 If the eNodeB is configured with multiple TMAs, repeat step 3 and step 4 to download the software of other TMAs. ----End Issue 03 (2010-08-10)


4-35



4.8 Commissioning the Antenna System on the M2000 Commissioning the antenna system helps to check for problems in the installed antenna system.

Prerequisite l

The antenna system of the eNodeB is installed.

l


Procedure Step 1 Run the LST RRU command to query the Voltage Standing Wave Ratio (VSWR) alarm threshold. Step 2 Run the STR VSWRTEST command to start the VSWR test. If ...

Then ...

The test value is smaller than the VSWR alarm threshold

The antenna system is properly installed. End the commissioning.

The test value is equal to or greater than the VSWR alarm threshold

The antenna system is not properly installed. Rectify the faults by referring to the handling procedures for the VSWR alarm in the eNodeB Alarm Reference.

NOTE

The offline VSWR test may interrupt the services of both working modes.

----End

4.9 Commissioning the Environment Monitoring Equipment on the M2000 This section describes how to check the environment monitoring equipment on the M2000. After the environment monitoring equipment is connected, you need to commission it so that it functions properly. 4.9.1 Setting the Environment Alarm Parameters This section describes how to set the parameters related to the environment alarms. You can set alarm parameters within the permissible range according to the actual situation. 4.9.2 Checking for the External Environment Alarms This section describes how to check for the external environment alarms. After the parameters of the environment alarms are set, you need to verify the parameter configuration by checking for the external environment alarms.

4-36


Issue 03 (2010-08-10)



4.9.1 Setting the Environment Alarm Parameters This section describes how to set the parameters related to the environment alarms. You can set alarm parameters within the permissible range according to the actual situation.

Prerequisite l

The M2000 communicates properly with the eNodeB.

l

The environment monitoring device is configured.

l

The DIP switches of the environment monitoring device are properly set. For details, see the APM30H&TMC11H&IBBS200D&IBBS200T(ver.B) User Guide and the EMUA User Guide.

Context The RRU, UPEU of BBU, EMUA, and PMU of the APM30H are all configured with extended alarm ports.

Procedure Step 1 Export an NE-type user-defined alarm binding template. 1.

On the M2000, choose Monitor > Alarm Setting > NE Alarm Setting.

2.

Click the User-Defined Alarm tab and then the Alarm Binding tab.

3.

Click Export Template. Alternatively, click Export to export the existing records on the Alarm Binding tag page by NE type.

4.

In the displayed Export Alarm Binding Template dialog box, set the NE type, and then specify the saving path and name of the exported template file.

5.

Click OK.

Step 2 Edit the user-defined alarm binding template. Edit the template according to the example in the template and actual requirements. NOTE

The alarms are normalized and the alarm ID ranges from 65033 to 65233.

Step 3 Import the user-defined alarm binding template. 1.

Click Import on the Alarm Binding tab page under the User-Defined Alarm tab page.

2.

In the displayed Import Alarm Binding Data dialog box, set the NE type, and then navigate to the template to be imported.

3.

Click OK. The user-defined alarm binding relationship in the template is displayed on the Alarm Binding tab page. Each record is prefixed with the

4.

Issue 03 (2010-08-10)

icon.

Click a record of alarm binding relationship, and then click Apply to apply the selected alarm binding relationship to the NE. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

4-37



The system displays a message, indicating whether the operation is successful. If the operation is successful, the icon disappears. If the operation fails, check the parameter settings and then import the user-defined alarm binding template again. Step 4 Add a user-defined alarm. 1.

Click the Alarm Definition tab and then click Add. In the displayed dialog box, set the parameters including NE type, alarm name, alarm ID, and alarm level.

2.

Click OK. The user-defined alarms to be added are listed on the Alarm Definition tab page. Each user-defined alarm is prefixed with the defined alarm is not applied to the M2000.

3.

icon. The

icon indicates that the user-

Click Apply to apply the user-defined alarm to the M2000. Thus, the information about the user-defined alarm is stored in the M2000 database. The system displays a message, indicating whether the operation is successful. If the icon disappears. If the operation fails, check the parameter operation is successful, the settings and then click Apply again.

----End

4.9.2 Checking for the External Environment Alarms This section describes how to check for the external environment alarms. After the parameters of the environment alarms are set, you need to verify the parameter configuration by checking for the external environment alarms.

Context Manually trigger an external environment alarm. If the alarm can be reported normally, the configuration of the external environment alarm is correct.

Procedure Step 1 Simulate the environment for generating an external environment alarm. Step 2 Check for the alarm on the M2000 client. For details, see 4.6.2 Handling the eNodeB Alarms. If the external environment alarm can be reported normally, it indicates that the related configuration is correct. If the external environment alarm cannot be reported normally, set the parameters again or contact Huawei for technical support. ----End

Example Assume that the APM30H is the environment monitoring device of the site. Check for the Mains Input Out of Range alarm.

4-38

1.

Cut off the AC power supply to the eNodeB, so that the AC voltage drops below the AC voltage lower threshold.

2.

Check for the Mains Input Out of Range alarm on the M2000 client. If the alarm exists, the related configuration is correct. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-08-10)



4.10 Setting the Maximum TX Power of RRU or RFU Set the maximum TX power of the RRU or RFU on site, according to the local regulations on power specifications.

Prerequisite l

The RRU or RFU is connected properly.

l

A laptop is ready.

Context The maximum TX power of the RRU or RFU is specified by the local operator.

CAUTION The maximum TX power of the RRU or RFU is set through the LMT on site.

Procedure Step 1 Run the DSP RRU command to query the cabinet/subrack/slot No. and TX channel No. of the RRU or RFU. Step 2 Run the LOC RRUTC command to set the maximum TX power of the RRU or RFU. NOTE

The LOC RRUTC command is used to set the maximum TX power of one RRU or RFU at a time.

Step 3 Run the RST BRD command to reset the RRU or RFU. NOTE

The RST BRD command is used to reset one RRU or RFU at a time.

Step 4 Run the DSP TXBRANCH command to check that the maximum TX power of each RRU or RFU is set successfully. If ...

Then ...

The maximum TX power of each RRU or RFU is set successfully

End this task.

The maximum TX power of each RRU or RFU is not set successfully

Check whether the maximum TX power exceeds the power specifications supported by the RRU or RFU. Set the maximum TX power again. If the setting of the maximum TX power still fails, contact Huawei for technical support.

----End Issue 03 (2010-08-10)


4-39



4.11 Testing the Basic Services of the eNodeB This section describes how to test the basic services of the eNodeB.

Prerequisite l

The eNodeB and the MME/S-GW are properly connected.

l

The negotiation data of the eNodeB to be commissioned is added to the MME/S-GW.

l

The testing UE is functional and is registered in the HSS.

l

The FTP server for testing the basic services is available.

l

The WWW server for testing the basic services is available.

l

Test the web page browsing service.

Procedure

l

l

l

Testing Method

Access the WWW server and browse the web pages through a UE. Perform the test 20 times.

Expectation

Success rate > 95%. Web browsing is normal.

Test the file uploading service. Testing Method

Access the FTP server and upload files through a UE. Perform the test 10 times.

Expectation

Success rate > 90%. The upload rate is stable.

Test the file downloading service. Testing Method

Access the FTP server and download files through a UE. Perform the test 10 times.

Expectation

Success rate >90%. The download rate is stable.

Test the VoIP services. Testing Method

Use the testing UE to call another UE 20 times.

Expectation

Connection success rate > 95%. The calls are uninterrupted and none of the calls get dropped till they are released. The voice is clear with no loud noise.

----End

4-40


Issue 03 (2010-08-10)



4.12 Acknowledging the eNodeB Commissioning on the M2000 After the eNodeB health check is complete, the status of the commissioning task changes to Awaiting_ack. In this case, you need to acknowledge the eNodeB commissioning.

Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tab page is displayed. Step 2 Right-click the target commissioning task and choose Acknowledge from the shortcut menu. The commissioning task is acknowledged. ----End

Issue 03 (2010-08-10)


4-41


5


Local eNodeB Commissioning Through the USB Storage Device

About This Chapter In the local eNodeB commissioning through the USB storage device, you can upgrade the eNodeB software and data configuration file by using the USB storage device, and check the running status of the eNodeB by the LEDs. Then, create the eNodeB commissioning task on the M2000 server. 5.1 Local eNodeB Commissioning Through the USB Storage Device This section describes the procedure of local eNodeB commissioning through the USB storage device. 5.2 Preparations for the Local eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to collect the related eNodeB information, arrange for commissioning tools and digital certificates, and save the required files to the USB storage device. 5.3 Downloading and Activating the Software and Data Configuration File Through the USB Storage Device This section describes how to download and activate the eNodeB software and data configuration file through the USB storage device. The eNodeB automatically downloads the software and data configuration file from the USB storage device, and then activates them. The software and data configuration take effect after the eNodeB resets. 5.4 Checking the Status of LEDs This describes how to check the status of LEDs to determine whether the eNodeB runs properly.

Issue 03 (2010-08-10)


5-1



5.1 Local eNodeB Commissioning Through the USB Storage Device This section describes the procedure of local eNodeB commissioning through the USB storage device. Figure 5-1 shows the procedure of local eNodeB commissioning through the USB storage device.

5-2


Issue 03 (2010-08-10)



Figure 5-1 Procedure of local eNodeB commissioning through the USB storage device

Issue 03 (2010-08-10)


5-3



Table 5-1 eNodeB commissioning procedure through the USB storage device Step

Operation

Manda tory/ Option al

1


Make preparations for the local eNodeB commissioning, which involves obtaining the eNodeB information and commissioning tools, configuring the security equipment, and obtaining associated files and digital certificates. For details, see 5.2 Preparations for the Local eNodeB Commissioning Through the USB Storage Device.

Mandat ory

2

Local operations

Download and activate the eNodeB software and data configuration through the USB storage device. For details, see 5.3 Downloading and Activating the Software and Data Configuration File Through the USB Storage Device.

Mandat ory

Learn the running status of the eNodeB by viewing the eNodeB LEDs on site. For details, see 5.4 Checking the Status of LEDs.

Mandat ory

After the eNodeB is connected to the M2000, create the eNodeB commissioning task on the M2000. For details, see 4.3 Creating the eNodeB Commissioning Task on the M2000.

Mandat ory

3

4


NOTE If the eNodeB software and data configuration are already upgraded to the target version through the USB storage device on site, you need to click Advanced when importing the EDS file on the M2000, and then clear the DownloadSoftware, DownloadData, and ActSoftware check boxes in the displayed Set Steps dialog box. In this case, these cleared steps are skipped in the automatic eNodeB commissioning.

5-4

5

Manage the eNodeB commissioning task on the M2000. For details, see 4.4 Managing the eNodeB Commissioning Task.

Mandat ory

6

Obtain the eNodeB commissioning report. For details, see 4.5 Obtaining the eNodeB Commissioning Report on the M2000.

Mandat ory

7

Learn the running status of the eNodeB by viewing the eNodeB commissioning report. For details, see 4.6 Checking the Running Status of the eNodeB on the M2000.

Mandat ory

8

Commission the TMA on the M2000. For details, see 4.7 Commissioning the TMA on the M2000.

Optiona l

9

Commission the antenna system on the M2000. For details, see 4.8 Commissioning the Antenna System on the M2000.

Optiona l


Issue 03 (2010-08-10)



Step

10

Operation

After the environment monitoring equipment is connected, perform the commissioning and enable the environment monitoring equipment to function properly. For details, see 4.9 Commissioning the Environment Monitoring Equipment on the M2000.

Optiona l

11


Optiona l

12


Mandat ory

After the eNodeB commissioning is complete, confirm the eNodeB commissioning task. For details, see 4.12 Acknowledging the eNodeB Commissioning on the M2000.

Mandat ory

13




5.2 Preparations for the Local eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to collect the related eNodeB information, arrange for commissioning tools and digital certificates, and save the required files to the USB storage device. 5.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to arrange for the related eNodeB information and tools. 5.2.2 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server. 5.2.3 Obtaining the Digital Certificate Required for the eNodeB Commissioning Through the USB Storage Device When the security GW is deployed in the network, the eNodeB and the security GW need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate on the eNodeB side incorporates the operator's cross certificate signed by Huawei, operator's root certification authority (CA) certificate (or CA certificate chain with the root CA certificate), and operator's certificate revocation list (CRL). The digital certificate on the security GW side incorporates Huawei root CA certificate and Huawei CRL file.

Issue 03 (2010-08-10)


5-5



5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to save the required files in a specified directory in the USB storage device.

5.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to arrange for the related eNodeB information and tools.


Source or Remarks

eNodeB name


eNodeB ID


eNodeB ESN



Step 2 Arrange for the tools required for the local commissioning through the USB storage device, as described in Table 5-3.

5-6


Issue 03 (2010-08-10)



Table 5-3 Tools required for the local commissioning through the USB storage device Tool

Description

USB storage device

l

The USB storage device is equipped with an indicator that indicates the data transmission status.

l

Capacity ≥ 256 MB

l

Recommended models: Netac U208, Netac U180, Netac U215, and Netac U210.

l

The USB storage device has no additional function. The additional functions include but are not limited to encryption, antivirus, bootstrap, MP3, MP4, and smart mobile phone.

l

The files required for the commissioning are stored in the USB storage device. The files are described in 5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device.


Testing UE

----End

5.2.2 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server.

Prerequisite l


l


l


l


Context

Table 5-4 Security GW configuration

Issue 03 (2010-08-10)

Item

Description

IP address



5-7


5-8


Item

Description

Route

l


l


ike local name


ike proposal

l


l


l


l


acl

It is recommended that permit ip be configured.

ike peer

l


l


ipsec proposal




ipsec policy





Issue 03 (2010-08-10)



l


l


Procedure Step 1 Check the configuration of the security GW according to Table 5-4. Step 2 Configure the authentication access equipment. The authentication access equipment may vary with different operators. The example here describes a typical configuration of an authentication access equipment. Take the Quidway S6500 series Ethernet switch as an example. Run the dot1x command to enable the global 802.1x feature. Run the dot1x [ interface interfacelist ] command to enable the 802.1x feature on a specified port. Run the dot1x authenticationmethod { chap | pap | eap } command to set the EAP authentication method. For details, see the Quidway S6500 Series Ethernet Switches Operation Manual. Step 3 Configure the eNodeB CA certificate for the AAA server. The AAA server may vary with different operators. The descriptions here take the infoX AAA as an example. For details, see the infoX AAA Commissioning Guide. 1.


2.


----End

5.2.3 Obtaining the Digital Certificate Required for the eNodeB Commissioning Through the USB Storage Device When the security GW is deployed in the network, the eNodeB and the security GW need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate on the eNodeB side incorporates the operator's cross certificate signed by Huawei, operator's root certification authority (CA) certificate (or CA certificate chain with the root CA certificate), and operator's certificate revocation list (CRL). The digital certificate on the security GW side incorporates Huawei root CA certificate and Huawei CRL file.

Prerequisite l

The operator already obtains the cross certificate signed by Huawei if cross certification is used. NOTE

Before Huawei signs the cross certificate for the operator, the operator is required to provide the request file of cross certificate for Huawei. The request file of cross certificate is in format of PKCS#10, which is generated by the operator's root CA certificate, or the operator's child CA certificate that is used for the certification of eNodeB, security GW, and M2000.

Issue 03 (2010-08-10)


5-9

5 Local eNodeB Commissioning Through the USB Storage Device l



Context NOTE


Procedure Step 1 Obtain the digital certificate required by the eNodeB. That is, save the operator's cross certificate, operator's root CA certificate, and operator's CRL file(optional) to the USB storage device. NOTE



5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device Before the local eNodeB commissioning through the USB storage device, you need to save the required files in a specified directory in the USB storage device.

Prerequisite l


l

The eNodeB software package and data configuration file are available.

l

When the security GW is deployed on the network, the common configuration file and digital certificate to be imported to the eNodeB are saved in the USB storage device. For details, see 4.2.6 Arranging for the Files in the USB Storage Device Required for the eNodeB Commissioning on the M2000.

Context The eNodeB software package is ready, and can be downloaded from http:// support.huawei.com/. The name of the data configuration file should be CFGDATA.XML. The file name is case sensitive. Complete the configuration by referring to the eNodeB Initial Configuration Guide. Then, save the data configuration file in the local computer. The name of the common configuration file should be PreInfo.xml. The file name is case sensitive. 5-10


Issue 03 (2010-08-10)



Procedure l

l

When the security GW is not deployed on the network, save the files required for local commissioning in the following specified paths in the USB storage device. The save path is case sensitive. File



usb:\eNodeB\Software\

Data configuration file

usb:\eNodeB\

When the security GW is deployed on the network, save the files required for local commissioning in the following specified paths in the USB storage device. The save path is case sensitive. File


Common configuration file

usb:\eNodeB\

Cross certificate granted by Huawei

usb:\eNodeB\Certificates\CrossCACert\

Operator's root CA certificate

usb:\eNodeB\Certificates\CACert\

Operator's CRL file

usb:\eNodeB\Certificates\CRL\


usb:\eNodeB\Software\

Data configuration file

usb:\eNodeB\

----End

5.3 Downloading and Activating the Software and Data Configuration File Through the USB Storage Device This section describes how to download and activate the eNodeB software and data configuration file through the USB storage device. The eNodeB automatically downloads the software and data configuration file from the USB storage device, and then activates them. The software and data configuration take effect after the eNodeB resets.

Prerequisite The USB storage device is ready for use. The required files are saved in the USB storage device. For details, see 5.2.4 Obtaining the Files Required for the eNodeB Commissioning Through the USB Storage Device.

Issue 03 (2010-08-10)


5-11



CAUTION If one USB storage device is used repeatedly, the target eNodeB software and data configuration file in the USB storage device should be updated before the USB storage device is used for an eNodeB deployment. When you save the eNodeB software and data configuration file to the USB storage device, ensure that the locking switch on the USB storage device is disabled. In other words, the USB storage device should be writable.

Context When the LMPT of the BBU3900 is started, it automatically detects the USB storage device, reads the related software and data configuration file in the USB storage device, and verifies the file names and formats. If you install the BBU before installing the RRU, you can install and power on the RRU during the process of BBU software downloading. After the BBU software is downloaded/activated successfully and the RRU is powered on, you can reset the LMPT to start the automatic upgrade of the RRU software. You should pay attention to the following points when you download and activate the software and the configuration file through the USB storage device:

5-12

l

If the USB storage device contains the common configuration file of the site, digital certificate and eNodeB software, the eNodeB parses the common configuration file, loads the digital certificate, and then downloads and activates the eNodeB software and data configuration. If the eNodeB cannot parse the common configuration file, it does not proceed with the subsequent process.

l

If the USB storage device contains only the eNodeB software and data configuration, the eNodeB downloads and activates the eNodeB software, and then downloads and activates the data configuration.

l

If the eNodeB software or data configuration file is missing in the USB storage device, the eNodeB performs the following steps: –

If the eNodeB software is missing in the USB storage device, the eNodeB commissioning through the USB storage device is not performed.

–

If the data configuration file is missing in the USB storage device, the eNodeB upgrades to the minimum configuration of the target version and skips the download and activation of data configuration.

l

If the eNodeB software upgrade fails, the eNodeB rolls back to the pre-upgrade version.

l

Before downloading and activating data configuration, the eNodeB does not check the compatibility between the data configuration file and the eNodeB software version. The eNodeB performs the following activities: –

If the eNodeB software is upgraded successfully but is not compatible with the data configuration file, or if the download and activation of data configuration fail, the eNodeB uses the minimum configuration of the target version.

–

When the active eNodeB software is consistent with the target software version, software upgrade is not performed. After the eNodeB resets, if the active eNodeB software is not compatible with the data configuration file or if the download and Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-08-10)



activation of data configuration fail, the eNodeB uses the data configuration of the earlier version. l

If any of the following situations occurs, the eNodeB would not download or activate the eNodeB software or data configuration file from the USB storage device. –

The directory or the file does not exist.

–

The eNodeB software is missing in the USB storage device, and therefore the software and data cannot be downloaded or activated.

–

The target software version is consistent with the active eNodeB software, and therefore the eNodeB software is not downloaded or activated. The download and activation of data configuration is still normal.

–

The data configuration file is consistent with the active data configuration, and therefore data configuration is not downloaded. The download and activation of the software is still normal.

Procedure Step 1 Insert the USB storage device into the USB port on the LMPT of the BBU3900, as shown in Figure 5-3. Figure 5-3 Inserting the USB storage device

Step 2 Check whether the eNodeB is powered on. If ...

Then ...

The eNodeB is not powered on

Power on the eNodeB. The eNodeB automatically detects the USB storage device during startup.

The eNodeB is powered on

Power off the eNodeB and power it on again. The eNodeB automatically detects the USB storage device during startup.

Step 3 After the eNodeB is started, it automatically upgrades the eNodeB software and data configuration. Issue 03 (2010-08-10)


5-13


1.


The RUN LED on the LMPT blinks (on for 0.125s and off for 0.125s) during the upgrade of software and data configuration. In this situation, observe the status of the LED on the USB storage device. If ...

Then ...

The LED on the USB storage device is on or blinking

It indicates that the software and data configuration are being downloaded or activated. In this case, go to step Step 3.2.

The LED on the USB storage device is off

It indicates that the download or activation fails. In this case, reinsert or replace the USB storage device, power off the eNodeB and power it on again, and then perform the commissioning through the USB storage device. If the download or activation still fails, perform the local eNodeB commissioning on the LMT.

WARNING Do not remove the USB storage device or reset the eNodeB during the download or activation of eNodeB software and data configuration through the USB storage device. After the files are downloaded, the eNodeB automatically activates the software and data configuration. Then, the eNodeB resets. 2.

After about 25 minutes when the eNodeB operates properly, the RUN LED on the LMPT blinks (on for 1s and off for 1s). In this situation, observe the status of the LED on the USB storage device. If ...

Then ...

The LED on the USB storage device is on or blinking

It indicates that the download and activation are successful. Go to step Step 4.

The LED on the USB storage device is off

It indicates that the download or activation fails. In this case, reinsert or replace the USB storage device, power off the eNodeB and power it on again, and then perform the commissioning through the USB storage device. If the download or activation still fails, perform the local eNodeB commissioning on the LMT.

Step 4 When the download and activation are successful, unplug the USB storage device, and proceed with 5.4 Checking the Status of LEDs. ----End 5-14


Issue 03 (2010-08-10)



Postrequisite

CAUTION The eNodeB software package contains the LMT software. To reduce the eNodeB deployment duration, some of the files of the LMT software are automatically downloaded to the eNodeB four hours after the eNodeB deployment. If you need to use the LMT immediately after the eNodeB deployment, run the SPL SOFTWARE command on the M2000 after the eNodeB is connected to the M2000. Set Delay Download File Supply Flag to YES(Supply File that Support Delay). Thus, the remaining files of LMT software are downloaded to the eNodeB.

5.4 Checking the Status of LEDs This describes how to check the status of LEDs to determine whether the eNodeB runs properly.

Context LED status of functional eNodeB If the status of the LEDs on the boards and auxiliary devices are the same as that shown in Table 5-5, the eNodeB runs properly. Table 5-5 LED status of the functional eNodeB LED

Status

RUN LED on each board in the BBU

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

Statuses of the ALM LEDs on the LMPT, LBBP, UTRP, PMU, AFMU, and EMUA

OFF

STATE LED on the FAN of the BBU3900

Blinking (green, ON for 1s and OFF for 1s)

CPRI LED on the LBBP

ON (green)

VSWR LED on the RRU or LRFU

OFF

LED status of the common faults Figure 5-4 shows the LED status of the common faults.

Issue 03 (2010-08-10)


5-15



Figure 5-4 LED status of the common faults

Procedure Step 1 Check the LED on each board in the BBU. 1.

2.

5-16

Check the RUN LED on each board in the BBU. If the RUN LED Is...

You can Infer That...

Then...

Blinking at 0.5 Hz (ON for 1s and OFF for 1s)

The board works properly.

Go to Step 1.2.

ON

The board is starting.

Wait until the board startup is complete.

Blinking at 4 Hz (ON for 0.125s and OFF for 0.125s)

The software is being loaded or the board is inserted in the wrong slot.

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

OFF

The power supply is unavailable, or the board is faulty.

l

Check whether the eNodeB is powered on. If not, power on the eNodeB.

l

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

If the RUN LED still blinks at 4 Hz, check whether the board is inserted in the correct slot. If not, reinstall the board.

Check the ALM LEDs on the LMPT, LBBP, and UTRP.


Issue 03 (2010-08-10)


3.

4.

Issue 03 (2010-08-10)


If the ALM LED Is ...


Then ...

OFF

The LBBP, LMPT, or UTRP is functioning properly.

Go to Step 1.3.

ON

The LMPT, LBBP, or UTRP is faulty.


Blinking

An alarm is reported but the board may not need to be changed. Check whether this alarm is due to faults caused by the associated boards or ports.

l

Check whether the RUN LEDs on the other boards blink quickly. –

If the RUN LED on the EMUA blinks quickly, check the RS485 signal cable connection.

–

Check the RUN LED on the LMPT or the LBBP.

l

Check the connection between the dry contact alarm signal cable and the corresponding port on the UPEU.

l

Reinstall the LBBP or LMPT to check whether the fault is rectified.

l

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

Check the STATE LED on the FAN. If the STATE LED Is ...


Then ...

Blinking (green)

The board works properly.

Go to Step 1.4.

Blinking (red)

The board is faulty.


Check the CPRI LED on the LBBP. If the CPRI LED Is ...


Then ...

ON (green)

The CPRI link is normal. The RRU or LRFU is functioning properly.

Go to Step 2.


5-17



If the CPRI LED Is ...


Then ...

OFF

The port of the optical module is not configured, the optical module is powered off, or the LED is faulty.

If the RRU or LRFU is connected to this port, check the installation of BBU and RRU according to configuration requirements. l

If the installation is inconsistent with configuration requirements, reinstall the RRU according to configuration requirements.

l

If the installation is consistent with configuration requirements, replace the boards.

ON (red)

The port of optical module is configured, but the optical module is not in position, or the CPRI optical cable is improperly connected.

Handle the alarm according to the suggestions. For details, see eNodeB Alarm Reference.

Blinking at 0.5 Hz (red, ON for 1s and OFF for 1s)

The RRU or LRFU on the CPRI link reports the VSWR alarm.

Handle the alarm according to related suggestions. For details, see eNodeB Alarm Reference.

Blinking at 2 Hz (red, ON for 0.25s and OFF for 0.25s)

The RRU or LRFU on the CPRI link is faulty.

Handle the alarm according to related suggestions. For details, see eNodeB Alarm Reference.

Step 2 Check the ALM LED on the PMU, AFMU, or EMUA.

5-18

If the ALM Indicator Is ...


Then ...

OFF

The module or the device is functioning properly.

The check is complete.


Issue 03 (2010-08-10)



If the ALM Indicator Is ...


Then ...

ON

The module or the device is faulty.

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

----End

Issue 03 (2010-08-10)


5-19


6


Local eNodeB Commissioning on the LMT

About This Chapter In the local eNodeB commissioning on the LMT, you can upgrade the eNodeB software, download the configuration file, perform the ALD commissioning, and check the running status of the eNodeB on the LMT. Then, establish the OM channel between the eNodeB and the M2000 through the M2000 server. 6.1 Local eNodeB Commissioning on the LMT This section describes the procedure of local eNodeB commissioning on the LMT. 6.2 Preparations for the Local eNodeB Commissioning on the LMT Before the local eNodeB commissioning on the LMT, you need to arrange for related information and tools required for eNodeB commissioning, and configure the FTP server. When the security GW is deployed in the network, the digital certificate is required if there is no configuration file and the digital certificate needs to be added to the eNodeB through the LMT. 6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT This section describes how to download and activate the eNodeB software and data configuration file on the LMT. The eNodeB software and data configuration file take effect after the eNodeB is automatically reset. The process for upgrading the eNodeB software and data configuration file takes about 45 minutes. 6.4 Downloading the License for eNodeB Commissioning on the LMT After downloading the commissioning license to the eNodeB on the LMT, you are authorized to use the eNodeB software. 6.5 Commissioning the ALD on the LMT This section describes how to commission the Antenna Line Device (ALD). The task consists of Remote Electrical Tilting (RET) antenna commissioning and Tower Mounted Amplifier (TMA) commissioning. 6.6 Commissioning the Antenna System on the LMT Commissioning the antenna system helps to check for problems in the installed antenna system. 6.7 Commissioning the Environment Monitoring Equipment on the LMT This section describes how to check the environment monitoring equipment on the M2000. After the environment monitoring equipment is connected, you need to commission it so that it functions properly. Issue 03 (2010-08-10)


6-1



6.8 Setting the Maximum TX Power of RRU or RFU Set the maximum TX power of the RRU or RFU on site, according to the local regulations on power specifications. 6.9 Handling the eNodeB Alarms on the LMT This section describes how to handle the alarms generated during the commissioning. 6.10 Querying the Running Status of the eNodeB on the LMT This section describes how to check the running status of the eNodeB on the LMT. 6.11 Testing the Basic Services of the eNodeB This section describes how to test the basic services of the eNodeB. 6.12 Establishing the OM Channel Between the M2000 and the eNodeB This section describes how to establish the OM channel between the M2000 and the eNodeB through the M2000 client. 6.13 Setting the eNodeB Status After the eNodeB commissioning is complete and the eNodeB starts to provide services properly, set the eNodeB to the normal state on the M2000.

6-2


Issue 03 (2010-08-10)



6.1 Local eNodeB Commissioning on the LMT This section describes the procedure of local eNodeB commissioning on the LMT. Figure 6-1 shows the procedure of local eNodeB commissioning on the LMT.

Issue 03 (2010-08-10)


6-3



Figure 6-1 Procedure of local eNodeB commissioning on the LMT

6-4


Issue 03 (2010-08-10)



Table 6-1 eNodeB commissioning procedure on the LMT Step


1


Make preparations for the local eNodeB commissioning, which involves obtaining the eNodeB information and commissioning tools, configuring the security equipment, and obtaining associated files and digital certificates. For details, see 6.2 Preparations for the Local eNodeB Commissioning on the LMT.

Mandat ory

2

Local operations on the LMT

Download and activate the eNodeB software and data configuration file on the LMT. For details, see 6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT.

Mandat ory

3

Download the license file for eNodeB commissioning on the LMT. For details, see 6.4 Downloading the License for eNodeB Commissioning on the LMT.

Optiona l

4

Commission the Antenna Line Device (ALD) on the LMT. For details, see 6.5 Commissioning the ALD on the LMT.

Optiona l

5

Commission the antenna system on the LMT. For details, see 6.6 Commissioning the Antenna System on the LMT.

Optiona l

6

After the environment monitoring equipment is connected, perform the commissioning and enable the environment monitoring equipment to function properly. For details, see 6.7 Commissioning the Environment Monitoring Equipment on the LMT.

Optiona l

7


Optiona l

8

Handle the eNodeB alarms on the LMT. For details, see 6.9 Handling the eNodeB Alarms on the LMT.

Mandat ory

9

Learn the running status of the eNodeB on the LMT. For details, see 6.10 Querying the Running Status of the eNodeB on the LMT.

Mandat ory

10


Mandat ory

After the eNodeB is connected to the M2000, establish the OM link for the eNodeB on the M2000. For details, see 6.12 Establishing the OM Channel Between the M2000 and the eNodeB.

Mandat ory

11

Issue 03 (2010-08-10)

Operation



6-5



Step

12

Operation


After the eNodeB commissioning is complete and the eNodeB starts to provide services properly, set the eNodeB to the normal state on the M2000. For details, see 6.13 Setting the eNodeB Status.

Mandat ory

6.2 Preparations for the Local eNodeB Commissioning on the LMT Before the local eNodeB commissioning on the LMT, you need to arrange for related information and tools required for eNodeB commissioning, and configure the FTP server. When the security GW is deployed in the network, the digital certificate is required if there is no configuration file and the digital certificate needs to be added to the eNodeB through the LMT. 6.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the LMT Before the local eNodeB commissioning on the LMT, you need to arrange for the related eNodeB information and tools. 6.2.2 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the LMT When the security GW is deployed on the network, the eNodeB and the interconnected device (such as the security GW) need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate on the eNodeB side incorporates the operator's cross certificate granted by Huawei, operator's root certification authority (CA) certificate (or CA certificate chain with the root CA certificate), and operator's certificate revocation list (CRL). The digital certificate on the security GW side incorporates Huawei root CA certificate and Huawei CRL file. 6.2.3 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server. 6.2.4 Configuring the FTP Server This section describes the preparations for the local commissioning on the LMT. Before performing local commissioning on the LMT, you must log in to the eNodeB on the LMT, and configure the FTP server. 6.2.5 Downloading the Digital Certificate on the LMT When the security GW is deployed in the network, the digital certificate needs to be added to the eNodeB on the LMT if there is no data configuration file.

6-6


Issue 03 (2010-08-10)



6.2.1 Arranging for Related Information and Tools Required for the eNodeB Commissioning on the LMT Before the local eNodeB commissioning on the LMT, you need to arrange for the related eNodeB information and tools.


Source or Remarks

eNodeB name


eNodeB ID


eNodeB ESN



Step 2 Arrange for the tools required for the local commissioning on the LMT, as described in Table 6-3.

Issue 03 (2010-08-10)


6-7



Table 6-3 Tools required for the local eNodeB commissioning on the LMT Tool

Description

Laptop

l

The hardware configuration, software configuration, and communication capabilities of the laptop should meet certain specifications. For details, see Configuration Requirements for the Computer Installed with the LMT in the eNodeB LMT User Guide.

l

The software and data configuration file required for the eNodeB commissioning on the LMT are saved in the laptop.

Ethernet cable

The Ethernet cable connects the laptop to the eNodeB.

Testing UE


----End

6.2.2 Obtaining the Digital Certificate Required for the eNodeB Commissioning on the LMT When the security GW is deployed on the network, the eNodeB and the interconnected device (such as the security GW) need to identify each other through the digital certificate. Therefore, the digital certificate is required for the eNodeB commissioning. The digital certificate on the eNodeB side incorporates the operator's cross certificate granted by Huawei, operator's root certification authority (CA) certificate (or CA certificate chain with the root CA certificate), and operator's certificate revocation list (CRL). The digital certificate on the security GW side incorporates Huawei root CA certificate and Huawei CRL file.

Prerequisite l

The operator obtains the cross certificate granted by Huawei in advance if cross certification is used. NOTE

Before Huawei grants the cross certificate to the operator, the operator is required to provide the request file of cross certificate for Huawei. The request file of cross certificate is in format of PKCS#10, which is generated by the operator's root CA certificate, or the operator's child CA certificate that is used for the certification of eNodeB, security GW, and M2000. l


Context NOTE


6-8


Issue 03 (2010-08-10)



Procedure Step 1 Obtain the digital certificate required by the eNodeB. That is, save the operator's cross certificate, operator's root CA certificate, and operator's CRL file(optional) to the local computer. NOTE



6.2.3 Configuring the Security Equipment When the security gateway (GW) is deployed in the network, you need to configure data for the security GW. In the case that the IEEE 802.1x authentication is adopted, the authentication access equipment and the authentication server should be configured. Generally, an authentication server is the Authentication, Authorization and Accounting (AAA) server.

Prerequisite l


l


l


l


Context

Table 6-4 Security GW configuration Item

Description

IP address


Route

l


l


ike local name

Issue 03 (2010-08-10)



6-9



Item

Description

ike proposal

l


l


l


l


acl

It is recommended that permit ip be configured.

ike peer

l


l


ipsec proposal




ipsec policy




l


l


Procedure Step 1 Check the configuration of the security GW according to Table 6-4. 6-10


Issue 03 (2010-08-10)



Step 2 Configure the authentication access equipment. The authentication access equipment may vary with different operators. The example here describes a typical configuration of an authentication access equipment. Take the Quidway S6500 series Ethernet switch as an example. Run the dot1x command to enable the global 802.1x feature. Run the dot1x [ interface interfacelist ] command to enable the 802.1x feature on a specified port. Run the dot1x authenticationmethod { chap | pap | eap } command to set the EAP authentication method. For details, see the Quidway S6500 Series Ethernet Switches Operation Manual. Step 3 Configure the eNodeB CA certificate for the AAA server. The AAA server may vary with different operators. The descriptions here take the infoX AAA as an example. For details, see the infoX AAA Commissioning Guide. 1.


2.


----End

6.2.4 Configuring the FTP Server This section describes the preparations for the local commissioning on the LMT. Before performing local commissioning on the LMT, you must log in to the eNodeB on the LMT, and configure the FTP server.

Prerequisite l

The firewall of the LMT is disabled to ensure that there is no firewall between the FTP server and the eNodeB.

l

All the FTP servers on the LMT PC are shut down.

l

The software and data configuration file are available, and are saved in the same directory on the LMT PC.

CAUTION The save path should not contain folders of more than three levels. If the save path contains folders of more than three levels, the downloading of files from the FTP server fails.

Context l

The hardware configuration, software configuration, and communication capabilities of the LMT PC should meet certain specifications. For details, see Configuration Requirements for the Computer Installed with the LMT in the eNodeB LMT User Guide.

l

FTP server IP address: IP address of the LMT PC. The IP address of the LMT PC is in the same network segment as the local maintenance IP address of the LMPT.

Procedure Step 1 In the IE address bar, enter the IP address for local maintenance of the eNodeB main control board. By default, the IP address is: 192.168.0.49. Issue 03 (2010-08-10)


6-11



Step 2 Click Go to for Logging In to the LMT. By default, the user name is admin and the password is admin123. Both the user name and password are case sensitive. Step 3 Download the FTP server software. (Optional. Perform this step only when there is no FTP server at the local computer.) 1.

On the LMT, click the Software Management button. The Software Management tab page is displayed.

2.

In the navigation tree, double-click FTP Server Configuration. The FTP Server Configuration tab page is displayed, as shown in Figure 6-3.

Figure 6-3 FTP Server Configuration tab page

3.

Click Download FTP Tool. The File Download - Security Warning dialog box is displayed.

4.

Click Save to save the FTP server software SFTPServer.exe to the local computer.

Step 4 Set the FTP server. 1.

Double-click SFTPServer.exe to start the FTP server. The FTP server icon is displayed as in the status area on the right of the taskbar.

2.

Right-click , and choose FTP server configure. The FTP server configuration dialog box is displayed, as shown in Figure 6-4. Figure 6-4 FTP server configuration dialog box

6-12


Issue 03 (2010-08-10)



3.

Set User name, Password, and Working directory of the FTP server. By default, the user name and password is admin. Working directory should be set as the directory where the software and data configuration file are saved.

4.

Click OK.

Step 5 Save the FTP server configuration information on the main interface of the LMT. 1.

On the LMT, click the Software Management button. The Software Management tab page is displayed.

2.

On the FTP Server Configure tab page, set IP address of the FTP server.

3.

According to the settings in step Step 4.3, enter User name and Password. By default, the user name and password is admin.

4.

Click Save. The FTP server configuration information is saved.

----End

6.2.5 Downloading the Digital Certificate on the LMT When the security GW is deployed in the network, the digital certificate needs to be added to the eNodeB on the LMT if there is no data configuration file.

Prerequisite l

The LMT communicates properly with the eNodeB.

l

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

l


l

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

l

The FTP server configuration is complete.

l

The Huawei cross certificate, operator's root CA certificate, and operator's CRL file are ready and saved in the same directory as that of the eNodeB software and data configuration file.

CAUTION The saving path should not contain folders saved in more than three levels. If the saving path contains folders saved in more than three levels, the downloading of files from the FTP server fails.

Procedure Step 1 Run the DLD GENFILE command to respectively download the Huawei cross certificate, operator's root CA certificate, and operator's CRL file to the eNodeB. Step 2 Run the ADD CROSSCERT command to add the cross certificate. Step 3 Run the ADD TRUSTCERT command to add the operator's root CA certificate. Issue 03 (2010-08-10)


6-13



Step 4 Run the ADD CRL command to add the operator's CRL file. ----End

6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT This section describes how to download and activate the eNodeB software and data configuration file on the LMT. The eNodeB software and data configuration file take effect after the eNodeB is automatically reset. The process for upgrading the eNodeB software and data configuration file takes about 45 minutes.

Prerequisite l


l

The FTP server functions properly and is connected to the eNodeB in the same network segment.

l


l


l

The eNodeB software package is ready, and can be downloaded from http:// support.huawei.com/. A digital signature is already labeled on the eNodeB software package. If the eNodeB software package is modified unauthorizedly, a warning will be prompted during software download. In this situation, you need to obtain the correct eNodeB software package.

l

The name of the data configuration file should be LMT.xml. The file name is case sensitive. Complete the configuration by referring to the eNodeB Initial Configuration Guide. Then, save the data configuration file in the local computer.

Context

Procedure Step 1 In the MML interface on the LMT, run the LST VER command to query the active eNodeB software version. If ...

Then ...


Download and activate only the data configuration file.


Download the eNodeB software and data configuration file, and then activate the data configuration file and eNodeB software in sequence.

Step 2 On the LMT, click the Software Management button. The Software Management tab page is displayed. Step 3 In the navigation tree, double-click Download and Activate Software. The Download and Activate Software interface is displayed, as shown in Figure 6-5. 6-14


Issue 03 (2010-08-10)



Figure 6-5 Download and Activate Software interface

Step 4 Select the tasks to be performed according to step Step 1 and set the parameters related to the tasks. NOTE

If a task is not selected, the eNodeB skips the task and proceeds with the next task.

Step 5 Click the Execute button. The eNodeB performs the selected tasks from top to bottom. There is a progress bar under the Execute button, indicating the current progress and status of the task. When the progress bar of each task displays 100%, the download and activation are complete.

CAUTION If a task fails, the eNodeB stops the task and does not continue with subsequent tasks. If only the data configuration file is downloaded and activated during the upgrade, you need to manually reset the eNodeB after the data configuration file is activated so that the updated data takes effect. The eNodeB is automatically reset after the eNodeB software is activated. Before the eNodeB is automatically reset, do not send any reset command to the eNodeB or boards, and do not power off the eNodeB or remove the boards. If you perform any of the preceding operations before the eNodeB is automatically reset, the download and activation fail, and the software and files on the boards may be cleared or damaged. ----End

Issue 03 (2010-08-10)


6-15



6.4 Downloading the License for eNodeB Commissioning on the LMT After downloading the commissioning license to the eNodeB on the LMT, you are authorized to use the eNodeB software.

Prerequisite l


l

The commissioning license is already obtained.

Context Apply for the commissioning license by referring to the license application guide, and store the commissioning license to the local computer. The license user guide can be downloaded from http://support.huawei.com/. NOTE

The commissioning license has a time limit. You should replace the commissioning license with a commercial license in time after the eNodeB commissioning is complete.

Procedure Step 1 Run the INS LICENSE command to download and activate the license file on the eNodeB. ----End

6.5 Commissioning the ALD on the LMT This section describes how to commission the Antenna Line Device (ALD). The task consists of Remote Electrical Tilting (RET) antenna commissioning and Tower Mounted Amplifier (TMA) commissioning.

Prerequisite l


l

The ALD management requires a license.

6.5.1 Commissioning the RET Antenna The procedures for commissioning the RET antenna are as follows: downloading the RET antenna software, downloading the configuration file of the RET antenna, and calibrating the RET antenna. 6.5.2 Commissioning the TMA This section describes how to commission the TMA. The first and most important step of commissioning is loading the TMA software. After the TMA software is loaded, the TMA is automatically reset. The software takes effect after the TMA is reset.

6-16


Issue 03 (2010-08-10)



6.5.1 Commissioning the RET Antenna The procedures for commissioning the RET antenna are as follows: downloading the RET antenna software, downloading the configuration file of the RET antenna, and calibrating the RET antenna.

Procedures for Commissioning the RET Antenna Figure 6-6 shows the procedures for commissioning the RET antenna. Figure 6-6 Procedures for commissioning the RET antenna

6.5.1.1 Querying the Active Software Version of the RET Antenna Before downloading the software, you need to set the ALD power switch, add an RET antenna, and query the active software version of the RET antenna on the LMT. 6.5.1.2 Downloading the RET Antenna Software This section describes how to download the RET antenna software from the FTP server to the RET antenna. After the download, the RET antenna is automatically reset. The software takes effect after the RET antenna is reset. 6.5.1.3 Downloading the Data Configuration File of the RET Antenna This section describes how to download the RET configuration file from the FTP server to the RET antenna. The data configuration file of the RET antenna takes effect immediately after the download is complete. Issue 03 (2010-08-10)


6-17



6.5.1.4 Calibrating the RET Antenna This section describes how to calibrate the RET antenna to ensure that all downtilts of the RET antenna are correctly configured.

6.5.1.1 Querying the Active Software Version of the RET Antenna Before downloading the software, you need to set the ALD power switch, add an RET antenna, and query the active software version of the RET antenna on the LMT.

Prerequisite The LMT communicates properly with the eNodeB. Table 6-5 lists the preparations to be made before commissioning the RET antenna. Table 6-5 Preparations for commissioning the RET antenna Item

Description

Software of the RET antenna

The software is supplied by the ALD vendor.

Data configuration file of the RET antenna

This file is supplied by the ALD vendor. The configuration data of the RET antennas may vary with vendors and models.

Downtilt of the RET antenna

The downtilt of the RET antenna is defined in the network planning.

Procedure Step 1 Run the SCN ALD command to scan the ALD that is connected with the RRU. Step 2 Run the DSP RETSUBUNIT command to check whether the RET antenna is working. If the RET antenna is not working, contact Huawei for technical support. Step 3 Run the DSP ALDVER command to check the active RET software version of the ALD. NOTE


If ...

Then ...


Record the device number of the RET antenna, and perform the step 6.5.1.3 Downloading the Data Configuration File of the RET Antenna without downloading the RET software.


Record the device number of the RET antenna, and commission the RET antenna after performing the step 6.5.1.2 Downloading the RET Antenna Software.

----End 6-18


Issue 03 (2010-08-10)



6.5.1.2 Downloading the RET Antenna Software This section describes how to download the RET antenna software from the FTP server to the RET antenna. After the download, the RET antenna is automatically reset. The software takes effect after the RET antenna is reset.

Prerequisite l

The RET antenna software is available.

l


l


l


l


Procedure Step 1 Run the DLD ALDSW command to download the RET antenna software. Step 2 If the eNodeB is configured with multiple RET antennas, repeat step 1 to download the software of other RET antennas. ----End

6.5.1.3 Downloading the Data Configuration File of the RET Antenna This section describes how to download the RET configuration file from the FTP server to the RET antenna. The data configuration file of the RET antenna takes effect immediately after the download is complete.

Prerequisite l

The data configuration file of the RET antenna is available.

l


l

The FTP server operates properly and is connected to the eNodeB in the same network segment.

l


l


Context The data configuration file of the RET antenna is provided by the vendor. The configuration data may vary with antenna models. The RET antenna does not has the file check function. If an incorrect RET configuration file is downloaded, the RET antenna may become unavailable.

Procedure Step 1 Run the DSP RET command to query the subunits of each RET antenna. Then, record the result. Issue 03 (2010-08-10)


6-19



NOTE

The RET subunits are numbered from one in ascending order. Download the required data configuration file for each subunit.

Step 2 Run the DLD RETCFGDATA command to download the data configuration file for each RET subunit. Step 3 If one RET antenna consists of multiple subunits, repeat 2 to download the data configuration files of other RET subunits. Step 4 If one eNodeB is configured with multiple RET antennas, repeat step 2 to download the data configuration files of other RET subunits. ----End

6.5.1.4 Calibrating the RET Antenna This section describes how to calibrate the RET antenna to ensure that all downtilts of the RET antenna are correctly configured.

Prerequisite The LMT communicates properly with the eNodeB.

Context l

The calibration is mandatory after the RET antenna is installed. If this operation is skipped, the network coverage may be affected.

l

The RET antenna does not need to be recalibrated after you reset or power off the RET antenna.

l

You need to set the antenna downtilt again after calibrating the RET antenna according to customer specifications.

l

Run the MML command CLB RET to calibrate the RET antenna.

Procedure NOTE

You can calibrate the RET antenna in batches if you run this command without specifying any parameter.

----End

6.5.2 Commissioning the TMA This section describes how to commission the TMA. The first and most important step of commissioning is loading the TMA software. After the TMA software is loaded, the TMA is automatically reset. The software takes effect after the TMA is reset.

Prerequisite

6-20

l

The TMA software is available.

l

The LMT communicates properly with the eNodeB. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-08-10)



l


l


CAUTION Ensure that there is no firewall between the FTP server and the eNodeB. If a firewall is installed on the PC, disable the firewall.

Context l

The TMA is one part of the antenna system and is used to amplify the received weak signals.

l

The software of the TMA is supplied by the ALD vendor.

l

If the incorrect TMA software is loaded, the TMA may fail to operate normally.

Procedure Step 1 Run the SCN ALD command to scan the ALD that is connected with the RRU. Step 2 Run the DSP TMASUBUNIT command to check whether the TMA is working. If the TMA is not working, contact Huawei for technical support. Step 3 Run the DSP ALDVER command to query the software version of the TMA to be commissioned. NOTE


If ...

Then ...


End this task.


Go to step 4.

Step 4 Run the DLD ALDSW command to download the TMA software to be commissioned. Step 5 If the eNodeB is configured with multiple TMAs, repeat step 3 and step 4 to download the software of other TMAs. ----End

6.6 Commissioning the Antenna System on the LMT Commissioning the antenna system helps to check for problems in the installed antenna system. Issue 03 (2010-08-10)


6-21



Prerequisite l

The antenna system of the eNodeB is installed.

l


Procedure Step 1 Run the LST RRU command to query the Voltage Standing Wave Ratio (VSWR) alarm threshold. Step 2 Run the STR VSWRTEST command to start the VSWR test. If ...

Then ...

The test value is smaller than the VSWR alarm threshold

The antenna system is properly installed. End the commissioning.

The test value is equal to or greater than the VSWR alarm threshold

The antenna system is not properly installed. Rectify the faults by referring to the handling procedures for the VSWR alarm in the eNodeB Alarm Reference.

NOTE

The offline VSWR test may interrupt the services of both working modes.

----End

6.7 Commissioning the Environment Monitoring Equipment on the LMT This section describes how to check the environment monitoring equipment on the M2000. After the environment monitoring equipment is connected, you need to commission it so that it functions properly. 6.7.1 Setting the Environment Alarm Parameters This section describes how to set the parameters related to the environment alarms. You can set alarm parameters within the permissible range according to the actual situation. 6.7.2 Checking for the External Environment Alarms This section describes how to check for external environment alarms. After the parameters of the environment alarms are set, you need to verify the parameter configuration by checking for the external environment alarms.

6.7.1 Setting the Environment Alarm Parameters This section describes how to set the parameters related to the environment alarms. You can set alarm parameters within the permissible range according to the actual situation.

Prerequisite l

6-22

The LMT communicates properly with the eNodeB. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-08-10)



l

The environment monitoring equipment is configured.

l

The DIP switches of the environment monitoring equipment are properly set. For details, see the APM30H&TMC11H&IBBS200D&IBBS200T(ver.B) User Guide and the EMUA User Guide.

Context The RRU, UPEU of BBU, EMUA, and PMU of the APM30H are all configured with extended alarm ports. The external environment alarm and the extended alarm port are already bound together. For details, see Table 6-6. Table 6-6 Extended alarm ports MO

MML Commands

Description

AlmPort

SET ALMPORT

Use this command to set the input port of the environment signals.

If the alarm ID of an external environment alarm is predefined, the following step is not necessary. For the alarm IDs of such alarms, see eNodeB Alarm Reference.

Procedure l

Run the SET ENVALMPARA command to set the name, level, and event type of an external environment alarm. NOTE

ALM ID is configured when the external environmental alarm and the extended alarm port are bound.

----End

6.7.2 Checking for the External Environment Alarms This section describes how to check for external environment alarms. After the parameters of the environment alarms are set, you need to verify the parameter configuration by checking for the external environment alarms.

Context Manually trigger an external environment alarm. If the alarm can be reported normally, the configuration of the external environment alarm is correct.

Procedure Step 1 Simulate the environment for generating an external environment alarm. Step 2 Check for active alarms on the LMT. For details, see 6.9 Handling the eNodeB Alarms on the LMT. If the external environment alarm can be reported normally, it indicates that the related configuration is correct. If the external environment alarm cannot be reported normally, set the parameters again or contact Huawei for technical support. ----End Issue 03 (2010-08-10)


6-23



Example Assume that the APM30H is the environment monitoring device of the site. Check for the Mains Input Out of Range alarm. 1.

Cut off the AC power supply to the eNodeB, so that the AC voltage drops below the AC voltage lower threshold.

2.

Check for the Mains Input Out of Range alarm on the LMT. If the alarm exists, the related configuration is correct.

6.8 Setting the Maximum TX Power of RRU or RFU Set the maximum TX power of the RRU or RFU on site, according to the local regulations on power specifications.

Prerequisite l

The RRU or RFU is connected properly.

l

A laptop is ready.

Context The maximum TX power of the RRU or RFU is specified by the local operator.

CAUTION The maximum TX power of the RRU or RFU is set through the LMT on site.

Procedure Step 1 Run the DSP RRU command to query the cabinet/subrack/slot No. and TX channel No. of the RRU or RFU. Step 2 Run the LOC RRUTC command to set the maximum TX power of the RRU or RFU. NOTE

The LOC RRUTC command is used to set the maximum TX power of one RRU or RFU at a time.

Step 3 Run the RST BRD command to reset the RRU or RFU. NOTE

The RST BRD command is used to reset one RRU or RFU at a time.

Step 4 Run the DSP TXBRANCH command to check that the maximum TX power of each RRU or RFU is set successfully.

6-24

If ...

Then ...

The maximum TX power of each RRU or RFU is set successfully

End this task.


Issue 03 (2010-08-10)



If ...

Then ...

The maximum TX power of each RRU or RFU is not set successfully

Check whether the maximum TX power exceeds the power specifications supported by the RRU or RFU. Set the maximum TX power again. If the setting of the maximum TX power still fails, contact Huawei for technical support.

----End

6.9 Handling the eNodeB Alarms on the LMT This section describes how to handle the alarms generated during the commissioning.


Procedure Step 1 On the LMT, click the Alarm button. The Alarm tab page is displayed. Step 2 Check for active alarms on the Engineering tab page of the Browse Alarm tab page. If ...

Then ...

No active alarm exists

End the task.

Active alarms exist

Go to step Step 3.

Step 3 Double-click an active alarm. The Alarm Detailed Information dialog box is displayed. Step 4 Click Solution... to learn the detailed information and alarm handling procedure. Clear the active alarm by following the alarm handling procedure. ----End

6.10 Querying the Running Status of the eNodeB on the LMT This section describes how to check the running status of the eNodeB on the LMT.


Context Table 6-7 lists the eNodeB device checklist. Issue 03 (2010-08-10)


6-25



Table 6-7 eNodeB device checklist Check Item

Description

eNodeB type

Check the eNodeB type in data configuration.

eNodeB software version

Check the active eNodeB software, including the version and running status.

Hardware status

Check the status of the RF unit, receive channel, transmit channel, and boards.

Interface status

Check the configuration related to IP Path, CPRI port, remote maintenance channel, E1/T1 port, Ethernet port, and SCTP link of the eNodeB.

Cell status

Check the cell status.

Active alarm query

Check for active alarms of the NE.

Procedure Step 1 On the LMT, click the Self-Test button. On the displayed Self-Test tab page, an MML command script with the complete parameter settings is automatically imported to the command area. Step 2 Click the Execute button. The test result is displayed in the area below the Execute button. NOTE

If the test fails, check for active alarms and rectify the related faults. If all active alarms are cleared but the test still fails, contact Huawei for technical support.

----End

6.11 Testing the Basic Services of the eNodeB This section describes how to test the basic services of the eNodeB.

Prerequisite l

The eNodeB and the MME/S-GW are properly connected.

l

The negotiation data of the eNodeB to be commissioned is added to the MME/S-GW.

l


l

The FTP server for testing the basic services is available.

l

The WWW server for testing the basic services is available.

l

Test the web page browsing service.

Procedure Testing Method

6-26

Access the WWW server and browse the web pages through a UE. Perform the test 20 times.


Issue 03 (2010-08-10)



Expectation

l

l

l

Success rate > 95%. Web browsing is normal.

Test the file uploading service. Testing Method

Access the FTP server and upload files through a UE. Perform the test 10 times.

Expectation

Success rate > 90%. The upload rate is stable.

Test the file downloading service. Testing Method

Access the FTP server and download files through a UE. Perform the test 10 times.

Expectation

Success rate >90%. The download rate is stable.

Test the VoIP services. Testing Method

Use the testing UE to call another UE 20 times.

Expectation

Connection success rate > 95%. The calls are uninterrupted and none of the calls get dropped till they are released. The voice is clear with no loud noise.

----End

6.12 Establishing the OM Channel Between the M2000 and the eNodeB This section describes how to establish the OM channel between the M2000 and the eNodeB through the M2000 client.

Prerequisite l


l

The M2000 server and client are running properly.

l

The main information of the NE is obtained, such as NE name, IP address of the NE, NE version, and administrative region of the NE.

Context To facilitate maintenance, the M2000 allows the creation of physical NEs in batch mode. You can create multiple physical NEs at one time in the topology. For details, see section Creating Multiple Physical NEs in the M2000 Online Help. In this section, the procedure for creating a single physical NE is described.

Issue 03 (2010-08-10)


6-27



Procedure Step 1 Create one physical NE in the topology. 1.

On the M2000 client, choose Topology > Main Topology. The Main Topology tab page is displayed, as shown in Figure 6-7.

Figure 6-7 Main Topology tab page

2.

6-28

In the navigation tree of Physical Root or the physical view, right-click the subnet of the NE to be created and choose New > Create Topo Object... from the shortcut menu. The Create Topo Object dialog box is displayed, as shown in Figure 6-8.


Issue 03 (2010-08-10)



Figure 6-8 Create Topo Object dialog box

3.

In the Create Topo Object dialog box, select an NE node under Single Create.

4.

Configure the NE information in the right pane of the dialog box.

5.

Click OK to create the NE. NOTE

The system displays the Create NE Progress dialog box to show the creating progress. After the NE is successfully created, the system automatically obtains the configuration information of the NE. If the network connection between the M2000 server and the newly-created NE malfunctions, the NE is still displayed in the specified location of the topology but the NE is disconnected. In this case, the NE is .

shown as

6.

Click Close. The Create NE Progress dialog box is closed.

Step 2 Wait for about five minutes, and then check the NE icon on the Main Topology tab page. If ...

Then ...

The NE icon is

The OM channel fails to be established. Contact Huawei for technical support. The OM channel is successfully established.

The NE icon is

Issue 03 (2010-08-10)


6-29



----End

6.13 Setting the eNodeB Status After the eNodeB commissioning is complete and the eNodeB starts to provide services properly, set the eNodeB to the normal state on the M2000.

Context Before delivery, the eNodeB is set to the testing state.

Procedure Step 1 On the M2000 client, choose Maintenance > Maintenance Mode. The Maintenance Mode tab page is displayed. Step 2 Click Set NE Mode at the upper left corner of the Maintenance Mode tab page. The Set NE Mode dialog box is displayed. Step 3 Select the target NE and specify the time. Step 4 Set Mode to NORMAL. The eNodeB is changed to the normal state. Step 5 Click OK. The setting of the maintenance mode is complete. NOTE

The alarms that are not cleared during commissioning will be reported on the eNodeB in normal state.

----End

6-30


Issue 03 (2010-08-10)


7

7 eNodeB Commissioning Reference

eNodeB Commissioning Reference

About This Chapter This chapter describes the communication ports on the eNodeB, and provides the eNodeB commissioning data sheet. 7.1 Data Sheet for eNodeB Commissioning This section provides the data sheet that is used to record the process and results of the eNodeB commissioning. The Data Sheet for Commissioning used at different sites may be different. This table serves as a reference only. 7.2 Communication Ports on the eNodeB This section describes the communication ports on the eNodeB.

Issue 03 (2010-08-10)


7-1



7.1 Data Sheet for eNodeB Commissioning This section provides the data sheet that is used to record the process and results of the eNodeB commissioning. The Data Sheet for Commissioning used at different sites may be different. This table serves as a reference only. Table 7-1 Data sheet for eNodeB commissioning eNodeB name eNodeB ID eNodeB Type ESN Commiss ioning Time Commiss ioning Engineer Commiss ioning Result

7-2

□ Successful; □ Failed

Commissioning Item

Conclus ion

Commiss ioning Prerequis ites

Faults in eNodeB hardware installation are rectified.

□ Yes; □ No

Negotiation data of the eNodeB to be commissioned is added to the MME/S-GW.

□ Yes; □ No

Remote eNodeB Commiss ioning on the M2000

Prepa ration Phase

The information regarding the eNodeB, such as name, ID, and ESN, is reported.

□ Yes; □ No

The eNodeB is powered on.

□ Yes; □ No

The eNodeB software and related files required for automatic deployment are ready.

□ Yes; □ No

Handling Exceptions


Issue 03 (2010-08-10)



Rem ote end of the eNod eB

Local eNodeB Commiss ioning Through the USB Storage Device

Prepa ration Phase

Local end of the eNod eB

Issue 03 (2010-08-10)

The digital certificate is ready.

□ Yes; □ No

The security equipment is ready.

□ Yes; □ No


□ Yes; □ No

The ESN is bound.

□ Yes; □ No

The automatic eNodeB commissioning task is complete.

□ Yes; □ No

The eNodeB commissioning report is obtained.

□ Yes; □ No

The running status of the eNodeB is normal.

□ Yes; □ No

The test result of the external environment alarm is correct.

□ Yes; □ No

The test result of the basic services is correct.

□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No

The software and data configuration file are loaded through the USB storage device.

□ Yes; □ No

The eNodeB is reset.

□ Yes; □ No

The indicator status is normal.

□ Yes; □ No


7-3




Local eNodeB Commiss ioning on the LMT

Prepa ration Phase

Local end of the eNod eB

7-4

The ESN is bound.

□ Yes; □ No

The automatic eNodeB commissioning task is complete.

□ Yes; □ No

The eNodeB commissioning report is obtained.

□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


□ Yes; □ No

The digital certificate is downloaded successfully.

□ Yes; □ No

The software and data configuration file are loaded through the LMT.

□ Yes; □ No

The software is upgraded to the target version.

□ Yes; □ No

All the active alarms are cleared.

□ Yes; □ No


□ Yes; □ No


□ Yes; □ No


Issue 03 (2010-08-10)





□ Yes; □ No

The ESN is bound.

□ Yes; □ No

The OM channel is established.

□ Yes; □ No

Problem Description

Impact

Component

P/N

Unsolved Problems After Commiss ioning

Faulty Board Record

7.2 Communication Ports on the eNodeB This section describes the communication ports on the eNodeB. Table 7-2 lists the communication ports on the eNodeB. Table 7-2 Communication ports on the eNodeB

Issue 03 (2010-08-10)

Prot ocol

A Side

A Side Port Number (RX)

B Side

B Side Port Number (TX)

Service

Author ity Manag ement

TCP

eNod eB

4443

M2000 serve

1024-65535

For M2000,Test digital certificate

None

TCP

eNod eB

6000

LMT

1024-65535

For the LMT to deliver the maintenance command and for the UE to respond. Format: MML

User name/ passwor d

TCP

eNod eB

6001

LMT

1024-65535

For the NE to report alarms. Format: MML

None


7-5



7-6

Prot ocol

A Side


B Side


Service


TCP

eNod eB

6006

LMT

1024-65535

For maintenance. Format: BIN

None

TCP

eNod eB

6007

M2000 serve

1024-65535

For M2000. Integration port for MML, alarm, and BIN.


TCP

eNod eB

1024-65535

Site debug console

21

For FTP. Commissioning mode. Local maintenance FE port only


TCP

eNod eB

23

Site debug console

1024-65535

For telnet. Commissioning mode. Local maintenance FE port only


TCP

eNod eB

80

LMT

1024-65535

For weblmt


TCP

eNod eB

443

LMT

1024-65535

For weblmt (security mode)


UDP

eNod eB

67/68

M2000 server or any other DHCP server

67/68

For DHCP services

None

UDP

M200 0 server or any other DHC P server

67/68

eNodeB

67/68

For DHCP services

None


Issue 03 (2010-08-10)


Issue 03 (2010-08-10)


Prot ocol

A Side


B Side


Service


UDP

M200 0 server or any other DHC P server

123

eNodeB

1024-65535

For synchronizing the NTP time

None


7-7

eNodeB Commissioning Guide(V100R002C00 03)

Recommend Documents