Troubleshooting Ultra Site and Metro Site Base Station

Troubleshooting UltraSite and MetroSite WCDMA Base Station

DN70558202

Issue 01DApproval Date 2010-04-23

2 DN70558202Issue 01D

Troubleshooting UltraSite and MetroSite WCDMABase Station

Id:0900d805807389a4

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN70558202Issue 01D

3


Id:0900d805807389a4

Table of ContentsThis document has 116 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Troubleshooting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Troubleshooting UltraSite and MetroSite WCDMA BTS . . . . . . . . . . . . 112.1 Accessing WCDMA BTS Site Manager connection. . . . . . . . . . . . . . . . 112.2 Checking PC firewall settings in Windows XP . . . . . . . . . . . . . . . . . . . . 122.3 Checking BTS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4 Checking BTS SW versions and SW download. . . . . . . . . . . . . . . . . . . 142.5 Checking the BTS commissioning file . . . . . . . . . . . . . . . . . . . . . . . . . . 152.6 Running a WCDMA loop test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.7 Analysis of the WCDMA loop test report . . . . . . . . . . . . . . . . . . . . . . . . 222.8 ATM-related problems in the Iub interface. . . . . . . . . . . . . . . . . . . . . . . 272.9 Checking ATM-related problems remotely and before a site visit . . . . . 282.10 Checking ATM-related problems at a BTS site . . . . . . . . . . . . . . . . . . . 302.11 Checking units, cables and connectors . . . . . . . . . . . . . . . . . . . . . . . . . 312.12 Installing plug-in units and front cabling. . . . . . . . . . . . . . . . . . . . . . . . . 322.13 Hot inserting WSPA/C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.14 Replacing the master WAM or inserting a new primary uncommissioned

WAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3 Identification of faulty units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.1 Checking faulty fan units from the NetAct™ Alarm Dialog window . . . . 463.2 Checking faulty fan units with IPA2800 MML (for example HIT2.8.0) . . 473.3 Checking faulty fan units from the WCDMA BTS Site Manager Alarms win-

dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.4 Checking the failure of the whole Fan Module (WFAx) . . . . . . . . . . . . . 48

4 Checking antenna line, MHA and Bias-T . . . . . . . . . . . . . . . . . . . . . . . . 50

5 Checking WSMA and WSMB bus errors . . . . . . . . . . . . . . . . . . . . . . . . 52

6 Troubleshooting WCDMA BTS without remote or local connection possible53

7 Checking the'No connection to unit' alarm. . . . . . . . . . . . . . . . . . . . . . . 54

8 WSMx cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.1 WSMA cabling for rel. 1 HW BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.2 WSMB cabling for rel. 2 HW BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

9 Backplane cabling with different cabinet types . . . . . . . . . . . . . . . . . . . 659.1 WCCA/WINA Nokia Supreme Indoor and WODA Nokia Supreme Outdoor

659.2 WCCC Nokia Optima Indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679.3 WREA Nokia Optima Compact RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699.4 WREB Nokia Optima Compact Outdoor . . . . . . . . . . . . . . . . . . . . . . . . 739.5 WBBA Nokia Optima Compact IBBU. . . . . . . . . . . . . . . . . . . . . . . . . . . 74

10 Signal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4 DN70558202Issue 01D


Id:0900d805807389a4

11 Operation and maintenance interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 78

12 Nokia UltraSite WCDMA BTS, 1+1+1 configuration . . . . . . . . . . . . . . . . 79

13 Power supply architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

14 Checking HSDPA settings in network elements . . . . . . . . . . . . . . . . . . . 8114.1 Setting Windows registry TCP values. . . . . . . . . . . . . . . . . . . . . . . . . . . 8114.2 Checking requirements for WCDMA BTS. . . . . . . . . . . . . . . . . . . . . . . . 8314.3 Checking HSDPA throughput problems at BTS or terminal side . . . . . . 8814.4 Monitoring performance with WCDMA BTS Site Manager . . . . . . . . . . . 9014.5 16QAM check list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9114.6 Checking HSPA parameters in RAS06. . . . . . . . . . . . . . . . . . . . . . . . . . 9414.6.1 How to get started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9414.6.2 HSUPA parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9414.6.3 For HSDPA maximum cell throughput, the following parameters should be

checked/modified from OMS parameters . . . . . . . . . . . . . . . . . . . . . . . . 9514.6.4 Miscellaneous parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

15 BTS Site Manager indicates Missing Cabinet Product Code . . . . . . . . . 98

16 Troubleshooting the AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10416.1 Accessing AXC with web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10416.2 Downloading the configuration file fails. . . . . . . . . . . . . . . . . . . . . . . . . 10516.3 Configuration file parsing fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10616.4 AXC Manager does not start up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10716.5 AXU LED remains yellow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10816.6 Local connection to AXC cannot be established. . . . . . . . . . . . . . . . . . 10916.7 IFU cannot be installed to S-AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11116.8 Remote IP connection to AXC fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11216.9 Remote management connection to AXC fails . . . . . . . . . . . . . . . . . . . 11316.10 AXU or IFU is continuously resetting . . . . . . . . . . . . . . . . . . . . . . . . . . 11416.11 Configuration is lost after software update . . . . . . . . . . . . . . . . . . . . . . 11516.12 Software update fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

DN70558202Issue 01D

5


Id:0900d805807389a4

List of FiguresFigure 1 Setting Internet Connection Firewall setting in Windows XP . . . . . . . . . 12Figure 2 Example showing WCDMA loop test signal path. . . . . . . . . . . . . . . . . . 17Figure 3 Selecting the units to be tested in the WCDMA loop test . . . . . . . . . . . 18Figure 4 WCDMA loop test results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 5 Detailed WCDMA loop test results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 6 Failure details of a WCDMA loop test . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 7 WCDMA loop test results file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 8 NetAct Alarms window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 9 Supreme cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 10 Optima cabinet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 11 Optima Compact Outdoor (WREB) cabinet . . . . . . . . . . . . . . . . . . . . . . 38Figure 12 Optima Compact IBBU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 13 Optima Compact RF extension cabinet . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 14 Triple-mode cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 15 MetroSite cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 16 MetroSite 50 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 17 Fan mapping in Supreme cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 18 Fan mapping in Supreme (WINB) cabinet . . . . . . . . . . . . . . . . . . . . . . . 43Figure 19 Fan mapping in Optima Compact Outdoor (WREB) cabinet . . . . . . . . . 43Figure 20 Fan mapping in Optima Compact IBBU cabinet . . . . . . . . . . . . . . . . . . 44Figure 21 Fan mapping in Optima Compact RF extension cabinet . . . . . . . . . . . . 44Figure 22 Fan mapping in Triple-mode cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 23 Fan mapping in MetroSite cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 24 Fan mapping in MetroSite 50 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 25 Faulty fan unit information from NetAct's Alarm Dialog window . . . . . . 46Figure 26 Faulty fan unit information with IPA2800 MML . . . . . . . . . . . . . . . . . . . 47Figure 27 Faulty fan unit information from WCDMA BTS Site Manager Alarms win-

dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 28 Fan module failure information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 29 BTS Site Manager view when the whole fan module is faulty . . . . . . . . 49Figure 30 Pinout order at Bias-T end. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 31 Main power connector not pushed firmly to backplane connector . . . . . 55Figure 32 Oxidized contacts in backplane power connector . . . . . . . . . . . . . . . . . 55Figure 33 Bad installation in WTR backplane (power connector) . . . . . . . . . . . . . 56Figure 34 One pin lifted out from the D-9 connector . . . . . . . . . . . . . . . . . . . . . . . 56Figure 35 Two bent wires in spider cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 36 Control cable of IBBU Fan left between backdoor and isolation rubber 58Figure 37 WSMA cabling for Supreme cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 38 WSMA cabling for Optima Compact RF extension cabinet . . . . . . . . . . 60Figure 39 WSMA cabling for Optima Compact IBBU cabinet . . . . . . . . . . . . . . . . 61Figure 40 WSMB cabling for Supreme cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 41 WSMB cabling for Optima Compact RF extension cabinet . . . . . . . . . . 63Figure 42 WSMB cabling for Optima Compact IBBU cabinet . . . . . . . . . . . . . . . . 64Figure 43 Bus cabling for Supreme Indoor WCCA/ WINA and Supreme Outdoor

WODA cabinets, rear side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 44 HCI cabling for Supreme Indoor WCCA/WINA and Supreme Outdoor

6 DN70558202Issue 01D


Id:0900d805807389a4

WODA cabinets, rear side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 45 LVDS harness cables for Optima Indoor cabinet . . . . . . . . . . . . . . . . . . 67Figure 46 Spider cabling for Optima Indoor cabinet . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 47 LVDS harness cables for Optima Compact RF cabinet . . . . . . . . . . . . . 69Figure 48 Spider cabling for Optima Compact RF cabinet . . . . . . . . . . . . . . . . . . . 70Figure 49 HCI cabling for Optima Compact RF cabinet (RF_1) . . . . . . . . . . . . . . . 71Figure 50 HCI cabling for Optima Compact RF cabinet (RF_2) . . . . . . . . . . . . . . . 72Figure 51 Spider cabling for Optima Compact Outdoor cabinet . . . . . . . . . . . . . . . 73Figure 52 HCI cabling, front side of Optima Compact Outdoor cabinet . . . . . . . . . 73Figure 53 HCI cabling, top side of Optima Compact Outdoor cabinet . . . . . . . . . . 74Figure 54 LVDS harness cables for Optima Compact IBBU cabinet . . . . . . . . . . . 74Figure 55 HCI cabling for Optima Compact IBBU cabinet 1 . . . . . . . . . . . . . . . . . . 75Figure 56 HCI cabling for Optima Compact IBBU cabinet 2 . . . . . . . . . . . . . . . . . . 76Figure 57 Nokia UltraSite WCDMA BTS, 1+1+1 configuration, from the SW point of

view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 58 Power supply architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 59 Starting Registry Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 60 Adding or editing DWORD values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 61 General settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 62 Ptx offset HSDPA 0.8 dB ok for all WCDMA BTSs. . . . . . . . . . . . . . . . . 85Figure 63 Enabling HSDPA at the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 64 Select measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 65 Modify WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 66 Modify WCDMA BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Figure 67 AAL2 User plane definition for HSUPA in CoCo. . . . . . . . . . . . . . . . . . . 95Figure 68 AAL2 User plane VCC settings in CoCo. . . . . . . . . . . . . . . . . . . . . . . . . 96Figure 69 Message about missing cabinet product code . . . . . . . . . . . . . . . . . . . . 98Figure 70 WID location e.g. in WINA cabinet (rear, bottom left) . . . . . . . . . . . . . . . 99Figure 71 WID location e.g. in WINB cabinet (inside WEA module) . . . . . . . . . . . 100Figure 72 I2C-bus cablings between racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 73 Fuse mapping in WINB cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Figure 74 I2C-bus cablings between racks (Supreme Outdoor cabinet). . . . . . . . 103

DN70558202Issue 01D

7


Id:0900d805807389a4

List of TablesTable 1 Connection Success/Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Table 2 Connection BER Success/Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 3 Connection SIR Success/Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 4 Signal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Table 5 Operation and maintenance interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 78Table 6 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Table 7 Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

8 DN70558202Issue 01D


Id:0900d805807389a4

DN70558202Issue 01D

9


Summary of changes

Id:0900d805807454fe

Summary of changesBecause of the changes in internal writing tool, issues have new labels.

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 01C and 01DUpdated section:

