LTE Troubleshooting in OSS

Nokia Siemens Networks NetAct OSS5.3 CD Set 3

Troubleshooting Flexi Multiradio BTS LTE sites DN0967995 Issue 1-0

Troubleshooting Flexi Multiradio BTS LTE sites

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR 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. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2011/7/6. 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.

The same text in German:

f

Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

Id:0900d805807bcb65

DN0967995 Issue 1-0


Table of Contents This document has 21 pages. 1 1.1 1.1.1 1.1.2 1.2 1.3

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality used in this operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . . Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 2.1 2.2 2.3 2.4 2.5

Overview of NetAct troubleshooting. . . . . . . . . . . . . . . . . . . . Avoiding operational problems. . . . . . . . . . . . . . . . . . . . . . . . Diagnostic tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking application licences . . . . . . . . . . . . . . . . . . . . . . . . Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . .

3 3.1 3.2 3.3 3.3.1 3.3.2 3.4

3.8 3.9 3.10

Troubleshooting Flexi Multiradio BTS LTE sites . . . . . . . . . . . . . . . . . . 13 Prerequisites for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Monitoring network regions to locate faulty Flexi Multiradio BTS LTEs . 14 Flexi Multiradio BTS LTE site alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . 15 iOMS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Checking the event history of the alarming Flexi Multiradio BTS LTE site 16 Checking the status of adjacent Flexi Multiradio BTS LTEs . . . . . . . . . 17 Referring to Alarm Manual for alarm-specific instructions . . . . . . . . . . . 17 Troubleshooting Flexi Multiradio BTS LTE modules using the local management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Generating reports on Flexi Multiradio BTS LTE performance . . . . . . . 18 Resetting the Flexi Multiradio BTS LTE site . . . . . . . . . . . . . . . . . . . . . 19 Initiating recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4

Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.5 3.6 3.7

....... ....... ....... ....... ....... .......

6 6 6 6 6 6

.. 8 .. 9 . 10 . 10 . 11 . 11

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

DN0967995 Issue 1-0

Id:0900d805807bcb65

3


List of Figures Figure 1 Figure 2

4

Overview of the common troubleshooting procedures . . . . . . . . . . . . . . . 9 Troubleshooting Flexi Multiradio BTS LTE sites . . . . . . . . . . . . . . . . . . . 14

Id:0900d805807bcb65

DN0967995 Issue 1-0


List of Tables Table 1 Table 2 Table 3 Table 4

DN0967995 Issue 1-0

Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 How to avoid operational problems in NetAct . . . . . . . . . . . . . . . . . . . . 10 Possible reasons for operational problems in NetAct . . . . . . . . . . . . . . 10 Compatibility levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Id:0900d805807bcb65

5

About this document


1 About this document This document provides you with an example workflow of the tasks performed in troubleshooting Flexi Multiradio BTS LTE in a NetAct regional cluster. Troubleshooting is an activity to detect, locate and correct any kind of equipment, installation, configuration or low performance error. Troubleshooting is based on alarms originated from actual faults and detected in the network monitoring center during the monitoring process.

1.1

Prerequisites This section lists the software and functionality requirements that enable you to perform the operations described in this document. Read this section carefully to avoid future unnecessary troubleshooting.

1.1.1

Supported releases The information in this document is related to the Nokia Siemens Networks software release OSS5.2 CD Set 3. We recommend that you do not use this document with any other Nokia Siemens Networks software releases.

1.1.2

Functionality used in this operation The following NetAct functionalities are used in troubleshooting: Monitor • • • • •

Top-level User Interface Alarm Monitor Alarm History (optional functionality) Modifiable Alarm Manual Trouble Ticket Interface

Reporter •

Report Builder

Other Nokia Siemens Networks functionality •

1.2

Flexi Multiradio BTS LTE Site Manager

NetAct compatibility and capacity information For information on the NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Information document.

1.3

Terms This section provides a brief list of the terms used in this document. If a term or word does not appear in this section, see the Glossary.

6

Id:0900d805807bcb39

DN0967995 Issue 1-0


Term

Explanation

BTS

Base Transceiver Station

DNS

Domain Name System

FM

Fault Management

FTM

Flexi Transport Module

ID

Unique Identification of an Object

LDAP

Lightweight Directory Access Protocol

LTE

Long Term Evolution

KPI

Key Performance Indicator

NE

Network Element

NOLS

