FDD LTE ENodeB (V2.10) Commissioning Configuration Guide - R1.0

FDD LTE eNodeB (V2.
10)
Commissioning Configuration Guide
FDD LTE eNodeB (V2.10) Commissioning Configuration Guide Internal Use Only▲
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2013 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone’s access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATION’s
products and technologies.
ZTE CORPORATION
Address: No. 55
Hi-tech Road South
Shenzhen
P. R. China
518057
Website: http://dms.zte.com.cn (Technical Support)
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. I

Revision History
Product Version Document Version Serial Number Reason for Revision

V2.10.050 R1.0 - First published
Author
Date Document Version Prepared by Reviewed by Approved by

2011-12-14 R1.0 Gao Yuxin
Xiang Yijie Ma Jun -
Hou Kun
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. II

Intended audience: FDD LTE eNodeB Technical Support Personnel
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ Knowledge and skills Reference material
ZXSDR B8200 L200 LTE eBBU System
1
Description Guide
ZXSDR B8200 L200 LTE eBBU Hardware
2
Description Guide
ZXSDR B8200 L200 LTE eBBU Hardware
3
Installation Guide
ZXSDR R8882 L268 (V2.00) LTE eRRU User
4
Manual
ZXSDR B8200 L200 LTE eBBU Maintenance
5
Guide
FDD LTE eNodeB Product Skill Certification NetNumen M31 (LTE) NE Management
6 Level II System eNodeB Radio Parameter Reference
(VOL I)
NetNumen M31 (LTE) NE Management
7 System eNodeB Radio Parameter Reference
(VOL II)
8 System eNodeB Ground Parameter
Reference
9 System eNodeB Alarm and Notification
Reference
Follow-up document: After reading this document, you may need the following information.
SEQ Reference material Information
1 - -
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. III
TABLE OF CONTENTS
1 Overview ......................................................................................................... 1
1.1 About This Guide .............................................................................................. 1
1.2 Product Version ................................................................................................ 1
1.3 Terminologies ................................................................................................... 1
2 Introduction to an eNodeB ............................................................................. 2

2.1 Typical FDD LTE Networking Modes ................................................................ 2
2.2 Key Components of an eNodeB........................................................................ 5
2.2.1 Key Components of an eBBU ........................................................................... 6
2.2.2 Key Components of an eRRU ........................................................................... 7
2.3 Common Ports of an eNodeB ........................................................................... 8
2.3.1 Common Ports of an eBBU............................................................................... 8
2.3.2 Common Ports of an eRRU .............................................................................. 9
2.4 Typical Physical Configuration of an eNodeB ................................................. 10
2.5 Process for Commissioning and Debugging an eNodeB ................................. 13
3 Preparing for Commissioning and Debugging an eNodeB ....................... 15

3.1 Reading the Contract Information ................................................................... 15
3.2 Inquiring the Shipment Information ................................................................. 16
3.3 Collecting the Frontline Information ................................................................ 16
3.4 Applying for a Software Version ...................................................................... 16
3.5 Checking the Labor for Readiness .................................................................. 17
3.6 Preparing the Debugging Tools ...................................................................... 17
3.7 Collecting the Site Information ........................................................................ 18
3.8 Generating the Configuration File ................................................................... 27
4 Powering on an eNodeB............................................................................... 29
4.1 Powering on an eBBU .................................................................................... 30
4.2 Powering on an eRRU .................................................................................... 31
5 Commissioning an eNodeB from the Foreground ..................................... 32

5.1 Querying the Version from the Foreground ..................................................... 32
5.2 (Optional) Upgrading the eNodeB Version ...................................................... 36
5.3 Importing the Configuration File from the Foreground ..................................... 37
5.4 Checking Transmission Parameters ............................................................... 40
5.4.1 Checking GE Parameters ............................................................................... 41
5.4.2 Checking Global Port Parameters................................................................... 42
5.4.3 Checking IP Parameters ................................................................................. 45
5.4.4 Checking Static Route Parameters ................................................................. 48
5.4.5 Checking OMC Parameters ............................................................................ 52
6 Configuring an eNodeB on the Background............................................... 56

6.1 Importing the Configuration File from the EMS ............................................... 56
6.2 Configuring Radio Parameters for an eNodeB ................................................ 68
6.3 Configuring Clock Parameters ........................................................................ 68
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. IV

6.3.1 Configuring SNTP and Clock Source Parameters ........................................... 68

6.3.2 Configuring the IP Clock and PTP Logical Port ............................................... 83
6.4 Configuring a Dry Contact............................................................................... 90
6.5 Configuring an Electrical Antenna ................................................................... 93
6.6 Performing Data Synchronization ................................................................... 97
7 Troubleshooting eNodeB Alarms .............................................................. 100
8 Verifying Basic eNodeB Services .............................................................. 100

8.1 Performing a UE Attachment Test (Connection and Release) ...................... 100
8.2 Performing a Ping Test (Uplink and Downlink) .............................................. 101
8.3 Performing a UDP Traffic Generation Test (Uplink and Downlink) ................ 103
8.4 Performing an FTP Test (Uplink and Downlink) ............................................ 105
8.5 (Optional) Performing an IEEE1588 Clock Test ............................................ 106
8.5.1 Detecting the Status of an IEEE1588 Clock .................................................. 106
8.5.2 1+1 Active/Standby Switchover of an IEEE1588 Clock Server...................... 111
8.6 (Optional) Performing a Dry Contact Test ..................................................... 113
AppA How to Use the BCT ................................................................................... 115
AppB How to Upgrade the eNodeB Version........................................................ 125

B.1 Upgrading V2.00.050* to V2.00.060eP01 ..................................................... 125
B.1.1 Interim Version Upgrade ............................................................................... 125
B.1.2 Upgrading the BOOT Version of the CC Board from V2.00.050* to
V2.00.060eP01 ............................................................................................ 134
B.2 Upgrading V2.00.060eP01 to V2.10.050e..................................................... 142
AppC How to Contra-Construct the Configuration Data .................................... 150
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. V

FIGURES
Figure 2-1 Typical FDD LTE Networking Mode .................................................................... 3

Figure 2-2 Appearance of a ZXSDR B8200 L200 ................................................................. 6
Figure 2-3 Appearance of a ZXSDR R8882 L268 ................................................................ 7
Figure 2-4 Common Ports of a ZXSDR B8200 L200 ............................................................ 8
Figure 2-5 Common Ports of a ZXSDR R8882 L268 ............................................................ 9
Figure 2-6 Typical Physical Configuration of a ZXSDR B8200 L200 .................................. 11
Figure 2-7 Typical Physical Configuration of a ZXSDR R8882 L268 .................................. 11
Figure 2-8 Board Layout of a ZXSDR B8200 L200 ............................................................. 12
Figure 2-9 Process for Commissioning and Debugging an eNodeB ................................... 13
Figure 4-1 eBBU Power Supply.......................................................................................... 29
Figure 4-2 Power Switch on the PM3 Board ....................................................................... 29
Figure 4-3 eRRU Power Supply ......................................................................................... 30
Figure 5-1 Telneting the eNodeB through a Laptop ............................................................ 33
Figure 5-2 Synchronization Entire Table Configuration Menu Item ............................... 38
Figure 5-3 Open Dialog Box .............................................................................................. 38
Figure 5-4 Choosing the Configuration File ........................................................................ 39
Figure 5-5 Syncing the Configuration File with the eNodeB................................................ 39
Figure 5-6 Success Message Box ...................................................................................... 40
Figure 5-7 Transmission Resource Layers ......................................................................... 40
Figure 5-8 GE Parameter Pane ......................................................................................... 41
Figure 5-9 Global Port Parameter Pane ........................................................................... 43
Figure 5-10 Configuration Example of a Global Port .......................................................... 44
Figure 5-11 IP Parameter Pane ......................................................................................... 45
Figure 5-12 Modify Menu Item........................................................................................... 46
Figure 5-13 Basic Information Tab Page ......................................................................... 47
Figure 5-14 Configuration Example of an IP Context .......................................................... 48
Figure 5-15 Static Route Parameter Pane........................................................................ 49
Figure 5-18 OMC Parameter Pane .................................................................................... 53
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. VI

Figure 6-1 Start NE Management Menu Item ................................................................... 57

Figure 6-2 Configuration Management Menu Item .......................................................... 58
Figure 6-3 Subnetwork Dialog Box ................................................................................... 59
Figure 6-4 Creating an FDD LTE Subnetwork .................................................................... 59
Figure 6-5 Adding a Base Station....................................................................................... 60
Figure 6-6 Base Station Dialog Box .................................................................................. 61
Figure 6-7 General Parameters Tab Page ........................................................................ 62
Figure 6-8 Newly Created Base Station ............................................................................. 63
Figure 6-9 Apply Mutex Right Menu Item ......................................................................... 63
Figure 6-10 Confirm Message Box .................................................................................... 64
Figure 6-11 Base Station Configuration Wizard (SDR) Menu Item ................................. 64
Figure 6-12 Configured by Standard Template Option.................................................... 65
Figure 6-13 Configuration Wizard (Step Two: Choose Data Files) Dialog Box .............. 65
Figure 6-14 Selecting the Configuration File....................................................................... 66
Figure 6-15 Selected Configuration File ............................................................................. 66
Figure 6-16 Confirm Message Box .................................................................................... 67
Figure 6-17 Success Switch Message Box....................................................................... 67
Figure 6-18 Successful Imported Base Station................................................................... 67
Figure 6-19 SNTP Configuration Pane ............................................................................. 69
Figure 6-20 SNTP Configuration Dialog Box .................................................................... 70
Figure 6-21 SNTP Configuration Completion ..................................................................... 71
Figure 6-22 Clock Parameter Configuration Pane .......................................................... 72
Figure 6-23 Clock Parameter Configuration Dialog Box.................................................. 72
Figure 6-24 Clock Source Configuration Completion .......................................................... 74
Figure 6-25 Clock Source Priority Pane .......................................................................... 75
Figure 6-26 Clock Source Priority Dialog Box .................................................................. 76
Figure 6-27 Only One IEEE1588 Clock Source Configured................................................ 78
Figure 6-28 Clock Source 1 (IEEE1588) ............................................................................ 79
Figure 6-29 Clock Source 2 (GPS) ..................................................................................... 79
Figure 6-30 Only GPS Clock Source .................................................................................. 80
Figure 6-31 GPS Cascading Mode ..................................................................................... 81
Figure 6-32 Only IEEE1588 Clock Source Priority Configured ........................................... 81
Figure 6-33 Two Clock Source Priorities Configured .......................................................... 82
Figure 6-34 Only GPS Clock Source Priority Configured .................................................... 82
Figure 6-35 Cascading GPS Clock Source Priority Configured .......................................... 83
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. VII
Figure 6-36 IEEE1588 Clock Networking Mode ................................................................. 84

Figure 6-37 IP Clock Pane ................................................................................................ 85
Figure 6-38 IP Clock Dialog Box........................................................................................ 86
Figure 6-39 IP Clock Configuration Completion .................................................................. 87
Figure 6-40 PTP Logical Port Pane .................................................................................. 88
Figure 6-41 PTP Logical Port Dialog Box ......................................................................... 88
Figure 6-42 PTP Logical Port Configuration (eNodeB 1) .................................................... 90
Figure 6-43 PTP Logical Port Configuration (eNodeB 2) .................................................... 90
Figure 6-44 Dry Contact Pane .......................................................................................... 91
Figure 6-45 Dry Contact Dialog Box.................................................................................. 92
Figure 6-46 Dry Contact Configuration Completion ............................................................ 93
Figure 6-47 Aisg Equipment Management Menu Item..................................................... 94
Figure 6-48 Parallel Scan Menu Item ................................................................................ 95
Figure 6-49 Adding the Results .......................................................................................... 95
Figure 6-50 Create AISG Device Dialog Box..................................................................... 96
Figure 6-51 Query AISG Device Menu Item ...................................................................... 96
Figure 6-52 Synchronize All Tables Menu Item ............................................................... 98
Figure 6-53 Radio Mode Selection Dialog Box ................................................................. 99
Figure 6-54 Data Synchronization Completion ................................................................... 99
Figure 8-1 BCT Startup .................................................................................................... 115
Figure 8-2 Files Encryption Checkbox ........................................................................... 117
Figure 8-3 Choosing the Network Planning Worksheet .................................................... 118
Figure 8-4 Checking the File for Validity ........................................................................... 119
Figure 8-5 Error Info Pane .............................................................................................. 120
Figure 8-6 Choosing a Director for Outputting the Configuration File ............................... 121
Figure 8-7 Generating the Configuration File.................................................................... 121
Figure 8-8 File Generation Succeeded ............................................................................. 122
Figure 8-9 File Generation Failed ..................................................................................... 123
Figure 8-10 Batch process tips Dialog Box .................................................................... 123
Figure 8-11 Customized Configuration File ...................................................................... 124
Figure 8-12 Connecting your Laptop to the eNodeB......................................................... 126
Figure 8-13 LMT-OMS Login Dialog Box ........................................................................ 126
Figure 8-14 Querying the Running Version of the eNodeB ............................................... 127
Figure 8-15 Download Menu Item ................................................................................... 128
Figure 8-16 Selecting Two Interim Software Version Packages to Be Downloaded.......... 129
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. VIII
Figure 8-17 Downloading the Software Version Packages ............................................... 130

Figure 8-18 Download Result Dialog Box ....................................................................... 130
Figure 8-19 Version Management Pane ......................................................................... 131
Figure 8-20 Adding the Configuration Templates ............................................................. 131
Figure 8-21 Activation Success Message Box.................................................................. 132
Figure 8-22 Verifying the Upgrade to the Interim Version ................................................. 133
Figure 8-23 Downloading the BOOT Version ................................................................... 135
Figure 8-24 Successful Downloading Results .................................................................. 136
Figure 8-25 Activating the Interim Firmware Version ........................................................ 137
Figure 8-26 Activate Dialog Box ...................................................................................... 137
Figure 8-27 Confirm Button ............................................................................................. 138
Figure 8-28 Confirmation Message Box ........................................................................... 138
Figure 8-29 eNodeB Communication Progress ................................................................ 138
Figure 8-30 Query Activation Result Dialog Box............................................................ 139
Figure 8-31 eNodeB Restart Confirmation........................................................................ 139
Figure 8-32 eNodeB Restart Success .............................................................................. 139
Figure 8-33 Reactivating the BOOT version and Restarting the eNodeB ......................... 140
Figure 8-34 Downloading a Single or Dual Control Software Package ............................. 143
Figure 8-35 Activating Two Software Version Packages in V2.10.050e............................ 144
Figure 8-36 Selecting the Configuration Files in V2.10.050e ............................................ 145
Figure 8-37 Verifying the Upgrade from V2.0 to V2.1 ....................................................... 146
Figure 8-38 Downloading a Single or Dual Control Software Package ............................. 147
Figure 8-39 Activating the Firmware Version Package in V2.1 ......................................... 147
Figure 8-40 Activating the BOOT versions of the CC, BPL, and TRM Boards .................. 148
Figure 8-41 Base Station Configuration Wizard (SDR) Menu Item ............................... 151
Figure 8-42 Configured by Base Station data Checkbox .............................................. 151
Figure 8-43 Parallelly Online Upload Data Result Dialog Box ....................................... 152
Figure 8-44 Switch to Master Checkbox ......................................................................... 153
Figure 8-45 Command executed successfully Syntax .................................................. 154
TABLES
Table 1-1 Product Version.................................................................................................... 1

Table 1-2 Terminologies....................................................................................................... 1
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. IX

Table 2-1 Basic Knowledge about an eNodeB ..................................................................... 2

Table 2-2 Functions and Connections of FDD LTE Network Devices ................................... 3
Table 2-3 Common Models of an eBBU and an eRRU ......................................................... 5
Table 2-4 Components and Functions of a ZXSDR B8200 L200 .......................................... 6
Table 2-5 Components and Functions of a ZXSDR R8882 L268.......................................... 7
Table 2-6 Common Ports of a ZXSDR B8200 L200 ............................................................. 8
Table 2-7 Common Ports of a ZXSDR R8882 L268 ........................................................... 10
Table 2-8 Physical Configuration Principles of a ZXSDR B8200 L200................................ 12
Table 2-9 Estimated Time Required for Commissioning and Debugging an eNodeB ......... 14
Table 3-1 Tools Required for Commissioning and Debugging an eNodeB ......................... 17
Table 3-2 Basic eNodeB Parameters ................................................................................. 19
Table 3-3 Basic eNodeB Information .................................................................................. 19
Table 3-4 Global Port Parameters of an eNodeB ............................................................... 20
Table 3-5 Global Port Information of an eNodeB ................................................................ 20
Table 3-6 IP Parameters of an eNodeB.............................................................................. 20
Table 3-7 IP Information of an eNodeB .............................................................................. 21
Table 3-8 IP Parameters of the OMC ................................................................................. 21
Table 3-9 IP Information of the OMC .................................................................................. 22
Table 3-10 Clock Parameters of an eNodeB ...................................................................... 22
Table 3-11 Clock Information of an eNodeB ....................................................................... 23
Table 3-12 Static Route Parameters .................................................................................. 23
Table 3-13 Static Route Information ................................................................................... 23
Table 3-14 SCTP Parameters of the S1 Interface .............................................................. 24
Table 3-15 SCTP Information of the S1 Interface ............................................................... 24
Table 3-16 Cell Parameters ............................................................................................... 25
Table 3-17 Cell Information ................................................................................................ 25
Table 3-18 Parameters to Be Modified in the Network Planning Worksheet ....................... 28
Table 5-1 Foreground Commissioning Tasks ..................................................................... 32
Table 5-2 IP Parameters .................................................................................................... 47
Table 5-3 Static Route Parameters .................................................................................... 51
Table 5-4 OMC Parameters ............................................................................................... 55
Table 6-1 Base Station Parameters ................................................................................... 61
Table 6-2 SNTP Parameters .............................................................................................. 70
Table 6-3 Clock Source Parameters................................................................................... 73
Table 6-4 Clock Source Priority Parameters....................................................................... 76
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. X

Table 6-5 Clock Source Priority Parameters....................................................................... 78

