Troubleshooting Sbts 19a

Single RAN, Rel.
SRAN 19A,
Operating Documentation,
Issue 01
Troubleshooting SBTS
DN09249569
Issue 01
Approval Date 2019-07-15
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
Copyright © 2019 Nokia. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
2 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

Table of Contents
This document has 128 pages
Summary of changes................................................................... 10
1 Troubleshooting methodology...................................................... 11
2 Monitoring SBTS.......................................................................... 12
2.1 Hardware and software monitoring.............................................. 12
2.1.1 Handling faults and alarms ..........................................................12
2.1.2 Fault and alarm troubleshooting outline....................................... 12
2.1.3 Viewing faults and alarms in Web Element Manager...................13
2.1.3.1 Site View...................................................................................... 13
2.1.3.2 Detailed Site View........................................................................ 14
2.1.3.3 Alarms in WebEM.........................................................................17
2.1.4 Alarm monitoring in NetAct.......................................................... 18
2.1.5 LED indications............................................................................ 19
2.1.5.1 Nokia AirScale System Module LED indicators........................... 19
2.1.5.2 LEDs of the Flexi Multiradio 10.................................................... 22
2.1.5.2.1 LEDs of the Flexi Multiradio 10 System Module (FSMF)............. 22
2.1.5.2.2 LEDs of the capacity extension sub-module (FBBA)................... 23
2.1.5.2.3 LEDs of the capacity extension sub-module (FBBC)................... 24
2.1.5.2.4 LEDs of the Flexi Multiradio 10 System Module (FSIH)...............25
2.1.5.2.5 LEDs of the capacity extension sub-module (FBIH).................... 27
2.2 Performance monitoring...............................................................28
2.2.1 Viewing counters and KPIs in Web Element Manager.................28
2.2.1.1 Performance Management view.................................................. 29
2.2.1.2 PM counter data...........................................................................30
2.2.1.3 KPI Dashboard.............................................................................31
2.2.2 Performance monitoring in NetAct............................................... 32
2.2.3 Network monitoring using Traffica................................................32
2.2.3.1 Traffica general use case for LTE troubleshooting....................... 33
2.3 Diagnostic tools in WebEM.......................................................... 34
2.3.1 Synchronization view................................................................... 34
2.3.2 IP Connectivity Test......................................................................35
2.3.3 RF Diagnostic Test....................................................................... 36
2.3.4 EAC Functionality Test................................................................. 36
2.3.5 Ethernet Port Mirroring.................................................................37
2.3.6 IP Traffic Capturing...................................................................... 38
2.3.7 SFP Monitoring............................................................................ 38
2.3.8 Antenna Line Online Monitoring...................................................39
2.3.9 RF Monitoring ..............................................................................39
2.3.9.1 PIM Desensitization..................................................................... 39
2.3.9.2 Distance to PIM (DTP)................................................................. 40
2.3.9.3 RF Scan....................................................................................... 40
DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 3

2.3.10 Test Models.................................................................................. 40

2.3.10.1 LTE Downlink............................................................................... 41
2.3.10.2 LTE Uplink.................................................................................... 41
2.3.10.3 WCDMA Downlink........................................................................41
2.3.10.4 WCDMA Uplink............................................................................ 42
2.3.10.5 GSM BCCH Transmission............................................................42
2.3.10.6 GSM Loop Test............................................................................ 43
2.3.11 Terminal........................................................................................43
2.3.12 Reset to Test Dedicated State......................................................43
2.3.13 TWAMP RTT Measurements....................................................... 43
2.3.14 Ethernet Link OAM.......................................................................44
2.3.15 Ethernet Service OAM................................................................. 45
2.3.16 PPP Interfaces............................................................................. 46
2.3.17 IP Routing.................................................................................... 46
2.3.17.1 IPv4/IPv6 Routing........................................................................ 46
2.3.17.2 Routing Policies........................................................................... 47
2.3.18 IP Security Associations...............................................................47
2.3.19 PMTU Discovery.......................................................................... 48
2.3.20 GSM Traffic Trace........................................................................ 48
2.3.21 PDH Loopback............................................................................. 49
3 Collecting and analyzing troubleshooting data.............................50

3.1 Common logs............................................................................... 50
3.1.1 BTS snapshot...............................................................................50
3.1.1.1 Snapshot preconditions................................................................51
3.1.1.2 BTS snapshot content..................................................................51
3.1.1.3 Saving a BTS snapshot file using Web Element Manager...........52
3.1.1.4 Changing RnD parameters using WebEM................................... 54
3.1.2 Taking IM snapshots with WebEM............................................... 56
3.1.3 WebEM logs................................................................................. 56
3.1.3.1 Collecting application logs............................................................56
3.1.3.2 Collecting browser console logs (JAVA logs)............................... 56
3.1.3.3 Collecting browser network logs (HAR logs)................................58
3.1.4 Transport related logs.................................................................. 59
3.1.4.1 Wireshark Traces......................................................................... 59
3.1.4.2 Local and remote IP traffic capturing on Flexi Multiradio 10 and
AirScale........................................................................................59
3.1.4.2.1 Activating IP traffic data capturing in streaming mode................. 60
3.1.4.2.2 Activating IP traffic data capturing in file mode............................ 62
3.1.4.2.3 Limitations for IP traffic capturing................................................. 63
3.2 GSM related logs......................................................................... 64
3.2.1 BTS logs.......................................................................................64
3.2.2 BSC logs...................................................................................... 65
3.2.3 Tools.............................................................................................66
3.3 WCDMA related logs....................................................................66
3.3.1 Reporting Suite and Default Reports........................................... 66

3.3.2 RNC logs...................................................................................... 66

3.4 LTE related logs........................................................................... 67
3.4.1 Cell trace...................................................................................... 68
3.4.1.1 Cell trace content......................................................................... 68
3.4.1.2 Activating trace ............................................................................69
3.4.1.3 Viewing and analyzing cell trace data using L3DA...................... 70
3.4.1.4 Tracing with NetAct...................................................................... 71
3.5 BTSMED...................................................................................... 72
3.6 RF related logs.............................................................................72
4 Basic troubleshooting steps......................................................... 73

4.1 Blocking and unblocking BTS units..............................................73
4.2 Resetting BTS units..................................................................... 75
4.3 RAT reset..................................................................................... 76
5 Advanced troubleshooting use cases.......................................... 78

5.1 Common.......................................................................................78
5.1.1 Software problems....................................................................... 78
5.1.1.1 Viewing software download report............................................... 78
5.1.1.2 Reset to failsafe partition..............................................................80
5.1.1.2.1 Reset to failsafe partition - case 1................................................80
5.1.1.2.2 Reset to failsafe partition - case 2................................................81
5.1.2 Synchronization problems............................................................81
5.1.2.1 GPS problems – synchronization source not detected................ 81
5.1.2.2 GPS problems – FYGA module is not detected...........................82
5.1.2.3 Fallback solution for phase synchronization................................ 83
5.1.3 Hardware problems......................................................................84
5.1.3.1 Performing routine maintenance tasks.........................................84
5.1.3.2 Identification of faulty units...........................................................88
5.1.3.3 Troubleshooting transmission module..........................................89
5.1.3.3.1 Dead peer detected (error in SCTP)............................................ 89
5.1.3.3.2 Ethernet interface is not working..................................................90
5.1.3.4 Troubleshooting system module.................................................. 91
5.1.3.4.1 Recovering system module with RFS tool................................... 91
5.1.4 Radio module problems............................................................... 98
5.1.4.1 RRH troubleshooting outline........................................................ 98
5.1.4.2 Finding faults in a snapshot file....................................................99
5.1.4.3 Maintaining optical fibers............................................................100
5.1.4.3.1 Cleaning optical fiber..................................................................102
5.1.4.4 Fault ID 3030: Failure in optical interface...................................103
5.1.4.5 Fault ID 4309 and 4310: Connection unstable...........................105
5.1.4.6 Radio module performs autonomous reset................................ 106
5.1.4.7 Optical cable connection issue with FRGU, FRMF and FXEE
radios......................................................................................... 106
5.1.4.8 CPRI-A radio issues in a Nokia network.................................... 109
5.1.5 Finding information about reset reasons in a snapshot file........ 110
5.1.6 Antenna line device problems.....................................................111

5.1.6.1 Antenna line, VSWR, and MHA troubleshooting outline.............111

5.1.6.2 Radio Access Server (RAS), Remote Electrical Tilt (RET)
troubleshooting guide................................................................. 113
5.1.6.3 RET is not detected.................................................................... 113
5.1.6.4 RET is not calibrated or it is jammed..........................................114
5.2 WCDMA use cases.................................................................... 115
5.2.1 KPI degradation..........................................................................115
5.2.2 Sleeping cell............................................................................... 116
5.3 LTE use cases............................................................................ 117
5.3.1 Cell is not in "onAir" state........................................................... 118
5.3.2 Sleeping cell............................................................................... 119
5.3.3 Call processing problems...........................................................120
5.3.3.1 Troubleshooting call processing problems ................................ 120
5.3.3.2 Parameters influencing call establishing and processing...........121
5.3.3.3 Data related to high RRC setup failure rate and RACH problems...
125
5.3.3.4 Data related to RAB setup problems..........................................125
5.3.3.5 VoLTE/ViLTE call drops when LTE1321 is enabled in the network..
126
5.3.4 BTS crash or reset..................................................................... 127
5.3.4.1 BTS in a reset loop.....................................................................127

List of Figures
Figure 1 Troubleshooting methodology ............................................................11
Figure 2 Site View.............................................................................................13
Figure 3 Site action options.............................................................................. 14
Figure 4 Detailed Site View............................................................................. 15
Figure 5 System module marked as master..................................................... 16
Figure 6 Site action options.............................................................................. 17
Figure 7 IoT cells in Site Runtime View............................................................ 17
Figure 8 Location of ASIA LED indicators........................................................ 19
Figure 9 Location of ASIB LED indicators........................................................ 19
Figure 10 Location of ABIA LED indicators........................................................ 20
Figure 11 LEDs of the Flexi Multiradio 10 System Module (FSMF)....................22
Figure 12 LEDs of the capacity extension sub-module (FBBA)..........................24
Figure 13 LEDs of the capacity extension sub-module (FBBC)......................... 25
Figure 14 LEDs of the Flexi Multiradio 10 System Module (FSIH)..................... 26
Figure 15 LEDs of the capacity extension sub-module (FBIH)...........................27
Figure 16 Performance monitoring data useful for troubleshooting....................28
Figure 17 Table View.......................................................................................... 29
Figure 18 Plot View.............................................................................................29
Figure 19 BTS Counters function in WebEM...................................................... 31
Figure 20 KPI Dashboard..................................................................................32
Figure 21 Ethernet Port Mirroring....................................................................... 37
Figure 22 Capture point options for IP traffic capturing ..................................... 38
Figure 23 LTE Downlink tab view...................................................................... 41
Figure 24 LTE Uplink tab view........................................................................... 41
Figure 25 WCDMA Downlink tab view.............................................................. 42
Figure 26 WCDMA Uplink tab view................................................................... 42
Figure 27 BTS site information........................................................................... 43
Figure 28 Checking critical link events............................................................... 45
Figure 29 GSM Traffic Trace view...................................................................... 49
Figure 30 PDH Loopback................................................................................... 49
Figure 31 Snapshot functionality in WebEM....................................................... 52
Figure 32 Snapshot collection settings............................................................... 53
Figure 33 Selecting the target location............................................................... 54
Figure 34 WebEM window.................................................................................. 55
Figure 35 WebEM Change BTS RnD parameters window................................. 55
Figure 36 IP traffic capturing setup in WebEM for FSMF................................... 61
Figure 37 IP traffic capturing setup in WebEM for AirScale................................62
Figure 38 IP traffic capturing setup in WebEM for FSMF................................... 63
Figure 39 IP traffic capturing setup in WebEM for AirScale................................63

Figure 40 Overview of symptoms for call processing related problems............. 67

Figure 41 Details pane for the unit selected for blocking or unblocking............. 74
Figure 42 Confirmation window for the blocking or unblocking action of a unit......
74
Figure 43 Details pane for the unit selected for reset......................................... 76
Figure 44 Confirmation window for the reset action of a unit..............................76
Figure 45 Site Status bar.................................................................................... 77
Figure 46 Reset confirmation..............................................................................77
Figure 47 Software update failed message........................................................ 79
Figure 48 Software update report....................................................................... 80
Figure 49 LMP IP plug installed..........................................................................85
Figure 50 LMP port IP cap not reinstalled after maintenance.............................85
Figure 51 Connector IP boot correctly installed firmly in place...........................86
Figure 52 Connector IP boot incorrectly installed (IP seals not firmly in place on
any edge)............................................................................................86
Figure 53 Connector IP boot incorrectly installed (not pushed all the way in).... 87
Figure 54 Cable installed without IP boot........................................................... 87
Figure 55 Target BTS software located in the RFS tool directory.......................92
Figure 56 Result view 1...................................................................................... 93
Figure 60 Finding an alarm ID in RawAlarmHistory.txt file................................. 99
Figure 61 Physically damaged fiber..................................................................100
Figure 62 Fiber test equipment.........................................................................101
Figure 63 Fiber cleaner.....................................................................................102
Figure 64 Example of connector cleaner.......................................................... 102
Figure 65 Example of how to clean a fiber....................................................... 103
Figure 66 Example of how to clean a fiber....................................................... 103
Figure 67 A. Installing optical cable connector seal B. Collision between
connector seal and latch...................................................................107
Figure 68 Problematic and non-problematic connectors.................................. 108
Figure 69 Removing connector locking release latch....................................... 108
Figure 70 Information about reset reasons in the BTSxxxx_1011_blackbox
file......................................................................................................111
Figure 71 Table of parameters.......................................................................... 116

List of Tables
Table 1 RAT releases covered by the document.............................................10
Table 2 LED indicators.................................................................................... 20
Table 3 LEDs of the Flexi Multiradio 10 System Module (FSMF)....................22
Table 4 LEDs of the capacity extension sub-module (FBBA) .........................24
Table 5 LEDs of the capacity extension sub-module (FBBC) ........................ 25
Table 6 LEDs of the Flexi Multiradio 10 System Module (FSIH)..................... 26
Table 7 LEDs of the capacity extension sub-module (FBIH)...........................27
Table 8 Required logs for GSM call processing.............................................. 64
Table 9 Tools needed for log collection........................................................... 66
Table 10 Explanation of NetAct Diagnostic Info paths...................................... 88
Table 11 Visual identification of SFPs and fibers............................................ 104
Table 12 LTE use cases.................................................................................. 117
Table 13 Parameters influencing establishing of call...................................... 121
Table 14 Parameters influencing call processing............................................ 121

Summary of changes Troubleshooting SBTS
Summary of changes
A list of changes between document issues. You can navigate through the respective
changed topics.
This document is based on the document SBTS Troubleshooting, release 19, Issue 01.
This document is common for all Radio Access Technologies (RAT). You can find here
information about solutions that are not available or supported in a specific SW release
or RAT. Table: RAT releases covered by the document lists all SW releases covered by
the content of this document. For features supported in your SW release, see the
respective feature documentation in the system library.
Table 1 RAT releases covered by the document
Radio Access Technology (RAT) Release
SRAN SRAN 19A
GSM GSM 19A
WCDMA WCDMA 19A
LTE LTE 19A
This is the first issue of the document.

Troubleshooting SBTS Troubleshooting methodology
1 Troubleshooting methodology
The troubleshooting methodology consists of the following procedures: monitoring,
collecting and analyzing data and finding root cause
The following figure presents a general example of the procedures performed and tools
used by the troubleshooting personnel.
Figure 1 Troubleshooting methodology
The order of actions and the selection of tools might vary depending on the use case and
operator preferences.
It depends on the nature of a problem if the root cause analysis is performed by the
operator (for example, site configuration-related problems) or by Nokia Services (for
example, defects inside a product). If it is not possible to find the root cause of the
problems, Nokia Services should be contacted.

Monitoring SBTS Troubleshooting SBTS
2 Monitoring SBTS
Monitoring of the network allows the operator to notice potential problems and unwanted
behaviors.
Network monitoring consists of:
• hardware and software monitoring (using faults and alarms)

• performance monitoring (using key performance indicators and counters)
Particular SBTS sites can be monitored using the element manager. NetAct and Traffica
applications allows the operator to monitor the whole network.
2.1 Hardware and software monitoring

Hardware and software can be monitored using faults, alarms, and LED indicators.
2.1.1 Handling faults and alarms

Issues with software or hardware are signaled using faults, which in turn raise alarms.
Fault messages come either from hardware devices or software components. The faults
are system-specific or hardware-specific. Faults are mapped to corresponding alarms,
which are sent to the element manager and to NetAct. Faults can also trigger LED
indicators.
The BTS can detect faults after it has been commissioned and it is in a configured state.
During the start-up, the BTS waits for the real-time clock from the Network Time Protocol
(NTP) server, and the fault diagnosis starts after the time has been set, or a time-out has
been detected. If the BTS cannot set the time using the NTP server, the default time (that
is 1.1.2004) is used.
When starting to solve a problem, first see the instructions given in an individual alarm
description (see the fields Fault source and Instructions in the alarm description).
2.1.2 Fault and alarm troubleshooting outline

Instructions on how to check the BTS faults and LED states
Procedure
1 Establish a connection with the BTS using the element manager.
2 Read the fault and alarm information.
For more information, see Viewing faults and alarms in Web Element Manager.

Troubleshooting SBTS Monitoring SBTS
3 Check the unit states signaled by LEDs.
For descriptions of a module's LED states, see LED indications.
2.1.3 Viewing faults and alarms in Web Element Manager

The Web Element Manger provide the possibility to view faults and alarms in: site view,
detailed site view, and alarms management menu.
2.1.3.1 Site View
This view shows the layout and related information.
Access to Site View view: Top Menu ► BTS Status ► Site Runtime View ► Site
View
Site View shows the hardware available on the site and configured cells.
Figure 2 Site View
Elements showed in Site View can by filtered by:

Hardware
• Show all
• SMODs/BBMODs
• External SMODs
• BTS Mediators
• BTS Controllers
• Fronthaul switches
• MHAs/LNAs

• RETs/RETUs
• RAEs/RAEUs
RATs
• Show all
• LTE
• WCDMA
• GSM
Radio ports
• Show all ports

• Show only used ports
In Site View, some alarms can appear. If an alarm occurs in a particular unit, it is
indicated by the alarm icon (the color of the icon represents the severity of the alarm).
In case of multiple alarms, the alarm icon on a particular unit indicates only the highest
severity, although there may be other alarms. To see the list of alarms for a unit, go to
the Details panel and open a Faults tab. To see even more details about an alarm, use
the icon to go to the Alarm Management view. The list of alarms is also visible on a
tooltip for that alarm.
The Export as image icon allows the user to save the site view in PNG format.
In configurations with two FSMF system modules, the modules are displayed in two
separate cabinets, due to the physical placement of the modules. In configurations with
two ASIA or ASIAA system modules, the modules are displayed in one cabinet.
Selecting any of the elements allows the user to see their details such as basic
information (state, name, and so on), and related parameters and faults, when the
Details panel is expanded. When applicable, some items can be reset, blocked or
unblocked using the appropriate buttons from the Details panel.
At the top of the view there are site action options, used to block the BCF, reset the site
or block and unblock the site. Note that the unblock site function causes the entire BTS
to reset.
Figure 3 Site action options
2.1.3.2 Detailed Site View
This view shows the layout and related information.
Access to Detailed Site View view: Top Menu ► BTS Status ► Site Runtime View
► Detailed Site View
Detailed Site View shows the hardware available on the site and configured cells, as
well as physical and logical links between them (including used ports).

Figure 4 Detailed Site View
Export Show Show Site

asimage filters sortitems Unitstatus actionoptions
Show
ChannelRelations
Connections between site elements and Antenna Line Devices (ALDs) can be filtered
from the upper menu. Note that the displayed fiber lengths might differ from the actual
lengths.
Available filters:
• Cell carriers:
– Show cell carriers
• ALDs:
– Show all
– Show MHAs
– Show RETs
– Show RAEs
• ALD links:
– Show all
– Show configuration links
– Show data links
– Show DC links
– Show RET unit associations
All elements can be sorted. FHSs, RMODs and ALDs can be sorted by:
• Configuration ID
• Product name
• State

ALDs can be also sorted by HW type.

Cells can be sorted by:
• Configuration ID
• Band
• State
In Detailed Site View, some alarms can appear. If an alarm occurs in a particular unit, it
is indicated by the alarm icon (the color of the icon represents the severity of the
alarm). In case of multiple alarms, the alarm icon on a particular unit indicates only the
highest severity, although there may be other alarms. To see the list of alarms for that
unit, go to the Details panel and open the Faults tab. To see even more details about
the alarm, use the icon to go to the Alarm Management view. A list of alarms is also
visible on a tooltip for that alarm.
The Export as image icon allows the user to save the site view in PNG format.
Selecting the cabinet allows the user to see its details such as basic information (state,
name, and so on), and related parameters and faults, when the Details panel is
expanded. The Show physical cabinet button opens a pop-up view displaying the
hardware available in the cabinet (including hardware names and port names). Clicking
anywhere outside the pop-up window closes it.
In configurations with two FSMF system modules, the modules are displayed in two
separate cabinets, due to the physical placement of the modules. In configurations with
two ASIA or ASIAA system modules, the modules are displayed in one cabinet.
The master module is marked by the M icon.
Figure 5 System module marked as master
Selecting any of the modules, physical connectors, antenna connectors, cells or carriers,
allows the user to see their details such as basic information (state, name, and so on),
and related parameters and faults, when the Details panel is expanded. The Show
Channel Relation button highlights links and other objects connected to a selected
object. If a channel is selected, all the hardware through which data is routed, or
elements creating that channel are highlighted. If the selected object is a unit, the button
shows the relation between all channels creating or routing data to or from it. If a cell is
selected, the button shows the channel relation for this cell.
The Diagnostics button opens the diagnostics for the selected transport unit. When
applicable, units, cells or GSM TRXs can be reset, blocked or unblocked using the
appropriate buttons from the Details panel. The icon informs about ongoing
procedures for objects. A list of procedures is on a tooltip of this icon. The icon
indicates a blocked object.

At the top of the view there are site action options, used to block the BCF, reset the site
or block and unblock the site. Note that the unblock site function causes the entire BTS
to reset.
Figure 6 Site action options
Other icons that might appear on objects:

•
- active UEs in LTE cell
•
- not configured hardware
•
- external ALD
•
- satellite count
In case any inband or guardband IoT cells are configured on the BTS, these are
represented in Runtime View next to the hosting FDD-LTE cell.
Figure 7 IoT cells in Site Runtime View
2.1.3.3 Alarms in WebEM
Alarm Management allows to see details on active BTS faults as well as fault history.
Access to Active Alarms view: Alarms ► Alarm Management ► Active Alarms

Access to Alarm History view: Alarms ► Alarm Management ► Alarm History
Alarm Management is divided into two tabs: Active Alarms showing the actual (real-
time) data about BTS faults, and Alarm History showing the historical data. Both tabs
are configured and navigated in exactly the same way.

g Note: The alarms in the Alarm History tab are available only when history is loaded in
the Navigation Panel.
Details of a selected alarm, such as time of appearance, description, and instructions on

how to deal with the fault, are visible in the Details panel.
Alarms can be sorted using the text field and ordered by severity or impacted RAT using
the Appeared column.
The Show Source button in the Details panel navigates to the Detailed Site View and
selects the object that triggered the alarm.
The Objects tab in the Navigation Panel can be used to filter alarms by the related
managed object.
Historical information goes back to a maximum of 24 hours or the last BTS reset.
Faults can be filtered by using:
• Text field to filter any alarm names, IDs, dates, objects that triggered the alarm
containing the provided text fragment.
• Alarm type:
– Critical alarms, presented by the icon
– Major alarms, presented by the icon
– Minor alarms, presented by the icon
– Warnings, presented by the icon
• Technology:
– LTE
– WCDMA
– GSM
– General BTS alarms
Additionally, the information presented in the table can be ordered and saved by
selecting a column and saving to a CSV file by using the Save button: .
g Note: Alarms before NTP synchronization can have incorrect timestamps, which are
not updated after NTP synchronisation.
Fault Toggling History
Fault toggling is a functionality that allows the user to suppress alarms that are raised
and cleared in a short period of time, thus having no further impact on the fault analysis.
This view enables generating and saving a Fault Toggling History report.
2.1.4 Alarm monitoring in NetAct

The NetAct Monitor application allows the user to view and process alarm information.
For information on available tools and functions, see the NetAct operating
documentation:
• Fault Management Overview and Operations

• Fault Management Helps
2.1.5 LED indications

Most hardware components have tricolor LEDs on the front panel to indicate the
operational status and fault conditions. It is recommended to read the information on the
LED indications carefully. A blinking red LED does not always require removing the
module.
2.1.5.1 Nokia AirScale System Module LED indicators
List and description of AirScale System Module LED indicators
Figure 8 Location of ASIA LED indicators
ASIAA LED indicators are located in the same locations.
Figure 9 Location of ASIB LED indicators
ASIBA LED indicators are located in the same locations.

Figure 10 Location of ABIA LED indicators
LEDs indicate operation of the plug-in units/modules as follows:

• Unit/module status LED.
• All SFP and RJ45 interface status LED.
• FAN status LED.
• SEI interface link status LED (ASIA).
• All LEDs are three-color (RED/GREEN/YELLOW) and have three possible states
when lit: stable, blinking, or alternating colors.
Table 2 LED indicators

Unit LED name LED description LED status
ASIA, ASIB STATUS Operational status of Stable GREEN: HW online or
the whole system commissioning configured
module
Blinking GREEN: Commissioning
Internal SW download while
configured
Stable YELLOW: HW blocked or
HW detected or commissioning
unconfigured
Blinking YELLOW: Commissioning
preparing or commissioning
configuring or commissioning
prepared
Stable RED: HW resetting or HW
failed
Blinking RED: HW degraded
FAN Operational status of Stable GREEN: all FANs working

FAN
Stable YELLOW: some faulty
Stable RED: all faulty
SEI1 Link status of System Not available

Extension interface
SEI1
SEI2 Link status of System Not available
Extension interface
SEI2

Table 2 LED indicators (Cont.)

SRIO1 Link status of SRIO Stable GREEN: SRIO port online
SFP+ interface SRIO1
Stable YELLOW: SRIO port
connecting
SRIO2 (ASIA Link status of SRIO Stable RED: SRIO port degraded
only) SFP+ interface SRIO2
Off: SRIO port failed or not used
EIF1 Link status of 1/10GE Stable GREEN: EIF online

SFP/SFP+ TRS
interface EIF1 Stable Yellow: SFP disconnected
EIF2 Link status of 1/10GE Stable RED: no link detected

SFP/SFP+ TRS
Stable RED: EIF failed
interface EIF2
Blinking RED: EIF degraded
EIF3 Link status of
100/1000Base-T TRS Off: EIF port not used
interface EIF3
EIF4 Link status of
100/1000Base-T TRS
interface EIF4
EIF5 Link status of
100/1000Base-T TRS
interface EIF5
LMP Link status of Local Stable GREEN: LMP port online
Management Port
Stable YELLOW: LMP port offline
(LTE)
Off: LMP port not used (LTE)
Off: LMP port offline or not used
(Single RAN)
ABIA STATUS Operational status of Stable GREEN: HW online or

the ABIA plug-in unit commissioning configured
Blinking GREEN: Commissioning
Internal SW download while
configured
Stable YELLOW: HW blocked or
HW detected or commissioning
unconfigured
Blinking YELLOW: commissioning
preparing or commissioning
configuring or commissioning
prepared
Stable RED: HW resetting or HW
failed
Blinking RED: HW degraded
RF1 Link status of RF SFP+ Stable GREEN: optical cable

interface RF1 online

Table 2 LED indicators (Cont.)

RF2 Link status of RF SFP+ Stable YELLOW: optical cable
interface RF2 disconnected
RF3 Link status of RF SFP+ Stable RED: optical cable failed
interface RF3
Blinking RED: optical cable
RF4 Link status of RF SFP+ degraded
interface RF4
Off: optical cable not used
RF5 Link status of RF SFP+
interface RF5
RF6 Link status of RF SFP+
interface RF6
2.1.5.2 LEDs of the Flexi Multiradio 10
List and description of Flexi Multiradio 10 modules LED indicators
2.1.5.2.1 LEDs of the Flexi Multiradio 10 System Module (FSMF)
List and description of Flexi Multiradio 10 System Module (FSMF) LED indicators
The figure and table below explain LED indications on the FSMF module.
Figure 11 LEDs of the Flexi Multiradio 10 System Module (FSMF)
EIF2/RF/6 STATUS
RF/EXT1 FAN
RF/EXT2 EIF1/TRS
RF/EXT3 SRIO
Table 3 LEDs of the Flexi Multiradio 10 System Module (FSMF)

LED name LED description Color
EIF2/RF/6 RF/EXT link 6 status or • Red: no connection
transport interface 2 status Green: connection OK
•
• Yellow: not in use
RF/EXT1 RF link 1 status • Red: no connection

• Green: connection OK


Table 3 LEDs of the Flexi Multiradio 10 System Module (FSMF) (Cont.)


SRIO SRIO connection status • Red: connection is faulty/no link

detected
• Red, blinking: connection is
degraded
• Yellow: SFP disconnected
• Green: connection OK/link
detected
• Off: port is not in use
EIF1/TRS transport interface 1 status • Red: no connection

• Red, blinking: degraded
• Off: uncommissioned site, SW
upgrade, disabled or locked
connector
FAN fan status • Red: fan fault

• Green: fan OK
STATUS system module status • Red: module self-test or reset

(LED red for < 5 seconds) or major
alarm or critical alarm
• Red, blinking: minor alarm
• Yellow: stand-by or blocked
• Yellow, blinking: SW download or
configuration ongoing, module
non-operational
• Green: module operational (the
cell can be locked in the RNC)
• Green, blinking: module is loading
software or parameters or local
maintenance access when
modules are operational
• Green and Yellow, blinking: only
TRS commissioned
2.1.5.2.2 LEDs of the capacity extension sub-module (FBBA)
List and description of Flexi Multiradio 10 capacity extension sub-module (FBBA) LED
indicators
The figure and table below explain LED indications on the FBBA module.

Figure 12 LEDs of the capacity extension sub-module (FBBA)
SRIO STATUS RF/EXT
Table 4 LEDs of the capacity extension sub-module (FBBA)

SRIO SRIO1 connection status • Red: no connection
• Off: uncommissioned or SW
upgrade
STATUS operational status • Red: module self-test or reset

non-operational
• Green: module operational
RF/EXT RF link status • Red: no connection

2.1.5.2.3 LEDs of the capacity extension sub-module (FBBC)
List and description of Flexi Multiradio 10 capacity extension sub-module (FBBC) LED
indicators

The figure and table below explain LED indications on the FBBC module.
Figure 13 LEDs of the capacity extension sub-module (FBBC)
CLASS1
LASERPRODUCT
STATUS
RF1 RF2 RF3 SRIO/RF4

Table 5 LEDs of the capacity extension sub-module (FBBC)
RF1/ RF2/ RF3 RF link status • Red: no connection
SRIO/RF4 RF4 link status or SRIO • Red: no connection

interface status • Green: connection OK

non-operational
2.1.5.2.4 LEDs of the Flexi Multiradio 10 System Module (FSIH)
List and description of Flexi Multiradio 10 System Module (FSIH) LED indicators
The figure and table below explain LED indications on the FSIH module.

Figure 14 LEDs of the Flexi Multiradio 10 System Module (FSIH)

RFEXT2 RFEXT3/10G
RFEXT1/10G RFEXT4
SRIO2 RFEXT5/10G
STATUS SRIO1 RFEXT6
FAN RF1-4
RF5
RF6/EIF5 EIF1-2
Table 6 LEDs of the Flexi Multiradio 10 System Module (FSIH)
FAN fan status • Red: fan fault
• Green: fan OK
STATUS system module status • Red: module self-test or reset

non-operational
RF1, RF2, RF3, RF4, RF link status • Red: no connection

RF5, RF6 • Green: connection OK
RF/EXT1, RF/EXT2, • Yellow: not in use
RF/EXT3, RF/EXT4,
RF/EXT5, RF/EXT6
SRIO1, SRIO2 SRIO1-2 connection status • Red: no connection

EIF1, EIF2 transport interface status • Red: no connection


Table 6 LEDs of the Flexi Multiradio 10 System Module (FSIH) (Cont.)

2.1.5.2.5 LEDs of the capacity extension sub-module (FBIH)
List and description of Flexi Multiradio 10 capacity extension sub-module (FBIH) LED
indicators
The figure and table below explain LED indications on the FBIH module.
Figure 15 LEDs of the capacity extension sub-module (FBIH)
RFEXT2 RFEXT3/10G
RFEXT1/10G RFEXT4
SRIO2 RFEXT5/10G
SRIO1 RFEXT6
STATUS
Table 7 LEDs of the capacity extension sub-module (FBIH)
non-operational
RF/EXT1, RF/EXT2, RF1-6 link status • Red: no connection

RF/EXT3, RF/EXT4, • Green: connection OK
RF/EXT5, RF/EXT6
SRIO1, SRIO2 SRIO1-2 connection status • Red: no connection


2.2 Performance monitoring

Performance monitoring is achieved using key performance indicators (KPIs), counters,
and measurements information.
The Figure 16: Performance monitoring data useful for troubleshooting illustrates how
KPI and counter data can be used for troubleshooting purposes.
Figure 16 Performance monitoring data useful for troubleshooting
Performance monitoring can be performed in GSM, WCDMA and LTE technologies and
every technology has its own set of KPIs, counters and measurements. The SRAN
solution has also its set of counters and measurements.
The KPIs, counters, and measurements descriptions regarding GSM, WCDMA and the
counters and measurements descriptions regarding SRAN can be found in the Single
RAN Operating Documentation/ Single RAN System/ SBTS Reference Data section.
The KPIs, counters, and measurements descriptions, as well as message sequence
charts regarding LTE can be found in the LTE Radio Access Operating Documentation/
BTD Reference/ Counters and Key Performance Indicators section.
2.2.1 Viewing counters and KPIs in Web Element Manager

Using Web Element Manger, it is possible to view counters and KPIs using two menus:
Performance Management and KPI Dashboard.

2.2.1.1 Performance Management view
Access to Performance Management view: Performance ► Performance

Management ► BTS Counters / Transport Counters / Real-time Measurements
Performance Management contains the following tabs: BTS Counters (opened by
default), Transport Counters and Real-time Measurements. Performance data is
gathered and presented in real time as long as WebEM is connected to the BTS.
After selecting an object from the Navigation Panel ► Objects, the related counters
and their values are displayed in either table view or plot view. The Table/Plot View
button is used to switch between the two. The selected counters are listed in the Details
pane, each counter with a different color assigned. The detailed value is displayed once
clicked on the chart. Up to 20 items can be displayed at the same time. The data is
displayed for the time intervals specified in a Display data for drop-down list.
Figure 17 Table View
Figure 18 Plot View
The date and time of the performance measurement (BTS) are used for BTS counters
and TRS counters. Real-time measurements are displayed in the BTS time.