• Checking requirements for WCDMA BTS

Removed section:

• Checking firewall settings for a PC equipped with CyberArmor

Changes between issues 1-2 and 01CUpdated section:

• Running a WCDMA loop test

Changes between issues 1-1 and 1-2In Identification of faulty units, the following new section has been added:

• Checking the failure of the whole Fan Module (WFAx)

Changes between issues 1-0 and 1-1Updated sections:

• Troubleshooting overview • Analysis of the WCDMA loop test report • Checking antenna line, MHA and Bias-T

Removed section:

• Checking WCDMA cell parameter settings for AIR

g Note that the UltraSite and MetroSite WCDMA Base Station Faults and Trouble-shooting document has been divided into two documents. BTS faults are in the UltraSite and MetroSite WCDMA Base Station Faults document (DN70558195).

10 DN70558202Issue 01D


Id:0900d805805fcc24

Troubleshooting overview

1 Troubleshooting overviewWhen the base station (BTS) reports an alarm, some basic steps need be taken to investigate the problem. Earlier troubleshooting actions for a related BTS are helpful for further investigation and should be followed up whenever possible.

Most of the troubleshooting actions can be performed remotely, but some actions may also be required on-site.

Information sources in fault situationsUse at least the following information sources when carrying out troubleshooting:

• AlarmsAlarms are the primary source of information in most situations where troubleshoot-ing is needed. Alarms are printed out on the alarm printer and/or other devices that you have specified for the network element. For instructions, see section Checking BTS alarms. For BTS fault descriptions, see document UltraSite and MetroSite WCDMA BTS Faults.

• BTS documentationYou can find the latest information in the updated BTS documentation and Technical Notes. Access to the web pages is confined and information is delivered via your local Nokia Siemens Networks representative. WCDMA BTS documentation is delivered via Nokia Online Services (NOLS). The latest SW related documentation, such as List of Generic Faults and Release Note, can be found on the WCDMA BTS Technical Support web pages.

• BTS log filesBTSTechreport files are useful for troubleshooting purposes and must be attached when Resolve case is raised to Tier 3. Logs can be fetched locally or remotely with WCDMA BTS Site Manager. For instructions, see WCDMA BTS Site Manager online help.

DN70558202Issue 01D

11


Troubleshooting UltraSite and MetroSite WCDMA BTS

Id:0900d8058074549b

2 Troubleshooting UltraSite and MetroSite WCDMA BTS

2.1 Accessing WCDMA BTS Site Manager connectionThe PC firewall settings must not prevent the start-up of the FTP server on the PC. If the WCDMA BTS Site Manager connection cannot be established, correct PC firewall settings have to be confirmed. For instructions, see Checking firewall settings in Windows XP.

g When using other than Nokia Siemens Networks laptops, it is recommended to remove all firewall and security software including Bluetooth and Wireless LAN.

12 DN70558202Issue 01D


Id:0900d805805fcc2e

2.2 Checking PC firewall settings in Windows XPPurposeIf the connection to WCDMA BTS Site Manager cannot be established, the PC firewall settings may prevent the start-up of the FTP server on the PC. This procedure describes how to correct the firewall settings.

Steps

1 Clear the Internet Connection Firewall checkbox.

a) Select Start → Settings → Network Connections → Properties → Advanced.b) Clear the Internet Connection Firewall checkbox.c) Click OK.

Figure 1 Setting Internet Connection Firewall setting in Windows XP

DN70558202Issue 01D

13


Id:0900d805805fcc31

2.3 Checking BTS alarmsPurposeFollow these instructions to check the BTS alarms and LED states.

Check the active BTS alarms from the RNC/OSS, if possible.

Steps

1 Check the alarms with OMS Fault Management.

a) Start an MML session.b) Check the active alarms with the ZAAP command.c) Check the alarm history at a defined time using the ZAHP command.

2 Establish a connection to the BTS using WCDMA BTS Site Manager.

3 Check the unit (LED) states. Ensure that WCDMA BTS Site Manager HW view corresponds with the actual BTS HW configuration. If there is a mismatch or grey units, check the SW level. For instructions, see Checking BTS SW versions and SW download.

Unit LED states are described in the unit description documents, see UltraSite and Met-roSite 50 WCDMA BTS descriptions.

4 Check the BTS alarms.BTS unit failures can be checked from the BTS alarms and should be followed up during the troubleshooting procedure.

Follow up the latest alarm handling disparities and other relevant information. These are described in separate BTS bulletins delivered via your local Nokia Siemens Networks representative.

If the alarms are related to the AXC or BTS WSC/WMC clock unit, check the network synchronisation, transmission, AXC and other network alarms from the related BTS. For more information, see ATM-related problems in Iub interface. For instructions, see Checking ATM-related problems remotely and before a site visit.

14 DN70558202Issue 01D


Id:0900d805805fcc34

2.4 Checking BTS SW versions and SW downloadSteps

1 Check the BTS SW versions with WCDMA BTS Site Manager and confirm that all the plug-in units are at the same SW level.

2 If the SW upgrade is unsuccessful, the WCDMA BTS Site Manager might not display the BTS SW used. Try a new SW download a couple of times.

Further informationThe BTS SW is upgraded to all the needed packages after updating the SW again, and all the packages will be in state ‘Not needed’. This means that the packet you tried to load is similar to the SW already active.

3 If the PC connection or BTS SW download is unsuccessful, ensure the correct PC settings and that the used cable is working and of correct model.You can try to ping the master WAM for example by using the DOS prompt.

For information on correct PC firewall settings, see Checking firewall settings for a PC equipped with CyberArmor and Checking firewall settings in Windows XP.

4 After a successful BTS SW download, launch a new WCDMA BTS Site Manager session to confirm the use of the correct WCDMA BTS Site Manager version.

5 Check that the BTS and AXC SW versions are compatible.For the correct AXC SW version, see the WCDMA BTS Compatibility document.

DN70558202Issue 01D

15


Id:0900d805805fcc39

2.5 Checking the BTS commissioning filePurposeThis procedure helps in solving problems with the BTS commissioning file.

Steps

1 Check the BTS commissioning file to ensure the correct BTS configuration and settings.

2 Check that the cabling matches the actual cabling of the BTS.

3 Check that the ATM information matches the settings at the CoCo and AXC Manager.

4 If the BTS cells do not come up to a working state (for example, BL-S) and the ATM traffic is terminated to more than one WAM unit, check that the BTS A2EA address matches the RNC setting (AAL2 end address in CoCo).

16 DN70558202Issue 01D


Id:0900d80580614836

2.6 Running a WCDMA loop testPurposeFollow these instructions to verify the signal path from the WAM to the WTR units and the functioning of the units in the path using WCDMA loop test. You should always perform the loop test in the commissioning phase.

When running the WCDMA loop test, note the following:

• WCDMA BTS Site Manager can run the test remotely or locally. The remote loop is done via the OAM Iub, whereas the local loop is done straight via the WAM front panel Ethernet port.

• The WSP and the corresponding subrack’s WAM must be selected simultaneously for the testing.

• CNBAP signalling (ATM termination) always reserves resources from the testing (that is, Common Channel Reservation) as well as HSDPA (that is, Physical Shared Reservation Failed).

• Optimisation reduces significantly the time necessary to complete the test. • It is recommended to run loops for one sector at a time so that it does not disturb the

entire BTS and traffic. • For a stand-alone BTS, it is mandatory that you reset to the test state before running

the loop test. Start from step 1. • For an integrated (Iub connected) BTS, the WCDMA loop test can be run in working

state. In that case start from step 2.

g • The loop test starts by measuring both downlink and uplink power and according to the levels the loop signal level in downlink is set and the loop test attenuators are adjusted correctly. Quick changes in the downlink or uplink power can affect the loop test results. This is more common if the HSDPA/HSUPA is in use.

• Bad VSWR value can also affect the test results. When the VSWR is not good enough then the reflected power might disturb the loop signal so much that the result is not good.

• Very high Prx value can also disturb the results when the disturbing signal from the antenna is on such high level that it disturbs the detection of wanted loop test signal. When the uplink average level is relatively high, the level changes normally more than when it is near the noise level. This is to affect also the loop test results.

• Above cases can affect loop test results. If there are combinations of the above cases it is possible that the loop test fails even though the transceiver works fine (for example Bad VSWR and high/fast level changes at up-/downlink).

• Nokia Siemens Networks recommends that the loop test is done during non busy hours. Even if the loop test results are not at a good level (especially indoor solution or distributed antenna solution) but the KPI figures are fine then the WBTS system works fine.

The following figure depicts an example of the operation of the WCDMA test loop on a general level.

DN70558202Issue 01D

17


Id:0900d80580614836

Figure 2 Example showing WCDMA loop test signal path

Before you startCheck that the BTS is in either ‘On air’ or ‘Test dedicated’ mode.

Steps

1 Select Tests → Enter BTS Test State... from the main menu to reset the BTS to test state.

2 Select Tests → WCDMA BTS Loop Test… from the main menu.

3 Select the units you want to test and the test duration for the single loop.If, for example, WSP6 is selected for testing, the corresponding subrack’s WAM2 must also be selected.

The maximum number of conducted elementary tests is large and running all of them is time-consuming. The Optimised Variation In Use parameter can be used to optimise the variation of units in elementary tests, so not all combinations will conduct an elementary test.

The number of required elementary tests is optimised excluding variations, which would be excessive from the viewpoint of required test coverage. Passing over excessive vari-ations will significantly reduce the time necessary to complete the test, especially if all units in a BTS must be included in the test.

Iub

IFUIFU

AXU

IFU

WSC

CarrierInterFace

WAF

WTR

WPA

WS

P

WS

P

WS

P

WS

P

WS

P

WS

P

WAM

DSC-BUS

T-busRT-bus

RR-bus

ST-busSR-bus

WAF

WTR

WPA

WSM WAM

R-bus

WAF

WTR

WPA

WAF

WTR

WPA

WS

P

WS

P

WS

P

WS

P

WS

P

WS

P

WAM

DSC-BUS

WAMWSM

WAF

WTR

WPA

WAF

WPA

WS

P

WS

P

WS

P

WS

P

WS

P

WS

P

WAM

DSC-BUS

WAMWSM

WTR

18 DN70558202Issue 01D


Id:0900d80580614836

Figure 3 Selecting the units to be tested in the WCDMA loop test

4 Click Start.

DN70558202Issue 01D

19


Id:0900d80580614836

5 At the end of the test, view the test result in the Test Summary window and save the test report, if needed.

Figure 4 WCDMA loop test results

g In case of an incorrect test result, check the WSMx cabling before further investiga-tions. For more information, see WSMx cabling.

20 DN70558202Issue 01D


Id:0900d80580614836

6 Select View Report to view the test report details.

Figure 5 Detailed WCDMA loop test results

Further informationFor a detailed explanation of the test results, see Analysis of the WCDMA loop test report.

DN70558202Issue 01D

21


Id:0900d80580614836

7 Select Failure Details to view more information on the test results.

Figure 6 Failure details of a WCDMA loop test

8 After you have executed the test, select Tests → Exit BTS Test State to restore the BTS back to the normal operational state.

22 DN70558202Issue 01D


Id:0900d805805fcc40

2.7 Analysis of the WCDMA loop test reportThe test report displays the tested loops by units and the results of the WCDMA loop test.

Figure 7 WCDMA loop test results file

