NodeB Local Commissioning

0NodeB Local Commissioning
NodeB Local Commissioning
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.
Page*
Foreword
Understand the installation steps of the NodeB cabinet, boards, modules and cables.
Describes the procedures for local commissioning and verifying the NodeB after it is installed. The commissioning and verification procedures ensure that the Nodeb operates as required
Page*
NodeB Overview
The 3900 series base stations are classified into macro base stations and distributed base stations. These base stations are used in different scenarios to meet operators' requirement for fast network deployment with low cost.
Macro base stations:
Indoor: BTS3900, BTS3900L
The 3900 series base stations have a modular structure.
The basic modules of the 3900 series base stations are the Base Band Unit (BBU), Radio Frequency Unit (RFU), and Remote Radio Unit (RRU). To meet the requirements for radio network deployment, the BBU and RFU/RRU are connected through a CPRI port that uses an electrical or optical cable to transmit CPRI signals.
P-*
Page*
Commissioning Resources
Before commissioning, you need to ensure that the required tools are available, obtain the information about the base station to be commissioned, and download the correct software for boards used in the base station
Tools: PC, Multimeter, Power Meter, Site Master, Ethernet cable, Serial port cable, Flat-head screwdriver, Light emitting diode (LED)
Site Information
Before commissioning, you must obtain the following basic information about the site Information on the networking and related configuration of the base station, including the base station type, transmission mode, networking mode, and cell configuration.
Base station data configured on the base station controller.
Board Information
Before commissioning, you need to download the related board software onto the PC. In the case that the commissioning is performed by using the USB disk, you need to download the software onto the USB disk in advance.
P-*
Page*
The NodeB hardware is installed and the cables are connected.
The NodeB has passed the hardware installation check before it is powered on.
The NodeB is powered on, and the boards operate normally as indicated by the LEDs on the boards.
The NodeB is installed. The system commissioning is completed, and the system is operating properly.
Software Requirements
Page*
Remote Commissioning Modes
Local LMT Commissioning
The upgrade of the NodeB software and configuration data can be implemented on the LMT on the site. Then, you can check the status and handle the alarms through LMT.
Page*
LMT Commissioning Scenarios
When transmission is unavailable, we can perform the on-site commissioning of the NodeB on the LMT. You can upgrade the software, download the data configuration file, and check the running status of the NodeB on the NodeB LMT
Page*
The configuration file on the LMT
Check the running status of the NodeB
Do the software and configurations
need to be upgraded?
Export the Commissioning Report
Checking External Environment Alarms
Page*
Page*
Logging in to NodeB with NodeB local IP address
The default password for NodeB is “NodeB”.
Proxy function is used to log in to the NodeB through M2000 or other proxy, M2000 server IP could be filled in Proxy server.
P-*
Page*
Page*
P-*
Page*
Page*
P-*
Page*
Page*
P-*
Page*
Page*
P-*
Page*
Page*
P-*
Page*
Page*
Checking Software Version of NodeB
Checking the current software version of the boards and modules of the NodeB by command LST VER
If The NodeB version doesn’t match, we need to upgrade the NodeB to the right version
Upgrading the NodeB Software and Downloading the Data Configuration File
P-*
Page*
Page*
Upgrading the NodeB Software and Downloading the Data Configuration File(Cont.)
Upgrade the NodeB
NodeB software
NodeB Program : Software.csp
Version file for each board of NodeB.
For NodeB software, Software is mandatory to upgrade, the BootROM is optional. For some versions, the new software file is compatible with old BootROM, and there is no new BootROM file in the new version folder, so it’s no need to upgrade the BootROM. If there is new BootROM file in the new version folder which means the new software file is not compatible with old BootROM file, we must upgrade the BootROM also.
P-*
Upgrade the NodeB BootROM
Confidential Information of Huawei. No Spreading Without Permission
Click the Maintenance tab in the navigation tree.
Choose Software Management > Update BootROM. The Update BootROM dialog box is displayed.Choose the directory where you store the version file, then click “Next” to download the new BootROM from laptop to NodeB.
If you click the “Activate BootROM”, the BootROM will be activated automatically after downloading.
Activating the BootROM does not reset the NodeB.
After you log in to the NodeB LMT by online mode, the SFTPServer is started up automatically. You’ll see in your windows tool bar. And the setting is done by system. Double-click the icon to check the detailed setting.
P-*
Page*
Page*
Upgrade the NodeB Software and Downloading Data Configuration File
Click the Maintenance tab in the navigation tree.
Choose Software Management > Software Update. The Software Update dialog box is displayed.
Select Upgrade NodeB Software in the dialog box. Click Next. The Update NodeB Software dialog box is displayed.
Select Downloading the Data Configuration File, Download NodeB Software Package, Download by Configuration, Effective Data Configuration File, and Activate NodeB Software in sequence, and set the directory for downloading the data configuration file and NodeB software package.
“Backup Data Configuration File” is used in case the new version or new configuration file is not working normally, we could downgrade the version back with old data configuration file.
“Downloading the Data Configuration File” is used to download the new configuration file to NodeB in case the old configuration file is not working normally with new NodeB version.
“Download NodeB Software Package” is used to download the new NodeB software file from laptop to NodeB.
“Download by Configuration” means only the new software of boards which have been configured in NodeB will be downloaded to NodeB. For example: If there is no UTRP board configured in NodeB now, the new UTRP board software will not be downloaded. If you install UTRP board with older version in this NodeB after NodeB upgrading, the UTRP board can not get the new software version from new NodeB software package. You have to upgrade the UTRP board software version again.
Effective data configuration file will cause the NodeB reset, so is Activate NodeB software. The NodeB will reset automatically after either or both of there two options is clicked.
P-*
Page*
Page*
Checking the Consistency Between Hardware Installation and Data Configuration of NodeB
In the NodeB LMT window, click the Device Panel tab to check the board configuration of the NodeB
Checking the operating status of the boards according to the board color
The green color indicates that the board operates normally. The red color indicates that the board is faulty, and an alarm related to the board exists.
P-*
Page*
Page*
Commissioning SNTP
Run the SET SNTPCLTPARA command to set the parameters of the SNTP client
Run the LST SNTPCLTPARA command to check the parameters of the SNTP client
P-*
Page*
Page*
Commissioning SNTP
Run the LST LATESTSUCCDATE command to query the time of latest successful synchronization of the SNTP client to the SNTP server, and whether the synchronization is successful
If...
Then...
The synchronization fails
Check the following items: Whether the SNTP server is running . Whether the IP address of the NodeB is correct. After the faults are rectified, set the parameters again.
The synchronization is successful
P-*
Page*
Checking the Status of a Cell
Run the DSP LOCELL command to check the status of all local and logical cells of the NodeB.
If...
Then...
Rectify the faults according to the information.
No information prompting faults is displayed
End the task.
Checking the Running Status of the NodeB(Cont.)
Measuring the RTWP
In the navigation tree of the Local Maintenance Terminal window, click the Maintenance tab.
Choose Realtime Specific Monitoring > Board RTWP. The Board RTWP dialog box is displayed, as shown in the figure.
Set the parameters in the dialog box.
Click OK. A window is displayed, showing the current monitoring task in graph.
To stop this test task, use either of the following methods:
Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed in the window.
Method 2: Right-click the task on the monitoring task list and choose Delete Task from the shortcut menu. The curve displayed for the task is deleted together with the task.
NOTE:
One RF module can be configured with one to four carriers. The system outputs the RTWP value of the corresponding carrier based on the actual configuration.
One carrier may be configured with main and diversity RX.
P-*
Checking the Running Status of the NodeB(Cont.)
Monitoring the Output Power of the NodeB
Page*
In the navigation tree of the Local Maintenance Terminal window, click the Maintenance tab.
Choose Realtime Specific Monitoring > Output Power Monitoring. The Output Power Monitoring dialog box is displayed, as shown in the figure.
Set the parameters in the dialog box.
Click OK. A window is displayed, showing the current monitoring task in graph.
To stop this test task, use either of the following methods:
Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed in the window.
Method 2: Right-click the task on the monitoring task list and choose Delete Task from the shortcut menu. The curve displayed for the task is deleted together with the task.
Result
The table monitoring items for the NodeB output power measurement
P-*
Carrier Output Power(Channel No: X; Carrier No: Y; Unit: 0.1dBm)
Indicates the output power of Y carrier in X channel.
Channel Output Power(Channel No: X; Unit: 0.1dBm)
Indicates the typical output power in X channel corresponding to the RF module.
Page*
Page*
Handling NodeB Alarms
Clicking Alarm in the NodeB LMT window, and the Browse Alarm tab page is displayed in the NodeB Alarm window
Clear the alarms related to the NodeB
If...
Then...
Clear the alarm based on the alarm online help.
An active alarm related to the NodeB cannot be cleared.
Record it in Data Sheet for NodeB Commissioning.
P-*
Page*
Run the STR VSWRTEST command to check the NodeB VSWR
Context
An excessively large VSWR results in short transmission distance, thus affecting the normal operation of the communication system. The normal VSWR ranges from 1 to 1.8. The VSWR less than 1.5 is preferred.
Postrequisites
Check that the antenna system is correctly installed based on the checked VSWR.
Ensure the NodeB services are resumed.
CAUTION: During testing of the VSWR, the services of the NodeB are interrupted. Therefore, you are advised to test the VSWR when the service volume is light or after the NodeB services are isolated.
P-*
Setting the Maximum Output Power of RRU or RFU
Run LOC RRUTC set the maximum output power of the RRU or RFU
Page*
Run the DSP RRU command to query the cabinet/subrack/slot number, TX channel number, and maximum output power of the RRU or RFU.
Run the LOC RRUTC command to set the maximum output power of the RRU or RFU.
Run the RST BRD command to reset the RRU or RFU.
Run the DSP TXBRANCH command to check that the maximum output power of each RRU or RFU is set successfully.
P-*
Page*
Page*
Checking External Environment Alarms
Run the LST ALMPORT command to query the status of external alarm ports
Check the external alarm settings according to the query result
Check that the reported alarm is consistent with the configured external alarm
P-*

Documents

NodeB Local Commissioning