In online mode (when WebEM gathers data from the BTS), the BTS Counters tab
shows historical values in table view and real-time data in chart view by default. It is
possible to show values for a selected timespan, when one is selected from the
Navigation Panel ► Timeline. For BTS and TRS counters, all data gathered up to the
current timestamp is available.
In offline mode, when data is loaded from a snapshot, the BTS Counters tab shows the
latest value and saved data in a chart view by default. It is possible to show values of
real-time and hardware monitoring for a selected timespan, when one is selected from
the Navigation Panel ► Timeline panel. For BTS and TRS counters, all the data
gathered up to the current timestamp is available.
When IMS2 is used, only real-time measurements and hardware monitoring are
available. When a snapshot is used, PM files are also available, and data from all PM
files from the snapshot is displayed.
Items in Navigation Panel can be filtered by name. Users can also manually select
counters and save a filter as an XML, by using the Export filter button in Navigation
Panel. To load a saved filter, click Import filter.
The Save Snapshot option allows to save the currently visible graph as a PNG file (only
in graph view).
BTS counters can be exported using the Export to CSV button.
2.2.1.2 PM counter data
Preconditions and collection of PM counter data
Preconditions for collecting PM counter data

The PM counter data can be collected either via Web Element Manager (covering a 24-
hour history) or via NetAct.
Collecting PM counter data using WebEM

The simplest way to collect PM counter data is to save an SBTS snapshot via WebEM
(see Saving a BTS snapshot file using Web Element Manager). However, for PM counter
data only, it is faster and more efficient to save it by using the Performance ►
Performance Management ► BTS Counters option in the top menu.

Figure 19 BTS Counters function in WebEM
g Note: PM counter data covers a 24-hour history only. If a longer period is required, use
NetAct instead.
For more information on how to collect PM counters using NetAct, see the NetAct
Customer Documentation.
2.2.1.3 KPI Dashboard
KPI Dashboard view allows to see respective KPIs for all objects.
Access to KPI Dashboard view: Performance ► KPI Dashboard

KPIs are displayed for objects selected in Navigation Panel ► Objects. The dashboard
can be grouped by objects or KPI name. KPIs can be filtered, by using the KPI filter,
ordered either by name or by related object, and searched by name. The list of all KPIs
can be collapsed and expanded. The Details panel displays details for all the selected
KPIs.

Figure 20 KPI Dashboard
2.2.2 Performance monitoring in NetAct

The NetAct Performance Manager application allows the user to view and process
counter and KPI data.
For information on available tools and functions, see the NetAct operating
documentation:
• Performance Management / Performance Management Overview

• Performance Management / Performance Manager Overview
• Thresholder and Profiler Overview
2.2.3 Network monitoring using Traffica

The Traffica application is introduced with two features: SR000919: SBTS Real Time
Performance Monitoring and SR000478: LTE L3 Data Collector Northbound Interface.
Traffica also supports RNC L3DC and BSC RTT, adding options to monitor the WCDMA
and GSM networks.
The SR000919: SBTS Real Time Performance Monitoring feature provides real-time
performance monitoring for the SBTS. The SBTS is connected directly to Traffica using a
real-time data interface. It contains the results of ongoing performance measurements
(PM-counter values) in real-time. These results are sent every minute.
The SR000478: LTE L3 Data Collector Northbound Interface feature offers a real-time
network monitoring solution based on the SBTS cell trace interface (introduced with the
SR000478: LTE L3 Data Collector Northbound Interface feature). The collected trace
data is sent to the Layer 3 Data Collector (L3DC) that transfers the data to Traffica for
visualization.
Traffica consists of:

• a Traffic News client for offline analysis of collected data

• a Traffic Views client for real-time monitoring (various graph sets to display collected
data in different time periods)
A Traffica user can configure threshold-based real-time alarms that can be forwarded to
the NetAct Monitor application.
For more details on Traffica applications and functions, see the Traffica operating
documentation:
• Traffica Principles
• Traffica Reference Guide
2.2.3.1 Traffica general use case for LTE troubleshooting
Traffica is a real-time traffic monitoring tool designed to monitor and analyze network
traffic. Traffica allows the operator to see how the network functions, from the network
element level down to individual subscriber information.
Before you start

To visualize the cell trace data and real-time counter data in Traffica, the following
requirements must be fulfilled:
• The L3 Data Collector (L3DC) is installed and configured.

• The LTE433: Cell Trace is activated.
• The Traffica - L3DC interface is configured.
Procedure
1 Follow network and service performance indicators using Traffic Views.
• Spot degradations (for example, RRC/RAB setup failure increase).

• Detect sites with no traffic.
• Define threshold alarms to automate fault detection.
2 Analyze problem severity and location using Traffic Views.
Use failure graphs to check whether the problem is limited to certain network
elements (NEs) or cells.
3 Troubleshoot the problem using linked graphs and Traffic News.
• Use drill-down graphs to isolate the problem further down in topology.

• Study call event reasons and call failure reasons to determine the actual fault.

2.3 Diagnostic tools in WebEM

Introduction of SBTS built-in tools for monitoring and troubleshooting purposes
2.3.1 Synchronization view

The Synchronization view has three tabs: Status, showing the actual (real-time) details
on synchronization, Tuning, allowing to configure synchronization tuning, Test Clocks,
allowing to synchronize the external RF measuring equipment.
Access to Synchronization view: Diagnostic ► Synchronization.

Status
Status displays the actual (real-time) details on the synchronization source and time
servers. It also shows the synchronization source detailed status, such as
synchronization hub, synchronous Ethernet, and Timing over Packet (ToP) status as well
as GNSS satellite information.
The Details panel displays the Synchronization hub and Timing over Packet details.
Tuning
Fast tuning can be used if the BTS clock must be adjusted or the user wants to
synchronize the BTS clock quickly. To start the fast tuning, select the Fast option and
click the Tune button.
Note that if the system module operates as a synchronization slave, it is not possible to
tune the BTS clock.
Tuning the BTS clock manually is used for the following purposes:
• To read the current digital-to-analog converter (DAC) word from the BTS or to
change the current DAC word on the BTS.
• To browse the history information about the difference between BTS clock and
external reference clock frequency to find out the frequency stability or accuracy.
If the BTS determines that the reference signal quality during fast tuning is insufficient,
fast tuning is interrupted and the BTS continues with normal tuning.
The Get History button allows the user to view the history information about the
difference between the BTS clock and the external reference clock frequency to find out
the frequency stability or accuracy. It is also possible to save and print the history
information, using the respective buttons.
Note that there can be entries with the date 01.01.2004 in the frequency history file. This
date is shown if Network Time Protocol (NTP) time has not been available.
Test Clocks

Test Clocks allow to test the functionality of the test clock output signal in the SYNC
OUT connector of the BTS. It is also possible to enable or disable the frame clock output
signal and to select which frame clock is used (100 Hz, 50 Hz, 25 Hz, 12.5 Hz or SFN0).
The clock signal is used for synchronizing external RF measuring equipment and must
be disabled during a normal BTS operation.
The current status of the 10 MHz test clock is visible at the top of the view. Use the
Enable checkbox to enable or disable the test and select which frame clock is used with
the Output list. The Send button saves the settings.
2.3.2 IP Connectivity Test

IP Connectivity Test allows to test ping connections to certain configured remote host
addresses.
Access to IP Connectivity Test view: Diagnostic ► IP Connectivity Test

To do an IP connectivity test, fill in the following settings:
• Scope - choose one option from a drop-down list. The possible options are:
– User-defined address (default)
– All configured hosts
– All configured IPv4 hosts
– All configured IPv6 hosts
– BFD <Y> x.x.x.x
– CMP/CA server x.x.x.x
– <IPRT-Y | IPRTV6-Y> routing default gateway x.x.x.x
– NTP server x.x.x.x
– Primary BSC x.x.x.x
– Primary DNS server x.x.x.x
– Primary LDAP x.x.x.x
– Primary MME x.x.x.x
– Primary OAM x.x.x.x
– Real-time PM collection entity x.x.x.x
– Remote syslog server x.x.x.x
– RNC
– RTT Measurement session <Y> x.x.x.x
– Secondary BSC x.x.x.x
– Secondary DNS server x.x.x.x
– Secondary MME x.x.x.x
– SGW x.x.x.x
– ToPF ToP master x.x.x.x
– ToPP ToP master x.x.x.x
– RNC x.x.x.x
• Address - only used and mandatory in case of a user-defined address scope.

• Source address - choose an address from a drop-down list.
• Payload Size - bytes [16...61411]
• DSCP - [0...63]

Press Start to display the test results in the table below. To stop testing, press Stop.
Note that a test failure does not always mean there is no connection. Various scenarios
must be taken into consideration. Therefore, make sure to select the correct source
address.
2.3.3 RF Diagnostic Test

RF Diagnostic Test allows to test and verify the RF characteristics of RF modules. RF
Diagnostic Test is supported for rel. 2 or newer HW.
Access to RF Diagnostic Test view: Diagnostic ► RF Diagnostic Test

The RF Diagnostic Test view contains two tabs: Test Setup and Test Result. RF
diagnostic is valid on LTE only.
Test Setup
To execute the test, select which cells are to be tested (all or an individual cell) and
define thresholds for the BTS:
• RF Power Error High Threshold (dB)
• RF Power Error Low Threshold (dB)
• RTWP High Threshold (dBm)
• RTWP Low Threshold (dBm)
• TX Antenna VSWR High Threshold
Click Activate remote RF diagnostic test check-box.

To define thresholds for bands, click the icon and fill in the required parameters (Band
class, Total RF power high threshold, Total RF power low threshold). To delete
thresholds for bands, use the icon.
Click the Save threshold button to send the configured thresholds to the BTS.
Click the Start Test button to initiate the test. The progress and results are displayed in
the Test Result tab when available.
Test Result
The Test Result tab contains a table with general test information and a table with a
detailed result for each antenna. Test results are displayed for selected cells. The list of
cells is in the left table and can be filtered by local cell ID. Test results can be saved for
one cell (Save Cell Results) or for all cells (Save All Results). Results are saved in a
text file.
2.3.4 EAC Functionality Test

EAC Functionality Test allows to test the functionality of the External Faults and
Controls (EAC) for the commissioned BTS. If the SW update is in progress, the test
cannot be run. The information for the test is checked from the site configuration file.
Access to Functionality Test view: Diagnostic ► EAC Functionality Test

This view contains two tabs: Faults and Controls.

Note that only commissioned EAC lines can be tested in EAC Functionality Test.
Faults are used to test external fault lines, if EAC is configured. Select the lines to be
tested in the Selected to test column and the results are updated when available. The
Save Results button allows to save the results to a TXT file.
Controls are used to test the external control lines. Change the state of the output line
and click Send to send the changes to the BTS. After the BTS has changed the state of
the external control line, check the state of the supervised external device. The operator
can update test results in the Test result column. The Save Results button allows to
save the results to a TXT file.
2.3.5 Ethernet Port Mirroring

Ethernet port mirroring is used to identify, monitor and troubleshoot network
abnormalities. The traffic that goes to and from a specific port number is automatically
copied and transmitted to a monitoring port.
Access to Ethernet Port Mirroring: Diagnostic ► Ethernet Port Mirroring

The port mirroring function enables you to perform on site mirroring (tracing, sniffing) of
Ethernet traffic. The function applies to the Ethernet traffic on a physical Ethernet
Interfaces of the BTS, as well as on internal Ethernet Interface, if a BTS-integrated, QoS-
aware switch is present.
To enable Ethernet port mirroring, mark the checkbox Enable Ethernet port mirroring.
Click Add Mirror group and set the direction, source and destination for the mirroring.
The Send button applies the changes to the configuration plan and triggers its validation
and activation. No BTS reset is required.
Figure 21 Ethernet Port Mirroring

2.3.6 IP Traffic Capturing

IP Traffic Capturing allows to capture the traffic to and from a local port into a file or
stream towards another port.
Access to IP Traffic Capturing view: Diagnostic ► IP Traffic Capturing.

To capture traffic at transport network interface level, select one of the capture point
options. For more information, see Figure 22: Capture point options for IP traffic
capturing
Figure 22 Capture point options for IP traffic capturing
Selection of a capturing point depends on the intended packets to be monitored. When

IPSec is configured, if we capture trace at point A, we can capture packets before IPSec
encryption. If we capture trace at point B, then we are able to capture the packets after
IPSec encryption.
The following options are also available:
• Include U-plane - includes user plane traffic
• Output - allows to define the data output: save the data to a file (and optionally
protect it with a password) or stream the data to another port.
Clicking on Start initiates the capture. The status and duration are displayed. The Stop
button stops the process. The BTS automatically stops the traffic capturing after 24
hours if the user does not stop it. The captured data is saved on the BTS, and is
generated as a file only if the user clicks the Generate and Download File button.
2.3.7 SFP Monitoring

The SFP Monitoring tab allows to view details on optical fiber connectivity between
modules (master system module, radio modules and extension system module). Optical
interface diagnostic data is read from SFP connectors. The SFP Monitoring test is
supported by FSMF modules and onwards.
Access to SFP Monitoring view: Diagnostic ► SFP Monitoring

An Small Form-factor Pluggable (SFP) is a physically compact connector design that
consists of a housing fitted on a host board and a pluggable transceiver. It is developed
for use in high-speed data transfer, including both copper-based and fiber-optic systems.

The SFP Monitoring tab shows current (real-time) information about the connection
between RF modules and system modules in the current configuration. Selecting any of
the listed SFPs displays further information in the Details panel.
2.3.8 Antenna Line Online Monitoring

This tab allows to monitor online antenna line characteristics.
Access to Antenna Line Online Monitoring view: Diagnostic ► Antenna Line Online
Monitoring
The Antenna Line Online Monitoring view allows the operator to monitor online
antenna line characteristics such as:
• The values of Voltage Standing Wave Ratio (VSWR) for the Tx-capable antenna
lines
• The values of Received Total Wideband Power (RWTP) for LTE and WCDMA
• The values of Received Signal Strength Indicator (RSSI) for GSM
To start monitoring, select the antenna line and click the Start button. The Stop button
stops the monitoring. The obtained results can be exported to a CSV file.
2.3.9 RF Monitoring
This view allows to monitor the spectrum in order to detect radio frequency interference
(RFI) and radio disturbance in the peripheral radio frequency (RF) path.
Access to RF Monitoring: Diagnostic ► RF Monitoring

Tests available in the RF Monitoring view:
• PIM Desensitization
• Distance to PIM (DTP)
• RF Scan
2.3.9.1 PIM Desensitization
This tab allows to perform PIM desensitization tests.
Access to PIM Desensitization: Diagnostic ► RF Monitoring ► PIM Desensitization

Passive Intermodulation Distortion (PIM) Desensitization is a test that verifies if PIM has
any impact on the uplink channel for a particular antenna. To perform the test it is
necessary to specify which antenna is to be tested. The following information on test
configuration is displayed:
• Local cell
• Frequency band
• Bandwidth
• Frequency/EARFCN

• Power
This test can be performed for the LTE and WCDMA technologies. The BTS
configuration used for the test can be exported into ZIP file. Use the Start button to
launch the test. The test results are saved to a local drive. For detailed instructions on
viewing the test results, see .
2.3.9.2 Distance to PIM (DTP)
This tab allows to perform Distance to PIM (DTP) tests.
Access to Distance to PIM (DTP): Diagnostic ► RF Monitoring ► Distance to PIM

(DTP)
Distance to Passive Intermodulation Distortion (DTP) is a test that helps localize the
actual place where Passive Intermodulation Distortion (PIM) is happening on an antenna
line. To perform the test it is necessary to specify which antenna is to be tested. It is
possible to configure additional test settings:
• Velocity factor
• Cable length
The following information on test configuration is displayed:
• Local cell
• Power
This test can be performed for LTE and WCDMA technologies. Use the Start button to
launch the test. The test results are saved to a local drive. For detailed instructions on
viewing the test results, .
2.3.9.3 RF Scan
This tab allows to perform RF scanning.
Access to RF Scan: Diagnostic ► RF Monitoring ► RF Scan

In this tab it is possible to trigger a scan to detect radio frequency (RF) interference.
There are several attributes that must be selected or configured to perform a scan:
• Radio
• Capture type
• Antenna
• Local cell
This test can be performed for the LTE and WCDMA technologies. Use the Start button
to launch the test. The test results are saved to a local drive. For detailed instructions on
viewing the test results, see .
2.3.10 Test Models

The Test Models views allow running downlink and uplink test models for each cell.

Access to Test Models: Diagnostic ► Test Models

The Test Models views allow running downlink and uplink test models for LTE and
WCDMA cells.
It also allows for running transmission and loop tests for GSM.
The tests are available only if the BTS is in Test Dedicated State.
2.3.10.1 LTE Downlink
The LTE Downlink tab allows to perform LTE downlink tests.
Access to LTE Downlink: Diagnostic ► Test Models ► LTE Downlink

To perform a test, select the cells for each test, as well as the test model and the
physical cell ID. Clicking Start begins the test, and Stop stops the test. The results are
displayed for each cell and can be saved to a file. The Details panel presents the status
of each started test.
Figure 23 LTE Downlink tab view
2.3.10.2 LTE Uplink
The LTE Uplink tab allows to perform LTE uplink tests.
Access to LTE Uplink: Diagnostic ► Test Models ► LTE Uplink

To perform a test, select cells for each test, as well as the test model, reporting time
interval and resource block offset. Clicking Start begins the test, and Stop stops the test.
The results are displayed for each cell and can be saved to a file. The Details panel
presents the status of each started test.
Figure 24 LTE Uplink tab view
2.3.10.3 WCDMA Downlink
The WCDMA Downlink tab allows to perform WCDMA downlink tests.

Access to WCDMA Downlink: Diagnostic ► Test Models ► WCDMA Downlink

To perform a test, select the cells for each test, as well as the test model, write the
primary scrambling code and select the number of DPCH. Clicking Start begins the test,
and Stop stops the test. The results are displayed for each cell and can be saved to a
file. The Details panel presents the status of each started test.
Figure 25 WCDMA Downlink tab view
2.3.10.4 WCDMA Uplink
The WCDMA Uplink tab allows to perform WCDMA uplink tests.
Access to WCDMA Uplink: Diagnostic ► Test Models ► WCDMA Uplink

