Edvdv Node B Commissio Ning Gui de

NodeB V100R008
Commissioning Guide
Issue Date Part Number
05 2007-09-30 00297726
Huawei Technologies Proprietary
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 http://www.huawei.com support@huawei.com
Website: Email:
Copyright 2007 Huawei Technologies Co., Ltd. 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.
NodeB Commissioning Guide
Contents
Contents
About This Document.....................................................................................................................1 1 NodeB Commissioning Resources..........................................................................................1-1 2 NodeB Commissioning Scenarios..........................................................................................2-1 3 Local commissioning of the NodeB (Transmission Available)........................................3-1
3.1 Locally Commissioning the Macro NodeB (Transmission Available)...........................................................3-2 3.2 Locally Commissioning the Distributed NodeB (Transmission Available)...................................................3-3
4 Locally Commissioning the NodeB (Transmission Unavailable)....................................4-1

4.1 Locally Commissioning the Macro NodeB (Transmission Unavailable).......................................................4-2 4.2 Locally Commissioning the Distributed NodeB (Transmission Unavailable)................................................4-3
5 Remotely Commissioning the NodeB....................................................................................5-1

5.1 Remotely Commissioning the Macro NodeB.................................................................................................5-2 5.2 Remotely Commissioning the Distributed NodeB..........................................................................................5-3
6 Checking the DIP Switches Settings of the NodeB.............................................................6-1

6.1 Checking the DIP Switches Settings of the Macro NodeB.............................................................................6-2 6.1.1 DIP Switches on the BESP Board..........................................................................................................6-2 6.1.2 DIP Switches on the NDTI Board..........................................................................................................6-2 6.1.3 DIP Switches on the NUTI Board..........................................................................................................6-5 6.2 Checking the DIP Switches Settings of the Distributed NodeB.....................................................................6-6 6.2.1 DIP Switch on the BBU3806.................................................................................................................6-7 6.2.2 DIP Switch on the BBU3806C...............................................................................................................6-8
7 Powering On the NodeB...........................................................................................................7-1

7.1 Powering On the BTS3812E...........................................................................................................................7-2 7.2 Powering On the BTS3812AE .......................................................................................................................7-3 7.3 Powering On the DBS3800.............................................................................................................................7-5 7.4 Powering On the iDBS3800............................................................................................................................7-8
8 Upgrading the NodeB Software and Downloading the Data Configuration File.........8-1
8.1 Setting the IP Address of NodeB LMT PC.....................................................................................................8-3 8.2 Connecting the LMT PC to the NodeB...........................................................................................................8-4 8.2.1 Locally Connecting the LMT PC to the NodeB.....................................................................................8-5 8.2.2 Remotely Connecting the LMT PC to the NodeB (Through RNC BAM).............................................8-7 Issue 05 (2007-09-30) Huawei Technologies Proprietary i
Contents
NodeB Commissioning Guide 8.2.3 Remotely Connecting the LMT PC to the NodeB (on M2000).............................................................8-8
8.3 Setting the Route from the LMT PC to the NodeB.........................................................................................8-8 8.4 Logging In to the NodeB on the NodeB LMT................................................................................................8-9 8.4.1 Locally Logging In to the NodeB on the LMT......................................................................................8-9 8.4.2 Remotely Logging In to the NodeB (Through RNC BAM)................................................................8-11 8.4.3 Remotely Logging In to the NodeB (on M2000).................................................................................8-13 8.5 Upgrading the NodeB Software....................................................................................................................8-15 8.5.1 Checking the Compatibility of the NodeB Software Version .............................................................8-16 8.5.2 Downloading the BootROM Software Package of the NodeB ...........................................................8-17 8.5.3 Activating the BootROM Software of the NodeB...............................................................................8-22 8.5.4 Downloading the Software of the NodeB............................................................................................8-25 8.5.5 Activating the Software of the NodeB.................................................................................................8-30 8.6 Downloading the NodeB Data Configuration File........................................................................................8-34 8.7 Resetting the NodeB......................................................................................................................................8-37
9 Checking the Connection of the RRU3801C in the Network............................................9-1

9.1 Checking the Connection Between the RRU3801C and the Macro NodeB...................................................9-2 9.1.1 Checking the Consistency in Connection and Data Configuration Between RRU3801C and Macro NodeB .........................................................................................................................................................................9-2 9.1.2 Checking the Links Between the Macro NodeB and the RRU3801C...................................................9-3 9.2 Checking the Internal Status of the DBS3800................................................................................................9-3 9.2.1 Checking the Consistency Between DBS3800 Hardware and Data Configuration...............................9-4 9.2.2 Checking the Link Between the BBU3806/BBU3806C and the RRU3801C.......................................9-4 9.3 Checking the Internal Status of the iDBS3800...............................................................................................9-5 9.3.1 Checking the Consistency Between iDBS3800 Hardware and Data Configuration..............................9-5 9.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU3801..................................................9-6
10 Checking the Running Status of the NodeB.....................................................................10-1

10.1 Checking NodeB Transmission...................................................................................................................10-2 10.1.1 Checking E1/T1 Links.......................................................................................................................10-2 10.1.2 Checking STM-1 Links......................................................................................................................10-3 10.1.3 Checking Ethernet Links....................................................................................................................10-4 10.2 Commissioning SNTP.................................................................................................................................10-5 10.3 Handling Alarms During NodeB Commissioning......................................................................................10-6 10.4 Checking the Status of a Cell......................................................................................................................10-7 10.5 Measuring the RTWP..................................................................................................................................10-7 10.6 Monitoring the Output Power of the NodeB...............................................................................................10-9
11 Commissioning the Alarm Equipment..............................................................................11-1

11.1 Adding the Alarm Equipment.....................................................................................................................11-2 11.2 Setting the External Alarm..........................................................................................................................11-3 11.3 Checking the External Alarm......................................................................................................................11-5
12 Commissioning the ALD......................................................................................................12-1

12.1 Commissioning the RET Antenna...............................................................................................................12-2 ii Huawei Technologies Proprietary Issue 05 (2007-09-30)
Contents
12.1.1 Setting the ALD Power Switch..........................................................................................................12-3 12.1.2 Adding ALDs.....................................................................................................................................12-3 12.1.3 Downloading the Data Configuration File of the RET Antenna........................................................12-4 12.1.4 Calibrating the RET Antenna.............................................................................................................12-4 12.1.5 Setting the Downtilt of the RET Antenna..........................................................................................12-5 12.1.6 Querying the Current Downtilt of the RET Antenna.........................................................................12-6 12.1.7 MML Commands Related to ALDs...................................................................................................12-6 12.2 Commissioning the STMA..........................................................................................................................12-7 12.2.1 Setting the ALD Power Switch..........................................................................................................12-8 12.2.2 Adding ALDs.....................................................................................................................................12-8 12.2.3 Querying the Gain Range of the STMA.............................................................................................12-9 12.2.4 Setting the Gain of the STMA............................................................................................................12-9 12.2.5 Querying the Gain of the STMA......................................................................................................12-10 12.2.6 MML Commands Related to the STMA..........................................................................................12-10
13 Testing NodeB Services .......................................................................................................13-1 14 Testing NodeB Services on RNC Simulator.....................................................................14-1

14.1 Configuring the RNC Simulator.................................................................................................................14-2 14.2 Connecting the RNC Simulator to the NodeB............................................................................................14-4 14.3 Logging In to the NodeB on the RNC Simulator........................................................................................14-5 14.4 Setting Up a Cell on the RNC Simulator....................................................................................................14-5 14.5 Testing Calls on the RNC Simulator...........................................................................................................14-6
15 NodeB Commissioning FAQs..............................................................................................15-1

15.1 Faulty Local Connection Between the LMT and the NodeB......................................................................15-3 15.2 Faulty Remote Connection Between the LMT and the NodeB................................................................... 15-3 15.3 Failure to Download the NodeB Data Configuration File..........................................................................15-3 15.4 Low Data Rate of PS Data..........................................................................................................................15-4 15.5 Failure of the UE to Search the Network....................................................................................................15-4 15.6 Failure to Conduct a Dialing Test...............................................................................................................15-5 15.7 Causes for the ALD Current Abnormal Alarm...........................................................................................15-5 15.8 ALD Information to Be Collected...............................................................................................................15-6 15.9 Failure to Set the Downtilt of the RET Antenna.........................................................................................15-6 15.10 FE Port in DOWN State ...........................................................................................................................15-7 15.11 PPP Link in the DOWN State ..................................................................................................................15-8 15.12 Faulty NCP and CCPs...............................................................................................................................15-8 15.13 Faulty E1 Links.........................................................................................................................................15-9 15.14 Removal of a Cell After Setup................................................................................................................15-10 15.15 Repeated Establishment and Removal of the Common Channel After Cell Setup.................................15-11 15.16 Removal of the Common Channel Upon Call Initiation.........................................................................15-11 15.17 Failure to Activate the HSDPA Service..................................................................................................15-12 15.18 Alarms Related to RET/TMA/STMA Links...........................................................................................15-12
16 NodeB Commissioning Data Sheet....................................................................................16-1

Issue 05 (2007-09-30) Huawei Technologies Proprietary iii
Contents
Index.................................................................................................................................................i-1
iv
Issue 05 (2007-09-30)
Figures
Figures
Figure 6-1 DIP switches on the NDTI..................................................................................................................6-3 Figure 6-2 DIP switch on the NUTI.....................................................................................................................6-6 Figure 6-3 DIP switch on the BBU3806..............................................................................................................6-7 Figure 6-4 DIP switch on the BBU3806C............................................................................................................6-8 Figure 7-1 Power switches on the power distribution box...................................................................................7-4 Figure 8-1 IP addresses in remote maintenance mode.........................................................................................8-3 Figure 8-2 Connecting LMT PC and NMPT in local maintenance mode............................................................8-6 Figure 8-3 Connecting LMT PC and BBU3806 in local maintenance mode.......................................................8-6 Figure 8-4 Connecting LMT PC and BBU3806C in local maintenance mode....................................................8-7 Figure 8-5 User Login dialog box........................................................................................................................8-9 Figure 8-6 Switching the NodeB language........................................................................................................8-10 Figure 8-7 User Login dialog box......................................................................................................................8-11 Figure 8-8 Switching the NodeB language........................................................................................................8-12 Figure 8-9 User Login dialog box......................................................................................................................8-13 Figure 8-10 NodeB List dialog box....................................................................................................................8-14 Figure 8-11 Switching the NodeB language......................................................................................................8-15 Figure 8-12 Software Update dialog box...........................................................................................................8-18 Figure 8-13 Upgrade BOOTROM dialog box...................................................................................................8-19 Figure 8-14 FTP Setting dialog box...................................................................................................................8-21 Figure 8-15 Software Update dialog box...........................................................................................................8-23 Figure 8-16 Upgrade BOOTROM dialog box...................................................................................................8-24 Figure 8-17 Software Update dialog box...........................................................................................................8-26 Figure 8-18 Upgrade NodeB Software dialog box.............................................................................................8-27 Figure 8-19 FTP Setting dialog box...................................................................................................................8-29 Figure 8-20 Software Update dialog box...........................................................................................................8-31 Figure 8-21 Upgrade NodeB Software dialog box.............................................................................................8-32 Figure 8-22 DataConfig File Transfer dialog box..............................................................................................8-35 Figure 8-23 FTP Setting dialog box...................................................................................................................8-37 Figure 10-1 Physical loopback of E1/T1s on the DDF......................................................................................10-3 Figure 10-2 RTWP Measurement dialog box....................................................................................................10-8 Figure 10-3 Output Power Monitoring dialog box...........................................................................................10-10 Figure 14-1 Starting LoadCaller......................................................................................................................14-2 Figure 14-2 Open Project File dialog box........................................................................................................14-3 Issue 05 (2007-09-30) Huawei Technologies Proprietary v
Figures
NodeB Commissioning Guide Figure 14-3 Selecting a project file of test.tpf.................................................................................................14-3
Figure 14-4 Configuring UE information dialog box.....................................................................................14-3 Figure 14-5 Configuring IP address of the board dialog box........................................................................14-4
vi
Issue 05 (2007-09-30)
Tables
Tables
Table 1-1 Tools required for commissioning.......................................................................................................1-1 Table 2-1 NodeB commissioning scenarios.........................................................................................................2-1 Table 6-1 DIP switches on the BESP...................................................................................................................6-2 Table 6-2 DIP switch S11 on the NDTI...............................................................................................................6-3 Table 6-3 DIP switch S11 on the NDTI...............................................................................................................6-4 Table 6-4 DIP switches S3, S4, S5, and S6 on the NDTI....................................................................................6-4 Table 6-5 DIP switches S3, S4, S5, and S6 on the NDTI....................................................................................6-4 Table 6-6 Definitions of bits on DIP switch S11 on the NUTI............................................................................6-6 Table 6-7 Settings of the 8-pin DIP switch - 1.....................................................................................................6-7 Table 6-8 Settings of the 8-pin DIP switch - 2.....................................................................................................6-7 Table 6-9 Settings of the 8-pin DIP switch - 3.....................................................................................................6-8 Table 6-10 Settings of bits 3 and 4 on the DIP switch.........................................................................................6-9 Table 7-1 Checklist for power supply to the cabinet components.......................................................................7-2 Table 7-2 Relationship between devices and DC power switches.......................................................................7-5 Table 7-3 LEDs on the BBU3806........................................................................................................................7-6 Table 7-4 LEDs on the BBU3806C......................................................................................................................7-6 Table 7-5 LEDs on the RRU3801C......................................................................................................................7-7 Table 7-6 LEDs on the BBU3806........................................................................................................................7-8 Table 8-1 IP parameters of LMT PC in local maintenance mode .......................................................................8-4 Table 8-2 IP parameters of LMT PC in remote maintenance mode.....................................................................8-4 Table 8-3 Description of route parameters...........................................................................................................8-8 Table 8-4 Elements in the User Login dialog box..............................................................................................8-10 Table 8-5 Elements in the User Login dialog box..............................................................................................8-11 Table 8-6 Elements in the User Login dialog box..............................................................................................8-13 Table 8-7 Elements in the Upgrade BOOTROM dialog box.............................................................................8-19 Table 8-8 Elements in the FTP Setting dialog box.............................................................................................8-21 Table 8-9 Elements in the Upgrade BOOTROM dialog box.............................................................................8-24 Table 8-10 Elements in the Upgrade NodeB Software dialog box....................................................................8-27 Table 8-11 Elements in the FTP Setting dialog box...........................................................................................8-29 Table 8-12 Elements in the Upgrade NodeB Software dialog box....................................................................8-32 Table 8-13 Elements in the DataConfig File Transfer dialog box......................................................................8-36 Table 8-14 Elements in the FTP Setting dialog box...........................................................................................8-37 Table 10-1 Elements in the RTWP Measurement dialog box............................................................................10-8 Issue 05 (2007-09-30) Huawei Technologies Proprietary vii
Tables
NodeB Commissioning Guide Table 10-2 Elements in the Output Power Monitoring dialog box..................................................................10-10 Table 11-1 Parameters of the added subrack......................................................................................................11-2 Table 11-2 Parameters of the added board.........................................................................................................11-2 Table 11-3 Parameters of the added board.........................................................................................................11-3 Table 11-4 Parameters of the Boolean alarm port..............................................................................................11-3 Table 11-5 Parameters of the analog alarm port.................................................................................................11-4 Table 12-1 Items for the RET antenna commissioning......................................................................................12-2 Table 13-1 Basic items in the service dialing test..............................................................................................13-1 Table 15-1 Information to be collected and the handling suggestion when a fault occurs to the ALD.............15-6 Table 16-1 NodeB Commissioning Data Sheet..................................................................................................16-1
viii
Issue 05 (2007-09-30)
About This Document
About This Document

Purpose
The NodeB Commissioning Guide describes the commissioning and verification after the NodeB installation, which ensures that the NodeB works as designed. This document provides guidelines to the commissioning of the macro NodeB (BTS3812E, BTS3812A, BTS3812AE) and distributed NodeB (DBS3800 and iDBS3800), including software upgrading and downloading, transmission commissioning, alarm handling, cell status checking, RTWP measuring, output power monitoring, RET/STMA commissioning, service commissioning, and typical FAQs about commissioning.
Related Versions
Product Name BTS3812E BTS3812A BTS3812AE DBS3800 iDBS3800 Related Versions V100R008 V100R008 V100R008 V100R008 V100R008
Intended Audience
l
This document is intended for field engineers.
Change History
Refer to Changes in NodeB Commissioning Guide.
Organization
1 NodeB Commissioning Resources Tools, site information, associated NodeB software, and data configuration files that are required for NodeB commissioning should be prepared. 2 NodeB Commissioning Scenarios
Issue 05 (2007-09-30) Huawei Technologies Proprietary 1
About This Document
This part describes the three scenarios for the NodeB commissioning: local commissioning (transmission available), local commissioning (transmission unavailable), and remote commissioning. 3 Local commissioning of the NodeB (Transmission Available) This task describes how to locally commission the NodeB (transmission available). The scenario for this task is as follows: The RNC and the NodeB are properly connected, the LMT PC is connected to the NodeB, and the NodeB is locally commissioned. 4 Locally Commissioning the NodeB (Transmission Unavailable) The RNC and NodeB are not properly connected. The NodeB is locally commissioned on the RNC Simulator. Ensure that the NodeB hardware is in good condition. After the RNC and the NodeB are properly connected, the NodeB can access the WCDMA Radio Access Network (RAN). 5 Remotely Commissioning the NodeB This task describes how to remotely commission the NodeB. The scenario for this task is as follows: The RNC and NodeB are properly connected. The IPoA channel between the RNC and the NodeB works properly. The NodeB is commissioned remotely in the equipment room where the RNC is located. 6 Checking the DIP Switches Settings of the NodeB This task describes how to check the DIP switches settings of the NodeB before commissioning. 7 Powering On the NodeB This task describes how to power on the NodeB after the DIP switches are correctly set. 8 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 idle space on the disk is not less than 1 G during the operation. 9 Checking the Connection of the RRU3801C in the Network This task describes how to check the internal status of the RRU, including link status between RRU and DBS3800 and iDBS3800. 10 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 occurred during working. 11 Commissioning the Alarm Equipment This task describes how to commission the alarm equipment, including adding the alarm monitoring equipment, setting external alarms, and checking external alarms. 12 Commissioning the ALD This task describes how to commission the ALD equipment. The task consists of commissioning the RET antenna and commissioning the STMA. 13 Testing NodeB Services
2 Huawei Technologies Proprietary Issue 05 (2007-09-30)
About This Document
This task describes how to test NodeB services on the UE to check whether the NodeB can properly provide all types of services. 14 Testing NodeB Services on RNC Simulator This task describes how to test NodeB services on the RNC Simulator in local commissioning (transmission unavailable). Before the test, ensure that all the data is configured and the NodeB works properly. 15 NodeB Commissioning FAQs This part describes the fault symptoms and cause analysis of the NodeB commissioning. 16 NodeB Commissioning Data Sheet NodeB commissioning data sheet is used to record the process and result of the commissioning.
Conventions
1. Symbol Conventions The following symbols may be found in this document. They are defined as follows Symbol Description Indicates a hazard with a high level of risk that, 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 that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time. Provides additional information to emphasize or supplement important points of the main text.
DANGER
WARNING
CAUTION
TIP
NOTE
2. General Conventions Convention Times New Roman Boldface Italic Courier New
Issue 05 (2007-09-30)
Description Normal paragraphs are in Times New Roman. Names of files,directories,folders,and users are in boldface. For example,log in as user root . Book titles are in italics. Terminal display is in Courier New.
Huawei Technologies Proprietary 3
About This Document
3. Command Conventions Convention Boldface Italic [] {x | y | ...} [ x | y | ... ] { x | y | ... } * [ x | y | ... ] * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars.One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars.One or none is selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of one or a maximum of all can be selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of zero or a maximum of all can be selected.
4. GUI Conventions Convention Boldface > Description 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 .
5. Keyboard Operation Convention Key Key1+Key2 Key1,Key2 Description Press the key.For example,press Enter and press Tab. Press the keys concurrently.For example,pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn.For example,pressing Alt,A means the two keys should be pressed in turn.
6. Mouse Operation Action Click Double-click Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer.
Issue 05 (2007-09-30)
About This Document
Action Drag
Description Press and hold the primary mouse button and move the pointer to a certain position.
Issue 05 (2007-09-30)
1 NodeB Commissioning Resources
1
Tools
Tools Computer
NodeB Commissioning Resources
Tools, site information, associated NodeB software, and data configuration files that are required for NodeB commissioning should be prepared.
Table 1-1 lists the tools required for commissioning. Table 1-1 Tools required for commissioning Quantit y 1 Description Requirements for hardware:
l l
Scenario The portable computer is recommended for local commissioning to meet all requirements for the computer. The desktop computer is recommended for remote commissioning where only the installation of RNC Simulator software is not required.
For details, refer to Table 1. Ethernet adapters
Requirements for the operating system:

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