Table 6-6 PTP Port Configuration Example ........................................................................ 84
Table 6-7 IP Clock Parameters .......................................................................................... 86
Table 6-8 PTP Logical Port Parameters ............................................................................. 89
Table 6-9 Dry Contact Parameters ..................................................................................... 92
Table 8-1 UE Attachment (Connection and Release) ....................................................... 100
Table 8-2 Ping Test (Uplink and Downlink)....................................................................... 101
Table 8-3 UDP Traffic Generation Test (Uplink and Downlink) ......................................... 103
Table 8-4 FTP Test (Uplink and Downlink) ....................................................................... 105
Table 8-5 1+1 Active/Standby Switchover (Active Clock Source Failure) of an IEEE1588
Clock Server ....................................................................................................................... 111
Table 8-6 1+1 Active/Standby Switchover (Modifying or Deleting the Priority of a PTP Port)
of an IEEE1588 Server ....................................................................................................... 112
Table 8-7 Dry Contact Test .............................................................................................. 113
Table 8-8 BCT Parameters .............................................................................................. 117
Table 8-9 Field Descriptions in the Process Info Pane .................................................... 122
Table 8-10 Single Control Version Packages ................................................................... 148
Table 8-11 Dual Control Version Packages ...................................................................... 149
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. XI

1 Overview
1.1 About This Guide

This guide describes how to make preparations for, commission, and debug an FDD LTE
eNodeB. When deploying an FDD LTE eNodeB, either on-site or in-house FDD LTE
technical support engineers can use this guide as your reference.
1.2 Product Version

Table 1-1 shows the product version that is applicable to this guide.
Table 1-1 Product Version

Product Name Product Version
FDD LTE eNodeB V2.10.050e
1.3 Terminologies
Table 1-2 summarizes the terminologies that are used in this guide.
Table 1-2 Terminologies
Terminology Full Name

eNodeB/eNB evolved Node B
EPC Evolved Packet Core Network
MME Mobility Management Entity
SGW Serving GateWay
UE User Equipment
eBBU evolved Base Band Unit
eRRU evolved Remote Radio Unit
Common Public Radio Interface
This CPRI standard has been developed and formulated by the
telecom industry’s major contributors including Ericsson, NEC, Nortel,
CPRI and Siemens. Through the CPRI, a single eBBU can be
interconnected to multiple eRRUs, which can help mobile operators
save spaces, lower costs, and improve networking efficiency.
Additionally, optical cables are employed for this interconnection,
thereby dramatically reducing electrical power consumption.
LMT Local Maintenance Terminal
ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 1

SCTP Stream Control Transmission Protocol

IEEE 1588 Precision Time Protocol (PTP), officially entitled “Precision
Clock Synchronization Protocol”, is designed to synchronize clocks
that are dispersed in different geographical areas throughout a packet
IEEE 1588 network such as Ethernet. This protocol can help achieve clock
accuracy between one master clock and multiple subordinate clocks
in a real-time manner, thereby making it suitable for measurement
and control systems.
Global Navigation Satellite System
GNSS Presently, GNSS has incorporated 100-plus available satellites
including GPS in USA, GLONASS in Russia, Compass in China, and
Galileo in Europe.
2 Introduction to an eNodeB
Before starting your commissioning work, you should become very familiar with the basic
knowledge about an eNodeB, as summarized in Table 2-1.
Table 2-1 Basic Knowledge about an eNodeB

Section Description
2.1 Typical FDD LTE This section describes how to connect an eNodeB to
Networking Modes its neighboring network devices.
2.2 Key Components of an This section presents the key components of an
eNodeB eNodeB.
This section introduces the common interfaces of an
2.3 Common Ports of an
eNodeB, such as POWER, CPRI, DEBUG, and
eNodeB
ANTENNA.
2.4 Typical Physical This section demonstrates the typical physical layout
Configuration of an eNodeB and configuration principles of an eNodeB.
2.1 Typical FDD LTE Networking Modes

In an FDD LTE network, the eNodeBs can be connected to the EPC, EMS, IEEE 1588
clock server, and other network devices, as shown in Figure 2-1.

Figure 2-1 Typical FDD LTE Networking Mode
Table 2-2 summarizes the functions and connections of each individual device in an FDD
LTE network.
Table 2-2 Functions and Connections of FDD LTE Network Devices
Network
Description
Device
An eBBU is designed to serve as a baseband unit. It can be connected to
one or more eRRUs through optical fibers, which a complete eNodeB.
eBBU
An eBBU is connected to the EPC through the S1 interface; an eBBU is
connected to another eBBU through the X2 interface.
An eBBU and multiple eRRUs can comprise a complete eNodeB, which
can provide the following functions:
eRRU
 Radio transmission in coverage areas
 Radio channel control

The EPC can provide FDD LTE users with the following functions:
 High-speed mobile broadband service
 Session management
 Mobility management
EPC
 Bearer management
 Handover management
The MME and SGW can act as the control plane of the EPC, whereas
the SGW can act as the user plane of the EPC.
The User Equipment (UE) can exchange data with a network device
UE
through the Uu interface.
The Element Management System (EMS) is designed to manage or
control network elements in a concentrated way. It can offer the following
functions:
 Topology management
 Log management
 Alarm management
EMS
 Performance management
 Command line management
 Maintenance tool
The EMS can work in client/server mode. Specifically, the client can run
on a PC workstation; whereas the server can run on the SUN Solaris or
IBM AIX operating system.
IEEE
This server is designed for time synchronization with an eNodeB in
1588
submicrosecond. By acting as a substitute of a GPS clock, it can reduce
Clock
costs incurred by mounting or maintaining any GPS antenna.
Server
The Local Maintenance Terminal (LMT) is used by engineering personnel
LMT
for deploying, operating, or maintaining a single base station.
 Connecting an eBBU to an eRRU through optical fibers
− One BPL board provides three pairs of optical ports, which are numbered
TX0/RX0, TX1/RX1, and TX2/RX2 from right to left. The transmitting end is
marked as TX, whereas the receiving end is marked as RX.
− An eRRU provides two pairs of optical ports. The first optical port is marked
as OPT1 that is used to connect an eRRU; the second optical port is marked
as OPT2 that is used to cascade another eRRU. Presently, no eRRU
cascading is applied in any existing deployment scenario. The transmitting
end is equivalent to the left end of each optical port, whereas the receiving
end is equivalent to the right end of each optical port.
− To connect an eBBU to an eRRU through optical fibers, insert one optical

module into the TX0/RX0 port of the BPL board and insert another optical
module into the OPT1 port of the eRRU, then connect their optical fibers to
the TX0/RX0 port of the BPL board as well as the OPT1 port of the eRRU,
respectively.
− To check whether a transmitting or receiving port is properly connected, you

can check its indicator (OF0, OF1, or OF2) on the BPL board. If any indicator

is blinking at 1 Hz, you can infer that the corresponding optical fiber is
properly connected.
 Tip:
Currently, the dual-core optical fiber is widely used on site.
An indicator will blink on the eRRU only when the version starts running normally.
 Connecting an eNodeB to an EPC
In most commercial networks, an eNodeB is connected to an electrical switch using an

Ethernet cable through the Eth0 port of the CC board; or the TX/RX port of the CC board
is connected to the optical switch through an optical fiber, and then connected to the EPC
through a transmission network.
2.2 Key Components of an eNodeB

A ZTE’s eNodeB is designed to separate the baseband unit from the radio frequency unit.
An eBBU can act as the baseband unit to implement the S1/X2 signaling control, service
data processing, and baseband data processing functions; whereas, an eRRU can act as
the radio frequency unit. Using this separation method, an eRRU can be deployed either
in a remote way or placed in the same cabinet where the eBBU resides (which is also
known as a macro base station). An eBBU can be connected to an eRRU through the
CPRI port, which is a standard baseband optical port.
Table 2-3 summarizes common models of an eBBU and an eRRU.
Table 2-3 Common Models of an eBBU and an eRRU

Product Name Model
eBBU ZXSDR B8200 L200
ZXSDR R8880 L218
ZXSDR R8880 L178
eRRU ZXSDR R8880 CL708
ZXSDR R8882 L268
ZXSDR R8882 L808
Note:
This document describes how to deploy and configure the most commonly used models:
ZXSDR B8200 L200 (eBBU) and ZXSDR R8882 L268 (eRRU). The remaining models are
beyond the scope of this document.

2.2.1 Key Components of an eBBU
A ZXSDR B8200 L200 consists of the subrack, CC board, SA board, BPL board, power
module, and fan module. The appearance of a ZXSDR B8200 L200 is shown in Figure
2-2.
Figure 2-2 Appearance of a ZXSDR B8200 L200
Table 2-4 summarizes the components and functions of a ZXSDR B8200 L200.
Table 2-4 Components and Functions of a ZXSDR B8200 L200
No. Components Functions

The PM can provide the following functions:
 Providing 3.3 VDC MP and 12 VDC PP
 Being used to reset the other boards of the eBBU by
using MML commands
1 PM (Power)  Detecting whether the other boards of an eBBU is
inserted or removed
 Providing both under-voltage or over-voltage input
protection
 Providing both over-current output protection and
overload power management
The subrack is used to accommodate the parts and
2 Subrack
components of an eBBU.
The FA can automatically adjust the rotation speed,
3 FA (Fan) depending on the operating temperature. In addition, it can
detect, control, and report the fan status.
The BPL board is used to process the physical-layer, MAC,
BPL
4 RLC, and PDCP protocols, as well as providing uplink and
(Baseband)
downlink I/Q signals.

The CC board can provide the following functions:

 Implementing the active/standby switchover function
 Providing either GPS or IEEE 1588 clock
 Providing two adaptive 100/1000M Ethernet ports
 Providing either a 1000BASE-LX/SX or a 100BASE-FX
CC (Clock and
5 optical port
Control)
 Providing a platform for exchanging media and signaling
streams
 Supporting both S1 and X2 interfaces
 Supporting the GE switch
 Offering the subrack management function
The SA can provide the following functions:
 Controlling the rotation speeds of all fans
 Raising or generating alarms
6 SA (Site Alarm)
 Providing external monitoring ports
 Monitoring the operating temperatures of all boards
 Providing dry-contact ports and lightning protection
2.2.2 Key Components of an eRRU
The appearance of a ZXSDR R8882 L268 is shown in Figure 2-3.
Figure 2-3 Appearance of a ZXSDR R8882 L268
Table 2-4 summarizes the components and functions of a ZXSDR R8882 L268.
Table 2-5 Components and Functions of a ZXSDR R8882 L268
No. Components Functions

The eRRU can provide the following functions:

 Supporting such bandwidth as 5 MHz, 10 MHz, 15
MHz, or 20 MHz
 Supporting 2500 MHz - 2570 MHz (uplink) and 2620
MHz - 2690 MHz (downlink)
 Supporting 2T4R (2T2R when replacing the duplex)
 Supporting 64 QAM (uplink/downlink channel)
 Supporting either uplink or downlink power report
1 eRRU  Supporting the power amplifier overload protection
 Supporting either power-on or power-off of a
transmitting channel
 Supporting dynamic power amplifier voltage
configuration for optimum efficiency in different loading
conditions
 Providing a platform that supports smooth switchover
between GSM, UMTS, and LTE systems with only
software upgrade
 Supporting the electical antenna for the AISG2.0 port
2.3 Common Ports of an eNodeB
2.3.1 Common Ports of an eBBU
Figure 2-4 shows the common ports of a ZXSDR B8200 L200.
Figure 2-4 Common Ports of a ZXSDR B8200 L200
Table 2-6 describes the common ports of a ZXSDR B8200 L200.
Table 2-6 Common Ports of a ZXSDR B8200 L200

No. Port Board Description
RS232 serial port for debugging
1 MON PM
purposes
2 -48 V/-48 VRTN PM -48 V (input)

Connecting to the CPRI port of the

TX0/RX0, TX0/RX0,
3 BPL eRRU through three pairs of optical
and TX2/RX2
ports
Adaptive 10M/100M/1000M Ethernet
4 DEBUG/CAS/LMT CC port used for eBBU cascading,
debugging, and maintenance
Adaptive 100M/1000M Ethernet port that
5 ETH0 CC can be used with the S1/X2 port, but
cannot be used with the TX/RX port
1000 BASE-LX/SX or 100 BASE-FX
optical port that can be used with the
6 TX/RX CC
S1/X2 port, but cannot be used with the
ETH0 port
7 REF CC GPS antenna port or BITS clock port
Mainly used for external GPS receiver or
clock extension
Being connected to a GPS antenna,
8 EXT CC retrieving GPS clock signals from
another (e)BBU through a 19 HDMI
cable, or outputting GPS clock signals to
another (e)BBU
9 No silkscreen SA RS485 or RS232 monitor port
2.3.2 Common Ports of an eRRU
Figure 2-5 shows the common ports of a ZXSDR R8882 L268.
Figure 2-5 Common Ports of a ZXSDR R8882 L268

Note:
The common ports of a ZXSDR R8882 L268 are located at the bottom and both sides of the
subrack.
Table 2-7 describes the common ports of a ZXSDR R8882 L268.
Table 2-7 Common Ports of a ZXSDR R8882 L268

No. Silkscreen Port Connector
Round plastic 6-core cable connector
1 PWR Power port
(hole)
Round straightly-welded 8-core plug
2 MON External monitor port
(pin)
3 AISG AISG device port Round 8-core connector
eBBU-to-eRRU
4 OPT1 port/eRRU cascading LC optical connector (IEC 874)
port
eBBU-to-eRRU
5 OPT2 port/eRRU cascading LC optical connector (IEC 874)
port
Transmitting/receiving
6 ANT4 50 Ω DIN connector
antenna port
Receiving diversity
antenna port
Receiving diversity
antenna port
ANT1 Transmitting/receiving
9 50 Ω DIN connector
antenna port
Ethernet operation Curving PCB-welded shielded 8P8C
10 LMT
and maintenance port telephone plug with LED
2.4 Typical Physical Configuration of an eNodeB

Figure 2-6 shows a typical physical configuration of a ZXSDR B8200 L200.

Figure 2-6 Typical Physical Configuration of a ZXSDR B8200 L200
Figure 2-7 shows a typical physical configuration of a ZXSDR R8882 L268.
Figure 2-7 Typical Physical Configuration of a ZXSDR R8882 L268
Note:
This document describes only typical physical configuration of a ZXSDR B8200 L200 and a
ZXSDR R8882 L268. The real physical configuration of a ZXSDR B8200 L200 and a
ZXSDR R8882 L268 may vary, depending on specific network planning data. Prior to initial
configuration, therefore, you must obtain hardware configuration depending on the real
requirements.
The CC, BPL, PM, SA, and other boards must be configured in their designated slots, as
shown in Figure 2-8.

Figure 2-8 Board Layout of a ZXSDR B8200 L200
BPL 4 BPL 8 4HP

6HP Power 15
BPL 3 BPL 7 F 4HP

16
A
6HP Power 14
CC 2 BPL 6 N 4HP
4HP SA 13 CC 1 BPL 5 4HP
Table 2-8 summarizes the physical configuration principles of a ZXSDR B8200 L200.
Table 2-8 Physical Configuration Principles of a ZXSDR B8200 L200
Board Physical Configuration Principles

When configuring a CC board, you must pay attention to the
following principles:
 Only one CC board is configured by default.
 Currently, no CC boards can be configured in active/standby
mode.
CC (mandatory)  When only an FDD LTE system is deployed, you must configure
the CC board in slot 1.
 When an FDD LTE system is collocated with a TDD LTE system
in the same subrack, you must configure two CC boards (one for
FDD LTE and the other for TDD LTE). But you are not allowed to
configure them in active/standby mode.
When configuring a BPL board, you must pay attention to the
 A maximum number of six BPL boards can be configured.
 The number of BPL boards must be configured, depending on
the real capacity as planned.
 Each BPL board can support three sectors.
 There are no special configuration requirements for BPL boards.
But for the purpose of heat dissipation, it is recommended to
BPL (mandatory) configure BPL boards in slots 3 through 8. However, you must
ensure that all BPL boards are consistently configured for all
eNodeBs in the entire network.
 By default, the BPL boards can be configured as follows:
- If only one BPL board is present, you must configure in slot 6.
- If two BPL boards are present, you must configure in slots 5
and 6.
- If three BPL boards are present, you must configure in slot 5,
6, and 7.
When configuring a PM board, you must pay attention to the
 One PM board can supply power for at most four BPL boards.
PM (mandatory)
 If any PM boards are configured in active/standby mode or more
than four BPL boards are configured, you need to configure two
PM boards.
SA (mandatory) Only one SA board is configured by default.

When configuring an SE board, you must pay attention to the

 If two RS232/485 ports or 16 dry contacts are present, you need
SE (Optional: Site to configure one SE board.
Alarm Extension
Board)  If 16 E1/T1 lines are required, you need to configure one SE
board.
 If only an LTE system is present, you do not need to configure
any SE board.
FA (mandatory) Only one FA board is configured by default.
 Note:
Take Hi3G for example. To support its dual-system in V2.1, the BPL board must be
configured in slot 3, 4, or 8, the PM board must configured in slot 14, the CC16 board of the
FDD LTE system must be configured in slot 1, and the CC16 board of the TDD LTE system
must be configured in slot 2.
2.5 Process for Commissioning and Debugging an

eNodeB
Figure 2-9 shows the process for commissioning and debugging an eNodeB.
Figure 2-9 Process for Commissioning and Debugging an eNodeB

Make Powering on the Debugging the eNodeB Configure the eNodeB Performing Verification
Start Troubleshooting alarms End
Preparations eNodeB on the foreground on the background Tests
Importing
Querying the Performing
Collecting Powering
the configuratio a UE
site on the
foreground n file from attachment
information eBBU
version the test
background
(Optional)
Performing
contra-
Powering Upgrading a ping test
Preparing construct
on the the eNodeB on both
tools the
eRRU version uplink and
configuratio
downlink
n data
Performing
Importing
a UDP
Preparing the
Configuring traffic
the configuratio
radio generation
configuratio n file from
parameters test on both
n files the
uplink and
foreground
downlink
Checking
Performing
transmissio Configuring
an FTP test
n IEEE1588
on both
parameters and GPS
uplink and
for clocks
downlink
correctness
Performing
Configuring an
dry contacts IEEE1588
clock test
Configuring Performing
electrical a dry
antennas contact test
Performing
data
synchroniati
on
Table 2-9 summarizes the estimated time required for commissioning and debugging an
eNodeB.