To perform a test, select the cells for each test and write the primary scrambling code.
Clicking Start begins the test, and Stop stops the test. The results are displayed for
each cell and can be saved to a file. The Details panel presents the status of each
started test.
Figure 26 WCDMA Uplink tab view
2.3.10.5 GSM BCCH Transmission
The GSM BCCH Transmission tab allows to perform GSM BCCH transmission tests.
Access to GSM BCCH Transmission view: Diagnostics ► Test Models ► GSM

BCCH Transmission
To perform a test, select the TRX number for each test, as well as the absolute radio
frequency number (ARFN). Choose the rest of test parameters. Clicking Start begins the
test, and Stop stops the test. The results are displayed for each cell and can be saved to
a file. The Details panel presents the status of each started test.

2.3.10.6 GSM Loop Test
The GSM Loop Test tab allows to perform GSM loop tests.
Access to GSM Loop Test view: Diagnostics ► Test Models ► GSM Loop Test
To perform a test, set up the test parameters and click Start. Clicking Stop stops the
test. The results are displayed for each cell and can be saved to a file. The Details panel
presents the status of each started test.
2.3.11 Terminal
Terminal view description
Access to Terminal view: Diagnostic ► Terminal

Terminal is the text console allowing you to execute text commands. The Terminal
output is cleared on each reload or view change. It is possible to save the output to a
TXT file by using the output-to-file command. Using the help command lists all
the available commands, while using the help <command> displays help information
on the given command. Press the Tab key while typing a command to autocomplete it.
g Note: Terminal view in WebEM is not an equivalent of WebEM Remote Tool.
2.3.12 Reset to Test Dedicated State

Reset to Test Dedicated State sets the site to a test dedicated state in order to perform
tests.
Access to Reset to Test Dedicated State view: Diagnostic ► Reset to Test Dedicated
State
To perform tests such as LTE Uplink, LTE Downlink, WCDMA Uplink and WCDMA
Downlink, the Execute procedure must be run first. It causes the site to reset to the
Test Dedicated State. While in the Test Dedicated State, the site is
treated as Blocked.
While the site is in Test Dedicated State, the icon is displayed in the BTS
site information area.
Figure 27 BTS site information
To leave the Test Dedicated State reset the BTS.
2.3.13 TWAMP RTT Measurements

RTT Measurements allow to measure and supervise the IP network conditions through
the mobile backhaul between the BTS and some other point.

Access to TWAMP RTT Measurements view: Diagnostic ► TWAMP ► TWAMP RTT

Measurements
The RTT Measurements tab allows to measure and supervise the IP network conditions
through the mobile backhaul between the BTS and some other point. The Round Trip
Time (RTT) measurement functionality provides Two-Way Active Measurement Protocol
(TWAMP)-light measurements, as specified in the IETF RFC 5357. The purpose of the
measurements is to have an estimation of the quality and performance of the IP-based
mobile backhaul for each QoS class independently, indicated by DiffServ Code points.
The results of the measurements are available in this tab if the hardware supports the
RTT measurements and if it is configured using Commissioning Wizard or Parameter
Editor.
2.3.14 Ethernet Link OAM

This view gives user access to link monitoring, Remote Failure Indication (RFI) and
loopback functionalities.
Access to Ethernet Link OAM: Diagnostic ► Ethernet Link OAM

Link Monitoring
WebEM shows information on:
• Latest Events
– Event type
– Event subtype
– Event time
– Event code
– Source address
– Destination address
• Event Statistics
– Event Type
– Last remote interval events
– Total remote events
– Total remote TLVs
• OAM/non-OAM Statistics
– Number of recived OAM protocol data units (OAMPDUs)
– Non-OAMPDUs frames transmitted
– Non-OAMPDUs frames received
There are four types of link events defined in the standard for a degraded Ethernet
connection:
• Errored Symbol Period Event
• Errored Frame Event
• Errored Frame Period Event

• Errored Frame Second Summary Event
Loopback
This function is used for testing purposes in which the remote peer loops all received
non-OAM Protocol Data Units (non-OAMPDUs). If the loopback mode is activated and it
does not receive a disable command, the BTS returns to the normal working state after a
timeout is reached.
The loopback testing is used for:
• Checking if the traffic is correctly sent and looped back to the local node.
• Checking statistics (errored frames).
• Identifying erroneous packets and packet drops in the link.
g Note: Loopback mode interrupts the regular traffic, therefore it is recommended to use
it for offline testing or only if all alternatives for online testing are exhausted.
Remote Failure Indication (RFI)

To check if there are any Critical Link Events detected, open the Details panel in the
Ethernet Link OAM window.
Figure 28 Checking critical link events
2.3.15 Ethernet Service OAM

This view provides information on Ethernet Continuity Check, Remote Defect Indication
(RDI), Loopback and Link Trace.
Access to Ethernet Service OAM: Diagnostic ► Ethernet Service OAM

The Maintenance Association Endpoint (MEP) sends Ethernet Continuity

Check Messages (Eth-CCMs) to its MEP peers according to the configured period.
The MEP expects Eth-CCMs from every MEP peer. The Eth-CCM reports continuity loss,
or unintended connectivity between MEPs. WebEM returns data such as:
• ID
• Mac address (static)
• Mac address (from remote MEP)
• Out of sequence CCM
• CCM reception
• CCM period
• Last RDI
Ethernet Link Trace retrieves information about the relationships between neighboring
MEPs or Maintenance Association Intermediate Points (MIPs). It allows the detection of
the number of S-OAM aware hops between two MEPs.
Ethernet Loopback verifies bidirectional connectivity between two peer MEPs, or
between an MEP and an MIP.
To start the Loopback or Link Trace, click the corresponding button in the Action
column.
2.3.16 PPP Interfaces

The PPP Interfaces view contains two tabs: Single Link View and Multi Link View.
Access to PPP Interfaces view: Diagnostic ► PPP Interfaces

The PPP Interfaces view allows to view PPP Single Link and Multi Link configuration
and status.
In case of PPP Multi Link view, details of all PPP links forming PPP multi link
configuration can be checked.
2.3.17 IP Routing
The IP Routing view allows to display information about static routes, routing policies
and so on.
2.3.17.1 IPv4/IPv6 Routing
A short description of the IPv4/IPv6 Routing views
Access to IPv4 Routing view: Diagnostic ► IP Routing ► IPv4 Routing

Access to IPv6 Routing view: Diagnostic ► IP Routing ► IPv6 Routing
This tab provides information about static routes and forwarding tables for selected
routing tables. The data is presented using two tables: Static routes and Forwarding
table.
Information provided by Static routes table:

• Destination
• Prefix length
• Preferred source
• Gateway
• Preference
• IP MTU
• Trigger ID
• Trigger state
Information provided by Forwarding table:

• Type
• Destination
• Prefix length
• Gateway
• IP interface reference
• Preferred source
• Preference
• IP MTU
• Trigger ID
The Change Static Routes button redirects the user to the object class in Parameter
Editor responsible for static route configuration.
2.3.17.2 Routing Policies
A short description of the Routing Policies view
Access to Routing Policies view: Diagnostic ► IP Routing ► Routing Policies

This view provides the following information about routing policies:
• Order number
• Reference to routing table
• Source IP address
• Source IP prefix length
The Change Routing Policies button redirects the user to the object class in Parameter
Editor responsible for routing policy configuration.
g Note: The policy order number of any new or old policy cannot be changed to an
existing policy order number.
2.3.18 IP Security Associations

A short description of the IP Security Associations view
Access to IP Security Associations view: Diagnostic ► IP Security Associations

The IP Security Associations view provides information on:

• Internet Key Exchange (IKE) associations

– Policy order number
– IKE request ID
– Local tunnel endpoint
– Remote tunnel endpoint
– Status
– Mode
• Overall status of IKE associations

• Association information
– Policy order number
– Association request ID
– Local IP address
– Remote IP address
– Peer state
– Inbound security policy index (SPI)
– Outbound SPI
The displayed data can be filtered by Policy order number.
2.3.19 PMTU Discovery

In this view, the on-demand path maximum transmission unit (PMTU) discovery can be
performed.
Access to PMTU Discovery: Diagnostic ► PMTU Discovery

To start the test, insert the Source IP address, Destination IP address and DSCP. In
return, WebEM displays Path Maximum Transmission Unit and Local Maximum
Transmission Unit.
2.3.20 GSM Traffic Trace

A short description of the GSM Traffic Trace view
The GSM Traffic Trace displays a graphical representation of the active or idle timeslots
for a GSM cell or sector at a given time. To display data for all TRXs under a specific cell
or a single TRX, choose the correct object in the Navigation Panel (Objects tab). GSM
Traffic Trace data for each displayed TRX is presented in the form of a graphical
representation of eight numbered timeslots. Each timeslot is colored according to the
type of traffic.
Data collection starts after selecting the cell or the sector or the TRX. To refresh the
results click the Refresh button. It is possible to enable Auto refresh by marking the
checkbox. Select the Auto refresh time interval from a drop-down list.

Figure 29 GSM Traffic Trace view
2.3.21 PDH Loopback

This tab allows to perform PDH loopback.
Access to PDH Loopback: Diagnostic ► PDH Loopback

To enable the PDH Loopback function, select the Interface and Loop configuration and
then click Send. Additionally, it is possible to set the time out.
Figure 30 PDH Loopback

Collecting and analyzing troubleshooting data Troubleshooting SBTS
3 Collecting and analyzing troubleshooting

data
To efficiently perform the troubleshooting process, a set of supporting data must be
collected.
In case of call processing and signaling problems, data can be collected using one of the
following methods:
• BTS snapshot
• Cell trace
Additional data can be obtained by collecting:
• drive test data

• end-user feedback
• core network indicators
• problematic site location (for example, from geographic location tools such as
Traffica)
Operators are recommended to contact Nokia Services if they cannot solve the problem
themselves, despite having all the available data.
3.1 Common logs

Detailed information about the most common logs in troubleshooting
The most common logs in troubleshooting are:

• BTS snapshot
• IM snapshots
• WebEM logs
• Transport related logs
3.1.1 BTS snapshot

The BTS snapshot related features, content and instructions for saving a snapshot.
The following features are related to the BTS snapshot functionality:

• LTE1099: Event-Triggered Symptom Data Collection and Provisioning
This feature introduces automatic fault-triggered BTS symptom data (troubleshooting
logs) collection. The triggering BTS faults can be configured by the operator. The
feature introduces also a recoveryResetDelay parameter, which is used to
configure a delay for a BTS reset triggered by a fault.
• LTE1909: BTS Diagnostics Toolkit

Troubleshooting SBTS Collecting and analyzing troubleshooting data
This feature provides the operator, technical support and the Nokia developer with
efficient data collection from eNB. The set of data collected, such as: trace data, BTS
snapshot data, is sent from the operator to Nokia. This feature supports resolving an
error at first occurrence given that all the necessary information is available for
detailed analysis. The following are the functions/features of this toolkit:
– Supervises the eNBs via cell tracing
– Triggers the BTS snapshot creation in a timely manner, based on the trigger
events in the cell trace content
– Comes with the SW of the Layer 3 Data Collector
– Is easy to use and install
• LTE2250: Syslog Substring-Triggered Automated Snapshot Collection

The LTE2250: Syslog Substring-triggered Automated Snapshot Collection feature
allows commissioning a BTS with the new category of an automated snapshot
collection trigger, based on a single substring occurrence in the syslog stream. There
are the following safety mechanisms built in:
– a minimum of 10-characters-long defined clause on a searched string – it is
necessary to avoid accidents that would trigger a snapshot too often
– a graceful period defined – a given string is being searched continuously; once it
has been found, the search stops to protect the system against a flood of
snapshots
– allows five snapshots triggered by the LTE2250: Syslog Substring-triggered
Automated Snapshot Collection feature maximum per 24h per BTS
g Note: The LTE2250: Syslog Substring-triggered Automated Snapshot Collection

feature is configurable in parallel with the
LTE1099: Event-triggered Symptom Data Collection and Provisioning feature.
The substring triggering log collection is defined by the Syslog substring
trigger(syslogSubstringTrigger) parameter in the TRBLCADM object. The
operator should modify it only on explicit request by technical support.
3.1.1.1 Snapshot preconditions
A short description of the preconditions for taking a snapshot
WebEM must be properly installed and connected to the BTS. The BTS can be accessed
through a browser, such as Google Chrome, at the URL https://192.168.255.129 when
the PC is connected locally to the LMP port of the SBTS or https:<
mPlaneIpAddressDN> when connected remotely.
For more information on collecting a snapshot file, see Saving a BTS snapshot file using
Web Element Manager.
Within the created archive package there is a TXT file listing all the files included in the
package: snapshot_file_list.txt.
3.1.1.2 BTS snapshot content
List of data that can be included in the BTS snapshot

Examples of data included in the BTS snapshot:
• Active alarms and alarm history

• Installed SW versions
• BTS configuration (commissioning parameters)
• Internal log files for different BTS components (including MAC TTI traces)
• PM counter data for a particular BTS (collected since the last BTS reset and kept for
a maximum of 24 hours)
3.1.1.3 Saving a BTS snapshot file using Web Element Manager
Instructions on how to save a BTS snapshot file using WebEM
Procedure
1 Start WebEM.
2 Go to Diagnostic ► Snapshot.
Step example
Figure 31 Snapshot functionality in WebEM
3 For Coverage, select either All log files or Most important log files.
The All log files snapshot coverage includes all the files, while the Most important
log files snapshot coverage includes only the most important files in the technical
log.

Step example
Figure 32 Snapshot collection settings
4 For the target location, select either Local or Remote.
The target location can be chosen based on the associated options below:
• Local drive: Create a snapshot and place it on the SBTS and download a copy to
the local drive.
• Server: Create a snapshot and place it on the SBTS and save a copy to an
external server.
g Note: If the target location is set to Remote, make sure that the
Diagnsostic Snapshot destination (diagSnapDestination)
parameter is configured. If the parameter value is lss, configure the parameters
under the Local symptoms server configuration (lssConfig)
structure as well. To configure these parameters go to
Configuration ► Configuration Management ► Parameter Editor. Use the
search box to find the required parameters.

Step example
Figure 33 Selecting the target location
In case of full AirScale system module:

• The technical logs related to the primary and secondary system modules and
related resources (BBMODs, RMODs, ALDs, cells and more) are collected and
saved in the technical report.
• If the connection between the two system modules is broken, connect with the
secondary system module using LMP to collect technical logs from the module
and the related resources. Then connect it to the primary system module using
LMP to collect technical logs from the module and the related resources.
5 Click Collect snapshot.
g Note: To stop the process during snapshot collection, click Cancel.
3.1.1.4 Changing RnD parameters using WebEM
Instructions on how to change RnD parameters using WebEM

Procedure
1 Start WebEM.
2 Go to Procedures ► Change BTS RnD parameters.
Figure 34 WebEM window
3 Change the parameters and click Execute.
Figure 35 WebEM Change BTS RnD parameters window
g Note: The RnD parameters values are provided by Nokia Support.

3.1.2 Taking IM snapshots with WebEM

Instructions on how to take IM snapshots with WebEM
Procedure
1 Open WebEM.
2 Go to Procedures ► IM Snapshot.
3 Click Execute.
3.1.3 WebEM logs

Detailed information about WebEM logs: application logs, console logs (JAVA) and
network logs (HAR)
In case of problems with the connection between WebEM and the SBTS, it is necessary
to collect additional logs from the browser: application logs, console logs (JAVA) and
network logs (HAR). Console JAVA logs contain errors and other debug items that
WebEM saves in the console. HAR log files are used to check HTTP requests and
responses that WebEM sends to and receives from the SBTS.
3.1.3.1 Collecting application logs
Instructions to save application logs
Procedure
1 Open WebEM.
2 In the top menu, go to Options.
3 Click Download application logs.
3.1.3.2 Collecting browser console logs (JAVA logs)
Instructions to save browser console logs

Procedure
1 Open Google Chrome and enter Developer Tools.
2 Open Developer Tools.
Use the keyboard shortcut Ctrl+Shift+I

or
Go to Customize and Control Google Chrome ► More Tools ► Developer Tools
3 Go to Console ► Console settings tab.

4 Check the Preserve log checkbox to ensure that WebEM does not clear the log during
test execution.
5 Reproduce the problem.
6 Select one of the collected log entries and right click on it to open the pop-up menu.
7 Select Save as... to save the collected log.
3.1.3.3 Collecting browser network logs (HAR logs)
Instructions to save browser network logs
Procedure
1 Open Google Chrome and enter Developer Tools.
2 Click the Network tab.
3 Select the Preserve log checkbox to ensure that WebEM does not clear the log during
test execution.
4 Reproduce the problem.
5 Select one of the collected log entries and right click on it to open the pop-up menu.
6 Select Save as HAR with content to save the collected log.

3.1.4 Transport related logs

Information on the collection of logs related to transport and transmission
Transport and transmission logs can be collected using either of the following options:
• Standard Wireshark logging tool
• SR000465: Local and Remote IP Traffic Capturing
3.1.4.1 Wireshark Traces
The standard Wireshark logging tool can be used for traffic capturing.
3.1.4.2 Local and remote IP traffic capturing on Flexi Multiradio 10 and

AirScale
Description of the SR000465: Local and Remote IP Traffic Capturing feature
The SR000465: Local and Remote IP Traffic Capturing feature enables capturing the
ingress and egress of IP traffic such as: control, management and synchronization, and
user plane. It also allows to download the collected traffic data for later root cause
analysis.
Capturing of IP traffic data is supported in two separate ways:
• Streaming mode
The IP packets are streamed to a storage device or a laptop connected to the
Ethernet port of the SBTS (local management port or backhaul interface port). The IP
packets can only be streamed to a storage device connected to the same LAN. The
output data rate of local streaming via local management port is limited to Fast
Ethernet, since the local management port does not support Gigabit Ethernet. Local
streaming towards a transport port supports Gigabit Ethernet.
• File mode
The IP packets are captured into a compressed libpcap file which is stored in the
SBTS RAM. This file can be downloaded using a local or remote connection (for
example with Network Operations Centre). The maximum size of a libpcap file
before compression is 150 MB and it contains the capture history involving only a
limited period of time. The file can be optionally protected with a password. The
reason for holding the libpcap file within RAM instead of flash memory is that the
captured data cannot be hacked in case of SBTS hardware theft.
The SR000465: Local and Remote IP Traffic Capturing feature is configured via WebEM
where the user selects the following options:
• U-plane traffic capturing included or excluded
• Capture Point
U-plane traffic capturing included or excluded