l
NodeB LMT. For details about installation and operations, refer to the NodeB LMT User Guide. CME. For details about installation and operations, refer to the CME User Guide. RNC Simulator software. Local commissioning of the NodeB
1-1
Ethernet cable
Connect the computer to the NodeB.

Issue 05 (2007-09-30)
Tools Light Emitting Diode (LED) (optional)
Quantit y 1
Description Distinguish the TX end from the RX end of the trunk cable.
Scenario Locally Commissioning the NodeB (Transmission Unavailable) Local commissioning of the NodeB (Transmission Available)
UE under test (including a SIM card)
Requirements for the UE under test:

l
The UE is subscribed to the HLR in the network. You can observe the PCPICH scrambling code, Ec/Io, and RSCP on the UE.
Locally Commissioning the NodeB (Transmission Unavailable) Local commissioning of the NodeB (Transmission Available)
Magic Test Box (MTB) Only in local commissioning of the NodeB (transmission unavailable)
Locally Commissioning the NodeB (Transmission Unavailable)
Site Information
The site information of the NodeB to be commissioned covers the following:
l
Critical information about the topology and configuration of the NodeB, such as the site type, transmission mode, networking topology, and cell configuration. NodeB-related negotiation data in the RNC
NodeB Software
If the default software version on the site is inconsistent with the planned version, the NodeB software on the site needs to be upgraded. Prepare the following NodeB software before commissioning:
l l
BOOTROM software. The file name is fixed to NBRom.pck. NodeB software. The file name is fixed to NodeB.pck.
Before commissioning, copy the correct NodeB software to the FTP server. If it is the local commissioning, copy the software to the specified directory of the computer used for commissioning.
Data Configuration File

The NodeB data configuration file is named NodeBCfg.xml.
1-2 Huawei Technologies Proprietary Issue 05 (2007-09-30)
Before commissioning, copy the correct NodeB data configuration file to the FTP server. If it is the local commissioning, copy the software to the specified directory of the computer used for commissioning.
NOTE
Before commissioning, you must query and record the IP address of the IPoA channel (local IP address) in the data configuration file.
Issue 05 (2007-09-30)
1-3
2 NodeB Commissioning Scenarios
2
Scenario
NodeB Commissioning Scenarios
This part describes the three scenarios for the NodeB commissioning: local commissioning (transmission available), local commissioning (transmission unavailable), and remote commissioning. Table 2-1 gives details about each scenario. Table 2-1 NodeB commissioning scenarios Description
l l l
Local commissioning of the NodeB (Transmission Available) Locally Commissioning the NodeB (Transmission Unavailable)
The RNC and NodeB are properly connected. The LMT PC is connected to the NodeB. The NodeB is locally commissioned. The RNC and NodeB are not properly connected. The NodeB is locally commissioned on the RNC Simulator. Ensure that the NodeB hardware is in good condition. After the RNC and the NodeB are properly connected, the NodeB can access the WCDMA Radio Access Network (RAN). The RNC and NodeB are properly connected. The IPoA channel between the RNC and the NodeB works properly. The NodeB is commissioned remotely in the equipment room where the RNC is located.
l l
Remotely Commissioning the NodeB
l l
Issue 05 (2007-09-30)
2-1
3 Local commissioning of the NodeB (Transmission Available)
Local commissioning of the NodeB (Transmission Available)
About This Chapter

This task describes how to locally commission the NodeB (transmission available). The scenario for this task is as follows: The RNC and the NodeB are properly connected, the LMT PC is connected to the NodeB, and the NodeB is locally commissioned. 3.1 Locally Commissioning the Macro NodeB (Transmission Available) This task describes how to locally commission the macro NodeB. 3.2 Locally Commissioning the Distributed NodeB (Transmission Available) This task describes how to locally commission the distributed NodeBs.
Issue 05 (2007-09-30)
3-1
3.1 Locally Commissioning the Macro NodeB (Transmission Available)

This task describes how to locally commission the macro NodeB.
Prerequisite
The requirements for the NodeB are as follows:
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. 1 NodeB Commissioning Resources are available. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded.
l l
The requirements for the RNC are as follows:

l
The RNC connected to the NodeB is installed and commissioned and the system works properly. The data of the NodeB to be commissioned is configured on the RNC and recorded.
Procedure
Step 1 6.1 Checking the DIP Switches Settings of the Macro NodeB. Step 2 7.1 Powering On the BTS3812E/7.2 Powering On the BTS3812AE . Step 3 8 Upgrading the NodeB Software and Downloading the Data Configuration File. 1. 2. 3. 4. 5. 6. 7. 8.1 Setting the IP Address of NodeB LMT PC. 8.2.1 Locally Connecting the LMT PC to the NodeB. 8.4.1 Locally Logging In to the NodeB on the LMT. 8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 4 9.1 Checking the Connection Between the RRU3801C and the Macro NodeB. This step is optional. This step is performed when the macro NodeB is configured with the RRU3801C. Step 5 10 Checking the Running Status of the NodeB. 1. 2. 3. 4. 5. 6.
3-2
10.1 Checking NodeB Transmission. 10.2 Commissioning SNTP. 10.3 Handling Alarms During NodeB Commissioning. 10.4 Checking the Status of a Cell. 10.5 Measuring the RTWP. 10.6 Monitoring the Output Power of the NodeB.
Huawei Technologies Proprietary Issue 05 (2007-09-30)
Step 6 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) at the site. If... The site is configured with the EMI, The site is not configured with the EMI, Then... 11 Commissioning the Alarm Equipment. Go to Step 7.
Step 7 Perform as follows according to the configuration of the antenna line device (ALD) at the site. If... The site is configured with the RET antenna, The site is configured with the STMA, The site is not configured with the ALD, Step 8 13 Testing NodeB Services . Step 9 Notify the M2000 administrator that the service-ready NodeB can be managed by the M2000. Step 10 Record the commissioning process and problems occurred during the commissioning in 16 NodeB Commissioning Data Sheet, and then export the commissioning report. ----End Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA. Go to Step 8.
3.2 Locally Commissioning the Distributed NodeB (Transmission Available)

This task describes how to locally commission the distributed NodeBs.
Prerequisite
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. 1 NodeB Commissioning Resources are available. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded.
l l

l
Huawei Technologies Proprietary 3-3
Issue 05 (2007-09-30)
Procedure
Step 1 6.2 Checking the DIP Switches Settings of the Distributed NodeB. Step 2 7.3 Powering On the DBS3800/7.4 Powering On the iDBS3800. Step 3 8 Upgrading the NodeB Software and Downloading the Data Configuration File. 1. 2. 3. 4. 5. 6. 7. 8.1 Setting the IP Address of NodeB LMT PC. 8.2.1 Locally Connecting the LMT PC to the NodeB. 8.4.1 Locally Logging In to the NodeB on the LMT. 8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 4 9.2 Checking the Internal Status of the DBS3800. To locally commission the DBS3800, perform this step. Step 5 9.3 Checking the Internal Status of the iDBS3800. To locally commission the iDBS3800, perform this step. Step 6 10 Checking the Running Status of the NodeB. 1. 2. 3. 4. 5. 6. 10.1 Checking NodeB Transmission. 10.2 Commissioning SNTP. 10.3 Handling Alarms During NodeB Commissioning. 10.4 Checking the Status of a Cell. 10.5 Measuring the RTWP. 10.6 Monitoring the Output Power of the NodeB.
Step 7 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) on the site. If... The site is configured with the EMI. The site is not configured with the EMI. Then... 11 Commissioning the Alarm Equipment. Go to Step 8.
Step 8 Perform as follows according to the configuration of the antenna line device (ALD) on the site. If... The site is configured with the RET antenna. The site is configured with the STMA Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA.
3-4
Issue 05 (2007-09-30)
If... The site is not configured with the ALD Step 9 13 Testing NodeB Services .
Then... Go to Step 9.
Step 10 Notify the M2000 administrator that the service-ready NodeB can be managed by the M2000. Step 11 Record the commissioning process and problems occurred during commissioning in 16 NodeB Commissioning Data Sheet, and then export the commissioning report. ----End
Issue 05 (2007-09-30)
3-5
4 Locally Commissioning the NodeB (Transmission Unavailable)
Locally Commissioning the NodeB (Transmission Unavailable)
About This Chapter

The RNC and NodeB are not properly connected. The NodeB is locally commissioned on the RNC Simulator. Ensure that the NodeB hardware is in good condition. After the RNC and the NodeB are properly connected, the NodeB can access the WCDMA Radio Access Network (RAN). 4.1 Locally Commissioning the Macro NodeB (Transmission Unavailable) This task describes how to commission the macro NodeB: BTS3812E, BTS3812A, and BTS3812AE on the RNC Simulator. 4.2 Locally Commissioning the Distributed NodeB (Transmission Unavailable) This task describes how to commission the distributed NodeBs: DBS3800 and iDBS3800 on the RNC Simulator.
Issue 05 (2007-09-30)
4-1
4.1 Locally Commissioning the Macro NodeB (Transmission Unavailable)

This task describes how to commission the macro NodeB: BTS3812E, BTS3812A, and BTS3812AE on the RNC Simulator.
Prerequisite
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. 1 NodeB Commissioning Resources are available. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded. The RNC connected to the NodeB is installed and commissioned and the system works properly. The data of the NodeB to be commissioned is configured on the RNC and recorded.
l l

l
Procedure
Step 1 6.1 Checking the DIP Switches Settings of the Macro NodeB. Step 2 7.1 Powering On the BTS3812E/7.2 Powering On the BTS3812AE . Step 3 8 Upgrading the NodeB Software and Downloading the Data Configuration File. 1. 2. 3. 4. 5. 6. 7. 8.1 Setting the IP Address of NodeB LMT PC. 8.2.1 Locally Connecting the LMT PC to the NodeB. 8.4.1 Locally Logging In to the NodeB on the LMT. 8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 4 14 Testing NodeB Services on RNC Simulator. Step 5 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) at the site. If... The site is configured with the EMI, The site is not configured with the EMI, Then... 11 Commissioning the Alarm Equipment. Go to Step 6.
Step 6 Perform as follows according to the configuration of the antenna line device (ALD) at the site.
If... The site is configured with the RET antenna, The site is configured with the STMA, The site is not configured with the ALD, Step 7 10.2 Commissioning SNTP.
Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA. Go to Step 7.
Step 8 10.3 Handling Alarms During NodeB Commissioning. Step 9 Notify the M2000 administrator that the service-ready NodeB can be managed by the M2000. Step 10 Record the commissioning process and problems occurred during the commissioning in 16 NodeB Commissioning Data Sheet, and then export the commissioning report. ----End
4.2 Locally Commissioning the Distributed NodeB (Transmission Unavailable)

This task describes how to commission the distributed NodeBs: DBS3800 and iDBS3800 on the RNC Simulator.
Prerequisite
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. 1 NodeB Commissioning Resources are available. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded. The RNC connected to the NodeB is installed and commissioned and the system works properly. The data of the NodeB to be commissioned is configured on the RNC and recorded.
l l

l
Procedure
Step 1 6.2 Checking the DIP Switches Settings of the Distributed NodeB. Step 2 7.3 Powering On the DBS3800/7.4 Powering On the iDBS3800. Step 3 8 Upgrading the NodeB Software and Downloading the Data Configuration File. 1. 2. 3.
Issue 05 (2007-09-30)
8.1 Setting the IP Address of NodeB LMT PC. 8.2.1 Locally Connecting the LMT PC to the NodeB. 8.4.1 Locally Logging In to the NodeB on the LMT.
4. 5. 6. 7.
8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 4 14 Testing NodeB Services on RNC Simulator. Step 5 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) on the site. If... The site is configured with the EMI. The site is not configured with the EMI. Then... 11 Commissioning the Alarm Equipment. Go to Step 6.
Step 6 Perform as follows according to the configuration of the antenna line device (ALD) on the site. If... The site is configured with the RET antenna. The site is configured with the STMA The site is not configured with the ALD Step 7 10.2 Commissioning SNTP. Step 8 10.3 Handling Alarms During NodeB Commissioning. Step 9 Notify the M2000 administrator that the service-ready NodeB can be managed by the M2000. Step 10 Record the commissioning process and problems occurred during commissioning in 16 NodeB Commissioning Data Sheet, and then export the commissioning report. ----End Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA. Go to Step 7.
4-4
Issue 05 (2007-09-30)
5 Remotely Commissioning the NodeB
Remotely Commissioning the NodeB
About This Chapter

This task describes how to remotely commission the NodeB. The scenario for this task is as follows: The RNC and NodeB are properly connected. The IPoA channel between the RNC and the NodeB works properly. The NodeB is commissioned remotely in the equipment room where the RNC is located. 5.1 Remotely Commissioning the Macro NodeB This task describes how to remotely commission the following macro NodeBs: BTS3812E, BTS3812A, and BTS3812AE. 5.2 Remotely Commissioning the Distributed NodeB This task describes how to remotely commission the distributed NodeBs: DBS3800 and iDBS3800 when they are connected to the RNC.
Issue 05 (2007-09-30)
5-1
5.1 Remotely Commissioning the Macro NodeB

This task describes how to remotely commission the following macro NodeBs: BTS3812E, BTS3812A, and BTS3812AE.
Prerequisite
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded. 1 NodeB Commissioning Resources are available. The cabinet is powered on.
l l

l
Procedure
Step 1 8 Upgrading the NodeB Software and Downloading the Data Configuration File. 1. 2. 3. 4. 5. 6. 7. 8. 8.1 Setting the IP Address of NodeB LMT PC. 8.2.2 Remotely Connecting the LMT PC to the NodeB (Through RNC BAM). 8.3 Setting the Route from the LMT PC to the NodeB. 8.4.2 Remotely Logging In to the NodeB (Through RNC BAM). 8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 2 10.2 Commissioning SNTP. Step 3 10.3 Handling Alarms During NodeB Commissioning. Step 4 10.4 Checking the Status of a Cell. Step 5 10.5 Measuring the RTWP. Step 6 10.6 Monitoring the Output Power of the NodeB. Step 7 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) on the site.
5-2
Issue 05 (2007-09-30)
If... The site is configured with the EMI. The site is not configured with the EMI.
Then... 11 Commissioning the Alarm Equipment. Go to Step 8.
Step 8 Perform as follows according to the configuration of the antenna line device (ALD) on the site. If... The site is configured with the RET antenna. The site is configured with the STMA The site is not configured with the ALD Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA. Go to Step 9.
5.2 Remotely Commissioning the Distributed NodeB

This task describes how to remotely commission the distributed NodeBs: DBS3800 and iDBS3800 when they are connected to the RNC.
Prerequisite
l
The hardware of the NodeB, such as the cabinet, cables, antenna system, and auxiliary devices, has passed the installation check. The associated data of the NodeB to be commissioned is negotiated with the RNC and the negotiation data is recorded. 1 NodeB Commissioning Resources are available. The cabinet is powered on.
l l

l
1 NodeB Commissioning Resources are available.
Procedure
Step 1 8 Upgrading the NodeB Software and Downloading the Data Configuration File.
Issue 05 (2007-09-30) Huawei Technologies Proprietary 5-3
1. 2. 3. 4. 5. 6. 7. 8.
8.1 Setting the IP Address of NodeB LMT PC. 8.2.2 Remotely Connecting the LMT PC to the NodeB (Through RNC BAM). 8.3 Setting the Route from the LMT PC to the NodeB. 8.4.2 Remotely Logging In to the NodeB (Through RNC BAM). 8.5 Upgrading the NodeB Software. 8.6 Downloading the NodeB Data Configuration File. 8.7 Resetting the NodeB. Log in to the NodeB LMT again.
Step 2 10.2 Commissioning SNTP. Step 3 10.3 Handling Alarms During NodeB Commissioning. Step 4 10.4 Checking the Status of a Cell. Step 5 Step 6 Step 7 Perform as follows according to the configuration of the Environment Monitoring Instrument (EMI) on the site. If... The site is configured with the EMI. The site is not configured with the EMI. Then... 11 Commissioning the Alarm Equipment. Go to Step 8.
Step 8 Perform as follows according to the configuration of the antenna line device (ALD) on the site. If... The site is configured with the RET antenna. The site is configured with the STMA The site is not configured with the ALD Then... 12.1 Commissioning the RET Antenna. 12.2 Commissioning the STMA. Go to Step 9.
5-4
Issue 05 (2007-09-30)
6 Checking the DIP Switches Settings of the NodeB
Checking the DIP Switches Settings of the NodeB
About This Chapter

This task describes how to check the DIP switches settings of the NodeB before commissioning. 6.1 Checking the DIP Switches Settings of the Macro NodeB This task describes how to check whether the DIP switches on the BESP, NDTI, and NUTI of the macro NodeB are correctly set before commissioning. 6.2 Checking the DIP Switches Settings of the Distributed NodeB This task describes how to check whether the DIP switches on the BBU3806 and BBU3806C of the distributed NodeB are correctly set before commissioning.
Issue 05 (2007-09-30)
6-1
6.1 Checking the DIP Switches Settings of the Macro NodeB

This task describes how to check whether the DIP switches on the BESP, NDTI, and NUTI of the macro NodeB are correctly set before commissioning.
Procedure
Step 1 Check the setting of the 6.1.1 DIP Switches on the BESP Board. Step 2 Check the setting of the 6.1.2 DIP Switches on the NDTI Board. Step 3 Check the setting of the 6.1.3 DIP Switches on the NUTI Board. ----End
6.1.1 DIP Switches on the BESP Board

Each BESP has four DIP switches numbered S1, S2, S3, and S4. They are used to set the grounding status of the RX and TX ends of an E1 cable. Bits 1 to 4 of each DIP switch define the grounding status of a transmission cable in the sequence of TX, RX, TX, RX. Note that ON indicates that the wire is grounded and that OFF indicates that the wire is not grounded. Table 6-1 describes the settings of the DIP switches. Table 6-1 DIP switches on the BESP S1 ON S2 ON S3 ON S4 ON Description Coaxial cable with the outer layer of its TX and RX ends grounded (default state). Coaxial cable with the outer layer of its TX ends grounded and that of its RX ends not grounded. Twisted pair Not defined.
ON
OFF
ON
OFF
OFF NOTE
OFF -
OFF -
OFF -
When the coaxial cable is used, the outer layer of the TX end is usually grounded. For example,
l l
When device A connects to device B, the outer layer of the TX ends on both devices must be grounded. If the outer layer is not enabled on device B, the outer layer of both RX and TX ends on device A must be grounded.
6.1.2 DIP Switches on the NDTI Board