Nokia Online Services

O&M

Operation and Maintenance

PM

Performance Management

RAN

Radio Access Network

Table 1

DN0967995 Issue 1-0

About this document

Terms

Id:0900d805807bcb39

7

Overview of NetAct troubleshooting


2 Overview of NetAct troubleshooting This chapter describes the basic principles of troubleshooting, which instructs you how to proceed when you first detect a fault in your system and begin the troubleshooting procedure. You should always read this chapter before using any of the recovery procedures presented in this document. It also briefly describes how you can avoid operational problems. Begin NetAct troubleshooting by checking the items listed in the following figure. You should first determine whether the problem only occurs in some network elements or all network elements. After determining the location of the problem, continue by checking compatibility and licences. You should proceed by first checking the DNS, LDAP, highavailability service and the NetAct processes because they affect the functionality of the entire system. However, the order of the other system checks is random.

8

Id:0900d805807bcb39

DN0967995 Issue 1-0



NE No

Does the problem occur with all NEs?

Yes

Check and compare the configurations of functional and nonfunctional NEs Check when the problem first occured Check and correct open faults

NetAct Check compatibility

Figure 1

2.1

Check licences

Check the NetAct database

Check file systems

Check DNS

Check GUIS

Check hardware

Check LDAP

Check LinAS

Check messaging

Check highavailability solution

Check CIFS/9000

Check user management

Check NetAct processes

Check DCN

Check fault management

Check Oracle processes

Check system level log files

Check performance management

Overview of the common troubleshooting procedures

Avoiding operational problems To avoid operational problems or considerably reduce the amount of trouble situations occurring in your system, see the following table as a quick reference to get to know the maintenance tasks you should carry out to keep your system fully functional at all times.

DN0967995 Issue 1-0

Id:0900d805807bcb39

9



What to do

Why to do it

Regularly perform the maintenance tasks described in NetAct System Administration Routines.

This document describes routine tasks which a NetAct system administrator should perform regularly. When maintenance tasks are performed regularly, problems in the system are less likely to occur.

Install all active NetAct Change Deliveries. Change Deliveries correct detected faults. To avoid these faults in your system, install all Change Deliveries. Read the NetAct Technical Notes.

Table 2

Technical Notes inform you of detected faults and help to avoid possible problems. Technical Notes also contain a correction schedule and indicate which notes are still valid. Technical Notes are available to all users of NetAct on NOLS at http://online.portal.nokiasiemensnetworks.com

How to avoid operational problems in NetAct

The following table lists some of the reasons for operational problems in NetAct: Failure

What can cause it

Hardware

• • •

Application use

Applications are misused.

System configuration

• • •

Software

Problems in the NetAct software

Table 3

2.2

Disk failure Cable problem Power breakdown

Faults in installing Change Deliveries Faults in integration Faults in commissioning

Possible reasons for operational problems in NetAct

Diagnostic tools Diagnostic tools provide a set of automatic and manual tests for detecting problems, analysing the configuration and verifying that NetAct is functioning properly. For more information on using these scripts and detailed descriptions of the tests, see Testing the System Platform.

2.3

Checking compatibility After determining the faulty network elements, check that they are compatible with NetAct. Network elements fall into three categories: fully supported, compatible and not supported. For an explanation on different compatibility levels, see the following table.

10

Id:0900d805807bcb39

DN0967995 Issue 1-0



Compatibility

Description

Support

The defined current (for example, fault management, performance management or configuration management) or relevant parts of the new features and related alarms, measurements and parameters of the new NE release are supported by NetAct releases or Change Deliveries on top of releases.

Compatible

Different releases of NetAct work together (installing a new version does not affect existing functionalities) but no new features, alarms or measurements are supported. You should upgrade NetAct if new functionality of a network element is needed.

Not supported

Combination of different NetAct releases is impossible. You must upgrade NetAct or the network element.

Table 4

Compatibility levels

For the latest information on supported network element releases and currently supporting functions provided for them by NetAct applications, see NetAct and Network Element Compatibility on NOLS at http://online.portal.nokiasiemensnetworks.com.

g

Authentication is required to get access to NOLS.

2.4

