NodeB Commissioning Guide (V100 - 04)

NodeB
V100
Commissioning Guide
Issue 04
Date 2009-06-30
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

NodeB
Commissioning Guide Contents
Contents
About This Document.....................................................................................................................1

1 Changes in the NodeB Commissioning Guide....................................................................1-1
2 Safety Information.....................................................................................................................2-1
2.1 Overview.........................................................................................................................................................2-1
2.1.1 Safety Precautions..................................................................................................................................2-1
2.1.2 General Requirements............................................................................................................................2-1
2.2 Electricity Safety.............................................................................................................................................2-3
2.3 Inflammable Environment...............................................................................................................................2-6
2.4 Battery.............................................................................................................................................................2-7
2.4.1 Storage Battery.......................................................................................................................................2-7
2.4.2 Lithium Battery......................................................................................................................................2-9
2.5 Electromagnetic Field Exposure.....................................................................................................................2-9
2.5.1 Introduction............................................................................................................................................2-9
2.5.2 Limits and Guidelines on Exposure to Electromagnetic Fields.............................................................2-9
2.5.3 Location of Base Station Antennas......................................................................................................2-10
2.5.4 Exclusion Zones...................................................................................................................................2-10
2.5.5 Guidelines on Arranging Antenna Sites...............................................................................................2-11
2.5.6 Location of Base Transceiver Station..................................................................................................2-11
2.5.7 Prediction of the Exposure to Electromagnetic Fields.........................................................................2-11
2.5.8 Laser.....................................................................................................................................................2-12
2.6 Working at Heights.......................................................................................................................................2-13
2.6.1 Weight Lifting......................................................................................................................................2-13
2.6.2 Safety Guide on Ladder Use................................................................................................................2-14
2.7 Mechanical Safety.........................................................................................................................................2-15
2.8 Miscellaneous................................................................................................................................................2-16
3 NodeB Commissioning Resources..........................................................................................3-1

4 Procedure for Commissioning the NodeB............................................................................4-1
5 Upgrading the NodeB Software and Downloading the Data Configuration File.........5-1
5.1 Setting the IP Address of the NodeB LMT PC...............................................................................................5-2
5.2 Locally Connecting the NodeB LMT PC to the NodeB.................................................................................5-4
5.2.1 Locally Connecting the NodeB LMT PC to the NMPT.........................................................................5-4
Issue 04 (2009-06-30) Huawei Proprietary and Confidential i

NodeB
Contents Commissioning Guide
5.2.2 Locally Connecting the NodeB LMT PC to the BBU3806...................................................................5-5

5.2.3 Locally Connecting the NodeB LMT PC to the BBU3806C.................................................................5-6
5.3 Locally Logging In to the NodeB on the NodeB LMT...................................................................................5-7
5.4 Upgrading the NodeB Software......................................................................................................................5-9
5.4.1 Checking the NodeB Software Version...............................................................................................5-10
5.4.2 Downloading the NodeB BootROM....................................................................................................5-11
5.4.3 Activating the NodeB BootROM.........................................................................................................5-14
5.4.4 Downloading the NodeB Software......................................................................................................5-16
5.4.5 Activate the NodeB Software...............................................................................................................5-19
5.5 Downloading the NodeB Data Configuration File........................................................................................5-22
5.6 Resetting the NodeB......................................................................................................................................5-24
5.6.1 Resetting the Macro NodeB.................................................................................................................5-24
5.6.2 Resetting the Distributed NodeB..........................................................................................................5-25
6 Checking the Connection for NodeB Networking..............................................................6-1

6.1 Checking the Connection Between the Macro NodeB and the RRU..............................................................6-2
6.1.1 Checking the Consistency in Connection and Data Configuration of the Macro NodeB......................6-2
6.1.2 Checking the Links Between the Macro NodeB and the RRU..............................................................6-3
6.2 Checking the Networking and Link Status of the DBS3800..........................................................................6-3
6.2.1 Checking the Consistency Between Actual Networking and Data Configuration of the DBS3800......6-4
6.2.2 Checking the Links Between the BBU and the RRU.............................................................................6-4
6.3 Checking the Connection for the iDBS3800 Networking...............................................................................6-5
6.3.1 Checking the Consistency Between Actual iDBS3800 Networking and Data Configuration...............6-5
6.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU..........................................................6-6
7 Checking Transmission Status on the Iub Interface...........................................................7-1

7.1 Checking E1/T1 Transmission Status on the Iub Interface.............................................................................7-2
7.2 Checking Optical Transmission Links on the Iub Interface............................................................................7-3
7.3 Checking Ethernet Transmission Links on the Iub Interface..........................................................................7-5
8 Checking the Running Status of the NodeB.........................................................................8-1

8.1 Commissioning SNTP.....................................................................................................................................8-2
8.2 Checking the Status of a Cell..........................................................................................................................8-3
8.3 Measuring RTWP............................................................................................................................................8-3
8.3.1 Measuring the RTWP of the Macro NodeB...........................................................................................8-3
8.3.2 Measuring the RTWP of the Distributed NodeB...................................................................................8-5
8.4 Monitoring Output Power...............................................................................................................................8-6
8.4.1 Monitoring Output Power of the MTRU................................................................................................8-6
8.4.2 Monitoring the Output Power of the RRU/pRRU..................................................................................8-7
9 Measuring the NodeB VSWR..................................................................................................9-1

10 Commissioning the Alarm Equipment of NodeB...........................................................10-1
10.1 Adding the Alarm Equipment to the NodeB...............................................................................................10-2
10.1.1 Adding the Alarm Equipment to the BTS3812E...............................................................................10-2
ii Huawei Proprietary and Confidential Issue 04 (2009-06-30)

NodeB
Commissioning Guide Contents
10.1.2 Adding the Alarm Equipment to the BTS3812AE.............................................................................10-4

10.1.3 Adding the Alarm Equipment to the Distributed NodeB...................................................................10-5
10.2 Setting External Alarms of the NodeB........................................................................................................10-6
10.2.1 Setting the External Alarm Port of the BTS3812E............................................................................10-6
10.2.2 Setting the External Alarm Port of the BTS3812AE.........................................................................10-8
10.2.3 Setting External Alarm Port of the Distributed NodeB......................................................................10-9
10.3 Checking the External Alarm Port of NodeB............................................................................................10-13
11 Checking the ALD..................................................................................................................11-1

11.1 Checking the RET Antenna.........................................................................................................................11-2
11.1.1 Setting the ALD Power Switch..........................................................................................................11-3
11.1.2 Adding ALDs.....................................................................................................................................11-3
11.1.3 Downloading the Data Configuration File of the RET Antenna........................................................11-4
11.1.4 Calibrating the RET Antenna.............................................................................................................11-4
11.1.5 Setting the Downtilt of the RET Antenna..........................................................................................11-5
11.1.6 Querying the Current Downtilt of the RET Antenna.........................................................................11-6
11.1.7 MML Commands Related to the RET Antenna.................................................................................11-6
11.2 Checking the STMA....................................................................................................................................11-7
11.2.1 Setting the ALD Power Switch..........................................................................................................11-8
11.2.2 Adding ALDs.....................................................................................................................................11-8
11.2.3 Setting the Gain of the STMA............................................................................................................11-9
11.2.4 Querying the Gain of the STMA........................................................................................................11-9
11.2.5 MML Commands Related to the STMA............................................................................................11-9
12 Handling Alarms During Commissioning NodeB..........................................................12-1

13 Testing NodeB Services with a UE.....................................................................................13-1
14 NodeB Commissioning FAQs..............................................................................................14-1
14.1 Common Causes to LMT Failure to Locally Connect the NodeB..............................................................14-3
14.2 Common Causes to Failure to Download the NodeB Data Configuration File..........................................14-3
14.3 Failure to Perform a CQT............................................................................................................................14-4
14.4 Common Causes to the ALD Current Abnormal Alarm.............................................................................14-4
14.5 ALD Information to Be Collected for Troubleshooting..............................................................................14-5
14.6 Failure to Set the Downtilt of the RET Antenna.........................................................................................14-5
14.7 FE Port in DOWN State..............................................................................................................................14-6
14.8 PPP Link in DOWN State...........................................................................................................................14-6
14.9 Faulty NCP and CCPs.................................................................................................................................14-7
14.10 Faulty E1 Links.........................................................................................................................................14-8
14.11 Removal of a Cell After Setup..................................................................................................................14-8
14.12 Repeated Establishment and Removal of the CCH After Cell Setup........................................................14-9
14.13 Removal of the Common Channel Upon Call Initiation...........................................................................14-9
14.14 Failure to Activate the HSDPA Service..................................................................................................14-10
14.15 Alarms Related to RET/STMA Links.....................................................................................................14-11
15 Data Sheet for NodeB Commissioning..............................................................................15-1
Issue 04 (2009-06-30) Huawei Proprietary and Confidential iii

NodeB
Contents Commissioning Guide
Index.................................................................................................................................................i-1
iv Huawei Proprietary and Confidential Issue 04 (2009-06-30)

NodeB
Commissioning Guide Figures
Figures
Figure 2-1 Wearing an ESD wrist strap...............................................................................................................2-6

Figure 2-2 Weight lifting....................................................................................................................................2-14
Figure 5-1 IP addresses in remote maintenance mode.........................................................................................5-2
Figure 5-2 Connecting LMT PC and NMPT in local maintenance mode............................................................5-5
Figure 5-3 Connecting LMT PC and BBU3806 in local maintenance mode.......................................................5-6
Figure 5-4 Connecting LMT PC and BBU3806C in local maintenance mode....................................................5-7
Figure 5-5 User Login dialog box........................................................................................................................5-8
Figure 5-6 Switching the language.......................................................................................................................5-9
Figure 5-7 Software Update dialog box.............................................................................................................5-12
Figure 5-8 Software Upgrade dialog box.........................................................................................................5-13
Figure 5-9 FTP Setting dialog box.....................................................................................................................5-13
Figure 5-10 Software Update dialog box .........................................................................................................5-15
Figure 5-11 Upgrade BOOTROM dialog box...................................................................................................5-16
Figure 5-12 Software upgrade dialog box........................................................................................................5-17
Figure 5-13 Upgrade NodeB Software dialog box..........................................................................................5-18
Figure 5-14 FTP Setting dialog box..................................................................................................................5-18
Figure 5-15 Software Update dialog box...........................................................................................................5-20
Figure 5-16 Upgrade NodeB Software dialog box.............................................................................................5-21
Figure 5-17 DataConfig File Transfer dialog box..............................................................................................5-22
Figure 5-18 FTP Setting dialog box...................................................................................................................5-23
Figure 7-1 Physical loopback of E1/T1s on the DDF..........................................................................................7-3
Figure 8-1 RTWP Measurement dialog box......................................................................................................8-4
Figure 8-2 RTWP Measurement dialog box......................................................................................................8-5
Figure 8-3 Output Power Monitoring dialog box.............................................................................................8-7
Figure 8-4 Output Power Monitoring dialog box.............................................................................................8-8
Issue 04 (2009-06-30) Huawei Proprietary and Confidential v

NodeB
Commissioning Guide Tables
Tables
Table 2-1 Fuse description...................................................................................................................................2-5

Table 2-2 Different regulations and reference....................................................................................................2-10
Table 3-1 Tools required for commissioning.......................................................................................................3-1
Table 5-1 IP parameters of the LMT PC for commissioning on the NodeB side................................................5-3
Table 5-2 IP parameters of the LMT PC for commissioning on the NodeB side................................................5-3
Table 5-3 Fields in the User Login dialog box.....................................................................................................5-8
Table 5-4 Fields in the FTP Setting dialog box................................................................................................5-14
Table 10-1 Parameters of the subrack................................................................................................................10-2
Table 10-2 Parameters of the board....................................................................................................................10-3
Table 10-3 Parameters of the board....................................................................................................................10-3
Table 10-4 Setting parameters of the board........................................................................................................10-4
Table 10-5 Parameters of the subrack................................................................................................................10-5
Table 10-6 Setting parameters of the board........................................................................................................10-6
Table 10-7 Setting parameters of the Boolean alarm port..................................................................................10-7
Table 10-8 Setting parameters of the analog alarm port.....................................................................................10-8
Table 10-9 Setting parameters of the Boolean alarm port..................................................................................10-9
Table 10-10 Setting the parameters of the Boolean alarm port........................................................................10-10
Table 10-11 Setting the parameters of the analog alarm port...........................................................................10-11
Table 10-12 Setting parameters of the Boolean alarm port..............................................................................10-12
Table 10-13 Setting the parameters of the Boolean alarm port........................................................................10-13
Table 11-1 Preparations before checking RET antenna.....................................................................................11-2
Table 13-1 Basic items in the service dialing test..............................................................................................13-1
Table 14-1 ALD information to be collected for troubleshooting......................................................................14-5
Table 15-1 Data sheet for NodeB commissioning..............................................................................................15-1
Issue 04 (2009-06-30) Huawei Proprietary and Confidential vii

NodeB
Commissioning Guide About This Document
About This Document
Purpose
This describes the commissioning and verification after the installation of the NodeB. The
commissioning ensures that the NodeB works properly as designed.
This document provides guidelines for NodeB commissioning, including upgrading and
downloading software, commissioning transmission and NodeB running state, commissioning
the ALD, testing services, and commissioning FAQs.
Version
The following table lists the product version related to this document.
Product Name Version
BTS3812E V100R009
V100R010
V100R011
BTS3812AE V100R009
V100R010
V100R011
DBS3800 V100R009
V100R010
V100R011
iDBS3800 V100R009
V100R010
V100R011
Intended Audience
This document is intended for:
Issue 04 (2009-06-30) Huawei Proprietary and Confidential 1

NodeB
About This Document Commissioning Guide
l Field engineers
Change History
For changes, refer to 1 Changes in the NodeB Commissioning Guide.
Organization
1 Changes in the NodeB Commissioning Guide

This describes the changes in the NodeB Commissioning Guide.
2 Safety Information
3 NodeB Commissioning Resources

Tools, site information, associated NodeB software, and data configuration files that are required
for NodeB commissioning should be prepared.
4 Procedure for Commissioning the NodeB
This describes the procedure for commissioning the NodeB.
5 Upgrading the NodeB Software and Downloading the Data Configuration File
This task describes how to upgrade the NodeB software and download the data configuration
file. Before performing this task, set the IP address of the NodeB, connect the NodeB to the
LMT, and log in to the LMT. Ensure that the free space on the disk is at least 1 GB during the
operation. Then, upgrade the NodeB software and download the data configuration file.
6 Checking the Connection for NodeB Networking
This describes how to check the connection of the NodeB networking. The task aims to check
the consistency between NodeB network topology and data configuration, and the link status
between the macro NodeB and the remote RRU, between the BBU and the RRU, or between
the BBU3806, RHUB3808, and pRRU3801.
7 Checking Transmission Status on the Iub Interface
This describes how to check the transmission status on the Iub interface. The check items can
be selected on the basis of the configuration of the physical layer on the Iub interface.
8 Checking the Running Status of the NodeB
This task describes how to check the running status of the NodeB to ensure proper working and
to rectify faults in working.
9 Measuring the NodeB VSWR
This describes how to check the VSWR. The VSWR is used to verity whether the antenna system
is correctly installed.
10 Commissioning the Alarm Equipment of NodeB
This task describes how to commission the alarm equipment of NodeB, including adding the
alarm monitoring equipment, setting external alarms, and checking external alarms.
11 Checking the ALD
2 Huawei Proprietary and Confidential Issue 04 (2009-06-30)

NodeB
This describes how to check the Antenna Line Device (ALD). The task consists of checking the
RET antenna and checking the Smart Tower Mounted Amplifier (STMA).
12 Handling Alarms During Commissioning NodeB
This describes how to check whether active alarms are present on the NodeB and clear these
alarms if any.
13 Testing NodeB Services with a UE
This describes how to test NodeB services on the UE to check whether the NodeB can properly
provide all types of services.
14 NodeB Commissioning FAQs
This describes the fault symptoms and cause analysis of FAQs during NodeB commissioning.
15 Data Sheet for NodeB Commissioning
This provides the data sheet that is used to record the process and results of the NodeB
commissioning
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided,will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.

NodeB
About This Document Commissioning Guide
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder .
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
4 Huawei Proprietary and Confidential Issue 04 (2009-06-30)

NodeB
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.

NodeB
Commissioning Guide 1 Changes in the NodeB Commissioning Guide
1 Changes in the NodeB Commissioning

Guide
This describes the changes in the NodeB Commissioning Guide.
04 (2009-06-30)
This is the third commercial release.
Compared with issue 03 (2009-03-20), this issue includes the following new topics:
The description of measuring the NodeB Voltage Standing Wave Ratio (VSWR) is added.
03 (2009-03-20)
This is the second commercial release.
Compared with issue 02 (2008-10-13), this issue incorporates the following changes:
The descriptions of the 7.2 Checking Optical Transmission Links on the Iub Interface and
the 10.1 Adding the Alarm Equipment to the NodeB are optimized.
02 (2008-10-13)
This is the first commercial release.
01 (2008-07-23)
This is the initial field trial release.
Issue 04 (2009-06-30) Huawei Proprietary and Confidential 1-1

NodeB
Commissioning Guide 2 Safety Information
2 Safety Information
2.1 Overview
2.1.1 Safety Precautions

This section describes the safety precautions to be taken before installing and maintaining the
Huawei device.
l Before performing an operation, read the operation instructions and precautions to be taken,
and follow them to prevent accidents. The Caution, Warning and Danger items in other
documents do not cover all the safety precautions that must be followed; they are only
supplementary information. The installation and maintenance personnel need to understand
the basic safety precautions to be taken.
l When operating the device, obey the local safety regulations. The safety precautions
provided in the documents are supplementary and shall be in compliance with the local
safety regulations.
l When operating the Huawei device, in addition to the precautions, follow the specific safety
instructions given by Huawei.
l The installation and maintenance personnel must receive training in safety precautions.
Only qualified personnel can install or maintain the device.
2.1.2 General Requirements