Table 2-9 Estimated Time Required for Commissioning and Debugging an eNodeB
No. Operation Procedure Estimated
Platform Time (Min)
1 Foreground Section 4 Powering on an eNodeB 10
2 Foreground Section 5.1 Querying the Version on the 5
Foreground
3 Foreground Section 5.2 Section B.1.1 Interim Version 14
(Optional) Upgrade
Upgrading Section B.1.2 Upgrading the CC 42
the eNodeB BOOT Version from V2.00.050*
Version to V2.00.060eP01
Section B.2 Upgrading 21
V2.00.060eP01 to V2.10.050e
4 Foreground Section 5.3 Importing the Configuration File from 5
the Foreground
5 Foreground Section 5.4 Checking Transmission Parameters 5
6 Background Section 6.1 Importing the Configuration File from 3
the EMS
7 Background Section 6.2 Configuring Radio Parameters for an 30
eNodeB
8 Background Section 6.3 Configuring Clock Parameters 10
9 Background Section 6.4 Configuring a Dry Contact 8
10 Background Section 6.5 Configuring an Electrical Antenna 15
11 Background Section 6.6 Performing Data Synchronization 14
(including
the eNodeB
restart and
link setup
between the
foreground
and the
background)
12 Background Section 7 Troubleshooting eNodeB Alarms Depending
on real
alarms
13 Foreground Section 8 Section 8.1 Performing a UE 10
Verifying Attachment Test (Connection and
Basic Release)
14 Foreground eNodeB Section 8.2 Performing a Ping 10
Services Test (Uplink and Downlink)
15 Foreground Section 8.3 Performing a UDP 10
Traffic Generation Test (Uplink
and Downlink)
16 Foreground Section 8.4 Performing an FTP 10
Test (Uplink and Downlink)
17 Foreground Section 8.5 (Optional) 20
Performing an IEEE1588 Clock
Test

18 Foreground Section 8.6 (Optional) 10

Performing a Dry Contact
Test(Optional) Performing a Dry
Contact Test
Note:
If an eNodeB is properly pre-installed without having to perform any version upgrade in the
foreground, it will take approximately 175 minutes to complete the previous tasks, including
the basic service verification test. This table does not imply the exact time required for
commissioning and debugging an eNodeB. Therefore, it is used for your reference only.
3 Preparing for Commissioning and

Debugging an eNodeB
Before commissioning and debugging an eNodeB, you must perform the following tasks:
 Getting to know the workload, schedule, labor, readiness of hardware and software,
readiness of goods, local rules and regulations, and customer requirements
 Getting relevant persons advised of making necessary preparations
 Searching the exact locations of sites as well as their drive routes
 Preparing the key to the equipment room, debugging tool, and spare parts (such as
one CC board and one BPL board)
 Collecting the site information and generating the configuration data files based on
the real situation
3.1 Reading the Contract Information

Before commissioning and debugging an eNodeB, you must carefully read the contract
information as follows:
 Retrieving the contract text from the local representative office
 Reading the contract information with care, such as hardware configuration,

software configuration, shipment date, project schedule, and special requirements
such as technical and commercial clarifications

 Contacting the engineering manager, technical manager, and sales representative

in the local representative office to know the contract details (including cautions and
warnings)
 Checking whether either the design or the configuration is conflicting with the
practical implementation; if yes, consulting the technical manager
3.2 Inquiring the Shipment Information

Before commissioning and debugging an eNodeB, you must inquire the shipment
information as follows:
 Inquiring the shipment date from the local representative office
 Verifying that the contract configuration is consistent with the packing list
 Checking whether the shipment is arrived intactly or in multiple batches
 Contacting the engineering manager immediately when you find any problem
3.3 Collecting the Frontline Information

Before commissioning and debugging an eNodeB, you must inquire the equipment room,
customer requirements, and subcontractors’ qualification:
 Obtaining the customer’s personnel, networking mode, engineering background,

project profile, and other required information from the local representative office
 Contacting the customer’s project leader to get the project details, such as project
schedule and special requirements including:
− Where the equipment is installed
− How the transportation is arranged
− How the subcontractors can perform their tasks
 Performing the site check in compliance with the FDD LTE ZXSDR eNodeB
Installation Quality Checklist.
3.4 Applying for a Software Version

Before using a formal software release, you must perform the following steps:
1. Filling out a version application form

2. Submitting the version application form to the approver and carbon-copying it to the
technical manager and engineer manager
3. Waiting for the version manager to review the version application form
Note:
You are not allowed to use a formal version release until the version manager has approved
your application.
3.5 Checking the Labor for Readiness

Before commissioning and debugging an eNodeB, you must check whether the human
labor is ready:
 Getting to know how the human labor is arranged from the engineering manager in
the local representative office, including the hardware and software supervisors,
hardware installers, and subcontractors
 Retaining the contact information of the previously mentioned persons
3.6 Preparing the Debugging Tools
Table 3-1 summarizes the tools required for commissioning and debugging an eNodeB.
Table 3-1 Tools Required for Commissioning and Debugging an eNodeB
No. Name Description

This is a network management tool for
operation and maintenance on a per eNodeB
1 LMT basis. This tool is released with the version
package; therefore, it varies from version to
version.
This tool can be used to batch-configure or
2 BCT quickly modify any data. This tool is released
with the version package.
The PC must be already equipped with the
3 PC JRE, DU Meter, Iperf, FileZilla, UE drive
program, and other required software.
Standard
The cable is used for telneting a board on the
4 straight-through/cross-connect
foreground.
Ethernet cable

3-pin serial port cable with a If the initial version of the eNodeB is
5 connector that can convert the incorrect, you can use this serial port cable to
serial port into the network port download the version from the foreground.
You can use, for example, Samsung
6 Test UEs
GT-B3730 or ZTE MF820 as test UEs.
Shipping version package and
You can obtain them from the project
7 commercial version package
person-in-charge or ZTE’s GCSC website.
for the eNodeB
The other tools include the multimeter,
screwdriver, antistatic wrist wrap,
8 Other special-purpose wrench or pliers used for
driving the bolts that can theft-proof an
eRRU.
3.7 Collecting the Site Information

Purpose
Before commissioning and debugging an eNodeB, you must collect the site information,
such as eNodeB, equipment, environmental monitoring, clock, link, and parameter
configuration. Subsequently, you must fill the collected information in the network
planning worksheet (*.xlsx), and then generate a configuration file.
Prerequisites
Before commissioning and debugging an eNodeB, you must meet the following
prerequisites:
 All the devices and cables have been properly mounted.
 All the eNodeB information has been successfully verified.
 The network planning worksheet in *.xlsx format is ready.
 Knowledge:
You can obtain the network planning worksheet in *.xlsx format (namely,
BatchDealTemplate.xlsx file provided by the BCT) from the zipped BCT package that
matches the target version.
Procedure
To collect the site information, you must perform the following steps:
1. Collect basic eNodeB information, as summarized in Table 3-2 and Table 3-3.

Table 3-2 Basic eNodeB Parameters
Table 3-3 Basic eNodeB Information

Parameter
Item Description Parameter Path in EMS
Name in EMS
This parameter is
used to identify an
eNodeB provided by Configuration
the network planning Management > eNB >
eNB ID Station ID
engineer. The Config Set > Platform
modification of this Equipment Resource
parameter will cause
the CC board to reset.
This parameter is
used to name an
eNodeB provided by Configuration
the network planning Management > eNB >
eNB Name Station Name
engineer. The Config Set > Platform
modification of this Equipment Resource
parameter will cause
the CC board to reset.
Configuration
This parameter is Management > eNB >
short for Mobile Config Set > Platform
MCC Country Code, which MCC Equipment Resource >
is provided by the eNodeB Equipment
mobile operator. Resource > eNodeB
Attribute
Configuration
This parameter is Management > eNB >
short for Mobile Config Set > Platform
MNC Network Code, which MNC Equipment Resource >
is provided by the eNodeB Equipment
mobile operator. Resource > eNodeB
Attribute
This parameter
specifies the Configuration
eNB longitude of an Management > eNB >
Longitude
Longitude eNodeB, which is Config Set > Platform
provided by the Equipment Resource
mobile operator.

This parameter
Configuration
specifies the latitude
Management > eNB >
eNB Latitude of an eNodeB, which Latitude
Config Set > Platform
is provided by the
Equipment Resource
mobile operator.
2. Collect the global port information of an eNodeB, as summarized in Table 3-4 and
Table 3-5.
Table 3-4 Global Port Parameters of an eNodeB
Table 3-5 Global Port Information of an eNodeB
Parameter
Name in EMS
This parameter
identifies the global
Global Port
port, which is provided Global Port ID
ID Configuration
by the network planning
engineer. Management > eNB >
This parameter Equipment Resource >
identifies the VLAN, Platform Transmission
which can be provided Resource > Link
either by the mobile Protocol > Global Port
VLAN ID VLAN ID
operator if planned, or Parameters
the network planning
engineer if not planned
by the mobile operator.
3. Collect the IP information of an eNodeB, as summarized in Table 3-6 and Table 3-7.
Table 3-6 IP Parameters of an eNodeB

Table 3-7 IP Information of an eNodeB
Parameter
Name in EMS
This parameter
specifies the IP
addresses configured
for an eNodeB, which
is provided by the
network planning
eNB IP engineer. You can IP Address of
Address configure multiple IP Global Port
addresses for the
SCTP of the control
plane, SCTP of the
media plane, IP clock,
and OMC channel Configuration
port, respectively. Management > eNB >
This parameter Config Set > Platform
specifies the subnet Equipment Resource >
IP Address Platform Transmission
Subnet Mask mask associated with
Mask Resource > IP
the IP address of the
eNodeB. Transmission > IP
Parameters
This parameter
specifies the gateway
Gateway address associated Gateway IP
with the IP address of
the eNodeB.
This parameter
specifies the global
Related port number (coupled
Used Global
Global Port with the VLAN ID)
Port
ID associated with the IP
address of the
eNodeB.
4. Collect the IP information of the OMC, as summarized in Table 3-8 and Table 3-9.
Table 3-8 IP Parameters of the OMC

Table 3-9 IP Information of the OMC

Parameter
Item Description Name in Parameter Path in EMS
EMS
This parameter
specifies the IP OMCB
OMC IP
address of the Server IP
OMC.
This parameter
specifies the
gateway
associated with the
IP address of the
OMC. In an FDD
LTE network, the IP
address of the
Configuration
OMC is an SIGIP OMC
OMC GateWay Management > eNB >
(namely, Gateway IP
mono-header IP);
Equipment Resource >
therefore, the IP
Platform Transmission
field of the network
Resource > Upper
management
Protocol > OMCB
system does not
Configuration
work and you do
not need to
configure it.
This parameter
specifies the IP
address that allows eNodeB
eNB Operation the OMC to gain Operation
and access to the and
Maintenance IP eNodeB. It can Maintenance
enable the eNodeB IP
to communicate
with the OMC.
5. Collect the clock information of an eNodeB, as summarized in Table 3-10 and Table
3-11.
Table 3-10 Clock Parameters of an eNodeB

Table 3-11 Clock Information of an eNodeB

Parameter
Item Description Name in Parameter Path in EMS
EMS
This parameter
specifies the IP
address of an
IEEE1588 clock
1588 Server server. This Destination Configuration
IP parameter is IP Management > eNB >
mandatory if an Config Set > Platform
IEEE1588 clock Equipment Resource >
server is present in Platform Transmission
the eNodeB. Resource > Clock
This parameter Management > PTP
specifies the gateway Logical Port
1588 Server associated with the
Gateway IP
GateWay IP address of the
IEEE1588 clock
server.
6. Collect static route information, as summarized in Table 3-12 and Table 3-13.
Table 3-12 Static Route Parameters
Table 3-13 Static Route Information
Parameter
Name in EMS
This parameter
specifies the IP
address of the target Configuration
network, where the Management > eNB >
control plane, user Config Set > Platform
Target plane, OMC, Destination Equipment Resource >
Network IP IEEE1588 packet Network Platform Transmission
destination is Resource > IP
residing, or this Transmission > Static
parameter can be Route
directly destined for a
specific IP address.

This parameter
Static Route specifies the subnet
Network Mask
Subnet Mask mask associated with
the target network.
This parameter
specifies the gateway
address of the next
hop, that is to say, the
Next Hop
first gateway address Next Hop IP
GateWay
through which the
eNodeB sends a
packet to the
destination.
This parameter
specifies the global
Static Route
port number (coupled
Related Used Global
with the VLAN ID)
Global Port Port
associated with the IP
ID
address of the static
route.
7. Collect the SCTP information of the S1 interface, as summarized in Table 3-14 and
Table 3-15.
Table 3-14 SCTP Parameters of the S1 Interface
Table 3-15 SCTP Information of the S1 Interface
Parameter Name in Parameter Path in

Item Description
EMS EMS
This parameter
Configuration
specifies the local
Management >
port number of the S1
eNB > Config Set >
association link,
Platform
which is provided by
Equipment
Local Port the network planning Local Port
Resource >
engineer. In other
Platform
words, this parameter
Transmission
must be set to the
Resource > Upper
local port number of
Protocol > SCTP
the eNodeB.

This parameter
specifies the peer
port number of the S1
association link,
which is provided by
Remote Port the network planning Remote Port
engineer. In other
words, this parameter
must be set to the
peer port number of
the MME.
This parameter
specifies the IP
address associated
with the peer port
number of the S1
Remote IP association link. In Remote IP Address
other words, this
parameter must be
set to the IP address
of the peer port on the
MME side.
 Knowledge:
Currently, you can configure a maximum number of 36 association links, among which you
need to configure at least one S1 association link and configure the remaining association
links as X2 association links. When an X2 association link is configured, you must set both
local and remote port to 36422.
8. Collect the cell information, as summarized in Table 3-16 and Table 3-17.
Table 3-16 Cell Parameters
Table 3-17 Cell Information

Parameter Name in Parameter Path in
Item Description
EMS EMS
This parameter Configuration
specifies the name Management >
of a cell, which is eNB > Config Set >
Cell Name provided by the User Label Global Parameters
network planning of eNodeB >
engineer. Serving Cell >
Serving Cell

This parameter
identifies a cell,
Cell ID which is provided by Cell Identity
engineer.
This parameter
specifies the name Configuration
RRU Name of the RRU that is RRU Rack Name Management >
associated with the eNB > Config Set >
cell. Platform
This parameter Equipment
specifies the number Resource >
RRU NO. of the RRU that is RRU Rack No. Platform Physical
associated with the Resource > Rack
cell.
This parameter
Physical Cell
identified a physical Physical Cell ID
ID
cell.
This parameter
specifies the tracking
area code, which is
TA Code Tracking Area Code
provided by the
network planning
engineer.
This parameter
specifies the
bandwidth indicator, Band Indicator for DL
Band Indicator
which is provided by and UL Frequency
engineer. Configuration
Management >
This parameter eNB > Config Set >
specifies the uplink Global Parameters
UL Center center frequency, Uplink Center Carrier of eNodeB >
Frequency which is provided by Frequency(MHz) Serving Cell >
the network planning Serving Cell
engineer.
This parameter
specifies the
downlink center Downlink Center
DL Center
frequency, which is Carrier
Frequency
provided by the Frequency(MHz)
network planning
engineer.
This parameter
specifies the uplink
UL System system bandwidth, Uplink System
BandWidth which is provided by BandWidth
engineer.

This parameter
specifies the
downlink system
DL System Downlink System
bandwidth, which is
BandWidth BandWidth
provided by the
network planning
engineer.
3.8 Generating the Configuration File

Purpose
Based on the collected eNodeB information, you can use the BCT to fill out the basic
configuration template, and then generate a configuration file that is suitable for the real
situation.
Note:
You are required to use the BCT to generate the configuration file in *.xml format for
VV2.10.050e or later. When using the BCT, you must pay attention to the following
principles:
 To ensure that the BCT can match the target version, you must obtain the BCT from the
target version package.
 When using the BCT, you must use the network planning worksheet in Excel format
titled BatchDealTemplate.xlsx.
 The fast configuration template in *.xml format provided by the BCT must have been
exported from a commissioned eNodeB on site.
Prerequisites
Before generating a configuration file, you must meet the following prerequisites:
1. You have already collected the eNodeB information.
2. You have already obtained the fast configuration template from the project
person-in-charge.
3. The PC that is running the BCT has been installed with JRE version 6 or later. If not,
go to http://www.java.com/en/download/inc/windows_upgrade_ie.jsp.
Procedure
To generate a configuration file, you must perform the following steps:

1. Uncompress the BCT package in the X:\BCT folder.
2. Display the BCT\input directory.
3. Place the fast configuration template in *.xml format (hereinafter referred to as

FastConfig_3Cell.xml) in the BCT\input directory.
4. Open the network planning worksheet in Excel format titled

BatchDealTemplate.xlsx.
5. Set Quote Template to the full file name of the fast configuration template.
6. Based on the collected eNodeB information, modify the parameters, such as Basic
Parameters, Global Parameters, eNB IP Parameters, OMC IP Parameters, 1588
Server IP Parameters, Static Route Parameters, S1 SCTP Parameters, and Cell
Parameters, as summarized in Table 3-18.
Table 3-18 Parameters to Be Modified in the Network Planning Worksheet
7. Use the BCT to generate a configuration file, as described in chapter AppA “How to
Use the BCT”.
Additional Information
Batch Configure Tool (BCT) is an easy-to-use tool that is used for batch-configure all
sites by using a configuration template. Using the BCT, you can generate a configuration
file in *.xml format through the fast configuration template. When the eNodeB is powered
on for commissioning and debugging, you need to sync the configuration file in *.xml
format with the eNodeB. In this way, you can complete the configuration task of all sites
for one time.
You can use the BCT to input the fast configuration template and network planning
worksheet in Excel format. The fast configuration template can be exported from the LMT
or EMS. The network planning worksheet in Excel format must be filled with the planned
site parameters. You can use the BCT to output a configuration file in *.xml format for all
sites that are included in the Excel worksheet.
For more information about how to generate a configuration file for a typical scenario,
refer to the FDD LTE eNodeB Initial Configuration Guide.

