enodeb commissioning guide(v100r005c00_07)(pdf)-en

eNodeBV100R005C00

Commissioning Guide

Issue 07

Date 2012-11-14

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 07 (2012-11-14) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes how to commission an eNodeB after the eNodeB is successfullyinstalled and configured to verify that the eNodeB works properly as designed. The eNodeBsupports three commissioning modes: M2000-based remote commissioning, USB-based localcommissioning+M2000-based remote commissioning, and LMT-based local commissioning.

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

Product Name Product Version

DBS3900 LTE V100R005C00

DBS3900 LTE TDD V100R005C00

BTS3900 LTE V100R005C00

BTS3900A LTE V100R005C00

BTS3900L LTE V100R005C00

BTS3900AL LTE V100R005C00

Intended AudienceThis document is intended for:

l eNodeB installation engineersl Field engineers

eNodeBCommissioning Guide About This Document


ii

Organization1 Changes in eNodeB Commissioning Guide

This chapter describes the changes in eNodeB Commissioning Guide.

2 Commissioning Mode

The eNodeB supports the following commissioning modes: PnP remote commissioning, localcommissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on theLMT. You can select a commissioning mode based on the site conditions. PnP remotecommissioning is recommended.

3 eNodeB Commissioning Procedures

This chapter describes the following procedures: plug and play (PnP) remote commissioning,local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioningon the LMT.

4 Appendix

This chapter describes how to encrypt files in a Universal Serial Bus (USB) storage device andprovides the eNodeB commissioning data sheet.

5 FAQ

This chapter describes some common problems and solutions during commissioning.

ConventionsSymbol Conventions

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

Symbol Description

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

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

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

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

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

General Conventions

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



iii

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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

Command Conventions

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


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

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

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

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

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

GUI Conventions

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


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

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

Keyboard Operations

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



iv

Format Description

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

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

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

Mouse Operations

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

Action Description

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

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

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



v

Contents

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

1 Changes in eNodeB Commissioning Guide............................................................................1

2 Commissioning Mode..................................................................................................................8

3 eNodeB Commissioning Procedures.......................................................................................103.1 Overview of eNodeB Automatic Discovery.....................................................................................................113.2 PnP Remote Commissioning............................................................................................................................13

3.2.1 Commissioning Procedure.......................................................................................................................133.2.2 Preparations.............................................................................................................................................163.2.3 Creating an eNodeB Commissioning Task.............................................................................................303.2.4 Starting an eNodeB Commissioning Task...............................................................................................323.2.5 Monitoring eNodeB Commissioning.......................................................................................................353.2.6 Confirming eNodeB Commissioning Completion..................................................................................393.2.7 Checking the Running Status of the eNodeB on the M2000...................................................................403.2.8 Commissioning the Antenna System on the M2000...............................................................................443.2.9 Commissioning the Environment Monitoring Equipment on the M2000...............................................483.2.10 Setting the Maximum Output Power for RRUs or RFUs......................................................................513.2.11 Testing the Basic Services of the eNodeB.............................................................................................523.2.12 Setting an NE to the NORMAL Mode..................................................................................................533.2.13 References to eNodeB Commissioning.................................................................................................54

3.3 Local Commissioning Using a USB Flash Drive.............................................................................................623.3.1 Commissioning Procedure.......................................................................................................................633.3.2 Preparations.............................................................................................................................................663.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB FlashDrive.................................................................................................................................................................693.3.4 Uploading Data Files...............................................................................................................................733.3.5 Creating an eNodeB Commissioning Task.............................................................................................833.3.6 Starting an eNodeB Commissioning Task...............................................................................................853.3.7 Monitoring eNodeB Commissioning.......................................................................................................883.3.8 Confirming eNodeB Commissioning Completion..................................................................................923.3.9 Checking the Running Status of the eNodeB on the M2000...................................................................933.3.10 Commissioning the Antenna System on the M2000.............................................................................973.3.11 Commissioning the Environment Monitoring Equipment on the M2000...........................................101

eNodeBCommissioning Guide Contents


vi

3.3.12 Setting the Maximum Output Power for RRUs or RFUs....................................................................1043.3.13 Testing the Basic Services of the eNodeB...........................................................................................1053.3.14 Setting an NE to the NORMAL Mode................................................................................................1063.3.15 References to eNodeB Commissioning...............................................................................................107

3.4 Local Commissioning on the LMT (Without the SeGW)..............................................................................1153.4.1 Commissioning Procedure.....................................................................................................................1163.4.2 Preparations...........................................................................................................................................1193.4.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........1223.4.4 Downloading the License for eNodeB Commissioning on the LMT....................................................1253.4.5 Commissioning the Antenna System on the LMT................................................................................1253.4.6 Commissioning the Environment Monitoring Equipment on the LMT................................................1313.4.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................1333.4.8 Handling the eNodeB Alarms on the LMT...........................................................................................1343.4.9 Checking the Operating Status of the eNodeB on the LMT..................................................................1343.4.10 Testing the Basic Services of the eNodeB...........................................................................................1353.4.11 Establishing an OML Between the M2000 and the eNodeB...............................................................1363.4.12 Setting an NE to the NORMAL Mode................................................................................................139

3.5 Local Commissioning on the LMT (with the SeGW)....................................................................................1393.5.1 Commissioning Procedure.....................................................................................................................1393.5.2 Preparations...........................................................................................................................................1423.5.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........1493.5.4 Downloading the License for eNodeB Commissioning on the LMT....................................................1523.5.5 Commissioning the Antenna System on the LMT................................................................................1533.5.6 Commissioning the Environment Monitoring Equipment on the LMT................................................1593.5.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................1613.5.8 Handling the eNodeB Alarms on the LMT...........................................................................................1623.5.9 Checking the Operating Status of the eNodeB on the LMT..................................................................1623.5.10 Testing the Basic Services of the eNodeB...........................................................................................1633.5.11 Establishing an OML Between the M2000 and the eNodeB...............................................................1643.5.12 Setting an NE to the NORMAL Mode................................................................................................166

4 Appendix.....................................................................................................................................1684.1 eNodeB Binding Using a Bar Code Scanner..................................................................................................170

4.1.1 Printing a Bar Code on the M2000........................................................................................................1704.1.2 Setting a Bar Code Scanner...................................................................................................................1734.1.3 Binding the eNodeB by Scanning a Bar Code......................................................................................176

4.2 Triggering Monitoring Device Alarms...........................................................................................................1774.2.1 Triggering PMU Alarms........................................................................................................................1774.2.2 Triggering FMU Alarms........................................................................................................................1834.2.3 Triggering TCU Alarms........................................................................................................................1854.2.4 Triggering EMU Alarms.......................................................................................................................187

4.3 Checking the Status of Indicators...................................................................................................................1894.4 Configuring the Preconfigurationn File..........................................................................................................195



vii

4.5 Applying Integrity and Encryption Protection to Files in the USB Flash Drive............................................1954.6 Binding Modes Between the M2000 and the eNodeB...................................................................................2014.7 Data Sheet for eNodeB Commissioning.........................................................................................................203

5 FAQ..............................................................................................................................................2075.1 Failing to Identify the USB Flash Drive.........................................................................................................2085.2 Failing to Read Files in the USB Flash Drive................................................................................................2095.3 Failing to Activate the Software.....................................................................................................................2105.4 Failing to Download the Software Based on the Preconfiguration File.........................................................210



viii

1 Changes in eNodeB Commissioning Guide

This chapter describes the changes in eNodeB Commissioning Guide.

07 (2012-11-14)

This is the seventh official release.

Compared with issue 06 (2012-09-20) of V100R005C00, this issue includes the following newinformation.

Topic Change Description

4.5 Applying Integrity and EncryptionProtection to Files in the USB Flash Drive

Added the description of how to performencryption and integrity protection onmultiple USB flash drives at the same time.

Compared with issue 06 (2012-09-20) of V100R005C00, this issue includes the followingchange.



Modified the description of the files for whichintegrity protection and encryption can beperformed.

No information in issue 06 (2012-09-20) of V100R005C00 is deleted from this issue.

06 (2012-09-20)

This is the sixth official release.


eNodeBCommissioning Guide 1 Changes in eNodeB Commissioning Guide


1


4.6 Binding Modes Between the M2000 andthe eNodeB

Added the section "Binding Modes Betweenthe M2000 and the eNodeB".

Compared with issue 05 (2012-07-30) of V100R005C00, this issue includes the followingchanges.


3 eNodeB Commissioning Procedures l Combined the PnP remote commissioningprocedures with the security gateway(SeGW) and without the SeGW.

l Combined the local commissioningprocedures using a Universal Serial Bus(USB) with the SeGW and without theSeGW.


Added the descriptions of files supportingintegrity and encryption protection.Optimized the procedure.

The following information in issue 05 (2012-07-30) of V100R005C00 is deleted from this issue:l Deleted the section "eNodeB Commissioning Procedures (with the SeGW)".

05 (2012-07-30)This is the fifth official release.

Compared with issue 04 (2012-06-29) of V100R005C00, this issue does not include any newinformation.



l Preparing a USB Flash Drive for LocalCommissioning


Combined steps 4 and 5 into step 4.

l Configuring the Security Equipmentl Configuring the Security Equipment

Modified tables of "SeGW configuration"and "Descriptions of customizedinformation" in the "Configuring the SecurityEquipment" topic.

No information in issue 04 (2012-06-29) of V100R005C00 is deleted from this issue.



2

04 (2012-06-29)This is the fourth official release.



Obtaining an Operator's Device CertificateManually (with PKI)

Added the procedure for manually obtainingoperators' certificates.



l 3 eNodeB Commissioning Proceduresl eNodeB Commissioning Procedures

(with the SeGW)

Modified the document organization byseparating the commissioning procedures forscenarios with the SeGW and without theSeGW, and separating the commissioningprocedures in unified encryption mode and indifferentiated encryption for the scenariowith the SeGW.

The following information in issue 03 (2012-05-11) of V100R005C00 is deleted from this issue:l Deleted the section "Obtaining the Common Configuration File."

03 (2012-05-11)This is the third official release.



l 4.4 Configuring the PreconfigurationnFile

l 5.4 Failing to Download the SoftwareBased on the Preconfiguration File

Added sections on obtaining the commonconfiguration file, configuring thepreconfiguration file and failing to downloadthe software based on the preconfigurationfile.

Compared with issue 02 (2012-04-28) of V100R005C00, this issue does not include any changesor delete any information.

02 (2012-04-28)This is the second official release.



3

Compared with issue 01 (2012-03-30) of V100R005C00, this issue does not include any newinformation.



l Overview of eNodeB AutomaticDiscovery (with the SeGW)

l 3.3.3 Downloading and Activating theSoftware, Data Configuration File, andLicense File Using a USB Flash Drive

l 4.3 Checking the Status of Indicatorsl Preparing a USB Flash Drive for Local

Commissioningl 4.5 Applying Integrity and Encryption

Protection to Files in the USB FlashDrive


Optimized the description.

The following information in issue 01 (2012-03-30) of V100R005C00 is deleted from this issue:l Obtaining the Common Configuration File

01 (2012-03-30)

This is the first official release.

Compared with draft B (2012-02-15) of V100R005C00, this issue includes the following newinformation.


4.3 Checking the Status of Indicators Added the descriptions of ACT indicator onthe main control board.



Added the description of downloading theboard software by using preconfigurationfile.

3.3.3 Downloading and Activating theSoftware, Data Configuration File, andLicense File Using a USB Flash Drive

Added the figure of the USB port on UMPTand the method of downloading the LMTcomplete package by using a USB flash drivewhen the LMPT is used.

Compared with draft B (2012-02-15) of V100R005C00, this issue does not include any changes.



4

The following information in draft B (2012-02-15) of V100R005C00 is deleted from this issue.


l 3.2 PnP Remote Commissioningl PnP Remote Commissioning in Unified

Encryption Mode (with the SeGW)l 3.3 Local Commissioning Using a USB

Flash Drivel Local Commissioning Using a USB Flash

Drive in Unified Encryption Mode (withthe SeGW)

l 3.4 Local Commissioning on the LMT(Without the SeGW)

l 3.5 Local Commissioning on the LMT(with the SeGW)

Deleted the procedure for comparing thelicense and configuration data in thecommissioning.

Draft B (2012-02-15)This is draft B.

Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following newinformation.


5 FAQ Added "FAQ."

Compared with draft A (2012-01-10) of V100R005C00, this issue includes the followingchanges.








Separated the description of remotecommissioning on the M2000, localcommissioning using a USB flash drive+remote commissioning on the M2000, andlocal commissioning on the LMT with theSeGW and those without the SeGW.



5


3.2.12 Setting an NE to the NORMALMode

Changed "Setting eNodeB State" to"Restoring the eNodeB to the Normal State"and changed the operation procedure.

Compared with draft A (2012-01-10) of V100R005C00, this issue has no information deleted.

Draft A (2012-01-10)This is draft A.









Added the procedure for comparing thelicense and configuration data in allcommissioning scenarios.


Added the procedure for activating thelicense file using the USB flash drive.

Preparing a USB Flash Drive for LocalCommissioning

3.2.12 Setting an NE to the NORMALMode

Added the procedure for querying theeNodeB state.

Compared with issue 02 (2011-11-15) of V100R004C00, this issue includes the followingchange.



Changed the description of downloading theLMT complete package using the USB flashdrive.



6

The following information in issue 02 (2011-11-15) of V100R004C00 is deleted from this issue.



7

2 Commissioning Mode

The eNodeB supports the following commissioning modes: PnP remote commissioning, localcommissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on theLMT. You can select a commissioning mode based on the site conditions. PnP remotecommissioning is recommended.

Prerequisitesl Requirements for the device status and commissioning environment are described as

follows:– All hardware devices and cables have been properly installed. For details, see related

installation guides, which can be obtained at http://support.huawei.com/.– The eNodeB has passed a hardware check before power-on.– Before remote commissioning on the M2000, you have installed the mediation software

matching the target version of the eNodeB to be commissioned on the M2000 server.l Requirements for the network are described as follows:

The eNodeB is connected to the mobility management entity (MME) or serving gateway(S-GW) in the evolved packet core (EPC), and the MME or S-GW is configured with theinterconnection data required for commissioning and can provide the basic functions of theEPC.

l Requirements for data configuration are described as follows:Based on live network and eNodeB design requirements, the eNodeB configuration dataare configured using the configuration management express (CME) or man-machinelanguage (MML) command. For details, see eNodeB Initial Configuration Guide.

Application ScenarioTable 2-1 lists the application description for each commissioning scenario.

eNodeBCommissioning Guide 2 Commissioning Mode


8

http://support.huawei.com/

Table 2-1 Application description for commissioning scenarios

CommissioningMode

Application Scenario

3.2 PnP RemoteCommissioning

l The operation and maintenance (OM) channel between theeNodeB and the M2000 works properly.

l The eNodeB is relocated with permissible downtime greater thanor equal to 1 hour.

l The security gateway (SeGW) is deployed in the network. TheeNodeB and the M2000 belong to different domains. TheeNodeB communicates with the M2000 through the SeGW.

3.3 LocalCommissioningUsing a USB FlashDrive

l No OM channel is established between the eNodeB and theM2000.

l A USB flash drive is available.l The eNodeB is relocated with permissible downtime less than 1

hour.l The security gateway (SeGW) is deployed in the network. The

eNodeB and the M2000 belong to different domains. TheeNodeB communicates with the M2000 through the SeGW.

3.4 LocalCommissioning onthe LMT (Withoutthe SeGW)


l The USB flash drive is unavailable or damaged, or eNodeBdeployment using the USB flash drive fails.

l The eNodeB is relocated with permissible downtime less than 1hour.

l No SeGW is deployed in the network.

3.5 LocalCommissioning onthe LMT (with theSeGW)


l The USB flash drive is unavailable or damaged, or eNodeBdeployment using the USB flash drive fails.

l The eNodeB is relocated with permissible downtime less than 1hour.

l The SeGW is deployed in the network.

CAUTIONIf you select the local commissioning, ensure that you have all required items, such as a laptop,the software package of the target version, the license file, a USB flash drive and referencedocuments before starting commissioning. For details about the required items, see the sectionon preparations for the commissioning mode used.

eNodeBCommissioning Guide 2 Commissioning Mode


9

3 eNodeB Commissioning Procedures

About This Chapter

This chapter describes the following procedures: plug and play (PnP) remote commissioning,local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioningon the LMT.

3.1 Overview of eNodeB Automatic DiscoveryDuring eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM)channel with the M2000 using automatic discovery.

3.2 PnP Remote CommissioningTo commission an eNodeB, you need to enable the plug and play (PnP) function of the eNodeBon the M2000 client. After the faults (if any) occurred during automatic commissioning arerectified and the commissioning procedure is complete, the eNodeB can work properly.

3.3 Local Commissioning Using a USB Flash DriveTo perform local eNodeB commissioning using a USB flash drive, you need to upgrade theeNodeB software and data configuration files using a Universal Serial Bus (USB) flash drive,and check the running status of indicators on the eNodeB. Then, create an eNodeBcommissioning task on the M2000.

3.4 Local Commissioning on the LMT (Without the SeGW)To commission an eNodeB on local using a local maintenance terminal (LMT), you need toupgrade the eNodeB software, download the configuration files, commission the antenna linedevices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish theoperation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000server.

3.5 Local Commissioning on the LMT (with the SeGW)To commission an eNodeB on local using a local maintenance terminal (LMT), you need toupgrade the eNodeB software, download the configuration files, commission the antenna linedevices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish theoperation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000server.

eNodeBCommissioning Guide 3 eNodeB Commissioning Procedures


10

3.1 Overview of eNodeB Automatic DiscoveryDuring eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM)channel with the M2000 using automatic discovery.

Introduction to the Automatic Discovery ProcessAutomatic discovery is a process during which the eNodeB is powered on and sets up an OMchannel with the M2000 after the hardware is installed, without manual intervention.

If the eNodeB and the Dynamic Host Configuration Protocol (DHCP) server are deployed ondifferent network segments, you are required to configure the router closest to the eNodeB onthe path between the eNodeB and the DHCP server as a DHCP relay. Configure the IP addressof the DHCP server for the M2000 as the DHCP relay address.

NOTEIf the M2000 server is deployed by using Server Load-Sharing (SLS), the previous IP address of the M2000DHCP server refers to the IP address of the master M2000 server.

eNodeB Automatic Discovery ProcessThe eNodeB automatic discovery process varies according to the commissioning scenario.

eNodeB Automatic Discovery During PnP Remote Commissioning

Figure 3-1 shows the eNodeB automatic discovery process in this scenario. The process is asfollows:

1. The eNodeB performs power on self-test (POST).2. The eNodeB learns virtual local area networks (VLANs) and obtains VLAN IDs (in VLAN

networking scenarios).3. The eNodeB sends a DHCP request to the DHCP server of the M2000. The DHCP server

binds the eNodeB and the M2000 using the ESN, deployment ID, or GPS information.After the binding, the DHCP server delivers information to the eNodeB. The informationincludes the OM IP address, M2000 IP address, OM IP address mask, and M2000 IP addressmask. For details about the three binding modes, see 4.6 Binding Modes Between theM2000 and the eNodeB.

4. The eNodeB sets up an OM channel with the M2000 after receiving a response to the DHCPrequest from the M2000.

5. The eNodeB downloads and activates the eNodeB software and configuration files fromthe M2000.

NOTE

l When the M2000 server is deployed by using SLS, if you want to create an eNodeB on the masterserver, the IP address of the M2000 refers to the IP address of the master server; if if you want to createan eNodeB on the slave server, the IP address of the M2000 refers to the IP address of the slave server.

l Check DHCP message in the following ways:

l Log in to the LMT and create a PnP tracing task on the LMT. For details, see eNodeB LMT UserGuide.

l Log in to the M2000 client, choose Configuration > DHCP Configuration Management. TheDHCP Configuration Management tab page is displayed. In the Server Information area onthe DHCP Configuration Management tab page, check the DHCP message.



11

Figure 3-1 eNodeB automatic discovery during PnP remote commissioning

eNodeB Automatic Discovery During Local Commissioning Using a USB Flash Drive

Figure 3-2 shows the eNodeB automatic discovery process in this scenario. The process is asfollows:

1. Insert the commissioning USB flash drive into the USB port on the eNodeB.2. The eNodeB performs power on self-test (POST).3. The eNodeB reads and activates the eNodeB software and configuration files in the USB

flash drive, and then automatically resets.4. The eNodeB sets up an OM link with the M2000.

Figure 3-2 eNodeB automatic discovery during local commissioning using a USB flash drive

Figure 3-3 shows a typical commissioning scenario without the SeGW deployed in the network.The eNodeB, mobility management entity (MME), serving gateway (SGW), and M2000 candirectly communicate with each other.



12

Figure 3-3 Commissioning scenario without the SeGW

3.2 PnP Remote CommissioningTo commission an eNodeB, you need to enable the plug and play (PnP) function of the eNodeBon the M2000 client. After the faults (if any) occurred during automatic commissioning arerectified and the commissioning procedure is complete, the eNodeB can work properly.

3.2.1 Commissioning ProcedureThis section describes how to perform plug and play (PnP) remote eNodeB commissioning.

Figure 3-4 shows the procedure for PnP remote eNodeB commissioning.



13

Figure 3-4 Procedure for PnP remote eNodeB commissioning



14

Table 3-1 Commissioning procedure

Step

Operation Mandatory/Optional

1 Local andremotecooperativeoperations

Prepare for remote eNodeB commissioning using the PnP,which involves obtaining eNodeB information andcommissioning tools, and obtaining the eNodeB softwareand files required for automatic deployment. For details, see3.2.2 Preparations.

Mandatory

2 Remoteoperationson theM2000

Create an eNodeB commissioning task on the M2000. Fordetails, see 3.2.3 Creating an eNodeB CommissioningTask.

Mandatory

3 Start the eNodeB commissioning task on the M2000. Fordetails, see 3.2.4 Starting an eNodeB CommissioningTask.

Mandatory

4 Monitor the eNodeB commissioning task on the M2000. Fordetails, see 3.2.5 Monitoring eNodeB Commissioning.

Mandatory

5 After eNodeB commissioning is complete, confirm theeNodeB commissioning task. For details, see 3.2.6Confirming eNodeB Commissioning Completion.

Mandatory

6 Check the eNodeB commissioning report for the eNodeBoperating status, and rectify the faults indicated in theeNodeB commissioning report if any. For details, see 3.2.7Checking the Running Status of the eNodeB on theM2000.

Mandatory

7 Commission the antenna system on the M2000. For details,see 3.2.8 Commissioning the Antenna System on theM2000.

Optional


After the environment monitoring equipment is connected,commission the equipment so that it operates properly. Fordetails, see 3.2.9 Commissioning the EnvironmentMonitoring Equipment on the M2000.

Optional


Set the maximum transmit power of RRUs or RFUs on theM2000. RRU and RFU are short for remote radio unit andradio frequency unit, respectively. For details, see 3.2.10Setting the Maximum Output Power for RRUs orRFUs.

Optional


Verify the basic services of the eNodeB. For details, see3.2.11 Testing the Basic Services of the eNodeB.

Optional



15

Step

Operation Mandatory/Optional


After eNodeB commissioning is complete and the eNodeBstarts to provide services properly, set the eNodeB to thenormal state on the M2000. For details, see 3.2.12 Settingan NE to the NORMAL Mode.

Mandatory

NOTEAfter an eNodeB is deployed, local engineers can determine whether the eNodeB is working properly byobserving the indicators on eNodeB boards. For details about the indicator descriptions and operations forrectifying possible faults, see 4.3 Checking the Status of Indicators.

3.2.2 PreparationsTo commission an eNodeB in PnP remote commissioning mode, you need to collect relatedeNodeB information, obtain commissioning tools, and upload the required files. When thesecurity gateway (SeGW) is deployed, prepare the bearer network by referring to TransmissionSecurity Feature Parameter Description.

Context

Figure 3-5 shows the procedure for preparing for PnP remote eNodeB commissioning.

Figure 3-5 Procedure for preparing for PnP remote commissioning



16

Obtaining eNodeB Information and Commissioning ToolsBefore PnP remote eNodeB commissioning, you must obtain eNodeB information andcommissioning tools.

Procedure

Step 1 Collect the information related to the eNodeB, as described in Table 3-2.

Table 3-2 Information related to the eNodeB

Item Source or Remarks

eNodeB name Planned by the operator.

Deployment ID Planned by the operator.

eNodeB electronicserial number (ESN)NOTE

The ESN information isoptional and it iscollected only inscenarios where theESN is used to bind theeNodeB.

ESN identifies an NE uniquely. During network deployment, theinstallation engineer reports the mapping relationship between thelocation of each site and the ESN to the staff at the maintenancecenter.The ESN is attached to the baseband unit (BBU) in the followingtwo ways:l If the fan module on the BBU is not attached with a label, the

ESN is printed on the mounting ear of the BBU, as shown inFigure 3-6. Record the ESN and the site information and thenreport them to the operation and maintenance (OM) personnel.

l If the fan module on the BBU is attached with a label, the ESNis printed on the label of the fan module and the mounting ear ofthe BBU, as shown in Figure 3-7. You must remove the label torecord the site information on the side labeled Site on the label.Then, report the information to the OM personnel.

Figure 3-6 Location of the ESN (I)



17

Figure 3-7 Location of the ESN (II)

Step 2 Obtain the tools required for the remote commissioning on the M2000, as described in Table3-3.

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

Tool Description

Testing UE The testing UE is functional and is registered in the home subscriberserver (HSS).

----End

Preparing an eNodeB Deployment ListYou need to prepare an eNodeB deployment list before uploading relevant data files.

Prerequisitesl You have logged in to the M2000 client if you need to export the eNodeB deployment list

from the M2000 client.l You have obtained planned data for eNodeB deployment from network planning engineers.

Procedure

Step 1 Obtain the deployment list.



18

Option Description

Deployment listsare exportedfrom the CME

If the CME has been deployed and you have initially configured theeNodeB on the CME, it is recommended that you use the CME to exportthe eNodeB deployment list. For detailed operations, see Exporting AutoDeployment Configuration Files in M2000 Help.

Obtain and open the exported deployment list. Check whether the softwareversion, cold patch, and hot patch are consistent with planned ones. If theyare inconsistent, you need to change them as planned. In addition, you needto enter other relevant data.

NOTEThe deployment list must be exported from the CME V200R012C00 or laterreleases.

Deployment listsare exportedfrom the M2000client

If the CME has not been deployed, you can export the eNodeB deploymentlist from the eNodeB Auto Deployment window on the M2000 client.

1. Choose Configuration > Auto Deployment > eNodeB AutoDeployment from the main menu of the M2000 client. The eNodeBAuto Deployment window is displayed.

2. Click . The Save dialog box is displayed.3. Specify a save path and click Save.4. Open the exported deployment list and enter or modify relevant data

based on the planned data that is confirmed with the network planningengineers.

NOTEl An eNodeB deployment list is in CSV format and its default name is

eNodeB_Auto_Deployment_List.csv. You can enter or modify relevant databased on the planned data that is confirmed with the network planning engineersby referring to Parameters for the eNodeB Deployment List.

l If there is a commissioning task in the commissioning task list, you can exportthe available deployment list and modify it based on the planned data.

l If there is no commissioning task in the commissioning task list, you can exportan empty deployment list and enter information based on the planned data.

Before the deployment, check whether the planned target version is consistent with the targetversion in the deployment list.l If they are consistent, use this deployment list to proceed with the deployment.l If they are inconsistent, change the target version in the deployment list to the planned target

version. The following uses eNodeB commissioning as an example.– If the planned target version is V100R003C00SPCXXX, edit the eNodeB Software

Version field.– If the planned target version is V100R003C00SPHXXX, edit the eNodeB Hot Patch

Version field. In the eNodeB Software Version field, you must enter the correspondingV100R003C00SPCXXX.



19

NOTE

l XXX consists of three digits, indicating the version number.

l Currently, the parameter for the cold patch version in the deployment list is not used.