Excluding U-plane traffic capturing maximizes the capturing duration. To maintain end-
user privacy and to comply with legal regulations in certain countries, user plane payload
is never captured. If user plane is selected, only user plane header information is
captured (UE level headers for LTE and transport headers for GSM and WCDMA).
Capture point
Depending on the location of the selected capture point in the traffic path, different traffic
is captured:
• IP traffic to and from the SBTS
At this capture point, the traffic is captured non-fragmented and IPsec decrypted (if
IPsec is in use). The TLS-encrypted M-plane is still encrypted (if TLS is in use). At
this capture point, downlink traffic is not filtered by the system firewall, uplink traffic
has already passed it. Capturing at this point simplifies the troubleshooting since it
allows accessing the decrypted traffic. The capturing does not depend on the used
data link layer protocol (for example Ethernet or IP/ML-PPP).
• IP traffic to and from the SBTS captured at the transport network interfaces
At this capture point, the traffic is captured fragmented and encrypted (if IPsec is in
use). Only the first fragment is captured completely (except the end user plane
payload or the encrypted part of the packet ciphered with IPsec), further fragments of
a packet are captured only with their IP header information.
At both capture points, traffic is captured in both ingress and egress direction.
For more information, see Single RAN / Operating Documentation / Single RAN /
Features / SR000465: Local and Remote IP Traffic Capturing.
3.1.4.2.1 Activating IP traffic data capturing in streaming mode
Instructions to activate IP traffic data capturing in streaming mode
Procedure
1 Log in to WebEM.
2 In the top menu, go to Diagnostic ► IP Traffic Capturing.
3 Select a capture point for IP traffic capturing (Point A or B).
4 Select whether the user plane is included or not.
5 Select Streaming as output option.
6 Select the egress Ethernet port.

7 Provide the destination MAC address of a local laptop or storage device.
8 Click Start to begin the traffic data capturing.
The SBTS raises an IP traffic capturing alarm (61641: IP Traffic Capturing

ongoing on $UNIT, $INTERFACE, $MACADDRESS).
The SBTS streams the captured IP data towards the configured MAC address at the
configured port.
9 Click Stop to end the traffic data capturing.
10 After the capture interval, click the Generate and Download File button to download the
libcap file to the local machine.
Figure 36 IP traffic capturing setup in WebEM for FSMF

Figure 37 IP traffic capturing setup in WebEM for AirScale
3.1.4.2.2 Activating IP traffic data capturing in file mode
Instructions to activate IP traffic data capturing in file mode
Procedure
1 Log in to WebEM.
2 In the top menu, go to Diagnostic ► IP Traffic Capturing.
3 Select a capture point for IP traffic capturing (Point A or B).
4 Select whether the user plane is included or not.
5 Select File as output option.
Filling the Password field is optional.
6 Click Start to begin the traffic data capturing.
The SBTS raises an IP traffic capturing alarm (61641: IP Traffic Capturing

ongoing on $UNIT, $INTERFACE, $MACADDRESS).

7 Click Stop to end the traffic data capturing.
8 After the capture interval, click the Generate and Download File button to download the
libcap file to the local machine.
Figure 38 IP traffic capturing setup in WebEM for FSMF
Figure 39 IP traffic capturing setup in WebEM for AirScale
3.1.4.2.3 Limitations for IP traffic capturing
Detailed information on a set of conditions and limitations related to the IP traffic

capturing functionality
The size of the libpcap file or local stream is usually smaller than the size of the
packets in the network. This occurs for several reasons:

• The maximum size of the libpcap file before compression is limited to 150 MB and
the size of the libpcap file after compression is limited to 40 MB. If the captured
data cannot be compressed into 40 MB, the oldest packets in the capturing history
are dropped.
• The BTS must provide 150 MB in the in-memory storage area. If the memory is
unavailable, the BTS retries the memory allocation procedure for a smaller amount of
data (up to 40 MB). If only 40 MB of data is captured, the size of the compressed
libpcap file decreases to 10 MB. If the captured data cannot be compressed into
10 MB, the oldest packets in the capturing history are dropped.
• A user can include or exclude U-plane traffic capturing. Excluding U-plane traffic
capturing maximizes the capturing duration. To maintain end-user privacy and
comply with legal regulations in certain countries, user-plane payload is never
captured. If the U-plane is included, only user-plane header information is captured
(up to UE-level TCP/UDP headers for LTE and transport headers for GSM and
WCDMA).
• If IPsec is enabled, the encrypted part of the packet is not captured, regardless of
which plane is used (C/U/M/S-plane).
• If IPsec is disabled, the payload of the U-plane IP packet is discarded.
3.2 GSM related logs

A detailed description of the GSM related logs
3.2.1 BTS logs

Guidelines for BTS logs
The type of detected problem or defect determines the level of information and data
collected. Faults can be grouped generally and the type of fault determines what type of
logs or traces is required. The following checklist summarizes the mandatory
requirements for each fault type.
Table 8 Required logs for GSM call processing

Defect BSC SBTS BTS Packet BTS Log BTS Drive
Type Logs SCF Snapshot Abis Internal Test Log
Over PSN Log
Log
WebEM n/a Applicable Applicable n/a Applicable n/a n/a
Commissio Applicable Applicable Applicable Applicable Applicable Applicable n/a
ning
O&M and Applicable Applicable Applicable Applicable n/a n/a n/a
alarm
handling
Telecom Applicable Applicable Applicable Applicable Applicable Applicable n/a
call related
Remote Applicable Applicable Applicable Applicable Applicable Applicable Applicable
Transcoder
/ MGW

Table 8 Required logs for GSM call processing (Cont.)

Defect BSC SBTS BTS Packet BTS Log BTS Drive
Type Logs SCF Snapshot Abis Internal Test Log
Over PSN Log
Log
GPRS / Applicable Applicable Applicable Applicable Applicable Applicable Applicable
EGPRS
KPI Applicable Applicable Applicable Applicable Applicable Applicable Applicable
Changes
g Note: It is very important to ensure that a fault condition exists when the traces or logs
are collected and, if different tools are used, that the clocks are synchronized (or the
time difference is noted).
Collecting BTS snapshots with WebEM
The SBTS snapshots can be collected with WebEM. For more information on how to do
that, see Saving a BTS snapshot file using Web Element Manager.
g Note: While collecting snapshots for GSM issues, LTE cells cannot be selected,
otherwise GSM DSP dump files are not collected. The snapshot must be collected as
early as possible after the issue has been noticed.
IP Traffic capturing and Wireshark logs

For a detailed procedure, see Activating IP traffic data capturing in streaming mode.
g Note: While collecting Wireshark logs for GSM issues from WebEM, it is not required to
select a U-plane option.
In case GSM U-plane traffic is needed, the IP traffic data capture must be collected
outside of the SBTS, in a router or a switch, due to the limitation that only user-plane
header information is captured.
3.2.2 BSC logs

Guidelines for BSC logs
For BSC logs, the BSCLogcol tool is recommended. It collects basic BSC logs including
cellular radio network data, active alarms with alarm history, and BSC measurement
files. It is mandatory to collect logs from the BSC with BSClogcol before any trouble
report is submitted and attach them to the ticket. Internal BSC monitoring is optional.
Measurement file collection is needed for KPI and measurement counter analysis cases,
and to support any analysis with measurement counters.
The Bsclogcol.exe User Interface (UI) provides the following symptom report options:
• Collect basic data
• Collect emergency logs
• Collect basic data and measurements
• Collect basic data and perform database integrity checks
• Collect basic data and measurements and perform database integrity checks
• Collect mcBSC embedded SW info

3.2.3 Tools
A summary of the tools needed for GSM log collection
The following table summarizes the tools needed for the corresponding type of trace or
log:
Table 9 Tools needed for log collection

Required Log BSC Logs & BTS snapshot Packet Abis BTS Drive
Tools BSC & BTS SCF Over PSN Logs Internal Test Log
Measurement Log
files
WebEM n/a Applicable n/a n/a n/a
BSCLogcol tool Applicable n/a n/a n/a n/a
Wireshark n/a n/a Applicable Applicabl n/a
e
BTSLog tool n/a n/a n/a Applicabl n/a
e
Drive Test tool n/a n/a n/a n/a Applicabl
e
3.3 WCDMA related logs

A short description of the WCDMA related logs
3.3.1 Reporting Suite and Default Reports

A short description of Reporting Suite, a useful NetAct tool that provides KPI information
useful in troubleshooting
One of the NetAct tools is Reporting Suite, which supports administration and
maintenance of the network. For troubleshooting purposes, it provides valuable
information about various KPI statistics. Based on the collected KPI statistics, it is
possible to check the exact time when the problem began. It is also possible to check the
decrease and increase levels in the KPIs.
Reporting Suite allows the collection of Default and Custom Reports.
3.3.2 RNC logs

Short description of the types of RNC logs
In some instances, it is necessary to compare alarm history or configuration settings

between RNC and BTS. In such situations, it is recommended to use the special macro
TS-RNC-SW-038, which can be found in NOLS. The macro requires a PC that can
execute an FTP connection to the RNC.

t Tip: There are three types of logs that can be collected by macro: Emergency,
Standard, and Basic. For alarm and configuration analysis, the Basic log version is
enough. The Standard log also includes samples of monitoring messages between the
BTS and the RNC.
3.4 LTE related logs

Short description of the LTE part of the SBTS and symptoms for call processing
problems
Throughout this topic, the term BTS refers to the SBTS and its LTE part and features.
That can be accessed on the SBTS through a browser, such as Google Chrome, at the
URL https://192.168.255.129 when the PC is connected locally to the LMP port of the
SBTS or https:< mPlaneIpAddressDN> when connected remotely.
Symptoms for call processing problems
The following symptoms are related to call processing problems:
Figure 40 Overview of symptoms for call processing related problems
CallEstablishmentFailures/Call
Scenario E2EThroughput/Latency
Drops/HO
NE Log/Trace Log/Trace Drive Labtest BadKPI Drive Labtest
test test
BTSsnapshot
BTS
PMcounters
S1-C,X2-C
BTS-EPC (Wireshark)
BTS-BTS S1-U,X2-U
(Wireshark)
SGi
EPC
S6a
Airitfscannertrace
Uu
UEtrace(basic)
Interface
UEtrace(advanced)
Drivetestreport
Terminal Wiresharktrace
Equipment
Applicationlogs
(jperf,ping,etc.)
Wiresharktrace
Application
Server
Applicationlogs
Legend:mandatory, stronglyrecommended,recommended.
For more information, see Flexi Multiradio BTS LTE / Maintenance Documentation / Flexi
Multiradio BTS LTE Technical Support Notes Library / Flexi LTE BTS Problem Report
Instructions, which applies to both FDD and TD. This document includes:
• A section dedicated to L3 Data collector / Analyzer (Customer EMIL)

• Conditions for SW release upgrade, feature activation, and hardware introductions

• S1, X2, S6a and SGi interface traces
• Symptoms from Uu, UE tracing and Application Server
• Event-triggered symptom data collection (LTE1099), Syslog substring-triggered
automated snapshot collection (LTE2250), and log collection triggered by BTS fault
cancellation (LTE2237).
Configuration is done under the TRBLCADM object: MRBTS ► MNL ► MNLENT ►
TRBLCADM.
• Per Call Measurement Data (PCMD).
g Note: Starting with SRAN 18SP, the Nokia service account toor4nsn with root
privileges is blocked by default. For backward compatibility reasons, it can be activated
to cope with exceptional cases, such as when older scripts with toor4nsn user login
must be executed. As such, customer EMIL traces can only be captured if the
BTS system account permissions enable (systemAcctPermEnable)
parameter value is set to false. Object path:
MRBTS ► MNL ► MNLENT ► FEATCADM
3.4.1 Cell trace

Cell trace content and instructions to activate cell trace
For more information about features related to tracing functionality, see LTE System
Description: Tracing.
3.4.1.1 Cell trace content
Short description of the content of cell trace data
Cell trace data consists of:

• S1 Interface: S1AP data
– Context management
– Handover signaling
– UE capability info indication
– E-RAB management
– NAS transport
– Location reporting
– Error indication
• X2 Interface: X2AP data

– Basic X2 mobility
– Error indication
• Uu Interface: RRC data

– RRC connection signaling
– Counter check
– Inter-RAT mobility

– Measurements
– UE capability
– UL/DL information transfer
g Note: The user plane is not traced.
3.4.1.2 Activating trace
Instructions to activate cell trace, MDT cell trace, or subscriber trace functionality with
Procedure
1 Start WebEM.
2 Go to Configuration ► Configuration Management ► Parameter editor.
3 In Navigation Panel select the Objects tab and go to MRBTS ► LNBTS object.
4 Set the cell trace related parameters.
Configure the following parameters to true:

• Activate cell trace (actCellTrace)
• Activate cell trace with IMSI (actCellTraceWithIMSI)
• Activate MDT cell trace (actMDTCellTrace)
• Activate subscriber and equipment
trace (actSubscriberTrace)
5 Go to the CTRLTS object.
LNBTS ► CTRLTS
g Note: If the CTRLTS object is not present then

a) Create the CTRLTS object.
b) Configure the NetAct IP address (netActIpAddr) parameter.
6 Create an MTRACE object under CTRLTS.
The CRTLTS object contains the basic trace parameters. Every active cell trace
session equals one MTRACE object.

7 Configure the MTRACE object parameters.
To view the cell trace data in a tool other than NetAct, enter the appropriate address
in MTRACE Trace collection entity IP address (tceIpAddress).
Result
The cell trace data can be viewed with the NetAct Traceviewer, L3DA, or Traffica.
g Note: Tracing should be enabled only during troubleshooting procedure time frame, as
it requires a lot of processing resources from the BTS.
3.4.1.3 Viewing and analyzing cell trace data using L3DA
Instructions how to use the L3DA application
Purpose
The following call processing problems can be analyzed using the L3DA:
• Call setup problems
• Call drops
• Handover failures
Before you start

To collect the cell trace data, the tracing must be activated on the BTS.
Procedure
1 Start the cell trace.
To view traces in L3DA, the L3DC IP address must be included in the cell trace
configuration. The cell trace configuration is done with Web Element Manager or the
TraceViewer application. The L3DC must be selected as the Trace Collection Entity
during the cell trace configuration (the L3DC’s IP address put as the
tceIpAddress parameter value).
2 Open the L3DA.
To manage sacks and profiles:

Sub-steps
a) Go to Environment ► Change sack and profile (SCREEN).
b) Select the one you need and click Load.
c) To configure the log paths (and other preferences) go to Tools ► Options.

3 Identify problematic calls by checking the Out cause column.
Every call scenario is displayed in one row. They can be grouped by clicking on one
of the columns in the main window (move the cursor on the column to see its
description). The grouping helps to locate common root causes for failed events.
Columns useful for troubleshooting:
• Out cause
Examples of abnormal call releases:
– No UE Reply
– No EPC Message
– No UE Messages
– Radiolink Failure
– Re-est Reject
• Failure Phase
Examples:
– RAB Active
– RAB Setup
– RAB Access
– RRC Active
– RRC Access
– Source S1 HO Setup
– Target S1 HO Access
• Missing Reply
Examples:
– RachPreamble
– InitialUEMessage
– rrcConnectionSetup
– securityModeCommand
• UE Distance
• HO Attempts
4 To view the scenario details, right-click on the selected row and choose Trace view or
Message view..
The Trace view shows the scenario in an L3 view, Sequence view, or Message
view.
3.4.1.4 Tracing with NetAct
The NetAct TraceViewer application allows the user to activate and configure tracing.
For information on available tools and functions, see the NetAct Operating
Documentation:

• TraceViewer Overview
• Tracing Subscribers and Equipment
3.5 BTSMED
BTSMED related logs
For more information, see Single RAN Operating Documentation / BTS Mediator /
BTSMED Troubleshooting documentation.
3.6 RF related logs

Summary on RF related logs
The SBTS snapshot file contains all the standard RF logs by default. For more
information, see BTS snapshot.

Troubleshooting SBTS Basic troubleshooting steps
4 Basic troubleshooting steps
4.1 Blocking and unblocking BTS units

Blocking and unblocking procedures can be done using Site View or Detailed Site View
functions of Web Element Manager.
Purpose
Many troubleshooting procedures require blocking or unblocking the whole BTS site or
specific BTS units.
This procedure is used to block or unblock
• BTS site
• Radio unit
• Local cells
These procedures can be performed in the Site View or in Detailed Site View in Web
Element Manager.
To block or unblock a BTS unit, do the following:
Procedure
1 In WebEM go to BTS Status ► Site Runtime View ► Site view or Detailed Site View.
2 Select the unit you want to block or unblock and go to the Details pane.
3 Click Block button.

Basic troubleshooting steps Troubleshooting SBTS
Step example
Figure 41 Details pane for the unit selected for blocking or unblocking
Step result
Figure 42 Confirmation window for the blocking or unblocking action of a unit
Result
The selected element is blocked or unblocked.
g Note:
• Blocking a unit may interrupt traffic.
• Unblocking a BTS site and system module causes a reset.

4.2 Resetting BTS units

Resetting procedures can be done using Site View or Detailed Site View functions of
Purpose
Many troubleshooting procedures require resetting the whole BTS site or specific BTS
units.
This procedure is used to reset
• BTS site
• Radio unit
• Local cells
These procedure can be performed in Site View or in Detailed Site View in Web
Element Manager.
To reset a BTS unit, do the following:
Procedure
1 In WebEM go to BTS Status ► Site Runtime View ► Site view or Detailed Site View.
2 Select the unit you want to reset and go to the Details pane.
3 Click Reset button.