4 Powering on an eNodeB
When powering on an eNodeB, you must follow the safety rules and regulations. Before
powering on any part or component, you must supply the eNodeB with an external power
source. After you have powered on a part or component, you must verify that it is
functioning normally.
Caution:
When powering on an eNodeB, you must carefully check the label of the air switch to verify
that the eNodeB is exactly the one you want to commission and debug it. Otherwise, you
may mis-power on or misoperate an existing device, or cause the running devices to be
powered off.
Figure 4-1 shows how the eBBU is supplied with power.
Figure 4-1 eBBU Power Supply
Figure 4-2 shows where the power switch is located on the PM3 board.
Figure 4-2 Power Switch on the PM3 Board
Figure 4-3 shows how the eRRU is supplied with power.

Figure 4-3 eRRU Power Supply
4.1 Powering on an eBBU

Purpose
This section describes how to power on an eBBU (ZXSDR B8200 L200).
Prerequisites
Before powering on an eBBU, you must meet the following prerequisites:
 Verify that the power supply can meet the requirements of the ZXSDR B8200 L200
(DC -40 V to -57 V).
 Verify that both ZXSDR B8200 L200 power and ground cables are properly
connected.
 Verify that the ZXSDR B8200 L200 power supply is disconnected.
Procedure
To power on an eBBU, you must perform the following steps:
1. Remove all boards from the subrack.
2. Switch on the power distribution cabinet to the ZXSDR B8200 L200, and use a
multimeter to measure the -48 V power supply, which is provided for the rack.
3. Switch off the power distribution cabinet that is connected to the ZXSDR B8200
L200, and connect the ZXSDR B8200 L200 power cable to the power source.

4. Insert all boards into the subrack, and switch on the power distribution cabinet that is
connected to the ZXSDR B8200 L200.
5. Turn on the power switch on the PM board.
6. If any problem occurs during the power-on procedure, you must turn off the power
supply and eliminate the problem.
There are two types of PM boards: PM1 and PM3. A PM1 board does not provide any
power switch, whereas a PM3 board provides a power switch. Presently, a normal
shipment usually supplies a PM3 board.
For more information about the ZXSDR B8200 L200 hardware installation requirements,
refer to the FDD LTE B8200 + R8882 Quick Installation Guide.
4.2 Powering on an eRRU

Purpose
This section describes how to power on an eRRU (ZXSDR R8882 L268).
Prerequisites
To power on an eRRU, you must perform the following steps:
 Verify that the power supply can meet the requirements of the ZXSDR R8882 L268.
 Verify that both ZXSDR R8882 L268 power and ground cables are properly
connected.
 Verify that the ZXSDR R8882 L268 power supply is disconnected.
Procedure
To power on an eRRU, you must perform the following steps:
1. A ZXSDR R8882 L268 does not provide any power switch. To power on a ZXSDR
R8882 L268, you need to switch on the external DC power supply.
2. If any problem occurs during the power-on procedure, you must turn off the power
supply and eliminate the problem.
For more information about the ZXSDR R8882 L268 hardware installation requirements,
refer to the FDD LTE B8200 + R8882 Quick Installation Guide.

5 Commissioning an eNodeB from the

Foreground
Prior to a formal commissioning, you must perform the following steps:
1. Log in to the eNodeB through the LMT.
2. Check whether the running version of the eNodeB is consistent with the target
version.
3. Check whether the CC flash space is sufficient for version upgrade.
4. Sync the configuration file stored in the PC that is running the LMT with the eNodeB.
5. Wait for the eNodeB to restart, after the synchronization procedure is complete and
the eNodeB has running the new data.
6. When necessary, connect the LMT to the eNodeB to check the eNodeB
transmission parameters.
Table 5-1 summarizes the foreground commissioning tasks.
Table 5-1 Foreground Commissioning Tasks
Section Commissioning Task

Check whether the running version of the eNodeB is
5.1 Querying the Version
consistent with the target version. If it is not V2.1, you
on the Foreground
need to firstly upgrade the eNodeB version.
Depending on the real situation of whether the version
5.2 (Optional) Upgrading
is preinstalled, you need to decide whether to perform
the eNodeB Version
the eNodeB version upgrade.
5.3 Importing the From the foreground, sync the configuration file with
Configuration File from the the eNodeB by using the LMT to complete the
Foreground configuration process.
After the configuration file is sync with the eNodeB,
5.4 Checking Transmission check whether the eNodeB has established a link with
Parameters the EMS successfully by verifying the transmission
parameters using the LMT.
5.1 Querying the Version from the Foreground

Purpose
Presently, all the board versions are stored in the CC board. During normal operation, the
other boards retrieve their respective versions from the CC board. This section describes
how to check whether the running version of the eNodeB is consistent with the target
version.
Prerequisites
The eBBU (ZXSDR B8200 L200) must have already been powered on.
Procedure
To check consistency between the running version and the target version, you must
perform the following steps:
1. Connect the laptop to the DEBUG port of the CC board through an Ethernet cable,
as shown in Figure 5-1.
Figure 5-1 Telneting the eNodeB through a Laptop
2. Set the IP address of the laptop in the same network segment as the IP address of
the DEBUG port (192.254.xxx.16, where xxx indicates the slot number of the CC
board; if the CC board is inserted in slot 1, the IP address is 192.254.1.16). Set the
subnet mask as same as that of the DEBUG port (255.255.0.0). Leave the gateway
blank.
3. Display the cmd.exe window, run the telnet 192.254.xxx.16 command to telnet the
CC board, and type the username (zte) and password (zte).
C:\Documents and Settings\Administrator>telnet 192.254.1.16
<none> login: zte
Password:

Processing /etc/profile… Done
4. After having logged in to the CC board, run the ./ushell command behind the #
prompt, type the password (zte), and verify that the $$ prompt is shown in the
cmd.exe window.
# ./ushell
-> Please input password!
->
***
-> Login success!!
ushell tool menu:
------------------------------------------------------------------------------
'ps' or 'PS' list process run on the board
'pr xxx' or 'PR xxx' take over xxx process printf info
'npr xxx' or 'NPR xxx' not take over xxx process printf info
'db xxx' or 'DB xxx' debug xxx process printf info
'ndb xxx' or 'NDB xxx' not debug xxx process printf info
'pad xxx' or 'PAD xxx' debug and take over xxx process printf info
'npad xxx' or 'NPAD xxx'not debug and take over xxx process printf info
'pall' or 'PALL' display current debug and take over info
'Q' or 'q' cancel all process debug and printf info
'exit' or 'EXIT' cancel ushell
xxx is process id you want to debug or take over printf inf
o
------------------------------------------------------------------------------
$$
5. Run the ps command behind the $$ prompt, query the PID of MGR.EXE (program
identification), and run the pad xxx command to bundle this program, where xxx
indicates the PID of MGR.EXE.
− If the window displays the ushell enter print mod and ushell enter debug
mod printout information, you can infer that the bundling process is successful.
− If not, you must run the pad xxx command again.
In this example, the PID of MGR.EXE is 681; therefore, you must run the pad 681
command.
$$ps
PID USER VSZ STAT COMMAND
1 zte 1448 S init
2 zte 0 SW [softirq-high/0]
3 zte 0 SW [softirq-timer/0]

4 zte 0 SW [softirq-net-tx/]
5 zte 0 SW [softirq-net-rx/]
6 zte 0 SW [softirq-block/0]
7 zte 0 SW [softirq-tasklet]
8 zte 0 SW [softirq-sched/0]
9 zte 0 SW [softirq-hrtimer]
10 zte 0 SW [softirq-rcu/0]
11 zte 0 SW [watchdog/0]
12 zte 0 SW [chkeventd/0]
13 zte 0 SW< [events/0]
14 zte 0 SW< [rt_events/0]
15 zte 0 SW< [khelper]
16 zte 0 SW< [kthread]
17 zte 0 SW< [rt_kthread]
37 zte 0 SW< [kblockd/0]
42 zte 0 SW< [khubd]
83 zte 0 SW [pdflush]
84 zte 0 SW [pdflush]
85 zte 0 SW< [kswapd0]
86 zte 0 SW< [aio/0]
621 zte 0 SW [mtdblockd]
681 zte 1276m S /MGR.EXE
682 zte 17348 S /tftp
684 zte 436 S /ztam
686 zte 1448 S telnetd
688 zte 1456 S inetd
690 zte 1520 S /bin/sw
695 zte 1456 S -/bin/ash
705 zte 0 SWN [jffs2_gcd_mtd0]
798 zte 712m S /Product_lte_fdd.o 61 64
821 zte 1460 S -sh
822 zte 9184 R ./ushell
824 zte 1448 R sh -c ps
825 zte 1448 R ps
$$pad 681
$$
[681]
ushell enter print mod

ushell enter debug mod
6. Run the VMP command to query the running version of the CC board.
VMP
[681]
[ begin to excel fun:VMP ]
*****************VMP Status Info *************

DEBUG VERSION
The Board Status--------------- MasterBoard!
Run CC Version ---------------- V2.00.060c

Run CC File Length ------------ 8141729
Bak CC Version ---------------- V2.00.050LP02
Bak CC File Length ------------ 8048490
Running Status ---------------- S_MasterIdle!
Run Package Path -------------- /mnt/flash/SW1/
Run Package Version ----------- V2.00.060c
Bak Package Path -------------- /mnt/flash/SW2/
Bak Package Version ----------- V2.00.050LP02
********************************************
value = 45
[ end to excel fun:VMP ]
$$
7. Run the exit command to exit the ushell mode.
8. When the # prompt is displayed in the cmd.exe window, exit the cmd.exe window.
5.2 (Optional) Upgrading the eNodeB Version

Purpose
Depending on whether the preinstalled version is consistent with the target version, you
may have to upgrade the eNodeB version.
Procedure
To upgrade an eNodeB version, you must perform the following steps:
1. Check whether the eNodeB version is V2.1.
i. If the eNodeB version is V2.1, you do not need to upgrade the eNodeB version.

ii. If the eNodeB version is V2.00.060eP01, you must upgrade it to V2.1.
For more information about how to upgrade the eNodeB version to V2.1, refer
to section B.2 “Upgrading V2.00.060eP01 to V2.10.050e”.
iii. If the version is earlier than V2.00.060eP01 including V2.00.050* and

V2.00.060d, you need to upgrade the eNodeB version to V2.00.060eP01 firstly,
and then upgrade V2.00.060eP01 to V2.1.
For more information about how to upgrade V2.00.050* to V2.00.060eP01,

refer to section B.1 “Upgrading V2.00.050* to V2.00.060eP01”.
For more information about how to upgrade V2.00.060d to V2.10.050e, refer to

section B.2 “Upgrading V2.00.060eP01 to V2.10.050e”.
5.3 Importing the Configuration File from the

Foreground
Purpose
This section describes how to sync the configuration file with the eNodeB using the LMT.
Prerequisites
Before importing the configuration file from the foreground, you must meet the following
prerequisites:
 The laptop that is running the LMT is installed with both JRE version 6 or later and
LMT V2.10.050e.
 The configuration file in *.xml format for V2.10.050e is ready.
 The running version of the eNodeB is V2.10.050e.
Procedure
To import the configuration file from the foreground, you must perform the following
steps:
1. Log in to the eNodeB using the LMT of the target version.
2. Choose System > Entire Table Configuration > synchronization Entire Table
Configuration.

Figure 5-2 Synchronization Entire Table Configuration Menu Item
Figure 5-3 Open Dialog Box

3. In the Open dialog box, choose the configuration file in *.xml format of the target
version, and then click the Open button.
Figure 5-4 Choosing the Configuration File
4. When the following prompt is displayed, click OK so that the LMT can sync the
configuration file with the eNodeB.
Figure 5-5 Syncing the Configuration File with the eNodeB
5. When the synchronization is successful, the LMT prompts the following message
box.

Figure 5-6 Success Message Box
6. Wait for 20 seconds, click OK. The LMT remains connected to the eNodeB and
displays the main window.
5.4 Checking Transmission Parameters

After the configuration file is sync with the eNodeB, you need to check the transmission
parameters for correctness, including GE Parameter, Global Port Parameter, IP
Parameter, Static Route Parameter, and OMC Parameter. The purpose of this task is
to ensure that the eNodeB can establish a link with the EMS successfully. If any
transmission parameter is incorrect, you need to use the BCT to generate a new
configuration file, and then import the new configuration file into the eNodeB.
Figure 5-7 Transmission Resource Layers
STREAM
Resources SCTP ID
(Transmission
Layer and SCTP OMC BFD IP Clock IPsec ...
Application
Layer)
IP ID IP ID IP ID IP ID IP ID IP ID
Resources
(Network IP Parameter ROUTE
Layer)
GlobalPortID GlobalPortID
Resources
(Logical GlobalPort
Layer)
PortID (VLAN or no VLAN)
Resources
(Link Layer)
GE

5.4.1 Checking GE Parameters
Purpose
This section describes how to check whether the GE parameters have been properly
configured as planned.
 Knowledge:
The GE port is used to connect the eNodeB to an external device. You need to configure
such GE parameters as operating mode and physical bandwidth.
Procedure
To check GE parameters, you must perform the following steps:
1. Log in to the eNodeB through the LMT of the target version.
2. On the left Configuration Management navigation tree, choose Configuration

Management > Transmission Resource Management > IP Bearing > GE
Parameter.
Figure 5-8 GE Parameter Pane
3. Check whether the following parameters have properly been configured as planned.

Parameter Description
Ethernet Port This parameter specifies the GE port number. An eNodeB
Identity supports only one Ethernet port. By default, it is set to 0.
This parameter specifies the operating mode of the GE port.
You can set it to one of the following values:
Ethernet Work  Self Adaptive
Mode  Electronic port 100Mbps FDT
 1000Mbps FDT
 Light port 100Mbps FDT
This parameter specifies the reverse bandwidth of the GE
Reverse Bandwidth
port. By default, it is set to 100000 (Kbps).
This parameter specifies the forward bandwidth of the GE
Forward Bandwidth
port. By default, it is set to 100000 (Kbps).
5.4.2 Checking Global Port Parameters
Purpose
This section describes how to check whether the global port parameters have been
properly configured as planned, including the VLAN information.
Procedure
To check global port parameters, you must perform the following steps:

Management > Transmission Resource Management > IP Bearing > Global
Port Parameter.

Figure 5-9 Global Port Parameter Pane
2. Check whether the following parameters have properly been configured as planned.
Global Port ID This parameter specifies the VLAN ID in the system.
This parameter specifies the GE port number.
Port ID
By default, it is set to 0.
You can set this parameter to the S1, X2, clock, or network
VLAN ID management port for each VLAN.
If no VLAN is in use, you must set it to 65535.
This parameter specifies the maximum number (byte) of
data packets that can pass through a specific layer based
Maximum transit unit
on the predefined protocol. It is usually related to such ports
as network port and serial port.
Configuration Example
Let us suppose that a global port is defined as follows:
 Only one IP address (10.10.93.28) is assigned on the eNodeB side.
 No VLAN is used for the SCTP of the control plane, and its VLAN ID is 65535.
 A VLAN is used for the user plane, and its VLAN ID is 1.
 A VLAN is used for the OMC channel, and its VLAN ID is 2.

 A VLAN is used for the IP clock, and its VLAN ID is 3.
In this context, you need to configure a total number of four records, as shown in Figure
5-10.
Figure 5-10 Configuration Example of a Global Port
A virtual local area network (VLAN) is commonly used in a transmission network.

Physically, a transmission network can be divided into multiple VLANs, each of which is
isolated respectively; therefore, they cannot gain access to each other. This technology is
used to avoid network broadcast storms, as well as provide security and encryption.
The VLAN standard is prescribed in IEEE802.1p/q. This standard defines the VLAN tag
format in the MAC header. A total number of four bytes are used for a VLAN tag, among
which the VLAN ID occupies 12 bits, the priority occupies three bits, the token ring
(optional) occupies one bit, and the Ethernet frame with the VLAN tag occupies the
remaining 16 bits.
IEEE802.1p also defined the layer-2 data priority, ranging from level 0 (lowest) to 7
(highest). In other words, the layer-2 device is required to control data streams based on
the defined priority.

5.4.3 Checking IP Parameters
Purpose
This section describes how to check whether the IP parameters have been properly
 Knowledge:
The IP parameters refer to the IP addresses of the control plane, user plane, OMC channel,
and IEEE1588 clock on the eNodeB side.
Procedure

Management > Transmission Resource Management > IP Bearing > IP
Parameter.
Figure 5-11 IP Parameter Pane
2. In the IP Parameter pane, choose the desired record, and then right-click Modify.

Figure 5-12 Modify Menu Item
The EOMS displays the Basic Information tab page, as shown in Figure 5-13.

Figure 5-13 Basic Information Tab Page
3. Check whether the IP parameters have properly been configured as planned.
Table 5-2 IP Parameters

This parameter specifies the wireless system. It
Wireless Radio Mode
should be set to LTE-FDD in this context.
This parameter specifies the global port number
associated with the IP address on the eNodeB side,
Global Port ID
including the VLAN IDs that are used for different IP
addresses as planned.
This parameter specifies the IP address on the
eNodeB side. You can configure multiple IP
IP Address of Global Port addresses for the SCTP of the control plane, SCTP
of the user plane, IP clock, and OMC channel port,
respectively.
This parameter specifies the subnet mask associated
IPv4 Address mask
with the IP address on the eNodeB side.
This parameter specifies the IP address of the default
Gateway IP
gateway on the eNodeB side.
This parameter specifies the Time-to-Live (TTL) of an
TTL
IP packet. By default, it is set to 255.

Configuration Example
Let us suppose that an IP context is defined as follows:
 Only one IP address (20.2.152.101) is assigned on the eNodeB side.
 No VLAN is used for the SCTP of the control plane, and its VLAN ID is 65535
(global port 1).
 A VLAN is used for the user plane, and its VLAN ID is 1 (global port 2).
 A VLAN is used for the OMC channel, and its VLAN ID is 2 (global port 3).
 A VLAN is used for the IP clock, and its VLAN ID is 3 (global port 4).
