SlideShare uma empresa Scribd logo
1 de 464
Baixar para ler offline
eNodeB
V100R005C00
Commissioning Guide
Issue 04
Date 2012-06-29
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 written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
i
About This Document
Purpose
This document describes how to commission an eNodeB after the eNodeB is successfully
installed and configured to verify that the eNodeB works properly as designed. The eNodeB
supports three commissioning modes: M2000-based remote commissioning, USB-based local
commissioning+M2000-based remote commissioning, and LMT-based local commissioning.
Product Versions
The 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 Audience
This document is intended for:
l eNodeB installation engineers
l Field engineers
eNodeB
Commissioning Guide About This Document
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ii
Organization
1 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, local
commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the
LMT. Each commissioning mode can be applied to the scenario where the SeGW is deployed
and the scenario where no SeGW is deployed. In the security scenario, PnP remote
commissioning is classified into PnP remote commissioning in unified encryption mode and
PnP remote commissioning in differentiated encryption mode; local commissioning using a USB
flash drive is classified into local commissioning using a USB flash drive in unified encryption
mode and local commissioning using a USB flash drive in differentiated encryption mode. You
can select a commissioning mode based on site conditions. PnP remote commissioning is
recommended.
3 eNodeB Commissioning Procedures (Without the SeGW)
This chapter describes the following procedures when no security gateway (SeGW) is deployed:
eNodeB automatic discovery, plug and play (PnP) remote commissioning, local commissioning
using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT.
4 eNodeB Commissioning Procedures (with the SeGW)
This chapter describes the following procedures when the SeGW is deployed in the network:
eNodeB automatic discovery, PnP remote commissioning in unified encryption mode, PnP
remote commissioning in differentiated encryption mode, local commissioning using a USB
flash drive in unified encryption mode, local commissioning using a USB flash drive in
differentiated encryption mode, and local commissioning on the LMT.
5 Appendix
This chapter describes how to encrypt files in a Universal Serial Bus (USB) storage device and
provides the eNodeB commissioning data sheet.
6 FAQ
This chapter describes some common problems and solutions during commissioning.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
eNodeB
Commissioning Guide About This Document
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iii
Symbol Description
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.
eNodeB
Commissioning Guide About This Document
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iv
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
eNodeB
Commissioning Guide About This Document
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
v
Contents
About This Document.....................................................................................................................ii
1 Changes in eNodeB Commissioning Guide............................................................................1
2 Commissioning Mode..................................................................................................................6
3 eNodeB Commissioning Procedures (Without the SeGW)...................................................9
3.1 Overview of eNodeB Automatic Discovery (Without the SeGW)..................................................................10
3.2 PnP Remote Commissioning (Without the SeGW)..........................................................................................12
3.2.1 Commissioning Procedure.......................................................................................................................12
3.2.2 Preparations.............................................................................................................................................15
3.2.3 Creating an eNodeB Commissioning Task.............................................................................................29
3.2.4 Starting an eNodeB Commissioning Task...............................................................................................31
3.2.5 Monitoring eNodeB Commissioning.......................................................................................................34
3.2.6 Confirming eNodeB Commissioning Completion..................................................................................38
3.2.7 Checking the Running Status of the eNodeB on the M2000...................................................................39
3.2.8 Commissioning the Antenna System on the M2000...............................................................................42
3.2.9 Commissioning the Environment Monitoring Equipment on the M2000...............................................47
3.2.10 Setting the Maximum Output Power for RRUs or RFUs......................................................................50
3.2.11 Testing the Basic Services of the eNodeB.............................................................................................51
3.2.12 Setting an NE to the NORMAL Mode..................................................................................................52
3.2.13 References to eNodeB Commissioning.................................................................................................53
3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW)...........................................................62
3.3.1 Commissioning Procedure.......................................................................................................................62
3.3.2 Preparations.............................................................................................................................................65
3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash
Drive.................................................................................................................................................................68
3.3.4 Uploading Data Files...............................................................................................................................72
3.3.5 Creating an eNodeB Commissioning Task.............................................................................................82
3.3.6 Starting an eNodeB Commissioning Task...............................................................................................84
3.3.7 Monitoring eNodeB Commissioning.......................................................................................................87
3.3.8 Confirming eNodeB Commissioning Completion..................................................................................91
3.3.9 Checking the Running Status of the eNodeB on the M2000...................................................................92
3.3.10 Commissioning the Antenna System on the M2000.............................................................................95
3.3.11 Commissioning the Environment Monitoring Equipment on the M2000...........................................100
eNodeB
Commissioning Guide Contents
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
vi
3.3.12 Setting the Maximum Output Power for RRUs or RFUs....................................................................103
3.3.13 Testing the Basic Services of the eNodeB...........................................................................................104
3.3.14 Setting an NE to the NORMAL Mode................................................................................................105
3.3.15 References to eNodeB Commissioning...............................................................................................106
3.4 Local Commissioning on the LMT(Without the SeGW)...............................................................................115
3.4.1 Commissioning Procedure.....................................................................................................................115
3.4.2 Preparations...........................................................................................................................................118
3.4.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........121
3.4.4 Downloading the License for eNodeB Commissioning on the LMT....................................................124
3.4.5 Commissioning the Antenna System on the LMT................................................................................124
3.4.6 Commissioning the Environment Monitoring Equipment on the LMT................................................130
3.4.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................132
3.4.8 Handling the eNodeB Alarms on the LMT...........................................................................................133
3.4.9 Checking the Operating Status of the eNodeB on the LMT..................................................................133
3.4.10 Testing the Basic Services of the eNodeB...........................................................................................134
3.4.11 Establishing an OML Between the M2000 and the eNodeB...............................................................135
3.4.12 Setting an NE to the NORMAL Mode................................................................................................138
4 eNodeB Commissioning Procedures (with the SeGW).....................................................139
4.1 Overview of eNodeB Automatic Discovery (with the SeGW)......................................................................142
4.2 PnP Remote Commissioning in Unified Encryption Mode (with the SeGW)...............................................150
4.2.1 Commissioning Procedure.....................................................................................................................150
4.2.2 Preparations...........................................................................................................................................153
4.2.3 Creating an eNodeB Commissioning Task...........................................................................................175
4.2.4 Starting an eNodeB Commissioning Task.............................................................................................177
4.2.5 Monitoring eNodeB Commissioning.....................................................................................................180
4.2.6 Confirming eNodeB Commissioning Completion................................................................................184
4.2.7 Checking the Running Status of the eNodeB on the M2000.................................................................185
4.2.8 Commissioning the Antenna System on the M2000.............................................................................189
4.2.9 Commissioning the Environment Monitoring Equipment on the M2000.............................................193
4.2.10 Setting the Maximum Output Power for RRUs or RFUs....................................................................196
4.2.11 Testing the Basic Services of the eNodeB...........................................................................................197
4.2.12 Setting an NE to the NORMAL Mode................................................................................................198
4.2.13 References to eNodeB Commissioning...............................................................................................199
4.3 PnP Remote Commissioning in Differentiated Encryption Mode (with the SeGW).....................................208
4.3.1 Commissioning Procedure.....................................................................................................................208
4.3.2 Preparations...........................................................................................................................................211
4.3.3 Creating an eNodeB Commissioning Task...........................................................................................229
4.3.4 Starting an eNodeB Commissioning Task.............................................................................................232
4.3.5 Monitoring eNodeB Commissioning.....................................................................................................235
4.3.6 Obtaining an Operator's Device Certificate Manually (with PKI)........................................................239
4.3.7 Confirming eNodeB Commissioning Completion................................................................................243
4.3.8 Checking the Running Status of the eNodeB on the M2000.................................................................244
eNodeB
Commissioning Guide Contents
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
vii
4.3.9 Commissioning the Antenna System on the M2000.............................................................................248
4.3.10 Commissioning the Environment Monitoring Equipment on the M2000...........................................252
4.3.11 Setting the Maximum Output Power for RRUs or RFUs....................................................................255
4.3.12 Testing the Basic Services of the eNodeB...........................................................................................256
4.3.13 Setting an NE to the NORMAL Mode................................................................................................257
4.3.14 References to eNodeB Commissioning...............................................................................................258
4.4 Local Commissioning Using a USB Flash Drive in Unified Encryption Mode (with the SeGW)................267
4.4.1 Commissioning Procedure.....................................................................................................................267
4.4.2 Preparations...........................................................................................................................................270
4.4.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash
Drive...............................................................................................................................................................281
4.4.4 Uploading Data Files.............................................................................................................................285
4.4.5 Creating an eNodeB Commissioning Task...........................................................................................295
4.4.6 Starting an eNodeB Commissioning Task.............................................................................................297
4.4.7 Monitoring eNodeB Commissioning.....................................................................................................300
4.4.8 Confirming eNodeB Commissioning Completion................................................................................304
4.4.9 Checking the Running Status of the eNodeB on the M2000.................................................................305
4.4.10 Commissioning the Antenna System on the M2000...........................................................................308
4.4.11 Commissioning the Environment Monitoring Equipment on the M2000...........................................313
4.4.12 Setting the Maximum Output Power for RRUs or RFUs....................................................................316
4.4.13 Testing the Basic Services of the eNodeB...........................................................................................317
4.4.14 Setting an NE to the NORMAL Mode................................................................................................318
4.4.15 References to eNodeB Commissioning...............................................................................................319
4.5 Local Commissioning Using a USB Flash Drive in Differentiated Encryption Mode (with the SeGW)
..............................................................................................................................................................................328
4.5.1 Commissioning Procedure.....................................................................................................................328
4.5.2 Preparations...........................................................................................................................................331
4.5.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash
Drive...............................................................................................................................................................337
4.5.4 Uploading Data Files.............................................................................................................................341
4.5.5 Creating an eNodeB Commissioning Task...........................................................................................351
4.5.6 Starting an eNodeB Commissioning Task.............................................................................................353
4.5.7 Monitoring eNodeB Commissioning.....................................................................................................356
4.5.8 Obtaining an Operator's Device Certificate Manually (with PKI)........................................................360
4.5.9 Confirming eNodeB Commissioning Completion................................................................................365
4.5.10 Checking the Running Status of the eNodeB on the M2000...............................................................365
4.5.11 Commissioning the Antenna System on the M2000...........................................................................369
4.5.12 Commissioning the Environment Monitoring Equipment on the M2000...........................................373
4.5.13 Setting the Maximum Output Power for RRUs or RFUs....................................................................377
4.5.14 Testing the Basic Services of the eNodeB...........................................................................................378
4.5.15 Setting an NE to the NORMAL Mode................................................................................................379
4.5.16 References to eNodeB Commissioning...............................................................................................379
4.6 Local Commissioning on the LMT(with the SeGW).....................................................................................388
eNodeB
Commissioning Guide Contents
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
viii
4.6.1 Commissioning Procedure.....................................................................................................................388
4.6.2 Preparations...........................................................................................................................................391
4.6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........398
4.6.4 Downloading the License for eNodeB Commissioning on the LMT....................................................401
4.6.5 Commissioning the Antenna System on the LMT................................................................................402
4.6.6 Commissioning the Environment Monitoring Equipment on the LMT................................................408
4.6.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................410
4.6.8 Handling the eNodeB Alarms on the LMT...........................................................................................411
4.6.9 Checking the Operating Status of the eNodeB on the LMT..................................................................411
4.6.10 Testing the Basic Services of the eNodeB...........................................................................................412
4.6.11 Establishing an OML Between the M2000 and the eNodeB...............................................................413
4.6.12 Setting an NE to the NORMAL Mode................................................................................................415
5 Appendix.....................................................................................................................................417
5.1 eNodeB Binding Using a Bar Code Scanner..................................................................................................418
5.1.1 Printing a Bar Code on the M2000........................................................................................................418
5.1.2 Setting a Bar Code Scanner...................................................................................................................421
5.1.3 Binding the eNodeB by Scanning a Bar Code......................................................................................423
5.2 Triggering Monitoring Device Alarms...........................................................................................................424
5.2.1 Triggering PMU Alarms........................................................................................................................424
5.2.2 Triggering FMU Alarms........................................................................................................................430
5.2.3 Triggering TCU Alarms........................................................................................................................432
5.2.4 Triggering EMU Alarms.......................................................................................................................434
5.3 Checking the Status of Indicators...................................................................................................................436
5.4 Configuring the Default Configuration File...................................................................................................442
5.5 Encrypting Files in the USB Flash Drive.......................................................................................................442
5.6 Data Sheet for eNodeB Commissioning.........................................................................................................445
6 FAQ.............................................................................................................................................. 450
6.1 Failing to Identify the USB Flash Drive.........................................................................................................451
6.2 Failing to Read Files in the USB Flash Drive................................................................................................452
6.3 Failing to Activate the Software.....................................................................................................................453
6.4 Failing to Download the Software Based on the Default Configuration File.................................................453
eNodeB
Commissioning Guide Contents
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ix
1Changes in eNodeB Commissioning Guide
This chapter describes the changes in eNodeB Commissioning Guide.
04 (2012-06-29)
This is the fourth official release.
Compared with issue 03 (2012-05-11) of V100R005C00, this issue includes the following new
information.
Topic Change Description
4.3.6 Obtaining an Operator's Device
Certificate Manually (with PKI)
Added the procedure for manually obtaining
operators' certificates.
Compared with issue 03 (2012-05-11) of V100R005C00, this issue includes the following
changes.
Topic Change Description
l 3 eNodeB Commissioning Procedures
(Without the SeGW)
l 4 eNodeB Commissioning Procedures
(with the SeGW)
Modified the document organization by
separating the commissioning procedures for
scenarios with the SeGW and without the
SeGW, and separating the commissioning
procedures in unified encryption mode and in
differentiated encryption for the scenario
with 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.
eNodeB
Commissioning Guide 1 Changes in eNodeB Commissioning Guide
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
1
Compared with issue 02 (2012-04-28) of V100R005C00, this issue includes the following new
information.
Topic Change Description
l 5.4 Configuring the Default
Configuration File
l 6.4 Failing to Download the Software
Based on the Default Configuration
File
Added sections on obtaining the common
configuration file, configuring the default
configuration file and failing to download the
software based on the default configuration
file.
Compared with issue 02 (2012-04-28) of V100R005C00, this issue does not include any changes
or delete any information.
02 (2012-04-28)
This is the second official release.
Compared with issue 01 (2012-03-30) of V100R005C00, this issue does not include any new
information.
Compared with issue 01 (2012-03-30) of V100R005C00, this issue includes the following
changes.
Topic Change Description
l 4.1 Overview of eNodeB Automatic
Discovery (with the SeGW)
l 3.3.3 Downloading and Activating the
Software, Data Configuration File, and
License File Using a USB Flash Drive
l 5.3 Checking the Status of Indicators
l Preparing a USB Flash Drive for Local
Commissioning
l 5.5 Encrypting Files in the USB Flash
Drive
l Preparing a USB Flash Drive for Local
Commissioning
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 new
information.
eNodeB
Commissioning Guide 1 Changes in eNodeB Commissioning Guide
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
2
Topic Change Description
5.3 Checking the Status of Indicators Added the descriptions of ACT indicator on
the main control board.
l Preparing a USB Flash Drive for Local
Commissioning
l Preparing a USB Flash Drive for Local
Commissioning
Added the description of downloading the
board software by using default configuration
file.
3.3.3 Downloading and Activating the
Software, Data Configuration File, and
License File Using a USB Flash Drive
Added the figure of the USB port on UMPT
and the method of downloading the LMT
complete package by using a USB flash drive
when the LMPT is used.
Compared with draft B (2012-02-15) of V100R005C00, this issue does not include any changes.
The following information in draft B (2012-02-15) of V100R005C00 is deleted from this issue.
Topic Change Description
l 3.2 PnP Remote Commissioning
(Without the SeGW)
l 4.2 PnP Remote Commissioning in
Unified Encryption Mode (with the
SeGW)
l 3.3 Local Commissioning Using a USB
Flash Drive (Without the SeGW)
l 4.4 Local Commissioning Using a USB
Flash Drive in Unified Encryption
Mode (with the SeGW)
l 3.4 Local Commissioning on the LMT
(Without the SeGW)
l 4.6 Local Commissioning on the LMT
(with the SeGW)
Deleted the procedure for comparing the
license and configuration data in the
commissioning.
Draft B (2012-02-15)
This is draft B.
Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following new
information.
Topic Change Description
6 FAQ Added "FAQ."
eNodeB
Commissioning Guide 1 Changes in eNodeB Commissioning Guide
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
3
Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following
changes.
Topic Change Description
l 3.2 PnP Remote Commissioning
(Without the SeGW)
l 4.2 PnP Remote Commissioning in
Unified Encryption Mode (with the
SeGW)
l 3.3 Local Commissioning Using a USB
Flash Drive (Without the SeGW)
l 4.4 Local Commissioning Using a USB
Flash Drive in Unified Encryption
Mode (with the SeGW)
l 3.4 Local Commissioning on the LMT
(Without the SeGW)
l 4.6 Local Commissioning on the LMT
(with the SeGW)
Separated the description of remote
commissioning on the M2000, local
commissioning using a USB flash drive
+remote commissioning on the M2000, and
local commissioning on the LMT with the
SeGW and those without the SeGW.
3.2.12 Setting an NE to the NORMAL
Mode
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.
Compared with issue 02 (2011-11-15) of V100R004C00, this issue includes the following new
information.
eNodeB
Commissioning Guide 1 Changes in eNodeB Commissioning Guide
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
4
Topic Change Description
l 3.2 PnP Remote Commissioning
(Without the SeGW)
l 4.2 PnP Remote Commissioning in
Unified Encryption Mode (with the
SeGW)
l 3.3 Local Commissioning Using a USB
Flash Drive (Without the SeGW)
l 4.4 Local Commissioning Using a USB
Flash Drive in Unified Encryption
Mode (with the SeGW)
l 3.4 Local Commissioning on the LMT
(Without the SeGW)
l 4.6 Local Commissioning on the LMT
(with the SeGW)
Added the procedure for comparing the
license and configuration data in all
commissioning scenarios.
3.3.3 Downloading and Activating the
Software, Data Configuration File, and
License File Using a USB Flash Drive
Added the procedure for activating the
license file using the USB flash drive.
Preparing a USB Flash Drive for Local
Commissioning
3.2.12 Setting an NE to the NORMAL
Mode
Added the procedure for querying the
eNodeB state.
Compared with issue 02 (2011-11-15) of V100R004C00, this issue includes the following
change.
Topic Change Description
3.3.3 Downloading and Activating the
Software, Data Configuration File, and
License File Using a USB Flash Drive
Changed the description of downloading the
LMT complete package using the USB flash
drive.
The following information in issue 02 (2011-11-15) of V100R004C00 is deleted from this issue.
eNodeB
Commissioning Guide 1 Changes in eNodeB Commissioning Guide
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
5
2Commissioning Mode
The eNodeB supports the following commissioning modes: PnP remote commissioning, local
commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the
LMT. Each commissioning mode can be applied to the scenario where the SeGW is deployed
and the scenario where no SeGW is deployed. In the security scenario, PnP remote
commissioning is classified into PnP remote commissioning in unified encryption mode and
PnP remote commissioning in differentiated encryption mode; local commissioning using a USB
flash drive is classified into local commissioning using a USB flash drive in unified encryption
mode and local commissioning using a USB flash drive in differentiated encryption mode. You
can select a commissioning mode based on site conditions. PnP remote commissioning is
recommended.
Prerequisites
l 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 the
interconnection data required for commissioning and can provide the basic functions of the
EPC.
l Requirements for data configuration are described as follows:
Based on live network and eNodeB design requirements, the eNodeB configuration data
are configured using the configuration management express (CME) or man-machine
language (MML) command. For details, see eNodeB Initial Configuration Guide.
Application Scenario
Table 2-1 lists the application description for each commissioning scenario.
eNodeB
Commissioning Guide 2 Commissioning Mode
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
6
Table 2-1 Application description for commissioning scenarios
Commissioning
Mode
Application Scenario
PnP remote
commissioning
(without the SeGW)
l The operation and maintenance (OM) channel between the
eNodeB and the M2000 works properly.
l The eNodeB is relocated with permissible downtime greater than
or equal to 1 hour.
l No SeGW is deployed in the network.
Local commissioning
using a USB flash
drive (without the
SeGW)
l No OM channel is established between the eNodeB and the
M2000.
l A USB flash drive is available.
l The eNodeB is relocated with permissible downtime less than 1
hour.
l No SeGW is deployed in the network.
Local commissioning
on the LMT (without
the SeGW)
l No OM channel is established between the eNodeB and the
M2000.
l The USB flash drive is unavailable or damaged, or eNodeB
deployment using the USB flash drive fails.
l The eNodeB is relocated with permissible downtime less than 1
hour.
l No SeGW is deployed in the network.
PnP remote
commissioning in
unified encryption
mode (with the
SeGW)
l The operation and maintenance (OM) channel between the
eNodeB and the M2000 works properly.
l The eNodeB is relocated with permissible downtime greater than
or equal to 1 hour.
l The SeGW is deployed in the network. A public Dynamic Host
Configuration Protocol (DHCP) server is available and it
supports option43.
l The eNodeB and the M2000 belong to different domains. The
eNodeB communicates with the M2000 through the SeGW.
PnP remote
commissioning in
differentiated
encryption mode
(with the SeGW)
l The operation and maintenance (OM) channel between the
eNodeB and the M2000 works properly.
l The eNodeB is relocated with permissible downtime greater than
or equal to 1 hour.
l The SeGW is deployed in the network.
l The eNodeB and the M2000 belong to the same domain. The
eNodeB can communicate with the M2000 without the SeGW.
eNodeB
Commissioning Guide 2 Commissioning Mode
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
7
Commissioning
Mode
Application Scenario
Local commissioning
using a USB flash
drive in unified
encryption mode
(with the SeGW)
l No OM channel is established between the eNodeB and the
M2000.
l A USB flash drive is available.
l The eNodeB is relocated with permissible downtime less than 1
hour.
l The SeGW is deployed in the network. A public Dynamic Host
Configuration Protocol (DHCP) server is available and it
supports option43.
l The eNodeB and the M2000 belong to different domains. The
eNodeB communicates with the M2000 through the SeGW.
Local commissioning
using a USB flash
drive in
differentiated
encryption mode
(with the SeGW)
l No OM channel is established between the eNodeB and the
M2000.
l A USB flash drive is available.
l The eNodeB is relocated with permissible downtime less than 1
hour.
l The SeGW is deployed in the network.
l The eNodeB and the M2000 belong to the same domain. The
eNodeB can communicate with the M2000 without the SeGW.
Local commissioning
on the LMT (with the
SeGW)
l No OM channel is established between the eNodeB and the
M2000.
l The USB flash drive is unavailable or damaged, or eNodeB
deployment using the USB flash drive fails.
l The eNodeB is relocated with permissible downtime less than 1
hour.
l The SeGW is deployed in the network.
CAUTION
If 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 reference
documents before starting commissioning. For details about the required items, see the section
on preparations for the commissioning mode used.
eNodeB
Commissioning Guide 2 Commissioning Mode
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
8
3eNodeB Commissioning Procedures
(Without the SeGW)
About This Chapter
This chapter describes the following procedures when no security gateway (SeGW) is deployed:
eNodeB automatic discovery, plug and play (PnP) remote commissioning, local commissioning
using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT.
3.1 Overview of eNodeB Automatic Discovery (Without the SeGW)
During eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM)
channel with the M2000 using automatic discovery. This process does not require manual
intervention.
3.2 PnP Remote Commissioning (Without the SeGW)
To commission an eNodeB when no SeGW is deployed in the network, you need to enable the
plug and play (PnP) function of the eNodeB on the M2000 client. After the faults (if any) occurred
during automatic commissioning are rectified and the commissioning procedure is complete,
the eNodeB can work properly.
3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW)
To perform local eNodeB commissioning using a USB flash drive when no SeGW is deployed,
you need to upgrade the eNodeB 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 eNodeB commissioning 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 to
upgrade the eNodeB software, download the configuration files, commission the antenna line
devices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish the
operation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000
server.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9
3.1 Overview of eNodeB Automatic Discovery (Without the
SeGW)
During eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM)
channel with the M2000 using automatic discovery. This process does not require manual
intervention.
Introduction to the Automatic Discovery Process
Automatic discovery is a process during which the eNodeB is powered on and sets up an OM
channel with the M2000 after the hardware is installed.
If the eNodeB and the M2000 server are deployed on different network segments, you need to
configure the router closest to the eNodeB on the path between the eNodeB and the M2000
server as a Dynamic Host Configuration Protocol (DHCP) relay. The IP address of the DHCP
server for the M2000 is used as the DHCP relay address.
NOTE
If the M2000 server is deployed by using Server Load-Sharing (SLS), the previous IP address of the M2000
DHCP server refers to the IP address of the master M2000 server.
eNodeB Automatic Discovery Process
The 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 as
follows:
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 provided by the M2000 to obtain
the information, such as OM IP address, OM IP mask, IP address of the M2000, and IP
mask of the M2000.
4. The eNodeB sets up an OM channel with the M2000 after receiving a response to the DHCP
request from the M2000.
5. The eNodeB downloads and activates the eNodeB software and configuration files from
the M2000.
NOTE
l When the M2000 server is deployed by using SLS, if you want to create an eNodeB on the master
server, the IP address of the M2000 refers to the IP address of the master server; if if you want to create
an 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 User
Guide.
l Log in to the M2000 client, choose Configuration > DHCP Configuration Management. The
DHCP Configuration Management tab page is displayed. In the Server Information area on
the DHCP Configuration Management tab page, check the DHCP message.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
10
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 as
follows:
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 can
directly communicate with each other.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
11
Figure 3-3 Commissioning scenario with the SeGW
3.2 PnP Remote Commissioning (Without the SeGW)
To commission an eNodeB when no SeGW is deployed in the network, you need to enable the
plug and play (PnP) function of the eNodeB on the M2000 client. After the faults (if any) occurred
during automatic commissioning are rectified and the commissioning procedure is complete,
the eNodeB can work properly.
3.2.1 Commissioning Procedure
This section describes how to perform plug and play (PnP) remote eNodeB commissioning when
no security gateway (SeGW) is deployed.
Figure 3-4 shows the procedure for PnP remote eNodeB commissioning when no SeGW is
deployed.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
12
Figure 3-4 Procedure for PnP remote eNodeB commissioning when no SeGW is deployed
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
13
Table 3-1 Commissioning procedure
St
ep
Operation Mandat
ory/
Option
al
1 Local and
remote
cooperative
operations
Prepare for remote eNodeB commissioning using the PnP,
which involves obtaining eNodeB information and
commissioning tools, and obtaining the eNodeB software
and files required for automatic deployment. For details, see
3.2.2 Preparations.
Mandato
ry
2 Remote
operations
on the
M2000
Create an eNodeB commissioning task on the M2000. For
details, see 3.2.3 Creating an eNodeB Commissioning
Task.
Mandato
ry
3 Start the eNodeB commissioning task on the M2000. For
details, see 3.2.4 Starting an eNodeB Commissioning
Task.
Mandato
ry
4 Monitor the eNodeB commissioning task on the M2000. For
details, see 3.2.5 Monitoring eNodeB Commissioning.
Mandato
ry
5 After the eNodeB commissioning is complete, confirm the
eNodeB commissioning task. For details, see 3.2.6
Confirming eNodeB Commissioning Completion.
Mandato
ry
6 Check the eNodeB commissioning report for the eNodeB
operating status, and rectify the faults indicated in the
eNodeB commissioning report if any. For details, see 3.2.7
Checking the Running Status of the eNodeB on the
M2000.
Mandato
ry
7 Commission the antenna system on the M2000. For details,
see 3.2.8 Commissioning the Antenna System on the
M2000.
Optional
8 Local and
remote
cooperative
operations
After the environment monitoring equipment is connected,
commission the equipment so that it operates properly. For
details, see 3.2.9 Commissioning the Environment
Monitoring Equipment on the M2000.
Optional
9 Remote
operations
on the
M2000
Set the maximum transmit power of RRUs or RFUs on the
M2000. RRU and RFU are short for remote radio unit and
radio frequency unit, respectively. For details, see 3.2.10
Setting the Maximum Output Power for RRUs or
RFUs.
Optional
10 Local and
remote
cooperative
operations
Verify the basic services of the eNodeB. For details, see
3.2.11 Testing the Basic Services of the eNodeB.
Optional
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
14
St
ep
Operation Mandat
ory/
Option
al
11 Remote
operations
on the
M2000
After eNodeB commissioning is complete and the eNodeB
starts to provide services properly, set the eNodeB to the
normal state on the M2000. For details, see 3.2.12 Setting
an NE to the NORMAL Mode.
Mandato
ry
NOTE
After an eNodeB is deployed, local engineers can determine whether the eNodeB is working properly by
observing the indicators on eNodeB boards. For details about the indicator descriptions and operations for
rectifying possible faults, see 5.3 Checking the Status of Indicators.
3.2.2 Preparations
To commission an eNodeB in PnP remote commissioning mode when the security gateway
(SeGW) is not deployed, you need to collect related eNodeB information, obtain commissioning
tools, and upload the required files.
Context
Figure 3-5 shows the procedure for preparing for PnP remote eNodeB commissioning when no
SeGW is deployed.
Figure 3-5 Procedure for preparing for PnP remote commissioning when the SeGW is not
deployed
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
15
Obtaining eNodeB Information and Commissioning Tools
Before PnP remote eNodeB commissioning, you must obtain eNodeB information and
commissioning 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.
eNodeB ID Planned by the operator.
eNodeB electronic
serial number (ESN)
NOTE
The ESN information is
optional and it is
collected only in
scenarios where the
ESN is used to bind the
eNodeB.
ESN identifies an NE uniquely. During network deployment, the
installation engineer reports the mapping relationship between the
location of each site and the ESN to the staff at the maintenance
center.
The ESN is attached to the baseband unit (BBU) in the following
two 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 in
Figure 3-6. Record the ESN and the site information and then
report them to the operation and maintenance (OM) personnel.
l If the fan module on the BBU is attached with a label, the ESN
is printed on the label of the fan module and the mounting ear of
the BBU, as shown in Figure 3-7. You must remove the label to
record 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)
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
16
Figure 3-7 Location of the ESN (II)
Step 2 Obtain the tools required for the remote commissioning on the M2000, as described in Table
3-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 subscriber
server (HSS).
----End
Preparing an eNodeB Deployment List
You need to prepare an eNodeB deployment list before uploading relevant data files.
Prerequisites
l 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.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
17
Option Description
Deployment lists
are exported
from the CME
If the CME has been deployed and you have initially configured the
eNodeB on the CME, it is recommended that you use the CME to export
the eNodeB deployment list. For detailed operations, see Exporting Auto
Deployment Configuration Files in M2000 Help.
Obtain and open the exported deployment list. Check whether the software
version, cold patch, and hot patch are consistent with planned ones. If they
are inconsistent, you need to change them as planned. In addition, you need
to enter other relevant data.
NOTE
The deployment list must be exported from the CME V200R012C00 or later
releases.
Deployment lists
are exported
from the M2000
client
If the CME has not been deployed, you can export the eNodeB deployment
list from the eNodeB Auto Deployment window on the M2000 client.
1. Choose Configuration > Auto Deployment > NodeB Auto
Deployment from the main menu of the Configuration > Auto
Deployment > eNodeB Auto Deployment client. The eNodeB Auto
Deployment window is displayed.
2. Click . The Save dialog box is displayed.
3. Specify a save path and click OK.
4. Open the exported deployment list and enter or modify relevant data
based on the planned data that is confirmed with the network planning
engineers.
NOTE
l An eNodeB deployment list is in CSV format and its default name is
eNodeB_Auto_Deployment_List.csv. You can enter or modify relevant data
based on the planned data that is confirmed with the network planning engineers
by referring to Parameters for the eNodeB Deployment List.
l If there is a commissioning task in the commissioning task list, you can export
the 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 export
an empty deployment list and enter information based on the planned data.
Before the deployment, check whether the planned target version is consistent with the target
version 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 corresponding
V100R003C00SPCXXX.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
18
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 out or modify the deployment list, ensure that all the characters you enter
are valid. The base station commissioning may fail if you enter invalid characters such as comma
(,) and quotation 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 required
for procedures of eNodeB commissioning tasks are NE software versions, cold patches, hot
patches, configuration data files, deployment lists, RET antenna software versions and
configuration data files, RET antenna templates, and commissioning licenses.
Prerequisites
You have logged in to the M2000 client.
Context
You need to upload data files in the following scenarios:
l Prepare for the commissioning.
Upload the required data files to the M2000 server before commissioning as required.
l The commissioning cannot be started because certain required data files are unavailable.
The M2000 automatically checks whether data files required for customized procedures
are available. If certain data files are unavailable, the commissioning cannot be started.
Upload the required data files that are previously unavailable from the client to the
M2000 server.
The data files required for eNodeB commissioning need to be saved in specified paths on the
M2000 server. For details, see Table 3-4.
Table 3-4 File save paths
File Type Save Path
Software
version
/export/home/sysm/ftproot/eNodeB Type/Software/eNodeB Software
Version/
Cold or hot
patch
/export/home/sysm/ftproot/eNodeB Type/Patch/eNodeB Patch Version/
Configurati
on data file
/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/CfgData/
Deploymen
t list
/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/ADList/
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
19
File Type Save Path
RET
antenna
software
version and
configurati
on data file
/export/home/sysm/ftproot/OutSourcing/RETFile/
RET
antenna
template
/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/
RETTemplate/
Commissio
ning license
/export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/
CommissionLicense/
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 Click Prepare File&Data. The window for preparing files and data is displayed. Upload data
files as required.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
20
If you
need to...
Then...
Upload NE
software
versions
l Upload one by one
One or multiple software versions corresponding to a certain NE type are
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. 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
Operation, Status, Source File Path, Destination File Path, and
Progress.
5. When Progress is 100%, the software versions are uploaded.
l Upload in batches
One or multiple software versions corresponding to one or multiple NE types
are 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 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Repeat the preceding two steps to select one or multiple files
corresponding to multiple NE types. The selected files are displayed in
the Source Path area.
5. In the Source Path area, select one or multiple files and click Add. The
files to be uploaded are displayed in the lower part of the dialog box.
6. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
21
If you
need to...
Then...
Operation, Status, Source File Path, Destination File Path, and
Progress.
7. When Progress is 100%, the software versions are uploaded.
NOTE
When uploading an NE software version, if the client displays a message indicating that
the NE software version supports multiple types of base stations in the same mode, you
need to upload the version only once for a base station. Then, the other types of base
stations in the same mode can use the uploaded NE software version.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
22
If you
need to...
Then...
Upload
cold
patches
l Upload one by one
One or multiple cold patches corresponding to a certain NE type are 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. 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
Operation, Status, Source File Path, Destination File Path, and
Progress.
5. When Progress is 100%, the cold patches are uploaded.
l Upload in batches
One or multiple cold patches corresponding to one or multiple NE types are
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 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Repeat the preceding two steps to select one or multiple files
corresponding to multiple NE types. The selected files are displayed in
the Source Path area.
5. In the Source Path area, select one or multiple files and click Add. The
files to be uploaded are displayed in the lower part of the dialog box.
6. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
23
If you
need to...
Then...
Operation, Status, Source File Path, Destination File Path, and
Progress.
7. When Progress is 100%, the cold patches are uploaded.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
24
If you
need to...
Then...
Upload hot
patches
l Upload one by one
One or multiple hot patches corresponding to a certain NE type are uploaded
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.
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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
Operation, Status, Source File Path, Destination File Path, and
Progress.
5. When Progress is 100%, the hot patches are uploaded.
l Upload in batches
One or multiple hot patches corresponding to one or multiple NE types are
uploaded 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.
2. Click in the lower left corner of the dialog box, 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Repeat the preceding two steps to select one or multiple files
corresponding to multiple NE types. The selected files are displayed in
the Source Path area.
5. In the Source Path area, select one or multiple files and click Add. The
files to be uploaded are displayed in the lower part of the dialog box.
6. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
25
If you
need to...
Then...
Operation, Status, Source File Path, Destination File Path, and
Progress.
7. When Progress is 100%, the hot patches are uploaded.
Upload
configurati
on data
files
1. On the NE Configuration Data tab page, choose Transfer > From OSS
Client to OSS Server. The Upload NE Configuration Data dialog box is
displayed.
2. Select an NE type from the NE Type drop-down list.
3. In the Source Path area, click . The dialog box for selecting files is
displayed. Select the folder where the configuration data file that you want
to upload is stored, click Select. The Upload NE Configuration Data dialog
box is displayed.
CAUTION
The path for saving the eNodeB configuration data file to be uploaded must be ..
eNodeBNameM2000.XML on the local PC. An eNodeBName folder contains only
one XML file. To upload eNodeB configuration data files, you must select the
eNodeBName folder where the files are stored. You can select multiple
eNodeBName folders at a time.
The save path for the files to be uploaded to the server is displayed in the Destination
Path area. You can only view the path.
Upload
deploymen
t lists
1. On the Deployment List tab page, choose Transfer > From OSS Client to
OSS Server. The Upload Deployment List dialog box is displayed.
2. Select an NE type from the NE Type drop-down list.
3. In the Source Path area, click . The dialog box for selecting files is
displayed. Select files that you want to upload and click Open to return to
the Upload Deployment List dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the Upload Deployment List dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed information
about the operations at the bottom of the window: Operation, Status, Source
File Path, Destination File Path, and Progress.
5. When Progress is 100%, the deployment lists are uploaded.
NOTE
If the CME is not deployed, you can click Export Template to export an empty
deployment template, fill out the template based on the planned data, and upload the
template. The default names of the exported empty deployment list templates are the
same. Therefore, you are advised to change the template names after filling out these
templates.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
26
If you
need to...
Then...
Upload
RET
antenna
software
versions
and
configurati
l Upload one by one
One or multiple RET antenna software versions and configuration data files
corresponding to a certain NE type are uploaded at a time.
1. On the RET 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
Operation, Status, Source File Path, Destination File Path, and
Progress.
5. When Progress is 100%, the RET antenna software versions and
configuration data files are uploaded.
l Upload in batches
One or multiple RET antenna software versions and configuration data files
corresponding to one or multiple NE types are uploaded at a time.
1. On the RET 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 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 selecting
files is displayed. Select files that you want to upload and click OK to
return to the NE File Transfer dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Repeat the preceding two steps to select one or multiple files
corresponding to multiple NE types. The selected files are displayed in
the Source Path area.
5. In the Source Path area, select one or multiple files and click Add. The
files to be uploaded are displayed in the lower part of the dialog box.
6. Click OK to close the NE File Transfer dialog box. The system starts
uploading the data files.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
27
If you
need to...
Then...
on data
files
The data file preparation window displays the following detailed
information about the operations at the bottom of the window:
Operation, Status, Source File Path, Destination File Path, and
Progress.
7. When Progress is 100%, the RET antenna software versions and
configuration data files are uploaded.
Upload
RET
antenna
templates
1. On the RET Template tab page, choose Transfer > From OSS Client to
OSS Server. The Upload RET Template dialog box is displayed.
2. Select an NE type from the NE Type drop-down list.
3. In the Source Path area, click . The dialog box for selecting files is
displayed. Select files that you want to upload and click Open to return to
the Upload RET Template dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the Upload RET Template dialog box. The system starts
uploading the data files.
The data file preparation window displays the following detailed information
about the operations at the bottom of the window: Operation, Status, Source
File 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 RET
antenna template, fill out the template based on the planned data, and upload the
template.
Upload
commissio
ning
licenses
1. On the Commission License tab page, choose Transfer > From OSS Client
to OSS Server. The Upload Commission License dialog box is displayed.
2. Select an NE type from the NE Type drop-down list.
3. In the Source Path area, click . The dialog box for selecting files is
displayed. Select files that you want to upload and click Open to return to
the Upload Commission License dialog box.
The save path for the files to be uploaded to the server is displayed in the
Destination Path area. You can only view the path.
4. Click OK to close the Upload Commission License dialog box. The system
starts uploading the data files.
The data file preparation window displays the following detailed information
about the operations at the bottom of the window: Operation, Status, Source
File Path, Destination File Path, and Progress.
5. When Progress is 100%, the commissioning licenses are uploaded.
----End
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
28
3.2.3 Creating an eNodeB Commissioning Task
This section describes how to create an eNodeB commissioning task on the M2000 client after
commissioning preparations are complete.
Prerequisites
l 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 If the eNodeB and the M2000 server are located on different network segments, you need
to configure the router nearest to the eNodeB as the DHCP relay.
– In an insecure scenario, you need to set the DHCP relay IP address on the router to the
DHCP server IP address of the M2000. In a secure scenario, you need to set the DHCP
relay IP address on the router to the common DHCP server IP address and on the security
gateway, you need to set the IP address of the DHCP server to the DHCP server IP
address of the M2000.
– In situations where the M2000 is deployed in SLS mode, the preceding DHCP server
IP address of the M2000 refers to the host IP address.
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 Select deployment lists.
1. Click . The Import Deployment List dialog box is displayed.
2. In the Specify Deployment List area, select a deployment list.
If you need
to...
Then...
Import a
deployment list
from the server
Select From Server and choose a deployment list from the drop-
down list box.
Import a
deployment list
from 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 the
M2000 is deployed in SLS mode, NEs are managed by different servers. On the CME client,
these NEs belong to different areas. Select the active or slave M2000 server that the NE
belongs to based on the planned data. Configure the data as follows:
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
29
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.
NOTE
Onsite deployment engineers need to perform operations based on the areas that have been planned
for 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: default connection mode.
l SSL Connection: If this mode is selected, you also need to set an authentication mode.
Authentication modes are Anonymous Authority and OSS Authentication NE, where
Anonymous Authority is the default authentication mode.
NOTE
To enable automatic SSL connection during NE deployment, you need to set the authentication mode
for NE in advance on the CME in addition to setting the connection mode between the M2000 and
NEs 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 values
and invalid base station configuration data. In addition, the information indicating whether the
import succeeded or failed is displayed on the Operation Information tab page.
l If the import is successful, the M2000 automatically creates a commissioning task for each
eNodeB. The imported eNodeB deployment lists are displayed on the Deployment List tab
page.
l If the import fails, the causes of the failure are displayed on the Operation Information tab
page.
Step 4 (Optional) Modify data in the imported deployment lists as required. This step is mandatory
when you need to modify the data in the imported deployment lists.
NOTE
You can check whether the parameters in eNodeB deployment lists can be modified by referring to
Parameters for the eNodeB Deployment List.
1. Select a commissioning task from the commissioning task list, and double-click the cells
containing parameter values to change the values.
You can change ESNs by double-clicking the cells containing ESNs. Alternatively, you
can perform the following operations to change the ESNs:
a. Click in the ESN value cell. The Bind ESN dialog box is displayed.
b. Select an ESN that is not bound, and click OK to return to the Deployment
Parameter dialog box.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
30
NOTE
You can change the ESNs before OM links are established between base stations and the
M2000.
2. The changed parameter values are displayed in the commissioning task window and
highlighted in red.
----End
3.2.4 Starting an eNodeB Commissioning Task
This section describes how to start an eNodeB commissioning task. After creating an eNodeB
commissioning task, you can set commissioning procedures and start the task. Then, the
M2000 automatically commissions the eNodeB.
Prerequisites
l You have logged in to the M2000 client.
l eNodeB commissioning tasks have been started.
Context
A maximum of 500 commissioning tasks can be started at a time. In which, a maximum of 200
commissioning tasks can be being executed and the rest are waiting to be executed in the queue.
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 On the Deployment List tab page, right-click one or multiple commissioning tasks and choose
Start from the shortcut menu. The Task Settings dialog box is displayed.
Step 3 Select steps in the Select column based on the actual plan.
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.
Table 3-5 Description of commissioning process
No. Procedur
e
Step Description
1 Auto
Discovery
Check OM
channel
When connection of the transport network is
proper, the M2000 automatically sets up an OM
channel to connect to the desired eNodeB based
on the deployment list, and commissions and
maintains the NodeB through this channel.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
31
No. Procedur
e
Step Description
Wait for manual
operation
After the OM channel is set up, the status of the
commissioning task changes to Waiting for
manual operation. Manually confirm the
completion and proceed with the commissioning
after the commissioning environment of the
network is ready.
2 Auto
Configura
tion
Download
software
The M2000 automatically checks whether the
current eNodeB version is the same as the target
software version given in the deployment list. If
the versions are not the same, the M2000
automatically downloads software from the
server to the eNodeB.
Download
configuration
The M2000 downloads the desired configuration
file from the server to the eNodeB based on the
target version information.
Activate Activate the eNodeB configuration data (takes
effect after next reset) and then activate the
software (automatic reset).
3 Auto
Planning
Auto Planning Only the BTS3202E is supported in eNodeB auto
deployment.
4 Upload
commissi
oning
license
Distribute
commissioning
license
When some eNodeB functions are restricted
because the eNodeB uses the default license upon
delivery, you need to install a commissioning
license. The commissioning license has time
restriction. You need to replace the
commissioning license with the commercial one
as soon as possible after the eNodeB
commissioning is complete.
5 Commissi
on RET
Upgrade RET
software version
The target RET antenna software version is
provided by antenna line device (ALD) suppliers
and 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, you
do not need to commission the RET antennas.
l When antennas are managed by the
management system of a third party, you do
not need to commission RET antennas.
Upgrade RET
configuration
The RET antenna configuration file is provided
by ALD suppliers and saved on the local PC. RET
antenna configuration data may vary according to
RET antenna types and suppliers.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
32
No. Procedur
e
Step Description
Tune RET Check whether RET antennas are commissioned
correctly during the commissioning.
6 Test and
monitor
Test installation
& deployment
quality
Services carried on the RF module will be
interrupted during operation. If an RF module is
shared by base stations of different RATs,
services of the other RAT will also be interrupted.
The check may take several minutes. The project
quality check involves the VSWR, offline
intermodulation interference, and crossed pair.
Monitor cell
service status
Check whether any active cells exist under the
eNodeB.
You can monitor alarms of the eNodeB on the
M2000 during software commissioning to locate
and handle exceptions in time.
7 Perform
NHC
Perform NHC You can perform health check to learn the
eNodeB operating status.
8 Wait for
confirmati
on
Wait for
confirmation
After service verification is complete, the
commissioning task is in the Waiting for
Confirmation state. You need to manually
confirm that the commissioning is complete.
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 proceed
with subsequent operations.
l If only some configured RF modules are usable, the system sets a timer (2.5 minutes in length and a
maximum of 5 times) to wait until all RF modules are usable. After all RF modules are usable, the
system issues project quality check commands to proceed with subsequent operations. If some RF
modules 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 are
available.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
33
If... Then...
Not all the
required data
files are available
1. The Data Preparation Check dialog box is displayed, showing check
results 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 required
data files are
available
The M2000 starts commissioning. The selected commissioning tasks enter
the Running state.
NOTE
If all the required data files are available, the Data Preparation Check dialog box
is not displayed.
----End
3.2.5 Monitoring eNodeB Commissioning
This section describes how to monitor eNodeB commissioning on the M2000 to learn about
commissioning 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 the
M2000 to learn about process of the tasks.
Prerequisites
l You have logged in to the M2000 client.
l eNodeB commissioning tasks have been started.
Context
l 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 not
restart NE upgrades but proceeds until the related NE upgrade task is complete. When the
system displays The NE is performing the following task: ******. Please try later. in
Description for a commissioning task, the NE upgrade task is running. If you want to
perform automatic deployment again, wait until the NE upgrade task is complete. You can
choose Software > NE Upgrade Task Management > NE Upgrade Task to query the
NE upgrade task.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
34
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 View the status and progress of commissioning tasks in the commissioning task list.
TIP
You can quickly view the status of commissioning tasks by using either of the following methods:
l In the commissioning task list, the status of the tasks is displayed in Status, the current procedures are
displayed in Current Phase, and details about each procedure are displayed in 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 of
steps for commissioning procedures.
The displayed information includes the execution status, description, start time and end time of each
commissioning substep.
Step 3 (Optional) Click . The Statistics dialog box is displayed, showing the number of
commissioning tasks in each status. Click OK to close the dialog box.
----End
Handling eNodeB Alarms
This section describes how to handle eNodeB alarms. After eNodeB software is automatically
upgraded, you can use the M2000 to view alarms on eNodeBs. All alarms related to eNodeBs
are categorized by object to help you query required alarms.
Prerequisites
l 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.
Context
The alarms are categorized into E1/T1 port alarms, transmission path alarms, antenna alarms,
software and configuration alarms, board alarms, cell alarms, external alarms, and other alarms
by object type. Other alarms refer to the alarms that cannot be categorized on the basis of specific
objects.
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you want
to handle alarms. Right-click the tasks, and then choose Open Monitor Window from the
shortcut menu. The alarm monitoring window is displayed.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
35
In the displayed window, you can view alarms on eNodeBs by monitored object. For details
about the alarm monitoring window, see Interface Description: eNodeB Commissioning
Window.
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 Diagnosis
This section describes how to perform antenna fault diagnosis. The M2000 provides automatic
fault diagnosis to antennas. When errors occur during eNodeB commissioning, you can use the
automatic fault diagnosis function provided by the M2000 to check whether the eNodeB that is
being commissioned is faulty. Then, you can take corresponding measures to rectify the faults
based on the diagnosis results.
Prerequisites
l 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
CAUTION
eNodeB services are interrupted upon antenna fault diagnosis. Therefore, you need to perform
the 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 involves
the VSWR test, offline intermodulation interference test, and crossed pair test.
After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task and
displays the diagnosis progress. After the fault diagnosis is complete, you can obtain the fault
diagnosis report.
If you delete a fault diagnosis task, the corresponding diagnosis report is deleted accordingly.
If you restart the M2000 server, all fault diagnosis tasks and reports are deleted.
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
36
Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you want
to handle alarms. Right-click the tasks, and then choose Open Monitor Window from the
shortcut menu. The alarm monitoring window is displayed.
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 or
alarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settings
dialog box is displayed.
2. Select an eNodeB in the Select NE area, select a diagnosis type in the Select diagnose
type area, type diagnosis parameters in the Type diagnosis parameters area, and then
click OK. The dialog box for confirming the diagnosis is displayed.
3. Click Yes. The system starts the fault diagnosis.
During the fault diagnosis, a diagnosis task is added to the diagnosis task list.
NOTE
Fault diagnosis may take a long time when there are a large number of detection services executed
by 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 task
list, and choose Diagnose Report from the shortcut menu to view diagnosis results.
----End
Managing eNodeB Commissioning Tasks
This section describes how to manage eNodeB commissioning tasks. After creating or starting
eNodeB commissioning tasks, you can delete, restart, pause, resume, or cancel the selected tasks.
Prerequisites
l You have logged in to the M2000 client.
l eNodeB commissioning tasks have been created or started.
Context
For details about operations on commissioning tasks, see Table 3-6.
Table 3-6 Operations on commissioning tasks
Opera
tion
Description
Delete You can perform this operation on commissioning tasks in any state.
Restart You can perform this operation on commissioning tasks in the Running,
Abnormal, Paused, or Waiting for Confirmation state.
Pause You can perform this operation on commissioning tasks in the Running state.
Resum
e
You can perform this operation on commissioning tasks in the Paused state.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
37
Opera
tion
Description
Cancel You can perform this operation on commissioning tasks in the Running,
Abnormal, or Paused state.
Procedure
Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu
of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB
Auto Deployment window is displayed.
Step 2 On the Deployment List tab page, select one or multiple commissioning tasks and perform
operations as required.
If you
need to...
Then...
Restart Right-click the tasks and choose Restart from the shortcut menu. The tasks
return to the Running state.
Pause Right-click the tasks and choose Pause from the shortcut menu. The tasks are
in the Paused state.
Resume Right-click the tasks and choose Resume from the shortcut menu. The tasks
proceed from where they are paused.
Cancel Right-click the tasks and choose Cancel from the shortcut menu. The tasks
return to the Wait for Start state.
Delete 1. Right-click the tasks and choose Delete from the shortcut menu. The
Confirm dialog box is displayed.
2. Click OK. The system starts deleting the tasks.
----End
3.2.6 Confirming eNodeB Commissioning Completion
When the status of an eNodeB commissioning task changes to Waiting for Confirmation, you
need to confirm that the eNodeB commissioning is complete.
Prerequisites
l The eNodeB is properly connected to the M2000.
l The status of the eNodeB commissioning task is Waiting for Confirmation.
Procedure
Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto
Deployment. The eNodeB Auto Deployment tag page is displayed.
eNodeB
Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW)
Issue 04 (2012-06-29) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
38
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en
E nodeb commissioning guide(v100r005c00 04)(pdf)-en