The NDTI has nine DIP switches numbered from S3 to S11. DIP switches S3 through S6 are used to set matched impedance for the eight E1/T1s. Switches S7 through S10 are used to set the grounding status of the eight E1/T1s. Switch S11 is used to set the working mode and selection indication of matched impedance.
Figure 6-1 shows the DIP switches on the NDTI. Figure 6-1 DIP switches on the NDTI
The DIP switch S11 determines the E1/T1 working mode and matched impedance of the E1/T1 cables. At present, eight E1/T1 cables can use only one matched impedance. Bits 1 and 2 are in use, and bits 3 and 4 are reserved. S11 informs the software of the matched impedance setting for the E1/T1 cable. DIP switches S3 through S10 are used to set the hardware. Note that DIP switches S3 through S6 are used to set matched impedance for the eight E1/T1s and that switches S7 through S10 are reserved to set grounding state of the eight E1/T1s.
NOTE
You can set the grounding status of the E1/T1s on the BESP. For details, refer to 6.1.1 DIP Switches on the BESP Board.
DIP switches on the NDTI are set to 75-ohm unbalanced transmission mode before delivery. Table 6-2, Table 6-3, Table 6-4, and Table 6-5 list definitions of the DIP switches. Table 6-2 DIP switch S11 on the NDTI DIP Switch S11 Bit 1 2 75-Ohm E1 ON ON 120-Ohm E1 ON OFF
Issue 05 (2007-09-30)
6-3
Table 6-3 DIP switch S11 on the NDTI DIP Switch S11 Bit 1 2 100-Ohm T1 OFF ON Reserved OFF OFF
Table 6-4 DIP switches S3, S4, S5, and S6 on the NDTI DIP Switch S3 Link No. 0 Bit 1 2 1 3 4 S4 2 1 2 3 3 4 S5 4 1 2 5 3 4 S6 6 1 2 7 3 4 75-Ohm E1 ON OFF ON OFF ON OFF ON OFF ON OFF ON OFF ON OFF ON OFF 120-Ohm E1 OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF
Table 6-5 DIP switches S3, S4, S5, and S6 on the NDTI DIP Switch S3 Link No. 0 Bit 1 2 1 3 4 S4 2 1 100-Ohm T1 OFF ON OFF ON OFF Reserved ON ON ON ON ON
6-4
Issue 05 (2007-09-30)
DIP Switch
Link No.
Bit 2
100-Ohm T1 ON OFF ON OFF ON OFF ON OFF ON OFF ON
Reserved ON ON ON ON ON ON ON ON ON ON ON
3 4
S5
1 2
3 4
S6
1 2
3 4
6.1.3 DIP Switches on the NUTI Board

The NUTI has only one DIP switch labeled S11. This DIP switch is used to select the E1/T1 working mode and the matched impedance of the E1/T1 cables. At present, eight E1s/T1s support only one type of the matched impedance. Bits 1 and 2 are in use while bits 3 and 4 are reserved. S11 is used to inform the software of the matched impedance setting for the E1/T1 cable. Figure 6-2 shows DIP switch S11 on the NUTI.
Issue 05 (2007-09-30)
6-5
Figure 6-2 DIP switch on the NUTI
Table 6-6 describe the two bits on DIP switch S11. Table 6-6 Definitions of bits on DIP switch S11 on the NUTI DIP Switch S11 Bit 1 2 3 4 75-Ohm E1 OFF OFF Reserved Reserved 120-Ohm E1 ON ON Reserved Reserved 100-Ohm T1 ON OFF Reserved Reserved Default Setting OFF OFF OFF OFF
NOTE
The DIP switch on the NUTI is set to 75-ohm unbalanced transmission mode before delivery.
6.2 Checking the DIP Switches Settings of the Distributed NodeB

This task describes how to check whether the DIP switches on the BBU3806 and BBU3806C of the distributed NodeB are correctly set before commissioning.
6-6
Issue 05 (2007-09-30)
Procedure
Step 1 Check the setting of the 6.2.1 DIP Switch on the BBU3806. Step 2 Check the setting of the 6.2.2 DIP Switch on the BBU3806C. ----End
6.2.1 DIP Switch on the BBU3806

There is only one 8-bit DIP switch on the front panel of the BBU3806. The DIP switch on the BBU3806 has bits 1 to 8 from the left to the right, as shown in Figure 6-3. Figure 6-3 DIP switch on the BBU3806
l l
Bits 1 to 3, labeled TYPE, are by default set to OFF and reserved for later use. Bits 4 to 6, labeled LOCAT_ID, are used to set the working mode of the BBU3806 to active, standby, or extended. Bits 7 and 8, labeled E1/T1, are used to distinguish between 75-ohm E1, 120-ohm E1, and 100-ohm T1.
Table 6-7, Table 6-8, and Table 6-9 describe the settings of the 8-pin DIP switch. Table 6-7 Settings of the 8-pin DIP switch - 1 Bit 1 OFF Bit 2 OFF Bit 3 OFF Description Undefined and set to OFF by default
Table 6-8 Settings of the 8-pin DIP switch - 2 Bit 4 OFF ON OFF ON Bit 5 OFF OFF ON ON Bit 6 OFF OFF OFF OFF Description Active BBU3806 by default Standby BBU3806 Extended BBU3806 1 Extended BBU3806 2
6-7
Issue 05 (2007-09-30)
Table 6-9 Settings of the 8-pin DIP switch - 3 Bit 7 OFF OFF ON ON Bit 8 OFF ON OFF ON Description 120-ohm E1 100-ohm T1 Reserved 75-ohm E1 by default
NOTE
The combined BBU3806s are classified into active BBU3806, standby BBU3806, and extended BBU3806 by functions.
l l
The active BBU3806 provides clock signals and control signals for other BBU3806s. When there is only one BBU3806, it is set to the active mode by default. The standby BBU3806 receives clock signals and switchover signals from the active BBU3806. Both BBU3806s form a baseband resource pool. If the active BBU3806 is faulty, the standby BBU3806 automatically switches over to the active mode. The active and standby BBU3806s are connected through EIa ports. The extended BBU3806 is only used for service processing. It forms a baseband resource pool with the active or the standby BBU3806 through EIb ports.
l l
6.2.2 DIP Switch on the BBU3806C

The BBU3806C has only one DIP switch. Figure 6-4 shows the DIP switch on the BBU3806C. Figure 6-4 DIP switch on the BBU3806C
Bits 1 and 2 are reserved, and bits 3 and 4 are used to set the E1/T1 mode and line impedance. Table 6-10 describes the settings of bits 3 and 4 on the DIP switch.
Table 6-10 Settings of bits 3 and 4 on the DIP switch Bit 3 OFF OFF ON ON Bit 4 OFF ON OFF ON Description 120-ohm E1 100-ohm T1 Reserved 75-ohm E1 by default
Issue 05 (2007-09-30)
6-9
7 Powering On the NodeB
7
About This Chapter
Powering On the NodeB
This task describes how to power on the NodeB after the DIP switches are correctly set. 7.1 Powering On the BTS3812E This describes how to power on the cabinet of the BTS3812E. Before BTS3812E power-on, check that all the power cables are installed and the power switches on the busbar are set to OFF. After power-on, you must check the power supplies to the components inside the cabinet. 7.2 Powering On the BTS3812AE Before powering on the BTS3812AE cabinet, connect the power cables of 196 V to 240 V AC power and set all the power switches to OFF. 7.3 Powering On the DBS3800 This task describes how to power on the DBS3800. The task consists of powering on the BBU3806, BBU3806C, and RRU3801C. 7.4 Powering On the iDBS3800 This task describes how to power on the iDBS3800. The task consists of powering on the BBU3806, RHUB3808, and pRRU3801.
Issue 05 (2007-09-30)
7-1
7.1 Powering On the BTS3812E

This describes how to power on the cabinet of the BTS3812E. Before BTS3812E power-on, check that all the power cables are installed and the power switches on the busbar are set to OFF. After power-on, you must check the power supplies to the components inside the cabinet.
Prerequisite
The power supply to the BTS3812E meets the requirements described in Power Supply Requirements of the BTS3812E.
Context
CAUTION
Before connecting external power supply to the cabinet, measure the impedance of the power supply wiring posts and grounding wiring posts by using a multimeter. Ensure that no short circuit exists.
NOTE
The color of the 48 V power cable is blue, and that of the 48 V RTN cable is black.
Procedure
Step 1 Set the FAN air breaker on the busbar to ON and ensure that the fans operate properly. Step 2 Set the NBBU air breaker on the busbar to ON and ensure that the boards in the NBBU subrack operate properly. Step 3 Set the air breakers TRU0TRU5 on the busbar to ON and ensure that the MTRU modules operate properly. Step 4 Set the AFU air breaker on the busbar to ON and ensure that the MAFU modules operate properly. ----End
Postrequisite
Check the power supply to the modules inside the cabinets according to Table 7-1. Table 7-1 Checklist for power supply to the cabinet components Component Fan drawer Cabinet Fan subrack Power LED The STATE LED is green and blinks at 0.5 Hz (1s ON, 1s OFF).
Issue 05 (2007-09-30)
7-2
Component Board MTRUs 0 to 5 MAFU
Cabinet Baseband subrack MTRU subrack MAFU subrack
Power LED The RUN LED is green and blinks at 0.5 Hz (1s ON, 1s OFF). The RUN LED is green and blinks at 0.5 Hz (1s ON, 1s OFF). The PWR LED is green and ON steady.
NOTE
Table 7-1 describes the status of the LEDs on the boards or modules when the power-on status is normal and the configuration files of the boards or modules are correct.
7.2 Powering On the BTS3812AE

Before powering on the BTS3812AE cabinet, connect the power cables of 196 V to 240 V AC power and set all the power switches to OFF.
Context
Figure 7-1 shows the power switches on the power distribution box.
Issue 05 (2007-09-30)
7-3
Figure 7-1 Power switches on the power distribution box
(1) AC power switches (2) Power distribution box (3) DC power switches
Table 7-2 lists the relationship between devices and DC power switches.
7-4
Issue 05 (2007-09-30)
Table 7-2 Relationship between devices and DC power switches Device MAFUs 0 to 5 MTRU0 MTRU1 MTRU2 MTRU3 MTRU4 MTRU5 FAN Boards in baseband subrack Heat exchanger Lamp DC Power Switch AFU TRU0 TRU1 TRU2 TRU3 TRU4 TRU5 FAN NBBU HEX LAMP
Procedure
Step 1 Set "PSU1, 4, 5", "PSU2, 6", and "PSU3, 7" to ON in sequence and ensure that all PSUs run properly. Step 2 Set the AC power switch ACU/HEX and DC power switches HEX and FAN to ON and ensure that the heat exchanger and fan subrack run properly. Step 3 Set DC power switches TRU0 to TRU5, NBBU, and AFU to ON and ensure that all the boards run properly. ----End
7.3 Powering On the DBS3800

This task describes how to power on the DBS3800. The task consists of powering on the BBU3806, BBU3806C, and RRU3801C.
Prerequisite
Ensure that the voltage range of the input power is normal.
Procedure
l Power on the BBU3806. 1. 2. Turn on the power switch of the BBU3806. Check the states of the LEDs on the BBU3806. Table 7-3 describes the LEDs and their states.
Issue 05 (2007-09-30)
Table 7-3 LEDs on the BBU3806 LED RUN Color Yellow State ON OFF 1 s ON, 1 s OFF 0.25 s ON, 0.25 s OFF ALM Red ON OFF ACT Yellow ON OFF 3. Description The BBU3806 has power input but the module is faulty. The BBU3806 has no power input, or the module is faulty. The BBU3806 is running as configured. Software is being loaded to the BBU3806, or the BBU3806 is not configured. The BBU3806 is reporting alarms (not including VSWR-related alarms). The BBU3806 is operational. The BBU3806 is running or is active. The BBU3806 is not running or is standby.
Perform the next step based on the states of the LEDs. If... The BBU3806 is operational, The BBU3806 is faulty, Then... End the power-on task. Clear the fault, and then go to Step 1.
Power on the BBU3806C. 1. 2. Turn on the power switch of the BBU3806C. Check the states of the LEDs in the maintenance cavity of the BBU3806C. Table 7-4 describes the LEDs and their states. Table 7-4 LEDs on the BBU3806C LED RUN Color Yellow State ON OFF 1 s ON, 1 s OFF 0.25 s ON, 0.25 s OFF Description The BBU3806C has power input but the module is faulty. The BBU3806C has no power input, or the module is faulty. The BBU3806C is running as configured. Software is being loaded to the BBU3806C, or the BBU3806C is not configured.
7-6
Issue 05 (2007-09-30)
LED ALM
Color Red
State ON
Description The BBU3806C is reporting alarms (not including VSWRrelated alarms). The BBU3806C is operational. The BBU3806C is running or is active. The BBU3806C is not running or is standby.
OFF ACT Yellow ON OFF 3.
Perform the next step based on the states of the LEDs. If... The BBU3806C is operational, The BBU3806C is faulty, Then... End the power-on task. Clear the fault, and then go to Step 1.
Power on the RRU3801C. 1. 2. Turn on the power switch of the RRU3801C. Check the states of the LEDs in the maintenance cavity of the RRU3801C. Table 7-5 describes the LEDs and their states. Table 7-5 LEDs on the RRU3801C LED RUN Color Yellow State ON OFF 1 s ON, 1 s OFF 0.5 s ON, 0.5 s OFF ALM Red ON Description The RRU3801C has power input but the module is faulty. The RRU3801C has no power input, or the module is faulty. The RRU3801C is running as configured. Software is being loaded to the RRU3801C, or the RRU3801C is not configured. The RRU3801C is reporting alarms (not including VSWRrelated alarms). The RRU3801C is operational.
OFF 3.
Perform the next step based on the states of the LEDs. If... The RRU3801C is operational, The RRU3801C is faulty, Then... End the power-on task. Clear the fault, and then go to Step 1.
----End
7.4 Powering On the iDBS3800

This task describes how to power on the iDBS3800. The task consists of powering on the BBU3806, RHUB3808, and pRRU3801.
Procedure
l Power on the BBU3806. 1. 2. Turn on the power switch of the BBU3806. Check the states of the LEDs on the BBU3806. Table 7-6 describes the LEDs and their states. Table 7-6 LEDs on the BBU3806 LED RUN Color Yellow State ON OFF 1 s ON, 1 s OFF 0.25 s ON, 0.25 s OFF ALM Red ON OFF ACT Yellow ON OFF 3. Description The BBU3806 has power input but the module is faulty. The BBU3806 has no power input, or the module is faulty. The BBU3806 is running as configured. Software is being loaded to the BBU3806, or the BBU3806 is not configured. The BBU3806 is reporting alarms (not including VSWR-related alarms). The BBU3806 is operational. The BBU3806 is running or is active. The BBU3806 is not running or is standby.
Perform the next step based on the states of the LEDs. If... The BBU3806 is operational, The BBU3806 is faulty, Then... End the power-on task. Clear the fault, and then go to Step 1.
Power on the RHUB3808. 1. 2. Turn on the power switch of the RHUB3808 to power on the RHUB3808. Check the status of the RUN LED of RHUB3808.
7-8
Issue 05 (2007-09-30)
Condition ON steady
Description The power input is functional but the RHUB3808 is faulty. There is no power input, or the RHUB3808 works with alarms.
Action Power off the RHUB3808 immediately, clear the fault, and power on the RHUB3808 again. Power off the RHUB3808 immediately, and check the power input again. If the power input is normal, clear the fault in the RHUB3808, and then power on the RHUB3808 again. End the operation. Wait until loading the software is complete. If loading the software is not complete within 5 minutes, power off the RHUB3808 and check whether the data configuration files are correct. After the fault is cleared, power on the RHUB3808 again.
OFF steady
1 s ON, 1 s OFF 0.125 s ON, 0.125 s OFF
The RHUB3808 runs properly. The RHUB3808 is loading the software.
Power on the pRRU3801. 1. Measure the power voltage of the pRRU3801. Condition The power adapter at the optical port of the pRRU3801 uses the AC power supply of 100 V to 240 V. The green indicator PWR at the electrical port of pRRU3801 is on steady. 2. Action Refer to 2; or find the cause until the requirement is met and then refer to 2.
Refer to 2; or find the cause until the requirement is met; then refer to 2.
Check the status of the indicator RUN of pRRU3801. Condition ON steady Description The power input is functional but the pRRU3801 is faulty. There is no power input, or the pRRU3801 works with alarms. Action Power off the pRRU3801 immediately, clear the fault, and power on the pRRU3801 again. Power off the pRRU3801 immediately, and check the power input again. If the power input is normal, clear the fault of pRRU3801, and then power on pRRU3801 again. End the operation.
OFF steady
1s ON, 1s OFF
The pRRU3801 runs properly.
Issue 05 (2007-09-30)
7-9
Condition 0.125s ON, 0.125s OFF
Description The pRRU3801 is loading the software.
Action Wait until loading the software is complete. If loading the software is not complete within 5 minutes, power off the pRRU3801. Check whether the data configuration files are correct. After the fault is cleared, power on the pRRU3801 again.
----End
7-10
Issue 05 (2007-09-30)
8 Upgrading the NodeB Software and Downloading the Data Configuration File
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 idle space on the disk is not less than 1 G during the operation. 8.1 Setting the IP Address of NodeB LMT PC This task describes how to set the IP address of the NodeB LMT PC. You must set a correct IP address for the LMT PC before logging in to the NodeB. 8.2 Connecting the LMT PC to the NodeB This task is of three types: local connection, remote connection through the RNC BAM server, and remote connection through the M2000. 8.3 Setting the Route from the LMT PC to the NodeB This task describes how to set the route from the LMT PC to the NodeB in remote maintenance mode. The route from the LMT PC to the NodeB must be set. Otherwise, you cannot log in to the NodeB on the LMT PC. 8.4 Logging In to the NodeB on the NodeB LMT This task is of three types: local login, remote login through the RNC BAM server, and remote login through the M2000. 8.5 Upgrading the NodeB Software This task describes how to upgrade the NodeB software. The task consists of the following: checking the compatibility of the NodeB software versions, downloading the NodeB BootROM, activating the NodeB BootROM, downloading the NodeB software, and activating the NodeB software. 8.6 Downloading the NodeB Data Configuration File This task describes how to download the NodeB data configuration file from the FTP server to the NodeB. The NodeB data configuration file will take effect after the NodeB is reset. 8.7 Resetting the NodeB
Upgrading the NodeB Software and
Issue 05 (2007-09-30)
8-1
This task describes how to reset the NodeB. You need to reset the NodeB upon a NodeB failure or after a configuration update.
8-2
Issue 05 (2007-09-30)
8.1 Setting the IP Address of NodeB LMT PC

This task describes how to set the IP address of the NodeB LMT PC. You must set a correct IP address for the LMT PC before logging in to the NodeB.
Prerequisite
The LMT PC has configured the TCP/IP protocol.
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. In remote maintenance, you need to set the route from the LMT PC to the NodeB; IP 1 and IP 2 are in the same network segment. 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 8-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. To set the IP address of the LMT PC with the Windows XP operating system as an example, perform the following steps:
Procedure
Step 1 Choose Start > Settings > Control Panel > Network Connections. The Network Connections window is displayed. Step 2 Right-click the icon of Local Area Connection. Step 3 Click Properties on the shortcut menu. The Local Area Connection Properties dialog box is displayed.
Step 4 Select Internet Protocol (TCP/IP). Step 5 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed. Step 6 Select Use the following IP address. Step 7 Enter the correct IP address, subnet mask, and default gateway. If... In local maintenance mode Then... Set the IP address, subnet mask, and default gateway, as shown in Table 8-1.
In remote maintenance mode Set the IP address, subnet mask, and default gateway, as shown in Table 8-2.
Table 8-1 IP parameters of LMT PC in local maintenance mode Parameter IP address Subnet mask Default gateway Description In the same network segment as that of the NodeB local maintenance channel. -
Table 8-2 IP parameters of LMT PC in remote maintenance mode Parameter IP address Subnet mask Default gateway Description In the same network segment as the external IP address of RNC BAM. The same subnet mask as the external subnet mask of RNC BAM. The IP address of BAM external network is the gateway from LMT to 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 8 Clock OK. The settings are complete. ----End
8.2 Connecting the LMT PC to the NodeB

This task is of three types: local connection, remote connection through the RNC BAM server, and remote connection through the M2000. 8.2.1 Locally Connecting the LMT PC to the NodeB
This task describes how to connect the LMT PC to the NodeB in local maintenance mode to operate and maintain the NodeB. 8.2.2 Remotely Connecting the LMT PC to the NodeB (Through RNC BAM) This task describes how to connect the LMT PC to RAN OM intranet (that is, the RNC BAM LAN) in remote maintenance mode. 8.2.3 Remotely Connecting the LMT PC to the NodeB (on M2000) This task describes how to connect the LMT PC to RAN on the M2000 server in remote maintenance mode.
8.2.1 Locally Connecting the LMT PC to the NodeB