To minimize the technically residual risk, it is imperative to obey the following rules. Read all
the instructions before operation.
Installation
l The device (or system) must be installed or used in the access restricted location.
l The device can be mounted only on concrete or non-combustible surfaces.
l Before operation, the device must be fixed securely on the floor or to other reliable objects,
such as the walls and the mounting racks.

NodeB
2 Safety Information Commissioning Guide
l When installing the unit, always make the ground connection first and disconnect it at the
end.
l Do not block the ventilation while the device is running. Keep a minimum distance of 5
cm from the ventilation to the walls or the other objects that block the ventilation.
l Tighten the thumbscrews by using a tool after both initial installation and subsequent access
to the panel.
Ground
l Do not damage the ground conductor or operate the device in the absence of well installed
ground conductor. Conduct the appropriate electrical inspection.
l The device (or system) must be connected permanently to the protection ground before an
operation. The cross sectional area of protective ground conductor shall be at least 10 mm.
Power Supply
l For AC supplied model: The device applies to TN power systems.
l For DC supplied model: Reinforced insulation or double insulation must be provided to
isolate DC source from the AC mains supply.
l For DC supplied model: The device applies to DC power source that complies with the
Safety Extra-Low Voltage (SELV) requirements in IEC 60950-1 based safety standards.
l Prepared conductors are connected to the terminal block, and only appropriate AWG/Type
of wire is secured in the listed lug terminals.
l This device relies on the buildings installation for short-circuit (overcurrent) protection.
Ensure that a fuse or circuit breaker no larger than 120 VAC, 15 A U.S. (240 VAC, 10 A
international) for AC supplied model or 80 VDC, 32 A for DC supplied model is used on
the phase conductors (all current-carrying conductors).
l For this device, a readily accessible disconnect device shall be incorporated in the building
installation wiring.
l For AC supplied model: The plug-socket combination must be accessible at all times
because it serves as the main disconnect device.
l For AC supplied model: The socket outlet shall be installed near the device and shall be
easily accessible.
l Because the device has several power supplies, disconnect all of them to switch off the
device.
l The AC power supply has double pole/neutral fusing.
l To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord.
Human Safety
l Do not operate the device or cables at lightning strikes.
l For AC supplied model: To ensure the safety of the device and human body, unplug the
AC power connector and do not use the fixed terminal in the lightning weather.
Furthermore, do not touch the terminal or antenna connector in such weather.
l To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to
telecommunication network voltage (TNV) circuits.
2-2 Huawei Proprietary and Confidential Issue 04 (2009-06-30)

NodeB
l When moving or lifting the chassis, by holding its lower edge. It is forbidden to use the
handles on certain modules such as power supply, fans or boards, because they cannot
support the weight of the device.
l At least two persons are required to lift the chassis. When lifting it, keep your back straight
and move stably.
l Do not look directly into the optical port to prevent the laser radiation from injuring your
eyes.
l Do not wear jewelry or watches when you operate the device.
Operator
l Only qualified and skilled personnel must install, configure, and disassemble the device.
l Only the personnel authorized must operate the device.
l Any replacement or change to the device or parts of the device (including the software)
must be done by qualified or authorized personnel of Huawei.
l Any fault or error that might cause safety problems must be reported immediately to the
person in charge.
l Only qualified personnel must remove or disable the safety facilities, or to troubleshoot
and maintain the device.
Ensure that the instructions provided in this document are followed completely. The document
also provides guidelines in selecting the measuring and testing device.
2.2 Electricity Safety
High Voltage
DANGER
The high voltage power supply offers power for the device operation. Direct or indirect contact
(through damp objects) with high voltage and AC mains supply may result in fatal danger.
l During the installation of the AC power supply facility, follow the local safety regulations.
The personnel who install the AC facility must be qualified to perform high voltage and
AC operations.
l Do not wear conductive articles, such as watches, hand chains, bracelets and rings during
the operation.
l When water is found in the rack or the rack is damp, switch off the power supply
immediately.
l When the operation is performed in a damp environment, make sure that the device is dry.

NodeB
WARNING
Non-standard and improper high voltage operations may result in fire and electric shock.
Therefore, you must obey the local rules and regulations when bridging and wiring AC cables.
Only qualified personnel must perform high voltage and AC operations.
WARNING
High leakage current and earth connection are essential before supply connection and
telecommunication network connections.
Thunderstorm
DANGER
High voltage and AC operations, or operations on a steel tower and a mast are prohibited during
thunderstorm.
During thunderstorm, the electromagnetic field generated in the thunderstorm area may damage
the electronic parts. To prevent damage to the device during lightning, ground the device
properly.
Tools
WARNING
Suggestion: Dedicated tools must be used during high voltage and AC operations. Avoid using
ordinary tools.
High Electrical Leakage
WARNING
Ground the device before powering on the device. Otherwise, the personnel and device are in
danger.
If the "high electrical leakage" flag is stuck to the power terminal of the device, you must ground
the device before powering it on.

NodeB
Power Cable
WARNING
Installation and removal of live line are prohibited. Transient contact between the core of the
power cable and the conductor may generate electric arc or spark, which may cause fire or eye
injury.
l Before installing or removing the power cable, turn off the power switch.
l Before connecting the power cable, confirm that the power cable and label comply with
the requirements of the actual installation.
CAUTION
l For the DC power supplied device, use ? mm or ? AWG minimum power supply cord.
l For AC power supplied device, use ? mm or ? AWG minimum power supply cord.
l Use the type H03VV-F or light PVC sheathed flexible cord based on IEC 60227.
Fuse
WARNING
If a fuse is to be replaced, the new fuse shall be of the same type and specifications.
Table 2-1 lists the fuses that will affect the safety of the device (or system). Use fuses according
to this list.
Table 2-1 Fuse description
Position Manufacturer Type Rating
Fuse F1, F2 (on Littelfuse 0215010.M 250 V, 10 A

SS01OPU)
19040089
Fuse F1 (on LVC) Littelfuse 0217.500.M F500 mAL/250 V

19040013
Bussman S500-500mA
Fuse F1, F2 (on Littelfuse 0313025.M 25 A

APIU) 19040079
Bussman MDL-25A

NodeB
Electrostatic Discharge
CAUTION
The static electricity generated by the human body may damage the electrostatic sensitive
components on the circuit board, such as the large-scale integrated circuit (LIC).
In the following situations, the human body will generate a static electromagnetic field:
l Human body moving
l Clothes friction
l Friction between shoes and the ground
l Holding ordinary plastic in hand
The static electromagnetic field will remain within the human body for a long time.
Before touching the device, hand-operating parts, circuit boards, or ASICs, wear a grounded
electrostatic discharge (ESD) wrist strap. It can prevent the sensitive components from damage
by the static electricity in the human body.
Figure 2-1 shows the wearing of an ESD wrist strap.
Figure 2-1 Wearing an ESD wrist strap
2.3 Inflammable Environment

Operating the electrical device in inflammable environment can be fatal.

NodeB
DANGER
Do not place the device in the environment that has inflammable and explosive air or fog. Do
not perform any operation in this environment.
2.4 Battery
2.4.1 Storage Battery
DANGER
Before handling the battery, read carefully the safety precautions to be taken for battery handling
and connections.
CAUTION
Non-standard operation on batteries may result in danger.
During operation:
l Protect the battery against short-circuit
l Prevent electrolyte overflow and leakage
Electrolyte overflow may damage the device. It will corrode the metal parts and the circuit
boards, and ultimately damage the device and cause short-circuit of the circuit boards.
General Operations
Before installing and maintaining the battery, note the following:
l Do not wear metal articles such as wristwatch, hand chain, bracelet and ring.
l Use special-purpose insulation tools.
l Take care to protect you eyes when operating the device.
l Wear rubber gloves and an apron in the case of electrolyte overflow.
l Always keep the electrode front upright when handling the battery. Do not place the battery
upside down or tilt it.

NodeB
Short-Circuit
WARNING
Battery short-circuit may cause physical injury. Though voltage of a general battery is low, high
transient current generated by short-circuit will release a large amount of power.
There is danger of explosion if the battery is incorrectly replaced. Therefore, replace the battery
only with the same or an equivalent type recommended by the manufacturer.
CAUTION
Keep away metal objects, which may cause battery short-circuit, from batteries. If they have to
be used, first disconnect the batteries in use before performing any other operations.
Harmful Gas
CAUTION
l Do not use unsealed lead-acid batteries, because the gas emitted from the battery may result
in fire or device corrosion.
l Lay the battery horizontally and fix it properly.
l The battery in use will emit flammable gas. Therefore, put the battery in a place with good
ventilation, and take fire precautions.
High Temperature
CAUTION
High temperature may result in distortion, damage and electrolyte overflow of the battery.
When the temperature of the battery exceeds 60C, check whether there is acid liquid overflow.
If acid liquid overflow occurs, handle the acid liquid immediately.
Acid Liquid
CAUTION
In case of acid liquid overflow, absorb and neutralize the liquid immediately.
When moving or removing a leaky battery, note the possible damage caused by the acid liquid.
Once the acid liquid spill is found, use the following materials to absorb and neutralize it.

NodeB
l Sodium bicarbonate (baking soda): NaHCO3

l Sodium carbonate (soda): Na2CO3
The use of antacids must follow the guide provided by the battery supplier.
2.4.2 Lithium Battery
WARNING

l There is danger of explosion if the battery is incorrectly replaced. Therefore, replace the
battery only with the same or an equivalent type recommended by the manufacturer.
l Dispose the used batteries according to the manufacturer's instructions.
l Do not dispose of lithium battery in fire.
2.5 Electromagnetic Field Exposure
WARNING
Radio-frequency signals with high intensity are harmful to the human body.
Before installing or maintaining an antenna in a steel tower or a mast with a large number of
transmitter antennas, the operator should coordinate with the parties concerned to shut down the
transmitter antennas.
2.5.1 Introduction
The BTS emits RF radiation (radiation hazard). Operators have to follow the related local
regulations when erecting the BTS.
Operators of BTSs must also follow the related local regulations when erecting the BTS.
2.5.2 Limits and Guidelines on Exposure to Electromagnetic Fields
There are a number of international regulations, standards and guidelines for exposure to
electromagnetic fields. Several European countries have adopted the recommendation of the
council of the European Union. It was released on July 12, 1999, focusing on the harmful effects
of exposure to electromagentic fields. The recommendation is based on the guideline published
by the ICNIRP.
Table 2-2 gives a comparison among regulations and reference levels applied in different
countries.

NodeB
Table 2-2 Different regulations and reference

Country Limit 950 Limit 950 Limit 1850 Limit 1850
MHz E MHz S Power MHz E MHz S Power
Electric Field Flux Density Electric Field Flux Density
Strength Strength
ICNIRP 42 V/m 4.75 W/m2 59 V/m 9.25 W/m2

International
Europe 42 V/m 4.75 W/m2 59 V/m 9.25 W/m2

(1999/519/EC)
Italy, Decreto 6 V/m 0.095 W/m2 6 V/m 0.095 W/m2

No. 381, 1998
Switzerland 6 V/m 0.043 W/m2 6 V/m 0.096 W/m2

Verord. 1999
Reference levels are provided for exposure assessment, that is to determine whether the basic
limit of restriction on exposure of humans to electromagnetic fields is exceeded. The basic
restriction on exposure to electromagnetic fields is based on established health effects and
biological considerations.
2.5.3 Location of Base Station Antennas

Base station antennas, the source of the radiation, are usually mounted.
l On freestanding towers, with a height up to 30 m, or
l On a tower on the top of buildings, or
l On rare occasion, to the side of the building
Generally, the height of the antenna position does not fall below 10 m. The power usually forms
a horizontal main beam and is slightly tilted downward. The remaining power forms into the
weaker beams on both sides of the main beam. The main beam, however, does not reach ground
level until the distance from the antenna position is around 50200 m.
The highest level of emission would be expected in close vicinity of the antenna and in line of
sight to the antenna.
2.5.4 Exclusion Zones

The requirements for exclusion zones are as follows.
l Antenna location should be designed so that the public cannot access the area where the
RF radiation exceeds the levels as described earlier.
l If areas, where the RF radiation exceeds the prescribed level, are accessible to the workers,
make sure that workers know where these areas are, and that they can power off (or shut
down) the transmitters before entering these areas. Such areas may not exist; but if they do,
they must be confined to areas within 10 m of the antennas.
l Each exclusion zone should be defined by a physical barrier and by a recognizable sign
warning the public or workers.

NodeB
2.5.5 Guidelines on Arranging Antenna Sites

The guidelines on arranging the antenna sites are as follows.
l For roof-mounted antennas, raise the antennas above the height of the persons, who may
have to work in the rooftop.
l For roof-mounted antennas, keep the transmitter antennas away from the areas where
people are most likely to be, such as roof access points, telephone service points, and HVAC
device.
l For roof-mounted directional antennas, place the antennas near the periphery, and do not
make the antennas face to the building.
l Consider the trade-off between large aperture antennas (lower maximum RF) and small
aperture antennas (lower visual impact).
l Pay special attention to keep higher-power antennas away from accessible areas.
l Keep the antennas in a site that is far away, though this may contradict the local zone
requirements.
l Exercise extra caution when designing co-location sites, that is, where multiple antennas
owned by different companies are located. This applies particularly to sites that include
high-power broadcast (FM/TV) antennas. Local zone often favors co-location, but co-
location may cause safety problems.
l Take special precautions for antenna sites near hospital and schools.
2.5.6 Location of Base Transceiver Station

The base transceiver station (BTS) is shielded from RF radiation hazards. The device has been
tested to comply with the radioactive spurious emission requirements of EN 301 502. These
limits fall below the limits for RF radiation hazard. Therefore, the BTS does not cause danger
to the public and workers under normal operation condition. However, it is still possible that
because of imperfect antenna cables or other faults the limits set out above can be exceeded.
l BTS sites should not be accessible to the public. Only authorized and trained workers should
access sites or rooms.
l Doors of the site or room shall be clearly marked. For example, mark a sign warning the
workers that inside the site or room where the RF radiation might exceed limits for radiation
exposure.
l BTS sites shall be regularly monitored and inspected after installation.
2.5.7 Prediction of the Exposure to Electromagnetic Fields

The section provides a theoretical approach to calculate possible exposure to electromagnetic
radiation around a BTS antenna. Precise statements are possible either with measurements or
complex calculations considering the complexity of the environment, such as soil conditions,
nearby buildings and other obstacles. The complexity may cause reflections and deflection,
scattering of electromagnetic fields.
The maximum output power (given in EIRP) of a BTS is usually limited by license conditions
of the network operator.
For the BTS30, the number of carriers (TRXs) is 6 with a maximum output power of 40 W (46
dBm) each.

NodeB
A rough estimation of the expected exposure in power flux density on a given point can be made
with the following equation:
P = Maximum output power in W
G numeric = Numeric gain (see below)
r = Distance between the antenna and the point of exposure in meters
For the calculation of the Gain numeric:
Gnumeric = 10GdB/10
GdB = Gantenna(dB) - Bvertical-attenutation(dB) - Bhorizontal-attenuation(dB)B = attenuation in dB
B = attenuation in dB
2.5.8 Laser
The laser hazard level of this device is Class 1.
WARNING
When handling optical fibers, do not stand close to, or look at the optical fiber outlet directly
with unaided eyes.
General Laser Information

Laser transceivers or transmitters are used in the optical transmission system and associated test
tools. The wavelength of the laser is between 780 nm and 1600 nm. Because the laser is
transmitted through the optical fiber, it has very high power density and is invisible to human
eyes. When a beam of light enters the eye, the retina may be damaged.
Laser of wavelengths used in telecommunications can cause thermal damage to the retina.
Lasers used in lightwave systems have a larger beam divergence, typically 10 to 20 degrees.
Viewing an un-terminated fiber or damaged fiber with the unaided eye at distances greater than
150 mm (6 inches) will normally not cause eye injury. However, damage may occur if an optical
tool such as a microscope, magnifying glass or eye loupe is used to view the energized fiber end.
In its normal operating mode, a lightwave system is totally enclosed and presents no risk of eye
injury. Additional safety is achieved by an automatic laser shut-down (ALS) of the system. The
ALS, however, can be applied for bi-directional transmission only. If the receiver side does not
detect the laser from the transmission side, it will give the transmission side a signal. Upon
receiving the signal, the ALS will shut down the laser emission within 100 ms.
Laser Safety Guidelines

Read the following guidelines to avoid laser radiation:

NodeB
l Read the instructions before installing, operating and maintaining the device. Ignoring the
instructions can cause exposure to dangerous laser radiation.
l Wear a pair of eye-protective glasses when you are handling lasers or fibers.
l All the operation shall be performed by personnel who have completed the approved
training courses.
l Make sure that the optical source is switched off before disconnecting optical fiber
connectors.
l Before opening the front door of an optical transmission system, make sure that you are
not exposed to laser radiation.
l Do not look at the end of an exposed fiber or an open connector when you are not sure
whether the optical source is switched off or not.
l Use an optical power meter to check and ensure that the optical source is switched off by
measuring the optical power.
l Do not use an optical tool such as a microscope, a magnifying glass or an eye loupe to view
the optical connector or fiber.
Handling Fibers
Read the instructions before handling fibers.
l Cutting and splicing fibers must be performed by the trained personnel only.
l Before cutting or splicing a fiber, ensure the fiber is disconnected from the optical source.
After disconnecting the fiber, use protecting caps to protect all the optical connectors.
2.6 Working at Heights
WARNING
When working at heights, be careful to prevent objects from falling.
When working at height, comply with the following requirements:

l The personnel who work at heights must be trained.
l The operating machines and tools shall be carried and handled safely to avoid falling.
l Safety protection measures, such as wearing a helmet and a safety belt, shall be taken.
l In cold regions, wear warm clothes when performing high-altitude operations.
l All lifting appliances must be thoroughly checked before the work is started.
2.6.1 Weight Lifting

This chapter describes the safety precaution on weight lifting.
WARNING
Do not access the areas under the jib arm and the goods in suspension when lifting weight.