Connection Success/FailureThis item indicates if running the elementary test for the connection was done without a problem or not. If some error occurred, the nature of the failure is reflected. Only one failure indication is stored per connection at a time, the latest one is reflected if multiple errors occur.

The following success/failure indications can be reported:

Result Description Corrective action

OK No failures regarding to the test. No actions required.

WAM Not Responding The WAM unit of the connection did not respond.

1. Try running the test again.2. If the failure reoccurs, reset the BTS

and run the test again. If the same unit causes the failure, replace the unit.

Table 1 Connection Success/Failure

DN70558202Issue 01D

23


Id:0900d805805fcc40

WAM State Inconsistent A test-dedicated state was required to execute the test (RNC was not connected), but the WAM unit of the connection failed to enter the state. The WAM is potentially in inconsistent state and requires a reset.



Interrupted The test requester interrupted the test. No actions required.

WTR Not Responding WTR unit did not respond. 1. Try running the test again.2. If the failure reoccurs, reset the BTS


WTR HW Version Detection Failed

Test Manager failed to detect WTR HW version.



WSP HW Version Detection Failed

Test Manager failed to detect WSP HW version.



BB-Pooling Detection Failed Test Manager failed to detect BB-pooling relations of this WSP and TRX.



WAM-WSP Pooling Mismatch The specified WSP is allocated to a differ-ent WAM in this subrack



No DSP4 in WSPC WSPC/WSPD/WSPE does not have DSP4 module, but this module was specified for test in test request.



No TRX2 in WTRA WTRA/C does not have TRX2 module, but this module was specified for test in test request.



BB-Pooling Mismatch The specified WSP does not belong to the same pool (Local Cell Group) with the TRX specified in test request.



WAM-WSP Pooling Detection Failed

Test Manager failed to detect WAM-WSP pooling relations of this WSP and WAM.



Signal-Path Not Closed WTR unit refused to close signal path for testing the connection.

1. Check that the cell exists in the RNC and that it is not locked.

2. Check that the cell is not blocked in the BTS.


Table 1 Connection Success/Failure (Cont.)

24 DN70558202Issue 01D


Id:0900d805805fcc40

Signal-Path Not Open WTR unit refused to open signal path after testing the connection.



RNC Not Connected The WAM unit of this connection refused to start an elementary test because it is in operational state while the RNC is not con-nected.



RNC Detection Failed Batch test scheduler could not start the elementary test because it failed to detect status of the RNC connection.



No Test Report WAM unit of the connection did not send the test report regarding to the connection.



Telecom Not Responding The test cannot be performed because Telecom did not respond.



Resources Not Reserved Telecom could not reserve resources for the test because they were already in use.

Run the test again if necessary.

Resources Not Released Telecom refused to release resources reserved for testing the connection.



ATM Not Responding ATM unit or TUP did not respond. 1. Try running the test again.2. If the failure reoccurs, reset the BTS


Test-Signal Not Started ATM unit or TUP refused to generate test signal for testing the connection.



Test-Signal Not Stopped ATM unit or TUP refused to stop the test signal after testing the connection.



Internal Error An unexpected error appears in BTSOM. 1. Try running the test again.2. If the failure reoccurs, reset the BTS


Skipped The test was excluded by the optimization procedure.

No actions required.

Cell Overload Current transmission power at the WTR unit was too high to start a new loop test.




DN70558202Issue 01D

25


Id:0900d805805fcc40

Connection BERThis item shows the BER value measured during the test for this connection. The BER value is expressed as a ratio of incorrect bits to correct bits. The parameter is evaluated only if it was possible to capture this value during the test. Whether this parameter is evaluated or not is indicated by the BER Success/Failure parameter.

Connection BER Success/FailureThis item indicates if BER/BLER were successfully evaluated for this connection. If the values are not valid, the failure reason is indicated. The following different success/fail-ure indications can be reported:

Loop Level Unfounded It was not possible to find suitable loop level in proportion with currently received/transmitted power at the WTR unit (even with the help of adjustable atten-uator inside the WTR unit).


Common Channels Reserved Telecom has reserved the DSP resources for common channels and the test cannot be performed.


Physical Shared Channels Reserved

The loop test is executed via a RAKE pro-cessor, which resources are reserved for the HSDPA call and the test cannot be per-formed.


Unexpected Internal Error WAM unit of the connection indicated an error, which refers to some malfunctioning in the master or slave parts of the Test Subsystem or in communication paths between them.



CH Code conflict Channelization code conflict (between loop signal and traffic) has occured during loop test and Telecom has released the code (for traffic) by interrupting the test.





OK Result was successfully evaluated. No actions required.

Not Passed Result was successfully evaluated, but did not pass the test.



Void Testing the connection is not (yet) done or the test procedure failed before the results could be captured.

ATM Not Responding ATM unit did not respond. 1. Try running the test again.2. If the failure reoccurs, reset the BTS


Table 2 Connection BER Success/Failure

26 DN70558202Issue 01D


Id:0900d805805fcc40

Connection SIRThis item shows the signal-to-interference ratio (SIR) of the uplink DPCH, measured in the BTS receiver while testing this connection. The parameter is evaluated only if it was possible to capture this value during the test. Whether the value is evaluated or not is indicated by the Connection SIR Success/Failure parameter.

Connection SIR Success/FailureThis item indicates if the SIR was successfully evaluated or not. If the value is not valid, the failure reason is indicated. The following different success/failure indications can be reported:

The SIR value ranges from -11 dB to 20 dB in steps of 0.5 dB. The minimum required value of SIR is 2.0 dB. If the measured SIR is below minimum, the value of the param-eter Connection SIR Success/Failure in report shows Not Passed.

Analyzer Not Synchronized BER analyzer could not synchronize at all or did synchronize for less than 30% of the required data amount.



Internal Error OAM or ATM SW is malfunctioning. 1. Try running the test again.2. If the failure reoccurs, reset the BTS



Table 2 Connection BER Success/Failure (Cont.)


OK Result was successfully evaluated. No actions required.

Not Passed Result was successfully evaluated, but did not pass the test.



Void Testing the connection is not (yet) done or the test procedure failed before it was possible to capture the value.

Telecom Not Responding Telecom did not respond. 1. Try running the test again.2. If the failure reoccurs, reset the BTS


Telecom Rejecting Telecom could not send the SIR value; known cause is that Telecom could not get its value from DSP (RAKE).



Table 3 Connection SIR Success/Failure

DN70558202Issue 01D

27


Id:0900d805805fcc43

2.8 ATM-related problems in the Iub interfaceTransmission network problems, such as link breaks, bit errors and cell loss may occur in transmission system between the RNC and the WCDMA BTS (WBTS). In some cases, the WBTS may be able to tolerate the transmission disturbances, but if the problem severity is high enough, the RAN performance decreases. In addition to the tol-erability, also the WBTS behaviour (alarms/indications) differs, depending on the trans-mission problem in question.

In the most common (synchronisation) configuration, when a physical layer link break occurs between an AXC and the first transmission node towards the RNC (note that in a leased line situation, the far-end node for the AXC may be located even at the very same WBTS site), the AXU, IFU and WSC units start alarming by a red LED, indicating a transmission link problem. When the transmission link is operating normally, the green LED is on again. In other words, the red LED indication does not automatically mean that the unit is faulty, and therefore there is no need to replace the unit(s) by default. Further troubleshooting is needed to verify whether the unit is faulty or if the indication is caused by transmission network problems.

During a link break, the following alarms are active in the BTS/RNC:

• After about a 1-minute break: • 7771 WCDMA cell out of use for each cell concerned

• After about a 5-minute break: • 7750 Failure in WCDMA O&M connection

• 3117 Failure in SAAL UNI signalling link activation • 3129 AAL2 type reset failed

• If the link break lasts more than 6 minutes: • Alarm 7651 BTS RNC interface signalling link failure is raised

at the WCDMA BTS Site Manager and the WAM LED is blinking red.

If short link breaks occur frequently (every ~10 s), the alarm 7651 BTS RNC interface signalling link failure may be activated. The alarm is also visible in the RNC because the O&M link still operates due to higher disturbance tolerability than the other signalling links. In this case the WAM LED indication is blinking red.

When the above mentioned alarms are active, cells are not necessarily in operational state and thus the network cell availability KPI may be affected. However, if the WAM is commissioned into use but the CoCo is not created (termination point is missing in the RNC), the WAM has an active alarm 7651 BTS RNC interface signalling link failure, and the WAM LED indication is blinking red. In this case the cell availability is not affected.

Note that there is a difference between physical layer and logical layer link breaks. The RAN detects (alarm activity) both types in a similar way, but the BTS LED indications (as well as the AXC alarms) are different between these cases.

Bit errors (and cell loss) may be caused by synchronisation problems in the transmission network or poor link quality (for example, too long hops, environmental disturbances, weather conditions, and poor microwave radio link budgeting). Depending on the sever-ity, these do not necessarily cause problems to the RAN performance, but may affect the end-user data applications. Furthermore, high error bursts in the transmission network may affect the RAN system similarly as the link breaks.

For instructions on troubleshooting ATM, see Checking ATM-related problems remotely and before a site visit and Checking ATM-related problems at a BTS site.

28 DN70558202Issue 01D


Id:0900d805805fcc46

2.9 Checking ATM-related problems remotely and before a site visitPurposeTroubleshooting must be performed to find out the reason for the alarms, abnormal LED indications and RAN performance degradation.

Steps

1 Prior to actual troubleshooting (before possible resets), record the BTS technical log and the AXC log as well as the RNC alarm history for the possible actions carried out by the BTS system support.

2 Check the active alarms (both the AXC and BTS/RNC) and act accordingly to remove the root cause for the alarm(s).See the alarm instructions, for example, from the NOLS system or via AXC and WCDMA BTS Site Manager online help.

3 Check the alarm history (both the AXC and BTS/RNC) to see how the transmission line and RAN have been performing in the past.

4 Check the AXC performance monitoring counters of different transmission layers.For instructions, see the Operating and maintaining AXC document.

5 Check that the parameters defined in the RNC match the ones in the AXC.For example, if the Peak Cell Rate (PCR) values in the AXC are a lot smaller than those configured in the RNC, it may lead to ATM traffic policing in the AXC side, which causes lost messages.

For more information, see the dimensioning documentation (for example in NOLS).

6 Check with the Iub log monitoring tool (for example, Nethawk) the missing signal-ling messages, re-transmission activity, and SSCOP layer polling of signalling links to find out if messages disappear along the transmission path between the RNC and the BTS.

7 Depending on the problem location, reboot the AXC (AXU and/or IFU) via AXC Manager (soft-reboot), or reboot the BTS via WCDMA BTS Site Manager.

Further informationIf the alarms/alarm history/error counters reveal that there is something wrong in the transmission network, the fault(s) and/or problems must be fixed. In this case, AXC/BTS resets or unit replacements do not correct the situation.

Most of the alarms are related to problems that occur at the far-end transmission device or in the transmission network between the RNC and the BTS. Troubleshooting may be

DN70558202Issue 01D

29


Id:0900d805805fcc46

difficult if leased lines are used. In this case, contact the leased line service provider and ask for investigation support from their side about the transmission line/network: perfor-mance/quality reports regarding the devices along the transmission line.

Furthermore, for the transmission lines suspected to be faulty either constantly or occa-sionally, a synchronisation audit for the transmission network and/or data integrity mea-surement (physical layer or ATM layer analyser, depending on the alarms and network structure) may be carried out. Most of the synchronisation measurements do not affect services, while the data integrity measurements cause service breaks.