This task describes how to connect the LMT PC to the NodeB in local maintenance mode to operate and maintain the NodeB.
Prerequisite
The IP address of the LMT PC and that of the local maintenance channel are in the same network segment.
Procedure
Step 1 To connect the LMT PC to the NodeB, perform the following steps: If... Then...
For macro NodeBs Connect the Ethernet port of the LMT PC to that of the NodeB NMPT through crossover cables, as shown in Figure 8-2. For the BBU3806 Connect the Ethernet port of the LMT PC to the upper ETH port of the BBU front plate with a crossover cable, as shown in Figure 8-3.
For the BBU3806C Connect the Ethernet port of the LMT PC to the ETH port of the BBU3806C maintenance cavity with a crossover cable, as shown in Figure 8-4.
Issue 05 (2007-09-30)
8-5
Figure 8-2 Connecting LMT PC and NMPT in local maintenance mode
(1) NMPT
(2) Crossover cable
(3) LMT PC
Figure 8-3 Connecting LMT PC and BBU3806 in local maintenance mode
(1) BBU3806
(2) Crossover cable
(3) LMT PC
8-6
Issue 05 (2007-09-30)
Figure 8-4 Connecting LMT PC and BBU3806C in local maintenance mode
(1) Maintenance cavity of the BBU3806C
(2) Crossover cable
(3) LMT PC
Step 2 Choose Start > Run on the LMT PC, run cmd in the Run dialog box. A command window is displayed. Step 3 Run ping target_name and verify the connection between computer and NodeB network. Where, target_name can be replaced with the IP address of the NodeB local maintenance channel. ----End
8.2.2 Remotely Connecting the LMT PC to the NodeB (Through RNC BAM)
This task describes how to connect the LMT PC to RAN OM intranet (that is, the RNC BAM LAN) in remote maintenance mode.
Prerequisite
The IP address of the remote LMT PC is set and it is in the same network segment as the external IP address of the RNC BAM.
Procedure
Step 1 Use an Ethernet cable to connect the Ethernet port of the LMT PC to one Ethernet port of the RAN OM intranet (that is, the RNC BAM LAN). 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 and verify the connection between the LMT PC and the communication gateway. Where, target_name can be replaced with the external IP address of the RNC BAM. ----End
8.2.3 Remotely Connecting the LMT PC to the NodeB (on M2000)

This task describes how to connect the LMT PC to RAN on the M2000 server in remote maintenance mode.
Prerequisite
The IP address of the remote LMT PC is set and it is in the same network segment as the M2000 server.
Procedure
Step 1 Use an Ethernet cable to connect the Ethernet port of the LMT PC to that of the M2000 server. Use an Ethernet cable to connect the Ethernet port of the M2000 server to that of the RAN OM intranet (that is, the RNC BAM external network). 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 and verify the connection between the LMT PC and the communication gateway. Where, target_name can be replaced with the IP address of the M2000 server. ----End
8.3 Setting the Route from the LMT PC to the NodeB

This task describes how to set the route from the LMT PC to the NodeB in remote maintenance mode. The route from the LMT PC to the NodeB must be set. Otherwise, you cannot log in to the NodeB on the LMT PC.
Procedure
Step 1 On the LMT PC, choose Start > Run, and then run the cmd command in the dialog box. The command window is displayed. Step 2 Run ROUTE ADD Networkaddress MASK netmask gatewayaddress in the command window to add a route from the computer to the gateway. Set Networkaddress, netmask, and gatewayaddress by referring to Table 8-3. Table 8-3 Description of route parameters Parameter Networkaddress netmask gatewayaddress Description IP address of the NodeB in remote maintenance mode Subnet mask that is the same as the external subnet mask of RNC BAM External IP address of the BAM
8-8
Issue 05 (2007-09-30)

NOTE
l l
Different NodeBs corresponds to different IP addresses. The IP address in the same network segment corresponds to the same subnet mask and subnet address (subnet mask AND IP address).
Step 3 Run ping target_name and verify the connection between the LMT PC and the NodeB. target_name is the IP address of the NodeB OMIP. ----End
8.4 Logging In to the NodeB on the NodeB LMT

This task is of three types: local login, remote login through the RNC BAM server, and remote login through the M2000. 8.4.1 Locally Logging In to the NodeB on the LMT This task describes how to log in to the NodeB on the LMT. 8.4.2 Remotely Logging In to the NodeB (Through RNC BAM) This task describes how to log in to the NodeB through the RNC BAM. 8.4.3 Remotely Logging In to the NodeB (on M2000) This task describes how to log in to the NodeB on the M2000. By performing this task, you can maintain the NodeB on the M2000 server.
8.4.1 Locally Logging In to the NodeB on the LMT

This task describes how to 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 Local Maintenance Terminal is started, choose System > Log Out or click . The User Login dialog box is displayed, as shown in Figure 8-5. Figure 8-5 User Login dialog box
Issue 05 (2007-09-30)
8-9
Table 8-4 describes the elements in the User Login dialog box. Table 8-4 Elements in the User Login dialog box Element User Description In this element, enter the user name that would be used to log in to the NodeB. It is a mandatory element and is case sensitive. The default name is admin. In this element, enter the password that would be used to log in to the NodeB. It consists of 6 to 16 characters and should contain only letters and numbers. It is case sensitive. The default password is NodeB. Select the name and IP address of the NodeB that is connected to the to edit the office information. For details, refer to LMT. Click Setting the Information of 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 Keep this element blank. Ensure that you do not select the check box.
Password
Office
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 8-6, it indicates that the NodeB language does not match the LMT language. In this case, switch the NodeB language to log in to the NodeB. Figure 8-6 Switching the NodeB language
CAUTION
The NodeB will be reset after you switch the NodeB language. Step 6 Click Yes to switch the NodeB language.
8-10
Issue 05 (2007-09-30)

NOTE
If you click No, The language of NE differs from LMT is displayed in the dialog box. Click OK. You can still log in to the NodeB. However, logging in to the NodeB leads to the following results:
l l
The language of the NodeB software message that is reported to the LMT does not match the LMT language. When software management operations are performed, message analysis fails.
----End
8.4.2 Remotely Logging In to the NodeB (Through RNC BAM)

This task describes how to log in to the NodeB through the RNC BAM.
Prerequisite
l l
The connections between the LMT PC, RNC BAM, and NodeB are normal. The route from the LMT PC to the NodeB is set.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Local Maintenance Terminal. If the Local Maintenance Terminal is started, choose System > Relogin or click . The User Login dialog box is displayed, as shown in Figure 8-7. Figure 8-7 User Login dialog box
Table 8-5 describes the elements User Login dialog box. Table 8-5 Elements in the User Login dialog box Element User Description In this element, enter the user name that would be used to log in to the NodeB. It is a mandatory element and is case sensitive. The default name is admin.
Issue 05 (2007-09-30)
Element Password
Description In this element, enter the password that would be used to log in to the NodeB. It consists of 6 to 16 characters and should contain only letters and numbers. It is case sensitive. The default password is NodeB. 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 of an Office on the NodeB LMT. When you log in to the NodeB remotely, the IP address of the office must be the same as that of the NodeB remote maintenance channel.
Office
Proxy server
Keep this element 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 8-8, it indicates that the NodeB language does not match the LMT language. In this case, switch the NodeB language to log in to the NodeB. Figure 8-8 Switching the NodeB language
CAUTION
NOTE
If you click No, The language of NE differs from LMT is displayed in the dialog box. Click OK. You can still log in to the NodeB. However, logging in to the NodeB leads to the following results:
l l
----End
8-12
Issue 05 (2007-09-30)
8.4.3 Remotely Logging In to the NodeB (on M2000)

This task describes how to log in to the NodeB on the M2000. By performing this task, you can maintain the NodeB on the M2000 server.
Prerequisite
The active M2000 user are authorized for managing the NodeB on the M2000 and a corresponding NE user exists.
Context
To log in to the NodeB on the M2000, you can use either of the following methods:
l
Method 1: Set the M2000 to the default gateway, set the route from the LMT PC to the NodeB, and then log in to the NodeB. Method 2: Log in to the M2000 on the LMT, and then maintain the NodeB.
Procedure
Step 1 Choose Start > All Programs > Huawei Local Maintenance Terminal > Local Maintenance Terminal. If the Local Maintenance Terminal is started, choose System > Log In or click to display the User Login dialog box, as shown in Figure 8-9. Figure 8-9 User Login dialog box
Table 8-6 describes the elements in the User Login dialog box. Table 8-6 Elements in the User Login dialog box Element User Description Enter the user name of the NodeB. The default user name is admin. The user name is mandatory and case-sensitive.
Issue 05 (2007-09-30)
8-13
Element Password
Description Enter the password of the NodeB. The default password is NodeB. The password consists of 6 to 16 alphanumeric and case-sensitive characters. Click to edit the office information. For details, refer to Setting the Information of an Office on the NodeB LMT.
l
Office
If you use method 1, select the name and IP address of the NodeB connected to the LMT. The IP address of the office is the IP address of the NodeB remote maintenance channel. If you use method 2, select the name and IP address of the M2000 server. The IP address of the office is the IP address of the M2000 server.
Proxy Server
Keep 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 Perform different steps according to different login methods. If... Then...
Method 1 is used Go to Step 7. Method 2 is used The NodeB List dialog box is displayed, as shown in Figure 8-10. Go to Step 6.
Figure 8-10 NodeB List dialog box
8-14
Issue 05 (2007-09-30)
Step 6 In the dialog box, select the NodeB to be maintained and then click OK. Step 7 If a dialog box is displayed, as shown in Figure 8-11, 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 8-11 Switching the NodeB language
CAUTION
NOTE
If you click No, a dialog box is displayed, prompting The language of NE differs from LMT. Click OK. You are logged in to the NodeB. But this step leads to the following results:
l l
----End
8.5 Upgrading the NodeB Software

This task describes how to upgrade the NodeB software. The task consists of the following: checking the compatibility of the NodeB software versions, downloading the NodeB BootROM, activating the NodeB BootROM, downloading the NodeB software, and activating the NodeB software. 1. 8.5.1 Checking the Compatibility of the NodeB Software Version This task 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. 8.5.2 Downloading the BootROM Software Package of the NodeB This task describes how to download the BootROM software package from the FTP server to the NodeB standby file directory. 8.5.3 Activating the BootROM Software of the NodeB This task describes how to activate the NodeB BootROM software. Activating the BootROM means downloading the BootROM in the NodeB standby file directory to each board and upgrading the board BootROM.
2.
3.
Issue 05 (2007-09-30)
4.
8.5.4 Downloading the Software of the NodeB This task describes how to download the NodeB software from the FTP server to the standby file directory on the NodeB. The NodeB software does not take effect immediately or damage the running software after the download. 8.5.5 Activating the Software of the NodeB This task describes how to download the software stored in the standby file directory to each board and make it effective. You can activate the NodeB software right after the downloading or later on.
5.
8.5.1 Checking the Compatibility of the NodeB Software Version

This task 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 l
You have logged in to the NodeB LMT. If two NMPTs or HBBUs are configured, use the command DSP BRD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check the board status in order to determine which NMPT or HBBU is active.
Procedure
Step 1 Querying the Software Version of the NodeB. Step 2 Check whether the current NodeB software version is consistent with that to be used. Then record the result in the 16 NodeB Commissioning Data Sheet. If... The current NodeB software version is consistent with that to be used. The current BootROM version is inconsistent with that to be used. The current NodeB software version is inconsistent with that to be used. Then... End this task. Go to Step 3. Go to Step 4.
Step 3 Check whether the BootROM version to be used is stored in the standby directory. If... Then...
The latest version is stored in the standby Activate the BootROM. For details, refer to directory. 8.5.3 Activating the BootROM Software of the NodeB.
8-16
Issue 05 (2007-09-30)
If... The latest version is not stored in the standby directory.
Then... Download and activate the new BootROM. For details, refer to 8.5.2 Downloading the BootROM Software Package of the NodeB and 8.5.3 Activating the BootROM Software of the NodeB.
Step 4 Check whether the NodeB version to be used is stored in the standby directory. If... Then...
The latest version is stored in the standby Activate the BootROM. For details, refer to directory. 8.5.5 Activating the Software of the NodeB. The latest version is not stored in the standby directory. Download and activate the new NodeB software. For details, refer to 8.5.4 Downloading the Software of the NodeB and 8.5.5 Activating the Software of the NodeB.
----End
8.5.2 Downloading the BootROM Software Package of the NodeB

This task describes how to download the BootROM software package from the FTP server to the NodeB standby file directory.
Prerequisite
l l l l
You are logged in to the NodeB LMT. The FTP server works properly and is connected to the NodeB in the same intranet. There is no firewall between the FTP server and the NodeB. The user name and password for logging in to the specified FTP server are correct. Ensure that you have the permission to read the data in the specified directory.
Procedure
Step 1 Click the Maintenance tab in the navigation pane. Step 2 Double-click Software Management > Software Update. The Software Update dialog box is displayed, as shown in Figure 8-12.
Issue 05 (2007-09-30)
8-17
Figure 8-12 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 8-13.
8-18
Issue 05 (2007-09-30)
Figure 8-13 Upgrade BOOTROM dialog box
Table 8-7 describes the elements in the Upgrade BOOTROM dialog box. Table 8-7 Elements in the Upgrade BOOTROM dialog box Element FTP Setting Description This enables you to set the FTP server for uploading and downloading BootROM software package. The FTP server in use is shown in the box for your reference. It can be a built-in server or a user-specified server. Click Modify on the right to set the FTP server.
Issue 05 (2007-09-30)
8-19
Element Download BOOTROM Package
Description This enables you to download the BootROM software package from the FTP server to the NodeB standby file directory. Click Browse to locate the directory of the BootROM software package in the FTP server. Select this check box to download the BootROM software package. This operation is mandatory for the BootROM upgrade. Because the BootROM software package has a fixed file name of NBRom.pck, you only need to specify the path of it.
Activate BOOTROM
This enables you to activate the BootROM software right after the BootROM software package is downloaded.
l
If you select both Download BOOTROM Package and Activate BOOTROM, the BootROM software version to be activated is the BootROM software package downloaded from the FTP server. You need not to select the version. If you select Activate BOOTROM without selecting Download BOOTROM Package, the system lists all the BootROM versions that can be activated. Select the BootROM version to be upgraded in the Version box.
NOTE
l l
The system downloads the BootROM package and then activates it. You can select only one of these operations. If one operation is not selected, it is skipped in the execution process.
Step 5 Click Modify. The FTP Setting dialog box is displayed, as shown in Figure 8-14.
8-20
Issue 05 (2007-09-30)
Figure 8-14 FTP Setting dialog box
Table 8-8 describes the elements in the FTP Setting dialog box. Table 8-8 Elements in the FTP Setting dialog box Element Use Built-in FTP Server Description 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. The FTP server can either be started from the local computer installed with the LMT application or from another computer. Here it refers to the IP address of the FTP server. This enables you to specify the user name for logging in to the FTP server. This enables you to specify the password for logging in to the FTP server.
Use Specified FTP Server
IP Address
User Password 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 BOOTROM Progress dialog box is displayed. The status and progress of the procedure are displayed in the dialog box. You can check the procedure by viewing this dialog box. ----End
Issue 05 (2007-09-30)
8-21
8.5.3 Activating the BootROM Software of the NodeB

This task describes how to activate the NodeB BootROM software. Activating the BootROM means downloading the BootROM in the NodeB standby file directory to each board and upgrading the board BootROM.
Prerequisite
You are logged in to the NodeB LMT.
Context
l
Before the activation, the system checks the BootROM versions of the boards. It activates the board BootROM only when there is a new BootROM version. If there is no new BootROM version, the system does not activate the board BootROM. If the BootROM activation of a board fails, locate the cause and then activate the BootROM software of that board again. For details, refer to Activating the BootROM Software of a Board. Because the BootROM software 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. After the BootROM is activated, the NodeB is not reset.
Procedure
Step 1 Click the Maintenance tab in the navigation pane. Step 2 Double-click Software Management > Software Update. The Software Update dialog box is displayed, as shown in Figure 8-15.
8-22
Issue 05 (2007-09-30)
Figure 8-15 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 8-16.
Issue 05 (2007-09-30)
8-23
Figure 8-16 Upgrade BOOTROM dialog box
Table 8-9 describes the elements in the Upgrade BOOTROM dialog box. Table 8-9 Elements in the Upgrade BOOTROM dialog box Element FTP Setting Description This enables you to set the FTP server for uploading and downloading BootROM software package. The FTP server in use is shown in the box for your reference. It can be a built-in server or a user-specified server. Click Modify on the right to set the FTP server.
8-24
Issue 05 (2007-09-30)
Element Download BOOTROM Package
Description This enables you to download the BootROM software package from the FTP server to the NodeB standby file directory. Click Browse to locate the directory of the BootROM software package in the FTP server. Select this check box to download the BootROM software package. This operation is mandatory for the BootROM upgrade. Because the BootROM software package has a fixed file name of NBRom.pck, you only need to specify the path of it.
Activate BOOTROM
This enables you to activate the BootROM software right after the BootROM software package is downloaded. If you select both Download BOOTROM Package and Activate BOOTROM, the BootROM software version to be activated is the BootROM software package downloaded from the FTP server. You need not to select the version. If you select Activate BOOTROM without selecting Download BOOTROM Package, the system lists all the BootROM versions that can be activated. Select the BootROM version to be upgraded in the Version box.
Step 5 Select Active BOOTROM in the dialog box. Then select the BootROM software version to be upgraded from the Version drop-down list.
NOTE
The Version box is displayed only when Download BOOTROM Package is not selected.
Step 6 Click Next. A dialog box is displayed for your confirmation. Step 7 Click Yes. The Upgrading BOOTROM Progress dialog box is displayed. The status and progress of the procedure are displayed in the dialog box. You can check the procedure by viewing this dialog box. ----End
8.5.4 Downloading the Software of the NodeB

This task describes how to download the NodeB software from the FTP server to the standby file directory on the NodeB. The NodeB software does not take effect immediately or damage the running software after the download.
Prerequisite
l