Mais conteúdo relacionado

Mais procurados

Huawei GSM Principles
Huawei GSM PrinciplesHuawei GSM Principles
Huawei GSM PrinciplesAchmad Fauzi
 
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarking
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarkingE2 e+call+setup+time+(cst)+enhacenments p3_benchmarking
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarkingOtseakemhe
 
Microwave Huawei RTN Hardware Structure
Microwave Huawei RTN Hardware StructureMicrowave Huawei RTN Hardware Structure
Microwave Huawei RTN Hardware Structureibrahimnabil17
 
240243228 huawei-bts-3900-training
240243228 huawei-bts-3900-training240243228 huawei-bts-3900-training
240243228 huawei-bts-3900-trainingShelton Siziba
 
Huawei case analysis call drop
Huawei case analysis call dropHuawei case analysis call drop
Huawei case analysis call dropMuffat Itoro
 
Simplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach ProcedureSimplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach Procedure3G4G
 
Ericsson BTS commisioning
Ericsson BTS commisioningEricsson BTS commisioning
Ericsson BTS commisioningShahid Rasool
 
2 g training optimization
2 g training optimization2 g training optimization
2 g training optimizationAhmed Gad
 
Call Setup Success Rate Definition and Troubleshooting
Call Setup Success Rate Definition and Troubleshooting Call Setup Success Rate Definition and Troubleshooting
Call Setup Success Rate Definition and Troubleshooting Assim Mubder
 
Simplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice CallSimplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice Call3G4G
 
Subrack and cabinet numbering rules
Subrack and cabinet numbering rulesSubrack and cabinet numbering rules
Subrack and cabinet numbering rulesKhawla Boulaares
 
Hw lte rf-optimization-guide
Hw lte rf-optimization-guideHw lte rf-optimization-guide
Hw lte rf-optimization-guidetharinduwije
 
Kpi 2g troubleshootin
Kpi 2g troubleshootinKpi 2g troubleshootin
Kpi 2g troubleshootinAbd Yehia
 

Mais procurados (20)

UMTS/LTE/EPC Call Flows for CSFB
UMTS/LTE/EPC Call Flows for CSFBUMTS/LTE/EPC Call Flows for CSFB
UMTS/LTE/EPC Call Flows for CSFB
 
Huawei GSM Principles
Huawei GSM PrinciplesHuawei GSM Principles
Huawei GSM Principles
 
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarking
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarkingE2 e+call+setup+time+(cst)+enhacenments p3_benchmarking
E2 e+call+setup+time+(cst)+enhacenments p3_benchmarking
 
Microwave Huawei RTN Hardware Structure
Microwave Huawei RTN Hardware StructureMicrowave Huawei RTN Hardware Structure
Microwave Huawei RTN Hardware Structure
 