After you have ensured that the transmission network is working correctly and if the above listed indicators suggest that there is a fault in the BTS, a site visit is required.

30 DN70558202Issue 01D


Id:0900d805805fcc49

2.10 Checking ATM-related problems at a BTS sitePurposeBy checking the ATM-related problems as instructed below helps you to avoid useless and expensive maintenance actions at the BTS site.

Note that if the root cause for the alarms/indications or poor RAN performance is caused by permanent or occasional problems in the transmission network between the RNC and the BTS, replacing the BTS units does not correct the situation.

Steps

1 Before the other actions at the BTS site, record the BTSTechreport log files and the AXC logs for the possible actions carried out by the BTS R&D System Support group.

2 Check the condition of the AXU/IFU cables and replace them if needed.

3 If the problem still exists, make a hard reboot for the BTS (power off and on).

g In case of a DC-powered BTS, the AXC (AXU and all the IFU units) must be removed from the subrack and re-inserted.

4 If the power reset does not help, clear the AXC settings and re-commission the AXC.

a) Perform the ‘Recovery’ command with AXC Manager/AXC web interface to clear the AXC settings.

b) Re-commission the AXC.

For detailed instructions, see Commissioning AXC.

5 Replace the HW unit.

g Replacing a HW unit is the last option to be carried out.

DN70558202Issue 01D

31


Id:0900d805805fcc4c

2.11 Checking units, cables and connectorsPurposeThis procedure describes how to perform general HW verification.

Steps

1 Before disconnecting any of the BTS units, block the cells either with WCDMA BTS Site Manager or from the OSS to avoid unnecessary alarms in the network.

2 Check visually that all cables and connectors are in order and firmly connected (according to the torque wrench values mentioned in the Product Documenta-tion).

3 Check that the cable codes are according to the Product Documentation labelling.This is very important when using the WOC because, for example, wrong cable lengths can cause different LPA faults.

4 Remove the unit and check the unit mechanicsto see if there are any visible damages.Also, make sure that the unit connector pins are not bent and the backplane connector is not damaged.

5 Swap the units between a working and a faulty one (for example, between faulty and working sectors) to ensure that the alarm is following the unit.

6 If the alarm is always in the same slot regardless of the unit, check the backplane cabling in front of/behind the cabinet and replace with a new one if needed.If the alarm is caused by a cable, backplane or another reason, which is cleared without changing the unit, there is no need to replace the unit with a new one.

32 DN70558202Issue 01D


Id:0900d805805fcc4f

2.12 Installing plug-in units and front cablingPurposeThis procedure describes the additional steps that must be taken when performing BTS on-site troubleshooting if a BTS unit HW failure is suspected.

Steps

1 Ensure that all plug-in units have a secure connection to the backplane.

2 Check the unit LED states and BTS alarms.

3 Check that all screws and dummy panels are placed and properly fastened.

4 Ensure proper installation of the BTS front RF and WSMx cabling. For more information, see WSMx cabling.

DN70558202Issue 01D

33


Id:0900d805805fcc55

2.13 Hot inserting WSPA/CPurposeThis procedure describes how to hot insert the WSPA/C if you have problems during or after the installation of WSP cards.

Before you startBefore a hot insert, all the WSPA/C units already inserted in the hot-inserted sector must be in a working state (green LED). Also, after every WSPA/C hot insert, you must wait until the LED of the previously installed unit has changed to stable green.

Steps

1 Open the ejectors from the WSP card.

2 Install the unit properly in the guiding rails.

3 Install the unit in one proper push in a horizontal angle by using the ejectors at the same time.Do not use extra force or hit the unit into its position:

• This may damage the connector • The hot-insert procedure is based on pins of different lengths. Therefore, the unit

has to be installed by one push, but not too fast (not by hitting).

It is important that all preparations are done so that the unit can be installed in one push.

34 DN70558202Issue 01D


Id:0900d805805fcc5a

2.14 Replacing the master WAM or inserting a new primary uncommissioned WAMPurposeThis procedure describes how to replace or insert a WAM if you have problems during or after the installation of the WAM.

Before you startCheck that the SW is updated to all WAMs. For instructions, see Checking BTS SW versions and SW download.

If, during commissioning, the BTS SW or WCDMA BTS Site Manager cannot detect all the WAMs inserted in the BTS, the BTS needs a power reset.

g Switching off the power to the subrack where the new primary WAM will be inserted is not enough. The whole BTS should be switched off before inserting the new WAM into the BTS.

Also, performing a site reset with WCDMA BTS Site Manager (BTS block/unblock) to detect new primary WAM units is not enough.

Steps

1 Block the site from traffic in a controlled way with WCDMA BTS Site Manager.

2 Switch the BTS power off.

3 Install the new units (a new WAM and possible other units).

4 Connect the unit cables according to your configuration.

5 Switch the BTS power back on.

DN70558202Issue 01D

35


Identification of faulty units

Id:0900d805805fcc5f

3 Identification of faulty unitsThis section describes how to identify WCDMA BTS modules and plug-in units in differ-ent UltraSite and MetroSite WCDMA BTS cabinets. Also, it describes how a faulty unit can be located with the NetAct system.

See below the explanations of an example 'Alarm Dialog' window for different fields in Figure NetAct Alarms window.

• 7652 *: reported severity • Suppl info field: fault name • Diag info field:

(01) number of the rack where the plug-in unit is located (HEX)(02) number of the shelf where the plug-in unit is located (HEX)(0A) number of the slot where the plug-in unit is located (HEX)(0010) not applicable(WFAA 04) faulty unit and ID

Figure 8 NetAct Alarms window

Unit location numbers are used in alarm information to locate a failed unit. The main principle for numbering locations is from top to bottom and from left to right. Location numbers are defined with the following parameters:

RACK Specifies the rack of the cabinet and separates BB and RF compart-ments from each other

SHELF Specifies the shelf in the cabinet

SLOT Specifies the location on the shelf

The figures below indicate how the rack, shelf and slot are defined in different UltraSite and MetroSite WCDMA BTS cabinets.

36 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 9 Supreme cabinet

DN70558202Issue 01D

37



Id:0900d805805fcc5f

Figure 10 Optima cabinet

38 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 11 Optima Compact Outdoor (WREB) cabinet

Figure 12 Optima Compact IBBU cabinet

DN70558202Issue 01D

39



Id:0900d805805fcc5f

Figure 13 Optima Compact RF extension cabinet

40 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 14 Triple-mode cabinet

DN70558202Issue 01D

41



Id:0900d805805fcc5f

Figure 15 MetroSite cabinet

42 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 16 MetroSite 50 cabinet

The figures below indicate how the fans are defined in different WCDMA BTS cabinets.

Note fan control naming: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower.

Figure 17 Fan mapping in Supreme cabinet

DN70558202Issue 01D

43



Id:0900d805805fcc5f

Figure 18 Fan mapping in Supreme (WINB) cabinet

Figure 19 Fan mapping in Optima Compact Outdoor (WREB) cabinet

WPA

53 55 57

54 56 58

51 48

50 49

WFA-unit

WTR

BB_WFA_10 TR_WFA

WTR

WPA

53 55 57

54 56 58

153 154

HEX FAN

155

MFUAMFUA MFUA

59

WFD

WEAC

44 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 20 Fan mapping in Optima Compact IBBU cabinet

Figure 21 Fan mapping in Optima Compact RF extension cabinet

DN70558202Issue 01D

45



Id:0900d805805fcc5f

Figure 22 Fan mapping in Triple-mode cabinet

Figure 23 Fan mapping in MetroSite cabinet

46 DN70558202Issue 01D


Id:0900d805805fcc5f


Figure 24 Fan mapping in MetroSite 50 cabinet

3.1 Checking faulty fan units from the NetAct™ Alarm Dialog windowExample: Optima Compact Outdoor (WREB) WCDMA BTS information from NetAct's Alarm Dialog window

Figure 25 Faulty fan unit information from NetAct's Alarm Dialog window

You can locate the faulty fan unit from row Diag Info 01 05 01 0000WFDA 00 38. Number 38 is in HEX format and means 56 in decimal. WFDA indicates Fan Driver control board (WFD) which controls WPA, MFUA and HEX fans in the Optima Compact Outdoor (WREB) cabinet. The WAM unit controls the WFD via I²C bus. For more infor-mation on WFD control, see Temperature Control System (TCS) Description.

DN70558202Issue 01D

47



Id:0900d805805fcc5f

3.2 Checking faulty fan units with IPA2800 MML (for example HIT2.8.0)Example: Optima Compact Outdoor (WREB) WCDMA BTS information with IPA2800 MML

Figure 26 Faulty fan unit information with IPA2800 MML

Note that the 'Cabinet door open' alarm in this case refers to the testing environment where the doors are often kept open to help the testing.

With < ZAAP:WBTS,18; command you can get active alarms from the BTS. Row 01 05 01 0000WFDA 00 38 shows the location of the faulty fan unit (in other words, the same information as in NetAct Alarm Dialog window). Note that IPA2800 MML shows the ID number in HEX format. In this case, the ID is 38 which is 56 in decimal.

48 DN70558202Issue 01D


Id:0900d805805fcc5f


3.3 Checking faulty fan units from the WCDMA BTS Site Manager Alarms windowExample: Nokia Optima Compact Outdoor (WREB) WCDMA BTS information from the WCDMA BTS Site Manager Alarms window

Figure 27 Faulty fan unit information from WCDMA BTS Site Manager Alarms window

Fan module operation degraded in the Description field of the Alarms window and BTS: BS 18/WFDA 0/Subunit 56 in the Source field indicate the same information as in the two examples above. Subunit 56 is now in decimal format. Location of the faulty fan can be seen in Figure Fan mapping in Optima Compact Outdoor (WREB) cabinet (in this case, the lower fan of the middle row, behind WPAs). You can locate faulty fan(s) for all the other cabinet types with this same procedure. Note that you should change the whole fan tray if one fan inside the unit is faulty, for example, WFAB alarming fan ID number 48, 49, 50 or 51.

3.4 Checking the failure of the whole Fan Module (WFAx)If the whole fan module fails, the following information about the alarm can be seen with an IPA2800 MML:

DN70558202Issue 01D

49



Id:0900d805805fcc5f

Figure 28 Fan module failure information

Indication of WFAA 01 00 means that fan module WFAA 1 is faulty (i.e. all fans are broken or WFA control board is broken) and the whole module needs to be changed.

Note that it will take altogether one hour to get the fan alarm visible.

Figure 29 BTS Site Manager view when the whole fan module is faulty

50 DN70558202Issue 01D


Id:0900d805805fcc62

Checking antenna line, MHA and Bias-T

4 Checking antenna line, MHA and Bias-TPurposeUse, for example, a Site Master type of equipment to measure the antenna line to be sure that connectors, feeders and antennas are as they should.

Use a spectrum analyser to check that there are no incoming external interferences causing problems in the WCDMA RX channel.

Steps

1 Check that antenna cables (main and diversity) are connected correctly.

2 Re-check antenna line connectors (7/16” connectors with moment 25 Nm).

3 In MHA problems, check first that the commissioning has been done properly. Check that the DC power is going to the MHA (you can also swap the PITA cables between other sectors to check this).

4 Check the VSWR with the Site Master to be sure that connectors, feeders and antennas are ok. Pin 4 in the PITA connector indicates if an alarm is on. Remember that the PITA is mon-itored only by the WAF unit, so no other units are involved in the VSWR monitoring.