In this context, you need to configure a total number of four records, as shown in Figure
5-14.
Figure 5-14 Configuration Example of an IP Context
5.4.4 Checking Static Route Parameters
Purpose
This section describes how to check whether the static route parameters have been
properly configured as planned.

Note:
When the default gateway cannot reach the destination network, you need to configure a
static route, which requires two IP addresses (one is the destination network and the other is
the next hop).
Procedure

Management > Transmission Resource Management > IP Bearing > Static
Route Parameter.
Figure 5-15 Static Route Parameter Pane
2. In the Static Route Parameter pane, choose the desired record, and then
right-click Modify.


3. Check whether static route parameters have properly been configured as planned.
Table 5-3 Static Route Parameters

This parameter must be the same as that is configured in
Global Port ID
section 5.4.3 Checking IP Parameters.
This parameter specifies the destination network, in
which the control plane, user plane, OMC, and
Destination network of
IEEE1588 clock are residing. It can be set to the IP
static route item
address of the MME port, SGW service, EMS server, or
IEEE1588 clock server.
Mask of static route This parameter specifies the subnet mask associated
item with the destination network.
This parameter specifies the IP address of the next hop,
Next hop IP of static equivalently, the first gateway through which a packet
route item that is sent from the eNodeB to the destination address
has travelled.
Using a simple unicast route protocol, a static route enables packets to pass through the
next hop or gateway before they can reach the destination network.

For a static route, you must configure the IP address of the destination network, subnet
mask of the destination network, IP address of the next hop, and outgoing port number.
 The first two parameters are used to define the destination network.
 The last two parameters are used to define the path through which data packets
should travel.
5.4.5 Checking OMC Parameters
Purpose
This section describes how to check whether the OMC parameters have been properly
 Knowledge:
You will have to access, configure, or manage an eNodeB through the EMS or a remote
LMT; therefore, you are required to configure the OMC parameters for their communication.
Procedure

Management > Transmission Resource Management > IP Bearing > OMC
Parameter.

Figure 5-18 OMC Parameter Pane
2. In the OMC Parameter pane, choose the desired record, and then right-click
Modify.


3. Check whether the OMC parameters have properly been configured as planned.
Table 5-4 OMC Parameters


This parameter can be set to one of the following values:

 IPINIP: This value indicates dual IP headers in a 2G
or 3G network. When this parameter is set to
IPINIP, you need to configure the IP address of the
gateway. In a 2G or 3G network, when sending a
data packet to the OMC, the BTS encapsulates the
IP header of the EMS in a data unit, then
encapsulates the IP header of the OMC gateway in
the outer layer, and finally sends it to the network
management system. Upon receipt of the data
packet, the BSC discards the IP header of the OMC
Operation and gateway, and then send the data to the EMS.
maintenance channel
 IPOA: This value indicates IP over ATM in a 2G or
type
3G network, that is to say, all IP packets are
transmitted over an ATM link.
 SIGIP: This value indicates a single IP header
because the eNodeB is directly reachable from the
OMC with no need to travel through any interim
path. As a result, when this parameter is set to
SIGIP, you do not need to configure the OMC
gateway IP parameter.
It should be noted that you must set it to SIGIP for an
FDD LTE network; otherwise, the eNodeB will fail to
communicate with the network management system.
NODEB operation and This parameter specifies the IP address that enables the
maintenance IP OMC to communicate with the eNodeB.
This parameter specifies the IP address of the OMC
OMCB server IP
server.
6 Configuring an eNodeB on the

Background
After the configuration file is sync with the foreground, you need to import the
configuration file into the EMS or perform data contra-construction, then configure
adjacent cell parameters, and finally synchronize them from the EMS to the eNodeB.
6.1 Importing the Configuration File from the EMS

Purpose
This section describes how to import the configuration file from the EMS.
Note:

It is recommended to import a configuration file into the EMS to ensure data consistency
between the foreground and the background. If there is no special requirement, any field
engineer is not allowed to perform the data contra-construction function.
Prerequisite
A network element (NE) agent has already been created in the EMS.
Procedure
To import the configuration file from the EMS, you must perform the following steps:
1. Log in to the EMS using the user name, password, and IP address.
2. Click OK. The NetNumen Unified Management System - EMS Client window is
displayed.
3. Choose Configuration > NE Management, right-click the desired NE node, and

select Start NE Management from the dropdown menu.
Figure 6-1 Start NE Management Menu Item
4. Wait for the NE agent to start up, right-click the desired NE node, and select
Configuration Management from the dropdown menu.

Figure 6-2 Configuration Management Menu Item
5. In the Configuration Management pane, right-click the desired NE agent, and then
choose Create > Subnetwork.

Figure 6-3 Subnetwork Dialog Box
6. In the Subnetwork dialog box, set the Alias, SubNetwork ID, and Set of MCC
parameters as required, and then click OK to create an FDD LTE subnetwork. In
this example, an FDD LTE subnetwork is created, for which the name is set to
Shenzhen, ID is set to 100, and subNetwork ID is set to 0 – 4095, as depicted in
Figure 6-4.
Figure 6-4 Creating an FDD LTE Subnetwork
7. In the Configuration Management pane, right-click the FDD LTE subnet, and then
choose Create > Base Station to add a base station.

Figure 6-5 Adding a Base Station
The EMS displays the Base Station dialog box, as shown in Figure 6-6.

Figure 6-6 Base Station Dialog Box
8. In the Base Station dialog box, configure the base station parameters as
summarized in Table 6-1, and then click OK.
Table 6-1 Base Station Parameters
This parameter specifies the name of the base
User Label
station.
This parameter specifies the NE number in the EMS,
ManagedElement ID
ranging from 0 to 65535. By default, it is se to 0.
This parameter specifies the type of the base station.
It can be set to one of the following values:
 ZXSDR BS8900A L200
 ZXSDR BS8906 L200
ManagedElement Type
 ZXSDR BS8800 L200
 ZXSDR BS8900
 ZXSDR B8200 L200
 ZXSDR BS8910A L200

ManagedElement IP This parameter specifies the IP address of the

Address foreground.
This parameter specifies the longitude of the base
Longitude
station.
This parameter specifies the latitude of the base
Latitude
station.
Figure 6-7 shows a typical example of how the previous parameters are configured.
Figure 6-7 General Parameters Tab Page
Figure 6-8 shows that a new base station has been created.

Figure 6-8 Newly Created Base Station
9. In the Configuration Management pane, right-click the newly created base station,
and then select Apply Mutex Right from the dropdown menu to apply for the mutex
right.
Figure 6-9 Apply Mutex Right Menu Item
10. Click Yes when the EMS pops up the Confirm message box.

Figure 6-10 Confirm Message Box
11. In the Configuration Management pane, right-click the newly created base station,
and then select Base Station Configuration Wizard (SDR) from the dropdown
menu to start the base station configuration wizard.
Figure 6-11 Base Station Configuration Wizard (SDR) Menu Item
12. In the Configuration Wizard (Step One: Select Configuration Method) dialog
box, select Configured by Standard Template, and click Next.

Figure 6-12 Configured by Standard Template Option
13. In the Configuration Wizard (Step Two: Choose Data Files) dialog box, click the
button, select the V2.1 configuration file, and then click Open.
Figure 6-13 Configuration Wizard (Step Two: Choose Data Files) Dialog Box
Figure 6-14 shows the configuration file that you need to select from the folder.

Figure 6-14 Selecting the Configuration File
14. Choose the correct configuration file, and then click Open to import the
configuration file into the EMS, as shown in Figure 6-15.
Figure 6-15 Selected Configuration File
15. Wait until the configuration file is successfully imported, that is to say, the EMS
displays the Confirm message box, as shown in Figure 6-16.

Figure 6-16 Confirm Message Box
16. Click Yes to confirm the switch of the configuration set to the master mode, as
Figure 6-17 Success Switch Message Box
17. Click OK to close the message box. The configuration file is successfully imported
from the EMS, as shown in Figure 6-18.
Figure 6-18 Successful Imported Base Station

6.2 Configuring Radio Parameters for an eNodeB

For an eNodeB, the radio parameters must be configured according to the real network
planning data. Radio parameters may include but are not limited to:
 Global Configuration Parameters
 QoS Parameters
 Measurement Parameters
 UE Constant Parameters
 Neighboring Cell Parameters
 Cell Radio Parameters
 Application Parameters
For more information about the descriptions and explanations of radio parameters, refer
to the NetNumen U31 (FDD LTE V2.10.050) NE Management System eNodeB Radio
Parameters Reference.
6.3 Configuring Clock Parameters
6.3.1 Configuring SNTP and Clock Source Parameters
6.3.1.1 Configuring SNTP Parameters
Purpose
This section describes how to configure the SNTP server and time zone.
Note:
After the SNTP server is successfully configured, you need to check whether the SNTP
server is working or not.
If the SNTP server is working, the eNodeB will automatically synchronize the time with the
SNTP server.

If the SNTP server is not working, the eNodeB will not synchronize the time with the SNTP
server, but raise an alarm regarding the time difference between the LMT and the SNTP
server.
Procedure
To configure SNTP parameters, you must perform the following steps:
1. In the left Configuration Management navigation tree, expand the base station
nodes, and then choose Config Set > Platform Equipment Resource > Platform
Physical Resource > Clock and SNTP > SNTP Configuration.
Figure 6-19 SNTP Configuration Pane
2. In the SNTP Configuration pane, click the button to display the SNTP
Configuration dialog box, as shown Figure 6-20.

Figure 6-20 SNTP Configuration Dialog Box
3. In the SNTP Configuration dialog box, configure the SNTP parameters, as shown
in Table 6-2.
Table 6-2 SNTP Parameters
This parameter specifies the IP address of the
SNTP Server IP Address
OMM server.
IP Address of SNTP Standby
This parameter can remain unconfigured.
Server
This parameter specifies the subnet mask
SNTP Server IP Mask associated with the IP address of the OMM
server.
This parameter must be configured, depending
Timezone
on the time zone of the local country.
If this parameter is set to Enable, it means that
the daylight saving time is enabled.
Summer Time Enable Flag
If this parameter is set to Disable, it means that
the daylight saving time is disabled.
Summer Time Offset
Summer Time Start Time
Summer Time End Time

4. Click OK. The SNTP configuration is complete.
Figure 6-21 SNTP Configuration Completion
Network Time Protocol (NTP) is a complicated time synchronization protocol for LANs
and WANs. It can achieve the accurate precision in millisecond (ms).
Simple Network Time Protocol (SNTP) is defined in RFC2030 [Mills 1996]. It is a subnet
of NTP, aiming at the hosts that require avoiding the complexity of NTP. Using the SNTP,
a number of hosts in a LAN synchronizes the time with the NTP host through the Internet,
and then provides time synchronization service for other clients in this LAN.
6.3.1.2 Configuring Clock Source Parameters
Purpose
This section describes how to configure clock source parameters, such as clock
synchronization method, switchover policy, and cascading mode.
Procedure
To configure clock source parameters, you must perform the following steps:
1. Choose Config Set > Platform Equipment Resource > Platform Physical
Resource > Clock and SNTP > Clock Parameter Configuration.

Figure 6-22 Clock Parameter Configuration Pane
2. In the Clock Parameter Configuration pane, click the button to display the
Clock Parameter Configuration dialog box, as shown in Figure 6-23.
Figure 6-23 Clock Parameter Configuration Dialog Box
3. In the Clock Parameter Configuration dialog box, configure the clock source
parameters, as shown in Table 6-3.

Table 6-3 Clock Source Parameters

 Frequency synchronization
 Phase synchronization
When configuring this parameter, you must pay special
attention to the following principles:
 In a single FDD LTE system with the GPS clock
Clock Synchronization source, it is set to Frequency synchronization by
Mode default. However, it can also be set to Phase
synchronization.
 If an FDD LTE system and a TDD LTE system are
collocated in the same subrack with the GPS clock
source, it must be set to Phase synchronization.
 In a single FDD LTE system with the IEEE1588 clock
source, it must be set to Frequency
synchronization.
 Clock source not switch: This value means that the
clock source switchover is not supported.
 Support priority switch: This value means that the
clock source switchover is supported. When clock
source 1 takes precedence over clock source 2 and
clock source 1 is the serving clock source, clock
source 2 takes over if clock source 1 fails. When clock
source 1 is recovered, clock source 1 will take over
again even if clock source 2 does not fail.
Clock Source Switch
Policy  Switch basing on the clock: This value means that
the clock source switchover occurs, depending on the
priority and quality. When clock source 1 takes
precedence over clock source 2 and clock source 1 is
the serving clock source, clock source 2 takes over if
clock source 1 fails. When clock source 1 is
recovered, the switchover is depending on whether
clock source 2 is locked. Specifically, clock source 1
will take over if clock source 2 is unlocked, clock
source 1 will not take over if clock source 2 is locked.
By default, it is set to Support priority switch.


 Unsupport cascading
 Support GNSS Union Output
 Support 1PPS+TOD Channel No.1 Output
 Support 1PPS+TOD Channel No.2 Output
 Support 1PPS+TOD Union Output
Clock output cascade By default, it is set to Unsupport cascading.
mode Support GNSS Union Output: This value means that
the cascading mode supports the GPS, CLONASS, and
compass. It must be set to Support GNSS Union
Output if the GPS clock is in use. Specifically, it must be
set to Support GNSS Union Output if an eNodeB is
equipped with the GPS clock as the primary clock while
another eNodeB receives GPS signals from it as the
secondary clock.
This parameter specifies the cascading output
UCI Cascade output configuration of the UCI board.
config Presently, this parameter is not used for an FDD LTE
system; therefore, it must be set to Invalid.
4. Click OK. The clock source configuration is complete.
Figure 6-24 Clock Source Configuration Completion
When an FDD LTE system and a TDD LTE system are collocated in the same subrack
with the GPS clock, the time splitter connects the GPS clock to the CC board of the FDD
LTE system and the CC board of the TDD LTE system, respectively. Once the CC board
of the FDD LTE system is started, the clock synchronization mode is under the control of

the FDD LTE system. If the GSP clock synchronization mode of the FDD LTE system is
set to Frequency synchronization, the clock synchronization mode of the TDD LTE
system will be ineffective. Consequently, when an FDD LTE system and a TDD LTE
system are collocated in the same subrack with the GPS clock, the clock synchronization
mode must be set to Phase synchronization.
6.3.1.3 Configure Clock Priorities
Purpose
This section describes how to configure the priorities of IEEE1588 and GPS clock
sources.
Procedure
To configure clock priorities, you must perform the following steps:
1. Choose Config Set > Platform Equipment Resource > Platform Physical
Resource > Clock and SNTP > Clock Source Priority.
Figure 6-25 Clock Source Priority Pane
2. In the Clock Source Priority pane, click the button to display the Clock
Source Priority dialog box, as shown in Figure 6-26.

Figure 6-26 Clock Source Priority Dialog Box
3. In the Clock Source Priority dialog box, configure the clock source priority
parameters, as shown in Table 6-4.
Table 6-4 Clock Source Priority Parameters
Clock Source
This parameter identifies the priority of a clock source.
Priority ID


 Inner GNSS
 Outer faceplate planet
 Outer backplate planet
 1PPS+TOD
 GNSS Cascading Clock
 BITS-2MHz clock
 BITS-2Mbps clock
 Line clock-local board
 Line clock-other board
 SyncE+1588 phase modulation
Clock Source Type  Traditional network 1588 frequency modulation
 Traditional network 1588 phase modulation
 SyncE Clock
 1PPS+TOD backup
 RRU Inner GNSS
Currently, an FDD LTE eNodeB can support only two types:
 Inner GNSS: This value means that GPS, GLONASS, and
compass are all supported.
 GNSS Cascading Clock: This value means that GPS,
GLONASS, and compass are cascaded.
Note:
SyncE Clock: This value indicates the Ethernet clock
synchronization mode.
This parameter specifies the clock source priority, ranging
Priority
from 1 to 13.
i. If an eNodeB provides only one IEEE1588 clock source, the Clock Source
Type parameter must be set to Traditional network 1588 frequency
modulation or Traditional network 1588 phase modulation, the Clock
Source Priority ID and Priority parameters must be set to 1, as shown in
Figure 6-27.

Figure 6-27 Only One IEEE1588 Clock Source Configured
ii. If an eNodeB can provide two clock sources (GPS and IEEE1588), you are
required to configure two clock priority records, as summarized in Table 6-5.
Table 6-5 Clock Source Priority Parameters

Clock Source
Clock Source Type Priority Clock Input Cascade Mode
Priority ID
Traditional network 1588
frequency modulation or
1 1 -
Traditional network 1588
phase modulation
When the clock source type
is set to GNSS, it must be
set to Divide Input.
Inner GNSS or GNSS
2 2 When the clock source type
Cascading Clock
is set to GNSS Cascading
Clock, it must be set to
Union Input.

The priority of clock source 1 (IEEE1588) must be set to 1, as shown in Figure 6-28.
Figure 6-28 Clock Source 1 (IEEE1588)
The priority of clock source 2 (GPS) must be set to 2, as shown in Figure 6-29.
Figure 6-29 Clock Source 2 (GPS)

Note:
The serving clock source is clock source 1 because a smaller priority takes precedence over a
greater priority.
iii. When an eNodeB provides only one GPS clock source or works in the GPS
cascading mode, the Clock Source Type and Clock Source Priority ID
parameters must be set to Inner GNSS / Divide Input or GNSS Cascading
Clock / Union Input, the Clock Source Priority ID and Priority parameters
must be set to 1.
Figure 6-30 Only GPS Clock Source

Figure 6-31 GPS Cascading Mode
4. Click OK. The clock source priority configuration is complete.
Figure 6-32 Only IEEE1588 Clock Source Priority Configured

Figure 6-33 Two Clock Source Priorities Configured
Figure 6-34 Only GPS Clock Source Priority Configured