Basic troubleshooting steps Troubleshooting SBTS
Step example
Figure 43 Details pane for the unit selected for reset
Step result
Figure 44 Confirmation window for the reset action of a unit
Result
The selected element is reset.
4.3 RAT reset

Resetting procedures can be done using Web Element Manager.
Purpose

Troubleshooting procedures sometimes require only one RAT reset (LTE, WCDMA or
GSM). This can be done in Web Element Manager.
g Note: The RAT reset works only on commissioned technologies.
Procedure
1 Go to Web Element Manager.
2 In the Site Status bar, in the upper-right corner, find the icons for each commissioned
RAT.
Click on to reset the respective RAT.
Figure 45 Site Status bar
4 Confirm the RAT reset.
Figure 46 Reset confirmation

Advanced troubleshooting use cases Troubleshooting SBTS
5 Advanced troubleshooting use cases

Troubleshooting advanced use cases for GSM, WCDMA and LTE technologies in SRAN
and for use cases common for all technologies.
5.1 Common
5.1.1 Software problems
This section contains use cases related to the most common software issues and faults.
Most troubleshooting procedures related to the software faults require:

• downloading software
All available software versions can be downloaded from NOLS, at the following
path Care ► Software Supply Tool.
• checking BTS software version
To check the current software used by the BTS in WebEM, choose Software ►
Software Management ► Software version from the upper menu.
• upgrading BTS software
To upgrade the software using BTS WebEM, choose Software ► Software
Management ► Software Update from the upper menu.
• blocking, unblocking, resetting, or replacing the unit
See Basic troubleshooting steps for more information about these procedures.
5.1.1.1 Viewing software download report
Follow this procedure in case of errors following software update to the BTS.
Purpose
If a software update fails, you can access the software download report to identify why.

Troubleshooting SBTS Advanced troubleshooting use cases
Procedure
1 When SW update failed, click on Save SW Update Report
Figure 47 Software update failed message
The software update report can also be found in the snapshot file
(BTSXXXXX_1011_SWDLreport)
Result
As a result, txt file is downloaded.

Figure below shows an example report. In this example, the software download was
cancelled on user request

Figure 48 Software update report
5.1.1.2 Reset to failsafe partition
Troubleshooting for cases where the module cannot boot up either from an active or
passive partition or when problems appear after a Plug and Play procedure, resulting in
incorrect software download. The following procedures are only for AirScale System
Module and describes the reset to a failsafe partition.
Symptoms
Case 1: The module cannot boot up either from an active or a passive partition - for
troubleshooting procedure see Reset to failsafe partition - case 1.
Case 2: Some problems appear following a Plug and Play procedure and the software is
not downloaded correctly - for troubleshooting procedure see Reset to failsafe partition -
case 2.
5.1.1.2.1 Reset to failsafe partition - case 1
Troubleshooting for cases where the module cannot boot up either from an active or
passive partition. The following procedure is only for AirScale System Module and
describes the reset to a failsafe partition.
Procedure
1 Press the service button.
2 Wait until the unit boots up from the failsafe partition.

3 Download the software again.
4 Update both partitions prior to the commissioning steps.
Result
The unit boots up from the failsafe partition.
Recovery action
To switch back from the failsafe partition to the normal partition quick press the Reset
button or execute a power reset.
5.1.1.2.2 Reset to failsafe partition - case 2
Troubleshooting for cases when problems appear after a Plug and Play procedure,
resulting in incorrect software download. The following procedure is only for AirScale
System Module and describes the reset to a failsafe partition.
Procedure
1 Press the service button.
2 Wait until the unit boots up from the failsafe partition.
3 Repeat the Plug and Play procedure.
Result
The unit boots up from the failsafe partition.
Recovery action
To switch back from the failsafe partition to the normal partition quick press the Reset
button or execute a power reset.
5.1.2 Synchronization problems

This section contains procedures for verification of synchronization.
5.1.2.1 GPS problems – synchronization source not detected
Symptoms

Element manager shows Diagnostic ► Synchronization ► Status ► "Not

available"status under GNSS receiver in Synchronization source and displays the "BTS
reference clock missing" fault.
Recovery procedure
Procedure
1 Check the cable connection at the GPS antenna head.
Verify the GPS cable was securely connected to the GPS antenna head – unplug it
and plug it back in.
2 Check GPS cable connections at surge arrester.
Verify the wiring at the surge arrester follows the documentation. This includes
shielding, color code, and correct pairs.
3 Check the GPS cable's connection to the system module.
In the case of an HDMI connection, ensure that the connector is properly inserted,
reseat the cable, and inspect the HDMI socket in the SM so that there are no bent
pins.
4 If the previous steps did not solve the issue, replace the GPS antenna head.
5.1.2.2 GPS problems – FYGA module is not detected
Symptoms
Element manager shows no FYGA module, or it is grayed out. The synchronization
source is detecting GPS, and the SBTS is not reporting any GPS alarms.
Recovery procedure
Procedure
1 Verify wiring at the surge protector.
Most of the time a missing FYGA module is traced back to a problem with the wiring
in the surge protector. Verify every wire is securely connected to the surge protector,
making sure the wire insulation is not preventing the wire from making good contact
with the corresponding terminal.
2 Check the GPS cable's connection to the system module.
In the case of an HDMI connection, ensure that the connector is properly inserted,
reseat the cable, and inspect the HDMI socket in the SM so that there are no bent
pins.

5.1.2.3 Fallback solution for phase synchronization
The following procedure is a fallback solution in case an FDD-LTE BTS in a phase

synchronization mode is not able to complete startup due to a missing GNSS receiver
control interface.
Purpose
The problem was visible in the field, where as a result of an installation issue with a
GNSS receiver or hardware malfunction, the GNSS receiver control interface
(containing, among others, time of day) is not available to the BTS. Without this
information, the BTS is not able to go to an onAir state. As a solution, the autonomous
switching from a phase to a frequency mode before a system frame number alignment
was introduced.
Procedure
1 The BTS performs phase mode startup.
2 The BTS detects that the GNSS receiver does not provide a sufficient signal to be used
as a phase synchronization reference.
The following faults can be raised:

• 4011 ("GPS receiver alarm: control interface not available")
• 4122 ("GPS receiver alarm: no tracking satellites")
• 4123 ("GPS receiver alarm: survey in progress")
• 4124 ("GPS receiver alarm: no stored position")
• 4125 ("GPS receiver alarm: position questionable")
• 4126 ("GPS receiver alarm: EEPROM invalid")
3 The BTS waits for other phase synchronization sources or for the issue with GNSS to be
resolved, until the timer expires.
Fault 4153 ("Reference clock missing in startup") is raised with additional info that
startup will be continued in a frequency mode with deactivated features.
4 If the BTS is not syncHubSlave in RfSharing, the tuning mode is changed to a frequency
mode.
The BTS deactivates features requiring network-level phase synchronization (for

example OTDOA, eICIC, MBMS, SIB8 broadcast) and features related to inter-BTS
carrier aggregation.
5 The BTS performs frequency tuning.

Result
The BTS goes to an onAir state.

When GNSS becomes available, all GPS receiver alarms and fault 4153 are cleared.
The BTS raises fault 4001 ("BTS reset required"), informing that a manual reset is
required. There is no need to configure the BTS to a phase synchronization mode or
manually enable features dependent on the phase synchronization. Once a manual reset
is done, those features will be on air automatically.
g Note: In case the GNSS receiver self-survey is not yet finished, the GNSS receiver will
not yet start to provide a 1pps/ToD signal to BTS. In case BTS is starting-up during this
phase and BTS is configured for phase synchronization mode, it will complete startup
using frequency synchronization and a manual restart later on is needed to change to
phase synchronization mode. The GNSS receiver self-survey takes about 30 minutes
and is usually only needed after an initial GNSS start-up or a manual triggered deletion
of the positioning data.
5.1.3 Hardware problems
5.1.3.1 Performing routine maintenance tasks
Follow this procedure during routine site visits to ensure that the base station remains in
a good condition.
Purpose
The Nokia BTS design itself is maintenance-free and therefore has no specified regular
maintenance intervals.
Procedure
1 Check whether the maintenance straps inside the module covers are damaged. Make
sure there are no visual defects. Replace worn or damaged maintenance straps.
2 Check the fans and air circulation.
For modules with fans, keep the fans free of leaves and debris. When cleaning the
fans, first remove the power connector from the fan or disable power to the module
(depending on the variant). For all modules, keep air inlets and outlets free of
obstructions to maintain proper air circulation and prevent overheating of the BTS.
Keep the BTS environment clean of dust.
3 Check the connector seals.
Check the connector seals visually. Replace worn or broken seals.

4 Make sure that all connector IP seals, plugs and boots are connected correctly.
• The LMP port or any unpopulated connector openings have IP protection.

Figure 49 LMP IP plug installed
Figure 50 LMP port IP cap not reinstalled after maintenance
• IP seals are firmly fitted around all edges of the IP boot.

Figure 51 Connector IP boot correctly installed firmly in place
Figure 52 Connector IP boot incorrectly installed (IP seals not firmly in place
on any edge)

Figure 53 Connector IP boot incorrectly installed (not pushed all the way in)
• Ensure that cables and connectors are fitted with IP boots.

Figure 54 Cable installed without IP boot
5 Check the antenna line and transmission cable connectors.

6 Check the module fixing screws.
Check the tightness of the module fixing screws. For RRH, also check the tightness
of the solar shield fixing screws. Tighten all loose screws and replace all damaged or
missing screws.
5.1.3.2 Identification of faulty units
This section describes how a faulty unit can be located with the NetAct system.
Finding additional fault-related information in NetAct can be useful for getting diagnostic
info. See the explanations of selected paths below:
Table 10 Explanation of NetAct Diagnostic Info paths

Paths Meaning
<path>= /SMOD-1/FSPC Baseband module (FSP)
<path>= /SMOD-1/bbext1/BBMOD- RF connected to FBBC module

1/rf2/RMOD-3
It means that radio module RMOD-3 is connected
to optical port RF2 on BBMOD-1, which is
connected to port BBEXT1 on system module
SMOD-1.
<path>= /SMOD-1/rf_ext1/SFP SFP on system module

It means that the SFP is connected to optical port
RF_EXT1 on system module SMOD-1.
<path>= /SMOD-1/opt-rf1/RMOD- Fan on RF Module (RFM)

2/FAN
It means that the fan on radio module RMOD-2 is
connected to optical port OPT_RF1 on system
module SMOD-1.
RET <path>= /SMOD- It means that the RET is connected to port ANT1
1/opt_rf1/RMOD-2/ant-1/ALD- on radio module RMOD-2, which is connected to
1/RETU-2 optical port OPT_RF1 on system module SMOD-
1.
g Note: The RET physical unit is present in

the SCF as RETU and belongs to the ALD
object.
g Note: A few RETs may be connected to

one port in chain configuration. There is no
possibility to indicate which RET has failed
in this case.
<path>= /SMOD-1/opt_rf1/RMOD- MHA

2/ant-4/ALD-1/LNA-1

Table 10 Explanation of NetAct Diagnostic Info paths (Cont.)

Paths Meaning
It means that MHA-1 is connected to antenna port
ANT4 on radio module RMOD-2, which is
connected to optical port OPT_RF1 on system
module SMOD-1.
g Note: The MHA physical unit is present in

the SCF as LNA and belongs to the ALD
object. The MHA consists of two LNA
objects.
<path>= /SMOD-1/GNSS GPS on system module

It means that the GPS receiver is on system
module SMOD-1.
<path>= /SMOD-1/syncport/GNSS External GPS

It means that the GPS is connected to the
syncport on system module SMOD-1.
<path>= /SMOD-1/BBEXT-1/BBMOD- SFP on extension baseband module

1/ rf-2/SFP
It means that the SFP is connected to optical port
RF2 on BBMOD-1, which is connected to port
BBEXT1 on system module SMOD- 1.
<path>= /FT Transport module (FT)
g Note: Suffix ‘_R’ describes the unit in

runtime.
Example
48 unitName=FRGT path=/SMOD_R-1(Primary)/rf_ext2/RMOD_R-1
serial_no=L1140707000 additionalFaultID=48 RMOD-2
It means that RMOD_1 is connected to the RF_EXT2 port on SMOD_R-1. The fault
number is 48, serial number of the faulty unit is L1140707000, and this is RMOD-2.
5.1.3.3 Troubleshooting transmission module
This section contains uses cases related to the transmission module problems.
5.1.3.3.1 Dead peer detected (error in SCTP)
The STCP (transport path) errors and red LEDs in the transmission module can be
caused by a cable cut/no cable connection to the interface or by a switched-off port at
the connected far endpoint.

Procedure
1 Check whether the cables are connected to the correct connectors.
2 Check whether the interface at the far-end interface is switched on.
3 Check whether backhaul routers and repeaters are compatible, and whether they are not
faulty.
4 Check if the speed and duplex setting of the BTS port is consistent with the switch port
that is connected directly to the BTS.
For example, they are both "Autodetect" or both "1000 Mbit/s Full duplex."
5 Check whether there are active faults at the far end.
5.1.3.3.2 Ethernet interface is not working
Follow this procedure in case of issues with an Ethernet interface.
Symptoms
• configured Ethernet interface is not working (for example, "Synchronization lost"

message appears)
• Ethernet interface is enabled and configured, but does not carry any user plane
traffic.
Procedure
1 Check that the cables are connected to the correct connectors.
Make sure the connectors are not loose and cables are not bent.
2 Check that the Ethernet interface is enabled.
3 Check that IP configuration is correct.
4 Check that there are no active faults for the Ethernet interface.

Postrequisites
g Note: FSMFr3 is equipped with two integrated transport interfaces: EIF1 and
EIF2/RF/6. The EIF2/RF/6 interface is SW configurable for transport purpose or for
RP3-01 interface. To operate in either (transport or RP3-01), it requires a SFP. In SBTS
the optical interface (EIF2/RF/6) is available as transport interface EIF2 (if not used for
RP3-01 connection).
5.1.3.4 Troubleshooting system module
5.1.3.4.1 Recovering system module with RFS tool
The Restore Factory Settings (RFS) tool restores the software to the factory condition.
As a result, configuration databases are cleaned and recreated, and target unit is started
with a given target SW release in a non-commissioned state.
Purpose
The Restore Factory Settings (RFS) tool can be used in the following situations:
• problems during installation and commissioning (for example HW exchange)
• no access via Web Element Manager
• SW mismatch between different kinds of modules
• failure during SW update
• commissioning is not successful or not possible
• deletion of double-target ID
• restoring vendor certificate
• restoring local account
• restoring service account
Before you start

• The restore factory setting procedure is not related to any hardware configuration.
• No working Web Element Manager connection is required.
• RFS recovery requires a successful ping response at 192.168.255.1/.127/.129/.131.
• Recovery can be started when asystem module is up and running or at the very
same time as system module is started.
• Typically, there is no need to remove any of the power/optical cabling in the existing
BTS setup when using a recovery tool.
Procedure
1 Download desired BTS software from NOLS.
NOLS
2 On your PC, navigate to the folder where the RFS tool is installed.

3 Copy the downloaded software to the BTSSW folder.
Step example
Figure 55 Target BTS software located in the RFS tool directory
4 Connect your PC to the LMP port of the system module.
PC's network properties must match the following settings:

• IP address as 192.168.255.126
• subnet mask as 255.255.254.0
5 Optional: Save the backup commissioning file and/or snapshot of the BTS.
6 Start the RFS tool by clicking RFStool and follow the information displayed on the
screen.
The restoring procedure takes 3 to 18 minutes. Do not power off the system module
during the procedure.
7 Delete certificates.
8 Activate passive SW version.
9 Clear the configuration.
10 Select SW from list you wish to use.
11 Check the target unit's status and commission it.
A backup commissioning file may be useful for this step.

Result
Figure 56 Result view 1




After a successful recovery, the system module is set to default factory settings. If the
problem persists and the BTS cannot reach operational state, it may indicate a more
severe system module issue that cannot be recovered with recovery tool.
After each execution, a report file in TXT format (significant to each system module
based on the serial number and current date or time) is created. The Restore Factory
Settings (RFS) tool report is stored in C:\Temp\logs and includes, on a more detailed
level, the actions and message scenarios between the tool and the target FSM unit. The
RFS report file name is specified by the serial number, product code, current date and
time (for example, L6130705629_084792A.101__20140902_143756.txt). When unit
identification information cannot be retrieved, meaning that access to the system module
is not available or the system module cannot provide the requested information, the
report file does not specify the serial number.
After a successful recovery scenario, a ping response at 192.168.255.129 may
occasionally not be resumed. This may happen when SM RAT is changed during the
restore procedure. An additional power cycle is required to regain access to the SM unit.
g Note: NOTE: This update takes place only on System Module (no on Radio Module).
To make an update on 3 + 4 configuration it is necessary to use RFStool twice.
Separately for FSMF and for AirScale.

5.1.4 Radio module problems

This section contains use cases related to issues with radio modules (RF module/ RRH),
remote antenna tilt (RET), masthead amplifier (MHA) and optical interfaces (SFP
connectors and fibers).
The radio module problems are most likely related to:

• Voltage Standing Wave Ratio (VSWR) or poor Received Signal Strength Indicator
(RSSI)
• fiber connections
• power connections.
5.1.4.1 RRH troubleshooting outline
The following procedure is an overview of the RRH troubleshooting methodology.
Purpose
Follow these steps until the radio module is operational.
Procedure
1 Check all active alarms in the SBTS and follow the information in the on-line help
window.
For more information, see Fault and alarm troubleshooting outline.
2 Check and clean cables between the system module and RF module.
3 Depending on the fault source, reset the RF module and/or system module.
4 Replace the SFP transceivers.
5 Replace RRH.
6 Power down the entire BTS for 5 minutes and then restart it.
7 Check or replace power modules.
8 Replace the chassis.

5.1.4.2 Finding faults in a snapshot file
The following procedure is an overview of troubleshooting methodology using a