Further informationPITA cable connections:

Figure 30 Pinout order at Bias-T end

Continuous DC power handling The unit must be able to withstand a minimum contin-uous DC current of 1000 mA with a voltage supply from 7.5 V to 14.4 V.

VSWR monitoring circuit voltage and current The power to the VSWR monitor circuit shall be supplied through Pin 2 of the PITA connector. Pin 3 is common ground for both MHA and Bias-T monitor circuit. The VSWR alarm

PINOUT OF M8 4 POLE MALECONNECTOR ON BIAS TEE

PIN 1: MHA DC POWER

PIN 2: ALARM CIRCUITDC POWER

PIN 3: DC GROUND

PIN 4: ALARM SIGNAL

BTS PORT7/16 MALE DIN

1

2

3

4

DN70558202Issue 01D

51


Checking antenna line, MHA and Bias-T

Id:0900d805805fcc62

circuits shall operate on voltage level from 7.5 V through 14.4 V. The maximum current to be drawn by the Bias-T alarm circuitry is 50 mA.

Alarm conditions Pin 4 is the open collector line indicator of the BTS.

Under normal (NO Alarm) conditions, the Pin 4 connection is grounded, a logical low will be read by the base station. Under these conditions, Pin 4 must be no more than 0.7 V DC above ground.

Under alarm conditions Pin 4 connection left open or set high, a logical high will be read by the base station. The preferred solution requires that Pin 4 be un-terminated when in alarm, but if this is not possible Pin 4 voltage should be set to +3.3 V DC.

Alarm signal current Pin 4 is the open collector line coming from the BTS. It must be able to withstand up to 50 mA when the alarm is in normal mode. No alarm current should be drawn when the Bias-T is in the alarm mode.

52 DN70558202Issue 01D


Id:0900d805805fcc65

Checking WSMA and WSMB bus errors

5 Checking WSMA and WSMB bus errorsPurposeFollow these instructions to check WSMA ST-bus, T-bus, as well as WSMB RR-bus, SR-bus, ST-bus, and T-bus errors.

Steps

1 Perform a WCDMA loop test and check if some failures can be found.For instructions, see Running a WCDMA loop test.

2 Check that all the cablings between the WSM units are correctly done and firmly connected.For more information, see WSMx-cabling.

3 Check which unit is causing the alarm.For more information, see the Fault source field in the alarm description.

4 Try if you can remove the alarm with a spare unit.Remember to check every unit behind the same bus.

For more information about buses and interfaces, see Signal interfaces.

DN70558202Issue 01D

53


Troubleshooting WCDMA BTS without remote or localconnection possible

Id:0900d805805fcc68

6 Troubleshooting WCDMA BTS without remote or local connection possiblePurposePerform the following steps to solve a WCDMA BTS problem when there is no remote or local connection to the WAM units via WCDMA BTS Site Manager.

Before you startCheck that the PC/firewall settings are not blocking the connection to WAMs.

Steps

1 Check the unit conditions and LEDs.Check if the unit conditions and LED indications are as follows:

• AXC LED is green. • WAMA LEDs are stable red. • WSPx LEDs are blinking yellow. • WSMx LEDs are stable red. • RF part is not operational. • WPS LEDs are green.

2 If there is only one clock unit in the BTS, replace WCS.

3 If replacing WCS does not help, replace WCI.

4 If there are two clock units (redundant WCS) in the BTS, replace WCI.

5 If replacing WCI does not help, replace both WSC units.

Further informationThe LED status listed above indicate that there is a problem with the WCI since WCI produces Baseband Reference Clock (BRCLK) and System Frame Clock (SFCLK) signals for WAM, WSM and WTR units. See figure Nokia UltraSite WCDMA BTS, 1+1+1 configuration, from the SW point of view in Nokia UltraSite WCDMA BTS, 1+1+1 config-uration chapter.

54 DN70558202Issue 01D


Id:0900d805805fcc6b

Checking the'No connection to unit' alarm

7 Checking the'No connection to unit' alarmPurposeThis procedure describes the actions to be taken when the 'No connection to unit' alarm is shown.

Before you startBe careful when changing the cables so that you do not cause problems to other cables.

Steps

1 During a site visit, check cables and connectors visually.

2 Swap the alarming unit with a neighbouring cell and check if the alarm follows the unit. If not, plug the unit back to the original position.

3 If there are several alarming units, check if they belong to the same control bus. If so, correct the bus cabling. Remember that the WSM and RF cables can also be broken, so try to change them, too.

For more information about buses and interfaces, see Signal interfaces.

4 If the alarm still exists, check the backplane cables and connectors.Check the I2C cable carefully because the WCDMA BTS is using this bus for detecting units.

In case of the WTR unit, check that the power cable and connectors between the WTR backplane and the BB subrack are in order (especially that the power cable connectors are firmly connected).

5 If the fault still exists, check that all D-connectors are firmly connected and pins are ok.

6 If the fault still exists, check the spider cable and change it and the D-connector cable related to the alarming unit.

7 Replace the backplane (or backplanes).

Further informationExamples of bad connector contacts and cable assembly due to transport, wrong instal-lation and maintenance work:

DN70558202Issue 01D

55



Id:0900d805805fcc6b

Figure 31 Main power connector not pushed firmly to backplane connector

Figure 32 Oxidized contacts in backplane power connector

56 DN70558202Issue 01D


Id:0900d805805fcc6b


Figure 33 Bad installation in WTR backplane (power connector)

Figure 34 One pin lifted out from the D-9 connector

DN70558202Issue 01D

57



Id:0900d805805fcc6b

Figure 35 Two bent wires in spider cable

58 DN70558202Issue 01D


Id:0900d805805fcc6b


Figure 36 Control cable of IBBU Fan left between backdoor and isolation rubber

DN70558202Issue 01D

59


WSMx cabling

Id:0900d805805fcc6e

8 WSMx cabling This section illustrates the WSMA (rel. 1 HW) and WSMB (rel. 2 HW) cabling as a quick reference to correct cabling. These figures describe a full WSMx-configuration. For more detailed information, see the installation and configuration instructions for UltraSite WCDMA BTS Supreme Indoor and UltraSite WCDMA BTS Optima Compact.

A WCDMA loop test can help you ensure that the WSMx cabling has been done cor-rectly and the cables are working as they should. For instructions, see Running a WCDMA loop test.

8.1 WSMA cabling for rel. 1 HW BTS

Figure 37 WSMA cabling for Supreme cabinet

60 DN70558202Issue 01D


Id:0900d805805fcc6e

WSMx cabling

Figure 38 WSMA cabling for Optima Compact RF extension cabinet

DN70558202Issue 01D

61


WSMx cabling

Id:0900d805805fcc6e

Figure 39 WSMA cabling for Optima Compact IBBU cabinet

62 DN70558202Issue 01D


Id:0900d805805fcc6e

WSMx cabling

8.2 WSMB cabling for rel. 2 HW BTS

Figure 40 WSMB cabling for Supreme cabinet

DN70558202Issue 01D

63


WSMx cabling

Id:0900d805805fcc6e

Figure 41 WSMB cabling for Optima Compact RF extension cabinet

64 DN70558202Issue 01D


Id:0900d805805fcc6e

WSMx cabling

Figure 42 WSMB cabling for Optima Compact IBBU cabinet

DN70558202Issue 01D

65


Backplane cabling with different cabinet types

Id:0900d805805fcc71

9 Backplane cabling with different cabinet types

9.1 WCCA/WINA Nokia Supreme Indoor and WODA Nokia Supreme Outdoor

Figure 43 Bus cabling for Supreme Indoor WCCA/ WINA and Supreme Outdoor WODA cabinets, rear side

Leave 300mm freelenght for the wiresbetween cablesupport andWTRs

Harness manufacturerbundle wires together

= bundling place

66 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 44 HCI cabling for Supreme Indoor WCCA/WINA and Supreme Outdoor WODA cabinets, rear side

DN70558202Issue 01D

67



Id:0900d805805fcc71

9.2 WCCC Nokia Optima Indoor

Figure 45 LVDS harness cables for Optima Indoor cabinet

68 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 46 Spider cabling for Optima Indoor cabinet

Leave 300mm free lenghtfor wires between bundlingplace and WSMs

Leave 150mm free lenghtfor wires between bundlingplace and WTRs

Leave 300mm free lenghtfor wires between bundlingplace and AXU´s and WCIs


DN70558202Issue 01D

69



Id:0900d805805fcc71

9.3 WREA Nokia Optima Compact RF

Figure 47 LVDS harness cables for Optima Compact RF cabinet

70 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 48 Spider cabling for Optima Compact RF cabinet

Leave 300mm free lenghtfor wires between bundlingplace and WSM 0 and WSM 1


Leave 300mm free lenghtfor wires between bundlingplace and WSM 2, AXUsand WCIs

Harness manufacturerfix container with tape


DN70558202Issue 01D

71



Id:0900d805805fcc71

Figure 49 HCI cabling for Optima Compact RF cabinet (RF_1)

72 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 50 HCI cabling for Optima Compact RF cabinet (RF_2)

DN70558202Issue 01D

73



Id:0900d805805fcc71

9.4 WREB Nokia Optima Compact Outdoor

Figure 51 Spider cabling for Optima Compact Outdoor cabinet

Figure 52 HCI cabling, front side of Optima Compact Outdoor cabinet

Leave 300mm free lenghtfor wires between bundlingplace and WSM 0 and WSM 1


Leave 300mm free lenght forwires between bundling placeand WSM 2, AXUs and WCIs


Harness manufacturerfix container with tape

74 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 53 HCI cabling, top side of Optima Compact Outdoor cabinet

9.5 WBBA Nokia Optima Compact IBBU

Figure 54 LVDS harness cables for Optima Compact IBBU cabinet

Note!

1. Cables should be fixed back of the CableHolder (816931)

2. Bundle cables to the Cable Holder (816931)with cable clamb (6401538)

3. There should be enough slack (~100mm) inboth ends of the cable.

4. minimum bend radius 25mm

DN70558202Issue 01D

75



Id:0900d805805fcc71

Figure 55 HCI cabling for Optima Compact IBBU cabinet 1

76 DN70558202Issue 01D


Id:0900d805805fcc71


Figure 56 HCI cabling for Optima Compact IBBU cabinet 2

Note!

There should be enough slack(~100mm) in both ends of thecables to make sure thatmotherboards can be changedfrom the front.

Note!

Route cable 994060_ from theopening between AXC/BB subrackand noise absorbent. Checkthe packing from sheet 1/2.

DN70558202Issue 01D

77


Signal interfaces

Id:0900d805805fcc74

10 Signal interfaces

For more information on how buses connect different units together, see Nokia Ultrasite WCDMA BTS, 1+1+1 configuration. There are other internal bus interfaces which are out of the scope of this document.

For information on power supply architecture, see Power supply architecture.

Interface Description

CIF Carrier Interface between the WAM and transmission sub-system (AXC). It carries user data and user-related signalling and O&M infor-mation from the RNC/NMS.

CLK Clock and synchronisation interface provides frequency reference, operational clocks and other timing signals for the use of other units in the BTS.

R-BUS Receive Bus delivers received samples from the WSM unit to a maximum of six WSPs.

SR-BUS Sector Receive Bus. Samples from adjacent sectors (adjacent WSMs) are received via this interface and are further forwarded towards the R-BUS.

RR-BUS Radio Receive Bus delivers the main and diversity received signal in digital form to the WSM unit for further distribution.