240243228 huawei-bts-3900-training
240243228 huawei-bts-3900-training240243228 huawei-bts-3900-training
240243228 huawei-bts-3900-training
 
Cs fallback feature
Cs fallback featureCs fallback feature
Cs fallback feature
 
ZTE BTS Manual
ZTE BTS ManualZTE BTS Manual
ZTE BTS Manual
 
Rtn
RtnRtn
Rtn
 
LTE Optimization
LTE OptimizationLTE Optimization
LTE Optimization
 
Huawei case analysis call drop
Huawei case analysis call dropHuawei case analysis call drop
Huawei case analysis call drop
 
Simplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach ProcedureSimplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach Procedure
 
Ericsson BTS commisioning
Ericsson BTS commisioningEricsson BTS commisioning
Ericsson BTS commisioning
 
LTE KPI
LTE KPILTE KPI
LTE KPI
 
2 g training optimization
2 g training optimization2 g training optimization
2 g training optimization
 
Call Setup Success Rate Definition and Troubleshooting
Call Setup Success Rate Definition and Troubleshooting Call Setup Success Rate Definition and Troubleshooting
Call Setup Success Rate Definition and Troubleshooting
 
Simplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice CallSimplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice Call
 
Ubbp
UbbpUbbp
Ubbp
 
Subrack and cabinet numbering rules
Subrack and cabinet numbering rulesSubrack and cabinet numbering rules
Subrack and cabinet numbering rules
 
Hw lte rf-optimization-guide
Hw lte rf-optimization-guideHw lte rf-optimization-guide
Hw lte rf-optimization-guide
 
Kpi 2g troubleshootin
Kpi 2g troubleshootinKpi 2g troubleshootin
Kpi 2g troubleshootin
 

Destaque

1.training lte ran kpi & counters rjil
1.training lte ran kpi & counters rjil1.training lte ran kpi & counters rjil
1.training lte ran kpi & counters rjilSatish Jadav
 
Wcdma Core Network Introduction
Wcdma Core Network IntroductionWcdma Core Network Introduction
Wcdma Core Network Introductionguest1f85dd
 
Bts3900 Site Maintenance Guide(V200 01)
Bts3900 Site Maintenance Guide(V200 01)Bts3900 Site Maintenance Guide(V200 01)
Bts3900 Site Maintenance Guide(V200 01)Atif Mahmood
 
Soft x3000 operation manual configuration guide
Soft x3000 operation manual configuration guideSoft x3000 operation manual configuration guide
Soft x3000 operation manual configuration guideTuhin Narayan
 
01 Bts3900 System Structure
01 Bts3900 System Structure01 Bts3900 System Structure
01 Bts3900 System StructureAtif Mahmood
 
Comparison between bts 312, 3012 and 3900 by usman zulfqar
Comparison between bts 312, 3012 and 3900 by usman zulfqarComparison between bts 312, 3012 and 3900 by usman zulfqar
Comparison between bts 312, 3012 and 3900 by usman zulfqarusman zulfqar
 
Bts3900 gsm commissioning guide (v300 r008-03)
Bts3900 gsm commissioning guide (v300 r008-03)Bts3900 gsm commissioning guide (v300 r008-03)
Bts3900 gsm commissioning guide (v300 r008-03)ihtisham ulhaq
 
Petrolium and gas processing
Petrolium and gas processingPetrolium and gas processing
Petrolium and gas processingwaseemakhtar120
 
Hydrocarbon preeti bhatt
Hydrocarbon preeti bhattHydrocarbon preeti bhatt
Hydrocarbon preeti bhattkapde1970
 
Hp 2011 Rph Refining Hydrocarbon Technologies Profiles
Hp 2011 Rph Refining Hydrocarbon Technologies ProfilesHp 2011 Rph Refining Hydrocarbon Technologies Profiles
Hp 2011 Rph Refining Hydrocarbon Technologies Profilesabakshi2011
 
Introduction to Mobile Core Network
Introduction to Mobile Core NetworkIntroduction to Mobile Core Network
Introduction to Mobile Core Networkyusufd
 
Commissioning & Interface With Engineering
Commissioning & Interface With EngineeringCommissioning & Interface With Engineering
Commissioning & Interface With Engineeringasim569
 
Commissioning Plan Robert Thelander, Svenska kraftnät
Commissioning Plan Robert Thelander, Svenska kraftnät Commissioning Plan Robert Thelander, Svenska kraftnät
Commissioning Plan Robert Thelander, Svenska kraftnät Fingrid Oyj
 
Power Point On Hydrocarbon
Power Point On HydrocarbonPower Point On Hydrocarbon
Power Point On HydrocarbonSamiran Ghosh
 
Mechanical Completions
Mechanical CompletionsMechanical Completions
Mechanical CompletionsAndy Lang
 
Oil And Gas Processing
Oil And Gas ProcessingOil And Gas Processing
Oil And Gas Processingmubarak2009
 

Destaque (20)

1.training lte ran kpi & counters rjil
1.training lte ran kpi & counters rjil1.training lte ran kpi & counters rjil
1.training lte ran kpi & counters rjil
 
Wcdma Core Network Introduction
Wcdma Core Network IntroductionWcdma Core Network Introduction
Wcdma Core Network Introduction
 
Bts3900 Site Maintenance Guide(V200 01)
Bts3900 Site Maintenance Guide(V200 01)Bts3900 Site Maintenance Guide(V200 01)
Bts3900 Site Maintenance Guide(V200 01)
 
Soft x3000 operation manual configuration guide
Soft x3000 operation manual configuration guideSoft x3000 operation manual configuration guide
Soft x3000 operation manual configuration guide
 
01 Bts3900 System Structure
01 Bts3900 System Structure01 Bts3900 System Structure
01 Bts3900 System Structure
 
Comparison between bts 312, 3012 and 3900 by usman zulfqar
Comparison between bts 312, 3012 and 3900 by usman zulfqarComparison between bts 312, 3012 and 3900 by usman zulfqar
Comparison between bts 312, 3012 and 3900 by usman zulfqar
 