Figure 6-35 Cascading GPS Clock Source Priority Configured
6.3.2 Configuring the IP Clock and PTP Logical Port
This section describes how to configure an IEEE1588 clock. The IEEE1588 clock
protocol is an alternative option of the GPS clock. By employing the time distribution and
time scheduling concepts, this time transmission mechanism is tailor-made to suit a
packet network. A client or device can synchronize the time with the primary clock source
through software scheduling by using a normal oscillator. This process is more simple
and reliable, consumes a little bandwidth. As compared to a GPS clock, it can
dramatically achieve cost-effectiveness as well as provide ease of maintenance. Even if
not totally replaceable of the GPS clock, the IEEE1588 clock can be used as an
alternative option when the GPS satellite is unavailable. An IEEE1588 clock can be
deployed as the primary clock source within a network and another IEEE1588 clock can
be deployed as the secondary clock source for an eNodeB, thereby ensuring
uninterrupted time synchronization.
Note:
If an eNodeB is equipped with a GPS clock source, you can skip this section.
If an eNodeB is equipped with an IEEE1588 clock source, you need to implement the
procedure as described in this section.
Let us suppose that an eNodeB is connected to two IEEE1588 servers in 1+1 mode. This
networking mode is the most commonly used clock solution in an FDD LTE system. In

this networking mode, you need to manually configure two PTP ports and their clock
priorities. If one IEEE1588 server fails, the other IEEE1588 server can take over.
As depicted in Figure 6-36, IEEE1588 servers 1 and 2 are operating in active/standby

mode for load sharing:
 For some eNodeBs, IEEE1588 server 1 acts as the primary clock source while
IEEE1588 server 2 acts as the secondary clock source.
 For other eNodeBs, IEEE1588 server 2 acts as the primary clock source while
IEEE1588 server 1 acts as the secondary clock source.
Figure 6-36 IEEE1588 Clock Networking Mode
Table 6-6 shows a typical PTP port configuration example.
Table 6-6 PTP Port Configuration Example
eNodeB PTP Port

PTP Port 1: IEEE1588 Server 1 (DestIP: 20.2.78.78), priority 1
1
2

6.3.2.1 Configure the IP Clock
Purpose
This section describes how to configure the IP clock.
Procedure
To configure the IP clock, you must perform the following steps:
nodes, choose Config Set > Platform Equipment Resource > Platform
Transmission Resource > Clock Management > IP Clock.
Figure 6-37 IP Clock Pane
2. In the IP Clock pane, click the button to display the IP Clock dialog box, as

Figure 6-38 IP Clock Dialog Box
3. In the IP Clock dialog box, configure the IP clock parameters, as shown in Table
6-7.
Table 6-7 IP Clock Parameters

Used Board This parameter must be set to CC16(1,1,1).
Algorithm Selection This parameter must be set to Standard protocols.
4. Click OK. The IP clock configuration is complete.

Figure 6-39 IP Clock Configuration Completion
6.3.2.2 Configuring the PTP Logical Port
Purpose
This section describes how to configure the PTP logical port.
Note:
The number of PTP logical ports is equivalent to that of IEEE1588 servers connected to the
eNodeB. The priority of each IEEE1588 server is dependent on the PTP link priority.
Procedure
To configure the PTP local port, you must perform the following steps:
nodes, choose Config Set > Platform Equipment Resource > Platform
Transmission Resource > Clock Management > PTP Logical Port.

Figure 6-40 PTP Logical Port Pane
2. In the PTP Logical Port pane, click the button to display the PTP Logical Port
dialog box, as shown in Figure 6-41.
Figure 6-41 PTP Logical Port Dialog Box
3. In the PTP Logical Port dialog box, configure the PTP logical port parameters, as
shown in Table 6-8.

Table 6-8 PTP Logical Port Parameters

PTP
The PTP logical port ID of eNodeB 1 is 1; the PTP logical port ID of
Logical
eNodeB 2 is 2.
Port ID
PTP Port The PTP logical port number of eNodeB 1 is 1; the PTP logical port
No. number of eNodeB 2 is 2.
The IP addresses of two clock sources must be configured for
eNodeBs 1 and 2 as follows:
 eNodeB 1
The IP address of the primary clock source must be set to the IP
address of IEEE1588 server 1 (20.2.78.78); the IP address of the
Destination secondary clock source must be set to the IP address of IEEE1588
IP server 2 (20.2.78.245).
 eNodeB 2
The IP address of the primary clock source must be set to the IP
address of IEEE1588 server 2 (20.2.78.245); the IP address of the
secondary clock source must be set to the IP address of IEEE1588
server 1 (20.2.78.78).
Delay_req  Multicast
packet
sent mode  Unicast
Keep in mind that it must be set to Unicast.
This parameter must be configured as follows:
 eNodeB 1
The PTP link priority of the primary clock source (20.2.78.78) must be
set to 1; the PTP link priority of the secondary clock source
PTP Link
(20.2.78.245) must be set to 2.
Priority
 eNodeB 2
The PTP link priority of the primary clock source (20.2.78.245) must be
set to 1; the PTP link priority of the secondary clock source
(20.2.78.78) must be set to 2.
4. Click OK. The PTP logical port configuration is complete.

Figure 6-42 PTP Logical Port Configuration (eNodeB 1)
Figure 6-43 PTP Logical Port Configuration (eNodeB 2)
6.4 Configuring a Dry Contact

Purpose
This section describes how to configure a dry contact in the EMS, depending on the
actual environmental monitoring configuration on site.

Prerequisites
The eNodeB foreground is properly connected to the dry contact through a cable.
Procedure
To configure a dry contact, you must perform the following steps:
nodes, choose Config Set > Platform Equipment Resource > Platform Physical
Resource > Dry Contact.
Figure 6-44 Dry Contact Pane
2. In the Dry Contact pane, click the button to display the Dry Contact dialog box,

Figure 6-45 Dry Contact Dialog Box
3. In the Dry Contact dialog box, configure the dry contact parameters, as shown in
Table 6-9.
Table 6-9 Dry Contact Parameters
Dry
This parameter specifies a unique identification of a dry contact.
Contact ID
This parameter specifies the board that is connected to a dry contact. If
you want to connect a dry contact to an eBBU, you must set it to SA; if
Used
you want to connect a dry contact to an eRRU, you must set it to the
Board
appropriate board of a corresponding eRRU model, for example, TRF
board for R8880.
This parameter specifies the sequence number of a dry contact. The
dry contact number filled in the EMS is equal to the real dry contact
Dry
number minus 1. For instance, the dry contact number filled in the EMS
Contact
must be 0 for the first dry contact, the dry contact number filled in the
No.
EMS must be 1 for the second dry contact, and the rest can be
deduced by analogy.
 Always open alarm
This alarm will be raised when the pin that matches the dry contact
Alarm
number loses contact with the ground cable.
Status
 Always close alarm
This alarm will be raised when the pin that matches the dry contact
number is short-circuited with the ground cable.

This parameter specifies the alarm code that is corresponding to the

Dry Fault alarm type predefined in the foreground. For instance, if the gate
Code access alarm is predefined for a specific dry contact, you must set it to
Gate Safety Alarm.
4. Click OK. The dry contact configuration is complete.
Figure 6-46 Dry Contact Configuration Completion
5. If you want to add other dry contacts, repeat steps 1 through 4.
When connecting an external device to an eNodeB through the SA board or eRRU, a

user can configure specific alarm parameters to monitor the external device through the
dry contact.
A dry contact can be either disconnected or short-circuited.
 When a dry contact is disconnected, it indicates a high signal level (plus).
 When a dry contact is disconnected, it indicates a low signal level (minus).
6.5 Configuring an Electrical Antenna

Purpose
This section describes how to create an AISG device by importing a configuration file.

Procedure
To configure an electrical antenna, you must perform the following steps:
1. In the left NE Management navigation tree, right-click the NE agent under the EMS
Server node, and then select Aisg Equipment Management from the dropdown
menu.
Figure 6-47 Aisg Equipment Management Menu Item
2. In the Aisg Equipment Management pane, right-click the desired eNodeB to be

configured under the Topology Tree node, and then select Parallel Scan from the
dropdown menu, as shown in Figure 6-48.

Figure 6-48 Parallel Scan Menu Item
3. Wait for the scanning of the AISG device until the EMS displays the scanned results.
Right-click the desired results, and then click the Create button to add them to the
lower right pane so that you can physically operate the AISG device, as shown in
Figure 6-49.
Figure 6-49 Adding the Results

4. In the Create AISG Device dialog box, configure such parameters as AISG ID,
Used Board, and ANT number as required, and then click OK.
Figure 6-50 Create AISG Device Dialog Box
5. Under the Topology Tree node, right-click the desired base station to be configured,
select Query AISG Device from the dropdown menu to query the newly created
AISG device, as shown in Figure 6-51.
Figure 6-51 Query AISG Device Menu Item

6. On the right Query AISG Device tab page, right-click the desired record, and then
select Send Configuration Data from the dropdown menu.
7. When the Open dialog box is displayed, choose the configuration file of the AISG
device, and then click Open to send the configuration file to the AISG device.
In general, Antenna Interface Standards Group (AISG) consists of Remote Electrical Tilt
Unit (RET) and Tower-mounted Amplifier (TMA). Remote Electrical Tilt Unit (RET), also
known as Remote Control Unit (RCU), can be used to remotely control the tilt angle of an
antenna because RET is physically connected to an antenna. If the tilt angle of an
antenna is manually adjusted during the installation, you are unable to query the actual
title angle of the antenna. During the deployment, therefore, you must firstly fine-tune the
RET, and then configure the AISG device through the EMS.
When configuring an AISG device through the EMS, you must pay special attention to the
 You must enable the EMS to output the scanned results by running the AISG device
scanning command; otherwise, you cannot add the AISG device without the
scanned results.
 You must perform the AISG device query after the AISG device has been added;
otherwise, you cannot import the configuration file until the queried results are
outputted.
6.6 Performing Data Synchronization

Purpose
In the case that you have performed critical operations (for example, you have modified
radio parameters of an eNodeB), you are required to synchronize the data that has been
modified through the EMS with the physical boards of the eNodeB. This section
describes how to perform data synchronization.
Procedure
To perform data synchronization, you must perform the following steps:
1. In the Configuration Management pane, right-click the desired base station under
the Configuration Resource Tree node, and then choose Synchronize >
Synchronize All Tables.

Figure 6-52 Synchronize All Tables Menu Item
2. When the Radio Mode Selection dialog box is displayed, select the LTE-FDD
checkbox, and then type the verification code.

Figure 6-53 Radio Mode Selection Dialog Box
3. Click OK. The data synchronization is complete.
Figure 6-54 Data Synchronization Completion
Note:
This procedure will cause the eNodeB to reboot.

7 Troubleshooting eNodeB Alarms

When the data synchronization is successfully completed, you must check whether there
is any alarm raised from the EMS:
 If an alarm is raised, refer to the ZXSDR B8200 L200 (V2.10.050) LTE Baseband
Unit Troubleshooting Guide.
 If no alarm is present, proceed with the verification test for the eNodeB, as
described in the subsequent chapter.
8 Verifying Basic eNodeB Services

This chapter describes how to verify basic eNodeB services. It contains the following
sections:
 Performing a UE Attachment Test (Connection and Release)
 Performing a Ping Test (Uplink and Downlink)
 Performing a UDP Traffic Generation Test (Uplink and Downlink)
 Performing an FTP Test (Uplink and Downlink)
 (Optional) Performing an IEEE1588 Clock Test
 (Optional) Performing a Dry Contact Test
For more information about how to test an eNodeB, refer to the FDD LTE ZXSDR B8200
and R8882 (V2.00.050) Commissioning Test Guide.
8.1 Performing a UE Attachment Test (Connection

and Release)
Table 8-1 UE Attachment (Connection and Release)

Test Purpose:
The purpose of this test is to verify that the UE can successfully establish and release
a connection during the attachment procedure.
Prerequisites:
The eNodeB is already present.
The UE has completed the PLMN and cell selection procedures.
Test Procedure:
1. On the eNodeB side, enable the signaling trace function; on the UE side, verify
that the UE has successfully searched the target cell.
2. Use the UE to access the network.
3. Query the signaling trace results, and then check whether an

S1AP_UplinkNasTransportMsg (Attach Complete) message is present. If yes,
you can infer that has successfully established a connection.
4. Use the UE to release the connection.
5. Query the signaling trace results, and then check whether an

S1AP_UeContextReleaseCompleteMsg message is present. If yes, you can
infer that the UE has successfully released a connection.
Acceptance Criteria:
1. The UE has successfully established a connection.
2. The UE has successfully released a connection.

Remarks:
The signaling flow of the UE attachment is shown as below:
8.2 Performing a Ping Test (Uplink and Downlink)
Table 8-2 Ping Test (Uplink and Downlink)
Test Purpose:
The purpose of this test is to verify that the UE can establish a link with the PDN
residing in the core network.
Prerequisites:
1. The UE has successfully accessed the wireless network.
2. The PDN server has already been configured on the core network.
Test Procedure:
1. Display the command line interface (CLI) on the laptop.
2. Run the ping 20.2.100.189 –t command, where 20.2.100.189 is the IP address of
the PDN server.
3. When the CLI shows Reply from 20.2.100.189 for 20 times, press Ctrl + C to stop
the ping procedure. In this case, you can find average transmission time.
4. Display the command line interface (CLI) on the PDN server.
5. Run the ping 30.40.5.41 –t command, where 30.40.5.41 is the IP address of the
UE.
6. When the CLI shows Reply from 30.40.5.41 for 20 times, press Ctrl + C to stop
the ping procedure. In this case, you can find average transmission time.
The UE can ping the PDN server successfully, that is to say, there are replies from the
destination.
Remarks:
The replies from the uplink are shown as below:
8.3 Performing a UDP Traffic Generation Test (Uplink

and Downlink)
Table 8-3 UDP Traffic Generation Test (Uplink and Downlink)

Test Purpose:
The purpose of this test is to verify that the UE can exchange data with the PDN
server using the UDP.
Prerequisites:
3. Both the PDN server and the laptop on the UE side have been already installed
with the Iperf and DU Meter.
Test Procedure:
1. Display the command line interface (CLI) on the laptop, and then enter the
directory in which Iperf is stored.
2. Run the iperf –u –c 20.2.100.189 –i 1 –t 9999 –b 40m command, where
20.2.100.189 is the IP address of the PDN server.
3. Start the DU Meter on the laptop to monitor the traffic flow of the network card on
the UE side.
4. Display the command line interface (CLI) on the PDN server, and then enter the
directory in which Iperf is stored.
5. Run the iperf –u –c 30.40.5.41 –i 1 –t 9999 –b 40m command, where 30.40.5.41
is the IP address of the UE.
6. Start the DU Meter on the PDN server to monitor the traffic flow of the network card
on the UE side.
The traffic can be successfully generated on both uplink and downlink, that is to say,
the DU Meter can show the traffic flows that are generated from both uplink and
downlink.
Remarks:
1. By running a server on one side and a client on the other side, the UDP traffic
generation test is used to check whether data traffic can be generated between the
server and the client. On the forward link, the UE serves as an Iperf server to
receive traffic and the wireless network serves as a client to send traffic. On the
reverse link, it is inversely true.
The command lines are shown as below:
 Server: iperf -s –u -i 1
 Client: iperf –u -c 10.51.70.44 –b 2.8M -n 10M -i 1

Where,
 -s: server
 -c: client (followed by the IP address of the Iperf server)
 -u: UDP
 -b: bandwidth (bit/s)
 -n: traffic in bytes (-t: time in seconds)
 -i: time interval (-i 1: one display for one second)

2. UDP traffic generation results on the uplink are shown as below:
3. UDP traffic generation results on the downlink are shown as below:
8.4 Performing an FTP Test (Uplink and Downlink)
Table 8-4 FTP Test (Uplink and Downlink)

Test Purpose:
The purpose of this test is to verify that the UE can exchange data with the PDN
server using TCP/IP.
Prerequisites:
3. The PDN server has been already installed with the FTP server (for example
Serv-U) and the laptop on the UE side has been already installed with the FTP
client (for example FileZilla).
4. The laptop on the UE side has already been installed with DU Meter.
Test Procedure:
1. Start the FTP server on the PDN side.
2. Start the FileZilla on the laptop, type the user name, password, IP address, and
port number of the PDN server, and then establish an FTP connection.
3. Upload a file to the FTP server to monitor the traffic flow using DU Meter.
4. Download a file to the UE to monitor the traffic flow using DU Meter.
The files can be successfully uploaded and downloaded, that is to say, the DU Meter
can show the traffic flows that are generated from both uplink and downlink.
Remarks:
1. FTP test results on the uplink are shown as below:
2. FTP test results on the downlink are shown as below:
8.5 (Optional) Performing an IEEE1588 Clock Test

If you have configured any IEEE1588 clock through the EMS, you need to verify that the
IEEE1588 clock can run normally on the eNodeB side.
8.5.1 Detecting the Status of an IEEE1588 Clock
This section describes how to detect the status of an IEEE1588 clock, including:
 Querying the PTP port status
 Querying the sent/received packet status
 Querying the clock status (active or idle)
 Querying the clock status (started or stopped)
8.5.1.1 Querying the PTP Port Status
Purpose
This section describes how to query the PTP port status.
Procedure
To query the PTP port status, you must perform the following steps:
1. Telnet the CC board and pad the MGP program.
For details, refer to section 5.1 “Querying the Version on the Foreground”.
2. Run the BrsPtpShowPtpPortParam 1 command behind the $$ prompt.

$$BrsPtpShowPtpPortParam 1
[682]
[ begin to excel fun:BrsPtpShowPtpPortParam ]
=======PtpPort Param of Logic Port : 1=======
port_exist = 1
port_enable = 1
LinkPriority = 1
port_mode = 9
EthPortId = 1
VlanId = 65535
announce_interval = 0
announce_duration = 30
announce_timeout = 3
sync_interval = -4
sync_duration = 30
delay_req_interval = -4
delay_resp_interval = -4
delay_resp_duration = 30
signaling_interval = 0
signaling_duration = 30
unicast_flag = 1
dlyreq_send_mode = 1
netprotocol = 1
wait_for_req = 1
SrcIP = 335695382
GateWayIP = 335695438
DestIP = 335695438
Qos = 184
TargetPortIdentity = 0-b0-ae-ff-fe-1-90-9e && 1
==============================================
value = 47(0x2f)
[ end to excel fun:BrsPtpShowPtpPortParam ]
Where,
− Port_exist: 1 means that the PTP port is already existent.
− Port_enable: 1 means that the PTP port is already enabled.
− Sync_interval: -4 represents the transmission speed of sync packets