Checking application licences Before beginning specific troubleshooting tasks, check that a licence exists for the application or a certain feature. An entry in the licence file lmdlicmx.dat exists for all licensed applications. NetAct uses two different mechanisms for licensing applications: 1. Installation licence The installation licence is used during the installation of the corresponding component or application. For example, PM Aggregation uses an installation-specific licence, which means that all software including database components are missing from the system without the appropriate licence. 2. Run-time licence Run-time licensing means that all software including database parts are installed into the system, but the corresponding application or feature cannot be used without a licence, for example PM-ASCII interfaces and the Alarm Forwarding application. To check the application licence 1. Log into the Data Server with the username omc. 2. In the $OMCPOLICE directory, in the file lmdlicmx.dat, check if the string “LTE_ADAPTATION” exists. For more information about the lmdlicmx.dat license file, see lmdlicmx.dat in System Platform Technical Reference Guide.

2.5

Contacting Technical Support When performing troubleshooting, you can turn to Nokia Siemens Networks Technical Support for help if the problem persists and can not be solved by yourself. In such case,

DN0967995 Issue 1-0

Id:0900d805807bcb39

11



it is suggested that certain files and reports related to the fault be saved and sent to Technical Support for further investigation. With regard to the files and reports needed, contact local Technical Support personnel for further information.

12

Id:0900d805807bcb39

DN0967995 Issue 1-0



3 Troubleshooting Flexi Multiradio BTS LTE sites The troubleshooting operation described in this chapter is based on the assumption that all the preparatory tasks listed in section Prerequisites for troubleshooting have been carried out. The supported releases and functionalities used in this operation are presented in chapter Prerequisites.

3.1

Prerequisites for troubleshooting To efficiently perform troubleshooting tasks on Flexi Multiradio BTS LTE sites and locate faults, carry out the following preparatory tasks in regional network management centers before you start troubleshooting procedures: •

•

•

•

Collect and store fault and performance data. For more information on measurement data management, see Reporter and Performance Management Principles. Create views for the LTE RAN network. For instructions, see Building and Maintaining Views and Creating views in Network Editor Help. Use advanced monitoring techniques for focused monitoring and execute strategies for reducing the alarm flow, for example: • Working sets For more information on creating and using working sets, see Working Set Manager Help. • Maintenance regions For more information on defining maintenance regions for monitoring, see Setting the area to be monitored in Alarm Monitor Help. • Filtering rules For more information on filtering rules, see Creating filtering rules in FM Rule Editor Help. • Alarm trigger rules For more information, see Using Alarm Trigger in Monitoring Principles. • Using Maintenance Mode For more information, see Using Maintenance Mode in Monitoring Principles. Necessary measurements are running and sufficient PM data is available for report generation in the regional databases.

For more information on monitoring tasks and tools as well as alarm reduction, see Monitoring Principles.

3.2

Overview of the operation The following figure illustrates the whole procedure for troubleshooting Flexi Multiradio BTS LTE sites. However, it is possible to find the fault at any phase of the operation. If you are familiar with the detailed steps involved in this operation, you can use the figure as a quick reference to the main phases of the operation. When you need more detailed information on how to perform a particular task, you can access the instructions by clicking the relevant step in the figure.

DN0967995 Issue 1-0

Id:0900d805807bcb39

13



Start

Alarm Monitor/ Top-level UI

Locate faulty Flexi Multiradio BTS LTE

Alarm History

Check event history of faulty Flexi Multiradio BTS LTE

Top-level UI

Check status of adjacent Flexi Multiradio BTS LTEs

Modifiable Alarm Monitor

Check alarm specific instructions

Flexi Multiradio BTS LTE Site Manager

Troubleshoot Flexi Multiradio BTS LTE modules and fetch the BSTechReport

Reporter

Generate reports on Flexi Multiradio BTS LTE performance

Trouble Ticket Interface

Initiate recovery actions

Stop Figure 2

3.3


Monitoring network regions to locate faulty Flexi Multiradio BTS LTEs Alarm Monitor is a key tool for monitoring the network fault situations and alarms in real-time. By dividing the network into regions and then monitoring alarms coming from smaller areas, it is much easier to find the faulty Flexi Multiradio BTS LTE site. Alarm

14

Id:0900d805807bcb39

DN0967995 Issue 1-0



reports can be filtered by maintenance regions, therefore alarms in different maintenance regions can be monitored separately using several windows. Once you receive an alarm in Alarm Monitor, the first task is to locate and identify the fault or the faulty element for more detailed troubleshooting.

t