T-BUS Transmit Bus carries spread and summed signals from one WSP to a WSM. The WSM can take input from up to six WSPs simultane-ously.

ST-BUS Sector Transmit Bus. Data intended for transmission in adjacent sectors is delivered via this interface to the adjacent WSMs.

RT-BUS Radio Transmit Bus. The WSM composes the whole carrier data from its own and adjacent sector input and forwards the resulting bit stream to the WTR via the RT-BUS for modulation and up-conver-sion.

DSC-BUS Data, Signalling and Control Bus. This is the 'backbone' of the BTS. All user data and signalling is carried via this interface from the WAM to the WSPs.

Table 4 Signal interfaces

78 DN70558202Issue 01D


Id:0900d8058069333f

Operation and maintenance interfaces

11 Operation and maintenance interfaces

For more information on how buses connect different units together, see Nokia UltraSite WCDMA BTS, 1+1+1 configuration.

Interface Description

ACI Antenna filter control interface. The two WAMs of a subrack are con-nected to the corresponding WIC and WAFs.

CCI Clock control interface. The interface between all WAMs and the WSC used to control the frequency source of the BTS.

HCI Heat control interface. Connects all WAMs to the WEA, WCC, heat exchanger, and the fan unit below the AXC and WSC tray.

OCI O&M and control interface for WSPs. This bus connects the two WAMs of a subrack to all WSPs on the same subrack. The bus is used for WSP serial and version number management, ISTI, and front panel LED control.

SCI Slow speed control interface. This bus is used to connect all WAMs of each subrack to the fan, power supply and WSM of the same subrack.

TLCI WPA and WTR control interface. Both WAMs of a baseband subrack are connected to the corresponding WPA and WTR via this interface for alarm, control, and software download purposes. During a WAM failure, the RF sectors can be saved by transferring the control of a certain RF sector to the neighbouring baseband subrack WAM unit by reconfiguring SW. This function is realised by the Ethernet hubs located inside the WIC units. During the failure, switches to the exten-sion ports are closed and a connection between the neighbouring subracks can be achieved.

Table 5 Operation and maintenance interfaces

DN70558202Issue 01D

79


Nokia UltraSite WCDMA BTS, 1+1+1 configuration

Id:0900d805805fcc7a

12 Nokia UltraSite WCDMA BTS, 1+1+1 configu-ration

Figure 57 Nokia UltraSite WCDMA BTS, 1+1+1 configuration, from the SW point of view

WID

(Identifier)

WPS(Power)

AC / DC

WEA

(Alarm)

WFA

(Fan unit)I2C Bus

LVDS (RS-644)

Analog signal

LVTTL Ethernet / 10Base-T

Serial UTOPIA (LVDS)

RS-232C

Ethernet / 10Base-2

GTL

Fan

ACI-Bus

TLCI-Bus

HCI-Bus

OCI-Bus

LMT

LMT

Powerto units

Powerto units

SCI-Bus

cable

cable

SR-Bus ST-Bus

RX

TX

RR-Bus

RT-Bus

RF Backplane

WTR

WAF

WPA

cable

cable

WIC TX

HUB

SR-Bus ST-Bus

R-Bus

DSC-Bus

T-Bus

Baseband BackplaneTRCLK(LVDS)

BRCLK(LVDS)

SFCLK(LVDS)

WS

PWSMW

SP

Q1cableWCI

WSC WSC

WS

C_

syn

c_

in

WS

C_sync_out

CC

I-Bus

CIF-Bus

WAM

HUB

CTRL ATM

I2C

CD

AIF

Iub

EEPROM

BI-Bus

RNCIFUAXU

80 DN70558202Issue 01D


Id:0900d805805fcc7d

Power supply architecture

13 Power supply architectureThe highlights of the power supply architecture are:

• Blue, green and red units are supplied by blue, green and red WPS, respectively • Brown units have redundant supply

• WSC is supplied by all WPSs (both AC and DC mains) • AXC and WHX have supply from all WPSs when AC mains are used • The heater uses always AC mains • Both AC and DC versions of WPA are available

Figure 58 Power supply architecture

DN70558202Issue 01D

81


Checking HSDPA settings in network elements

Id:0900d80580745418

14 Checking HSDPA settings in network elements

14.1 Setting Windows registry TCP valuesBefore you startBefore changing Windows registry values, store the original registry file as backup and make sure that the PC owner accepts the change of values. Changing values may cause Windows to have operating problems. Check also the UE or mobile vendor rec-ommended parameters.

Steps

1 Start the Registry Editor.

a) Select Start → Run....b) Type regedit.c) Click OK.

Figure 59 Starting Registry Editor.

2 Add or edit the DWORD values.

In the Registry Editor, select Edit → New → DWORD Value.

82 DN70558202Issue 01D


Id:0900d80580745418

Checking HSDPA settings in network elements

Figure 60 Adding or editing DWORD values.

Add the following values to the Parameters folder:

MyComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Name Type Data

TcpWindowSize REG_DWORD 0x7D780 (513920)

Tcp1323Opts REG_DWORD 0x1 (1)

GlobalMaxTcpWindowSize REG_DWORD 0x7D780 (513920)

Table 6 Parameters

DN70558202Issue 01D

83


Id:0900d80580745415

14.2 Checking requirements for WCDMA BTSSW requirementsThe minimum SW requirement is BTS SW WN3.2 release. QPSK modulation with 5 codes and QPSK/16QAM modulation with 5 codes are supported from that release onwards.

Both QPSK and 16QAM modulations with 15 codes are supported in WN4.0 SW or later.

It is recommended to use the latest BTS SW release.

HW requirementsThe use of HSDPA in the UltraSite WCDMA BTS requires that at least one WSPC is installed in the BTS. 16 users per cell requires one WSPC card per cell.

Supported configurationsFor information on supported configurations, see the Release Note document.

Common channels require 16 CEs and HSDPA 32 CEs, so capacity left for users is 16 CEs.

Licence requirementsLicence requirements, see New Features document and other SW release documenta-tion.

Check that the SW in networks is at a level that supports HSDPA, for example RAS05 or later level. Check also core network support for HSDPA.

It is recommended to use the latest SW releases for example with the following upgrade path:

• RNC RN5.0 • AXC C6.0 • BTS WN6.0

After verifying that SW and HW are HSDPA compatible, set HSDPA to enabled with RNW Object Browser (WCDMA Cell).

The HSDPA parameter values recommended below are meant for testing in a laboratory environment. The actual use and field environment parameters are the responsibility of network planners.

WCDMA BTS example parameter values for HSDPA lab testing in trials and pilotsThe WCDMA BTS example parameter values for HSDPA lab testing in trials and pilots for Flexi WCDMA BTS are shown in the following figures.

84 DN70558202Issue 01D


Id:0900d80580745415

Figure 61 General settings

DN70558202Issue 01D

85


Id:0900d80580745415

WCEL level parameters

Figure 62 Ptx offset HSDPA 0.8 dB ok for all WCDMA BTSs

86 DN70558202Issue 01D


Id:0900d80580745415

Figure 63 Enabling HSDPA at the cell

Check also RNC TN78 and BTS TN35.

DN70558202Issue 01D

87


Id:0900d80580745415

Modifications due to less DL output powerSome modifications due to less DL output power for WCDMA BTS Metrosite 8W and WCDMA BTS Triplemode 8W are recommended, especially if HSDPA is tested with other traffic.

88 DN70558202Issue 01D


Id:0900d805805fcc86

14.3 Checking HSDPA throughput problems at BTS or terminal sidePurposeAfter data testing, check the following steps to be able to reach maximum or expected data rates.

Steps

1 Check the HSDPA related Object Browser values.

2 Check the AXC configuration.Full data rate is achievable if the AXC is configured to meet with dimensional require-ments, that is, big enough user plane VCC.

3 Check the AXC SW version.See the WCDMA BTS Compatibility document.

With 5000 PCR used at AAL2 UP, it is safe to get the maximum throughput for QPSK, that is, 1.6 Mbps.

With 10000 PCR used at AAL2 UP, it is safe to get the maximum throughput for 16QAM, that is, 3.4 Mbps.

With 32000 PCR used at AAL2 UP, it is safe to get the maximum throughput for 16QAM, that is, 6.7 Mbps.

The Maximum throughput 13 Mbps needs a 55000 PCR at AAL2UP.

4 Check the user QoS profile.Check that in the UE or terminal IMSI, it has been defined that HSDPA can be used for example for a QPSK check (commands only for a Nokia HLR):

(DWNMAX.MAXIMUM BIT RATE FOR DOWNLINK ....... 1600),

• First, check which QoS profile index is in use: ZMNO:IMSI=xxxxxxxxxxxxxxx:;

• Next, check that the QoS profile index number is equal, using the command: ZMYO:TYPE=QOS:INDEX=___:;

5 Check the PC requirements.

• Encryption in the PC is disabled. • TCP/IP window settings: recommended settings.

6 Check the UE capabilities and vendor requirements for the PC.

7 Check that other network elements besides RAN are defined correctly.Check that there are no data speed limitations, enough user plane in IuPs (that is, between the RNC and SGSN), firewalls, and so on. The used FTP server may also

DN70558202Issue 01D

89


Id:0900d805805fcc86

sometimes limit the data rate. If you have problems, try to use different FTP or UDP applications to see if there is a difference.

8 To test the DL data throughput, use for example FTP in the command prompt, and programs such as the WS FTP. Do not use ping to test DL data throughput.

9 Double check the HSDPA cell parameters from the OMS.The HSDPA capability must be HSDPA capable and the operational HSDSCH state must be enabled.

90 DN70558202Issue 01D


Id:0900d805805fcc89

14.4 Monitoring performance with WCDMA BTS Site ManagerPurposeYou can check the HSDPA-related performance monitoring (PM) values using WCDMA BTS Site Manager.

Checking counters with WCDMA BTS Site Manager was tested with WCDMA BTS SW WN4.0_6.7-104 , with WCDMA BTS Site Manager version 3.0.65.

Before you start

• To get PM files to a WAM ROM and see the graph and values in WCDMA BTS Site Manager, NTP timing has to be set right. You can check this from AXC Manager System Timing; NTP must be OK.

• The OAM link must be working in order to get the graph and values to be monitored using the Application Launcher.

• After a BTS reset, the PM counter files are deleted. It can take about three hours at maximum to get the next PM counter files.

Steps

1 To view measurements; select View → BTS Performance Monitoring.

2 Select the Show by: Counter and Presentation: Graph options.

3 Select the counter you want to view.

Figure 64 Select measurements

DN70558202Issue 01D

91


Id:0900d805805fcc8c

14.5 16QAM check listFollow the basic 16QAM check list to make a 16QAM PS data call with RAS05 or later releases.

BTSRAS05.1 licences required for UltraSite or MetroSite BTS:

• 16QAM licence • No need for Licence based channel capacity licence but the minimum HW require-

ment, 1 WSPC, has to be in the BTS in HSDPA per BTS mode. In HSDPA per cell mode, all cells need a WSPC.

OMS parameters, RNC, and AXC

• RNC SW must be at least RN2.1 GCD1.0 or newer. • Enable the HSDPA cell parameters to use a cell with 16QAM. • WCDMA BTS recommended parameters, see figures below:

• The Shared HSDPA flow control allocation (SHFCA) value must be the same or less than the User Plane value in Mbps.For an example, if you have 2 x E1, the maximum value for SHFCA is 4 Mbits. In case of 4 x E1, the maximum value for SHFCA is 8 Mbits. If the SHFCA value is too high, throughput starts to vary a lot. The BTS puts too much data to User Plane VCC towards the RNC.