configured in the OMC.
− Unicast_flag: 1 represents the unicast mode.
− Netprotocol: 1 represents the UDP protocol (Netprotocol: 3 represents

IEEE802.3 for layer 2).
8.5.1.2 Querying the Sent/Received Packet Status
Purpose
This section describes how to check whether an eNodeB can exchange data with an
IEEE1588 clock server.
Procedure
To query the sent/received packet status, you must perform the following steps:
2. Run the stt_show_ptp 1 command behind the $$ prompt.

$$stt_show_ptp 1
[682]
[ begin to excel fun:stt_show_ptp ]
=========PTP Packet Static of Logic Port : 1========
Ptp_port_state = 9
ToatlRxPtpCount = 206
RxSigReqCount = 0
RxSigGrantCount = 0
RxSigCancleCount = 0
RxSigCancleAckCount = 0
RxAnnounceCount = 0
RxSyncCount = 98
RxFollowUpCount = 0
RxManagementCount = 0
RxDelayReqCount = 0
RxDelayRespCount = 99
ToatlTxPtpCount = 102
TxSigReqCount = 3
TxSigGrantCount = 0
TxSigCancleCount = 0
TxSigCancleAckCount = 0
TxAnnounceCount = 0
TxSyncCount = 0
TxFollowUpCount = 0
TxDelayReqCount = 99
TxDelayRespCount = 0
TxManagementCount = 0
TxFailCount = 0
============================================================
value = 61(0x3d)
[ end to excel fun:stt_show_ptp ]
You need to check whether the number of RxSyncCount, RxDelayRespCount,

and TxDelayReqCount are all changing:
− If the number of RxSyncCount, RxDelayRespCount, and

TxDelayReqCount are all changing, you can infer that the packets can be
sent and received normally.
− If the number of TxDelayReqCount is constantly changing but the numbers

of both RxSyncCount and RxDelayRespCount remains 0, you can infer
that the link is problematic. In this case, you need to check whether the link
between the eNodeB and the IEEE1588 server is working normally, or you
need to check whether the IP parameters are correctly configured.
8.5.1.3 Querying the Clock Status (Active or Idle)
Purpose
This section describes how to check whether an IEEE1588 clock is locked or not.
Procedure
To check whether an IEEE1588 clock is locked, you must perform the following steps:
2. Run the ShowFreqSync1588Info command behind the $$ prompt.

$$ShowFreqSync1588Info
[682]
[ begin to excel fun:ShowFreqSync1588Info ]
********** Freq Sync 1588 INFO **********
Active Freq Sync 1588 : Active
Master type : 0
SyncInter : -4
Free tick (s): 3805509
Capture tick(s): 3806034
Normal tick (s): 3807043
Hold tick (s): 0
Traced time (s): 1534
************** Ptp Static **************
T1Count = 101622
T2Count = 101623
T3Count = 106279
T4Count = 102030
LoseRate = 0 (Bad:10)
Current IP Clock Status : GOOD
********** Freq Sync 1588 PLL ***********
10M default Dac Value = 32345
10M current Dac = 32341
10M input of DAC = 32341
10M capture1 Dac = 32340
the value of kf = 0.488000
10M PLL Mode = NORMAL

**************** END ********************
value = 0(0x0)
[ end to excel fun:ShowFreqSync1588Info ]
8.5.1.4 Querying the Clock Status (Started or Stopped)
Purpose
This section describes how to check whether an IEEE1588 clock is started or stopped.
Procedure
To check whether an IEEE1588 clock is enabled, you must perform the following steps:
2. Run the Show1588CtrlStatus command behind the $$ prompt.

$$Show1588CtrlStatus
[682]
[ begin to excel fun:Show1588CtrlStatus ]
--------1588 PllCtrl Status----------
RefUseableFlag = 2(1:not ok,2:ok)
RefStatusLastTime = 72158(s)
Brs1588 Abnormal Last Time = 72159(s)
Abis Link State = link ok
Toffset Avaiable Flag = 0
Packet lost Rate = 0
StartFlag = started
StopFlag = Not stop
StartTimes = 1
StopTimes = 1
gul1588WorkingMode = 11(1588 Id)
value = 34(0x22)
[ end to excel fun:Show1588CtrlStatus ]
Where,
− RefUsableFlag: 2 means that the packets can be sent and received

normally.
− StartFlag: started means that the IEEE1588 clock is enabled.
− gul1588WorkingMode: 11 means that the activated clock source is working

in IEEE1588 Frequency Synchronization mode.
8.5.2 1+1 Active/Standby Switchover of an IEEE1588 Clock Server
Table 8-5 1+1 Active/Standby Switchover (Active Clock Source Failure) of an

IEEE1588 Clock Server
Test Purpose:
The purpose of this test is to verify that the 1+1 active/standby switchover can be
performed normally when the active clock source fails.
Prerequisites:
1. IEEE1588 clock servers are configured to be working 1+1 active/standby mode.
2. eNodeB 1 has already been configured with PTP Port 1: IEEE1588 Server 1
(priority 1) and PTP Port 2: IEEE1588 Server 2 (priority 2); eNodeB 2 has already
been configured with PTP Port 1: IEEE1588 Server 2 (priority 1) and PTP Port 2:
IEEE1588 Server 1 (priority 2).
3. IEEE1588 Server 1 is the active clock source of eNodeB 1 and IEEE1588 Server 2
is the active clock source of eNodeB 2.
Test Procedure:
Test Scenario 1
1. Increase the number of lost packets on IEEE1588 server 1 until the packet loss
(15%) exceeds the packet loss threshold (10%). IEEE1588 server 2 takes over
IEEE1588 server 1 for eNodeB 1, but the active clock source of eNodeB 2
remained unchanged.
2. Waive the packet loss test until IEEE1588 server 1 is recovered. The active clock
source of eNodeB 1 is changed back to IEEE1588 server 1, but the active clock
source of eNodeB 2 remained unchanged.
Test Scenario 2
1. Increase the number of lost packets on IEEE1588 server 2 until the packet loss
(15%) exceeds the packet loss threshold (10%). IEEE1588 server 1 takes over
IEEE1588 server 2 for eNodeB 2, but the active clock source of eNodeB 1
remained unchanged.
2. Waive the packet loss test until IEEE1588 server 2 is recovered. The active clock
source of eNodeB 2 is changed back to IEEE1588 server 2, but the active clock
source of eNodeB 1 remained unchanged.
Acceptance Criteria for Test Scenario 1
 Initially, the active clock source of eNodeB 1 is IEEE1588 server 1.
 After the switchover, the active clock source of eNodeB 1 is IEEE1588 server 2.
 After the recovery, the active clock source of eNodeB 1 is IEEE1588 server 1.
 The active clock source of eNodeB 2 is always IEEE1588 server 2.

Acceptance Criteria for Test Scenario 2
 After the switchover, the active clock source of eNodeB 2 is IEEE1588 server 1.
 After the recovery, the active clock source of eNodeB 2 is IEEE1588 server 2.
 The active clock source of eNodeB 1 is always IEEE1588 server 1.

Remarks:
 To query the sent/received packet status, you can run the stt_show_ptp [port
num] command.
 To query the port number of the active clock source, you can run the
BrsPtpShowPtpPortParam [port num] command.
 To query the IEEE1588 clock frequency synchronization status, you can run the
ShowFreqSync1588Info command.
Table 8-6 1+1 Active/Standby Switchover (Modifying or Deleting the Priority of a PTP
Port) of an IEEE1588 Server
Test Purpose:
The purpose of this test is to verify that the 1+1 active/standby switchover can be
performed normally when the priority of a PTP port is modified or deleted.
Prerequisites:
1. IEEE1588 clock servers are configured to be working 1+1 active/standby mode.
2. eNodeB 1 has already been configured with PTP Port 1: IEEE1588 Server 1
(priority 1) and PTP Port 2: IEEE1588 Server 2 (priority 2); eNodeB 2 has already
been configured with PTP Port 1: IEEE1588 Server 2 (priority 1) and PTP Port 2:
IEEE1588 Server 1 (priority 2).
3. IEEE1588 Server 1 is the active clock source of eNodeB 1 and IEEE1588 Server 2
is the active clock source of eNodeB 2.
Test Procedure:
Test Scenario 1
1. Change PTP port 1 of eNodeB 1 to PTP port 3. The active clock source of eNodeB
1 is changed from IEEE1588 server 1 to IEEE1588 server 2.
2. Delete PTP port 1 of eNodeB 1. The active clock source of eNodeB 1 is changed
from IEEE1588 server 1 to IEEE1588 server 2.
Test Scenario 2
1. Change PTP port 1 of eNodeB 2 to PTP port 3. The active clock source of eNodeB
2 is changed from IEEE1588 server 2 to IEEE1588 server 1.
2. Delete PTP port 1 of eNodeB 2. The active clock source of eNodeB 2 is changed
from IEEE1588 server 2 to IEEE1588 server 1.
 After the PTP port is modified or deleted, the active clock source of eNodeB 1 is
changed from IEEE1588 server 1 to IEEE1588 server 1.
 After the PTP port is modified or deleted, the active clock source of eNodeB 2 is
changed from IEEE1588 server 2 to IEEE1588 server 1.
Remarks:
 To query the sent/received packet status, you can run the stt_show_ptp [port
num] command.
 To query the port number of the active clock source, you can run the
BrsPtpShowPtpPortParam [port num] command.
 To query the IEEE1588 clock frequency synchronization status, you can run the
ShowFreqSync1588Info command.
8.6 (Optional) Performing a Dry Contact Test
Table 8-7 Dry Contact Test
Test Purpose:
The purpose of this test is to verify that a dry contact alarm can be raised and
recovered by taking a lightning protection unit (LPU) for example.
Prerequisites:
1. The EMS has been correctly configured with an LPU.
2. The eNodeB has been already connected to the LPU through a dry contact cable.
Test Procedure:
1. Raising a dry contact alarm.
i. Depending on how the Alarm Status parameter is configured in the EMS,

disconnect or short-circuit the alarm cable on the foreground side.
− Disconnect the alarm cable on the foreground side if the Alarm Status
parameter is set to Always open alarm.
− Short-circuit the alarm cable on the foreground side if the Alarm Status
parameter is set to Always close alarm.
ii. In the Alarm Query window, verify that a dry contact alarm is raised.
2. Recovering a dry contact alarm.
i. Depending on how the Alarm Status parameter is configured in the EMS,

disconnect or short-circuit the alarm cable on the LPU side.
− Short-circuit the alarm cable on the LPU side if the Alarm Status
parameter is set to Always open alarm.
− Disconnect the alarm cable on the LPU side if the Alarm Status
parameter is set to Always close alarm.
ii. In the Alarm Query window, verify that the dry contact alarm disappears.
The dry contact alarm can be successfully raised and recovered.
Remarks:
None
AppA How to Use the BCT

Purpose
This section describes how to generate a configuration file using the Batch Configure
Tool (BCT).
Procedure
To generate a configuration file using the BCT, you must perform the following steps:
1. In the directory where the BCT is stored, double-click BCT.jar to start the BCT, as
Figure 8-1 BCT Startup
Tip:
If the BCT fails to start up after you’ve double-clicked BCT.jar, you must reinstall the JRE.
To obtain the JRE installation package, visit
http://www.java.com/en/download/inc/windows_upgrade_ie.jsp.
When running a Windows XP operating system, choose either of the following options:
To run BCT.jar, you can perform the following steps:
1. Display the command line interface (CLI).
2. Enter the directory where BCT.jar is stored.
3. Run the java -jar bct.jar command.
To run BCT.jar, you can also perform the following steps:
1. Record the directory where javaw.exe is stored, for example, C:\Program

Files\Java\jre6\bin\javaw.exe.
2. Right-click *.jar, select Open File, navigate to C:\Program

Files\Java\jre6\bin\javaw.exe, and finally double-click it.
3. If an error message box pops up, saying that the main entrance cannot be found, choose
My Computer > Open or double-click My Computer.
4. In the My Computer window, choose Tools > File Option (O)... > File Type to display
the File Type tab page.
5. Select the JAR file, and then click Advanced to display the Editing File Type dialog
box.
6. In the Editing File Type dialog box, replace the directory with C:\Program
Files\Java\jre6\bin\javaw.exe" -jar "%1, and then click OK.
When running a Windows 7 operating system, you must perform the following steps:
1. Record the directory where javaw.exe is stored, for example, C:\Program

Files\Java\jre6\bin\javaw.exe.
2. Open regedit.exe as an administrator, and then find

HKEY_CLASSES_ROOT\jar_auto_file\shell\open\command.
3. Replace the default character string with "C:\Program Files\Java\jre6\bin\javaw.exe"

-jar "%1". It should be noted that the quotation marks cannot be omitted.
Table 8-8 describes the BCT parameters.
Table 8-8 BCT Parameters

Encryption This parameter specifies whether to encrypt a generated file.
Radio This parameter specifies whether it is an FDD LTE system or a TDD
Mode LTE system.
Excel
This parameter specifies the directory where an Excel file is stored.
Directory
Output This parameter specifies the directory where a configuration file is
Directory stored.
This parameter specifies the directory where the processing
Save Info
information in BCT.xls format is saved.
Process
This parameter outputs the file generation information.
Info
2. Select the Files Encryption checkbox, as shown in Figure 8-2.
Figure 8-2 Files Encryption Checkbox
Note:
If the Files Encryption checkbox is selected, the fast configuration template will be
encrypted. In other words, the character string of the file name will begin with “Enc”, which
can be opened with MINI-EOMS only.
If the Files Encryption checkbox is not selected, the character string of the file name will
not begin with “Enc”, which can be opened with LMT only.
3. Select the FDD checkbox.
4. In the Excel Directory field, click Browse…, choose the desired network planning
worksheet in Excel format, and click Open.
Figure 8-3 Choosing the Network Planning Worksheet
5. Click Check File to check the file for validity, as shown in Figure 8-4.
Figure 8-4 Checking the File for Validity
This validity check is used to check whether the network planning worksheet contains
any invalid data. The user must ensure that all the data in the Excel file are correct by
checking the output information. If this validity check fails, the BCT displays the error
information in the Error Info pane, as shown in Figure 8-5.
Figure 8-5 Error Info Pane
6. In the Output Directory field, click Browse…, and then choose the desired
directory to which the configuration file is outputted.
Figure 8-6 Choosing a Director for Outputting the Configuration File
7. Click OK. The BCT starts generating the configuration file.
Figure 8-7 Generating the Configuration File
The processing information is recorded in the Process Info pane, as summarized in

Table 8-9.
Table 8-9 Field Descriptions in the Process Info Pane
Field Description
Excel Row This field specifies the rows of an Excel file.
SiteName This field specifies the name of a site.
Template
This field specifies the name of the fast configuration template.
Name
Description
This field describes the processing information.
(Process Info)
Proccess
This field indicates whether the file configuration process is
Status
succeeded or failed.
(Process Info)
This field explains why an error message is displayed. For
Error Cause
example, No record of IP ID For Clock in template indicates that
(Error Info)
there is no record of the IP ID For Clock field in the Excel file.
You should
This field prompts the user to add a record in the original file.
add record
If the BCT generates the configuration file successfully, you can find Succeed in the
Proccess Status field, as shown in Figure 8-8.
Figure 8-8 File Generation Succeeded
If the BCT fails to generate the configuration file, you can find Failed in the Proccess
Status field, as shown in Figure 8-9.
Figure 8-9 File Generation Failed
8. When the file generation procedure is complete, the BCT displays the Batch
process tips dialog box, as shown in Figure 8-10.
Figure 8-10 Batch process tips Dialog Box
9. Click Confirm so that you will get a configuration file that is customized for the
desired eNodeB, as shown in Figure 8-11.
Figure 8-11 Customized Configuration File
AppB How to Upgrade the eNodeB Version

This appendix describes how to upgrade V2.0 to V2.1 for an eNodeB. Only 128 M is
reserved for the flash of the CC board in V2.0, but a 256 M file system is used in V2.1.
Therefore, you need to upgrade the eNodeB to an interim version (V2.00.060eP01) so
that you can expand the flash of the CC board to 256 M. Finally, you can upgrade
V2.00.060eP01 to V2.1.
B.1 Upgrading V2.00.050* to V2.00.060eP01
B.1.1 Interim Version Upgrade
Purpose
This section describes how to upgrade V2.00.050* to an interim version

(V2.00.060eP01).
Prerequisites
Before upgrading V2.00.050* to an interim version (V2.00.060eP01), you must meet the
following prerequisites:
1. The laptop that is running the LMT has been already installed with JRE version 6 or
later.
2. The eNodeB is running V2.00.050*.
3. Both the running version (V2.00.050*) and the interim version (V2.00.060eP01)
have been already installed with their respective LMT.
4. The configuration file in *.xml format of V2.00.060eP01 is ready.
Example:
Let us suppose that the eNodeB is running V2.00.050fP03 and the interim version to be
upgraded is V2.00.060eP01. In this case, you are required to duplicate their respective LMT
software for both V2.00.050fP03 and V2.00.060eP01 in your laptop, and prepare the
configuration file for V2.00.060eP01.
Procedure
To upgrade V2.00.050* to an interim version (V2.00.060eP01), you must perform the

following steps:
1. Connect your laptop to the DEBUG port of the CC board, as shown in Figure 8-12.
Figure 8-12 Connecting your Laptop to the eNodeB
2. Configure the IP address of the LMT in the same network segment as the IP
address of the DEBUG port (192.254.1.16).
3. Configure the subnet mask of the LMT as same as the DUBUG port of the CC board
(255.255.0.0), and leave the gateway defaulted.
4. Log in to the eNodeB through the LMT on your laptop by double-clicking EOMS.jar
in the X:\LMT\EOMS_EFMS\EOMS.jar directory.
5. In the LMT-OMS Login dialog box, type the user name (root), password (default),
and IP address (DEBUG port), and then click OK, as shown in Figure 8-13.
Figure 8-13 LMT-OMS Login Dialog Box
6. On the left navigation tree of the EMOS window, choose Configuration