You can also start the Alarm Monitor application from a managed object’s pop-up menu and monitor only this particular object’s alarms. Another way to select only one Flexi Multiradio BTS LTE site to be monitored is to drag and drop the object into Alarm Monitor and set the Monitoring Criteria to cover only this particular element.

3.3.1

Flexi Multiradio BTS LTE site alarms This chapter provides information on alarms related to Flexi Multiradio BTS LTE sites. Examples of Flexi Multiradio BTS LTE site alarms are listed below. These alarms are originated from the BTS itself. • • • • • • • • • • • • • • • • • •

61006 THE FTM BOOTED AT $DATE DUE TO $RCAUSE 61010 BTS RESET REQUIRED 61030 DEAD PEER DETECTED 61050 MISSING OR NON-COMPLIANT SFP MODULE ON UNIT $U, INTERFACE $I 61058 SYNCHRONIZATION LOST 61073 ROUTING MISCONFIGURATION FOR APPLICATION $A 61104 EBER ON UNIT $U, INTERFACE $IF 61150 LOMF ON SLOT $U, INTERFACE $IF 61400 LICENSE MISSING FOR FEATURE $FEATURE ON INTERFACE $IF 61500 FIVE FAILED LOGINS TO FTM DUE TO WRONG USER NAME OR PASSWORD 7424 EXTERNAL AL 24 7651 BASE STATION OPERATION DEGRADED 7654 CELL OPERATION DEGRADED 7660 BASE STATION LICENCE EXPIRED 7665 BASE STATION TRANSMISSION ALARM 71058 NE CONNECTION FAILURE 71101 OMS ALARM UPLOAD FROM NE FAILED 71103 ID CONFLICT IN BTS O&M CONNECTION

For more information on Flexi Multiradio BTS LTE site alarms, see LBTS Alarms (DN0951924) available on NOLS: http://online.portal.nokiasiemensnetworks.com. For more detailed information on each alarm, see the Modifiable Alarm Manual in Monitoring Principles. Examples of Flexi Multiradio BTS LTE Transport Module (FTM) alarms are listed below. These alarms are triggered by the FTM modules in Flexi Multiradio base stations and they are transmitted via the base station O&M part. • • • •

DN0967995 Issue 1-0

-r-xr-xr-x -r-xr-xr-x -r-xr-xr-x -r-xr-xr-x

1 ccvobadm nms 1 ccvobadm nms 1 ccvobadm nms 1 ccvobadm nms

766 Apr 14 14:04 ama61006.man 417 Apr 14 14:04 ama61010.man 1247 Apr 14 14:04 ama61028.man 529 Apr 14 14:04 ama61050.man

Id:0900d805807bcb39

15


• • •

3.3.2


-r-xr-xr-x 1 ccvobadm nms 787 Apr 14 14:04 ama61150.man -r-xr-xr-x 1 ccvobadm nms 741 Apr 14 14:04 ama61400.man -r-xr-xr-x 1 ccvobadm nms 333 Apr 14 14:04 ama61500.man

iOMS alarms Examples of iOMS alarms for Flexi Multiradio BTS LTE-related failures are listed below: • • • • • •

71000 PM FTP CONNECTION FAILED 71001 MEASUREMENT DATA NOT TRANSFERRED 71003 OMS MEASUREMENT DATA PROCESSING OVERLOAD 71052 OMS FTP CONNECTION COULD NOT BE OPENED 71054 O&M MEDIATION FAILURE 71057 NWI3 NOTIFICATION MISSING

For more information on LTE iOMS alarms, see LTE iOMS Alarms and Troubleshooting(DN0962937) available on NOLS: http://online.portal.nokiasiemensnetworks.com. To locate and identify the faulty Flexi Multiradio BTS LTE site based on an alarm 1. Start Alarm Monitor from Application Manager or from Top-level User Interface. 2. Double-click an alarm in Alarm Monitor to open the Alarm Details dialog if you need more detailed information on the alarm. 3. For information on the original reasons behind BTS alarms and on corrective actions, see the Alarm Manual pages. For instructions, see chapter Referring to Alarm Manual for alarm specific instructions. 4. Locate the faulty element on Top-level User Interface. Check the alarm lists to find the element that has generated the alarm. Concentrate first on the alarms generated by BTS and FTM, and then on the alarms generated by iOMS. Always proceed by targeting the most severe alarm first. After locating the BTS on Top-level User Interface, you can start applications and access the BTS Site Manager. . For instructions on how to navigate through the views on Top-level User Interface, see Navigating through subviews in Top-level User Interface Help. 5. You can also drag and drop the BTS into Alarm Monitor to get the basic information about it. The information in Alarm Monitor tells you the type, ID, name and geographical location(site address and name) of the faulty Flexi Multiradio BTS LTE site.