PS Core Presentation
PS Core PresentationPS Core Presentation
PS Core Presentation
 
Call flows
Call flowsCall flows
Call flows
 
Bts3900 gsm commissioning guide (v300 r008-03)
Bts3900 gsm commissioning guide (v300 r008-03)Bts3900 gsm commissioning guide (v300 r008-03)
Bts3900 gsm commissioning guide (v300 r008-03)
 
Petrolium and gas processing
Petrolium and gas processingPetrolium and gas processing
Petrolium and gas processing
 
Hydrocarbon preeti bhatt
Hydrocarbon preeti bhattHydrocarbon preeti bhatt
Hydrocarbon preeti bhatt
 
Hp 2011 Rph Refining Hydrocarbon Technologies Profiles
Hp 2011 Rph Refining Hydrocarbon Technologies ProfilesHp 2011 Rph Refining Hydrocarbon Technologies Profiles
Hp 2011 Rph Refining Hydrocarbon Technologies Profiles
 
Introduction to Mobile Core Network
Introduction to Mobile Core NetworkIntroduction to Mobile Core Network
Introduction to Mobile Core Network
 
Hydrocarbons
HydrocarbonsHydrocarbons
Hydrocarbons
 
Commissioning & Interface With Engineering
Commissioning & Interface With EngineeringCommissioning & Interface With Engineering
Commissioning & Interface With Engineering
 
Hydrocarbons
HydrocarbonsHydrocarbons
Hydrocarbons
 
Commissioning Plan Robert Thelander, Svenska kraftnät
Commissioning Plan Robert Thelander, Svenska kraftnät Commissioning Plan Robert Thelander, Svenska kraftnät
Commissioning Plan Robert Thelander, Svenska kraftnät
 
Power Point On Hydrocarbon
Power Point On HydrocarbonPower Point On Hydrocarbon
Power Point On Hydrocarbon
 
Mechanical Completions
Mechanical CompletionsMechanical Completions
Mechanical Completions
 
Oil And Gas Processing
Oil And Gas ProcessingOil And Gas Processing
Oil And Gas Processing
 

Semelhante a E nodeb commissioning guide(v100r005c00 04)(pdf)-en

Huawei node b technical-description
Huawei node b technical-descriptionHuawei node b technical-description
Huawei node b technical-descriptionYasir Jami
 
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdf
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdfConfiguration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdf
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdfRandyDookheran1
 
Bsc6900 gsm-site-maintenance-guide
Bsc6900 gsm-site-maintenance-guideBsc6900 gsm-site-maintenance-guide
Bsc6900 gsm-site-maintenance-guidemalikaliasadawan
 
Rfu hardware description(v100 r008c00 04)(pdf)-en
Rfu hardware description(v100 r008c00 04)(pdf)-enRfu hardware description(v100 r008c00 04)(pdf)-en
Rfu hardware description(v100 r008c00 04)(pdf)-enCharles Mbaziira
 
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01moussaCoulibaly22
 
3900 series base station performance counter reference(v4r6c08) 3
3900 series base station performance counter reference(v4r6c08) 33900 series base station performance counter reference(v4r6c08) 3
3900 series base station performance counter reference(v4r6c08) 3Altaie Al-Taie
 
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-en
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-enBsc6910 spare parts catalog(v100 r016c00 01)(pdf)-en
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-enMohammed Jaber
 
Og for sdh ason network management (v100 r002c01-02)
Og for sdh ason network management (v100 r002c01-02)Og for sdh ason network management (v100 r002c01-02)
Og for sdh ason network management (v100 r002c01-02)Nicat Mikayilov
 
Routine maintenance(v600 r003c00 02)
Routine maintenance(v600 r003c00 02)Routine maintenance(v600 r003c00 02)
Routine maintenance(v600 r003c00 02)Hjsaavedra Linarte
 
Configuration guide basic configurations(v800 r002c01-01)
Configuration guide   basic configurations(v800 r002c01-01)Configuration guide   basic configurations(v800 r002c01-01)
Configuration guide basic configurations(v800 r002c01-01)KIRAN KUMAR M
 
Huawei Bts3900C (omb+rru) (ver.c) hardware description
Huawei Bts3900C (omb+rru) (ver.c) hardware descriptionHuawei Bts3900C (omb+rru) (ver.c) hardware description
Huawei Bts3900C (omb+rru) (ver.c) hardware descriptionYassmina AGHIL
 
Configuration guide vpn(v200 r002c00-02)
Configuration guide   vpn(v200 r002c00-02)Configuration guide   vpn(v200 r002c00-02)
Configuration guide vpn(v200 r002c00-02)mohsin225
 
Configuration guide basic configurations(v800 r002c01-01)
Configuration guide   basic configurations(v800 r002c01-01)Configuration guide   basic configurations(v800 r002c01-01)
Configuration guide basic configurations(v800 r002c01-01)Ghulam Mohyud Din
 
4G troubleshooting
4G troubleshooting4G troubleshooting
4G troubleshootingThang Dang
 
Ma5631 configuration guide(v800 r308c02 02)
Ma5631 configuration guide(v800 r308c02 02)Ma5631 configuration guide(v800 r308c02 02)
Ma5631 configuration guide(v800 r308c02 02)Jb Menezes
 
Configuration guide ethernet(v100 r006c01-02)
Configuration guide   ethernet(v100 r006c01-02)Configuration guide   ethernet(v100 r006c01-02)
Configuration guide ethernet(v100 r006c01-02)Edgar Rocha
 
Configuration guide basic configuration(v100 r006c00-01)
Configuration guide   basic configuration(v100 r006c00-01)Configuration guide   basic configuration(v100 r006c00-01)
Configuration guide basic configuration(v100 r006c00-01)Ivo Rodrigues
 

Semelhante a E nodeb commissioning guide(v100r005c00 04)(pdf)-en (20)

Huawei node b technical-description
Huawei node b technical-descriptionHuawei node b technical-description
Huawei node b technical-description
 
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdf
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdfConfiguration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdf
Configuration Guide - IP Multicast(V600R001C00_04) - NE80E40E.pdf
 
Bsc6900 gsm-site-maintenance-guide
Bsc6900 gsm-site-maintenance-guideBsc6900 gsm-site-maintenance-guide
Bsc6900 gsm-site-maintenance-guide
 
Rfu hardware description(v100 r008c00 04)(pdf)-en
Rfu hardware description(v100 r008c00 04)(pdf)-enRfu hardware description(v100 r008c00 04)(pdf)-en
Rfu hardware description(v100 r008c00 04)(pdf)-en
 
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01
Bsc6900 gsm-site-maintenance-guide-131210234714-phpapp01
 
dbs3900.pdf
dbs3900.pdfdbs3900.pdf
dbs3900.pdf
 
3900 series base station performance counter reference(v4r6c08) 3
3900 series base station performance counter reference(v4r6c08) 33900 series base station performance counter reference(v4r6c08) 3
3900 series base station performance counter reference(v4r6c08) 3
 
rru.pdf
rru.pdfrru.pdf
rru.pdf
 
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-en
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-enBsc6910 spare parts catalog(v100 r016c00 01)(pdf)-en
Bsc6910 spare parts catalog(v100 r016c00 01)(pdf)-en
 
Og for sdh ason network management (v100 r002c01-02)
Og for sdh ason network management (v100 r002c01-02)Og for sdh ason network management (v100 r002c01-02)
Og for sdh ason network management (v100 r002c01-02)
 
Routine maintenance(v600 r003c00 02)
Routine maintenance(v600 r003c00 02)Routine maintenance(v600 r003c00 02)
Routine maintenance(v600 r003c00 02)
 
Configuration guide basic configurations(v800 r002c01-01)
Configuration guide   basic configurations(v800 r002c01-01)Configuration guide   basic configurations(v800 r002c01-01)
Configuration guide basic configurations(v800 r002c01-01)
 
Huawei Bts3900C (omb+rru) (ver.c) hardware description
Huawei Bts3900C (omb+rru) (ver.c) hardware descriptionHuawei Bts3900C (omb+rru) (ver.c) hardware description
Huawei Bts3900C (omb+rru) (ver.c) hardware description
 
Configuration guide vpn(v200 r002c00-02)
Configuration guide   vpn(v200 r002c00-02)Configuration guide   vpn(v200 r002c00-02)
Configuration guide vpn(v200 r002c00-02)
 
Configuration guide basic configurations(v800 r002c01-01)
Configuration guide   basic configurations(v800 r002c01-01)Configuration guide   basic configurations(v800 r002c01-01)
Configuration guide basic configurations(v800 r002c01-01)
 
4G troubleshooting
4G troubleshooting4G troubleshooting
4G troubleshooting
 
huawei doc
huawei dochuawei doc
huawei doc
 
Ma5631 configuration guide(v800 r308c02 02)
Ma5631 configuration guide(v800 r308c02 02)Ma5631 configuration guide(v800 r308c02 02)
Ma5631 configuration guide(v800 r308c02 02)
 
Configuration guide ethernet(v100 r006c01-02)
Configuration guide   ethernet(v100 r006c01-02)Configuration guide   ethernet(v100 r006c01-02)
Configuration guide ethernet(v100 r006c01-02)
 
Configuration guide basic configuration(v100 r006c00-01)
Configuration guide   basic configuration(v100 r006c00-01)Configuration guide   basic configuration(v100 r006c00-01)
Configuration guide basic configuration(v100 r006c00-01)
 

Último

Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfAijun Zhang
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...DianaGray10
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsSeth Reyes
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1DianaGray10
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7DianaGray10
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdfJamie (Taka) Wang
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
Cloud Revolution: Exploring the New Wave of Serverless Spatial Data
Cloud Revolution: Exploring the New Wave of Serverless Spatial DataCloud Revolution: Exploring the New Wave of Serverless Spatial Data
Cloud Revolution: Exploring the New Wave of Serverless Spatial DataSafe Software
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaborationbruanjhuli
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Spring24-Release Overview - Wellingtion User Group-1.pdf
Spring24-Release Overview - Wellingtion User Group-1.pdfSpring24-Release Overview - Wellingtion User Group-1.pdf
Spring24-Release Overview - Wellingtion User Group-1.pdfAnna Loughnan Colquhoun
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IES VE
 
Babel Compiler - Transforming JavaScript for All Browsers.pptx
Babel Compiler - Transforming JavaScript for All Browsers.pptxBabel Compiler - Transforming JavaScript for All Browsers.pptx
Babel Compiler - Transforming JavaScript for All Browsers.pptxYounusS2
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 

Último (20)

Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdf
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and Hazards
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf
20200723_insight_release_plan_v6.pdf20200723_insight_release_plan_v6.pdf
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
Cloud Revolution: Exploring the New Wave of Serverless Spatial Data
Cloud Revolution: Exploring the New Wave of Serverless Spatial DataCloud Revolution: Exploring the New Wave of Serverless Spatial Data
Cloud Revolution: Exploring the New Wave of Serverless Spatial Data
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Spring24-Release Overview - Wellingtion User Group-1.pdf
Spring24-Release Overview - Wellingtion User Group-1.pdfSpring24-Release Overview - Wellingtion User Group-1.pdf
Spring24-Release Overview - Wellingtion User Group-1.pdf
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
 
Babel Compiler - Transforming JavaScript for All Browsers.pptx
Babel Compiler - Transforming JavaScript for All Browsers.pptxBabel Compiler - Transforming JavaScript for All Browsers.pptx
Babel Compiler - Transforming JavaScript for All Browsers.pptx
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 