Management > Version Management > Version Management to query the
running version, as shown in Figure 8-14.
Figure 8-14 Querying the Running Version of the eNodeB
7. In the Version Management pane, right-click the desired software package from
the Base Station field, and then select Download from the dropdown menu, as
Figure 8-15 Download Menu Item
8. In the open dialog box, select two interim version packages to be downloaded,
including a product version package and a platform version package. In this
example, both LTE-FDD-SW-B8200-L200-V2.00.060eP01.9bit.pkg and
PLAT-SW-B8200-L200-V2.00.060eP01.singlectrl.pkg need to be downloaded.
Figure 8-16 Selecting Two Interim Software Version Packages to Be Downloaded
Note:
Depending on the model of an eRRU, you can download the product version package as
follows:
1. If R8880 is used, download the xxx.15bit.pkg file, where xxx represents the product
version number.
2. If R8882 or any other model is used, download the xxx.9bit.pkg file, where xxx
represents the product version number.
The platform version packages of V2.00.060eP01 can be categorized into two groups: single
control (single mode) or dual control (dual mode).
1. If the eNodeB is configured as a single mode, download the xxx.singlectrl.pkg file.
2. If the eNodeB is configured as a dual mode (FDD + TDD), download the

xxx.dualctrl.pkg file.
9. Click Open and the LMT starts downloading the software version packages, as
Figure 8-17 Downloading the Software Version Packages
10. Wait until the software version packages have successfully been downloaded, that
is to say, the Download Result dialog box displays successful results, as shown in
Figure 8-18.
Figure 8-18 Download Result Dialog Box
11. Click Confirm and the EMS returns to the Version Management pane, as shown in
Figure 8-19.
Figure 8-19 Version Management Pane
12. Right-click two interim software version packages, and then select Activate from
the dropdown menu.
13. In the Activate dialog box, select the Reset Base Station automatically after
activation and Select configuration data. If not, will use default data on
eNodeB checkboxes, and then click the button to add the configuration
templates of two interim versions, as shown in Figure 8-20.
Figure 8-20 Adding the Configuration Templates
Note:
When upgrading the eNodeB through the LMT, you must activate the appropriate
configuration template in *.xml format.
14. Click Confirm and the EOMS displays the Succeed in activating... message box,
Figure 8-21 Activation Success Message Box
15. Click OK and wait for the eNodeB to be automatically restarted. Do not perform any
operation during the restart (If the LMT is interruptted for two times, you can regard
them as normal operations).
16. Log in to the eNodeB again through the LMT of the interim version.

Management > Version Management > Version Management.
18. Query the running version to verify that the eNodeB has already been upgraded to
the interim version, as shown in Figure 8-22.
Figure 8-22 Verifying the Upgrade to the Interim Version
The procedure for upgrading an eNodeB from version A to version B is summarized as

follows:
1. Connect the LMT of version A to the eNodeB of version A.
2. Download version B to the LMT of version A.
3. Activate version B on the LMT of version A
Note:
When activating version B on the LMT of version A, you must use the configuration file of
version B.
4. Connect the LMT of version B to the eNodeB of version B, query the version status,
and finally verify that all the boards are running version B.
B.1.2 Upgrading the BOOT Version of the CC Board from V2.00.050* to

V2.00.060eP01
B.1.2.1 Querying Available Space for the Flash of the CC Board
Purpose
This section describes how to check whether the available space of the flash of the CC
board is sufficient for version upgrade.
Procedure
To upgrade the CC BOOT version from V2.00.050 to V2.00.060eP01, you must perform
the following steps:
1. Run the cmd.exe command to display the command line interface (CLI).
2. Run the telnet 192.254.xxx.16 command to log in to the CC board (192.254.xxx.16,

where xxx is the slot number of the CC board, such as 192.254.1.16 when the CC
board is inserted in slot 1).
3. Type the user name (zte) and password (zte).
4. Run the df –k command in the # prompt to query the available space in the flash of
the CC board. In this example, the flash of the CC board is 110592. Therefore, you
need to upgrade the BOOT.
# df –k
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 511940 100608 411332 20% /dev/shm
/dev/mtdblock0 110592 59556 51036 54% /mnt/flash
#
Note:
1. The original flash of the CC board provides only 128M; however, 256 M is required for
V2.1.
2. The file system of V2.1 requires 256 M, and therefore you must upgrade the BOOT of
the CC board at first, in order to upgrade V2.0 to V2.1.
B.1.2.2 Upgrading the BOOT Version of the CC board
Purpose
This section describes how to upgrade the BOOT version of the CC board from
V2.00.050* to V2.00.060eP01 so that the flash of the CC board can be expanded to an
available space of 256 M.
Prerequisites
The eNodeB has been already upgraded from V2.00.050* to V2.00.060eP01.
Procedure
To upgrade the BOOT version of the CC board, you must perform the following steps:
1. The BOOT version upgrade is similar to the eNodeB version upgrade. Firstly, log in
to the eNodeB through the LMT (V2.00.060eP01); secondly, download the BOOT
version. In this example, we download PLAT-FW-B8200-L200-V2.00.060eP01.pkg,
Figure 8-23 Downloading the BOOT Version
2. Click Open and the LMT starts downloading the BOOT version package. When the
download is complete, the Download Result dialog box displays the final results, as
Figure 8-24 Successful Downloading Results
3. In the Base Station field, right-click the desired firmware version package, and then
select Activate from the dropdown menu to activate the interim firmware version, as
Figure 8-25 Activating the Interim Firmware Version
4. In the Activate dialog box, choose CC in the Standby field, and then click the
button to activate the BOOT version of the CC board, as shown in Figure
8-26.
Figure 8-26 Activate Dialog Box
5. Click Confirm and the confirmation message box is displayed.
Figure 8-27 Confirm Button
Figure 8-28 Confirmation Message Box
6. Click OK, and the eNodeB communication progress is displayed.
Figure 8-29 eNodeB Communication Progress
When the BOOT version of the CC board is successfully activated, the Query Activation
Result dialog box is displayed to show the final results, as shown in Figure 8-30.
Figure 8-30 Query Activation Result Dialog Box
7. Click Confirm and a message box will be displayed to ask you whether to restart
the eNodeB. Click OK to restart the eNodeB, as shown in Figure 8-31.
Figure 8-31 eNodeB Restart Confirmation
After the eNodeB is successfully restarted, a success message box is displayed.
Figure 8-32 eNodeB Restart Success
8. Log in to the eNodeB through the LMT, repeat steps 3 through 7 to reactivate the
BOOT version of the CC board and restart the eNodeB, as shown in Figure 8-33.
Figure 8-33 Reactivating the BOOT version and Restarting the eNodeB
9. Wait until the eNodeB is successfully restarted for the second time. Run the
cmd.exe command to display the command line interface (CLI). Run the telnet
192.254.xxx.16 command to log in to the CC board. Run the reboot command
behind the # prompt to manually restart the eNodeB for the third time.
C:\Documents and Settings\Administrator>telnet 192.254.1.16
(none) login: zte
Password:
Processing /etc/profile... Done
# reboot
The system is going down NOW.
sending SIGTERM to all processes
When upgrading the BOOT version of the CC board, you need to activate the BOOT
version for two times and restart the eNodeB for three times. When activating the BOOT
version and restarting the eNodeB, you must pay special attention to the following
principles:
 Every time when you activate the BOOT version, you need to manually reset the
eNodeB if the eNodeB is not automatically restarted.
 You are not allowed to proceed with the next step until all the eRRUs and all the
cells of the eNodeB have been running normally.
 After you have activated the BOOT version for two times and restarted the eNodeB
for two times, you need to manually restart the eNodeB for the third time through the
CLI.
 In most cases, the BOOT version will be successfully upgraded after you have
activated the BOOT version for two times and restarted the eNodeB for three times.
In rare cases, you need to reset the eNodeB for several more times.
 All in all, you can verify that the BOOT version is successfully upgraded by checking
whether the flash of the CC board has reached 256 M.
B.1.2.3 Querying Available Space after Expanding the Flash of the CC Board
Purpose
This section describes how to verify that the flash of the CC board has reached 256 M.
Procedure
To verify that the flash of the CC board has reached 256 M, you must perform the
following steps:
1. Run the cmd.exe command to display the command line interface, and then run the
telnet 192.254.xxx.16 command to log in to the CC board.
2. Run the df –k command behind the # prompt to query the available space of the
flash. In this example, the flash of the CC board is 241664, which indicates that the
BOOT version of the CC board is successfully upgraded to V2.1.
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 511428 135068 376360 26% /dev/shm
/dev/mtdblock0 241664 85544 156120 35% /mnt/flash
/dev/memblk 3963 35 3724 1% /mnt/ram0
#
B.2 Upgrading V2.00.060eP01 to V2.10.050e

Purpose
This section describes how to upgrade the eNodeB from V2.00.060eP01 to V2.10.050e
(including both software version and BOOT version).
Prerequisites
Before upgrading the eNodeB from V2.00.060eP01 to V2.10.050e, you must meet the
following prerequisites:
1. The eNodeB is running V2.00.060eP01 and the available space of the flash of the
CC board is 256 M.
2. Both the running version (V2.00.060eP01) and the target version (V2.10.050e) have
been already installed with their respective LMT.
3. The configuration file in *.xml format of V2.10.050e is ready.
Note:
Before upgrading the eNodeB from V2.00.060eP01 to V2.10.050e, you must ensure that the
eRRU is running V2.00.060eP01; otherwise, you may fail to detect the eRRU after the
upgrade is complete.
Procedure
To upgrade the eNodeB from V2.00.060eP01 to V2.10.050e, you must perform the
following steps:
1. The upgrade procedure is similar to that is described in section B.1.1 “Interim

Version Upgrade”.
i. Log in to the eNodeB through the LMT (V2.00.060eP01), and then display the
Version Management window.
ii. Download the single control (single mode) software package or the dual
control (dual mode) software package based on the real situation. In this
example, two single control software packages are to be downloaded, as
Figure 8-34 Downloading a Single or Dual Control Software Package
iii. Activate two software version packages in V2.10.050e, as shown in Figure

8-35.
Figure 8-35 Activating Two Software Version Packages in V2.10.050e
iv. Select the configuration files in V2.10.050e, as shown in Figure 8-36.
Figure 8-36 Selecting the Configuration Files in V2.10.050e
v. Wait until the eNodeB is successfully restarted.
vi. Log in to the eNodeB through the LMT (V2.10.050e), query the running version
of the eNodeB, and verify that the eNodeB has been already upgraded to
V2.10.050e, as shown in Figure 8-37.
Figure 8-37 Verifying the Upgrade from V2.0 to V2.1
2. Upgrade the BOOT version of each board such as CC, BPL, and TRF to V2.10.050e
by following the normal upgrade procedure.
i. Log in to the eNodeB through the LMT (V2.1), and then display the Version
Management window.
ii. Download the single control (single mode) software package or dual control
(dual mode) software package based on the real situation. In this example, a
single control software package is to be downloaded, as shown in Figure 8-38.
Figure 8-38 Downloading a Single or Dual Control Software Package
iii. Activate the firmware version package in V2.1, as shown in Figure 8-39.
Figure 8-39 Activating the Firmware Version Package in V2.1
iv. Activate the BOOT versions of the CC, BPL, and TRM boards, as shown in
Figure 8-40.
Figure 8-40 Activating the BOOT versions of the CC, BPL, and TRM Boards
v. Wait until the eNodeB is successfully restarted.
vi. Verify that the eNodeB has been already upgraded to V2.10.050e, as shown in
Figure 8-37.
There are two types of V2.10.050e packages:
 Single control version package (only one CC16 board for a single mode)
 Dual control version package (two CC16 boards for FDD and TDD respectively, for
example, Hi3G project)
Table 8-10 summarizes the single control version packages.
Table 8-10 Single Control Version Packages
Path Version File Name
 LTE-FDD-SW-B8200-L200-V2.10.050e.9bit.pkg
\V2.10.050e\enodeb\Versi  LTE-FDD-SW-B8200-L200-V2.10.050e.15bit.pkg
onNo
 PLAT-FW-B8200-L200-V2.10.050e.singlectrl.pkg
 PLAT-SW-B8200-L200-V2.10.050e.singlectrl.pkg
Table 8-11 summarizes the dual control version packages.
Table 8-11 Dual Control Version Packages
Path Version File Name
 LTE-FDD-SW-B8200-L200-V2.10.050e.9bit.pkg
\V2.10.050e\enodeb\Versi  LTE-FDD-SW-B8200-L200-V2.10.050e.15bit.pkg
onNo
 PLAT-FW-B8200-L200-V2.10.050e.dualctrl.pkg
 PLAT-SW-B8200-L200-V2.10.050e.dualctrl.pkg
AppC How to Contra-Construct the

Configuration Data
Purpose
This section describes how to contra-construct the configuration data from the foreground
to the EMS.
Note:
1. This data contra-construction approach can be used only when no data is configured in
the EMS, that is to say, no available link has ever been established for the eNodeB. In any
other case, you are not allowed to use this approach, especially in any commercially running
eNodeBs.
2. If the configuration file does not contain all required site information, you are not
allowed to use this data contra-construction approach.
Prerequisites
Before contra-constructing the configuration data from the foreground to the EMS, you
must meet the following prerequisites:
1. The configuration file has been already synchronized with the eNodeB through the
LMT on the foreground.
2. The EMS has successfully established a link with the eNodeB.
Procedure
To contra-construct the configuration data from the foreground to the EMS, you must
perform the following steps:
1. In the Configuration Management pane, right-click the desired base station under
the Configuration Resource Tree node, and then choose Base Station
Configuration Wizard (SDR) from the dropdown menu to start the eNodeB
configuration wizard, as shown in Figure 8-41.
Figure 8-41 Base Station Configuration Wizard (SDR) Menu Item
2. In the Configuration Wizard (Step One: Select Configuration Method) dialog

box, select the Configured by Base Station data checkbox, as shown in Figure
8-42.
Figure 8-42 Configured by Base Station data Checkbox
3. Click Next and the EMS displays the Parallelly Online Upload Data Result dialog
box, as shown in Figure 8-43.
Figure 8-43 Parallelly Online Upload Data Result Dialog Box
4. Wait for the eNodeB uploading the configuration data to the EMS.
− When the Result field displays Processing, it indicates that the eNodeB is
uploading the configuration data to the EMS.
− When the Result field displays Success, it indicates that the eNodeB has
successfully uploaded the configuration data to the EMS.
5. When the Result field displays Success, select the Switch to Master checkbox,
and then click OK.
Figure 8-44 Switch to Master Checkbox
Note:
This step enables the EMS to generate a new configuration set based on the
contra-constructed configuration data and then switch this new configuration set to the active
state.
6. Wait until the new configuration set has successfully switched over, that is to say,
the Detailed Info field displays the Command executed successfully syntax.
Figure 8-45 Command executed successfully Syntax
7. The data contra-construction procedure is complete.

FDD LTE ENodeB (V2.10) Commissioning Configuration Guide - R1.0

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

FDD LTE ENodeB (V2.10) Commissioning Configuration Guide - R1.0

Caricato da

Copyright:

Formati disponibili

FDD LTE eNodeB (V2.

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. I

Product Version Document Version Serial Number Reason for Revision

Date Document Version Prepared by Reviewed by Approved by

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. II

Intended audience: FDD LTE eNodeB Technical Support Personnel

2 Introduction to an eNodeB ............................................................................. 2

3 Preparing for Commissioning and Debugging an eNodeB ....................... 15

5 Commissioning an eNodeB from the Foreground ..................................... 32

6 Configuring an eNodeB on the Background............................................... 56

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. IV

6.3.1 Configuring SNTP and Clock Source Parameters ........................................... 68

7 Troubleshooting eNodeB Alarms .............................................................. 100

8 Verifying Basic eNodeB Services .............................................................. 100

AppA How to Use the BCT ................................................................................... 115

AppB How to Upgrade the eNodeB Version........................................................ 125

AppC How to Contra-Construct the Configuration Data .................................... 150

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. V

Figure 2-1 Typical FDD LTE Networking Mode .................................................................... 3

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. VI

Figure 6-1 Start NE Management Menu Item ................................................................... 57

Figure 6-36 IEEE1588 Clock Networking Mode ................................................................. 84

Figure 8-17 Downloading the Software Version Packages ............................................... 130

Table 1-1 Product Version.................................................................................................... 1

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. IX

Table 2-1 Basic Knowledge about an eNodeB ..................................................................... 2

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. X

Table 6-5 Clock Source Priority Parameters....................................................................... 78

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. XI

1.1 About This Guide

1.2 Product Version

Table 1-1 Product Version

Table 1-2 Terminologies

Terminology Full Name

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 1

SCTP Stream Control Transmission Protocol

Table 2-1 Basic Knowledge about an eNodeB

2.1 Typical FDD LTE Networking Modes

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 2

Figure 2-1 Typical FDD LTE Networking Mode

Table 2-2 Functions and Connections of FDD LTE Network Devices

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 3

 Connecting an eBBU to an eRRU through optical fibers

− To connect an eBBU to an eRRU through optical fibers, insert one optical

− To check whether a transmitting or receiving port is properly connected, you

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 4

Currently, the dual-core optical fiber is widely used on site.

 Connecting an eNodeB to an EPC

In most commercial networks, an eNodeB is connected to an electrical switch using an

2.2 Key Components of an eNodeB

Table 2-3 summarizes common models of an eBBU and an eRRU.

Table 2-3 Common Models of an eBBU and an eRRU

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 5

2.2.1 Key Components of an eBBU

Figure 2-2 Appearance of a ZXSDR B8200 L200

Table 2-4 Components and Functions of a ZXSDR B8200 L200

No. Components Functions

ZTE Confidential Proprietary © 2013 ZTE CORPORATION. All rights reserved. 6

The CC board can provide the following functions:

2.2.2 Key Components of an eRRU

The appearance of a ZXSDR R8882 L268 is shown in Figure 2-3.

Figure 2-3 Appearance of a ZXSDR R8882 L268

Table 2-5 Components and Functions of a ZXSDR R8882 L268