3.4

Checking the event history of the alarming Flexi Multiradio BTS LTE site You can get information on alarms originated from Flexi Multiradio BTS LTE site by referring to the textual information on alarms in Alarm History. Alarm History provides you with access to all alarms in the faulty Flexi Multiradio BTS LTE site and allows you to create different queries by defining different search criteria. Because the amount of alarms can be significant, search criteria help you narrow down the search. With Alarm History, you can search for alarm history data in a certain maintenance region and make very accurate searches within a precise time frame like one minute. In addition, you can see other alarms that are related to a certain fault. It also

16

Id:0900d805807bcb39

DN0967995 Issue 1-0



tells you how often the fault has occurred in the Flexi Multiradio BTS LTE site through a certain period of time. To check alarm history data of a specific Flexi Multiradio BTS LTE site 1. In Top-level User Interface, start Alarm History. 2. Select Search → Search Criteria. 3. Set the managed object search criterion to include the faulty BTS. 4. Fill in other search criteria, such as the alarm period, if you want to define your search even further. 5. Start the search. You may find the root cause of the fault you are investigating by checking the status of Flexi Multiradio BTS LTE site from a longer time period, such as bad weather conditions, BTS down and so on.

3.5

Checking the status of adjacent Flexi Multiradio BTS LTEs Once you have located the alarming Flexi Multiradio BTS LTE and analysed the alarm data, you should check the adjacent BTSs within the same maintenance region to see if they are affected by something similar. For example, bad weather might cause problems with microwave links and more than one base station might suffer from this influence. In addition to adjacent BTSs, problems in a faulty cell may also be caused by problems in adjacent cells. Investigate the adjacent Flexi Multiradio BTS LTEs to see if they have generated alarms that are possibly related to the malfunction.

3.6

Referring to Alarm Manual for alarm-specific instructions Once the faulty Flexi Multiradio BTS LTE site has been identified, you can take a closer look at the alarm in the Modifiable Alarm Manual application. Alarm Manual contains more comprehensive information on alarms and instructions on how to recover from a failure. To get more detailed information on the fault 1. Start Alarm Monitor (or Alarm History) if it is not yet open. 2. Select the alarm you located earlier. 3. Open the Alarm Manual page, check the alarm information and take corrective actions according to instructions, if possible. The Alarm Manual pages describe the alarms and diagnostic reports. They provide a textual explanation of the reason for an alarm and of its impact.

3.7

Troubleshooting Flexi Multiradio BTS LTE modules using the local management tool The Flexi Multiradio BTS LTE Site Manager provides you with information on a single BTS and helps you locate the fault within the BTS. The Site Manager can be used locally or remotely to see the status and the alarm data of all the modules in a Flexi Multiradio BTS LTE site.

DN0967995 Issue 1-0

Id:0900d805807bcb39

17



You will get more information on alarms and modules by selecting different views or generating history information. The following views are useful in locating and troubleshooting the BTS and its modules: •

• •

g

The Equipment View shows all connected active modules and their state, which helps you locate the faulty module. You immediately see the status of the modules from the LED colour and the number of dot symbols (faulty -red/three dots; degraded - yellow/two dots; working - green/one dot). The Alarm Pane shows the BTS alarms that are generated by itself during a Site Manager session. It shows the current, most recent alarms. Alarm History dialog shows all the alarms that have been saved into the BTS. You can also see alarms other than those saved in the NetAct database.

BSTechReports are also useful for troubleshooting purposes. They can be fetched locally or remotely with the BTS Site Manager. To troubleshoot the faulty modules using the BTS Site Manager 1. Locate the BTS on the Top-level User Interface. 2. Launch BTS Site Manager from the BTS’s pop-up menu. 3. Locate the faulty modules (in Equipment View) and check the status and the alarm data. 4. Correct the fault or contact Nokia Siemens Networks Technical Support.

g