NodeB
l Ensure the operators have completed the related training and are qualified.
l Check the weight lifting tools and confirm that the tools are in good condition.
l Lift the weight only when the weight lifting tools are firmly fixed onto the weight-bearing
object or the wall.
l Use a concise command to avoid incorrect operation.
l Ensure the angle between the two cables is less than or equal to 90 degrees during the lift.
(see Figure 2-2).
Figure 2-2 Weight lifting
2.6.2 Safety Guide on Ladder Use
Checking the Ladder

Before using the ladder, first check if the ladder is in good condition. Make sure that you know
the maximum weight that the ladder can support; overweight on the ladder is strictly prohibited.
Placing the Ladder

Slant angle is suggested to be 75 degrees. The slant can be measured with the angle square or
with arms. When using a ladder, place the wider end of the ladder on the ground. Otherwise,

NodeB
take protective measures on the base part of the ladder to avoid skidding. Place the ladder on
stable ground.
Climbing the Ladder

When climbing the ladder, note the following.
l Ensure the gravity center of your body does not deviate from the ladder edge.
l To lessen the danger and ensure the safety, hold your balance on the ladder before any
operation.
l Do not climb higher than the fourth highest step of the ladder.
l If you are about to climb to the top, the length of the ladder shall be one meter higher than
the eave.
2.7 Mechanical Safety
Drilling
WARNING
Drilling on the rack without permission is strictly prohibited. Drilling that does not satisfy the
requirements concerned may damage the wires and cables inside the rack. If the metal shavings
from the drilling fall into the rack, it may result in short circuit of the circuit boards.
l Before drilling a hole on the rack, wear insulation gloves, and remove the cables inside the
rack.
l During the drilling, ensure that your eyes are well protected. The hot shavings may injure
your eyes.
l Ensure that the metal shavings do not fall into the rack.
l Non-standard drilling may damage the electromagnetic shielding performance of the rack.
l After drilling, clean the metal shavings in time.
Sharp Objects
WARNING
When carrying the device by hand, wear protection gloves to avoid injury by sharp objects.
Handling Fans
Ensure the following:
l When replacing a component, place the component, screw, and tool at a safe place to prevent
them from falling into the running fan.

NodeB
l When replacing the ambient equipment around the fan, do not place the finger or board
into the running fan until the fan is switched off and stops running.
Lifting Heavy Objects
WARNING
When lifting heavy objects, do not stand or walk under the arm or the lifted object.
2.8 Miscellaneous
Inserting and Removing a Board

To insert or remove a board, abide by the following requirements:
CAUTION
When inserting a board, handle it gently to avoid distorting pins on the backplane.
l Insert the board along the slot guide.

l The two sides of one board should not contact another board to avoid short-circuit or prevent
scratch.
l When holding a board in hand, do not touch the board circuit, components, connectors, or
connection slots.
Bundling Signal Cables
CAUTION
l Bundle the signal cables separately from the strong current cables or high voltage cables.
l Maintain a minimum space of 150 mm between adjacent ties.
Cabling Requirements
At a very low temperature, movement of the cable may damage the plastic skin of the cable. To
ensure the construction safety, comply with the following requirements:
l When installing cables, ensure that the environment temperature is above 0C.
l If cables are stored in the place below 0C, move the cables into a place at a room
temperature and store the cables for more than 24 hours before installation.
l Move the cables with care, especially at a low temperature. Do not drop the cables directly
from the vehicle.

NodeB
Commissioning Guide 3 NodeB Commissioning Resources
3 NodeB Commissioning Resources
Tools, site information, associated NodeB software, and data configuration files that are required
for NodeB commissioning should be prepared.
Tools
Table 3-1 lists the tools required for commissioning.
Table 3-1 Tools required for commissioning

Tools Quantit Unit Description
y
Computer 1 Piece For the hardware configuration of computer, refer

to Computer Requirements of the LMT in NodeB
LMT User Guide.
Requirements for the operating system:

l Windows 2000 + Server Pack 4 or later packs, or
Windows XP + SP2
l Internet Explorer 5.1 or later (128 bit encryption
supported)
Requirements for the software:

l NodeB LMT. For details about installation and
operations, refer to the NodeB LMT User
Guide.
l CME. For details about installation and
operations, refer to the CME User Guide.
Ethernet cable 1 Piece The cable is used to connect the computer to the
NodeB.
Light Emitting 1 Piece The LED is used to distinguish the TX end from the
Diode (LED) RX end of the trunk cable.
(optional)

NodeB
3 NodeB Commissioning Resources Commissioning Guide
Tools Quantit Unit Description

y
Tester UE 1 Piece Requirements for the tester UE:

l The UE is configured with the SIM card.
l The UE is registered at the HLR in the network.
l The UE enables you to observe the PCPICH
scrambling code, Ec/Io, and RSCP.
Site Information
The site information of the NodeB to be commissioned consists of the following:
l Critical information about the networking and configuration of the NodeB, such as the site
type, transmission mode, networking, and cell configuration.
l NodeB-related negotiation data on the RNC
NodeB Software
If the default software version on the site is inconsistent with the planned version, the NodeB
software on the site must be upgraded.
Before commissioning, ensure that the following NodeB software is available:
l BOOTROM software. The file name is fixed to NBRom.pck.
l NodeB software. The file name is fixed to NodeB.pck.
Before commissioning, copy the correct NodeB software version to the specified directory of
the computer for commissioning.
NodeB Data Configuration File

The NodeB data configuration file is named NodeBCfg.xml.
Before commissioning, copy the correct NodeB data configuration file to the specified directory
of the computer for commissioning.
NOTE
Before commissioning, query and record the IP address of the NodeB local maintenance channel (local IP
address) in the data configuration file.

NodeB
Commissioning Guide 4 Procedure for Commissioning the NodeB
4 Procedure for Commissioning the NodeB
This describes the procedure for commissioning the NodeB.
Prerequisite
Before commissioning, the NodeB should meet the following requirements:
l The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary
devices, passes the installation check.
l 3 NodeB Commissioning Resources are available.
l The data of the NodeB to be commissioned is negotiated with the RNC and recorded.
l The cabinet is powered on.
The requirements for the RNC are as follows:

l The RNC connected to the NodeB is installed and commissioned and the system works
properly.
l The data of the NodeB to be commissioned is configured on the RNC and recorded.
Procedure
Step 1 Go to 5 Upgrading the NodeB Software and Downloading the Data Configuration File.
1. Go to 5.1 Setting the IP Address of the NodeB LMT PC.
2. Go to 5.2 Locally Connecting the NodeB LMT PC to the NodeB.
3. Go to 5.3 Locally Logging In to the NodeB on the NodeB LMT.
4. Go to 5.4 Upgrading the NodeB Software.
5. Go to 5.5 Downloading the NodeB Data Configuration File.
6. 5.6 Resetting the NodeB.
7. Wait for five minutes. After the NodeB is started, 5.3 Locally Logging In to the NodeB
on the NodeB LMT.
Step 2 6 Checking the Connection for NodeB Networking.
NOTE
This step is optional for macro NodeBs. This step is performed when the RRU is configured.
Step 3 7 Checking Transmission Status on the Iub Interface.

NodeB
4 Procedure for Commissioning the NodeB Commissioning Guide
Step 4 8 Checking the Running Status of the NodeB.

1. 8.1 Commissioning SNTP.
2. 8.2 Checking the Status of a Cell.
3. 8.3 Measuring RTWP.
4. 8.4 Monitoring Output Power.
Step 5 9 Measuring the NodeB VSWR.
Step 6 Choose appropriate operation based on the configuration of the alarm equipment at the site.
If... Then...
The alarm equipment is configured Go to 10 Commissioning the Alarm Equipment of

NodeB.
No alarm equipment is configured Go to Step 7.
Step 7 Choose appropriate operation based on the configuration of the antenna line device (ALD) at
the site.
If... Then...
The RET antenna is configured Go to 11.1 Checking the RET Antenna.
The STMA is configured Go to 11.2 Checking the STMA.
No ALD is configured Go to Step 8.
NOTE
If the iDBS3800 is not configured with the ALD, skip the step.
Step 8 12 Handling Alarms During Commissioning NodeB.

Step 9 13 Testing NodeB Services with a UE.
Step 10 Notify the M2000 administrator that the commissioned NodeB can be managed by the M2000.
Step 11 Record the commissioning procedure and problems in the 15 Data Sheet for NodeB
Commissioning, and then export a commissioning report.
----End

NodeB 5 Upgrading the NodeB Software and Downloading the Data
Commissioning Guide Configuration File
5 Upgrading the NodeB Software and

Downloading the Data Configuration File
About This Chapter
This task describes how to upgrade the NodeB software and download the data configuration
file. Before performing this task, set the IP address of the NodeB, connect the NodeB to the
LMT, and log in to the LMT. Ensure that the free space on the disk is at least 1 GB during the
operation. Then, upgrade the NodeB software and download the data configuration file.
5.1 Setting the IP Address of the NodeB LMT PC

This describes how to set the IP address of the LMT PC. You must set a correct IP address for
the LMT PC before logging in to the NodeB.
5.2 Locally Connecting the NodeB LMT PC to the NodeB
This describes how to connect the LMT PC to the NodeB in NodeB local maintenance mode to
operate and maintain the NodeB.
5.3 Locally Logging In to the NodeB on the NodeB LMT
This describes how to locally log in to the NodeB on the LMT.
5.4 Upgrading the NodeB Software
This describes how to upgrade the NodeB software. The task consists of the following steps:
checking the NodeB software version, downloading the NodeB BootROM, activating the NodeB
BootROM, downloading the NodeB software, and activating the NodeB software.
5.5 Downloading the NodeB Data Configuration File
This describes how to download the NodeB data configuration file from the FTP server to the
NodeB. The downloaded data configuration files take effect after the NodeB is reset.
5.6 Resetting the NodeB
This describes how to reset the NodeB by resetting the NMPT of the macro NodeB or the
BBU3806/BBU3806C after login to LMT.

5 Upgrading the NodeB Software and Downloading the Data NodeB
Configuration File Commissioning Guide
5.1 Setting the IP Address of the NodeB LMT PC

This describes how to set the IP address of the LMT PC. You must set a correct IP address for
the LMT PC before logging in to the NodeB.
Prerequisite
The TCP/IP protocol is configured on the LMT PC.
Context
Before you perform the maintenance, set the IP address for the LMT PC as follows:
l In local maintenance, IP addresses of the LMT PC and the NodeB local maintenance
channel are in the same network segment.
l In remote maintenance, you need to set the route from the LMT PC to the NodeB. For
details, see Setting the Route from the NodeB LMT PC to the NodeB ; IP 1 and IP 2 are
in the same network segment, as shown in Figure 5-1. IP 1 stands for the IP address of the
LMT PC. IP 2 stands for the IP address of the external network composed of the entity
directly connected to the LMT PC and the LAN where the LMT PC is located, for example,
the IP address of the RNC BAM external network.
Figure 5-1 IP addresses in remote maintenance mode
CAUTION
Ensure that the IP address of the LMT PC does not conflict with the IP address of another
computer within the same local area network.
Procedure
Step 1 For example, to set the IP address of the LMT PC with the Windows XP operating system,
perform the following steps: Choose Start > Control Panel .
If... Then...
The control panel is displayed in category Go to Step 2.

view,

If... Then...
The control panel is displayed in classical Go to Step 3.

view,
Step 2 Click Network and Internet Connections.

Step 3 Double-click Network Connections. The Network Connections window is displayed. Right-
click the icon of Local Area Connection.
Step 4 Choose Properties from the shortcut menu. The Local Area Connection Properties dialog
box is displayed.
Step 5 Select Internet Protocol (TCP/IP).
Step 6 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed.
Step 7 Select Use the following IP address.
Step 8 Enter the correct IP address, subnet mask, and default gateway.
If... Then...
The LMT PC is used in local maintenance Set the IP address, subnet mask, and default
mode, gateway, as shown in Table 5-1.
The LMT PC is used in remote maintenance Set the IP address, subnet mask, and default
mode, gateway, as shown in Table 5-2.
Table 5-1 IP parameters of the LMT PC for commissioning on the NodeB side
Parameter Description
IP Address The IP address of the LMT PC is in the same network segment as that
of the NodeB local maintenance channel.
In local maintenance mode, the default NodeB IP address is 17.21.2.5.
Subnet mask The LMT PC has the same subnet mask as that of the NodeB local
maintenance channel.
Default gateway -
Table 5-2 IP parameters of the LMT PC for commissioning on the NodeB side
IP Address The IP address of the LMT PC is in the same network segment as the
external IP address of RNC BAM.
Subnet mask The subnet mask of the LMT PC is the same as the external subnet mask
of RNC BAM.

Default gateway The IP address of the BAM external network is the gateway from the
LMT to the NodeB.
NOTE
The IP address in the same network segment corresponds to the same subnet mask and subnet address
(subnet mask AND IP address).
Step 9 Click OK to complete the settings.
----End
5.2 Locally Connecting the NodeB LMT PC to the NodeB

This describes how to connect the LMT PC to the NodeB in NodeB local maintenance mode to
operate and maintain the NodeB.
5.2.1 Locally Connecting the NodeB LMT PC to the NMPT

This describes how to locally connect the LMT PC to the NMPT through a Ethernet cable when
the NodeB LMT PC is locally connected to a macro NodeB.
5.2.2 Locally Connecting the NodeB LMT PC to the BBU3806
This describes how to locally connect the LMT PC to the BBU3806 through a Ethernet cable
when the NodeB LMT PC is locally connected to a distributed NodeB.
5.2.3 Locally Connecting the NodeB LMT PC to the BBU3806C
This describes how to locally connect the LMT PC to the BBU3806C through a Ethernet cable
5.2.1 Locally Connecting the NodeB LMT PC to the NMPT

This describes how to locally connect the LMT PC to the NMPT through a Ethernet cable when
the NodeB LMT PC is locally connected to a macro NodeB.
Prerequisite
The IP address of the LMT PC and that of the NodeB local maintenance channel are in the same
network segment.
Procedure
Step 1 Connect the Ethernet port of the LMT PC to the maintenance Ethernet port of the NMPT board
with a crossover cable, as shown in Figure 5-2.

Figure 5-2 Connecting LMT PC and NMPT in local maintenance mode
(1) NMPT (2) Crossover cable (3) LMT PC
Step 2 On the LMT PC, choose Start > Run, and then run the cmd command in the Run dialog box.
The command window is displayed.
Step 3 Run ping target_name -t and verify the connection between the LMT PC and the NodeB. Here,
target_name represents the IP address of the NodeB local maintenance channel.
----End
5.2.2 Locally Connecting the NodeB LMT PC to the BBU3806

This describes how to locally connect the LMT PC to the BBU3806 through a Ethernet cable
Prerequisite
network segment.
Procedure
Step 1 Connect the Ethernet port of the LMT PC to the ETH_RS232 port on the BBU3806 panel with
a crossover cable, as shown in Figure 5-3.

Figure 5-3 Connecting LMT PC and BBU3806 in local maintenance mode
(1) BBU3806 (2) Crossover cable (3) LMT PC
----End
5.2.3 Locally Connecting the NodeB LMT PC to the BBU3806C

This describes how to locally connect the LMT PC to the BBU3806C through a Ethernet cable
Prerequisite
network segment.
Procedure
Step 1 Connect the Ethernet port of the LMT PC to the ETH_RS232 port of the BBU3806C panel with
a crossover cable, as shown in Figure 5-4.

Figure 5-4 Connecting LMT PC and BBU3806C in local maintenance mode
(1) Maintenance cavity of the BBU3806C (2) Crossover cable (3) LMT PC
----End
5.3 Locally Logging In to the NodeB on the NodeB LMT

This describes how to locally log in to the NodeB on the LMT.
Prerequisite
The LMT PC is properly connected to the NodeB.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Local Maintenance
Terminal. If the LMT is started, choose System > Log Out or click . The User Login
dialog box is displayed, as shown in Figure 5-5.

Figure 5-5 User Login dialog box
Table 5-3 describes the fields in the User Login dialog box.
Table 5-3 Fields in the User Login dialog box

Field Description
User Name Enter the user name of the NodeB. The default user name is admin.
The user name is mandatory and case-sensitive.
Password Enter the password of the NodeB. The default password is NodeB. The
password consists of 6 to 16 alphanumeric and case-sensitive
characters.
Office Select the name and IP address of the NodeB that is connected to the
LMT. Click to edit the office information. For details, refer to
Setting the Information About an Office on the NodeB LMT.
When you log in to the NodeB locally, the IP address of the office must
be the same as that of the NodeB local maintenance channel.
Proxy server Leave this field blank. Ensure that you do not select the check box.
Step 2 In the Office area, set IP Address and Office.

Step 3 Enter the user name and password in the dialog box.
Step 4 Click Login to log in to the NodeB.
Step 5 If a dialog box is displayed, as shown in Figure 5-6, you can infer the NodeB language does not
match the LMT language. In this case, switch the NodeB language to log in to the NodeB.

Figure 5-6 Switching the language
CAUTION
The NodeB will be reset after you switch the NodeB language.
Step 6 Click Yes to switch the NodeB language.

NOTE
If you click No, a dialog box is displayed, prompting The language of NE differs from LMT. You click
OK to log in to the NodeB. But this step leads to the following results:
l The language of the NodeB software message that is reported to the LMT does not match the LMT
language.
l When software management operations are performed, message analysis fails.
----End
5.4 Upgrading the NodeB Software

This describes how to upgrade the NodeB software. The task consists of the following steps:
checking the NodeB software version, downloading the NodeB BootROM, activating the NodeB
BootROM, downloading the NodeB software, and activating the NodeB software.
1. 5.4.1 Checking the NodeB Software Version

This describes how to check the current NodeB software version to obtain detailed
information. If the current NodeB software version is inconsistent with that to be used,
upgrade the current software version.
2. 5.4.2 Downloading the NodeB BootROM
This describes how to download the NodeB BootROM software from the FTP server to the
temporary directory on the main processing board and then to the related boards.
3. 5.4.3 Activating the NodeB BootROM
This describes how to activate the NodeB BootROM. Activating the BootROM refers that
the main processing board sends the BootROM update command to all the boards that
successfully download the BootROM, and then updates each board BootROM.
4. 5.4.4 Downloading the NodeB Software
This describes how to download the NodeB software from the FTP server to the NodeB.
The NodeB file directories are the active directory and the standby directory. The active
directory saves the running NodeB software version. The standby directory saves the