Issue 05 (2007-09-30)
l l l
The FTP server works properly and is connected to the NodeB in the same intranet. There is no firewall between the FTP server and the NodeB. The user name and password for logging in to the specified FTP server are correct. Ensure that you have the permission to read the data in the specified directory.
Procedure
Step 1 Click the Maintenance tab in the navigation pane. Step 2 Double-click Software Management > Software Update. The Software Update dialog box is displayed, as shown in Figure 8-17. Figure 8-17 Software Update 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 8-18.
8-26
Issue 05 (2007-09-30)
Figure 8-18 Upgrade NodeB Software dialog box
Table 8-10 describes the elements in the Upgrade NodeB Software dialog box. Table 8-10 Elements in the Upgrade NodeB Software dialog box Element FTP Setting Description This enables you to set the FTP server for downloading files. The FTP server that is in use is shown in the box for your reference. The FTP server can be a built-in server or a userspecified server. To set the FTP server, click Modify on the right side of the element.
Issue 05 (2007-09-30)
8-27
Element Backup Data Configuration File
Description This enables you to upload the configuration file from the NodeB to the FTP server. To specify a path for the file upload, click Browse under Backup Data Configuration File. Select the path to back up the active configuration file in the system. If you have already backed up the file, you can skip this step. In case of upgrade failure, you can reload the backup configuration file in the FTP server to guarantee stable operation of the NodeB.
This enables you to download the data configuration file from the server to the NodeB and overwrite the previous data configuration file. To specify a path for the file download, click Browse. This operation is optional. The data configuration file has a fixed name of NodeBCfg.xml. Therefore, you only need to specify the path in which the file would be saved.
Download NodeB Software Package
This enables you to download the NodeB software package from the FTP server to the NodeB standby directory. Click Browse under Download NodeB Software Package. Select the directory of the package in the FTP server. The system will start the download after backing up the configuration file. This operation is mandatory for NodeB software upgrade. Therefore, you only need to specify the path in which the file would be saved.
Download by Configuration
By selecting Download by Configuration, you can download the required board software of the boards in position according to the current NodeB configuration. If you do not select the check box, all the board software is downloaded. This step is optional. By selecting Effective Data Configuration File, you can make the downloaded data configuration file take effect.
Effective Data Configuration File
8-28
Issue 05 (2007-09-30)
Element Activate NodeB Software
Description This enables you to download the unpacked software package in the NodeB standby directory to the target boards, and then activate the package. You must reset the NodeB after conducting this operation. If you select Activate NodeB Software, the NodeB software will be activated right after the NodeB software package is downloaded.
l
If you select both Download NodeB Software Package and Activate NodeB Software, the software to be activated is the NodeB software package downloaded from the FTP server. You need not to select the version. If you select Activate NodeB Software without selecting Download NodeB Software Package, the system will list all the NodeB software versions. Select the version to be activated in the active and standby directories from the Version drop-down list.
NOTE
l l
The steps explained in the preceding table are performed in order: Backup Data Configuration File, Download NodeB Software Package, and then Activate NodeB Software. You can choose one or multiple steps 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 8-19. Figure 8-19 FTP Setting dialog box
Table 8-11 describes the elements in the FTP Setting dialog box. Table 8-11 Elements in the FTP Setting dialog box Element Use Built-in FTP Server Description 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.
Issue 05 (2007-09-30)
Element Use Specified FTP Server IP Address
Description The FTP server can either be started from the local computer installed with the LMT application or from another computer. Here it refers to the IP address of the FTP server. This enables you to specify the user name for logging in to the FTP server. This enables you to specify the password for logging in to the FTP server.
User Password
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 to specify a directory for backing up the file. Select Download NodeB Software Package to specify a directory for downloading the NodeB software package.
NOTE
Backup Data Configuration File is optional.
Step 9 Click Next. A dialog box is displayed for your confirmation. Step 10 Click Yes. The Upgrading NodeB Software Progress dialog box is displayed. The status and progress of the procedure are displayed in the dialog box. You can check the procedure by viewing this dialog box.
NOTE
The NodeB file directories are the active directory and the standby directory. Active directory: stores the running NodeB software version. Standby directory: stores the inactive NodeB software version.
----End
8.5.5 Activating the Software of the NodeB

This task describes how to download the software stored in the standby file directory to each board and make it effective. You can activate the NodeB software right after the downloading or later on.
Prerequisite
Context
The NodeB software does not take effect immediately or damage the running software after the download. You can activate the NodeB software to make the new software effective.
Procedure
Step 1 Click the Maintenance tab in the navigation pane.
Step 2 Double-click Software Management > Software Update. The Software Update dialog box is displayed, as shown in Figure 8-20. Figure 8-20 Software Update 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 8-21.
Issue 05 (2007-09-30)
8-31
Figure 8-21 Upgrade NodeB Software dialog box
Table 8-12 describes the elements in the Upgrade NodeB Software dialog box. Table 8-12 Elements in the Upgrade NodeB Software dialog box Element FTP Setting Description This enables you to set the FTP server for downloading files. The FTP server that is in use is shown in the box for your reference. The FTP server can be a built-in server or a userspecified server. To set the FTP server, click Modify on the right side of the element.
8-32
Issue 05 (2007-09-30)
Element Backup Data Configuration File
Description This enables you to upload the configuration file from the NodeB to the FTP server. To specify a path for the file upload, click Browse under Backup Data Configuration File. Select the path to back up the active configuration file in the system. If you have already backed up the file, you can skip this step. In case of upgrade failure, you can reload the backup configuration file in the FTP server to guarantee stable operation of the NodeB.
This enables you to download the data configuration file from the server to the NodeB and overwrite the previous data configuration file. To specify a path for the file download, click Browse. This operation is optional. The data configuration file has a fixed name of NodeBCfg.xml. Therefore, you only need to specify the path in which the file would be saved.
Download NodeB Software Package
This enables you to download the NodeB software package from the FTP server to the NodeB standby directory. Click Browse under Download NodeB Software Package. Select the directory of the package in the FTP server. The system will start the download after backing up the configuration file. This operation is mandatory for NodeB software upgrade. Therefore, you only need to specify the path in which the file would be saved.
Download by Configuration
By selecting Download by Configuration, you can download the required software of all the boards that are in position according to the current NodeB configuration. Otherwise, all the board software is downloaded. This step is optional. By selecting Effective Data Configuration File, you can make the downloaded data configuration file take effect.
Effective Data Configuration File
Issue 05 (2007-09-30)
8-33
Element Activate NodeB Software
Description This enables you to download the unpacked software package in the NodeB standby directory to the target boards, and then activate the package. You must reset the NodeB after conducting this operation. If you select Activate NodeB Software, the NodeB software will be activated right after the NodeB software package is downloaded.
l
If you select both Download NodeB Software Package and Activate NodeB Software, the software to be activated is the NodeB software package downloaded from the FTP server. You need not to select the version. If you select Activate NodeB Software without selecting Download NodeB Software Package, the system will list all the NodeB software versions. Select the version to be activated in the active and standby directories from the Version drop-down list.
NOTE
l l
The steps explained in the preceding table are performed in order: Backup Data Configuration File, Download NodeB Software Package, and then Activate NodeB Software. You can choose one or multiple steps each time and the system proceeds with the task you customize.
Step 5 Select Activate NodeB Software and select the NodeB software version to be upgraded in the Version box.
NOTE
The Version box is displayed only when Download NodeB Software is not selected.
Step 6 Click Next. A dialog box is displayed for your confirmation. Step 7 Click Yes. The Software Update Progress dialog box is displayed. The status and progress of the procedure are displayed in the dialog box. You can check the procedure by viewing this dialog box.
NOTE
l l l
If the activation of a board fails, locate the problem and then activate the software of that board again. For details, refer to Activating the Software of a Board. The NodeB is reset and the new NodeB software version is started when NodeB software is activated. Reactivate the NodeB software version in the standby file directory or reinstall the NodeB software upon activation failure.
----End
8.6 Downloading the NodeB Data Configuration File

This task describes how to download the NodeB data configuration file from the FTP server to the NodeB. The NodeB data configuration file will take effect after the NodeB is reset.
Prerequisite
Procedure
l In GUI mode 1. 2. Click the Maintenance tab in the navigation pane. Double-click Software Management > DataConfig File Transfer. The DataConfig File Transfer dialog box is displayed, as shown in Figure 8-22.
Figure 8-22 DataConfig File Transfer dialog box
Table 8-13 describes the elements in the DataConfig File Transfer dialog box.
Issue 05 (2007-09-30)
8-35
Table 8-13 Elements in the DataConfig File Transfer dialog box Element Para meter Settin g Trans fer Type Description Selecting Upload (NodeB to FTP Server): The system uploads the configuration file of NodeBCfg.xml from the NodeB to the FTP server for viewing, modifying, and saving. In the Compress Flag area, select an option to decide whether to compress the data configuration file or not.
l
Uncompress: The uploaded data configuration file is not compressed. Compress: The uploaded data configuration file is compressed.
Selecting Download (FTP Server to NodeB): The system downloads the configuration file of NodeBCfg.xml from the FTP server to the NodeB. The configuration file of the latest version takes effect after the NodeB is reset.
In the Effective Data Configuration File area, select an option to decide whether to reset the NodeB immediately or not. Resetting the NodeB activates the data configuration file.
l
Reset Promptly: The NodeB is immediately reset and the data configuration file is validated. Reset Later: The NodeB is manually reset later to validate the data configuration file.
Direct ory Name
This enables you to specify the directory for the configuration file in the FTP server. The configuration file has a fixed file name. Therefore, the system can identify it in the directory.
l
If you select Upload (NodeB to FTP Server), it is the destination path. If you select Download (FTP Server to NodeB), it is the source path.
FTP Settin g
This enables you to set the FTP server for downloading the patch. The FTP server that is in use is shown in the box for your reference. Click Modify on the right to set the FTP server.
Trans fer status 3. 4.
Status Progr ess
Active status of the started task of the data configuration file Transfer progress of the data configuration file
Select Download (FTP Server to NodeB) in the Transfer Type area. Click Modify in the dialog box. The FTP Setting dialog box is displayed, as shown in Figure 8-23.
8-36
Issue 05 (2007-09-30)
Figure 8-23 FTP Setting dialog box
Table 8-14 describes the elements in the FTP Setting dialog box. Table 8-14 Elements in the FTP Setting dialog box Element Use Built-in FTP Server Description This enables you to decide whether to use a builtin or a specified FTP server. The built-in FTP server is started by default. The FTP server can either be started from the local computer installed with the LMT application or from another computer. Here it refers to the IP address of the FTP server. This enables you to specify the user name for logging in to the FTP server. This enables you to specify the password for logging in to the FTP server.
Use Specified FTP Server
IP Address
User Password 5. 6. 7. 8. l Set the FTP server.
Click OK. The FTP Setting dialog box is closed and the DataConfig File Transfer dialog box is displayed. Set the other parameters in the dialog box. Click Start. The system starts downloading the data configuration file.
In MML mode To download the data configuration file, run DLD CFGFILE (BTS3812E, BTS3812A, BTS3812AE, BBU3806, and BBU3806C).
----End
8.7 Resetting the NodeB

This task describes how to reset the NodeB. You need to reset the NodeB upon a NodeB failure or after a configuration update.
Prerequisite
Context
CAUTION
Resetting the NodeB interrupts the NodeB services.
Procedure
l In GUI mode Macro NodeB: 1. 2. 3. 4. 5. 6. Click the Maintenance tab in the navigation pane. Double-click Topology Management > Master Cabinet. The device panel interface is displayed. Select the board to be reset. Right-click the board. The shortcut menu is displayed. Click Reset Board. A dialog box is displayed for your confirmation. Click Yes in the dialog box. The LMT displays the result. If the board is reset, the LMT is disconnected from the NodeB. You need to re-log in to the NodeB.
Distributed NodeB: 1. 2. 3. 4. 5. l Click the Maintenance tab in the navigation pane. Double-click Topology Management > RRU Physical Topology. The physical topology is displayed. Right-click the node to be reset. The shortcut menu is displayed. Click Reset Board. A dialog box is displayed for your confirmation. Click Yes in the dialog box. The LMT displays the result. If the board is reset, the LMT is disconnected from the NodeB. You need to re-log in to the NodeB.
In MML mode To reset the NodeB, run RST SYS (BTS3812E, BTS3812A, BTS3812AE, BBU3806, and BBU3806C).
----End
8-38
Issue 05 (2007-09-30)
9 Checking the Connection of the RRU3801C in the Network
Checking the Connection of the RRU3801C in the Network
About This Chapter

This task describes how to check the internal status of the RRU, including link status between RRU and DBS3800 and iDBS3800. 9.1 Checking the Connection Between the RRU3801C and the Macro NodeB This task describes how to check the internal status of the macro NodeB to ensure consistency between actual networking and data configuration. This task also checks the link status between the macro NodeB and the RRU3801C. 9.2 Checking the Internal Status of the DBS3800 This task describes how to check the internal status of the DBS3800. The task checks the consistency between DBS3800 network topology and data configuration, and the link status between BBU3806/BBU3806C and RRU3801C. 9.3 Checking the Internal Status of the iDBS3800 This task describes how to check the status of the iDBS3800. The task checks the consistency between iDBS3800 network topology and data configuration, and the link status between BBU3806 and pRRU3801.
Issue 05 (2007-09-30)
9-1
9.1 Checking the Connection Between the RRU3801C and the Macro NodeB
This task describes how to check the internal status of the macro NodeB to ensure consistency between actual networking and data configuration. This task also checks the link status between the macro NodeB and the RRU3801C. 9.1.1 Checking the Consistency in Connection and Data Configuration Between RRU3801C and Macro NodeB This task describes how to check the macro NodeB and RRU3801C to ensure consistency between hardware installation and data configuration. 9.1.2 Checking the Links Between the Macro NodeB and the RRU3801C This task describes how to check the connection between the macro NodeB and the RRU3801C to rectify the fault caused by improper cable connections.
9.1.1 Checking the Consistency in Connection and Data Configuration Between RRU3801C and Macro NodeB
This task describes how to check the macro NodeB and RRU3801C to ensure consistency between hardware installation and data configuration.
Procedure
Step 1 Use the commands to check whether the macro NodeB data configuration is consistent with the actual hardware installation. The items to be checked include the network topology, quantity, cabinet number, subrack number, slot number, interface board number, and configuration of RRUs.
l
Use the command LST RRUCHAIN (BTS3812E, BTS3812A, BTS3812AE) to check the consistency between hardware installation and data configuration of the RRU3801C. Use the command LST CABINET (BTS3812E, BTS3812A, BTS3812AE) to check the consistency between hardware installation and cabinet configuration of the macro NodeB. Use the command LST SUBRACK (BTS3812E, BTS3812A, BTS3812AE) to check the consistency between hardware installation and subrack configuration of the macro NodeB. Then... End this task.
If... The data configuration and the hardware installation are consistent.
The data configuration and the hardware installation are not consistent. Go to Step 2. Step 2 Check whether the fault is caused by errors in the data configuration or in the hardware with relevant personnel in charge.
9-2
Issue 05 (2007-09-30)
If... The fault occurs in the data configuration. The fault occurs in the hardware installation. ----End
Then... Modify the data configuration. Install the hardware again.
9.1.2 Checking the Links Between the Macro NodeB and the RRU3801C
This task describes how to check the connection between the macro NodeB and the RRU3801C to rectify the fault caused by improper cable connections.
Procedure
Step 1 Use the command DSP RRUCHAINSTATE (BTS3812E, BTS3812A, BTS3812AE) 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... The RRU chain or ring is operational, The RRU chain or ring is faulty, Then... End this task. Go to Step 2.
Step 2 Ensure that the connection between any two devices on the chain or ring hosting RRU3801C is proper. The two devices can be the macro NodeB and RRU3801C or two RRU3801Cs. 1. Ensure that the optical cables are properly connected to the optical ports labeled CPRI_W and CPRI_E in the RRU3801C cabling cavity, and that the LC connectors at both ends of the optical cables are in proper connection. Ensure that the optical cables are properly connected to the optical ports labeled OPT0, OPT1 and OPT2 in the macro NodeB cabling cavity, and that the LC connectors at both ends of the optical cables are in proper connection. Ensure that the RX and TX ends of the optical cables from the macro NodeB are connected to the TX and RX ends of those from the RRU3801C respectively.
2.
3.
For details about the ports and connectors on the RRU3801C, refer to Panel of the RRU3801C. Step 3 Use the command DSP RRUCHAINSTATE (BTS3812E, BTS3812A, BTS3812AE) to ensure that the query result is operational. In the case of abnormality, perform Step 1 to Step 2 again. ----End
9.2 Checking the Internal Status of the DBS3800

This task describes how to check the internal status of the DBS3800. The task checks the consistency between DBS3800 network topology and data configuration, and the link status between BBU3806/BBU3806C and RRU3801C.
1.
9.2.1 Checking the Consistency Between DBS3800 Hardware and Data Configuration This task describes how to check the DBS3800 to ensure the consistency between hardware installation and data configuration. The task consists of checking the RRU3801C, BBU3806, and BBU3806C. 9.2.2 Checking the Link Between the BBU3806/BBU3806C and the RRU3801C This task describes how to check the connection between the macro NodeB and the RRU3801C to rectify the fault caused by improper cable connections.
2.
9.2.1 Checking the Consistency Between DBS3800 Hardware and Data Configuration
This task describes how to check the DBS3800 to ensure the consistency between hardware installation and data configuration. The task consists of checking the RRU3801C, BBU3806, and BBU3806C.
Procedure
Step 1 Use the commands to check whether the DBS3800 data configuration is consistent with the actual 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.
l
Use the command LST RRUCHAIN (, BBU3806, BBU3806C) to check the consistency between hardware installation and network data configuration of the RRU3801C. Use the command LST BBU (BBU3806, BBU3806C) to check the consistency between hardware installation and network data configuration of the BBU3806 and BBU3806C. Then... End this task.
The data configuration and the hardware installation are not consistent. Go to Step 2. Step 2 Check whether the fault is caused by errors in the data configuration or in the hardware with relevant personnel in charge. If... The fault occurs in the data configuration. The fault occurs in the hardware installation. ----End Then... Modify the data configuration. Install the hardware again.
9.2.2 Checking the Link Between the BBU3806/BBU3806C and the RRU3801C
Procedure
Step 1 Run the command DSP RRUCHAINSTATE (BBU3806, BBU3806C) 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... The RRU chain or ring is operational, The RRU chain or ring is faulty, Then... End this task. Go to Step 2.
Step 2 Ensure that the connection between any two devices on the chain or ring hosting the RRU3801C is sound. The two devices can be the BBU3806/BBU3806C and RRU3801C or two RRU3801Cs. 1. Ensure that the optical cables are properly connected to the optical ports labeled CPRI_W and CPRI_E in the RRU3801C cabling cavity, and that the connectors at both ends of the optical cables are in sound condition. Ensure that the optical cables are properly connected to the optical ports labeled CPRI0, CPRI1, or CPRI2 on the BBU3806 and BBU3806C panel, and that the connectors at both ends of the optical cables are in sound condition. Ensure that the optical cables correctly connect the TX and RX ports of the BBU3806/ BBU3806C and the RRU3801C.
2.
3.
For details about the ports and connectors on the RRU3801C, refer to Panel of the RRU3801C. Step 3 Run the command DSP RRUCHAINSTATE (BBU3806, BBU3806C) to ensure that the query result is normal. In the case of abnormality, perform Step 1 to Step 2 again. ----End
9.3 Checking the Internal Status of the iDBS3800