Because of the correlation techniques in the Flexi Multiradio BTS LTE software, only the original cause of the failure is reported, not the secondary alarms which follow the original failure. For more information on troubleshooting Flexi Multiradio BTS LTE modules, see Replacing Flexi Multiradio BTS Units (DN0964047), Maintaining Flexi Cabinet for Outdoor (FCOA) (DN0964059), Maintaining Flexi Cabinet for Indoor (FCIA) (DN0964062) available on NOLS: http://online.portal.nokiasiemensnetworks.com.

3.8

Generating reports on Flexi Multiradio BTS LTE performance The NetAct Reporter functionality is used for generating PM reports of a certain Flexi Multiradio BTS LTE site. The Report Builder application provides you with methods to generate ad hoc and pre-made reports on network performance. With Report Builder you can generate your self-defined reports to visualise the performance data of network elements in a LTE RAN network based on performance indicators of your choice. You can also select different time and object level granularities for your reports according to your needs. For information on how to generate reports with Report Builder, see the application’s help document.

18

t

In addition to analysing single network element with these reports, you can also get a consistent overview of a region as well as locate problematic areas in the network.

t

After a KPI or a report with several KPIs has been created with Report Builder, you can easily access them via the web by using Report Explorer.

Id:0900d805807bcb39

DN0967995 Issue 1-0


3.9


Resetting the Flexi Multiradio BTS LTE site If the error persists or corrective actions require resetting, you can reset the equipment remotely. To reset the element manually 1. In the Top-level User Interface, locate the Flexi Multiradio BTS LTE site object. 2. Open the object’s pop-up menu. 3. Select Reset BTS. 4. If resetting does not help, contact your local Nokia Siemens Networks Technical Support personnel.

3.10

Initiating recovery actions With NetAct trouble ticketing solution, you can initiate recovery actions and make sure that the fault is corrected. Trouble ticketing functionality assists in trouble management by transferring information between NetAct and Trouble Ticket solution. You can create a trouble ticket based on an alarm or a managed object. You can also create tickets without any default information.

g

Trouble ticket creation is an optional feature in Alarm Monitor and it will only work correctly if a complete trouble ticket system has been fully integrated to NetAct. To create a trouble ticket based on an alarm 1. In Alarm Monitor, select an alarm (You can also create a trouble ticket from Alarm History or from the Top-level User Interface) 2. In the Alarm Monitor tool bar, click the Create... icon. The fields in the trouble ticket form are automatically filled in with the information on the alarm and the alarming object. 3. Edit the information, if needed. 4. Click Save. You can follow the status of the ticket in Alarm Monitor. For more information and instructions, see section To create a trouble ticket based on a managed object in Trouble Ticket Interface Help.

DN0967995 Issue 1-0

Id:0900d805807bcb39

19

Where to find more information


4 Where to find more information For more information, see the following NetAct documents: • •

•

•

For more information on Nokia Siemens Networks's monitoring functionality and the concepts associated with managing network fault data, see Monitoring Principles. For more information on Nokia Siemens Networks's reporting functionality and the concepts associated with managing performance data, see Reporter and Performance Management Principles. For more information on Nokia Siemens Networks’s LTE network management functionality and the concepts associated with managing your network configuration, see NetAct Configurator Principles. For more information on tracing subscribers and equipment, see Tracing Subscribers and Equipment and, for general troubleshooting information, see Tracing Principles.

Network element documentation •

20

For more information on related documents for troubleshooting Flexi Multiradio BTS LTE, see Troubleshooting the LTE/EPC System (DN0966512), Troubleshooting the eNB/Flexi Multiradio BTS (DN0966524), Monitoring and Measuring LTE RAN Performance (DN0958759), Measuring LTE RAN System (DN0958762), Tracing LTE RAN System (DN0958774), Real Time Monitoring LTE RAN System (DN0958786), Maintaining Flexi Multiradio BTS Transmission (DN0966509) documents in the LTE RAN System Information Set available on NOLS: http://online.portal.nokiasiemensnetworks.com.

Id:0900d805807bcb39

DN0967995 Issue 1-0


Index A Alarm History 16 Alarm Manual 17 Alarm Monitor 14, 17

B BTS manager resetting 19

C Change Deliveries 10

D diagnostics tools 10

F Flexi Multiradio BTS LTE Site Manager troubleshooting 18

R recovery 19 Report Builder 18 reset 19

S scripts for diagnostic purposes 10

T Technical Notes 10 Technical Support 11 troubleshooting 8

DN0967995 Issue 1-0

Id:0900d805807bcb65

21

LTE Troubleshooting in OSS

Recommend Documents