inactive NodeB software version. After the NodeB software is downloaded, it is saved in
the standby directory. The NodeB software does not take effect immediately or damage the
running software.
5. 5.4.5 Activate the NodeB Software
This describes how to switch the standby directory to the active one, and then download
the NodeB software to each board and validate it. You can activate the NodeB software
right after the downloading or later on. After the activation, the NodeB is reset. Thus, all
the services are disrupted.
5.4.1 Checking the NodeB Software Version

This describes how to check the current NodeB software version to obtain detailed information.
If the current NodeB software version is inconsistent with that to be used, upgrade the current
software version.
Prerequisite
l You have logged in to the NodeB LMT.
l If the macro NodeB is configured with two NMPTs, run the command DSP BRD to query
the board status, and thus distinguishing the active NMPT.
l If the distributed NodeB is configured with two BBUs, run the command DSP BRD to
query the board status, and thus distinguishing the active BBU.
Procedure
Step 1 Query NodeB software version
If... Then...
The NodeB is a macro NodeB, Go to Querying the Software Version of the Macro
NodeB.
The NodeB is a distributed NodeB, Go to Querying the Software Version of the

Distributed NodeB.
Step 2 Check whether the current NodeB software version is consistent with that to be used.
If... Then...
The current NodeB software version is consistent with that to be used, End this task.
The current NodeB software version is inconsistent with that to be used, Go to Step 3.
Step 3 Check whether the NodeB software version to be used is saved in the standby directory.

If... Then...
The version to be used is saved in the Activate the BootROM. For details, refer to
standby directory, 5.4.5 Activate the NodeB Software.
The version to be used is not saved in the Download and activate the new NodeB
standby directory, software. For details, refer to 5.4.4
Downloading the NodeB Software and 5.4.5
Activate the NodeB Software.
----End
5.4.2 Downloading the NodeB BootROM

This describes how to download the NodeB BootROM software from the FTP server to the
temporary directory on the main processing board and then to the related boards.
Prerequisite
l The FTP server works properly and is correctly connected to the NodeB in the same intranet.
l There is no firewall between the FTP server and the NodeB.
l The FTP user can access the specified directory.
Procedure
Step 1 In the navigation pane, click the Maintenance tab.
Step 2 Double-click Software Management > Software Update. The Software Update dialog box
is displayed, as shown in Figure 5-7.

Figure 5-7 Software Update dialog box
Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed, as shown in Figure 5-8.

Figure 5-8 Software Upgrade dialog box
NOTE
l The system downloads the BootROM package and then activates it.
l You can choose one step each time and the system proceeds with the task you customize.
Step 5 Click Modify. The FTP Setting dialog box is displayed, as shown in Figure 5-9.
Figure 5-9 FTP Setting dialog box

Table 5-4 describes the fields in the FTP Setting dialog box.
Table 5-4 Fields in the FTP Setting dialog box
Field Description
Use Built-in FTP Server This enables you to decide whether to use a built-in or
a specified FTP server. The built-in FTP server is
started by default.
Use Specified FTP IP address The FTP server can be started either from the local
Server computer installed with the LMT application or from
another computer. Here it refers to the IP address of
the FTP server.
User Name This enables you to specify the user name for logging
in to the FTP server.
Password This enables you to specify the password for logging

in to the FTP server.
Step 6 Set the FTP server.
Step 7 Click OK. The FTP Setting dialog box is closed and the Upgrade BOOTROM dialog box is
displayed.
Step 8 Select Download BOOTROM Package and then specify a path to download the BootROM
package.
Step 9 Click Next. A dialog box is displayed for your confirmation.
Step 10 Click Yes. The Upgrading Patch Progress dialog box is displayed. The status and progress of
the patch upgrade is displayed in the dialog box. You may check the process by viewing this
dialog box.
----End
5.4.3 Activating the NodeB BootROM

This describes how to activate the NodeB BootROM. Activating the BootROM refers that the
main processing board sends the BootROM update command to all the boards that successfully
download the BootROM, and then updates each board BootROM.
Context
l Before the activation, the system checks the BootROM versions of the boards. It activates
the board BootROM only when there is an upgraded BootROM version.
l Because the BootROM does not affect the NodeB services, you need not reset the
NodeB to make the BootROM effective. The NodeB starts with the upgraded BootROM
during next reset.
l After the BootROM is activated, the NodeB is not reset.

Procedure
Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed, as shown in Figure 5-11.

Figure 5-11 Upgrade BOOTROM dialog box
NOTE
l The system downloads the BootROM package and then activates it.
l You can choose one step each time and the system proceeds with the task you customize.
Step 5 Select Activate BOOTROM.

dialog box.
----End
5.4.4 Downloading the NodeB Software

This describes how to download the NodeB software from the FTP server to the NodeB. The
NodeB file directories are the active directory and the standby directory. The active directory
saves the running NodeB software version. The standby directory saves the inactive NodeB
software version. After the NodeB software is downloaded, it is saved in the standby directory.
The NodeB software does not take effect immediately or damage the running software.

Prerequisite
l The FTP server works properly and is correctly connected to the NodeB in the same intranet.
l The FTP user can access the specified directory.
Procedure
Step 1 In the navigation pane, click the Maintenance Tab.
Step 2 Choose Software Management > Software Update. The Software Upgrade dialog box is
displayed, as shown inFigure 5-12.
Figure 5-12 Software upgrade dialog box
Step 3 Select Upgrade NodeB Software in the dialog box.
Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed, as shown in Figure 5-13.

Figure 5-13 Upgrade NodeB Software dialog box
Step 5 Click Modify. The FTP Setting dialog box is displayed, as shown in Figure 5-14.


Field Description
Use Built-in FTP Server This enables you to decide whether to use a built-in or a
specified FTP server. The built-in FTP server is selected
by default.
Use Specified FTP IP The FTP server can be started either from the local
Server Address computer installed with the LMT application or from
another computer. Here it refers to the IP address of the
FTP server.
User This enables you to specify the user name for logging in
Name to the FTP server.
Password This enables you to specify the password for logging in

to the FTP server.
Step 6 Set the FTP server.

Step 7 Click OK. The FTP Setting dialog box is closed and the Upgrade NodeB Software dialog box
is displayed.
Step 8 Select Backup Data Configuration File, Download NodeB Software Package, and
Download by Configuration to specify a directory for backing up the file and a directory for
downloading the NodeB software package.
NOTE
l Backup Data Configuration File is optional. It is recommended that you choose the option.
l When the configuration and initial configuration changes or the configuration file encounters an error,
click Download Data Configuration File to download the data configuration file again. Meanwhile
click Effective Data Configuration File to confirm its validity before activating the NodeB software.
l It is recommended that you select Download by Configuration. If it is not selected, the dialog box is
displayed to prompt that this may cause the software download failure. Click OK to start the
downloading of the software. Click Cancel to select again, and download the software by configuration.
l Downloading by configuration indicates that you can download all the board software package required
according to the current NodeB configuration. This reduces the total volume of data during
downloading, shortens the time of downloading the software, and saves the storage space for the NodeB.

dialog box.
----End
5.4.5 Activate the NodeB Software

This describes how to switch the standby directory to the active one, and then download the
NodeB software to each board and validate it. You can activate the NodeB software right after

the downloading or later on. After the activation, the NodeB is reset. Thus, all the services are
disrupted.
Procedure
Step 1 Click the Maintenance tab.
Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed, as shown in Figure 5-16.

Figure 5-16 Upgrade NodeB Software dialog box
Step 5 Select Activate NodeB Software and select the NodeB software version to be upgraded in the
Version box.
NOTE
l The Version box is displayed only when Download NodeB Software is not selected.
l When the configuration and initial configuration changes or the configuration file encounters an error,
click Download Data Configuration File to download the data configuration file again. And click
Effective Data Configuration File to confirm its validity before activating the NodeB software.

dialog box.

NOTE
l The NodeB is reset and the new NodeB software version is started when NodeB software is activated.
l Reactivate the NodeB software version in the standby file directory or reinstall the NodeB software
upon activation failure.
----End
5.5 Downloading the NodeB Data Configuration File

This describes how to download the NodeB data configuration file from the FTP server to the
NodeB. The downloaded data configuration files take effect after the NodeB is reset.
Procedure
l In GUI mode
1. In the navigation pane, click the Maintenance tab.
2. Double-click Software Management > Data Config File Transfer. The Data
Configuration File Transfer dialog box is displayed, as shown in Figure 5-17.
Figure 5-17 DataConfig File Transfer dialog box

3. Select the Download (FTP Server to NodeB).

4. Click Modify in the dialog box. The FTP Setting dialog box is displayed, as shown
in Figure 5-18.

Field Description
Use Built-in FTP Server This enables you to decide whether to use a
built-in or a specified FTP server. The built-in
FTP server is started by default.
Use Specified FTP IP address The FTP server can be started either from the
Server local computer installed with the LMT
application or from another computer. Here it
refers to the IP address of the FTP server.
User This enables you to specify the user name for

Name logging in to the FTP server.
Password This enables you to specify the password for

logging in to the FTP server.
5. Set the FTP server.

6. Click OK. The FTP Setting dialog box is closed and the DataConfig File
Transfer dialog box is displayed.
7. Set the other parameters in the dialog box.
8. Click Start.
l In MML mode
Run the command DLD CFGFILE.
----End

5.6 Resetting the NodeB

This describes how to reset the NodeB by resetting the NMPT of the macro NodeB or the
BBU3806/BBU3806C after login to LMT.
5.6.1 Resetting the Macro NodeB

This describes how to reset the macro NodeB. Resetting the NMPT leads to the reset of all the
boards in the macro NodeB. Thus, the macro NodeB is reset.
5.6.2 Resetting the Distributed NodeB
This describes how to reset the distributed NodeB. Resetting the BBU3806 or BBU3806C leads
to the reset of all the boards in the distributed NodeB. Thus, the distributed NodeB is reset.
5.6.1 Resetting the Macro NodeB

This describes how to reset the macro NodeB. Resetting the NMPT leads to the reset of all the
boards in the macro NodeB. Thus, the macro NodeB is reset.
Context
CAUTION
Resetting the macro NodeB disrupts the services carried on the macro NodeB.
Procedure
l In GUI mode
2. Double-click Topology Management > Master Cabinet. The device panel is
displayed.
3. Select the NMPT on the device panel.
4. Right-click the board. A shortcut menu is displayed.
5. Choose Reset Board. A dialog box is displayed for your confirmation.
6. Click Yes in the dialog box.
CAUTION
After the reset, the LMT displays the result. If the reset is successful, the LMT is
disconnected from the NodeB. You need to log in to the NodeB.
l In MML mode
Run the command RST NodeB.
----End

5.6.2 Resetting the Distributed NodeB

This describes how to reset the distributed NodeB. Resetting the BBU3806 or BBU3806C leads
to the reset of all the boards in the distributed NodeB. Thus, the distributed NodeB is reset.
Context
CAUTION
Resetting the distributed NodeB disrupts the carried services.
Procedure
l In GUI mode
2. Double-click Topology Management > RRU Physical Topology. The physical
topology is displayed.
3. Right-click the BBU. The shortcut menu is displayed.
4. Choose Reset Board. A dialog box is displayed for your confirmation.
5. Click Yes in the dialog box.
CAUTION
After the reset, the LMT displays the result. If the reset is successful, the LMT is
disconnected from the NodeB. You need to log in to the LMT again to connect to the NodeB.
l In MML mode
Run the command RST NodeB.
----End

NodeB
Commissioning Guide 6 Checking the Connection for NodeB Networking
6 Checking the Connection for NodeB

Networking
About This Chapter
This describes how to check the connection of the NodeB networking. The task aims to check
the consistency between NodeB network topology and data configuration, and the link status
between the macro NodeB and the remote RRU, between the BBU and the RRU, or between
the BBU3806, RHUB3808, and pRRU3801.
6.1 Checking the Connection Between the Macro NodeB and the RRU
This describes how to check the consistency between actual macro NodeB networking and data
configuration, and the link status between the macro NodeB and the remote RRU.
6.2 Checking the Networking and Link Status of the DBS3800
This describes how to check the consistency between actual DBS3800 networking and data
configuration, and the link status between the BBU and the RRU.
6.3 Checking the Connection for the iDBS3800 Networking
This describes how to check the consistency between actual iDBS3800 networking and data
configuration, and the link status between BBU3806, RHUB3808, and pRRU3801.

NodeB
6 Checking the Connection for NodeB Networking Commissioning Guide
6.1 Checking the Connection Between the Macro NodeB and

the RRU
This describes how to check the consistency between actual macro NodeB networking and data
configuration, and the link status between the macro NodeB and the remote RRU.
1. 6.1.1 Checking the Consistency in Connection and Data Configuration of the Macro NodeB
This describes how to check the macro NodeB and RRU to ensure consistency in hardware
installation and data configuration.
2. 6.1.2 Checking the Links Between the Macro NodeB and the RRU
This describes how to check the links between the Macro NodeB and the RRU to rectify
the faults caused by improper cable connections.
6.1.1 Checking the Consistency in Connection and Data

Configuration of the Macro NodeB
This describes how to check the macro NodeB and RRU to ensure consistency in hardware
installation and data configuration.
Procedure
Step 1 Run the commands to check whether the NodeB data configuration is consistent with the
hardware installation. The items to be checked consist of the network topology, quantity, cabinet
number, subrack number, slot number, interface board number, subrack type, and configuration.
1. Run the command LST RRUCHAIN to check the consistency between hardware
installation and data configuration of the RRU networking.
2. Run the command LST CABINET to check the consistency between hardware installation
and configuration in cabinet.
3. Run the command LST SUBRACK to check the consistency between hardware installation
and configuration in subracks.
Step 2 Choose operations according to query results.
If... Then...
The data configuration and hardware installation are consistent, End the task.
The data configuration and hardware installation are inconsistent, Go to Step 3.
Step 3 Determine whether the data configuration or the hardware installation is incorrect.
If... Then...
The data configuration is incorrect, Modify the data configuration. For details, refer to
the NodeB Initial Configuration Guide.

NodeB
If... Then...
The hardware installation is incorrect, Install the hardware again. For details, refer to the
associated installation guide.
----End
6.1.2 Checking the Links Between the Macro NodeB and the RRU
This describes how to check the links between the Macro NodeB and the RRU to rectify the
faults caused by improper cable connections.
Procedure
Step 1 Run the command DSP RRUCHAINSTATE to check the RRU chain or ring status. The items
to be checked consist of all break points in the RRU chain or ring and the status of RRUs in the
RRU chain or ring.
If... Then...
The RRU chain or ring is operational, End the task.
The RRU chain or ring is faulty, Go to Step 2.
Step 2 Ensure that the connection between any two devices on the chain or ring hosting the RRU is
sound. The two devices can be the NodeB and RRU or two RRUs.
1. Ensure that the optical cables are properly connected to the ports labeled CPRI_W and
CPRI_E in the RRU cabling cavity, and that the connectors at both ends of the optical cables
are in sound connection.
2. Ensure that the optical cables are properly connected to the optical ports labeled OPT0,
OPT1, and OPT2 in the NodeB cabling cavity, and that the connectors at both ends of the
optical cables are in sound condition.
3. Ensure that the optical cables are properly connected to the TX and RX ports of the NodeB
and the RRU.
Step 3 Repeat Step 1 through Step 2 until the query result is normal.
----End
6.2 Checking the Networking and Link Status of the

DBS3800
This describes how to check the consistency between actual DBS3800 networking and data
configuration, and the link status between the BBU and the RRU.
1. 6.2.1 Checking the Consistency Between Actual Networking and Data Configuration of
the DBS3800

NodeB
This describes how to check the DBS3800 to ensure the consistency between hardware
installation and data configuration. The task consists of checking the RRU, BBU3806, or
BBU3806C.
2. 6.2.2 Checking the Links Between the BBU and the RRU
This describes how to check the links between the BBU and the RRU to rectify the faults
caused by improper cable connections.
6.2.1 Checking the Consistency Between Actual Networking and

Data Configuration of the DBS3800
This describes how to check the DBS3800 to ensure the consistency between hardware
installation and data configuration. The task consists of checking the RRU, BBU3806, or
BBU3806C.
Procedure
Step 1 Run the commands to check whether the DBS3800 data configuration is consistent with the
l Run the command LST RRUCHAIN to check the consistency between hardware installation
and data configuration of the RRU networking.
l Run the command LST BBU to check the consistency between hardware installation and
data configuration of the BBU networking.
If... Then...
If... Then...
----End
6.2.2 Checking the Links Between the BBU and the RRU
This describes how to check the links between the BBU and the RRU to rectify the faults caused
by improper cable connections.

NodeB
Procedure
RRU chain or ring.
If... Then...
The RRU chain or ring is faulty, Go to Step 2.
Step 2 Ensure that the connection between any two devices on the chain or ring hosting the RRU is
sound. The two devices can be the BBU and RRU or two RRUs.
CPRI_E in the RRU cabling cavity, and that the connectors at both ends of the optical cables
are in sound connection.
2. Ensure that the optical cables are properly connected to the optical ports labeled CPRI0,
CPRI1, or CPRI2 on the BBU panel, and that the connectors at both ends of the optical
cables are in sound condition.
3. Ensure that the optical cables between the BBU and the RRU are properly connected to the
RX and TX ends of the BBU or RRU.
Step 3 Run the command DSP RRUCHAINSTATE. The query result must be normal. In case of
abnormality, repeat Step 1 to Step 2 until the query result is normal.
----End
6.3 Checking the Connection for the iDBS3800 Networking

This describes how to check the consistency between actual iDBS3800 networking and data
configuration, and the link status between BBU3806, RHUB3808, and pRRU3801.
1. 6.3.1 Checking the Consistency Between Actual iDBS3800 Networking and Data
Configuration
This describes how to check the iDBS3800 to ensure the consistency between hardware
installation and data configuration. The task consists of checking the RHUB3808, checking
the pRRU3801, and checking the BBU3806.
2. 6.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU
This describes how to check the links between the BBU3806, RHUB3808, and the
pRRU3801 to rectify the faults caused by improper cable connections.
6.3.1 Checking the Consistency Between Actual iDBS3800