This task describes how to check the status of the iDBS3800. The task checks the consistency between iDBS3800 network topology and data configuration, and the link status between BBU3806 and pRRU3801. 1. 9.3.1 Checking the Consistency Between iDBS3800 Hardware and Data Configuration This task describes how to check the iDBS3800 to ensure the consistency between hardware and data configuration. The task consists of checking the pRRU3801 and checking the BBU3806. 9.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU3801 This task describes how to check the connection between the macro NodeB and the RRU3801C to rectify the fault caused by improper cable connections.
2.
9.3.1 Checking the Consistency Between iDBS3800 Hardware and Data Configuration
This task describes how to check the iDBS3800 to ensure the consistency between hardware and data configuration. The task consists of checking the pRRU3801 and checking the BBU3806.
Procedure
Step 1 Use the commands to check whether the iDBS3800 data configuration is consistent with the hardware. The items to be checked include the network topology, quantity of the iDBS3800s, cabinet number, subrack number, slot number, interface board number, subrack type, and configuration.
l
Use the command LST RRUCHAIN ( BBU3806) to check the consistency between hardware and network data configuration of the pRRU3801. Use the command LST BBU (BBU3806) to check the consistency between hardware installation and network data configuration of the BBU3806. Then... End this task.
The data configuration and the hardware installation are not consistent. Go to Step 2. Step 2 Check whether the fault is caused by errors in the data configuration or in the hardware with relevant personnel in charge. If... The fault occurs in the data configuration. The fault occurs in the hardware installation. ----End Then... Modify the data configuration. Install the hardware again.
9.3.2 Checking the Links Between the BBU3806, RHUB, and pRRU3801
Context
The two modes to connect the BBU3806 and the pRRU3801 are as follows:
l l
The BBU3806 is directly connected to the pRRU3801 with optical ports. The BBU3806 is connected to the pRRU3801 with electrical ports through the RHUB3808.
Procedure
Step 1 Run the command DSP RRUCHAINSTATE (BBU3806) 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.
9-6
Issue 05 (2007-09-30)
If...
Then...
The RRU chain or ring is operational, End this task. The RRU chain or ring is faulty, When the BBU is directly connected to the pRRU, the fault may occur on the connection between BBU3806 and pRRU3801. Go to Step 2 When the BBU is connected to the pRRU through the RHUB, the fault may occur on the connection between pRRU3801 or RHUB3806 and BBU3806. Go to Step 3. Step 2 Ensure that the connection between any two devices on the chain or ring hosting pRRU3801 is proper. 1. Ensure that the optical cables are properly connected to the ports labeled CPRI_W and 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. Ensure that the optical cables are properly connected to the optical ports labeled CPRI0, CPRI1, or CPRI2 on the BBU3806 panel, and that the connectors at both ends of the optical cables are in sound condition. Ensure that the optical cables between the BBU3806 and the pRRU3801 are properly connected to the RX and TX ends of the BBU3806 or pRRU3801.
2.
3.
For details about the panel of the pRRU3801, refer to Panel of the pRRU3801 with Optical Ports . Step 3 Ensure that the connection between any two devices on the chain or ring hosting pRRU3801 is proper. 1. 2. Ensure that the CAT5/6 cables are properly connected to the RJ45 electrical port in the pRRU3801 cabling cavity. Ensure that the optical cables are properly connected to the optical ports labeled CPRI0, CPRI1, or CPRI2 on the BBU3806 panel, and that the connectors at both ends of the optical cables are in sound condition. Ensure that the optical cables are properly connected to the ports labeled CPRI_W and CPRI_E in the RHUB3808 cabling cavity, and that the connectors at both ends of the optical cables are in sound connection. Ensure that the optical cables between the BBU3806 and the RHUB3808 are properly connected to the RX and TX ends of the BBU3806 or pRRU3801. Ensure the Ethernet cable between the RHUB3808 and the pRRU3801 is properly connected to the Ethernet port.
3.
4. 5.
For details about the ports on the RHUB3808 panel, refer to Panel of the RHUB3808. For details about the ports on the pRRU3801 panel, refer to Panel of the pRRU3801 with Electrical Ports . Step 4 Run the command DSP RRUCHAINSTATE ( BBU3806) to query whether the result is normal. In the case of abnormality, go to Step 1. ----End
10 Checking the Running Status of the NodeB
10
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 occurred during working. 10.1 Checking NodeB Transmission This task describes how to check the NodeB transmission. The items to be checked can be selected based on the configuration of the physical layer on the Iub interface. 10.2 Commissioning SNTP This task describes how to commission the 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. 10.3 Handling Alarms During NodeB Commissioning This task describes how to check whether active alarms exist on the NodeB and clear these alarms if any. 10.4 Checking the Status of a Cell This task describes how to check the status of a local cell or a logical cell, acquiring you with the running state of the active cell and enabling you perform OM on the cell. 10.5 Measuring the RTWP This task describes how to measure the RTWP. You can calibrate the gain of uplink RF channels through RTWP measurement. The NodeB RTWP test has no negative effect on the services. 10.6 Monitoring the Output Power of the NodeB This task describes how to monitor the output power of the NodeB. The output power test measures the output power of the MTRU/RRU/pRRU, including: typical output power and output power of each carrier.
Issue 05 (2007-09-30)
10-1
10.1 Checking NodeB Transmission

This task describes how to check the NodeB transmission. The items to be checked can be selected based on the configuration of the physical layer on the Iub interface. 10.1.1 Checking E1/T1 Links This task describes how to check whether the transmission is operational between the RNC and the NodeB when they are connected through E1/T1 links. 10.1.2 Checking STM-1 Links This task describes how to check whether the optical transmission links (STM-1) between the NodeB and the RNC are operational when they are connected through optical cables. 10.1.3 Checking Ethernet Links This task describes how to check whether the transmission links between the NodeB and the RNC are operational when they are connected through the Ethernet.
10.1.1 Checking E1/T1 Links

This task 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 determining whether the end is the E1/T1 RX end or 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.
NOTE
Not all the E1 TX ends can light the LED. When the TX ends on some transmission equipment are disconnected, there is no current received. Therefore, the LED is not lit, which makes the LED fail to distinguish the RX end from the TX end.
Procedure
Step 1 On the NodeB side, ensure that the E1/T1 connectors are in good contact with the Digital Distribution Frame (DDF). Poor jointing may cause poor E1/T1 connection. Step 2 Ensure that the physical connections of the E1/T1 cables are proper. Step 3 On the NodeB side, check whether the actual number of E1/T1 links on the DDF is consistent with the transmission data negotiated between the NodeB and the RNC. If not, modify the data configuration. Step 4 On the NodeB side, perform an E1/T1 physical loopback test as follows: 1. Form a physical loopback between the RNC and the DDF on the NodeB side. In general, for a pair of E1/T1s connecting the NodeB and the RNC on the DDF, 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 C to D, as shown in Figure 10-1. Then a physical loopback is formed between the RNC and the DDF on the NodeB side.
10-2
Figure 10-1 Physical loopback of E1/T1s on the DDF
2. 3. If...
On the RNC side, use the SET E1T1LOP command to set the E1/T1 link mode. On the RNC side, use the LOP E1T1 command to test all the E1/T1 links. Then...
The loopback test succeeds Transmission links between the NodeB and the RNC are operational. The loopback test fails Transmission links between the NodeB and the RNC are faulty. Contact the Huawei engineers to clear the transmission fault.
Step 5 After the loopback test, set the E1/T1s on the DDF to normal connection. Ensure that the connections are sound. ----End
10.1.2 Checking STM-1 Links

This task describes how to check whether the optical transmission links (STM-1) between the NodeB and the RNC are operational when they are connected through optical cables.
Context
When testing the loopback on the optical cable, you must use an optical attenuator if the DBS3800 with an optical module supporting transmission over 40 km is commissioned.
Procedure
Step 1 On the RNC side, connect the TX end to the RX end of the optical fibers. Step 2 On the NodeB side, use the command STR STM1OFFLTST (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to test the error bit rate of fibers. The test lasts for five minutes. If.. The error bit rate is less than 10-10. The error bit rate is greater than or equal to 10-10. Then.. The remote equipment is faulty. The optical fiber is faulty.
Issue 05 (2007-09-30)
10-3
Step 3 On the NodeB LMT, use the command STP STM1OFFLTST (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to stop the test. Step 4 After the test is complete, disconnect the optical fibers on the RNC side. ----End
10.1.3 Checking Ethernet Links

This task 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 Use the command DSP ETHPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check whether the MAC address is consistent with that labeled on the board. If... The two addresses are consistent. The two addresses are not consistent. Then... Replace the board. 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 connected Go to Step 3.
Step 3 Use the command LST ETHPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check whether settings of the Bit Rate and Duplex Mode are correct. Ensure that the Bit Rate is set to 100M and Duplex Mode is set to Full. If... The settings of the Bit Rate and Duplex Mode are not correct The settings of the Bit Rate and Duplex Mode are correct Step 4 Check other Ethernet adapters. Then... Reset the Bit Rate to 100M and Duplex Mode to FULL. Go to Step 4.
10-4
Issue 05 (2007-09-30)
If...
Then...
The transmission is still poor The adapter may be damaged. Replace the associated parts. The network is operational ----End End this task.
10.2 Commissioning SNTP

This task describes how to commission the 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 Simple Network Time Protocol (SNTP) can synchronize the time (year/ month/date/hour/minute/second) in real time between multiple SNTP clients by using a unique SNTP server.
Procedure
Step 1 Start the SNTP server. An SNTP server can be at the RNC or at the M2000 server, which is determined by the actual requirement.
l l
At the RNC: Start the SNTP server on the security and monitor manager on the BAM server. At the M2000 Server: The Sun operating system has the self-contained SNTP services. For details, refer to the M2000 Administration Guide.
Step 2 Use the command SET SNTPCLTPARA (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the parameters of the SNTP client. Parameter SW Name Switch of Time Sync Description Switch of Time Sync Value range: ON (need to be synchronized), OFF (not need to be synchronized) 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 (minute) Value range: 1 to 525600 Unit: minute Default value: none
Step 3 Use the command LST SNTPCLTPARA (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to list SNTP client parameters. If.. The setting is correct. The setting is incorrect. Then.. Go to Step 4. Go to Step 2 to reset parameters.
Step 4 After setting the synchronization period in Step 2, use the command LST SNTPCLTLATESTSUCCDATE (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the time of latest successful synchronization of the SNTP client to the SNTP Server, and whether the synchronization succeeds. If.. Then..
The synchronization succeeds. End this task. The synchronization fails. Check the following:
l l
Whether the SNTP server is started. Whether the IP address of the NodeB is correct.
After the faults are cleared, go to Step 2 to reset parameters. ----End
10.3 Handling Alarms During NodeB Commissioning

This task describes how to check whether active alarms exist on the NodeB and clear these alarms if any.
Prerequisite
Procedure
Step 1 Query active alarms on the NodeB LMT. Step 2 Handle alarms. If... An active alarm exists Then... Clear it according to LMT alarm online help.
An active alarm cannot be cleared Record it in the 16 NodeB Commissioning Data Sheet.
10-6
Issue 05 (2007-09-30)

TIP
For details about clearing an alarm, refer to the NodeB LMT User Guide.
----End
10.4 Checking the Status of a Cell

This task describes how to check the status of a local cell or a logical cell, acquiring you with the running state of the active cell and enabling you perform OM on the cell.
Prerequisite
Procedure
Step 1 Use the command DSP LOCELL (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check the statuses of all local cells and logical cells. Step 2 If a local cell or a logical cell is abnormal, rectify the fault according to related LMT alarm online help. ----End
10.5 Measuring the RTWP

This task describes how to measure the RTWP. You can calibrate the gain of uplink RF channels through RTWP measurement. The NodeB RTWP test has no negative effect on the services.
Prerequisite
Context
The Received Total Wideband Power (RTWP) is the received wideband power in an uplink channel band measured at the UMTS Terrestrial Radio Network Access (UTRAN) access point. Analyses of the RTWP measurement are as follows:
l
If the NodeB is not connected to the antenna and feeder system or a matched load, the RTWP is about 108 dBm. If the NodeB is connected to the antenna and feeder system (with TMA switched on) or a matched load, the RTWP is about 105 dBm. 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 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. When the reported RTWPs are invalid, abnormal RTWP curves are displayed. The RTWPs for the main antenna form a horizontal line at 1120 dBm on the vertical axis. The RTWPs for the diversity antenna form a horizontal line at 1115 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.
Issue 05 (2007-09-30)
10-7
Procedure
Step 1 Click the Maintenance tab in the navigation pane. Step 2 Double-click Realtime Specific Monitoring > RTWP Measurement. The RTWP Measurement dialog box is displayed, as shown in Figure 10-2. Figure 10-2 RTWP Measurement dialog box
Table 10-1 describes the elements in the RTWP Measurement dialog box. Table 10-1 Elements in the RTWP Measurement dialog box Element Subrack No. Description
l
Macro NodeB: subrack number of the MTRU or MRRU Distributed NodeB: subrack number of the RRU Macro NodeB: slot number of the MTRU or MRRU Distributed NodeB: slot number of the RRU
Slot No.
l l
Report Period (s) Text File Name
Expected reporting periods. Unit: second. Value: 1s Name of the .txt file to save the measurement data
Step 3 Set the parameters in the dialog box. Step 4 Click OK. A monitor window is displayed, showing the current monitoring task in graphs. Step 5 Stop the test in one of the following ways: If... Close the monitor window Then... All the displayed monitoring tasks are stopped.
10-8
Issue 05 (2007-09-30)
If...
Then...
Right-click the task in the task list area and The task and its chart are deleted. then click Delete Task on the shortcut menu ----End
10.6 Monitoring the Output Power of the NodeB

This task describes how to monitor the output power of the NodeB. The output power test measures the output power of the MTRU/RRU/pRRU, including: typical output power and output power of each carrier.
Prerequisite
Context
If the test is started, the system reports the typical output power of the MTRU/RRU/pRRU and each carrier every two seconds. Configuration of the MTRU/RRU/pRRU output power depends on the specified services. If the pilot power and typical output power are configured, the difference between the MTRU/RRU/ pRRU output power and the pilot power is not large when the NodeB does not carry services. If the MTRU/RRU/pRRU output power is lower than the pilot power by a large amount, the MTRU/RRU/pRRU output power must be abnormal. Because of the different output powers, the MTRU/RRU/pRRU can be configured with different pilot powers and typical powers.
l l
MTRU/RRU: The pilot power can be 33 dBm and the typical power can be 43 dBm. pRRU: Because the output power is relative small, the pilot power can be 20 dBm and the typical power can be 27 dBm.
Procedure
Step 1 Click the Maintenance tab in the navigation pane. Step 2 Double-click Realtime Specific Monitoring > Output Power Monitoring. The Output Power Monitoring dialog box is displayed, as shown in Figure 10-3.
Issue 05 (2007-09-30)
10-9
Figure 10-3 Output Power Monitoring dialog box
Table 10-2 describes the elements in the Output Power Monitoring dialog box. Table 10-2 Elements in the Output Power Monitoring dialog box Element Cabinet No. Subrack No. Description Default value: Master cabinet
l
Macro NodeB: subrack number of the MTRU or MRRU Distributed NodeB: subrack number of the RRU or pRRU Macro NodeB: slot number of the MTRU or MRRU Distributed NodeB: slot number of the RRU or pRRU
Slot No.
l l
Text File Name
Name of the .txt file to save the measurement data
Step 3 Set the parameters in the dialog box. Step 4 Click OK. A monitor window is displayed, showing the current monitoring task in graphs. Step 5 Stop the test in one of the following ways: If... Close the monitor window Then... All the displayed monitoring tasks are stopped.
Right-click the task in the task list area and The task and its chart are deleted. then click Delete Task on the shortcut menu ----End
10-10
Issue 05 (2007-09-30)
11 Commissioning the Alarm Equipment
11
Commissioning the Alarm Equipment
About This Chapter

This task describes how to commission the alarm equipment, including adding the alarm monitoring equipment, setting external alarms, and checking external alarms. 11.1 Adding the Alarm Equipment This task describes how to add the alarm equipment to monitor the indoor environment index in real time, thus ensuring that the indoor NodeB equipment can work properly. 11.2 Setting the External Alarm This task describes how to set an external alarm. You can set parameters of the external alarm port of the NodeB and the binding between the port and the customized alarm ID. 11.3 Checking the External Alarm This task describes how to check the external alarm, such as to check the setting of the external alarm port.
Issue 05 (2007-09-30)
11-1
11.1 Adding the Alarm Equipment

This task describes how to add the alarm equipment to monitor the indoor environment index in real time, thus ensuring that the indoor NodeB equipment can work properly.
Prerequisite
Before adding the alarm equipment, check whether the NodeB has configured with the alarm equipment. 1. 2. Use the command LST SUBRACK (BTS3812E, BBU3806) to check subrack configuration. Use the command LST BRD (BTS3812E, BBU3806) to check board configuration.
Context
If... The NodeB is configured with the alarm equipment. The NodeB is not configured with the alarm equipment. Then... End this task. Perform the following steps.
Procedure
l Add an EMI. 1. 2. Use the command ADD SUBRACK (BTS3812E, BBU3806) to add a subrack. Set the parameters of the subrack, as listed in Table 11-1. Table 11-1 Parameters of the added subrack Name Cabinet number Subrack number Subrack type 3. 4. 5. Value MASTER 6 EXT
Click , prompting the execution is successful. The setting of the subrack is complete. Use the command ADD BRD (BTS3812E, BBU3806) to add a board. Set the parameters of the board, as listed in Table 11-2. Table 11-2 Parameters of the added board Name Cabinet number Value MASTER
Issue 05 (2007-09-30)
11-2
Name Subrack number Slot number Board type 6. l
Value 6 0 NEMU
Click , prompting the execution is successful. The setting of the board is complete. Use the command ADD BRD (BTS3812E) to add a board. Set the parameters of the board, as listed in Table 11-3. Table 11-3 Parameters of the added board Name Cabinet number Subrack number Slot number Board type Value MASTER 0 16 NMON
Add an NMON. 1. 2.
3. ----End
, prompting the execution is successful. The setting of the board is Click complete.
11.2 Setting the External Alarm

This task describes how to set an external alarm. You can set parameters of the external alarm port of the NodeB and the binding between the 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 and setting of the analog alarm.
Procedure
l Set the Boolean alarm. 1. 2. Use the command SET ALMPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the external alarm port. Set the parameters of the Boolean alarm port, as listed in Table 11-4. Table 11-4 Parameters of the Boolean alarm port Name Cabinet No.
Issue 05 (2007-09-30)
Value MASTER
Name Subrack No.
Value
l l
NEMU: 6 NMON: 0 NEMU: 0 NMON: 16
Slot No.
l l
Port No.
0 to 31
l
NEMU: corresponding to 1 to 32 Boolean inputs and to ports S1+/S1to S32+/S32- for Boolean signals detection of the EMUA NMON: The associated external Boolean alarm input is from 0 to 31. For details, refer to Table 1. Select CUSTOM if configured. Select OFF if not configured.
Work Mode
l l
Port Type Alarm ID 3. l
BOOL 65334 to 65534
Click . The system prompts the execution is successful. The setting of the Boolean alarm port is complete.
NOTE
Set the analog alarm.

If the external ports 32 to 35 are needed, perform the following steps:
1. 2.
Use the command SET ALMPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the external alarm port. Set the parameters of the analog alarm port, as listed in Table 11-5. Table 11-5 Parameters of the analog alarm port Name Cabinet No. Subrack No. Slot No. Port No. Value MASTER 6 0 32 to 35
l
Corresponding to 1 to 4 external analog alarms Corresponding to ports ANA1 to ANA4 of analog signals detection of the EMUA
11-4
Issue 05 (2007-09-30)
Name Work Mode
Value
l l
Select CUSTOM if configured. Select OFF if not configured.
Port Type Alarm ID Upper Alarm Occur Limit Lower Alarm Occur Limit 3. ----End
VALUE 65334 to 65534 Set as required. Set as required.
Click . The system prompts the execution is successful. The setting of the analog alarm port is complete.
11.3 Checking the External Alarm

This task describes how to check the external alarm, such as to check the setting of the external alarm port.
Procedure
Step 1 Use the command LST OUTPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to list the external alarm port status. Step 2 Enter the number of the port of the external alarm to be listed.
NOTE
If the port number is not specified, configuration of all the alarm ports are listed.
Step 3 Click ----End
to output the result.
Issue 05 (2007-09-30)
11-5
12 Commissioning the ALD
12
About This Chapter
Commissioning the ALD
This task describes how to commission the ALD equipment. The task consists of commissioning the RET antenna and commissioning the STMA. 12.1 Commissioning the RET Antenna This task describes how to commission 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. 12.2 Commissioning the STMA This task describes how to commission the STMA to ensure proper working and to adjust the gain of the STMA and the NodeB uplink coverage. The STMA is a part of the antenna system used for amplifying the signals.
Issue 05 (2007-09-30)
12-1
12.1 Commissioning the RET Antenna

This task describes how to commission 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.
Prerequisite
Table 12-1 lists the items you should prepare before RET antenna commissioning. Table 12-1 Items for the RET antenna commissioning Item Vendor code and type of NodeB RET antenna Data configuration file of the RET antenna Description The aim is to download the correct configuration data of the RET antenna.
l
Data configuration of the RET antennas varies from vendor to vendor and from type to type. The NodeB software package contains the data configuration file of the RET antenna.
Downtilt of the RET antenna to be commissioned 1.
The downtilt of the RET antenna is defined in the network planning.
12.1.1 Setting the ALD Power Switch This task 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 the ON state and set the current alarm thresholds. 12.1.2 Adding ALDs This task describes how to add ALDs on the NodeB data when the NodeB to be commissioned supports the RET antenna or the TMA. 12.1.3 Downloading the Data Configuration File of the RET Antenna This task describes how to download the data configuration that maps with the antenna model to enable the RET antenna work properly. 12.1.4 Calibrating the RET Antenna This task describes how to calibrate the tilt of the RET antenna to ensures that all the tilts are correctly set. 12.1.5 Setting the Downtilt of the RET Antenna This task describes how to set the downtilt of the RET antenna. The task affects the antenna coverage. Therefore, the downtilt should be kept consistent with the data in the network planning. 12.1.6 Querying the Current Downtilt of the RET Antenna This task describes how to query the current downtilt of the RET antenna to verify whether the configured downtilt is valid.
2.
3.
4.
5.
6.
12-2
Issue 05 (2007-09-30)
12.1.1 Setting the ALD Power Switch

This task 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 the ON state and set the current alarm thresholds.
Prerequisite
l l
You have logged in to the NodeB LMT. The MAFU of RRU connected to the antenna port works properly.
Procedure
Step 1 Use the command LST SUBRACK (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the subrack number of the MAFU of the RRU3801C.
NOTE
For the macro NodeB without an RRU3801C configured, skip this step. The subrack number of the MAFU of the macro NodeB is permanently 3.
Step 2 Use the command SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the ALD power switch and current alarm thresholds. ----End
12.1.2 Adding ALDs

This task describes how to add ALDs on the NodeB data when the NodeB to be commissioned supports the RET antenna or the TMA.
Prerequisite
Context
l
The ALDs are of the following two types: AISG RET: RET antenna that supports the Antenna Interface Standard Group (AISG) protocol. AISG TMA: TMA that supports the AISG protocol. The AISG TMA is optional, but the AISG RET is mandatory for the RET system. This task is not required if the ALD has been configured in the data configuration file.
l l
Procedure
Use the command ADD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to add an AISG RET or an AISG TMA.
CAUTION
After adding the ALD, wait about one minute for initialization. ----End
12.1.3 Downloading the Data Configuration File of the RET Antenna

This task describes how to download the data configuration that maps with the antenna model to enable the RET antenna work properly.
Prerequisite
l l l l l
The data configuration file of the RET antenna to be commissioned is obtained. You have logged in to the NodeB LMT. The FTP server works properly and connects to the NodeB in the same intranet. There is no firewall between the FTP server and the NodeB. The name and password of the specified FTP server are valid. Ensure that you have the right to read the specified directories. The NodeB software package is downloaded from a specified server.
Context
The data configuration file of the RET antenna is provided by the vendor. Data configuration files vary with antenna models.
Procedure
Step 1 Use the command DLD ALDCFG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to download the data configuration file. Step 2 Repeat Step 1 to download data configuration files for other RET antennas when multiple RET antennas are configured for the NodeB.
NOTE
Ensure that data configuration files are downloaded for all the RET antennas.
----End
12.1.4 Calibrating the RET Antenna

This task describes how to calibrate the tilt of the RET antenna to ensures that all the tilts are correctly set.
Prerequisite
12-4
Issue 05 (2007-09-30)
Context
CAUTION
l
Calibrate the RET after the antenna is installed. Otherwise, the tilt of the antenna and the network coverage may be affected. It takes two to four minutes to calibrate one antenna. It is unnecessary to recalibrate the RET after you reset or power off the RET. You need to set the antenna tilt again after calibrating the RET antenna to ensure the exact tilt of the calibrated RET antenna and the good coverage. For details, refer to 12.1.5 Setting the Downtilt of the RET Antenna.
l l l
Procedure
Step 1 Use the command CLB ANT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to calibrate the antenna. Step 2 Repeat Step 1 to calibrate all the RET antennas when multiple RET antennas are configured.
NOTE
All the RET antennas are required to be calibrated.
----End
12.1.5 Setting the Downtilt of the RET Antenna

This task describes how to set the downtilt of the RET antenna. The task affects the antenna coverage. Therefore, the downtilt should be kept consistent with the data in the network planning.
Prerequisite
Context
CAUTION
l
Ensure that you have added an RET antenna before setting the antenna downtilt. For details, refer to 12.1.2 Adding ALDs. Ensure that you have calibrated the antenna before setting the antenna downtilt. For details, refer to 12.1.4 Calibrating the RET Antenna. It takes two minutes at most to set the RET antenna downtilt.
Issue 05 (2007-09-30)
12-5
Procedure
Step 1 Use the command LST SITE (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to list the site number and name. Step 2 Use the command LST ANTTILTRNG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the antenna downtilt range. Step 3 Use the command SET ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the 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 the data in the network planning.
----End
12.1.6 Querying the Current Downtilt of the RET Antenna

This task describes how to query the current downtilt of the RET antenna to verify whether the configured downtilt is valid.
Prerequisite
l l
You have logged in to the NodeB LMT. The antenna downtilt is correctly set.
Procedure
Step 1 Use the command DSP ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the current antenna downtilt and configured tilt. Step 2 Repeat Step 1 to query current antenna downtilts of other antennas when multiple RET antennas are configured. Step 3 Check whether the current antenna downtilt is consistent with the configured downtilt. If the two downtilts are inconsistent, reset the downtilt. For details, refer to 12.1.5 Setting the Downtilt of the RET Antenna. ----End
12.1.7 MML Commands Related to ALDs

Command ADD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) CLB ANT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) DSP ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C)
12-6 Huawei Technologies Proprietary
Description To add an ALD To calibrate the antenna To query the current antenna downtilt
Issue 05 (2007-09-30)
Command DSP ANTCON (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) DSP ALDDEV(BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) DSP ALDVER (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) DLD ALDCFG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) DLD ALDSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) LST ANTTILTRNG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) LST ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) LST ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) RMV ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) RST ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) RST ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) MOD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) SCN ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) SET ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C)
Description To query the working status of the antenna connector To query the ALD data To query the ALD version To download the RET antenna configuration data file To download the ALD software To query the RET antenna downtilt range
To query the ALD power switch
To query configuration of all the ALDs To delete the ALD To reset the ALD To reset the ALD power switch
To modify the ALD To scan the ALD To set the ALD power switch
To set the current antenna downtilt
12.2 Commissioning the STMA