l When you manually fill in or modify the deployment list, ensure that all the characters you enterare valid. The commissioning may fail if you enter invalid characters such as comma (,) andquotation mark (") or press Enter during deployment list modification.

----End

Uploading Data Files

Upload data files that are required for procedures of eNodeB commissioning. Data files requiredfor procedures of eNodeB commissioning tasks are NE software versions, cold patches, hotpatches, configuration data files, deployment lists, RET antenna software versions andconfiguration data files, RET antenna templates, and commissioning licenses.

PrerequisitesYou have logged in to the M2000 client.

Context

You need to upload data files in the following scenarios:

l Prepare for the commissioning.

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

l The commissioning cannot be started because certain required data files are unavailable.

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

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

Table 3-4 File save paths

File Type Save Path

Softwareversion orcold patch

/export/home/sysm/ftproot/eNodeB Type/Software/eNodeB SoftwareVersion/

Hot patch /export/home/sysm/ftproot/eNodeB Type/Patch/eNodeB Patch Version/

Configuration data file

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

Deployment list

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



20

File Type Save Path

RETantennasoftwareversion andconfiguration data file

/export/home/sysm/ftproot/OutSourcing/RETFile/

RETantennatemplate

/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/RETTemplate/

Commissioning license

/export/home/sysm/ftproot/adn/YYMMDD/CommissionLicense/

Procedure

Step 1 Choose Configuration > Auto Deployment > eNodeB Auto Deployment from the main menuof the M2000 client. The eNodeB Auto Deployment window is displayed.

Step 2 Click Prepare File&Data. The window for preparing files and data is displayed. Upload datafiles as required.



21

If youneed to...

Then...

Upload NEsoftwareversions

l Upload one by oneOne or multiple software versions corresponding to a certain NE type areuploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS

Client to OSS Server. The NE File Transfer dialog box is displayed.2. Select an NE type from the NE Type drop-down list and select

Software from the File Type drop-down list.

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

4. Click OK to close the NE File Transfer dialog box. The system startsuploading the data files.The data file preparation window displays the following detailedinformation about the operations at the bottom of the window:Operation, Status, Source File Path, Destination File Path, andProgress.

5. When Progress is 100%, the software versions are uploaded.l Upload in batches

One or multiple software versions corresponding to one or multiple NE typesare uploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS

Client to OSS Server. The NE File Transfer dialog box is displayed.

2. Click in the lower left corner of the dialog box, select an NE typefrom the NE Type drop-down list, and select Software from the FileType drop-down list.


4. Repeat the preceding two steps to select one or multiple filescorresponding to multiple NE types. The selected files are displayed inthe Source Path area.

5. In the Source Path area, select one or multiple files and click Add. Thefiles to be uploaded are displayed in the lower part of the dialog box.

6. Click OK to close the NE File Transfer dialog box. The system startsuploading the data files.The data file preparation window displays the following detailedinformation about the operations at the bottom of the window:



22

If youneed to...

Then...

Operation, Status, Source File Path, Destination File Path, andProgress.

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

When uploading an NE software version, if the client displays a message indicating thatthe NE software version supports multiple types of base stations in the same mode, youneed to upload the version only once for a base station. Then, the other types of basestations in the same mode can use the uploaded NE software version.



23

If youneed to...

Then...

Uploadcoldpatches

l Upload one by oneOne or multiple cold patches corresponding to a certain NE type are uploadedat a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS





5. When Progress is 100%, the cold patches are uploaded.l Upload in batches

One or multiple cold patches corresponding to one or multiple NE types areuploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS









24

If youneed to...

Then...


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



25

If youneed to...

Then...

Upload hotpatches

l Upload one by oneOne or multiple hot patches corresponding to a certain NE type are uploadedat a time.1. On the Hot Patch tab page, choose Transfer > From OSS Client to OSS

Server. The NE File Transfer dialog box is displayed.2. Select an NE type from the NE Type drop-down list and select




5. When Progress is 100%, the hot patches are uploaded.l Upload in batches

One or multiple hot patches corresponding to one or multiple NE types areuploaded at a time.1. On the Hot Patch tab page, choose Transfer > From OSS Client to OSS

Server. The NE File Transfer dialog box is displayed.








26

If youneed to...

Then...


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

Uploadconfiguration datafiles

1. On the NE Configuration Data tab page, choose Transfer > From OSSClient to OSS Server. The Upload NE Configuration Data dialog box isdisplayed.

2. Select an NE type from the NE Type drop-down list.

3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select the folder where the configuration data file that you wantto upload is stored, click Select. The Upload NE Configuration Data dialogbox is displayed.CAUTION

The path for saving the eNodeB configuration data file to be uploaded must be ..\eNodeBName\M2000.XML on the local PC. An eNodeBName folder contains onlyone XML file. To upload eNodeB configuration data files, you must select theeNodeBName folder where the files are stored. You can select multipleeNodeBName folders at a time.

The save path for the files to be uploaded to the server is displayed in the DestinationPath area. You can only view the path.

Uploaddeployment lists

1. On the Deployment List tab page, choose Transfer > From OSS Client toOSS Server. The Upload Deployment List dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload Deployment List dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload Deployment List dialog box. The system startsuploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the deployment lists are uploaded.NOTE

If the CME is not deployed, you can click Export Template to export an emptydeployment template, fill out the template based on the planned data, and upload thetemplate. The default names of the exported empty deployment list templates are thesame. Therefore, you are advised to change the template names after filling out thesetemplates.



27

If youneed to...

Then...

UploadRETantennasoftwareversionsandconfigurati

l Upload one by oneOne or multiple RET antenna software versions and configuration data filescorresponding to a certain NE type are uploaded at a time.1. On the RET tab page, choose Transfer > From OSS Client to OSS





5. When Progress is 100%, the RET antenna software versions andconfiguration data files are uploaded.

l Upload in batchesOne or multiple RET antenna software versions and configuration data filescorresponding to one or multiple NE types are uploaded at a time.1. On the RET tab page, choose Transfer > From OSS Client to OSS






6. Click OK to close the NE File Transfer dialog box. The system startsuploading the data files.



28

If youneed to...

Then...

on datafiles

The data file preparation window displays the following detailedinformation about the operations at the bottom of the window:Operation, Status, Source File Path, Destination File Path, andProgress.


UploadRETantennatemplates

1. On the RET Template tab page, choose Transfer > From OSS Client toOSS Server. The Upload RET Template dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload RET Template dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload RET Template dialog box. The system startsuploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the RET antenna templates are uploaded.NOTE

If the CME is not deployed, you can click Export Template to export an empty RETantenna template, fill out the template based on the planned data, and upload thetemplate.

Uploadcommissioninglicenses

1. On the Commission License tab page, choose Transfer > From OSS Clientto OSS Server. The Upload Commission License dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload Commission License dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload Commission License dialog box. The systemstarts uploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the commissioning licenses are uploaded.

----End



29

3.2.3 Creating an eNodeB Commissioning TaskThis section describes how to create an eNodeB commissioning task on the M2000 client aftercommissioning preparations are complete.

Prerequisitesl You have logged in to the M2000 client.l eNodeB commissioning preparations are complete.l If the M2000 is deployed in SLS mode, radio network planning engineers need to plan the

area to which the eNodeB belongs.l In scenarios without the SeGW, if the eNodeB and the M2000 server are deployed on

different network segments, you are required to configure the router closest to the eNodeBon the path between the eNodeB and the M2000 server as a Dynamic Host ConfigurationProtocol (DHCP) relay. Configure the IP address of the DHCP server for the M2000 as theDHCP relay address.

l In scenarios with the SeGW, if the eNodeB and the public DHCP server are deployed ondifferent segments, you are required to configure the router closest to the eNodeB on thepath between the eNodeB and the public DHCP server as a DHCP relay. Configure the IPaddress of the DHCP relay as the public DHCP server address, and the IP address of theDHCP server in scenarios with the SeGW as the IP address of the DCHP server for theM2000.

NOTEIn situations where the M2000 is deployed in SLS mode, the preceding DHCP server IP address of theM2000 refers to the host IP address.

Procedure


Step 2 Select deployment lists.

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

If you needto...

Then...

Import adeployment listfrom the server

Select From Server and choose a deployment list from the drop-down list box.

Import adeployment listfrom the client

Select From Client and click to select a deployment list.

3. (Optional) Select the area to which an eNodeB belongs in the Sub-area area. This step is

mandatory when theM2000 is deployed in SLS mode.

NEs belong to different areas when they are managed by different M2000 servers. If theM2000 is deployed in SLS mode, NEs are managed by different servers. On the CME client,



30

these NEs belong to different areas. Select the active or slave M2000 server that the NEbelongs to based on the planned data. Configure the data as follows:l If the NE was created on the active M2000 server, set the PEERIP parameter for the

OMCH to the IP address of the active M2000 server.l If the NE was created on the slave M2000 server, set the PEERIP parameter for the

OMCH to the IP address of the slave M2000 server.l Set the Destination IP parameter for the IP router from the NE to the M2000 server to

an IP address on the the network segment where the M2000 server is located.

NOTEOnsite deployment engineers need to perform operations based on the areas that have been plannedfor eNodeBs by radio network planning engineers.

l If eNodeBs belong to one area, import one deployment list to create eNodeBs in batches.

l If eNodeBs belong to different areas, import multiple deployment lists by area to create eNodeBs.

4. In NE Connection Mode, set a mode for connecting the M2000 and NEs.

Modes for connecting the M2000 and NEs are as follows:l Common Connection: Security authentication is not performed between the M2000

and the NE.l SSL Connection: Security authentication is performed between the M2000 and the NE.

After security authentication is passed, a secure connection can be established, therebyensuring communication security and integrity. If this mode is selected, you also needto set an authentication mode. Authentication modes are Anonymous Authority andOSS Authentication NE, where Anonymous Authority is the default authenticationmode.

NOTETo enable automatic SSL connection during NE deployment, you need to set the authentication modefor NE in advance on the CME in addition to setting the connection mode between the M2000 andNEs in this step.

Step 3 Click OK. The system starts the import.

After the import is complete, the M2000 checks for mandatory parameters with empty valuesand invalid NE configuration data. In addition, the information indicating whether the importsucceeded or failed is displayed on the Operation Information tab page.

l If the import is successful, the M2000 automatically creates a commissioning task for eacheNodeB. The imported eNodeB deployment lists are displayed on the Deployment List tabpage.

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

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

NOTEYou can check whether the parameters in eNodeB deployment lists can be modified by referring toParameters for the eNodeB Deployment List.

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

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



31

a. Click in the ESN value cell. The Bind ESN dialog box is displayed.b. Select an ESN that is not bound, and click OK to return to the Deployment

Parameter dialog box.

NOTE

You can change the ESNs before OM links are established between NEs and the M2000.

2. The changed parameter values are displayed in the commissioning task window andhighlighted in red.

----End

3.2.4 Starting an eNodeB Commissioning TaskThis section describes how to start an eNodeB commissioning task. After creating an eNodeBcommissioning task, you can set commissioning procedures and start the task. Then, theM2000 automatically commissions the eNodeB.

Prerequisitesl You have logged in to the M2000 client.l eNodeB commissioning tasks have been started.

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

Procedure


Step 2 On the Deployment List tab page, right-click one or multiple commissioning tasks and chooseStart from the shortcut menu. The Task Settings dialog box is displayed.

Step 3 Select steps in the Select column based on the actual plan.

NOTE

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

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

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

For details about commissioning procedures and steps, see Table 3-5.



32

Table 3-5 Description of commissioning process

No. Procedure

Step Description

1 AutoDiscovery

Check OMchannel

When connection of the transport network isproper, the M2000 automatically sets up an OMchannel to connect to the desired eNodeB basedon the deployment list, and commissions andmaintains the NodeB through this channel.

Wait for manualoperation

After the OM channel is set up, the status of thecommissioning task changes to Waiting formanual operation. Manually confirm thecompletion and proceed with the commissioningafter the commissioning environment of thenetwork is ready.

2 AutoConfiguration

Downloadsoftware

The M2000 automatically checks whether thecurrent eNodeB version is the same as the targetsoftware version given in the deployment list. Ifthe versions are not the same, the M2000automatically downloads software from theserver to the eNodeB.

Downloadconfiguration

The M2000 downloads the desired configurationfile from the server to the eNodeB based on thetarget version information.

Activate Activate the eNodeB configuration data (takeseffect after next reset) and then activate thesoftware (automatic reset).

3 AutoPlanning

Auto Planning Only the BTS3202E is supported in eNodeB autodeployment.

4 Uploadcommissioninglicense

Distributecommissioninglicense

When some eNodeB functions are restrictedbecause the eNodeB uses the default license upondelivery, you need to install a commissioninglicense. The commissioning license has timerestriction. You need to replace thecommissioning license with the commercial oneas soon as possible after the eNodeBcommissioning is complete.



33

No. Procedure

Step Description

5 Commission RET

Upgrade RETsoftware version

The target RET antenna software version isprovided by antenna line device (ALD) suppliersand saved on the local PC.l RET antennas managed by eNodeBs on the

sites must be commissioned.l If an eNodeB and a NodeB share antennas and

the antennas are managed by the NodeB, youdo not need to commission the RET antennas.

l When antennas are managed by themanagement system of a third party, you donot need to commission RET antennas.

Upgrade RETconfiguration

The RET antenna configuration file is providedby ALD suppliers and saved on the local PC. RETantenna configuration data may vary according toRET antenna types and suppliers.

Tune RET Check whether RET antennas are commissionedcorrectly during the commissioning.

6 Test andmonitor

Test installation& deploymentquality

Services carried on the RF module will beinterrupted during operation. If an RF module isshared by base stations of different RATs,services of the other RAT will also be interrupted.The check may take several minutes. The projectquality check involves the VSWR, offlineintermodulation interference, and crossed pair.

Monitor cellservice status

Check whether any active cells exist under theeNodeB.You can monitor alarms of the eNodeB on theM2000 during software commissioning to locateand handle exceptions in time.

7 PerformNHC

Perform NHC You can perform health check to learn theeNodeB operating status.

8 Wait forconfirmation

Wait forconfirmation

After service verification is complete, thecommissioning task is in the Waiting forConfirmation state. You need to manuallyconfirm that the commissioning is complete.



34

NOTE

The system checks whether all configured RF modules are usable before starting project quality check.

l If all configured RF modules are usable, the system issues project quality check commands to proceedwith subsequent operations.

l If only some configured RF modules are usable, the system sets a timer (2.5 minutes in length and amaximum of 5 times) to wait until all RF modules are usable. After all RF modules are usable, thesystem issues project quality check commands to proceed with subsequent operations. If some RFmodules are still unusable after the timer expires, the system ends the project quality check task.

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

If... Then...

Not all therequired datafiles are available

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

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

l : Indicates that not all the required data files are available.2. Click OK. The Data Preparation Check dialog box is closed.3. Obtain relevant data files based on the check results.

For detailed operations, see Uploading Data Files.4. After the required data files are uploaded, start the commissioning

tasks again.

All the requireddata files areavailable

The M2000 starts commissioning. The selected commissioning tasks enterthe Running state.NOTE

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

----End

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

Viewing Progress and Status of eNodeB Commissioning Tasks

This section describes how to view progress and status of eNodeB commissioning tasks on theM2000 to learn about process of the tasks.

Prerequisitesl You have logged in to the M2000 client.

l eNodeB commissioning tasks have been started.



35

Contextl By default, the GUI displays only commissioning tasks created by a specific user. To view

commissioning tasks created by other users, click on the toolbar.l When the system performs NE upgrades during the automatic configuration phase of a

commissioning task, if you restart or delete the commissioning task, the system does notrestart NE upgrades but proceeds until the related NE upgrade task is complete. When thesystem displays The NE is performing the following task: ******. Please try later. inDescription for a commissioning task, the NE upgrade task is running. If you want toperform automatic deployment again, wait until the NE upgrade task is complete. You canchoose Software > NE Upgrade Task Management > NE Upgrade Task to query theNE upgrade task.

Procedure


Step 2 View the status and progress of commissioning tasks in the commissioning task list.TIP

You can quickly view the status of commissioning tasks by using either of the following methods:

l In the commissioning task list, the status of the tasks is displayed in Status, the current procedures aredisplayed in Current Phase, and details about each procedure are displayed in Description.

l In the commissioning task list, select one or multiple commissioning tasks whose status you want to

view, and then click . The right pane displays execution status ofsteps for commissioning procedures.

The displayed information includes the execution status, description, start time and end time of eachcommissioning substep.

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

----End

Handling eNodeB AlarmsThis section describes how to handle eNodeB alarms. After eNodeB software is automaticallyupgraded, you can use the M2000 to view alarms on eNodeBs. All alarms related to eNodeBsare categorized by object to help you query required alarms.

Prerequisitesl You have logged in to the M2000 client.l Software commissioning monitoring has already started, and the completion of the

commissioning has not yet been confirmed.

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



36

Procedure


Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you wantto handle alarms. Right-click the tasks, and then choose Open Monitor Window from theshortcut menu. The alarm monitoring window is displayed.

In the displayed window, you can view alarms on eNodeBs by monitored object. For detailsabout the alarm monitoring window, see Interface Description: eNodeB CommissioningWindow.

Step 3 Handle alarms.1. Double-click an alarm that you want to handle.2. In the displayed dialog box that shows the alarm details, click the link in Reason And

Advice.3. Handle alarms based on the alarm reference.

----End

Performing eNodeB Antenna Fault DiagnosisThis section describes how to perform antenna fault diagnosis. The M2000 provides automaticfault diagnosis to antennas. When errors occur during eNodeB commissioning, you can use theautomatic fault diagnosis function provided by the M2000 to check whether the eNodeB that isbeing commissioned is faulty. Then, you can take corresponding measures to rectify the faultsbased on the diagnosis results.

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

tasks has not yet been confirmed.

Context

CAUTIONeNodeB services are interrupted upon antenna fault diagnosis. Therefore, you need to performthe diagnosis when the eNodeB is not providing services or the services are isolated.

eNodeB fault diagnosis aims to check whether antennas are functioning normally. It involvesthe VSWR test, offline intermodulation interference test, and crossed pair test.

After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task anddisplays the diagnosis progress. After the fault diagnosis is complete, you can obtain the faultdiagnosis report.

If you delete a fault diagnosis task, the corresponding diagnosis report is deleted accordingly.If you restart the M2000 server, all fault diagnosis tasks and reports are deleted.



37

Procedure



Step 3 Perform fault analysis on antenna alarms.1. Select an object (antenna) from the left pane of the displayed window, or select a specific

alarm of the object (antenna) from the alarm list in the right pane, right-click the object oralarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settingsdialog box is displayed.

2. Select an eNodeB in the Select NE area, select a diagnosis type in the Select diagnosetype area, type diagnosis parameters in the Type diagnosis parameters area, and thenclick OK. The dialog box for confirming the diagnosis is displayed.

3. Click Yes. The system starts the fault diagnosis.

During the fault diagnosis, a diagnosis task is added to the diagnosis task list.

NOTEFault diagnosis may take a long time when there are a large number of detection services executedby the detection script and there are a large number of NE configuration services.

4. After fault diagnosis is complete, you can right-click a diagnosis task in the diagnosis tasklist, and choose Diagnose Report from the shortcut menu to view diagnosis results.

----End

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

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

ContextFor details about operations on commissioning tasks, see Table 3-6.

Table 3-6 Operations on commissioning tasks

Operation

Description

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

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

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



38

Operation

Description

Resume

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

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

Procedure


Step 2 On the Deployment List tab page, select one or multiple commissioning tasks and performoperations as required.

If youneed to...

Then...

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

Pause Right-click the tasks and choose Pause from the shortcut menu. The tasks arein the Paused state.

Resume Right-click the tasks and choose Resume from the shortcut menu. The tasksproceed from where they are paused.

Cancel Right-click the tasks and choose Cancel from the shortcut menu. The tasksreturn to the Wait for Start state.

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

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

----End

3.2.6 Confirming eNodeB Commissioning CompletionWhen the status of an eNodeB commissioning task changes to Waiting for Confirmation, youneed to confirm that the eNodeB commissioning is complete.

Prerequisitesl The eNodeB is properly connected to the M2000.l The status of the eNodeB commissioning task is Waiting for Confirmation.



39

Procedure

Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB AutoDeployment. The eNodeB Auto Deployment tag page is displayed.

Step 2 Right-click one or more eNodeB commissioning tasks to be confirmed from the commissioningtask list, and choose Confirm Completion from the shortcut menu.

----End

3.2.7 Checking the Running Status of the eNodeB on the M2000This section describes how to perform the health check and alarm check on the eNodeB throughthe M2000.

Obtaining eNodeB Commissioning ReportsThis section describes how to obtain eNodeB commissioning reports. An eNodeBcommissioning report records the details about user operations, commissioning results, errorinformation, and health check report. You can obtain the report of eNodeB commissioning taskswhen the tasks are in progress and archive the report when the tasks are complete.

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

ContextThe exported commissioning report records the information about only the selectedcommissioning tasks. After you manually delete a commissioning task, the generatedcommissioning report does not contain the information about this task.

The deployment report can be stored for a maximum of 30 days. The start date is specified asthe date when the deployment report is generated for the first time.

Procedure


Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you wantto export the report, right-click the tasks, and then choose Export Deployment Report fromthe shortcut menu. A dialog box is displayed, asking you whether to export alarm data at thesame time.

If... Then...

You need to export alarm data Click Yes. The Save dialog box is displayed.

You do not need to export alarm data Click No. The Save dialog box is displayed.

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



40

You can customize a filename for the commissioning report. If you do not specify the filename,the M2000 names and saves the file based on the naming conventioneNodeB_Auto_Deployment_Report.zip. For example,eNodeB_Auto_Deployment_Report.zip.

Step 4 (Optional) Decompress the generated report file. In the decompressed folder, double-clickeNodeB_Auto_Deployment_Report_index.html to view the commissioning report.

If you choose to export alarm data at the same time in Step 2, the file containing the alarm datais saved in the alarm sub-folder.

----End

Rectifying Faults and Clearing Alarms Against the eNodeB Health Check Report

This section descries how to rectify faults and clear alarms against the eNodeB health checkreport to ensure that the eNodeB runs properly.

PrerequisitesThe eNodeB commissioning report is available.

Context

Table 3-7 shows the eNodeB health checklist.

Table 3-7 eNodeB health checklist

Item Subitem Description

eNodeB softwareversion

eNodeB software status Check the operating status of theeNodeB software.

eNodeB software versioninformation

Check the information about therunning eNodeB softwareversion.

Environment status RRU temperature Check the RRU temperature.

Environment temperature andhumidity

Check the environmenttemperature and humidity.

eNodeB type eNodeB type Check whether the eNodeB typeis correct in the dataconfiguration.

Configuration data Configuration data consistency Check whether the effective dataapplied to modules is consistentwith the configured data in thedatabase.

Active alarms Check for the active alarmsreported by an NE.

Cell status Cell status Check the cell status.



41


MBTS alarmsNOTE

This item is notrequired for a single-mode eNodeB.

Inter-RAT communicationalarms

Check the status of inter-RATcommunication.

Inter-RAT BBU board parametersettings conflict alarms

Check whether inter-RATparameter settings are consistentfor BBU boards.

Inter-RAT cabinet configurationconflict alarms

Check whether inter-RATconfigurations are consistent forcabinets.

Inter-RAT monitoring deviceparameter settings conflictalarms

Check whether inter-RATparameter settings are consistentfor monitoring devices.

Inter-RAT board objectconfiguration conflict alarms

Check inter-RAT configurationsare consistent for board objects.

Inter-RAT RF unit parametersettings conflict alarms

Check whether inter-RATparameter settings are consistentfor RF units.

Inter-RAT site-levelconfiguration conflict alarms

Check whether inter-RATconfigurations are consistent forsites.

Inter-RAT control rights conflictalarms

Check whether inter-RATcontrol rights are consistent.

RF unit working mode and boardcapability mismatch alarms

Check whether the workingmode for the RF unit matches theboard capability.

Hardware status CPU usage Check the CPU usage.

Transmit channel status Check the status of the transmitchannel.

Receive channel status Check the status of the receivechannel.

RRU status Check the status of an RF unit.

Memory usage Check the memory usage.

Flash memory usage Check the usage of the flashmemory.

Board status Check the status of a board.

Interface status X2-interface link Check the status of the X2interface and the informationabout the peer eNodeB.



42


S1-interface link Check the parameters for the S1interface and the informationabout the MME.

GE/FE port status Check the parameter settings forthe Ethernet port.

E1/T1 port status Check the parameter settings forthe E1/T1 port.

Remote maintenance channelstatus

Check the parameter settings forall remote maintenance channelsof the eNodeB.

SCTP link status Check the parameter settings forthe SCTP link.

IP path status Check the parameter settings foran IP path.

CPRI port status Check the parameter settings forthe CPRI port.

Clock status Clock status Check the status of the currentclock in the basic cabinet,including the reference clock,clock quality, clock priority,clock working mode, and statusof the phase-locked loop.

Procedure

Step 1 Open the eNodeB commissioning report and view the health check report to determine theeNodeB operating status.

Step 2 Check the health check report for faults and alarms, and rectify the faults and clear the alarmsby referring to eNodeB Alarm Reference. If all the alarms are cleared but the eNodeB does notwork properly, contact Huawei for technical support.

Step 3 Check for eNodeB alarms.

You can check for eNodeB alarms using one of the following methods:l on the M2000 client, choose Monitor > Browse Current Alarm. Set the search criteria in

the displayed Filter dialog box to check for eNodeB alarms. For details, see Browse CurrentAlarm in the M2000 Online Help.

l On the M2000 client, choose Topology > Main Topology. On the Main Topology tab page,right-click the eNodeB and choose Query Alarm/Event > Current Alarm from the shortcutmenu. Then, double-click an alarm to view details

Step 4 Clear the alarms by taking recommended actions or by referring to eNodeB Alarm Reference.

----End



43

3.2.8 Commissioning the Antenna System on the M2000Commissioning the antenna system on the M2000 includes commissioning the remote electricaltilt (RET) and tower-mounted amplifier (TMA).

(Optional) Commissioning the RET Antenna on the M2000

This section describes how to use MML commands to commission the remote electrical tilt(RET) antenna on the M2000. If tasks for RET commissioning in the commissioning phase arenot selected on the M2000, the M2000 does not perform RET commissioning after thecommissioning phase starts. In this case, you need to use MML commands to commission theRET antenna.

Prerequisitesl The antenna line device (ALD) is installed correctly.

l The LMT communicates with the eNodeB properly.

l The RET software and data configuration file are available.

l The FTP server functions properly and is connected to the eNodeB correctly.

l Each FTP user has the permission to read a specified folder.

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

Context

l Commissioning the RET antenna includes downloading the RET software and dataconfiguration file, calibrating the RET antenna, setting the RET downtilt, and query RETovercurrent or undercurrent alarms.

l The RET downtilt must be configured based on the planned network data. Otherwise, theRET downtilt affects antenna coverage.

Procedure

Step 1 Set the ALD power switch and overcurrent or undercurrent alarm thresholds.

If... Run...

The RET is connected using the RET port MOD RETPORT

The RET is connected using the antenna porton the RRU or RFU

MOD ANTENNAPORT

NOTEThe ALD power switch is OFF by default. Before using the RET, set the ALD power switch to ON andset current alarm thresholds. If the current exceeds the overcurrent or undercurrent alarm threshold, theALD power switch automatically turns off. This affects the subsequent RET commissioning.

Step 2 Scan the ALD connected to the RRU.MML command: SCN ALD



44

Step 3 Add an RET antenna.MML command: ADD RET

Step 4 Check whether the RET antenna is working. If the RET antenna is not working, contact Huaweifor technical support.MML command: DSP RETSUBUNIT

Step 5 Query the current RET software version of the ALD.MML command:DSP ALDVER

NOTE

You can set Operation Mode to SITE(Site) to query all ALD information.

If... Then...

The current RET softwareversion is the same as thetarget RET softwareversion

Record the device number of the RET antenna, and performStep 7 to download the RET data configuration file.

The current RET softwareversion is different from thetarget RET softwareversion

Record the device number of the RET antenna, and performStep 6 to download the RET software.

Step 6 Download the RET software.MML command: DLD ALDSW

If the eNodeB is configured with multiple RET antennas, repeat Step 6 to download the softwareof other RET antennas.

Step 7 Download the RET data configuration file supplied by the ALD vendor.1. Query the number of subunits for each RET antenna and record the query results.

MML command: DSP RET

The subunits of an RET antenna are numbered from 1 in ascending order. You mustdownload the data configuration file for each subunit.

2. Download the data configuration file for each subunit.MML command: DLD RETCFGDATA

If an RET antenna consists of multiple subunits or an eNodeB is configured with multipleRET antennas, repeat Step 7.2 to download the data configuration files for other subunits.

Step 8 Calibrate the RET antenna.MML command: CLB RET

NOTE

If the RET downtilt fails to be calibrated, check for the cabinet, subrack, and slot configurations and themapping between the RET antenna and the sector. If the configurations and mapping are incorrect, run theMOD RETSUBUNIT command to set them gain, and calibrate the RET downtilt again.If you run this command without specifying any parameters, RET antennas can be calibrated in batches.

Step 9 Set the RET downtilt.If the downtilt has been set in the data configuration file, perform Step 9.3 to check whether theRET downtilt is calibrated successfully.



45

1. Query the downtilt range supported by the RET antenna.MML command: DSP RETDEVICEDATA

2. Set the RET downtilt.MML command:MOD RETTILT

If multiple sectors are configured, repeat Step 9.1 and Step 9.2 to set the downtilts for otherRET antennas.

3. Query the current RET downtilt. If the queried downtilt is the same as the configureddowntilt, the RET downtilt is set successfully.MML command: DSP RETSUBUNIT

Step 10 Check whether overcurrent or undercurrent alarms are generated on the RET antenna. Ifovercurrent or undercurrent alarms are generated, clear them by referring to eNodeB AlarmReference.MML command: DSP RETPORT

----End

Commissioning the TMA on the M2000This section describes how to commission the tower-mounted amplifier (TMA) to check whetherthe current TMA software version is the same as the target TMA software version. If they aredifferent, load the target TMA software. After the TMA software is loaded, the TMAautomatically resets. The software then takes effect and the TMA starts working properly.

Prerequisitesl The TMA is installed correctly.l The TMA software has been uploaded to the M2000 server.l The eNodeB is properly connected to the M2000.l Each FTP user has the permission to read a specified folder.l The File Transfer Protocol (FTP) port has been enabled on the firewall between the eNodeB

and the M2000 server.

Contextl The FTP server transmits data in plaintext mode by default.l As a part of the antenna system, the TMA is used to amplify the received weak signals.l The TMA software is supplied by the antenna line device (ALD) vendor.l If incorrect TMA software is loaded, the TMA may not work property.

Procedure


If... Run...

The TMA is connected using the RET port MOD RETPORT

The TMA is connected using the antenna porton the RRU or RFU

MOD ANTENNAPORT



46

NOTEThe ALD power switch is OFF by default. Before using the TMA, set the ALD power switch to ON andset current alarm thresholds. If the current exceeds the overcurrent or undercurrent alarm threshold, theALD power switch automatically turns off. This affects the subsequent TMA commissioning.


Step 3 Add a TMA.MML command: ADD TMA

Step 4 Check whether the TMA starts working and whether the TMA gain is set correctly.MML command: DSP TMASUBUNIT

l If the maximum gain is the same as the minimum gain, the TMA has a fixed gain. In thissituation, you are not allowed to set any gains.

l If the TMA is not working, contact Huawei for technical support.

Step 5 Query the software version of the TMA to be commissioned.MML command: DSP ALDVER

NOTE


If... Then...

The current TMA softwareversion is the same as thetarget TMA softwareversion

Perform Step 8 to set the TMA gain as required, and performStep 9 to check whether the TMA generates overcurrent orundercurrent alarms.

The current TMA softwareversion is different from thetarget TMA softwareversion

Go to Step 6.

Step 6 Download the TMA software to be commissioned.MML command: DLD ALDSW

Step 7 If the eNodeB is configured with multiple TMAs, repeat Step 5 to download the software ofother TMAs.

Step 8 Set the TMA gain.MML command: MOD TMASUBUNIT

If the eNodeB is configured with multiple TMAs whose gains can be set, repeat this step to setthe gains for other TMAs.

Step 9 Check whether the TMA generates overcurrent or undercurrent alarms.MML command: DSP ANTENNAPORT



47

If the TMA generates overcurrent or undercurrent alarms, clear the alarms by referring to eNodeBAlarm Reference.

----End

3.2.9 Commissioning the Environment Monitoring Equipment onthe M2000

After the environment monitoring equipment is connected, you need to commission it so that itfunctions properly.

Setting Environment Alarm ParametersThis section describes how to set environment alarm parameters within the permissible rangeand add user-defined alarms as required.

Prerequisitesl The M2000 communicates properly with the eNodeB.l Environment monitoring devices have been configured.l The dual in-line package (DIP) switches on the environment monitoring device are properly

set. For details, see APM30H&TMC11H&IBBS200D&IBBS200T(Ver.B) ProductDescription, APM30H&TMC11H&IBBS200D&IBBS200T(Ver.C) Product Descriptionand EMUA User Guide.

ContextThe remote radio unit (RRU), universal power environment unit (UPEU) in the baseband unit(BBU), environment monitoring unit type A (EMUA), and power monitoring unit (PMU) in theAPM30H are all equipped with extended alarm ports. Setting environment alarm parametersincludes adding user-defined alarms and binding the user-defined alarms to the eNodeB.Environment alarms are used to monitor the equipment room where the eNodeB is located. Whensetting environment alarm parameters, you need to bind a user-defined alarm to the specificsubrack, slot, and port on the eNodeB.

Procedure

Step 1 Add a user-defined alarm.1. Choose Monitor > Alarm Setting > NE Alarm Settings.2. On the User-Defined Alarm tab page, click the Alarm Definition tab, and click Add. The

Add User-Defined Alarm dialog box is displayed, as shown in Figure 3-8.



48

Figure 3-8 Adding a user-defined alarm

3. Select an NE type on the left, and set the user-defined alarm parameters, including Alarm

Name, Alarm ID, Alarm Severity Level, and Alarm Type.NOTE

l Each type of user-defined alarm is allocated a unique alarm ID. The alarm ID ranges from 65033to 65233.

l The same type of alarm must use the same alarm ID for all eNodeBs. For example, if the doorstatus alarm ID for an eNodeB is 65035, the door status alarm IDs for other eNodeBs must alsobe 65035.

4. Click OK. The information about the added user-defined alarm is displayed in the NEAlarm Setting window.

5. Click Apply to save the user-defined alarm.A message is displayed, indicating that saving the user-defined alarm is successful or fails.

If saving the user-defined alarm is successful, click OK. The icon disappears. Ifsaving the user-defined alarm fails, click Details to view the failure cause and rectify thefault accordingly. Then, add the user-defined alarm again.

Step 2 Bind the user-defined alarm to the eNodeB.1. Choose Monitor > Alarm Setting > NE Alarm Settings.2. On the User-Defined Alarm tab page, click the Alarm Binding tab. Then, add the user-

defined alarm binding relationship.l Single binding

a. Choose Edit > Add. The Add Alarm Binding dialog box is displayed, as shownin Figure 3-9.

b. Select an NE from the Select NE navigation tree or enter an NE name in the Searchby name text box on the left. Select an alarm from the Select Alarm/Eventnavigation tree or enter an alarm name in the Search by name text box in the



49

middle. Select an alarm or event ID based on the NE type, and set bindingparameters, including port type, cabinet No., subrack No., and slot No. of the port,alarm voltage, and upper and lower alarm thresholds.

NOTEIf a digital port is used for the monitoring board, you must set alarm voltage to specify acondition for reporting alarms. If an analog port is used for the monitoring board, you mustset upper and lower alarm thresholds to specify a condition for reporting alarms.

c. Click OK. The information about the added user-defined alarm is displayed in theNE Alarm Setting window.

Figure 3-9 Adding alarm binding

l Batch binding

a. Choose Import/Export > Export Template. The Export Alarm BindingTemplate dialog box is displayed, as shown in Figure 3-10.Alternatively, choose Import/Export > Export to export the existing records onthe Alarm Binding tab page by NE type.

Figure 3-10 Exporting alarm binding template

b. In the displayed Export Alarm Binding Template dialog box, select the NE type,

and specify the save path and name for the exported template.



50

c. Open the template and edit it based on actual requirements by referring to theexample in the template.

d. Choose Import/Export > Import to import the edited template to the M2000.Then, 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 icon.3. Select an alarm binding relationship record and click Apply to apply it to the NE.

A message is displayed, indicating that applying the alarm binding relationship is successful

or fails. If applying the alarm binding relationship is successful, click OK. The icondisappears. If applying the alarm binding relationship fails, click Details to view the failurecause and rectify the fault accordingly. Then, apply the alarm binding relationship again.

----End

Checking for External Environment AlarmsThis section describes how to check for external environment alarms. After setting theparameters for environment alarms, you need to verify the parameter settings by checking forexternal environment alarms.

ContextYou can manually trigger several external environment alarms to verify the parameter settings.If external environment alarms can be reported, the parameter settings are correct.

Procedure

Step 1 Manually trigger several external environment alarms. For details, see the appendix TriggeringMonitoring Device Alarms.

Step 2 Check for the external environment alarms on the M2000. For details, see Rectifying Faultsand Clearing Alarms Against the eNodeB Health Check Report. If external environmentalarms can be reported, the parameter settings are correct. If no external environment alarm isreported, set the parameters again or contact Huawei for technical support.

----End

ExampleAssuming that a water sensor is installed for the fan monitoring unit (FMU), to check whetherthe parameter settings for water damage alarms are correct, perform the following operations:

1. Run the MOD FMU command with WS_DISABLE(Water-Immersed SensorDisabled) in Special Boolean Alarm Flag cleared.

2. Immerse the water sensor or its probe in water for more than 10s, and check whether waterdamage alarms are reported. If water damage alarms are reported, the parameter settingsare correct.

3.2.10 Setting the Maximum Output Power for RRUs or RFUsThis section describes how to set the maximum output power for remote radio units (RRUs) orradio frequency units (RFUs) according to the local regulations on power specifications.



51

Prerequisitesl The RRU or RFU is connected properly.l The local maintenance terminal (LMT) or M2000 communicates properly with the eNodeB.l You have logged in to the M2000 as administrator.

ContextThe maximum output power of the RRU or RFU is specified by the local operator.

If an eNodeB is configured with multiple RRUs or RFUs, you must use MML commands tomanually reset RRUs or RFUs one by one.

The maximum output power for the RRU or RFU needs to be set only if it is less than themaximum output power that the RRU or RFU can physically achieve.

Procedure

Step 1 Run the DSP RRU command to query the cabinet No., subrack No., slot No., and transmitchannel No. of the RRU or RFU.

Step 2 Run the DSP TXBRANCH command to query the maximum output power supported by theRRU or RFU based on the information queried in Step 1.

Step 3 Run the LOC RRUTC command to set the maximum output power for the RRU or RFU.

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

Step 5 Run the DSP TXBRANCH command to check whether the setting of the maximum outputpower for the RRU or RFU takes effect.

If... Then...

The maximum outputpower takes effect

No further action is required.

The maximum transmitpower fails to be set

Set the maximum output power within the power specificationssupported by the RRU or RFU. If the maximum output powerstill fails to be set, contact Huawei for technical support.

NOTEBefore returning a used but not faulty RRU or RFU to the Spare Parts Center, run the LOC RRUTCcommand to set the maximum output power (TXMAXPWR) to 0 and reset the RRU or RFU for the settingto take effect.

----End

3.2.11 Testing the Basic Services of the eNodeBThis section describes how to test the basic services of the eNodeB.

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



52

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.

Procedurel Test the web page browsing service.

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.

l Test the file uploading service.

Testing Method Access the FTP server and upload files through a UE. Perform thetest 10 times.

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

l Test the file downloading service.

Testing Method Access the FTP server and download files through a UE. Perform thetest 10 times.

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

l 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 noneof the calls get dropped till they are released. The voice is clear withno loud noise.

----End

3.2.12 Setting an NE to the NORMAL ModeAfter eNodeB commissioning is complete and the eNodeB starts to provide services properly,set the eNodeB to the normal state on the M2000.

Procedure

Step 1 Query the eNodeB state.1. On the M2000 tab page, choose Topology > Main Topology. The Main Topology tab

page is displayed.2. On the Main Topology tab page, select the target network element (NE) and right-click

Query Maintenance Mode. Then, the Query Maintenance Mode dialog box is displayed.



53

3. Check whether Current NE Maintenance Mode is set to NORMAL. If it is, theconfiguration is complete. If it is not, go to Step 2.

Step 2 Set the eNodeB state.1. On the M2000 tab page, choose Maintenance > Maintenance Mode. The Maintenance

Mode tab page is displayed.

2. Click Set NE Mode at the upper left corner of the Maintenance Mode tab page. TheSet Maintenance Mode dialog box is displayed.

3. Select the target NE and specify the time.4. Set NE Mode to NORMAL. The eNodeB is changed to the normal state.5. Click OK. The setting of the maintenance mode is complete.6. Ensure that the current the eNodeB state is NORMAL by executing Step 1 again.

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

----End

3.2.13 References to eNodeB CommissioningThis chapter describes references for commissioning eNodeBs, including introduction to thedeployment list, interface description, parameter description, and technical specifications.

Interface Description: eNodeB Commissioning WindowThis section describes the elements of the eNodeB Auto Deployment window and the functionof each element.

Main WindowFigure 3-11 shows the main window for eNodeB commissioning. Table 3-8 describes thewindow.



54

Figure 3-11 Main window for eNodeB commissioning

Table 3-8 Window description

AreaNo.

ElementName

Description

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

2 Commissioning task list

Displays all the commissioning tasks and their progress. You canright-click a task, and then choose the corresponding menu itemfrom the shortcut menu to perform an operation.NOTEl By default, the GUI displays only commissioning tasks created by a

specific user. To view commissioning tasks created by other users,

click on the toolbar.

l When the system performs NE upgrades during the automaticconfiguration phase of a commissioning task, if you restart or deletethe commissioning task, the system does not restart NE upgrades butproceeds until the related NE upgrade task is complete. When thesystem displays The NE is performing the following task: ******.Please try later. in Description for a commissioning task, the NEupgrade task is running. If you want to perform automatic deploymentagain, wait until the NE upgrade task is complete. You can chooseSoftware > NE Upgrade Task Management > NE Upgrade Taskto query the NE upgrade task.

3 Shortcutmenu

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



55

AreaNo.

ElementName

Description

4 Operationresult

Records the results of each operation.

Alarm Commissioning Monitoring Window

Figure 3-12 shows the alarm commissioning monitoring window of eNodeBs. Table 3-9describes the window.

Figure 3-12 Alarm commissioning monitoring window of eNodeBs


AreaNo.

ElementName

Description

1 Alarm objecttree

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

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

3 Diagnosistask list

Displays the details about diagnosis tasks.



56

Window for Uploading Data FilesFigure 3-13 shows the window for uploading data files. Table 3-10 describes the window.

Figure 3-13 Window for uploading eNodeB data files


AreaNo.

ElementName

Description

1 File list Displays the files on the M2000 server.

2 Button Provides buttons for operations on uploading data files.

3 Tab named aftera data file type

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

4 Operation result Displays the details about the operations on uploading the typeof data file.

Parameters for the eNodeB Deployment ListThis section describes the parameters in the eNodeB deployment list for your reference.

Table 3-11 provides the meanings of the parameters.



57

NOTE

l If you use the CME to export the deployment list:

l Mandatory: indicates whether the parameter is mandatory. After the deployment list is imported,the M2000 performs non-blank check and validity check on each parameter.

l Export Using the CME by Default: identifies the parameter values that are to be exported or not tobe exported by default when you use the CME to export the site deployment list.

l Auto Deployment Window Can Be Edited: indicates whether a parameter value can be edited inthe auto deployment window after the eNodeB deployment list exported using the CME is importedinto the M2000.

l To use the M2000 to export the site deployment list, edit the list by referring to the Mandatory columnin Table 3-11.

l One of eNodeB ESN, Deployment ID, and eNodeB Longitude/eNodeB Latitude must be specified.

l Only in V100R005C00 and later versions, the Deployment ID can be used as the keyword in thedeployment.

l One of eNodeB Software Version, eNodeB Cold Patch Version, and eNodeB Hot Patch Version mustbe specified.

Table 3-11 Parameters for the eNodeB deployment list

Parameter Field Description Mandatory

Export Using theCME by Default

AutoDeploymentWindow CanBe Edited

eNodeB ID eNodeB ID. Yes Yes No

eNodeB Name Name of theeNodeB. Theparameter contains0 to 64 characters.

Yes Yes No

eNodeB ESN ESN on the eNodeBbackplane.The ESN uniquelyidentifies aneNodeB.

No l If the parameterhas been set onthe CME,export theparameter.

l If the parameterhas not been seton the CME, donot export theparameter.

Yes

Deployment ID ID for deploying aneNodeB.



No



58




eNodeB Type NodeB type. Yes Yes No

eNodeB OMInterface Type

Type of the interfacefor carrying the OMchannel of theeNodeB.

Yes Yes No

eNodeB OMBearing Board

Board carried by theOM channel of theeNodeB.

Yes Yes No

eNodeB OM IPAddress

IP addresses of theOM channel for theeNodeB.

Yes Yes No

eNodeB OM IPSubnet Mask

IP address subnetmask of the OMchannel for theeNodeB.

Yes Yes No

eNodeB InterfaceIP Address

Interface IP addressused by the eNodeB.

Yes Yes No

eNodeB InterfaceIP Subnet Mask

Subnet mask of theinterface IP addressused by the eNodeB.

Yes Yes No

eNodeB M2000IP Address

IP address of theM2000.

Yes Yes No

eNodeB M2000IP Subnet Mask

Subnet mask for theIP address of theM2000.

Yes Yes No

eNodeB OM NextHop IP Address

Next-hop IP addressfrom the eNodeB tothe M2000.

Yes Yes No

eNodeB OMVLAN ID

VLAN ID of theeNodeB.

Theparameter isspecified ifVLANsareconfigured inthenetwork.

l If the parameterhas been set onthe CME,export theparameter.


No



59




eNodeB OMVLAN Priority

VLAN priority ofthe OM channelused by the eNodeB.




No

eNodeB ServingSecGW IPAddress

IP address of thesecurity gatewayused by the eNodeB.



No

eNodeB ServingSecGW LocalName

Name of the securitygateway used by theeNodeB.



No

eNodeBLongitude

Longitude of theeNodeB.



No



60




eNodeB Latitude Latitude of theeNodeB.



No

eNodeB SoftwareVersion

Software versionnumber of the targeteNodeB.



Yes

eNodeB ColdPatch Version

Cold patch versionnumber of the targeteNodeB.



Yes

eNodeB HotPatch Version

Hot patch versionnumber of the targeteNodeB.



Yes



61




eNodeB PhysicalLocation

Physical position ofthe eNodeB. Thisparameter contains0 to 128 characters.

Yes Yes No

eNodeB CAName

Name of acertificationauthority (CA).



No

eNodeB CA URL Path for obtainingthe CA certificate.The format is http(s)://CAIP:CAport/CAPath.This parameter is setin secure scenariosfor certificateacquisition. Onlythe CMPv2 protocolis supported.



No

Contact Onsite personneland contactinformation.



Yes

3.3 Local Commissioning Using a USB Flash DriveTo perform local eNodeB commissioning using a USB flash drive, you need to upgrade theeNodeB software and data configuration files using a Universal Serial Bus (USB) flash drive,and check the running status of indicators on the eNodeB. Then, create an eNodeBcommissioning task on the M2000.



62

3.3.1 Commissioning ProcedureThis section describes how to perform local eNodeB commissioning using a Universal SerialBus (USB) flash drive.

Figure 3-14 shows the procedure for local eNodeB commissioning using a USB flash drive.



63

Figure 3-14 Procedure for local eNodeB commissioning using a USB storage device



64

NOTEYou can insert the USB flash drive before or after the eNodeB is powered on. The figure takes insertingthe USB flash drive after the eNodeB is powered on as an example.


Step Operation Mandatory/Optional


Prepare for local eNodeB commissioning using a USBflash drive, which involves obtaining the eNodeBinformation and commissioning tools, and obtaining files.For details, see 3.3.2 Preparations.

Mandatory

2 Localoperations

Download and activate the eNodeB software and dataconfiguration files using a USB flash drive. For details, see3.3.3 Downloading and Activating the Software, DataConfiguration File, and License File Using a USB FlashDrive.

Mandatory


After the eNodeB is correctly connected to the M2000,upload the eNodeB deployment list and the files requiredfor remote commissioning on the M2000.For details, see3.3.4 Uploading Data Files.

Optional

4 Create an eNodeB commissioning task on the M2000. Fordetails, see 3.3.5 Creating an eNodeB CommissioningTask.NOTE

If eNodeB software and data configuration files are alreadyupgraded using a USB flash drive onsite, right-click a deploymentlist imported to the M2000 and choose Task Settings from theshortcut menu. In the displayed Task Settings dialog box, clearthe Download Software, Download Configuration, and Activecheck boxes to skip these steps during the commissioning.

Mandatory

5 Start the eNodeB commissioning task on the M2000. Fordetails, see 3.3.6 Starting an eNodeB CommissioningTask.

Mandatory

6 Monitor the eNodeB commissioning task on the M2000.For details, see 3.3.7 Monitoring eNodeBCommissioning.

Mandatory

7 After eNodeB commissioning is complete, confirm theeNodeB commissioning task. For details, see 3.3.8Confirming eNodeB Commissioning Completion.

Mandatory

8 Check the eNodeB commissioning report for the eNodeBoperating status, and rectify the faults, if any, indicated inthe eNodeB commissioning report. For details, see 3.3.9Checking the Running Status of the eNodeB on theM2000.

Mandatory



65


9 Commission the antenna system on the M2000. For details,see 3.3.10 Commissioning the Antenna System on theM2000.

Optional


After the environment monitoring equipment is connected,commission the equipment so that it operates properly. Fordetails, see 3.3.11 Commissioning the EnvironmentMonitoring Equipment on the M2000.

Optional


Set the maximum transmit power of RRUs or RFUs. RRUand RFU are short for remote radio unit and radio frequencyunit, respectively. For details, see 3.3.12 Setting theMaximum Output Power for RRUs or RFUs.

Optional


Verify the basic services of the eNodeB. For details, see3.3.13 Testing the Basic Services of the eNodeB.

Optional


After eNodeB commissioning is complete and the eNodeBstarts to provide services properly, set the eNodeB to thenormal state on the M2000. For details, see 3.3.14 Settingan NE to the NORMAL Mode.

Mandatory


3.3.2 PreparationsTo perform local eNodeB commissioning using a USB flash drive, you need to collect relatedeNodeB information, obtain commissioning tools, and save the required files to the USB flashdrive. When the security gateway (SeGW) is deployed, prepare the bearer network by referringto Transmission Security Feature Parameter Description..

Preparing a USB Flash Drive for Local Commissioning

Before commissioning an eNodeB using a USB flash drive locally, you need to save the requiredfiles in the specified directory in the USB flash drive.

Prerequisitesl The eNodeB software package and data configuration files are available.l The commissioning license is ready if you need to load and activate the license file using

the USB flash drive.



66

l The USB flash drive and commissioning files have been scanned by using the antivirussoftware and no virus was detected. The commissioning files include the software package,data configuration file, and license file.

ContextThe security of the USB loading port is ensured by applying encryption and integrity protectionto files in the USB flash drive.

Procedure

Step 1 Obtain the tools required for the local commissioning using the USB flash drive, as describedin Table 3-13.

Table 3-13 Tools required for the local commissioning using the USB flash drive

Tool Description

USB flash drive l The USB flash drive is equipped with an indicator that indicatesthe data transmission status.

l Capacity ≥ 256 MBl Model: The USB flash drive must be provided by Huawei.l The USB flash drive must not provide any additional functions,

such as encryption, virus scanning, and bootstrapping. Inaddition, it cannot be an MP3 player, MP4 player, or smartphone.

l The USB flash drive used for commissioning cannot be used forother purposes. In addition, irrelevant files, especially those withChinese file names, cannot be saved in the USB flash drive.

The USB securityprotection tool(optional)

Obtain the tool from M2000 installation folder\client\client\USBProtector.

Step 2 Obtain the eNodeB software and files for automatic eNodeB deployment. The required files areshown in Table 3-14.

NOTE

l The eNodeB software package is ready, and can be downloaded from http://support.huawei.com.The preconfiguration file (Precfg.ini) is provided in the software package.

l The name of the data configuration file must be CFGDATA.XML. The file name is case-sensitive.Perform configurations according to eNodeB Initial Configuration Guide, change the name of the dataconfiguration file from M2000.XML to CFGDATA.XML, and save the file to a local computer.

Step 3 Save the required files to the following paths of the USB flash drive, depending on the specificscenarios, shown in Table 3-14. (The save path is case-sensitive and cannot be changed.)



67


NOTE

l If only one data configuration file is saved to the USB flash drive, save it to usb:\eNodeB\CFGDATA.XML. If several data configuration files are saved to the USB flash drive, create several newESN folders and save the data configuration files to the corresponding ESN folders. The save path is usb:\eNodeB\ESN\CFGDATA.XML. The eNodeB preferentially reads the data configuration file in the ESNfolder.

l If you want to load BootROM version during the eNodeB deployment, save the BootROM software(FIRMWARE.CSP) in the directory where the eNodeB software package (SOFTWARE.CSP) is saved.

l If you want to load a hot or cold patch during the eNodeB deployment, save the patch package(SWCPATCH.CSP or SWHPATCH.CSP) in the directory where the eNodeB software package(SOFTWARE.CSP) is saved.

l When you save the software package, save the software version file, that is, the .CSP file to usb:\eNodeB\Software\.

l The preconfiguration file is used to download the files for the boards not configured yet. For details abouthow to configure the preconfiguration file, see 4.4 Configuring the Preconfigurationn File.

l If only one preconfiguration file is saved to the USB flash drive, save it to usb:\eNodeB\Precfg.ini. If severalpreconfiguration files are saved to the USB flash drive, create several new ESN folders and save the dataconfiguration files to the corresponding ESN folders. The save path is usb:\eNodeB\ESN\Precfg.ini. TheeNodeB preferentially reads the preconfiguration file in the ESN folder.

l Only one license file is allowed in the folder that contains the license file, and the value of ESN must beANY.

Table 3-14 Mappings between the files and the specified file paths in the USB flash drive

File Specified File Path in the USB Flash Drive

BootROM software package usb:\eNodeB\Software\

eNodeB software package usb:\eNodeB\Software\

Cold patch software package usb:\eNodeB\Software\

Hot patch software package usb:\eNodeB\Software\

Data configuration file usb:\eNodeB\CFGDATA.XML or usb:\eNodeB\ESN\CFGDATA.XML

License file usb:\eNodeB\License\

Preconfiguration file usb:\eNodeB\Precfg.ini or usb:\eNodeB\ESN\Precfg.ini

Step 4 Perform encryption and integrity protection on files in the USB flash drive. For details, see 4.5Applying Integrity and Encryption Protection to Files in the USB Flash Drive.

CAUTIONBefore performing the encryption and integrity protection, read 4.5 Applying Integrity andEncryption Protection to Files in the USB Flash Drive carefully.

----End



68

3.3.3 Downloading and Activating the Software, DataConfiguration File, and License File Using a USB Flash Drive

The eNodeB automatically downloads the software, data configuration file and license file fromthe USB flash drive. After the download is complete, the eNodeB automatically activates thesoftware, data configuration file, and the license file. Then, the eNodeB is reset.

Prerequisitesl A USB flash drive is ready. The required files are saved in the USB flash drive.l The hardware such as remote radio units (RRUs) and LTE baseband processing units

(LBBPs) have been properly connected.

CAUTIONWhen you save the required files into the USB flash drive, ensure that the locking switch on theUSB flash drive is disabled. In other words, the USB flash drive must be writable.

ContextBefore downloading files from a USB flash drive, the eNodeB verifies the names and formatsof the files. If integrity protection has been applied to files in the USB flash drive, the eNodeBverifies the integrity of the files. If the verification fails, the eNodeB does not download the files.

Before downloading the software and data configuration file, the eNodeB automatically checksthe working mode of the RRU. Then, the eNodeB downloads and activates the correspondingsoftware and data configuration file based on the working mode of the RRU.

You must pay attention to the following points when you download and activate the software,data configuration file, and license file using the USB flash drive:l If the software and data configuration file in the USB flash drive are already activated, they

cannot be reactivated for the same eNodeB because of the cyclic redundancy check (CRC)function. The CRC function can prevent the software and data configuration file from beingreactivated when the USB flash drive is always inserted into the eNodeB. The CRC functioncan also prevent the eNodeB from being reset again after eNodeB deployment using theUSB flash drive.

l If the USB flash drive contains only the eNodeB software and data configuration file, theeNodeB downloads and activates the eNodeB software, and then downloads and activatesthe data configuration file.

l If the eNodeB software or data configuration file is missing in the USB flash drive, theeNodeB performs the following steps:– If the software is missing, the eNodeB downloads and activates the data configuration

file and license file except the software.– If the data configuration file is missing, the eNodeB upgrades to the minimum

configuration of the target version and downloads and activates the license file exceptthe data configuration file.

– If the license file is missing, the eNodeB downloads and activates the software and dataconfiguration file except the license file.



69

l If the eNodeB software upgrade fails, the eNodeB will roll back its software to the sourceversion.

l Before downloading and activating the data configuration file, the eNodeB does not checkthe compatibility between the data configuration file and the eNodeB software version. TheeNodeB performs the following activities:– If the target software version is not the same as the active software version, the eNodeB

checks the mapping between the data configuration file and the software after thesoftware is upgraded and the eNodeB is reset. If the software is incompatible with thedata configuration file or the download and activation of the data configuration file fail,the eNodeB upgrades to the minimum configuration of the target version.

– If the target software version is the same as the active software version, the eNodeBchecks the mapping between the data configuration file and the software withoutupgrading the software. If the software is incompatible with the data configuration fileor the download and activation of the data configuration file fail, the eNodeB uses thedata configuration file of the source version.

l The eNodeB does not download or activate the eNodeB software, data configuration file,or license file from the USB flash drive in any of the following cases:– The eNodeB software and data configuration file or their saving paths do not exist in

the USB flash drive.– The target software version is the same as the active software version. In this case, the

eNodeB software cannot be downloaded or activated, but the data configuration file andlicense file can be downloaded and activated.

– The data configuration file is the same as the active data configuration. In this case, thedata configuration file cannot be downloaded or activated, but the software and licensefile can be downloaded and activated.

– The license file cannot be downloaded, but the software and data configuration file canbe downloaded and activated in any of the following cases:– The license file to be downloaded is not the commissioning license.– The license file to be downloaded is the commissioning license, but the value of

ESN is not ANY.– The configurations or the names of the license file to be downloaded and the active

license file are the same.

Procedure

Step 1 Check whether the eNodeB is powered on. If it is not powered on, power on the eNodeB. If itis already powered on, go to Step 2.

NOTEEnsure that the RRU is powered on and the common public radio interface (CPRI) connections are correctbefore you power on the eNodeB. Check for faults by monitoring the CPRI indicator status on the LBBPafter the eNodeB is powered on. For details, see 4.3 Checking the Status of Indicators.

Step 2 When the eNodeB operates properly, insert the USB flash drive into the USB port on theBBU3900 main control board. If an LMPT is used, the USB port is shown in Figure 3-15; if anUMPT is used, the USB port is shown in Figure 3-16.



70

Figure 3-15 USB port on the LMPT

Figure 3-16 USB port on the UMPT

Step 3 Wait for the eNodeB to automatically upgrade the software and data configuration file.

If the download or activation fails, commission the eNodeB by updating the software and dataconfiguration file in the USB flash drive or using a new USB flash drive.

If the download or activation still fails, perform the local eNodeB commissioning on the LMT.When the software and data configuration file are being upgraded, the normal status of theindicators on the USB flash drive and main control board is shown in Table 3-15. If the indicatorsare abnormal, see 4.3 Checking the Status of Indicators.



71

Table 3-15 Indicator status

Indicator on the USBFlash Drive

RUN Indicator on the LMPT/UMPT

Automatically detectingthe USB flash drive

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

Downloading the softwareand data configuration filefrom the USB flash drive

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

Activating the eNodeBsoftware and dataconfiguration file

Steady on Blinking (on for 0.125s and off for0.125s)

Starting the eNodeB Steady off Steady on

Normal eNodeB operation Steady on Blinking (on for 1s and off for 1s)

WARNINGDo not remove the USB flash drive or reset the eNodeB when downloading or activating theeNodeB software and data configuration file using the USB flash drive. After the download iscomplete, the eNodeB automatically activates the software and data configuration file. Then,the eNodeB is reset.

Step 4 When the download and activation are successful, rectify faults by referring to Checking theStatus of Indicators.

----End



72

Follow-up Procedure

CAUTIONThe eNodeB software package contains the LMT software. Before downloading the eNodeBsoftware package, pay attention to the following points:

l When the LMPT is used: the speed of writing to the flash memory is limited, the LMPTdoes not support download of the LMT complete package through the USB flash drive. Toreduce the eNodeB deployment duration, some of the files of the LMT software areautomatically downloaded from the M2000 to the eNodeB four hours after the eNodeBdeployment. If you need to use the LMT complete package immediately after the eNodeBdeployment, run the SPL SOFTWARE command on the M2000 after the eNodeB isconnected to the M2000. Set Delay Download File Supply Flag to YES(Supply File thatSupport Delay). The remaining files of LMT software are downloaded to the eNodeB. Ifyou want the LMPT to support download of the LMT complete package through the USBflash drive, when preparing the files in the USB flash drive, configure the value ofWEBLMT from the preconfiguration files as YES (case-insensitive).

l When the UMPT is used: the speed of writing to the flash memory increases. The UMPTsupports download of the LMT complete package through the USB flash drive. Therefore,an LMT package is not required after software activation.

3.3.4 Uploading Data FilesUpload data files that are required for procedures of eNodeB commissioning. Data files requiredfor procedures of eNodeB commissioning tasks are NE software versions, cold patches, hotpatches, configuration data files, deployment lists, RET antenna software versions andconfiguration data files, RET antenna templates, and commissioning licenses.

PrerequisitesYou have logged in to the M2000 client.

Context

You need to upload data files in the following scenarios:

l Prepare for the commissioning.

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

l The commissioning cannot be started because certain required data files are unavailable.

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

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



73

Table 3-16 File save paths

File Type Save Path

Softwareversion orcold patch

/export/home/sysm/ftproot/eNodeB Type/Software/eNodeB SoftwareVersion/

Hot patch /export/home/sysm/ftproot/eNodeB Type/Patch/eNodeB Patch Version/

Configuration data file

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

Deployment list

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

RETantennasoftwareversion andconfiguration data file

/export/home/sysm/ftproot/OutSourcing/RETFile/

RETantennatemplate

/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/RETTemplate/

Commissioning license

/export/home/sysm/ftproot/adn/YYMMDD/CommissionLicense/

Procedure


Step 2 Click Prepare File&Data. The window for preparing files and data is displayed. Upload datafiles as required.



74

If youneed to...

Then...

Upload NEsoftwareversions

l Upload one by oneOne or multiple software versions corresponding to a certain NE type areuploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS





5. When Progress is 100%, the software versions are uploaded.l Upload in batches

One or multiple software versions corresponding to one or multiple NE typesare uploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS









75

If youneed to...

Then...


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

When uploading an NE software version, if the client displays a message indicating thatthe NE software version supports multiple types of base stations in the same mode, youneed to upload the version only once for a base station. Then, the other types of basestations in the same mode can use the uploaded NE software version.



76

If youneed to...

Then...

Uploadcoldpatches

l Upload one by oneOne or multiple cold patches corresponding to a certain NE type are uploadedat a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS





5. When Progress is 100%, the cold patches are uploaded.l Upload in batches

One or multiple cold patches corresponding to one or multiple NE types areuploaded at a time.1. On the Software & Cold Patch tab page, choose Transfer > From OSS









77

If youneed to...

Then...


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



78

If youneed to...

Then...

Upload hotpatches

l Upload one by oneOne or multiple hot patches corresponding to a certain NE type are uploadedat a time.1. On the Hot Patch tab page, choose Transfer > From OSS Client to OSS





5. When Progress is 100%, the hot patches are uploaded.l Upload in batches

One or multiple hot patches corresponding to one or multiple NE types areuploaded at a time.1. On the Hot Patch tab page, choose Transfer > From OSS Client to OSS









79

If youneed to...

Then...


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

Uploadconfiguration datafiles

1. On the NE Configuration Data tab page, choose Transfer > From OSSClient to OSS Server. The Upload NE Configuration Data dialog box isdisplayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select the folder where the configuration data file that you wantto upload is stored, click Select. The Upload NE Configuration Data dialogbox is displayed.CAUTION

The path for saving the eNodeB configuration data file to be uploaded must be ..\eNodeBName\M2000.XML on the local PC. An eNodeBName folder contains onlyone XML file. To upload eNodeB configuration data files, you must select theeNodeBName folder where the files are stored. You can select multipleeNodeBName folders at a time.

The save path for the files to be uploaded to the server is displayed in the DestinationPath area. You can only view the path.

Uploaddeployment lists

1. On the Deployment List tab page, choose Transfer > From OSS Client toOSS Server. The Upload Deployment List dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload Deployment List dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload Deployment List dialog box. The system startsuploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the deployment lists are uploaded.NOTE

If the CME is not deployed, you can click Export Template to export an emptydeployment template, fill out the template based on the planned data, and upload thetemplate. The default names of the exported empty deployment list templates are thesame. Therefore, you are advised to change the template names after filling out thesetemplates.



80

If youneed to...

Then...

UploadRETantennasoftwareversionsandconfigurati

l Upload one by oneOne or multiple RET antenna software versions and configuration data filescorresponding to a certain NE type are uploaded at a time.1. On the RET tab page, choose Transfer > From OSS Client to OSS






l Upload in batchesOne or multiple RET antenna software versions and configuration data filescorresponding to one or multiple NE types are uploaded at a time.1. On the RET tab page, choose Transfer > From OSS Client to OSS






6. Click OK to close the NE File Transfer dialog box. The system startsuploading the data files.



81

If youneed to...

Then...

on datafiles

The data file preparation window displays the following detailedinformation about the operations at the bottom of the window:Operation, Status, Source File Path, Destination File Path, andProgress.


UploadRETantennatemplates

1. On the RET Template tab page, choose Transfer > From OSS Client toOSS Server. The Upload RET Template dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload RET Template dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload RET Template dialog box. The system startsuploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the RET antenna templates are uploaded.NOTE

If the CME is not deployed, you can click Export Template to export an empty RETantenna template, fill out the template based on the planned data, and upload thetemplate.

Uploadcommissioninglicenses

1. On the Commission License tab page, choose Transfer > From OSS Clientto OSS Server. The Upload Commission License dialog box is displayed.


3. In the Source Path area, click . The dialog box for selecting files isdisplayed. Select files that you want to upload and click Open to return tothe Upload Commission License dialog box.The save path for the files to be uploaded to the server is displayed in theDestination Path area. You can only view the path.

4. Click OK to close the Upload Commission License dialog box. The systemstarts uploading the data files.The data file preparation window displays the following detailed informationabout the operations at the bottom of the window: Operation, Status, SourceFile Path, Destination File Path, and Progress.

5. When Progress is 100%, the commissioning licenses are uploaded.

----End



82

3.3.5 Creating an eNodeB Commissioning TaskThis section describes how to create an eNodeB commissioning task on the M2000 client aftercommissioning preparations are complete.

Prerequisitesl You have logged in to the M2000 client.l eNodeB commissioning preparations are complete.l If the M2000 is deployed in SLS mode, radio network planning engineers need to plan the

area to which the eNodeB belongs.l In scenarios without the SeGW, if the eNodeB and the M2000 server are deployed on

different network segments, you are required to configure the router closest to the eNodeBon the path between the eNodeB and the M2000 server as a Dynamic Host ConfigurationProtocol (DHCP) relay. Configure the IP address of the DHCP server for the M2000 as theDHCP relay address.

l In scenarios with the SeGW, if the eNodeB and the public DHCP server are deployed ondifferent segments, you are required to configure the router closest to the eNodeB on thepath between the eNodeB and the public DHCP server as a DHCP relay. Configure the IPaddress of the DHCP relay as the public DHCP server address, and the IP address of theDHCP server in scenarios with the SeGW as the IP address of the DCHP server for theM2000.

NOTEIn situations where the M2000 is deployed in SLS mode, the preceding DHCP server IP address of theM2000 refers to the host IP address.

Procedure


Step 2 Select deployment lists.

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

If you needto...

Then...

Import adeployment listfrom the server

Select From Server and choose a deployment list from the drop-down list box.

Import adeployment listfrom the client

Select From Client and click to select a deployment list.

3. (Optional) Select the area to which an eNodeB belongs in the Sub-area area. This step is

mandatory when theM2000 is deployed in SLS mode.

NEs belong to different areas when they are managed by different M2000 servers. If theM2000 is deployed in SLS mode, NEs are managed by different servers. On the CME client,



83

these NEs belong to different areas. Select the active or slave M2000 server that the NEbelongs to based on the planned data. Configure the data as follows:l If the NE was created on the active M2000 server, set the PEERIP parameter for the

OMCH to the IP address of the active M2000 server.l If the NE was created on the slave M2000 server, set the PEERIP parameter for the

OMCH to the IP address of the slave M2000 server.l Set the Destination IP parameter for the IP router from the NE to the M2000 server to

an IP address on the the network segment where the M2000 server is located.

NOTEOnsite deployment engineers need to perform operations based on the areas that have been plannedfor eNodeBs by radio network planning engineers.

l If eNodeBs belong to one area, import one deployment list to create eNodeBs in batches.

l If eNodeBs belong to different areas, import multiple deployment lists by area to create eNodeBs.

4. In NE Connection Mode, set a mode for connecting the M2000 and NEs.

Modes for connecting the M2000 and NEs are as follows:l Common Connection: Security authentication is not performed between the M2000

and the NE.l SSL Connection: Security authentication is performed between the M2000 and the NE.

After security authentication is passed, a secure connection can be established, therebyensuring communication security and integrity. If this mode is selected, you also needto set an authentication mode. Authentication modes are Anonymous Authority andOSS Authentication NE, where Anonymous Authority is the default authenticationmode.

NOTETo enable automatic SSL connection during NE deployment, you need to set the authentication modefor NE in advance on the CME in addition to setting the connection mode between the M2000 andNEs in this step.

Step 3 Click OK. The system starts the import.

After the import is complete, the M2000 checks for mandatory parameters with empty valuesand invalid NE configuration data. In addition, the information indicating whether the importsucceeded or failed is displayed on the Operation Information tab page.

l If the import is successful, the M2000 automatically creates a commissioning task for eacheNodeB. The imported eNodeB deployment lists are displayed on the Deployment List tabpage.

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

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

NOTEYou can check whether the parameters in eNodeB deployment lists can be modified by referring toParameters for the eNodeB Deployment List.

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

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



84

a. Click in the ESN value cell. The Bind ESN dialog box is displayed.b. Select an ESN that is not bound, and click OK to return to the Deployment

Parameter dialog box.

NOTE

You can change the ESNs before OM links are established between NEs and the M2000.

2. The changed parameter values are displayed in the commissioning task window andhighlighted in red.

----End

3.3.6 Starting an eNodeB Commissioning TaskThis section describes how to start an eNodeB commissioning task. After creating an eNodeBcommissioning task, you can set commissioning procedures and start the task. Then, theM2000 automatically commissions the eNodeB.

Prerequisitesl You have logged in to the M2000 client.l eNodeB commissioning tasks have been started.

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

Procedure


Step 2 On the Deployment List tab page, right-click one or multiple commissioning tasks and chooseStart from the shortcut menu. The Task Settings dialog box is displayed.

Step 3 Select steps in the Select column based on the actual plan.

NOTE

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

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

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

For details about commissioning procedures and steps, see Table 3-17.



85

Table 3-17 Description of commissioning process

No. Procedure

Step Description

1 AutoDiscovery

Check OMchannel

When connection of the transport network isproper, the M2000 automatically sets up an OMchannel to connect to the desired eNodeB basedon the deployment list, and commissions andmaintains the NodeB through this channel.

Wait for manualoperation

After the OM channel is set up, the status of thecommissioning task changes to Waiting formanual operation. Manually confirm thecompletion and proceed with the commissioningafter the commissioning environment of thenetwork is ready.

2 AutoConfiguration

Downloadsoftware

The M2000 automatically checks whether thecurrent eNodeB version is the same as the targetsoftware version given in the deployment list. Ifthe versions are not the same, the M2000automatically downloads software from theserver to the eNodeB.

Downloadconfiguration

The M2000 downloads the desired configurationfile from the server to the eNodeB based on thetarget version information.

Activate Activate the eNodeB configuration data (takeseffect after next reset) and then activate thesoftware (automatic reset).

3 AutoPlanning

Auto Planning Only the BTS3202E is supported in eNodeB autodeployment.

4 Uploadcommissioninglicense

Distributecommissioninglicense

When some eNodeB functions are restrictedbecause the eNodeB uses the default license upondelivery, you need to install a commissioninglicense. The commissioning license has timerestriction. You need to replace thecommissioning license with the commercial oneas soon as possible after the eNodeBcommissioning is complete.



86

No. Procedure

Step Description

5 Commission RET

Upgrade RETsoftware version

The target RET antenna software version isprovided by antenna line device (ALD) suppliersand saved on the local PC.l RET antennas managed by eNodeBs on the

sites must be commissioned.l If an eNodeB and a NodeB share antennas and

the antennas are managed by the NodeB, youdo not need to commission the RET antennas.

l When antennas are managed by themanagement system of a third party, you donot need to commission RET antennas.

Upgrade RETconfiguration

The RET antenna configuration file is providedby ALD suppliers and saved on the local PC. RETantenna configuration data may vary according toRET antenna types and suppliers.

Tune RET Check whether RET antennas are commissionedcorrectly during the commissioning.

6 Test andmonitor

Test installation& deploymentquality

Services carried on the RF module will beinterrupted during operation. If an RF module isshared by base stations of different RATs,services of the other RAT will also be interrupted.The check may take several minutes. The projectquality check involves the VSWR, offlineintermodulation interference, and crossed pair.

Monitor cellservice status

Check whether any active cells exist under theeNodeB.You can monitor alarms of the eNodeB on theM2000 during software commissioning to locateand handle exceptions in time.

7 PerformNHC

Perform NHC You can perform health check to learn theeNodeB operating status.

8 Wait forconfirmation

Wait forconfirmation

After service verification is complete, thecommissioning task is in the Waiting forConfirmation state. You need to manuallyconfirm that the commissioning is complete.



87

NOTE

The system checks whether all configured RF modules are usable before starting project quality check.

l If all configured RF modules are usable, the system issues project quality check commands to proceedwith subsequent operations.

l If only some configured RF modules are usable, the system sets a timer (2.5 minutes in length and amaximum of 5 times) to wait until all RF modules are usable. After all RF modules are usable, thesystem issues project quality check commands to proceed with subsequent operations. If some RFmodules are still unusable after the timer expires, the system ends the project quality check task.

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

If... Then...

Not all therequired datafiles are available

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

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

l : Indicates that not all the required data files are available.2. Click OK. The Data Preparation Check dialog box is closed.3. Obtain relevant data files based on the check results.

For detailed operations, see Uploading Data Files.4. After the required data files are uploaded, start the commissioning

tasks again.

All the requireddata files areavailable

The M2000 starts commissioning. The selected commissioning tasks enterthe Running state.NOTE

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

----End

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

Viewing Progress and Status of eNodeB Commissioning Tasks

This section describes how to view progress and status of eNodeB commissioning tasks on theM2000 to learn about process of the tasks.

Prerequisitesl You have logged in to the M2000 client.

l eNodeB commissioning tasks have been started.



88

Contextl By default, the GUI displays only commissioning tasks created by a specific user. To view

commissioning tasks created by other users, click on the toolbar.l When the system performs NE upgrades during the automatic configuration phase of a

commissioning task, if you restart or delete the commissioning task, the system does notrestart NE upgrades but proceeds until the related NE upgrade task is complete. When thesystem displays The NE is performing the following task: ******. Please try later. inDescription for a commissioning task, the NE upgrade task is running. If you want toperform automatic deployment again, wait until the NE upgrade task is complete. You canchoose Software > NE Upgrade Task Management > NE Upgrade Task to query theNE upgrade task.

Procedure


Step 2 View the status and progress of commissioning tasks in the commissioning task list.TIP

You can quickly view the status of commissioning tasks by using either of the following methods:

l In the commissioning task list, the status of the tasks is displayed in Status, the current procedures aredisplayed in Current Phase, and details about each procedure are displayed in Description.

l In the commissioning task list, select one or multiple commissioning tasks whose status you want to

view, and then click . The right pane displays execution status ofsteps for commissioning procedures.

The displayed information includes the execution status, description, start time and end time of eachcommissioning substep.

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

----End

Handling eNodeB AlarmsThis section describes how to handle eNodeB alarms. After eNodeB software is automaticallyupgraded, you can use the M2000 to view alarms on eNodeBs. All alarms related to eNodeBsare categorized by object to help you query required alarms.

Prerequisitesl You have logged in to the M2000 client.l Software commissioning monitoring has already started, and the completion of the

commissioning has not yet been confirmed.

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



89

Procedure



In the displayed window, you can view alarms on eNodeBs by monitored object. For detailsabout the alarm monitoring window, see Interface Description: eNodeB CommissioningWindow.

Step 3 Handle alarms.1. Double-click an alarm that you want to handle.2. In the displayed dialog box that shows the alarm details, click the link in Reason And

Advice.3. Handle alarms based on the alarm reference.

----End

Performing eNodeB Antenna Fault DiagnosisThis section describes how to perform antenna fault diagnosis. The M2000 provides automaticfault diagnosis to antennas. When errors occur during eNodeB commissioning, you can use theautomatic fault diagnosis function provided by the M2000 to check whether the eNodeB that isbeing commissioned is faulty. Then, you can take corresponding measures to rectify the faultsbased on the diagnosis results.

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

tasks has not yet been confirmed.

Context

CAUTIONeNodeB services are interrupted upon antenna fault diagnosis. Therefore, you need to performthe diagnosis when the eNodeB is not providing services or the services are isolated.

eNodeB fault diagnosis aims to check whether antennas are functioning normally. It involvesthe VSWR test, offline intermodulation interference test, and crossed pair test.

After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task anddisplays the diagnosis progress. After the fault diagnosis is complete, you can obtain the faultdiagnosis report.

If you delete a fault diagnosis task, the corresponding diagnosis report is deleted accordingly.If you restart the M2000 server, all fault diagnosis tasks and reports are deleted.



90

Procedure



Step 3 Perform fault analysis on antenna alarms.1. Select an object (antenna) from the left pane of the displayed window, or select a specific

alarm of the object (antenna) from the alarm list in the right pane, right-click the object oralarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settingsdialog box is displayed.

2. Select an eNodeB in the Select NE area, select a diagnosis type in the Select diagnosetype area, type diagnosis parameters in the Type diagnosis parameters area, and thenclick OK. The dialog box for confirming the diagnosis is displayed.

3. Click Yes. The system starts the fault diagnosis.

During the fault diagnosis, a diagnosis task is added to the diagnosis task list.

NOTEFault diagnosis may take a long time when there are a large number of detection services executedby the detection script and there are a large number of NE configuration services.

4. After fault diagnosis is complete, you can right-click a diagnosis task in the diagnosis tasklist, and choose Diagnose Report from the shortcut menu to view diagnosis results.

----End

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

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

ContextFor details about operations on commissioning tasks, see Table 3-18.

Table 3-18 Operations on commissioning tasks

Operation

Description

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

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

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



91

Operation

Description

Resume

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

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

Procedure


Step 2 On the Deployment List tab page, select one or multiple commissioning tasks and performoperations as required.

If youneed to...

Then...

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

Pause Right-click the tasks and choose Pause from the shortcut menu. The tasks arein the Paused state.

Resume Right-click the tasks and choose Resume from the shortcut menu. The tasksproceed from where they are paused.

Cancel Right-click the tasks and choose Cancel from the shortcut menu. The tasksreturn to the Wait for Start state.

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

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

----End

3.3.8 Confirming eNodeB Commissioning CompletionWhen the status of an eNodeB commissioning task changes to Waiting for Confirmation, youneed to confirm that the eNodeB commissioning is complete.

Prerequisitesl The eNodeB is properly connected to the M2000.l The status of the eNodeB commissioning task is Waiting for Confirmation.



92

Procedure

Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB AutoDeployment. The eNodeB Auto Deployment tag page is displayed.

Step 2 Right-click one or more eNodeB commissioning tasks to be confirmed from the commissioningtask list, and choose Confirm Completion from the shortcut menu.

----End

3.3.9 Checking the Running Status of the eNodeB on the M2000This section describes how to perform the health check and alarm check on the eNodeB throughthe M2000.

Obtaining eNodeB Commissioning ReportsThis section describes how to obtain eNodeB commissioning reports. An eNodeBcommissioning report records the details about user operations, commissioning results, errorinformation, and health check report. You can obtain the report of eNodeB commissioning taskswhen the tasks are in progress and archive the report when the tasks are complete.

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

ContextThe exported commissioning report records the information about only the selectedcommissioning tasks. After you manually delete a commissioning task, the generatedcommissioning report does not contain the information about this task.

The deployment report can be stored for a maximum of 30 days. The start date is specified asthe date when the deployment report is generated for the first time.

Procedure


Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you wantto export the report, right-click the tasks, and then choose Export Deployment Report fromthe shortcut menu. A dialog box is displayed, asking you whether to export alarm data at thesame time.

If... Then...

You need to export alarm data Click Yes. The Save dialog box is displayed.

You do not need to export alarm data Click No. The Save dialog box is displayed.

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



93

You can customize a filename for the commissioning report. If you do not specify the filename,the M2000 names and saves the file based on the naming conventioneNodeB_Auto_Deployment_Report.zip. For example,eNodeB_Auto_Deployment_Report.zip.

Step 4 (Optional) Decompress the generated report file. In the decompressed folder, double-clickeNodeB_Auto_Deployment_Report_index.html to view the commissioning report.

If you choose to export alarm data at the same time in Step 2, the file containing the alarm datais saved in the alarm sub-folder.

----End

Rectifying Faults and Clearing Alarms Against the eNodeB Health Check Report

This section descries how to rectify faults and clear alarms against the eNodeB health checkreport to ensure that the eNodeB runs properly.

PrerequisitesThe eNodeB commissioning report is available.

Context

Table 3-19 shows the eNodeB health checklist.

Table 3-19 eNodeB health checklist


eNodeB softwareversion

eNodeB software status Check the operating status of theeNodeB software.

eNodeB software versioninformation

Check the information about therunning eNodeB softwareversion.

Environment status RRU temperature Check the RRU temperature.

Environment temperature andhumidity

Check the environmenttemperature and humidity.

eNodeB type eNodeB type Check whether the eNodeB typeis correct in the dataconfiguration.

Configuration data Configuration data consistency Check whether the effective dataapplied to modules is consistentwith the configured data in thedatabase.

Active alarms Check for the active alarmsreported by an NE.

Cell status Cell status Check the cell status.



94


MBTS alarmsNOTE

This item is notrequired for a single-mode eNodeB.

Inter-RAT communicationalarms

Check the status of inter-RATcommunication.

Inter-RAT BBU board parametersettings conflict alarms

Check whether inter-RATparameter settings are consistentfor BBU boards.

Inter-RAT cabinet configurationconflict alarms

Check whether inter-RATconfigurations are consistent forcabinets.

Inter-RAT monitoring deviceparameter settings conflictalarms

Check whether inter-RATparameter settings are consistentfor monitoring devices.

Inter-RAT board objectconfiguration conflict alarms

Check inter-RAT configurationsare consistent for board objects.

Inter-RAT RF unit parametersettings conflict alarms

Check whether inter-RATparameter settings are consistentfor RF units.

Inter-RAT site-levelconfiguration conflict alarms

Check whether inter-RATconfigurations are consistent forsites.

Inter-RAT control rights conflictalarms

Check whether inter-RATcontrol rights are consistent.

RF unit working mode and boardcapability mismatch alarms

Check whether the workingmode for the RF unit matches theboard capability.

Hardware status CPU usage Check the CPU usage.

Transmit channel status Check the status of the transmitchannel.

Receive channel status Check the status of the receivechannel.

RRU status Check the status of an RF unit.

Memory usage Check the memory usage.

Flash memory usage Check the usage of the flashmemory.

Board status Check the status of a board.

Interface status X2-interface link Check the status of the X2interface and the informationabout the peer eNodeB.



95


S1-interface link Check the parameters for the S1interface and the informationabout the MME.

GE/FE port status Check the parameter settings forthe Ethernet port.

E1/T1 port status Check the parameter settings forthe E1/T1 port.

Remote maintenance channelstatus

Check the parameter settings forall remote maintenance channelsof the eNodeB.

SCTP link status Check the parameter settings forthe SCTP link.

IP path status Check the parameter settings foran IP path.

CPRI port status Check the parameter settings forthe CPRI port.

Clock status Clock status Check the status of the currentclock in the basic cabinet,including the reference clock,clock quality, clock priority,clock working mode, and statusof the phase-locked loop.

Procedure

Step 1 Open the eNodeB commissioning report and view the health check report to determine theeNodeB operating status.

Step 2 Check the health check report for faults and alarms, and rectify the faults and clear the alarmsby referring to eNodeB Alarm Reference. If all the alarms are cleared but the eNodeB does notwork properly, contact Huawei for technical support.

Step 3 Check for eNodeB alarms.

You can check for eNodeB alarms using one of the following methods:l on the M2000 client, choose Monitor > Browse Current Alarm. Set the search criteria in

the displayed Filter dialog box to check for eNodeB alarms. For details, see Browse CurrentAlarm in the M2000 Online Help.

l On the M2000 client, choose Topology > Main Topology. On the Main Topology tab page,right-click the eNodeB and choose Query Alarm/Event > Current Alarm from the shortcutmenu. Then, double-click an alarm to view details

Step 4 Clear the alarms by taking recommended actions or by referring to eNodeB Alarm Reference.

----End



96

3.3.10 Commissioning the Antenna System on the M2000Commissioning the antenna system on the M2000 includes commissioning the remote electricaltilt (RET) and tower-mounted amplifier (TMA).

(Optional) Commissioning the RET Antenna on the M2000

This section describes how to use MML commands to commission the remote electrical tilt(RET) antenna on the M2000. If tasks for RET commissioning in the commissioning phase arenot selected on the M2000, the M2000 does not perform RET commissioning after thecommissioning phase starts. In this case, you need to use MML commands to commission theRET antenna.

Prerequisitesl The antenna line device (ALD) is installed correctly.

l The LMT communicates with the eNodeB properly.

l The RET software and data configuration file are available.

l The FTP server functions properly and is connected to the eNodeB correctly.

l Each FTP user has the permission to read a specified folder.

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

Context

l Commissioning the RET antenna includes downloading the RET software and dataconfiguration file, calibrating the RET antenna, setting the RET downtilt, and query RETovercurrent or undercurrent alarms.

l The RET downtilt must be configured based on the planned network data. Otherwise, theRET downtilt affects antenna coverage.

Procedure


If... Run...



MOD ANTENNAPORT





97




NOTE


If... Then...













NOTE

If the RET downtilt fails to be calibrated, check for the cabinet, subrack, and slot configurations and themapping between the RET antenna and the sector. If the configurations and mapping are incorrect, run theMOD RETSUBUNIT command to set them gain, and calibrate the RET downtilt again.If you run this command without specifying any parameters, RET antennas can be calibrated in batches.

Step 9 Set the RET downtilt.If the downtilt has been set in the data configuration file, perform Step 9.3 to check whether theRET downtilt is calibrated successfully.



98

1. Query the downtilt range supported by the RET antenna.MML command: DSP RETDEVICEDATA

2. Set the RET downtilt.MML command:MOD RETTILT




----End

Commissioning the TMA on the M2000This section describes how to commission the tower-mounted amplifier (TMA) to check whetherthe current TMA software version is the same as the target TMA software version. If they aredifferent, load the target TMA software. After the TMA software is loaded, the TMAautomatically resets. The software then takes effect and the TMA starts working properly.

Prerequisitesl The TMA is installed correctly.l The TMA software has been uploaded to the M2000 server.l The eNodeB is properly connected to the M2000.l Each FTP user has the permission to read a specified folder.l The File Transfer Protocol (FTP) port has been enabled on the firewall between the eNodeB

and the M2000 server.

Contextl The FTP server transmits data in plaintext mode by default.l As a part of the antenna system, the TMA is used to amplify the received weak signals.l The TMA software is supplied by the antenna line device (ALD) vendor.l If incorrect TMA software is loaded, the TMA may not work property.

Procedure


If... Run...



MOD ANTENNAPORT



99




Step 4 Check whether the TMA starts working and whether the TMA gain is set correctly.MML command: DSP TMASUBUNIT

l If the maximum gain is the same as the minimum gain, the TMA has a fixed gain. In thissituation, you are not allowed to set any gains.



NOTE


If... Then...




Go to Step 6.








100


----End

3.3.11 Commissioning the Environment Monitoring Equipment onthe M2000

After the environment monitoring equipment is connected, you need to commission it so that itfunctions properly.

Setting Environment Alarm ParametersThis section describes how to set environment alarm parameters within the permissible rangeand add user-defined alarms as required.

Prerequisitesl The M2000 communicates properly with the eNodeB.l Environment monitoring devices have been configured.l The dual in-line package (DIP) switches on the environment monitoring device are properly

set. For details, see APM30H&TMC11H&IBBS200D&IBBS200T(Ver.B) ProductDescription, APM30H&TMC11H&IBBS200D&IBBS200T(Ver.C) Product Descriptionand EMUA User Guide.

ContextThe remote radio unit (RRU), universal power environment unit (UPEU) in the baseband unit(BBU), environment monitoring unit type A (EMUA), and power monitoring unit (PMU) in theAPM30H are all equipped with extended alarm ports. Setting environment alarm parametersincludes adding user-defined alarms and binding the user-defined alarms to the eNodeB.Environment alarms are used to monitor the equipment room where the eNodeB is located. Whensetting environment alarm parameters, you need to bind a user-defined alarm to the specificsubrack, slot, and port on the eNodeB.

Procedure

Step 1 Add a user-defined alarm.1. Choose Monitor > Alarm Setting > NE Alarm Settings.2. On the User-Defined Alarm tab page, click the Alarm Definition tab, and click Add. The

Add User-Defined Alarm dialog box is displayed, as shown in Figure 3-17.



101

Figure 3-17 Adding a user-defined alarm

3. Select an NE type on the left, and set the user-defined alarm parameters, including Alarm

Name, Alarm ID, Alarm Severity Level, and Alarm Type.NOTE

l Each type of user-defined alarm is allocated a unique alarm ID. The alarm ID ranges from 65033to 65233.

l The same type of alarm must use the same alarm ID for all eNodeBs. For example, if the doorstatus alarm ID for an eNodeB is 65035, the door status alarm IDs for other eNodeBs must alsobe 65035.

4. Click OK. The information about the added user-defined alarm is displayed in the NEAlarm Setting window.

5. Click Apply to save the user-defined alarm.A message is displayed, indicating that saving the user-defined alarm is successful or fails.

If saving the user-defined alarm is successful, click OK. The icon disappears. Ifsaving the user-defined alarm fails, click Details to view the failure cause and rectify thefault accordingly. Then, add the user-defined alarm again.

Step 2 Bind the user-defined alarm to the eNodeB.1. Choose Monitor > Alarm Setting > NE Alarm Settings.2. On the User-Defined Alarm tab page, click the Alarm Binding tab. Then, add the user-

defined alarm binding relationship.l Single binding

a. Choose Edit > Add. The Add Alarm Binding dialog box is displayed, as shownin Figure 3-18.

b. Select an NE from the Select NE navigation tree or enter an NE name in the Searchby name text box on the left. Select an alarm from the Select Alarm/Eventnavigation tree or enter an alarm name in the Search by name text box in the



102

middle. Select an alarm or event ID based on the NE type, and set bindingparameters, including port type, cabinet No., subrack No., and slot No. of the port,alarm voltage, and upper and lower alarm thresholds.

NOTEIf a digital port is used for the monitoring board, you must set alarm voltage to specify acondition for reporting alarms. If an analog port is used for the monitoring board, you mustset upper and lower alarm thresholds to specify a condition for reporting alarms.

c. Click OK. The information about the added user-defined alarm is displayed in theNE Alarm Setting window.

Figure 3-18 Adding alarm binding

l Batch binding

a. Choose Import/Export > Export Template. The Export Alarm BindingTemplate dialog box is displayed, as shown in Figure 3-19.Alternatively, choose Import/Export > Export to export the existing records onthe Alarm Binding tab page by NE type.

Figure 3-19 Exporting alarm binding template

b. In the displayed Export Alarm Binding Template dialog box, select the NE type,

and specify the save path and name for the exported template.



103

c. Open the template and edit it based on actual requirements by referring to theexample in the template.

d. Choose Import/Export > Import to import the edited template to the M2000.Then, 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 icon.3. Select an alarm binding relationship record and click Apply to apply it to the NE.

A message is displayed, indicating that applying the alarm binding relationship is successful

or fails. If applying the alarm binding relationship is successful, click OK. The icondisappears. If applying the alarm binding relationship fails, click Details to view the failurecause and rectify the fault accordingly. Then, apply the alarm binding relationship again.

----End

Checking for External Environment AlarmsThis section describes how to check for external environment alarms. After setting theparameters for environment alarms, you need to verify the parameter settings by checking forexternal environment alarms.

ContextYou can manually trigger several external environment alarms to verify the parameter settings.If external environment alarms can be reported, the parameter settings are correct.

Procedure

Step 1 Manually trigger several external environment alarms. For details, see the appendix TriggeringMonitoring Device Alarms.

Step 2 Check for the external environment alarms on the M2000. For details, see Rectifying Faultsand Clearing Alarms Against the eNodeB Health Check Report. If external environmentalarms can be reported, the parameter settings are correct. If no external environment alarm isreported, set the parameters again or contact Huawei for technical support.

----End







104





Procedure






If... Then...






----End


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



105

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.













----End


Procedure

Step 1 Query the eNodeB state.1. On the M2000 tab page, choose Topology > Main Topology. The Main Topology tab

page is displayed.2. On the Main Topology tab page, select the target network element (NE) and right-click

Query Maintenance Mode. Then, the Query Maintenance Mode dialog box is displayed.



106


Step 2 Set the eNodeB state.1. On the M2000 tab page, choose Maintenance > Maintenance Mode. The Maintenance

Mode tab page is displayed.


3. Select the target NE and specify the time.4. Set NE Mode to NORMAL. The eNodeB is changed to the normal state.5. Click OK. The setting of the maintenance mode is complete.6. Ensure that the current the eNodeB state is NORMAL by executing Step 1 again.


----End

3.3.15 References to eNodeB CommissioningThis chapter describes references for commissioning eNodeBs, including introduction to thedeployment list, interface description, parameter description, and technical specifications.

Interface Description: eNodeB Commissioning WindowThis section describes the elements of the eNodeB Auto Deployment window and the functionof each element.

Main WindowFigure 3-20 shows the main window for eNodeB commissioning. Table 3-20 describes thewindow.



107

Figure 3-20 Main window for eNodeB commissioning


AreaNo.

ElementName

Description

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

2 Commissioning task list

Displays all the commissioning tasks and their progress. You canright-click a task, and then choose the corresponding menu itemfrom the shortcut menu to perform an operation.NOTEl By default, the GUI displays only commissioning tasks created by a

specific user. To view commissioning tasks created by other users,

click on the toolbar.

l When the system performs NE upgrades during the automaticconfiguration phase of a commissioning task, if you restart or deletethe commissioning task, the system does not restart NE upgrades butproceeds until the related NE upgrade task is complete. When thesystem displays The NE is performing the following task: ******.Please try later. in Description for a commissioning task, the NEupgrade task is running. If you want to perform automatic deploymentagain, wait until the NE upgrade task is complete. You can chooseSoftware > NE Upgrade Task Management > NE Upgrade Taskto query the NE upgrade task.

3 Shortcutmenu

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



108

AreaNo.

ElementName

Description

4 Operationresult

Records the results of each operation.

Alarm Commissioning Monitoring Window

Figure 3-21 shows the alarm commissioning monitoring window of eNodeBs. Table 3-21describes the window.

Figure 3-21 Alarm commissioning monitoring window of eNodeBs


AreaNo.

ElementName

Description

1 Alarm objecttree

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

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

3 Diagnosistask list

Displays the details about diagnosis tasks.



109

Window for Uploading Data FilesFigure 3-22 shows the window for uploading data files. Table 3-22 describes the window.

Figure 3-22 Window for uploading eNodeB data files


AreaNo.

ElementName

Description

1 File list Displays the files on the M2000 server.

2 Button Provides buttons for operations on uploading data files.

3 Tab named aftera data file type

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

4 Operation result Displays the details about the operations on uploading the typeof data file.

Parameters for the eNodeB Deployment ListThis section describes the parameters in the eNodeB deployment list for your reference.

Table 3-23 provides the meanings of the parameters.



110

NOTE

l If you use the CME to export the deployment list:

l Mandatory: indicates whether the parameter is mandatory. After the deployment list is imported,the M2000 performs non-blank check and validity check on each parameter.

l Export Using the CME by Default: identifies the parameter values that are to be exported or not tobe exported by default when you use the CME to export the site deployment list.

l Auto Deployment Window Can Be Edited: indicates whether a parameter value can be edited inthe auto deployment window after the eNodeB deployment list exported using the CME is importedinto the M2000.

l To use the M2000 to export the site deployment list, edit the list by referring to the Mandatory columnin Table 3-23.

l One of eNodeB ESN, Deployment ID, and eNodeB Longitude/eNodeB Latitude must be specified.

l Only in V100R005C00 and later versions, the Deployment ID can be used as the keyword in thedeployment.

l One of eNodeB Software Version, eNodeB Cold Patch Version, and eNodeB Hot Patch Version mustbe specified.

Table 3-23 Parameters for the eNodeB deployment list




eNodeB ID eNodeB ID. Yes Yes No

eNodeB Name Name of theeNodeB. Theparameter contains0 to 64 characters.

Yes Yes No

eNodeB ESN ESN on the eNodeBbackplane.The ESN uniquelyidentifies aneNodeB.



Yes

Deployment ID ID for deploying aneNodeB.



No



111




eNodeB Type NodeB type. Yes Yes No

eNodeB OMInterface Type

Type of the interfacefor carrying the OMchannel of theeNodeB.

Yes Yes No

eNodeB OMBearing Board

Board carried by theOM channel of theeNodeB.

Yes Yes No

eNodeB OM IPAddress

IP addresses of theOM channel for theeNodeB.

Yes Yes No

eNodeB OM IPSubnet Mask

IP address subnetmask of the OMchannel for theeNodeB.

Yes Yes No

eNodeB InterfaceIP Address

Interface IP addressused by the eNodeB.

Yes Yes No

eNodeB InterfaceIP Subnet Mask

Subnet mask of theinterface IP addressused by the eNodeB.

Yes Yes No

eNodeB M2000IP Address

IP address of theM2000.

Yes Yes No

eNodeB M2000IP Subnet Mask

Subnet mask for theIP address of theM2000.

Yes Yes No

eNodeB OM NextHop IP Address

Next-hop IP addressfrom the eNodeB tothe M2000.

Yes Yes No

eNodeB OMVLAN ID

VLAN ID of theeNodeB.




No



112




eNodeB OMVLAN Priority

VLAN priority ofthe OM channelused by the eNodeB.




No

eNodeB ServingSecGW IPAddress

IP address of thesecurity gatewayused by the eNodeB.



No

eNodeB ServingSecGW LocalName

Name of the securitygateway used by theeNodeB.



No

eNodeBLongitude

Longitude of theeNodeB.



No



113




eNodeB Latitude Latitude of theeNodeB.



No

eNodeB SoftwareVersion

Software versionnumber of the targeteNodeB.



Yes

eNodeB ColdPatch Version

Cold patch versionnumber of the targeteNodeB.



Yes

eNodeB HotPatch Version

Hot patch versionnumber of the targeteNodeB.



Yes



114




eNodeB PhysicalLocation

Physical position ofthe eNodeB. Thisparameter contains0 to 128 characters.

Yes Yes No

eNodeB CAName

Name of acertificationauthority (CA).



No

eNodeB CA URL Path for obtainingthe CA certificate.The format is http(s)://CAIP:CAport/CAPath.This parameter is setin secure scenariosfor certificateacquisition. Onlythe CMPv2 protocolis supported.



No

Contact Onsite personneland contactinformation.



Yes

3.4 Local Commissioning on the LMT (Without the SeGW)To commission an eNodeB on local using a local maintenance terminal (LMT), you need toupgrade the eNodeB software, download the configuration files, commission the antenna linedevices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish the



115

operation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000server.

3.4.1 Commissioning ProcedureThis section describes how to perform eNodeB commissioning on the LMT when no securitygateway (SeGW) is deployed.

Figure 3-23 shows the procedure for eNodeB commissioning on the LMT when no SeGW isdeployed.



116

Figure 3-23 Procedure for eNodeB commissioning on the LMT when no SeGW is deployed



117




Prepare for local eNodeB commissioning on the LMT,which involves obtaining the eNodeB information andcommissioning tools, and obtaining files. For details, see3.4.2 Preparations.

Mandatory

2 Localoperationson the LMT

Download and activate eNodeB software and dataconfiguration files on the LMT. For details, see 3.4.3Downloading and Activating the eNodeB Software andData Configuration File on the LMT.

Mandatory

3 Download the license file for eNodeB commissioning onthe LMT. For details, see 3.4.4 Downloading the Licensefor eNodeB Commissioning on the LMT.

Optional

4 Commission the antenna system on the LMT. For details,see 3.4.5 Commissioning the Antenna System on theLMT.

Optional

5 After the environment monitoring equipment is connected,commission the equipment so that it operates properly. Fordetails, see 3.4.6 Commissioning the EnvironmentMonitoring Equipment on the LMT.

Optional

6 Set the maximum transmit power of RRUs or RFUs. RRUand RFU are short for remote radio unit and radio frequencyunit, respectively. For details, see 3.4.7 Setting theMaximum Output Power for RRUs or RFUs.

Optional

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

Mandatory

8 Check the running status of the eNodeB on the LMT. Fordetails, see 3.4.9 Checking the Operating Status of theeNodeB on the LMT.

Mandatory

9 Verify the basic services of the eNodeB. For details, see3.4.10 Testing the Basic Services of the eNodeB.

Mandatory


After the eNodeB is correctly connected to the M2000,establish an operation and maintenance (OM) link for theeNodeB on the M2000. For details, see 3.4.11 Establishingan OML Between the M2000 and the eNodeB.

Mandatory

11 After eNodeB commissioning is complete and the eNodeBstarts to provide services properly, set the eNodeB to thenormal state on the M2000. For details, see 3.4.12 Settingan NE to the NORMAL Mode.

Mandatory



118


3.4.2 PreparationsBefore commissioning an eNodeB locally using an LMT when no SeGW is deployed, you needto collect related eNodeB information, obtain commissioning tools, and configure the FileTransfer Protocol (FTP) server.

Obtaining Related Information and Tools Required for eNodeB Commissioningon the LMT

Before local eNodeB commissioning on the local maintenance terminal (LMT), you must obtainrelated eNodeB information and commissioning tools.

Procedure




eNodeB name Planned by the operator

eNodeB ID Planned by the operator

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

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

Tool Description

Laptop l The hardware configuration, software configuration, andcommunication capabilities of the laptop must meetrequirements. For details, see System Requirements for theLMT Installation in the eNodeB LMT User Guide.

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

Ethernet cable LMPT: The Ethernet cable directly connects the laptop to theeNodeB. UMPT: The Ethernet cable connects the laptop to the USB-to-Ethernet port transfer cable.

Local maintenanceadapter (LMA)

The LMA connects the USB port on the UMPT to the Ethernet cable.

Testing UE The testing UE is functional and has been registered with the homesubscriber server (HSS).



119

----End

Configuring the FTP Server

This section describes how to log in to the eNodeB using the LMT to configure a File TransferProtocol (FTP) server before performing LMT-based local commissioning.

Prerequisitesl The firewall has been disabled between the FTP server and the eNodeB.

l All the FTP servers on the LMT PC have been disabled.

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

CAUTIONThe maximum length of the file name plus the path cannot be larger than the maximumlength of file name supported by the FTP server and cannot be more than 248 characters.(Some servers do not support a full-path file name consisting of 248 characters. For details,see the related FTP server manual.)

Context

The FTP server uses the IP address of the LMT PC. This IP address must be in the same networksegment as the OM IP address of the LMPT or UMPT board.

Procedure

Step 1 Enter the OM IP address of the main control board of the eNodeB. The default IP address is192.168.0.49.

Step 2 Click Go to. The LMT login page is displayed. The default user name is admin. The defaultpassword is case-sensitive and varies with the delivery date of the base station:

l The default password is hwbs@com if the base station is delivered on or after July 18, 2012.

l The default password is admin123 if the base station is delivered before July 18, 2012.

l The default password remains unchanged after a base station upgrade.

Step 3 Download the FTP server software if no FTP server is available.

1. On the LMT, click the Software Management tab. The Software Management tab pageis displayed.

2. In the navigation tree, double-click FTP Server Configuration. The FTP ServerConfiguration window is displayed, as shown in Figure 3-24.



120

Figure 3-24 FTP Server Configuration window

3. Click Download FTP Tool. The File Download-Security Warning dialog box isdisplayed.

4. Click Save to save the FTP server software package (SFTPServer.exe) to the LMT PC.

Step 4 Configure 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 from the shortcut menu. The FTP serverconfiguration dialog box is displayed, as shown in Figure 3-25.

Figure 3-25 FTP server configuration dialog box

3. Set User name, Password, and Working directory for the FTP server. The default username and password are admin. Working directory must be set to the directory where thesoftware and data configuration file are saved. The default transmission security mode isBoth.

4. Click OK.



121

Step 5 Save the FTP server configuration on the LMT main window.1. On the LMT, click Software Management. The Software Management tab page is

displayed.2. On the FTP Server Configure tab page, set IP address for the FTP server.3. Enter User name and Password based on the settings in Step 4.3. The default name and

password are admin.4. Click Save to save the FTP server configuration.

----End

3.4.3 Downloading and Activating the eNodeB Software and DataConfiguration File on the LMT

This section describes how to download and activate the eNodeB software and data configurationfile on the LMT. The eNodeB software and data configuration file take effect after the eNodeBis reset.

Prerequisitesl The LMT communicates properly with the eNodeB.l The FTP server is connected to the eNodeB in the same network segment and is functioning

properly.l Each FTP user has the permission to read a specified folder.l There is no firewall between the FTP server and the eNodeB.

Contextl You can obtain the eNodeB software package from http://support.huawei.com/ and save

it onto the local computer. The eNodeB software package has been digitally signed. If theeNodeB software package has been tampered with, a warning message is displayed whenthe package is being downloaded. In this situation, you must obtain a correct eNodeBsoftware package.

l The name of the data configuration file for local commissioning on the LMT is LMT.xml.The file name is case-sensitive. You can configure the data configuration file by referringto the eNodeB Initial Configuration Guide and save it onto the local PC. Then, change thefile name to LMT.xml.

l If you configure eNodeB parameters by running MML commands, do not download oractivate the LMT.xml file.

Procedure

Step 1 In the MML window on the LMT, run the LST VER command to query the active eNodeBsoftware version.

If... Then...

The active software version isthe target software version

Download and activate only the data configuration file.

The active software version isnot the target software version

Download and activate both the eNodeB software and dataconfiguration file.



122


Step 2 Download and activate the eNodeB software and data configuration file using the GUI or MMLcommands.

l Using GUI

1. On the LMT, click Software Management. The Software Management dialog box isdisplayed.

NOTEIf the software management function on the LMT is unavailable, the LMT provides a minimumconfiguration. In this case, you must supplement the LMT software package to a complete oneto download the eNodeB software and data configuration file using the software managementfunction. For details, see "How to Switch a Minimum LMT Package to a Complete LMTPackage" in eNodeB LMT User Guide.

2. In the navigation tree, double-click Download and Activate Software. The Downloadand Activate Software window is displayed, as shown in Figure 3-26.

Figure 3-26 Download and Activate Software window

3. Select tasks to be performed according to Step 1 and set the parameters related to thetasks.

NOTE

l You are advised to select YES(Delay Download) before downloading the eNodeB software.After the software activation is complete, you can use only the basic LMT functions. To useall LMT functions, run the SPL SOFTWARE command with Delay Download File SupplyFlag set to YES(Supply File that Support Delay).

l If you have selectedYES(Delay Download), but did not supplement the software, you canuse only the basic LMT functions. However, this does not affect the establishment of an OMLbetween the M2000 and the eNodeB.

l If you have selectedNO(Not Delay Download), you can use all LMT functions after thesoftware is activated. However, the eNodeB deployment will be prolonged for 10 minutes.

l You can select XML or DBS, depending on the type of the data configuration file to bedownloaded and activated.

l You must enter the version number of the target software for activation.

l You must save the eNodeB software package, data configuration file, and license file in thesame directory on the FTP server.



123

4. Click Execute. The eNodeB performs the selected tasks in sequence. There is a progressbar under the Execute button, indicating the current progress and task status. When theprogress bar of each task displays 100%, the download and activation are complete.

NOTE

l If a task is not selected, the eNodeB skips the task and goes to the next task.

l If a task fails, the eNodeB stops the task and subsequent tasks.

l After the data configuration file is activated, it will take effect by default when the eNodeB isreset.

l After the eNodeB software is activated, the software will take effect when the eNodeB isautomatically reset. If the data configuration file has been activated, it will also take effect whenthe eNodeB is reset.

l Using MML commands

1. Select tasks to be performed according to Step 1. Table 3-27 describes the mappingbetween tasks and MML commands.

Table 3-27 Mapping between tasks and MML commands

Sequence Task MML Command

1 Download theBootROM

DLD SOFTWARE

2 Activate theBootROM

ACT SOFTWARE

3 Download theeNodeB software

DLD SOFTWARE

4 Download the dataconfiguration file

DLD CFGFILE

5 Activate the dataconfiguration file

ACT CFGFILE

6 Activate theeNodeB software

ACT SOFTWARE

7 Query the softwaremanagement statusNOTE

The commandsupports queryingthe download,activation, andsupplement status ofthe software.

DSP SOFTSTATUS



124

CAUTIONl After the eNodeB software is downloaded and activated and the eNodeB is reset, log in to

the eNodeB using the LMT within 30 minutes. Otherwise, the eNodeB will roll back to thesource version.

l The eNodeB is automatically reset after the eNodeB software is activated. Before the eNodeBis automatically reset, do not run a reset command to reset the eNodeB or boards, power offthe eNodeB, or remove any boards. Otherwise, the software may fail to be downloaded oractivated, or the software and files may be cleared or damaged.

----End

3.4.4 Downloading the License for eNodeB Commissioning on theLMT

After downloading the commissioning license to the eNodeB on the LMT, you are authorizedto use the eNodeB software.

Prerequisitesl The LMT communicates properly with the eNodeB.l The commissioning license is available on the FTP server.

ContextApply for the commissioning license of the eNodeB with the help of Huawei technical support.

NOTEThe commissioning license has a time limit. Replace the commissioning license with a commercial license intime after the eNodeB commissioning is complete.

ProcedureStep 1 Run the INS LICENSE command to download and activate the license file on the eNodeB.

----End

3.4.5 Commissioning the Antenna System on the LMTThis section describes how to commission the antenna system on the local maintenance terminal(LMT), which involves commissioning antenna line devices (ALDs) such as remote electricaltilt (RET) antennas and tower-mounted amplifiers (TMAs) and measuring voltage standing waveratios (VSWRs).

Prerequisitesl The LMT communicates properly with the eNodeB.l The license for ALD management is available.

Commissioning the RET AntennaThis section describes how to use MML commands to commission the remote electrical tilt(RET) antenna, including downloading the RET software and data configuration file, calibrating



125

the RET antenna, setting the RET antenna downtilt, and querying RET overcurrent orundercurrent alarms. The RET downtilt must be configured based on the planned network data.Otherwise, the RET downtilt affects antenna coverage.

Prerequisitesl The antenna line device (ALD) is installed correctly.l The LMT communicates with the eNodeB properly.l The RET software and data configuration file are available.l The FTP server functions properly and is connected to the eNodeB correctly.l Each FTP user has the permission to read a specified folder.l There is no firewall between the FTP server and the eNodeB.

ContextFigure 3-27 shows the procedure for commissioning the RET antenna.

Figure 3-27 Procedure for commissioning the RET antenna



126

Table 3-28 describes the preparations for commissioning the RET antenna.

Table 3-28 Preparations for commissioning the RET antenna

Item Description

RET software The RET software is supplied by the ALDvendor.

RET data configuration file The RET data configuration file is suppliedby the ALD vendor. The configuration datavaries according to the vendor and RETantenna model.

Information about the RET downtilt The RET downtilt is defined in the networkplan.

l The RET antenna does not provide the file check function. If an incorrect RET dataconfiguration file is downloaded, the RET antenna may become unavailable.

l Calibrating the RET antenna is mandatory after the RET antenna is installed. If you skipthis step, the RET downtilt may be incorrect and the network coverage is affected.

l The RET antenna does not need to be calibrated again after you reset or power off the RETantenna. After calibrating the RET antenna, you must set the RET downtilt again to ensurethat the downtilt is correct without affecting the network coverage.

l Setting an RET downtilt takes a maximum of 2 minutes.

Procedure


If... Run...



MOD ANTENNAPORT






127



NOTE


If... Then...













NOTE

If the RET downtilt fails to be calibrated, check for the cabinet, subrack, and slot configurations and themapping between the RET antenna and the sector. If the configurations and mapping are incorrect, run theMOD RETSUBUNIT command to set them gain, and calibrate the RET downtilt again.

If you run this command without specifying any parameters, RET antennas can be calibrated in batches.

Step 9 Set the RET downtilt.If the downtilt has been set in the data configuration file, perform Step 9.3 to check whether theRET downtilt is calibrated successfully.1. Query the downtilt range supported by the RET antenna.



128

MML command: DSP RETDEVICEDATA2. Set the RET downtilt.

MML command:MOD RETTILT




----End

Commissioning the TMAThis section describes how to use MML commands to commission the tower-mounted amplifier(TMA). Commissioning the TMA aims to check whether the current TMA software version isthe same as the target TMA software version. If they are different, load the target TMA software.After the TMA software is loaded, the TMA automatically resets. The software then takes effectand the TMA starts working properly.

Prerequisitesl The TMA is installed correctly.l The TMA software is available.l The LMT communicates properly with the eNodeB.l The FTP server functions properly and is properly connected to the eNodeB on the same

network segment.l Each FTP user has the permission to read a specified folder.

CAUTIONEnsure that there is no firewall between the FTP server and the eNodeB. If a firewall is installedon the PC, disable it.

Contextl As a part of the antenna system, the TMA is used to amplify the received weak signals.l The TMA software is supplied by the antenna line device (ALD) vendor.l If incorrect TMA software is loaded, the TMA may not work property.

Procedure




129

If... Run...



MOD ANTENNAPORT




Step 4 Check whether the TMA starts working and whether the TMA gain is set correctly.MML command: DSP TMASUBUNITl If the maximum gain is the same as the minimum gain, the TMA has a fixed gain. In this

situation, you are not allowed to set any gains.



NOTE


If... Then...




Go to Step 6.






130




----End

Measuring the VSWR

This section describes how to measure the voltage standing wave ratio (VSWR) to verify theantenna system.

Prerequisitesl The antenna system has been properly installed on the eNodeB.

l The local maintenance terminal (LMT) communicates properly with the eNodeB.

Procedure

Step 1 Run the LST RRU command to query the VSWR alarm threshold.

Step 2 Run the STR VSWRTEST command to start a VSWR test.

If... Then...

The test value is less thanthe VSWR alarm threshold

The antenna system is properly installed. End thecommissioning.

The test value is greaterthan or equal to the VSWRalarm threshold

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

----End

3.4.6 Commissioning the Environment Monitoring Equipment onthe LMT

This section describes how to check the environment monitoring equipment on the LMT. Afterthe environment monitoring equipment is connected, you need to commission it so that itfunctions properly.

Setting Environment Alarm Parameters

This section describes how to set environment alarm parameters within the permissible rangeas required.



131

Prerequisitesl The local maintenance terminal (LMT) communicates properly with the eNodeB.l The environment monitoring equipment has been configured.l The DIP switches on the environment monitoring device are properly set. For details, see

the APM30H&TMC11H&IBBS200D&IBBS200T(Ver.B) Product Description,APM30H&TMC11H&IBBS200D&IBBS200T(Ver.C) Product Description and EMUAUser Guide.

ContextThe remote radio unit (RRU), universal power environment unit (UPEU) in the baseband unit(BBU), environment monitoring unit type A (EMUA), and power monitoring unit (PMU) in theAPM30H are all equipped with extended alarm ports.

The external environment alarm and the extended alarm port are already bound together. Fordetails, see Table 3-29.

Table 3-29 Extended alarm ports

MO MML Command Description

AlmPort SET ALMPORT This command is used to set the input port ofenvironment signals.

If the alarm ID of an external environment alarm is predefined, the following steps can beskipped. For details about the predefined alarm IDs, see eNodeB Alarm Reference.

Procedure

Step 1 Run the LST ALMPORT command to check whether external alarm ports are configuredcorrectly, whether ports are enabled, and whether port types and alarm severities are the sameas the configured values.

Step 2 Run the SET ENVALMPARA command to set the name, severity, and event type of an externalenvironment alarm.

NOTE

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

----End

Checking for External Environment AlarmsThis section describes how to check for external environment alarms. After setting theparameters for environment alarms, you must verify the parameter settings by checking forexternal environment alarms.

ContextYou can manually trigger external environment alarms to verify the parameter settings. If theexternal environment alarms can be reported correctly, the parameter settings are correct.



132

Procedure

Step 1 Manually trigger external environment alarms. For details, see the appendix TriggeringMonitoring Device Alarms.

Step 2 Check for active alarms on the local maintenance terminal (LMT). For details, see 3.4.8Handling the eNodeB Alarms on the LMT. If the external environment alarms can be reportedcorrectly, the parameter settings are correct. If no external environment alarm is reported, resetthe parameters or contact Huawei for technical support.

----End









Procedure







133


If... Then...






----End

3.4.8 Handling the eNodeB Alarms on the LMTThis section describes how to handle the alarms generated during the commissioning.

Prerequisites

The LMT communicates properly with the eNodeB.

Procedure

Step 1 On the LMT, click the Alarm/Event button. The Alarm/Event tab page is displayed.

Step 2 Check for active alarms on the Engineering Alarm tab page under the Browse Alarm/Eventtab page.

If ... Then ...

No active alarm exists End the task.

Active alarms exist Go to Step 3.

Step 3 Double-click an active alarm. The Detailed Information dialog box is displayed.

Step 4 Click Solution... to know the detailed information and alarm handling procedure. Clear the activealarm by following the alarm handling procedure.

----End

3.4.9 Checking the Operating Status of the eNodeB on the LMTThis section describes how to check the operating status of the eNodeB on the local maintenanceterminal (LMT).



134

PrerequisitesThe LMT communicates properly with the eNodeB.

ContextTable 3-30 lists the eNodeB device checklist.

Table 3-30 eNodeB device checklist

Check Item Description

eNodeB type Check the eNodeB type in data configuration.

eNodeBsoftware version

Check the active eNodeB software, including the version and operatingstatus.

Hardware status Check the status of the radio frequency (RF) unit, receive channel,transmit channel, and boards.

Interface status Check the configuration related to IP paths, common public radiointerface (CPRI) ports, remote maintenance channels, E1/T1 ports,Ethernet ports, and Stream Control Transmission Protocol (SCTP) linksof the eNodeB.

Cell status Check the cell status.

Active alarmquery

Check for active alarms of the eNodeB.

Procedure

Step 1 On the LMT, click Self-Test. On the displayed Self-Test tab page, a man-machine language(MML) command script with the complete parameter settings is automatically imported to thecommand area.

Step 2 Click Execute. The execution result is displayed in the area below Execute.

NOTE

If all items pass the check, the eNodeB operates properly. Otherwise, check for active alarms and clear them. Ifall active alarms are cleared but the fault persists, contact Huawei for technical support.

----End


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



135

l The FTP server for testing the basic services is available.

l The WWW server for testing the basic services is available.













----End

3.4.11 Establishing an OML Between the M2000 and the eNodeBThis section describes how to establish an operation and maintenance link (OML) between theM2000 and the eNodeB on the M2000 client.

Prerequisitesl The transmission link between the eNodeB and M2000 is functioning properly.

l The M2000 server and client are running properly.

l You have obtained the eNodeB information such as the name, IP address, version, andadministrative region of the eNodeB.



136

ContextTo reduce maintenance workload, the M2000 enables you to create eNodeBs in batches in thetopology. For details, see Creating Multiple Physical NEs in the M2000 Online Help. Thissection describes the procedure for creating an eNodeB.

Procedure

Step 1 Create an eNodeB in the topology.1. On the M2000 client, choose Topology > Main Topology. The Main Topology tab page

is displayed, as shown in Figure 3-28.

Figure 3-28 Main Topology tab page

2. In the Physical Root navigation tree or the physical view, right-click the subnet for the

eNodeB to be created and choose New > NE from the shortcut menu. The Create NE dialogbox is displayed, as shown in Figure 3-29.



137

Figure 3-29 Create NE dialog box

3. In the Create NE dialog box, select the specific eNodeB from Access Network Series.

4. Configure the eNodeB information in the right window of the dialog box.

5. Click OK to create the eNodeB.

NOTE

The Create NE Progress dialog box is displayed, indicating the NE creation progress. After the eNodeBis successfully created, the M2000 automatically obtains the eNodeB configuration information.

If the network connection between the M2000 and the created eNodeB is faulty, the eNodeB is stilldisplayed in the specified location in the topology. However, the eNodeB is disconnected and is shown

as .

6. Click Close to close the Progress dialog box.

Step 2 About 5 minutes later, observe the eNodeB icon on the Main Topology tab page.

If... Then...

The eNodeB icon is

The OML fails to be established. ContactHuawei for technical support.

The eNodeB icon is The OML is successfully established.

----End



138


Procedure

Step 1 Query the eNodeB state.

1. On the M2000 tab page, choose Topology > Main Topology. The Main Topology tabpage is displayed.

2. On the Main Topology tab page, select the target network element (NE) and right-clickQuery Maintenance Mode. Then, the Query Maintenance Mode dialog box is displayed.


Step 2 Set the eNodeB state.

1. On the M2000 tab page, choose Maintenance > Maintenance Mode. The MaintenanceMode tab page is displayed.


3. Select the target NE and specify the time.

4. Set NE Mode to NORMAL. The eNodeB is changed to the normal state.

5. Click OK. The setting of the maintenance mode is complete.

6. Ensure that the current the eNodeB state is NORMAL by executing Step 1 again.


----End

3.5 Local Commissioning on the LMT (with the SeGW)To commission an eNodeB on local using a local maintenance terminal (LMT), you need toupgrade the eNodeB software, download the configuration files, commission the antenna linedevices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish theoperation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000server.

3.5.1 Commissioning ProcedureThis section describes how to perform eNodeB commissioning on the LMT when the securitygateway (SeGW) is deployed.

Figure 3-30 shows the procedure for eNodeB commissioning on the LMT when the SeGW isdeployed.



139

Figure 3-30 Procedure for eNodeB commissioning on the LMT when the SeGW is deployed



140




Prepare for performing LMT-based commissioning, whichinvolves obtaining the eNodeB information andcommissioning tools, configuring the security equipment,and obtaining associated files and digital certificates. Fordetails, see 3.5.2 Preparations.

Mandatory

2 Localoperationson the LMT

Download and activate eNodeB software and dataconfiguration files on the LMT. For details, see 3.5.3Downloading and Activating the eNodeB Software andData Configuration File on the LMT.

Mandatory

3 Download the license file for eNodeB commissioning onthe LMT. For details, see 3.5.4 Downloading the Licensefor eNodeB Commissioning on the LMT.

Optional

4 Commission the antenna system on the LMT. For details,see 3.5.5 Commissioning the Antenna System on theLMT.

Optional

5 After the environment monitoring equipment is connected,commission the equipment so that it operates properly. Fordetails, see 3.5.6 Commissioning the EnvironmentMonitoring Equipment on the LMT.

Optional

6 Set the maximum transmit power of RRUs or RFUs. RRUand RFU are short for remote radio unit and radio frequencyunit, respectively. For details, see 3.5.7 Setting theMaximum Output Power for RRUs or RFUs.

Optional

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

Mandatory

8 Check the running status of the eNodeB on the LMT. Fordetails, see 3.5.9 Checking the Operating Status of theeNodeB on the LMT.

Mandatory

9 Verify the basic services of the eNodeB. For details, see3.5.10 Testing the Basic Services of the eNodeB.

Mandatory


After the eNodeB is correctly connected to the M2000,establish an operation and maintenance (OM) link for theeNodeB on the M2000. For details, see 3.5.11 Establishingan OML Between the M2000 and the eNodeB.

Mandatory

11 After eNodeB commissioning is complete and the eNodeBstarts to provide services properly, set the eNodeB to thenormal state on the M2000. For details, see 3.5.12 Settingan NE to the NORMAL Mode.

Mandatory



141


3.5.2 PreparationsBefore local eNodeB commissioning on the LMT when the SeGW is deployed in the network,you need to collect related eNodeB information, obtain commissioning tools, and configure theFile Transfer Protocol (FTP) server. If digital certificate files are unavailable in PKI-basedauthentication mode, obtain digital certificates and add them to the eNodeB using the LMT.

Obtaining Related Information and Tools Required for eNodeB Commissioningon the LMT

Before local eNodeB commissioning on the local maintenance terminal (LMT), you must obtainrelated eNodeB information and commissioning tools.

Procedure




eNodeB name Planned by the operator

eNodeB ID Planned by the operator

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

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

Tool Description

Laptop l The hardware configuration, software configuration, andcommunication capabilities of the laptop must meetrequirements. For details, see System Requirements for theLMT Installation in the eNodeB LMT User Guide.

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

Ethernet cable LMPT: The Ethernet cable directly connects the laptop to theeNodeB. UMPT: The Ethernet cable connects the laptop to the USB-to-Ethernet port transfer cable.

Local maintenanceadapter (LMA)

The LMA connects the USB port on the UMPT to the Ethernet cable.

Testing UE The testing UE is functional and has been registered with the homesubscriber server (HSS).



142

----End

Obtaining Digital CertificatesBefore commissioning an eNodeB, obtain the operator's root certificate and the eNodeBcertificate request file. The operator's root certificate is used for the eNodeB to authenticate theSeGW when establishing IPSec tunnels, and the eNodeB certificate request file is used to obtainthe operator-issued device certificate in offline mode.

ContextFigure 3-31 shows the procedure for obtaining digital certificates.

Figure 3-31 Procedure for obtaining digital certificates

Procedure

Step 1 Obtain the operator's root certificate.

Step 2 Generate the certificate request file on the eNodeB.Run the CRE CERTREQFILE command with FILENAME set to the name of the certificaterequest file (in the XXX.req format) and REQMODE set to NEW.

----End

Configuring the Security EquipmentOn the live networks, operators use different security gateway (SeGW) equipment with differentconfiguration data. Based on the operators' network planning and network design, the equipmentis configured according to the user guide of a corresponding equipment type. The followingconfigurations and operations are based on Huawei S6500 series Ethernet switches. If theeNodeB performs IEEE 802.1X-based access control, operations on authentication devices arebased on Huawei Authentication, Authorization and Accounting (AAA) server.



143

Prerequisitesl Quidway S6500 Series Ethernet Switches Operation Manual is available. You can obtain

the document from http://support.huawei.com.

l HUAWEI AAA Commissioning Guide is available. You can obtain the document fromhttp://support.huawei.com.

l If IEEE 802.1X-based access control is adopted, the operator must use the authenticationaccess equipment that supports IEEE 802.1X-based access control authentication and thecorresponding AAA server that supports Extensible Authentication Protocol (EAP).

Context

In scenarios with the security gateway (SeGW) deployed, the SeGW must be configured. If theeNodeB performs IEEE 802.1X-based access control, authentication access equipment andauthentication server must be configured. Generally, the authentication server refers to theAuthentication, Authorization and Accounting (AAA) server.

l Table 3-34 describes the SeGW configurations.

Table 3-34 SeGW configurations

Item Description

IP address Set two port IP addresses for the SeGW. One is used to communicatewith the eNodeB through the untrusted domain, and the other is used tocommunicate with the core network through the trusted domain.

Route Configure the routes to the M2000, S-GW, mobility management entity(MME), eNodeB port IP address, S1 signaling and service IP addresses,and OM IP address.

IKE localname

Set this parameter for the SeGW.

ike proposal l Set authentication method to digital certificate mode.l Set authentication algorithm to SHA_1 or MD5. Generally, set

this parameter to SHA_1.l Set encryption algorithm to AES or DES. Generally, set this

parameter to AES.l Set DH group to DH group2.

acl Set this parameter to allow all IP packets to pass through the SeGW.Assume that the SeGW is Huawei eduemon. Then, set this parameterto permit ip.

ike peer Set a key or certificate based on the authentication method specified inthe IKE proposal. Set local id type to name. Set the IKE proposal basedon the preceding settings. Set the IKE version to V1 or V2.

ipsecproposal

Set encapsulation mode to tunnel or transport. Generally, set thisparameter to tunnel.Set transform to esp or AH. Generally, set this parameter to esp.Set esp authentication to SHA_1, and set esp encryption to AES.



144



Item Description

ipsec policy-template

Set this parameter to template for the SeGW.Set an ACL rule based on the preceding setting.Set psf group to DH group2.Set ike peer and ipsec proposal based on the preceding settings.

ipsec policy Set this parameter based on the value of ipsec policy-template.

ipsec bindingto port

Set this parameter to bind the policy specified by ipsec policy to aplanned port.

NOTEDifferent from the versions earlier than V100R005C00, if the SeGW functions as a security gatewayas well as a firewall in V100R005C00, you are required to enable UDP 67 and UDP 68 ports on theSeGW.

l When the authentication access equipment is used, the authentication mode and theauthentication method must be set to Remote Authentication Dial-In User Service(RADIUS) and EAP respectively, because certificate authentication is adopted currently.

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

Procedure

Step 1 Check the configuration of the SeGW by referring to Table 3-34.

Step 2 Ensure that the Huawei root CA certificate and Huawei CRL file are configured on the SeGW.

Step 3 Configure the authentication access equipment.

The authentication access equipment may vary according to different operators. HuaweiQuidway S6500 series Ethernet switches are taken as an example.

1. Enable the global IEEE 802.1X-based access control feature.Run sys to enter the system command state. Run dot1x to enable the global IEEE 802.1X-based access control feature.

2. Enable the IEEE 802.1X feature on the port.For example, to enable the IEEE 802.1X feature for port 3, run the interfaceGigabitEthernet 1/0/3 command to enter the port view, and run the dot1x command toenable IEEE 802.1X feature.

3. Run dot1x authentication-method { chap | pap | eap } to set the authentication methodto EAP.

4. Configure the VLAN and add the route relationship between the transmission network andAAA server.

For example, run the vlan 4 command to add a VLAN whose ID is 4. Run the interfacevlan 4 command to enter the VLAN view, and run the ip add 10.147.209.38255.255.255.0 command to add an IP address and subnet mask for the VLAN. Run theip route-static 10.166.27.48 24 10.147.209.1 command to add the switch-to-AAA serverroute relationship.



145

5. Set the parameters of AAA server on the switch.Run the radius scheme accounting command to create a RADIUS solution namedradius1, and enter the RADIUS view. Then, run the primary authentication 10.166.27.481812 command to set the port No. to 1812 and the IP address to 10.166.27.48 for the primaryauthentication server. Then, run key authentication itellin to set the authentication key toitellin.

For details, see Quidway S6500 Series Ethernet Switches Operation Manual.

Step 4 Configure the eNodeB CA certificate for the AAA server.

The AAA server may vary according to different operators. The descriptions here take theHuawei AAA server as an example. For details, see HUAWEI AAA Commissioning Guide.

1. Upload the CA certificate of a terminal user to the iscc2/config/secert directory of infoXAAA server.

2. Change the file names of the user certificate and private key in the SCPCFG.INI file. Ensurethat the file names are consistent with the file names of the user certificate and private keyuploaded in Step 4.1.

----End

Configuring the FTP Server

This section describes how to log in to the eNodeB using the LMT to configure a File TransferProtocol (FTP) server before performing LMT-based local commissioning.

Prerequisitesl The firewall has been disabled between the FTP server and the eNodeB.l All the FTP servers on the LMT PC have been disabled.l The software and data configuration file are available and saved in the same directory on

the LMT PC.


Context

The FTP server uses the IP address of the LMT PC. This IP address must be in the same networksegment as the OM IP address of the LMPT or UMPT board.

Procedure

Step 1 Enter the OM IP address of the main control board of the eNodeB. The default IP address is192.168.0.49.



146

Step 2 Click Go to. The LMT login page is displayed. The default user name is admin. The defaultpassword is case-sensitive and varies with the delivery date of the base station:l The default password is hwbs@com if the base station is delivered on or after July 18, 2012.l The default password is admin123 if the base station is delivered before July 18, 2012.l The default password remains unchanged after a base station upgrade.

Step 3 Download the FTP server software if no FTP server is available.1. On the LMT, click the Software Management tab. The Software Management tab page

is displayed.2. In the navigation tree, double-click FTP Server Configuration. The FTP Server

Configuration window is displayed, as shown in Figure 3-32.

Figure 3-32 FTP Server Configuration window

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

displayed.4. Click Save to save the FTP server software package (SFTPServer.exe) to the LMT PC.

Step 4 Configure 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 from the shortcut menu. The FTP serverconfiguration dialog box is displayed, as shown in Figure 3-33.



147

Figure 3-33 FTP server configuration dialog box

3. Set User name, Password, and Working directory for the FTP server. The default user

name and password are admin. Working directory must be set to the directory where thesoftware and data configuration file are saved. The default transmission security mode isBoth.

4. Click OK.

Step 5 Save the FTP server configuration on the LMT main window.1. On the LMT, click Software Management. The Software Management tab page is

displayed.2. On the FTP Server Configure tab page, set IP address for the FTP server.3. Enter User name and Password based on the settings in Step 4.3. The default name and

password are admin.4. Click Save to save the FTP server configuration.

----End

Downloading the Digital Certificate on the LMT

When the security gateway (SeGW) is deployed in the network, the digital certificate must beadded to the eNodeB on the local maintenance terminal (LMT) if there is no data configurationfile.

Prerequisitesl The LMT communicates properly with the eNodeB.l The FTP user can access the specified directory.l There is no firewall between the FTP server and the eNodeB.l The FTP server configuration is complete.l The operator's root Certificate Authority (CA) certificate and Charging Rule Language

(CRL) file are available, and they are saved in the same directory as that of the eNodeBsoftware and data configuration files.



148


Procedure

Step 1 Download the operator's root CA certificate and CRL file to the eNodeB by running the DLDCERTFILE command.

Step 2 Add the operator's root CA certificate by running the ADD TRUSTCERT.

Step 3 Add the operator's CRL file by running the ADD CRL command.

Step 4 Export the certificate request file by running the ULD NEFILE command.

Step 5 Use the certificate request file to apply for the operator-issued device certificate in offline mode.

Step 6 Download the operator-issued device certificate to the eNodeB by running the DLDCERTFILE command.

Step 7 Load the operator-issued device certificate to the eNodeB by running the ADD CERTMKcommand.

Step 8 Activate the operator-issued device certificate on the eNodeB by running the MODAPPCERT command.

----End

3.5.3 Downloading and Activating the eNodeB Software and DataConfiguration File on the LMT

This section describes how to download and activate the eNodeB software and data configurationfile on the LMT. The eNodeB software and data configuration file take effect after the eNodeBis reset.

Prerequisitesl The LMT communicates properly with the eNodeB.l The FTP server is connected to the eNodeB in the same network segment and is functioning

properly.l Each FTP user has the permission to read a specified folder.l There is no firewall between the FTP server and the eNodeB.

Contextl You can obtain the eNodeB software package from http://support.huawei.com/ and save

it onto the local computer. The eNodeB software package has been digitally signed. If theeNodeB software package has been tampered with, a warning message is displayed whenthe package is being downloaded. In this situation, you must obtain a correct eNodeBsoftware package.



149


l The name of the data configuration file for local commissioning on the LMT is LMT.xml.The file name is case-sensitive. You can configure the data configuration file by referringto the eNodeB Initial Configuration Guide and save it onto the local PC. Then, change thefile name to LMT.xml.

l If you configure eNodeB parameters by running MML commands, do not download oractivate the LMT.xml file.

Procedure

Step 1 In the MML window on the LMT, run the LST VER command to query the active eNodeBsoftware version.

If... Then...

The active software version isthe target software version

Download and activate only the data configuration file.

The active software version isnot the target software version

Download and activate both the eNodeB software and dataconfiguration file.

Step 2 Download and activate the eNodeB software and data configuration file using the GUI or MMLcommands.l Using GUI

1. On the LMT, click Software Management. The Software Management dialog box isdisplayed.

NOTEIf the software management function on the LMT is unavailable, the LMT provides a minimumconfiguration. In this case, you must supplement the LMT software package to a complete oneto download the eNodeB software and data configuration file using the software managementfunction. For details, see "How to Switch a Minimum LMT Package to a Complete LMTPackage" in eNodeB LMT User Guide.

2. In the navigation tree, double-click Download and Activate Software. The Downloadand Activate Software window is displayed, as shown in Figure 3-34.

Figure 3-34 Download and Activate Software window



150

3. Select tasks to be performed according to Step 1 and set the parameters related to thetasks.

NOTE

l You are advised to select YES(Delay Download) before downloading the eNodeB software.After the software activation is complete, you can use only the basic LMT functions. To useall LMT functions, run the SPL SOFTWARE command with Delay Download File SupplyFlag set to YES(Supply File that Support Delay).

l If you have selectedYES(Delay Download), but did not supplement the software, you canuse only the basic LMT functions. However, this does not affect the establishment of an OMLbetween the M2000 and the eNodeB.

l If you have selectedNO(Not Delay Download), you can use all LMT functions after thesoftware is activated. However, the eNodeB deployment will be prolonged for 10 minutes.

l You can select XML or DBS, depending on the type of the data configuration file to bedownloaded and activated.

l You must enter the version number of the target software for activation.

l You must save the eNodeB software package, data configuration file, and license file in thesame directory on the FTP server.

4. Click Execute. The eNodeB performs the selected tasks in sequence. There is a progressbar under the Execute button, indicating the current progress and task status. When theprogress bar of each task displays 100%, the download and activation are complete.

NOTE

l If a task is not selected, the eNodeB skips the task and goes to the next task.

l If a task fails, the eNodeB stops the task and subsequent tasks.

l After the data configuration file is activated, it will take effect by default when the eNodeB isreset.

l After the eNodeB software is activated, the software will take effect when the eNodeB isautomatically reset. If the data configuration file has been activated, it will also take effect whenthe eNodeB is reset.

l Using MML commands

1. Select tasks to be performed according to Step 1. Table 3-35 describes the mappingbetween tasks and MML commands.

Table 3-35 Mapping between tasks and MML commands


1 Download theBootROM

DLD SOFTWARE

2 Activate theBootROM

ACT SOFTWARE

3 Download theeNodeB software

DLD SOFTWARE

4 Download the dataconfiguration file

DLD CFGFILE

5 Activate the dataconfiguration file

ACT CFGFILE



151


6 Activate theeNodeB software

ACT SOFTWARE

7 Query the softwaremanagement statusNOTE

The commandsupports queryingthe download,activation, andsupplement status ofthe software.

DSP SOFTSTATUS

CAUTIONl After the eNodeB software is downloaded and activated and the eNodeB is reset, log in to

the eNodeB using the LMT within 30 minutes. Otherwise, the eNodeB will roll back to thesource version.

l The eNodeB is automatically reset after the eNodeB software is activated. Before the eNodeBis automatically reset, do not run a reset command to reset the eNodeB or boards, power offthe eNodeB, or remove any boards. Otherwise, the software may fail to be downloaded oractivated, or the software and files may be cleared or damaged.

----End

3.5.4 Downloading the License for eNodeB Commissioning on theLMT

After downloading the commissioning license to the eNodeB on the LMT, you are authorizedto use the eNodeB software.

Prerequisitesl The LMT communicates properly with the eNodeB.l The commissioning license is available on the FTP server.

ContextApply for the commissioning license of the eNodeB with the help of Huawei technical support.

NOTEThe commissioning license has a time limit. Replace the commissioning license with a commercial license intime after the eNodeB commissioning is complete.



152

Procedure

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

----End

3.5.5 Commissioning the Antenna System on the LMTThis section describes how to commission the antenna system on the local maintenance terminal(LMT), which involves commissioning antenna line devices (ALDs) such as remote electricaltilt (RET) antennas and tower-mounted amplifiers (TMAs) and measuring voltage standing waveratios (VSWRs).

Prerequisitesl The LMT communicates properly with the eNodeB.l The license for ALD management is available.

Commissioning the RET AntennaThis section describes how to use MML commands to commission the remote electrical tilt(RET) antenna, including downloading the RET software and data configuration file, calibratingthe RET antenna, setting the RET antenna downtilt, and querying RET overcurrent orundercurrent alarms. The RET downtilt must be configured based on the planned network data.Otherwise, the RET downtilt affects antenna coverage.

Prerequisitesl The antenna line device (ALD) is installed correctly.l The LMT communicates with the eNodeB properly.l The RET software and data configuration file are available.l The FTP server functions properly and is connected to the eNodeB correctly.l Each FTP user has the permission to read a specified folder.l There is no firewall between the FTP server and the eNodeB.

ContextFigure 3-35 shows the procedure for commissioning the RET antenna.



153

Figure 3-35 Procedure for commissioning the RET antenna

Table 3-36 describes the preparations for commissioning the RET antenna.

Table 3-36 Preparations for commissioning the RET antenna

Item Description

RET software The RET software is supplied by the ALDvendor.

RET data configuration file The RET data configuration file is suppliedby the ALD vendor. The configuration datavaries according to the vendor and RETantenna model.

Information about the RET downtilt The RET downtilt is defined in the networkplan.



154

l The RET antenna does not provide the file check function. If an incorrect RET dataconfiguration file is downloaded, the RET antenna may become unavailable.

l Calibrating the RET antenna is mandatory after the RET antenna is installed. If you skipthis step, the RET downtilt may be incorrect and the network coverage is affected.

l The RET antenna does not need to be calibrated again after you reset or power off the RETantenna. After calibrating the RET antenna, you must set the RET downtilt again to ensurethat the downtilt is correct without affecting the network coverage.

l Setting an RET downtilt takes a maximum of 2 minutes.

Procedure


If... Run...



MOD ANTENNAPORT






NOTE


If... Then...





155

If... Then...











NOTE

If the RET downtilt fails to be calibrated, check for the cabinet, subrack, and slot configurations and themapping between the RET antenna and the sector. If the configurations and mapping are incorrect, run theMOD RETSUBUNIT command to set them gain, and calibrate the RET downtilt again.

If you run this command without specifying any parameters, RET antennas can be calibrated in batches.

Step 9 Set the RET downtilt.If the downtilt has been set in the data configuration file, perform Step 9.3 to check whether theRET downtilt is calibrated successfully.1. Query the downtilt range supported by the RET antenna.

MML command: DSP RETDEVICEDATA2. Set the RET downtilt.

MML command:MOD RETTILT



Step 10 Check whether overcurrent or undercurrent alarms are generated on the RET antenna. Ifovercurrent or undercurrent alarms are generated, clear them by referring to eNodeB AlarmReference.



156

MML command: DSP RETPORT

----End

Commissioning the TMAThis section describes how to use MML commands to commission the tower-mounted amplifier(TMA). Commissioning the TMA aims to check whether the current TMA software version isthe same as the target TMA software version. If they are different, load the target TMA software.After the TMA software is loaded, the TMA automatically resets. The software then takes effectand the TMA starts working properly.

Prerequisitesl The TMA is installed correctly.l The TMA software is available.l The LMT communicates properly with the eNodeB.l The FTP server functions properly and is properly connected to the eNodeB on the same

network segment.l Each FTP user has the permission to read a specified folder.

CAUTIONEnsure that there is no firewall between the FTP server and the eNodeB. If a firewall is installedon the PC, disable it.

Context

l As a part of the antenna system, the TMA is used to amplify the received weak signals.l The TMA software is supplied by the antenna line device (ALD) vendor.l If incorrect TMA software is loaded, the TMA may not work property.

Procedure


If... Run...



MOD ANTENNAPORT




157



Step 4 Check whether the TMA starts working and whether the TMA gain is set correctly.MML command: DSP TMASUBUNITl If the maximum gain is the same as the minimum gain, the TMA has a fixed gain. In this

situation, you are not allowed to set any gains.l If the TMA is not working, contact Huawei for technical support.


NOTE


If... Then...




Go to Step 6.







----End

Measuring the VSWRThis section describes how to measure the voltage standing wave ratio (VSWR) to verify theantenna system.



158

Prerequisitesl The antenna system has been properly installed on the eNodeB.l The local maintenance terminal (LMT) communicates properly with the eNodeB.

Procedure

Step 1 Run the LST RRU command to query the VSWR alarm threshold.

Step 2 Run the STR VSWRTEST command to start a VSWR test.

If... Then...

The test value is less thanthe VSWR alarm threshold

The antenna system is properly installed. End thecommissioning.

The test value is greaterthan or equal to the VSWRalarm threshold

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

----End

3.5.6 Commissioning the Environment Monitoring Equipment onthe LMT

This section describes how to check the environment monitoring equipment on the LMT. Afterthe environment monitoring equipment is connected, you need to commission it so that itfunctions properly.

Setting Environment Alarm ParametersThis section describes how to set environment alarm parameters within the permissible rangeas required.

Prerequisitesl The local maintenance terminal (LMT) communicates properly with the eNodeB.l The environment monitoring equipment has been configured.l The DIP switches on the environment monitoring device are properly set. For details, see

the APM30H&TMC11H&IBBS200D&IBBS200T(Ver.B) Product Description,APM30H&TMC11H&IBBS200D&IBBS200T(Ver.C) Product Description and EMUAUser Guide.

ContextThe remote radio unit (RRU), universal power environment unit (UPEU) in the baseband unit(BBU), environment monitoring unit type A (EMUA), and power monitoring unit (PMU) in theAPM30H are all equipped with extended alarm ports.

The external environment alarm and the extended alarm port are already bound together. Fordetails, see Table 3-37.



159

Table 3-37 Extended alarm ports

MO MML Command Description

AlmPort SET ALMPORT This command is used to set the input port ofenvironment signals.

If the alarm ID of an external environment alarm is predefined, the following steps can beskipped. For details about the predefined alarm IDs, see eNodeB Alarm Reference.

Procedure

Step 1 Run the LST ALMPORT command to check whether external alarm ports are configuredcorrectly, whether ports are enabled, and whether port types and alarm severities are the sameas the configured values.

Step 2 Run the SET ENVALMPARA command to set the name, severity, and event type of an externalenvironment alarm.

NOTE

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

----End

Checking for External Environment Alarms

This section describes how to check for external environment alarms. After setting theparameters for environment alarms, you must verify the parameter settings by checking forexternal environment alarms.

ContextYou can manually trigger external environment alarms to verify the parameter settings. If theexternal environment alarms can be reported correctly, the parameter settings are correct.

Procedure

Step 1 Manually trigger external environment alarms. For details, see the appendix TriggeringMonitoring Device Alarms.

Step 2 Check for active alarms on the local maintenance terminal (LMT). For details, see 3.4.8Handling the eNodeB Alarms on the LMT. If the external environment alarms can be reportedcorrectly, the parameter settings are correct. If no external environment alarm is reported, resetthe parameters or contact Huawei for technical support.

----End




160




Prerequisitesl The RRU or RFU is connected properly.

l The local maintenance terminal (LMT) or M2000 communicates properly with the eNodeB.

l You have logged in to the M2000 as administrator.

Context

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



Procedure






If... Then...







161


----End

3.5.8 Handling the eNodeB Alarms on the LMTThis section describes how to handle the alarms generated during the commissioning.


Procedure

Step 1 On the LMT, click the Alarm/Event button. The Alarm/Event tab page is displayed.

Step 2 Check for active alarms on the Engineering Alarm tab page under the Browse Alarm/Eventtab page.

If ... Then ...

No active alarm exists End the task.

Active alarms exist Go to Step 3.

Step 3 Double-click an active alarm. The Detailed Information dialog box is displayed.

Step 4 Click Solution... to know the detailed information and alarm handling procedure. Clear the activealarm by following the alarm handling procedure.

----End

3.5.9 Checking the Operating Status of the eNodeB on the LMTThis section describes how to check the operating status of the eNodeB on the local maintenanceterminal (LMT).


ContextTable 3-38 lists the eNodeB device checklist.

Table 3-38 eNodeB device checklist


eNodeB type Check the eNodeB type in data configuration.



162


eNodeBsoftware version

Check the active eNodeB software, including the version and operatingstatus.

Hardware status Check the status of the radio frequency (RF) unit, receive channel,transmit channel, and boards.

Interface status Check the configuration related to IP paths, common public radiointerface (CPRI) ports, remote maintenance channels, E1/T1 ports,Ethernet ports, and Stream Control Transmission Protocol (SCTP) linksof the eNodeB.

Cell status Check the cell status.

Active alarmquery

Check for active alarms of the eNodeB.

Procedure

Step 1 On the LMT, click Self-Test. On the displayed Self-Test tab page, a man-machine language(MML) command script with the complete parameter settings is automatically imported to thecommand area.

Step 2 Click Execute. The execution result is displayed in the area below Execute.

NOTE

If all items pass the check, the eNodeB operates properly. Otherwise, check for active alarms and clear them. Ifall active alarms are cleared but the fault persists, contact Huawei for technical support.

----End


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






163










----End

3.5.11 Establishing an OML Between the M2000 and the eNodeBThis section describes how to establish an operation and maintenance link (OML) between theM2000 and the eNodeB on the M2000 client.

Prerequisitesl The transmission link between the eNodeB and M2000 is functioning properly.

l The M2000 server and client are running properly.

l You have obtained the eNodeB information such as the name, IP address, version, andadministrative region of the eNodeB.

Context

To reduce maintenance workload, the M2000 enables you to create eNodeBs in batches in thetopology. For details, see Creating Multiple Physical NEs in the M2000 Online Help. Thissection describes the procedure for creating an eNodeB.

Procedure

Step 1 Create an eNodeB in the topology.

1. On the M2000 client, choose Topology > Main Topology. The Main Topology tab pageis displayed, as shown in Figure 3-36.



164

Figure 3-36 Main Topology tab page

2. In the Physical Root navigation tree or the physical view, right-click the subnet for the

eNodeB to be created and choose New > NE from the shortcut menu. The Create NE dialogbox is displayed, as shown in Figure 3-37.

Figure 3-37 Create NE dialog box

3. In the Create NE dialog box, select the specific eNodeB from Access Network Series.4. Configure the eNodeB information in the right window of the dialog box.



165

5. Click OK to create the eNodeB.

NOTE

The Create NE Progress dialog box is displayed, indicating the NE creation progress. After the eNodeBis successfully created, the M2000 automatically obtains the eNodeB configuration information.

If the network connection between the M2000 and the created eNodeB is faulty, the eNodeB is stilldisplayed in the specified location in the topology. However, the eNodeB is disconnected and is shown

as .

6. Click Close to close the Progress dialog box.

Step 2 About 5 minutes later, observe the eNodeB icon on the Main Topology tab page.

If... Then...

The eNodeB icon is

The OML fails to be established. ContactHuawei for technical support.

The eNodeB icon is The OML is successfully established.

----End


Procedure

Step 1 Query the eNodeB state.

1. On the M2000 tab page, choose Topology > Main Topology. The Main Topology tabpage is displayed.

2. On the Main Topology tab page, select the target network element (NE) and right-clickQuery Maintenance Mode. Then, the Query Maintenance Mode dialog box is displayed.


Step 2 Set the eNodeB state.

1. On the M2000 tab page, choose Maintenance > Maintenance Mode. The MaintenanceMode tab page is displayed.


3. Select the target NE and specify the time.

4. Set NE Mode to NORMAL. The eNodeB is changed to the normal state.

5. Click OK. The setting of the maintenance mode is complete.

6. Ensure that the current the eNodeB state is NORMAL by executing Step 1 again.



166


----End



167

4 Appendix

About This Chapter

This chapter describes how to encrypt files in a Universal Serial Bus (USB) storage device andprovides the eNodeB commissioning data sheet.

4.1 eNodeB Binding Using a Bar Code ScannerThis section describes how to bind the eNodeB using a bar code scanner, which involves printinga bar code, setting the bar code scanner, and using a bar code scanner to scan a bar code.

4.2 Triggering Monitoring Device AlarmsAfter setting monitoring device alarms, you must manually trigger the alarms to check whetherthe monitoring device can correctly report them. If the monitoring device can correctly reportthe alarms, the related settings are correct.

4.3 Checking the Status of IndicatorsThis section describes how to check the status of indicators to determine whether the eNodeBis running properly.

4.4 Configuring the Preconfigurationn FileThis section describes how to configure the preconfiguration file.

4.5 Applying Integrity and Encryption Protection to Files in the USB Flash DriveTo prevent information leak or unauthorized modification, integrity protection or encryptionprotection is required for the files in the Universal Serial Bus (USB) flash drive.

4.6 Binding Modes Between the M2000 and the eNodeBIn eNodeB automatic discovery during PnP remote commissioning, the eNodeB periodicallysends dynamic host configuration protocol (DHCP) requests to the DHCP server of M2000before the operation and maintenance channel (OMCH) is set up. After receiving the DHCPrequests, the DHCP server matches the electronic serial number (ESN), deployment ID, andinformation about the latitude and longitude of the eNodeB in the request message with that inthe eNodeB deployment list. In this way, the eNodeB is bound to the M2000. This sectiondescribes modes and process for binding an eNodeB to the M2000.

4.7 Data Sheet for eNodeB Commissioning

eNodeBCommissioning Guide 4 Appendix


168

This section provides the data sheet that is used to record the process and results of the eNodeBcommissioning. The Data Sheet for Commissioning used at different sites may be different. Thistable serves as a reference only.



169

4.1 eNodeB Binding Using a Bar Code ScannerThis section describes how to bind the eNodeB using a bar code scanner, which involves printinga bar code, setting the bar code scanner, and using a bar code scanner to scan a bar code.

4.1.1 Printing a Bar Code on the M2000This section describes how to print a bar code on the M2000.

Prerequisitesl Deployment IDs have been planned, and a deployment list has been imported to the M2000.

For details about how to import a deployment list, see Uploading Data Files.l A printer for printing bar codes has been ready and is communicating properly with the

M2000.

ContextBar codes are identified by the width of black and white bars. The resolution for printing barcodes must be set to 1200 DPI or a greater value to ensure that a bar code scanner can successfullyread bar codes. A professional bar code printer or a common laser printer can be used.

Figure 4-1 shows the process of binding the eNodeB using a bar code scanner.



170

Figure 4-1 Process of binding the eNodeB using a bar code scanner

Procedure

Step 1 In the iManager M2000, choose Configuration > Auto Deployment > eNodeB AutoDeployment. The eNodeB Auto Deployment dialog box is displayed, as shown in Figure4-2.



171

Figure 4-2 eNodeB Auto Deployment dialog box

Step 2 In the eNodeB Auto Deployment dialog box, click the Deployment List tab. On theDeployment List tab page, select a list to be printed, right-click it, and then choose PrintBarcode from the shortcut menu. The Print Barcode dialog box is displayed, as shown inFigure 4-3.



172

Figure 4-3 Print Barcode dialog box

NOTE

l You can print one deployment list separately or more deployment lists in batches.

l You can print only the information about one deployment ID on a bar code sheet.

Step 3 Click OK. The print page setup dialog box is displayed.

Step 4 Select a correct printer, set print attributes, and then click Print.

----End

4.1.2 Setting a Bar Code ScannerThis section describes how to set a bar code scanner before you use a bar code scanner to bindthe eNodeB for the first time. The setting method of a bar code scanner varies with its model.For details, see the related operation guide. The following procedure uses a Honeywell 3800G(USB-type) bar code scanner as an example.

Prerequisitesl A personal computer (PC) is available.



173

l A Honeywell 3800G (USB-type) bar code scanner with configurations before shipment isavailable.

l An electronic operation guide to the bar code scanner is available.

Context

The bar code scanner must meet the following requirements:

l Supporting Code128 bar codes.

l Supporting a USB port and low-speed interrupt transmission mode and complying withgeneral USB keyboard specifications.

l Supporting plug-and-play. No driver is required for the operating systems such as WindowsXP and Windows 2003.

l Supporting laser scanning.

l Complying with Restriction of Hazardous Substances (RoHS).

Honeywell 3800G (USB port) bar code scanner is recommended.

NOTEYou need to set a bar code scanner only once before using it on eNodeBs.

Procedure

Step 1 Print the electronic operation guide on a piece of A4 paper to facilitate scanning of setting codes.

Step 2 Connect the bar code scanner to the PC through a USB port.

CAUTIONDo not connect a bar code scanner that is not set to the eNodeB because this may result inabnormal eNodeB data processing.

For details about how to check whether a bar code scanner is set, see step 4.

Step 3 Scan the setting codes printed on the A4 paper.1. Scan the Standard Product Defaults code, as shown in Figure 4-4.

Figure 4-4 Standard Product Defaults code

2. Scan the USB Keyboard (PC) code, as shown in Figure 4-5.



174

Figure 4-5 USB Keyboard (PC) code

3. Scan the Save code, as shown in Figure 4-6.

Figure 4-6 Save code

NOTETo prevent configured parameters from being lost, you are advised to scan the Save code once aftertwo parameters are configured.

4. Scan the Manual Trigger code, as shown in Figure 4-7.

Figure 4-7 Manual Trigger code

5. Scan the Add CR Suffix code, as shown in Figure 4-8.

Figure 4-8 Add CR Suffix code

6. Repeat step 3.c and save the parameter settings.

Step 4 Check whether the bar code scanner is set correctly.



175

Remove the bar code scanner and reconnect it to the PC. Create a .txt file on the PC and openit. Scan a printed eNodeB ID using the bar code scanner and check whether a correct deploymentID is displayed in the file. If an incorrect deployment ID is displayed, contact Huawei fortechnical support.

----End

4.1.3 Binding the eNodeB by Scanning a Bar CodeThis section describes how to bind the eNodeB by scanning a bar code.

Prerequisitesl A bar code sheet containing bar code information is available.l The bar code information is consistent with the actual eNodeB information.l A bar code scanner is available.l The eNodeB has been powered onl The eNodeB communicates with the M2000 properly.

ContextAfter the bar code scanner scans a bar code successfully, the eNodeB reports the deploymentID on the bar code to the M2000. If the deployment ID is consistent with that in the eNodeBdeployment list on the M2000, the M2000 automatically binds the eNodeB.

Procedure

Step 1 Connect the bar code scanner to the USB port on the main control board.

NOTE

l You can scan a bar code about 10s after the indicator on the bar code scanner turns on.

l Ensure that the scanner camera is less than 30 cm away from the bar code.

Step 2 Use the bar code scanner to read the deployment ID on the bar code to the eNodeB.

After the eNodeB obtains the deployment ID, the bar code scanner emits a sound and its laserindicator turns off. In addition, you can check whether the eNodeB binding is successful byviewing the RUN indicator on the main control board and checking download of the softwarepackage. For details, see 4.3 Checking the Status of Indicators.

Step 3 Remove the bar code scanner after the bar code is successfully scanned.



176

NOTE

l If one of the following problems occurs, replace the hardware as follows:

l If the bar code scanner is faulty, replace the bar code scanner and scan the bar code again.

l If the bar code is damaged, print the bar code and scan the bar code again.

l If the bar code scanner cannot be connected to the eNodeB, check whether the USB port on theeNodeB main control board is functioning properly. If the USB port is faulty, replace the maincontrol board and scan the bar code again.

l If the hardware functions properly but the eNodeB does not download the software package from theM2000 after scanning, perform the following operations:

l If binding the eNodeB fails because an incorrect deployment ID is scanned and the eNodeB cannotfind the corresponding configuration, the eNodeB fails to establish an OML. When this occurs,scan the correct deployment ID.

l If an incorrect deployment ID is scanned and used to establish an OML, and if the eNodeB bindsthe M2000 server to the O&M IP address, the eNodeB with a correct deployment ID fails to bedeployed. When this occurs, download correct configuration and then scan the correct deploymentID for deployment.

----End

4.2 Triggering Monitoring Device AlarmsAfter setting monitoring device alarms, you must manually trigger the alarms to check whetherthe monitoring device can correctly report them. If the monitoring device can correctly reportthe alarms, the related settings are correct.

4.2.1 Triggering PMU AlarmsPower monitoring unit (PMU) alarms include burglar, water, and smoke alarms.

Prerequisitesl The PMU is running properly.l PMU parameters are set correctly.

ContextDiesel generator or solar device alarms can be triggered only when a diesel generator or a solardevice is configured.

Procedurel Trigger PMU alarms. For details, see Table 4-1.



177

Table 4-1 Triggering PMU alarms

Alarm ID AlarmName

AlarmTriggeringParameter

Default Alarm Value or TriggeringMethod

25672 BurglarAlarm

Special BooleanAlarm Flag

1. Run the MOD PMU command withGS_DISABLE(Gating SensorDisabled) in the Special BooleanAlarm Flag selected.

2. Install the door status sensor properlyand keep the cabinet door open formore than 10s.

25670 WaterAlarm


1. Run the MOD PMU command withWS_DISABLE(Water-ImmersedSensor Disabled) in the SpecialBoolean Alarm Flag selected.

2. Install the water sensor properly andimmerse the water sensor or its probein water for more than 10s.

25671 SmokeAlarm


1. Run the MOD PMU command withSS_DISABLE(Smog SensorDisabled) in the Special BooleanAlarm Flag selected.

2. Install the smoke sensor properly andproduce smoke around the smokesensor for more than 30s. Generally,smoke alarms are difficult to trigger.

NOTEYou must clear smoke alarms manually.

25600 Monitoring DeviceMaintenance LinkFailure

None Keep the communication cabledisconnected from the COM-IN port onthe FMU for 1 minute.

25622 MainsInput OutofThreshold

l AC VoltageAlarm UpperThreshold

l AC VoltageAlarm LowerThreshold

1. Run the DSP PMU command toquery the current AC voltage.

2. Run the LST PMU command toquery the upper and lower thresholdsfor AC voltage alarms.

3. Run the MOD PMU command withAC Voltage Alarm UpperThreshold set to a value 10 V lessthan the current AC voltage or ACVoltage Alarm Lower Thresholdset to a value 10 V greater than thecurrent AC voltage. Then, wait formore than 10s.



178

Alarm ID AlarmName



25628 AC SurgeProtectorFault

None l Disconnect the alarm cable from alightning rod that can be maintainedindependently.

l Use a faulty lightning rod that cannotbe maintained independently.

25621 PowerSupplyDCOutputOut ofRange

l DC VoltageAlarm UpperThreshold

l DC VoltageAlarm LowerThreshold

1. Run the LST PMU command toquery the lower threshold for DCvoltage alarms.

2. Run the MOD PMU command tochange the lower threshold for DCvoltage alarms to 51.4 V. (Thedefault threshold is 45 V.)

3. Turn off the AC power supply anduse batteries to supply power.

4. Run the DSP PMU command toquery the busbar voltage until thebusbar voltage is less than the lowerthreshold for DC voltage alarms.

25623 LoadDisconnect

l LoadShutdownFlag

l LoadShutdownVoltage

1. Run the LST PMU command toquery the load shutdown flag andload shutdown voltage. (This alarmcan be tested together with the PowerSupply DC Output Out of Rangealarm.)

2. Run the MOD PMU command withLoad Shutdown Flag set toENABLE and the load shutdownvoltage (default value: 44 V) set 51.3V. (This alarm can be tested togetherwith the Power Supply DC OutputOut of Range alarm.)


4. Run the DSP PMU command toquery the busbar voltage until thebusbar voltage is less than the loadshutdown voltage.



179

Alarm ID AlarmName



25624 BatteryPowerUnavailable (batteryalarm:Batteriesmust beconfigured.)

l ShutdownTemperature

l ShutdownVoltage

1. Run the LST BATTERY commandto query the low voltage shutdownflag and shutdown voltage.

2. Run the MOD BATTERYcommand with Low VoltageShutdown Flag set to ENABLE andthe shutdown voltage (default value:43 V) set to 51 V. (This alarm can betested together with the PowerSupply DC Output Out of Rangealarm.)


4. Run the DSP PMU command toquery the busbar voltage until thebusbar voltage is less than theshutdown voltage.

25625 BatteryCurrentOut ofRange(batteryalarm:Batteriesmust beconfigured.)

None Turn off batteries for more than 1minute. For new batteries, you areadvised to turn off the AC power supplyand test this alarm about 5 minutes afterthe batteries discharge.

25630 PowerModuleandMonitoring ModuleCommunicationFailure(PSUalarm: APSU mustbeconfigured.)

None 1. Run the LST PSU command to querythe PSU status.

2. Keep the PSU disconnected for morethan 10s. For example, if PSUs inslots 1 and 2 are configured on theLMT, remove the PSU in slot 1 or 2.If the PSU in slot 3 is removed, thisalarm cannot be triggered. Inaddition, ensure that the systempower is sufficient after you removea PSU.



180

Alarm ID AlarmName



25626 PowerModuleAbnormal(PSUalarm: APSU mustbeconfigured.)

None Use a small rod to stop the PSU fan untilthe indicator on the PSU turns yellow orred. Ensure that the system power issufficient after you remove a PSU.

25652 CabinetTemperatureUnacceptable

l CabinetTemperatureAlarm UpperThreshold

l CabinetTemperatureAlarm LowerThreshold

1. Run the DSP PMU command toquery the current cabinettemperature.

2. Run the LST PMU command toquery the upper and lower thresholdsfor cabinet temperature alarms.

3. Run the MOD PMU command withCabinet Temperature AlarmUpper Threshold set to a value 5°Cless than the current cabinettemperature or CabinetTemperature Alarm LowerThreshold set to a value 5°C greaterthan the current cabinet temperature.Then, wait for more than 10s.

25653 CabinetHumidityunacceptable

l CabinetHumidityAlarm UpperThreshold

l CabinetTemperatureAlarm LowerThreshold

1. Run the DSP PMU command toquery the current cabinet humidity.

2. Run the LST PMU command toquery the upper and lower thresholdsfor cabinet humidity alarms.

3. Run the MOD PMU command withCabinet Humidity Alarm UpperThreshold set to a value 10% lessthan the current cabinet relativehumidity (RH) or CabinetHumidity Alarm LowerThreshold set to a value 10% greaterthan the current cabinet RH. Then,wait for more than 10s.



181

Alarm ID AlarmName



25654 BatteryTemperatureUnacceptable(batteryalarm:Batteriesmust beconfigured inadvance.)

l TemperatureAlarm UpperThreshold

l TemperatureAlarm LowerThreshold

1. Run the DSP PMU command toquery the current batterytemperature.

2. Run the LST BATTERY commandto query the upper and lowerthresholds for battery temperaturealarms.

3. Run the MOD BATTERYcommand with TemperatureAlarm Upper Threshold set to avalue 5°C less than the currentbattery temperature or TemperatureAlarm Lower Threshold set to avalue 5°C greater than the currentbattery temperature. Then, wait formore than 10s.

25602 SensorFailure

Special AnalogAlarm Flag

If no sensor is connected, run the MODPMU command with the temperature orhumidity sensor option in SpecialAnalog Alarm Flag.

25631 Load FuseBroken

None Remove the load fuse.

25632 BatteryCabinHeaterFault

None Use a faulty battery compartment heater.

25633 PMUInternalInterfaceCommunicationFailure

None Remove the communication cablebetween the PMU and the sensor signalboard.

25634 BatteryNot InPosition

None 1. Do not connect batteries to the powersupply system.

2. Power on the power system and runthe ADD BATTERY command toadd batteries. Then, wait for morethan 1 minute.

25601 Monitoring DeviceHardwareFault

None Use a faulty monitoring board. (Exercisecaution when triggering this alarm.)



182

----End

4.2.2 Triggering FMU AlarmsFan monitoring unit (FMU) alarms include burglar, water, and smoke alarms.

Prerequisitesl The FMU is running properly.l FMU parameters have been correctly set.

ContextNo burglar, water, smoke, or external Boolean alarm is available for indoor eNodeBs.

Procedurel Trigger FMU alarms. For details, see Table 4-2.

Table 4-2 FMU alarm triggering

AlarmID

AlarmName

Alarm TriggeringParameter


25672 BurglarAlarm


1. Enter the MOD FMU command withthe GS_DISABLE(Gating SensorDisabled) check box in the SpecialBoolean Alarm Flag drop-down listbox cleared.

2. Install the door status sensor properlyand keep the cabinet door open formore than 10s.

25670 WaterAlarm


1. Run the MOD FMU command withthe WS_DISABLE(Water-Immersed Sensor Disabled) checkbox in the Special Boolean AlarmFlag drop-down list box cleared.

2. Install the water sensor properly andimmerse the sensor probe or thewater sensor in water for more than10s.



183

AlarmID

AlarmName



25671 SmokeAlarm


1. Run the MOD FMU command withthe SS_DISABLE(Smog SensorDisabled) check box in the SpecialBoolean Alarm Flag drop-down listbox cleared.

2. Install the smoke sensor properly andgenerate smoke around the smokesensor for more than 30s (smokealarms are generally difficult totrigger).

NOTESmoke alarms must be manually cleared.

25600 MonitoringDeviceMaintenanceLinkFailure

None Remove the communication cable fromthe COM_IN port on the PMU for 1minute.

25602 SensorFailure

Special AnalogAlarm Flag

Remove the temperature sensor from theTEMP port on the FMU.

25673 FanStalled

None Remove a normal fan.

25656 CabinetAir InletTemperatureUnacceptable

Upper threshold forcabinet air inlettemperature alarms(60° by default) andlower threshold forcabinet air inlettemperature alarms(-20° by default)

Trigger the cabinet air inlet temperatureto be greater than the upper threshold orto be less than the lower threshold (thisalarm is difficult to trigger because theupper and lower thresholds cannot bechanged).

25655 CabinetAirOutletTemperatureUnacceptable

Upper threshold forcabinet air outlettemperature alarms(80° by default) andlower threshold forcabinet air outlettemperature alarms(-20° by default)

Trigger the cabinet air outlet temperatureto be greater than the upper threshold orto be less than the lower threshold (thisalarm is difficult to trigger because theupper and lower thresholds cannot bechanged).

25601 MonitoringDeviceHardware Fault

None Use a faulty monitoring board (exercisecaution when performing thisoperation).



184

----End

4.2.3 Triggering TCU AlarmsTemperature control unit (TCU) alarms include burglar, water, and smoke alarms.

Prerequisitesl The TCU is running properly.l TCU parameters have been correctly set.

Procedurel Trigger TCU alarms. For details, see Table 4-3.

Table 4-3 TCU alarm triggering

Alarm ID AlarmName


Default Alarm Value orTriggering Method

25672 BurglarAlarm

Special Boolean AlarmFlag

1. Enter the MOD TCU commandwith the GS_DISABLE(Gating Sensor Disabled)check box in the SpecialBoolean Alarm Flag drop-down list box cleared.

2. Install the door status sensorproperly and keep the cabinetdoor open for more than 10s.

25670 WaterAlarm


1. Run the MOD TCU commandwith the WS_DISABLE(Water-Immersed SensorDisabled) check box in theSpecial Boolean Alarm Flagdrop-down list box cleared.

2. Install the water sensor properlyand immerse the sensor probe orthe water sensor in water formore than 10s.



185

Alarm ID AlarmName



25671 SmokeAlarm


1. Run the MOD TCU commandwith the SS_DISABLE(SmogSensor Disabled) check box inthe Special Boolean AlarmFlag drop-down list box cleared.

2. Install the smoke sensorproperly and generate smokearound the smoke sensor formore than 30s (smoke alarmsare generally difficult totrigger).

NOTESmoke alarms must be manuallycleared.

25628 AC SurgeProtectorFault

None l Disconnect the alarm cable froma surge protector that can beindependently maintained.

l Use a faulty surge protector thatcannot be independentlymaintained.

25600 Monitoring DeviceMaintenance LinkFailure

None Keep the communication cabledisconnected from the COM_INport on the TCU for 1 minute.

25601 Monitoring DeviceHardwareFault

None Use a faulty monitoring board(exercise caution when performingthis operation).

25602 SensorFailure

Special Analog AlarmFlag

Remove the temperature sensorfrom the TEMP port on the TCU.

25655 CabinetAir OutletTemperatureUnacceptable

Upper threshold forcabinet air outlettemperature alarms(80° by default) andlower threshold forcabinet air outlettemperature alarms(-20° by default)

1. Run the DSP TCU command toquery the current air outlettemperature.

2. Run the MOD TCU commandto set the upper threshold forcabinet air outlet temperaturealarms to be less than the currentair outlet temperature or thelower threshold for cabinet airoutlet temperature alarms to begreater than the current air outlettemperature.



186

Alarm ID AlarmName



25673 FanStalled

None Remove a normal fan.

----End

4.2.4 Triggering EMU AlarmsEnvironment monitoring unit (EMU) alarms include infrared, water, and smoke alarms.

Prerequisitesl The EMU is running properly.l EMU parameters have been correctly set.

ContextTo trigger EMU alarms, turn on the related alarm switches.

Procedurel Trigger EMU alarms. For details, see Table 4-4.

Table 4-4 EMU alarm triggering

Alarm ID AlarmName



25672 BurglarAlarm


1. Enter the MOD EMUcommand with theGS_DISABLE(GatingSensor Disabled) checkbox in the Special BooleanAlarm Flag drop-down listbox cleared.

2. Install the door statussensor properly and keepthe cabinet door open formore than 10s.



187

Alarm ID AlarmName



25672 BurglarAlarm


1. Run the MOD EMUcommand with theIS_DISABLE(InfraredSensor Disabled) checkbox in the Special BooleanAlarm Flag drop-down listbox cleared.

2. Use either of the followingmethods to trigger thisalarm:l Install the infrared

sensor properly andmove in its monitoringarea.

l Do not install theinfrared sensor andshort-circuit the infraredsensor port.

25670 WaterAlarm


1. Run the MOD EMUcommand with theWS_DISABLE(Water-Immersed SensorDisabled) check box in theSpecial Boolean AlarmFlag drop-down list boxcleared.

2. Install the water sensorproperly and immerse thesensor probe or the watersensor in water for morethan 10s.

25671 SmokeAlarm


1. Run the MOD EMUcommand with theSS_DISABLE(SmogSensor Disabled) checkbox in the Special BooleanAlarm Flag drop-down listbox cleared.

2. Install the smoke sensorproperly and generatesmoke around the smokesensor for more than 30s(smoke alarms aregenerally difficult totrigger).



188

Alarm ID AlarmName



25651 AmbientHumidityUnacceptable

Ambient humidity 1. Run the LST EMUcommand to query thethreshold for ambienthumidity alarms.

2. Run the DSP EMUcommand to query thecurrent ambient humidity.

3. Run the MOD EMUcommand to set thethreshold for ambienthumidity alarms to begreater than or less than thecurrent ambient humidity.

25650 AmbientTemperatureUnacceptable

Ambient temperature 1. Run the LST EMUcommand to query thethreshold for ambienttemperature alarms.

2. Run the DSP EMUcommand to query thecurrent ambienttemperature.

3. Run the MOD EMUcommand to set thethreshold for ambienttemperature alarms to begreater than or less than thecurrent ambienttemperature.

25600 MonitoringDeviceMaintenanceLinkFailure

None Keep the communication cabledisconnected from theCOM_IN port on the EMU for1 minute.

NOTEBurglar, infrared, and smoke alarms must be manually cleared.

----End

4.3 Checking the Status of IndicatorsThis section describes how to check the status of indicators to determine whether the eNodeBis running properly.



189

Context

Indicator status of the functional eNodeB

If the status of the indicators on the boards or auxiliary devices is the same as that shown inTable 4-5, the eNodeB is running properly.

Table 4-5 Indicator status of the functional eNodeB

Indicator Status

RUN indicator on each board in the BBU Blinking (on for 1s and off for 1s)

Status of the ALM indicators on the LMPT,UMPT, LBBP, UTRP, PMU, AFMU andEMUA

Off

STATE indicator on the FAN of theBBU3900

Blinking green

CPRI indicator on the LBBP Steady green

ACT indicator on the LMPT/UMPT Steady on

VSWR indicator on the RRU/RFU Off

Indicator on the USB flash drive Steady on

Indicator status for common faults

Figure 4-9 shows the indicator status for common faults.

Figure 4-9 Indicator status for common faults



190

Procedure

Step 1 Check the indicator on each board in the BBU.1. Check the RUN indicator on each board.

If the RUNIndicator Is...

It Indicates that... Then...

Blinking (on for 1sand off for 1s)

The board is runningproperly.

Go to Step 1.2.

Steady on The board is startingup.

Wait until the board startup iscomplete.

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

The board is loadingsoftware, or the boardis in the incorrect slot.

Wait 5 minutes and then check thestatus of the RUN indicator again.If the RUN indicator is still blinking(on for 0.125s and off for 0.125s),check whether the board is inserted intothe correct slot. If not, reinstall theboard.

Off The power supply isunavailable, or theboard is faulty.

l Check whether the eNodeB hasbeen powered on. If not, power onthe eNodeB.

l Reinstall the board to checkwhether the fault is rectified. If thefault persists, replace the board.

2. Check the ALM indicators on the LMPT, UMPT, LBBP and UTRP.

If the ALMIndicator Is...


Off The LMPT, UMPT,LBBP and UTRP arefunctioning properly.

Go to Step 1.3.

Steady on The LMPT, UMPT,LBBP or UTRP isfaulty.

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



191



Blinking An alarm is generated,and the alarm may becaused by anassociated board orport fault. Therefore,you must identify thefault before replacingthe board.

l Check whether the RUN indicatorson the other boards are blinkingquickly.– If the RUN indicator on the

EMUA is blinking quickly,check the RS485 signal cableconnection.

– Check the RUN indicators onthe LMPT, UMPT andLBBP.

l Check the connection between thedry contact alarm signal cable andthe corresponding port on theUPEU.

l Reinstall the LBBP, LMPT andUMPT to check whether the fault isrectified.

l If the GPS antenna system isconfigured, check whether it isproperly connected.

3. Check the STATE indicator on the FAN.

If the STATEIndicator Is...


Blinking green The module isfunctioning properly.

Go to Step 1.4.

Blinking red The module is faulty. Reinstall the board to check whetherthe fault is rectified. If the faultpersists, replace the board.

4. Check the CPRI indicator on the LBBP.

If the CPRI IndicatorIs...


Steady green The common public radiointerface (CPRI) link isfunctional, and the RRUand LRFU are functional.

Go to Step 1.5.



192

If the CPRI IndicatorIs...


Red indicator off The optical module is notconfigured properly orpowered on, or no cable isconnected to the opticalmodule. Or the indicator isfaulty.

If the RRU or LRFU isconnected to this port,check whether theinstallation conforms to theconfiguration plan.l If the installation does

not conform to theconfiguration plan,reinstall the RRUaccording to theconfiguration plan.

l If the installationconforms to theconfiguration plan,replace the boards.

Steady red The optical module doesnot receive or send datacorrectly, the CPRIconnection is faulty, or theoptical cable is broken.

Handle the alarm accordingto the related suggestions.For details, see eNodeBAlarm Reference

Blinking red (on for 1s andoff for 1s)

The CPRI link is out oflock, or the RRU or LRFUon the CPRI link reportsVSWR alarms.

If the ACT indicator is inthe testing state (on for 1sand off for 1s), handle thealarm according to therelated suggestions. If theACT indicator is not in thetesting state, the CPRI linkis unlocked due to dual-clock-source lock orincompatible CPRI rate.For details, see the eNodeBAlarm Reference.

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

The RRU or LRFUhardware on the CPRI linkis faulty.

Handle the alarm accordingto the related suggestions,see eNodeB AlarmReference

5. Check the ACT indicators on the LMPT and UMPT.

If the ACT Indicator Is... It Indicates that... Then...

Steady on The board is runningproperly.

Go to Step 2.



193

If the ACT Indicator Is... It Indicates that... Then...

Off The board is not activated. l Check whether theeNodeB is powered on.If not, power on theboard.

l Check whether theboard is configured. Ifnot, configure theboard.

l Check whether theboard is manuallyblocked. If it is, unblockthe board.

Blinking at 4 Hz (on for0.125s and off for 0.125s)

The OM channel is faulty. Check the OM channel andrectify the fault.

Blinking at 4 Hz (blinkingfor 2s and off for 2s,blinking for 2s means on for0.125s and off for 0.125s.)

The service is not ready. l Check the cell status. Ifthe cell is not activated,activate the cell. If theCell Unavailable alarmis generated, handle thealarm according to therelated suggestions.

l Check whether the S1interface is normal. Ifnot, handle the alarmaccording to the relatedsuggestions.

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



Off The module or thedevice is functioningproperly.

The check is complete.

Steady on The module or thedevice is faulty.

Reinstall the module or power on thedevice again to check whether the fault iscleared.If the fault persists, record the fault andthe indicator status in the Data Sheet forCommissioning. Then, clear the fault onthe LMT or M2000.

----End



194

4.4 Configuring the Preconfigurationn FileThis section describes how to configure the preconfiguration file.

Procedure

Step 1 Enter the board software package name.

In the PRECONFIG of the preconfiguration file, enter the board software package name basedon the format ALL=XXXX.

NOTE.

l XXXX indicates the board software package name.

l Querying the board software package name: The board software package name corresponding to aboard type can be queried by checking the notes in the preconfiguration file. The notes in thepreconfiguration file are classified based on the format ;AAAA:BBBB. BBBB indicates the boardtype. AAAA indicates the corresponding board software package name. For example, in thenote ;LRRUFDD:LRFU,RRU3808,RRU3201/RRU3203, the board software package name ofRRU3201 is LRRUFDD.

l If multiple board software packages are downloaded, use the character "|" to separate the names. Forexample, ALL=1800|LRRUFDD..

Step 2 Enter the LMT complete package downloading information in WEBLMT.

NOTEThe value of WEBLMT can only be YES or NO (case-insensitive). If the value is YES, the LMPT supportsthe download of the LMT complete package by using a USB flash drive. If the value isNO, the LMPT doesnot support the download of the LMT complete package by using a USB flash drive.

----End

4.5 Applying Integrity and Encryption Protection to Files inthe USB Flash Drive

To prevent information leak or unauthorized modification, integrity protection or encryptionprotection is required for the files in the Universal Serial Bus (USB) flash drive.

Prerequisitesl Files requiring encryption and integrity protection are ready in the USB flash drive.l The USB security protection tool is ready. The tool is available in M2000 installation folder

\client\USBProtector on the computer where the M2000 client is installed.

Context

The USB security protection tool is used to apply integrity or encryption protection to selectedfiles or files in the specified folder. The integrity protection protects files against unauthorizedmodification based on the message authentication code (MAC) value of files. Encryptionprotects critical information in files using the cipher key. The instructions on integrity protectionand encryption are as follows:



195

l Do not perform integrity protection on the BootROM software package, eNodeB softwarepackage, cold patch software package, or hot patch software package. Otherwise, theeNodeB fails to be deployed or upgraded using the USB flash drive.

l eNodeBs of version V100R005C00SPC230 or a later version support USB encryption.When performing USB encryption, adhere to the following rules:– Do not perform encryption on BootROM software, version software, cold patches, hot

patches, or preconfiguration file Precfg.ini, no matter whether the target version of aneNodeB supports USB encryption. Otherwise, the eNodeB cannot be successfullydeployed or upgraded using the USB flash drive.

– If the target version of an eNodeB does not support USB encryption, do not performencryption on the files in the USB flash drive. Otherwise, the eNodeB cannot besuccessfully deployed or upgraded using the USB flash drive.

– If the target version of an eNodeB supports USB encryption, perform encryption on theconfiguration file CFGDATA.XML in the USB flash drive. Other files are encryptedbased on site requirements.

After integrity or encryption protection is applied, the file USBConf.xml is generated in theUSB flash drive. The file name is unchangeable. Based on the generated file, the eNodeB checksthe file integrity or decrypts the files in the USB flash drive.

ProcedureStep 1 Copy files from USB flash drives to the PC where the USB security protection tool is installed.

Option Description

Applying integrity andencryption protection tofiles in a single USB flashdrive

Copy files from the USB flash drive to the PC in the samedirectory structure.

Applying integrity andencryption protection tofiles in multiple USBflash drives

1. Copy files from each USB flash drive to the PC in the samedirectory structure. Then mark each folder where files arestored for identification. For example, name the folders forstoring files in the first and second USB flash drives USB1 andUSB2. The rest can be done in the same manner.

2. Store all the marked folders under the same directory on thePC.

TIP

The USB security protection tool directly applies integrity and encryption protection to source files but itdoes not support decryption of files. To ensure the usability of source files, back up these files beforeapplying encryption and integrity protection to them.

Example: Assume that you copy files from USB flash drives to the directory E:\USBencrypt onthe PC.l Copy files from a single USB flash drive to the PC.

Directory Structure on the USB FlashDrive

Directory Structure on the PC for FilesCopied from the USB Flash Drive

usb:\A E:\USBencrypt\A



196

NOTE

A, B, and C specify the folder names on the USB flash drive and they can be BTS3900 GSM, NodeB, oreNodeB.

l Copy files from multiple USB flash drives to the PC (for example, USB1, USB2, and USB3).

Directory Structure on the USB FlashDrive

Directory Structure on the PC for FilesCopied from the USB Flash Drive

USB1: usb:\A E:\USBencrypt\USB1\A

USB2: usb:\B E:\USBencrypt\USB2\B

USB3: usb:\C E:\USBencrypt\USB3\C

Step 2 In the directory M2000 installation directory\client\client\USBProtector, double-clickUSBProtector.exe to start the USB security protection tool.

Figure 4-10 USB security protection tool dialog box

Step 3 Continue depending on the scenario:



197

Option Description

Applying integrity andencryption protection tofiles in a single USB flashdrive

Go to steps Step 4 through Step 9.

Applying integrity andencryption protection tofiles in multiple USBflash drives

Go to steps Step 10 through Step 12.

Step 4 In the menu bar, choose One USB Setting > Set Security Policies. The Set Security Policiesdialog box is displayed, as shown in the following figure.

Figure 4-11 Set Security Policies dialog box

1. In the Save Path area, click to set a save path for the USBConf.xml file and thenclick OK.Note that if no save path is specified, the USBConf.xml file is saved in the directory M2000installation directory\client\client\USBProtector by default after protection operationsare complete.

2. In the Protection Algorithm area, select algorithms to meet your individual need from theEncryption Algorithm and Integrity Algorithm drop-down lists.

Encryption Algorithm can be DES3_CBC, AES192_CBC, or AES256_CBC. IntegrityAlgorithm can be HMAC_SHA1 or HMAC_SHA256. You can choose any encryptionand integrity algorithms but the default ones are recommended.



198

3. Click OK.

Step 5 In the menu bar, choose One USB Setting > Set USB Root Path to set a root path for the USBflash drive. Then, click OK.For example, if you copy files in the directory usb:\A from the USB flash drive to the directoryE:\USBencrypt\A on the PC for integrity and encryption protection, E:\USBencrypt\A isconsidered as the corresponding USB root path on the PC.

Step 6 Click Add Files to select files to be protected in the USB root path. By default, the system appliesonly integrity protection to the added files. If you need to apply encryption protection to thesefiles, select the IsEncrypted:Index check box.

Step 7 Click Execute Protect.l The system applies encryption protection to files based on the specified protection algorithm

and applies integrity protection to all files in the current file list area based on the specifiedintegrity algorithm.

l Sizes of files remain the same before and after being encrypted because the system uses asymmetrical encryption algorithm.

Step 8 Click OK when a dialog box is displayed indicating that the integrity and encryption protectionis complete.After the integrity and encryption protection is complete, integrity protection codes ofcorresponding files are displayed in the MAC list and the USBConf.xml file generated by theUSB security protection tool are saved in the path specified in Step 4.1.

Step 9 Copy files from the PC to the USB flash drive.1. Delete source files from the USB flash drive and then copy files that have been protected

by using the USB security protection tool to the USB flash drive in the same directorystructure.

2. Copy the USBConf.xml file to one of the following fixed directories on the USB flashdrivel GBTS: usb:\BTS3900 GSM\USBConf.xmll NodeB: usb:\NodeB\USBConf.xmll eNodeB: usb:\eNodeB\USBConf.xml

CAUTIONThe USBConf.xml file must be copied to a correct path. Otherwise, the base station cannotdownload files from the USB flash drive.

Step 10 In the menu bar, choose Multi USB Setting > Set Root Directory and Security Policies. TheMulti USB Protection Settings dialog box is displayed, as shown in the following figure.



199

Figure 4-12 Multi USB Protection Settings dialog box

1. In the Root Path area, click to set a root path for USB flash drives. Then, clickOK.For example, if you copy files from the USB flash drives to the directory E:\USBencrypt on the PC for integrity and encryption protection, E:\USBencrypt isconsidered as the corresponding USB root path on the PC.

2. In the Protection Algorithm area, select algorithms to meet your individual need from theEncryption Algorithm and Integrity Algorithm drop-down lists.

Encryption Algorithm can be DES3_CBC, AES192_CBC, or AES256_CBC. IntegrityAlgorithm can be HMAC_SHA1 or HMAC_SHA256. You can choose any encryptionand integrity algorithms but the default ones are recommended.

3. Click the IsEncrypted:Index check box: In the file list area, if IsEncrypted:Index isclicked for a file, the system applies encryption protection to this file. Otherwise, the systemapplies only integrity protection to the file.

The file list area only lists files that must be encrypted. If you need to encrypt other files,go to Step 11 after the USB security protection tool finishes the integrity and encryptionprotection.

4. Click Execute Protect.5. Click OK when a dialog box is displayed indicating that the integrity and encryption

protection is complete.



200

CAUTIONDo not delete or move the USBConf.xml file which has been automatically saved to a fixedpath. Otherwise, the base station cannot download files from the USB flash drives.The following table assumes that you apply integrity and encryption protection to threeUSB flash drives.

If the save path on the PC for filescopied from the three USB flashdrives is...

Then the correspondingUSBConf.xml file is saved in thepath...

USB1: E:\USBencrypt\USB1\A E:\USBencrypt\USB1\A\USBConf.xml

USB2: E:\USBencrypt\USB2\B E:\USBencrypt\USB2\B\USBConf.xml

USB3: E:\USBencrypt\USB3\C E:\USBencrypt\USB3\C\USBConf.xml

Step 11 Optional: Apply encryption protection to files not listed in the File List Area.1. In the menu bar, choose One USB Setting > Set USB Root Path to set a root path for the

USB flash drives. Then, click OK.

For example, if you save the files for encryption protection in the directory E:\USBencrypt\USB1\A, E:\USBencrypt\USB1\A is considered as the corresponding USB root path onthe PC.

NOTE

You can apply encryption protection to files in a single directory at a time, not in multiple directories.

2. In the menu bar, choose One USB Setting > Load Existing Configure and load theUSBConf.xml file stored in the USB root path.

3. Click Add Files, select files to be protected in the USB root path, and select theIsEncrypted:Index check box for this file.

4. Click Execute Protect.5. Click OK when a dialog box is displayed indicating that the integrity and encryption

protection is complete.

Step 12 Delete source files from the USB flash drives and then copy files that have been protected byusing the USB security protection tool to the USB flash drives in the same directory structure.

----End

4.6 Binding Modes Between the M2000 and the eNodeBIn eNodeB automatic discovery during PnP remote commissioning, the eNodeB periodicallysends dynamic host configuration protocol (DHCP) requests to the DHCP server of M2000before the operation and maintenance channel (OMCH) is set up. After receiving the DHCPrequests, the DHCP server matches the electronic serial number (ESN), deployment ID, andinformation about the latitude and longitude of the eNodeB in the request message with that inthe eNodeB deployment list. In this way, the eNodeB is bound to the M2000. This sectiondescribes modes and process for binding an eNodeB to the M2000.



201

The DHCP server binds an eNodeB to the M2000 using the ESN, deployment ID or globalpositioning system (GPS) information. The priorities of these methods are arranged in adescending order. Figure 4-13 shows the binding process.

Figure 4-13 Binding the M2000 and the eNodeB

Binding Modesl ESN

Each eNodeB has a unique ESN, which is contained in the DHCP request sent to the DHCPserver. After receiving the DHCP request from the eNodeB, the DHCP server matches theESN with that in the eNodeB deployment list. If the eNodeB deployment list does not recordthe ESN or the matching fails, the DHCP server only records the ESN, but does not bindan eNodeB to the M2000. If the matching is successful, the DHCP server binds the eNodeBto the M2000 and returns an acknowledgement to the eNodeB. After the eNodeB receivesthe DHCP acknowledgement, the OMCH between the M2000 and the eNodeB is set up.

l Deployment IDIf the eNodeB bar code is scanned within 3 minutes after the eNodeB is powered on duringeNodeB deployment, the eNodeB contains the eNodeB bar code, known as the deploymentID, in a DHCP request sent to the DHCP server. If the DHCP server fails to bind the M2000and the eNodeB using the ESN after receiving the DHCP request, the DHCP server matchesthe deployment ID in the request with that in the eNodeB deployment list. If the eNodeBdeployment list does not record the deployment ID or the matching fails, the DHCP serverbinds the M2000 and the eNodeB using the GPS information. If the matching is successful,the DHCP server first obtains the ESN from the request message and fills the ESN in theeNodeB deployment list matching the deployment ID. After receiving another DHCPrequest from the eNodeB, the DHCP server binds the M2000 and the eNodeB using theESN.



202

l GPSIn eNodeB deployment, if the eNodeB connects to and locks the GPS, the eNodeB sendsa DHCP request containing the latitude and longitude of the eNodeB to the DHCP server.If the DHCP server cannot use the ESN or Deployment ID for binding, it uses the receivedinformation about the latitude and longitude of the eNodeB for matching. If the eNodeBdeployment list does not record this information or the matching fails, the DHCP serverdiscards the DHCP request. If the distance between the eNodeB calculated based on thelatitude and longitude of the eNodeB in the DHCP request and that calculated based on theinformation in the eNodeB deployment list is less than 100 meters, the matching issuccessful. Then the DHCP server first obtains the ESN from the request message and fillsthe ESN in the eNodeB deployment list matching the information about the latitude andlongitude of the eNodeB. After receiving another DHCP request from the eNodeB, theDHCP server binds the M2000 and the eNodeB using the ESN.You must manually configure the GPS on the eNodeB to use the GPS information for thebinding. To configure the GPS, perform the following steps:

1. Connect the GPS antenna to the main control board or USCU board of the eNodeB.2. Log in to the eNodeB on the local maintenance terminal (LMT).3. Run the ADD GPS command to add the GPS.4. Run the DSP GPS command to query the value of GPS Satellites Traced.

NOTEWhen the value of GPS Satellites Traced is greater than 3, the latitude and longitude of theeNodeB can be obtained and contained in DHCP requests.

4.7 Data Sheet for eNodeB CommissioningThis section provides the data sheet that is used to record the process and results of the eNodeBcommissioning. The Data Sheet for Commissioning used at different sites may be different. Thistable serves as a reference only.

Table 4-6 Data sheet for eNodeB commissioning

eNodeBname

eNodeBID

eNodeBType

ESN

CommissioningTime

CommissioningEngineer



203

CommissioningResult

□ Successful; □ Failed

Commissioning Item Conclusion

Handling Exceptions

CommissioningPrerequisites

Faults in eNodeB hardwareinstallation are rectified.

□ Yes;□ No

Negotiation data of theeNodeB to be commissioned isadded to the MME/S-GW.

□ Yes;□ No

PnPRemoteCommissioning

PreparationPhase

The informationregarding the eNodeB,such as name, ID, andESN, is reported.

□ Yes;□ No

The eNodeB ispowered on.

□ Yes;□ No

The eNodeB softwareand related filesrequired for automaticdeployment are ready.

□ Yes;□ No

The digital certificateis ready.

□ Yes;□ No

The securityequipment is ready.

□ Yes;□ No

The USB storagedevice is ready.

□ Yes;□ No

Remoteendof theeNodeB

The ESN is bound. □ Yes;□ No

The automaticeNodeBcommissioning task iscomplete.

□ Yes;□ No

The eNodeBcommissioning reportis obtained.

□ Yes;□ No

The running status ofthe eNodeB is normal.

□ Yes;□ No

The test result of theexternal environmentalarm is correct.

□ Yes;□ No



204

The test result of thebasic services iscorrect.

□ Yes;□ No

LocalCommissioningUsing aUSBFlashDrive

PreparationPhase


□ Yes;□ No


□ Yes;□ No


□ Yes;□ No

The USB storagedevice is ready.

□ Yes;□ No

Localendof theeNodeB

The software and dataconfiguration file areloaded through theUSB storage device.

□ Yes;□ No

The eNodeB is reset. □ Yes;□ No

The indicator status isnormal.

□ Yes;□ No



The automaticeNodeBcommissioning task iscomplete.

□ Yes;□ No

The eNodeBcommissioning reportis obtained.

□ Yes;□ No


□ Yes;□ No


□ Yes;□ No


□ Yes;□ No

LocalCommissioning onthe LMT

PreparationPhase


□ Yes;□ No



205


□ Yes;□ No


□ Yes;□ No

The digital certificateis downloadedsuccessfully.

□ Yes;□ No

Localendof theeNodeB

The software and dataconfiguration file areloaded through theLMT.

□ Yes;□ No

The software isupgraded to the targetversion.

□ Yes;□ No

All the active alarmsare cleared.

□ Yes;□ No


□ Yes;□ No


□ Yes;□ No


□ Yes;□ No



The OM channel isestablished.

□ Yes;□ No

Problem Description Impact

UnsolvedProblemsAfterCommissioning

Component P/N

FaultyBoardRecord



206

5 FAQ

About This Chapter

This chapter describes some common problems and solutions during commissioning.

5.1 Failing to Identify the USB Flash DriveFor eNodeB commissioning in hybrid mode using a Universal Serial Bus (USB) flash drivelocally and the M2000 remotely, eNodeB fails to identify the USB flash drive if the USBindicator is off after the eNodeB is powered on and the USB flash drive is inserted.

5.2 Failing to Read Files in the USB Flash DriveAfter the eNodeB is powered on for about 5 minutes, observe the RUN indicator on the maincontrol board of the eNodeB and the indicator on the USB flash drive. If the RUN indicator isnot blinking on for 0.125s and off for 0.125s and the indicator on the USB flash drive is steadyoff, the eNodeB fails to read files in the USB flash drive.

5.3 Failing to Activate the SoftwareAfter the eNodeB deployment is complete, log in to the eNodeB on the Web local maintenanceterminal (LMT). Then run the MML command LST SOFTWARE to check the eNodeB versioninformation. If the backup software version is the target version, the eNodeB succeeds indownloading the software but fails to activate the software.

5.4 Failing to Download the Software Based on the Preconfiguration FileAfter the eNodeB is deployed using a USB flash drive, the eNodeB does not download the boardsoftware based on the board information configured in the preconfiguration file. For example,based on the preconfiguration file, the Web LMT complete package should have beendownloaded. However, if you find a minimum LMT package was downloaded after logging into the eNodeB on the Web LMT, the eNodeB failed to download the software based on thepreconfiguration file.

eNodeBCommissioning Guide 5 FAQ


207

5.1 Failing to Identify the USB Flash DriveFor eNodeB commissioning in hybrid mode using a Universal Serial Bus (USB) flash drivelocally and the M2000 remotely, eNodeB fails to identify the USB flash drive if the USBindicator is off after the eNodeB is powered on and the USB flash drive is inserted.

Procedure

Step 1 Check whether the eNodeB is working properly by observing the eNodeB indicator. For details,see 4.3 Checking the Status of Indicators.

Step 2 Ensure that the USB flash drive is correctly inserted into the USB port on the LTE mainprocessing and transmission unit (LMPT). If an LMPT is used, the USB port is shown in Figure5-1. If a UMPT is used, the USB port is shown in Figure 5-2.

Figure 5-1 USB port on the LMPT



208

Figure 5-2 USB port on the UMPT

Step 3 Remove the USB flash drive, and power off the eNodeB.

Step 4 Wait for about 1 minute, power on the eNodeB, and then insert the USB flash drive again intothe USB port on the main control board of the eNodeB.

----End

5.2 Failing to Read Files in the USB Flash DriveAfter the eNodeB is powered on for about 5 minutes, observe the RUN indicator on the maincontrol board of the eNodeB and the indicator on the USB flash drive. If the RUN indicator isnot blinking on for 0.125s and off for 0.125s and the indicator on the USB flash drive is steadyoff, the eNodeB fails to read files in the USB flash drive.

ProcedureStep 1 Ensure that the USB flash drive meets requirements in Table 5-1.

Table 5-1 Tools required for the local commissioning using the USB flash drive

Tool Description

USB flash drive l The USB flash drive is equipped with an indicator that indicatesthe data transmission status.

l Capacity ≥ 256 MBl Model: The USB flash drive must be provided by Huawei.l The USB flash drive must not provide any additional functions,

such as encryption, virus scanning, and bootstrapping. Inaddition, it cannot be an MP3 player, MP4 player, or smartphone.

l The USB flash drive used for commissioning cannot be used forother purposes. In addition, irrelevant files, especially those withChinese file names, cannot be saved in the USB flash drive.



209

Step 2 Ensure that the version software package and data configuration files are named correctly andsaved in correct paths.

Step 3 Remove the USB flash drive, and power off the eNodeB.

Step 4 Wait for about 1 minute, power on the eNodeB, and then insert the USB flash drive again intothe USB port on the main control board of the eNodeB.

----End

5.3 Failing to Activate the SoftwareAfter the eNodeB deployment is complete, log in to the eNodeB on the Web local maintenanceterminal (LMT). Then run the MML command LST SOFTWARE to check the eNodeB versioninformation. If the backup software version is the target version, the eNodeB succeeds indownloading the software but fails to activate the software.

Procedure

Step 1 Local commissioning using a USB flash drive1. Ensure that the version software package and data configuration files are named correctly

and saved in correct paths.2. Remove the USB flash drive, and power off the eNodeB.3. Wait for about 1 minute, power on the eNodeB, and then insert the USB flash drive again

into the USB port on the main control board of the eNodeB.4. Deploy the eNodeB again.

Step 2 PnP remote commissioningEnsure that the version in the eNodeB deployment list is consistent with the target version. If itis inconsistent with the target version, change the eNodeB deployment list according to the targetversion and then deploy the eNodeB again.

----End

5.4 Failing to Download the Software Based on thePreconfiguration File

After the eNodeB is deployed using a USB flash drive, the eNodeB does not download the boardsoftware based on the board information configured in the preconfiguration file. For example,based on the preconfiguration file, the Web LMT complete package should have beendownloaded. However, if you find a minimum LMT package was downloaded after logging into the eNodeB on the Web LMT, the eNodeB failed to download the software based on thepreconfiguration file.

Procedure

Step 1 Check the information in and saving path of the preconfiguration file. If they are incorrect,modify the preconfiguration file.



210

Step 2 Check whether the preconfiguration file is integrity protected. If it is not integrity protected, see4.5 Applying Integrity and Encryption Protection to Files in the USB Flash Drive.

Step 3 Delete the board information not to be downloaded from the preconfiguration file.

Step 4 Check the software version in the USB flash drive and ensure the target version is not the sameas the active version.

NOTEIf the target version is the same as the active version, the eNodeB does not read the preconfiguration filein the USB flash drive, which leads to the failure of downloading.

----End



211

enodeb commissioning guide(v100r005c00_07)(pdf)-en

Documents