Networking and Data Configuration
This describes how to check the iDBS3800 to ensure the consistency between hardware
installation and data configuration. The task consists of checking the RHUB3808, checking the
pRRU3801, and checking the BBU3806.

NodeB
Procedure
Step 1 Run the commands to check whether the iDBS3800 data configuration is consistent with the
l Run the command LST RRUCHAIN to check the consistency between hardware installation
and data configuration of the RHUB3808 and pRRU3801 networking.
l Run the command LST BBU to check the consistency between hardware installation and
data configuration of the BBU3806 networking.
If... Then...
If... Then...
----End
6.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU
This describes how to check the links between the BBU3806, RHUB3808, and the pRRU3801
to rectify the faults caused by improper cable connections.
Context
The two modes to connect the BBU3806 and the pRRU3801 are as follows:
l The BBU3806 is directly connected to the pRRU3801 with optical ports.
l The BBU3806 is connected to the pRRU3801 with electrical ports through the RHUB3808.
Procedure
RRU chain or ring.
If... Then...

NodeB
If... Then...
The RRU chain or ring is faulty, l When the BBU3806 is directly connected to the
pRRU3801, the fault may occur in the
connection between BBU3806 and pRRU3801
with optical ports. Go to Step 2.
l When the BBU3806 is connected to the
pRRU3801 through the RHUB3808, the fault
may occur in the connection between the
RHUB3808 and the BBU3806 or pRRU3801
with electrical ports. Go to Step 3.
Step 2 Ensure that the connection between any two devices on the chain or ring hosting the pRRU3801
with optical ports is operational.
CPRI_E on the panel of the pRRU3801 with optical ports, and that the connectors at both
ends of the optical cables are in sound condition.
CPRI1, or CPRI2 on the BBU3806 panel, and that the connectors at both ends of the optical
3. Ensure that the optical cables between the BBU3806 and the pRRU3801 with optical ports
are properly connected to the RX and TX ends of the BBU3806 or pRRU3801 with optical
ports.
After the checking, go to Step 4.
Step 3 Ensure that the connection between any two devices on the chain or ring hosting the pRRU3801
with electrical ports is operational.
1. Ensure that the CAT5/6 cables are properly connected to the PWR_CPRI port on the panel
of the pRRU3801 with electrical ports.
2. Ensure that the CAT5/6 cables are properly connected to ports PWR0_CPRI0 through
PWR7_CPRI7 on the panel of the RHUB3808.
CPRI1, or CPRI2 on the BBU3806 panel, and that the connectors at both ends of the optical
CPRI_E on the RHUB3808 panel, and that the connectors at both ends of the optical cables
are in sound condition.
5. Ensure that the optical cables between the BBU3806 and the RHUB3808 are properly
connected to the RX and TX ends of the BBU3806 or RHUB3808.
6. Ensure the Ethernet cable between the RHUB3808 and the pRRU3801 with electrical ports
is properly connected to the transmission port of the RHUB3808 or pRRU3801 with
electrical ports.
Step 4 Run the command DSP RRUCHAINSTATE to check whether the result is normal. In case of
abnormality, go to Step 1.
----End

NodeB
Commissioning Guide 7 Checking Transmission Status on the Iub Interface
7 Checking Transmission Status on the Iub

Interface
About This Chapter
This describes how to check the transmission status on the Iub interface. The check items can
be selected on the basis of the configuration of the physical layer on the Iub interface.
7.1 Checking E1/T1 Transmission Status on the Iub Interface

This describes how to check whether the transmission is operational between the RNC and the
NodeB when they are connected through E1/T1 links.
7.2 Checking Optical Transmission Links on the Iub Interface
This describes how to check whether the optical transmission links between the NodeB and the
RNC are operational when they are connected through optical cables.
7.3 Checking Ethernet Transmission Links on the Iub Interface
This describes how to check whether the transmission links between the NodeB and the RNC
are operational when they are connected through the Ethernet.

NodeB
7 Checking Transmission Status on the Iub Interface Commissioning Guide
7.1 Checking E1/T1 Transmission Status on the Iub Interface

This describes how to check whether the transmission is operational between the RNC and the
NodeB when they are connected through E1/T1 links.
Context
The method for distinguishing the E1/T1 RX end from the E1/T1 TX end is as follows:
Connect a pin of an LED to the wire of the E1 cable, and the other pin to the shielding jacket of
the E1 cable. If the LED is on, that end is a TX end. Otherwise, that end is an RX end.
Procedure
Step 1 On the NodeB side, ensure that the E1/T1 connectors are in good contact with the Digital
Distribution Frame (DDF). Ensure sound jointing, because poor jointing may cause poor E1/T1
connection.
Step 2 Ensure that the physical connections of the E1/T1 cables are correct.
Step 3 On the NodeB side, check whether the actual number of the E1/T1 link on the DDF is consistent
with the transmission data negotiated between the NodeB and the RNC. If no, modify the data
configuration.
Step 4 On the NodeB side, run the command DSP E1T1 to query the status of the E1/T1 link.
If... Then...
The link status is The transmission links between the NodeB and the RNC are
normal, operational. End this task.
The link status is faulty, The transmission links between the NodeB and the RNC are faulty.
Go to Step 5.
Step 5 Conduct an E1/T1 physical loopback test between the RNC and the DDF on the NodeB side as
follows:
1. On the RNC side, run the SET E1T1LOP command to set Loopback Type to
REMOTE.
2. On the NodeB side, run the command DSP E1T1 to query the status of the E1/T1 link.
If... Then...
The link status is link in The links on the RNC side are faulty. Contact Huawei
physical loop, engineers for troubleshooting. Go to Step 8.
The link status is not link in The links on the NodeB side or links between NodeB and
physical loop, RNC are faulty. Go to Step 5.3.
3. On the NodeB side, run the command SET E1T1LOP to set Loopback Mode to
LOCAL.

NodeB
If... Then...
The link status is link in local loop, The transmission chip of the NodeB is
operational. Go to Step 5.5.
The link status is not link in local loop, The transmission chip of the NodeB is
faulty. Replace the chip with a new one. Go
to Step 7.
5. In general, for a pair of E1/T1s connecting the NodeB and the RNC, A is connected to C
while B is connected to D. In the loopback test, disconnect A from C, B from D, and then
connect A to B, as shown in Figure 7-1. Then a physical loopback is formed on the NodeB
side.
Figure 7-1 Physical loopback of E1/T1s on the DDF
If... Then...
The link status is link in physical loop, The links on the NodeB side are
operational but links between RNC and
NodeB are faulty. Rectify the fault.
The link status is not link in physical loop, The links on the NodeB side are faulty.
Rectify the fault.
Step 6 Set the E1s/T1s on the DDF from physical loopback to normal connection. Ensure that the
connections are sound.
Step 7 On the NodeB side, run the command SET E1T1LOP to set Loopback Mode to NOLOOP.
Step 8 On the RNC side, run the SET E1T1LOP command to set Loopback Type to NOLOOP.
----End
7.2 Checking Optical Transmission Links on the Iub

Interface
This describes how to check whether the optical transmission links between the NodeB and the
RNC are operational when they are connected through optical cables.

NodeB
Procedure
Step 1 On the NodeB side, run the command DSP STM1 to query the status of optical port for the Iub
interface.
If... Then...
The status of the optical The transmission links between the NodeB and the RNC are
port is normal operational. End this task.
The status of the optical The transmission links between the NodeB and the RNC are faulty.
port is faulty Go to Step 2.
CAUTION
If the optical port carries nothing, it is disabled for the sake of protection. In this case, the status
of the optical port queried by this command is not normal.
Step 2 Conduct the loopback test on the optical port from the RNC to the NodeB.
1. On the RNC side, run the command SET STM1LOP to set Loopback Mode to
REMOTE.
2. On the NodeB side, run the command DSP STM1 to query the status of optical port for
the Iub interface.
If... Then...
The status of the optical The links on the RNC side are faulty. Contact Huawei
port is normal engineers for troubleshooting.
The status of the optical The links on the NodeB side or optical fibers are faulty.
port is faulty Go to Step 2.3.
3. On the NodeB side, run the command SET STM1LOP to set Loopback Mode to
LOCAL.
the Iub interface.
If... Then...
The status of the optical The transmission chip of the NodeB is operational. Go to
port is optical port in local Step 2.5.
loop
The status of the optical The optical module or optical fiber is faulty. Replace the
port is not optical port in chip. Go to Step 4.
local loop
5. On the NodeB side, connect the TX end to the RX end of the optical fiber.
the Iub interface.

NodeB
If... Then...
The status of the optical The NodeB optical module is operational but the optical
port is normal fiber between the NodeB and the RNC is faulty. Rectify
the fault.
The status of the optical The NodeB optical module is faulty. Replace the optical
port is faulty module.
Step 3 Restore the optical fiber connecting the RX and TX ends on the NodeB side.
Step 4 On the NodeB side, run the command SET STM1LOP to set Loopback Mode to NOLOOP.
----End
7.3 Checking Ethernet Transmission Links on the Iub

Interface
This describes how to check whether the transmission links between the NodeB and the RNC
are operational when they are connected through the Ethernet.
Procedure
Step 1 Run the command DSP ETHPORT to check whether the MAC address is consistent with the
address on the board label.
If... Then...
The two addresses are inconsistent, Replace the board.
The two addresses are consistent, Go to Step 2.
Step 2 Check whether the Ethernet cables are properly connected to the Ethernet adapters.
If... Then...
The cables are poorly connected, Reconnect the cables and check whether the
faults are rectified.
The cables are properly connected, Go to Step 3.
Step 3 Run the command LST ETHPORT to check whether the rate and duplex mode are correctly
set. Ensure that the rate is set to 100M and the duplex mode is set to FULL.
If... Then...
The rate and duplex mode are incorrectly set, Run the command SET ETHPORT to reset
the rate and duplex mode.
The rate and duplex mode are correctly set, Go to Step 4.

NodeB
Step 4 Check other Ethernet adapters.

If... Then...
The transmission is still faulty, The adapter may be damaged. Replace the
associated parts.
The network is operational, End the task.
----End

NodeB
Commissioning Guide 8 Checking the Running Status of the NodeB
8 Checking the Running Status of the NodeB
About This Chapter
This task describes how to check the running status of the NodeB to ensure proper working and
to rectify faults in working.
1. 8.1 Commissioning SNTP

This describes how to commission the Simple Network Time Protocol (SNTP) to
synchronize the time between NEs and to keep the operating time consistent, such as the
operating time of alarms. The task facilitates the centralized maintenance and management.
2. 8.2 Checking the Status of a Cell
This describes how to check the status of a local cell or a logical cell. The task helps you
learn the running state of the active cell and perform OM on the cell.
3. 8.3 Measuring RTWP
This describes how to measure RTWP of NodeB to calibrate the parameters related to uplink
RF channel. Measuring RTWP does not affect services.
4. 8.4 Monitoring Output Power
This describes how to monitor output power. The monitoring covers typical output power
and output power of each carrier.

NodeB
8 Checking the Running Status of the NodeB Commissioning Guide
8.1 Commissioning SNTP

This describes how to commission the Simple Network Time Protocol (SNTP) to synchronize
the time between NEs and to keep the operating time consistent, such as the operating time of
alarms. The task facilitates the centralized maintenance and management.
Prerequisite
You have logged in to the NodeB LMT.
Context
Application of the SNTP can synchronize the time (year/month/date/hour/minute/second)
between multiple SNTP clients in real time by using a unique SNTP server.
Procedure
Step 1 Start the SNTP server. An SNTP server can be on the RNC side or on the M2000 side, which
depends on the actual condition.
l On the RNC side: Start the SNTP server on the security and monitor manager on the BAM
server.
l On the M2000 server side: The Sun operating system has the self-contained SNTP services.
For details, refer to the M2000 Administrator Guide.
Step 2 Run the command SET SNTPCLTPARA to set the parameters of SNTP clients.
Parameter Name Description
SW Switch of Time Sync Switch of Time Sync

Value range: ON (synchronization
required), OFF (synchronization not
required)
Default value: none
IP SNTP Server IP Address Value range: 0.0.0.1 to 255.255.255.254

Default value: none
SP Synchronization period Value range: 1 to 525600

(minute) Unit: minute
Default value: none
Step 3 Run the command LST SNTPCLTPARA to query the parameters of SNTP clients.
If.. Then..
The setting is correct, Go to Step 4.
The setting is incorrect, Go to Step 2 to reset parameters.

NodeB
Step 4 After setting the synchronization period in Step 2, run the command LST
SNTPCLTLATESTSUCCDATE to query the time of the latest successful synchronization of
the SNTP clients to the SNTP server, and check whether the synchronization is successful.
If.. Then..
The synchronization is successful, End this task.
The synchronization fails, Check the following:

l Whether the SNTP server is started.
l Whether the IP address of the NodeB is correct.
After the faults are rectified, go to Step 2 to reset

parameters.
----End
8.2 Checking the Status of a Cell

This describes how to check the status of a local cell or a logical cell. The task helps you learn
the running state of the active cell and perform OM on the cell.
Procedure
Step 1 Run the command DSP LOCELL to check the statuses of all local cells and logical cells.
Step 2 If a local cell or a logical cell is faulty, rectify the fault according to the related LMT Alarm
Online Help.
----End
8.3 Measuring RTWP

This describes how to measure RTWP of NodeB to calibrate the parameters related to uplink
RF channel. Measuring RTWP does not affect services.
8.3.1 Measuring the RTWP of the Macro NodeB

This describes how to measure the RTWP of the macro NodeB. You can calibrate the gain of
uplink RF channels through RTWP measurement. The NodeB RTWP test has no impact on the
services.
8.3.2 Measuring the RTWP of the Distributed NodeB
This describes how to measure the RTWP of the distributed NodeB. You can calibrate the gain
of uplink RF channels through RTWP measurement. The NodeB RTWP test has no impact on
the services.
8.3.1 Measuring the RTWP of the Macro NodeB

This describes how to measure the RTWP of the macro NodeB. You can calibrate the gain of
uplink RF channels through RTWP measurement. The NodeB RTWP test has no impact on the
services.

NodeB
Context
Analyses of the RTWP measurement are as follows:
l If the NodeB is not connected to the antenna system or a matched load, the RTWP is about
-108 dBm. If the NodeB is connected to the antenna system (with TMA switched on) or a
matched load, the RTWP is about -105 dBm.
l If the services are normal and the uplink load reaches 75%, the RTWP is 6 dB higher than
the RTWP when the NodeB does not carry any service.
NOTE
l When the reported RTWP is valid, the curve is normal. The vertical axis corresponds to the reported
RTWP with the unit of 0.1 dBm.
l When the reported RTWP is invalid, abnormal RTWP curves are displayed. The RTWP for the main
antenna forms a horizontal line at -112 dBm on the vertical axis. The RTWP for the diversity antenna
forms a horizontal line at -111.5 dBm on the vertical axis. The error may lie in the absent MTRU/
MRRU, a broken link, or a faulty channel. In this case, clear the fault first.
Procedure
Step 2 Double-click Realtime Specific Monitoring > RTWP Measurement. The RTWP
Measurement dialog box is displayed, as shown in Figure 8-1.
Figure 8-1 RTWP Measurement dialog box
Step 3 Set the parameters in the dialog box.
Step 4 Click OK. A monitoring window is displayed, showing the current monitoring task in graphs.
Step 5 Stop the test in one of the following ways.
Method 1: Close the task monitoring window directly to end all monitoring tasks of the
active window.
Method 2: Right-click the monitoring task list pane, choose Delete Task from the shortcut
menu. The curve displayed with the task is also deleted.

NodeB
----End
8.3.2 Measuring the RTWP of the Distributed NodeB

This describes how to measure the RTWP of the distributed NodeB. You can calibrate the gain
of uplink RF channels through RTWP measurement. The NodeB RTWP test has no impact on
the services.
Context
Reference criteria of the RTWP measurement are as follows:
l If the NodeB is not connected to the antenna system or a matched load, the RTWP is about
-108 dBm. If the NodeB is connected to the antenna system (with TMA switched on) or a
matched load, the RTWP is about -105 dBm.
l If the services are normal and the uplink load reaches 75%, the RTWP is 6 dB higher than
the RTWP when the NodeB does not carry any service.
NOTE
l When the reported RTWP is valid, the curve is normal. The vertical axis corresponds to the reported
RTWP with the unit of 0.1 dBm.
l When the reported RTWP is invalid, abnormal RTWP curves are displayed. The RTWP for the main
antenna forms a horizontal line at -112 dBm on the vertical axis. The RTWP for the diversity antenna
forms a horizontal line at -111.5 dBm on the vertical axis. The error may lie in the absent RRU, a
broken link, or a faulty channel. In this case, clear the fault first.
Procedure
Step 2 Double-click Realtime Specific Monitoring > RTWP Measurement. The RTWP
Measurement dialog box is displayed, as shown in Figure 8-2.
Figure 8-2 RTWP Measurement dialog box

NodeB
active window.
----End
8.4 Monitoring Output Power

This describes how to monitor output power. The monitoring covers typical output power and
output power of each carrier.
8.4.1 Monitoring Output Power of the MTRU

This describes how to monitor output power of the MTRU, including the typical output power
and carrier output power.
8.4.2 Monitoring the Output Power of the RRU/pRRU
This describes how to monitor the output power of the RRU/pRRU. The output power test
measures the output power of the RRU/pRRU, including the typical output power and output
power of each carrier.
8.4.1 Monitoring Output Power of the MTRU

This describes how to monitor output power of the MTRU, including the typical output power
and carrier output power.
Context
If the test is started, the system reports the typical output power and each carrier every two
seconds.
Configuration of the NodeB output power depends on the specified services.
If the pilot power is 33 dBm and typical output power is 43 dBm, the difference between the
MTRU/MTRU output power and the pilot power should not be large when the NodeB does not
carry services. If the RRU/pRRU output power is much lower than the pilot power, the MTRU
output power must be abnormal.
Procedure
Step 2 Double-click Realtime Specific Monitoring > Output Power Monitoring. The Output Power
Monitoring dialog box is displayed, as shown in Figure 8-3.