This task describes how to commission the STMA to ensure proper working and to adjust the gain of the STMA and the NodeB uplink coverage. The STMA is a part of the antenna system used for amplifying the signals.
1.
12.2.1 Setting the ALD Power Switch This task 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 the ON state and set the current alarm thresholds. 12.2.2 Adding ALDs This task describes how to add ALDs on the NodeB data when the NodeB to be commissioned supports the RET antenna or the TMA. 12.2.3 Querying the Gain Range of the STMA This task describes how to query the STMA gain range before setting the STMA gain. The STMA gain range varies with different models and vendors of the STMA. 12.2.4 Setting the Gain of the STMA This task describes how to set the gain of the STMA to balance the amplifying gain of the uplink signals and the uplink coverage. 12.2.5 Querying the Gain of the STMA This task describes how to query the gain of the STMA to check whether the gain is correctly set.
2.
3.
4.
5.
12.2.1 Setting the ALD Power Switch

This task 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 the ON state and set the current alarm thresholds.
Prerequisite
l l
You have logged in to the NodeB LMT. The MAFU of RRU connected to the antenna port works properly.
Procedure
Step 1 Use the command LST SUBRACK (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the subrack number of the MAFU of the RRU3801C.
NOTE
For the macro NodeB without an RRU3801C configured, skip this step. The subrack number of the MAFU of the macro NodeB is permanently 3.
Step 2 Use the command SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the ALD power switch and current alarm thresholds. ----End
12.2.2 Adding ALDs

This task describes how to add ALDs on the NodeB data when the NodeB to be commissioned supports the RET antenna or the TMA.
Prerequisite
Context
l
The ALDs are of the following two types: AISG RET: RET antenna that supports the Antenna Interface Standard Group (AISG) protocol. AISG TMA: TMA that supports the AISG protocol. The AISG TMA is optional, but the AISG RET is mandatory for the RET system. This task is not required if the ALD has been configured in the data configuration file.
l l
Procedure
Use the command ADD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to add an AISG RET or an AISG TMA.
CAUTION
After adding the ALD, wait about one minute for initialization. ----End
12.2.3 Querying the Gain Range of the STMA

This task describes how to query the STMA gain range before setting the STMA gain. The STMA gain range varies with different models and vendors of the STMA.
Prerequisite
Procedure
Step 1 Use the command LST TMAGAINRNG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the gain range supported by the STMA. Step 2 Repeat Step 1 to query the gain range of other STMAs when multiple STMAs are configured. ----End
12.2.4 Setting the Gain of the STMA

This task 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 Use the command SET TMAGAIN (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the STMA gain.
Step 2 Repeat Step 1 to set the gains of other STMAs when multiple STMAs are configured. ----End
12.2.5 Querying the Gain of the STMA

This task describes how to query the gain of the STMA to check whether the gain is correctly set.
Prerequisite
l l
You have logged in to the NodeB LMT. The STMA gain is set.
Procedure
Step 1 Use the command LST TMAGAIN (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the STMA gain. Step 2 Repeat Step 1 to query the gains of other STMAs when multiple STMAs are configured. ----End
12.2.6 MML Commands Related to the STMA

The MML commands related to the STMA can be used to query the gain range, working mode, and gain of the STMA, and to set the gain of the STMA. Command LST TMAGAINRNG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) LST TMAMODE (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) SET TMAGAIN (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) LST TMAGAIN (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) ADD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C)
12-10
Description To query the gain range supported by the STMA
To query the working mode of the STMA
To set the STMA gain
To query the STMA gain
To add an ALD
Issue 05 (2007-09-30)
Command SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) MOD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) RST ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) SET RXATTEN (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C)
Description To set the ALD power switch
To modify the ALD
To reset the ALD
To set the RX attenuation value
Issue 05 (2007-09-30)
12-11
13 Testing NodeB Services
13
Prerequisite
l l l l l
Testing NodeB Services
This task describes how to test NodeB services on the UE to check whether the NodeB can properly provide all types of services.
Two UEs with USIM cards are available. The two UEs under test are registered in the HLR. The RNC works properly. The CS domain and PS domain at the CN work properly. Use the DSP CELL command on the RNC LMT to verify whether all the logical cells of the NodeB on the RNC side are operational. Use the command DSP LOCELL (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) on the NodeB LMT to verify whether all the logical cells of the NodeB on the NodeB side are operational.
Context
Table 13-1 describes basic items in the service dialing test. Table 13-1 Basic items in the service dialing test Item Voice service Method UE calls the local fixed-line telephone. The local fixed-line telephone calls UE. UE1 calls UE2. CS streaming service UE1 initiates video service to UE2. Expectation Voice is clear without obvious noise. Voice is clear without obvious noise. Voice is clear without obvious noise.
l l l
Voice is clear. Video is continuous. Voice and video are synchronous.

13-1
Issue 05 (2007-09-30)
Item PS service
Method UE activates data service and browses web pages.
Expectation Web browsing is operational.
When a NodeB carries multiple logical cells, you should conduct a service test on each logical cell. The following description of the service dialing test is based on the logical cell i.
Procedure
Step 1 On the RNC side, start the single UE tracing. The IMSIs are allocated to the two UEs under test. Step 2 On the NodeB side, start the Iub interface tracing. Step 3 Use the DEA CELL command on the RNC LMT to deactivate all the NodeB logical cells. Step 4 Use the ACT CELL command on the RNC LMT to activate the logical cell i. Step 5 On the RNC side, start the Uu interface tracing of the logical cell i. Step 6 Switch on a UE. Step 7 Observe the WCDMA network auto-search process. If... The search fails Then... For details, refer to 15.5 Failure of the UE to Search the Network.
The search succeeds Go to Step 8. Step 8 Check the DL scramble, Ec/I0, and RSCP of the DL pilot channel.
NOTE
If the UE is not the specified one for test, skip this step.
If...
Then...
The DL scramble matches cell i and the Ec/ For details, refer to Step 9. I0 of the DL pilot channel is greater than 10 dB, or DL pilot RSCP is greater than 95 dBm The DL scramble does not match cell i and the Ec/I0 of the DL pilot channel is less than 10 dB, or DL pilot RSCP is less than 95 dBm The signal coverage is poor. Choose another location with better signal coverage (Ec/I0 > 10 dB) and the DL pilot RSCP greater than 95 dBm to do the test.
Step 9 The UE automatically updates its location. Refer to 15.14 Removal of a Cell After Setup in case of failure. Step 10 The UE calls a local fixed-line telephone. Refer to 15.14 Removal of a Cell After Setup in case of failure.
Step 11 The local fixed-line telephone calls UE. Refer to 15.14 Removal of a Cell After Setup in case of failure. Step 12 UE1 calls UE2. Refer to 15.14 Removal of a Cell After Setup in case of failure. Step 13 UE1 calls UE2 by VP. Refer to 15.14 Removal of a Cell After Setup in case of failure. Step 14 The UE activates data service and browses web pages. Refer to 15.14 Removal of a Cell After Setup in case of failure. Step 15 Repeat steps Step 2 through Step 14 on other logical cells of the NodeB. ----End
Issue 05 (2007-09-30)
13-3
14 Testing NodeB Services on RNC Simulator
14
1.
Testing NodeB Services on RNC Simulator
About This Chapter

This task describes how to test NodeB services on the RNC Simulator in local commissioning (transmission unavailable). Before the test, ensure that all the data is configured and the NodeB works properly. 14.1 Configuring the RNC Simulator This task describes how to configure the RNC Simulator before commissioning. The task consists of the following: configuring the UE, configuring the MTB, and preparing the NodeB configuration file. 14.2 Connecting the RNC Simulator to the NodeB This task describes how to connect the RNC Simulator to the NodeB to enable proper communication between them. 14.3 Logging In to the NodeB on the RNC Simulator The RNC Simulator provides OM channels for the NodeB. When the Ethernet port is unavailable, you can log in to the NodeB through the NodeB OMIP provided by the RNC Simulator. 14.4 Setting Up a Cell on the RNC Simulator This part describes how to manually set up a cell on the RNC Simulator. 14.5 Testing Calls on the RNC Simulator This task describes how to conduct a call test on the RNC Simulator to test the NodeB performance.
2.
3.
4. 5.
Issue 05 (2007-09-30)
14-1
14.1 Configuring the RNC Simulator

This task describes how to configure the RNC Simulator before commissioning. The task consists of the following: configuring the UE, configuring the MTB, and preparing the NodeB configuration file.
Prerequisite
The commissioning of basic NodeB services is complete.
Context
The RNC Simulator consists of a computer and a Magic TBox (MTB). The computer is connected to the MTB through an Ethernet cable. The RNC Simulator is connected to the NodeB through an E1 cable or an optical port.
Procedure
l Configuring the UE 1. Choose Start > All Programs > RNC Simulator > RNC Simulator or double-click LoadCaller_SimRNC.exe under the installation directory of the LoadCaller on the computer. The LoadCaller is started. A window is displayed, as shown in Figure 14-1.
Figure 14-1 Starting LoadCaller
2.
Choose File > Open Project. A dialog box is displayed, as shown in Figure 14-2.
14-2
Issue 05 (2007-09-30)
Figure 14-2 Open Project File dialog box
3.
Open the TestCases folder, and then select a project file in .tpf format, as shown in Figure 14-3. Figure 14-3 Selecting a project file of test.tpf
4.
Open the selected project file in .tpf format. The Configuring UE information dialog box is displayed, as shown in Figure 14-4. Figure 14-4 Configuring UE information dialog box
Issue 05 (2007-09-30)
14-3

NOTE
After the LoadCaller is installed, a project file named test.tpf is generated under the directory by default. You can create a new project with reference to the format of that file or modify that file directly. When opening the project next time, you may choose File > Reopen.
5.
Set parameters in the dialog box shown in Figure 14-4. Set the IMSI, ISDN, KI, and OPC for each UE. The TMSI is not required. Click to save the UE information.
6. l 1.
Configuring the MTB Choose Start > All Programs > RNC Simulator > RNC Simulator or double-click LoadCaller_SimRNC.exe under the LoadCaller installation directory on the computer. Choose File > Config. A dialog box is displayed, as shown in Figure 14-5. Figure 14-5 Configuring IP address of the board dialog box
2.
3.
Click the LoadCtrl tab. Then set the IP address of the MTB in Board IP. The IP address of the MTB and that of the computer must be in the same network segment. Other items may use the default settings. In the dialog box shown in Figure 14-4, change the value of ConfigData IP to the IP address of the MTB.
4. l
Preparing the Data Configuration File Copy the data configuration file to the bin\NodeBConfig directory of the LoadCaller installation directory.
NOTE
Special configuration data, including data on the link layer and transport layer, for the RNC simulator when it is connected to the NodeB is not required.
----End
14.2 Connecting the RNC Simulator to the NodeB

This task describes how to connect the RNC Simulator to the NodeB to enable proper communication between them.
Procedure
Step 1 Connect the computer of the RNC Simulator system to the MTB through an Ethernet cable. Step 2 Turn on the red power switch on the MTB panel, and wait until the MTB starts. Step 3 Start the LoadCaller on the computer and check that all the data is correctly configured. Step 4 Click on the toolbar of the LoadCaller. Wait until the connection between the LoadCaller and the MTB is set up. on the toolbar of the LoadCaller to start the configuration. Step 5 Click The Shell window displays the instructions for connecting the RNC Simulator to the NodeB. For example,
CFG INFO: In Order to Ensure Connect Correct! Please Connect NodeB Side E1 And SimRNC Side E1 According the Following Prompt!" CFG INFO: Connect SimRNC Side No:1 E1 Link To NodeB Side No:3 E1 Link!
The example means that the No.1 E1 cable on the RNC Simulator should be connected to the No.3 E1 cable on the NodeB. Step 6 Connect the RNC Simulator to the NodeB by following the instructions. ----End
14.3 Logging In to the NodeB on the RNC Simulator

The RNC Simulator provides OM channels for the NodeB. When the Ethernet port is unavailable, you can log in to the NodeB through the NodeB OMIP provided by the RNC Simulator.
Prerequisite
The data configured on the NodeB is correct. The IP address of the computer and the peer IP address of the OMIP in the data configuration file are in the same network segment.
Procedure
Step 1 Connect the computer of the RNC Simulator system to the MTB through an Ethernet cable. Step 2 Turn on the red power switch on the MTB panel, and wait until the MTB starts. Step 3 Start the LoadCaller on the computer and check that all the data is correctly configured. ----End
14.4 Setting Up a Cell on the RNC Simulator

This part describes how to manually set up a cell on the RNC Simulator.
Prerequisite
l l
The NodeB has a data configuration file. The RNC Simulator is successfully configured.
Issue 05 (2007-09-30)

l
The RNC Simulator is correctly connected to the NodeB. The bottom layer links are operational.
Context
Setting up a cell on the RNC Simulator is different from setting up a cell on a real RNC. When setting up a cell on the RNC Simulator, you can control the process.
Procedure
Step 1 Click on the toolbar of the LoadCaller to set up a cell.
Step 2 Observe messages in the message tracing window of the LoadCaller when setting up the cell. The cell establishment succeeds when the system displays the following messages:
l
CELL SETUP REQUEST: a setup request message sent from the RNC Simulator to the NodeB CELL SETUP RESPONSE: a setup response message sent from the NodeB to the RNC Simulator
----End
14.5 Testing Calls on the RNC Simulator