E nodeb commissioning guide(v100r005c00 04)(pdf)-en

  • 1. eNodeB V100R005C00 Commissioning Guide Issue 04 Date 2012-06-29 HUAWEI TECHNOLOGIES CO., LTD.
  • 2. 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 written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: http://www.huawei.com Email: support@huawei.com Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. i
  • 3. About This Document Purpose This document describes how to commission an eNodeB after the eNodeB is successfully installed and configured to verify that the eNodeB works properly as designed. The eNodeB supports three commissioning modes: M2000-based remote commissioning, USB-based local commissioning+M2000-based remote commissioning, and LMT-based local commissioning. Product Versions The 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 Audience This document is intended for: l eNodeB installation engineers l Field engineers eNodeB Commissioning Guide About This Document Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. ii
  • 4. Organization 1 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, local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT. Each commissioning mode can be applied to the scenario where the SeGW is deployed and the scenario where no SeGW is deployed. In the security scenario, PnP remote commissioning is classified into PnP remote commissioning in unified encryption mode and PnP remote commissioning in differentiated encryption mode; local commissioning using a USB flash drive is classified into local commissioning using a USB flash drive in unified encryption mode and local commissioning using a USB flash drive in differentiated encryption mode. You can select a commissioning mode based on site conditions. PnP remote commissioning is recommended. 3 eNodeB Commissioning Procedures (Without the SeGW) This chapter describes the following procedures when no security gateway (SeGW) is deployed: eNodeB automatic discovery, plug and play (PnP) remote commissioning, local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT. 4 eNodeB Commissioning Procedures (with the SeGW) This chapter describes the following procedures when the SeGW is deployed in the network: eNodeB automatic discovery, PnP remote commissioning in unified encryption mode, PnP remote commissioning in differentiated encryption mode, local commissioning using a USB flash drive in unified encryption mode, local commissioning using a USB flash drive in differentiated encryption mode, and local commissioning on the LMT. 5 Appendix This chapter describes how to encrypt files in a Universal Serial Bus (USB) storage device and provides the eNodeB commissioning data sheet. 6 FAQ This chapter describes some common problems and solutions during commissioning. Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. eNodeB Commissioning Guide About This Document Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. iii
  • 5. Symbol Description Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text. General Conventions The general conventions that may be found in this document are defined as follows. Convention Description Times New Roman Normal paragraphs are in Times New Roman. Boldface Names of files, directories, folders, and users are in boldface. For example, log in as user root. Italic Book titles are in italics. Courier New Examples of information displayed on the screen are in Courier New. Command Conventions The command conventions that may be found in this document are defined as follows. Convention Description Boldface The keywords of a command line are in boldface. Italic Command arguments are in italics. [ ] Items (keywords or arguments) in brackets [ ] are optional. { x | y | ... } Optional items are grouped in braces and separated by vertical bars. One item is selected. [ x | y | ... ] Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. { x | y | ... }* Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. [ x | y | ... ]* Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected. eNodeB Commissioning Guide About This Document Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. iv
  • 6. GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Description Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. > Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder. Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Description Key Press the key. For example, press Enter and press Tab. Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn. Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Description Click Select and release the primary mouse button without moving the pointer. Double-click Press the primary mouse button twice continuously and quickly without moving the pointer. Drag Press and hold the primary mouse button and move the pointer to a certain position. eNodeB Commissioning Guide About This Document Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. v
  • 7. Contents About This Document.....................................................................................................................ii 1 Changes in eNodeB Commissioning Guide............................................................................1 2 Commissioning Mode..................................................................................................................6 3 eNodeB Commissioning Procedures (Without the SeGW)...................................................9 3.1 Overview of eNodeB Automatic Discovery (Without the SeGW)..................................................................10 3.2 PnP Remote Commissioning (Without the SeGW)..........................................................................................12 3.2.1 Commissioning Procedure.......................................................................................................................12 3.2.2 Preparations.............................................................................................................................................15 3.2.3 Creating an eNodeB Commissioning Task.............................................................................................29 3.2.4 Starting an eNodeB Commissioning Task...............................................................................................31 3.2.5 Monitoring eNodeB Commissioning.......................................................................................................34 3.2.6 Confirming eNodeB Commissioning Completion..................................................................................38 3.2.7 Checking the Running Status of the eNodeB on the M2000...................................................................39 3.2.8 Commissioning the Antenna System on the M2000...............................................................................42 3.2.9 Commissioning the Environment Monitoring Equipment on the M2000...............................................47 3.2.10 Setting the Maximum Output Power for RRUs or RFUs......................................................................50 3.2.11 Testing the Basic Services of the eNodeB.............................................................................................51 3.2.12 Setting an NE to the NORMAL Mode..................................................................................................52 3.2.13 References to eNodeB Commissioning.................................................................................................53 3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW)...........................................................62 3.3.1 Commissioning Procedure.......................................................................................................................62 3.3.2 Preparations.............................................................................................................................................65 3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive.................................................................................................................................................................68 3.3.4 Uploading Data Files...............................................................................................................................72 3.3.5 Creating an eNodeB Commissioning Task.............................................................................................82 3.3.6 Starting an eNodeB Commissioning Task...............................................................................................84 3.3.7 Monitoring eNodeB Commissioning.......................................................................................................87 3.3.8 Confirming eNodeB Commissioning Completion..................................................................................91 3.3.9 Checking the Running Status of the eNodeB on the M2000...................................................................92 3.3.10 Commissioning the Antenna System on the M2000.............................................................................95 3.3.11 Commissioning the Environment Monitoring Equipment on the M2000...........................................100 eNodeB Commissioning Guide Contents Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. vi
  • 8. 3.3.12 Setting the Maximum Output Power for RRUs or RFUs....................................................................103 3.3.13 Testing the Basic Services of the eNodeB...........................................................................................104 3.3.14 Setting an NE to the NORMAL Mode................................................................................................105 3.3.15 References to eNodeB Commissioning...............................................................................................106 3.4 Local Commissioning on the LMT(Without the SeGW)...............................................................................115 3.4.1 Commissioning Procedure.....................................................................................................................115 3.4.2 Preparations...........................................................................................................................................118 3.4.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........121 3.4.4 Downloading the License for eNodeB Commissioning on the LMT....................................................124 3.4.5 Commissioning the Antenna System on the LMT................................................................................124 3.4.6 Commissioning the Environment Monitoring Equipment on the LMT................................................130 3.4.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................132 3.4.8 Handling the eNodeB Alarms on the LMT...........................................................................................133 3.4.9 Checking the Operating Status of the eNodeB on the LMT..................................................................133 3.4.10 Testing the Basic Services of the eNodeB...........................................................................................134 3.4.11 Establishing an OML Between the M2000 and the eNodeB...............................................................135 3.4.12 Setting an NE to the NORMAL Mode................................................................................................138 4 eNodeB Commissioning Procedures (with the SeGW).....................................................139 4.1 Overview of eNodeB Automatic Discovery (with the SeGW)......................................................................142 4.2 PnP Remote Commissioning in Unified Encryption Mode (with the SeGW)...............................................150 4.2.1 Commissioning Procedure.....................................................................................................................150 4.2.2 Preparations...........................................................................................................................................153 4.2.3 Creating an eNodeB Commissioning Task...........................................................................................175 4.2.4 Starting an eNodeB Commissioning Task.............................................................................................177 4.2.5 Monitoring eNodeB Commissioning.....................................................................................................180 4.2.6 Confirming eNodeB Commissioning Completion................................................................................184 4.2.7 Checking the Running Status of the eNodeB on the M2000.................................................................185 4.2.8 Commissioning the Antenna System on the M2000.............................................................................189 4.2.9 Commissioning the Environment Monitoring Equipment on the M2000.............................................193 4.2.10 Setting the Maximum Output Power for RRUs or RFUs....................................................................196 4.2.11 Testing the Basic Services of the eNodeB...........................................................................................197 4.2.12 Setting an NE to the NORMAL Mode................................................................................................198 4.2.13 References to eNodeB Commissioning...............................................................................................199 4.3 PnP Remote Commissioning in Differentiated Encryption Mode (with the SeGW).....................................208 4.3.1 Commissioning Procedure.....................................................................................................................208 4.3.2 Preparations...........................................................................................................................................211 4.3.3 Creating an eNodeB Commissioning Task...........................................................................................229 4.3.4 Starting an eNodeB Commissioning Task.............................................................................................232 4.3.5 Monitoring eNodeB Commissioning.....................................................................................................235 4.3.6 Obtaining an Operator's Device Certificate Manually (with PKI)........................................................239 4.3.7 Confirming eNodeB Commissioning Completion................................................................................243 4.3.8 Checking the Running Status of the eNodeB on the M2000.................................................................244 eNodeB Commissioning Guide Contents Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. vii
  • 9. 4.3.9 Commissioning the Antenna System on the M2000.............................................................................248 4.3.10 Commissioning the Environment Monitoring Equipment on the M2000...........................................252 4.3.11 Setting the Maximum Output Power for RRUs or RFUs....................................................................255 4.3.12 Testing the Basic Services of the eNodeB...........................................................................................256 4.3.13 Setting an NE to the NORMAL Mode................................................................................................257 4.3.14 References to eNodeB Commissioning...............................................................................................258 4.4 Local Commissioning Using a USB Flash Drive in Unified Encryption Mode (with the SeGW)................267 4.4.1 Commissioning Procedure.....................................................................................................................267 4.4.2 Preparations...........................................................................................................................................270 4.4.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive...............................................................................................................................................................281 4.4.4 Uploading Data Files.............................................................................................................................285 4.4.5 Creating an eNodeB Commissioning Task...........................................................................................295 4.4.6 Starting an eNodeB Commissioning Task.............................................................................................297 4.4.7 Monitoring eNodeB Commissioning.....................................................................................................300 4.4.8 Confirming eNodeB Commissioning Completion................................................................................304 4.4.9 Checking the Running Status of the eNodeB on the M2000.................................................................305 4.4.10 Commissioning the Antenna System on the M2000...........................................................................308 4.4.11 Commissioning the Environment Monitoring Equipment on the M2000...........................................313 4.4.12 Setting the Maximum Output Power for RRUs or RFUs....................................................................316 4.4.13 Testing the Basic Services of the eNodeB...........................................................................................317 4.4.14 Setting an NE to the NORMAL Mode................................................................................................318 4.4.15 References to eNodeB Commissioning...............................................................................................319 4.5 Local Commissioning Using a USB Flash Drive in Differentiated Encryption Mode (with the SeGW) ..............................................................................................................................................................................328 4.5.1 Commissioning Procedure.....................................................................................................................328 4.5.2 Preparations...........................................................................................................................................331 4.5.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive...............................................................................................................................................................337 4.5.4 Uploading Data Files.............................................................................................................................341 4.5.5 Creating an eNodeB Commissioning Task...........................................................................................351 4.5.6 Starting an eNodeB Commissioning Task.............................................................................................353 4.5.7 Monitoring eNodeB Commissioning.....................................................................................................356 4.5.8 Obtaining an Operator's Device Certificate Manually (with PKI)........................................................360 4.5.9 Confirming eNodeB Commissioning Completion................................................................................365 4.5.10 Checking the Running Status of the eNodeB on the M2000...............................................................365 4.5.11 Commissioning the Antenna System on the M2000...........................................................................369 4.5.12 Commissioning the Environment Monitoring Equipment on the M2000...........................................373 4.5.13 Setting the Maximum Output Power for RRUs or RFUs....................................................................377 4.5.14 Testing the Basic Services of the eNodeB...........................................................................................378 4.5.15 Setting an NE to the NORMAL Mode................................................................................................379 4.5.16 References to eNodeB Commissioning...............................................................................................379 4.6 Local Commissioning on the LMT(with the SeGW).....................................................................................388 eNodeB Commissioning Guide Contents Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. viii
  • 10. 4.6.1 Commissioning Procedure.....................................................................................................................388 4.6.2 Preparations...........................................................................................................................................391 4.6.3 Downloading and Activating the eNodeB Software and Data Configuration File on the LMT...........398 4.6.4 Downloading the License for eNodeB Commissioning on the LMT....................................................401 4.6.5 Commissioning the Antenna System on the LMT................................................................................402 4.6.6 Commissioning the Environment Monitoring Equipment on the LMT................................................408 4.6.7 Setting the Maximum Output Power for RRUs or RFUs......................................................................410 4.6.8 Handling the eNodeB Alarms on the LMT...........................................................................................411 4.6.9 Checking the Operating Status of the eNodeB on the LMT..................................................................411 4.6.10 Testing the Basic Services of the eNodeB...........................................................................................412 4.6.11 Establishing an OML Between the M2000 and the eNodeB...............................................................413 4.6.12 Setting an NE to the NORMAL Mode................................................................................................415 5 Appendix.....................................................................................................................................417 5.1 eNodeB Binding Using a Bar Code Scanner..................................................................................................418 5.1.1 Printing a Bar Code on the M2000........................................................................................................418 5.1.2 Setting a Bar Code Scanner...................................................................................................................421 5.1.3 Binding the eNodeB by Scanning a Bar Code......................................................................................423 5.2 Triggering Monitoring Device Alarms...........................................................................................................424 5.2.1 Triggering PMU Alarms........................................................................................................................424 5.2.2 Triggering FMU Alarms........................................................................................................................430 5.2.3 Triggering TCU Alarms........................................................................................................................432 5.2.4 Triggering EMU Alarms.......................................................................................................................434 5.3 Checking the Status of Indicators...................................................................................................................436 5.4 Configuring the Default Configuration File...................................................................................................442 5.5 Encrypting Files in the USB Flash Drive.......................................................................................................442 5.6 Data Sheet for eNodeB Commissioning.........................................................................................................445 6 FAQ.............................................................................................................................................. 450 6.1 Failing to Identify the USB Flash Drive.........................................................................................................451 6.2 Failing to Read Files in the USB Flash Drive................................................................................................452 6.3 Failing to Activate the Software.....................................................................................................................453 6.4 Failing to Download the Software Based on the Default Configuration File.................................................453 eNodeB Commissioning Guide Contents Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. ix
  • 11. 1Changes in eNodeB Commissioning Guide This chapter describes the changes in eNodeB Commissioning Guide. 04 (2012-06-29) This is the fourth official release. Compared with issue 03 (2012-05-11) of V100R005C00, this issue includes the following new information. Topic Change Description 4.3.6 Obtaining an Operator's Device Certificate Manually (with PKI) Added the procedure for manually obtaining operators' certificates. Compared with issue 03 (2012-05-11) of V100R005C00, this issue includes the following changes. Topic Change Description l 3 eNodeB Commissioning Procedures (Without the SeGW) l 4 eNodeB Commissioning Procedures (with the SeGW) Modified the document organization by separating the commissioning procedures for scenarios with the SeGW and without the SeGW, and separating the commissioning procedures in unified encryption mode and in differentiated encryption for the scenario with 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. eNodeB Commissioning Guide 1 Changes in eNodeB Commissioning Guide Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 1
  • 12. Compared with issue 02 (2012-04-28) of V100R005C00, this issue includes the following new information. Topic Change Description l 5.4 Configuring the Default Configuration File l 6.4 Failing to Download the Software Based on the Default Configuration File Added sections on obtaining the common configuration file, configuring the default configuration file and failing to download the software based on the default configuration file. Compared with issue 02 (2012-04-28) of V100R005C00, this issue does not include any changes or delete any information. 02 (2012-04-28) This is the second official release. Compared with issue 01 (2012-03-30) of V100R005C00, this issue does not include any new information. Compared with issue 01 (2012-03-30) of V100R005C00, this issue includes the following changes. Topic Change Description l 4.1 Overview of eNodeB Automatic Discovery (with the SeGW) l 3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive l 5.3 Checking the Status of Indicators l Preparing a USB Flash Drive for Local Commissioning l 5.5 Encrypting Files in the USB Flash Drive l Preparing a USB Flash Drive for Local Commissioning 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 new information. eNodeB Commissioning Guide 1 Changes in eNodeB Commissioning Guide Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 2
  • 13. Topic Change Description 5.3 Checking the Status of Indicators Added the descriptions of ACT indicator on the main control board. l Preparing a USB Flash Drive for Local Commissioning l Preparing a USB Flash Drive for Local Commissioning Added the description of downloading the board software by using default configuration file. 3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive Added the figure of the USB port on UMPT and the method of downloading the LMT complete package by using a USB flash drive when the LMPT is used. Compared with draft B (2012-02-15) of V100R005C00, this issue does not include any changes. The following information in draft B (2012-02-15) of V100R005C00 is deleted from this issue. Topic Change Description l 3.2 PnP Remote Commissioning (Without the SeGW) l 4.2 PnP Remote Commissioning in Unified Encryption Mode (with the SeGW) l 3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW) l 4.4 Local Commissioning Using a USB Flash Drive in Unified Encryption Mode (with the SeGW) l 3.4 Local Commissioning on the LMT (Without the SeGW) l 4.6 Local Commissioning on the LMT (with the SeGW) Deleted the procedure for comparing the license and configuration data in the commissioning. Draft B (2012-02-15) This is draft B. Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following new information. Topic Change Description 6 FAQ Added "FAQ." eNodeB Commissioning Guide 1 Changes in eNodeB Commissioning Guide Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 3
  • 14. Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following changes. Topic Change Description l 3.2 PnP Remote Commissioning (Without the SeGW) l 4.2 PnP Remote Commissioning in Unified Encryption Mode (with the SeGW) l 3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW) l 4.4 Local Commissioning Using a USB Flash Drive in Unified Encryption Mode (with the SeGW) l 3.4 Local Commissioning on the LMT (Without the SeGW) l 4.6 Local Commissioning on the LMT (with the SeGW) Separated the description of remote commissioning on the M2000, local commissioning using a USB flash drive +remote commissioning on the M2000, and local commissioning on the LMT with the SeGW and those without the SeGW. 3.2.12 Setting an NE to the NORMAL Mode 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. Compared with issue 02 (2011-11-15) of V100R004C00, this issue includes the following new information. eNodeB Commissioning Guide 1 Changes in eNodeB Commissioning Guide Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 4
  • 15. Topic Change Description l 3.2 PnP Remote Commissioning (Without the SeGW) l 4.2 PnP Remote Commissioning in Unified Encryption Mode (with the SeGW) l 3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW) l 4.4 Local Commissioning Using a USB Flash Drive in Unified Encryption Mode (with the SeGW) l 3.4 Local Commissioning on the LMT (Without the SeGW) l 4.6 Local Commissioning on the LMT (with the SeGW) Added the procedure for comparing the license and configuration data in all commissioning scenarios. 3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive Added the procedure for activating the license file using the USB flash drive. Preparing a USB Flash Drive for Local Commissioning 3.2.12 Setting an NE to the NORMAL Mode Added the procedure for querying the eNodeB state. Compared with issue 02 (2011-11-15) of V100R004C00, this issue includes the following change. Topic Change Description 3.3.3 Downloading and Activating the Software, Data Configuration File, and License File Using a USB Flash Drive Changed the description of downloading the LMT complete package using the USB flash drive. The following information in issue 02 (2011-11-15) of V100R004C00 is deleted from this issue. eNodeB Commissioning Guide 1 Changes in eNodeB Commissioning Guide Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 5
  • 16. 2Commissioning Mode The eNodeB supports the following commissioning modes: PnP remote commissioning, local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT. Each commissioning mode can be applied to the scenario where the SeGW is deployed and the scenario where no SeGW is deployed. In the security scenario, PnP remote commissioning is classified into PnP remote commissioning in unified encryption mode and PnP remote commissioning in differentiated encryption mode; local commissioning using a USB flash drive is classified into local commissioning using a USB flash drive in unified encryption mode and local commissioning using a USB flash drive in differentiated encryption mode. You can select a commissioning mode based on site conditions. PnP remote commissioning is recommended. Prerequisites l 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 the interconnection data required for commissioning and can provide the basic functions of the EPC. l Requirements for data configuration are described as follows: Based on live network and eNodeB design requirements, the eNodeB configuration data are configured using the configuration management express (CME) or man-machine language (MML) command. For details, see eNodeB Initial Configuration Guide. Application Scenario Table 2-1 lists the application description for each commissioning scenario. eNodeB Commissioning Guide 2 Commissioning Mode Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 6
  • 17. Table 2-1 Application description for commissioning scenarios Commissioning Mode Application Scenario PnP remote commissioning (without the SeGW) l The operation and maintenance (OM) channel between the eNodeB and the M2000 works properly. l The eNodeB is relocated with permissible downtime greater than or equal to 1 hour. l No SeGW is deployed in the network. Local commissioning using a USB flash drive (without the SeGW) l No OM channel is established between the eNodeB and the M2000. l A USB flash drive is available. l The eNodeB is relocated with permissible downtime less than 1 hour. l No SeGW is deployed in the network. Local commissioning on the LMT (without the SeGW) l No OM channel is established between the eNodeB and the M2000. l The USB flash drive is unavailable or damaged, or eNodeB deployment using the USB flash drive fails. l The eNodeB is relocated with permissible downtime less than 1 hour. l No SeGW is deployed in the network. PnP remote commissioning in unified encryption mode (with the SeGW) l The operation and maintenance (OM) channel between the eNodeB and the M2000 works properly. l The eNodeB is relocated with permissible downtime greater than or equal to 1 hour. l The SeGW is deployed in the network. A public Dynamic Host Configuration Protocol (DHCP) server is available and it supports option43. l The eNodeB and the M2000 belong to different domains. The eNodeB communicates with the M2000 through the SeGW. PnP remote commissioning in differentiated encryption mode (with the SeGW) l The operation and maintenance (OM) channel between the eNodeB and the M2000 works properly. l The eNodeB is relocated with permissible downtime greater than or equal to 1 hour. l The SeGW is deployed in the network. l The eNodeB and the M2000 belong to the same domain. The eNodeB can communicate with the M2000 without the SeGW. eNodeB Commissioning Guide 2 Commissioning Mode Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 7
  • 18. Commissioning Mode Application Scenario Local commissioning using a USB flash drive in unified encryption mode (with the SeGW) l No OM channel is established between the eNodeB and the M2000. l A USB flash drive is available. l The eNodeB is relocated with permissible downtime less than 1 hour. l The SeGW is deployed in the network. A public Dynamic Host Configuration Protocol (DHCP) server is available and it supports option43. l The eNodeB and the M2000 belong to different domains. The eNodeB communicates with the M2000 through the SeGW. Local commissioning using a USB flash drive in differentiated encryption mode (with the SeGW) l No OM channel is established between the eNodeB and the M2000. l A USB flash drive is available. l The eNodeB is relocated with permissible downtime less than 1 hour. l The SeGW is deployed in the network. l The eNodeB and the M2000 belong to the same domain. The eNodeB can communicate with the M2000 without the SeGW. Local commissioning on the LMT (with the SeGW) l No OM channel is established between the eNodeB and the M2000. l The USB flash drive is unavailable or damaged, or eNodeB deployment using the USB flash drive fails. l The eNodeB is relocated with permissible downtime less than 1 hour. l The SeGW is deployed in the network. CAUTION If 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 reference documents before starting commissioning. For details about the required items, see the section on preparations for the commissioning mode used. eNodeB Commissioning Guide 2 Commissioning Mode Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 8
  • 19. 3eNodeB Commissioning Procedures (Without the SeGW) About This Chapter This chapter describes the following procedures when no security gateway (SeGW) is deployed: eNodeB automatic discovery, plug and play (PnP) remote commissioning, local commissioning using a Universal Serial Bus (USB) flash drive, and local commissioning on the LMT. 3.1 Overview of eNodeB Automatic Discovery (Without the SeGW) During eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM) channel with the M2000 using automatic discovery. This process does not require manual intervention. 3.2 PnP Remote Commissioning (Without the SeGW) To commission an eNodeB when no SeGW is deployed in the network, you need to enable the plug and play (PnP) function of the eNodeB on the M2000 client. After the faults (if any) occurred during automatic commissioning are rectified and the commissioning procedure is complete, the eNodeB can work properly. 3.3 Local Commissioning Using a USB Flash Drive (Without the SeGW) To perform local eNodeB commissioning using a USB flash drive when no SeGW is deployed, you need to upgrade the eNodeB 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 eNodeB commissioning 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 to upgrade the eNodeB software, download the configuration files, commission the antenna line devices (ALDs), and check the running status of the eNodeB on the LMT. Then, establish the operation and maintenance (O&M) channel between the eNodeB and the M2000 on the M2000 server. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 9
  • 20. 3.1 Overview of eNodeB Automatic Discovery (Without the SeGW) During eNodeB commissioning, the eNodeB sets up an operation and maintenance (OM) channel with the M2000 using automatic discovery. This process does not require manual intervention. Introduction to the Automatic Discovery Process Automatic discovery is a process during which the eNodeB is powered on and sets up an OM channel with the M2000 after the hardware is installed. If the eNodeB and the M2000 server are deployed on different network segments, you need to configure the router closest to the eNodeB on the path between the eNodeB and the M2000 server as a Dynamic Host Configuration Protocol (DHCP) relay. The IP address of the DHCP server for the M2000 is used as the DHCP relay address. NOTE If the M2000 server is deployed by using Server Load-Sharing (SLS), the previous IP address of the M2000 DHCP server refers to the IP address of the master M2000 server. eNodeB Automatic Discovery Process The 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 as follows: 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 provided by the M2000 to obtain the information, such as OM IP address, OM IP mask, IP address of the M2000, and IP mask of the M2000. 4. The eNodeB sets up an OM channel with the M2000 after receiving a response to the DHCP request from the M2000. 5. The eNodeB downloads and activates the eNodeB software and configuration files from the M2000. NOTE l When the M2000 server is deployed by using SLS, if you want to create an eNodeB on the master server, the IP address of the M2000 refers to the IP address of the master server; if if you want to create an 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 User Guide. l Log in to the M2000 client, choose Configuration > DHCP Configuration Management. The DHCP Configuration Management tab page is displayed. In the Server Information area on the DHCP Configuration Management tab page, check the DHCP message. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 10
  • 21. 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 as follows: 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 can directly communicate with each other. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 11
  • 22. Figure 3-3 Commissioning scenario with the SeGW 3.2 PnP Remote Commissioning (Without the SeGW) To commission an eNodeB when no SeGW is deployed in the network, you need to enable the plug and play (PnP) function of the eNodeB on the M2000 client. After the faults (if any) occurred during automatic commissioning are rectified and the commissioning procedure is complete, the eNodeB can work properly. 3.2.1 Commissioning Procedure This section describes how to perform plug and play (PnP) remote eNodeB commissioning when no security gateway (SeGW) is deployed. Figure 3-4 shows the procedure for PnP remote eNodeB commissioning when no SeGW is deployed. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 12
  • 23. Figure 3-4 Procedure for PnP remote eNodeB commissioning when no SeGW is deployed eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 13
  • 24. Table 3-1 Commissioning procedure St ep Operation Mandat ory/ Option al 1 Local and remote cooperative operations Prepare for remote eNodeB commissioning using the PnP, which involves obtaining eNodeB information and commissioning tools, and obtaining the eNodeB software and files required for automatic deployment. For details, see 3.2.2 Preparations. Mandato ry 2 Remote operations on the M2000 Create an eNodeB commissioning task on the M2000. For details, see 3.2.3 Creating an eNodeB Commissioning Task. Mandato ry 3 Start the eNodeB commissioning task on the M2000. For details, see 3.2.4 Starting an eNodeB Commissioning Task. Mandato ry 4 Monitor the eNodeB commissioning task on the M2000. For details, see 3.2.5 Monitoring eNodeB Commissioning. Mandato ry 5 After the eNodeB commissioning is complete, confirm the eNodeB commissioning task. For details, see 3.2.6 Confirming eNodeB Commissioning Completion. Mandato ry 6 Check the eNodeB commissioning report for the eNodeB operating status, and rectify the faults indicated in the eNodeB commissioning report if any. For details, see 3.2.7 Checking the Running Status of the eNodeB on the M2000. Mandato ry 7 Commission the antenna system on the M2000. For details, see 3.2.8 Commissioning the Antenna System on the M2000. Optional 8 Local and remote cooperative operations After the environment monitoring equipment is connected, commission the equipment so that it operates properly. For details, see 3.2.9 Commissioning the Environment Monitoring Equipment on the M2000. Optional 9 Remote operations on the M2000 Set the maximum transmit power of RRUs or RFUs on the M2000. RRU and RFU are short for remote radio unit and radio frequency unit, respectively. For details, see 3.2.10 Setting the Maximum Output Power for RRUs or RFUs. Optional 10 Local and remote cooperative operations Verify the basic services of the eNodeB. For details, see 3.2.11 Testing the Basic Services of the eNodeB. Optional eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 14
  • 25. St ep Operation Mandat ory/ Option al 11 Remote operations on the M2000 After eNodeB commissioning is complete and the eNodeB starts to provide services properly, set the eNodeB to the normal state on the M2000. For details, see 3.2.12 Setting an NE to the NORMAL Mode. Mandato ry NOTE After an eNodeB is deployed, local engineers can determine whether the eNodeB is working properly by observing the indicators on eNodeB boards. For details about the indicator descriptions and operations for rectifying possible faults, see 5.3 Checking the Status of Indicators. 3.2.2 Preparations To commission an eNodeB in PnP remote commissioning mode when the security gateway (SeGW) is not deployed, you need to collect related eNodeB information, obtain commissioning tools, and upload the required files. Context Figure 3-5 shows the procedure for preparing for PnP remote eNodeB commissioning when no SeGW is deployed. Figure 3-5 Procedure for preparing for PnP remote commissioning when the SeGW is not deployed eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 15
  • 26. Obtaining eNodeB Information and Commissioning Tools Before PnP remote eNodeB commissioning, you must obtain eNodeB information and commissioning 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. eNodeB ID Planned by the operator. eNodeB electronic serial number (ESN) NOTE The ESN information is optional and it is collected only in scenarios where the ESN is used to bind the eNodeB. ESN identifies an NE uniquely. During network deployment, the installation engineer reports the mapping relationship between the location of each site and the ESN to the staff at the maintenance center. The ESN is attached to the baseband unit (BBU) in the following two 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 in Figure 3-6. Record the ESN and the site information and then report them to the operation and maintenance (OM) personnel. l If the fan module on the BBU is attached with a label, the ESN is printed on the label of the fan module and the mounting ear of the BBU, as shown in Figure 3-7. You must remove the label to record 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) eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 16
  • 27. Figure 3-7 Location of the ESN (II) Step 2 Obtain the tools required for the remote commissioning on the M2000, as described in Table 3-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 subscriber server (HSS). ----End Preparing an eNodeB Deployment List You need to prepare an eNodeB deployment list before uploading relevant data files. Prerequisites l 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. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 17
  • 28. Option Description Deployment lists are exported from the CME If the CME has been deployed and you have initially configured the eNodeB on the CME, it is recommended that you use the CME to export the eNodeB deployment list. For detailed operations, see Exporting Auto Deployment Configuration Files in M2000 Help. Obtain and open the exported deployment list. Check whether the software version, cold patch, and hot patch are consistent with planned ones. If they are inconsistent, you need to change them as planned. In addition, you need to enter other relevant data. NOTE The deployment list must be exported from the CME V200R012C00 or later releases. Deployment lists are exported from the M2000 client If the CME has not been deployed, you can export the eNodeB deployment list from the eNodeB Auto Deployment window on the M2000 client. 1. Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. 2. Click . The Save dialog box is displayed. 3. Specify a save path and click OK. 4. Open the exported deployment list and enter or modify relevant data based on the planned data that is confirmed with the network planning engineers. NOTE l An eNodeB deployment list is in CSV format and its default name is eNodeB_Auto_Deployment_List.csv. You can enter or modify relevant data based on the planned data that is confirmed with the network planning engineers by referring to Parameters for the eNodeB Deployment List. l If there is a commissioning task in the commissioning task list, you can export the 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 export an empty deployment list and enter information based on the planned data. Before the deployment, check whether the planned target version is consistent with the target version 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 corresponding V100R003C00SPCXXX. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 18
  • 29. 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 out or modify the deployment list, ensure that all the characters you enter are valid. The base station commissioning may fail if you enter invalid characters such as comma (,) and quotation 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 required for procedures of eNodeB commissioning tasks are NE software versions, cold patches, hot patches, configuration data files, deployment lists, RET antenna software versions and configuration data files, RET antenna templates, and commissioning licenses. Prerequisites You have logged in to the M2000 client. Context You need to upload data files in the following scenarios: l Prepare for the commissioning. Upload the required data files to the M2000 server before commissioning as required. l The commissioning cannot be started because certain required data files are unavailable. The M2000 automatically checks whether data files required for customized procedures are available. If certain data files are unavailable, the commissioning cannot be started. Upload the required data files that are previously unavailable from the client to the M2000 server. The data files required for eNodeB commissioning need to be saved in specified paths on the M2000 server. For details, see Table 3-4. Table 3-4 File save paths File Type Save Path Software version /export/home/sysm/ftproot/eNodeB Type/Software/eNodeB Software Version/ Cold or hot patch /export/home/sysm/ftproot/eNodeB Type/Patch/eNodeB Patch Version/ Configurati on data file /export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/CfgData/ Deploymen t list /export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/ADList/ eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 19
  • 30. File Type Save Path RET antenna software version and configurati on data file /export/home/sysm/ftproot/OutSourcing/RETFile/ RET antenna template /export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/ RETTemplate/ Commissio ning license /export/home/sysm/ftproot/adn/AutoDeploymentData/eNodeB/ CommissionLicense/ Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 Click Prepare File&Data. The window for preparing files and data is displayed. Upload data files as required. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 20
  • 31. If you need to... Then... Upload NE software versions l Upload one by one One or multiple software versions corresponding to a certain NE type are 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. 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the software versions are uploaded. l Upload in batches One or multiple software versions corresponding to one or multiple NE types are 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 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or multiple files corresponding to multiple NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or multiple files and click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 21
  • 32. If you need to... Then... Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the software versions are uploaded. NOTE When uploading an NE software version, if the client displays a message indicating that the NE software version supports multiple types of base stations in the same mode, you need to upload the version only once for a base station. Then, the other types of base stations in the same mode can use the uploaded NE software version. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 22
  • 33. If you need to... Then... Upload cold patches l Upload one by one One or multiple cold patches corresponding to a certain NE type are 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. 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the cold patches are uploaded. l Upload in batches One or multiple cold patches corresponding to one or multiple NE types are 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 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or multiple files corresponding to multiple NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or multiple files and click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 23
  • 34. If you need to... Then... Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the cold patches are uploaded. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 24
  • 35. If you need to... Then... Upload hot patches l Upload one by one One or multiple hot patches corresponding to a certain NE type are uploaded 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. 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the hot patches are uploaded. l Upload in batches One or multiple hot patches corresponding to one or multiple NE types are uploaded 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. 2. Click in the lower left corner of the dialog box, 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or multiple files corresponding to multiple NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or multiple files and click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 25
  • 36. If you need to... Then... Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the hot patches are uploaded. Upload configurati on data files 1. On the NE Configuration Data tab page, choose Transfer > From OSS Client to OSS Server. The Upload NE Configuration Data dialog box is displayed. 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select the folder where the configuration data file that you want to upload is stored, click Select. The Upload NE Configuration Data dialog box is displayed. CAUTION The path for saving the eNodeB configuration data file to be uploaded must be .. eNodeBNameM2000.XML on the local PC. An eNodeBName folder contains only one XML file. To upload eNodeB configuration data files, you must select the eNodeBName folder where the files are stored. You can select multiple eNodeBName folders at a time. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. Upload deploymen t lists 1. On the Deployment List tab page, choose Transfer > From OSS Client to OSS Server. The Upload Deployment List dialog box is displayed. 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload and click Open to return to the Upload Deployment List dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the Upload Deployment List dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the deployment lists are uploaded. NOTE If the CME is not deployed, you can click Export Template to export an empty deployment template, fill out the template based on the planned data, and upload the template. The default names of the exported empty deployment list templates are the same. Therefore, you are advised to change the template names after filling out these templates. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 26
  • 37. If you need to... Then... Upload RET antenna software versions and configurati l Upload one by one One or multiple RET antenna software versions and configuration data files corresponding to a certain NE type are uploaded at a time. 1. On the RET 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the RET antenna software versions and configuration data files are uploaded. l Upload in batches One or multiple RET antenna software versions and configuration data files corresponding to one or multiple NE types are uploaded at a time. 1. On the RET 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 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 selecting files is displayed. Select files that you want to upload and click OK to return to the NE File Transfer dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Repeat the preceding two steps to select one or multiple files corresponding to multiple NE types. The selected files are displayed in the Source Path area. 5. In the Source Path area, select one or multiple files and click Add. The files to be uploaded are displayed in the lower part of the dialog box. 6. Click OK to close the NE File Transfer dialog box. The system starts uploading the data files. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 27
  • 38. If you need to... Then... on data files The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 7. When Progress is 100%, the RET antenna software versions and configuration data files are uploaded. Upload RET antenna templates 1. On the RET Template tab page, choose Transfer > From OSS Client to OSS Server. The Upload RET Template dialog box is displayed. 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload and click Open to return to the Upload RET Template dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the Upload RET Template dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File 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 RET antenna template, fill out the template based on the planned data, and upload the template. Upload commissio ning licenses 1. On the Commission License tab page, choose Transfer > From OSS Client to OSS Server. The Upload Commission License dialog box is displayed. 2. Select an NE type from the NE Type drop-down list. 3. In the Source Path area, click . The dialog box for selecting files is displayed. Select files that you want to upload and click Open to return to the Upload Commission License dialog box. The save path for the files to be uploaded to the server is displayed in the Destination Path area. You can only view the path. 4. Click OK to close the Upload Commission License dialog box. The system starts uploading the data files. The data file preparation window displays the following detailed information about the operations at the bottom of the window: Operation, Status, Source File Path, Destination File Path, and Progress. 5. When Progress is 100%, the commissioning licenses are uploaded. ----End eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 28
  • 39. 3.2.3 Creating an eNodeB Commissioning Task This section describes how to create an eNodeB commissioning task on the M2000 client after commissioning preparations are complete. Prerequisites l 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 If the eNodeB and the M2000 server are located on different network segments, you need to configure the router nearest to the eNodeB as the DHCP relay. – In an insecure scenario, you need to set the DHCP relay IP address on the router to the DHCP server IP address of the M2000. In a secure scenario, you need to set the DHCP relay IP address on the router to the common DHCP server IP address and on the security gateway, you need to set the IP address of the DHCP server to the DHCP server IP address of the M2000. – In situations where the M2000 is deployed in SLS mode, the preceding DHCP server IP address of the M2000 refers to the host IP address. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 Select deployment lists. 1. Click . The Import Deployment List dialog box is displayed. 2. In the Specify Deployment List area, select a deployment list. If you need to... Then... Import a deployment list from the server Select From Server and choose a deployment list from the drop- down list box. Import a deployment list from 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 the M2000 is deployed in SLS mode, NEs are managed by different servers. On the CME client, these NEs belong to different areas. Select the active or slave M2000 server that the NE belongs to based on the planned data. Configure the data as follows: eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 29
  • 40. 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. NOTE Onsite deployment engineers need to perform operations based on the areas that have been planned for 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: default connection mode. l SSL Connection: If this mode is selected, you also need to set an authentication mode. Authentication modes are Anonymous Authority and OSS Authentication NE, where Anonymous Authority is the default authentication mode. NOTE To enable automatic SSL connection during NE deployment, you need to set the authentication mode for NE in advance on the CME in addition to setting the connection mode between the M2000 and NEs 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 values and invalid base station configuration data. In addition, the information indicating whether the import succeeded or failed is displayed on the Operation Information tab page. l If the import is successful, the M2000 automatically creates a commissioning task for each eNodeB. The imported eNodeB deployment lists are displayed on the Deployment List tab page. l If the import fails, the causes of the failure are displayed on the Operation Information tab page. Step 4 (Optional) Modify data in the imported deployment lists as required. This step is mandatory when you need to modify the data in the imported deployment lists. NOTE You can check whether the parameters in eNodeB deployment lists can be modified by referring to Parameters for the eNodeB Deployment List. 1. Select a commissioning task from the commissioning task list, and double-click the cells containing parameter values to change the values. You can change ESNs by double-clicking the cells containing ESNs. Alternatively, you can perform the following operations to change the ESNs: a. Click in the ESN value cell. The Bind ESN dialog box is displayed. b. Select an ESN that is not bound, and click OK to return to the Deployment Parameter dialog box. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 30
  • 41. NOTE You can change the ESNs before OM links are established between base stations and the M2000. 2. The changed parameter values are displayed in the commissioning task window and highlighted in red. ----End 3.2.4 Starting an eNodeB Commissioning Task This section describes how to start an eNodeB commissioning task. After creating an eNodeB commissioning task, you can set commissioning procedures and start the task. Then, the M2000 automatically commissions the eNodeB. Prerequisites l You have logged in to the M2000 client. l eNodeB commissioning tasks have been started. Context A maximum of 500 commissioning tasks can be started at a time. In which, a maximum of 200 commissioning tasks can be being executed and the rest are waiting to be executed in the queue. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 On the Deployment List tab page, right-click one or multiple commissioning tasks and choose Start from the shortcut menu. The Task Settings dialog box is displayed. Step 3 Select steps in the Select column based on the actual plan. 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. Table 3-5 Description of commissioning process No. Procedur e Step Description 1 Auto Discovery Check OM channel When connection of the transport network is proper, the M2000 automatically sets up an OM channel to connect to the desired eNodeB based on the deployment list, and commissions and maintains the NodeB through this channel. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 31
  • 42. No. Procedur e Step Description Wait for manual operation After the OM channel is set up, the status of the commissioning task changes to Waiting for manual operation. Manually confirm the completion and proceed with the commissioning after the commissioning environment of the network is ready. 2 Auto Configura tion Download software The M2000 automatically checks whether the current eNodeB version is the same as the target software version given in the deployment list. If the versions are not the same, the M2000 automatically downloads software from the server to the eNodeB. Download configuration The M2000 downloads the desired configuration file from the server to the eNodeB based on the target version information. Activate Activate the eNodeB configuration data (takes effect after next reset) and then activate the software (automatic reset). 3 Auto Planning Auto Planning Only the BTS3202E is supported in eNodeB auto deployment. 4 Upload commissi oning license Distribute commissioning license When some eNodeB functions are restricted because the eNodeB uses the default license upon delivery, you need to install a commissioning license. The commissioning license has time restriction. You need to replace the commissioning license with the commercial one as soon as possible after the eNodeB commissioning is complete. 5 Commissi on RET Upgrade RET software version The target RET antenna software version is provided by antenna line device (ALD) suppliers and 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, you do not need to commission the RET antennas. l When antennas are managed by the management system of a third party, you do not need to commission RET antennas. Upgrade RET configuration The RET antenna configuration file is provided by ALD suppliers and saved on the local PC. RET antenna configuration data may vary according to RET antenna types and suppliers. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 32
  • 43. No. Procedur e Step Description Tune RET Check whether RET antennas are commissioned correctly during the commissioning. 6 Test and monitor Test installation & deployment quality Services carried on the RF module will be interrupted during operation. If an RF module is shared by base stations of different RATs, services of the other RAT will also be interrupted. The check may take several minutes. The project quality check involves the VSWR, offline intermodulation interference, and crossed pair. Monitor cell service status Check whether any active cells exist under the eNodeB. You can monitor alarms of the eNodeB on the M2000 during software commissioning to locate and handle exceptions in time. 7 Perform NHC Perform NHC You can perform health check to learn the eNodeB operating status. 8 Wait for confirmati on Wait for confirmation After service verification is complete, the commissioning task is in the Waiting for Confirmation state. You need to manually confirm that the commissioning is complete. 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 proceed with subsequent operations. l If only some configured RF modules are usable, the system sets a timer (2.5 minutes in length and a maximum of 5 times) to wait until all RF modules are usable. After all RF modules are usable, the system issues project quality check commands to proceed with subsequent operations. If some RF modules 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 are available. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 33
  • 44. If... Then... Not all the required data files are available 1. The Data Preparation Check dialog box is displayed, showing check results 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 required data files are available The M2000 starts commissioning. The selected commissioning tasks enter the Running state. NOTE If all the required data files are available, the Data Preparation Check dialog box is not displayed. ----End 3.2.5 Monitoring eNodeB Commissioning This section describes how to monitor eNodeB commissioning on the M2000 to learn about commissioning 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 the M2000 to learn about process of the tasks. Prerequisites l You have logged in to the M2000 client. l eNodeB commissioning tasks have been started. Context l 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 not restart NE upgrades but proceeds until the related NE upgrade task is complete. When the system displays The NE is performing the following task: ******. Please try later. in Description for a commissioning task, the NE upgrade task is running. If you want to perform automatic deployment again, wait until the NE upgrade task is complete. You can choose Software > NE Upgrade Task Management > NE Upgrade Task to query the NE upgrade task. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 34
  • 45. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 View the status and progress of commissioning tasks in the commissioning task list. TIP You can quickly view the status of commissioning tasks by using either of the following methods: l In the commissioning task list, the status of the tasks is displayed in Status, the current procedures are displayed in Current Phase, and details about each procedure are displayed in 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 of steps for commissioning procedures. The displayed information includes the execution status, description, start time and end time of each commissioning substep. Step 3 (Optional) Click . The Statistics dialog box is displayed, showing the number of commissioning tasks in each status. Click OK to close the dialog box. ----End Handling eNodeB Alarms This section describes how to handle eNodeB alarms. After eNodeB software is automatically upgraded, you can use the M2000 to view alarms on eNodeBs. All alarms related to eNodeBs are categorized by object to help you query required alarms. Prerequisites l 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. Context The alarms are categorized into E1/T1 port alarms, transmission path alarms, antenna alarms, software and configuration alarms, board alarms, cell alarms, external alarms, and other alarms by object type. Other alarms refer to the alarms that cannot be categorized on the basis of specific objects. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you want to handle alarms. Right-click the tasks, and then choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 35
  • 46. In the displayed window, you can view alarms on eNodeBs by monitored object. For details about the alarm monitoring window, see Interface Description: eNodeB Commissioning Window. 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 Diagnosis This section describes how to perform antenna fault diagnosis. The M2000 provides automatic fault diagnosis to antennas. When errors occur during eNodeB commissioning, you can use the automatic fault diagnosis function provided by the M2000 to check whether the eNodeB that is being commissioned is faulty. Then, you can take corresponding measures to rectify the faults based on the diagnosis results. Prerequisites l 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 CAUTION eNodeB services are interrupted upon antenna fault diagnosis. Therefore, you need to perform the 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 involves the VSWR test, offline intermodulation interference test, and crossed pair test. After one fault diagnosis operation is performed, the M2000 creates a fault diagnosis task and displays the diagnosis progress. After the fault diagnosis is complete, you can obtain the fault diagnosis report. If you delete a fault diagnosis task, the corresponding diagnosis report is deleted accordingly. If you restart the M2000 server, all fault diagnosis tasks and reports are deleted. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 36
  • 47. Step 2 In the commissioning task list, select one or multiple commissioning tasks for which you want to handle alarms. Right-click the tasks, and then choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. 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 or alarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settings dialog box is displayed. 2. Select an eNodeB in the Select NE area, select a diagnosis type in the Select diagnose type area, type diagnosis parameters in the Type diagnosis parameters area, and then click OK. The dialog box for confirming the diagnosis is displayed. 3. Click Yes. The system starts the fault diagnosis. During the fault diagnosis, a diagnosis task is added to the diagnosis task list. NOTE Fault diagnosis may take a long time when there are a large number of detection services executed by 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 task list, and choose Diagnose Report from the shortcut menu to view diagnosis results. ----End Managing eNodeB Commissioning Tasks This section describes how to manage eNodeB commissioning tasks. After creating or starting eNodeB commissioning tasks, you can delete, restart, pause, resume, or cancel the selected tasks. Prerequisites l You have logged in to the M2000 client. l eNodeB commissioning tasks have been created or started. Context For details about operations on commissioning tasks, see Table 3-6. Table 3-6 Operations on commissioning tasks Opera tion Description Delete You can perform this operation on commissioning tasks in any state. Restart You can perform this operation on commissioning tasks in the Running, Abnormal, Paused, or Waiting for Confirmation state. Pause You can perform this operation on commissioning tasks in the Running state. Resum e You can perform this operation on commissioning tasks in the Paused state. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 37
  • 48. Opera tion Description Cancel You can perform this operation on commissioning tasks in the Running, Abnormal, or Paused state. Procedure Step 1 Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the Configuration > Auto Deployment > eNodeB Auto Deployment client. The eNodeB Auto Deployment window is displayed. Step 2 On the Deployment List tab page, select one or multiple commissioning tasks and perform operations as required. If you need to... Then... Restart Right-click the tasks and choose Restart from the shortcut menu. The tasks return to the Running state. Pause Right-click the tasks and choose Pause from the shortcut menu. The tasks are in the Paused state. Resume Right-click the tasks and choose Resume from the shortcut menu. The tasks proceed from where they are paused. Cancel Right-click the tasks and choose Cancel from the shortcut menu. The tasks return to the Wait for Start state. Delete 1. Right-click the tasks and choose Delete from the shortcut menu. The Confirm dialog box is displayed. 2. Click OK. The system starts deleting the tasks. ----End 3.2.6 Confirming eNodeB Commissioning Completion When the status of an eNodeB commissioning task changes to Waiting for Confirmation, you need to confirm that the eNodeB commissioning is complete. Prerequisites l The eNodeB is properly connected to the M2000. l The status of the eNodeB commissioning task is Waiting for Confirmation. Procedure Step 1 On the M2000 client, choose Configuration > Auto Deployment > eNodeB Auto Deployment. The eNodeB Auto Deployment tag page is displayed. eNodeB Commissioning Guide 3 eNodeB Commissioning Procedures (Without the SeGW) Issue 04 (2012-06-29) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 38