NodeB
Figure 8-3 Output Power Monitoring dialog box
active window.
----End
8.4.2 Monitoring the Output Power of the RRU/pRRU

This describes how to monitor the output power of the RRU/pRRU. The output power test
measures the output power of the RRU/pRRU, including the typical output power and output
power of each carrier.
Context
If the test is started, the system reports the typical output power and each carrier every two
seconds.
Configuration of the RRU/pRRU output power depends on the specified services.
The pilot power and typical power can be set as follows:

l RRU: The pilot power can be set to 33 dBm and the typical power can be set to 43 dBm.
l pRRU: The pilot power can be set to 20 dBm and the typical power can be set to 27 dBm.
The different from the output power and the pilot power of RRU/pRRU is about 3 dBm when
the NodeB does not carry any service. If the RRU/pRRU output power is much lower than the
pilot power, the RRU/pRRU output power must be abnormal.

NodeB
Procedure
Step 2 Double-click Realtime Specific Monitoring > Output Power Monitoring. The Output Power
Monitoring dialog box is displayed, as shown in Figure 8-4.
Figure 8-4 Output Power Monitoring dialog box

active window.
----End

NodeB
Commissioning Guide 9 Measuring the NodeB VSWR
9 Measuring the NodeB VSWR
This describes how to check the VSWR. The VSWR is used to verity whether the antenna system
is correctly installed.
Prerequisite
l The NodeB does not provide any service or the services are isolated.
Context
An excessively large VSWR results in short transmission distance, thus affecting the normal
operation of the communication system. The normal VSWR ranges from 1 to 1.8. The VSWR
less than 1.5 is preferred.
CAUTION
During testing of the VSWR, the services of the NodeB are interrupted. Therefore, you are
advised to test the VSWR when the service volume is light or after the NodeB services are
isolated.
Procedure
Step 1 Run the STR VSWRTEST command to check the NodeB VSWR.
----End
Postrequisite
1. Check that the antenna system is correctly installed based on the measured VSWR.
2. Ensure the NodeB services are resumed.

NodeB
Commissioning Guide 10 Commissioning the Alarm Equipment of NodeB
10 Commissioning the Alarm Equipment of

NodeB
About This Chapter
This task describes how to commission the alarm equipment of NodeB, including adding the
alarm monitoring equipment, setting external alarms, and checking external alarms.
10.1 Adding the Alarm Equipment to the NodeB

This describes how to add the alarm equipment to the NodeB to monitor the environment
specifications in real time, thus ensuring that the NodeB can work properly.
10.2 Setting External Alarms of the NodeB
This task describes how to set external alarm port. You can set parameters of the external alarm
port of the NodeB and the binding between the port and the customized alarm ID.
10.3 Checking the External Alarm Port of NodeB
This task describes how to check the external alarm port of NodeB, such as to check the setting
of the external alarm port.

NodeB
10 Commissioning the Alarm Equipment of NodeB Commissioning Guide
10.1 Adding the Alarm Equipment to the NodeB

This describes how to add the alarm equipment to the NodeB to monitor the environment
specifications in real time, thus ensuring that the NodeB can work properly.
10.1.1 Adding the Alarm Equipment to the BTS3812E

This describes how to add the alarm equipment to the BTS3812E to monitor the environment
specifications in real time, thus ensuring that the BTS3812E equipment can work properly.
10.1.2 Adding the Alarm Equipment to the BTS3812AE
This describes how to add the alarm equipment to the BTS3812AE to monitor the environment
specifications in real time, thus ensuring that the BTS3812AE equipment can work properly.
10.1.3 Adding the Alarm Equipment to the Distributed NodeB
This describes how to add the alarm equipment to the distributed NodeB to monitor the
environment specifications in real time, thus ensuring that the distributed NodeB equipment can
work properly.
10.1.1 Adding the Alarm Equipment to the BTS3812E

This describes how to add the alarm equipment to the BTS3812E to monitor the environment
specifications in real time, thus ensuring that the BTS3812E equipment can work properly.
Procedure
l Add an Environment Monitoring Instrument (EMI).
1. Run the command LST SUBRACK to check whether the subrack is configured as
listed in Table 10-1.
If... Then...
The configurations The EMI subrack is configured. Go to Step 5.

are consistent
The configurations The EMI subrack is not configured. Go to Step 2.

are inconsistent
2. Run the command ADD SUBRACK to add a subrack.

3. Set the parameters of the subrack, as listed in Table 10-1.
Table 10-1 Parameters of the subrack
Name Value
Cabinet No. MASTER
Subrack No. 6
Subrack Type EXT

NodeB
4. Click . The system displays a message that the execution is successful. The
configuration of the subrack is complete.
5. Run the command LST BRD to check whether the board is configured as listed in
Table 10-2.
If... Then...
The configurations The EMI board is configured. End the operation.

are consistent
The configurations The EMI board is not configured. Go to Step 6.

are inconsistent
6. Run the command ADD BRD to add a board.

7. Set parameters of the board, as listed in Table 10-2.
Table 10-2 Parameters of the board
Name Value
Cabinet No. MASTER
Subrack No. 6
Slot No. 0
Board Type NEMU
setting of the board is complete.
l Add an NMON.
1. Run the command LST BRD to check whether the board is configured as listed in
Table 10-3.
If... Then...
The configurations The NMON is configured. End the operation.

are consistent
The configurations The NMON is not configured. Go to Step 2.

are inconsistent
2. Run the command ADD BRD to add a board.

3. Set parameters of the board, as listed in Table 10-3.
Table 10-3 Parameters of the board
Name Value
Cabinet No. MASTER

NodeB
Name Value
Subrack No. 0
Slot No. 16
Board Type NMON
setting of the board is complete.
----End
10.1.2 Adding the Alarm Equipment to the BTS3812AE

This describes how to add the alarm equipment to the BTS3812AE to monitor the environment
specifications in real time, thus ensuring that the BTS3812AE equipment can work properly.
Prerequisite
Before adding the alarm equipment, check whether the BTS3812AE is configured with the alarm
equipment.
l Run the command LST BRD to check whether the board is configured as listed in Table
10-4.
If... Then...
The configurations are The alarm equipment is configured. No operation is required.

consistent,
The configurations are No alarm equipment is configured. Therefore perform the

inconsistent, following operations.
Procedure
Step 1 Run the command ADD BRD to add a board.
Step 2 Set parameters of the board, as listed in Table 10-4.
Table 10-4 Setting parameters of the board
Name Value
Cabinet No. MASTER
Subrack No. 0
Slot No. 16
Board Type NMON

NodeB
Step 3 Click . The system displays a message that the execution is successful. The configuration
of the board is complete.
----End
10.1.3 Adding the Alarm Equipment to the Distributed NodeB

This describes how to add the alarm equipment to the distributed NodeB to monitor the
environment specifications in real time, thus ensuring that the distributed NodeB equipment can
work properly.
Procedure
Step 1 Run the command LST SUBRACK to check whether the subrack is configured as listed in
Table 10-5.
If... Then...
The configurations are The subrack of the environment monitoring device is configured.
consistent Go to Step 5.
The configurations are The subrack of the environment monitoring device is not
inconsistent configured. Go to Step 2.
Step 2 Run the command ADD SUBRACK to add a subrack.
Step 3 Set the parameters of the subrack, as listed in Table 10-5.
Table 10-5 Parameters of the subrack
Name Value
Cabinet No. MASTER
Subrack No. 6
Subrack Type EXT
of the subrack is complete.
Step 5 Run the command LST BRD to check whether the board is configured as listed in Table
10-6.
If... Then...
The configurations are The board of the environment monitoring device is configured. End
consistent the operation.
The configurations are The board of the environment monitoring device is not configured.
inconsistent Go to Step 6.

NodeB
Step 6 Run the command ADD BRD to add a board.
Step 7 Set parameters of the board, as listed in Table 10-6.
Table 10-6 Setting parameters of the board
Name Value
Cabinet No. MASTER
Subrack No. 6
Slot No. 0
Board Type NEMU
of the board is complete.
----End
10.2 Setting External Alarms of the NodeB

This task describes how to set external alarm port. You can set parameters of the external alarm
port of the NodeB and the binding between the port and the customized alarm ID.
10.2.1 Setting the External Alarm Port of the BTS3812E

This describes how to set the external alarm port of the BTS3812E. You can set parameters of
the external alarm port of the BTS3812E and also the binding between the external alarm port
and the customized alarm ID.
10.2.2 Setting the External Alarm Port of the BTS3812AE
This describes how to set the external alarm port of the BTS3812AE. You can set parameters
of the external alarm port of the BTS3812AE and also the binding between the external alarm
port of the BTS3812AE and the customized alarm ID.
10.2.3 Setting External Alarm Port of the Distributed NodeB
This describes how to set the external alarm port of the distributed NodeB. You can set
parameters of the external alarm port of the the distributed NodeB and also the binding between
the external alarm port and the customized alarm ID.
10.2.1 Setting the External Alarm Port of the BTS3812E

This describes how to set the external alarm port of the BTS3812E. You can set parameters of
the external alarm port of the BTS3812E and also the binding between the external alarm port
and the customized alarm ID.
Context
According to the port type, the setting of external alarm can be of two types: setting of the
Boolean alarm port and setting of the analog alarm port.

NodeB
Procedure
l Set the Boolean alarm port.
1. Run the command SET ALMPORT to set the external alarm port.
2. Set the parameters of the Boolean alarm port, as listed in Table 10-7.
Table 10-7 Setting parameters of the Boolean alarm port
Name Value
Cabinet No. MASTER
Subrack No. l NEMU: 6

l NMON: 0
Slot No. l NEMU: 0

l NMON: 16
Port No. Value range: 0 to 31

l NEMU: corresponding to Boolean inputs 1 to 32 and to
ports S1+/S1- to S32+/S32- for Boolean signals detection
of the EMUA
l NMON: corresponding to external Boolean input alarms
0 to 31. For details about the relationship, refer to
Boolean Input Cable of the BTS3812E.
Work Mode l Select CUSTOM, if configured.

l Select OFF, if not configured.
Port Type Set to BOOL.

l If Work Mode is CUSTOM, this parameter is valid.
l If the parameter is null, the existing type is retained.
Alarm ID Value range: 65334 to 65534

l If the parameter is null, the existing binding is retained.
Alarm Voltage Value range: HIGH, LOW

If the parameter is null, the existing configuration is
retained.
setting of the Boolean alarm port is complete.
l Set the analog alarm.
NOTE
If the external ports 32 to 35 are required, perform the following steps:
2. Set the parameters of the analog alarm port, as listed in Table 10-8.

NodeB
Table 10-8 Setting parameters of the analog alarm port
Name Value
Cabinet No. MASTER
Subrack No. 6
Slot No. 0

l Corresponding to external analog alarms 1 to 4
l Corresponding to ports ANA1 to ANA4 of analog
signals detection of the EMUA

Port Type Set to VALUE.


l If the parameter is null, the existing binding is
retained.
Upper Alarm Occur Set as required. If the parameter is null, the existing
Limit configuration is retained.
Lower Alarm Occur Set as required. If the parameter is null, the existing
Limit configuration is retained.
setting of the analog alarm port is complete.
----End
10.2.2 Setting the External Alarm Port of the BTS3812AE

This describes how to set the external alarm port of the BTS3812AE. You can set parameters
of the external alarm port of the BTS3812AE and also the binding between the external alarm
port of the BTS3812AE and the customized alarm ID.
Context
The external alarm port of the BTS3812AE is the Boolean alarm port. Therefore, to set the
external alarm of the BTS3812AE is to set the Boolean alarm.
Procedure
Step 1 Run the command SET ALMPORT to set the external alarm port.

NodeB
Step 2 Set the parameters of the Boolean alarm port, as listed in Table 10-9.
Name Value
Cabinet No. MASTER
Subrack No. 0
Slot No. 16

NMON: corresponding to external input Boolean alarms 0 to 31.
For details about the relationship, refer to Boolean Input Cable of
the BTS3812AE.




If the parameter is null, the existing configuration is retained.
Step 3 Click . The system displays a message that the execution is successful. The setting of the
Boolean alarm port is complete.
----End
10.2.3 Setting External Alarm Port of the Distributed NodeB

This describes how to set the external alarm port of the distributed NodeB. You can set
parameters of the external alarm port of the the distributed NodeB and also the binding between
the external alarm port and the customized alarm ID.
Context
According to the port type, the setting of external alarm port can be of two types: setting of the
Boolean alarm port and setting of the analog alarm port.
Set the parameters of external alarm port according to the configuration of auxiliary equipment.
l When the AFB or OFB is configured as auxiliary equipment, the Boolean alarm alarms of
the AFB or OFB are used as the external alarms of the BBU. For details about setting

NodeB
parameters, refer to 10.2.3.1 Sample 1: Setting AFB Alarms and 10.2.3.2 Sample 2:
Setting OFB Alarms.
l When the APM30 or APM100 is configured as auxiliary equipment, the external alarms
of the APM30 or APM100 are reported to the BBU through RS485 port. Setting the
parameters of external alarms is unnecessary.
Procedure
l Set the Boolean alarm port.
2. Set the parameters of the Boolean alarm port, as listed in Table 10-10.
Table 10-10 Setting the parameters of the Boolean alarm port
Name Value
Cabinet No. MASTER
Subrack No. l NEMU: 6

l HBBU/HBBUC: 0
Slot No. 0
Port No. l NEMU: 0 to 31, corresponding to Boolean inputs 1 to 32

and corresponding to ports S1+/S1- to S32+/S32- for
Boolean signals detection of the EMUA
l HBBU: 0 to 3, corresponding to four external Boolean
alarms and cables labeled Switch_input+0/-0 to
Switch_input+3/-3. For details about the port
relationship, refer to Boolean Input Cable of the
BBU3806 (Supporting 4-Channel Alarm Signals).
l HBBUC: 0 to 3, corresponding to four external Boolean
alarms and cables labeled BBU-SWITCH-INPUT0+/0-
to BBU-SWITCH-INPUT3+/3-. For details about the
ports, refer to Boolean Input Cable of the BBU3806C.




If the parameter is null, the existing configuration is
retained.

NodeB
setting of the Boolean alarm port is complete.
l Set the analog alarm port.
NOTE
If the external ports 32 to 35 are required, perform the following steps:
2. Set the parameters of the analog alarm port, as listed in Table 10-11.
Table 10-11 Setting the parameters of the analog alarm port
Name Value
Cabinet No. MASTER
Subrack No. 6
Slot No. 0

l Corresponding to external analog alarm 1 to 4
l Corresponding to ports ANA1 to ANA4 of
analog signals detection of the EMUA

Port Type Set to VALUE.

l If Work Mode is CUSTOM, this parameter is
valid.
l If the parameter is null, the existing type is
retained.

l If Work Mode is CUSTOM, this parameter is
valid.
l If the parameter is null, the existing binding is
retained.
Upper Alarm Occur Limit Set as required. If the parameter is null, the existing
configuration is retained.
Lower Alarm Occur Limit Set as required. If the parameter is null, the existing
configuration is retained.
setting of the analog alarm port is complete.
----End

NodeB
Sample 1: Setting AFB Alarms

This describes how to set AFB alarms. When the AFB is configured, its Boolean alarms, as the
external alarms of the BBU3806, brings the alarm signal of the power module, the heat
exchanger, and the surge protector to the BBU3806.
Procedure
Name Value
Cabinet No. MASTER
Subrack No. 0
Slot No. 0
Port No. Value range: 0 to 3. For the connection between the BBU3806 and the
Boolean input cables, refer to Boolean Input Cable of the BBU3806 (for
AFB).
l Value: 0, corresponding to the power module.
l Value: 1, corresponding to the heat exchanger.
l Value: 2, corresponding to the surge protector.
Work Mode Value: CUSTOM
Port Type Set to BOOL
Alarm Voltage Value: HIGH
----End
Postrequisite
Set the alarm name of Boolean alarm port on M2000.
Sample 2: Setting OFB Alarms

This describes how to set OFB alarms. When the OFB is configured, its Boolean alarms, as the
external alarms of the BBU, brings the alarm signal of the DC power distribution box, the heat
exchanger, and the surge protector to the BBU.

NodeB
Procedure
Table 10-13 Setting the parameters of the Boolean alarm port
Name Value
Cabinet No. MASTER
Subrack No. 0
Slot No. 0
Port No. Value range: 0 to 3. For the connection between the BBU3806 and the
Boolean input cables of the OFB, refer to OFB User Guide.
l Value: 0, corresponding to the DC power distribution box.
l Value: 1, corresponding to the heat exchanger.
l Value: 2, corresponding to the door status sensor.
Work Mode Value: CUSTOM
Port Type Set to BOOL
Alarm Voltage Value: HIGH
----End
Postrequisite
Set the alarm name of Boolean alarm port on M2000.
10.3 Checking the External Alarm Port of NodeB

This task describes how to check the external alarm port of NodeB, such as to check the setting
of the external alarm port.
Procedure
Step 1 Run the command LST ALMPORT to query the status of external alarm port.
Step 2 Enter the number of the external alarm port to be queried.

NOTE
If the port number is not specified, configurations of all the alarm ports are queried.

NodeB
Step 3 Click to view the result.

Step 4 Check the external alarm port setting according to the query result.
If... Then...
The external alarm port is incorrectly set, Modify the setting. For details, refer to 10.2
Setting External Alarms of the NodeB.
The external alarm port is correctly set, Go to Step 5.
Step 5 Check whether the reported alarm is consistent with the external alarm.
For example, enable the Boolean alarm to be reported in high level. Then, disconnect the cables
of port S1+/S1- of the EMUA. If port 0 reports the alarm, then the reported alarm is consistent
with the external alarm.
----End

NodeB
Commissioning Guide 11 Checking the ALD
11 Checking the ALD
About This Chapter
This describes how to check the Antenna Line Device (ALD). The task consists of checking the
RET antenna and checking the Smart Tower Mounted Amplifier (STMA).
11.1 Checking the RET Antenna