snapshot file.
Before you start

In order to follow these steps, you need 7zip and NotePad++ applications (which can be
downloaded out of charge from the Internet).
Procedure
1 Save an BTS snapshot on your computer.
For more information, see BTS snapshot.
2 Unzip the snapshot files using 7zip.
3 Go to the LTEBTS/BTSLogFile or TDLTEBTS/BTSLogFile folder (depending on the BTS

technology).
4 Extract the BTSXXXXX_1011_RawAlarmHistory.txt/.xz file using 7zip and then open

*_RawAlarmHistory.txt using NotePad++.
5 Locate the fault in the *_RawAlarmHistory.txt file.
Using NotePad++, perform the "Find" operation and locate an alarm ID, for example
2004 .
Figure 60 Finding an alarm ID in RawAlarmHistory.txt file

6 Find the source of the fault.
Once you have located an alarm ID, scroll to the right to see "Fault Source." For
example, when you see a line:
2019-Mar-13 11:36:22 (0010) EFaultId_NoConnectionToUnitAl
/MRBTS-1/RAT-1/RUNTIME_VIEW-1/MRBTS_R-1/EQM_R-1/APEQM_R-1/RMOD_R-1
It means that the connection with the module that belongs to the BTS configuration
has been lost.
7 Troubleshoot the issues with identified faulty port.
5.1.4.3 Maintaining optical fibers
Clean fiber optic components are a requirement for quality connections between fiber
optic equipment (for example, system and radio module).
Inspection, cleaning, and re-inspection are critical steps which must be performed before
making any fiber optic connection.
f Always turn off any laser sources before you inspect fiber connectors, optical
components, or bulkheads. Always wear the appropriate safety glasses when required.
Ensure laser safety glasses are used and meet current regulations. They must be
matched to the lasers used within your environment.
Fiber test equipment

The first step in testing the fibers is visual inspection. It is important to check whether the
fiber is not overbend or physically damaged. Excessive bending of a fiber cable can
cause mechanical destruction or micro/macro-bending losses.
g Note: Do not bend optical cables beyond the minimum radius of 70 mm.
An example of a physically damaged optical cable can be seen in the figure below.
Figure 61 Physically damaged fiber
NORMALFIBER DAMAGEDFIBER

More detailed testing can be performed using proper tools. The following equipment is
required to complete a satisfactory fiber testing:
• Visible Light Source – used for checking end-to-end fiber continuity
• Light Source and Power Meter – used for measuring the fiber insertion loss
• Fiber Scope – used for inspecting fiber cleanliness
Figure 62 Fiber test equipment
VisualLightSource FiberScope
LightSourceandPowerMeter
The manufacturer of the equipment can be decided on by the tester, but the equipment
must be capable of successfully and accurately carrying out the required tests.
Cleaning fiber
Cleaning the fiber optic equipment is one of the most basic and important procedures for
maintaining high quality connections.
Any contamination in the fiber connection can cause failure of the component or failure
of the whole system. Even microscopic dust particles can cause a variety of problems for
optical connections. A particle that partially or completely blocks the core generates
strong back reflections, which can cause instability in the laser system. Dust particles
trapped between two fiber faces can scratch the glass surfaces. Even if a particle is only
situated on the cladding or the edge of the end face, it can cause an air gap or
misalignment between the fiber cores which will significantly degrade the optical signal.
In addition to dust, other types of contamination must also be cleaned off the end face.
Such materials include:
• oils (frequently from human hands)
• film residues (condensed from vapours in the air)
• powdery coatings (left after water or other solvents evaporate away).
g Note: With the high-powered lasers now in use for communications systems, any
contaminant can be burned into the fiber end face if it blocks the core while the laser is
turned on. This burning may damage the optical surface enough that it cannot be
cleaned.
The fibers should be cleaned using a dry-cloth cleaner, for example Cletop.

Figure 63 Fiber cleaner
5.1.4.3.1 Cleaning optical fiber
It is important to clean every fiber prior to creating connection. Any contamination in the
fiber connection can cause failure of the whole system.
Before you start

Ensure that you have spare refill cartridges for appropriate fiber cleaning in the field. Do
not reuse old/dirty cartridges.
Procedure
1 Advance the tape belt and expose a fresh film section through the slots in the top of the
Cletop self-contained connector cleaner.
Step example
Figure 64 Example of connector cleaner
2 Hold the fiber optic connector in one hand at 90 degrees to the cassette ferrule guide.
3 Insert the ferrule tip into the first ferrule guide hole.

4 Wipe a single stroke in the direction shown on the instruction label.
Step example
Figure 65 Example of how to clean a fiber
5 Turn the fiber optic connector ¼ turn and repeat the same operation either in the second
guide hole or on a fresh film section.
Step example
Figure 66 Example of how to clean a fiber
g Note: Do not wipe the fiber optic ferrule back and forth in the guide hole and
never wipe more than once over the same film section.
5.1.4.4 Fault ID 3030: Failure in optical interface
This fault occurs when a system module has detected an abnormal operation or a failure
in an optical RP3 interface between system and radio module. There are several
possible fault sources, for example, fiber optical cable, SFP, or individual module.

Description and symptoms
• Fault Failure in optical interface (3030) is active.
Solution
Before the detailed troubleshooting procedure, check if the fault can be solved by:
• troubleshooting other alarms first
• if an alarm appeared after any changes such as
– software updates
– configuration changes
– commissioning
– hardware swap
return to the previous state if possible
• resetting the radio module and system module
If none of these actions help, perform the following steps on site, until the issue is
resolved:
Procedure
1 Check the cables between the system module and radio module.
Dirty optical connectors might cause the signal level to drop excessively. Clean the
cable end, if needed. Ensure that an minimum bending radius has not been
exceeded (excessively tight bending might damage an optical fiber).
2 Make sure that no MultiMode (MM) or SingleMode (SM) optical cable is mixed in the
configuration.
Do not mix the MM and SM optical cable, or SFPs in the configuration. For a quick
visual checking at the site, see table below.
Table 11 Visual identification of SFPs and fibers
Item SM color MM color
SFP "Locking ring" blue black
Connector housing blue gray or black
Cable ID (plain fiber) yellow OM2: orange; OM3: blue-
green
3 Make sure that SFP connectors are the same as suggested in Nokia documentation.

4 Make sure that the same type of SFP connector is used at both ends of the cable.
5 Make sure the cables are connected correctly.
6 Replace the SFP
7 Replace the radio module.
8 Replace the system module.
5.1.4.5 Fault ID 4309 and 4310: Connection unstable
This fault indicates that the RP3 connection between the system and radio module is not
stable at 3 Gbps or 6 Gbps.
• The Connection Unstable At 6Gbps (4309) or Connection Unstable

At 6Gbps (4310) fault is active.
• The transmission to the radio module at 3Gbps or 6Gbps is lost.
• Data is not being transmitted from/to the radio module at all, or, in case of fault
4310, is transmitted at a lower speed (3Gbps).
• The cell(s) supported by the faulty link are disabled, or their operability is degraded.
Solution
g Note: This fault can be triggered by mistake as a result of frequent power on/off cycles
of the RRH (for example, due to testing). If power resets of the RRH are frequently
required, please hold the SBTS at least five minutes in an on-air state before next
power reset.
Procedure
1 If fault "Radio master conflict (4038)" is reported at the same time, troubleshoot it first.

2 Check if the optical transmission network connecting the system and radio module
supports the required transmission speed.
3 Ensure that the cable connecting the modules in connected firmly.
4 Replace the cable.
5 Change the radio module where the unstable link is terminated.
6 If this does not solve the issue, replace the system module.
5.1.4.6 Radio module performs autonomous reset
Radio module is performing autonomous reset.
Solution
Possible cause
This is an expected behaviour. Radio module that was not detected by system module
performs autonomous recovery reset. Recovery reset is initiated after defined time
period. Time period depends on amount of already performed consecutive recovery
resets.
Troubleshooting procedure: Solution
• Connect radio to the system module or power-off the radio module
5.1.4.7 Optical cable connection issue with FRGU, FRMF and FXEE radios
The connection between system module and radio module may be unreliable if the
connector locking mechanism is released when the connector seal is installed.

• loss of optical connection between system and radio module
Solution
It is possible that the shapes of the optical cable connector, the connector seal and the
unit mechanics are incompatible. As a result, the interior of the optical cable connector
seal collides with the connector's locking release latch, releasing the connector locking
clasps.
Figure 67 A. Installing optical cable connector seal B. Collision between connector
seal and latch.
A B
The above scenario is applicable to a specific cable connector. This problematic cable
connector is:
• provided by a vendor, which is indicated on the label of the cable with the marking V6
(for example, with marking Lot: V6 1535)
• on a straight and flexible cable
Problematic and non-problematic connectors are shown in the figure below.

Figure 68 Problematic and non-problematic connectors
Problematicconnectors
Non-problematicconnectors
rigid,pre-bentcable
2-visiblemetalshielding
3-bumpintheback
1-shortconnector 4-openinginthelatch
To solve this issue, the following workaround is proposed:
• Remove the connector locking release latch by using pilers.
Step example
Figure 69 Removing connector locking release latch
Step result
Once the locking release latch of the optical connector has been removed, the
connector can no longer be accidentally unlocked by the connector seal. However,
the connector can also no longer be unlocked and removed from the SFP module by
simply pressing the locking release latch – it can only be released by carefully
pressing down the two locking clasps of the connector, for example, with a small
screwdriver.

5.1.4.8 CPRI-A radio issues in a Nokia network
There are certain permanent differences in the way CPRI-A radios act in a Nokia
network in comparison to an Alcatel network. These differences and potential issues are
explained below.
SFP swapping
After swapping the SFP connectors, the SFP monitoring tool continue to show the data
of the previous SFP instead of the new one. To update the monitoring tool, a reset of the
radio unit is required.
The affected radios are:
• NG2 family (UHID, UHLA, UHMA, UHIA)
• NG3 family (UHHA, UHFB), OEM1 (UNBC, UHBB)
• MH Asset (UHFA, UHBA)
Optical cable swapping between SBTSs

When moving radios between eNBs, the operator must wait 30 seconds after
disconnecting a CPRI link, before inserting the CPRI link in the target eNB. Otherwise,
additional 30 seconds of outage will occur on the moved radio, and 2 minutes 30
seconds outage will occur on another radio in the target SBTS.
The affected radios are: all CPRI-A radios.
Optical cable swapping in the same SBTSs

When moving radios between different ports on the same SBTS, the operator must wait
30 seconds after disconnecting a CPRI link, before inserting the CPRI links into the
target ports. Otherwise, the moved radios will go off-air and remain in an off-air state until
a site reset.
The affected radios are: all CPRI-A radios.
ACF file download

In case of an failed ACF file download, the operator must execute a RET calibration.
Otherwise, the RET will remain uncalibrated after the ACF download.
The affected radio is UHFB and UHED.
Radio alarm rate

For the affected radios it is possible, but very unlikely, that alarm events which exceed a
rate of 10 events per 5 seconds from one radio may not be reported in the alarm event
stream to the eNB.
The affected radios are: UHLB, UHFD, UHLC, UHFF, UHCB.
Radio LEDs
The LEDs indications on certain radios do not follow the standard Nokia LED indication.
However, the graphical representation of LEDs in the BTS Web Element Manager
follows the Nokia standards.

The affected radios are: UHMB, UHHB, UHAA, UHED, UHEE.
RX blocking
The UHIA and UHID radios fail the RX Blocking Sensitive Requirement by
around 2 dB. If the blocker differs more than +/- 2dB from specified blocking level, then
sensitivity meets the requirement.
The affected radios are: UHIA and UHID.
Low voltage alarm

The UHFB and UHHA radios do not report a low voltage alarm for low voltage scenarios.
Overcurrent alarm generation

The UHED ALD Overcurrent Behavior, including radio protection, is normal; except that
the radio does not generate an Overcurrent Alarm.
5.1.5 Finding information about reset reasons in a snapshot file

The following procedure is an overview of troubleshooting methodology using a
snapshot file.
Before you start

In order to follow these steps, you need 7zip and NotePad++ applications (which can be
downloaded out of charge from the Internet).
Procedure
1 Save a BTS snapshot on your computer.
For more information, see BTS snapshot.
2 Unzip the snapshot files using 7zip.
3 Extract the BTSxxxx_1011_blackbox.xz file using 7zip.
4 Open the BTSxxxx_1011_blackbox file.
5 5. Find the following information:
• Reset counter
• Reset reason and timestamp
• Active software version
• Passive software version

Figure 70 Information about reset reasons in the BTSxxxx_1011_blackbox

file.
5.1.6 Antenna line device problems