• Parameter Shared HSDPA flow control allocation (BTS parameter in RNC) should not exceed the available AAL2 user plane capacity in Mbits if the internal HSDPA flow control method is set to 'none' or 'static' (RNC parameter) or if RAS05 (RN2.1) RNC SW is used.

• HSDPA with Shared HSDPA AAL2 Allocation: If HSDPA is tested without other traffic, the default value 0 Mbps can be used. If testing with a lot of Rel99 traffic, you can reserve IUB capacity in the user plane to be used for HSDPA.

• In the user plane pipe size minimum, UP 10000 PCR is safe for full throughput of 16QAM. The user throughput maximum is approximately 3.3 to 3.4 Mbps.

• With UP 32000 PCR and 16QAM user throughput, the maximum is 6.7 Mbps. • HSUPA with 2 Mbps requires UP 10000 PCR.

92 DN70558202Issue 01D


Id:0900d805805fcc8c

Figure 65 Modify WCEL

DN70558202Issue 01D

93


Id:0900d805805fcc8c

Figure 66 Modify WCDMA BTS

HLR and QoSCheck that the IMSI you are using has a 16QAM QoS profile defined in the HLR. The following QoS profile example was defined in a Nokia Oulu HLR. (Indexes can be selected in other ways.)

HSDPA terminal and the data cardCheck that the 16QAM terminal or the data card is category 6 capable.

CAT 12 QPSK CAT 6 16QAM

Index Datarate (UL/DL) Index Datarate (UL/DL)

220 16/2048 224 16/3600

221 64/2048 225 64/3600

222 128/2048 226 128/3600

223 384/2048 227 384/3600

Table 7 Indexes

94 DN70558202Issue 01D


Id:0900d805805fcc92

14.6 Checking HSPA parameters in RAS06New HSPA features were introduced in RAS06 release. The purpose of these instruc-tions is to gather frequently asked questions about parametrisation for these new features together.

14.6.1 How to get startedCheck with HIT that all the necessary features are activated in the RNC:

• W7I:FEA,FULL:FSTATE=ON,:; • ZWOS;

Enable HSPA from OMS for the tested cells

• HSDPA enabling is in WCEL/AC interleaf. • HSUPA enabling is in WCEL/PS interleaf. (Note that HSUPA must be enabled for

all On Air cells within one BTS using the same carrier frequency. Also HSDPA must be enabled for all HSUPA enabled cells.)

HSDPA mobility must be enabled to HSUPA to work. HSDPA mobility can be enabled from the OMS RNC/HC&PC interleaf:

• SHO of the HSDPA capable UE -> SHO allowed • Serving HS-DSCH cell change and SHO on/off switch -> enabled

If testing MultiRAB HSPA service, usage of AMR with HSPA must be enabled from OMS:

• RNC/HC&PC interleaf : Usage of AMR with E-DCH -> enable • RNC/PS interleaf: Usage of AMR service with HS-DSCH -> enable

14.6.2 HSUPA parametersHSUPA traffic requires either HSUPA or HSPA AAL2 User plane to work (check both CoCo and FTM). For example:

DN70558202Issue 01D

95


Id:0900d805805fcc92

Figure 67 AAL2 User plane definition for HSUPA in CoCo

For the most part, default parameters are suitable for HSUPA testing for as long as the HSUPA parameters previously mentioned in this document are configured.

The HSUPA UL data rate used in the cell can be configured from OMS:

• WCEL/PS interleaf -> Maximum uplink total symbol rate. There are three options: • o 960 ksps (corresponds to about ~700kbps cell throughput) • o 1920 ksps (corresponds to 1.4 Mbit/s cell throughput) • o 3840 ksps (corresponds to 2.0 Mbit/s cell throughput, requires RNC license)

14.6.3 For HSDPA maximum cell throughput, the following parameters should be checked/modified from OMS parametersRNC/PS interleaf:

• HSDPA peak rate limitation to the RAB maximum = no limitation • HSDPA Dynamic Resource Allocation = Enabled

RNC/AC interleaf:

• Number of HS-PDSCH codes for greater RLC PDU size = 5 (For RLC pdu size 656 usage)

• SIR threshold for RLC PDU size 656 with HS-DSCH = Not used (For RLC pdu size 656 usage)

• Maximum bit rate of the MAC-d flow = 9600

96 DN70558202Issue 01D


Id:0900d805805fcc92

• AM RLC status period min for PS NRT with HS-DSCH = 10 (RLC pdu size 336 works better)

• AM RLC status period poll_PDU for PS NRT with HS-DSCH = 1 (RLC pdu size 336 works better)

WCDMA BTS:

• Shared HSDPA flow control allocation: 20Mbps (To get actual throughput, this parameter value is multiplied with ~0.7. For example, in this case 20 Mbps x 0.7 = 14Mbps.)

WCEL/AC interleaf:

• Maximum number of HS-SCCH codes = 2 • Enable 15 codes usage from HS-PDSCH code set (Recommended code set for all

testing is 5, 8, 10, 12, 14, 15.)

COCO:

• AAL2 User plane 50 000 • Internal HSDPA Flow Control Method for BTS = Dynamic

Figure 68 AAL2 User plane VCC settings in CoCo

In addition, the BTS needs to be commissioned so that 48 users per cell option is used (with shared HSDPA scheduler for baseband efficiency, maximum scheduler throughput is only10.8 Mbit/s).

DN70558202Issue 01D

97


Id:0900d805805fcc92

Also depending on the used configuration, the following parameters might need modifi-cation:

WCEL/PC interleaf:

• CPICH

WCEL/AC interleaf:

• Cell maximum transmission power: Default 43 dB works ok for 20W carrier. For 40W carrier 46 dB might improve cell throughput.

• HS-PDSCH code upgrade margin for SF128 codes. With default value 8, only 14 HS-PDSCH codes can be allocated. If this parameter is changed to 0, 15 HS-PDSCH codes can be used.

14.6.4 Miscellaneous parametersRecommended HS-PDSCH code set is 5, 8, 10, 12, 14, 15 (WCEL/AC interleaf).

If HS-PDSCH code set 15 is in use in the cell, NRT DPCH over HS-PDSCH code offset (WCEL/AC interleaf) should be changed from 0 (default) to 10. Otherwise NRT services can not be established in the cell when there are active HSDPA users.

Shared HSDPA scheduler for baseband efficiency requires a BTS license. The sched-uler works only if BTS is commissioned as 16 users/BTS or 16 users/cell. 48 users/cells overrides this license.

If shared scheduler needs to be allocated to certain cells, this can be defined with Frame timing offset of a cell parameter (WCEL/general interleaf). Timing values 0-512 are using same scheduler, values 768-1280 another scheduler, values 1536-2048 to a third scheduler and so on.

98 DN70558202Issue 01D


Id:0900d805805fcc97

BTS Site Manager indicates Missing Cabinet Product Code

15 BTS Site Manager indicates Missing Cabinet Product CodePop-up window showing error when reading product code from WID:

Figure 69 Message about missing cabinet product code

The following checkings must be done:

• Check the WID location and connection/connector inside the cabinet and replace the WID if necessary.

DN70558202Issue 01D

99


BTS Site Manager indicates Missing Cabinet ProductCode

Id:0900d805805fcc97

Figure 70 WID location e.g. in WINA cabinet (rear, bottom left)

100 DN70558202Issue 01D


Id:0900d805805fcc97


Figure 71 WID location e.g. in WINB cabinet (inside WEA module) • Checking e.g. WCCA, WINA, WODA, WINB I2C bus:

Units WEA, WID, TR_WFA, and temperature sensor are controlled with same I2Cbus. In the Supreme indoor cabinet this I2C bus is always controlled by the master WAM, which requires the interconnection of BB1, BB2, BB3 and AXC sub-racks. The cables which constitute this bus are: • BB1 X67 - BB2 X67 (993881) • BB1 X66 - AXC X901 (993880) • BB2 X66-BB3 X67 (993880) • BB3X66 = WID • AXC X905 - WEA X2003. (This cable also carries power to the WEA unit.) • AXC X908 - Cabinet Temperature Sensor (not included in the figure below)

DN70558202Issue 01D

101



Id:0900d805805fcc97

Figure 72 I2C-bus cablings between racks

Some differencies in WINB compareing to WINA:

• WID is integrated on WEA board • Cable code between WEA and BB/AXC is 994725 and connectors are BB/AXC

X3301 – WEACX2005 • Code for the Temperature sensor is 994807 and connector is BB/AXC X3302 • Power feeding to WEA is separate cable compareing to WINA. • In a case of WINB it is recommended to check the fuses too.

102 DN70558202Issue 01D


Id:0900d805805fcc97


Figure 73 Fuse mapping in WINB cabinet

WAF1

WAF2

WAF3

WAF4

WAF5

WAF6

WPA1

WPA2

WPA3

WPA4

WPA5

WPA6

WTR1

WIC1

WTR2

WTR3

WIC3

WIC2

WTR4

WTR5

WTR6

WSM2

WSP7

WSP8

WSP9

WSP10

WSP11

WSP12

WAM3

WAM4

WPS2

WSM3

WSP13

WSP14

WSP15

WSP16

WSP17

WSP18

WAM5

WAM6

WPS3

WFA1 WFA2

WSM1

WSP1

WSP2

WSP3

WSP4

WSP5

WSP6

WAM1

WAM2

WPS1

WSC1

AXU1

IFU1

IFU2

IFU3

IFU4

IFU5/AXU2

WSC2

DN0582912

50A3 pcs

5A

30A

A

B

C

D

E

F

G

H

40A

30A

15A

Fuseand unit

dependency

WEA D

ABC

E

F G

H

Power and unit dependency

WAF1WAF2WTR1WIC1WTR2WSM1WSP1

E WPS1

WSP2WSP3WSP4WSP5WSP6WAM1WAM2

F



WPS2

G



WPS3

AXU1IFU1IFU2IFU3IFU4

H IFU5AXU2WFA1WFA2

DN70558202Issue 01D

103



Id:0900d805805fcc97

Figure 74 I2C-bus cablings between racks (Supreme Outdoor cabinet).

More cabinet backplane cablings in chapter Backplane Cabling with Different Cabinet Types.

104 DN70558202Issue 01D


Id:0900d805806e55e7

Troubleshooting the AXC

16 Troubleshooting the AXC

16.1 Accessing AXC with web browserPurposeThis procedure describes how you can use your web browser for reading AXC alarms, retrieving log files, resetting and recovering the AXC, and performing various other oper-ations.

Steps

1 Open your web browser.

2 Connect to the AXC.Enter the local IP address (192.168.255.129) or remote IP address to the Address field in the web browser.

You can now, for example, view AXC alarms, retrieve AXC log files, view the results of the latest XML parsing and reboot or recover the AXC by clicking on the appropriate link in the web browser.

Note that recovering the AXC resets it to factory default settings and deletes all config-urations including the DCN connection. Recover can be performed only locally.

If you reboot the AXC while logged in as a remote user, make sure the remote user account has Hardware Management change permissions. Click Node → User Management → View Permissions in AXC Manager.

Further informationIf you cannot connect to the AXC, make sure that the LAN settings of your web browser are correct.

In Internet Explorer, click Tools → Internet Options... and select the Connections pane. Click LAN Settings... and check that the settings are as follows:

• "Automatically detect settings" cleared • "Use automatic configuration script" cleared • "Use a proxy server" selected • "Bypass proxy server for local addresses" selected

Proxy settings are needed only when connected locally.

In Netscape Navigator, click Edit → Preferences... and select the Advanced/Proxies pane. Make sure that "Direct connection to the Internet" is selected.

DN70558202Issue 01D

105


Id:0900d805805fcc9d

16.2 Downloading the configuration file fails

DescriptionDownloading the XML configuration file fails. The configuration file is available on either an external FTP server or on the LMT. AXC Manager is connected to the AXC locally or remotely.

Symptoms • XML file download has failed

Recovery proceduresCheck the following in the order they are described.

Check the user permissionsIf you are logged in as a remote user, check the configuration file management permis-sions from Node → User Management → View Permissions in AXC Manager.

Check that username and password are correctCheck that the username and password for the external FTP session are correct. You can do this by opening an FTP session with the DOS command shell prompt. The internal FTP server of AXC Manager is activated automatically during software down-load.

Check that the FTP server is runningIf the external FTP server is used, check that the FTP server is running. The internal FTP server of AXC Manager is activated automatically during software download.

Check that no other FTP servers are running on the LMTCheck that there are no other FTP servers running on the LMT apart from the internal FTP server of AXC Manager, as this can cause port conflicts. Close any other FTP servers.

Check that the access rights of the user are set correctlyCheck that the access rights for the external FTP server are set correctly.

Check the firewall rules and bandwidth for the external FTPIf the external FTP is used, check that the firewall rules are appropriate. Check also that the bandwidth of the DCN is sufficient.

Check the path of the configuration fileCheck that the path of the configuration file is correct.

106 DN70558202Issue 01D


Id:0900d805806e5519

16.3 Configuration file parsing fails

DescriptionAXC Manager is connected to the AXC locally or remotely. The XML configuration file has been downloaded and activated successfully and the node has been booted up. When connecting to the AXC, the configuration is incomplete or completely missing.

Symptoms • XML file parsing has failed

Recovery procedures

Check the configuration fileUse the information in the parsing log file (AML_PARSING.LOG) to check the objects whose creation failed in the XML configuration file. See Accessing AXC with web browser for instructions on how to retrieve the information.

Check the parsing log file for errors and go through the problematic sections of the XML configuration file carefully. Contact your planning department and ask them to check the file or provide a new one for this site.

DN70558202Issue 01D

107


Id:0900d805806932ab

16.4 AXC Manager does not start up

DescriptionAXC Manager does not start up from the Start menu (Start → Programs → AXC Manager).

Symptoms • the application does not open • an error message is displayed

Recovery proceduresCheck the following in the order they are described. Try to start AXC Manager after each recovery action.

Delete all processes called AXCEMStart.exeOpen Task Manager and delete all processes called AXCEMStart.exe.

Check that regional settings are correctCheck that regional settings of the Local Management Tool are as required. Only one of the following settings is allowed: English (United States, United Kingdom, Ireland), Finnish or German (Standard).

Reboot the LMTRestart the Local Management Tool.

Reinstall AXC ManagerReinstall AXC Manager on the LMT. For more information, see Installing AXC Manager from NOLS.

108 DN70558202Issue 01D


Id:0900d805805fcca6

16.5 AXU LED remains yellow

DescriptionThe LED of the ATM Cross-connect Unit (AXU) remains yellow when it is installed to AXC.

The boot time depends on the configuration and can be up to 5 minutes. As long as the AXU LED is yellow, AXC cannot be operated.

Symptoms • the AXU LED is yellow • no connection possible • the IFU LED is also yellow


Check the plug-in unitsMake sure that the AXU and the interface units are installed in the correct slots. Check that they are completely plugged in.

Reset the AXC nodeSwitch the AXC off and start it again. Wait for a while to see if the AXU LED switches to green. It is recommended that you try to reset the AXC manually several times.

Delete AXC system configuration informationIf the AXU LED stays yellow after several manual resets, it is possible that AXC system configuration information is corrupted and must be deleted.

Connect to the AXC locally as instructed in Accessing AXC with web browser and click Recover.The AXC resets and comes up with factory default settings. Use the configuration back-up file to restore the configuration of the AXC or re-commission the AXC manually with AXC Manager.

DN70558202Issue 01D

109


Id:0900d805805fcca9

16.6 Local connection to AXC cannot be established

DescriptionLocal connection to the AXC cannot be established with AXC Manager (File → Connect).

Symptoms • no connection can be established • a CORBA error occurs • there are errors during the reading of the IOR file

Recovery proceduresCheck the following in the order they are described. Try to connect to the AXC after each recovery action.

Check that the LAN cable is of the correct typeCheck that you are using a crossed Ethernet cable with RJ-45 connector.

Check also that the Ethernet interface of the LMT PC is configured to 10 Mbit/s half-duplex.

Check your personal firewallMake sure that the IP address of the AXC is included in the friend list of your personal firewall or remove the firewall.

You must also clear "Check Point SecuRemote" check box. In Windows 2000, you can find it from Settings → Network/Dial-up Connections → Local Area Connection Proper-ties.

Check that communications between the LMT and AXC worksCheck that the communications between the LMT and the AXC works using the ping command. To do this, open a DOS prompt window and enter the following command: ping 192.168.255.129.

Check that the IP addresses of the AXC and LMT and make sure that their subnets fit together.

Check that AXC Manager is compatible with AXC software and hardwareCheck that AXC Manager is compatible with the installed AXC hardware and software. Each AXC software release has to be used with a dedicated AXC Manager.

Check that username and password are correctCheck that the username and password are correct. The default username is "Nemuad-min" and default password "nemuuser".

Restart AXC ManagerClose and restart AXC Manager.

Reboot the LMTRestart the Local Management Tool.

110 DN70558202Issue 01D


Id:0900d805805fcca9

Reinstall AXC Manager Reinstall AXC Manager on the LMT. For more information, see Installing AXC Manager from NOLS.

Restart the AXCRestart the AXC.

DN70558202Issue 01D

111


Id:0900d805805fccac

16.7 IFU cannot be installed to S-AXC

DescriptionInstallation of an interface unit to the Stand-alone AXC is unsuccessful.

Symptoms • the unit does not boot automatically when installed to the Stand-alone AXC

Recovery procedures

Check for alarm 61202Check whether the alarm 61202 SW version mismatch is active and update the software if necessary.

Check the fan unit jumper settingsIf the S-AXC fan unit is of the type that has jumpers, check the jumper settings against Fan unit jumper settings. Change the settings if necessary.

112 DN70558202Issue 01D


Id:0900d805805fccaf

16.8 Remote IP connection to AXC fails

DescriptionRemote IP connection to AXC is not working correctly.

Symptoms • no connection can be established • AXC cannot be pinged


Check the active alarmsCheck which alarms are active in the network.

Check the IP addressCheck that the IP address of the AXC is correct. Try to ping the AXC with the address. Check the IP address of the LMT.

You can also use the traceroute tool to try to locate the part of the network in which the problem resides.

Check that the bandwidth is sufficientCheck that the bandwidth reserved within the DCN connection is sufficient. The band-width must be at least 150 cells/s.

If possible, reduce the amount of CBR traffic over the same line.

Check ATM parametersCheck the following ATM parameters in the RNC and modify them if necessary:

• policing • Cell Delay Variation Tolerance • conformance definition • service category • shaping

Recreate the IP over ATM settings of the RNCDelete the IP over ATM settings for this AXC in the RNC and recreate them.

Visit the siteGo to the site and continue with local troubleshooting instructions.

DN70558202Issue 01D

113


Id:0900d805806e5521

16.9 Remote management connection to AXC fails

DescriptionRemote management connection to AXC is not working correctly.

Symptoms • AXC can be pinged (if not, see Remote IP connection to AXC fails) • a CORBA error occurs • there are errors during the reading of the IOR file


Check account informationCheck that the username, password and IP address are correct in the Connect dialog of AXC Manager. The default username is "Nemuadmin" and password "nemuuser".

Restart AXC ManagerClose and restart AXC Manager.

Reset the AXC remotelyReset the AXC using the web interface.

Continue with local troubleshootingGo to the site and continue with the local troubleshooting instructions.

114 DN70558202Issue 01D


Id:0900d805805fccb5

16.10 AXU or IFU is continuously resetting

DescriptionAXU or IFU is continuously resetting.

Symptoms • AXU or IFU is continuously resetting • AXC behaves in an unusual way

Recovery procedures

Reboot the AXCReboot the AXC manually.

Recreate AXC system configuration information remotelyIf AXC behaves in an unusual way, it is possible that AXC system configuration informa-tion is corrupted and must be re-created. You can do this remotely as follows:

1. Connect to AXC with AXC Manager.2. Export the current configuration by selecting Node → Export Configuration....

You can also use a back-up of the current configuration if it is available.3. Import the same configuration by selecting Node → Import Configuration... and

activate it. For detailed instructions, see Modifying AXC configuration with XML con-figuration file.

DN70558202Issue 01D

115


Id:0900d805806e5530

16.11 Configuration is lost after software update

DescriptionConfiguration is not correctly maintained across the software update of AXC.

Symptoms • AXC has lost settings • AXC starts with factory default configuration after the software update • remote management connection is lost after software update

For more information, see Changing AXC software.


Check whether RNC and other DCN network elements work correctlyIf the remote management connection is not working, check carefully and reconfigure RNC and IP over ATM, for example, before going to the site.

Check the results of the XML downloadGo to the site and check the parsing log. For more information, see Configuration file parsing fails.

If possible correct the XML file and perform an automated commissioning proce-dureUpload the AXC configuration in an XML file via AXC Manager. Correct the XML file, download it to the AXC and activate it. For more information, see Commissioning the AXC with XML configuration file.

Perform an automated commissioning procedure with a configuration back-up XML fileDownload the back-up XML file and activate it. For more information, see Commission-ing the AXC with XML configuration file.

116 DN70558202Issue 01D


Id:0900d805805fccbc

16.12 Software update fails

DescriptionUpdating the software of the AXC is unsuccessful.

Symptoms • download or activation of the software has failed. You can check the success of the

activation from the Node Software window. For more information, see Changing AXC software.


Check the software update instructionsCheck the software update instructions that are included in the Release Binder. The instructions contain the latest information on how to update the AXC software.

Check the user permissionsIf you are logged in as a remote user, check the software management permissions from Node → User Management → View Permissions in AXC Manager.

Check that the node runs the software of the previous releaseCheck that the node that you are updating runs the software of the previous release. You can check the software version in the AXC by selecting Node → Software.

Check that username and password are correctCheck that the username and password for the external FTP session are correct. The integrated FTP server is activated automatically during software download.

Check that the FTP server is runningIf an external FTP server is used, check that the FTP server is running. The integrated FTP server is activated automatically during software download.

Check that no other FTP servers are running on the LMTCheck that there is no other FTP server running on the LMT apart from the integrated FTP server, as this can cause a port conflict. Close all other FTP servers.

Check that the access rights of the users are set correctlyCheck that the access rights for the external FTP server are set correctly. See relevant documentation for more information.

Check the path of the software package in the Target Build DescriptorIf an external FTP server is used the path specified in the Target Build Descriptor should be relative to the root directory specified for the FTP server. This is not required for the integrated FTP server.

Troubleshooting Ultra Site and Metro Site Base Station

Documents

target build descriptor

processes called axcemstart

ethernet 10base

optima compact outdoor

corba error occurs

local management tool

dl output power

nokia siemens networks