This describes how to check the RET antenna. The task consists of the following: setting the
ALD power switch, adding ALDs, downloading the data configuration file of the RET antenna,
calibrating the RET antenna, setting the downtilt of the RET antenna, and querying the current
downtilt of the RET antenna.
11.2 Checking the STMA
This describes how to check the Smart Tower Mounted Amplifier (STMA), part of the antenna
system, to amplify the received weak signals. Check the STMA to ensure that the STMA works
properly and to adjust the gain of the STMA and the uplink coverage range of NodeB.

NodeB
11 Checking the ALD Commissioning Guide
11.1 Checking the RET Antenna

This describes how to check the RET antenna. The task consists of the following: setting the
ALD power switch, adding ALDs, downloading the data configuration file of the RET antenna,
calibrating the RET antenna, setting the downtilt of the RET antenna, and querying the current
Prerequisite
Table 11-1 lists the items to be prepared before checking RET antenna.
Table 11-1 Preparations before checking RET antenna
Item Description
Obtain the vendor information and Obtain the vendor information and model of the RET
model of the RET antenna antenna to download the correct configuration files of
RET antenna.
Obtain the data configuration files of l Configuration data of the RET antennas varies with
the RET antenna vendors and models.
l The NodeB software package includes the data
configuration file of the RET antenna.
Obtain the downtilt of the RET The downtilt of the RET antenna is determined in
antenna network planning.
Obtain the equipment serial number The equipment serial number of the cascaded RET
of the cascaded RET antenna (if antenna is recorded during hardware installation.
commissioning of the cascaded RET NOTE
antenna is required) Fail to support obtaining the equipment serial number by
running the command SCAN ALD.
1. 11.1.1 Setting the ALD Power Switch

This describes how to set the ALD power switch. The ALD power switch is in OFF state
by default. To use the RET antenna or the TMA, you need to set the ALD power switch to
ON and set the current alarm thresholds.
2. 11.1.2 Adding ALDs
This describes how to add ALDs to the NodeB data when the NodeB to be commissioned
requires the RET antenna or the TMA.
3. 11.1.3 Downloading the Data Configuration File of the RET Antenna
This describes how to download the configuration data that maps with the RET antenna
model to enable the RET antenna to work properly.
4. 11.1.4 Calibrating the RET Antenna
This describes how to calibrate the location and control the precision according to the
antenna data configuration file and physical capability, thus ensuring that all the downtilts
of the RET antenna are correctly set.
5. 11.1.5 Setting the Downtilt of the RET Antenna

NodeB
This describes how to set the downtilt of the RET antenna. The task may affect the antenna
coverage. Therefore, the downtilt should be kept consistent with network planning.
6. 11.1.6 Querying the Current Downtilt of the RET Antenna
This describes how to query the current downtilt of the RET antenna to verify whether the
configured downtilt is valid.
11.1.1 Setting the ALD Power Switch

This describes how to set the ALD power switch. The ALD power switch is in OFF state by
default. To use the RET antenna or the TMA, you need to set the ALD power switch to ON and
set the current alarm thresholds.
Prerequisite
l The MAFU of the RRU corresponding to the antenna port works properly.
Procedure
Step 1 Run the command LST SUBRACK to query the subrack number of the MAFU/RRU.
NOTE
Skip this step if the RRU is not configured. The subrack number of the MAFU is fixed to 3.
Step 2 Run the command SET ALDPWRSW to set the ALD power switch and current alarm
thresholds.
----End
11.1.2 Adding ALDs

This describes how to add ALDs to the NodeB data when the NodeB to be commissioned requires
the RET antenna or the TMA.
Prerequisite
Context
l The ALD contains AISG_RET and AISG_TMA, and both of them support the Antenna
Interface Standard Group (AISG) protocol.
l For the RET antenna system, the AISG_TMA is optional while the AISG_RET is
mandatory.
l This task is not required if the ALD has been configured in the data configuration file.
Procedure
l Run the command ADD ALD to add an AISG_RET or AISG_TMA.

NodeB
CAUTION
After adding the ALD, wait for about one minute for initialization.
----End
11.1.3 Downloading the Data Configuration File of the RET

Antenna
This describes how to download the configuration data that maps with the RET antenna model
to enable the RET antenna to work properly.
Prerequisite
l The configuration data of the RET antenna to be checked is obtained.
l The FTP server works properly and is correctly connected to the NodeB in the same Intranet.
l The given name and password of the specified FTP server are consistent with the actual
ones. Ensure that you have the right to visit the specified directories.
Context
The configuration data of the RET antenna is provided by the vendor. The configuration data
varies with antenna models.
Procedure
Step 1 Run the command DLD ALDCFG to download the configuration data.
Step 2 Repeat Step 1 to download configuration data for other RET antennas when multiple RET
antennas are configured for the NodeB.
NOTE
Ensure that configuration data is downloaded for all the RET antennas.
----End
11.1.4 Calibrating the RET Antenna

This describes how to calibrate the location and control the precision according to the antenna
data configuration file and physical capability, thus ensuring that all the downtilts of the RET
antenna are correctly set.
Prerequisite

NodeB
Context
CAUTION
l The calibration is mandatory after the RET antenna is installed. Otherwise, the correctness
of the antenna downtilt and the network coverage may be affected.
l It takes two to four minutes to calibrate one antenna.
l It is unnecessary to recalibrate the RET after you reset or power off the RET antenna.
l The downtilt after calibration is unpredictable, thus affecting the coverage range. Therefore,
reset the antenna downtilt after calibration. For details, refer to 11.1.5 Setting the Downtilt
of the RET Antenna.
Procedure
Step 1 Run the command CLB ANT to calibrate the RET antenna.
Step 2 Repeat Step 1 to calibrate all the RET antennas when multiple RET antennas are configured.
NOTE
All the RET antennas must be calibrated.
----End
11.1.5 Setting the Downtilt of the RET Antenna

This describes how to set the downtilt of the RET antenna. The task may affect the antenna
coverage. Therefore, the downtilt should be kept consistent with network planning.
Prerequisite
Context
CAUTION
l Ensure that you have added an RET antenna before setting the antenna downtilt. For details,
refer to 11.1.2 Adding ALDs.
l Ensure that you have calibrated the antenna before setting the antenna downtilt. For details,
refer to 11.1.4 Calibrating the RET Antenna.
l It takes at most two minutes to set the RET antenna downtilt.
Procedure
Step 1 Run the command LST SITE to query the site number and name.

NodeB
Step 2 Run the command LST ANTTILTRNG to query the antenna downtilt range.
Step 3 Run the command SET ANTTILT to set the RET antenna downtilt.
Step 4 Repeat Step 3 to set downtilts of other RET antennas when multiple sectors are configured.
NOTE
Ensure that downtilts of all the RET antennas are consistent with network planning.
----End
11.1.6 Querying the Current Downtilt of the RET Antenna

This describes how to query the current downtilt of the RET antenna to verify whether the
configured downtilt is valid.
Prerequisite
l The downtilt of the RET antenna is correctly set.
Procedure
Step 1 Run the command DSP ANTTILT to query the current downtilt and configured downtilt of the
RET antenna.
Step 2 Repeat Step 1 to query current downtilts of other RET antennas when multiple RET antennas
are configured.
Step 3 Check whether the current downtilt of each RET antenna is consistent with the configured
downtilt.
If... Then...
The two downtilts are consistent, End the task.
The two downtilts are inconsistent, Refer to 11.1.5 Setting the Downtilt of the RET
Antenna to reset the downtilt.
----End
11.1.7 MML Commands Related to the RET Antenna

This describes the MML commands related to the RET antenna. You can operate the RET
antenna by running the related commands.
Command Description
ADD ALD Adding an ALD
CLB ANT Calibrating the RET antenna
DSP ANTTILT Querying the current downtilt of the RET

antenna

NodeB
Command Description
DSP ANTCON Querying the work status of the antenna port
DSP ALDDEV Querying the ALD data
DSP ALDVER Querying the ALD version
DLD ALDCFG Downloading the configuration data file of the

RET antenna
DLD ALDSW Downloading the ALD software
LST ANTTILTRNG Querying the downtilt range of the antenna
LST ALDPWRSW Querying the ALD power switch
LST ALD Querying configuration of all the ALDs
RMV ALD Deleting the ALD
RST ALD Resetting the ALD
RST ALDPWRSW Resetting the ALD power switch
MOD ALD Modifying the ALD configuration
SCN ALD Scanning the ALD
SET ALDPWRSW Setting the ALD power switch
SET ANTTILT Setting the current downtilt of the RET antenna
11.2 Checking the STMA

This describes how to check the Smart Tower Mounted Amplifier (STMA), part of the antenna
system, to amplify the received weak signals. Check the STMA to ensure that the STMA works
properly and to adjust the gain of the STMA and the uplink coverage range of NodeB.
1. 11.2.1 Setting the ALD Power Switch

This describes how to set the ALD power switch. The ALD power switch is in OFF state
by default. To use the RET antenna or the TMA, you need to set the ALD power switch to
ON and set the current alarm thresholds.
2. 11.2.2 Adding ALDs
This describes how to add ALDs to the NodeB data when the NodeB to be commissioned
requires the RET antenna or the TMA.
3. 11.2.3 Setting the Gain of the STMA
This describes how to set the gain of the STMA to balance the amplifying gain of the uplink
signals and the uplink coverage.
4. 11.2.4 Querying the Gain of the STMA
This describes how to query the gain of the STMA to check whether the gain is correctly
set.

NodeB
11.2.1 Setting the ALD Power Switch

This describes how to set the ALD power switch. The ALD power switch is in OFF state by
default. To use the RET antenna or the TMA, you need to set the ALD power switch to ON and
set the current alarm thresholds.
Prerequisite
l The MAFU of the RRU corresponding to the antenna port works properly.
Procedure
Step 1 Run the command LST SUBRACK to query the subrack number of the MAFU/RRU.
NOTE
Skip this step if the RRU is not configured. The subrack number of the MAFU is fixed to 3.
Step 2 Run the command SET ALDPWRSW to set the ALD power switch and current alarm
thresholds.
----End
11.2.2 Adding ALDs

This describes how to add ALDs to the NodeB data when the NodeB to be commissioned requires
the RET antenna or the TMA.
Prerequisite
Context
l The ALD contains AISG_RET and AISG_TMA, and both of them support the Antenna
Interface Standard Group (AISG) protocol.
l For the RET antenna system, the AISG_TMA is optional while the AISG_RET is
mandatory.
l This task is not required if the ALD has been configured in the data configuration file.
Procedure
l Run the command ADD ALD to add an AISG_RET or AISG_TMA.
CAUTION
After adding the ALD, wait for about one minute for initialization.
----End

NodeB
11.2.3 Setting the Gain of the STMA

This describes how to set the gain of the STMA to balance the amplifying gain of the uplink
signals and the uplink coverage.
Prerequisite
Procedure
Step 1 Run the command SET TMAGAIN to set the STMA gain.
Step 2 Repeat Step 1 to set the gains of other STMAs when multiple STMAs are configured.
----End
11.2.4 Querying the Gain of the STMA

This describes how to query the gain of the STMA to check whether the gain is correctly set.
Prerequisite
l The STMA gain is set.
Procedure
Step 1 Run the command LST TMAGAIN to query the STMA gain.
Step 2 Repeat Step 1 to query the gains of other STMAs when multiple STMAs are configured.
----End
11.2.5 MML Commands Related to the STMA

This describes the MML commands related to the STMA antenna. You can operate the STMA
antenna by running the related commands.
Command Description
SET TMAMODE To set the working mode of the STMA
LST TMAMODE To query the working mode of the STMA
SET TMAGAIN To set the STMA gain
LST TMAGAIN To query the STMA gain
ADD ALD To add an ALD
SET ALDPWRSW To set the ALD power switch
MOD ALD To modify the ALD
RST ALD To reset the ALD

NodeB
Command Description
SET RXATTEN To set the RX attenuation value

NodeB
Commissioning Guide 12 Handling Alarms During Commissioning NodeB
12 Handling Alarms During

Commissioning NodeB
This describes how to check whether active alarms are present on the NodeB and clear these
alarms if any.
Prerequisite
Procedure
Step 1 Run the command LST ALMAF to query the current active alarms.
Step 2 Handle the alarms.
If... Then...
An active alarm is present, Clear it according to the LMT alarm online help.
An active alarm cannot be cleared, Record it in the 15 Data Sheet for NodeB
Commissioning.
TIP
For details about clearing an alarm, refer to the NodeB LMT User Guide.
----End

NodeB
Commissioning Guide 13 Testing NodeB Services with a UE
13 Testing NodeB Services with a UE
This describes how to test NodeB services on the UE to check whether the NodeB can properly
provide all types of services.
Prerequisite
l Two UEs with USIM card are available.
l The two tester UEs are registered in the HLR.
l The RNC works properly.
l The CS domain and PS domain in the CN properly.
l Run the DSP CELL command on the RNC LMT to verify whether all the logical cells of
the NodeB on the RNC side are operational.
l Run the DSP LOCELL command on the NodeB side to verify whether all the logical cells
of the NodeB on the NodeB side are operational.
Context
Table 13-1 describes the basic items in the NodeB service call quality test (CQT).
Table 13-1 Basic items in the service dialing test
Item Method Expectation
Voice service Use the UE to call the local The voice is clear.
fixed-line telephone.
Use the local fixed-line The voice is clear.

telephone to call the UE.
Use UE 1 to call UE 2. The voice is clear.
CS streaming service Use UE 1 to initiate the video l The voice is clear.

phone service to UE 2. l The video is continuous.
l The voice and video are
synchronous.

NodeB
13 Testing NodeB Services with a UE Commissioning Guide
Item Method Expectation
PS service Use the UE to activate data Web browsing is normal.

service and to browse web
pages.
When a NodeB carries multiple logical cells, you should perform a service test on each logical
cell. The following description of the CQT is based on logical cell i.
Procedure
Step 1 On the RNC side, start the single UE tracing. The IMSIs are allocated to the two tester UEs.
Step 2 On the NodeB side, start the Iub interface tracing.
Step 3 Run the command DEA CELL on the RNC side to deactivate all the logical cells of NodeB.
Step 4 Run the command ACT CELL on the RNC side to activate logical cell i of NodeB.
Step 5 On the RNC side, start the Uu interface tracing of logical cell i.
Step 6 Power on a UE.
Step 7 Check the automatical search for WCDMA network while the UE is starting.
If... Then...
The search fails, For details, refer to Common Causes to UE Failure to Search
Out the Network.
The search is successful, Go to Step 8.
Step 8 Check the downlink scramble, Ec/Io, and RSCP of the downlink pilot channel.
NOTE
If the UE is not the tester UE, skip this step.
If... Then...
The DL scramble matches cell i, and the Ec/ For details, refer to Step 9.
Io of the downlink pilot channel is greater
than -10 dB, or downlink pilot RSCP is
greater than -95 dBm,
The downlink scramble does not match cell The signal coverage is poor. Choose another
i, or the Ec/Io of the downlink pilot channel location with better signal coverage (Ec/Io >
is smaller than -10 dB, or the downlink pilot -10 dB) and the downlink pilot RSCP greater
RSCP is smaller than -95 dBm, than -95 dBm to conduct the test again.

NodeB
Commissioning Guide 13 Testing NodeB Services with a UE
Step 9 The UE automatically updates its location information. If the updates fail, refer to 14.11
Removal of a Cell After Setup to rectify the fault.
Step 10 Use the UE to call a local fixed-line telephone. If the updates fail, refer to 14.11 Removal of a
Cell After Setup to rectify the fault.
Step 11 Use the local fixed-line telephone to call the UE. If the updates fail, refer to 14.11 Removal of
a Cell After Setup to remove the fault.
Step 12 Use UE 1 to call UE 2 through the common phone. If the updates fail, refer to 14.11 Removal
of a Cell After Setup to rectify the fault.
Step 13 Use UE 1 to call UE 2 to through the video phone. If the updates fail, refer to 14.11 Removal
of a Cell After Setup to rectify the fault.
Step 14 Use the UE to activate data service and browse web pages. If the updates fail, refer to 14.11
Removal of a Cell After Setup to rectify the fault.
Step 15 Repeat Step 2 through Step 14 on other logical cells of the NodeB.
----End

NodeB
Commissioning Guide 14 NodeB Commissioning FAQs
14 NodeB Commissioning FAQs
About This Chapter
This describes the fault symptoms and cause analysis of FAQs during NodeB commissioning.
14.1 Common Causes to LMT Failure to Locally Connect the NodeB

This describes the fault symptom and cause analysis of the LMT failure to connect to the NodeB.
14.2 Common Causes to Failure to Download the NodeB Data Configuration File
This describes the cause analysis of the failure to download the NodeB data configuration file.
14.3 Failure to Perform a CQT
This describes the fault symptom and cause analysis of the failure to conduct a call quality test
(CQT).
14.4 Common Causes to the ALD Current Abnormal Alarm
This describes the fault symptom, cause analysis, and handling suggestions for the ALD current
abnormal alarm.
14.5 ALD Information to Be Collected for Troubleshooting
This describes how to collect the related ALD information to facilitate troubleshooting when a
fault occurs to the ALD.
14.6 Failure to Set the Downtilt of the RET Antenna
This describes the fault symptom, cause analysis, and handling suggestions for the failure to set
the downtilt of the RET antenna.
14.7 FE Port in DOWN State
This describes the fault symptom, cause analysis, and handling suggestions for the FE port in
DOWN state.
14.8 PPP Link in DOWN State
This describes the fault symptom, cause analysis, and handling suggestions for the failure of the
PPP link in DOWN state.
14.9 Faulty NCP and CCPs
This describes the fault symptom, cause analysis, and handling suggestions for the faulty NCP
and CCPs.
14.10 Faulty E1 Links