This section contains use cases related to issues with antenna line devices, remote
antenna tilt (RET), and masthead amplifier (MHA).
5.1.6.1 Antenna line, VSWR, and MHA troubleshooting outline
The following procedure shows steps, which can be performed in case of various
antenna line-related problems.
• There are problems with antenna line functionality, for example active alarms with
MHA`s and VSWR.
• Uplink and downlink power levels are not correct, and do not match with the related
commissioning parameters.
• MHAs are not visible in HW view or Commissioning.

Solution
Procedure
1 Check that the DC power is going to the MHA.
• If MHA is not visible in the HW view or Commissioning, measure DC voltage from

an antenna connector with a proper tool.
• Missing DC voltage indicates a problem in an RF module and an existing DC
voltage problem in either MHA, feeder cable, or connections between the MHA
and feeder cable.
For more information, see the detailed procedure below:
2 Check if the antenna cables (main and diversity) are correctly connected to the correct
ports.
3 Re-check antenna line connectors (7/16” connectors with torque 25 Nm) for loose
connections. Also check the conditions of the cables to see if there is any visible
damage.
4 Use proper instruments for measuring the antenna line, like Site MasterTM Cable and
Antenna analyzer, for verifying if connectors, feeders and antennas are installed
correctly.
5 In MHA problems, first, check that the commissioning has been done properly. Check
that the DC power is going to the MHA.
If the MHA is not visible in the HW view or Commissioning, measure the DC voltage
from an antenna connector with the corresponding tool. Missing DC voltage indicates
a problem in the RF module and an existing DC voltage problem in either the MHA,
the feeder cable, or connections between the MHA and the feeder cable.
6 Check that the VSWR and the antenna line faults, for example, with the Site Master, to
ensure that connectors, feeders, and antennas are connected properly.
A VSWR fault indicates that there are problems in the antenna line devices. Check
that the cables, connectors, MHAs, and antennas match and are not damaged. The
overcurrent fault indicates a short circuit in the antenna line or that the power feed to
MHAs is too low.
7 Check the site on the next working day to ensure that the problem has been solved.

5.1.6.2 Radio Access Server (RAS), Remote Electrical Tilt (RET)

troubleshooting guide
This procedure is designed to help troubleshoot potential problems that may occur
during installation of the following RAS models: FASA, FASB, and FASC (as a
supplement to the installation instructions in the RAS Quick Guide).
Solution
Procedure
1 Ensure that RET and/or RF (BiasT Port) cables are firmly connected to the RAS ports.
2 Cycle the DC power (on ► off ► on).
3 Perform a RET calibration.
Sub-steps
a) If the calibration is successful, set the tilt to maximum angle, then set the tilt to
minimum angle.
b) Repeat tilting actions several times.
c) If the RET operates without alarms and other abnormalities, continue with RAS
installation to the site.
4 If problems continue, upgrade or re-load the latest firmware, and then repeat steps 2 and
3.
5 If problems continue, swap cables and repeat steps 2 and 3.
6 If problems continue, return the RAS to Nokia for inspection using the appropriate RMA
or Red Tag process.
5.1.6.3 RET is not detected
After the commissioning is completed, RET is not detected by the SBTS.

Solution
Procedure
1 Ensure that the correct firmware is installed.
Check the antenna type and verify that the device is updated with the correct
firmware.
2 Disable/enable AISG and DC voltages.
In BTS Web Element Manager, from the main menu go to Configuration ►

Configuration Management ► Commissioning Wizard and disable AISG and DC
voltages, then click the send button. Once the SBTS is back up, re-enable the AISG
and DC voltages and click once again the send button. Verify visibility to the RET
units once the SBTS is back up.
3 Check the connection between antenna line and jumper cable.
There should not be any Bias-T installed between the antenna line and jumper cable.
4 Check if Top Bias-Ts are installed backwards.
If Top Bias-Ts are installed backwards, they should be properly installed. Antenna
crew should go to the top of the tower and fix this.
5 Check antenna line labeling.
Follow antenna lines from an antenna to RF MODULE and make sure the labeling is
consistent. Swap line 1 and line 2 of antenna lines. Top Bias-T should be connected
to the antenna line -1 (according to RF MODULE labeling).
5.1.6.4 RET is not calibrated or it is jammed
After the commissioning is completed, RET is detected by the SBTS, but "Not calibrated"
or "Motor jammed" error is displayed.

Solution
Procedure
1 Un-jam the RET motor by re-calibrating.
Set the RET angle to 0 degrees and try to calibrate RET again.
2 Send an antenna crew up to the tower to un-jam the motor.
This step involves physically un-jamming the RET motor by an antenna crew. If un-
jamming the RET motor does not solve the problem, then replace the RET actuator.
If the RET is still jammed, then the antenna may need replacing.
5.2 WCDMA use cases

This chapters contains troubleshooting procedures (use cases) for most common
problems.
5.2.1 KPI degradation

Follow this procedure to troubleshoot the KPI degradation issue.
Symptoms
After a SW upgrade or a feature enabling, certain KPI or KPI's are degraded.
Procedure
1 Confirm SW upgrade or feature activation time matches the KPI change time stamp.
2 Decompose KPI to raw counters MxxxxCxxx.
For more information on counters, see Single RAN Operating

Documentation > IPARNC and mcRNC > RNC Counters >
Introduction to RNC Counters
3 Check the SW release note (TSN if KPI).
Step result
The counters are changed.

4 Check for changed and new parameters in case of KPI change.
Single RAN Operating Documentation ► IPA-RNC and mcRNC ► RNW

Parameters
Figure 71 Table of parameters
5 Check the number of affected sites.
If even a single site is affected, HW inspection is necessary.
5.2.2 Sleeping cell

Follow this procedure to troubleshoot the sleeping cell issue.
Symptoms
• The end-user is unable to make a call in a given area, despite being OnAir.
• KPI or counter accessibility shows no RRC attempts in a given cell, while cell
availability is 100%.
Procedure
1 Check if there is no mismatch in the cell configuration.
2 Check for HW issues (especially in the antenna line and RF module).
3 Collect a snapshot.
4 Lock/Unlock cell or Reset WCDMA RAT if needed.
For more information, see RAT reset
5 If any specific alarm in RawAlarmHistory (see appeared around the zero RRC attempts
timestamp, set a fault-triggered snapshot collection for recurring scenario.

5.3 LTE use cases

This chapters contains troubleshooting procedures (use cases) for most common
problems.
The table below lists symptoms of the most common issues encountered in the LTE
network. You can find troubleshooting methodology for some of the use cases by clicking
their name. When creating a problem report for Nokia Services, it is recommended to
use the naming the same as in the table below.
Table 12 LTE use cases
Use case category Exemplary symptoms
Management tools • problems with BTS Web Element Manager connection via
problems remote IP address or local management port
• issues with BTS Web Element Manager account
• issues with management tools under Linux
Software problems • software download or activation fails when started from the
NetAct or BTS Web Element Manager
• software fallback fails when performed as a recovery action
Commissioning problems • problems with starting or finishing commissioning

• missing commissioning parameters or units
Synchronization problems • synchronization source / unit not detected

• GPS receiver alarms are present
State change problems • the unit or cell state is incorrect

• changing state of unit or cell cannot be executed
• accidental state change
BTS crash or reset • eNB crashes or reset as a recovery action

• eNB reset as a result of adding new frequency/cell
• eNB continuously performs reset after it boots up
Call processing problem • calls cannot be established

• RACH storms are visible
• high RRC setup failure rate
• certain type of service cannot be activated for an established
call
Cell problems Cell is faulty or cell operation is degraded.

High call drop rate Calls are dropping.
Uplink signal level or quality Interference or signal levels are abnormal, or the IQ constellation is
problems bad.
HO problems Handover-related mobility is not working properly.
Throughput problems The DL or UL throughput is lower than expected or is fluctuating.

Table 12 LTE use cases (Cont.)

Use case category Exemplary symptoms
Paging problem • paging messages are not visible in S1/Iub/Uu interfaces
• paging content is corrupted or IDs are invalid
Call load related Problems related mostly to a high call load coming, for example,
performance issues from mass events. Performance degradation can be seen from
eNB's stability, alarms, or call processing KPIs.
DSP crash A single DSP has crashed.
FSP connectivity/crash The whole FSP has crashed or reset as a recovery action.
Memory consumption Memory consumption is abnormally high or low; memory is leaking.
problems
CS fallback / cell The interoperability between different RAT technologies is not
reselection or redirect working fluently (for example, UEs keep camping in a bad quality
problems network.
Time based problems Different time stamps do not match the NTP time or are not aligned
internally.
ANR problems • ANR is creating an excessive number of neighbours
• neighbour objects are not created or their content is empty
• automatically created neighbours cannot succeed in a HO
S1/Iub/X2 interface Either a link setup fails or link connection is breaking.

problems
Latency problems The measurable time events (for example, ping times, DL/UL
packet delays, signalling responses) are abnormally long.
Alarms problem • eNB has clearly visible problems, but no alarms are visible in
the BTS Web Element Manageror NetAct (for example, unit
resets are seen from logs or the RF carrier is lost, but no
alarms are visible)
• BTS Web Element Manager or NetAct shows an abnormal
number of certain types of alarms
• a certain type of alarms is toggling between 'on' and 'off'
KPI/PM counter problems • counters are not visible in the BTS Web Element Manager or
NetAct
• counters or KPIs are having invalid values, for example,
success rate over 100%
• counters cannot be processed with official tools
Hardware problems Issues related to faulty unit, not working interfaces or recovering
services.
Radio module problems • radio unit connectivity problems
• radio unit crash
Antenna line device Problems with antenna line devices (for example, antenna line
problems devices are not detected, VSWr alarms, RET calibration).
5.3.1 Cell is not in "onAir" state

Follow this procedure to troubleshoot an issue with a cell not coming on air.

Symptoms
After commissioning, HW/SW reset, or unblock, the cells will not go into "On Air" state.
Procedure
1 Verify that BTS and TRS are commissioned.
2 Verify that the cell is unblocked and unlocked.
3 Verify S1 link connectivity.
In case of any problems, there will be an S1 link alarm.
4 Verify that site has a valid timing source.
5 Check for configuration-related issues that need to be corrected by re-commissioning the

site.
6 If problem is not caused by configuration issues, then it is likely an hardware issue. That
means that the unit must be swapped.
5.3.2 Sleeping cell

Follow this procedure to troubleshoot the sleeping cell problem.
Symptoms
According to the element manager or NetAct, the cell is in the "onAir" state, but no calls
can be set up or handed over to the cell. No alarms that would indicate the problem have
been raised.
Procedure
1 Check if KPIs are showing traffic in the cell.
2 Check if there is no mismatch in the cell configuration.
Check the configuration of:

• power levels
• maximum number of RRC connected users

• neighbor cells
3 Check if there are no faulty radio RF cabling or other critical hardware issues.
4 Check the configuration of broadcast information.
UEs might not be able to read the system information required to access the cell.
5 Collect the logs (snapshot, cell traces) and restart the site.
For more information, see RAT reset
Postrequisites
g Note: Follow SR001933: Automatic Sleeping Cell Detection and Recovery feature to
find sleeping cells for LTE.
5.3.3 Call processing problems

This section contains use cases related to the problems with calls processing.
5.3.3.1 Troubleshooting call processing problems
The following generic steps describe a typical call processing troubleshooting procedure.
Before you start

You can use following tools for a call processing troubleshooting:
• KPI data viewer (for example, NetAct Reporting Suite)
• KPI and counter documentation
• cell trace data
• Wireshark logs
• BTS snapshot
Procedure
1 Check which KPIs are indicating bad performance.
2 Check the KPI formula to find out which counters are causing the KPI degradation.
The counter description ('Updated' field) helps to determine the signaling scenario
that affects the degradation. This information is useful to decide which interface
should be further investigated. Details are explained in #unique_149.

3 Check when the KPI degradation started.
Check if any significant activities (for example, a site reconfiguration or SW upgrade)

have been done at the time when the KPI degradation started.
4 Analyze available logs and traces to gather more details.
Based on the counter investigation, the following data can be analyzed:

• call traces: the analysis can be done using the L3DA
• interface monitoring: Wireshark can be used
• BTS snapshot: it can be opened with the element manager
5.3.3.2 Parameters influencing call establishing and processing
In case of any issues related to the calls, check the following cell parameters.
During commissioning, several cell parameters can be configured in such a way that
UEs may be having problems with establishing calls (including emergency sessions), or
problems with calls processing may occur. Tables below list those parameters and
explains their values.
Table 13 Parameters influencing establishing of call
Cell barred flag (cellBarred) The cell barred flag parameter indicates if the cell
status is barred or notBarred. A barred cell is a cell that a
UE is not allowed to camp on, not even for emergency
calls. If a cell on which a UE is currently camped becomes
barred, a cell reselection is triggered.
Cell reserved for operator use Cells reserved for operator use are treated as barred by
(primPlmnCellres) 'normal' UEs without a USIM with AC 11 or 15 inserted.
UEs with AC 11 or 15 USIM inserted are specific operator
UEs and thus allowed to camp on and access such cells.
Table 14 Parameters influencing call processing

Parameter name Meaning
Maximum number of RRC This parameter is a threshold for maximum number of UEs
connections (maxNumRrc) in the cell, which may establish RRC connection. The
maximum value depends on the bandwidth of the cell. The
maximum value depends on the bandwidth of the cell. The
following values are allowed:
• for 1.4 MHz bandwidth: 0–40
• for 3 MHz bandwidth: 0–120

Table 14 Parameters influencing call processing (Cont.)


The default value is not suitable for all bandwidths. The

recommended values are:
• for 1.4 MHz bandwidth: 20
• for 3 MHz bandwidth: 80
Additional active UE with reason This parameter is an additional margin for maximum
radio reason handover number of active UEs in the cell, accessing the cell via
(addAUeRrHo) handover with HO-cause: "HO desirable for radio reasons".
This additional margin is used also for UEs accessing the
cell via hand ver with HO-cause: "Reduce load in serving
cell" but only when Composite Available Capacity (CAC) in
the Cell is bigger than 0. If CAC in the Cell is zero, the HO
for "Reduce load in serving cell" are always rejected. This
margin is added to the threshold maxNumActUe. The
following values are allowed:

Additional active UE with reason This parameter is an additional margin for maximum
time critical handover number of active UEs in the cell, accessing the cell via
(addAUeTcHo) handover with HO-cause: "Time Critical HO". This margin
is added to the threshold maxNumActUe. TThe following
values are allowed:




Maximum number RRC emergency This parameter is a threshold for maximum number of UEs
(maxNumRrcEmergency) in the cell, which may establish RRC connection, used to
admit RRC connections for emergency calls. In order to
give emergency sessions more chance to be established
than normal traffic, maxNumRrcEmergency should be
greater than maxNumRrc + max(addAUeRrHo,
addAUeTcHo). The parameter is only relevant if
actEmerCallRedir is set to "true"
ORactIMSEmerSessR9 is set to "true" and ignored
otherwise.
The emergency call is only recognized when the UE was in
idle state before initiating the connection.
The maximum additional margin depends on the
bandwidth of the cell. The following values are allowed:

Maximum number of active UEs This parameter is a threshold for maximum number of
(maxNumActUE) active UEs in the cell. Active UEs are UEs with at least one
DRB. In case CAT-M UEs are served in the same cell


(hosting cell) and have at least one DRB, the admitted
CAT-M UEs will reduce the number of legacy active UEs
accordingly because they share the same resources.
The maximum margin depends on the bandwidth of the
cell. The following values are allowed:
The default value is not suitable for all bandwidths. User

shall configure this parameter based on different
bandwidth and BTS type. The recommended values are:
g maxNumActUe + max(addAUeRrHo,
addAUeTcHo) must be less than the margin values
for the used bandwidth (see values above
(40,120,840,1000,1250,1500))
Max number act DRB This parameter is a threshold for maximum number of
(maxNumActDrb) established DRBs in the cell. The maximum number of
established DRBs depends on the bandwidth of the cell.
The following values are allowed:



For more information about parameters, see

. When troubleshooting call problems, the state of a cell should also be taken into
consideration. For more information, see System management and State change
problems.
5.3.3.3 Data related to high RRC setup failure rate and RACH problems
This is an example of a call processing troubleshooting area along with examples of

useful data.
Related KPIs
• LTE_5218d Total E-UTRAN RRC Connection Setup Success Ratio

• RRC Connection Setup Failure Ratio per Cause (LTE_5229c, LTE_5230c,
LTE_5590a)
For KPI and counters descriptions, refer to the

.
L3 Data Analyzer indicators
• Out Cause: No UE Reply

• Failure phase: RRC Setup
• Missing Reply: RrcConnectionSetup
Related parameters
• Timer T300 (T300)

• Maximum number of RRC connections (maxNumRrc)
• Maximum number RRC emergency (maxNumRrcEmergency)
g Note: Parameter optimization is a complex task; therefore, it is recommended to use

the Nokia Network Planning and Optimization (NPO) Services.
For parameter descriptions, refer to the .
5.3.3.4 Data related to RAB setup problems
This is an example of a call processing troubleshooting area along with examples of

useful data.
Related KPIs
• LTE_5017a E-UTRAN E-RAB Setup Success Ratio

• E-UTRAN E-RAB Setup Ratio per Cause (LTE_5086a, LTE_5087a, LTE_5088a,

LTE_5089a)
For KPI and counters descriptions, refer to the .
L3 Data Analyzer indicators
• Out Cause: RAB Setup Failure

• Failure phase: RAB Setup
Related parameters
• Max number act DRB (maxNumActDrb)

• Maximum number of active UEs (maxNumActUE)
• Max number QCI1 DRBs (GBRs) (maxNumQci1Drb)
g Note: Parameter optimization is a complex task; therefore, it is recommended to use

the Nokia Network Planning and Optimization (NPO) Services.
For parameter descriptions, refer to the .
5.3.3.5 VoLTE/ViLTE call drops when LTE1321 is enabled in the network
Follow this procedure to troubleshoot an issue with the VoLTE/ViLTE call drops.
The LTE1321:eRAB modification - GBR feature introduces an check on e-RAB-

GuaranteedBitrate (GBR) if the GBR is increased during E-RAB modification. This could
lead to VoLTE/ViLTE call drops during voice/video conference setup phase if the BTS
maximum GBR parameters do not take GBR overhead during voice/video conference
setup into account.
Solution
Possible cause
In releases before FL15A/TL15A, the BTS did not check the e-RAB-
GuaranteedBitrateDL/UL if this E-RAB parameter is changed during E-RAB modification
procedure. With introduction of the LTE1321: eRAB modification – GBR feature, the BTS
is checking whether an increased GBR value is still in the allowed range that is defined
by the Maximum GBR uplink and Maximum GBR downlink parameters in QCI1
and QCI2 parameter tables of the LNBTS object, respectively.
If VoLTE or ViLTE calls are extended to include additional parties or if VoLTE/ViLTE
conference calls are started, the E-RAB modification procedure is used to temporarily
increase the QCI1/QCI2 GBR by a factor of 2 or 3. As a consequence, the GBR
configured by an MME for an existing E-RAB might exceed the “Maximum GBR” as
defined in the BTS configuration (LNBTS object) and the call might be dropped.

In order to avoid this call drop during VoLTE/ViLTE conference set-up, it is recommended
to increase the Maximum GBR uplink and Maximum GBR downlink parameters
in QCI1 and QCI2 parameter tables of LNBTS object to at least 3 times the value used
for a simple (non-conference) VoLTE/ViLTE call in order to have sufficient margin for the
GBR increase during conference call setup.
Troubleshooting procedure: Increasing value of maximum GBR

downlink/uplink using Web Element Manager
Procedure
1 Go to Configuration ► Configuration Management ► Parameter editor
2 In Navigation Panel select the Objects tab and go to MRBTS ► LNBTS object.
3 Under the QCI translation table QCI 1 (qciTab1) set the following
parameters to a value at least 3 times the value used for a simple call.
Parameters:
Maximum GBR downlink (maxGbrDl)
Maximum GBR uplink (maxGbrUl)
4 Under the QCI translation table QCI 2 (qciTab2) set the following
parameters to a value at least 3 times the value used for a simple call.
Parameters:
Maximum GBR downlink (maxGbrDl)
Maximum GBR uplink (maxGbrUl)
5.3.4 BTS crash or reset

This section contains use cases related to problems with BTS crash or restart.
5.3.4.1 BTS in a reset loop
Follow this procedure to troubleshoot the BTS-in-a-reset-loop issue.
Symptoms
The BTS continuously performs reset after it boots up. It gets stuck in a continuous reset
loop, and it is not possible to gather the log files to analyze the fault.

Procedure
1 Check all cables and connectors.
Ensure the connectors are not loose, and cables are not bent.
2 Reboot the RF modules.
3 Switch the power off and turn it on again.
4 If the problem occurred after an SW upgrade, revert to an older SW version.
5 Manually replace the site configuration file.
For more information about uncommissioning manually see Commissioning SBTS/

Uncommissioning/ Uncommissioning manually.

Troubleshooting Sbts 19a

Uploaded by

Copyright:

Available Formats

Troubleshooting Sbts 19a

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting Sbts 19a

Uploaded by

Copyright:

Available Formats

Single RAN, Rel.

Copyright © 2019 Nokia. All rights reserved.

f Important Notice on Product Safety

2 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 3

2.3.10 Test Models.................................................................................. 40

3 Collecting and analyzing troubleshooting data.............................50

4 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

3.3.2 RNC logs...................................................................................... 66

4 Basic troubleshooting steps......................................................... 73

5 Advanced troubleshooting use cases.......................................... 78

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 5

5.1.6.1 Antenna line, VSWR, and MHA troubleshooting outline.............111

6 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 7

Figure 40 Overview of symptoms for call processing related problems............. 67

8 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 9

This is the first issue of the document.

10 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

Figure 1 Troubleshooting methodology

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 11

Network monitoring consists of:

• hardware and software monitoring (using faults and alarms)

2.1 Hardware and software monitoring

2.1.1 Handling faults and alarms

2.1.2 Fault and alarm troubleshooting outline

1 Establish a connection with the BTS using the element manager.

2 Read the fault and alarm information.

12 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

3 Check the unit states signaled by LEDs.

For descriptions of a module's LED states, see LED indications.

2.1.3 Viewing faults and alarms in Web Element Manager

2.1.3.1 Site View

This view shows the layout and related information.

Figure 2 Site View

Elements showed in Site View can by filtered by:

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 13

• Show all ports

2.1.3.2 Detailed Site View

This view shows the layout and related information.

14 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

Figure 4 Detailed Site View

Export Show Show Site

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 15

ALDs can be also sorted by HW type.

16 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

Other icons that might appear on objects:

2.1.3.3 Alarms in WebEM

Access to Active Alarms view: Alarms ► Alarm Management ► Active Alarms

DN09249569 Issue: 01 © 2019 Nokia. Nokia confidential. 17

Details of a selected alarm, such as time of appearance, description, and instructions on

2.1.4 Alarm monitoring in NetAct

• Fault Management Overview and Operations

18 © 2019 Nokia. Nokia confidential. DN09249569 Issue: 01

• Fault Management Helps

2.1.5 LED indications

2.1.5.1 Nokia AirScale System Module LED indicators

List and description of AirScale System Module LED indicators