This task describes how to conduct a call test on the RNC Simulator to test the NodeB performance.
Prerequisite
l l
Cells have been set up on the RNC simulator. The UE used in the call test has been configured on the RNC Simulator.
Procedure
Step 1 Switch on the UE, and wait until the UE registers its location. Step 2 Call another UE. Check whether the voice is clear. Step 3 Dial a line phone number by the UE, and then check whether you can hear your voice. The voice loopback set up by the RNC Simulator enables you to hear your voice and perform the call test from the UE to the fixed-line phone. ----End
14-6
Issue 05 (2007-09-30)
15 NodeB Commissioning FAQs
15
About This Chapter
NodeB Commissioning FAQs
This part describes the fault symptoms and cause analysis of the NodeB commissioning. 15.1 Faulty Local Connection Between the LMT and the NodeB This part describes the fault symptom and cause analysis of the faulty local connection between the LMT and the NodeB. 15.2 Faulty Remote Connection Between the LMT and the NodeB This part describes the fault symptom and cause analysis of the faulty remote connection between the LMT and the NodeB. 15.3 Failure to Download the NodeB Data Configuration File This part describes the cause analysis of the failure to download the NodeB data configuration file. 15.4 Low Data Rate of PS Data This part describes the fault symptom and cause analysis of the PS data at low data rate. 15.5 Failure of the UE to Search the Network This part describes the fault symptom and cause analysis of the failure of the UE to search the network. 15.6 Failure to Conduct a Dialing Test This part describes the fault symptom and cause analysis of the failure to conduct a dialing test. 15.7 Causes for the ALD Current Abnormal Alarm This part describes the fault symptom, cause analysis, and handling suggestions for the ALD current abnormal alarm. 15.8 ALD Information to Be Collected This part describes how to collect the related information that facilitates fault location when a fault occurs to the ALD. 15.9 Failure to Set the Downtilt of the RET Antenna This part describes the fault symptom, cause analysis, and handling suggestions for the failure to set the tilt of the RET antenna. 15.10 FE Port in DOWN State
This part describes the fault symptom, cause analysis, and handling suggestions for the FE port in DOWN state. 15.11 PPP Link in the DOWN State This part describes the fault symptom, cause analysis, and handling suggestions for the failure of the PPP link in the DOWN state. 15.12 Faulty NCP and CCPs This part describes the fault symptom, cause analysis, and handling suggestions for the faulty NCP and CCPs. 15.13 Faulty E1 Links This part describes the fault symptom, cause analysis, and handling suggestions for the faulty E1 links. 15.14 Removal of a Cell After Setup This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when a cell is removed after setup. 15.15 Repeated Establishment and Removal of the Common Channel After Cell Setup This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when the common channel is repeatedly established and removed after the setup of a cell. 15.16 Removal of the Common Channel Upon Call Initiation This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when the common channel is removed upon call initiation. 15.17 Failure to Activate the HSDPA Service This part describes the fault symptom, cause analysis, and handling suggestions for the failure to activate the HSDPA service. 15.18 Alarms Related to RET/TMA/STMA Links This part describes the fault symptom, cause analysis, and handling suggestions for the alarms related to RET/TMA/STMA links.
15-2
Issue 05 (2007-09-30)
15.1 Faulty Local Connection Between the LMT and the NodeB
This part describes the fault symptom and cause analysis of the faulty local connection between the LMT and the NodeB.
Fault Symptom
You can neither locally log in to the NodeB LMT nor find the NodeB using the ping command.
Analysis
When there is a faulty connection between the LMT and the NodeB at the local end, the cause may be either of the following:
l l
Faulty crossover Ethernet cable Wrong IP address settings of the LMT PC
15.2 Faulty Remote Connection Between the LMT and the NodeB
This part describes the fault symptom and cause analysis of the faulty remote connection between the LMT and the NodeB.
Fault Symptom
You can neither remotely log in to the NodeB on the LMT nor find the NodeB by using the ping command.
Analysis
When there is a faulty remote connection between the LMT and the NodeB, the cause may be either of the following:
l l l
Commands for setting the routes are incorrect. OMIP settings of the NodeB are incorrect. The IP address of the LMT PC under commissioning and the peer IP address of the NodeB OMIP are not in the same network segment. Communication between the communication gateway and the NodeB is faulty.
15.3 Failure to Download the NodeB Data Configuration File

This part 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
When the system fails to download the NodeB data configuration file, the cause may be either of the following:
l
The length of the path to the NodeB data configuration file exceeds the stipulated bytes which should be of 230 bytes. The current software version is not consistent with the current data configuration file.
15.4 Low Data Rate of PS Data

This part describes the fault symptom and cause analysis of the PS data at low data rate.
Fault Symptom
In the service dialing test, data in the PS domain of the newly added NodeB is at low rate and bit error rate of the Iub interface is high.
Analysis
The cause may be one of the following:
l l l l
The data configuration is inconsistently negotiated. The FTP service of the upper-layer RAN works improperly. The cell signal presents too low. The capability of the UE is restricted.
15.5 Failure of the UE to Search the Network

This part describes the fault symptom and cause analysis of the failure of the UE to search the network.
Fault Symptom
The UE fails to search the network.
Analysis
When the UE fails to search the network, the causes may be either of the following:
l
Weak DL signals. The DL pilot channel Ec/I0 is less than 10 dB and the RSCP of the DL pilot channel is less than 90 dBm. The DL scramble searched by the UE is not the scramble of the testing cell. Therefore, the UE is unable to find the cell. Strong DL interference. The DL pilot channel Ec/I0 is less than 10 dB but the RSCP of the DL pilot channel is greater than 90 dBm. Therefore, the UE is unable to find the cell or receive the correct DL system messages.
15-4

l
Small cell radius.

NOTE
Pay special attention to the local cell output power and the radio network coverage when the UE fails to search the network.
15.6 Failure to Conduct a Dialing Test

This part describes the fault symptom and cause analysis of the failure to conduct a dialing test.
Fault Symptom
Service dialing failure may occur in location update or service dialing test.
l l
Location update failure Service dialing test failure
Analysis
When the dialing test fails, the cause may be either of the following:
l
UE faults such as lack of the USIM card, and authentication encryption not supported by the USIM card. In this situation, replace the UE with a new one. The UE under test is not registered on the HLR at the CN side, or the registration is incorrect. In this situation, register the UE under test correctly. The CS domain or PS domain is not ready. In this situation, get CS domain and PS domain ready.
15.7 Causes for the ALD Current Abnormal Alarm

This part describes the fault symptom, cause analysis, and handling suggestions for the ALD current abnormal alarm.
Fault Symptom
The system reports the alarm of ALD current abnormality. The ALD power switch is automatically disabled and can be enabled only through manual operation.
Analysis
The cause of the alarm may be either of the following:
l l
Overcurrent Undercurrent
Handling Suggestions
1. Use the command DSP ANTCON (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check the following information:
Issue 05 (2007-09-30)

l l l
Operating status of the ALD power switch Existing current value Configured overcurrent alarm threshold If the fault is caused by undercurrent, infer that the connection of ALDs may be poor. Check the cables, and then restore the ALD power switch to the configured state by using the command RST ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C). If the fault is caused by overcurrent, infer that the configured current threshold cannot meet the requirement. Reconfigure the threshold by using the command SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C).
2.
Locate the cause of the alarm according to the above information.

l
15.8 ALD Information to Be Collected

This part describes how to collect the related information that facilitates fault location when a fault occurs to the ALD. When a fault occurs to the ALD, determine what information should be collected as shown in Table 15-1. Table 15-1 Information to be collected and the handling suggestion when a fault occurs to the ALD Information Manufacturer and serial number of the ALD Suggestion
l
Use the command SCN ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to obtain the information. Copy the information from the silk screen.
ALD model ALD version number
Copy the information from the silk screen. Use the command DSP ALDVER (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to obtain the information. Use the command LST ANTTILTRNG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to obtain the information.
Antenna tilt range
15.9 Failure to Set the Downtilt of the RET Antenna

This part describes the fault symptom, cause analysis, and handling suggestions for the failure to set the tilt of the RET antenna.
15-6
Issue 05 (2007-09-30)
Fault Symptom
You can reset, scan, or calibrate the NodeB RET antenna, but you cannot set or query the tilt of the RET antenna.
Analysis
The cause may be one of the following:
l l l l
The tilt of the RET antenna is beyond the threshold. The RCU is faulty. Sector information is not matched. The configuration file to record the relation between the movement of the RCU and the tilt of the RET antenna fails to be configured.
1. Ensure that the following information is correct:
l l l
The tilt of the RET antenna is within the threshold. The RET antenna can be calibrated and the RCU works properly. Relevant sets of sector information correspond to each other.
2.
Check whether correct configuration files are downloaded.
Example
The following description is based on the RET antenna of the BTS3812E.
l
Use the command SET ALDPWRSW (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to enable the ALD switch and then set the overcurrent threshold. Use the command ADD ALD (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to add the ALD. After adding the ALD, wait about 10 s to 20 s for initialization. Use the command DLD ALDCFG (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to download the ALD switch configuration file Use the command CLB ANT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to calibrate the antenna. Use the command SET ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to set the antenna tilt. Use the command DSP ANTTILT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to query the antenna tilt.
15.10 FE Port in DOWN State

This part describes the fault symptom, cause analysis, and handling suggestions for the FE port in DOWN state.
Fault Symptom
The FE port is unable to be up. Check the port and find that the port is in DOWN state. All the LEDs for the port are OFF.
Analysis
When the FE port is in DOWN state, the cause may be one of the following:
l l l l
Incorrect settings of the rate and duplex mode of the FE ports Poor or faulty connection of the Ethernet cables Faulty board or incorrect setting of the MAC address Faulty FE port
1. Use the command LST ETHPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check whether the settings of the rate and duplex mode are correct. Ensure that the rate and duplex mode are set to 100 M/bits and FULL respectively. Check the connection of the Ethernet cables. If the Ethernet cables are not connected to the ports, connect the cables and check whether the fault is rectified. Use the command DSP ETHPORT (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) to check the MAC address. That is, to check whether the MAC address is consistent with that labeled on the board. If they are inconsistent, replace the board. Connect the cable to the other Ethernet port. If the fault persists, the port may be damaged. Replace the faulty board with a new one.
2. 3.
4.
15.11 PPP Link in the DOWN State

This part describes the fault symptom, cause analysis, and handling suggestions for the failure of the PPP link in the DOWN state.
Fault Symptom
The PPP link is in the DOWN state and no IP address is obtained.
Analysis
When the PPP link is in the DOWN state, the cause may be either of the following:
l l
Poor connection of the E1 cable Incorrect settings of the PPP link
1. 2. 3. Check the status of the E1 cable. Ensure that the E1 cable is properly connected. Check the settings of the PPP link, E1 port number, and timeslot. Ensure that their settings are correct. Check whether the peer settings are consistent with the negotiated data.
15.12 Faulty NCP and CCPs

This part describes the fault symptom, cause analysis, and handling suggestions for the faulty NCP and CCPs.
Fault Symptom
Connection of the NCP/CCPs is faulty.
Analysis
When the NCP and CCPs are faulty, the cause may be either of the following:
l l
Communication of the IP transport network is faulty. Configurations of the negotiated data at both sides are inconsistent.
1. Check whether the signaling address of the RNC can be pinged on the NodeB LMT. If the signaling address of the RNC cannot be pinged, 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. If the fault still persists, check the transmission status.
l
2.
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 15.10 FE Port in DOWN State . When the E1/T1 cables are applied to the networking on the NodeB, alarms are generated. Then, check the transmission status. For details, refer to the related online help for corresponding alarms.
3.
If the signaling address of the RNC can be pinged, 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. 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, download a valid data configuration file onto the NodeB, reset the NodeB, and then configure the file correctly.
4.
15.13 Faulty E1 Links

This part describes the fault symptom, cause analysis, and handling suggestions for the faulty E1 links.
Fault Symptom
When logical cells and all the links of the upper layers are available, if you use the command DSP E1T1 on the RNC side, the E1/T1 link is available. If you use this command on the NodeB side, the E1/T1 link is in Abnormal state. In a loopback, if you use the command DSP E1T1 (BTS3812E, BTS3812A, BTS3812AE, BBU3806, BBU3806C) on the NodeB side, the E1 link changes to the link in loop state. When the loop mode is changed to the No Loop state, the E1 link changes to Normal for a moment, but soon back to Abnormal.
Analysis
When the E1 links are faulty, the cause may be one of the following:

l l l
Wrong ATM traffic configuration Poor physical connection of cables Wrong setting of the E1/T1 mode
1. 2. 3. Check the transmission channels to ensure that all the transmission channels are available. Check the physical connection of the cables to ensure that the connection is sound and all the links are available. Check the E1/T1 mode. When the E1/T1 cable on the NodeB side is set to the double-frame mode while that on the RNC side is set to the multi-mode, the E1/T1 link on the NodeB side is displayed as Abnormal, but the E1 link is still available on the RNC side.
Summary of Suggestions
Although the default setting is multi-mode, check the setting of the E1/T1 mode when the fault occurs.
15.14 Removal of a Cell After Setup

This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when a cell is removed after setup.
Fault Symptom
A cell cannot be set up. It is found through the Iub interface tracing that a cell is removed after setup. The RNC reports that a common channel fails to be established, but the message is not found on the Iub interface.
Analysis
The bandwidth is insufficient.
1. 2. Deactivate and activate the cell on the RNC side to check whether the cell is restored. 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. If the fault is not cleared after the IP path bandwidth is modified, keep tracing the results by using the debug terminal on the RNC side to find the causes of the fault.
3.
15-10
Issue 05 (2007-09-30)
15.15 Repeated Establishment and Removal of the Common Channel After Cell Setup
This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when the common channel is repeatedly established and removed after the setup of a cell.
Fault Symptom
After a cell is set up, the common channels are removed. The results on the RNC side show that the common channels fail to be synchronized.
Analysis
The fault is mainly caused by poor communication on the user plane or mass packet loss.
1. 2. Ensure that a route is added to the address of the RNC user plane configured on the NodeB side. If the route for the equipment of the network is wrong, modify the route configurations. If the fault persists, check the request and response for establishing common channel on the Iub interface, and then check whether the tla IP address in the protocol is correct.
l
If the IP address of the RNC request is not correct, modify the IP address of the IP path on the RNC side. If the IP address of the NodeB response is not correct, modify the IP address of the IP path on the NodeB side and reset the NodeB.
15.16 Removal of the Common Channel Upon Call Initiation

This part describes the fault symptom, cause analysis, and handling suggestions for the failure that occurs when the common channel is removed upon call initiation.
Fault Symptom
When the network is connected through FE ports, the cells are successfully set up. However, either of the following cases may occur:
l
Common channels are removed after a call is initiated. This results in the failure in communication. Common channels are removed periodically. This results in the disconnection of activated services.
Analysis
The fault is mainly caused by the connection quality on the user plane.
1. 2. 3. Check the route configurations. Ensure that the IP address can be pinged. If the common channels are successfully established, the IP path is operational. Check the configuration and the status of the FE ports. Insufficient bandwidth may cause the congestion, which results in low packet transmission rate or packet loss and even removal of the common channels.
Solutions
Modify the LR configurations and set the bandwidth for the port to the physical bandwidth.
15.17 Failure to Activate the HSDPA Service

This part 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.
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. Check whether the HSDPA-NRT IP path is configured on the RNC side. Ensure that the bandwidth of the IP path is large enough. Otherwise, the IP path may be not available. After the configuration, re-activate the cell. If the cell cannot be re-activated, trace the signaling over the Uu interface and analyze the cause of the fault. If the maximum rate of the USIM card registered in the HLR is set to 384 kbit/s or less, the HSDPA service may not be activated. Only the service of 384 kbit/s can be activated.
2.
3. 4.
Solutions
Modify the configurations of the HSDPA services on the RNC side and on the NodeB side. Modify the configurations of the HSDPA IP path.
15.18 Alarms Related to RET/TMA/STMA Links

This part describes the fault symptom, cause analysis, and handling suggestions for the alarms related to RET/TMA/STMA links.
Fault Symptom
The system reports the alarm of communication abnormality of RET/TMA/STMA.
Analysis
The alarm may be caused by the broken ALD link.
l
To clear the alarm on the macro NodeB, you can use any of the following methods: 1. 2. 3. Reset the MAFU. Reset the NMON. Use the command RST ALD (BTS3812E, BTS3812A, BTS3812AE) to reset the ALD.
NOTE
It is recommended that you use method 3 which does not interrupt services.
l
To clear the alarm on the distributed NodeB, you can use either of the following methods: 1. 2. Reset the RRU3801C. Use the command RST ALD (BBU3806, BBU3806C) to reset the ALD.
NOTE
It is recommended that you use method 2 which does not interrupt services.
Issue 05 (2007-09-30)
15-13
16 NodeB Commissioning Data Sheet
16
NodeB Commissioning Data Sheet
NodeB commissioning data sheet is used to record the process and result of the commissioning. Table 16-1 NodeB Commissioning Data Sheet Site Name NodeB Model Date & Time Commissioning Engineers Commissioning Mode Commissioning Result Item Local commissioning (transmission available) Local commissioning (transmission unavailable) Remote commissioning Successful Failed Conclusion Handling Exceptional Cases
NodeB commissioning preparation
Faults in NodeB hardware installation are rectified. Transmission links between NodeB and RNC are ready. Configuration data for NodeB is added to the RNC. NodeB data configuration file is downloaded. Local IP address in NodeB data configuration file is configured.
Issue 05 (2007-09-30)
16-1
Item
Conclusion
Handling Exceptional Cases
Local commissioning (transmission available)
Checking compatibility of NodeB software versions Upgrading BootROM Upgrading NodeB software Downloading NodeB data configuration files Commissioning transmission by using the NDTI Commissioning transmission by using NUTI Commissioning SNTP Handling alarms Checking cell status Measuring RTWP Testing output power of MTRU or RRU3801C Testing services Notifying the M2000 administrator
Local commissioning (transmission unavailable)
Checking compatibility of NodeB software versions Upgrading BootROM Upgrading NodeB software Downloading NodeB data configuration files Commissioning SNTP Handling alarms Checking cell status Setting Up a Cell on the RNC Simulator Testing Calls on the RNC Simulator
16-2
Issue 05 (2007-09-30)
Notifying the M2000 administrator Remote commissioning Checking compatibility of NodeB software versions Upgrading BootROM Upgrading NodeB software Downloading NodeB data configuration files Checking transmission links between RNC and macro NodeB Checking transmission links between RNC and distributed NodeB Commissioning SNTP Handling alarms Checking cell status Measuring RTWP Testing output power of MTRU or RRU3801C Notifying the M2000 administrator
Remaining problems Remaining problems during commissioning
Impact
Issue 05 (2007-09-30)
16-3
Index
Index
Issue 05 (2007-09-30)
i-1

Edvdv Node B Commissio Ning Gui de

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Edvdv Node B Commissio Ning Gui de

Transféré par

Droits d'auteur :

Formats disponibles

NodeB V100R008

Issue Date Part Number

Huawei Technologies Proprietary

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Technologies Proprietary

NodeB Commissioning Guide

4 Locally Commissioning the NodeB (Transmission Unavailable)....................................4-1

5 Remotely Commissioning the NodeB....................................................................................5-1

6 Checking the DIP Switches Settings of the NodeB.............................................................6-1

7 Powering On the NodeB...........................................................................................................7-1

9 Checking the Connection of the RRU3801C in the Network............................................9-1

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

11 Commissioning the Alarm Equipment..............................................................................11-1

12 Commissioning the ALD......................................................................................................12-1

NodeB Commissioning Guide

13 Testing NodeB Services .......................................................................................................13-1 14 Testing NodeB Services on RNC Simulator.....................................................................14-1

15 NodeB Commissioning FAQs..............................................................................................15-1

16 NodeB Commissioning Data Sheet....................................................................................16-1

NodeB Commissioning Guide

Huawei Technologies Proprietary

NodeB Commissioning Guide

NodeB Commissioning Guide Figure 14-3 Selecting a project file of test.tpf.................................................................................................14-3

Huawei Technologies Proprietary

NodeB Commissioning Guide

Huawei Technologies Proprietary

NodeB Commissioning Guide

About This Document

About This Document

This document is intended for field engineers.

About This Document

NodeB Commissioning Guide

NodeB Commissioning Guide

About This Document

About This Document

NodeB Commissioning Guide

Huawei Technologies Proprietary

NodeB Commissioning Guide

About This Document

Huawei Technologies Proprietary

NodeB Commissioning Guide

1 NodeB Commissioning Resources

NodeB Commissioning Resources

For details, refer to Table 1. Ethernet adapters

Requirements for the operating system:

Requirements for the software:

Connect the computer to the NodeB.

1 NodeB Commissioning Resources

NodeB Commissioning Guide

Tools Light Emitting Diode (LED) (optional)

UE under test (including a SIM card)

Requirements for the UE under test:

Locally Commissioning the NodeB (Transmission Unavailable)

Data Configuration File

NodeB Commissioning Guide

1 NodeB Commissioning Resources

Huawei Technologies Proprietary

NodeB Commissioning Guide

2 NodeB Commissioning Scenarios

NodeB Commissioning Scenarios

Remotely Commissioning the NodeB

Huawei Technologies Proprietary

NodeB Commissioning Guide