NodeB
14 NodeB Commissioning FAQs Commissioning Guide
This describes the fault symptom, cause analysis, and handling suggestions for the faulty E1
links.
14.11 Removal of a Cell After Setup
This describes the fault symptom, cause analysis, and handling suggestions for the problem that
a cell is removed after setup.
14.12 Repeated Establishment and Removal of the CCH After Cell Setup
This describes the fault symptom, cause analysis, and handling suggestions for the fault that the
common channel (CCH) is repeatedly established and removed after the setup of a cell.
14.13 Removal of the Common Channel Upon Call Initiation
This describes the fault symptom, cause analysis, and handling suggestions for the failure that
the common channel is removed upon call initiation.
14.14 Failure to Activate the HSDPA Service
This describes the fault symptom, cause analysis, and handling suggestions for the failure to
activate the HSDPA service.
14.15 Alarms Related to RET/STMA Links
This describes the fault symptom, cause analysis, and handling suggestions for the alarms related
to the RET/STMA links.

NodeB
14.1 Common Causes to LMT Failure to Locally Connect the

NodeB
This describes the fault symptom and cause analysis of the LMT failure to connect to the NodeB.
Fault Symptom
You cannot locally log in to the NodeB LMT or ping the NodeB.
Analysis
The fault may occur due to the following causes:
l Faulty crossover Ethernet cable

l Wrong IP address of the LMT computer
Handling Suggestions
l Check whether the crossover Ethernet cable is faulty and rectify the fault if any. For details,
refer to 5.2 Locally Connecting the NodeB LMT PC to the NodeB
l Check whether the IP address of the LMT computer is correct. For details, refer to 5.1
Setting the IP Address of the NodeB LMT PC.
14.2 Common Causes to Failure to Download the NodeB

Data Configuration File
This describes the cause analysis of the failure to download the NodeB data configuration file.
Fault Symptom
The system fails to download the NodeB data configuration file.
Analysis
l The length of the path to the NodeB data configuration file saved on the LMT PC exceeds
the stipulated bytes which is 230 bytes.
l The current software version is inconsistent with the current data configuration file.
l Change the path of the NodeB data configuration file on the LMT computer, thus ensuring
that the path length is within the stipulated range.
l Choose the correct data configuration file and download the file again.

NodeB
14.3 Failure to Perform a CQT

This describes the fault symptom and cause analysis of the failure to conduct a call quality test
(CQT).
Fault Symptom
CQT failure may occur in following situations:
l Location update failure
l Service CQT failure
Analysis
l The UE is faulty, such as lack of the USIM card and authentication encryption not supported
by the USIM card.
l The tester UE is not registered in the HLR on the CN side, or the registration is incorrect.
l The CS domain or PS domain is not ready.
l Replace the UE with a new one.
l Register the tester UE correctly.
l Keep CS domain and PS domain ready.
14.4 Common Causes to the ALD Current Abnormal Alarm

This describes the fault symptom, cause analysis, and handling suggestions for the ALD current
abnormal alarm.
Fault Symptom
The system reports ALD current abnormal alarm.
The ALD power switch is automatically disabled and can be enabled only manually.
Analysis
l Overcurrent
l Undercurrent
1. Run the command DSP ANTCON to check the following information:
l Operating status of the ALD power switch

NodeB
l Present current value

l Configured overcurrent alarm threshold
2. Search out the cause to the alarm based on the proceeding information.
l If the fault is caused by undercurrent, the physical connection of ALDs may be loose.
Check the cables, and then restore the ALD power switch to the configured state by
using the command RST ALDPWRSW.
l If the fault is caused by overcurrent, the configured current threshold cannot meet the
requirement. Run the command SET ALDPWRSW to set the alarm threshold.
14.5 ALD Information to Be Collected for Troubleshooting

This describes how to collect the related ALD information to facilitate troubleshooting when a
fault occurs to the ALD.
When a fault occurs to the ALD, collect the information as listed in Table 14-1.
Table 14-1 ALD information to be collected for troubleshooting
Information Suggestion
Manufacturer and serial number of the ALD l Run the command SCN ALD.
l Copy the information from the silk screen.
ALD model Copy the information from the silk screen.
ALD version number Run the command DSP ALDVER.
Antenna tilt range Run the command LST ANTTILTRNG.
14.6 Failure to Set the Downtilt of the RET Antenna

This describes the fault symptom, cause analysis, and handling suggestions for the failure to set
the downtilt of the RET antenna.
Fault Symptom
You can perform reset, scan, and calibration on the RET antenna but cannot set or query the
Analysis
l The downtilt of the RET antenna is beyond the range.

l The RCU is faulty.
l Sector information is not matched.
l The configuration file recording the relation between the movement of the RCU and the
downtilt of the RET antenna is not configured.

NodeB
1. Ensure that the following information is correct:
l The downtilt of the RET antenna is within the range.
l The RET antenna can be calibrated and the RCU works properly.
l Relevant settings of sector information correspond to each other.
2. The correct configuration files are downloaded.
14.7 FE Port in DOWN State

This describes the fault symptom, cause analysis, and handling suggestions for the FE port in
DOWN state.
Fault Symptom
The FE port is unable to enter UP state. Check the port and find that the port is in DOWN state.
The green Link is not ON.
Analysis
l Incorrect settings of the rate and duplex mode of the FE ports

l Poor or faulty connection of the Ethernet cables
l Faulty board or incorrect setting of the MAC address
l Faulty FE port
1. Run the command LST ETHPORT to check whether the settings of the rate and duplex
mode are correct. Ensure that the rate and duplex mode are set to 100 Mbit/s and FULL
respectively.
2. Ensure that the Ethernet cables are correctly connected. If the Ethernet cables are not
connected to the ports, connect the cables and check whether the fault is rectified.
3. Run the command DSP ETHPORT to check whether the MAC address is consistent with
the address on the board label.
Check whether the query result is consistent with the MAC address labeled on the board.
If they are inconsistent, replace the board.
4. Connect the cable to the other Ethernet port. If the fault persists, the board may be damaged.
Replace the faulty board with a new one.
14.8 PPP Link in DOWN State

This describes the fault symptom, cause analysis, and handling suggestions for the failure of the
PPP link in DOWN state.

NodeB
Fault Symptom
The PPP link is in DOWN state and IP address is not obtained.
Analysis
l Poor connection of the E1 cable
l Incorrect settings of the PPP link
1. Check the status of the E1 cable. Ensure that the E1 cable is properly connected.
2. Check the settings of the PPP link, E1 port number, and timeslot. Ensure that their settings
are correct.
3. Check whether the peer settings are consistent with the negotiated data.
14.9 Faulty NCP and CCPs

This describes the fault symptom, cause analysis, and handling suggestions for the faulty NCP
and CCPs.
Fault Symptom
Connection of the NCP and CCPs is faulty.
Analysis
l Communication failure in IP transport network
l Inconsistent negotiated configuration data at both sides
1. Check whether pinging the signaling address of the RNC is available on the NodeB LMT.
If pinging the signaling address of the RNC fails, ping the IP address of the network that
connects the PIE board, and check whether the internal route of the RNC and the route of
the NodeB are correctly set.
2. If the fault persists not due to faulty route, check the transmission status.
l When the FE ports are applied to the networking on the NodeB, check the cable
connection and the FE port status. For details, refer to 14.7 FE Port in DOWN State.
l When the E1/T1 cables are applied to the networking on the NodeB, alarms are reported.
Then, check the transmission status. For details, refer to the related online help for
corresponding alarms.
3. If ping the signaling address of the RNC succeeds, check whether the SCTP port number
of the NodeB and that of the RNC are consistent, and whether the IP addresses configured
on both sides are in the same network segment.
4. If an NCP fault occurs after the NodeB is started, check whether there is an alarm related
to the data configuration file. If there is an alarm related to the data configuration file,

NodeB
download a valid data configuration file to the NodeB, reset the NodeB, and then configure
the file correctly.
14.10 Faulty E1 Links

This describes the fault symptom, cause analysis, and handling suggestions for the faulty E1
links.
Fault Symptom
When the logical cell and all the upper-layer links are available,
l If you run the command DSP E1T1 on the RNC side, the E1/T1 link is available. If you
run this command on the NodeB side, the E1/T1 link is Abnormal.
l In a loopback, if you use the command DSP E1T1 on the NodeB side, the E1 link changes
to link in loop. When the E1 link is changed to No Loop, it changes to Normal
for a moment, and then changes back to Abnormal.
Analysis
l Incorrect ATM traffic configuration
l Faulty physical connection of cables
l Incorrect setting of the E1/T1 mode
1. Check the transmission channels to ensure that all the transmission channels are available.
2. Check the physical connection of the cables to ensure that the connection is sound and all
the links are available.
3. Check the E1/T1 mode. When the E1/T1 cable is set to the double-frame mode on the
NodeB side and multi-mode on the RNC side, the E1/T1 link is still available on the RNC
side, but the E1/T1 link on the NodeB side is displayed as Abnormal.
Summary of Suggestions
Though the default setting is multi-mode, the setting of the E1/T1 mode should be checked when
the fault occurs.
14.11 Removal of a Cell After Setup

This describes the fault symptom, cause analysis, and handling suggestions for the problem that
a cell is removed after setup.
Fault Symptom
A cell cannot be set up. The cell is removed after setup through the Iub interface tracing. The
RNC reports that a common channel fails to be established, but the message is not found on the
Iub interface.

NodeB
Analysis
The fault may occur due to insufficient configured bandwidth.
1. Deactivate and then activate the cell on the RNC side to check whether the cell is restored.
2. If the cell is not restored, check whether the bandwidth for the IP path on the RNC side is
sufficient. Set the bandwidth of the IP path on the RNC side to 100 Mbit/s and set the
bandwidth type to RT. This ensures successful setup of the common channel. If the fault
is caused by improper settings of the bandwidth, set the bandwidth to the default value. For
example, set the bandwidth of an E1 link to 1.92 Mbit/s.
3. If the fault persists after the IP path bandwidth is modified, keep tracing the results on the
RNC side to find the causes to the fault.
14.12 Repeated Establishment and Removal of the CCH

After Cell Setup
This describes the fault symptom, cause analysis, and handling suggestions for the fault that the
common channel (CCH) is repeatedly established and removed after the setup of a cell.
Fault Symptom
After a cell is set up, the common channel is removed. The result on the RNC side shows that
the common channel fails to be synchronized.
Analysis
The cause may be that the data links are faulty or heavy packet loss exists.
1. Ensure that a route is added to the address of the RNC data link plane configured on the
NodeB side. If no, add the route. If the route for the equipment of the network is incorrect,
modify the route configuration.
2. If the fault persists, check the request and response for establishing common channel on
the Iub interface, and then check whether the IP address is correct.
l If the IP address requested by the RNC is incorrect, modify the IP address of the IP path
on the RNC side.
l If the IP address replied by the NodeB is incorrect, modify the IP address of the IP path
on the NodeB side and reset the NodeB.
14.13 Removal of the Common Channel Upon Call

Initiation
This describes the fault symptom, cause analysis, and handling suggestions for the failure that
the common channel is removed upon call initiation.

NodeB
Fault Symptom
When the network is connected through FE ports, the cells are successfully set up. The following
cases, however, may occur:
l Common channels are removed after a call is initiated. This causes communication failure.
l The common channel is periodically removed. This causes the disruption of activated
services.
Analysis
The cause may be the quality of the user plane channel.
1. Check the route configurations. Ensure that pinging the IP address is available.
2. If the common channel is successfully established, the IP path is operational.
3. Check the configuration and the status of the FE ports. Insufficient bandwidth may cause
the congestion, which causes in low packet transmission rate or packet loss and even
removal of the common channel.
Solutions
Modify the LR configurations and set the bandwidth of the port to the bandwidth of the physical
port.
14.14 Failure to Activate the HSDPA Service

This describes the fault symptom, cause analysis, and handling suggestions for the failure to
activate the HSDPA service.
Fault Symptom
The HSDPA service at 1920 kbit/s fails to be activated, but the R99 service at 64 kbit/s can be
successfully activated.
Analysis
l The cell is not configured with the HSDPA function or the HSDPA is not activated.
l The RNC is not configured with the IP path of the HSDPA-NRT.
l If the maximum rate of the USIM card registered in the HLR is set to 384 kbit/s or smaller,
the HSDPA service may not be activated. Only the service at 384 kbis/s can be activated.
1. Check whether the HSDPA service is configured on the RNC side and if the HSDPA cell
is activated. If not, configure the HSDPA service on the RNC side and activate the HSDPA
cell.

NodeB
2. Check whether the HSDPA-NRT IP path is configured on the RNC side. Ensure that the
bandwidth of the IP path is sufficient enough. Otherwise, the IP path may be unavailable.
After the configuration, re-activate the cell.
3. If the cell cannot be re-activated, trace the signaling over the Uu interface and search out
the cause of the fault.
Solutions
Modify the configurations of the HSDPA services on the RNC side and on the NodeB side.
Modify the configuration of the HSDPA IP path.
14.15 Alarms Related to RET/STMA Links

This describes the fault symptom, cause analysis, and handling suggestions for the alarms related
to the RET/STMA links.
Fault Symptom
The system reports the abnormal communication alarm of the RET/STMA.
Possible Causes
The fault may occur due to the following causes: The ALD link is disconnected.
l Reset boards or modules.
Macro NodeB: reset the MTRU or NMON board.
Distributed NodeB: reset the BBU.
l Run the command RST ALD to reset the ALD.
NOTE
You are advised to run the command RST ALD, which does not disrupt any services.

NodeB
Commissioning Guide 15 Data Sheet for NodeB Commissioning
15 Data Sheet for NodeB Commissioning
This provides the data sheet that is used to record the process and results of the NodeB
commissioning
Table 15-1 Data sheet for NodeB commissioning

Site Name
NodeB Type
Commission
Time
Commissioning
Engineer
Commissioning Successful Failed

Result
Commissioning Item Conclusion Handling

Exceptional
Cases
Commissioning Faults in the NodeB hardware

Preparation Phase installation are rectified.
Transmission links between the

NodeB and RNC are ready.
Data of the NodeB to be

commissioned is added to the
RNC.
The NodeB data configuration file

is ready.
The local IP address in the NodeB

data configuration file is set.

NodeB
15 Data Sheet for NodeB Commissioning Commissioning Guide
Commissioning Item Conclusion Handling

Exceptional
Cases
Commissioning The IP address of the LMT PC is

Phase configured.
The LMT PC is locally connected

to the NMPT.
You are locally logged in to the

NodeB LMT.
The NodeB software is upgraded.
The NodeB data configuration file

is downloaded.
The NodeB is reset.
The network connections are

checked if the macro base station is
configured with the RRU.
The status of transmission on the

Iub interface is checked.
The running status of the NodeB is

checked.
The VSWR of the NodeB is

measured.
The alarm equipment of NodeB is

commissioned.
The ALD equipment is

commissioned.
The alarms generated during the

NodeB commissioning are
handled.
The NodeB services are tested on

the UE.
The M2000 administrator is

notified.
Unsolved Problems Impact
Unsolved
Problems After
Commissioning

NodeB
Commissioning Guide Index
Index
A activating, 5-20
downloading, 5-16
activating
BootROM software, 5-14 R
NodeB software, 5-20
resetting, 5-24, 5-25
B
S
BootROM software
activating, 5-14 setting
downloading, 5-11 LMT PC
IP address, 5-2
D
data configuration file
downloading, 5-22
downloading
BootROM software, 5-11
data configuration file, 5-22
NodeB software, 5-16
I
IP address
setting, 5-2
L
LMT
logging in
locally, 5-7
LMT PC
setting
IP address, 5-2
logging in
locally, 5-7
M
monitoring
output power of the MTRU, 8-6
N
NodeB software
Issue 04 (2009-06-30) Huawei Proprietary and Confidential i-1


NodeB Commissioning Guide (V100 - 04)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NodeB Commissioning Guide (V100 - 04)

Uploaded by

Copyright:

Available Formats

NodeB

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

3 NodeB Commissioning Resources..........................................................................................3-1

Issue 04 (2009-06-30) Huawei Proprietary and Confidential i

5.2.2 Locally Connecting the NodeB LMT PC to the BBU3806...................................................................5-5

6 Checking the Connection for NodeB Networking..............................................................6-1

7 Checking Transmission Status on the Iub Interface...........................................................7-1

8 Checking the Running Status of the NodeB.........................................................................8-1

9 Measuring the NodeB VSWR..................................................................................................9-1

ii Huawei Proprietary and Confidential Issue 04 (2009-06-30)

10.1.2 Adding the Alarm Equipment to the BTS3812AE.............................................................................10-4

11 Checking the ALD..................................................................................................................11-1

12 Handling Alarms During Commissioning NodeB..........................................................12-1

15 Data Sheet for NodeB Commissioning..............................................................................15-1

Issue 04 (2009-06-30) Huawei Proprietary and Confidential iii

iv Huawei Proprietary and Confidential Issue 04 (2009-06-30)

Figure 2-1 Wearing an ESD wrist strap...............................................................................................................2-6

Issue 04 (2009-06-30) Huawei Proprietary and Confidential v

Table 2-1 Fuse description...................................................................................................................................2-5

Issue 04 (2009-06-30) Huawei Proprietary and Confidential vii

About This Document

Product Name Version

Issue 04 (2009-06-30) Huawei Proprietary and Confidential 1

1 Changes in the NodeB Commissioning Guide

3 NodeB Commissioning Resources

2 Huawei Proprietary and Confidential Issue 04 (2009-06-30)

12 Handling Alarms During Commissioning NodeB

13 Testing NodeB Services with a UE

14 NodeB Commissioning FAQs

15 Data Sheet for NodeB Commissioning

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Issue 04 (2009-06-30) Huawei Proprietary and Confidential 3

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

4 Huawei Proprietary and Confidential Issue 04 (2009-06-30)

Double-click Press the primary mouse button twice continuously and

Issue 04 (2009-06-30) Huawei Proprietary and Confidential 5

1 Changes in the NodeB Commissioning

This describes the changes in the NodeB Commissioning Guide.

Issue 04 (2009-06-30) Huawei Proprietary and Confidential 1-1

2.1.1 Safety Precautions

2.1.2 General Requirements

Issue 04 (2009-06-30) Huawei Proprietary and Confidential 2-1

2-2 Huawei Proprietary and Confidential Issue 04 (2009-06-30)